Q1: Why are all withdrawable, non-backflush components not always issued on the list?
Ans: In addition to the reservation item criteria (movement allowed, non-backflush, requirement quantity > 0 and so on), components are not isssued if the order status does not allow goods withdrawal, if the reservation items require reprocessing as a future change or error record, or if a delivery exists for the reservation item, for example, for storage locations managed in handling units.
Q2: You specify selection conditions at componentlevel (Transaction CO27/COIK). However, components that do not correspond to these conditions are also issued in the component list.
Ans: The selection conditions on the initial screen of the information system are used to identify an order. For the orders that are found, all the components of these orders are then displayed on the corresponding list. If you want to restrict the display of the components, use a filter in the layout (as of Release 4.6C) or a profile that filters out the unwanted components.
Q3: What are the main differences between Transactions CO27/COIK and the picking list Transaction MB26?
Ans: Transactions CO27/COIK are lists, based on the order information system, whereas Transaction MB26 is reservation-based. However, it is also possible to make an order-based selection in Transaction MB26 using the 'Production order' selection window. In this case, both lists should also issue the same components for identical orders.
In the event of incorrect goods movements in Transaction COGI, picking using Transaction MB26 generates postprocessing records, whereas Transactions CO27 and COIK send an error handling. If the goods movements cannot be corrected, the records are returned unchanged.
Picking using Transaction MB26 can be scheduled as a background job. This is not possible with Transaction CO27/COIK.
Read More Here About SAP PP Transaction Codes
In Transactions COIK/COHV, you can use mass processing to store goods movements of the picking as future change records and you can then update them later using a report (for example CORUPROC). There is no function of this type in Transaction MB26.
Transaction OPJ2 can be used to trigger an automatic stock or batch determination for picking with Transaction CO27/COIK. This is not possible for Transaction MB26.
Q4: How I can pick in a batch, that is, how can I flag goods movements for update?
Ans: Production order: Due to frequent incorrect use, the 'Pick in batch' function has been removed for Release 4.6. However, you can still use the function via 'Mass processing' in function parameter 'B: Execute goods movements in a batch program'.
Process order: in Transaction COIK you can use the right mouse button to select the 'Pick/batch' function or you can call the function via 'Mass processing' in function parameter 'B: Execute goods movements in a batch program'.
Q5: Why is the batch determination executed in the picking list without an availability check?
Ans: The availability check for the batch determination is deactivated for technical reasons. During batch determination for multiple lines of a specific material, the batches confirmed as available for one line would also be determined for other lines.
Get More Questions and Answers with Explanation at SAP PP (Production Planning) Forums.