Use 'Output Service. Open' (MNS216) to define the service identity (ID). The service ID identifies an external application or output server used to process output generated by M3 BE.
Every service ID is connected to a service type that defines the output format for the service. For that reason, one service ID can only support one single output format.
The Communication type defines the technical solution to communicate to the external application or output server.
The field is sent through a TCP/IP socket connection to an output server. Technically, the connector is defined as a port at a host, which is the output server.
An Infor reporting event is created and sent to M3 Event Hub when the file has been created.
The file is placed in M3 Transfer Files.
The file is sent to IDM Output Management using IDM’s Application Programming Interface (API). A search sequence with a maximum of six document types is defined.
An Amazon S3 bucket can be used to transfer large XML files from M3 BE to an external consumer. The Amazon S3 bucket is owned and maintained by the customer and is not a part of the hosted solution. To be able to write XML files to an S3 bucket, the Amazon S3 bucket location and credentials must be configured. This is performed in the Cloud File Transfer Agent Administration Tool in the tab Tenant Configuration. The Cloud File Transfer Agent Administration Tool is found in the M3 Administration Tools menu.
The file is sent to IDM Output Management using IDM’s Application Programming Interface (API), similar to communication type 3 which is IDM Output Mgmt, single interface. The only difference is that communication type allows the ability to simultaneously process XML and CSV in the same batch job.