======= Create type records =======

{{:images:sign_warning.png?nolink|}}**Note: ** The specific intended use forces the individual parameterization of the type ((Generally, one type record is created for each individual case. In exceptional cases a combination is possible.)). See also [[en:partnerverwaltung:typset:start#applications|Applications]].

To create a new type record for a partner, click on the corresponding section Trade Partner, System Partner or Reference Partner. Then select the partner for which you want to create a type set and double-click on it. \\  
Then enter the corresponding type set information in the fields of the right window:
^name ^meaning  |
|**Communication direction** ((mandatory))|Select a reference direction (incoming/outgoing) for the communication direction. To do this, click in the field to display the list of reference directions and then click on the corresponding reference direction to select it. |
|**Type** ((mandatory))|Select the[[en:prozessdefinition:repositorien:entitaetstyp:start|]]. To do this, click in the field to display the list of entity types and then click on the appropriate entity type to select it. \\ {{:images:sign_warning.png?nolink|}}**Note: ** The **Type** must always be specified because this determines where the type set is to be applied.|
|**Mapping**((optional))|This specification is **only** relevant for determining a **specific mapping** using the [[en:prozessdefinition:jobs:jobsteps:allgemein:EntityTransformer|]] or [[en:prozessdefinition:jobs:jobsteps:allgemein:MultiEntityTransformer|]]. Choose the mapping. To do this, click in the field to display the list of mappings, and then click on the corresponding mapping to select it. \\ {{:images:sign_warning.png?nolink|}}**Note: ** Here, the **entity** of the **source type**, of the mapping to be used, must be specified in the type set parameter **Type**.|
|**Communication channel**((optional))|This specification is **only** relevant for determining a **specific communication channel** and is queried when using the jobStep [[en:prozessdefinition:jobs:jobsteps:kommunikation:channelsender|]]. Select a [[en:kommunikation:kanal:start|Communication channel]] to be stored for this type set. To do this, click in the field to display the list of channels and then click on the corresponding channel to select it.\\ {{:images:sign_warning.png?nolink|}}**Note: ** Here, the **entity** for which an alternative communication channel (for outgoing messages) is required must be specified in the type set parameter **Type**.|
|**Entity containerizer**((optional))| This specification is **only** relevant for the determination of a **specific containerizer** and is queried when using the JobStep[[en:prozessdefinition:jobs:jobsteps:allgemein:entitymessagecreator]]. Select a[[[en:prozessdefinition:repositorien:kontainerisierer:start|]] to be stored for this type set. To do this, click in the field to display the list of available containerizers and then click on the corresponding[[en:prozessdefinition:repositorien:kontainerisierer:start|]] to select the appropriate one to select\\ {{:images:sign_warning.png?nolink|}}** Note: ** Here, the type set parameter **Type** must be set to **Entity**, for which an alternative container|
|**Related Partner**((optional))((Depending on message direction!))|This parameter is to be used for the **Exceptional case** that this type set is to occur only in the specified combination of message sender and message receiver.|

Complete your entries by clicking on **Save**, so that the type sets are transferred to the eBiss database.