/SAPAPO/OM_FIX_PEGGING_CHANGE - Create/Change/Delete Fixed Pegging

CPI1466 during Backup   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Functionality

This function module changes, deletes or creates fixed pegging relationships (hard pegging).

A fixed pegging relationship fixes the material flow between two orders in the APO network. To be moreprecise, this defines the pegging quantities between an output node in the first order and an input node in the second order. The system does not subsequently change the this quantity relationship.

The METHOD field is used to determine whether the associated pegging relationship (= row in the IT_FIXPEG_PROFILE table) will be created (METHOD = 'N'), deleted (METHOD = 'D') or changed (METHOD = 'C').

Beziehung (= Zeile in der Tabelle IT_FIXPEG_PROFILE) angelegt (METHOD = 'N'), gelöscht (METHOD = 'D') oder verändert (METHOD = 'C') werden soll.

OUTPUT_IONODE identifies the output node in the pegging relationship.

INPUT_IONODE identifies the input node in the pegging relationship.

PEG_AMOUNT defines the pegging amount.

If METHOD = 'C' is selected, an existing pegging relationship is overwritten with the new data (amount).

Example

Notes

If errors occur, return code tables ET_RC and ET_FIXPEG_RC both return the same error codes. However,table ET_FIXPEG_RC contains the complete I/O node keys (ORDERID, POSITION_NO and LINE_NO) of both I/Onodes in a pegging relationship, while table ET_RC (as a standard return code table) contains only theORDERIDs of the associated orders as keys (OBJECTKEY contains the ORDERID of the output node; ERROR_OBJECT_KEY contains the ORDERID of the input node; ERROR_OBJECT_TYPE contains the value gc_om_object_order).

Return codes to be queried (table ET_RC or ET_FIXPEG_RC):

• om_object_locked: Order contains an I/O node that is currently locked.

• om_invalid_pegarea: Invalid pegging area GUID

• om_invalid_order: Invalid order GUID

• om_invalid_input_node: Order does not contain the specified input interface node

• om_invalid_output_node: Order does not contain the specified output interface node

• om_inconsistent_peg_relation: Inconsistent fixed pegging relationship. The fixed pegging relationshipis invalid, as the receipt due date in the input interface node is later than the requirement time-spot in the output interface node.

• om_invalid_peg_amount: Incorrect pegging amount. The fixed pegging relationship is invalid, as the pegging amount is incorrect. The following is correct: pegging amount >= 0 and pegging amount <= available amount of the input reference node in question.

• om_invalid_peg_relation: The fixed pegging relationship already exists and cannot therefore be created again (only if METHOD = 'N') or a fixed pegging relationship does not exist and cannot therefore be changed.

Further information

Parameters

ET_FIXPEG_RC
ET_RC
IS_GEN_PARAMS
IT_FIXPEG_PROFILE
IV_SIMSESSION

Exceptions

LC_APPL_ERROR
LC_COM_ERROR
LC_CONNECT_FAILED

Function Group

APO/SAPLOM_PLANNINGTABLE

General Material Data   BAL Application Log Documentation  
This documentation is copyright by SAP AG.


Length: 3727 Date: 20120525 Time: 042418     triton ( 152 ms )