Ansicht
Dokumentation
BAPI_MOSRVAPS_CREATESNPORDER - Create or Change orders with SNP PPMs
Fill RESBD Structure from EBP Component Structure BAL_S_LOG - Application Log: Log header dataThis documentation is copyright by SAP AG.
Functionality
With this method you can create or change orders with SNP-PPMs.
To create an order, a production process model (PPM) of type SNP must exist. The system uses the PPM to generate the order. The order structure (components, operations, durations, capacity requirements, and so on) is determined on the basis of the PPM explosion. If a valid PPM does not exist and the CHECK_PPM_EXISTENCE parameter is set, the order is not created and an error message is returned. If the CHECK_PPM_EXISTENCE parameter is not set, the order is created without PPM.
If you are using this function for the first time, you can find detailed documentation in the following important information.
Notes
,,If you want to create or change an order you have the following options:
- With external number assignment
- ORDER_NUMBER + ORDER_TYPE entered.
The system assigns a GUID internally. The order is displayed in the APO System with the ORDER_NUMBER. In the mapping table the system returns the GUID with which this order was created.
- This is only possible for the active planning version
- With internal number assignment
If an order is created with internal number assignment, it is given the order type "APO local order" (fixed value 8).
- ORDER_NUMBER entered.
The system internally assigns a GUID and an internal order number. The order is displayed with this internal order number in the APO System. In the mapping table, the system returns the GUID and the internally assigned order number together with the transferred ORDER_NUMBER. The transferred ORDER_NUMBER only determines the assignment in the mapping table and is in this case not used in the APO System.
- ORDER_NUMBER + ORDID entered.
The system behaves in the same way as if you had only entered the ORDER_NUMBER. The only difference is that the system does not assign a new GUID internally, but instead uses the ORDID you transferred.
Attention:
- Note that you cannot call an "APO local order" (fixed value 8) by its external number (if you want to change it). You must only use its GUID.
- If you want to access an order via its GUID set EXT_NUMBER_ASSIGNMENT to internal number assignment.
- Note that orders with SNP-PPMs are created or changed via SNP applications. That means that no PP/DS planning settings are used (for example scheduling, automatic planning, etc.) and not all methods for PP/DS (for example confirmations) can be used for such an order. planning). It always uses backward scheduling. Also note that because There is always backward scheduling.
- Orders that were previously created with other PPM types (for example, PP/DS PPMs) cannot be changed using this BAPI. Only orders with identical PPM types can be changed.
- When an order is changed this always results in a new PPM selection and explosion. The existing order is completely replaced by the new order. If the order was created by another application than SNP (for example, CTM) the application specific values (such as priority in CTM) are not retained.
- Transaction behavior:
Note that the method can automatically execute a COMMIT- or ROLLBACK WORK, depending on the COMMIT_CONTROL parameter.
Messages are returned in the Return parameter. The parameter documentation shows the return codes and their meanings.
Further information
Parameters
CHANGE_IF_EXISTSCHECK_PPM_EXISTENCE
COMMIT_CONTROL
EXTENSION_IN
EXT_NUMBER_ASSIGNMENT
LOGICAL_SYSTEM
MAPPING_DATA
ORDER_HEAD
ORDER_TYPE
PLANNING_VERSION
RETURN
SNP_PLANNING_PROFILE
Exceptions
Function Group
10503Vendor Master (General Section) PERFORM Short Reference
This documentation is copyright by SAP AG.
Length: 5501 Date: 20240523 Time: 182509 sap01-206 ( 89 ms )
