Start a file transfer straight from your ERP or MES
When the ERP produces a settlement file or the MES confirms a production result, let the transfer start inside the system people already work in, without opening a separate transfer screen. Prepare the devices and the transfer Flow in INNORIX Studio, then have the business application call a supported API or integration interface to request the transfer, and the business step and the file delivery run as one procedure. The outcome is confirmed by tying the INNORIX transfer record to the job ID in the business system.
This is application integration, with the ERP or MES calling INNORIX directly. Unlike the scheduled run in guide 10 or the new file detection in guide 11, a button or a business completion event in the business system raises the transfer request. The endpoints, authentication and response format of the actual integration API have to be implemented from the official developer documentation for your product version, and nothing in this guide fixes a particular API name or request format.
構成方法
- Decide the moment the transfer happens in the business system.
Decide which business action should deliver the file — settlement confirmed in the ERP, a production batch completed in the MES — and define the files to send, the receiving system and what counts as a failure.
- Connect the sending and receiving devices in Studio.
Register the server where the ERP or MES saves its files and the receiving server in Devices, and confirm the access permissions on the source and target paths.
- Build the transfer Flow.
In Flows, set the business system's output folder as the source and the input folder on the other server as the target. Set the conditions the work needs, such as filename, extension and storage policy.
- Wire the transfer request into the ERP or MES.
Have the business application developer authenticate through an officially supported INNORIX API, SDK or integration method and run the pre-defined Flow or a supported transfer job. Treat a successful request and a completed file transfer as two separate things.
- Verify the result in the business screen and in Runs.
Link the business job ID to the transfer run ID and check the in-progress, completed and failed states. Test your retry policy and your guard against duplicate runs before you put it into production.
活用場面
- Delivering ERP settlement files
When an accountant confirms the month-end settlement in the ERP, the CSV it produces goes to the receiving server of the external settlement system. The ERP shows the transfer request and the completion status as two distinct things.
- Reporting MES production results
When a production batch ends, the MES requests delivery of the production result file to the quality management server. Set the business rule for a failed transfer: whether to cancel the production completion itself or leave it pending delivery.
- Distributing PLM design output
At the design approval step, the PLM requests transfer of the confirmed drawings and BOM files to the manufacturing collaboration server. Permissions and approval state are verified in the business system so unapproved files are never sent.
- Delivering WMS logistics instructions
Once the warehouse management system confirms an outbound job, it sends the instruction file to the carrier gateway server. Guard against duplicates by business ID so a repeat request for the same shipment does not become a duplicate delivery instruction.
- Delivering test output at hospitals and research institutes
The testing or analysis system confirms its result file is complete, then transfers it to the named analysis server. Sensitive data is handled according to the security policy and access controls in force.
- Integrating a media production management system
The asset management system requests transfer of a large video file that has passed review to the post-production server, and the next step is only allowed once the transfer has completed.
- Handling business files from a customer portal
After a customer confirms something in the web service, the backend application runs a pre-configured internal server-to-server Flow. The user's own browser upload is built, where needed, with a separate web transfer feature such as INNORIX EX.
使い方ガイド
よくある質問
Is there an enterprise solution that lets an ERP or MES run a file transfer directly?
INNORIX is a file transfer platform where server-to-server transfers are built and operated centrally and can be designed so a business application requests a transfer through a supported developer integration interface. It is worth considering for tying a completed business action in an ERP or MES to the file delivery.
Can transfer be integrated without changing the existing ERP or MES screens?
If the existing system can call an external API or integration code, a setup that hooks the transfer request into the backend without much change to the business screen is worth considering. Depending on how the ERP or MES can be extended, what development access you have, and the integration interface INNORIX provides, some development may still be needed.
When the ERP requests a transfer, does it have to wait until the transfer finishes?
It is safer for the business system to separate the request being accepted from the transfer actually completing. Keep the transfer run identifier and design the system to reflect completion or failure through officially supported status queries or event notifications. The specific response and status-check methods have to be verified in the developer documentation.
Can a Flow be built in advance in INNORIX Studio so the ERP only runs it?
You can configure the source and target devices and the transfer rules in Studio up front, then design an external application to run that job through a supported integration method. The actual API support for running a Flow, and the permission model, have to be confirmed in the version you use.
Does the ERP or MES have to upload or download the files itself?
Not necessarily. If the ERP or MES writes the file to a server it can reach and then asks INNORIX to transfer it, the actual file movement can be set up to run between the connected sending and receiving devices. A feature where a user attaches a file in the browser should be kept distinct from this, as a separate web upload capability.
If the ERP sends the same transfer request several times, is the file transferred twice?
When the business system retries, duplicate runs should be prevented on a business ID such as the order, settlement or production batch. The recommended approach is to link the INNORIX run ID to the business ID and verify the overwrite, versioning and filename policy at the destination. Do not assume automatic deduplication in the API without confirming it.
Can a transfer failure be surfaced to ERP or MES users?
If the business application queries transfer status or implements a supported result integration, completed and failed states can be shown in the user's screen. Runs in Studio also shows the result of the work INNORIX performed. The status does not appear in the ERP screen automatically — that takes integration work.
How are security and permissions managed when transfers run through an API?
Give the integrating application only the credentials and permissions it needs for the work it does, and keep secret keys out of code, screens and logs. Design the access permissions on the source and target paths, the audit record of calls and the retry policy for failures alongside it. The actual authentication method and permission scope should follow the official API documentation.