Skip to Content
avatar image
Former Member

Why the 'Ship-to party' field is not included in VBAK?

Why the 'Ship-to party' field is not included in VBAK?

Thanks!

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Jun 20, 2007 at 02:04 PM

    Hello Hoo Laa,

    The partner information is included in the table VBPA. In VBAK is included only the information which is valid for the whole sales order - for example the sold-to party is the same for all items or also the credit account. You can have different ship-to-s for the different items - or item ship-to might be different from the header ship-to.

    Best regards,

    Lela

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jun 20, 2007 at 01:52 PM

    Hi Hoo,

    Its a SAP STANDARD TABLE.

    If you want to add this you have to create Structure for this and we can add this field in

    the VBAK Table by Using the User Exit. But what would be the Implications later we

    can not say.i Suggest you not to insert this field unless and untill its a compulsary

    Requirment from the client.

    Hope this Clarifies your Doubts and Please Reward If Really Helpful,

    Thanks and Regards,

    Sateesh.Kandula

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jun 20, 2007 at 02:08 PM

    Hi,

    VBAK is for Sales document header data.

    Fields can be copied to the sales document from the master records of the sold-to party, ship-to party and payer. You have the following possibilities:

    Case 1: KNA1 -> VBAK

    You can include a field from the sold-to party (general data) in the sales document header.

    Case 2: KNVV -> VBAK

    You can include a field from the sold-to party (SD data) in the sales document header.

    <b>Case 1: Copy sold-to party field (KNA1) -> sales document header (VBAK)</b>

    You want to use a sold-to party field (KNA1) in the sales document header (VBAK). There are two possibilities for copying fields. They are distinguished by the way in which values are assigned to fields.

    The field exists in KNA1 and can be copied to the sold-to party view KUAGV and to VBAK. The name is the same.

    The field does not exist in KNA1 or VBAK. You must create it there. Note that new data elements and new field names must begin with the letters "ZZ". The names are not the same.

    Proceed as follows:

    1. Make sure that the field exists in the sold-to party view KUAGV. If necessary, enter it in KUAGVZ (= INCLUDE in KUAGV).

    2. Activate the structure.

    3. The way in which a value is assigned to the new fields in the sold-to party view (KUAGV) depends on whether the names are the same.

    If the names are the same, a value is automatically assigned to the field in user exit V05EA1AG via MOVE CORRESPONDING.

    If the names are not the same, you must assign a value to the field manually. The statement is, for example: KUAGV-ZZFELD = LKNA1-XXXXX.

    4. Finally, you must assign a value to the field in the sales document header.

    You do so in program MV45AFZZ in user exit USEREXIT_MOVE_FIELD_TO_VBAK. The statement is, for example:

    FORM USEREXIT_MOVE_FIELD_TO_VBAK.

    VBAK-ZZFELD3 = KUAGV-ZZFELD.

    ENDFORM.

    Proceed in the same way for case 2.

    <b>Case 2: Copy sold-to party field KNVV -> sales document header VBAK</b>

    Include the field in KUAGVZ if it is not contained in KUAGV. Assign a value to the field in MV45AFZZ in USEREXIT_MOVE_FIELD_TO_VBAK. If the names are not the same, do so in V05EA1AG.

    Proceed in the same way to copy fields from the ship-to party or the payer to the sales document. You will find the necessary information in the above basics on copying data.

    Hope this will help.

    Regards,

    Naveen.

    Add comment
    10|10000 characters needed characters exceeded