Tables sold to Warehouse

Sales Orders must go through four major stages: registration, issuance, database picking, and delivery. Some tables have different characteristics in each stage. The author lists several common tables, other information forms, such as cargo routes and docks, are not involved.

The following are the four main links of a sales order and common tables used in each link:

I. Registration

1. oe_order_headers_all -- order header information table

 

2. oe_order_lines_all
-- Header_id = oe_order_headers_all.header_id
-- Order Line Info table

 

3. mtl_sales_orders
-- Segment1 = oe_order_headers_all.order_number
-- Sales_order_id = mtl_material_transaction.transaction_source_id
-- Information table that records the order number

 

4. wsh_delivery_details
-- Source_header_id = oe_order_headers_all.header_id
-- Source_line_id = oe_order_lines_all.line_id
-- Record the shipping details of the item in the order. This table records the status (released_status) at this stage as R (ready to release: 'R' means "ready to release ")

 

5. wsh_delivery_assignments
-- Delivery_detail_id = wsh_delivery_details.delivery_detail_id
-- Connect the information table of wsh_delivery_details and wsh_new_deliveries.
-- Connect wsh_delivery_details in this phase

Ii. Issuance

1. wsh_delivery_details
-- The status (released_status) of the table is S (released to warehouse:'s 'means "submitted for release ")

 

2. wsh_new_deliveries
-- Source_header_id = oe_order_headers_all.header_id
-- Record the order delivery information table. The status of this stage (status_code) Is OP (delivery is open, has not been shipped)

 

3. wsh_delivery_assignments
-- Delivery_id = wsh_new_delipolices.delivery_id
-- Connect the information table of wsh_delivery_details and wsh_new_deliveries.
-- Connect wsh_new_deliveries in this phase

 

4. wsh_picking_batches
-- Order_header_id = oe_order_headers_all.header_id
-- Records the order issuance information table

 

Iii. Picking Databases

1. wsh_delivery_details
-- The status (released_status) of the table is Y (staged ). If serial number is enabled, records are split by a single serial number.

 

2. mtl_material_transactions
-- Transaction_source_id = mtl_sales_orders.sales_order_id
-- Trx_source_line_id = oe_order_lines_all.line_id
-- Record information about the changes in the storage location of materials in the "sales order picking" phase

 

3. mtl_onhand_quantities
-- Record the existing quantity information table of the item

 

4. mtl_transaction_lot_numbers
-- Transaction_id = mtl_material_transactions.transaction_id
-- Lot_number = mtl_onhand_quantities.lot_number
-- Records the batch information table generated when the storage location of the item changes

 

5. mtl_serial_numbers
-- Last_txn_source_id = mtl_material_transactions.transaction_source_id
-- Information table that records the current status of the item serial number

4. Delivery

1. wsh_delivery_details
-- The record of this table is in this stage (released_status) as C (shipped)

 

2. wsh_new_deliveries
-- The table's records are in this state (status_code) as Cl (delivery has arrived at the destination)

 

3. mtl_material_transactions
-- Record the information about the change in the storage location of materials in the "Distribution of sales orders" phase
-- If the serial number is enabled, records are split by a single serial number.

 

After workflow is completed in the background, the data will be imported into the RA interface table.
Ra_interface_lines_all
Ra_interface_salescredits_all
After the data is imported, run the automatic invoicing command to import the data to the following tables:
Ra_customer_trx
Ra_customer_trx_lines
Ar_payment_schedules

 

(5) Oracle om supports the invoicing process in the following two layers:
1. invoicing at the Order header layer: the whole order data is poured into the result or AR is returned.
2. invoicing at the order line level: this refers to the result of dumping data in the order line or returning ar

 

(6) Automatic invoicing
Navigation: interface-> RUN autoinvoice
Program: autoinvoice master program

Interface table: ra_interface_lines_all
Error table: ra_interface_errors_all
Base tables: ra_batches_all
Ra_customer_trx_all
Ra_customer_trx_lines_all

Oe_order_headers_all.order_number = ra_customer_trx_all.interface_header_attribute1
The following lists the fields used to pass reference in om to Ar through automatic invoicing.

Number name column
1 order number interface_line_attribute1
2 order type interface_line_attribute2
3 Delivery interface_line_attribute3
4 waybill interface_line_attribute4
5 count interface_line_attribute5
6 line ID interface_line_attribute6
7 picking line ID interface_line_attribute7
8 bill of lading interface_line_attribute8
9 customer item part interface_line_attribute9
10 Warehouse interface_line_attribute10
11 price adjustment ID interface_line_attribute11
12 shipment number interface_line_attribute12
13 option number interface_line_attribute13
14 service number interface_line_attribute14

Invoice grouping rules)
Menu: navigation> setup> transactions> autoinvoice> grouping rule
Autoinvoice uses grouping rules to group lines to create one transaction.

 

 

 

1 interface table:
A) Oe_headers_iface_all : This table is a multi-organizational table used to insert a sales order header into an open interface.
This table stores the order header information from other subsystems that need to import the OM module,
Fields/conditions required for importing the table:
Order_source_id: Order source ID (optional)
Orig_sys_document_ref: original system document reference is required.
Order_source: Order source (optional)
Operation_code: operation code is required
Order_type_id: Order Type ID (optional)
Order_type: Order type is optional.
Return_reason_code: Return Reason code is only used for order return
Salesrep_id: salesrep ID
Price_list_id: Price List ID is used for a booking order.
Price_list: Price List is used for booking orders.
Example:
Insert into oe_headers_iface_all (
Order_source_id
, Orig_sys_document_ref
, Org_id
, Order_type_id
, Price_list_id
, Transactional_curr_code
, Sold_to_org_id
, Ship_to_org_id
, Created_by
, Creation_date
, Last_updated_by
, Last_update_date
, Operation_code
) Select ooha. order_source_id
, Ooha. orig_sys_document_ref
, Ooha.org _ id
, Ooha. order_type_id
, Ooha. price_list_id
, Ooha. transactional_curr_code
, Ooha. sold_to_org_id
, Ooha. ship_to_org_id
, Ooha. created_by
, Ooha. creation_date
, Fnd_global.user_id
, Sysdate
, P_operation_code
From oe_order_headers_all ooha
Where order_number = p_order_number;

 

B)Oe_lines_iface_all This table is a multi-organizational table used to insert a sales order row into an open interface.
This table stores the order line information from other subsystems that need to import the OM module,
Fields/conditions required for importing the table:
Order_source_id: Order source ID is required
Orig_sys_document_ref: original system document reference is required.
Orig_sys_line_ref: original system line reference is required.
Orig_sys_shipment_ref: original system Shipment reference is required
Inventory_item: inventory item is required
Inventory_item_id: inventory item ID (optional)
Top_model_line_ref: Top Model line reference (optional)
Link_to_line_ref: Link to line reference (optional)
Request_date: Required for request date
Delivery_lead_time: delivery lead time is required
Delivery_id: the delivery ID is required.
Ordered_quantity: ordered quantity is required.
Order_quantity_uom: Order Quantity UOM required
Shipping_quantity: quantity which has been shipped by shipping in shipping UOM. Optional
Shipping_quantity_uom: the UOM for shipping quantity optional
Shipped_quantity: shipped quantity optional
Cancelled_quantity
Fulfilled_quantity: The fulfilled quantity for the line is optional
Pricing_quantity: pricing quantity optional
Pricing_quantity_uom: pricing quantity UOM optional
Example:
Insert into oe_lines_iface_all
(Order_source_id,
Orig_sys_document_ref,
Orig_sys_line_ref,
Orig_sys_shipment_ref,
Org_id,
Line_number
, Line_type_id,
Item_type_code,
Inventory_item_id,
Source_type_code,
Price_list_id,
Sold_to_org_id,
Sold_from_org_id,
Ship_to_org_id
, Ship_from_org_id,
Operation_code,
Ordered_quantity,
Order_quantity_uom,
Created_by, creation_date, last_updated_by, last_update_date, last_update_login)
Values
(L_line_tbl (j). order_source_id,
Rochelle line_tbl (j). orig_sys_document_ref,
Rochelle line_tbl (j). orig_sys_line_ref,
Rochelle line_tbl (j). orig_sys_shipment_ref
, L_line_tbl (j). org_id,
Rochelle line_tbl (j). line_number,
Rochelle line_tbl (j). line_type_id,
Rochelle line_tbl (j). item_type_code,
P_new_item,
Rochelle line_tbl (j). source_type_code,
Rochelle line_tbl (j). price_list_id,
Rochelle line_tbl (j). sold_to_org_id,
Rochelle line_tbl (j). sold_from_org_id,
Rochelle line_tbl (j). ship_to_org_id,
Rochelle line_tbl (j). ship_from_org_id,
P_operation_code,
Rochelle line_tbl (j). ordered_quantity,
Rochelle line_tbl (j). order_quantity_uom,
Rochelle line_tbl (j). created_by, Rochelle line_tbl (j). creation_date, fnd_global.user_id, sysdate, fnd_global.user_id
);

 

C)Oe_price_adjs_iface_all
D) API of the import interface:Oe_order_pub
Common process:
(1) oe_order_pub.process_order: Provides operations for creating, modifying, and deleting order entities. This method also applies to other operations on orders through record sets or external requests,
(2) oe_order_pub.get_order: returns all records of a single order object.
(3) oe_order_pub.lock_order: Lock the order object.
You can use get_order to obtain the record. You can call lock_order to lock the record.

 

E) record error information
Oe_processing_msgs
Oe_processing_msgs_tl
F) The sales order must go through four major stages: registration, issuance, picking, and delivery. Some tables have different characteristics in each stage,
There are several commonly used tables. If there are other information tables, such as cargo routes and parking stops, we will not go into detail.