OIC - ERP - Automated Payment File Transmission Using ERP PR Process, Manage Transmission Configuration & OIC

Working...

🔎 Overview

In Oracle ERP Cloud, the Payment Process Request (PR) generates payment files (ACH/RTGS/FPS/TT, etc.).

Using Manage Transmission Configurations, ERP securely sends the payment file to an OIC SFTP server. An event is generated, which OIC subscribes to. OIC then downloads, transforms, and forwards the file to the target bank or external system.

This architecture ensures secure, automated, and event-driven payment file processing.

📌 Use Case

🎯 Business Scenario

• Organization runs Payment Process Request (PR) in ERP.
• Payment file must be transmitted to bank in specific format.
• File transformation required before sending to bank.
• Need automated, event-driven, secure integration.

🔁 End-to-End Flow

1. PR process runs in ERP.
2. ERP generates payment file.
3. Manage Transmission Configuration pushes file to OIC SFTP.
4. ERP raises transmission event.
5. OIC subscribes to event.
6. OIC downloads file from SFTP.
7. OIC transforms file (mapping/formatting).
8. OIC sends file to target bank SFTP/API.

✅ Solution Architecture & Steps

🟢 Step 1: Configure Payment Process Request (PR) in ERP

Navigate to:

Payables → Payments → Create Payment Process Request

Ensure payment format is configured.

Associate transmission configuration with payment format.

✔ Validate payment file is generated successfully.

🟢 Step 2: Configure Manage Transmission Configuration in ERP

Navigate to: Setup and Maintenance → Manage Transmission Configurations

Configure:

Protocol → Secure File Transfer Protocol (SFTP)

Host → OIC SFTP endpoint

Port → 22

Username/Authentication

Remote Directory

Assign this configuration to payment format.

✔ Test connection.

🟢 Step 3: File Transmission from ERP to OIC SFTP

Once PR completes:

ERP automatically transmits file to OIC SFTP.

Transmission status updates to “Completed”.

An ERP business event is generated.

🟢 Step 4: OIC Event Subscription

In Oracle Integration Cloud:

Create integration using ERP Adapter (Business Event Trigger)

Subscribe to Payment Transmission event

Event contains metadata such as:

File name

Transmission status

Payment reference

🟢 Step 5: Download File from OIC SFTP

Inside main OIC orchestration:

Use SFTP Adapter

Read file from inbound directory

Store file in staging variable

🟢 Step 6: Transform File

Use Mapper

Convert ERP format to Bank-specific format

Apply:

Header changes

Footer calculation

Field reformatting

Encoding changes (if required)

🟢 Step 7: Send to Target System

Based on bank requirement:

Push via SFTP

OR

Call Bank API

OR

Send via secure socket

Log response and update tracking.

🏗️ Architecture Diagram (Logical View)

ERP PR

⬇

Manage Transmission Config (SFTP)

⬇

OIC SFTP

⬇

ERP Event

⬇

OIC Event Subscription

⬇

Main OIC Orchestration

⬇

Transform

⬇

Target Bank

🔐 Security Considerations

✔ Use SSH key-based authentication

✔ Restrict IP whitelisting

✔ Use separate inbound/outbound directories

✔ Enable encryption if bank requires PGP

✔ Mask sensitive payment data in logs

🏆 Benefits

Fully automated payment transmission

Event-driven architecture

Secure file handling

Flexible transformation capability

Reduced manual intervention

Clear monitoring in ERP & OIC

🔚 Conclusion

By integrating Payment Process Request → Manage Transmission Configuration → OIC Event Subscription → Transformation → Bank Delivery, organizations can build a robust and secure payment automation framework.

This approach ensures scalability, traceability, and compliance with banking standards.