Ansicht
Dokumentation

CIFORD04 - Determine Rework Operations or Triggering Operation

CIFORD04 - Determine Rework Operations or Triggering Operation

Vendor Master (General Section)   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

SAP enhancement CIFORD04 is used to determine, in a different way to in the standard system, rework operations for an operation triggering a rework, or to determine the operation triggering the rework for a confirmation of a rework operation in the integration with APO.

Rework operations cannot be displayed in APO at this time (APO 3.0). A confirmed rework quantity is first transferred to APO as a yield of the triggering operation to credit the resource and because it is assumed that the rework quantity can be converted to a yield in R/3 as a result of the rework. In a rework operation confirmation in R/3, the triggering operation is first determined. If scrap is confirmed for the rework operation, this scrap reduces the yield of the triggering operation and raises the scrap quantity of the triggering operation in APO. The confirmation for the rework operation is, so to say, redirected to the triggering operation in APO.

Customer Exit exit_saplcova_003:

This customer exit is processed during the confirmation for a rework operation for each rework operation. You can use this user exit to determine, in a manner different from in the SAP standard system, an operation triggering a rework and redirect the confirmation to it for APO. In the SAP standard system, it is assumed that the rework operations directly follow the operation triggering the rework.

Customer Exit exit_saplcova_004:

This customer exit is processed during the initial supply of production orders from R/3 to APO per operation triggering a rework. The rework quantity of a operation triggering a rework is added to the yield during the initial supply. All rework operations for this operation are then determined and the scrap quantity of all rework operations is cumulated. The cumulated scrap quantity is added to the scrap quantity of the triggering operation and subtracted from the yield of the triggering operation. In this user exit, you can determine the cumulated scrap quantity of the triggering operation yourself. In the standard system, it is assumed that the rework operations directly follow the triggering operation during the confirmation (based on the operation number).






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

Length: 2290 Date: 20240426 Time: 050144     sap01-206 ( 97 ms )