/PACG/ECM_I_MSG_T – E4C: Messages for Time Effort with send back to the cloud

Open

This transaction allows re-sending time efforts back to Time&Material Journal for approval/additional changes if an error occurred during inbound idoc processing.

See also /PACG/ECM_I_MSG_E – Messages for Expense with send back to the cloud , /PACG/ECM_I_MSG_A – Messages for Material which with send back to the cl

Prerequisite

Maintain the following entry in transaction /PACG/ECM_APRVT:

Open

When an error occurs, a generic idoc with a relevant syncStatus (‘REQUIRES_APPROVAL’ or ‘REQUIRES_CHANGE_FOR_APPROVAL’) is sent to FSM. Apart from that, an Approval object idoc with decisionStatus (‘PENDING’ or ‘DECLINED’) is sent. Prerequisite for the error message is a special UDF whose name is entered in transaction /PACG/ECM_MSG_U - UDFID for Cloud Message Type:

It should also be added to screen configuration in SAP FSM for each relevant object:

Example

Pending

If an inbound time effort idoc runs into errors, message 002 of class LR will be searched for. Such a time effort will be resent to FSM as pending, with the mentioned message as approval remark.

Create a time effort. Approve it and block the CATS transaction to make sure the error above will occur.

Notice that a deletion idoc for the initial generic was sent, as well as a new generic with syncStatus and an outbound Approval object.

The time effort is now pending again in the Time&Material journal.

Requires change

If an inbound time effort idoc runs into errors, message 002 of class LR will be searched for. Such a time effort will be resent to FSM as requiring technician’s change, with the mentioned message as approval remark.

Create a time effort. Approve it and block the CATS transaction to make sure the error above will occur.

Notice that a deletion idoc for the initial generic was sent, as well as a new generic with syncStatus and an outbound Approval object.

The time effort is now requiring change in the Time&Material journal.

Technical remarks

After error inbound idoc processing, a deletion idoc for the initial generic is sent. Then a new generic idoc, with syncStatus is transferred, together with an Approval object idoc. The following table describes property values for the mentioned fields, depending on the target T&J status: