
Defining and Using a Basic Type
Purpose
An SAP development creates a new basic type, which represents a new business process within which data can be exchanged electronically.
Prerequisites
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.
Process flow
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.
Process flow diagram
Individual steps
General DefinitionsCombining segments and
defining new segments Defining a Basic Type Optional: Creating Messages. Mandatory: Assigning Messages to IDoc Types Creating Object TypesConfiguring inbound processing