on 12-08-2014 2:42 PM
Special requirement to Certificate of Origin and sale process:
i. As the CoO is purchase order / delivery specific, there is the following process:
1. Company purchases items and items are delivered to customer.
2. Comapny receives CoO document for the related PO, where the CoO is managed in GTS.
If company is selling items, GTS needs to get the information until which state, all items are consumed.
After all items from the related PO are consumed, the CoO document in GTS needs to get “invalid” in a way, it can not be used for other deliveries.
This means: as the CoO is PO/delivery related, the CoO is only valid for the related PO. If all items, from the PO, are consumed, the CoO can not be used for further shipments, which means, this information needs to be available in GTS.
1) Company purchases 3 items, which are scanned in inbound:
2) In GTS, we will have the CoO document (e.g. with number: CoO123), the PO (with number PO123) and the 3 items.
3) Company is consuming 2 items (1 remaining in stock)
4) In GTS, we need to see, that we can use the CoO123 for the 2 items to be delivered
5) Company is consuming the last remaining item:
6) In GTS, we need to see, that we can use the CoO123 for the last remaining item.
7) In GTS, it needs to be ensured, that the CoO123 can not be used for any other deliveries, as all 3 items are consumed.
So question is can we track the stock in GTS and SAP /ECC system for the CoO certificate and how much stock is available under particular LTVD and SAP system deliver goods accordingly and reduce the remaining qty in GTS as well.
Hi Ashish,
Just an idea - you can perhaps reuse and tweak quantity based licensing for your requirement.
As the CoO is a trade document you keep/forward on to customer, in your case it also serves as a hard limit in terms of quantity of items avalable for delivery.
How this could work
1) Create license for the CoO, your own license type, with quantity depreciacion instead of value depreciations
2) make the license PO specific
3) make your SO/delivery relevant for the license check against CoO dummy license, make the PO information stick to the SO/Delivery transfer to gts so that CoO can be assigned (may need some Z code) to customs document.
4) Quantity based license would prevent deliveries that exceed CoO allowed capacity, either by block/message/etc.. thats up to you..
Hope this helps,
Branio
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Branio,
Appreciate your idea for CoO and will discuss with team.
I am just exploring if we have GTS standard functionality to handle this requirement.
Also, can we have Stock ID (Batch or Equipment) and quantity field in LTVD worklist with reference to either PO or GR.
Whts the use of billing document worklist in preference processing.
Regards
Ashish
Hi Ashish,
Q: Also, can we have Stock ID (Batch or Equipment) and quantity field in LTVD worklist with reference to either PO or GR.
A: It sound like that you need a SVD, single vendor declaration solution, if different batches come from different sources for the same material/vendor combination. I dont think its possible to achieve in the standard LTVD worklist. There is a Badi to extend the standard logic, and the VD worklist structure can also be enhanced or forked, but with these steps you`re making a tailor made solution..
Cheers,
Branio
User | Count |
---|---|
13 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.