# SAP SD Partner Determination Design Template

> Source: https://netray.co/tools/sap-sd-partner-determination-design-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Document your partner functions, partner determination procedures and sources per document level, then export a design page for review.

## Category

sap

## Erp

SAP S/4HANA

## Audience

- SAP SD consultant
- Master data lead

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Project

**Key:** project

**Type:** text

**Default:** S/4HANA Wave 2 Rollout

#### Sales organisation

**Key:** org

**Type:** text

**Default:** 1000

#### Procedure applies to

**Key:** level

**Type:** select

**Options:**

- Customer master
- Sales document header
- Sales document item
- Delivery
- Billing document

**Default:** Customer master

#### Partner determination procedure

**Key:** proc

**Type:** text

**Default:** ZAG

#### Extra partner functions needed

**Key:** extra

**Type:** textarea

**Default:** Sales employee (VE), carrier (SP), forwarding agent (SH), end customer for projects (ZE, custom)

#### Source of partner

**Key:** source

**Type:** textarea

**Default:** Sold-to from the customer master (KNVP). Ship-to defaults from the customer master and may be overridden in the order. Bill-to and payer default from sold-to.

#### Mandatory partners

**Key:** mandatory

**Type:** text

**Default:** AG, WE, RE, RG

#### Open design points

**Key:** issues

**Type:** textarea

**Default:** Decide whether the carrier is fixed per ship-to or chosen per order. Confirm whether hierarchy relationships are needed for key accounts.

**Blocks:**

#### Partner Determination Design - {{project}}

**Body:** Sales organisation: {{org}}
Procedure level: {{level}}
Procedure: {{proc}}

#### Standard Partner Functions

**Table:**

**Columns:**

- Code
- Name
- Typical use
- Mandatory

**Rows:**

**0:** AG

**1:** Sold-to party

**2:** Places the order

**3:** Yes

**0:** WE

**1:** Ship-to party

**2:** Receives the goods

**3:** Yes

**0:** RE

**1:** Bill-to party

**2:** Receives the invoice

**3:** Yes

**0:** RG

**1:** Payer

**2:** Pays the invoice

**3:** Yes

#### Mandatory partners in this procedure

**Body:** {{mandatory}}

#### Additional partner functions

**Body:** {{extra}}

#### Source and defaulting rules

**Body:** {{source}}

#### Open design points

**Body:** {{issues}}

#### Configuration Checklist

**Table:**

**Columns:**

- Step
- Where
- Done

**Rows:**

**0:** Define partner function

**1:** VOPA, partner functions

**0:** Define partner determination procedure

**1:** VOPA, procedures

**0:** Assign procedure to account group or document type

**1:** VOPA, assignments

**0:** Set source and mandatory flags

**1:** VOPA

**0:** Test in XD01 and VA01

**1:** Master data and order

#### Approvals

**Signatures:**

- SD lead
- Master data lead
- Business owner

**Notes:** Standard partner function codes AG, WE, RE and RG are delivered by SAP. Custom codes should start with Z. Confirm names and customising paths in your release.

## Content

**Intro:** Partner determination decides who the sold-to, ship-to, bill-to and payer are on every document. This template captures the design in one page so master data, SD and finance agree before anyone touches VOPA.

**Sections:**

#### How to use it

**Body:** Choose the document level the procedure applies to, name the procedure, then list extra partner functions beyond AG, WE, RE and RG. Describe where each partner comes from: the customer master, the order, or a higher-level hierarchy. Export the page, circulate it to the master data owner and attach it to the blueprint. The configuration checklist at the bottom turns the design into a short build task list.

#### How partner determination works

**Body:** A partner determination procedure is a set of partner functions with flags such as mandatory, not changeable and source. Procedures are assigned by customer account group for the customer master, and by sales document type, item category or billing type for documents. Partners proposed on the customer master (table KNVP) are copied into the order, and then flow to delivery and billing based on copy control.

#### Reading the output

**Body:** Check that every mandatory function has a clear source. If a partner function is mandatory on the sales document but missing from the customer master, order entry will stop with an error. For key accounts with several ship-to addresses, decide whether the default ship-to is stored on the sold-to or picked on each order.

**Bullets:**

- One owner for each partner function
- Custom functions use the Z namespace
- Record what happens to the partner in billing

#### Common mistakes

**Body:** Teams often create a new partner function when an existing one would do, or forget to assign the procedure to the account group, so the customer cannot be created. Another error is making the partner not changeable at document level and then discovering that sales support needs to override the ship-to. Test with a real customer in XD01 and VA01 before transport.

**Cta:** Need help auditing partner setups across a large customer master? Netray can run read-only checks against your ERP data and show you the exceptions.

**Faq:**

#### What are the standard SAP partner functions?

**Answer:** The four most used are AG sold-to party, WE ship-to party, RE bill-to party and RG payer. SAP also delivers functions such as VE sales employee and SP forwarding agent depending on your release and configuration.

#### Where do I configure partner determination?

**Answer:** In customising under Sales and Distribution, Basic Functions, Partner Determination, and via transaction VOPA. You define partner functions, procedures and then assign procedures to account groups and document types.

#### Can partners be changed after the order is saved?

**Answer:** Only if the partner function is not flagged as not changeable in the procedure, and only while later documents have not already used the value. Changes can also trigger repricing or new output.

#### Do I need a different procedure per document type?

**Answer:** Often one procedure is shared across similar order types. Create a separate procedure only when the mandatory partners or sources really differ, for example for consignment or project orders.

## Search terms

sap partner determination design, sap sd partner function template, sap vopa partner determination procedure, sap sold-to ship-to bill-to payer design, sap partner determination document, sap sd blueprint partner functions

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json