Two Billing made through Single PGI

[Former Member]

Hi,experts

In my business this happen for the second time one delivery doc with packing material created in two billing doc.i found split criteria

the split invoice which is generated by assignment number and payment

reference at header level data .(vf03-envirionment --split criteria)apart from this i m not able to compare both doc.so please suggest me how to verify .this is the reason in document to split .

[Former Member]

Hi,

As Brian said, the splitting of invoice happens based on different data at item level and this can be controlled by data transfer routine.

If you know the splitting criteria in analysis then ask your developer to clear it out in VBRP-zukri field. Please note if those fields are cleared out then they wont be appeared on invoice document.

Hope it helps.

Thanks,

Jaydip

[former_member131691]

Hi

when the billing document is being created the system processes each item one at a time
and rolls the information from the item into the header table VBRK. If it processes and item and the
information it is trying to pass to the header differs from what it already has in there it splits the billing document (you can only have one value in each header field)

You want to find out which field is causing the split.
The easiest way to analyse a delivery related billing split from VF01 is as follows:

LV60AA21 -> form FAKTURAPOSI_LIEFERBEZOGEN
...
PERFORM VBRK_VBRP_DATENTRANSPORT USING RC   >>> VBRK created
...
PERFORM XVBRK_BEARBEITEN.   >>> VBRK moved to XVBRK & ovbrk-fix

LV60AB09 -> form XVBRK_BEARBEITEN
...
form xvbrk_bearbeiten.
  xvbrk = vbrk.
  rc = 4.
  if ovbrk-fix  = vbrk.      >>>>>>>>>>>>>>>>>>>>>>>>

As each line is being processed table ovbrk-fix has the previous values and vbrk has the new item

data. If they differ it splits so in the debugger you have to compare the contents of each table to find the problem field. Normally all splits can be avoided with a data transfer routine at the item level where you can set a common value or clear field contents to avoid splits.

Hope it helps you further
Kind regards
Brian