ORACLE INFORMATION

INTERFACE DETAILS

CUSTOMERS UPLOAD USING INTERFACE:
RA_CUSTOMERS_INTERFACE_ALL
RA_CUSTOMER_PROFILES_INT_ALL
RA_CONTACT_PHONES_INT_ALL
RA_CUSTOMER_BANKS_INT_ALL
RA_CUST_PAY_METHOD_INT_ALL
----------------------------------------------------
HZ_PARTIES
HZ_PARTY_SITES
HZ_CUSTOMER_PROFILES
HZ_CUST_SITE_USES_ALL
HZ_CUST_ACCT_SITES_ALL
HZ_CUST_ACCOUNTS
HZ_CUST_ACCT_RELATE_ALL
HZ_LOCATIONS

CUSTOMER UPLOAD USING API:
-- Creation of Customer Account and Party using API
HZ_CUST_ACCOUNT_V2PUB.create_cust_account
-> Check whether the customer account exist for the above party_id
-- To create a location
HZ_LOCATION_V2PUB.create_location
-> Check whether the given city, county, state combination is valid
-> Check whether the location already available
-- To create a party site using party_id and location_id
-- which were created from the earlier steps
HZ_PARTY_SITE_V2PUB.create_party_site
-> Checking Party Site already present in the system
-- To create an account site using cust_account_id and party_site_id
HZ_CUST_ACCOUNT_SITE_V2PUB.create_cust_acct_site
-> Checking Customer site already Present
-- To create an account site use using cust_acct_site_id
HZ_CUST_ACCOUNT_SITE_V2PUB.create_cust_site_use
-> Checking Site Use already exist
-> get the payment term id from ra_terms table
` -> get the sales rep id from ra_salesreps table
-> get the territory_id from ra_territories table
-> Check primary site already exist for the SHIP_TO site
-> Create Profile amounts only if site is BILL_TO
-> get the customer account id to create relationship
-> Get the cust account profile id to create customer profile amounts
-> create customer profile amounts
HZ_CUSTOMER_PROFILE_V2PUB.create_cust_profile_amt
-- Creation of Contact Points
-- 1. Create Person
-- 2. Create relation contact-org between the person and org
-- 3. Create a contact point at customer level/Address level
-- (Here the contact point is created at customer level and
-- PHONE, EMAIL has been added to the contact point)
HZ_PARTY_V2PUB.create_person
-- Create a relation cont-org to the contact and the customer
HZ_PARTY_CONTACT_V2PUB.create_org_contact
-- Create a contact point at customer level using the create role
HZ_CUST_ACCOUNT_ROLE_V2PUB.create_cust_account_role
-- Create a contact PHONE / EMAIL for the above contact point
HZ_CONTACT_POINT_V2PUB.create_contact_point



VENDOR INTERFACE:
AP_SUPPLIERS_INT
AP_SUPPLIER_SITES_INT
AP_SUP_SITE_CONTACT_INT
--------------------------------------------
PO_VENDORS
PO_VENDOR_SITES_ALL
PO_VENDOR_CONTACTS

VENDOR AND SITE LEVELS
--Validation for SHIP TO and BILL TO LOCATION ID
-- Validation for SHIP and BILL TO for vendors
-- Validation for TERM_ID for vendors
-- Validating the VAT CODe
-- Validating invoice Currency codes of vendors
-- Validating Payment Currency codes vendors
--Validating the vendor type lookup code
--Validating the Minority group lookup code
--Validating the pay group lookup code
--Validating the FREIGHT_TERMS_LOOKUP_CODE_V
--validating FOB_LOOKUP_CODE_V

CONTACTS LEVEL
--Validation for Vendor
--Validation for Site

TAX RATES INTERFACE:
AR_TAX_INTERFACE
-----------------------------------------
AR_LOCATION_VALUES
AR_LOCATION_RATES


ITEM MASTER INTERFACE:
MTL_SYSTEM_ITEMS_INTERFACE
-------------------------------------
MTL_SYSTEM_ITEMS_B
--validating for NULL Item Description
--validating Template (mtl_item_templates)
--Validating for Item Already Existing in Base Table (mtl_system_items_b)
--validating for Buyer (po_agents_v)
--validating for Planner (mtl_planners)
--validating for Cost Of Sales Account (gl_code_combinations_kfv)
--validating for Sales Account (gl_code_combinations_kfv)


ITEM CATEGORIES INTERFACE:
MTL_ITEM_CATEGORIES_INTERFACE
-----------------------------------------
MTL_ITEM_CATEGORIES
--validating For Item Not Present in Base Table (mtl_system_items_b)
--validating for NULL MANUFACTURER
--validating for NULL PRODUCT_GROUP
--validating for NULL TYPE
--validating for NULL Sub Type
--validating For MANUFACTURER, PRODUCT_GROUP, TYPE, SUB_TYPE Combination in Base Table (mtl_categories_b)

PRICE LIST API:
QP_PRICE_LIST_PUB.PROCESS_PRICE_LIST
-----------------------------------------------
QP_LIST_HEADERS
QP_LIST_LINES
--Validating For Item is Present in Base Table (mtl_system_items_b)
--Deriving Concatenated Category Segment For the Given Inventory Item ID (mtl_categories_b_kfv)
--Validating For Dynamic Formula is Present in Base Table (qp_price_formulas_tl)


STOCK LOCATORS API:
INV_LOC_WMS_PUB.CREATE_LOCATOR
-----------------------------------------------------------
MTL_ITEM_LOCATIONS
--Combination is already Exists (mtl_item_locations_kfv)
--Sub Inventory is not exists (mtl_secondary_inventories)




PURCHASE ORDER INTERFACE:
PO_HEADERS_INTERFACE
PO_LINES_INTERFACE
PO_DISTRIBUTIONS_INTERFACE
------------------------------------------------
PO_HEADERS_ALL
PO_LINES_ALL
PO_LINE_LOCATIONS_ALL
PO_DISTRIBUTIONS_ALL
-- populating Project information from mapping table
-- Project ID population (pa_projects_all)
-- Task ID population (pa_tasks)
-- Get Mapping Values for charge account, accrual account and Varaiance account
-- getting the requestor info (per_all_people_f)
-- Populating New Deliver to location from mapping table
-- Populating New Ship to location from mapping table
-- Populating New Bill to location from mapping table





GOODS RECEIPTS INTERFACE:
RCV_HEADERS_INTERFACE
RCV_TRANSACTIONS_INTERFACE
-----------------------------------------------------------
RCV_SHIPMENT_HEADERS
RCV_SHIPMENT_LINES
RCV_TRANSACTIONS
-- Checking PO is exists are not
-- Receipt is Already in Interface Table (rcv_headers_interface)
-- getting mapped inv org (mtl_parameters)
-- fetching Vendor, Site, Ship to location and Agent_Id from PO (po_headers_all)
-- getting employee/person name (per_all_people_f)
-- Fetching new ship to lotion code part (hr_locations_all)
-- Fetching new deliver to location code part (hr_locations_all)


AR INVOICES INTERFACE:
RA_INTERFACE_LINES_ALL
RA_INTERFACE_SALESCREDITS_ALL
---------------------------------------------------------
RA_CUSTOMER_TRX_ALL
RA_CUSTOMER_TRX_LINES_ALL
RA_CUST_TRX_LINE_GL_DIST_ALL
RA_CUST_TRX_LINE_SALESREPS_ALL
-- Validation for transaction type (RA_CUST_TRX_TYPES)
-- derive_cust_trxtype_id (ra_cust_trx_types)
-- validate_trx_amount is null
-- validate_tax_code (ar_vat_tax)
-- derive_term_id (ra_terms)
-- derive_salesrep_id (ra_salesreps)
-- derive_orig_system_customer_id (hz_cust_accounts)
-- derive_orig_system_address_id (hz_cust_acct_sites, hz_cust_site_uses)



AP INVOICES INTERFACE:
AP_INVOICES_INTERFACE
AP_INVOICE_LINES_INTERFACE
----------------------------------------------------
AP_INVOICES_ALL
AP_INVOICE_DISTRIBUTIONS_ALL
AP_INVOICE_PAYMENTS_ALL
-- duplicate_inv_check (ap_invoices)
-- get_vendor_details (po_vendors, po_vendor_sites)
-- get_term_id (ap_terms_tl)
-- get_ccid (gl_code_combinations)
-- check for invoice number is null
-- check for invoice net amount is null
-- check for invoice date is null


AR RECEIPTS (AUTO LOCK BOX):
AR_INTERIM_CASH_RECEIPTS_ALL
----------------------------------------------------
AR_CASH_RECEIPTS_ALL
-- Batch Name Validation (ar_batches)
-- Currency Code Validation (fnd_currencies)
-- Bill Customer / Address Validation (hz_cust_acct_sites, hz_cust_site_uses, hz_cust_accounts)


FIXED ASSETS
FA_MASS_ADDITIONS
--------------------------
FA_ADDITIONS
-- Validation for Location KFF (fa_locations)
-- Validation for Categories KFF (fa_categories)
-- Validation for Expense Account KFF (gl_code_combinations)



SALES ORDER IMPORT:
OE_HEADERS_IFACE_ALL
OE_LINES_IFACE_ALL
------------------------------------------
OE_ORDER_HEADERS_ALL
OE_ORDER_LINES_ALL
WSH_DELIVERY_DETAILS
Headers:
-- Code FOR SOLD TO ORG ID (hz_cust_accounts)
-- Code For Bill To From Orig System Reference (hz_cust_acct_sites, hz_cust_site_uses)
-- Code For Order Type (oe_order_types_v)
-- Code For Sales Rep (ra_salesreps_all)
-- Code For Payment Term (ra_terms)

Lines:
-- Item not exists in Price list for Item (qp_list_lines_v, mtl_system_items)


CUSTOMER ITEM CROSS REFERENCE INTERFACE:
MTL_CI_INTERFACE
MTL_CI_XREFS_INTERFACE
------------------------------
MTL_CUSTOMER_ITEMS
MTL_CUSTOMER_ITEM_XREFS
--validating for NULL Customer Number
--validating Duplicate Customer Number, Cross Reference Combination In Staging Table
--validating Duplicate Item Number, Customer Number, Cross Reference Combination In Staging Table
--validating for Item (mtl_system_items_b)
--validating for Customer (ra_customers)



BOM INTERFACE:
BOM_BILL_OF_MTLS_INTERFACE
BOM_INVENTORY_COMPS_INTERFACE
--------------------------------------------
BOM_BILL_OF_MATERIALS
BOM_INVENTORY_COMPONENTS
--validating for NULL Assembly Item
--Validating for Assembly Item Is Existing in Base Table (mtl_system_items_b)
--Validating for Component Item Is Existing in Base Table (mtl_system_items_b)


ON HAND QUANTITIES INTERFACE:
MTL_TRANSACTIONS_INTERFACE
---------------------------------------
MTL_ONHAND_QUANTITIES_DETAIL
--validating for NULL Item Number
--validating for NULL SubInventory
--validating For Item Not Present in Base Table (mtl_system_items_b)
--validating For NULL OnHand Quantity
--validating For Zero OnHand Quantity
--Validating For Unit Of Measure (mtl_units_of_measure)
--Validating For SubInventory (mtl_secondary_inventories)
--Validating For Distribution Account (gl_code_combinations_kfv)
--Validating For Locators (mtl_item_locations_kfv)
--Validating For Transaction Type (mtl_transaction_types)



PURCHASE REQUISION INTERFACE:
PO_REQUISITIONS_INTERFACE_ALL
PO_REQ_DIST_INTERFACE_ALL
--------------------------------------------------
PO_REQUISITION_HEADERS_ALL
PO_REQUISITION_LINES_ALL
PO_REQ_DISTRIBUTIONS_ALL







REPORT DEVELOPMENT/CUSTOMIZATION

CREDIT MEMO
Optio Report will be using Oracle reports to capture the information and will print the output with business logo and required format.
1. Pull standard Invoice Print Selected Invoices report
2. Add seven fields in the standard report and save as custom NAE Credit Memo Invoice Print Selected Invoices report.
Fields
1. Warehouse location – Should appear to the right of Amount in the line item section.
2. Customer collector – Should appear to the right of salesperson.
3. Item No. – Should appear to the left of Description.
4. UOM (unit of measure) – Should appear to the right of Description.
5. Sales tax – Should appear below Invoice discount.
6. Amount subject to sales tax – Should appear below sales tax. This amount is the total of Line Item Amounts where tax code is not Exempt.
7. Amount exempt from sales tax – Should appear below Amount subject to sales tax. This amount is the total of Line Item Amounts where tax code is Exempt.
8. Customer Item No. (From Customer Cross Reference table) – Should appear to the right of Item Number. (8/18/05)
9. Invoice Discount – Should appear below tax summary by tax name. (8/18/05)

ORACLE INFORMATION

1. What is Mutating? How will you resolve it?

"Mutating" means "changing". A mutating table is a table that is currently being modified by an update, delete, or insert statement. When a trigger tries to reference a table that is in state of flux (being changed), it is considered "mutating" and raises an error since Oracle should not return data that has not yet reached its final state.

Avoiding the mutating table error is fairly easy. We must defer processing against the mutating or constrainng table until an AFTER trigger. We will consider two cases:

• Hitting the ORA-4091 in an INSERT trigger or an UPDATE trigger where you only need access to the :new values
• Hitting the ORA-4091 in a DELETE trigger or an UPDATE trigger where you need to access the :old values

2. What is PL/SQL table and its syntax? What is Index by Binary Integer?

An associative array (or INDEX-BY table) that can be indexed by NUMBER or VARCHAR2. Elements are retrieved using number or string subscript values. Unlike with data tables, PL/SQL tables are stored in memory. PL/SQL Tables are sparse and elements are unordered.

First I can declare a type as a collection type as follows:-

            create or replace type jpl_row as object(

                        id                      number, 

                        description          varchar2(40)

            );

            /

            create or replace type jpl_array as table of jpl_row;

            /

So I have a type which is an array of objects. I can now populate a variable of this type with code of the following form:

            declare

                        my_table            jpl_array:= jpl_array();

            begin

                        my_table := jpl_array(

                                     jpl_row(3,'Desc 3'),

                                     jpl_row(1,'Desc 1'),

                                     jpl_row(2,'Desc 2')

                        );          

            end;

            /

3. What are the Mandatory Parameters in PL/SQL Procedure in Apps. What is the use of it?

Mandatory Parameters are “Errorbuf” and “Retcode”.

Errorbuf for Generating the error message of the concurrent program.

Retcode for Generating the status of the concurrent program.

0 – Success 1 – Warning 2 – Error

4. How do you develop new form in Apps?

1. Open Template.fmb and Appstand.fmb

2. Remove the Default datablock, Canvas and Window

3. Create New Window and Canvas

4. Set Window’s Primary Canvas as New Canvas

5. Set Canvas Window Property as New Window

6. Create New Datablock

7. Modify the code in PRE-FORM (change the template.fmb file name in header) and WHEN-NEW-FORM-INSTANCE triggers (change the as New Window)

8. Apply the “SUBCLASS” Property for all the objects Module, Window, Canvas and all the data block objects

5. What are all triggers fire when we Commit, Query and Update a record?

Commit - ON SAVE

Query -

Update -

6. What are the statuses of record level in forms?

Forms statuses

1. from QUERY to CHANGED

2. from NEW to INSERT

7. What are all PLLs we attach in a form and what is APPDAYPK library?

1. APPCORE.pll

2. APPCORE2.pll

3. APPDAYPK.pll

4. APPFLDR.pll

5. FNDSQF.pll

6. GLOBAL.pll

8. How do you display message in forms?

Two Types:

First Method:

1. Difine Message in Application
2. Set Message (FND_MESSAGE.SET_MESSAGE)
3. Show Message (FND_MESSAGE.SHOW)

Second Method:

1. Display Message Direct form the form

FND_MESSAGE.SET_STRING(‘Message’)

FND_MESSAGE.SHOW

9. When we select a query what exceptions we raise?

NO-DATA-FOUND, TOO-MANY-ROWS

10. How do you pass data from one form to another form?

Through Parameters we will pass data from one form to another form

11. What is the difference between Open_Form and Call_Form?

OPEN FORM:

To programmatically open another form, execute the OPEN_FORM built-in procedure:

OPEN_FORM('stocks');

By default, Form Builder immediately activates the opened form and sets focus in the form's first navigable item. To explicitly specify this default behavior, include the optional ACTIVATE parameter:

OPEN_FORM('stocks', activate);

When you open a form with ACTIVATE specified, Form Builder ignores (and never executes) any trigger statements that follow the call to OPEN_FORM.

If you do not want Form Builder to place focus in the opened form, include the NO_ACTIVATE parameter:

OPEN_FORM('stocks', no_activate);

When you open a form with NO_ACTIVATE specified, Form Builder executes any trigger statements that follow the call to OPEN_FORM after the opened form has been loaded into memory and its initial start-up triggers (if any) have been fired.

CALL FORM:

Runs an indicated form while keeping the parent form active. Form Builder runs the called form with the same Runform preferences as the parent form. When the called form is exited Form Builder processing resumes in the calling form at the point from which you initiated the call to CALL_FORM.

Syntax

PROCEDURE CALL_FORM

(formmodule_name VARCHAR2,

display NUMBER,

switch_menu NUMBER,

query_mode NUMBER,

data_mode NUMBER,

paramlist_name VARCHAR2);

12. What is the difference between Database block and Control block?

Database Block represents the fields map to database.

Control Block represents the fields like Buttons etc.

13. How do you setup Set of Books in GL?

1. Creating the Value Sets for the Segments

2. Creating the Structure for KFF (Accounting Flexfiled)

3. Entering Values for Value Sets

4. Defining Period Type

5. Define Accounting Calendar

6. Define Currency

7. Define SOB using (Chart of Accounts, Accounting Calendar and Currency)

14. After giving update statement how do you know that how many records are updated?

SQL%ROWCOUNT

15. What is Multi-Org and its structure?

Business Unit ->

Legal Entity ->

SOB ->

Item Master Organization ->

Operating Unit->

Inventory Organizations ->

Sub Inventory ->

Locator ->

Row, Rack, Bin etc.

16. What are user-exits and where do we use it in reports?

SRWINIT

SRWEXIT

FORMAT_CURRENCY

17. What is mandatory parameter in reports? Do we need to register this parameter in Apps?

P_CONC_REQUEST_ID, Registration is not required in Apps

18. How do you pass parameters in Apps?

In the concurrent program we need to register the parameters.

19. How do you display message in Reports and where it will display?

SRW.MESSAGE(Number, ‘Message’)

The message will display in Log file

Oracle Order Management (OM)

The process flow for Internal Orders

Internal orders normally start with creation of requisitions in Oracle Purchasing (which is created as Internal Sales Orders) .

Once the requisitions created from the MRP and Inventory modules, the Requisition Import program must be run in order to move records from the requisition interface tables to the historical

PO_REQUISITION_HEADERS_ALL,

PO_REQUISITION_LINES_ALL

and PO_REQ_DISTRIBUTIONS_ALL.

Now next is to create internal requisitions from Purchasing module.When each requisition is approved, data will be inserted into the MTL_SUPPLY table. When the items on the requisition are stocked in inventory, the supply data can be viewed from the inventory form called Item Supply/Demand.

Once the Internal Requisition is approved, a user should run Create Internal Sales Orders (from a Purchasing responsibility) to load the internal sales orders interface tables called in Order Entry.

After the Creation of Internal Sales Orders has completed, a Import Orders concurrent program need to run from an Order Management.

at this stage, Oracle order Workflow will process the internal sales order using the workflow definition listed for the Transaction Type definition in Order Management. When the workflow completes the Shipping Network is checked to see if the Transfer Type between the source and destination organization is In transit or Direct.

You can use Oracle Order Entry/Shipping to define order cycles, approvals and holds.
Internal Requisitions use the Account Generator, which automatically builds account distributions. You can specify only one accounting distribution per inventory sourced line.

This internal requisition process provides the features needed to define your inter- organization shipping network. For transfers between two organizations, you can specify whether to use in transit or direct shipments. You can also require internal requisitions for transfers between specific organizations.





The Data Flow for Internal orders

Understanding data flow for “Standard Order”

August 5th, 2007 by Anand Print-Friendly Version Email This Post
Last week, got a mail from one of reader who requested for providing data flow of standard orders and Return Orders. So,here are the information for data flow. Normally standard sales order can be split into nine sub steps , which jointly carried out by some module like INV,OM, Pricing, Shipping and AR. Lets take each sub steps with data flow conditions. These are based out of the flow which is available in 11.5.10.2.

1. Order Entry

This is first stage when Order in enter in system.When the order is entered it basically create a record in order headers and Order Lines table.
· oe_order_headers_all (Here the flow_status_code as entered)
· oe_order_lines_all (flow_status_code as entered) ( order number is generated)

2.Order Booking

This is next stage , when Order which is entered in step 1 is booked and Flow status changed from Entered to Booked.At this stage , these table get affected.
· oe_order_headers_all (flow_status_code as booked ,booked_flag updated)
· oe_order_lines_all (flow_status_code as awaiting shipping, booked_flag updated)
· wsh_new_deliveries (status_code OP open)
· wsh_delivery_details (released_status ‘R’ ready to release)
Same time, Demand interface program runs in background And insert into inventory tables mtl_demand

3. Reservation

This step is required for doing reservations SCHEDULE ORDER PROGRAM runs in the background and quantities are reserved.Once this program get successfully get completed , the mtl_reservations table get updated.

4. Pick Release

Ideally pick release is the process which is defined in which the items on the sales order are taken out from inventory.
Normally pick release SRS program runs in background . Once the program get completed these are the table get affected:
· oe_order_lines_all (flow_status_code ‘PICKED’ )
· wsh_delivery_details (released_status ‘S’ ‘submitted for release’ )
· mtl_txn_request_headers
· mtl_txn_request_lines(move order tables.Here request is generated to move item from saleble to staging sub inventory)
· Mtl_material_transactions_temp (link to above tables through move_order_header_id/line_id

5.Pick Confirm

Items are transferred from saleble to staging Subinventory.
mtl_material_transactions
mtl_transaction_accounts
wsh_delivery_details (released_status ‘Y’‘Released’ )
wsh_delivery_assignments

6.Ship Confirm

Here ship confirm interface program runs in background . Data removed from wsh_new_deliveries
· oe_order_lines_all (flow_status_code ‘shipped’)
· wsh_delivery_details (released_status ‘C’ ‘Shipped’)
· mtl_transaction_interface
· mtl_material_transactions(linked through Transaction source header id)
· mtl_transaction_accounts
· Data deleted from mtl_demand,mtl_reservations
· Item deducted from mtl_onhand_quantities

7.Enter Invoice

This is also called Receivables interface, that mean information moved to accounting area for invoicing details.
· Invoicing workflow activity transfers shipped item information to Oracle Receivables.
· ra_interface_lines_all (interface table into which the data is transferred from order management)T
· Then Autoinvoice program imports data from this
· Table which get affected into this stage are recievables base table.
o ra_customer_trx_all (cust_trx_id is primary key to link it to trx_lines table and trx_number is the invoice number)
o ra_customer_trx_lines_all (line_attribute_1 and line_attribute_6 are linked to header_id (or order number) and line_id of the orders)

8.Complete Line

In this stage order line leval table get updated with Flow status and open flag.
· oe_order_lines_all (flow_status_code ‘shipped’, open_flag “N”)

9.Close Order

This is last step of Order Processing . In this stage only oe_order_lines_all table get updated.
These are the table get affected in this step.
· oe_order_lines_all (flow_status_code ‘closed’,open_flag “N”)
These are the typically data flow of a order to cash model for a standard order
Understand “Drop Shipment” in Order Management?
Order Management allows you to enter drop-ship sales orders as well as standard sales orders.
It means you can receive orders for items that you do not stock or for which you lack sufficient inventory, and have a supplier provide the items directly to your customer.

The best can be described as:
These are the following activity takes place when you have drop shipment
Supplier
Warehouse Item
Ship order
Shipment notification
Order Entry
Enter customer
Enter order
Demand order (optional)
Cancel order (optional)
Close order
Purchasing
Create and send Purchase Order
Enter shipment notification in system
Receivables
Create invoice
Collection of payment
Receipt
hence, drop ship order items ship directly from a supplier to the customer of the order processing company. A purchase requisition, then a purchase order, is generated to notify the supplier of the requirement. After the supplier ships the order, it notifies Purchasing to enter this information in the Purchasing module.
What are the advantages of Drop Shipment Orders?
These are the benefits:
No inventory is required
Reduced order fulfillment processing costs
Reduced flow times
Elimination of losses on non-sellable goods
Elimination of packing and shipping costs
Reduced inventory space requirements
Reduced shipping time to your customer
Allows you to offer a variety of products to your customers




How to understand the dataflow for Drop shipment Orders?
To understand, here are the processes divided in sub process and the underline activity is highlighted here:
Here are the Details as per Mark

1.Order Entry

Here the activity is entering process where oe_order_headers_all (flow_status_code as entered) oe_order_lines_all . The order is booked as DROP SHIP

2. Order Booking

3. The Purchase Release program passes information about eligible drop-ship order lines to Oracle Purchasing.The interface table which gets populated ispo_requisitions_interface_all

4. After Purchase Release has completed successfully, run Requisition Import in Oracle Purchasing to generate purchase requisitions for the processed order lines.

The Requisition Import program reads the table po_requisitions_interface_all validates your data, derives or defaults additional information and writes an error message for every validation that fails into the po_interface_errors table.The validated data is then inserted into the requisition base tables

po_requisition_headers_all,

po_requisition_lines_all,

po_requisition_distributions_all.

Then use autocreate PO fuctionality to create purchase orders and then perform receipts against these purchase orders

7. After the goods are successfully received invoices for vendors are created in accounts payables as in normal purchase orders.

8. Invoices are generated for customers In account receivables.

9. oe_order_lines_all (flow_status_code ’shipped’, open_flag “N”)

10. oe_order_lines_all (flow_status_code ‘closed’, open_flag “N”)

Hope this is great help to understand the flow.