Page Comparison

Time efforts can be modified in SAP FSM using a business rule. Updated time efforts will be compared to their initial versions in SAP ECC/S4. Depending on the setting ‘Upd Rel Docs’ in transaction /PACG/ECM_CTET - Time Effort Type, different actions will be performed.

Prerequisites

‘Check GUID on input’ should be disabled in the inbound class assignment transaction (/PACG/ECM_CLSASSIGIN -FSM Connector's Incoming Messages Configuration):

...

To enable storing time efforts in the special table, setting ‘No book E4C’ should be disabled in transaction /PACG/ECM_CTET - Time posting settings. If the

Display information about time effort changes

If a time effort was updated (idoc data differs from the data stored in the special table), the idoc is set to status 51.

Changes in the following idoc fields are compared:

...

If the time effort was modified in SAP FSM but no comparison-relevant idoc field was changed, no confirmation/CATS is created/updated either. A message informs the user that the object was updated but this change is not relevant for SAP ECC/S4.

...

Additional remarks

To enable time effort comparison, all new and successfully processed inbound time efforts are stored in table /PACG/ECM_ALTEW. Time efforts not meant for postponed booking, do not have any ‘reason’ value and contain SAPKEY.

...

To enable storing time efforts in the special table, setting ‘No book E4C’ should be disabled in transaction /PACG/ECM_CTET - Time Effort Type:

...

Detailed example with technical insight

Create a time effort on the mobile app:

...

. Information about a new entry added to table /PACG/ECM_ALTEW can be found in the inbound time effort idoc:

...

. The entry in table /PACG/ECM_ALTEW should exist and contain SAPKEY:

...

Depending on settings in /PACG/ECM_CTET, a CATS entry or confirmation should be created.

...

Before updating the time effort using a business rule, make sure that the following company setting is set to true:

...

Create a simple business rule which would update the time effort’s start and end date:

...

. An inbound time effort idoc should contain updated data and a SAPID:

...

. Its logs inform the user about the updated time effort data, point to the relevant document, and encourage the user to update it manually. 

...

Table /PACG/ECM_ALTEW should not be updated:

...

In case of updating the time effort in FSM and no change to the comparison-relevant idoc fields, the following logs are displayed:  

...

In both cases a generic idoc should be sent to SAP FSM.

Cancel the related CATS/confirmation entries and create new ones

The following time effort properties are compared during inbound processing:

·       STARTDATETIME

·       ENDDATETIME

·       CHARGEOPTION

·       BREAKINMINUTES

·       SAPOBJECTKEY

If any of these properties was modified in FSM after synchronization with SAP (e.g. with a business rule):

·       CATS are used - CATS entries created based on this time effort will be set to status 60 (cancelled), then new ones will be created

...

·       Confirmations are used – confirmations created based on this time effort will be reverted, then new ones will be created

...

The logic also supports splits and breaks, i.e. cases when out of one inbound time effort, multiple CATS/confirmation entries are created. In such a case, all of them would be cancelled and re-created (for technical reference, see table /PACG/ECM_ALTEWS).

If none of the relevant properties were changed in FSM, CATS/confirmations will not be affected. A message informs the user that the object was updated but this change is not relevant for SAP ECC/S4.

...

If posting date is no longer relevant for an object (closed periods), then the affected objects should be corrected manually.