Oracle R12 Warehouse Management System (WMS) – LPN Contexts:

Oracle R12 Warehouse Management System (WMS) – LPN Contexts:

License Plate Number (LPN):

In Oracle Warehouse Management, LPN (License Plate Number) is an object that holds items in the WMS enabled organization. Although LPNs are associated with containers, they do not need to represent a physical entity, such as a box / container. Thus, a collection of items can be defined in a LPN. A single LPN can contain many quantities of the same item and or different items.

Oracle Warehouse Management system (WMS) defines a context for each LPN to denote the current state of the LPN. Some of these contexts can be used in the WMS Rules Engine to define specialized picking and put away rules.

The below table summarizes the LPN Contexts:

LPN Context Code	Description	Definition
1	Resides in Inventory	An LPN with a context of 1 indicates that material associated with this LPN has been costed and accounted for in inventory. Outbound transactions can be performed on LPNs with a context of 1.
2	Resides in WIP	An LPN with a context of 2 indicates that material associated with this LPN is currently being transacted in WIP. Therefore, the associated material is not yet in inventory and has not been costed to inventory.
3	Resides in Receiving	An LPN with a context of 3 indicates that material associated with this LPN have been received using a standard routing or inspection routing receipt and have not been put away yet. Therefore, the associated material is not yet in inventory and has not been costed to inventory.
4	Resides in Stores	LPNs with a context of 4 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.
5	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.
6	Resides in Intransit	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.
7	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 a context of 7. Material associated with LPNs of this context are not on-hand or costed until it is actually received.
8	Packing context, used as a temporary context value	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
9	Loaded for shipment	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.
10	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.
11	Picked	LPNs picked during the picking process receive this context. They are intransit within the warehouse.

Query to find the context of a LPN:

select LPN_CONTEXT from apps.wms_license_plate_numbers WHERE LICENSE_PLATE_NUMBER =:P_LPN_NO

Oracle R12 Warehouse Management System (WMS) – Implementing Profile Options

Oracle R12 Warehouse Management System (WMS) – Implementing Profile Options

During Oracle Warehouse Management implementation, a value is set for each user profile option to specify how WMS controls access to and processes data.

Please find below the Profile options used in WMS Module and purposes.

Profile Option Name	Purpose
WMS: Allow Mixed Statuses in an LPN	It controls whether the material of different statuses can be packed into the same LPN.
WMS: Assign Task Types	It indicates whether task type stamping, cartonization, task consolidation and task splitting happen during pick release.
WMS: Barcode Font Name	Barcode Font Name used for Oracle Warehouse Management Reports
WMS: Barcode Type	Barcode Type used for Oracle Warehouse Management Reports
WMS: Default Source Type for Control Board	Default Source Type for WMS Control Board Query
WMS: Deployment Mode	Deployment Mode for WMS
WMS: EPC ASN LPN import column	To specify the column that should be used to populate EPC in wms_lpn_interface table
WMS: EPC ASN Serial import column	To specify the column that should be used to populate EPC in mtl_serial_numbers_interface table
WMS: EPC Generation Encoding	To specify the Number System (Binary, Hex, Decimal) in which EPC should be spit out to Labels
WMS: Express Returns	Indicates if user wants returns to be processed without involving the mobile return confirmation.
WMS: Ignore Equipment	This option will decide the meaning of blank equipment field on the task sign on page
WMS: Item/Revision Delimiter	Character on multi-field barcode used to separate item number and revision
WMS: Label file prefix	String prepended to the XML label file name when they are dropped in the label printing directory
WMS: Label output directory	Directory into which XML label files should be dropped
WMS: Label Print Mode	Identifies if a label print request is submitted in a Synchronous or Asynchronous mode
WMS: Label Printing for Cycle Count	Option to print the label during cycle count
WMS: Online Putaway	Indicates if user wants putaway process to run putaway rules engine online
WMS: PO Number/Line Delimiter	Character on multi-field barcode used to separate PO number and PO line number
WMS: RFID User	To set RFID related transactions in the context of a specific user
WMS: Sequence Picks Across Waves	Picks will be sequenced across waves based on this option
WMS: Subinventory/Locator Delimiter	Character on multi-line barcode used to separate subinventory and locator
WMS: Suggestion Stale Period	Indicates time after which a suggestion becomes stale
WMS: Synchronous TCP/IP label request delay	Time delay (in milliseconds) that will be introduced after every label is sent using 'Synchronous TCP/IP' mode.

Oracle SCM Functional Interview Questions & Answers – India Localization – Part III

Oracle SCM Functional Interview Questions & Answers – India Localization – Part III

What is Bond Register?

The calculation of ED & updates of excise registers are based on the setup made in the define bond register. Before making this setup, you need to define the order types & transaction sources.

Excise transactions are classified into the following categories:

1. Domestic with Excise

2. Domestic without excise

3. Export with Excise

4. Bond Register (Export under bond)

Why to create Excise invoice number and document Sequence? What are the concurrent involved and to run the same for a shipment?

Without document sequence excise & VAT cannot be claimed.

For Excise, “India – Excise Invoice Generation” & delivery number to be provided as parameter for generation.

For VAT, “India – VAT Invoice Generation / Accounting” & registration value to be provided.

How to insert taxes in AP and AR invoice?

Following concurrent are to be triggered:

For AP: “India to insert tax for pay on receipt”

For AR: “Local concurrent for processing order lines to AR”

What is Bonded Sub-inventory and what is the use of it?

Excise related transactions & records will be updated only for those subinventories which are identified as bonded for manufacturing organizations.

Example:

If bonded sub-inventory is not defined, then claim cannot be made and the excise & VAT recoverable will go into the material cost. As a result, the cost of material will increase.

What is RG Consolidation?

RG consolidation (excise) is performed to make sure that our balances available in RG registers are adjusted against PLA register & to find out the liability to be paid to the tax authority of excise.

What are the sources used to import Excise, Service Tax and VAT into GL?

Sources used to import into GL:

For Excise: Purchasing India

For VAT: VAT India

For ST: Service tax India

During the PO Return will the taxes be reversed?

Yes, the taxes will be reversed.

Where to see the receipt accounting entry and delivery accounting entry?

Receipt accounting entry: (After the receipt and the delivery).

Accounting entry can be viewed in the Receiving Transaction Summary

Navigation:

India Local Purchasing > Oracle Purchasing > Receiving > Receiving Transaction Summary

Delivery Accounting Entry:

Accounting entry can be viewed in Material Transaction.

Navigation:

India Local Inventory > Oracle Inventory > Transaction > Material Transaction

Can we have the same invoice number for Excise and VAT?

Yes. We can have the same invoice number for Excise & VAT

How do differentiate between manufacturing org and trading org?

When navigating to the org additional information, the accounting information will be grayed out for trading org while the trading information will be grayed out for manufacturing org.

What is BOE invoice?

During customs accounting process, BOE invoice is the one through which the payment is made to the customs authority.

What are the setups for TCS?

1. Tax

2. Tax Category

3. Item Catagory

4. Item classification

5. Transaction type

6. Transaction source

7. Receipt class

8. Regime registration

9. Tax calendar

10. Tax authority & Tax authority additional information

11. Customer & Customer additional information

What is the difference between Accrual Basis and Cash Basis?

Accrual accounting method recognizes the revenue when it is earned & expenses when they are incurred. While cash basis accounting recognizes revenue & expense when cash is actually spent or received.

How to create tax code for VAT?

Tax Code can be created for VAT through Asia pacific lookup, the look-up name is JAI_TAX_TYPE

Reference: Collected from various web sources.

Please do refer below links for Oracle SCM Functional interview questions & Answers on India Localization module.

http://learnoraclecsbscm.blogspot.in/2015/09/oracle-india-localization-interview.html

http://learnoraclecsbscm.blogspot.in/2015/09/oracle-scm-functional-interview_29.html

Oracle R12 Order Management – Automatic Attachment

Oracle R12 Order Management – Automatic Attachment

Attachment in Oracle R12 Apps:

Attachment is a file, text doc or a web file attached to a particular entity to capture additional information or data that is otherwise not captured through applications.

Enable users to link unstructured data, such as images, word doc, spreadsheets, or text to application data.

Automatic Attachment in Oracle R12 Order Management:
Automatic Attachment in Order Management means, when user creates and Save the Sales Order, System will attach Attachment automatically to Order Header/Lines based on the Rules and Attributes created.

Option 1:

Automatic Attachment will be applied based on the additional rules specified:

User can also set a profile option so that the system will automatically apply the automatic attachment.

Setup Steps:

1. Set the profile option OM: Apply Automatic Attachments to Yes.

2. Define Document Category

3. Define Documents

4. Define Addition Rules

1. Setting up Profile Option:

2. Define Document Category:

Navigation:

India Local Order Management Responsibility > Oracle Order Management > Setup > Orders > Attachments > Documents Categories

Category: Define a Document Category

Default Datatype: Select a Datatype from the list of values.

Effective Dates: Select a start & end date

Click Category Assignments

Select the Type & Name

3. Define Documents:

Navigation:

India Local Order Management Responsibility > Oracle Order Management > Setup > Orders > Attachments > Documents

Category: Select a category from the list of values. It defines the purpose of an attachment and controls which forms or pages can access it.

Title: Define a unique title for the Document

Description: Define a description for the Document

Data Type: Select the attachment from the list of values

Text: Enter text that is less than 2000 characters.

File: Launch the Upload a File window in the browser. Select the Browse button to locate the file in file system or enter the file location in the File field.

Web Page: Cursor advances to the URL field on the Source tab of the window. Enter the URL for the Web page.

4. Define Addition Rules:

Click Addition Rules Button.

Select the Entity from the list of values:

Order Header

Order Line

Quote Header

Quote Line

Supported Attributes for Order Headers are:

Bill To

Customer

Customer PO

Order Category

Order Type

Ship To

Supported Attributes for Order Lines are:

Bill To

Customer

Customer PO

Inventory Item

Line Category

Line Type

Ship To

Ex:

While user creates a sales order for non-specified order type, attachment will not be available.

And when user created a sales order for specified order type, attachment will be automatically available.

Option 2:

To apply an automatic attachment on an order Manually:

In the Sales Orders window, click Actions and select Apply Automatic Attachments from the list of values.

Oracle R12 Inventory - Transaction Source Types

Oracle R12 Inventory - Transaction Source Types:

Transaction Source Type is the type of entity against which Oracle Inventory charges a transaction. Along with a transaction action, it uniquely identifies the type of transaction is performed.

Oracle Inventory provides the following predefined 17 Transaction Source Types:

Account

Account Alias

Cycle Count

External Requisition

Internal Order

Internal Requisition

Inventory

Job or Schedule

Layer Cost Update

Move Order

Periodic Cost Update

Physical Inventory

Project Contract

Purchase Order

RMA (Return Material Authorization)

Sales Order

Standard Cost Update

Additional Transaction Source Types can also be defined in the Transaction Source Types window. Then these user-defined transaction source types can be used and predefined transaction actions to define a new transaction type. This user-defined transaction type is now a customized form of tracking transactions with which can be grouped and sort reports and inquiries.

When a transaction is performed, a transaction type to be specified and a source.

Example:

For a PO receipt transaction, the transaction source type is Purchase Order and the actual PO number is the source.

Addition of more source types to this list is possible or update the predefined types, however, the predefined types cannot be deleted. User can add source types for miscellaneous transactions, inter-organization and subinventory transfers and account transactions.

Defining & Updating Transaction Source Types:

Navigation:

India Local Inventory Responsibility > Oracle Inventory > Setup > Transactions > Source Types

To update a system-defined transaction source type:

Navigate to System Tab.

Update the name or description for a source type.

Save your work.

To create a user-defined transaction source type:

Navigate to User Tab.

Name: Enter a unique name for the transaction source type.

Description: Define a description for the Transaction Source Type

Validation Type: Select a validation type from the list of values.

None: Do not validate the source against a predefined list of values.

Value Set: Validate the source against a predefined list of values.

Context: This field will be enabled only if Value Set is selected in the Type field and select a valid context field value associated with the Transaction Source descriptive flexfield.

Inactive On: Select the end date of this Transaction Source Type.

Oracle R12 Inventory - Types of Transaction Managers

Oracle R12 Inventory - Types of Transaction Managers:

Oracle Inventory Transaction Managers run at periodic intervals that can be specified until to delete them with the concurrent manager. They control the number of transaction workers, processing intervals and number of transactions processed by each worker during each interval.

Oracle Inventory have below Transaction Managers Setup that can be launched & scheduled to run at the scheduled frequency. Each Transaction Manager processes different type of transactions.

Material Transaction:

Material Transaction Manager immediately executes a material transaction after user save the changes in a transaction window. By starting the transaction manager that can be determined how to execute transactions immediately through immediate concurrent request submissions or through periodic concurrent request submissions. Transaction mode can be defined for individual transaction windows in the Personal Profile Values window.  

Demand Reservation:

Demand Reservation Manager periodically updates Oracle Inventory with the demands (Sales order scheduled shipments and reservations) created by Oracle Order Entry or by using the open demand interface.

Move Transaction:

Move Transaction Manager processes move transactions in Oracle Work in Process and move transactions can be imported from devices such as portable bar code readers or custom data entry forms using the Open Move Transaction Interface.  

Resource Cost Transaction:

Resource Cost Transaction Manager processes resource transactions in Oracle Work in Process and resource transactions import from barcode readers, payroll systems, time cards, routing sheets and custom data entry forms using the Open Resource Transaction Interface.  

Material Cost Transaction:

Material Cost Transaction Manager costs material transactions in Oracle Inventory and Oracle Work in Process in the background.

Oracle Inventory – Defining Item Relationships

Oracle Inventory – Defining Item Relationships

Item Relationships functionality allows users to search for items through these relationships. Except in Oracle Purchasing, these relationships are for inquiry and reporting purposes only.

Within Oracle Purchasing users can define acceptable substitute items for receiving. A list of substitutes should be defined before receiving a substitute item in place of an original item.

To receive a substitute item correctly, ensure that the ordered item and the substitute item share the same base unit of measure.

Item Relationships is controlled organizational level and if the relationships is defined at Master Org level then the relationships be will applicable for all organizations.

Defining Item Relationships:

Navigation:

India Local Inventory Responsibility > Oracle Inventory > Items > Item Relationships

Or

India Local inventory Responsibility > Oracle Inventory > Items

Query the item & define the Item Relationships by choosing Item Relationships from the Tools Menu

Click Find button to find the already defined Item Relationships.

Choose New button to define a new relationship between the items.

From Item:

Enter an item that represents the From part of the relationship.

To Item:

Enter an item that represents the To part of the relationship.

Type:

Please find the below options that can be used to relate one part from another:

Related: The items are related in a non-specific way.

Substitute: One item is a substitute for another.

Cross-Sell: This relationship indicates that one item may be sold in lieu of another item.

Up-Sell: This relationship indicates that a newer version of the item exists, and can be sold in place of the older item.

Service: This relationship establishes service items for a repairable item.

Prerequisite: This relationship indicates that user must possess one of the items as a requirement to possessing the other item.

Collateral: This relationship indicates collateral, such as marketing brochures, that user possess for an item.

Superceded: This relationship indicates that one item has replaced another item that is no longer available.

Complimentary: This relationship indicates if a customer purchases one item, the other item is received for free.

Impact: This relationship is used to relate items to each other but only under special conditions.

Conflict: This relationship indicates that these items may never be used together.

Mandatory Charge: This relationship indicates a mandatory charge if the customer purchases both items.

Optional Charge: This relationship indicates an optional charge if the customer purchases both items.

Promotional Upgrade: This relationship enables a customer to upgrade from one item to another item or equal or higher value, without an additional charge.

Split: This relationship enables user to split support for an item so user you do not need to manually split support at contract renewal. Enabled for a planning enabled organization.

Merge: This relationship enables rules based consolidation of contracts. User may use the earliest or latest target end date for consolidation. This allows user to choose how contracts are consolidated. Enabled for a planning enabled organization.

Migration: During contact renewal user are given the option of renewing contracts based on new licenses, or old licenses. Enabled for a planning enabled organization.

Repair to: User can use the Repair to item relationship with field service operations that use spares management functionality. If a part has been superseded by another part, the Repair to item relationship determines the replacement part.

Reciprocal:

Define whether the item relationship is Reciprocal.

Planning Enabled:

Define if the item relationship type is substitute & if planning is enabled for the substitute item.

Effective From To Dates:

Enter the Effective Dates if the item relationship is Split, Merge, or Migration.

Save the work.

To define details for Substitute Item Relationships:

Click Planning Details Button

Planning Details Block:

Substitution Set: Enter the Substitution set.

Partial Fulfillment check box: Enable the check box if required.

Effective From To Dates: Enter the Effective Dates for the Substitution.

All Customers check box: Enable the check box if the substitution applies to all customers,

If not checked the check box, define enter the customer information in the Customer References region.

Save the work.