on 07-15-2014 10:15 PM
We are facing an issue with our packing list for a division we are going live with in three weeks. Our current business process for our plants already on SAP is to create the Packing List when the Delivery is created, with timing code "3" in the Packing List output condition, but to not print it until the "Check-in" button is clicked with the Shipment in VT02N based on an activity profile.
However, for the service shipments in this division going live August 1, we do not need to create a Shipment nor generate a Bill of Lading from VT02N. We will post goods issue from the Delivery itself, and we want the Packing List to print at the time of Post Goods Issue from the Delivery. We have an access sequence for these service Deliveries with Shipping Point/Distribution Channel/Delivery Type, so only Distribution Channel 02 Deliveries will have Goods Issue from the Delivery, but we are not sure how to get the Packing List to not print until Goods Issue. Any advice would be appreciated.
Regards,
Jeff Stewart
Please make sure to search before posting (see #3 in ROE). I googled for 'delivery output PGI site:sap.com' and there are very many existing posts on this on SCN.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Go to IMG>Logistics Execution>Shipping> Basic Shipping Functions>Output Determination> Maintain Output Determination for Outbound Deliveries.
Select the Procedure you are using and check the control data to find the Cond. Type you are executing at the moment of the Outbound Delivery.
Check the fifth column and see you have plenty of options, check them out helped by an ABAP team member; if there is nothing already there, just ask him/her to create a new routine with the validation you need and set it there.
This is the same that Joao is suggesting I just went a little bit more in details.
Good luck Jeff!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can have 2 message types in NACE for the exact same program/form. That way you have a different behavior for both situation since you can set the goods issue requirement for one of them (and not the other).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.