Ansicht
Dokumentation

BAPI_SLSRVAPS_SAVEMULTI2 - Create or Change Sales Orders

BAPI_SLSRVAPS_SAVEMULTI2 - Create or Change Sales Orders

BAL_S_LOG - Application Log: Log header data   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

You can use this method to create or change a sales order or the items and schedule lines it contains. If the order or item/schedule line does not yet exist it is created, otherwise it is changed.

The NO_CREATE parameter can be used to change system behavior in such a way that an error message is issued if the order does not already exist and a new order is not created.

Create sales order or schedule line:

  • To create a new sales order or schedule lines, use the following fields as the key: ORDER_NUMBER, ITEM_NUMBER, and SCHED_LINE. Leave the fields ORDID and SCHEDID empty because these are assigned by SAP APO.

Change sales order or schedule line:

  • Created by external system:
    If you want to change a schedule line that you previously created using ORDER_TYPE, ORDER_NUMBER, ITEM_NUMBER, and SCHED_LINE, use these keys again to change the schedule line. As before, leave the ORDID and SCHEDID empty.

If you are using this function for the first time, you can find detailed documentation in the following important information.

Notes

  • Sales orders (for example in VMI scenarios) that were created in APO and that were not transferred from an external system cannot be changed using this interface.
  • Note also the following restrictions for certain (internal) order types.
  • Transaction behavior:
    Note that this function can automatically carry out a COMMIT WORK or ROLLBACK WORK depending on the settings made in the COMMIT_CONTROL parameter.

Messages are returned in the Return parameter. The parameter documentation shows the return codes and their meanings.

Further information

  • For standard scenarios or to create a sales order, it is sufficient to fill the import parameter and the table parameters REQUIREMENTS and REQUIREMENTS_X. All other table parameters are intended for specific cases or R/3 scenarios.




Parameters

ATP_EXTRA_FIELDS
ATP_QUOTATIONS
ATP_REQUEST_KEYS
CFG_BLOB
CFG_HEADERS
CFG_INSTANCES
CFG_PART_OF
CFG_REF_OBJECT
CFG_VALUES
CFG_VAR_KEYS
COMMIT_CONTROL
DOCUMENTS
DOCUMENTS_X
EXTENSION_IN
LOGICAL_SYSTEM
NO_CREATE
ORDER_TYPE
PLANNING_MODE_USAGE
REQUIREMENTS
REQUIREMENTS_X
RETURN
SHIP_INFO

Exceptions

Function Group

10501

General Material Data   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 4767 Date: 20240523 Time: 151803     sap01-206 ( 59 ms )