Skip to Content
avatar image
Former Member

Error :Item 000020: delivery split due to conflicting header data (Function

Hi Gurus,

Issue :-

Item 000020: delivery split due to conflicting header data (Function SH: Address Indictr: D <-> E)

Message no. VL033

Diagnosis

Item 000020 cannot be shipped in the same delivery with the other items in the document because the header data (Function SH: Address Indictr) is different. The Function SH: Address Indictr item field has the value E, but in the delivery checked for concatenation it has the value D.

Scenariot:-

2 line items(10 and nd 20) in the Order

I think that the VBPA-ADRDA(adress Indicator) is different for line item 10 and 20 and b'se of that delivery is splitting. But my question iswhy both the line items 10 and 20 , why the ADRDA is different?? and if it is different how to solve this problem to create a single delivery document??

Requirement:-

To create a single delivery document

Regards,

Mohit Singh

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • Sep 17, 2014 at 04:58 PM

    HI!

    I had the same problem in our project and we find a solution:

    Go to tx SE37 and use the following module--> SHP_CHECK_PARTNER_COMBINATION (go to the end of the program)

    I had the problem only with eventual customers so we put an enhancement:

    ENHANCEMENT 1 ZSD_DELIVERY_SPLIT. "active version

    *

    DATA: ls_vbpa TYPE vbpavb,

    lv_xcpdk TYPE kna1-XCPDK.

    READ TABLE lt_vbpa_check INTO ls_vbpa INDEX 1.

    CHECK sy-subrc EQ 0.

    * Chequea si deudor es CPD

    SELECT SINGLE xcpdk

    INTO lv_xcpdk

    FROM kna1

    WHERE kunnr EQ ls_vbpa-kunnr.

    CHECK sy-subrc EQ 0.

    CHECK lv_xcpdk EQ 'X'.

    CLEAR: ls_vbpa,

    lv_xcpdk.

    READ TABLE lt_vbpa INTO ls_vbpa INDEX 1.

    CHECK sy-subrc EQ 0.

    * Chequea si deudor es CPD

    SELECT SINGLE xcpdk

    INTO lv_xcpdk

    FROM kna1

    WHERE kunnr EQ ls_vbpa-kunnr.

    CHECK sy-subrc EQ 0.

    CHECK lv_xcpdk EQ 'X'.

    MOVE 'X' TO ef_partners_identical.

    ENDENHANCEMENT.

    *$*$-End: (1)---------------------------------------------------------------------------------$*$*

    endfunction.



    Hope to help to resolve your problems, too.



    V. Vazquez

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 22, 2011 at 09:12 AM

    Hi,

    As per my knowledge , any duplicate data in the header level will cause the document split. If you want the system to split the delivery, I suggest you do some change for the partner function determine in delivery. The partner is located in the header level in delivery,

    http://www.sap-img.com/sap-sd/delivery-split-because-of-conflicting-header-data.htm

    Hope this could be of some help to you

    Regards

    DSR

    Add comment
    10|10000 characters needed characters exceeded

  • Nov 22, 2011 at 10:27 AM

    From the message what you had indicated, it seems, the address number is different from header to item level for second line item and hence, system is splitting the delivery. Either it should be unique or you have to add this logic to your existing routine assigned in VTLA at item level. If I am correct, in standard, 101 is assigned. Here, you have to add the logic in such a way that system should ignore if address is different from header.

    G. Lakshmipathi

    Add comment
    10|10000 characters needed characters exceeded