Skip to main content

We are mapping PDF orders and passing them through ICO, to follow the same path as our EDI orders.  Our PDF orders are being created as Single Occurrence Addresses though.

 

In ICO, we are providing the EAN Address Location - Delivery which matches the Customer Address - “Customer’s Own Address Id”, which is how we connect the EDI orders to IFS customer addresses.  What am I missing?   Are there additional fields required that we are not mapping in ICO to load the Customer stored addresses instead of the the CO creating a Single Occurrence address?

Hi ​@dioluke , great question! While I have limited hands-on experience with IFS Apps 10 specifically, I understand this is a fairly common issue when configuring PDF order parsing to follow the same flow as EDI orders.

It sounds like the system isn’t fully matching the incoming address to a stored Customer Delivery Address, which is why it’s defaulting to a Single Occurrence Address. Even though you're supplying the EAN Address Location – Delivery, there may be additional required fields missing or mismatched in the ICO message. This may also require assistance from your IFS Partner or technical support team to fully troubleshoot.

Here are a few things worth checking:

🔍 1. EAN Accuracy & Format
Ensure the EAN in the ICO message is an exact match to what’s stored in the customer’s delivery address — even small formatting differences (like leading zeros or spaces) can cause the match to fail.

🧩 2. Full Address Field Mapping
IFS often requires additional supporting fields like DeliveryAddressId, CustomerId, street, city, and zip, alongside the EAN, to validate a proper match. Missing one of these can cause the system to create a new single occurrence address.

📥 3. Compare Payloads
If you have access to the XML/BOD of a working EDI order, compare it side-by-side with one of the PDF orders. Differences in how the address data is structured or named could help pinpoint the issue.

🛠️️ 4. ICO Mapping Review
Make sure your ICO mapping includes all relevant delivery-related fields — not just the EAN. Depending on your configuration, fields like DeliveryTerm or AddressUsage may also be needed for proper recognition.

Hope this helps point you in the right direction.

– Aaron

Hi ​@dioluke ,

Previous post is totally right. Please, check the delivery address details you are providing in your ORDERS message. EAN is first used to find the customer id in application, in case it has not been provided in EDI message. So, if customer is correctly fetched, then EAN value should be fine. But then, system should be able to identify univocally the delivery address id for this EAN. If not, and if rest of delivery address details are provided in the message (address1, address2, etc.), then system will identify this as a different address and then check the Single Occurrence.

Another possibility is that you have different address ids configured with the same EAN (Customer Own Address Id). If that’s the case, system won’t be able to identify the Address id for the customer and then will mark the address details provided in message as single occurrence.

Regards,

Pilar

Reply


Terms & ConditionsCookie settings