Trading partner-specific UOM
This section describes UOM Data Substitution records to enable a trading partner specific unit of measure cross-references. These would be used in scenario where a trading partner uses a UOM code in a different way. For example, is CS. Per X12, CA is the code for CASE. If you or your partner uses CS, then you can use a trading partner specific UOM lookup.
L1_O_USE_TP_UOM
Configuration to enable and disable using outbound trading partner specific unit of measure data substitutions.
- Configuration
- Optional
- Default behavior: If record does not exist or record exists and Partner value is not Y, then LOOKUP_O_UOM logic is followed.
- Related: <tpid>_O_UOM, L1_I_USE_TP_UOM
| Field | Value | Example | Comment |
|---|---|---|---|
| List Name | L1_O_USE_TP_UOM | ||
| Your Value | <tpid> or <tpid> or * | ||
| Partner Value | Y | Use N to disable for specific trading partner ID |
Use to enable trading partner specific unit of measure lookup for trading partners that do not use X12 UOM codes in the standard way. A known example is CS. Per X12, CA is the code for CASE. If you or your partner uses CS, then you can enable a trading partner specific lookup
L1_I_USE_TP_UOM
Configuration to enable/disable using inbound trading partner specific unit of measure data substitutions.
- Configuration
- Optional
- Default behavior: If record does not exist or record exists and Partner value is not Y, LOOKUP_I_UOM logic is followed.
- Related: <tpid>_I_UOM, L1_O_USE_TP_UOM
| Field | Value | Examples | Comment |
|---|---|---|---|
| Your Name | L1_I_USE_TP_UOM | ||
| Your Value | Y | Use N to disable. | |
| Partner Value | <tpid> OR * |
Use to enable trading partner specific unit of measure lookup for trading partners that do not use X12 UOM codes in the standard way.
<tpid>_O_UOM
Cross-reference for trading partner specific outbound unit of measure.
- Cross-reference
- Optional
- Default behavior: If record does not exist, and LOOKUP_O_UOM is not disabled, L1_O_UOM lookup is performed. If no cross-reference is found the UOM from the input is mapped.
- Related: L1_O_USE_TP_UOM, LOOKUP_O_UOM
- Requires L1_O_USE_TP_UOM
| Field | Value | Comments/Examples |
|---|---|---|
| Your Name | <tpid>_O_UOM | |
| Your Value | <your UOM> | |
| Partner Value | <outbound UOM> |
Use if your trading partner uses X12 code in a non-standard way. A known example is CS for CASE. Per X12, CA is the code for CASE. If you or your partner uses CS, you can enable a trading partner specific lookup.
<tpid>_I_UOM
Cross-reference for trading partner specific inbound unit of measure.
- Cross-reference
- Optional
- Default behavior: If record does not exist, and LOOKUP_I_UOM is not disabled, L1_I_UOM lookup is performed. If no cross-reference is found the UOM from the input is mapped.
- Related: L1_I_USE_TP_UOM, LOOKUP_I_UOM
- Requires L1_I_USE_TP_UOM
| Field | Value | Example | Comment |
|---|---|---|---|
| List Name | <tpid>_I_UOM | ||
| Your Name | <your UOM> | ||
| Partner Name | <inbound UOM> |
Use if your trading partner uses X12 code in a non-standard way. A known example is CS. Per X12, CA is the code for CASE. If you or your partner uses CS, you can enable a trading partner specific lookup.