1. Integration Playbooks for Procurement
  2. File-Based Data Import (FBDI)

File-Based Data Import (FBDI)

Use the FBDI feature to create data in Oracle Purchasing or to import large volumes of data from third-party or other Oracle applications.

For example, you can create purchase or import purchase orders from external applications into Oracle Fusion Cloud Procurement. For a complete list of business objects that can be imported, see Purchase Orders Import in File-Based Data Import (FBDI) for Procurement. You also can use some file-based data import features to update large volumes of specific blanket and contract agreement attributes in the application. For example, you can update specific blanket purchase agreement line attributes in Oracle Purchasing.

Spreadsheet Templates

Use the provided FBDI templates to quickly create and import data.

Key Features

  • Use spreadsheet templates and macros to organize object data for purchasing-document import and to generate the compressed file (ZIP) file that contains comma-separated values (CSV) files used during the import process.

  • Import large volume of data to create purchasing documents.

Best Practices

  • Batch ID
    • Because the batch ID provides an index, it's best to use the same batch ID in the FBDI spreadsheet and in the import order job context menu for better performance.
    • Concurrent jobs that are submitted expecting to be processed in parallel should have a unique procurement business unit and batch ID combination. Concurrent jobs with the same procurement business unit and batch ID combination will be processed in serial.
  • Purge
    • The volume of data in the interface table could affect the overall performance. Periodically purge this content by running the Purge Processed Open Interface Documents scheduled process.
    • We recommend that you review the po_interface_errors table for any errors and take appropriate actions to re-process them.
    • Records in the po_interface_errors table will not be purged automatically. This is now the default behavior to help with debugging. To revert to purging the records after generating the error PDF, enable the PO_PURGE_INTERFACE_ERRORS profile option.
  • Approved Transactions
    • To import purchasing documents bypassing approval, enter BYPASS in the approval action. Note that do the user doing the import must have the Import Purchasing Document Bypassing Approval function security privilege.
  • Attachments
  • Descriptive Flexfields (DFFs)
    • The valid values for DFFs aren't shown as a drop-down list. They will be treated as free text.
  • Parent-Child Relationships
    • Use the interface keys to enforce parent-child relationships.

Constraints

  • There's no option to re-process the import for a batch that failed validation. The spreadsheet must be loaded again for import.
  • Using FBDI to create Approved Supplier List Entries isn't supported. Use REST APIs instead.

Purchase Orders

Key Features

  • Create purchase orders.
  • Add purchase order lines.

Best Practices

  • This is an ideal way to import many purchase orders in either incomplete or open status.
  • To import closed purchase orders, set the receipt close and invoice close tolerances to 100%.
  • To add new lines to a purchase order, use the Update action. If a purchase order is open, this action will result in a change order.
  • Secured by the Import Purchase Order function security privilege.
  • To source to an agreement, the agreement reference must be provided explicitly. Populate the Source Agreement Procurement BU, Source Agreement, and Source Agreement Line columns on the PO_LINES_INTERFACE sheet. The Source Agreement line is needed only when the source agreement is a blanket agreement.
  • FBDI supports the expense and inventory destination types.

Constraints

  • FBDI doesn't support the creation or update of purchasing documents with more than 10,000 distributions. Exceeding 10,000 distributions can cause performance issues and could lead to failures.
  • Use FBDI instead of REST APIs in these situations:
    • To update (other than adding new lines) and cancel purchase orders, use REST APIs instead of FBDI.
    • To create purchase orders with progress payment schedules, use REST APIs instead of FBDI.
    • To import a purchase order referencing a requisition, use the Requisition Processing Requests REST resource instead of FBDI.

Purchase Agreements

Key Features

  • Create and update blanket and contract agreements.
  • Add blanket agreement lines.
  • Create items during blanket agreement import.

Best Practices

  • This is an ideal way to import many purchase orders in either incomplete or open status.
  • Update is only supported for a subset of attributes on the blanket and contract agreement. See How You Import Purchasing Documents for more information.
  • When adding new lines to a blanket purchase agreement:
    • The header action should be UPDATE.
    • The line action should be ADD or SYNC.
      • For ADD, the line number should not be one that already exists on the document.
      • For SYNC, Purchasing Documents Open Interface (PDOI) updates the line for lines that match. For lines that don't match, PDOI creates a new line on the blanket purchase agreement (BPA).
  • For information about creating items when importing a blanket agreement, see How You Create Master Items from the Blanket Purchase Agreement Import.

Constraints

  • Importing blanket purchase agreement lines using FBDI: 10,000.
  • To cancel and close purchase agreements use REST APIs instead of FBDI.
  • Importing Notification Controls isn't supported.

Related Topics