Comparing Two Input Columns in Mapping Rules

When defining mapping rules, a common requirement is to apply logic based on the comparison of two different source columns, for example, handling third-party posting when the Partner Consolidation Unit (PU) equals the Consolidation Unit (CU).

The recommended, two-step solution is to create a temporary column (T) to calculate the result of the comparison, and then use the state, {EMPTY} or <>{EMPTY}, of that temporary column to drive your final rule logic.

1. Create the temporary column (for example, T_PUequalsCU)

   Create a new column in your mapping sheet and set it as a temporary column (T). This column calculates the equality of CU and PU using the SUBSTITUTE function.

   

   Logic: The formula removes the first occurrence of the [PartnerConsolidationUnit] value from the [ConsolidationUnit] value.

   • If PU = CU: The entire CU value is removed, and T_PUequalsCU returns {EMPTY}.

   • If PU ≠ CU: A non-empty value (the remainder of CU) is returned, meaning T_PUequalsCU is <>{EMPTY}.

2. Define the rules using the temporary column

   You now use the temporary column to separate the PU=CU case (third-party) from the PU ≠ CU case (Intercompany).

   

   This structure ensures that the system correctly identifies when the two fields are equal and applies the required reclassification or elimination rule.