cancel
Showing results for 
Search instead for 
Did you mean: 

2 invoices for one delivery

Former Member
0 Kudos

Hi,

The system create 2 invoices for one delivery and can't create collective billing document.

Item 1 & 2 of delivery x : Invoice 1

Item 3 of delivery x : Invoice 2

they only diffrence i found is in the item type.

Item 1 : TAQ

Item 3 : TAN

what needed to create a collective billing document.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi

Check the criterias,which must be same if you want to combine several deliveries into one Billing document.

They are,

- Payer

- Payment term

- Incoterm

- Billing date

- Destination country

Beside this ,ensure that in the copy control at item level,in VBRK/VBRP field you have value "001".

I think,Billing relevance will not be a cause for split.

You can combine an order-related item and Delivery-related item in one Billing document provided the above criterias are same.

For example, if you have purchased a machine (Delivery related item), installation of the machine (it is a service,so order-related ),you can combine these order related item and delivery related item in one billing document.

Answers (3)

Answers (3)

former_member550050
Active Contributor
0 Kudos

Hi

For billing doc to be combined at item level in VTFL the routine in VBRK/VBRP fields should be 001

But i am not sure if the item categories , that is item types of delivery document are different ,whether the billing will be split or not ( i feel this will be also a split parameter)

But if the billing relevance field in both of them are different ( billing relevance in TAN and TAQ) are different it causes a split in billing which you cannot avoid

So make sure that in VOV7 the billing relevances of both TAN and TAQ are same and try and post back

Regards

Raja

former_member211108
Contributor
0 Kudos

Hi,

In Customizing for copying control, you can specify requirements for splitting to prevent sales orders or deliveries from being combined into a collective billing document.

As a rule, the system combines into one billing document all transactions for the same customer, default billing date and sales organization.

If data from the related reference documents differs in the header fields of the billing document, the system will automatically split the invoice.

The reason for this is explained below:

The billing split uses a field in table VBRK called ZUKRI. This is a field with the ability

to hold 40 characters. Generally, the routine allocated to this field uses an internal table in its

calculation called ZUK. A value of a reference field to check is passed in the routine to a

portion of the 40-character field. The contents of this 40-character value in field ZUKRI is

then compared to the next record to be combined in the billing document. If these two

values of VBRK-ZUKRI are not equal, the document will not be combined.

ZUK is a string of 40 characters that is stored on the billing header table (VBRK).

Therefore, you cannot check a combination of field values in excess of 40 characters.

for example, table ZUK is comparing

u2022 VTWEG Distribution channel

u2022 SPART Division

u2022 VGBEL Document number of the reference document

u2022 terms of payment at header

u2022Billing Document Type

u2022reference document type (i.e. type of order, delivery or billing document on which the sales document is based)

u2022item category in the reference document

Thus those deliveries that do not have the same entry in these fields will be assigned an

individual invoice. (They will be split.)

Should a customer wish to have consolidated invoicing, his billing schedule date must

resemble the dates he wishes to be billed on, and he must realize he will have his invoice

split according to the splitting requirements set globally, not according to his individual

requirements.

Hope this will help you.

Regards,

Atul

Former Member
0 Kudos

Hi

Please check the copy control VTFL at item category level.