Invoice

[Former Member]

Pls. provide any idea about the item-wise invoice splitting.

[Former Member]

Suppose, in the Delivery you have two items and they have different Payment Terms, so when you create a Billing document for the Delivery, System will automatically splitt the Delivery into two invoice.

Beacuse, Payment term is a header data in Billing document.

In one billing document you can not have two Terms of Payment like wise you can not have two Payer in one Billing document.

If the header data are not same , then there will be automatically invoice splitt take place. It is already defined in the standard system, through the routine in the copy control in VBRK/VBRP field.

Combination criteria of different delivery items into one billing document are,

Payer,Payment Term, Billing Date,Destination country & Incoterm.

If they are not same then there will be automatic invoice splitt.

[Former Member]

first need to go for copying controls either from sales to billing (invoice) or delivery to billing or billing to billing

use transactions (vtaa,vtaf,vtla,vtfa,vtfl,vtff) all possibilities for copy controls. this basicly is flow of doc to doc. (may it be sales to billing, del to bil, or bil to bil etc..)

-> this is where you see the Item category and you control whether split is possible or not with the indicator"B". eg: representing split in invoice based on item category. The field here "data VBRK/VBRP" (headre/item)whcih actually is used for splits or combining different deliveries. create a splitting rule using VOFM (you need access key to get here). Here you define comparisions for the fields at header table and item tables and the comparision fields say SPART"division". "purchase order "BSTKD Instance: 5 sales orders combined into 2 deliveries and the split at the invoice would be 5 individual billing with respect to fields PO and DIv. of each sales order would let you create 5 billings. You need to define the exact "field" in the comparisions both at header and item level that could lead to invoice split. the key here is the field that is different

from header to item will cause split at the item level.