Ansicht
Dokumentation

/SAPAPO/OM_TRANS_ORDER_CHANGE - Create/Change/Delete Stock Transfer Delivery Objects in liveCache

/SAPAPO/OM_TRANS_ORDER_CHANGE - Create/Change/Delete Stock Transfer Delivery Objects in liveCache

BAL_S_LOG - Application Log: Log header data   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

This function creates, deletes, or changes the transportation schedule lines specified in the table IT_SCHEDULE. The operation to be performed depends on the data in the METHOD field in IT_SCHEDULE:

  • If METHOD = GC_NEW:
The transportation schedule line with the key SCHEDULING_LINE is created for the order specified in ORDERID. If the order with the key ORDERID does not exist, it is created.
  • If METHOD = GC_DELETE:
The transportation schedule line with the key SCHEDULING_LINE is deleted. If it is the only schedule line in the order, the order itself is also deleted.
  • If METHOD = GC_CHANGE:
The transportation schedule line with the key SCHEDULING_LINE is deleted and created again with the specified new attributes.
  • Falls METHOD = GC_DELETE_ORDER:
The complete deployment stock transfer with the key ORDERID is deleted, with all its schedule lines.

ET_RC contains return codes for schedule lines with processing errors.

If required, fixed pegging relationships are deleted when schedule lines or orders are deleted or changed. These deleted relationships are returned in the table ET_DELETED_FIX_PEGGING. If you want to recover them, this is the responsibility of the calling program.

If top level orders have been deleted (explicitly with the method GC_DELETE, or implicitly when the last suborder in the affected top level order was deleted), their keys are returned in the table ET_DELETED_TOP_ORDERS.

Example

Notes

Return codes (see table ET_RC):

  • om_duplicate_sched_key:
A transportation schedule line with this key already exists in liveCache (if METHOD = GC_NEW).
  • om_invalid_sched_key:
No transportation schedule line with this key exists in liveCache (if METHOD = GC_CHANGE or METHOD = GC_DELETE).
  • om_invalid_order:
No transportation order with this key exists in liveCache (if METHOD = GC_DELETE_ORDER).

Further information





Parameters

ET_CHANGED_TOP_ORDERS
ET_DELETED_FIX_PEGGING
ET_DELETED_TOP_ORDERS
ET_RC
IS_ATP_INFO
IS_GEN_PARAMS
IT_CHARACT_REQ_INPNODE
IT_CHARACT_VAL_OUTNODE
IT_ORDKEYS
IT_ORDMAPS
IT_SCHEDULE
IV_SIMSESSION

Exceptions

LC_APPL_ERROR
LC_COM_ERROR
LC_CONNECT_FAILED

Function Group

APO/SAPLOM_TRANSFER

General Data in Customer Master   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 2875 Date: 20240523 Time: 062036     sap01-206 ( 48 ms )