While we can control the billing of F2, there is no telling which sales org has delivered the goods. So, for F2, you schedule the billing run (VF04) specific to the sales org (NL). After a gap of about 10 minutes, schedule another billing run ONLY for intercompany billing, leaving the sales org blank. This will ensure that interco billing initiated by the first F2 run get processed, irrespective of delivering sales org. My client has 42 jobs scheduled for F2 billing for different sales orgs. Earlier, these jobs were set for both F2 as well as IV. This resulted in a lag of a day between F2 and IV and the IVs created on the 1st day of the month (for the F2 of the last day of the earlier month) invariably had IDOCs stuck as unposted since the posting period for the previous month is closed in the receiving company code. This new sequencing was my recommendation to avoid such a situation. While this reduces such occurrences substantially, does not totally remove the issue (when the IV is between, say US and China). In this case, I have 42 additional runs for only IV (with sales org blank) scheduled 10 mins after each F2 run.
| | | ---------------Original Message--------------- From: Typewriter Sent: Friday, October 28, 2011 4:03 AM Subject: Inter company condition type HI Rajan, Thank you for your post. I have marked it as helpful. Please comment on an example - when Delivering sales org = GER, Ordering sales org = NL. Then how are the sequence of generation of billing documents "controlled"? | | __.____._ Copyright © 2011 Toolbox.com and message author. Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251 | | PSD Rajan SAP Logistics Sales and Distribution Helper
Posted helpful replies on 5 threads in a group to earn a Bronze Achievement Popular White Papers In the Spotlight _.____.__ |