Mapping Tool

Mapping Tool

Configuration Manager Mapping Tool purpose

The Mapping Tool allows you to create custom mapping profiles to define the correlation between imported XML tag values and document attributes in the ERP system.

Custom document attribute mapping is setup in the Configuration Manager in the Mapping Tool category.

The mapping tool provides a way to map values without changing the XSL transformation files in BPEL.

Mapping from ReadSoft INVOICES

The mapping documents are linked to profiles setup in ReadSoft INVOICES. The Doctype transferred from INVOICES determines the mapping document used. Only one mapping document is used per invoice.

If you have 3 different INVOICES profiles, you might want to have 3 different mapping documents to perform different mappings based on the INVOICES profile type.

Mapping Configuration

Mapping Document

You can define one or more Mapping Documents. Each Mapping Document should be given an appropriate description, and has its own table of mappings. You can define if a Mapping Document should be active or not.

Create a new Mapping Document

1. Click New
2. Supply a Mapping Document Name
3. Supply a Mapping Description
4. Select whether the Mapping Document should be active or not.
5. Click Save

Browse Existing Mapping Documents

1. Use the Next and Previous to navigate between documents.
2. Use the First and Last to navigate to the first or last created document.

Delete an existing Mapping Document

1. Navigate to the Mapping Document that you want to delete.
2. Click Delete
3. Click Save

Mapping Attributes

You can define any number of attribute mapping rules within a given Mapping Document. To create a new attribute mapping:

1. Click Create in the Mapping Rule Table Menu to create a new line.
2. Select the Mapping Document that the attribute mapping should belong to. If the Mapping Document is not active, the mapping attribute rule is not active.
3. Select the Table Name that the parameter you wish to map belongs to. Current available tables are:
   • D4_INVOICES
   • D4_INVOICE_LINES
   • D4_DESCRIPTIVE_FLEX_FIELDS
4. Select the Column Name from the selected Table. Data Type is populated with the Column data type.
5. Optionally, Specify the XML Attribute Name defining the incoming value in the document XML schema.
6. Select whether the Attribute Mapping Rule should be active or not.
7. Select whether the Attribute Mapping Rule should be mandatory or not.
8. Specify whether the Attribute Mapping Rule is a header value. Use this option to determine where to look for XML attributes when importing data from ReadSoft INVOICES.
9. Optionally, define a Default Value. If a Default Value is specified, the defined value is assigned to every document attribute that matches the xml tag. The default value is overwritten if any other method assigns a value to the field.
10. Optionally, define a Sequence. The defined sequence overwrites XML tag value or the default value.
11. Optionally, define a SQL Statement. The SQL Statement precedes all other ways of populating a field.
12. Click Save in the Mapping Rule Table Menu to create a new line.

The hierarchy for populating a field is: (higher level overrides lower level)

1. SQL Statement
2. Sequence
3. XML Tag Value
4. Default Value

To delete an attribute mapping:

1. Select the attribute mapping rule line you want to delete.
2. Click Delete in the Mapping Rule Table Menu to create a new line.
3. Click Save in the Mapping Rule Table Menu to create a new line.

Mapping and Invoice XML

If you are sending invoices in xml format directly to PROCESSIT, for instance from PROCESSIT WebTest, the invoice xml must include a <DOCTYPE></DOCTYPE> xml tag with a value that corresponds to the mapping document you wish to use.

If you do not include the tag, the mapping does not take effect. This is specific to xml invoices.

Mapping Custom Fields

There are two exceptions when mapping custom fields:

• You must select the table D4_CUSTOM_FIELD_VALUES as table name.
• Select the appropriate custom field id.