Update cart on order / template transfer

Question

Hi,
Whenever we transfer items from order template or an order, the cart value in the header stays as it is.
It is not getting updated.
Can you kindly lemme know, how to update that on the event of transfer?
-Aarthi

Answer 1

Hello Aarthi,
With templates and carts you have two options.
Scenario-1: You convert the entire template using the option "Create new order on the basis of an order template" in the welcome page to create a new cart. This you can do only when the cart is empty. Makes sense. In this scenario, all the header and item(s) details are used to create the cart.
Scenario-2: You can transfer item(s) from a template to an existing cart. Since this is an existing cart (you have made some header and item input already), no attempt is made by the program to change the cart header.
I think you are trying scenario-3.
Scenario-3: You want to transfer item(s) from a template to an empty cart. In this case it should create an empty cart and then transfers the item(s). You expect It should also copy the header information from the chosen template.
Hmmm, looks like SAP did not consider this in their usecases. Looks like SAP is strictly treating transfer as transfer of item only. Not a convert + transfer when the transfer is made to an empty cart.
See what is technically involved in these scenarios.
Scenario-1 uses Copy Transaction (Java+ABAP) - All you need here is the template Guid..
Scenario-2 uses Copy Item(s) (Java+ABAP) or Create Transaction + Copy Item(s). Here it takes only the Product id (or guid), qty and Uom only
Your scenario is slightly complex. It has to do, (a) Create Transaction, (b) Copy Item(s) as scenario-2. It also has to do (c) Read Header information from template and (d) Update Cart Header. Since SAP is not doing the last two tasks, you have to do them.
One more issue will be with the setting of Requested Delivery dates at Header and Item level. If you have noticed, when you input the Header RDD for the first time, an attempt is made how to migrate this to items. A confusing popup message asks three options. This is provided to "reduce" the pain of entering the RDD for each item. Since the tempates are created in the past and carts are made in the present, the RDD is usually irrelevant. And that is the reason when you use scenario-1, all header information except the RDD get copied over from template to cart.
So, your logic should take care to clear the RDD of the header and copied item and also see that the user is prompted to enter them appropriately in the cart. These are all business decisions which will drag your requirement easily to a BIG development effort.
Tell me why you can't use scenario-1 where it converts the template to cart? Did you try that?
Easwar Ram
http://www.parxlns.com