Ansicht
Dokumentation
BAPI_MOSRVAPS_MERGEPPE - Method for Grouping Orders Into One Order
General Material Data BAL Application Log DocumentationThis documentation is copyright by SAP AG.
Functionality
iPPE-based APO orders can be merged using this method.
In order to merge orders, the orders must be created using iPPE-based model and released. The information of the surviving and merging orders is sent in the table parameter ORDER_HEAD.
You may provide the reporting points mapping information between surviving order and merging order(s) in the table parameter RP_MAPPING.
Notes
Depending on the settings in the COMMIT_CONTROL parameter, the function may automatically execute a COMMIT or ROLLBACK WORK.
Default Assignments
If there is no mapping available, an internal mapping will be added to the RP mapping table in the following manner:
- For Hard merge, the mapping will be added between the first RP of the surviving order and the first RP in the merging order with non-zero WIP.
- For SoftUP merge, the mapping will be added between the first RP of the surviving order and the first RP in the merging order.
- For SoftDOWN merge, the mapping will be added between the first RP of the surviving order and the last RP in the merging order with non-zero WIP.
If the mapping between the Goods Receipt (GR) reporting points of the surviving and merging orders is not present, it will be added by the system automatically for correct GR postings.
Types of Merges
There are three ways the merging orders can be merged into a surviving order, distinguished by the field WIPMOVE in table /SAPAPO/FOTMOD:
- Hard merge (default):
- All reporting points that have some WIP in the merging orders, must have a mapping entry in the RP_MAPPING table. (Note: Use WIPMOVE = 'H' in table /SAPAPO/FOTMOD for CALLTYPE = 'B' (for BAPI).)
- Soft UP merge
- WIPs at merging order reporting points without any mapping will be transferred with the earlier mapped reporting point (or the first reporting point in the surviving order if there is no earlier mapped reporting point). The WIP at the GR reporting point will always be transferred to the GR reporting point of the surviving order. (Note: Use WIPMOVE = 'U' in table /SAPAPO/FOTMOD for CALLTYPE = 'B' (for BAPI).)
- Soft DOWN merge
- WIPs at merging order reporting points without any mapping will be transferred with the next mapped reporting point (or the GR reporting point in the surviving order if there is no other mapped reporting point). The WIP at the GR reporting point will always be transferred to the GR reporting point of the surviving order (Note: Use WIPMOVE = 'D' in table /SAPAPO/FOTMOD for CALLTYPE = 'B' (for BAPI).)
Order Merge Restrictions
- The merge order functionality is available only for non-configurable products.
- All the orders involved in the merge must be in active planning version.
- All orders involved in the merge must be in same location.
- All reporting points in the merging orders which have some WIP, must have a mapping entry, except if a Soft UP or DOWN action type is used appropriately.
Parameters
COMMIT_CONTROLGEN_SETTINGS_FOT
LOGICAL_SYSTEM
ORDER_HEAD
PLNG_VERSION
RETURN
RP_MAPPING
STRATEGY_PROFILE
Exceptions
Function Group
10503Fill RESBD Structure from EBP Component Structure BAL_S_LOG - Application Log: Log header data
This documentation is copyright by SAP AG.
Length: 4562 Date: 20240523 Time: 155254 sap01-206 ( 66 ms )
