Skip to main content
Question

How to replace EDI messages from IFS8 in IFS Cloud?

  • November 21, 2023
  • 4 replies
  • 287 views

Forum|alt.badge.img+8

Hello,

Do you think the following approach will be effective in replacing EDI messages from IFS8 in IFS Cloud?

For outbound EDI messages from IFS8, convert JSON to XML using a transformer (perhaps the standard one IFS_JSON_TO_XML_GENERIC?) and apply customized transformers to map fields from EDI messages to IFS Cloud projection fields.

The same logic for inbound, but in a different direction and with the assumption that BizAPIs that were used are no longer available in the Cloud.

If yes then mappings between EDI and Cloud projection for different types of messages are required, do you have something like that?

Or perhaps you have any other ideas to fulfill the requirements?

Best regards

Bart

dsj
Superhero (Partner)
Forum|alt.badge.img+22
  • Superhero (Partner)
  • November 24, 2023

Hi @bartlomiej.pobocha 

 

We have successfully implemented ORDERS (inbound/outbound) and DESADV (inbound) and the steps taken were similar to what you’ve described, so your approach is correct :)

One thing to note that is we developed own java transformers instead of using standard IFS transformers since we found problems with the mappings and it was easier to do our own.

 

Hope it helps!
Damith


AveTonitM
Sidekick (Partner)
Forum|alt.badge.img+9
  • Sidekick (Partner)
  • June 25, 2024
bartlomiej.pobocha wrote:

Hello,

Do you think the following approach will be effective in replacing EDI messages from IFS8 in IFS Cloud?

For outbound EDI messages from IFS8, convert JSON to XML using a transformer (perhaps the standard one IFS_JSON_TO_XML_GENERIC?) and apply customized transformers to map fields from EDI messages to IFS Cloud projection fields.

The same logic for inbound, but in a different direction and with the assumption that BizAPIs that were used are no longer available in the Cloud.

If yes then mappings between EDI and Cloud projection for different types of messages are required, do you have something like that?

Or perhaps you have any other ideas to fulfill the requirements?

Best regards

Bart

I’m working with IFS Cloud upgrade project where IFS apps 10 where DESADV (outbound) messages should be generated from IFS Cloud with same EDI XML schema as IFS apps 10 generated the DESADV messages.

I’ve tried to apply IFS_JSON_TO_XML_GENERIC to the routing address that handle the outbound EDI messages. However the outcome from IFS Cloud is not the same as the EDI messages from IFS Apps 10. Hence the IFS_JSON_TO_XML_GENERIC transformer is not suitable.

With IFS Cloud BizApis are not supported anymore. Is there any solution for this or is it required that all IFS Cloud customers will need to develop custom transformers to be able to generate EDI messages as it was done in IFS Apps 10?


Forum|alt.badge.img+8
  • Hero (Customer)
  • January 15, 2025

@AveTonitM ​@bartlomiej.pobocha 

 

Were you ever able to find a solution for this? We are facing a similar situation.

 

@dsj do you have any resources you would suggest if one were to develop their own transformer as you suggest?

 

Thanks

-LEdwards


AveTonitM
Sidekick (Partner)
Forum|alt.badge.img+9
  • Sidekick (Partner)
  • January 16, 2025
Edwards wrote:

@AveTonitM ​@bartlomiej.pobocha 

 

Were you ever able to find a solution for this? We are facing a similar situation.

 

@dsj do you have any resources you would suggest if one were to develop their own transformer as you suggest?

 

Thanks

-LEdwards

@Edwards 

IFS Cloud didn’t have any suitable inbound/outbound EDI XML-file transformers. IFS Connect uses only generic JSON schemas.

For outbound DESADV messages we developed a BOOMI integration process that handle the IFS Cloud JSON-files and transform them to XMLs.

For inbound EDI messages there is no suitable EDI XML file handling. We developed a BOOMI integration process that parse the EDI message and call a IFS Cloud REST APIs.

 

IFS Cloud 24R2 has a component as below. I’m not sure what it actually includes as we haven’t found any suitable EDI transformers in the system.

IC17305 EDI messages for Supply Chain

Reply


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