Skip to Content

Partner Determination in Sales order Item level

Hello Experts ,

When a sales order is created , the partners are determined by the partner procedure linked with sale document type header.

As per , standard configuration , the partners SP,SH,BP,PY all copied to all the items as default.

But there is an Item level partner determination procedure that is linked to Item category of the material.

If the partners at item is copied as default from header and also saved later , What is the significance of Item level partner determination procedure ? Suppose if Both are different partner det. procedures , what partner determination will the item perform as priority ? But will it be a case that the partner copied from header need to be available in the item partner determination procedure ? Thanks for your time ,

Add comment
10|10000 characters needed characters exceeded

3 Answers

  • Posted on May 15, 2019 at 07:12 PM

    The significance is that in some cases the partner determination needs to be performed at the item level. You could have an order placed by a corporate HQ to be delivered to two different warehouses. This would be a single purchase order from the customer and they would want it referenced and then billed as a single document. So you'd just create an order with two different ship-to's assigned to each item (or multiple items).

    When partner assignment (or other business data) is maintained at item level it overrides any header level assignment.

    Add comment
    10|10000 characters needed characters exceeded

    • Karthik Kumar was there a question? Not sure I understand your comment...

      There is no need for manual assignment to each item. Have you ever actually tried to enter an order in SAP? You'd see exactly what happens. When you enter a Ship-to at header level, it applies to all the items. Then you can enter a different Ship-to in one or more items, as needed. The rest of the items will still use the header partner. You can observe the entries in VBPA table afterwards. (Not sure if it's the same table name in S4.)

      It's not feasible to maintain "many ship-tos at header level", VBPA table key won't allow this.

      What clarification is needed exactly?

  • Posted on May 17, 2019 at 08:45 PM

    Hi Karthik,

    Since partners can also be internal to an organization, one scenario I could imagine needing the Item Partner Determination is for special internal processing of service items or other special non-stock items like design services etc.

    So, for example, based on an Item Category like DIEN or similar, we add special internal partners for billable services or special handling. Then, using workflow or similar technologies based on these assigned partner functions, one could route notifications to appropriate teams for special handling / processing only when needed based on pre-determined partner relationships.

    Best Regards,


    Add comment
    10|10000 characters needed characters exceeded

  • Posted on May 20, 2019 at 07:20 AM

    Hello Brian ,

    So , as per you told , my understanding is that , for any special Item category like DIEN or any internal partners for billing or any information pass to a specific partner , this partner is exclusively determined through the item category Partner determination .But most cases , it can be only Header to Item partners flow I think. I am quite clear , still , i will try test and find the actuals. Thanks for sharing your knowledge and your time.

    Add comment
    10|10000 characters needed characters exceeded