1. Using Procurement
  2. Import Requisitions

Import Requisitions

As a buyer, you can import requisitions into Oracle Fusion Cloud Procurement from other Oracle applications or other external applications.

Before You Start

Only a buyer can run the import process. Before you run the import process, you must have loaded the requisition data into the appropriate interface tables.

Note: You can load requisition data to interface tables using predefined templates and the Load Interface File for Import scheduled process. These are both part of the External Data Integration Services for Oracle Cloud feature.

For more information refer to the Oracle Fusion Cloud Procurement: File-Based Data Import (FBDI)for Procurement guide on the Oracle Help Center.

Import Process

To run the process to import requisitions, follow these steps:

  1. In the Purchase Agreements or Purchase Orders work area, on the Tasks tab, open the Import Requisitions task.

  2. On the Import Requisitions page, click Submit New Process.

  3. On the Import Requisitions dialog, select one or more import parameters before running the process. The following table lists the available parameters and their descriptions:

    Parameter

    Description

    Import Source (optional)

    Use to match against the records in the interface tables to retrieve the right set of records for processing.

    Import Batch ID (optional)

    Use to match against the records in the interface tables to retrieve the right set of records for processing.

    Maximum Batch Size (optional)

    Use to limit the number of requisition lines that are batch processed. If the parameter isn't specified, the default value of 2500 is used as the maximum batch size.

    Requisitioning BU (required)

    Use to ensure only the records with the specified requisitioning business unit (BU) are processed.

    Group By (required)

    Use to specify grouping of requisition lines. Choices include: Item, Buyer, Category, Location, Supplier, and None. None means to group all requisition lines together.

    This field is dependent on the Requisitioning BU field. When you select a requisitioning BU, the value from the business unit's Group Requisition Import By field is displayed as a default here.

    Next Requisition Number (optional)

    Use to specify the next requisition number when none is specified in the requisition header interface table.

    Initiate Approval after Requisition Import (required)

    Set the value to Yes if you want imported draft requisitions submitted for approval immediately after the process completes.

    Error Processing (required)

    Select from the possible values All or Partial.

    All: The default value for this parameter. A requisition is created only if all the lines from the interface header pass validation.

    Partial: A requisition is created with only the lines that pass validation, even though some lines fail validation.

  4. Click Submit.

How Imported Requisitions are Processed

During the import process, the requisition levels are validated in succession: header, line, and distribution. Any records that fail validation are reported and not included in further processing.

The requisition lines are then grouped into individual requisitions and given unique numbers. Due to the grouping of lines, one record in a requisition header interface table may correspond to multiple created requisitions.

Requisitions that are valid, grouped, and numbered are then inserted into the main requisition tables.

Then either the Generate Orders program or the Requisition Approval process is initiated, depending on the:

  • Status of the requisition

  • Value of the input parameter Initiate Approval after Requisition Import

  • Value of the requisitioning business function configuration option Create Order Immediately After Requisition Import

In the event of an interruption such as a server stoppage, the job restarts automatically from the point of failure without having to reprocess the entire set of records.

Related Topics