​@PorAlineM check the below public URL:

https://docs.ifs.com/ifsclouddocs/25r1/lang/en/GeneralIFSApplications/AboutEDIMessages.htm?StandAlone=true

For what it is worth, not much has changed in Cloud from 10 in this area.  

I believe in 24R1/24R2, they allowed for some configuration fields to be included in some of the outbound messages.  

If you’re looking for EDI sample JSON files, you’ll also need to review the API explorer and the Outbound Message Viewer on the Landing Page.  

hi,

thanks a lot:)

yes, I can see, looks the columns are the same,

in fact, at first,  I need to do a mapping for Incoming files (DELSH - delivery schedule). do you know what is it about, this JSON files?

I heard JSON files is when you will comunicate with some external system by Rest API right? like request and response by API

I remember in version 10 it was possible to work by reading XML files to receive and send  DELSCH (customer and supplier schedules)...do you know if something change about it?

thanks, 

At a high level, both JSON and XML are sending a data identifier and a value.  Underneath the surface, the presentation is different.  JSON files use key value pairs and arrays where XML uses tags and attributes.  This is just a simple, basic functional explanation.  I am sure technical folks can share many distinct aspects of each. 

Process wise, the inbound file (JSON) can be dropped in an SFTP/FTP directory or posted to a REST API.  From there, IFS processes the file and generates an application message that either passes or fails based on if the inbound message has sent the required items correctly.    

In your example, if the Application Message was generated successfully, then an Incoming Customer Schedule should be created.