Reusing Shipped LPNs in Oracle WMS

Yes LPNs can be reused in either same inventory organization or a different organization.
This can be achieved using container public API

Provided the current context of the LPN is issued out of store and there is no pending transaction on that LPN and LPN name is a valid LPN name.

Prior to R12.1.1, oracle was not allowing to re use the LPN once shipped out.

But in certain business case this is necessary to reuse.
Like logistic business they have they container returned to dock or warehouse after delivering to customer and which can be resused, so why not the LPN tagged to that.

As of now there is no functionality in oracle forms using which this can be achieved.
In those cases, this can be achieved by using the below API

apps.wms_container_pub.reuse_lpns
It will Validate the LPN on below points

• It should be issued out of stores. 
• It should have a valid LPN name. 
• There should not be any pending transactions for this LPN.

It derives the contents from WMS_LPN_CONTENTS & WMS_LICENSE_PLATE_NUMBERS. This will update the WMS_LPN_HISTORIES table as well

• It marks the LPN as ‘Defined but not used’ with no Subinventory/Locator. 
• LPN is ready for reuse in the organization provided. 

–SAMPLE API CODE 

prompt Enter License Plate Number which has to be reused accept lpn;

Declare

l_Return_Status Varchar2(1);

l_Msg_Count Number;

l_Msg_Data Varchar2(100);

l_Lpn_Id Number;

l_Clear_Attributes Varchar2(10) := ‘Y’;

l_Unpack_Inner_Lpns Varchar2(10) := ‘N’;

l_Clear_Containter_Item_Id Varchar2(10) := ‘N’;

l_Organization_Id Number := Null;

— l_License_Plate_Number Varchar2(100) := ‘JR1’;

l_License_Plate_Number VARCHAR2(100):= ‘&lpn’;

Begin

Select Lpn_Id

Into l_Lpn_Id

From Wms_License_Plate_Numbers

Where License_Plate_Number = l_License_Plate_Number;

Wms_Container_Pub.Reuse_Lpns

(

p_Api_Version => 1,

x_Return_Status => l_Return_Status,

x_Msg_Count => l_Msg_Count,

x_Msg_Data => l_Msg_Data,

p_Lpn_Id => l_Lpn_Id,

p_Clear_Attributes => l_Clear_Attributes,

p_New_Org_Id => l_Organization_Id,

p_Unpack_Inner_Lpns => l_Unpack_Inner_Lpns,

p_Clear_Containter_Item_Id => l_Clear_Containter_Item_Id

);

Commit;

Exception

When Others Then

Dbms_Output.Put_Line(‘SQLEERM ‘ || Sqlerrm);

End;

Multi Org Access Control Setup: Business Group to Inventory Organization

Below is the MO Hierarchy

Business Group àLegal Entity àOperating Unit àInventory Organization

Business Group Setup

Below are the pre-setups required for Business Group

Define a Location

Navigate to Human Recourses Responsibility -> Work Structure -> Location

Enter Address Style, Address details, Timezone in Address Details Tab
In Shipping Details Tab, select all required business purposes for this location

Define the Business Group

Navigate to Human Recourses Responsibility -> Work Structure -> Organization -> Description

Select New

Enter the Business Group Name
Enter the location you have created
Select Internal in Internal or External field
Then Click Save
Enter Business Group in Name under Organization Classification Check Enabled and the Save

Click on Others Button, select *Business Group Info option from the LOV

Click on the Business Group Info. Field, it will open the DFF

Fill All the details

Click Ok and then Save

Setup Legal Entity

Need to create below 2 Legal Entities
India LE
Singapore LE Switch responsibility to General Ledger, Visions Operations (USA)

Navigate to Setup à  Financials à Accounting Setup Manager à Accounting Setups

Select Legal Entity Tab, the click on create Legal Entity

Enter the details

Select on Create New Address radio button for creating new address, else select an address from the existing list
Fill the details in General Information

Then Click on Apply.

Again go to Legal Entity tab and click on Create Legal Entity to create Singapore LE

Create or Select from the list

Click on Apply

Confirmation message displays

Create Ledger

We have to create 2 ledgers here

Currency
Calendar
Chart of Account

Accounting Convention In multi org structure we will follow the same calendar, currency and chart of accounts for the companies. In the above scenario as we have the companies in 2 different countries we will have 2 different ledgers.

• India Ledger
• Sinapore Ledger

Switch responsibility to General Ledger, Visions Operations (USA)

Navigate to Setup à  Financials à Accounting Setup Manager à Accounting Setups

Click on Create Accounting Setup

We have already created the legal entity, so we can move to next

Enter the Primary Ledger details

You can create your own Chart of Account, Calendar, Currency and Subledger Accounting Method or you can use from the system.

Click Next

Click Finish

Create the Singapore Ledger Similarly

Create and Assign Operating Unit and Legal Entity

Switch responsibility to General Ledger, Visions Operations (USA)

Navigate to Setup à  Financials à Accounting Setup Manager à Accounting Setups

Enter the Ledger Name and Click Go 

Click Update Accounting Option button

Click Add Legal Entity 

Search for the India Legal Entity

Click on Apply button
Legal entity now attached
Click on the Update action for Ledger options and proceed next till finish.

After finish, operating unit option will be enabled

Adding Operating Unit to the Ledger

Click on the update button on the operating unit

Click on Add Operating Unit

Click Apply

Now Search the OU created

Click on Complete 

Now complete all other ledger option

Click Complete

Similarly complete the ledger setup and Operating and LE assignment for both the operating Units 

Create Inventory Organization

Read more on Oracle Inventory Organization

Navigate to Human Recourses Responsibility -> Work Structure -> Organization -> Description

Click on Others and select Accounting information

Click Ok, then Yes for the Save pop up.

Now Click others again and select Inventory Information

Enter details in the Inventory Tab

Enter the details in the costing tab

Enter the details in Revision, LOT, Serial And LPN tab

Enter the details in ATP, Pick, Item Sourcing tab

Enter the details in the Inter-org informations tab

Enter the details in the Other Accounts tab

Click on SAVE

Click OK

Create the other Inventory orgs for Kolkata and Singapore similary

Run the required programs to get access to all created OUs and Multi org structure

Run the Replicate Seed Data conc program to get access to the Operating Units created

Submit this program for all the Operating Units created

*Note: If the program not exists in Human Resource responsibility, try to look in System Administrator

Run the Multi-Org Setup Validation Report

Multi Org Access Control

This special feature of R12 allows users to submit or access data of multi operating usint using one responsibility.
Pre-requisites for this is to create a security profile and attach the required operating units under that
Navigate to Human resource responsibility

Security à Profile

Define the profile option and attach both the operating units

There are 4 ways you can control the security profile

• View All organizations (no security) 
• Secure organizations by organization hierarchy and/or organization list 
• Secure organization by single operating unit 
• Secure organizations by operating units and inventory organizations

Submit the Security List Maintenance concurrent program to activate the created security profile

Now create a new responsibility and user, assign the Multi org profile option to the responsibility and the responsibility to the user

Create Responsibility

Navigate to the System Administrator

Security à Responsibility à Define

Create User

Navigate to the System Administrator

Security à User à Define

Assign the responsibility 

Set the profile

Navigate to the System Administrator

Profile à System

You can use below profile options as as well for multi org access control

MO: Default Operating Unit: Even though you have the flexibility to choose many orgs or operating unit from the responsibility, if you want to default any specific operating unit in the responsibility, you can use this profile option.
This can be set at responsibility and user level. This comes into picture when you are using Multi Org Access Control (MOAC).

But if you are not using MOAC and want to tag the responsibility or user to an Operating Unit, you can use the profile option MO: Operating Unit.

Note:

If you are using Order Management responsibility to test this and using Sales Order Form, then Operating Unit field is not visible.

To show Operating Unit in Sales Order form, you can use folder tool to move the existing field and and show the Operating Unit filed.

You can define your own folder.

Also you can default folders to any responsibility.

Read more on how to change the folder details in a form

Download the doc in PDF

Oracle WMS: LPN Context

LPN Context

LPN Context is nothing but the state/status of the LPN. Oracle WMS provided many states for an LPN. As per the current state/context, the usage of the LPN will change.

These context can be used to customize specialized picking and put away rules. Also context will help in querying tasks in warehouse control board.

Below are the different LPN context and their state definition

These context have a numeric value in the back end table.

Definition

Resides in Inventory:

Indicates that material associated with this LPN has been costed and accounted for in inventory. A LPN with this context may not be used when receiving material against a standard or inspection routed receipt, but may be used during a direct delivery routed receipt. Outbound transactions can be performed on LPNs with this context.

Resides in WIP:

Indicates that material associated with this LPN is currently being transacted in WIP (Work in Process). Therefore, the associated material is not yet in inventory and has not been costed to inventory.

Resides in Receiving:

Indicates that material associated with this LPN have been received using a standard routing or inspection routing receipt and have not been delivered/put away yet. Therefore, the associated material is not yet in inventory and has not been costed to inventory.

Issued out of Stores:

These LPNs are no longer tracked by the system, and hence, no longer associated with a locator within the warehouse. The system does however retain history information pertaining to transactions this LPN was involved in and material it was associated with prior to leaving the warehouse. LPNs shipped out of inventory receive this context and may not be re-received.

Pre-generated:

When LPNs are pre-generated by Oracle WMS and have not been used yet, they are not associated with any physical material. They can be printed and used to identify material during any stage of the material management process such as inbound, replenishment, outbound, and so on. Essentially, this context refers to LPNs that are ready to be used.

Resides in In-Transit:

A LPN with this context is an indication that it is currently moving from one location to another. Possible uses for this are when a LPN is moved from one organization to the next, for example while the LPN is on a truck. The LPN is in an intermediary state, but resides within the entire system. This context is used only for inter-org transit or internal sales orders where an indirect shipping network is defined between the organizations.

Resides in Vendor Site:

When a vendor sends an Advanced Shipment Notice (ASN) to Oracle WMS, the system internally generates LPNs and associates them with material information on the ASN. These LPNs receive this context. Material associated with LPNs of this context are not on-hand or costed until it is actually received.

Packing Context:

This context is temporary and used internally by the software as an intermediary. It should not be used or referenced anywhere including the setup of picking or put away rules.

Loaded for Shipments:

An LPN loaded for shipment has just been loaded onto a carrier ready to leave the warehouse. Once the entire carrier leaves the dock, the LPN obtains a context of 6 Resides in Intransit or 4 Issued out of Stores.

Prepack of WIP:

LPNs that reside in WIP and are associated with material that is pre-packed by WIP receive this context. This context adds an extra level of granularity to an LPN’s usage within WIP. This is used when the system has associated the LPN with material and printed the labels, but the material has not yet been physically packed.

Picked:

LPNs picked during the picking process receive this context. They are intransit within the warehouse.

Oracle Warehouse Management System: License Plate Number (LPN)

Oracle WMS: LPN

LPN is License Plate Number.

This is nothing but an identification of a certain object which holds Item/Items.
So for understanding, you can say LPN is an identification of a box in which you have kept the item/s whether in your warehouse locations or you have consolidated for shipping or identified for picking or receiving. At any point of time, item/s/group of items can be tracked using one single identification that is called LPN.

•  This can be a physical container or a logical grouping.
•  A single LPN can contain one or many qty of the same or different items
• This is used to store information of items such as LOT, Revision, Serial, Organization, subinventory, locator, etc.
• Contents of an LPN can be tracked during inventory stocking, shipping, receiving, in-transit
• Receiving, Shipping, Picking, Packing of material can be done using LPN
• Onhands can be tracked using LPN
• Multiple items and qty can be transacted using LPN
• Contents can be packed, unpacked, split or updated in LPN
• Labels can be printed based on LPN for the contents inside an LPN
• LPNs can be reused if that is empty or not assigned to any content

Nesting LPN

Oracle WMS allows to use LPN in nested also.

For example, you have made a Combo deal sale for Christmas.

If customer buys 2 laptop units, they will get one USB hub free.

And for better and faster shipment, you have already packed the units and kept for ready to ship.

So now the nesting hierarchy is like this