Ansicht
Dokumentation

PPC1PR_STEP2_SINGLE_EXE - DE-EN-LANG-SWITCH-NO-TRANSLATION

PPC1PR_STEP2_SINGLE_EXE - DE-EN-LANG-SWITCH-NO-TRANSLATION

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

This function module posts (in one particular LUW) goods movements for all materials that are assigned to a cost collector and a posting date in the second phase of the two-step production backflush..

For the given package (parameters IF_POST_DATE, IF_ACCASSOBJ, IF_PLANT, IF_VERSION, IF_BAUGR, IF_RMPROFILE, IF_AUFNR, IF_FLGINFODEST, IF_CONFLOGSYS), the function module attempts to post a goods issue for the components found in input table IT_COMPLIST. The successful items are all posted in one material document, and the incorrect movements are saved for postprocessing (transaction COGI). Subsequently, the function module attempts to update the completion flag for processed materials in table PPC_STEP2using input table IT_INDEXLIST, which contains the keys for all material items.

The activities are recorded and transferred as an input parameter (IF_LOG_HANDLE). The export parameters are the number of components that were posted in material document, and the number of components saved for postprocessing (EF_NUMMAT_OK and EF_NUMMAT_FAIL).

Assumptions: The input data is consistent with the material postings. That is, only the permitted number of components exists in one material document. If necessary, the call of the function module splits the component list (see documentation for the function module PPC_STEP2_EXE.)

No explicit COMMIT WORK is executed by the function module, but the calling process should do a COMMITbefore calling this function again, as there can be no more than one material document posting per COMMIT WORK.

If errors occur, exceptions are triggered, but there is no explicit ROLLBACK WORK. The calling process should execute the ROLLBACK WORK as well as the corresponding update of PPC log.

The exceptions raised are:

  • PROTOCOL_ERROR: An error occurs when writing or saving the PPC log;
  • PROFILE_ERROR: The repetitive manufacturing profile determined by IF_RMPROFILE) is inconsistent or incomplete;
  • UPDATE_ERROR: An error occurs when updating the completion flag in table PPC_STEP2;
  • BATCH_OVERFLOW: After batch determination, the number of individual goods movements exceeds the number of possible rows in the MM-IM-material document.

Example

Notes

Further information





Parameters

EF_NUMMAT_FAIL
EF_NUMMAT_OK
IF_ACCASSOBJ
IF_AUFNR
IF_BAUGR
IF_COMPCOUNT
IF_COMPLMODE
IF_CONFLOGSYS
IF_FLGINFODEST
IF_LOG_HANDLE
IF_PLANT
IF_POST_DATE
IF_RMPROFILE
IF_VERSION
IT_COMPLIST
IT_INDEXLIST

Exceptions

MATPOS_OVERFLOW
PROFILE_ERROR
PROTOCOL_ERROR

Function Group

PPC1PR

BAL Application Log Documentation   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 3718 Date: 20240523 Time: 133459     sap01-206 ( 69 ms )