Automatic Goods Movement FAQs
Q-1) Upon confirming by utilizing the single entry transactions, why does the user get a message regarding the number of successfully posted goods movements, however user does not get it when he confirms using the collective entry transactions?
As of Release 4. 5, the goods movements belonging to the collective entry as well as the BAPI confirmation, of mass processing, or of the dependent goods movements are all executed in the update program and not in the dialog. Due to this the system is unable to issue a message.
Q-2) Upon cancelling a confirmation and while post-processing incorrect goods movements from confirmation cancellations, why is the goods movement overview not ready for input?
As of Release 4. 6, A document reversal is executed. The system always cancels what was initially updated by the confirmation to the material document. As a result no more changes are essential on the goods movement overview.
Q-3) During the customizing for the confirmation (transaction OPK4), the user has set the error handling incase there are incorrect goods movements. However, during the confirmation cancellation, there is no error handling provided inspite of the incorrect goods movements. The system does not also provide error handling when posting the confirmations via the collective entry or via BAPI and when updating the dependent goods movements of the collective order processing.
As of Release 4.6, The goods movements of the cancellation are always executed in the update program; as per Release 4.5, goods movements of the direct production assembly from collective orders are executed always in the update program. Therefore, the system does not display an error handling or a message regarding the number of successfully posted goods movements.
Q-4) In the case of incorrect goods movements for a reversal in the standard system, is a termination possible?
Yes, for doing this the user is required to set the flag for error handling in Customizing transaction OPK4 along with the flag for termination for the incorrect goods movements. The system displays an error message in transaction CO13, the reversal is ultimately terminated.
Q-5) During the confirmation cancellation, goods movements "disappear". These are not posted successfully and they are not in transaction COGI under the incorrect goods movements. How can the user find the goods movements?
As of Release 4. 6, the goods movements of the reversal are always executed in the update program. No error record is generated, in case there are locks, however, in place a request is generated for a later update as the system tends to assume that the lock is only meant for the temporary purpose. These requests can be located for the confirmation or for the order with the transaction CO1P.
Q-6) How can we avoid COGI records during the confirmation?
For all the transactions which can execute the goods movements online, the user gets an option incase the error handling has been activated: As long as the user answers the dialog box with the SAP Note related to the incorrect goods movements with "Cancel", the overall confirmation is terminated. However incase the user answers with "No", COGI records are generated.
As of Release 4. 70, there is a customizable setting for generating a termination for incorrect goods movements.
Q-7) For co-products, how can an automatic goods receipt be achieved?
This function is available up to and including Release 600 Enhancement Package 5, not in the SAP standard system.
The enhancement LOG_PP_CI_1 is delivered With Release 600 Enhancement Package 6, and this enables an automatic goods receipt meant for the co-products. The user can find details regarding this in the documentation meant for this enhancement.
Q-8) Why system doesn’t perform automatic goods receipt for co-products?
Note the following restrictions:
For the confirmations for collective orders, the system does not provide any support automatic goods receipt for co-products for subordinate orders. The usage of WIP batches in the confirmation also does not also support the automatic goods receipt of co-productsIn all other cases, check the following points:
- The indicator for automatic goods receipt must be set in Customizing (transaction OPK4 or OPK4N).
- In Customizing for the message type (transaction OPJB), the message C6 040 must not be set as a warning or error.
- The order must contain only one operation with a control key that has the attribute "Automatic Goods Receipt".
- The co-product must be assigned to the last operation.
If the system doesn’t perform goods receipt, user should check whether IS Mill is active in his system. If so, he should use Customizing for the confirmation parameters (transaction OPK4 or OPK4N) for assigning a process control key with the attribute "immed. in update task" or "later in background" for "Auto. GR" and "Backflush".
Q-9) When posting confirmations with automatic goods movements with mass processing COHV, the collective entry CO12/CORR via confirmation BAPIS, confirmations via the PDC interface, or when saving requested confirmations with CO1L or predefined goods movements with CO1P, the goods movements are processed incorrectly and the system issues error M7 120 or M7 121 although the user has the authorization for the corresponding transactions. Incase the goods movements are not processed incorrectly, the user receives the goods receipt and goods issue items on separate material documents. Why is that so?
For separated goods movements, which is goods movements which are posted in the update program or via requests, because of technical reasons only one transaction code can be specified. This is always COGI. Hence, this user should have an authorization for COGI; else the goods movements are incorrectly processed.
Due to technical reasons, the goods receipts and goods issues should be transferred in separate packages of inventory management. This leading to the various material documents.
Q-10) The material document is not updated in the field AFRU-WABLNR inspite of the successful goods movements. Where can the user locate the document number?
As of Release 3. 1H, the system provides the reference from confirmation to material document via table AFWI. The system still utilizes the AFRU-WABLNR for header confirmations or confirmations for an individual operation. With milestone confirmations or with separate goods movements,that is, goods movements which are all posted in the update program or via requests (BAPIs, collective entry, mass processing, BDC/PDC), table AFWI is always provided because of technical reasons.
Q-11) When posting confirmations with the automatic goods movements via mass processing COHV, the collective entry CO12/CORR, via confirmation BAPIs, or during the saving requested confirmations with CO1L or predefined goods movements with CO1P, the printouts (goods receipts/issue slips) are not generated as per the Customizing of the transaction executed in each case.
Since the original transaction code (COHV, CO12, and so on) is not available when the user posts the separated goods movements (posting in the update program in a separate process) because of technical reasons, the system utilizes transaction code COGI by default. Therefore, it is important that user sets up Customizing for the print control appropriately for transaction COGI.
Q-12) User posts a final confirmation with a quantity of 0. As a result, the components of the order are assigned the final issue indicator (the content of the field RESB-KZEAR has been set to "X") even though COGI entries exist for this order and this material.
The behaviour corresponds to the SAP standard system. For a final confirmation with quantity 0, the system sets the final issue indicator and doesn’t verify whether post-processing records still exist in the COGI or if the future change records still exist. For avoiding these situations, it is suggested that user processes the post-processing records and future change records as fast as possible and that the user schedules the report CORUPROC, for instance, regularly.
Q-13) User enters a partial confirmation for a production order which has a component quantity with backflushing flagged and which is defined as a fixed quantity. The component quantity has not been adjusted proportionally here.
The behavior corresponds to the SAP standard system. Incase a component is flagged for backflushing and the "Fixed Quantity" indicator is position, in that case the quantity of these components is not adjusted proportionally for a partial confirmation. The "Final Issue Effected" indicator is not set. User should remove the "Fixed Quantity" indicator if he wants to adjust the quantity for a partial confirmation.
Q-14) Despite the "All Components" flag in confirmation Customizing (OPK4), the system posts the components only if the user goes to the goods movement overview in the confirmation.
This behaviour related to the SAP standard system. With the "All Components" flag in Customizing, the system will showcase the components which have not been backflushed in the goods movement overview to which user has to navigate. If the user does not call the goods movement overview, the system will only post the components which have to be backflushed.
Q-15) When is the indicator "Final issue" (KZEAR) set for the reservation?
In this case, you must differentiate between two different scenarios.
1) Goods movements are posted in the dialog
Incase the goods movements in the confirmation have been posted in the dialog, the indicator "Completed" (COWB_COMP-ENDKZ) is then set automatically incase a final confirmation is posted. The indicator can be reset manually or be influenced via the user exit or BAdI.
If it is not reset, then it is transferred to inventory management (MM) and later activated in the reservation. By the inventory management, there is no automatic adjustment. Accordingly, the indicator is displayed in the confirmation (transaction CO14 or CORT) and in the order.
2) Goods movements are posted separately
The decoupled posting of the goods movements takes place during the mass processing, collective entry, confirmation via BAPI, or incase it is defined in this manner with a corresponding process control key.
If the goods movements have been posted separately, the system always creates data records in the table AFFW. The logic for the posting of the AFFW records varies from the posting of the goods movements in the dialog: In this scenario, the inventory management decides whether or not the "Completed" indicator has been set. Post successful posting of the goods movements, the system executes the final issue or the final delivery in case the operation or order which belongs to the goods movement has been confirmed finally
Q-16) I frequently experience terminations with the error MESSAGE_TYPE_X, error RU803/RU805. What can I do?
In general, the termination does not take place because of a program error. The main course for the settings for posting the goods movements or the scheduled jobs is in relation to this.
There are no settings which provide an optimal approach for every data constellation. It is therefore suggested that the user speaks to a PP consultant.
Generally, the termination takes place occurs incase a process which writes AFFW data records is initiated when another such process is already active.
Q-17) Which are these processes?
- Reports CORUPROC, CORUAFFW, CORUPORC1, CORUAFWP
- Manual posting in COGI, CO1P, CO16N
- Goods movements from the subsystem if the "Immediate Update" indicator is active in transaction CI41.
- Goods movements via the confirmation with the immediate process control in update mode
Scheduled jobs and these processes should be reconciled in such a manner that no overlaps exist.
Some basic recommendations are listed below:
- Incase goods movements are posted utilizing a BAPI, the goods movements should be posted in completely decoupled form. SAP Note 208477 describes the settings.
- If the user uses a subsystem (PDC, interface) for posting goods movements, the "Immediate Update" indicator may result in problems. User should carefully check incase this setting is making sense for you. If you dont receive data from the subsystem in packages, we recommend that you dont set this flag and instead schedule the program CORUPROC1.
- User should schedule the update of incorrect goods movements less frequently than the update of the flagged goods movements. Therefore, user should not simply update everything utilizing the program CORUPROC on each occasion.