Split due to different partner data

[Former Member]

Hi

Initially Order, delivery and billing documents didn't display Ship to Party details at header partnerfunction level.

Consultant did config to display Ship to party details in all above documents at header level.

After that, collective Invoice functionality is not working.

(Split analysis shows different Ship to number)

Any suggestions to fix collective invoice issue.

Split analysis.

Split due to different partner data

PR Fld Name $000000001 $000000002

SH Customer Number 1 2000000078 2000000010

SH Address 0000052083 0000051941

Thanks in advance.

[Former Member · Accepted solution]

check any if any user changed manually partenr data or any thing if differnt it will spilt

[Former Member · Accepted solution]

Thanks Ram.

Recently we added new config which will display ship to party details at header level. Before collective invoice was working with

same Payer, Bill to, sold to and different ship to. But after moving new changes we are encountering invoice split. We are searching for the solution.

Best regards,

Pradeep.

[Shiva_Ram · Accepted solution]

As mentioned before, in the copy control settings (t.code VTFA and VTFL), go to item details. In the field Data VBRK/VBRP, check the routine assigned. You may need to change/enter a new routine (after creating in VOFM) to avoid invoice splitting.

Please have a look into note 1561427 - Billing document split and Note 11162 - Invoice split criteria in billing document for additional information.

Regards,

[Former Member]

Thanks to everyone for your valuable sugessions.

Finally we used userexits to resolve the issue. I just want share the solution with SDN.

Used USEREXIT_NEWROLE_XVBPAK_AVBPAK(RV60AFZD) to delete ship to party from the header and Item.

*Delete Ship-to party from header

IF VBRK-VKORG = 'XXXX' AND ( VBRK-FKART = 'XXX' OR VBRK-FKART = 'YYY' ).

DELETE XVBPAK WHERE PARVW = 'WE'.

ENDIF.

*Added ship-to-party at Item level using USEREXIT_NEWROLE_XVBPAP_AVBPAK(RV60AFZD).

IF VBRK-VKORG = 'XXXX' AND ( VBRK-FKART = 'XXX' OR VBRK-FKART = 'YYY' ).

PERFORM XVBPAP_ROLE_ADD_NEW USING 'WE'.

ENDIF.

----

---

• FORM XVBPAP_ROLE_ADD *

----

---

• ........ *

----

---

• --> LOC_PARVW *

----

---

FORM XVBPAP_ROLE_ADD_NEW USING LOC_PARVW.

DATA : BEGIN OF LOC_KNVP.

INCLUDE STRUCTURE KNVP.

DATA : END OF LOC_KNVP.

DATA : LOC_RC LIKE SY-SUBRC.

DATA : LOC_ROLE_FOUND(1) TYPE C.

CLEAR LOC_ROLE_FOUND.

LOOP AT AVBPAK WHERE PARVW EQ LOC_PARVW.

PERFORM KNVP_READ USING VBRK-VKORG VBRK-VTWEG VBRK-SPART

AVBPAK-KUNNR LOC_PARVW

CHANGING LOC_KNVP LOC_RC.

ENDLOOP.

IF LOC_RC EQ 0 AND

NOT LOC_KNVP-PARNR IS INITIAL OR

NOT LOC_KNVP-KUNN2 IS INITIAL OR

NOT LOC_KNVP-LIFNR IS INITIAL OR

NOT LOC_KNVP-PERNR IS INITIAL.

LOOP AT XVBPAP

WHERE PARVW EQ LOC_PARVW.

LOC_ROLE_FOUND = 'X'.

XVBPAP-KUNNR = LOC_KNVP-KUNN2.

XVBPAP-PARNR = LOC_KNVP-PARNR.

XVBPAP-LIFNR = LOC_KNVP-LIFNR.

XVBPAP-PERNR = LOC_KNVP-PERNR.

CLEAR XVBPAP-ADRNR.

PERFORM KUPAV_READ CHANGING XVBPAP.

MODIFY XVBPAP.

XVBPA = XVBPAP.

PERFORM KUNDENVIEWS_FUELLEN USING LOC_RC.

ENDLOOP.

IF LOC_ROLE_FOUND NE 'X'.

XVBPAP-PARVW = LOC_PARVW.

XVBPAP-PARNR = LOC_KNVP-PARNR.

XVBPAP-KUNNR = LOC_KNVP-KUNN2.

XVBPAP-LIFNR = LOC_KNVP-LIFNR.

XVBPAP-PERNR = LOC_KNVP-PERNR.

CLEAR XVBPAP-ADRNR.

PERFORM KUPAV_READ CHANGING XVBPAP.

APPEND XVBPAP.

XVBPA = XVBPAP.

PERFORM KUNDENVIEWS_FUELLEN USING LOC_RC.

SORT XVBPAP BY PARVW.

ENDIF.

ENDIF.

ENDFORM. "xvbpap_role_add_new using loc_parvw.

[Lakshmipathi]

Yes it is a standard feature that if ship to party code is different while generating deliveries, it will get splitted based on that code. You can deviate this by adding a logic to your existing routine assigned in VTLA

thanks

G. Lakshmipathi

[Former Member]

Thank you for the reply.

We tried to clear the values from VBPA table in VOFM routine. But no use. Could you please explain how can we deviate the split.

Thanks&

Best regards,

Pradeep.

[Lakshmipathi]

As I said earlier, in VTLA, for the field Combination requirement at header level, you would have assigned some routine. Take the help of ABAPer and ask to include a code in such a way that if ship to is different in preceding document (sale order), system should not consider that and club such those documents.

thanks

G. Lakshmipathi

Edited by: Lakshmipathi on Mar 4, 2011 9:14 PM

[Former Member]

Thanks Lakshmipathi for the reply.

As you suggested we can make changes in VBRK table using routine. Any changes to VBPA table will not make effect split.

I think it is not possible through routine(I am developer myself). I have gone through the forum and some people archived through editing the include LV60AB14 in ECC 6.0. But we are in 5.0 and want to confirm the right procedure before making any changes.

Thanks&

Best regards,

Kumar.

[Former Member]

Invoice split due to different partner data

Recently we moved Ship-to(Partner function) to header level. Before collective invoice was working fine. Aftyer the changes SAP started splitting the Invoices.

plz help me on this

Thank you and best regards.

[eduardo_hinojosa]

Hi

Search in forum with the string ZUKRI. The question is how to populate the field VBRK-ZUKRI with ZUK in the VOFM subroutine.

Regards

Eduardo

[Former Member]

Hinojosa,

Thanks for the reply.

we don't need split criteria here. We added partner function(Ship to party) at sales documents header lever. Now SAP standard is creating Invoice split due to different Ship to party. Finally we decided to go with EXIT_SAPLV09A_003 - User Exit Partner Determination (Entry Mode XYZ).

Parameter FIF_PARVW contains the current partner function and FIF_NRART contains the partner type for which possible partner functions should be determined.

For collective invoice this will ignore ship to party at header level.

Thanks to everyone.

Best regards,

Pradeep.