# SAP IDoc Partner Profile (WE20) Setup Template > Source: https://netray.co/tools/sap-idoc-partner-profile-we20-setup-template > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A fill-in setup sheet for WE20 partner profiles, WE21 ports and the inbound and outbound parameters behind each IDoc partner. ## Category sap ## Erp SAP S/4HANA ## Audience - SAP integration developer - SAP Basis administrator - Interface consultant ## Tool **Kind:** template **Output:** document **Fields:** #### Project or interface name **Key:** project **Type:** text **Default:** Customer EDI 850 to Sales Order #### SAP system and client **Key:** system **Type:** text **Default:** S4P / 100 #### Partner number **Key:** partner_no **Type:** text **Default:** EDI_CUST_1001 #### Partner type **Key:** partner_type **Type:** select **Options:** - LS (Logical system) - KU (Customer) - LI (Vendor) - B (Bank) **Default:** KU (Customer) #### Partner role **Key:** partner_role **Type:** text **Default:** SP #### Port (WE21) **Key:** port **Type:** text **Default:** EDISUB01 #### Port type **Key:** port_type **Type:** select **Options:** - tRFC - File - XML HTTP - Web service - ABAP-PI **Default:** File #### Message type **Key:** msg_type **Type:** text **Default:** ORDERS #### Basic type **Key:** basic_type **Type:** text **Default:** ORDERS05 #### Direction **Key:** direction **Type:** select **Options:** - Inbound - Outbound **Default:** Inbound #### Process code **Key:** process_code **Type:** text **Default:** ORDE #### Processing mode **Key:** trigger **Type:** select **Options:** - Trigger immediately - Collect IDocs - Background job **Default:** Trigger immediately #### Technical owner **Key:** contact **Type:** text **Default:** Priya Nair #### Date **Key:** date **Type:** date **Default:** 2026-10-20 **Blocks:** #### Partner Profile Setup Sheet **Body:** Project: {{project}} System and client: {{system}} Technical owner: {{contact}} Date: {{date}} #### General partner data (WE20) **Table:** **Columns:** - Field - Value - Notes **Rows:** **0:** Partner number **1:** {{partner_no}} **2:** Must exist as logical system, customer or vendor master **0:** Partner type **1:** {{partner_type}} **2:** Drives where the partner number is validated **0:** Partner role **1:** {{partner_role}} **2:** Used for partner function mapping on inbound **0:** Status **1:** Active **2:** Set to inactive to stop processing without deleting **0:** Classification **2:** Optional, for authorization grouping #### Port definition (WE21) **Table:** **Columns:** - Field - Value - Notes **Rows:** **0:** Port name **1:** {{port}} **2:** Name referenced from outbound parameters **0:** Port type **1:** {{port_type}} **2:** tRFC needs an RFC destination from SM59 **0:** Destination or directory **2:** SM59 destination name or file path **0:** Version **2:** IDoc record types version, normally the current one #### Message parameters **Table:** **Columns:** - Field - Value - Notes **Rows:** **0:** Direction **1:** {{direction}} **2:** Inbound or outbound parameter block in WE20 **0:** Message type **1:** {{msg_type}} **2:** Logical message such as ORDERS or DESADV **0:** Basic type **1:** {{basic_type}} **2:** Check the exact version in WE30 or WE60 **0:** Process code **1:** {{process_code}} **2:** Maintained in WE42 for inbound, WE41 for outbound **0:** Processing mode **1:** {{trigger}} **2:** Collect mode needs RSEOUT00 or RBDAPP01 scheduled **0:** Test mode in WE19 **2:** Record the test IDoc number used for sign off #### Verification and sign off **Signatures:** - Interface developer - Basis or integration admin - Business process owner **Notes:** Transaction names are standard SAP, but menu paths and available port types depend on your release. Always confirm process codes and basic type versions in your own system before transport. ## Content **Intro:** A WE20 partner profile is the object that tells SAP which IDoc types a business partner may send or receive and how each one is processed. This template captures every field you need in one document so the setup is repeatable across dev, test and production. **Sections:** #### How to use the setup sheet **Body:** Fill the fields at the top, then export the document and attach it to the interface ticket. The same sheet drives the configuration in three places: the partner profile in WE20, the port in WE21 and the process code in WE41 or WE42. Keeping all three in one view prevents the most common go-live failure, where the partner profile exists in test but the inbound parameter for one message type was never created in the target client. Print or share the PDF with the Basis team so the RFC destination is created before the profile is transported. **Bullets:** - Create the logical system or partner master before the profile - Create the RFC destination in SM59 before the tRFC port - Add one inbound or outbound parameter row per message type - Record the WE19 test IDoc number as evidence #### What each part of the profile does **Body:** The partner number and type identify who is talking to SAP. For EDI trading partners this is usually a customer or vendor number, while for system to system links it is a logical system. Outbound parameters name the receiver port, the basic IDoc type and whether IDocs are sent immediately or collected for a batch job. Inbound parameters name the process code, which in turn points to a function module or workflow that posts the document. Message type and basic type are different things: the message type is the business meaning, the basic type is the segment structure. #### Common mistakes **Body:** Most partner profile defects come from small mismatches that only show up at runtime. An inbound IDoc arrives with a sender partner number that has no profile and ends up in status 56. A process code points at the wrong function module for a custom message variant. A collect mode profile is saved but the job that dispatches collected IDocs was never scheduled, so IDocs sit at status 30 forever. Capturing the processing mode and its dependent job in the sheet makes these gaps visible during review rather than after the first live order. **Bullets:** - Status 56 usually means a missing or inactive partner profile - Status 30 for hours means no dispatch job in collect mode - Wrong partner role breaks partner function mapping - Transport the profile and the port together **Cta:** If you maintain dozens of partner profiles across systems, Netray can help build a read-only inventory of your WE20 data and flag gaps before go-live. **Faq:** #### What is the difference between WE20 and WE21? **Answer:** WE20 holds the partner profile: who the partner is and which message types and process codes apply. WE21 holds ports, which define the technical channel such as tRFC, file or HTTP. An outbound parameter in WE20 refers to a port defined in WE21. #### Do I need a partner profile for inbound IDocs? **Answer:** Yes. SAP checks the sender partner against the control record. If no matching inbound parameter exists for the partner and message type, the IDoc is rejected with a syntax or partner error and typically lands in status 56 or 60. #### Where do I define the process code? **Answer:** Inbound process codes are maintained in WE42 and outbound process codes in WE41. They link a message type to the function module, workflow task or ALE service that performs the processing. #### Can I transport partner profiles? **Answer:** Partner profiles can be added to a transport request from WE20, but many teams recreate them per system because partner numbers and ports differ. Whichever method you use, document the values so each environment is consistent. ## Search terms we20 partner profile setup, sap partner profile template, idoc partner profile configuration, we20 inbound parameters, we21 port setup, sap idoc configuration document, idoc partner profile checklist --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json