Skip to main content
Skip table of contents

Data-Transformation Statements: Creating Statements Apply To All Trading Partners or Just One

Use data transformation statements (business-logic statements) to systematically alter data to match ERP requirements–either globally or only with specific trading partners.

Data Transformations

Data-transformation statements, (also known as business-logic statements), allow you to systematically alter data to match requirements. You can create or modify existing data transformations and also choose whether those transformations are applied to all documents or just those documents whose text meets a specific condition.

Create Transformations from One of Two Locations

As described in the article "Accessing Tools For Data-Transformation Statements," there are two locations where these tools exist, so there are two locations from which to create or modify transformations. The difference is important:

  • If you are using Conexiom's Configuration Studio, the following instructions apply to individual trading partners that you have selected.

  • If you are using the Transformation Settings in Conexiom Premier, the changes you make will apply to all of your trading partners.

Data transformations can be simple or they can be elaborate. If a transformation you need is very elaborate--not simply translating one listed factor to another, as shown in examples below--we encourage you to submit a change request rather than attempting the transformation yourself.

Examples of Data Transformations

Here are few practical examples of data transformations:

  • Always set Ship-To Country to “US.”

  • If the Unit of Measure is a "Package,"  set it to “PKG”

You can also do something more elaborate, like splitting up a package:

  • Set the Unit of Measure from PKG to individual units, "EA,” (for “each”)

  • Multiply the Quantity by 6, (given there are six units per package)

  • Divide the Price by 6, (given there are six units per package so the price of each unit need to be one sixth of the package price)

Or, as it is expressed programmatically, using the drop-down menu items of the interface below, select the menu items one at a time:

Line 1 / RED - If the Line Item - Buyer UOM is Equal to PKG

Line 2 / GREEN - Set the Line Item - Buyer UOM to EA

Line 3 / YELLOW - Multiply the Line Item - UOM Quantity by 6

Line 4 / PURPLE - Divide the Line Item – Quantity Per Unit Price by 6

Note: Colors correspond to components in the example image pictured below but the colors will not appear in the actual dialog box on your screen).

2 Picture2

Creating Data Transformations

5Picture5

To create a new data transformation, follow these steps.

  1. From the Transformations screen in Premier or the Business Logic screen in Configuration Studio, click Add Logic. The Create Custom Logic dialog displays.

  2. Select whether the data transformation should be run on every document, or only when a certain condition applies.

4 Picture4

Make your selection based on the descriptions in the following table:

Selection

When to Use

Always

To run the logic for every document regardless of any other condition found. This applies to header level information where data should be the same with every document.

Example: “Always Set the Ship-To Country to the US.”

If

Along with creating the data-transforming action, create a condition to trigger when the data transformation is run.

Example: If the unit or measure is “Case,” (the trigger), set the unit or measure to the abbreviation “CS.”

In Step 2, above, if you selected Always, follow these steps:

  1. Click the Action field directly below the Always-radio button and from the drop-down menu, select one of the actions. Depending on what you choose, different fields and menus display to the right of that Action field. For example, if you wanted to create the transformation statement Always Set the Ship To Country to the US, in the first field, you would select Set from the drop-down menu. When you make a selection, two or more other fields display, which are for selecting Values to define the Action.
    Note: For descriptions of possible actions to select, click here. For descriptions of possible Values to select, click here.

    • In each of the Values fields that displayed, by either selecting a choice from a drop-down menu or by entering information in with your keyboard, create a statement to define the transformation.
      To stay with the same example as in Step a, in the second field you would scroll until you found the heading Ship To Address and then select Country. Then in the third field, using your keyboard, you would enter in the letters “US.” (As you enter letters, the application gives you the choice to add those letters as your selection).

In Step 2, above, if you selectedIf, follow these steps:

  1. Of the two fields that display to the right, click the first field to select a value from the drop-down menu. Using the above example, scroll down to Line Items and select Buyer UOM.
    Note: For descriptions of possible Values to select, click here.

    • In the second field, click to select an Condition from the menu. Using the same example, you would select Is Equal To. At that point, another field displays, asking for another value.
      Note: For descriptions of possible Conditions to select, click here.

    • Select or enter a value. Using the same example, you would enter the word “Case.” This completes the condition upon which the action is triggered.
      Note: At this point, you can add another condition to trigger the action. To do so, click Add Condition and repeat the above step.

    • Below the Add New Group bar, click the Action field to display a drop-down menu and select an action. To continue with the example, you would select Set. Another field then displays to the right, asking for a Line Item.

    • Click the field to display a drop-down menu and from it make a selection. For the example, again you would select Buyer UOM. Another field displays to the right, asking for a Value.

    • Enter a value to define the action. For the example, using your keyboard, you would enter the letters “CS.” As you enter letters, the application gives you the choice to add those letters as your selection.

    • To Add more actions, click Add Action. To Add a new group of actions, including conditions and actions, click Add New Group.

    • When finished, click Save Logic.

6Picture6

Possible Actions to Use in Data Transformations

Following are available actions you can take when creating transformations in Configuration Studio.

Action

Description

Example

Add 

 For adding numeric fields.

 Add Shipped Quantity to Scheduled Quantity to calculate the Order Quantity

Add Days

 For Adding Day to date fields

 Add 10 days to the order date to calculate the Due Date

Append Text

Add text to the end of a field

 Append the Company name with '3453'

Combine

 Use two fields together in the output

 Combine the Description and Part Type fields in a single Description Field

Disable Address Lookup

 Turn off Address Alerts

 I don's want to trigger a ship to alert from this customer

Divide

 Divide two numeric fields

 Divide the order quantity by 2. Common for UOM conversions

Multiply

 Multiply numeric fields

 Multiply the unit price by 2. Common for UOM conversions

Pre-pend Text

Add text before the beginning transformation.

 Append the customer number to the beginning of the document number.

Reject and Notify

 Do not process the document and notify the business rep for the trading partner that the document was not processed.

 If the document contains the word Quote please reject the document

Remove Characters

 Remove set characters from a specific field.

 Remove all '-' from the part number

Remove Days

 Remove Days from a date field

 Remove 3 days from the Due Date

Replace

 Replace a specific character within a field with another

 In the part number replace any space with a dash

Set

 Hardcode a valued for a specific field

 hardcode the unit of measure to EA

Set Field to Uppercase

 Set the characters of a field in the output to uppercase

 Always set the characters for Unit of measure to Upper case (ea becomes EA)

Subtract

 Subtract a numeric field from another

 Subtract the shipped quantity from the order quantity for the scheduled quantity

Truncate

 Limit the amount of characters sent for a specific field

 Only send the first 50 characters for description

Possible Values to Define Actions

Following are available Values you can use to define the Action you want to take in the data transformation.

Action

Description

Example

Currency 

Type of money

Dollar, Euro Deutsche Mark

Customer Number

Unique identification of customer in numeric form

10003321

Delivery Terms

Date and or time product or service will be delivered.

05/01/2025, five-day delivery, etc.

Document Date

Date document was created

05/01/2025

Document Number

Unique identification of document in numeric form

50055B 621

Due Date

Date that product of service is to be expected

05/01/2025

Federal Tax

Taxation fee by a country's government

$5.05

FOB

FOB, Free On Board, is a transportation term that indicates that the price for goods includes delivery at the Seller's expense to a specified point and no further

A company buys products from a seller but they are damaged in transit. The seller must deliver new products or reimburse the buyer. 

Freight

Method of transportation and/or carrier

FedEx, UPS, USPS, ground, air, etc. 

Label

Information attached to a shipment's packaging that's used by shipping carriers to ensure a shipment is delivered correctly

Recipient's name, address, city, state, and postal code.

Legal Note

Can list the products that are being sent along with possible conditions and other information. When the order is accepted the system may send an automatic shipping note to the customer.

Itemization of products, terms, conditions, etc. 

Notes

Any extraneous information directed at the recipient

Attention: Bob Smith

Order Discount

Reduction in monetary price of product or service

10% off, "2 for 1," etc.

Payment Method

Means of exchanging money.

Cash on delivery (COD), credit account, wire transfer, Venmo, etc.

Payment Terms

Agreement on time in which payment is made

Cash on demand, Net 60 days, etc.

Revision

Number of times document is changed.

Version 1, v. 2, etc.

Possible Conditions to Use in Data Transformations

The following table lists conditions you can use as triggers in If statements, including definitions and examples.

Condition

Description

Example

Contains

Search a field for string of characters

If the Buyer Part Number Contains “HNY,” then….

Ends with

Select a field and check a string of characters at the end of the field’s captured value.

If the Buyer Part Number Ends With “HNY,” then…

Is greater than

 

Check if the value captured in a numeric field is greater than a set number.

If the Document Total is greater than “$100,000.00,” then…

Is greater than or equal to

 

Check if the value captured in a numeric field is greater than or equal to a set number.

If the Document Total is greater than or equal to “$100,000.00,” then…

Is not empty

 

Check if a field has a captured value.

If the Ship Via is not empty, then…

Is equal to

 

Check if the captured value is equal to either another captured value or a set string.

If the Buyer UOM is equal to “EA,” then…

Is not equal to

 

Check if the captured value is not equal to either another captured value or a set string.

If the Buyer UOM is not equal to “EA,” then…

Is empty

 

Check if a field has no captured value.

If the Buyer UOM is empty, then….

Is less than

 

Check if the value captured in a numeric field is less than a set number.

If the Document Total is less than “$100,000.00,” then…

Is less than or equal to

 

Check if the value captured in a numeric field is less than or equal to a set number.

If the Document Total is less than or equal to “$100,000.00,” then…

Starts with

 

Select a field and check a string of characters at the start of the field value captured.

If the Buyer Part Number starts with “HNY,” then….

 

 

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.