Shipto name (N1ST02) based on requesting location: <tpid>_O_N102_REQLOC
Lookup for value to send in N1ST02 based on header requesting location. The Shipto Location name is sent by default in N1ST02. These data substitution records enable sending a different value based on the requesting location or shipto location.
- Cross-reference
- Optional
- Default behavior: Shipto Location Name is sent in N1ST02 if matching record is not found.
- Related: MAP_SHIPTO_ACCOUNT, <tpid>_O_SHIPTO, <tpid>_O_N104_REQLOC, <tpid>_O_N102_SHIPTO
To send the Requesting Location in N1ST02, use `REQLOC'.
Field | Value | Example | Comment |
---|---|---|---|
List Name | <tpid>_O_N102_REQLOC | JT_O_N102_REQLOC | n/a |
Your Value | <header requesting location> | RLOC1 | n/a |
Partner Value | REQLOC | REQLOC | N1^ST^RLOC1^91^293084752 |
Send value based on requesting location.
Field | Value | Example | Comment |
---|---|---|---|
List Name | <tpid>_O_N102_REQLOC | JT_O_N102_REQLOC | n/a |
Your Value | <header requesting location> | RLOC1 | Use just reqloc, if that is unique enough |
Partner Value | <N1ST02 value> | CALVIN | N1^ST^CALVIN^91^293084752 |
If requesting locations are standardized across companies, or if different values are required based on a purchase from, then Your Value is a combination. This is similar to the _O_SHIPTO records.
Usage
The Ship To Location name is mapped to N1ST02 by default. Use the <tpid>_O_N102_REQLOC record to send a different value in N1ST02 based on the Header Requesting location.
- Partner Value
- Specify REQLOC to send the header value for requesting location
- Specify a value that you and your trading partner agree upon to send in N1ST02