Shipto based on requesting location: <tpid>_O_N104_REQLOC
Cross-reference lookup for N1ST04 based on header requesting location.
- Cross-reference
- Optional
- Default behavior: Perform the <tpid>_O_SHIPTO lookup if a record does not exist.
- Related: MAP_SHIPTO_ACCOUNT, <tpid>_O_SHIPTO, MAP_REQUESTER
| Field | Value | Example | Comment |
|---|---|---|---|
| List Name | <tpid>_O_N104_REQLOC | JT_O_N104_REQLOC | n/a |
| Your Value | <requesting company>+<requesting location> | 1022+RLOC1 | Values are from the PurchaseOrderEDIOutput header record. |
| Partner Value | <value to map to N1ST04> | 1022RLOC1 | N1^ST^SHIPTO NAME^91^1022RLOC1 |
| Field | Value | Example | Comment |
|---|---|---|---|
| List Name | <tpid>_O_N104_REQLOC | JT_O_N104_REQLOC | n/a |
| Your Name | <requesting location> | UNIQR | If you have single company or unique req location. |
| Partner Value | <value to map to N1ST04> | 679999 | N1^ST^SHIPTO NAME^91^679999 |
Usage
This data substitution enables you to send an identifier in N1ST04 that is specific to the requesting location if the trading partner requests it. An example is ordering from Staples for desktop delivery. The default is to send shipto account number in N1ST04. Line level requesting location information is sent in SDQ segments. Use the <tpid>_O_N104_REQLOC record to send a value in N1ST04 based on the requesting company and requesting location.
- If a _O_N104_REQLOC is found, then the Partner Value is mapped to N1ST04. No further _O_SHIPTO processing is performed.
- If a _O_N104_REQLOC is not found, then _O_SHIPTO processing is performed.