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

Requisition Import for File-Based Data Import (FBDI)

Use this import option to import requisitions and related entities, such as headers, lines and distributions.

For example, you can create requisitions or import requisitions from third-party or other Oracle Fusion Cloud Applications. For a complete list of business objects that can be imported, see Import Requisitions in File-Based Data Import (FBDI) for Procurement.

Key Features

  • Uses spreadsheet templates to organize object data for requisition import with macros that generate a compressed file containing comma-separated values (CSV) files used during the import process.
  • Imports large volume of data to create requisitions with multiple lines and distributions.
  • Optionally, builds an orchestrated integration process with Oracle Integration Cloud (OIC).

Best Practices

For a large volume of data import:

  • For incomplete requisitions, the total number of lines can't exceed 500 and the total number of distributions per line can't exceed 500.
  • For auto-approved requisitions, the limit is 10,000 lines. For a more comprehensive list of the application limits on requisitions see What's the application limit on requisitions?.
  • When handling a large requisition where more than a 100 distributions are required per line, consider splitting the line for better performance.
  • The maximum batch size parameter limits the number of requisition lines that are batch processed. If the parameter isn't specified, the default value of 2,500 is used as the maximum batch size.

    The parameter limits the number of requisition interface lines processed at one time (per batch) to avoid memory issues. It doesn't limit the total number of requisition interface lines that can be processed.

Common for all use cases:

  • Use the interface line key to indicate the sequence in which the imported lines should be ordered. The interface line key isn't a numeric attribute. If you provide values such as 1, 2, and 114, the lines will be sorted as 1, 114 and 2, and not as 1, 2 and 114. This is because the first character of the attribute decides the sort position first, then the next character, and so on.
  • There are two distinct ways of grouping requisition lines in requisition headers:
    • Requisition line Group-by Code column: Users can provide any value in this column. All requisition lines with the same group code are grouped together in one requisition header. Null values aren't considered for grouping. The Group-by Code column in requisition lines takes precedence while grouping. If the intention is to group based on the group-by input parameter than the group-by code in the line should be set to null.
    • Requisition import Group By input parameter: This parameter accepts the following values: Buyer, Category, Item, Supplier, Location or None. All requisition lines with the same value in the corresponding column will be grouped together in one requisition header. For example, if the Group By parameter is set to Category, then requisition lines with the same category will be grouped together in a requisition header. This form of grouping works across batches.

Data validation for all use cases:

  • Emails are used to identify the preparer, the requester, the approver, and the suggested buyer. Emails should be unique in the organization or the requisition might be assigned to incorrect users.
  • Descriptive flexfield (DFF) context for header, line, and distribution is always defaulted from the Configure Requisitioning Business Function for the requisitioning business unit. Any DFF context provided in the spreadsheet will be ignored. To make sure that DFF segments are properly validated, verify that the profile Import Requisition with Invalid Descriptive Flexfields Allowed (ORA_POR_IMPORT_REQ_WITH_INVALID_DFF) is set to No.
  • Provide item and revision if you have blanket purchase agreement (BPA) lines with master items and revision. Otherwise, the requisition line won't match the BPA line for pricing.
  • The agreement released amount in the BPA header, plus the requisition line amount must be less than or equal to the agreement amount limit in the BPA header. Otherwise, an invalid agreement error will be raised. This validation applies for agreements explicitly provided in the spreadsheet or automatically sourced by the system.
  • Set the Allow requisition-to-agreement unit of measure (UOM) conversion option in the Configure Requisitioning Business Function page, when the unit of measure of the requisition line may not match the unit of measure of the BPA line, otherwise the BPA won't be automatically sourced.
  • When there are multiple active blanket purchase agreements that apply for the same item, the application will try to select the best agreement based on certain criteria. However, there's a way to assign priorities to blanket purchase agreements. See How You Assign Priorities to Blanket Purchase Agreements to Rank Source Agreements for Requisitions and Purchase Orders.
  • The Oracle Self Service Procurement user's preferences setup doesn't apply for requisition import. This means that:
    • The deliver-to organization must be provided.
    • The deliver-to location must be provided if it can't be defaulted from the requester's Oracle Fusion Cloud Human Capital Management location.
    • The charge account is provided in the spreadsheet or is defaulted from the Transaction Account Builder setup. For inventory or work order destinations, the charge account is always defaulted from the account builder. Transaction Account Builder will always be used for deriving accrual and variance accounts.
  • To import requisitions as approved, provide the document status as Approved and the approver unique email. Also, the user doing the import must have the Import Approved Requisition function security privilege.
  • To import attachments and associate them to requisitions, first create the requisition, and then use the ERP SOAP Object Attachment Service web service to upload attachments to requisitions. See:

Constraints

  • For draft requisitions, the maximum number of lines that can be uploaded is 500. For approved requisitions, the maximum number of lines that can be uploaded is 10,000.
  • To update requisitions, consider using REST APIs.
  • To cancel requisitions, consider using REST APIs or SOAP services.
  • The import of legacy data isn't supported. The requisition import via FBDI is to create requisitions to be placed on purchase orders after the approvals are complete.
  • There's no option to re-process requisition import for a batch that failed validation. The spreadsheet needs to be loaded again for import.
  • There's no option to purge the requisition interface tables.
  • The import of requisitions for internal material transfers, maintenance work orders, and with one-time locations isn't supported.
  • For DFF attributes, the valid values aren't shown as drop-down list. They will be treated as free text and will be validated as part of the import validations.

Related Topics