You can use addressee scenarios to find a valid address to which to send a document. The address can be, for example, a postal address or an email address.
Name | Responsible | Description |
---|---|---|
Set up addressee entity relations |
Designer |
Before you can set up and use addressee scenarios, set up the addressee entity relations. Use an addressee entity relation to define from where to get the address information for a table and entity combination. |
Set up addressee types |
Designer |
An entity can have several types of addresses. For example, business address and invoice address. For each entity, you can set up the required address types. |
Set up addressee scenarios |
Designer |
You can use an addressee scenario to find a valid address to which to send a document. The address can be, for example, a postal address or an email address. For each addressee scenario, you can define several priority lines. An addressee scenario priority line links an address type to an output type and entity. When an addressee scenario is applied, the priority lines are checked in sequence to find valid address information. |
Set up addressee profiles |
Designer |
Usually, the addressee scenario, as defined for the document type, is used to find the applicable address. However, in some cases another addressee scenario can be required. In this case, you can set up an addressee profile for a specific record. Use the addressee profile to indicate which other addressee scenario must be used in case of a specific addressee scenario and document type combination. Before you can set up an addressee profile, set up the 'Addressee setup' button for the applicable form. Example: For document type 'Contract', scenario 'A' applies to most customers. So, you define scenario 'A' for the communication profile of type 'To'. For customer '123', for document type 'Contract', scenario 'B' applies. Set up the 'Addressee setup' form button for the CustTable form. For customer '123', set up an addressee profile. This addressee profile says: For customer '123', in case of scenario 'A' and document type 'Contract', use scenario 'B'. Note: In the steps, as an example, an addressee profile is set up for a customer. |
Name | Responsible | Description |
---|---|---|
Set up addressee entity relations |
Designer |
Before you can set up and use addressee scenarios, set up the addressee entity relations. Use an addressee entity relation to define from where to get the address information for a table and entity combination. |
Set up addressee types |
Designer |
An entity can have several types of addresses. For example, business address and invoice address. For each entity, you can set up the required address types. |
Set up addressee scenarios |
Designer |
You can use an addressee scenario to find a valid address to which to send a document. The address can be, for example, a postal address or an email address. For each addressee scenario, you can define several priority lines. An addressee scenario priority line links an address type to an output type and entity. When an addressee scenario is applied, the priority lines are checked in sequence to find valid address information. |
Set up addressee profiles |
Designer |
Usually, the addressee scenario, as defined for the document type, is used to find the applicable address. However, in some cases another addressee scenario can be required. In this case, you can set up an addressee profile for a specific record. Use the addressee profile to indicate which other addressee scenario must be used in case of a specific addressee scenario and document type combination. Before you can set up an addressee profile, set up the 'Addressee setup' button for the applicable form. Example: For document type 'Contract', scenario 'A' applies to most customers. So, you define scenario 'A' for the communication profile of type 'To'. For customer '123', for document type 'Contract', scenario 'B' applies. Set up the 'Addressee setup' form button for the CustTable form. For customer '123', set up an addressee profile. This addressee profile says: For customer '123', in case of scenario 'A' and document type 'Contract', use scenario 'B'. Note: In the steps, as an example, an addressee profile is set up for a customer. |