Skip to main content
Question

EDI incoming customer order using custom fields

  • January 21, 2021
  • 2 replies
  • 1254 views

Forum|alt.badge.img+8

We are rolling out EDI using IFS and have come across and issue with custom fields.  Standard .XML tags apparently do not handle $ sign.  All of IFS’s standard custom field attribute configuration uses $ in the field name, i.e. ( CF$_SP_ATTENTION, CF$_SP_SHPPING_ACCT).  Below you can see the two fields created on the incoming customer order screen:

 

The .xml file sent from our EDI integrator is showing  below:

 

<?xml version="1.0" encoding="UTF-8"?>

-<ORDERS xmlns="urn:ifsworld-com:schemas:inbound_distribution_transactions_create_customer_order_request">

<CURRENCY_CODE>USD</CURRENCY_CODE>

<CUSTOMER_COMPANY_COUNTRY>USA</CUSTOMER_COMPANY_COUNTRY>

<CUSTOMER_COMPANY_NAME>Webstaurant Store</CUSTOMER_COMPANY_NAME>

<CUSTOMER_POSTAL_ADDRESS>2205 OLD PHILADELPHIA PIKE,,,,USA</CUSTOMER_POSTAL_ADDRESS>

<EAN_LOCATION_DOCUMENT_ADDRESS>23-1855710</EAN_LOCATION_DOCUMENT_ADDRESS>

<EAN_SUPPLIER_DOCUMENT_ADDRESS>39-0792349</EAN_SUPPLIER_DOCUMENT_ADDRESS>

<CF_SP_ATTENTION>levi kravetz 3478669114</CF_SP_ATTENTION>

<CF_SP_SHIPPING_ACCT>339973245</CF_SP_SHIPPING_ACCT>

<HEADER_NOTE>Residential 339973245</HEADER_NOTE>

<LABEL_NOTE>Residential 339973245</LABEL_NOTE>

<ORDER_DATE>2020-07-10T00:00:00</ORDER_DATE>

<ORDER_NO>1775721test</ORDER_NO>

<OUR_CUSTOMER_NO>144840</OUR_CUSTOMER_NO>

<SHIP_VIA_DESCRIPTION>Next Day Air FedEx TRS 133296492</SHIP_VIA_DESCRIPTION>

<RECEIVER_COMMUNICATION_ID>CONNECT</RECEIVER_COMMUNICATION_ID>

<VENDOR_NO>39-0792349</VENDOR_NO>

<WANTED_DELIVERY_DATE>2020-07-10T00:00:00</WANTED_DELIVERY_DATE>

<SENDER_COMMUNICATION_ID>CONNECT</SENDER_COMMUNICATION_ID>

<SHIP_VIA_CODE>202</SHIP_VIA_CODE>

<ALLOW_BACKORDERS_DB>1. No Partial Deliveries Allowed</ALLOW_BACKORDERS_DB>

<MESSAGE_TYPE>ORDERS</MESSAGE_TYPE>

 

When they created the .xml, they said they cannot insert the $ in the xml as it will not allow it.  When trying to load the file without the $, IFS gives this error:

 

So basically is there any way to handle incoming EDI .XML files using standard IFS custom field attributes?

Thanks,

Mark

 

This topic has been closed for comments

2 replies

william.klotz
Superhero (Customer)
Forum|alt.badge.img+21
  • Superhero (Customer)
  • 479 replies
  • January 21, 2021

Hi @svrmhuebner ,

 

I’m not sure IFS will handle mapping incoming EDI 850 with custom XML tags.  I believe IFS will handle only XML tags it knows about.  If you refer to the link below these are the tags in IFS Application 10 Update 8.  https://<YOUR SERVER>:PORT/int/soapgateway?handler=InboundDistributionTransactions&op=CreateCustomerOrder&type=xml_request

 

What we did is we mapped custom data to an existing field so the data would import into IFS into the incoming customer order screen.  Then we create a custom event  on the incoming customer order logical unit that would fire when the state would change to created we’d update the move the information from the two fields on the customer order to our custom fields.  Its a round about way but it works for us.  We could have asked for a customization to IFS but we really limit the customizations so we can upgrade easier not to mention the cost.

 

Regards,

William Klotz


paul harland
Superhero (Employee)
Forum|alt.badge.img+24

I agree with what @william.klotz wrote :point_up:


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings