Ansicht
Dokumentation
/SAPAPO/OM_CUS_ORDER_CHANGE - Create, Change, or Delete Sales Orders
Addresses (Business Address Services) Addresses (Business Address Services)This documentation is copyright by SAP AG.
Further information
@0P@Schedule Lines
Functionality
This module creates, changes, or deletes schedule lines of sales orders. It only supports orders with one of the following order types:
| DEC | HEX | Constant | Description | ||
|---|---|---|---|---|---|
| 51 | 33 | gc_om_forecast_order | Forecast | ||
| 52 | 34 | gc_om_sales_order_consumption | Sales order with consumption | ||
| 53 | 35 | gc_om_sales_order_no_cons | Sales order without consumption |
liveCache converts each schedule line of a sales order into a suborder with a dummy activivity and an input node.
How It Works
The schedule lines passed in the table IT_SCHEDULE_LINES are processed in accordance with the appropriate method (field METHOD):
| Value | Constant | Description | |
|---|---|---|---|
| N | gc_new | Adds the schedule line with the key SCHEDULING_LINE to the order with the key ORDERID. This order is created implicitly if it does not exist. | |
| C | gc_change | Deletes the schedule line with the key SCHEDULING_LINE and creates it again with the specified data. | |
| D | gc_delete | Deletes the schedule line with the key SCHEDULING_LINE from the order with the key ORDERID. The order is deleted implicitly if no longer has any schedule lines. | |
| R | gc_delete_order | Deletes the order with the key ORDERID with all its schedule lines. |
The keys of orders deleted explicitly by the method gc_delete_order or deleted implicitly by the deletion of their last schedule line are written to the table ET_DELETED_TOP_ORDERS.
The table ET_CHANGED_TOP_ORDERS contains the orders that still exist and in which schedule lines were created, changed, or deleted.
When schedule lines are changed or deleted, fixed pegging edges can also be deleted. These deletions are returned in the table ET_DELETED_FIX_PEGGING.
Notes
Error Handling and Troubleshooting
Possible return codes:
- 54 = om_duplicate_order:
An order with the key ORDERID or a schedule lines with the key SCHEDULING_LINE already exists in liveCache.
- 40 = om_invalid_order:
The schedule line or order in question does not exist in liveCache.
- 10 = om_invalid_order_type:
Invalid or unsupported order type. Only the order types listed above are valid.
Parameters
ET_CHANGED_PEGIDSET_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_INPNODE
IT_ORDKEYS
IT_ORDMAPS
IT_POSITIONS
IT_SCHEDULE_LINES
IV_SIMSESSION
IV_USE_IO_SHLF_LIFE
Exceptions
LC_APPL_ERRORLC_COM_ERROR
LC_CONNECT_FAILED
Function Group
APO/SAPLOM_CUSTOMERPERFORM Short Reference ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 6142 Date: 20240420 Time: 064242 sap01-206 ( 58 ms )
