Functional profile is a collection of TPM templates that uses custom key values. During runtime message mapping you can access these values in two ways as discussed in the purpose section below.
The default key-value pairs defined in a template are applied to test and production values. You cannot add a new key-value pair to an existing profile but you can edit any existing values in a profile. During message mapping runtime, either the test or production value is returned based on the selected system environment. You can configure the system environment as shown in the figure below:
The figure below explains different sections in Functional Profile screen:
The figure above describes a runtime message mapping scenario, wherein an Idoc XML file is mapped to an EDI XML file using a functional profile that is defined as per an agreement.
For example, you can build a functional profile for processing transaction requirements such as material codes, partner specific delimiters and so on.
See the following links for more information:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
13 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 |