on 06-24-2008 10:48 AM
Dear All,
i have an issue. one delivery has been split into multiple invoices. i have checked the GI date which is different from delivery dat date in the sales order.
i believe this should be the reason for the invoice split.
to avoid this what actions need to be taken?
pls adive me eventhough GI date and delivery date differes invocie split should not happen.
what changes are need to be done for this?
Provide me some material on what instances invocie split takes place.
TIA
KOGI
Hi
I agree with sankar. Basically routine is playing important role at copy contral between delivery to order.
In the routine check the standard field taken by SAP if you do not want to split to happen based on the field taken by SAP then you need to clear those field in the routine.
Refer following routine code and comment for clerification.
.g. Program FV60C900
DATA: BEGIN OF ZUK,
MODUL(3) VALUE '900',
BUPLA LIKE VBRK-BUPLA, "Business place
LIFNR LIKE LFA1-LIFNR, "Consignor (Vendor Consignment)
MWSKZ LIKE VBRP-MWSKZ, "Tax code
END OF ZUK.
ZUK-BUPLA = VBRK-BUPLA.
ZUK-LIFNR = LFA1-LIFNR.
ZUK-MWSKZ = VBRP-MWSKZ.
VTFL - Check copy control rules
Target Source
e.g. Select F2 - Invoice LF Delivery
Click Item
e.g. Double click on Tan - Standard Item
Check Data VBRK/VBRP - Copy rule number in use e.g. 900
VOFM - Creating a splitting rule
Click Data Transafer -> Billing documents
Copy the standard 1 - Inv.split (sample) to a e.g. 900 series number range
A new splitting rule 900 will be created, follows by a program FV60C900.
In program FV60C900, SAP has a standard internal table called ZUK where you can define fields that must be compared and be equal before a billing may be combined. However, total characters allowed is 40 will be store on the billing header table VBRK.
Reward points if it helps
Vijay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
my feeling is that the split happened not beacuse of the reason that you quoted.
When you create an Invoice in which there could be a split, the system first issues a log of the split where you can know why the split is happening.
If you cancel your invoice and then try to invoice, you can then see the log to know for sure why the split is happening.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
There are many reasons why the invoice split happens.
If there is a difference in the following the invoice will be splitted.
1. Payment terms
2. Payer
3. Billing date
4. Exchange rate
5. Splitting rule in copying control.
etc...
The best way is to check the split analysis of the billing documents.
Prase
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kogi,
Invoice split will takes place for the following reasons
1.Different payment terms
2.Different bill to party
3.Copy control settings at item level between your delivery document type and your invoice document type in VTFL transaction.
Please go through this linkt more about Invoice split
http://help.sap.com/saphelp_47x200/helpdata/en/dd/560f63545a11d1a7020000e829fd11/frameset.htm
I hope it will help you,
Regards,
Murali.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
As per SAP standard invoice date will be generally determined based on goods issue date.. If the goods issue dates are different then billing split will happen..
If u dont want this then u need to change copy control routine from delviery to billing. Please take help from abaper and do the need ful changes to routine by creating cusotmized routine which will meet ur requirement...
Generally invoice split will happen when the following field values differs..
Invoice date..
Payment terms...
Payer...
Regards
sankar
regards
sankar
Edited by: sankar sankar on Jun 24, 2008 11:53 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
12 | |
11 | |
6 | |
6 | |
4 | |
3 | |
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.