Common Terms in SAP EDI Implementation

SAP EDI implementation involves several technical terms and concepts. Here's a list of the most common ones, along with their descriptions:

Term	Description
IDoc (Intermediate Document)	A standard SAP data structure used for electronic data exchange between systems (SAP-to-SAP or SAP-to-Non-SAP).
Basic Type	The structure of the IDoc, defining the segments, fields, and data types for a specific business process. Example: ORDERS01.
Message Type	Represents the business document or purpose of the IDoc. It maps to the Basic Type. Example: ORDERS for purchase orders.
Segment	A logical grouping of fields in an IDoc. Segments represent sections of the IDoc. Example: E1EDK01 for header data.
Control Record	The header information of an IDoc, containing metadata like sender/receiver details, message type, and processing status.
Data Record	The main content of the IDoc, containing the business data in hierarchical segments.
Status Record	Tracks the processing status of an IDoc (e.g., created, sent, error). Each IDoc has status updates as it is processed.
Partner Profile	Defines how SAP communicates with a specific trading partner for EDI. Configured in WE20.
Port	The communication channel through which IDocs are sent or received. Configured in WE21.
Logical System	Represents systems involved in the communication process, such as SAP systems or external systems.
RFC (Remote Function Call)	A protocol used for communication between SAP systems. Often used in EDI setups for direct data exchange.
ALE (Application Link Enabling)	Facilitates data exchange within SAP landscapes using IDocs but without external partners.
Process Code	Defines the business logic for inbound or outbound IDocs, specifying how they are processed.
Distribution Model	Configures how data is distributed between SAP systems using ALE. Managed in BD64.
Transaction Code	Shortcuts to specific functionalities in SAP (e.g., WE02 to view IDocs, WE19 for testing).
Basic Data Module	A pre-defined structure used to create or process IDocs. Example: EDI_DC40 (control data).
Partner Type	Categorizes trading partners. Common types: KU (Customer), LI (Vendor), LS (Logical System).
Output Type	Configures how documents like purchase orders or invoices are sent to trading partners.
Processing Status	The current state of the IDoc. Common statuses include:
	- 01: IDoc created.
	- 03: IDoc sent to the receiver/port.
	- 12: IDoc successfully processed.
	- 51: Application error during processing.
Inbound IDoc	An IDoc received into the SAP system for processing (e.g., an incoming order).
Outbound IDoc	An IDoc generated by SAP and sent to a trading partner (e.g., an outgoing invoice).
EDI Subsystem	A middleware or third-party solution used to manage EDI communication and mapping. Example: Seeburger.
Mapping	Transforms IDoc data into an EDI standard format (e.g., X12 or EDIFACT) and vice versa.
Conversion Agent	Software that converts IDocs into EDI messages or vice versa (e.g., SAP PI/PO, B2B Add-On).
SAP TCodes	Transaction codes used for IDoc processing:
	- WE02: Display IDocs.
	- WE20: Partner profile configuration.
	- WE19: Test IDocs.
	- WE30: Create IDoc types.
Qualifier	A code used in segments to identify the type of data (e.g., LI for Line Item, BT for Bill-To).