Introduction
In Oracle Fusion SaaS, every AR invoice print action generates a PDF file attached to the invoice record. By default, this allows users to reopen and print the invoice multiple times—a behavior that many businesses seek to prevent.
However, Oracle’s standard REST APIs do not provide a way to restrict access while keeping the file available for IT personnel. The only feasible approach is to overwrite the invoice attachment with a dummy file, ensuring that users cannot access the original document while allowing IT to retrieve it when needed.
In this post, we introduce a custom solution using Oracle Integration Cloud (OIC), ESS Jobs, and BIP Reports to effectively control invoice document access.
The Business Challenge: Restricting AR Invoice Reprints
Many organizations have compliance or operational requirements that restrict users from reprinting invoice PDFs after the first print. The main challenges include:
✅ Invoices Remain Accessible – Once printed, the invoice PDF is permanently attached to the invoice record.
✅ No Standard API to Remove Attachments – Oracle’s REST APIs do not allow selective removal or restriction of attachments.
✅ IT Must Retain Access – While users should be restricted, IT and administrators need a way to retrieve the original document when necessary.
Our Solution
To achieve this, we developed a solution that:
🔹 Stores the original invoice document reference securely in a DFF (Descriptive Flexfield).
🔹 Automatically replaces the user-accessible PDF with a dummy file to prevent unauthorized reprints.
🔹 Allows IT personnel to retrieve the original document when needed.
Solution Architecture: ESS Job, BIP Report, and OIC Integration
Our approach includes the following components:
1️⃣ A new read-only DFF (Descriptive Flexfield) on the Invoice level called “Printed Document Version Number” to store the original attachment reference.
2️⃣ An ESS (Enterprise Scheduler Service) Job that identifies invoices where the document needs to be replaced.
3️⃣ A BIP (BI Publisher) Report, which retrieves the invoices and triggers an OIC integration via an HTTP XML Feed connection.
4️⃣ An OIC Integration, which processes each invoice, saves the original document reference, and replaces the user-accessible file with a dummy PDF.
Step-by-Step Technical Implementation
Step 1: Create a Read-Only DFF on Invoice Level
• DFF Name: “Printed Document Version Number”
• Purpose: This will store the UCM Document Number of the original invoice attachment for IT retrieval.
• Read-Only Access: Prevents users from modifying or accessing the stored reference.
Step 2: Develop an ESS Job to Identify Printed Invoices
🔹 ESS Job Purpose:
• Runs on a specific invoice or a range of invoices.
• Identifies invoices where:
• A PDF document exists.
• The Printed Document Version Number DFF is blank (indicating the document hasn’t been replaced yet).
🔹 Workflow:
• The ESS Job calls a BIP Report, which retrieves the list of eligible invoices.
Step 3: Use a BIP Report to Trigger an OIC Integration
🔹 Why BIP Report?
• BIP Reports can pass invoice data to OIC using an HTTP XML Feed connection.
• Allows controlled selection of invoices that require processing.
🔹 Workflow:
• The BIP Report queries the invoices that need document replacement.
• Calls an OIC Integration via HTTP XML Feed.
Step 4: OIC Integration – Processing Invoices and Replacing Attachments
The OIC integration processes invoices retrieved by the BIP Report and performs the following actions:
4.1. Store the Original Document Reference in the Read-Only DFF
• Retrieve the UCM Document Number of the current printed invoice PDF.
• Save this value into the Printed Document Version Number DFF using the ERPObjectAttachmentService API.
• This step ensures IT can later retrieve the original invoice if needed.
🔗 Related Blog Post:
For details on using ERPObjectAttachmentService, refer to our previous guide:
📌 Fusion SaaS: AppUI Enable Groovy-Only Solution for SOAP-Based ERPObjectAttachmentService
4.2. Replace the User-Accessible PDF with a Dummy File
Once the original document reference is secured:
• Use the PUT method on the Oracle REST API endpoint:/fscmRestApi/resources/11.13.18.05/receivablesInvoices/{invoiceId}/child/attachments/{attachmentId}/enclosure/FileContents
• Replace the existing file with a dummy or empty PDF, ensuring users can no longer reprint the original invoice.
Solution Benefits
✅ Prevents Unauthorized Reprints
• Users cannot reopen or print the original invoice after the first print.
✅ Ensures IT Can Retrieve the Original Document
• The original UCM Document Number is securely stored in a read-only DFF for IT access.
✅ Fully Automated Process
• The ESS Job, BIP Report, and OIC Integration work together without manual intervention.
✅ Complies with Oracle Fusion SaaS Constraints
• Since Oracle REST APIs do not allow attachment deletion, this approach provides a valid alternative using document replacement.
Conclusion
By implementing this OIC-based solution, we successfully prevent users from reprinting invoice documents while still ensuring IT access when necessary.
This approach:
✅ Adheres to Oracle Fusion SaaS restrictions
✅ Automates document replacement seamlessly
✅ Provides a structured way to store and retrieve original invoices
🔹 Need a custom Oracle Fusion solution?
📢 Contact CID Solutions today to implement tailored automation for your business!