====== SAP IDoc Types ======

===== Creating the Type with the Type Editor =====

Once the IDoc XSD is created with transaction **WE60** -> **Menu Documentation** -> **XML Schema** or DTD,
one can build the new Type by creating a new **System Managed Type** inside an existing or a new **Type Library**.\\ 
This can be done by **Create**->**Objectdefinition**->**generate Type Definition**->**from XSD**

{{:images:sign_warning.png?nolink|}}**Note:**Create iDoc XSD with transaction **WE60** -> **Menu Documentation** -> **XML Schema** or DTD

Once the XSD is imported successful, it is important to modify the data type. In particular all children(complex and simply types) of the complex element named **IDOC ** must be moved up one level. 
And the complex element named **IDOC ** has to be deleted afterwards.\\ 


===== Defining the Type within the Type Repository =====
Afterwards the specific **Type Repository** settings have to be defined.
No matter what message direction(()INBOUND or OUTBOUND), one always needs to define the **Entity Type** first, given the **Type Library** has been compiled already and the DLL is known to the eBiss Client.

The remaining **Repository Components** depend on the message direction.

See HowTo **[[en:howtos:data_rail#repositorien_anlegen|Create Repositories]]**

**The following components are necessary for the recognition of IDoc types:**

  - Recognizer: [[en:prozessdefinition:repositorien:erkennungskomponenten:typen|XmlTypeRecognizer]]
  - Analyzer: [[en:prozessdefinition:repositorien:analysator:typen#ebisssapsapidocanalyzer|eBiss.Sap.SapIDocAnalyzer]]
  - Reader: [[en:prozessdefinition:repositorien:lesekomponenten:typen:sapidoc]]

**These components are required for generating IDoc types:**

  - Writer: [[en:prozessdefinition:repositorien:schreibkomponenten:typen:sapidoc]]
  - Containeriser: [[en:prozessdefinition:repositorien:kontainerisierer:kontainertypen|eBiss.ClassLib.Containerizers.PlainContainerizer]]