Map Editing
Click Edit on the Partner Maps grid control bar to add or modify field definitions for the trading partner map you selected.
|
NOTE Mapping Manager has locking mechanisms to prevent users from editing maps while they are in use by someone else. |
The section covers the tools, components, and process for editing your trading partner maps:
Mapping Page
The Mapping page is launced for editing a specific trading partner's import or export map. For example, if you were to select your Amazon Purchase Order map, then this task page would be labelled Mapping – Amazon – Purchase Order, where the partner and entity are identified in the page header.
The Mapping page is divided into the Mapping and Summary workspaces, where:
|
Mapping |
Primary workspace for adding or modifying field definitions. The split-panel configuration allows you to choose elements and values from the panel on the left and apply them to the definitions you are editing using the grid on the right, as outlined in the sections that follow. |
|
Summary |
Utility workspace for monitoring previous activity associated with the currently-selected map. For details, see Mapping Summary. |
Elements and Values
The panel on the left side of the Mapping workspace lists all the elements and values that can be used to create your mapping definitions. For usage, see see Editing Maps. Switch between the three tabs to access different panel contents described below.
Partner Tokens
The initial tab lists token mappings aligned with the Mappings Tokens from the TrueCommerce EPP, as created by the TrueCommerce Mapping Services. Tokens are the values used for mapping the correlation between EDI fields and your entity fields within a transaction type. For details, see Tokens.
Note that when the Map as Link Token checkbox is set (under the Partner Tokens control) this can be used to link a selected token back to the originating inbound document and pull the value from it. For details, see Map as Link Token.
"Entity" Name
The middle tab lists the integrated transaction fields pertaining to the map entity identified in the page header ("Purchase Order" in the example above). The fields listed under this tab reflect the mapping definitions that may be edited on the grid. Export field definitions are the transactions and options used when exporting to th entity from Transaction Manager. Import field definitions are the transactions and options used when importing the entity into Transaction Manager.
Tools
Under this tab, the panel is subdivided into five sets of tools, each with different purposes for use in your field definitions:
Functions – Lists the functions that can be applied to the mapping logic.
Terms – Parses out the individual terms fields required on an EDI transaction, based on the invoice date and the terms description being passed in on an import into Transaction Manager. This is most commonly used for invoices being imported into Transaction Manager.
Addresses – For when trading partners want to reduce the number of characters being sent in an EDI transaction. The address code is converted to your actual address by your trading partner's EDI system. Address codes can be entered into the Address table. They can be either store codes or distribution center (DC) codes.
AccountInfo – Defines the Project on which integration to use.
Lookups – Corresponds with Lookup Tables in Transaction Manager. These are custom translation tables that can be built based on any criteria of a transaction and used in both importing and exporting with Transaction Manager.
For details, see Mapping Tools.
Mapping Definitions
The two column grid on the right side of the Mapping workspace is where field definitions are created and edited according to the direction of your map. Import definitions are configured to map your Project fields (source) to Transaction Manager fields (destination). Export definitions map your Transaction Manager fields (source) to Project fields (destination).
The first column of each row is the destination, to where you are passing the values in.
The second column or each row is the source, where you are pulling the values from. It contains an editable text box for adding or modifying mapping instructions, using tokens, lookups, line item conversions, plugin settings, and import/export format settings. See Editing Maps below.
Use the Search Elements search box and/or Hide Unmapped option to filter records displayed on the grid. If you are pulling values from Transaction Manager you can also use the Row/Column Selection box to filter records. Required fields should already be listed on the grid whether or not they include the code elements necessary for mapping.
Field Definitions
As mentioned, the second column of each field definition is where your code elements (instructions) can be added for importing or exporting data. A number of different fields can be mapped. Following are some examples of fields with descriptions of how they would be labeled.
Project:
[R:1.5 Header.CustPONo] (Row Based) or [C:5. Purchase Order Number] (Column Based)
Transaction Manager:
[T:Main.Invoice Information.PO #]
Lookup Tables:
[F:Ship To Code]
Transaction Manager Setup:
[I:Account ID]
Transaction Manager Address:
[A:Ship To.Name]
Terms:
[D:Discount Days Due]
If desired, you can also build a custom row/line function for the definition via Custom Formulas.
Editing Process
There are different ways to add or insert items from the left panel into the import or export definitions selected on the right. Depending on the token/element required, you can click either the or controls or you can drag selected items and drop them into the definition. You can also enter hard-coded values directly in the definition text box.
Click Save on the grid control bar to commit your changes. For deployment to Transaction Manager, click Deploy on the Action Bar.
|
IMPORTANT If you receive the message that mapping values are in use by another user, please consult that user before proceeding with deployment. See Multi-User Access for more information. |
What can I do?
-
Create Lookup Tables for use in your field definitions
-
Check out your Mapping Summary
Related Topics