Item Creation in Orcale Inventory

Creating Items

Oracle Inventory provides us with the functionality to create Items. Sets of attributes are assigned to an Item. The attributes define the characteristics of the Item. A group of attributes values defines a template, and a template can be assigned to an Item to automatically define the set of attribute values.
An Item template defines the Item Type. For example, a Finished Good template will identify certain characteristics that define the Item as a finished good, with attributes such as "Inventory Item" and "Stockable" with a value of "Yes". Let's look at how to create an Item in Oracle Inventory. We will also assign a Finished Good template to the Item.

Getting ready

Log in to Oracle E-Business Suite R12 with the username and password assigned to you by the System Administrator. If you are working on the Vision demonstration database, you can use OPERATIONS/WELCOME as the USERNAME/PASSWORD:

1. Select the Inventory Responsibility.
2. Select the V1 Inventory Organization.

How to do it...

Let's list the steps required to create an Item:

1. Navigate to Items | Master Items. Please note that Items are defined in the Master Organization.
2. Enter the Item code, for example, PRD20001.
3. Enter a description for the Item:
   
   
4. Select Copy From from the tools menu (or press Alt+T). We are going to copy the attributes from the Finished Good template:
   
   
5. We can also copy attributes from an existing Item.
6. Enter Finished Good and click on the Apply button (or press Alt+A) and click on the Done button.
7. Save the Item definition by clicking on the Save icon (or press Ctrl+S).

How it works...

Items contain attributes and attributes contain information about an Item. Attributes can be controlled centrally at the Master Organization level or at the Inventory Organization level.

There's more...

Once the Item is created, we need to assign it to a category and an inventory organization.

Assigning Items to inventory organizations

For us to be able to perform transactions with the Item in the inventory, we need to assign the Item to an inventory organization. We can also use the organization Item form to change the attributes at the organization level. For example, an Item may be classified as raw materials in one organization and finished goods in another organization.

1. From the Tools menu, select Organization Assignment.
2. Select the inventory organization for the Item. For example, A1–ACME Corporation. Click on the Assigned checkbox.
   
   
3. Save the assignment.

Assigning Items to categories

When an Item is created, it is assigned to a default category. However, you may want to perform transactions with the Item in more than one functional area, such as Inventory, Purchasing, Cost Management, Service, Engineering, and so on. You need to assign the Item to the relevant functional area. A category within a functional area is a logical classification of Items with similar characteristics.

1. From the Tools menu, select Categories.
2. Select the Categories Set, Control Level, and the Category combination to assign to the Item:
   
   
3. Save the assignment.

Exploring Item attributes

There are more than 250 Item attributes grouped into 17 main attribute groups. In this recipe, we will explore the main groups that are used within the financial modules.

How to do it...

Let's explore some Item attributes:

1. Search for the Finished Good Item by navigating to Items | Master Items:
   
   
2. Click on the Find icon. You then enter the Item code and click on the Find button to search for the Item.
3. Select the tabs to review each of the attributes group:
   
   
4. In the Main tab, check that the Item Status is Active. We can also enter a long description in the Long Description field.
5. The default value of the primary Unit of Measure (UOM) can be defined in the INV: Default Primary Unit of Measure profile option. The value can be overwritten when creating the Item. The Primary UOM is the default UOM used in other modules. For example, in Receivables it is used for invoices and credit memos.
   
   
6. In the Inventory tab, check that the following are enabled:
   • Inventory Item: It enables the Item to be transacted in Inventory. The default Inventory Item category is automatically assigned to the Item, if enabled.
   • Stockable: It enables the Item to be stocked in Inventory.
   • Transactable: Order Management uses this flag to determine how returns are transacted in Inventory.
   • Reservable: It enables the reservation of Items during transactions. For example, during order entry in Order Management.
     
     
7. In the Costing tab, check that the following are enabled:
   • Costing: Enables the accounting for Item costs. It can be overridden in the Cost Management module, if average costing is used.
   • Cost of Goods Sold Account: The cost of goods sold account is entered. This is a general ledger account. The value defaults from the Organization parameters.
     
     
8. In the Purchasing tab, enter a Default Buyer for the purchase orders, a List Price, and an Expense Account. Check that the following are enabled:
   • Purchased: It enables us to purchase and receive the Item.
   • Purchasable: It enables us to create a Purchase Order for the Item.
   • Allow Description Update: It enables us to change the description of the Item when raising the Purchase Order.
   • RFQ Required: Set this value to Yes to enable us to require a quotation for this Item.
   • Taxable: Set this value to Yes with the Input Tax Classification Code as VAT–15%. This can be used with the default rules in E-Tax.
   • Invoice Matching: Receipt Required–Yes. This is to allow for three-way matching.
9. In the Receiving tab, review the controls.
   
   
10. In the Order Management tab, check that the following are enabled:
    • Customer Ordered: This enables us to define prices for an Item assigned to a price list.
    • Customer Orders Enabled: This enables us to sell the Item.
    • Shippable: This enables us to ship the Item to the Customer.
    • Internal Ordered: This enables us to order an Item via internal requisitions.
    • Internal Orders Enabled: This enables us to temporarily exclude an Item from internal requisitions.
    • OE Transactable: This is used for demand management of an Item.
      
      
11. In the Invoicing tab, enter values for the Accounting Rule, Invoicing Rule, Output Tax Classification Code, and Payment Terms. Enter the Sales Account code and check that the Invoiceable Item and Invoice Enabled checkboxes are enabled.

Oracle E-Business Suite 12 Financials Cookbook

Take the hard work out of your daily interactions with Oracle E-Business Suite financials by using the 50+ recipes from this book and eBook

Read more about this book

(For more resources on Oracle, see here.)

Creating Item templates

An Item template is a set of attributes that enable the 'quick' creation of an Item. In this recipe, we will create an Item template that can be used to create many similar Items. We will copy from the Finished Good template to our new template called ACME Finished Good.

Getting ready

Log in to Oracle E-Business Suite and select the Inventory responsibility.

How to do it...

Let's list the steps required to create an Item template:

1. Navigate to Setup | Items | Templates.
2. Select the Inventory Organization.
   
   
3. From the Find Item Templates form, click on New button or press Alt+N.
   
   
4. In the Template field, enter the name of the new template; for example, enter ACME Finished Good.
5. In the Description field, enter a suitable description, for example, enter ACME Finished Good Template.
   
   
6. Select Copy Template from the Tools menu.
7. We can use this form to select the attributes groups that we want to copy from the Finished Good template.
8. Click on the Apply button.
9. Click on the Done button.
10. In the dialog box presented to us, with the message "Do you want to save the changes you have made?", click on the Yes button.

How it works...

Item templates can be created from scratch. To make the template creation process easier, Oracle has provided us with a number of seeded templates as a starting point to copy from. We can also combine templates and manually amend the attributes to define our template. When we copy from an existing template, we have choices that determine how the copy will occur.

The three main choices are as follows:

1. Overwrite: All selected attribute values are copied to the new template and any values that we have manually created will be overwritten.
2. Append: Attributes that have no value will be copied across to our template. This mode is useful if you are using a combination of templates.
3. Overwrite Not Null: Only the selected attributes that contain values will be copied.

There's more...

Let's amend the template to allow us to automatically populate the template with some default values. Let's create an Item and apply the amended template to the Item.

Amending the template

Let's search for the template and amend the templates to include some of the default values:

1. Search for the ACME Finished Good template by navigating to Setup | Items | Templates.
2. Enter ACME Finished Good in the Template field and click on the Find button.
3. Click on the Open button to view the template.
   
   
4. In the Attributes Group region, select Purchasing and enter some default values, for example:
   • Default Buyer: Stock, Ms. Pat
   • Input Tax Classification Code: VAT-15%
   • Taxable: Yes
   • Allow Description Update: Yes
   • Receipt Required: Yes
5. Save the template.
   
   
6. In the Attributes Group region, select Receiving and enter some default values, for example:
   • Over-Receipt Qty Action: Warning
   • Receipt Routing: Direct Delivery
   • Days Early Receipt Allowed: 5
   • Days Late Receipt Allowed: 2
   • Receipt Date Action: Warning
7. Save the template.
8. In the Attributes Group region, select Invoicing and enter some default values, for example:
   • Accounting Rule: Immediate
   • Payment Terms: Immediate
9. Save the template.

Creating an Item and applying the template to the Item

Let's create an Item and apply the template to the Item:

1. Navigate to Items | Master Items.
2. Enter the Item code and description.
3. Select Copy From in the Tools menu.
   
   
4. Click on the Apply button.
5. Click on the Done button. This action will validate the template created.
   
   
6. Click on the Purchasing tab to review the default values of the attributes assigned automatically by the template.
7. Save the Item.

Exploring Item controls

During the creation of Items, we may decide to restrict the use of the Items by controlling Items within an Inventory Organization. When an Item is defined, it is defined in the Item Master Organization and can then be assigned to other Inventory Organizations. Items are then held in Subinventories, which can contain Locators. Locator, Serial number, Lot number, and Revision number within a Subinventory can be used to control Items. In this recipe, we will explore some of the control parameters for Items.

Getting ready

Log in to Oracle E-Business Suite and select the Inventory responsibility.

How to do it...

Let's explore the following Item controls:

1. Item Status
2. Item Attribute

The Item Status is the status of an Item and it determines the actions that can be performed on an Item. For example, an obsolete Item may not be sold to the customer, but can be used as parts for repairs and can still be stockable. Let's create an Item status for obsolete Items.

1. Navigate to Setup | Items | Status Code.
   
   
2. In the Status field, enter Obsolete and ACME Obsolete in the Translated Status field.
3. Enter a Description, for example, ACME Obsolete Items.
4. Enable the following attributes:
   • BOM Allowed
   • Stockable
   • Transactable
5. Save the form.

The levels that the attributes can be controlled at are set in the Item Attribute Controls form. Let's look at some of the Item Attribute Controls:

1. Navigate to Setup Items | Attribute Controls|
2. From the menu, select View | Query By Example | Enter (or press F11 on the keyboard).
3. In the Group Name field, enter Main%.
   
   
4. From the Menu, select View | Query By Example | Run (or press Ctrl+F11 on the keyboard).
5. Observe that some attributes are controlled at the Master Level and some at the Org Level.
6. Close the form.

There's more...

Items are stored in a Subinventory and can be controlled using a locator. Items can be identified by lot and by serial numbers.

Storing Items by Subinventories

Subinventories are distinct separations of Items within an Inventory Organization. Subinventories can be physical or logical. Items within an Inventory Organization must reside in a Subinventory.
Transactions are performed from the Subinventories. Examples of Subinventories include: finished goods, van, stores, staging area, and fast moving goods. Let's create a finished goods Subinventory and restrict an Item to the Subinventory.

1. Navigate to Setup | Organizations | Subinventories.
2. Click on the New button.
   
   
3. In the Name field, enter ACME-FG.
4. In the Description, enter ACME Finished Goods.
5. In the Locator Control field, select Item level. This will enable the Inventory transactions for this Subinventory to use locator control, which we define at the Item level.
6. Save the record.

Let's restrict an Item to the Subinventory:

1. Navigate to Items | Organization Items.
2. Search for the PRD20001 Item.
   
   
3. Select the Inventory tab and select the Restrict Subinventories checkbox.
4. Save the record.
   
   
5. In the Tools menu, select Items Subinventories.
6. Select ACME-FG in the Subinventory field.
7. Save the record.

Storing Items by locators

Stock locators identify the physical areas where Items are stored. Additional controls can be placed on the Items in stock locators. For example, we can control the shelf life of an Item with stock locators. Stock locators are usually defined as Row, Rack, and Bin. Let's create three stock locators for the ACME Finished Goods Subinventory and restrict an Item by locator control:

1. Navigate to Setup | Organizations | Subinventories.
   
   
2. Search for the ACME-FG Subinventory (press F11 on the keyboard, and enter the search mask ACME%, then press Ctrl+F11 on the keyboard).
3. Click on the Locator button to enter the locator details.
   
   
4. Enter A1.1.1 in the Locator field.
5. In the Description field, enter ACME FG 1.
6. In the Type field, select Storage Locator.
7. Enter another row for A1.1.2, ACME FG 2, with Storage Locator in the Type field.
8. Repeat for A1.1.3, ACME FG 3, with Storage Locator in the Type field.
9. Save the record.

The structure of the stock locator is defined in the stock locator Flexfield structure and can be defined to fit your business requirements. Locator Control can be "prespecified" before they are used or can be defined dynamically as Items are received or shipped.
Let's restrict an Item to the Locator:

1. Navigate to Items | Organization Items.
2. Search for the PRD20001 Item.

3. Select the Inventory tab, select the Restrict Locators checkbox, and then select the Locator Control as Prespecified.
4. Save the record.
   
   
5. In the Tools menu, select Items Subinventories.
6. Select A1.1.1 in the Locator field.
7. Save the record.

Identifying Items by lot control

A lot of numbers can be used to identify Items that share the same specifications. For example, lot numbers can be used to specify the expiry period of an Item. Let's look at how to use lot numbers to control Items. We will impose a shelf life of 30 days on the Item and assign lot numbers to the Item:

1. Navigate to Items | Organization Items.
2. Search for the PRD20001 Item.
   
   
3. Select the Inventory tab.
4. In the Lot Expiration (Shelf Life) region, select the Control field and select Shelf Life Days.
5. Enter 30 as the number of days.
6. In the Lot region, select Full Control in the Control field.
7. Save the record.

Tracking Items using serial control

Serial numbers can be used to track an Item. A serial number is assigned to each unit of the Item, if serial control is used:

1. Navigate to Items | Organization Items.
2. Search for the PRD20001 Item.
   
   
3. Select the Inventory tab.
4. In the Serial region, select the Generation field, and select At Receipt. This will allow us to specify the format of the serial numbers at the time of receipt.
5. Save the record.

Controlling Items using revisions

Items can have versions. Item versions are controlled using revisions. For example, we can decide to make the PRD20002 revision controlled, and have another version of the Item. Let's change the attribute to revision controlled and add a revision B to the Item:

1. Navigate to Items | Organization Items.
2. Search for the Item PRD20002.
   
   
3. In the Inventory tab, enable the Revision Control checkbox.
4. In the displayed message, select OK.
5. Save the Item.
   
   
6. From the Tools menu, select Revisions.
7. Add a line for Revision B of the Item with the description Revised Widget.
8. Save the record.

Order Management Tips and Script

Allocation Error During Transact Move Order
"Error: The material sourcing process failed to create picking suggestions for line 2 of move order number 59641464"
"APP-INV-05297: Invalid transaction and serial control combination"
Encountered the above error message after clicked on "Allocate" button in Transact Move Orders form. Even after I backordered the line, I could not proceed to Pick Release, failed Pick Release.
Root Cause: Item lot reserved for the order line is no more valid.
Action: Unreserve the invalid item lot, pick release, transact move order & ship confirm successfully.

Cannot Perform Shipping Transactions At Shipping Transactions form, Action combo box is disabled. Can't perform pick release, create delivery, etc.
Grant role to user at OM responsibility. At Shipping Execution Grants form, add record, enter user name & save.
Setup -> Shipping -> Grants and Role Definitions -> Grants
Default role is "Upgrade Role", which you can maintain it in
Setup -> Shipping -> Grants and Role Definitions -> Define Roles


Launch Pick Release Failed My Sales Order (SO) has been booked successfully. Order header status is Booked, order line status is Awaiting Shipping. Quantity on-hand is sufficient. At Shipping Transactions form, I performed "Launch Pick Release", order line status remained Awaiting Shipping, it did not change to Picked.
No warning or error was prompted.
In my case, it was due to Credit Hold. Go Order Header -> Actions -> Additional Order Information, I saw Hold with message "Credit check hold applied. Overall limit exceeded.". GoActions -> Release Holds to release hold before proceed to Pick Release.
In order to perform Release Holds action, you need to be given authorities. Get the Holds Name and check the authorizations at Setup -> Orders -> Holds.


Where to Setup New Sales Order Type Under Order Management responsibility, Setup -> Transactions Types -> Define

Pick List Ship-To Address Not Get Updated
It is an address issue.
The Ship-to Address appears on the Pick List (for ISO) is retrieved from wsh_locations table. As for IR-ISO setup, ship-to-address comes from Customer address instead of Location address.

When we updates the customer address, hz_locations table get update. By right, bothhz_locations table and wsh_locations table should be synchronized automatically. But, in my case, it was not. Business event "oracle.apps.ar.hz.Location.update" is enabled, everything else is fine. But the synchronize is not happening.

Logged a tar and Oracle came back with suggestion to run "Import Shipping Location" program in OM responsibility to synchronize the table. These was their reply (copied from some another article).

"...The 'Import Shipping locations' concurrent program imports all of the internal and external
locations from HR/HZ LOCATIONS tables into the WSH_LOCATIONS tables.

This program should be executed at least once when upgrading to 11.5.9. After the
upgrade, it should not be required to rerun this concurrent program since any
changes in the HR/HZ LOCATIONS tables are automatically synced up with WSH
tables.

There are a few exceptions when Import Shipping Locations concurrent program should be run. These exceptions would be only when any updates to a
Customer's information does not get reflected when creating a new sales order
or when you find any inconsistencies in Location records when interfaced from
HR to WSH Locations, such as an incorrect country code..."

Question is the auto-sync is not happening and Oracle can't give reason why.

End up I have to run "Import Shipping Location" program to solve the issue (and it took 3.5 hours to complete with the Start-Date value = sysdate-4).


HL Pick Slip SRS Report -> Completed Warning After Pick Release action, pick slip report will get submitted, but it often completed warning.
How to know if actual picking taken place? Picking could be failed or success even the program completed warning. E.g. For printing issue, even it completed warning, but the stock has been picked.
From Requests list, click on the request, view Output. If there is records there, it was successfully picked. Another faster way, observe the request in the list, if the 4th and 5th parameters have value, it is successful.



Unable to Pick Release Internal Sales Order (ISO)
ISO was created from Internal Requisition (IR), order line status is "Awaiting Shipping", shipment line status is "Ready to Release", next step is "Pick Release". Performed Pick Release, shipment line status is not changed. As usual, no error shown in the log.
After investigation, found onhand no issue, inventory period is opened, what else could be the cause?
Ans: The ISO has tied to subinventory ABC, but the manual Pick Release is picked from subinventory DEF. So, change the "Pick From" subinventory to ABC, problem solved. Note: ISO subinventory is defaulted from IR subinventory.


Meaning of wsh_new_deliveries.released_status
Meaning of wsh_new_deliveries.released_status field value, reproduced from Document406189.1.
B Backordered Line failed to be allocated in Inventory
C Shipped Line has been shipped
D Cancelled Line is Cancelled
N Not ready for release Line is not ready to be released
R Ready to release Line is ready to be released
S Released to Warehouse Line has been released to Inventory for processing
X Not Applicable Line is not applicable for Pick Release
Y Staged Line has been picked and staged by Inventory


Order Shipping Line Status Stuck in "Shipped", Next Step "Run Interfaces" Obviously "Interface Trip Stop" program has been ran, but status is not change. What could be the reason behind?
Check error records in Transaction Open Interface (Transactions->Transaction Open Interface). Any error stuck with error in the interface will cause this issue.
Table:
mtl_transactions_interface
Fields:
process_flag => 3, if error
organization_id => Inventory Organization
error_code

OE_ORDER_HEADERS_ALL -> SOLD_TO_ORG_ID and SHIP_TO_ORG_ID At the Order Header table, SOLD_TO_ORG_ID refers to customer_id whereas SHIP_TO_ORG_ID is the ORGANIZATION_ID from OE_SHIP_TO_ORGS_V. From the SHIP_TO_ORG_ID field, we can trace back the actual ship-to address for a particular order.
Before we can use OE_SHIP_TO_ORGS_V view in sql, we have to first initialize the view. However, we can skip it by going direct to the tables.

--to get actual ship to address for a Sales Order
select hl.*
from
apps.hz_cust_site_uses_all cs,
apps.hz_cust_acct_sites_all cas,
apps.hz_party_sites ps,
apps.hz_locations hl
where
hl.location_id=ps.location_id and
ps.party_site_id=cas.party_site_id and
cas.cust_acct_site_id=cs.cust_acct_site_id and
hl.country='IN' and
hl.state='JAMMU AND KASHMIR' and
cs.site_use_code='SHIP_TO' and
cs.org_id=123
order by cs.site_use_id desc

--to get order base on ship to address
-- cs.site_use_id equals oe_order_headers_all.ship_to_org_id
select * from apps.oe_order_headers_all where ship_to_org_id in (
select cs.site_use_id
from
apps.hz_cust_site_uses_all cs,
apps.hz_cust_acct_sites_all cas,
apps.hz_party_sites ps,
apps.hz_locations hl
where
hl.location_id=ps.location_id and
ps.party_site_id=cas.party_site_id and
cas.cust_acct_site_id=cs.cust_acct_site_id and
hl.country='IN' and
hl.state='JAMMU AND KASHMIR' and
cs.site_use_code='SHIP_TO' and
cs.org_id=123 )
and order_type_id=2345



Validation failed for the field - Ship To
Encountered this error during Order Copy (at header level).
Root Cause:
Customer Site Location is deactivated.
Fix:
Activate it. Customer->Standard. Choose the correct address base on the ship to address shown in the sale order, click "Open". Identify "Ship To" underUsage column, check the Active checkbox.
Some useful backend table for these:
Take oe_order_headers_all.ship_to_org_id to hz_cust_site_uses_all.site_use_id, hz_cust_site_uses_all.location field refers Customer Site Location.
We can get the Customer Site Number by using
select ps.party_site_number
from
apps.hz_cust_site_uses_all cs,
apps.hz_cust_acct_sites_all cas,
apps.hz_party_sites ps,
apps.hz_locations hl
where
hl.location_id=ps.location_id and
ps.party_site_id=cas.party_site_id and
cas.cust_acct_site_id=cs.cust_acct_site_id and
cs.site_use_code='SHIP_TO' and
cs.org_id=123 and
cs.site_use_id = 12345678


Query Manager for Shipping Transactions Form
Org Code is not defaulted to the OU's inventory organization, but it is defaulted to another inventory organization which has no relationship with current OU. Somemore, Org Code field is disabled. Why?
Ans: Setup->Shipping->Grants and Role Definitions->Grants. Grant to your Oracle user id, the Org Code will be enabled with blank. Set the Org Code from there (the field is optional).



Shipping Method - Lookups
To look at the complete list of Shipping Method, you need to go to Setup->Organizations->Shipping Methods in Inventory responsibility. It is a System Lookups, type: SHIP_METHOD.You can add/modify/remove Shipping Method there.

Picked Quantity Auto Transferred Back After Backordered?
Picked quantity (Pick Release process) will NOT be transferred back automatically to original locator/subinventory after Backordered transaction.


1 Delivery Has Many Delivery Lines, How to Backorder Only 1 Delivery Line
At Shipping Transactions form, query the delivery line by order number and item code (assuming this item has only 1 delivery line), enter the Shipped Qty as 0, Backordered Qty as the total quantity at the delivery line.Click Delivery tab, select "Ship Entered Quantities", press OK. If a delivery has multiple lines, only the selected line will be backordered.

Setting Up Internal Customer for IR-ISO
How does customer get recognized during Internal Sales Order (ISO) creation?
Ans: Location. In IR, there is a Ship-to-Location, and this internal location must tie to the same location defined in Customer Address (Customers->Addresses->Location->Internal Location). Each unique location can only assigned to only 1 customer and 1 address.Table for customer address and location: RA_SITE_USES_ALL

Auto Allocation in Transact Move Order for a Sales Order If the SO shipment status is now "Released to Warehouse", we need to perform Transact Move Orders. For the Move Order, which setup trigger auto allocation?
Ans: In the Release Rules form, Inventory tab, Auto Allocate selection (Yes/No)


No Delivery Detail Found After Ship-Confirm action, shipping line status is Closed, Interface Trip Stop program completed Warning, with warning message "No Delivery Detail Found" in the log file.
Where to rectify this?
Ans: Go Inventory responsibility, Transactions->Transaction Open Interface, check for any errors in the shipping organization. Rectify from there.


Pick Release in Shipping Transactions Form This is an alternate way to perform pick release at a place other than Release Sales Ordersform.
Shipping->Transactions
Only Lines/LPNs tab is enabled, other tabs like "Delivery", "Path by Stop" & "Path by Trip" are disabled as picking is not done yet. Go "Action" LOV, choose "Launch Pick Release", clickGo button.


Internal Requisition Approved, Internal Sales Order Created and Picked, Need to Cancel All, How? Ans: First perform backorder for ISO, cancel the ISO, then cancel the IR. Do remember to move back the inventory from staging to picking.

Collection from unknown author ( oraclea2z )

Singal Query cover P2P cycle

The consultant life while working at client site is not easy during ERP transformation projects, many times it's required to provide some adhoc query for extract to ends users, therefore it is important to have a cheat sheet so that such untimely things can be easily handled in sort span. Hope these query and tips useful to all Inhouse IT personals who is part of Implementation Project team.
1. You need to list out all Internal Requisitions that do not have an associated Internal Sales order.
Internal Requisitions without Sales order
2. You want to display what requisition and PO are linked(Relation with Requisition and PO )

Requisition and PO

3. You need to list out all cancel Requisitions
Cancel Requisition
4. You need to list those PR which havn't auto created to PO.(Purchase Requisition without a Purchase Order)

PR without PO

5. You need to list all information form PR to PO ...as a requisition moved from different stages till converting into PR. This query capture all details related to that PR to PO.
PR to PO

6.Identifying all PO's which does not have any PR's
PO without Requisition
7. Relation between Requisition and PO tables
Here is link:
PO_DISTRIBUTIONS_ALL =>PO_HEADER_ID, REQ_DISTRIBUTION_ID
PO_HEADERS_ALL=>PO_HEADER_ID, SEGMENT1
PO_REQ_DISTRIBUTIONS_ALL =>DISTRIBUTION_ID, REQUISITION_LINE_ID
PO_REQUISITION_LINES_ALL =>REQUISITION_LINE_ID)
PO_REQUISITION_HEADERS_ALL =>REQUISITION_HEADER_ID, REQUISITION_LINE_ID, SEGMENT1
What you have to make a join on PO_DISTRIBUTIONS_ALL (REQ_DISTRIBUTION_ID) and PO_REQ_DISTRIBUTIONS_ALL (DISTRIBUTION_ID) to see if there is a PO for the req.
8.You need to find table which hold PO Approval path...
These two table keeps the data:

• PO_APPROVAL_LIST_HEADERS
• PO_APPROVAL_LIST_LINES

9. List all the PO's with there approval ,invoice and Payment Details
List PO's with Approval , invoice and Payment info

10.You need to know the link to GL_JE_LINES table for purchasing accrual and budgetary control actions..
The budgetary (encumbrance) and accrual actions in the purchasing module generate records that will be imported into GL for the corresponding accrual and budgetary journals.
The following reference fields are used to capture and keep PO information in the GL_JE_LINES table.
These reference fields are populated when the Journal source (JE_SOURCE in GL_JE_HEADERS) is
Purchasing.
Budgetary Records from PO (These include reservations, reversals and cancellations):

• REFERENCE_1- Source (PO or REQ)
• REFERENCE_2- PO Header ID or Requisition Header ID (from po_headers_all.po_header_id or
  po_requisition_headers_all.requisition_header_id)
• REFERENCE_3- Distribution ID (from po_distributions_all.po_distribution_id or
  po_req_distributions_all.distribution_id)
• REFERENCE_4- Purchase Order or Requisition number (from po_headers_all.segment1 or
  po_requisition_headers_all.segment1)
• REFERENCE_5- (Autocreated Purchase Orders only) Backing requisition number (from po_requisition_headers_all.segment1)

Accrual Records from PO:

• REFERENCE_1- Source (PO)
• REFERENCE_2- PO Header ID (from po_headers_all.po_header_id)
• REFERENCE_3- Distribution ID (from po_distributions_all.po_distribution_id
• REFERENCE_4- Purchase Order number (from po_headers_all.segment1)
• REFERENCE_5- (ON LINE ACCRUALS ONLY) Receiving Transaction ID (from rcv_receiving_sub_ledger.rcv_transaction_id)

Take a note for Period end accruals, the REFERENCE_5 column is not used.
11. List me all open PO's
List me all Open PO'S
12.There are different authorization_status can a requisition have.

• Approved
• Cancelled
• In Process
• Incomplete
• Pre-Approved
• Rejected

and you should note: When we finally close the requisition from Requisition Summary form the authorization_status of the requisition does not change. Instead it's closed_code becomes 'FINALLY CLOSED'.
13. A standard Quotations one that you can tie back to a PO.
Navigate to RFQ -> Auto create -> enter a PO and reference it back.
14. I want to debug for a PO , where should I start.
Thats is possible, your PO get stuck somewhere, so what you have to do is to analyze which stage it stucked.Get po_header_id first and run each query and then analyze the data.For better understanding this is splited into 5 major stages.
Stage 1: PO Creation :

PO_HEADERS_ALL

select po_header_id from po_headers_all where segment1 =<po_number>;
select * from po_headers_all where po_header_id =<po_header_id>;

po_lines_all

select * from po_lines_all where po_header_id =<po_header_id>;
po_line_locations_all
select * from po_line_locations_all where po_header_id =<po_header_id>;
po_distributions_all

select * from po_distributions_all where po_header_id =<po_header_id>;

po_releases_all
SELECT * FROM po_releases_all WHERE po_header_id =<po_header_id>;

Stage 2: Once PO is received data is moved to respective receving tables and inventory tables

RCV_SHIPMENT_HEADERS

select * from rcv_shipment_headers where shipment_header_id in
(select shipment_header_id from rcv_shipment_lines
where po_header_id =<po_header_id>);

RCV_SHIPMENT_LINES

select * from rcv_shipment_lines where po_header_id =<po_header_id>;

RCV_TRANSACTIONS

select * from rcv_transactions where po_header_id =<po_header_id>;

RCV_ACCOUNTING_EVENTS

SELECT * FROM rcv_Accounting_Events WHERE rcv_transaction_id IN
(select transaction_id from rcv_transactions
where po_header_id =<po_header_id>);

RCV_RECEIVING_SUB_LEDGER

select * from rcv_receiving_sub_ledger where rcv_transaction_id in (select transaction_id from rcv_transactions where po_header_id =<po_header_id>);

RCV_SUB_LEDGER_DETAILS

select * from rcv_sub_ledger_details
where rcv_transaction_id in (select transaction_id from rcv_transactions where po_header_id =<po_header_id>);

MTL_MATERIAL_TRANSACTIONS

select * from mtl_material_transactions where transaction_source_id =<po_header_id>;

MTL_TRANSACTION_ACCOUNTS

select * from mtl_transaction_accounts where transaction_id in ( select transaction_id from mtl_material_transactions where transaction_source_id = =<po_header_id>);

Stage 3: Invoicing details

AP_INVOICE_DISTRIBUTIONS_ALL

select * from ap_invoice_distributions_all where po_distribution_id in ( select po_distribution_id from po_distributions_all where po_header_id =<po_header_id>);

AP_INVOICES_ALL

select * from ap_invoices_all where invoice_id in
(select invoice_id from ap_invoice_distributions_all where po_distribution_id in
( select po_distribution_id from po_distributions_all where po_header_id =<po_header_id>));

Stage 4 : Many Time there is tie up with Project related PO

PA_EXPENDITURE_ITEMS_ALL

select * from pa_expenditure_items_all peia where peia.orig_transaction_reference in
( select to_char(transaction_id) from mtl_material_transactions
where transaction_source_id = <po_header_id> );

Stage 5 : General Ledger

Prompt 17. GL_BC_PACKETS ..This is for encumbrances

SELECT * FROM gl_bc_packets WHERE reference2 IN ('<po_header_id>');

GL_INTERFACE

SELECT *
FROM GL_INTERFACE GLI
WHERE user_je_source_name ='Purchasing'
AND gl_sl_link_table ='RSL'
AND reference21='PO'
AND EXISTS
( SELECT 1
FROM rcv_receiving_sub_ledger RRSL
WHERE GLI.reference22 =RRSL.reference2
AND GLI.reference23 =RRSL.reference3
AND GLI.reference24 =RRSL.reference4
AND RRSL.rcv_transaction_id in
(select transaction_id from rcv_transactions
where po_header_id <po_header_id>));

GL_IMPORT_REFERENCES

SELECT *
FROM gl_import_references GLIR
WHERE reference_1='PO'
AND gl_sl_link_table ='RSL'
AND EXISTS
( SELECT 1
FROM rcv_receiving_sub_ledger RRSL
WHERE GLIR.reference_2 =RRSL.reference2
AND GLIR.reference_3 =RRSL.reference3
AND GLIR.reference_4 =RRSL.reference4
AND RRSL.rcv_transaction_id in
(select transaction_id from rcv_transactions
where po_header_id =<po_header_id>))

Feel free to share or comment..