Manage Internal Sales Delivery Address Information
The final delivery address on Purchase Order (PO) header and line is assigned as the delivery address in the Customer Order (CO) batch entry as an order unique delivery address. In addition, the ship-via address identity of the PO header and line is assigned as the ship-via on the CO's order unique delivery address.
The CO header's unique delivery address is either given an identity (#xxxx, where x is a number) or is left as blank, as controlled by the CO type setting 'Create address' in 'CO Type. Open' (OIS010). The CO line inherits the address unless the PO sends in a unique line address.
The CO line's unique delivery address is given the identity * in combination with the order line number. If the same delivery address is received for several order line, then the * identity is re-used for additional order line. The reuse of * identity ensures that order lines are consolidated into the same delivery.
For manual change of the ship-via address on an internal PO, a new ship-via address identity is selected. Upon prompting on the 'Ship-via' field, the program 'Via Address. Open' (CRS300) is displayed for the user to select a new ship-via address identity. For an internal purchase order it is prevented to manually change the individual address lines of the ship-via address, as the internal customer order cannot accept the actual ship-via address lines but only a predefined ship-via identity.
This table shows the default values for the internal customer order's delivery address information at time of internal CO creation:
| Internal CO information | Comment |
|---|---|
| Company name | The field value is set based on the PO's final delivery address. |
| Address (ADR1-4) | The field value is set based on the PO's final delivery address. |
| City (TOWN) | The field value is set based on the PO's final delivery address. |
| County (FRCO) | The field value is set based on the PO's final delivery address. |
| State (ECAR) | The field value is set based on the PO's final delivery address. |
| Postal code (PONO) | The field value is set based on the PO's final delivery address. |
| Country (CSCD) | The field value is set based on the PO's final delivery address. |
| Planning node (PNOD) | n/a
Not supported for internal sales, since these values are not supported for any type of customer order. |
| SPCL code (SPLE) | The field value is left blank. |
| Geo code X, Y, Z | n/a
Not supported for internal sales, since these values are not supported for any type of customer order. |
| Ship via | The field value is set based on the PO order header and line. |
| Rail station (RASN) | The field value is left blank. Internal sales are not supported because the field may differ between the PO and CO. The field is used for calculation of transport cost. Therefore, it is most likely to be set on the side that is responsible for the transportation cost and be left blank on the other side. Another argument for the design is that the field is not printed on the PO document, which means that is not a field that is sent to an external supplier either. |
| Tel no (PHNO) | From the buyer’s user record using the same logic as the PO document. |
| Fax (TFNO) | From the buyer’s user record using the same logic as the PO document. |
| Your ref 1 (YREF) | From CO header. |
| VAT reg no (VRNO) | The field value is set based on the buying warehouse only. It is never retrieved based on the customer master settings, since one customer record may correspond to any number of final delivery addresses of the buying warehouses that may have different VAT reg no.
Note: When the internal customer order is created through direct delivery and a taxable address is applied, the VRNO is retrieved from the delivery address of the external customer order line instead of the buying warehouse. The VRNO from the external customer's delivery address serves as the third-party VRNO in the triangulation scenario for determining VAT, while the VRNO for the actual invoice is based on the taxable address.
|
| Tax code (TAXC) | The field value is set based on the customer master. |
| Geo code (GEOC) | The field value is set based on the buying warehouse only. It is never retrieved based on the customer master settings, since one customer record may correspond to any number of final delivery addresses of the buying warehouses. |
| Route | From CO header. |
| Route departure | From CO header. |
| Place | The field is set based on the receiving warehouse, which is the destination of the PO's final delivery address. |
| Unloading zone | n/a - Not supported for internal sales. |
| Delivery specification | n/a - Not supported for internal sales. |
| Delivery method | From CO header. |
| Delivery term | From CO header. |
| Terms text 2 | From CO header. |
| Harbor/Airport | The field is set based on the internal PO. |
Limitations
- Delivery address: Predefined customer order address identities are not supported for internal sale, which disables functionality such as transportation planning or using the address identity as control object for supply model and pricing.
- Pick up address: Pick-up addresses on the internal purchase order are not transferred to the customer order. The pick-up address type is not supported for any type is not supported for any type of customer order sales, including external internal.
- Ship-via address: It is not enabled to manually write a ship-via address on an internal purchase order. A new predefined ship-via address identity is selected. As always, the dispatch policy parameter 470 'Ship-via control' is set to 1-'Consignee' on (MWS010/H) if the ship-via address on the CO should be used for the delivery.
- Invoice address: Invoice address on the internal purchase order is not transferred to the internal customer order.
- Origin address: For global contract management (GCM). The origin addresses on the internal purchase order is not transferred to the internal customer order. The origin address type is not supported for any type of customer order sales, including external internal.