Product: Mapping Manager

Article link: http://help.truecommerce.com/en/articles/5878428-mapping-manager-editing-partner-maps

You can edit and perform partner-level mapping by selecting Maps from the Mapping Manager navigation menu, then clicking the Partner Maps tab if it is not selected by default.

On the Maps - [Project] Framework page, click the desired partner map row (Partner/Map/Type) in the grid, then click the Edit button.
Values for each transaction's source and destination can be mapped using one of two preferred methods:
Click the Tools tab on the left pane, then click the specific chevron next to the desired value in the list for mapping;

Or...
Click and drag the value from the Partner Token, Entity Definition, or Tools tab to the destination column in the grid on the right. The middle tab in the left pane will change according to the Entity Definition selection on the Partner Maps page.

The content of the grid on the right is dynamic relevant to what is selected in the left pane. It is on this grid that mappings are created and stored and most tasks are performed. This grid can include:
- Token Mapping
- Lookups
- Line Item Conversions
- Plugin Settings
- Import Format Settings
- Export Format Settings

Trading Partner fields

The content in the Partner Maps | Partner Tokens tab pertains to the particular trading partner with which the customer is doing business. These partner token selections per document (Purchase Order, Invoice, and others) will change according to partner per document.

Under the Partner Tokens tab, trading partner fields can be matched to the fields on the Transaction Detail view within Transaction Manager. Each row in the left pane with the right-pointing arrow represents a tab on the transaction in Transaction Manager. The last field listed is the field name listed in the transaction. The values preceding that field can be subtabs or the group boxes where the field is contained.

Project [Entity] fields

The Projects [Entity Definitions] field tab displays the available fields that can be mapped to and from Transaction Manager. Project fields are accessed when making modifications to token mapping for a specific transaction type. Project values are only available for the Import Definition transactions. Transaction Manager maps the data from your Project software into EDI terms, allowing vendors to interact with trading partners, regardless of their business system.

Additional business system fields may or may not be added for all integrations, depending on the business system.

Tools tab

The Tools tab includes the following expandable subtabs:

Functions - Highlight the desired Memo field in the grid, then expand the Functions drop-down and click the desired Function chevron to insert it into the Memo.
Terms - Use to parse 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 table is an example of the terms description of 2% 10 NET 30 being parsed out into individual term fields during the import process into Transaction Manager.

TRANSACTION MANAGER FIELD	MAPPING TOOL TERMS PARSER VALUE	IMPORT RESULT
Description	[D:Description]	2% 10, Net 30
Discount	[D:Discount Percent]	2
Net Due Date	[D:Due Date]	4/24/2010 (The current date plus 30 days)
Discount Days Due	[D:Discount Days Due]	10
Discount Due Date	[D:Discount Due Date]	4/4/2010 (The current date plus 10 days)

When listed in Token Mapping, Terms fields will start with a D (i.e. "[D: Discount Days]", and more).

TRANSACTION MANAGER FIELD	PROJECT FIELD
Terms.Discount Amount	[D:Discount Amount]
Terms.Discount %	[D:Discount Percent]
Terms.Discount Date	[D:Discount Due Date]
Terms.Discount Days Due	[D:Discount Days Due

Addresses - Use these codes 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 as either store codes or distribution center (DC) codes. The codes can be dragged from under the Tools tab to the Memo box in the grid.

The Address table in Transaction Manager must be populated with addresses for each ship to location.

AccountInfo - Use these codes to define the Project on which integration to use.
Lookups - Lookups in Mapping Manager correspond to Lookup tables in Transaction Manager, and are custom translation tables that can be built based on any criteria in a transaction, then used in both importing and exporting within Transaction Manager. Lookups can only translate on a one-to-one relationship. New Lookup tables can be added at any time.

Lookup tables are stored by Trading Partner within the Trading Partner section of Transaction Manager. See Lookups.

All Lookups have different functions. Default Lookups (such as BIllToAddress, BillToAddress2, and others) are hard-coded, while conversion Lookups are conversions that the customer designates.

It is not one-size-fits-all with trading partners within Transaction Manager. Different trading partners have different Lookup setups for their business systems.

Map as Link Token

Check the Map as Link Token box and select a token from the Partner Tokens tab for inclusion in the grid on the right by clicking its chevron or clicking the dragging it to the grid.

If, for example, Bill To Name was selected with Map as Link Token indicated, but BillTo Name is not in the customer's Project nor on the Purchase Order, Mapping Manager can relay that this data is not available upon import into Transaction Manager from the Project. However, when an Invoice is created, Mapping Manager's Map as Link Token function will seek another Purchase Order with the same token and copy its data from the Transaction Manager Inbox or Received folder.

For details on custom formulas for Partner Maps, see Building, Validating, and Linearizing a Custom Formula.

Field Definitions

Field Definitions are codes that specify instructions to Transaction Manager for importing or exporting data. A number of different field mappings can be mapped using Mapping Manager. Each is represented differently.

Below are examples of each of the fields and a description of how they are labeled in Mapping Manager.

Project fields:

[R:1.5 Header.CustPONo] (Row Based) or [C:5. Purchase Order Number] (Column Based)

Transaction Manager fields:

[T:Main.Invoice Information.PO #]

Lookup Tables:

[F:Ship To Code]

Transaction Manager Setup fields:

[I:Account ID]

Transaction Manager Address fields:

[A:Ship To.Name]

Terms fields:

[D:Discount Days Due]