We are testing implementing EDI Customer orders. For an inbound customer order (EDI850) how is the ship-to location for a customer that has many ship to locations specified in the XML? Today, in our current system, our ship- to locations are coded by an alphanumeric designation Specifically where in the XML should we specify the customers ship to code so that in IFS the correct shipping address is on the order? I hope this makes sense.
Thank you. Any help would be appreciated.
Page 1 / 1
Hi @BPC2710 ,
We are using IFS Application 10 Update 8 and we are a manufacturer who sells products to distributors. Our customers who utilize EDI provide us the specification initially and we work with them to map their information to IFS. We utilize a third party to handle the actual EDI formatting and translation and they hand off to us the IFS XML file for the customer order. Most of our customers utilize x.12 4010 format for the 850, 856 and 810 documents.
We generally map theN1|ST|Ship To Name|92|Ship To Number~ to the IFS XML tag
<EAN_LOCATION_DELIVERY_ADDRESS>Ship To Number</EAN_LOCATION_DELIVERY_ADDRESS>
Most of our customers transmit their customer number or dealer number for the ship to number and we enter that number in the customer record on the address tab in the Customer’s Own Address ID position which is right next to the address ID on the tab. The address id we generally start with 1 and work sequentially since its not used with EDI its the EAN Location that IFS utilizes to find the correct ship to on the customer record.
The only criteria for the Customer’s Own Address ID is it must be unique within the customer record IFS will not allow duplicates. So you and your customer must find a field they can send you to uniquely identify a ship to location. If you add UNIQUE_OWN_ADDR property in the system definitions and set it to FALSE you’ll be able use the same Customer’s Own Address ID in different customer records. If you do not add this property then the Customer’s Own Address ID must be unique across all customer records. We set this property to FALSE because we can not guarantee all customers will have a unique value.
Regards,
William Klotz
Thank you so much for your explanation. It was very helpful. We were mapping as above, but Customer’s Own ID field was not populated for the ship-to’s.
Thank you for the information! We have tested Object Property works on APP9 too. It allow different customers to define same ‘own EAN location’ identifier.
