/SAPAPO/SEQR_GET_SEQPLMAT - Calculate Restriction Hits Matrix for Sequencing

RFUMSV00 - Advance Return for Tax on Sales/Purchases   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Functionality

This function module provides many CUOBJs and KNOBJs with information on whether or not the characteristicvaluations of the CUOBJs fulfill the selection conditions of the KNOBJs (it must be selection conditions - other types of object dependencies are not allowed).

As well as the planning version in IS_GEN_PARAMS and the SIMSESSION (optional) you must enter a table(IT_KNOBJS) of the KNOBJs, whose sequence determines the sequence of the results table, and a table (IT_CONFIGS) with the following structure:

1. MATID
2. LOCID
3. Table of structure PEGID, CUOBJ,

Another optional entry is the structure IS_CONTEXT4BADI of type /SAPAPO/SEQ_CONTEXT4BADI_STR which isbasically ignored in the function module except that it is passed on to the BADI which is accessed to valuate the special characteristics (see the note below for more information).

The output is table ET_BITS - the bit string in the n-th row contains the information on the KNOBJ inthe n-th row of the input table. The m-th bit in such a bit string contains information on the PEGID-CUOBJ-Pairswhose COLIDX is equal to m in the additionally issued table ET_SPMHEAD. The sequence of the PEGID-CUOBJ-Pairswhich is defined in this table by the COLIDX column may vary from the sequence in which the PEGID-CUOBJ-Pairswere entered. (Column LOTSZ in table ET_SPMHEAD is not filled, its purpose is to avoid parts of tablesbeing copied to the sequencing programs.) A bit in such a bit string is set if the selection condition of the corresponding KNOBJ is fulfilled by the characteristic valuation of the corresponding CUOBJ.

If no CUOBJs or KNOBJs are found on the database or if errors occur during the valuation they are enteredin the output tables of the missing CUOBJs or KNOBJs but they are still listed in the results matrix (with empty bit strings).

Example

Notes

In the selection conditions recorded in the input table IT_KNOBJS, you can also use characteristicswhich are not valuated at order creation. These characteristics, however, must exist in the Customizingtable /SAPAPO/RET_TCVC and you have to ensure that the BADI /SAPAPO/IF_EX_SEQ_CVCVALUE->CHARATERISTICS_VALUES_SETvaluates these characteristics for all orders. This BADI requires the entries: planning version, simulationversion and the passed-on structure IS_CONTEXT4BADI and the parameters to be changed include a tableof all orders (PEGID-CUOBJ-Pairs) with all the characteristics to be valuated in which the suitable characteristics from the BADI have to be recorded.

If material requirements planning is executed per RPM (Rapid Planning Matrix) for many of the product-location-combinationsinvolved and if such a material requirements planning run has already been executed for many of theCUOBJs involved, then the majority of the calculations take place in the liveCache. Otherwise, moreABAP calculations are required, the database is accessed more often and the calculations may then takea lot longer. In mixed cases (that is, some COUBJs have been planned per RPM and others have not) the sequence of the PEGID-CUOBJ-Pairs becomes mixed up.

Further information

Parameters

ET_BITS
ET_INVALID_CUOBJS
ET_INVALID_KNOBJS
ET_SPMHEAD
IS_CONTEXT4BADI
IS_GEN_PARAMS
IT_CONFIGS
IT_KNOBJS
IV_SIMSESSION

Exceptions

FATAL_ERROR

Function Group

APO/SAPLSEQ_RPM

BAL_S_LOG - Application Log: Log header data   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.


Length: 3534 Date: 20120525 Time: 104704     triton ( 202 ms )