LPN Label Printing

 LPN Label Printing

For LPN Label Printing, follow the below steps:

1. WSH Manager > define label format 

2. Define Custom SQL Fields > Define label field variable (btn) > assign label type to business flow. [Table: WMS_LABEL_REQUESTS].

3. Assign Label Types to Business Flows [Warehouse Manager: Setup > Warehouse Configuration > Printing > Assign Label Types to Business Flows]

4. Custom Label Fields :

a. You can create custom label fields and associate them with label formats. This enables you to have additional control over the values that are listed on a label. You can write a custom SQL statement to create the custom label field. The following restrictions apply to custom SQL statements:

i. You must include the WMS_LABEL_REQUESTS table in the from clause of your SQL statement and use the alias WLR to refer to this table. The system automatically appends the condition "wlr.label_request_id = :id" to your SQL statement. See subsequent examples for the proper inclusion of the WMS_LABEL_REQUESTS table.

ii. The SQL returns one value.

iii. The system cannot verify the SQL statement will execute properly because it does not know the transaction values until run-time when the SQL is executed. The system does, however, check the SQL for the following conditions:

1. The custom label field definition contains only a SELECT statement. The system does not accept any other type of SQL.

2. The SELECT statement syntax is correct.

3. The custom label field name is unique within the label types.

iv. If a violation occurs during SQL execution, then the system records the violation in the WMS_LABEL_REQUESTS_HIST table.

1. Example: The following is an example of a correct SQL statement for the field name Supplier Type for the LPN Contents label type: select ap.vendor_type_lookup_code from ap_suppliers ap, wms_label_requests wlr where wlr.supplier_id = ap.vendor_id

2. Example : The following is an example of a correct SQL statement for the field name PRO_NUM for the Shipping label type:select wc.attribute1 from wsh_carriers wc, wsh_delivery_details wdd wms_label_requests wlr where wc.carrier_id = wdd.carrier_id and wlr.delivery_detail_id = wdd.delivery_detail_id

b. Assigning Label Types to Business Flows: Multiple Label Types can be assigned to a single Business Flow if it is necessary for multiple labels to be printed. However, multiple label types print only if there are multiple assignments for the business flow at the same level. For instance, if both the LPN and LPN Content Label Types are assigned to print during a Miscellaneous Receipt for a particular user, both label types print. However, if the LPN Label Type is assigned to a responsibility and the LPN Content Label Type is assigned to a user, even if the user logs in under that responsibility, only the LPN Content Label Type prints. The following table lists the available business flow label type assignments.

MWA Personalization in Oracle Apps R12 WMS

 MWA Personalization in Oracle Apps R12 WMS

This personalization can be done on 3 levels: Function, Organization, and Responsibility.

Below profile options need to be steps: 

• MWA: Enable Personalization: This will decide whether you want to enable personalization or not. 
• MWA: Cache Personalized Metadata: This controls whether or not you need to bounce the MWA server.

1. Navigate to the Warehouse Manager Responsibility and select the MWA Personalization framework option under the Setup sub-menu. 

2. Select a page and click on personalize, this will show all the fields in that page and their function level values with an edit option in the light of every field. 

3. After clicking the edit button, make the required changes, and click apply. [Prompt, Copy From, Default Value, Rendered, Read Only, Required]

4. Navigate to the mobile page and review your personalization for the page. Note: If the profile option “MWA: Cache Personalized Metadata” is set to “Yes” then, the personalization made will come into effect only after bouncing the mobile server

Buyer Setup in Oracle Apps R12

 Buyer Setup in Oracle Apps R12

1. In HRMS ‘People > Enter and maintain’, Create New Employee whose Last name must be the same as User name which we are logged in. Go to Assignment; Enter Org, Position, and Job. Save the record.

2. In Sysadmin ‘Security > User > Define’, Query for the user & enter the ‘person’ field with employee name created in HRMS. Save the record.

3. In PO’ Setup >Personal > Buyers ‘, Create a new buyer for our user. Now we can create a PO

4. In PO’ Setup >Approvals > Approval groups ’, Create an approval group.

5. Go to ‘Setup >Approvals > Approval Assignments’, Select the position (as given in HRMS) and assign the approval group for different document types. Now we can approve Documents

License Plate Number (LPN) in Oracle Warehouse Management (WMS)

 License Plate Number (LPN)

LPN is the backbone of Oracle WMS. Most of the entries in the HHT device are based on LPN scanning. You can define Sub-inventory also LPN controlled or non-LPN control after implementing Oracle WMS. You can find Item in material workbench packed in LPN or Loose Material(not packed in LPN).

Below are the some sql query which helps you debug the LPN related issues:

-- Lookup related to LPN

select * from apps.fnd_lookup_types_VL Where lookup_type = 'WMS_LPN_CONTEXT';

select * from apps.fnd_lookup_values  Where lookup_type = 'WMS_LPN_CONTEXT' and LANGUAGE = 'US';

LOOKUP_CODE     MEANING

7                   At Vendor

5                   Defined but not used

1                   In Inventory

3                   In Receiving

2                   In WIP

6                   Intransit

4                   Issued out of Stores

12                   Loaded in Staging

9                   Loaded to Dock

8                   Packing context

11                   Picked

10                   Prepack for WIP

-- To find current LPN details

 select a.LPN_ID, a.LICENSE_PLATE_NUMBER,a.LPN_CONTEXT, b.MEANING

from apps.wms_license_plate_numbers a, apps.fnd_lookup_values b

where LICENSE_PLATE_NUMBER = '&LPN_NUMBER'

and b.lookup_type = 'WMS_LPN_CONTEXT'

and a.LPN_CONTEXT = b.LOOKUP_CODE

and b.LANGUAGE = 'US';

-- LPN related main table

select * from apps.wms_license_plate_numbers where LICENSE_PLATE_NUMBER = '&LPN_NUMBER';

select * from apps.wms_lpn_contents where PARENT_LPN_ID = &LPN_ID;

select * from apps.wms_lpn_histories where PARENT_LPN_ID = LPN_ID;

Behind the Oracle WMS Rule

Whenever you create and save a rule in Oracle WMS; the system creates a package in the background. The name will be WMS_RULE_ruleid. To find the rule ID you can use below SQL:

Select RULE_ID, NAME From apps.WMS_RULES_TL Where NAME like '%Seeded Default%' and LANGUAGE = 'US';

Select * From ALL_OBJECTS Where OBJECT_TYPE ='PACKAGE' and OBJECT_NAME = 'WMS_RULE_10';

Select text From all_source Where name = 'WMS_RULE_10'

and type = 'PACKAGE BODY'

order by line;

PACKAGE WMS_RULE_XXX have considered 3 procedure:

1. PROCEDURE open_curs : Open the record based on SQL inside it
2. PROCEDURE fetch_one_row : It fetches records multiple time and performs the action
3. PROCEDURE close_curs: For a normal rule, it used to close the cursor. But in case of customization, it holds and performs an action.

Once you run Generate All Rules concurrent program it will compile the procedure and your changes are activated.

Steps to copy and paste Oracle Apps form data

Steps to copy and paste Oracle Apps form data

Open the form and find the data which you want to copy

1. press ctrl + down (it copy form-data)
2. open a new entry screen 
3. to go next line press tab 
4. shift + F5 for paste copied records.

Oracle Warehouse Management Setups - Define Strategies

Oracle Warehouse Management Setups -  Define Strategies

Below are the details of  Define Strategies as part of Oracle Warehouse Management Setups 

Navigation: - Warehouse Manager Responsibility >> Setup >> Warehouse Configuration >> Warehouse Execution >> Strategies >> Double Click

Can select Strategy Type from LOV  

Note: - Make Strategy Enabled to get it assigned to business flow. Without enabling it Strategy will not be visible in Rule Workbench. Like this, we can assign multiple rules in a strategy along with their sequence of executions.

Assignment of Rules/Strategies to business flow

Navigation: - Warehouse Manager Responsibility >> Setup >> Warehouse Configuration >> Warehouse Execution >> Rules Workbench >> Double Click