| Status | ||||
|---|---|---|---|---|
|
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.
Display information about time effort changes
| Status | ||||
|---|---|---|---|---|
|
| Info |
|---|
If the setting ‘Upd Rel Docs’ is disabled in transaction /PACG/ECM_CTET - Time Effort Type, or FSM Cloud Connector version (S4)PACG 200 SP03 or SP04 is installed (the setting was not yet available). |
If the time effort was updated (idoc data differs from the data stored in the special table), the idoc is set to status 51.
...
In both cases a generic idoc should be sent to SAP FSM.
Cancel the related CATS/confirmation entries and create new ones
| Status | ||
|---|---|---|
|
| Info |
|---|
If the setting ‘Upd Rel Docs’ is enabled in transaction /PACG/ECM_CTET - Time Effort Type |
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 cancelled, 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.
Prerequisites
‘Check GUID on input’ should be disabled in the inbound class assignment transaction (/PACG/ECM_CLSASSIGIN -FSM Connector's Incoming Messages Configuration):
...