EBS first project learning Summary-shipping Module

EBS organizational structure:

(1) Business Group (BG)

(2) Legal Entity (LE)

(3) Business Entity (OU)

(4) Inventory Organization (INV)

(5) cost center (cost center)

(6) HR Organization

(7) multi-organization Access Control

Ship confirm shipping function module of sale order:

 

When changing the status, remember to modify the status of the WHO field.

 

Required table information:

Oe_order_headers_all order header information table

Oe_order_lines_all

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

 

There is a concept:

For example

Order_number: 101852

There are two order headers.

Header_id: A header_id: B

The concept of line_number is that the two orders belong to the same row as follows:

Header_id: A B

Line_number: 1 line_id: A1 line_id: B1

Line_number: 2 line_id: A2 line_id: B2

Line_number: 3 line_id: A3 line_id: B3

The sales order is a logical relationship.

Important Fields in oe_order_headers_all:

Header_id order header ID

ID of the request_id concurrent request
Org_id: ID of the business entity
Ship_to_org_id the recipient's organization ID
Ship_from_org_id the Organization ID of the sender

Important Field in oe_order_lines_all
Header_id order header ID
ID of the request_id concurrent request
Org_id organization ID
Line_id order line ID
Line_number order line number
Ship_to_org_id the recipient's organization ID
Ship_from_org_id the Organization ID of the sender

Wsh_delivery_details
-- Source_header_id = oe_order_headers_all.header_id
-- Source_line_id = oe_order_lines_all.line_id
Material shipment details table
Delivery_detail_id ID of the ticket
Source_header_id order header ID
Source_line_id: Order line ID
Customer_id customer ID
Inventory_item_id: ID of the item corresponding to the item table
Organazation_id ID of the inventory Organization
Number of requested_quantity requests
Shipped_quantity quantity
Subinventory sub-inventory name
Released_status status of the current item
Org_id: ID of the business entity
ID of the request_id concurrent request
Locator_id goods inventory No.

Lot_number: batch number of the item

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

Delivery_id producer
Delivery_detail_id Material ID



Mtl_serial_numbers
Information table that records the current status of the item serial number
Inventory_item_id Material ID
Serial_number serial number


Mtl_serial_numbers_temp
Table of serial number and bill of materials
Associated by transaction_temp_id





The shipping module can be understood as taking out the materials in the retained warehouse for shipment. The completion of the shipping confirmation indicates the transfer of this property right. There are many delays in delivery. For example, if the quantity of items you want to ship is insufficient to meet the buyer's quantity, you can delay delivery and wait until the quantity meets the same delivery conditions.

The shipping module obtains a pile of material orders after the material picking is completed, and generates a material number for each material order. The material number is used to let the shipping know, the materials to be shipped and the generation of item numbers may vary.

Shipping Module Interface operation:
Log on and find an owner with the responsibility of order management. Go to transaction processing.

You can query the order number based on the order number.

Each item corresponds to a bill of materials.
Detail is the item number.
Item name is the name of the item.
Delivery is the sender of a material.
Line status indicates the current status of the item, and the status is staged/pick confirm.
Next step is the next state of the material.
Order is the order number.

Requested qty is the required quantity
Shipped qty is the quantity to be shipped
Backordered qty indicates the quantity to be postponed

Serial number is a serial number. If the serial number control is enabled for the item, org code is the current inventory organization, and subinventory sub-Inventory
If you want to ship, you must assign the item number,

Select the operation here. The only thing you know is:
Split line branch. When the serial number is started, the branch rule is unknown for the moment, but the serial number is automatically assigned to the split row.
Lauch pick release automatically picks up the database. This operation can be used to pick up the backordered or ready to release. In this case, it will automatically pick up the database for this material order and assign a token.
Picking a database can be understood as distributing the materials in your inventory to the retained database. The materials in the retained database cannot be passive in the future, so that they are all allocated and waiting for shipment. Materials in stock can also be allocated.
Auto-create deliveries

For the Blue Line in the figure, you can ship it at this time and enter the delivery interface,

Click ship confirm to ship.

Here are some instructions,

Shipconfirm rule contains the shipping rules defined by the current system,

Click ship entered quantities, and select the shipping method for the unknown quantity of materials on the right,
For example, if requested qty = 10 shipped qty = 5 backordered qty = 3, the unknown quantity is 2.
If ship is selected, the unknown quantity 2 will be shipped, that is, 7 will be shipped and 3 will be postponed
If Backorder is selected, the unknown quantity 2 is postponed, that is, 5 is postponed to 5
If stage is selected, the unknown quantity is returned to the staged/pick confirm status. This works with the following

If this option is selected, a producer is automatically assigned to the staged/pick confirm status.
If cyclecount is selected, the unknown number of items is returned to the staged/pick confirm state, and the quantity of shipped qty is empty.

Ship all means to ship all materials. The same is true for others.
Note that a trip stop operation must be performed on the shipping ticket to determine whether the shipping is successful.

Code implementation is far more complex than interface implementation. First, we need to introduce several APIs used.

wsh_deliveries_pub.delivery_action(p_api_version_number => 1.0,                                       p_init_msg_list      => fnd_api.g_true,                                       x_return_status      => lv_return_status,                                       x_msg_count          => ln_msg_count,                                       x_msg_data           => lv_msg_data,                                       p_action_code        => 'CONFIRM',                                       p_delivery_id        => 104483,                                        p_delivery_name      => 104483,                                       p_sc_action_flag     => 'C',                                       p_sc_close_trip_flag => 'Y',                                       x_trip_id            => ln_trip_id,                                       x_trip_name          => lv_trip_name);

The input parameters here can be:

P_action_code has many values:

'PLAN','UNPLAN','PACK','CONFIRM','RE-OPEN','IN-TRANSIT','CLOSE', 'ASSIGN-TRIP','UNASSIGN-TRIP','AUTOCREATE-TRIP', 'WT-VOL', 'PICK-RELEASE', 'DELETE'

All I know is,

-- Re-open: make the status reopen
-- Delete: delete a part number.
-- Confirm: The ship confirm operation corresponds to the ship confirm operation, and the operations in actions:

p_sc_action_flag  ： ship confirm option - 'S', 'B', 'T', 'A', 'C'

This is equivalent

S is ship B is backorder T is stag C is cyclecount A is ship all

Other parameters include:

P_ SC _intransit_flag: Check whether set delivery in-transit is selected on the graph, and whether y is n no

P_ SC _close_trip_flag: Check whether the close trip on the graph is checked, and Y is n no

P_ SC _stage_del_flag: Create delivery for staged Quan .. check box, Y is n no

P_ SC _trip_ship_method: varchar2 type input by ship method on the graph. It can be null.

P_ SC _actual_dep_date: indicates the actual departure date on the graph. If it is null, the value is automatically assigned to the current time.

P_ SC _defer_interface_flag: Check whether the defer interface is selected on the graph, and Y is n no

Other APIs will be explained in a single article. If there is something wrong, I hope you can give comments and suggestions. Thank you.

EBS first project learning Summary-shipping Module