requisition import whitepaper v1 (1)

7/24/2019 Requisition Import Whitepaper v1 (1)

1/39


2/39

Requisition Import

Introduction ....................................................................................... 1

Importing Requisitions ....................................................................... 3

Grouping Requisitions ....................................................................... 4

Understanding the Interface Tables ................................................... 4

How to Read this Document .............................................................. 5

Requisition Header Interface Table ................................................... 5

Requisition Line Interface Table ...................................................... 12

Requisition Distribution Interface Table ........................................... 26

Resolving Failed Requisition Interface Rows ................................... 36


3/39

Requisition Import

Introduction

The Import Requisitions process can be used to import requisitions from other Oracle or non-Oracle

applications. For the import, requisition information must be loaded into three interface tables: header,

line, and distribution. Once the data is loaded in the interface tables, the import program can be

executed to validate and process the data. Any records that fail validation are reported and not included

in further processing.

Requisition lines loaded in the interface table are grouped into individual requisitions and given unique

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

tables.

Finally, the requisition approval process will be automatically initiated for requisitions imported as

incomplete if the parameter Initiate Approval After Requisition Import is set to Yes. And the Generate

Orders program will be initiated to create purchase orders for the approved requisitions, if the

requisitioning business function configuration option Create Order Immediately After Requisition

Import is set to Yes.

The following diagram illustrates the Import Requisition process:

1


4/39

Requisition Import

Figure 1. Import Requisi tion Process

2


5/39

Requisition Import

Importing Requisitions

The Import Requisitions process is used to import requisitions from Oracle applications or external

applications into Oracle Fusion Self Service Procurement. The task Import Requisitions is controlled

by the privilege Import Requisition. By default, the buyer inherits the Requisition Import Submission

Duty, which contains the Import Requisition privilege. Thus the Import Requisition task is available by

default from the Purchasing work area.As part of the External Data Integration Services for Oracle Cloud feature, predefined Excel templates

are available to load data to interface tables. The scheduled process Load Interface File for Import

Requisitions loads transaction data from the data file on the content management server to the

interface tables. For convenience, the ID columns are not available in the Excel templates and will be

derived by the application.

The table below displays details of the input parameters of the Import Requisitions process:

Table 1. Input Parameters

ATTRIBUTE REQUIRED DEFAULT DESCRIPTION AND VALIDAT ION

Import Source No Used to retrieve the correct set of records

for processing by matching the values

provided for the attribute

INTERFACE_SOURCE_CODE in the

interface table.

Import BatchID

No Used to retrieve the correct set of recordsfor processing by matching against therecords in the interface tables.

MaximumBatch Size

No 2,500 Number field used to limit the number ofrequisition lines that will be batchprocessed. If the parameter is notspecified, the default value of 2500 will beused as the maximum batch size.

RequisitioningBU

Yes Only the records with the specifiedrequisitioning BU are processed.

Group By Yes From the Requisitioning BU Configuration Choice list with the following choices: Item,Buyer, Category, Location, Supplier, andNone (where None means group allrequisition lines together). This field isdependent on the Requisitioning BU field:When a requisitioning BU is selected, theGroup Requisition Import By value from the

3


6/39

Requisition Import

ATTRIBUTE REQUIRED DEFAULT DESCRIPTION AND VALIDAT ION

Requisitioning BU Configuration will bedefaulted.

NextRequisitionNumber

No Used for numbering requisitions whenrequisition numbers are not specified in therequisition header interface table.

InitiateApprovalAfterRequisitionImport

Yes No Used to allow incomplete requisitions to besubmitted for approval immediately after theprocesses is complete.

Grouping Requisitions

Requisition lines associated with a requisition header interface record where a requisition number is

specified, are grouped first under the specified requisition number. The remaining requisition lines in

the lines interface table will be grouped into one or multiple requisitions based on the following logic:

1.All requisition lines with the same group code are grouped together under one requisition header.

2.Grouped requisition lines are then grouped again based on the Group-By input parameter under one

requisition header. The Group By parameter can have one of the following values: Buyer, Category,

Item, Supplier, Location or None. The value None is used when no further grouping is needed and

all requisition lines are grouped together under one requisition header.

Note: The Maximum Batch Size (input parameter of the ESS request) is used to enhance performance

during the grouping of the lines, but it will not affect the grouping logic.

Understanding the Interface Tables

Table 2. Glossary

TERM DEFINITION

BPA Purchasing document known as blanket purchase agreement. Blanket Purchase

Agreement is an agreement between a buyer and a seller that identifies terms for

subsequent orders including goods, services, and pricing.

CPA Purchasing document known as contract purchase agreement. Contract

Purchase Agreement is an agreement between buyer and seller that identifies

general terms for subsequent orders without identifying goods, services and

pricing.

4


7/39

Requisition Import

How to Read this Document

This section contains details of the Requisition Header Interface Table, Requisition LineInterface Table, and Requisition Distribution Interface Table.

Attribute column: Indicates the name of the attribute as it appears in the interface table

definition.

Oracle Cloud Spreadsheet Column: Indicates the name of the attribute as it appears in the

Oracle Cloud spreadsheet.

Required Column: Indicates whether or not a value for the attribute is required.

Default Column: Indicates whether the application can default any value to the attribute.

Certain required attributes can also have a default value. In those cases, when the attribute is null in the

interface table, the application will attempt to obtain a default value. If the application cannotdetermine a default value for a required attribute that has a null value in the interface table, an error will

be raised.

The attributes indicated as N/A (Not Applicable) in the required column, are attributes that are

populated by the application and should not be provided by the integrating application.

1. Description and Validation columns: Provides a brief description of the attribute and any

additional validation applied to the loaded data.

2. Data Type column: Indicates whether the attribute is number, text, date, or timestamp.

3. Size column: Provides the size in bytes for each attribute.

Requisition Header Interface Table

Table 3. Requisi tion Header Interface Table

ATTRIBUTE ORACLE CLOUD

SPREADSHEET

COLUMN

REQUIRED DEFAULT DESCRIPTION AND

VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

REQ_HEADER_INTERFACE_ID

N/A Yes Requisition headerinterface unique identifier.

Number 18

PROCESS_FLAG N/A N/A Application-updated flag

that tracks the processingstatus of the record in theinterface table.

Text 30

INTERFACE_SOURCE_CODE

Interface SourceCode

Yes The source from which therequisition lines weresubmitted for processing. Ifa value is provided duringjob submission, it is used tomatch the requisition lines

Text 25

5


8/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

that are selected forprocessing.

INTERFACE_SOURCE_LINE_ID

Interface SourceLine ID

No Source transactionreference identification.

Number 18

DOCUMENT_STATUS Status Code Yes Status code of therequisition. The possiblelookup code values areINCOMPLETE, andAPPROVED.

When loading incompleterequisitions, you can setthe input parameter InitiateApproval After RequisitionImport to Y, so therequisition is submitted forapproval once it is fully

loaded in the requisitiontables.

Text 25

BATCH_ID Batch ID No An identifier if providedduring job submission thatis used to match therequisition lines that areselected for processing.

Number 18

APPROVER_ID N/A Yes (Whendocumentstatus =APPROVEDand approvere-mail isnull.)

Unique identification of theapprover of the requisition.The person ID must beprovided within OracleFusion Application.

Number 18

APPROVER_EMAIL Approver Yes (Whendocumentstatus =APPROVEDand approverID is null.)

E-mail of the requisitionapprover.

The approver e-mail isused to derive theApprover ID.

Text 240

JUSTIFICATION Justification No Reason for the requisition. Text 1000

PREPARER_ID N/A Yes (Ifpreparer e-mail is null.)

Unique identifier of theperson who created therequisition.

Number 18

PREPARER_EMAIL Entered By Yes (Ifpreparer ID isnull.)

E-mail of the person whocreated the requisition.

The preparer e-mail is usedto derive the preparer ID.

Text 240

REQUISITION_NUMBER

Requisition Yes Nextrequisitionnumberinputparameterorfrom theConfiguredRequisitio

Number used to identify therequisition.

The requisition numbermust be unique within arequisitioning BU.

Text 64

6


9/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

ning BU

DESCRIPTION Description Yes Description of therequisition.

Text 240

REQ_BU_ID N/A Yes (IfrequisitionBU name isnull.)

Unique identifier for thebusiness unit of therequisition.

Number 18

REQ_BU_NAME Requisitioning BU Yes (IfrequisitionBU ID isnull.)

Name of the business unitof the requisition.

The requisitioning BUname is used to derive therequisitioning BU ID.

Text 240

EMERGENCY_PO_NUMBER

EmergencyPurchase Order

No Purchase order numberreserved in advance for anemergency requisition.

Emergency PO numberprovided must not alreadyexist in the sold-to BU fromsupplier site assignment.All lines of the requisitionwith an emergencypurchase order numbermust have the samesupplier and supplier site.

Text 20

PRC_BU_ID N/A No Unique identifier for thebusiness unit that managesand owns the purchasingdocument.

Number 18

PRC_BU_NAME Procurement BU No Name of the business unitthat manages and ownsthe purchasing document.

The Procurement BU nameis used to derive theProcurement BU ID.

Text 240

CREATED_BY N/A N/A Who column indicating theuser who created the row.

Text 64

CREATION_DATE N/A N/A Who column indicating thedate and time of thecreation of the row.

Timestamp

6

LAST_UPDATED_BY N/A N/A Who column indicating theuser who last updated therow.

Text 64

LAST_UPDATE_DATE N/A N/A Who column indicating thedate and time of the lastupdate of the row.

Timestamp

6

LAST_UPDATE_LOGIN N/A N/A Who column indicating thesession login associated tothe user who last updatedthe row.

Text 32

REQUEST_ID N/A N/A Scheduled Process requestID indicating the job thatcreated or last updated therow.

Number 18

7


10/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

JOB_DEFINITION_NAME N/A N/A Scheduled Process jobname indicating the job thatcreated or last updated therow.

Text 100

JOB_DEFINITION_PACKAGE

N/A N/A Scheduled Processpackage name indicatingpackage that created orlast updated the row.

Text 900

OBJECT_VERSION_NUMBER

N/A N/A Used to implementOptimistic Locking. Thenumber is incrementedevery time the row isupdated and compared atthe start and end of atransaction to detectwhether another sessionhas updated the row since

it was queried.

Number 9

ATTRIBUTE_CATEGORY

N/A No Descriptive Flexfield:structure definition of theuser descriptive flexfield.

Text 30

ATTRIBUTE1 ATTRIBUTE1 No Descriptive Flexfield:Segment of the userdescriptive flexfield.

Text 150


Text 150


Text 150

ATTRIBUTE4 ATTRIBUTE4 No Descriptive Flexfield:Segment of the user

descriptive flexfield.

Text 150


Text 150


Text 150


Text 150


Text 150

ATTRIBUTE9 ATTRIBUTE9 No Descriptive Flexfield:

Segment of the userdescriptive flexfield.

Text 150


Text 150


Text 150

8


11/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)


Text 150


Text 150


Text 150


Text 150


Text 150


Text 150


Text 150


Text 150


Text 150

ATTRIBUTE_DATE1 ATTRIBUTE_DATE1

No Descriptive Flexfield:Segment of the userdescriptive flexfield.

Date



Date



Date



Date



Date


No Descriptive Flexfield:Segment of the user


Date



Date



Date

ATTRIBUTE_DATE9 ATTRIBUTE_DA No Descriptive Flexfield: Date

9


12/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

TE9 Segment of the userdescriptive flexfield.



Date

ATTRIBUTE_TIMESTAMP1



Timestamp

6




Timestamp

6




Timestamp

6




Timestamp

6




Timestamp

6




Timestamp

6




Timestamp

6




Timestamp

6




Timestamp

6




Timestamp

6

ATTRIBUTE_NUMBER1 ATTRIBUTE_NUMBER1


Number



Number



Number



Number



Number



Number

10


13/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)




Number



Number



Number

ATTRIBUTE_NUMBER10

ATTRIBUTE_NUMBER10


Number

DEFAULT_TAXATION_COUNTRY

Taxation Country No DefaultfromOracleFusionTax setup

Country where thetransaction is deemed tohave taken place fortaxation purposes.

Text 2

DEFAULT_TAXATION_TERRITORY

Taxation Territory No DefaultfromOracleFusionTax setup

Territory where thetransaction is deemed tohave taken place fortaxation purposes.

Text 80

DOCUMENT_SUB_TYPE

Document SubType

No DefaultfromOracleFusionTax setup

Document sub type code. Text 240

DOCUMENT_SUB_TYPE_NAME

Document SubType Name

No DefaultfromOracle

FusionTax setup

Document sub type name. Text 240

LOAD_REQUEST_ID N/A N/A Application-generatednumber that uniquelyidentifies the request tocreate requisitions throughOracle Cloud.

Number 18

INTERFACE_HEADER_KEY

Interface HeaderKey

Yes, forOracle Cloud

Oracle Cloud alternateheader key code forintegrating applications tobe able to identify therequisition header dataloaded in the interfacetable.

For Oracle Cloud, theprovided header key must

be unique for a loadrequest.

Text 50

11


14/39

Requisition Import

Requisition Line Interface Table

Table 4. Requisit ion Line Interface Table


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

REQ_LINE_INTERFACE_ID

Yes Requisition line interfaceunique identifier.

Number 18

REQ_HEADER_INTERFACE_ID

No Requisition headerinterface unique identifier.

Number 18

PROCESS_FLAG N/A N/A Application-updated flagthat tracks the processingstatus of the record in theinterface table.

Text 30

GROUP_CODE Group-By Code No Value by which therequisition lines aregrouped when they are

being processed by theimport program.Requisition lines that aregrouped together will beput on the same requisitionheader.

Text 30

PRC_BU_ID N/A No From thesuppliersite orfrom thefirst BUassignedto thebuyer.

Unique identifier of thebusiness unit that managesand owns the purchasingdocument.

The Procurement BU mustbe a BU that has aprocurement serviceprovider relationship withthe Requisitioning BUspecified on the requisitionheader.

Number 18

PRC_BU_NAME Procurement BU No From thesuppliersite orfrom thefirst BUassignedto thebuyer.

Business unit thatmanages and owns thepurchasing document.

The procurement BU nameis used to derive theprocurement BU ID.

Text 240

ITEM_ID N/A No Unique number for an item.

ITEM_ID is not applicablefor fixed price service lines.The item must be astandard purchasable itemin the item master.

Number 18

ITEM_NUMBER Item No Unique number for an item.

The item number is used toderive the item ID.

Text 300

ITEM_DESCRIPTION Item Description Yes Defaultsfrom BPAor fromitemmasteritem

Description of therequested item.

Text 240

12


15/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

ITEM_REVISION Revision No A version of an item.

Item revision must exist forthe item with the item IDprovided.

Text 10

CATEGORY_ID N/A Yes (Ifcategoryname is null.)

From itemmasteritem orfrom aBPA.

Unique identifier of thecategory of the item.

The category must be apurchasing category.For item master items, thecategory provided mustexist and match thecategory of the master itemin the deliver-toorganization.

For item master items not

in BPA, UOM and categorymust be null to obtain themaster item default values.

Number 18

CATEGORY_NAME Category Name Yes (Ifcategory IDis null.)

From itemmasteritem orfrom aBPA.

Indicates the name thatuniquely defines an itemcategory.

The category name is usedto derive the category ID.

Text 250

UOM_CODE UOM Yes (Forgoods linetype.)

Frommasteritem orfrom aBPA.

Code in which the quantityof an item is expressed.

For master items, the UOMprovided must exist and beassociated with the item inthe deliver-to organization.

For master items not inBPA, the UOM andcategory must be null toobtain the master itemdefault values.

Text 3

QUANTITY Quantity Yes Quantity of the item to beadded to the requisition.

Number

NEED_BY_DATE Need-by Date Yes Date by which therequested item is needed.

Date

DESTINATION_TYPE_CODE

Destination TypeCode

Yes EXPENSEfornonmasteritems.

Type of destination towhich the requested itemshould be delivered. Thepossible lookup codevalues are INVENTORY,and EXPENSE.

For inventory destinationtype, the following must betrue:- Inventory must beimplemented.- Item must be a masteritem, stockable in thedeliver-to organization.- Line type must be a

Text 25

13


16/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

goods based line type.- Deliver-to Location mustnot be a one-time location.- Project information mustnot be provided in thedistribution.

DESTINATION_ORGANIZATION_ID

N/A Yes (Ifdestinationorganizationcode is null.)

From thedeliver-tolocation,or fromtheRequisitioning BUConfiguration.

Unique identification of theorganization to which therequested item will bedelivered.

When not provided, thedeliver-to organization isbased on the deliver-tolocation if it is not a globallocation. Otherwise, it isdefaulted fromRequisitioning BU

Configuration.

Number 18

DESTINATION_ORGANIZATION_CODE

Deliver-toOrganization

Yes (IfdestinationorganizationID is null.)

From thedeliver-tolocation,or fromtheRequisitioning BUConfiguration.

Code of the organization towhich the requested itemwill be delivered.

The destinationorganization code is usedto derive the destinationorganization ID.

Text 3

DESTINATION_SUBINVENTORY

Subinventory No Subinventory to which therequested item should bedelivered.

Applies only for Inventorydestination type. Thesubinventory must belongto the deliver-toorganization, and must notbe restricted for the item.

Text 10

DELIVER_TO_LOCATION_ID

N/A Yes (Ifdeliver-tolocation codeis null.)

Thelocation oftherequester.

Unique identification of thefinal location where thegoods previously receivedfrom the supplier will bedelivered.

The deliver-to locationmust be active and must bein the Requisitioning BU'sset of locations.If the deliver-toorganization is providedand the deliver-to locationis not global, then thedeliver-to location must beassociated to the deliver-toorganization.

Number 18

DELIVER_TO_LOCATION_CODE

Deliver-toLocation

Yes (Ifdeliver-tolocation ID isnull.)

Thelocation oftherequester.

Code of the final locationwhere the goods previouslyreceived from the supplierwill be delivered.

The deliver-to locationcode is used to derive the

Text 60

14


17/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

deliver-to location ID.

REQUESTER_ID N/A Yes From thepreparer.

Unique identification of therequester.

Number 18

REQUESTER_EMAIL Requester Yes (Ifrequester IDis null.)

From thepreparer.

E-mail of the requester.

The requester e-mail isused to derive therequester ID.

Text 240

SUGGESTED_BUYER_ID

N/A No Based ontherequisitionprocurement BU.

Unique identification of theperson responsible forplacing item resupplyorders with suppliers andnegotiating suppliercontracts.

The suggested buyer mustbe a purchasing agentdefined for the requisitionprocurement BU if there isa procurement BU context,or for one of theprocurement serviceproviders for therequisitioning BU.

Number 18

SUGGESTED_BUYER_EMAIL

Suggested Buyer No Based ontherequisitionprocurement BU.

E-mail of the personresponsible for placing itemresupply orders withsuppliers and negotiatingsupplier contracts.

The suggested buyer e-mail is used to derive thesuggested buyer ID.

Text 240

NEW_SUPPLIER_FLAG New Supplier No N Indicates whether or notthe supplier is new.

Possible values are Y, orN.When the new supplier isY, the application will notattempt to autosource anagreement for therequisition line.

Text 1

SUGGESTED_VENDOR_NAME

Supplier No From theBPA.

Organization or individualthat provides goods orservices to the buyingorganization for payment.

When the new supplier is Nor null, the suggestedvendor name is used toderive the vendor ID.

Text 360

VENDOR_ID N/A No From theBPA.

Unique identification of theorganization or individualthat provides goods orservices to the buyingorganization for payment.

Vendor ID should not beprovided when the newsupplier is Y.

Number 18

15


18/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

SUGGESTED_VENDOR_SITE Supplier Site No From theBPA. Entity that models how thebuying organizationconducts business with thesupplier.

When the new supplier is Nor null, the suggestedvendor site name is used toderive the vendor site ID.

Text 240

VENDOR_SITE_ID N/A No From theBPA.

Unique identification of theentity that models how thebuying organizationconducts business with thesupplier.

Number 18

SUGGESTED_VENDOR_CONTACT

Supplier Contact No From theBPA.

Employee of the supplieridentified on purchasingdocuments and represents

the supplier incommunications with thebuying organization.

When the new supplier is Nor null, the suggestedvendor contact name isused to derive the vendorcontact ID.

Text 80

VENDOR_CONTACT_ID

N/A No From theBPA.

Unique identification of theemployee of the supplieridentified on purchasingdocuments and representsthe supplier incommunications with thebuying organization.

Number 18

SUGGESTED_VENDOR_CONTACT_PHONE

Phone No From thesuppliercontact ifnot a newsupplier.

Identifies the full phonenumber for a suppliercontact.

Text 30

SUGGESTED_VENDOR_CONTACT_FAX

Fax No From thesuppliercontact ifnot a newsupplier.

The formatted fax numberfor a supplier address.

Text 30

SUGGESTED_VENDOR_CONTACT_EMAIL

E-Mail No From thesuppliercontact ifnot a newsupplier.

Identifies the e-mail for asupplier contact.

Text 1000

SUGGESTED_SUPPLIER_ITEM_NUM

Supplier Item No The name or numbersupplier assigns to an item.

CURRENCY_CODE Currency Yes From theBPA orfrom thefunctionalcurrencyof theRequisitioning BU.

Three-letter ISO codeassociated with a currency.

Text 15

CURRENCY_UNIT_PRI Price Yes From the Unit price of the requested Number

16


19/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

CE BPA. item in the currencyprovided.

The currency unit price isnot applicable for fixedprice service lines.When a BPA exists, theprice is defaulted from theBPA. If the BPA allowsprice override, then theprovided price will besaved in the requisitionline; otherwise, the BPAprice will override theprovided price.The price must not exceedthe maximum price allowedfor the blanket agreementline.

RATE Conversion Rate Yes (Whenrate type isUser.)

Based onthe ratetype andfor a givenrate date.

Ratio at which the principalunit of one currency can beconverted into anothercurrency.

Number

RATE_DATE Conversion Date Yes (Whenrate type isnot User.)

Currentdate.

Date as of which aconversion rate is used toconvert an amount intoanother currency.

Date

RATE_TYPE Conversion RateType

Yes (Whentherequisitiontransactioncurrency isdifferent fromthe functionalcurrency.)

From theConversion RateTypedefined onthe currentRequisitioning BU'sFinancialoptions.

Source of a currencyconversion rate, such asuser defined, spot, orcorporate. For user-definedrate, provide USER in therate type.

Text 30

SECONDARY_UOM_CODE

Secondary UOM No From themasteritem.

Secondary unit of measureof the requested item.

When provided, it mustmatch the secondary UOMof the item.

Text 3

SECONDARY_QUANTITY

SecondaryQuantity

Yes(If item issecondaryitem trackingenabled.)

Quantity in the secondaryunit of measure of therequested item.

The secondary quantitymust be within thedeviation factor specifiedfor the provided item.

Number

CURRENCY_AMOUNT Amount Yes (Forfixed priceservicelines.)

From theBPA.

Amount of the item to beadded to the requisition inthe currency provided.

Only applies for fixed priceservice requisition lines.When there is a BPA, theamount is defaulted fromthe BPA. If the BPA allowsprice override, then the

Number

17


20/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

provided amount will besaved in the requisitionline; otherwise, the BPAamount will override theprovided amount.The amount cannot begreater than the price limiton the source document forthe fixed price line.

NEGOTIATED_BY_PREPARER_FLAG

Negotiated No Indicates if the requesteditem is negotiated with thesupplier.

Must be Y to automate thepurchase order creation foritems with CPA as a sourcedocument.

Text 1

NEGOTIATION_REQUIRED_FLAG

NegotiationRequired

No Indicates if negotiation isrequired for the requesteditem.

Possible values are Y or N.

Text 1

AUTOSOURCE_FLAG Autosource Flag No Y Allows purchasingdocuments to derive thesupply source frompurchase agreements. Thesupplier and the priceinformation are derivedfrom the sourceagreement.

Possible values are Y andN.When Y, the application willautosource an agreement,BPA, or CPA, by amatching some or all theinformation below,depending on what isavailable:

Item and its revision

Currency

Category

Deliver-toOrganization

Supplier

Supplier SiteLine Type

Purchase Basis(Goods or Services)UOM Code

Text 1

SOURCE_DOC_HEADER_ID

N/A No Autosourced

The unique identifier of anagreement in aProcurement BU.

The source document,BPA, or CPA, must beopen in the ProcurementBU, valid for the need-bydate (or sysdate), and

Number 18

18


21/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

assigned to theRequisitioning BU of therequisition.When the provided sourcedocument is invalid, or itsline is invalid (e.g. expired),and the autosource flag isY, the application willattempt to source therequisition line to anothervalid document source.

When values are providedfor the following attributes,and they do not match thevalues in the sourcedocument, then theprovided values will bereplaced with the source

document values:

- Price or Amount - will bereplaced with the BPAvalues only if the BPA doesnot allow price override:- Item Revision- Item Description- Supplier- Supplier Site- Supplier Contact- Currency Code- Category- Negotiated By PreparerFlag

SOURCE_DOC_HEADER_NUMBER

Agreement No Autosourced

The unique number of anagreement in aProcurement BU.

The source documentheader number is used toderive the sourcedocument header ID.

Text 20

SOURCE_DOC_LINE_ID

N/A No Autosourced

Unique identifier of theagreement line recordnumber.

There must be anagreement header for thisagreement line ID, eitherderived by the applicationor provided in the interfacetable.

Number 18

SOURCE_DOC_LINE_NUMBER

Agreement Line No Autosourced

Agreement line recordnumber.

The source document linenumber is used to derivethe source document lineID.

Number

URGENT_FLAG Urgent No Indicates whether or notthe requisition is urgent.

Possible values are Y andN.

Text 1

19


22/39


23/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

user who last updated therow.


Text 64


Text 32

REQUEST_ID N/A N/A Enterprise ServiceScheduler indicating therequest ID of the job thatcreated or last updated therow.

Number 18

JOB_DEFINITION_NAME

N/A N/A Enterprise ServiceScheduler indicating thename of the job thatcreated or last updated therow.

Text 100


N/A N/A Enterprise ServiceScheduler indicating thepackage name of the jobthat created or last updatedthe row.

Text 900


N/A N/A Used to implementOptimistic Locking. Thenumber is incrementedevery time that the row isupdated and is comparedat the start and end of atransaction to detectwhether another sessionhas updated the row since

it was queried.

Number 9

ATTRIBUTE_CATEGORY

N/A No Descriptive Flexfield:Structure definition of theuser descriptive flexfield.

Text 30


Text 150


Text 150


Text 150


Segment of the userdescriptive flexfield.

Text 150


Text 150


Text 150

21


24/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)


Text 150


Text 150


Text 150


Text 150


Text 150


Text 150


Text 150


Text 150


Text 150


Text 150


Text 150


Text 150


Text 150


Text 150




Text 150



Date



Date

ATTRIBUTE_DATE4 ATTRIBUTE_DA No Descriptive Flexfield: Date

22


25/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

TE4 Segment of the userdescriptive flexfield.



Date



Date



Date



Date



Date



Date




Timestamp

6




Timestamp

6




Timestamp

6




Timestamp

6




Timestamp

6




Timestamp

6




Timestamp

6




Timestamp

6




Timestamp

6




Timestamp

6



Number

23


26/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)




Number



Number



Number



Number



Number



Number



Number



Number

ATTRIBUTE_NUMBER10

ATTRIBUTE_NUMBER10


Number

TRX_BUSINESS_CATE

GORY

Transaction

BusinessCategory

No From

OracleFusionTax setup.

Code of a business

classification used byOracle Fusion Tax toidentify and categorize anexternal transaction into aFusion Tax transaction.

Text 240

TRX_BUSINESS_CATEGORY_NAME

TransactionBusinessCategory Name

No FromOracleFusionTax setup.

Name of a businessclassification used byOracle Fusion Tax toidentify and categorize anexternal transaction into aFusion Tax transaction.

Text 240

PRODUCT_TYPE Product Type No FromOracleFusionTax setup.

Code of the nature of theproduct involved in ataxable transaction. Forexample, goods orservices.

Text 240

PRODUCT_TYPE_NAME

Product TypeName

No FromOracleFusionTax setup

Name of the nature of theproduct involved in ataxable transaction. Forexample, goods orservices.

Text 80

PRODUCT_FISC_CLASSIFICATION_ID

N/A No FromOracleFusionTax setup.

Unique identification of theclassification used by a taxauthority to categorize aproduct for a tax.

Number 18

24


27/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

PRODUCT_FISC_CLASSIFICATION Product FiscalClassification No FromOracleFusionTax setup.

Code of the classificationused by a tax authority tocategorize a product for atax.

Text 240

PRODUCT_FISC_CLASS_NAME

Product FiscalClassificationName


Name of the classificationused by a tax authority tocategorize a product for atax.

Text 250

PRODUCT_CATEGORY

Product Category No FromOracleFusionTax setup.

Code of the type of productfiscal classification used toclassify products.

Text 240

PRODUCT_CATEGORY_NAME

Product CategoryName


Name of the type ofproduct fiscal classificationused to classify products.

Text 1996

LINE_INTENDED_USE_ID

N/A No FromOracleFusionTax setup.

Tax classification uniqueidentifier based on thepurpose for which aproduct is used.

Number 18

LINE_INTENDED_USE Intended Use No FromOracleFusionTax setup.

Tax classification codebased on the purpose forwhich a product is used.

Text 240

LINE_INTENDED_USE_NAME

Intended UseName


Tax classification namebased on the purpose forwhich a product is used.

Text 250

USER_DEFINED_FISC_CLASS

User-DefinedFiscalClassification


A classification code forany tax requirement thatyou cannot define using theexisting fiscal classification

types.

Text 240

USER_DEFINED_FISC_CLASS_NAME

User-DefinedFiscalClassificationName


Classification name for anytax requirement that youcannot define using theexisting fiscal classificationtypes.

Text 240

TAX_CLASSIFICATION_CODE

Tax ClassificationCode


Code for the taxclassification, a grouping oftaxes for reporting andprocessing purposes.

Text 50

TAX_CLASSIFICATION_NAME

Tax ClassificationName


Name for the taxclassification, a grouping oftaxes for reporting andprocessing purposes.

Text 80

ASSESSABLE_VALUE Assessable Value No From

OracleFusionTax setup.

Deemed price at which a

product is valued by a taxauthority for tax calculationpurposes.

Number

LOAD_REQUEST_ID N/A N/A Application-generatednumber uniquely identifyingthe request to createrequisitions via OracleCloud.

Number 18

25


28/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

INTERFACE_LINE_KEY Interface LineKey Yes, forOracleCloud.

Oracle Cloud alternate linekey code for integratingapplications identifying therequisition line data loadedin the interface table.

The provided line key mustbe unique for a loadrequest.

Text 50

INTERFACE_HEADER_KEY

Interface HeaderKey

Yes, forOracleCloud.

Oracle Cloud alternateheader key code forintegrating applicationsidentifying the requisitionheader data loaded in theinterface table.

The provided header key inthe interface lines table

must exist in the interfaceheaders table.

Text 50

Requisition Distribution Interface Table

Table 5. Requisi tion Dist ribu tion Interface Table


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

REQ_DIST_INTERFACE_ID

N/A Yes Requisition distributioninterface unique identifier

Number 18

REQ_LINE_INTERFACE_ID

N/A Yes Requisition line interfaceunique identifier.

Number 18

PROCESS_FLAG N/A N/A Application-updated flagthat tracks the processingstatus of the record in theinterface table.

Text 30

CHARGE_ACCOUNT_ID

N/A Yes FromOracleTransaction AccountBuilder.

Unique identifier for theGeneral Ledger chargeaccount.

The charge accountsegments are used toderive the charge account

ID.

Number 18

CHARGE_ACCOUNT_SEGMENT1

N/A No General Ledger chargeaccount key flexfieldsegment.

When the charge accountsegment is provided and isvalid, it will be used toretrieve the charge account

Text 25

26


29/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

code combination ID. If thecode combination IDcannot be derived, and theaccount key flexfieldstructure instance has theDynamic combinationcreation allowed set, thenthe code combination IDwill be generated for thesegment provided.



Text 25



Text 25


N/A

No

General Ledger chargeaccount key flexfieldsegment.

Text

25



Text 25



Text 25



Text 25



Text 25



Text 25



Text 25



Text 25



Text 25



Text 25



Text 25



Text 25

CHARGE_ACCOUNT_S N/A No General Ledger charge Text 25

27


30/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

EGMENT16 account key flexfieldsegment.



Text 25



Text 25



Text 25



Text 25



Text 25



Text 25



Text 25



Text 25



Text 25



Text 25



Text 25



Text 25



Text 25



Text 25

INTERFACE_SOURCE_LINE_ID

N/A No Application-updatedidentifier that referencesthe source transaction.

Number 18

PERCENT Percentage Yes Calculatedifdistribution quantityisprovided.

Percentage of thedistribution. A requesteditem can be charged to oneor more accounts. Thecharges are distributed tothe respective accounts

Number

28


31/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

specified at the distributionlevel.

The sum of percentallocations should add upto 100 percent.

DISTRIBUTION_NUMBER

Distribution Yes Number identifier of thedistribution. A requesteditem can be charged to oneor more accounts. Thecharges are distributed tothe respective accountsspecified at the distributionlevel.

Number

DISTRIBUTION_QUANTITY

Quantity Yes Yes, it iscalculatedbased on

thepercentageprovided.

Quantity of the distribution.A requested item can becharged to one or more

accounts. The charges aredistributed to the respectiveaccounts specified at thedistribution level.

Number

DISTRIBUTION_CURRENCY_AMOUNT

Amount No Amount of the distributionin the currency of thesupplier.

Number

PJC_CONTEXT_CATEGORY

N/A N/A The context of the projectcost collection flexfield.

When project information isprovided, the applicationwill populate this attributewith POR_Requisition.

Text 40

PJC_PROJECT_ID N/A No Identifier of the project to

which the transactionbelongs.

Number 18

PJC_PROJECT_NAME Project Name No Name of the project towhich the transactionbelongs.

The project name is usedto derive the project ID.

Text 240

PJC_TASK_ID N/A No Identifier of the task towhich the transactionbelongs.

Number 18

PJC_TASK_NAME Task Number No Name of the task to whichthe transaction belongs.

The task name is used toderive the task ID.

Text 240

PJC_EXPENDITURE_TYPE_ID

N/A No Identifier of the expendituretype to which thetransaction belongs.

Number 18

PJC_EXPENDITURE_TYPE_NAME

Expenditure Type No Name of the expendituretype to which thetransaction belongs.

The expenditure type name

Text 240

29


32/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

is used to derive theexpenditure type ID.

PJC_EXPENDITURE_ITEM_DATE

Expenditure ItemDate

No Date on which thetransaction was incurred.

Date

PJC_ORGANIZATION_ID

N/A No Identifier of theorganization that incurredthe cost of the transaction.

Number 18

PJC_ORGANIZATION_NAME

ExpenditureOrganization

No Name of the organizationthat incurred the cost of thetransaction.

The organization name isused to derive theorganization ID.

Text 240

PJC_BILLABLE_FLAG Billable No Indicates the billable statusof the transaction.

Valid values are Y or N.

Text 1

PJC_CAPITALIZABLE_FLAG

Capitalizable No Indicates the capitalizablestatus of the transaction.

Valid values are Y or N.

Text 1

PJC_WORK_TYPE_ID N/A No Identifier of the work typeto which the transactionbelongs.

Number 18

PJC_CONTRACT_ID N/A No Identifier of the contract towhich the transactionbelongs.

Number 18

PJC_CONTRACT_LINE_ID

N/A No Identifier of the contractline to which thetransaction belongs.

Number 18

PJC_FUNDING_ALLOCATION_ID

N/A No Identifier of the fundingallocation to which thetransaction belongs.

Number 18

PJC_RESERVED_ATTRIBUTE1


No Reserved for future use inthe project cost collectionflexfield.

Text 150




Text 150




Text 150



No Reserved for future use inthe project cost collection

flexfield.

Text 150




Text 150




Text 150

PJC_RESERVED_ATT PJC_RESERVED No Reserved for future use in Text 150

30


33/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

RIBUTE7 _ATTRIBUTE7 the project cost collectionflexfield.




Text 150




Text 150




Text 150

PJC_USER_DEF_ATTRIBUTE1


No User-defined segment ofthe project cost collectionflexfield.

Text 150




Text 150




Text 150




Text 150




Text 150




Text 150




Text 150




Text 150




Text 150




Text 150

ATTRIBUTE_CATEGORY

N/A No Descriptive Flexfield:Structure definition of theuser descriptive flexfield.

Text 30

ATTRIBUTE1 ATTRIBUTE1 No Descriptive Flexfield:Structure definition of theuser descriptive flexfield.

Text 150


Text 150

ATTRIBUTE3 ATTRIBUTE3 No Descriptive Flexfield:Structure definition of the

Text 150

31


34/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

user descriptive flexfield.


Text 150


Text 150


Text 150


Text 150


Text 150


Text 150


Text 150


Text 150


Text 150


Structure definition of theuser descriptive flexfield.

Text 150


Text 150


Text 150


Text 150


Text 150


Text 150


Text 150


Text 150

32


35/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

ATTRIBUTE_DATE1 ATTRIBUTE_DATE1 No Descriptive Flexfield:Structure definition of theuser descriptive flexfield.

Date


No Descriptive Flexfield:Structure definition of theuser descriptive flexfield.

Date



Date



Date



Date



Date



Date



Date



Date



Date




Timestamp

6




Timestamp

6




Timestamp

6




Timestamp

6



No Descriptive Flexfield:Structure definition of the

user descriptive flexfield.

Timestamp

6




Timestamp

6




Timestamp

6

ATTRIBUTE_TIMESTA ATTRIBUTE_TIM No Descriptive Flexfield: Timesta 6

33


36/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

MP8 ESTAMP8 Structure definition of theuser descriptive flexfield. mp




Timestamp

6




Timestamp

6



Number



Number



Number



Number



Number



Number



Number



Number



Number

ATTRIBUTE_NUMBER10

ATTRIBUTE_NUMBER10


Number

LOAD_REQUEST_ID N/A N/A Application-generatednumber uniquely identifyingthe request to createrequisitions via OracleCloud.

Number 18

INTERFACE_DISTRIBU

TION_KEY

Interface

Distribution Key

Yes, for

OracleCloud.

Oracle Cloud alternate

distribution key code forintegrating applicationsidentifying the requisitiondistribution data loaded inthe interface table.

The provided distributionkey must be unique for aload request.

Text 50

34


37/39

Requisition Import


SPREADSHEET

COLUMN


VALIDATION

DATA

TYPE

SIZE

(IN

BYTES)

INTERFACE_LINE_KEY Interface LineKey Yes, forOracle Cloudinterface.

Oracle Cloud alternate linekey code for integratingapplications identifying therequisition line data loadedin the interface table.

The provided line key in theinterface distributions tablemust exist in the interfacelines table.

Text 50

CREATED_BY N/A N/A Who column indicating theuser who created the row.

Text 64

CREATION_DATE N/A N/A Who column indicating thedate and time of thecreation of the row.

Timestamp

6

LAST_UPDATED_BY N/A N/A Who column indicating theuser who last updated therow.

Text 64


Timestamp

6


Text 32

REQUEST_ID N/A N/A Enterprise ServiceScheduler indicating therequest ID of the job thatcreated or last updated therow.

Number 18

JOB_DEFINITION_NAME

N/A N/A Enterprise ServiceScheduler indicating the

name of the job thatcreated or last updated therow.

Text 100


N/A N/A Enterprise ServiceScheduler indicating thepackage name of the jobthat created or last updatedthe row.

Text 900


N/A N/A Used to implementOptimistic Locking. Thisnumber is incrementedevery time that the row isupdated and compared atthe start and end of atransaction to detectwhether another sessionhas updated the row since

it was queried.

Number 9

35


38/39

Requisition Import

Resolving Failed Requisition Interface Rows

The Import Requisitions program may display specific error messages during interface processing. You

can report on all rows that failed validation through the Requisition Import Exceptions report. For

every transaction in the interface table that fails validation, the Requisition Import Exceptions report

lists all the columns that failed validation along with the reason for the failure.

You can also identify failed transactions in the requisitions interface tables by selecting rows with a

PROCESS_FLAG of ERROR. For any previously processed set of rows identified by

INTERFACE_SOURCE_CODE and BATCH_ID, only rows that failed validation remain in the

interface table, as all the successfully imported rows are deleted.

For each row in the requisition interface tables that fails validation, the Import Requisitions program

creates one or more rows with error information in the POR_ESS_REPORT_TEXT table.

36


39/39

Requisition Import

Oracle Fusion Self Service Procurement

11.1.7.0.0

June 2013

Author: Mara Prieto

Oracle Corporation

World Headquarters

500 Oracle Parkway

Redwood Shores, CA 94065

U.S.A.

Worldwide Inquiries:

Phone: +1.650.506.7000

Fax: +1.650.506.7200

oracle.com

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

This document is provided for information purposes only, and the contents hereof are subject to change without notice. This

document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in

law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any

liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This

document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our

prior written permission.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and

are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are

trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0113

requisition import whitepaper v1 (1)

Documents