Ansicht
Dokumentation

BAPI_MOSRVAPS_SAVETMPLPPM - Create or change production orders for template PDS or PPM

Addresses (Business Address Services)   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Functionality

Production orders can be created with reference to a template PPM or a template PDS using this method. When the method is called either only orders with reference to template PPM or only orders with reference to template PDS can be transferred.

Definition of Template PPM

Definition Template-PDS

In order to create an order, a template PPM or a template PDS must exist. The fields PLAN_NUMBER and PPM_NUMBER specify which template PPM should be used. The PDS_NAME specifies which template PDS should be used.
Because a template PPM or a template PDS only serves as a template, the concrete attributes of the order (that is, which activities, components, and so on this order should contain) must be transferred when the order is created.

Example and Possible Application Areas

The individual BAPI parameters are used to specify the appearance of the concrete order to be created using the template PPM or template PDS. For more precise information on the parameters, see the relevant parameter documentation.

Special Features and Restrictions:

Special Features when Using Template PPMor Template PDS

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 when 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. The GUID is returned in the mapping table 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 internal number assignment, it receives the order type APO local order (domain fixed value 8)

• Specified 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.

• Specified 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 released ORDID already exists for the logical system (LOGICAL_SYSTEM) used, the system issues an error message.
You can change system behavior using parameter CHANGE_IF_EXISTS in such a way that the system does not issue an error message in this case, but that the order is automatically changed with the new values instead.

Attention

• Informationen for fields, TEMPLATE_OPNR (operation number), TEMPLATE_OPNR_EXTENSION (extension of operation number) and TEMPLATE_ACTNR (activity number):

When you display the PDS the data from these fields is visible in the Activity field. The number that you see there is structured as follows:

• The first 4 characters are the operation number

• The next 8 characters are the extension of the operation number

• The final characters are the activity number

Example:

When you display the PDS, you see the following number in the Activity field:

0010000000011P

Explanation:

Operation number: 0010

Extension of operation number: 00000001

Activity number: 1P

• Note that an APO local order (domain fixed value 8) cannot be reached using its external number (to be changed). Instead you must use its GUID.

• If you want to access an order via its GUID you have to set EXT_NUMBER_ASSIGNMENT to internal number assignment.

• Transaction behavior:
  Note that, depending on the COMMIT_CONTROL parameter, this method can automatically post (COMMIT WORK) or discard (ROLLBACK WORK) data changes.

• For scenarios in which orders are transferred between R/3 and APO, you should pay attention to the restrictions for integration mentioned above.

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

Further information

Parameters

CHANGE_IF_EXISTS
CHARACTERISTICS_VAL_ACT
CHARACTERISTICS_VAL_IO
COMMIT_CONTROL
EVENT_CONTROL
EXTENSION_IN
EXT_NUMBER_ASSIGNMENT
LOGICAL_SYSTEM
MAPPING_DATA
ORDER_CAPREQS
ORDER_COMPONENTS
ORDER_HEAD
ORDER_MODES
ORDER_STRUCTURE
ORDER_TYPE
PLANNING_MODE_USAGE
PLANNING_VERSION
RETURN
STRATEGY_PROFILE

Exceptions

Function Group

10503

ROGBILLS - Synchronize billing plans   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 8103 Date: 20240523 Time: 180624     sap01-206 ( 107 ms )