requisition interface

30
As long as the Multiple Distributions field in the Requisition Import program is No (or blank), Requisition Import looks for distribu information in the PO_REQUISITIONS_INTERFACE_ALL table. should use the PO_REQ_DIST_INTERFACE_ALL table to create multiple distributions only for requisitions created in non-Oracle sys multiple distributions. If you specify a value in the REQ_ NUMBER_SEGMENT1 column of the PO_REQUISITIONS_INTERFACE_ALL table, all lines with the same value for this column are grouped toget requisition header. If you provide a value in the GROUP_CODE column, a with the same value in this column are grouped together under a requis If you provide a value in the REQ_NUMBER_SEGMENT1 column of the PO_ REQUISITIONS_INTERFACE_ALL table, this value becomes the requisition number. If not, the Requisition Import program uses either the Last Re Number parameter if specified or the next unique number stored in the UNIQUE_IDENTIFIER_CONTROL table, adds 1 to this number, and starts numbering requisitions. If any of the requisition numbers generated al the program loops until it finds a unique number. For every line that imported, a default distribution is created with the account informati specify. (You specify account information in any of the following colu the PO_REQUISITIONS_INTERFACE_ALL or the PO_REQ_DIST_INTERFACE_ ALL table: CHARGE_ACCOUNT_ID, ACCRUAL_ACCOUNT_ID, VARIANCE_ ACCOUNT_ID, BUDGET_ACCOUNT_ID, or any of the CHARGE_ACCOUNT_ SEGMENT columns.) Requisition supply is also created for every approve requisition that is successfully imported.

Upload: shyam77

Post on 22-Oct-2015

496 views

Category:

Documents


10 download

DESCRIPTION

Requisition Interface Table description

TRANSCRIPT

Page 1: Requisition Interface

As long as the Multiple Distributions field in the RequisitionImport program is No (or blank), Requisition Import looks for distributioninformation in the PO_REQUISITIONS_INTERFACE_ALL table.

should use the PO_REQ_DIST_INTERFACE_ALL table to createmultiple distributions only for requisitions created in non-Oracle systems that usemultiple distributions.

If you specify a value in the REQ_NUMBER_SEGMENT1 column of the PO_REQUISITIONS_INTERFACE_ALLtable, all lines with the same value for this column are grouped together under arequisition header. If you provide a value in the GROUP_CODE column, all lineswith the same value in this column are grouped together under a requisition header.

If you provide a value in the REQ_NUMBER_SEGMENT1 column of the PO_REQUISITIONS_INTERFACE_ALL table, this value becomes the requisitionnumber. If not, the Requisition Import program uses either the Last RequisitionNumber parameter if specified or the next unique number stored in the PO_UNIQUE_IDENTIFIER_CONTROL table, adds 1 to this number, and startsnumbering requisitions. If any of the requisition numbers generated already exists,the program loops until it finds a unique number. For every line that is successfullyimported, a default distribution is created with the account information that youspecify. (You specify account information in any of the following columns in eitherthe PO_REQUISITIONS_INTERFACE_ALL or the PO_REQ_DIST_INTERFACE_ALL table: CHARGE_ACCOUNT_ID, ACCRUAL_ACCOUNT_ID, VARIANCE_ACCOUNT_ID, BUDGET_ACCOUNT_ID, or any of the CHARGE_ACCOUNT_SEGMENT columns.) Requisition supply is also created for every approvedrequisition that is successfully imported.

Page 2: Requisition Interface

Column Name Data Type NullableTRANSACTION_ID NUMBER YesPROCESS_FLAG VARCHAR2(YesREQUEST_ID NUMBER YesPROGRAM_ID NUMBER YesPROGRAM_APPLICATION_ID NUMBER YesPROGRAM_UPDATE_DATE DATE YesLAST_UPDATED_BY NUMBER YesLAST_UPDATE_DATE DATE YesLAST_UPDATE_LOGIN NUMBER YesCREATION_DATE DATE YesCREATED_BY NUMBER Yes

INTERFACE_SOURCE_CODE VARCHAR2(NoINTERFACE_SOURCE_LINE_ID NUMBER Yes

SOURCE_TYPE_CODE VARCHAR2(YesREQUISITION_HEADER_ID NUMBER YesREQUISITION_LINE_ID NUMBER YesREQ_DISTRIBUTION_ID NUMBER YesREQUISITION_TYPE VARCHAR2(YesDESTINATION_TYPE_CODE VARCHAR2(No

ITEM_DESCRIPTION VARCHAR2(YesQUANTITY NUMBER Yes

UNIT_PRICE NUMBER YesAUTHORIZATION_STATUS VARCHAR2(NoBATCH_ID NUMBER YesGROUP_CODE VARCHAR2(YesDELETE_ENABLED_FLAG VARCHAR2(YesUPDATE_ENABLED_FLAG VARCHAR2(YesAPPROVER_ID NUMBER(9,YesAPPROVER_NAME VARCHAR2(YesAPPROVAL_PATH_ID NUMBER YesNOTE_TO_APPROVER VARCHAR2(YesPREPARER_ID NUMBER(9,Yes

Page 3: Requisition Interface

AUTOSOURCE_FLAG VARCHAR2(Yes

REQ_NUMBER_SEGMENT1 VARCHAR2(YesREQ_NUMBER_SEGMENT2 VARCHAR2(YesREQ_NUMBER_SEGMENT3 VARCHAR2(YesREQ_NUMBER_SEGMENT4 VARCHAR2(YesREQ_NUMBER_SEGMENT5 VARCHAR2(YesHEADER_DESCRIPTION VARCHAR2(YesHEADER_ATTRIBUTE_CATEGORY VARCHAR2(YesHEADER_ATTRIBUTE1 VARCHAR2(YesHEADER_ATTRIBUTE2 VARCHAR2(YesHEADER_ATTRIBUTE3 VARCHAR2(YesHEADER_ATTRIBUTE4 VARCHAR2(YesHEADER_ATTRIBUTE5 VARCHAR2(YesHEADER_ATTRIBUTE6 VARCHAR2(YesHEADER_ATTRIBUTE7 VARCHAR2(YesHEADER_ATTRIBUTE8 VARCHAR2(YesHEADER_ATTRIBUTE9 VARCHAR2(YesHEADER_ATTRIBUTE10 VARCHAR2(YesHEADER_ATTRIBUTE11 VARCHAR2(YesHEADER_ATTRIBUTE12 VARCHAR2(YesHEADER_ATTRIBUTE13 VARCHAR2(YesHEADER_ATTRIBUTE14 VARCHAR2(YesURGENT_FLAG VARCHAR2(YesHEADER_ATTRIBUTE15 VARCHAR2(YesRFQ_REQUIRED_FLAG VARCHAR2(YesJUSTIFICATION VARCHAR2(YesNOTE_TO_BUYER VARCHAR2(YesNOTE_TO_RECEIVER VARCHAR2(YesITEM_ID NUMBER Yes

Page 4: Requisition Interface

ITEM_SEGMENT1 VARCHAR2(YesITEM_SEGMENT2 VARCHAR2(YesITEM_SEGMENT3 VARCHAR2(YesITEM_SEGMENT4 VARCHAR2(YesITEM_SEGMENT5 VARCHAR2(YesITEM_SEGMENT6 VARCHAR2(YesITEM_SEGMENT7 VARCHAR2(YesITEM_SEGMENT8 VARCHAR2(YesITEM_SEGMENT9 VARCHAR2(YesITEM_SEGMENT10 VARCHAR2(YesITEM_SEGMENT11 VARCHAR2(YesITEM_SEGMENT12 VARCHAR2(YesITEM_SEGMENT13 VARCHAR2(YesITEM_SEGMENT14 VARCHAR2(YesITEM_SEGMENT15 VARCHAR2(YesITEM_SEGMENT16 VARCHAR2(YesITEM_SEGMENT17 VARCHAR2(YesITEM_SEGMENT18 VARCHAR2(YesITEM_SEGMENT19 VARCHAR2(YesITEM_SEGMENT20 VARCHAR2(YesITEM_REVISION VARCHAR2(YesCHARGE_ACCOUNT_ID NUMBER YesCHARGE_ACCOUNT_SEGMENT1 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT2 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT3 VARCHAR2(Yes

CHARGE_ACCOUNT_SEGMENT4 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT5 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT6 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT7 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT8 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT9 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT10 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT11 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT12 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT13 VARCHAR2(Yes

Page 5: Requisition Interface

CHARGE_ACCOUNT_SEGMENT14 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT15 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT16 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT17 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT18 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT19 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT20 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT21 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT22 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT23 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT24 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT25 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT26 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT27 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT28 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT29 VARCHAR2(YesCHARGE_ACCOUNT_SEGMENT30 VARCHAR2(YesCATEGORY_ID NUMBER YesCATEGORY_SEGMENT1 VARCHAR2(YesCATEGORY_SEGMENT2 VARCHAR2(YesCATEGORY_SEGMENT3 VARCHAR2(YesCATEGORY_SEGMENT4 VARCHAR2(YesCATEGORY_SEGMENT5 VARCHAR2(YesCATEGORY_SEGMENT6 VARCHAR2(YesCATEGORY_SEGMENT7 VARCHAR2(YesCATEGORY_SEGMENT8 VARCHAR2(YesCATEGORY_SEGMENT9 VARCHAR2(YesCATEGORY_SEGMENT10 VARCHAR2(YesCATEGORY_SEGMENT11 VARCHAR2(YesCATEGORY_SEGMENT12 VARCHAR2(YesCATEGORY_SEGMENT13 VARCHAR2(YesCATEGORY_SEGMENT14 VARCHAR2(YesCATEGORY_SEGMENT15 VARCHAR2(YesCATEGORY_SEGMENT16 VARCHAR2(YesCATEGORY_SEGMENT17 VARCHAR2(YesCATEGORY_SEGMENT18 VARCHAR2(YesCATEGORY_SEGMENT19 VARCHAR2(YesCATEGORY_SEGMENT20 VARCHAR2(YesUNIT_OF_MEASURE VARCHAR2(YesUOM_CODE VARCHAR2(YesLINE_TYPE_ID NUMBER YesLINE_TYPE VARCHAR2(YesUN_NUMBER_ID NUMBER YesUN_NUMBER VARCHAR2(YesHAZARD_CLASS_ID NUMBER Yes

Page 6: Requisition Interface

HAZARD_CLASS VARCHAR2(Yes

MUST_USE_SUGG_VENDOR_FLAG VARCHAR2(YesREFERENCE_NUM VARCHAR2(YesWIP_ENTITY_ID NUMBER YesWIP_LINE_ID NUMBER YesWIP_OPERATION_SEQ_NUM NUMBER YesWIP_RESOURCE_SEQ_NUM NUMBER YesWIP_REPETITIVE_SCHEDULE_ID NUMBER Yes

PROJECT_NUM VARCHAR2(Yes

TASK_NUM VARCHAR2(Yes

EXPENDITURE_TYPE VARCHAR2(YesSOURCE_ORGANIZATION_ID NUMBER Yes

SOURCE_ORGANIZATION_CODE VARCHAR2(Yes

SOURCE_SUBINVENTORY VARCHAR2(YesDESTINATION_ORGANIZATION_ID NUMBER YesDESTINATION_ORGANIZATION_CODE VARCHAR2(YesDESTINATION_SUBINVENTORY VARCHAR2(YesDELIVER_TO_LOCATION_ID NUMBER YesDELIVER_TO_LOCATION_CODE VARCHAR2(YesDELIVER_TO_REQUESTOR_ID NUMBER(9,YesDELIVER_TO_REQUESTOR_NAME VARCHAR2(YesSUGGESTED_BUYER_ID NUMBER(9,YesSUGGESTED_BUYER_NAME VARCHAR2(YesSUGGESTED_VENDOR_NAME VARCHAR2(YesSUGGESTED_VENDOR_ID NUMBER YesSUGGESTED_VENDOR_SITE VARCHAR2(YesSUGGESTED_VENDOR_SITE_ID NUMBER YesSUGGESTED_VENDOR_CONTACT VARCHAR2(YesSUGGESTED_VENDOR_CONTACT_ID NUMBER YesSUGGESTED_VENDOR_PHONE VARCHAR2(YesSUGGESTED_VENDOR_ITEM_NUM VARCHAR2(YesLINE_ATTRIBUTE_CATEGORY VARCHAR2(YesLINE_ATTRIBUTE1 VARCHAR2(YesLINE_ATTRIBUTE2 VARCHAR2(YesLINE_ATTRIBUTE3 VARCHAR2(YesLINE_ATTRIBUTE4 VARCHAR2(YesLINE_ATTRIBUTE5 VARCHAR2(YesLINE_ATTRIBUTE6 VARCHAR2(YesLINE_ATTRIBUTE7 VARCHAR2(Yes

Page 7: Requisition Interface

LINE_ATTRIBUTE8 VARCHAR2(YesLINE_ATTRIBUTE9 VARCHAR2(YesLINE_ATTRIBUTE10 VARCHAR2(YesLINE_ATTRIBUTE11 VARCHAR2(YesLINE_ATTRIBUTE12 VARCHAR2(YesLINE_ATTRIBUTE13 VARCHAR2(YesLINE_ATTRIBUTE14 VARCHAR2(YesLINE_ATTRIBUTE15 VARCHAR2(YesNEED_BY_DATE DATE YesNOTE1_ID NUMBER YesNOTE2_ID NUMBER YesNOTE3_ID NUMBER YesNOTE4_ID NUMBER YesNOTE5_ID NUMBER YesNOTE6_ID NUMBER YesNOTE7_ID NUMBER YesNOTE8_ID NUMBER YesNOTE9_ID NUMBER YesNOTE10_ID NUMBER YesNOTE1_TITLE VARCHAR2(YesNOTE2_TITLE VARCHAR2(YesNOTE3_TITLE VARCHAR2(YesNOTE4_TITLE VARCHAR2(YesNOTE5_TITLE VARCHAR2(YesNOTE6_TITLE VARCHAR2(YesNOTE7_TITLE VARCHAR2(YesNOTE8_TITLE VARCHAR2(YesNOTE9_TITLE VARCHAR2(YesNOTE10_TITLE VARCHAR2(Yes

GL_DATE DATE YesDIST_ATTRIBUTE_CATEGORY VARCHAR2(YesDISTRIBUTION_ATTRIBUTE1 VARCHAR2(YesDISTRIBUTION_ATTRIBUTE2 VARCHAR2(YesDISTRIBUTION_ATTRIBUTE3 VARCHAR2(YesDISTRIBUTION_ATTRIBUTE4 VARCHAR2(YesDISTRIBUTION_ATTRIBUTE5 VARCHAR2(YesDISTRIBUTION_ATTRIBUTE6 VARCHAR2(YesDISTRIBUTION_ATTRIBUTE7 VARCHAR2(YesDISTRIBUTION_ATTRIBUTE8 VARCHAR2(YesDISTRIBUTION_ATTRIBUTE9 VARCHAR2(YesDISTRIBUTION_ATTRIBUTE10 VARCHAR2(Yes

Page 8: Requisition Interface

DISTRIBUTION_ATTRIBUTE11 VARCHAR2(YesDISTRIBUTION_ATTRIBUTE12 VARCHAR2(YesDISTRIBUTION_ATTRIBUTE13 VARCHAR2(YesDISTRIBUTION_ATTRIBUTE14 VARCHAR2(YesDISTRIBUTION_ATTRIBUTE15 VARCHAR2(YesPREPARER_NAME VARCHAR2(NoBOM_RESOURCE_ID NUMBER YesACCRUAL_ACCOUNT_ID NUMBER YesVARIANCE_ACCOUNT_ID NUMBER YesBUDGET_ACCOUNT_ID NUMBER YesUSSGL_TRANSACTION_CODE VARCHAR2(YesGOVERNMENT_CONTEXT VARCHAR2(YesCURRENCY_CODE VARCHAR2(YesCURRENCY_UNIT_PRICE NUMBER YesRATE NUMBER YesRATE_DATE DATE YesRATE_TYPE VARCHAR2(YesPREVENT_ENCUMBRANCE_FLAG VARCHAR2(YesAUTOSOURCE_DOC_HEADER_ID NUMBER YesAUTOSOURCE_DOC_LINE_NUM NUMBER Yes

PROJECT_ACCOUNTING_CONTEXT VARCHAR2(YesEXPENDITURE_ORGANIZATION_ID NUMBER YesPROJECT_ID NUMBER YesTASK_ID NUMBER YesEND_ITEM_UNIT_NUMBER VARCHAR2(YesEXPENDITURE_ITEM_DATE DATE YesDOCUMENT_TYPE_CODE VARCHAR2(YesORG_ID NUMBER YesTRANSACTION_REASON_CODE VARCHAR2(YesALLOCATION_TYPE VARCHAR2(YesALLOCATION_VALUE NUMBER Yes

MULTI_DISTRIBUTIONS VARCHAR2(Yes

REQ_DIST_SEQUENCE_ID NUMBER YesKANBAN_CARD_ID NUMBER YesEMERGENCY_PO_NUM VARCHAR2(YesAWARD_ID NUMBER(15YesTAX_CODE_ID NUMBER YesOKE_CONTRACT_HEADER_ID NUMBER YesOKE_CONTRACT_NUM VARCHAR2(YesOKE_CONTRACT_VERSION_ID NUMBER Yes

Page 9: Requisition Interface

OKE_CONTRACT_LINE_ID NUMBER YesOKE_CONTRACT_LINE_NUM VARCHAR2(YesOKE_CONTRACT_DELIVERABLE_ID NUMBER YesOKE_CONTRACT_DELIVERABLE_NUM VARCHAR2(YesSECONDARY_UNIT_OF_MEASURE VARCHAR2(YesSECONDARY_UOM_CODE VARCHAR2(YesSECONDARY_QUANTITY NUMBER YesPREFERRED_GRADE VARCHAR2(YesVMI_FLAG VARCHAR2(YesTAX_USER_OVERRIDE_FLAG VARCHAR2(YesAMOUNT NUMBER YesCURRENCY_AMOUNT NUMBER YesSHIP_METHOD VARCHAR2(YesESTIMATED_PICKUP_DATE DATE YesBASE_UNIT_PRICE NUMBER YesNEGOTIATED_BY_PREPARER_FLAG VARCHAR2(YesTAX_NAME VARCHAR2(Yes

Page 10: Requisition Interface

DescriptioNA- Derived by Oracle during Requisition ImportNA- Derived by Oracle during Requisition ImportNA- Derived by Oracle during Requisition ImportNA- Derived by Oracle during Requisition ImportNA- Derived by Oracle during Requisition ImportNA- Derived by Oracle during Requisition ImportNA- Derived by Oracle during Requisition ImportNA- Derived by Oracle during Requisition ImportNA- Derived by Oracle during Requisition ImportNA- Derived by Oracle during Requisition ImportNA- Derived by Oracle during Requisition Import

This is optional. Required during technical development.

NA- Derived by Oracle during Requisition ImportNA- Derived by Oracle during Requisition ImportNA- Derived by Oracle during Requisition ImportNA- Derived by Oracle during Requisition ImportEXPENSE / INVENTORY

Default 'APPROVED' if we want to import approved requisitionThis is optional. Required during technical development.This is optional. Required during technical development.No longer usedNo longer usedNANANANANA

To identify the source of your importedrequisitions. Constant Value

Default 'VENDOR'. Mandatory if the DESTINATION_TYPE_CODE is 'EXPENSE' or 'SHOP FLOOR'.DESTINATION_TYPE_CODE of 'INVENTORY', then leave NULL

Description of Inventory Items. Mandatory in case requistion is for NON Inventory items.

If NULL can be derived in the UNIT_PRICE and CURRENCY_UNIT_PRICE columns. If no sourcing rules are found for the item, supplier sourcing fails and the UNIT_PRICE is defaulted from the item master forsupplier requisition lines and from the CST_ITEM_COSTS_FOR_GL_VIEW for internal requisitions.

Page 11: Requisition Interface

NANANANARequisition DescriptionNANANANANANANANANANANANANANANAOptionalNANAOptionalOptionalOptionalPopulate Item_segment1

The Requisition Import program automatically derives sourcing information for both your inventory and purchase requisition lines if you set theAUTOSOURCE_FLAG to 'Y' and set up the sourcing rules for the item.Should not be populated if we know the Vendor detailsIf you set the AUTOSOURCE_FLAG to 'P' and set up the sourcing rules for theitem, the program uses the following columns for supplier-sourced requisitionlines, if they're provided in the requisitions interface table:SUGGESTED_VENDOR_IDSUGGESTED_VENDOR_SITE_IDIf the above columns are not provided when the AUTOSOURCE_FLAG is set to'P', the program derives them from the sourcing rules.

Mandatory if we want to Group requisilion based on Requisition Number. Otherw wise Oracle will group the requision headers based on Grouping Rule defined.

Page 12: Requisition Interface

OWNER

BOLINF XXNBTY_R INDEXBOLINF XXNBTY_R INDEX

NA BOLINF XXNBTY_R INDEXNA BOLINF XXNBTY_REINDEXNA BOLINF XXNBTY_REINDEXNA BOLINF XXNBTY_R INDEXNA BOLINF XXNBTY_REINDEXNA BOLINF XXNBTY_REINDEXNA BOLINF XXNBTY_REPACKAGE

Mandatory if SOURCE_TYPE_CODE or DESTINATION_TYPE_CODEis 'INVENTORY'. Items should be VALID IN MTL_SYSTEM_ITEMS_B for Destination Organization. item must be purchasing-enabled for the purchasing and destination organizations.If you enter a DESTINATION_TYPE_CODE of 'INVENTORY', the ITEM_ID isrequired and it must be stock-enabled for the destination organization. If you also enter a DESTINATION_SUBINVENTORY, the item must either be valid in the subinventory or it must not be restricted to a subinventory.

The segment should be a Valid Combinations defined in GL_CODE_COMBINATIONS table for the current Chart of accounts

OBJECT_NAME

OBJECT_TYPE

Page 13: Requisition Interface

NA BOLINF XXNBTY_REPACKAGE BONA BOLINF XXNBTY_RESEQUENCENA BOLINF XXNBTY_R SEQUENCENA BOLINF XXNBTY_R TABLENA BOLINF XXNBTY_R TABLENA BOLINF XXNBTY_R TABLENA BOLINF XXNBTY_R TABLENA BOLINF XXNBTY_RETABLENA BOLINF XXNBTY_RETABLENA BOLINF XXNBTY_RETABLENA BOLINF XXNBTY_R TABLENANANANANANA

Must be Valid in MTL_CATEGORY_B for the destination Organization

NANANANANANANANANANANANANANANAPopulate UOM CodeValid UOM CodeNAOptionalNAOptionalNA

Page 14: Requisition Interface

Optional

OptionalNANANANANA

NA

NA in our case. This is mandatory in case source_type_code is INVENTORY

NA in our case. This is mandatory in case source_type_code is INVENTORYNAValid Organization defined in MTL_PARAMETERSMandatory if DESTINATION_TYPE_CODE is 'INVENTORY'.NAValid Locations defined in HR_LOCATIONS TableNAValid employeeNAOPTIONALmust be a Valid vendor in ap_supplier TableNAmust be a Valid vendor site in ap_supplier_site TableNAmust be a Valid vendor contact in ap_supplier_contacts TableNANANAOptionalOptionalOptionalOptionalNANANANA

Optional. If item is marked as approved supplier list item in Item master then this flag to be Y

IF PROJECT_ACCOUNTING_CONTEXT = Y then mandatory. Have to be a Valid project defined in PA_PROJECTS_ALL

IF PROJECT_ACCOUNTING_CONTEXT = Y then mandatory. Have to be a Valid project defined in pa_tasks

IF PROJECT_ACCOUNTING_CONTEXT = Y then mandatory. Have to be a Valid project defined in pa_expenditure_type

Page 15: Requisition Interface

NANANANANANANANAMandatory for For MRP or Inventory planned itemsNANANANANANANANANANANANANANANANANANANANA

OptionalOptionalOptionalNANANANANANANANA

Default NULL. If you are using requisition encumbrance, the GL_DATE that you enter must be in an open or future General Ledger period and an open Purchasing period. Furthermore, if you are using Oracle Inventory, the GL_DATE must be in an open Inventory period for inventory-sourced requisitions.

Page 16: Requisition Interface

NANANANANAValid employee and valid UserNANANANANANAMandatory if CURRENCY is foreign currency. NULL for ledger_currency.NAMandatoty if RATE_TYPE = USER. Else should be NULLMandatory if you provide a value in CURRENCY_CODEMandatory if you provide a value in CURRENCY_CODENADerived by Requisition import program if AUTOSOURCE_FLAG = 'Y'Derived by Requisition import program if AUTOSOURCE_FLAG = 'Y'

Mandatory if PROJECT_ACCOUNTING_CONTEXT = YNANANANANAMandatory NANANA

NANANANANANANA

Default N, Mandatory if Requistion is raised for a Particular Project. Value populated to be Y.

Default N in case we have multiple distributions for one req line then we have to populate the distribution interface table and populate the DIST_SEQUENCE_ID

in case we have multiple distributions for one req line then we have to populate the distribution interface table and populate the DIST_SEQUENCE_ID

Page 17: Requisition Interface

NANANANANANANANANANANANANANANANAoptional

Page 18: Requisition Interface

STATUS

VALID 10-Jan-14VALID 10-Jan-14VALID 10-Jan-14VALID 9-Jan-14VALID 9-Jan-14VALID 10-Jan-14VALID 9-Jan-14VALID 9-Jan-14VALID 9-Jan-14

LAST_DDL_TIME

Page 19: Requisition Interface

VALID 10-Jan-14VALID ###VALID 8-Jan-14VALID 10-Jan-14VALID 7-Jan-14VALID 8-Jan-14VALID 10-Jan-14VALID 7-Jan-14VALID 10-Jan-14VALID 9-Jan-14VALID ###

Page 20: Requisition Interface

Populate only if there is multiple distribution for one requisition LineColumn Name ID Pk Null? Data Type Default

ACCRUAL_ACCOUNT_ID 1 Y NUMBERALLOCATION_TYPE 2 Y VARCHAR2 (25 Byte)ALLOCATION_VALUE 3 Y NUMBERBATCH_ID 4 Y NUMBERBUDGET_ACCOUNT_ID 5 Y NUMBERCHARGE_ACCOUNT_ID 6 Y NUMBERCHARGE_ACCOUNT_SEGMENT1 7 Y VARCHAR2 (25 Byte)CHARGE_ACCOUNT_SEGMENT2 8 Y VARCHAR2 (25 Byte)CHARGE_ACCOUNT_SEGMENT3 9 Y VARCHAR2 (25 Byte)CHARGE_ACCOUNT_SEGMENT4 10 Y VARCHAR2 (25 Byte)CHARGE_ACCOUNT_SEGMENT5 11 Y VARCHAR2 (25 Byte)CHARGE_ACCOUNT_SEGMENT6 12 Y VARCHAR2 (25 Byte)CHARGE_ACCOUNT_SEGMENT7 13 Y VARCHAR2 (25 Byte)CREATED_BY 37 Y NUMBERCREATION_DATE 38 Y DATE

DESTINATION_ORGANIZATION_ID/ CODE 39 Y NUMBERDESTINATION_SUBINVENTORY 40 Y VARCHAR2 (10 Byte)DESTINATION_TYPE_CODE 41 Y VARCHAR2 (25 Byte)DISTRIBUTION_ATTRIBUTE1 42 Y VARCHAR2 (150 Byte)DISTRIBUTION_ATTRIBUTE10 43 Y VARCHAR2 (150 Byte)DISTRIBUTION_ATTRIBUTE11 44 Y VARCHAR2 (150 Byte)DISTRIBUTION_ATTRIBUTE12 45 Y VARCHAR2 (150 Byte)DISTRIBUTION_ATTRIBUTE13 46 Y VARCHAR2 (150 Byte)DISTRIBUTION_ATTRIBUTE14 47 Y VARCHAR2 (150 Byte)DISTRIBUTION_ATTRIBUTE15 48 Y VARCHAR2 (150 Byte)DISTRIBUTION_ATTRIBUTE2 49 Y VARCHAR2 (150 Byte)DISTRIBUTION_ATTRIBUTE3 50 Y VARCHAR2 (150 Byte)DISTRIBUTION_ATTRIBUTE4 51 Y VARCHAR2 (150 Byte)DISTRIBUTION_ATTRIBUTE5 52 Y VARCHAR2 (150 Byte)DISTRIBUTION_ATTRIBUTE6 53 Y VARCHAR2 (150 Byte)DISTRIBUTION_ATTRIBUTE7 54 Y VARCHAR2 (150 Byte)DISTRIBUTION_ATTRIBUTE8 55 Y VARCHAR2 (150 Byte)DISTRIBUTION_ATTRIBUTE9 56 Y VARCHAR2 (150 Byte)DISTRIBUTION_NUMBER 57 Y NUMBERDIST_ATTRIBUTE_CATEGORY 58 Y VARCHAR2 (30 Byte)DIST_SEQUENCE_ID 59 Y NUMBEREXPENDITURE_ITEM_DATE 60 Y DATEEXPENDITURE_ORGANIZATION_ID 61 Y NUMBEREXPENDITURE_TYPE 62 Y VARCHAR2 (30 Byte)GL_DATE 63 Y DATEGOVERNMENT_CONTEXT 64 Y VARCHAR2 (30 Byte)

Page 21: Requisition Interface

GROUP_CODE 65 Y VARCHAR2 (30 Byte)INTERFACE_SOURCE_CODE 66 N VARCHAR2 (25 Byte)INTERFACE_SOURCE_LINE_ID 67 Y NUMBERITEM_ID 68 Y NUMBERLAST_UPDATED_BY 69 Y NUMBERLAST_UPDATE_DATE 70 Y DATELAST_UPDATE_LOGIN 71 Y NUMBERORG_ID 72 Y NUMBER NULL PREVENT_ENCUMBRANCE_FLAG 73 Y VARCHAR2 (1 Byte)PROCESS_FLAG 74 Y VARCHAR2 (30 Byte)PROGRAM_APPLICATION_ID 75 Y NUMBERPROGRAM_ID 76 Y NUMBERPROGRAM_UPDATE_DATE 77 Y DATEPROJECT_ACCOUNTING_CONTEXT 78 Y VARCHAR2 (30 Byte)PROJECT_ID 79 Y NUMBERPROJECT_NUM 80 Y VARCHAR2 (25 Byte)QUANTITY 81 Y NUMBERREQUEST_ID 82 Y NUMBERREQUISITION_HEADER_ID 83 Y NUMBERREQ_NUMBER_SEGMENT1 84 Y VARCHAR2 (20 Byte)REQUISITION_LINE_ID 85 Y NUMBERREQ_DISTRIBUTION_ID 86 Y NUMBERTASK_ID 87 Y NUMBERTASK_NUM 88 Y VARCHAR2 (25 Byte)TRANSACTION_ID 89 Y NUMBERUPDATE_ENABLED_FLAG 90 Y VARCHAR2 (1 Byte)USSGL_TRANSACTION_CODE 91 Y VARCHAR2 (30 Byte)VARIANCE_ACCOUNT_ID 92 Y NUMBEROKE_CONTRACT_LINE_ID 93 Y NUMBEROKE_CONTRACT_LINE_NUM 94 Y VARCHAR2 (150 Byte)OKE_CONTRACT_DELIVERABLE_ID 95 Y NUMBEROKE_CONTRACT_DELIVERABLE_NUM 96 Y VARCHAR2 (150 Byte)AMOUNT 97 Y NUMBERCURRENCY_AMOUNT 98 Y NUMBER

Page 22: Requisition Interface

Histogram

Yes NAYes NAYes NAYes Same as PO_REQUISITIONS_INTERFACE_ALLYes NAYes NAYesYesYesYesYesYesYesYes default profileYes Default sysdate

YesYes Same as PO_REQUISITIONS_INTERFACE_ALLYes Same as PO_REQUISITIONS_INTERFACE_ALLYes NAYes NAYes NAYes NAYes NAYes NAYes NAYes NAYes NAYes NAYes NAYes NAYes NAYes NAYes NAYes Seq 1, 2, 3Yes NAYes Same as PO_REQUISITIONS_INTERFACE_ALLYes NAYes Same as PO_REQUISITIONS_INTERFACE_ALLYes Same as PO_REQUISITIONS_INTERFACE_ALLYes Same as PO_REQUISITIONS_INTERFACE_ALLYes NA

Data file will have Code and the same need to be valiated from MTL_PARAMETERS

Page 23: Requisition Interface

Yes Same as PO_REQUISITIONS_INTERFACE_ALLYes Same as PO_REQUISITIONS_INTERFACE_ALLYes NAYes NAYes PROFILEYes PROFILEYes PROFILEYes Same as PO_REQUISITIONS_INTERFACE_ALLYes NAYes NAYes NAYes NAYes NAYes Same as PO_REQUISITIONS_INTERFACE_ALLYes NAYes Same as PO_REQUISITIONS_INTERFACE_ALLYes Sum should be equal to requisition lines QUANITYYes NAYes NAYes Same as PO_REQUISITIONS_INTERFACE_ALLYes NAYes NAYes NAYes Same as PO_REQUISITIONS_INTERFACE_ALLYes NAYes NAYes NAYes NAYes NAYes NAYes NAYes NAYes NAYes NA

Page 24: Requisition Interface

Rescheduling RequisitionsIf you use Oracle Master Scheduling/MRP or a non-Oracle MRP system withOracle Purchasing, you may find that you need to reschedule requisitions as yourplanning requirements change. Purchasing's Requisition Import program lets youreschedule requisition lines according to changes in your planned orders.Reschedule Interface TableYou can reschedule requisitions from your planning application with theReschedule Interface table. Since you have already loaded your requisitions intoPurchasing, you simply need to identify for Purchasing the requisition lines youwant to reschedule. After you identify each line to reschedule, you can update thequantity and the need-by date for the corresponding requisition line. You decidewhen to import the information from the requisitions interface table intoPurchasing. Purchasing lets you use the Reschedule Interface table as often as youwant.

Understanding the PO_RESCHEDULE_INTERFACE TablePO_RESCHEDULE_INTERFACE is the table Purchasing uses to import informationfor requisition lines your planning system has rescheduled. One row in the tablecorresponds to a requisition line whose quantity or need-by date you want tochange. Requisition Import updates your requisition lines within Purchasing withthe information in this table. The table PO_RESCHEDULE_INTERFACE consists ofcolumns Purchasing uses to identify requisition lines for update. The table PO_RESCHEDULE_INTERFACE contains the following columns:

For PO_RESCHEDULE_INTERFACE Shree you can refer the below Notes for details.. (I have copied from the Manufacturing API Guide)

Page 25: Requisition Interface

The column LINE_ID identifies a requisition line which your planning systemreschedules. The columns QUANTITY and NEED_BY_DATE contain newinformation for the requisition lines your planning system updates.The other columns in the table store the same information the PO_REQUISITIONS_INTERFACE_ALL table uses to track when you place data in the PO_RESCHEDULE_INTERFACE table.Columns Reserved for Requisition ImportRequisition Import inserts values into the column PROCESS_ID. RequisitionImport inserts the PROCESS_ID to identify all requisition lines which youreschedule at one time. You should not insert any data in this column.

Page 26: Requisition Interface

Shree you can refer the below Notes for details.. (I have copied from the Manufacturing API Guide)