LV60A003 is a copy requirement routine and doesn't have anything to do with determining splits, only whether a billing doc is created at all. By saying that they want the carrier as a header condition, do you mean header partner? If so they can keep the carrier as a header partner on the delivery, but configure it to be an item partner on the billing doc, so that they're not trying to populate a single header partner with multiple values
| | | ---------------Original Message--------------- From: Typewriter Sent: Thursday, July 14, 2011 9:31 AM Subject: No invoice split for different carriers Jim, What I understand from Patrick's latest post is that they have set up Carrier as one of the header partner function in Delivery. E.g.: Delivery 80070940 has carrier A in header Delivery 80070941 has carrier B in header By creating the invoice the invoice will be splittet with argument of the different carriers i.e. 2 bills are created. The reason is in VTFL, Copy condition for header is 003 (Include LV60A003). I am assuming that business wants to continue having carrier as header condition in Delivery, therefore my suggestion of copying and modifying 003. (to not include LV60A003) And then doing relevant steps in VOPAN to get carrier as partner function in item line and not as header partner function; in billing doc. i.e. your idea. I haven't tested this so I can not say if it works or not. Your comments please. | | __.____._ Copyright © 2011 Toolbox.com and message author. Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251 | | Popular White Papers In the Spotlight _.____.__ |