Explore topic-wise InterviewSolutions in .

RCV_SHIPMENT_HEADERS:It contains supplier shipment HEADER DATA LIKE Shipment date, supplier NAME

RCV_TRANSACTIONS_INTERFACE:It contains received data like Item name, quantity, and receiving LOCATION

• RCV_SHIPMENT_LINES
• MTL_MATERIAL_TRANSACTIONS_TEMP
• PO_LINE_LOCATIONS_ALL
• PO_DISTRIBUTIONS_ALL

RCV_SHIPMENT_HEADERS:It contains supplier shipment header data like Shipment date, supplier Name

RCV_TRANSACTIONS_INTERFACE:It contains received data like Item name, quantity, and receiving location

A Purchase order is a COMMERCIAL document and first official order ISSUED by the buyer to the supplier, indicating types, quantities, and agreed prices for products or services the supplier will provide to the buyer.

BASICALLY, there are four types of Purchase Orders

Standard Purchase Order:

Used for One-time purchases for goods and services. Here you know the item, price, payment terms an DELIVERY schedule

Planned Purchase Order:

Created when you have long-term agreement with the supplier. You must specify the DETAILS of goods and services, payment terms and the tentative delivery schedule

Blanket Purchase Agreement:

Created when the details of items and services, payment terms are known but not specific about the delivery schedule

Contract Purchase Agreement:

Created when the terms and conditions of a purchase are known but specific goods and services are not.

A Purchase order is a commercial document and first official order issued by the buyer to the supplier, indicating types, quantities, and agreed prices for products or services the supplier will provide to the buyer.

Basically, there are four types of Purchase Orders

Standard Purchase Order:

Used for One-time purchases for goods and services. Here you know the item, price, payment terms an delivery schedule

Planned Purchase Order:

Created when you have long-term agreement with the supplier. You must specify the details of goods and services, payment terms and the tentative delivery schedule

Blanket Purchase Agreement:

Created when the details of items and services, payment terms are known but not specific about the delivery schedule

Contract Purchase Agreement:

Created when the terms and conditions of a purchase are known but specific goods and services are not.

A quotation is a supplier’s response to RFQ.
Quote analysis is the PROCESS of REVIEWING the quotations given by the suppliers. The best quotation will be selected by analyzing CERTAIN factors like price, quality, delivery TIME etc.

A quotation is a supplier’s response to RFQ.
Quote analysis is the process of reviewing the quotations given by the suppliers. The best quotation will be selected by analyzing certain factors like price, quality, delivery time etc.

A Request for Quotation (RFQ) is a formal request sent to the suppliers to find the pricing and other information for an item or items. BASED on the information supplied, the supplier quotes a quotation against the RFQ form.
In general, RFQ’s are created before purchasing any item to actually know the price quotes from one or more suppliers.
In Oracle EBS, RFQ’s can be auto created from an existing Purchase Requisition or can be a fresh RFQ.

There are three types of quotations and RFQs that come with Purchasing by default:

Catalog: USED for high-volume items or items for which your supplier sends you information regularly. A Catalog quotation or RFQ also INCLUDES price breaks at different quantity levels.

Standard: Used for items you’ll NEED only once or not very often, but not necessarily for a specific, fixed quantity, location, and DATE. For example, you could use a Catalog quotation or RFQ for office supplies, but use a Standard quotation or RFQ for a special type of pen you don’t order very often. A Standard quotation or RFQ also includes price breaks at different quantity levels.

Bid: Used for a specific, fixed quantity, location, and date. For example, a Bid would be used for a large or expensive piece of equipment that you’ve never ordered before, or for an item that incurs transportation or other special costs. You cannot specify price breaks for a Bid quotation or RFQ.

A Request for Quotation (RFQ) is a formal request sent to the suppliers to find the pricing and other information for an item or items. Based on the information supplied, the supplier quotes a quotation against the RFQ form.
In general, RFQ’s are created before purchasing any item to actually know the price quotes from one or more suppliers.
In Oracle EBS, RFQ’s can be auto created from an existing Purchase Requisition or can be a fresh RFQ.

There are three types of quotations and RFQs that come with Purchasing by default:

Catalog: Used for high-volume items or items for which your supplier sends you information regularly. A Catalog quotation or RFQ also includes price breaks at different quantity levels.

Standard: Used for items you’ll need only once or not very often, but not necessarily for a specific, fixed quantity, location, and date. For example, you could use a Catalog quotation or RFQ for office supplies, but use a Standard quotation or RFQ for a special type of pen you don’t order very often. A Standard quotation or RFQ also includes price breaks at different quantity levels.

Bid: Used for a specific, fixed quantity, location, and date. For example, a Bid would be used for a large or expensive piece of equipment that you’ve never ordered before, or for an item that incurs transportation or other special costs. You cannot specify price breaks for a Bid quotation or RFQ.

Only an APPROVER or a REVIEWER can reject requisition. Only a buyer can return a requisition. A buyer will return a requisition to the PREPARER for INCOMPLETE or inaccurate information.

Only an approver or a reviewer can reject requisition. Only a buyer can return a requisition. A buyer will return a requisition to the preparer for incomplete or inaccurate information.

Pre-APPROVED is the status of a requisition when an authorized approver has approved the requisition and has forwarded the requisition to ANOTHER INDIVIDUAL to review.

Pre-Approved is the status of a requisition when an authorized approver has approved the requisition and has forwarded the requisition to another individual to review.

The Category BOX is a required FIELD and is used to define GOODS and services at a summary or detailed level.

The Category box is a required field and is used to define goods and services at a summary or detailed level.

Requisition templates can be used to help you quickly create requisitions. A requisition template contains much of the information needed to create a requisition, THUS reducing the AMOUNT of data entry required to create a new requisition. If you find yourself repeatedly creating similar requisitions for your group or department, you should CONSIDER creating and SAVING requisition templates as a time-saver.

If the data of requisition remain the same for repeated purchase of an item, the information can be copied to a template and the same can be copied to the Requisition as many number of times as required.

Requisition templates can be used to help you quickly create requisitions. A requisition template contains much of the information needed to create a requisition, thus reducing the amount of data entry required to create a new requisition. If you find yourself repeatedly creating similar requisitions for your group or department, you should consider creating and saving requisition templates as a time-saver.

If the data of requisition remain the same for repeated purchase of an item, the information can be copied to a template and the same can be copied to the Requisition as many number of times as required.

Requisition Import RUN Report: We can view the number of requisitions created and the number of records that SHOWED an error

Requisition Import Exceptions Report: In this report we can SEE all the rows that fail VALIDATION.

Requisition Import Run Report: We can view the number of requisitions created and the number of records that showed an error

Requisition Import Exceptions Report: In this report we can see all the rows that fail validation.

• PO_REQUISITION_INTERFACE_ALL
• PO_REQ_DIST_INTERFACE_ALL
• PO_INTERFACE_ERRORS

It is a concurrent program, which is used to import requisition from ORACLE or Non-Oracle system.

DATA is first loaded in PO_REQUISITION_ALL table. The RIP can then be run, to import the records from the interface table as requisition in Oracle Processing.

RIP creates a requisition line and ONE or more requisition distribution for each row it FINDS in the interface table. It then groups these lines on Requisitions according to PARAMETERS defined

It is a concurrent program, which is used to import requisition from Oracle or Non-Oracle system.

Data is first loaded in PO_REQUISITION_ALL table. The RIP can then be run, to import the records from the interface table as requisition in Oracle Processing.

RIP creates a requisition line and one or more requisition distribution for each row it finds in the interface table. It then groups these lines on Requisitions according to parameters defined

PO_REQUISITION_HEADERS_ALL (SEGMENT1 column in this table represents the requisition number):

This table stores HEADER information of a Purchase Requisition.

Important columns of this table:

REQUISITION_HEADER_ID:It is a unique system generated Requisition identifier

PREPARER_ID:It is a unique identifier of the employee who prepared the requisition

SEGMENT1:It is the Requisition number

AUTHORIZATION_STATUS:Authorization status type

TYPE_LOOKUP_CODE:Requisition type

ORG_ID:Unique OPERATING unit unique identifier

PO_REQUISITION_LINES_ALL:

This table stores information about Requisition lines in a Purchase Requisition. This table stores information related to the line number, item number, item category, item description, item quantities, units, prices, need-by date, deliver-to location, REQUESTOR, notes, and suggested supplier information for the requisition line.

Important columns of this table:

REQUISITION_HEADER_ID:It is a unique system generated Requisition identifier

REQUISITION_LINE_ID:Link between PO_REQUISITION_LINES_ALL And PO_REQ_DISTRIBUTIONS_ALL

LINE_NUM:INDICATES the Line number

LINE_TYPE_ID:Indicates the Line type

CATEGORY_ID:Unique Item category identifier

ITEM_DESCRIPTION:Description of the Item

QUANTITY NUMBER:Quantity ordered

PO_REQ_DISTRIBUTIONS_ALL:

This table stores information about the accounting distributions of a requisition line. Each requisition line must have at least one accounting distribution. Each row includes the Accounting Flexfield ID and Requisition line quantity.

Important columns of this table:

DISTRIBUTION_ID:Unique Requisition distribution identifier

REQUISITION_LINE_ID:Unique Requisition line identifier

CODE_COMBINATION_ID:Unique General Ledger charge account identifier

 DISTRIBUTION_NUM:Distribution number

PO_REQUISITION_HEADERS_ALL (SEGMENT1 column in this table represents the requisition number):

This table stores Header information of a Purchase Requisition.

Important columns of this table:

REQUISITION_HEADER_ID:It is a unique system generated Requisition identifier

PREPARER_ID:It is a unique identifier of the employee who prepared the requisition

SEGMENT1:It is the Requisition number

AUTHORIZATION_STATUS:Authorization status type

TYPE_LOOKUP_CODE:Requisition type

ORG_ID:Unique Operating unit unique identifier

PO_REQUISITION_LINES_ALL:

This table stores information about Requisition lines in a Purchase Requisition. This table stores information related to the line number, item number, item category, item description, item quantities, units, prices, need-by date, deliver-to location, requestor, notes, and suggested supplier information for the requisition line.

Important columns of this table:

REQUISITION_HEADER_ID:It is a unique system generated Requisition identifier

REQUISITION_LINE_ID:Link between PO_REQUISITION_LINES_ALL And PO_REQ_DISTRIBUTIONS_ALL

LINE_NUM:Indicates the Line number

LINE_TYPE_ID:Indicates the Line type

CATEGORY_ID:Unique Item category identifier

ITEM_DESCRIPTION:Description of the Item

QUANTITY NUMBER:Quantity ordered

PO_REQ_DISTRIBUTIONS_ALL:

This table stores information about the accounting distributions of a requisition line. Each requisition line must have at least one accounting distribution. Each row includes the Accounting Flexfield ID and Requisition line quantity.

Important columns of this table:

DISTRIBUTION_ID:Unique Requisition distribution identifier

REQUISITION_LINE_ID:Unique Requisition line identifier

CODE_COMBINATION_ID:Unique General Ledger charge account identifier

 DISTRIBUTION_NUM:Distribution number