Ansicht
Dokumentation
BAPI_POSRVAPS_SAVEMULTI2 - Obsolete: Create or Change One or More Procurement Items
ROGBILLS - Synchronize billing plans CPI1466 during BackupThis documentation is copyright by SAP AG.
Successor function: BAPI_POSRVAPS_SAVEMULTI3 ("SaveMultiple2").
Functionality
This method can be used to create or change procurement orders.
Via the individual parameters you can either create or change a procurement order with receipt elements only (output node) or with both, receipt and issue elements (output and input nodes).
If you are using this function for the first time, you can find detailed documentation under the following important information.
Notes
You have the following options for creating or changing an order:
- Using external number assignment:
- Specify ORDER_NUMBER + ORDER_TYPE
A GUID is assigned internally. The order is displayed in the APO System with the ORDER_NUMBER. In the mapping table the GUID is returned with which the order was created.
- This is only possible for the active planning version.
- Using internal number assignment:
If an order is created with an internal order number, it has the order type "APO local order" (domain fixed value 8)
- Specify ORDER_NUMBER.
A GUID and an internal order number are assigned internally. The order is displayed with this internal order number in the APO System. The GUID and the internally assigned order number, together with the transferred ORDER_NUMBER, are returned in the mapping table. The ORDER_NUMBER transferred is only used for assignment in the mapping table and is not used in the APO System in this case.
- Specify ORDER_NUMBER + ORDID
The system reacts in the same manner as when only the ORDER_NUMBER is assigned. The difference is that no new internal GUID is assigned. Instead, the transferred ORDID is used.
If the released order (ORDER_NUMBER for external number assignment) or the released ORDID already exists for the BUSINESS_SYSTEM_GROUP used, the order will be changed automatically.
With the parameter NO_CREATE the reaction can be thus changed that in case an order does not exist, an error message is released and the order is not created.
Attention:
- Transaction behavior:
Note that this function can carry out an automatic COMMIT WORK or ROLLBACK WORK, depending on the COMMIT_CONTROL parameter.
- Orders that are still able to be changed (on a plan basis) in APO (for example, by an optimization or heuristic), may only consist of one item and schedule line. This is normal for APO local orders and purchase requisitions (ORDER_TYPE = '1') because APO should be able to change or delete these automatically. If an order of this type consists of several items or schedule lines, APO cannot plan it automatically (that is, change or delete it).
- Note that an "APO local order" (domain fixed value 8) cannot be addressed using its external number. Instead, you must use its GUID.
Messages are returned in the Return parameter. The parameter documentation shows the return codes and their meanings.
Further information
Parameters
COMMIT_CONTROLEXTENSION_IN
EXT_NUMBER_ASSIGNMENT
LOGICAL_SYSTEM
MAPPING_DATA
NO_CREATE
ORDER_TYPE
PLANNING_MODE_USAGE
PLANNING_VERSION
RECEIPTS
RECEIPTS_X
REQUIREMENTS
REQUIREMENTS_X
RETURN
Exceptions
Function Group
10502RFUMSV00 - Advance Return for Tax on Sales/Purchases CPI1466 during Backup
This documentation is copyright by SAP AG.
Length: 5149 Date: 20240523 Time: 154749 sap01-206 ( 87 ms )
