Network order integration has been designed with one of our customers in mind. In order to avoid misunderstandings or issues, we strongly recommend implementing it only with Proaxia’s Expert Support.
This is a project-spefic (PS integration) version of transaction /PACG/ECM_CKDET - Control key determination.
Define which control keys (in combination with network order types) are relevant for activity transfer to SAP FSM. First consideration is given to the setting which are responsible for definition of network definition (/pacg/ecm_sctdo). In that customizing must be entered row with same network type and also has marked ‘Active’ field. The important thing to note is that the transaction is about determining the value when creating a copy of the activity in FSM. If an activity was created in FSM without any reference, then the determining field is 'No new operation' in /pacg/ecm_sctdo. Details are shown in the table:
Create AE | Customize if a new (copied in SAP FSM) activity should be assigned to the same operation as the source activity (option ‘N') or if a new operation should be created for this activity (option ‘Y’). Field ‘No new operation’ from /pacg/ecm_sctdo must be active to use this option. |
|---|---|
Update Act (S4) PACG 200 SP06 | Allow to set up in which situation activity can be modified or it has blockade. in case the activity is blocked then any modifications will remain on the FSM side without interfering with the data presented in SAP. There are 4 provided scenarios:
Working of this option depends on the settings in /pacg/ecm_sctdo. Field ‘Actualize Operation’ must be checked when activity will be updated in SAP/FSM. |
Res. cntr. key | If the field ‘Create AE’ is set to ‘Y', a new control key can be specified for the new operation. |