WMS Receipt Label Print flow

1. Once Receiving transaction saved, it processes the transaction and inserts the data into rcv_shipment_headers, rcv_transactions.
2. Once transaction completed in the same flow, inv_rcv_integration_apis.complete_lpn_group calls inv_label.print_label_wrap
3. inv_label.print_label_wrap generates the detailed XML and publishes in label history table
4. Once label history table populated with all data, inv_label.print_label_wrap calls INV_PRINT_REQUEST.SYNC_PRINT_REQUEST to print the label based on print mode and printers from profiles of either user or responsibility.

To get the label print work below basic setups need to be there

1. Responsibility or user which does the transaction needs to be assigned to the Receipt business flow with required label format(material or lpn or serial, etc)
2. For each label type, there should be a default label format
3. If you want to have specific labels printed for different conditions then specific label format rules need to be defined in the system.

Oracle HRMS Extra Information Types

HRMS Extra Information Types(EIT)

Extra Information Types allow users to hold unlimited amounts of extra information on people, assignments, locations, positions, jobs and organizations.
The format of this data is defined by the user in descriptive flexfield structures and accessed via Extra Information forms that can be added to taskflows and menus.

Defining an Extra Information Type

You define EITs in the relevant descriptive flexfield. 

These are

Extra Assignment Info. Details

Extra Assignment Information

Extra Contact Info Details

Extra Job Info Details

Extra Job Information

Extra Location Info Details

Extra Location Information

Extra Person Information

Extra Previous Job Details

Extra Contact Information

Extra Document Info Details

Extra Document Information

Extra Position Information

Extra Previous Job Information

Extra Person Info. Details

Extra Position Info Details

Developer define the Context Reference Field on these flexfields is seeded with the value INFORMATION_TYPE. 

You create a new context value for each EIT you require.
Then create segments to hold the information you want to record, as you would for any other descriptive flexfield.
Then freeze the flexfield structure.

Registering an Extra Information Type

Each Extra Information Type needs to be registered in the relevant EIT table (example, PER_PEOPLE_INFO_TYPES for Person EITs).
This is done by running the concurrent process ‘Register Extra Information Types (EITs)’.
The Parameter ‘Table Name’ uses a LOV which, as well as the table name, displays the EIT name associated with that table. After selecting the Table Name, you select the ‘Information Type’ which is the name of the dff context you created for this new EIT. Enter values for ‘Multiple Rows’ (‘Yes’ if more than one set of values can be entered for this EIT); ‘Legislation Code’; and ‘Description’.
If the new EIT is an Organization EIT then you can also restrict it to a single classification using the ‘Organization Classification’ parameter. It will then be available from the ‘Others’ button only for the relevant classifications.

Restricting Access to Extra Information Types

To allow a responsibility to access an EIT, you need to navigate to the Information Type Security form in HRMS

Security->Extra Information Security. 

Highlight the responsibility that should have access to the EIT and then pick in the EIT name in the Information Types zone.
Organization EITs are not visible in the Information Type Security form 

Security->Extra Information Security.
They are automatically accessible from the Others button in the Define Organization screen

Work Structures->Organization->Description for the relevant classification when the Register Extra Information Types (EITs) process is complete.

Adding Extra Information Types forms to a Taskflow

Task flow nodes for all EIT forms are seeded, but not included in any seeded task flows.
So you will need to either update an existing taskflow or create a new one in order to access the EIT forms.
Use the Define Task Flows screen  to create or update your task flow.

Navigate->Security->Task Flow->Definitions

Adding EIT forms to a Menu

It is necessary to create a function for a new task flow before it can be added to a menu.
In System Administrator 

Navigate->Application->Function

Enter a function name and a user function name then enter the following parameter: WORKFLOW_NAME=””
Go to the Define Menu screen 

Navigate->Application->Menu 

Query the menu that you wish to change. The value that you pick in the Function field will be what was entered as the User Function Name in the Define Function form.
There is also a seeded function for each EIT form that could be added to a menu.

Example

Lets Take the example of Location form.

There is option for maintaining Extra Information for a location

Table & API Information

New contexts for the EIT descriptive flexfields are held in FND_DESCR_FLEX_CONTEXTS, and the segments are held in FND_DESCR_FLEX_COL_USAGE as with any other descriptive flexfield.

An EIT is registered by inserting a row into the relevant EIT table. The information here includes the EIT name, legislation code and whether the EIT allows single or multiple entry.
The EIT tables are:

HR_LOCATION_INFO_TYPES
PER_JOB_INFO_TYPES
PER_POSITION_INFO_TYPES
PER_PEOPLE_INFO_TYPES
PER_ASSIGNMENT_INFO_TYPES
HR_ORG_INFORMATION_TYPES

For Organization EITs it is also necessary to link the EIT with an organization classification. This link is held in HR_ORG_INFO_TYPES_BY_CLASS.

PER_INFO_TYPE_SECURITY is used to hold the EITs that a responsibility may access (excluding organization EITs). This information is entered in the Information Type Security form 

Security->Extra Information Security.

The location of the data entered into EITs depends on the EIT type (eg Person EIT, Org EIT, etc).

The tables holding this data are:

HR_LOCATION_EXTRA_INFO
HR_ORGANIZATION_INFORMATION
PER_JOB_EXTRA_INFO
PER_POSITION_EXTRA_INFO
PER_PEOPLE_EXTRA_INFO
PER_ASSIGNMENT_EXTRA_INFO

There are a number of APIs which allow you to create, update and delete EIT information:
create_location_extra_info,
update_location_extra_info,
delete_location_extra_info

create_job_extra_info,
update_job_extra_info,
delete_job_extra_info

create_position_extra_info,
update_position_extra_info,
delete_position_extra_info

create_person_extra_info,
update_person_extra_info,
delete_person_extra_info

create_assignment_extra_info,
update_assignment_extra_info,
delete_assignment_extra_info

WMS Label Format Setup and Demo

Labels are an integral part of WMS functionalities.
This will help in easy transaction, clear tracking and using this transactions can be automated.
Oracle provides different types of labels to setup as per your business transactions.
Supplier labeling speeds-up the receiving process by enabling bar code scanning of inbound purchase orders, that results in less receipt processing time, immediate recognition of available materials, and higher receiving accuracy.

Labels can be customized as per customer needs to cpmly with specific business or govt compliances with fields and barcodes.

Even you can print customized documents as labels in case of requirement using label printing api.
Below is the step wise setup with an example for clear understanding

Create an Item

Navigation:
Inventory Super User -> Inventory -> Items -> Master Items

Assign Items to the organization

Tools -> Organization Assignments

Define Label Format

You can use oracle provided standard Labels or you can customize as per your business need

Warehouse Manager -> Setup -> Warehouse Configuration -> Printers & Devices -> Define Label Format

Select label type and entity type, find seeded label format and click on Label Fields and variables to check visible fields. You can define your custom format and select required fields.

Assign Label Format to Business Flow

Setup -> Warehouse Configuration -> Printers & Devices -> Assign Label Format to Business Flow

*Drill down business flow and select Miscellaneous / Alias Receipt. Assign label type at user level

Create Label Format Rule

Setup -> Warehouse Configuration -> Rules -> Warehouse Execution -> Rules

*Create a new Label format rule to satisfy the business condition

Then run Generate All Rule concurrent program

Do A transaction to understand how it works

Do a Misc Receipt Transaction using MSCA 

Check the generated Labels

Navigate to

Warehouse manager -> Inquiry -> View Label Requests

Query by giving your user id or any such specific parameter in the form and you will be able to see the label, its status with details and the XML format of the label.

This labels can be printed in all types of label printers provided by many different vendors like Zebra, etc.

Explore More here

Label Printing in MSCA/WMS

Labels

Either we can use the existing labels or we can design new labels

Label Types:

There are different label types depending on the different business and requirement with data elements.

Label Format:

A single design of a label that may include fixed data (such as field prompts) and variable data (such as Part Number). A Label Format is associated to a Label Type. It includes a subset of the available data elements from a particular Label Type. A label type can have multiple label formats, however each Label Format belongs to only one label type. Label Formats are registered within Oracle Warehouse Management after you create the label design in the third party software package.

Either you can use the seeded label format or you can design your own label format

We can customize the label as per our requirement with required and customized fields

Printing Modes

Asynchronous:

An integration mode between Oracle Warehouse Management and the third party software supplier that is handled through dropping an XML file into a watched directory. When using this mode, Oracle Warehouse Management has no knowledge of the status of the print request after creation of the XML file.

Synchronous:

Generic:

A real-time integration mode between Oracle Warehouse Management and the third party software vendor that is handled through a PL/SQL API. When using this mode, the third party supplier is able to return success or failure messages regarding the status of the label print request. Oracle Warehouse Management stores those messages in the label print history so label printing problems can be easily identified and diagnosed.

TCP/IP:

A real-time integration mode between Oracle Warehouse Management and the 3rd Party software vendor that is handled through a standard Ethernet TCP/IP connection. When using this mode, Oracle ensures that the printer or print server is listening to the IP and port and has successfully received the message, but no knowledge of the detailed status of the print request beyond acceptance of the XML message is known by Oracle Warehouse Management.

Example Printer vendors like Zebra, Intermec, Cognitive Solutions, Datamax, Toshiba TEC, Printronix and Sato

Printer

·        Define the printer details in Oracle system (Sysadmin) with proper styles and drivers and with unique name

·         Assign IP and Port to printers

Assigning Label Types to Business Flow

Business Flow: An identifiable business process that occurs as part of material handling within Oracle Warehouse Management. Oracle Warehouse Management recognizes a pre-determined list of Business Flows you can set up to include label printing as part of the transaction processing.

Defining Label Format Rules

Creating label format rules is an optional step. Some implementations may require only a single label format for each label type. If this is the case, the system picks the default label format for each type. The system also picks the default if there are no applicable rules. If the implementation requires more than one label format for a label type label format rules are necessary.

Assigning Printer to the Required Level

Printers can be assigned to Site level, responsibility level, user level.