Price List Type causing Billing Split

[Former Member]

Dear All,

I am getting the following scenario.

I am using Transaction Code VF01 to create a Billing Document with reference to TWO different Delivery Notes. These two Delivery Notes are reference to two different Sales Order. The two Sales Order have the same Customer X.

The first Sales Order was created when the Customer had "Price List Type" (KNVV-PLTYP) as BLANK and the second Sales Order was created when the Customer had "Price List Type" (KNVV-PLTYP) as WHOLESALE.

Now after Post Goods Issue for both Delivery Notes, I am trying to create Billing Document using VF01 with reference to both Delivery Notes. But then I am getting this notification that the Billing Document has been split due to the following reason.

"Split Due to Different Header Data"

"Price List Type (Previous Value) - Blank (New Value) - 01"

Now the question is, does anyone know which criteria will cause this split during Billing Creation. I searched on the forum and someone mentioned the Billing Date, Exchange Rate, etc will cause this. But I don't find that difference in "Price List Type" will trigger this Bill Spliting.

Can anyone please advice where in SPRO or VTFL can I configure this?

Thanks in advance.

[former_member386433]

Dear All,

I have problem about billing split too. The different item price list type effect to billing split.

one sales order was created with two price list type at item level, then create delivery, post goods issue and create billing. Split analysis show that billing document have been split due to different header data, price list type field.

Ivano said if the field is at header level, it cann't be avoided to split blilling. In my case,Is it similar to?

Best regards,

Papaporn.

[ivano_raimondi]

Hi,

the billing header table VBRK has field price list type PLTYP.

It is filled form the correposponding field of sales order.

If two deliveries come from sales orders with different PLTYPs, then the system can only create two VBRK records, and so two separate billing documents.

This cannot be avoided.

Best regards,

Ivano.

[former_member183879]

Hi Ivano,

This is very good analysis.

As Ivano said, because the field is at the header level, this behaviour is unavoidable.

[former_member183879]

Hi,

This may be due to your Z customisation also.

Please go to VBRK-ZUKRI field in SE12, and put a where used list query for all the programs. If it is going to any program with the prefix FV60C*, then go to VOFM and there go to Data Transfer--Invoices and find out the routine number which is nothing but the * in FV60C*. Now find out where is this routine used in copy control. That will give you where the functionality is implemented and what are the other fields which can lead to billing split.

BTW...ZUKRI is the field which will save the split criteria, so any change in the standard split shoudl be enabled only through ZUKRI, thats why I am asking you find where this field is used in program.

Hope this helps you