An SAP development creates a new basic type, which represents a new business process within which data can be exchanged electronically.
You require corresponding authorizations (authorization object S_IDOCDEFT, for example, in the role SAP_BC_SRV_EDI_DEVELOPER) for the developments. Development takes place in an SAP System.
The following subsections contain the individual steps. The list can be used as a checklist when defining the new basic type. More information about the required steps and any alternatives can be found in the process flow diagram.
With the help of an example, you can define an actual IDoc type and process the type in a number of different ways. The example is used in each individual step. As a prerequisite, master data for the test customer TESTCUST (partner type KU) and the test vendor TESTVEND (partner type LI) must be present in the system. In addition, the example also assumes that the file port TESTPORT has been created.
Combining segments and defining new segments
Optional: Creating Messages. Mandatory: Assigning Messages to IDoc Types
Writing Function Modules (Outbound)
Creating and Assigning Process Codes
Testing Outbound Processing for the New Basic Type
Configuring Direct Inbound Processing (with ALE)
Creating a New Function Module
Maintaining the Attributes of a Function Module
Assigning a Function Module (Direct Inbound Processing)
Assigning a Process Code (Direct Inbound Processing)
Defining a Partner (Direct Inbound Processing)
Configuring Inbound Processing Using Workflow
Defining Inbound Processing as an Object Method
Creating a Task (Inbound Processing Using Workflow)
Creating a Process Code (Inbound Processing Using Workflow)
Creating Tasks (Exception for Workflow Inbound)
Defining a Partner (Inbound Processing using Workflow)
Testing Exception Handling (Inbound Processing Using Workflow)
Troubleshooting in Workflow Processing