Kontakt

Ansicht
Dokumentation

/SAPAPO/OM_ORDER_GET - Get Orders for Activities, Resources, and Pegging Areas

/SAPAPO/OM_ORDER_GET - Get Orders for Activities, Resources, and Pegging Areas

Vendor Master (General Section)   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

Further information

@0P@Selection Modules for the Planning Board

Functionality

This function module gets the orders of the specified import tables. For the header data of these orders, it gets the constraints of all activities of the order, all I/O nodes of the order, and any peggings on these I/O nodes.

This module is particularly complex and you should avoid using it for new developments. Instead, you should request a new module tailor-made for your purposes.

An order is selected

  • if it contains one of the specified activities (IT_ACT) and this activity overlaps the time interval [IV_START_TIME, IV_END_TIME[
  • or if it contains an activity that is allocated on one of the specified resources (IT_RES) and that overlaps the time interval [IV_START_TIME, IV_END_TIME[
  • or if it contains an I/O node that is allocated to one of the specified pegging areas (IT_PEGAREA) and whose requirement or availability time is wholly or partly in the time interval [IV_START_TIME, IV_END_TIME[.
    The tables IT_CHARACT_REQ_OUTNODE and IT_CHARACT_VAL_INPNODE allow filtering by pattern characteristics.
    If a suitable I/O node contains a pegging for another I/O node (pegging partner) and if the switch IV_GET_ALL_PEG_DEPENDANTS is selected, the pegging-dependent order, i.e. the order of the pegging partner, is also selected.

If the switch IV_GET_SUBORDERS is activated, and if the activities and I/O nodes in the order selection belong to a suborder, the suborder is selected, and not the top order.

If the import table IT_ORDER_TYPES is filled, only those orders are selected that have one of the order tyoes listed there. In addition, further import parameters can be used to specify additional selection criteria; see Selection Modules for the Planning Board.

Pegging-dependent orders (see above) are filtered either by order type or by other selection criteria.

Notes

Error Handling and Troubleshooting

Possible return codes:

  • 38 = om_invalid_pegarea:
    The specified pegging area does not exist in liveCache.
  • 43 = om_invalid_segment:
    The specified activity does not exist in liveCache.
  • 47 = om_invalid_resource:
    The specified activity does not exist in liveCache.




Parameters

ET_CONSTR
ET_IO
ET_ORDER
ET_PEG
ET_RC
IS_GEN_PARAMS
IT_ACT
IT_CHARACT_REQ_OUTNODE
IT_CHARACT_VAL_INPNODE
IT_PEGAREA
IT_RES
IV_ACT_PLANNED_STATUS_SEL
IV_CONSTR_SELECTION
IV_END_TIME
IV_GET_ALL_PEG_DEPENDANTS
IV_GET_SUBORDERS
IV_IO_SEL
IV_ORDER_TYPE
IV_ORD_PLANNING_TYPE_SEL
IV_PEGAREA_SEL
IV_PEG_SELECTION
IV_RPM_GET_VIRTUAL_INPUTS
IV_SIMSESSION
IV_START_TIME

Exceptions

LC_APPL_ERROR
LC_COM_ERROR
LC_CONNECT_FAILED

Function Group

APO/SAPLOM_PLANNINGTABLE

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 5713 Date: 20240420 Time: 091225     sap01-206 ( 66 ms )