on 03-11-2009 12:29 PM
Can anyone tell me how we can issue just one invoice for multiple sales orders when the customer is the same.
If we have a number of sales orders for one customer, we only want to issue one invoice, but currently we are sending one invoice for each sales order.
In our test system, I have created an order, and then created another order with reference to the first, so everything between the two documents is identical other than the sale order number itself.
When running the billing due list VF04, if I simulate, the system proposes seperate bills. Split analysis shows this is due to different header data, namely the reference document number. How can I fix this? I'm not an SD person, I'm in technical support and am trying to help out, so if you do reply, please speak in layman's terms as I'm not overly familiar with this module.
Thanks for your help.
Angela.
Hi Angela
To create a Single Invoice from Multiple Deliveries during Collective Billing the following should apply
1) the header data appearing in the billing document must agree
2) the split conditions specified do not apply ( here is where you solution lies )
In your case as the Split Analysis mentions " Split analysis shows this is due to different header data, namely the reference document number" . The two delivery document has Reference Document No which is the Order No ( Present in Item Data on the Predecessor Data Tab) different , and hence the invoice is splitting. You need to see that the Split Condition specified in you Copy Control Do not Apply and the issue should be solved
You can check this in VTFL then choose the Target and Source Document ..for the required Item Category and check the copy control details . There in the Data VBRK/VBRP a routine will be maintained which defines the split criteria .
Please let me know if it solves your problem
Regards
A
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Changing the entry to 007 still did not work. However, in VTFA at the Header level we previously had reference number as sales order number (B). I have removed this entry and the billing simulation now proposes just one invoice.
I now need to check the impact of this change with the business to understand if this will cause a problem elsewhere.
Thank you all for your suggestions. If you know of a reason why I should not make this change or possible impacts, your responses would be appreciated.
Thanks,
Angela 🐵
Hello,
The most possible cause of assigning the sales order number as refernce is to understand what the sales order number is from the accouting document generated and to link the accouting document generated after the inovicing
this also ccold be usefull to check the accounts in FBL5N, and to know what was the sales order number
removing this would remove the link, which business uses it at present
but for combining multiple sales order inot single invocie , this requirement would not be met anyways
hope this helps
Thanks
akasha
Hello Angela
you could do the following things to check and rectiofy the error
The setting for the split is controlled in the transaction VTFL, copy control from delivery docuemnt to billing document
check for the document type of the delivery by going to vl03n > header> adminstrative data
also u can know the docu,emt type of the billing by checking which document is generated when u enter vf01
enter the delivery document and the billing document in source and target coloumns int he t code
in header t, there is field VBRK/VBRP . the routine set here determines the split. since you are a techincal person you can set a break point and analsyse or check the code for the split cirteria
the field VBRK-_ZUKRI influences the split criteria
you could debug and get the right criteria
Hope this helps
Thanks
akasha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Please confirm the order dates are same that is creation date.
Regards,
Mann.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
102 | |
12 | |
11 | |
6 | |
5 | |
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.