AVAILABLE SINCE ADD-ON 200 SP3
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.
If the 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:
· STARTDATETIME
· ENDDATETIME
· CHARGEOPTION
· BREAKINMINUTES
· SAPOBJECTKEY
A message encourages the user to manually update the related document (e.g. a CATS entry). No new CATS/confirmation is created/updated in such a case.
If the time effort was not updated (no comparison-relevant idoc field was changed), no confirmation/CATS is created/updated. 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.