Purchase Order Fbdi Template Oracle Fusion

Standard Operating Procedure: Procurement Document Ingestion via File-Based Data Import (FBDI) in Oracle Fusion Cloud ERP

1. Document Control Block

• Document ID: SOP-TR-ORA-FBDI-PO-042
• Effective Date: October 24, 2023
• Version: 4.2.0
• Review Cadence: Semi-Annual
• Target Audience: Enterprise Integration Architects, Procurement Operations Managers, Database Administrators, Supply Chain Systems Analysts

2. Executive Summary & Scope

This Standard Operating Procedure (SOP) defines the mandatory, institutional-grade protocol for executing high-volume purchase order (PO) creation, modification, and closure within Oracle Fusion Cloud Procurement using the File-Based Data Import (FBDI) architecture.

Adherence to this protocol is mandatory to maintain compliance with Sarbanes-Oxley (SOX) IT General Controls (ITGC) regarding financial data integrity, segregation of duties (SoD), and master data governance. This SOP applies to all legal entities, business units, and shared service centers operating within the enterprise Oracle Fusion Cloud ERP ecosystem (Release 13+).

3. Prerequisites & Tool Requirements

• Software Access & Utilities:
  • Oracle Fusion Cloud Procurement application instance with administrative or designated integration-user provisioning (Role: Procurement Application Administrator or IT Security Manager).
  • Microsoft Excel (Office 365 ProPlus or Excel 2019/2021) with embedded Microsoft Visual Basic for Applications (VBA) enabled for macro execution.
  • Oracle Enterprise Repository (OER) certified PurchaseOrderImportTemplate.xlsm matching the exact target Oracle Cloud quarterly release patch.
  • Secure File Transfer Protocol (SFTP) client (e.g., WinSCP, FileZilla Enterprise) or direct WebCenter Content (WCC) access for file staging.
• Data & Configuration Prerequisites:
  • Target Business Unit, Buyer Name, Requisitioning Business Unit, Bill-to/Ship-to Locations, and Supplier Site mappings pre-validated in Oracle Cloud.
  • Open accounting periods verified as Open or Future Entry within Oracle Fusion General Ledger and Payables.

4. Roles & Responsibilities (RACI Matrix Table)

5. Step-by-Step Operational Procedure

Phase 1: Template Acquisition and Data Staging

• 1.1 Download the exact version-matched PurchaseOrderImportTemplate.xlsm from the Oracle Enterprise Repository corresponding to the current production cloud quarterly update.
• 1.2 Enable Excel macros and clear any legacy sample data contained within the worksheet tabs (PO_HEADERS_INT, PO_LINES_INT, PO_DISTRIBUTIONS_INT).
• 1.3 Map source enterprise resource planning (ERP) or legacy database extracts to the mandatory columns of the FBDI template, enforcing strict data typing (e.g., string limits, date format YYYY-MM-DD).
• 1.4 Validate that all mandatory foreign keys (PO_HEADER_ID, INTERFACE_SOURCE_CODE, ACTION) align with Oracle Fusion Lookup Codes and Flexfield configurations.

Phase 2: CSV Generation and Cloud Staging Transfer

• 2.1 Execute the macro within PurchaseOrderImportTemplate.xlsm to generate the comma-separated values (CSV) zip package (PoImport.zip).
• 2.2 Verify the integrity of the generated CSV files within the archive to ensure delimiter consistency and absence of truncated string vectors.
• 2.3 Establish a secure connection to the Oracle Fusion WebCenter Content (WCC) server using the designated integration user credentials.
• 2.4 Upload PoImport.zip to the specific content account: scm/po/import (Account: cgp/procurement/import).

Phase 3: Interface Loading and Execution

• 3.1 Navigate to Oracle Fusion Cloud Procurement > Scheduled Processes.
• 3.2 Invoke the Enterprise Scheduler Service (ESS) job: Load Interface File for Import.
• 3.3 Set parameters:
  • Data File: Select the uploaded PoImport.zip from the content repository.
  • Import Process: Select Import Purchase Orders.
• 3.4 Submit the ESS job and record the resulting Process ID (Parent Job ID). Monitor child processes until completion status reflects Succeeded.
• 3.5 Navigate to Procurement > Purchase Orders > Task Panel > Run Import Purchase Orders (if not auto-chained by the interface loader).
• 3.6 Configure parameters:
  • Batch ID: Leave blank (to process all staged uncommitted batches) or input specific batch identifier.
  • Action: CREATE or UPDATE.
  • Document Numbering: Choose pre-assigned or automatic based on enterprise numbering schema.
• 3.7 Submit the import process and track the generated ESS job to completion.

6. Quality Assurance & Verification Criteria

• Audit Checklist:
  • Interface error logs reviewed via the View Import Exceptions diagnostic report. Zero critical errors allowed in staging tables.
  • Successful record count in PO_HEADERS_ALL matches total record count declared in source dataset manifest.
  • Financial impact review: Total commitment values cross-referenced against departmental budgetary controls and tolerance limits.
• Tolerance Thresholds & Benchmarks:
  • Processing Velocity: Maximum allowable processing threshold of 5,000 purchase order lines per 15-minute ESS batch interval.
  • Error Rate Benchmark: Target < 0.01% interface failure rate due to data validation anomalies; any failure rate exceeding 1.0% mandates immediate batch rollback and root-cause analysis.

7. Practical Troubleshooting Scenarios

Scenario A: Interface Failure Due to Invalid Supplier Site Assignment

• Symptom: ESS job Import Purchase Orders completes with warning/error status; interface table PO_INTERFACE_ERRORS displays error code PO_PJC_INVALID_SUPPLIER_SITE.
• Immediate Corrective Action Protocol:
  1. Query the PO_INTERFACE_ERRORS table using the specific BATCH_ID to isolate the affected INTERFACE_HEADER_ID.
  2. Access Oracle Fusion Procurement > Suppliers work area and verify that the specified Supplier Site is active, assigned to the correct Procurement Business Unit, and tax-profiled.
  3. Update the source staging table or re-export the corrected record within the Excel template.
  4. Clear the errored interface records using the Oracle-provided purge scripts or interface UI correction tool.
  5. Re-zip, re-upload, and re-execute the import sequence from Phase 2, Step 2.3.

Scenario B: General Ledger Period Closed Exception

• Symptom: Purchase orders remain stuck in interface tables; audit log reports error PO_PO_CLOSED_PERIOD or APP-FND-01564: Date falls in a closed period.
• Immediate Corrective Action Protocol:
  1. Coordinate with the Enterprise General Ledger Accounting Manager to verify the status of the target accounting period in the Ledger Options.
  2. If the transaction date falls within a hard-closed period, either:
     • Re-open the corresponding GL period via Financials Accounting Hub (subject to compliance sign-off), OR
     • Update the FBDI template ACTION_DATE and distribution accounting dates to map to the current open fiscal period.
  3. Re-run the Load Interface File for Import and Import Purchase Orders jobs after updating the staging payload.