SAP EDI Configuration: Partner Profiles, Ports and Logical Systems (WE20, WE21, BD54)

Keep this: job aid

EDI partner configuration checklist

• BD54 / SCC4: the client has its own logical system (CMQCLNT100 in CMQ, CMPCLNT100 in CMP), converted with BDLS after every copy.
• SM59: the destination to the middleware passes a connection test and points to the right system (XQ1 for CMQ, XP1 for CMP).
• WE21: the port uses that destination (tRFC for PO 7.5); port names follow the system, for example XQ1_PO and XP1_PO.
• WE20 general profile: partner type and number match the master data (KU 17100001), status A (active), permitted agent set.
• Outbound rows: message type, partner function, receiver port, output mode, basic type (and extension), plus message control: application, output type, process code.
• Inbound rows: message type, process code (ORDE for ORDERS), syntax check setting, trigger immediately or by RBDAPP01.
• Status 56 inbound = no matching inbound profile; status 02 outbound = port or destination problem; status 30 = waiting for RSEOUT00.
• Compare CMQ and CMP partner profiles field by field before go-live; differences are deliberate (port) or defects.
• Evidence for sign-off: WE20 screenshots or export, SM59 test, one inbound and one outbound IDoc per message type with status 53 or 03.