SCM


What is Supply Chain Management?
Oracle Supply Chain Management R12 enables you to drive supply chain processes based on real-time demand information, and in turn provide customers accurate information on pricing and availability. The results you maximize value in your supply chain while increasing revenues and customer satisfaction levels.






Oracle Asset Tracking

Contents

Understanding Oracle Asset Tracking
Overview of Oracle Asset Tracking
About Oracle Asset Tracking
Tracking Internal Products and Assets
About Oracle Install Base Integration
About Inventory Item and Asset Tracking
About Item Parameters in Oracle Inventory
About the Messaging Architecture
Understanding Inventory Integration
Overview of Understanding Inventory Integration
About Item Instance and Transaction Records
Expiring an Association Between a Fixed Asset and Item Instance
About Purchase Order Receipt into Inventory
Receiving Items into Asset Subinventories
About Move Orders
Creating a Move Order
Transacting a Move Order
Creating Miscellaneous Transactions
About Miscellaneous Receipts
About Miscellaneous Receipts from Projects
About Miscellaneous Receipts from Field Location
Entering a Miscellaneous Receipt Transaction
Entering the Item to Transfer
About Miscellaneous Issues
About Miscellaneous Issues to Projects
About Miscellaneous Issues to Field Location
About Subinventory Transfers
About Inter-Organization Transfers
About Physical Cycle Counts
About Asset Handling for Internal Sales Orders
Explaining Other Inventory Transactions
Understanding Asset Deployment
Overview of Understanding Asset Deployment
About Asset Deployment
About Asset Deployment Transactions
About Partial Installation and In-Service Conditions
Selecting the Location for the Item Instance
Using the Item Instance Deployment Page
Understanding Field Service Integration
Overview of Understanding Field Service Integration
About Field Service Integration
Viewing Service Request Numbers and Task Numbers
Understanding Projects Integration
Overview of Understanding Projects Integration
How Purchase Order Receipts Flow into Project Transactions
Receiving Items Directly into an Oracle Project
About Transaction Sources for Project Import
About Expenditure Inquiry
About Asset Creation
Running the PRC: Generate Asset Lines for a Single Project Program
Running the PRC: Interface Assets to Oracle Asset Program
Understanding the Fixed Asset Architecture
Overview of Fixed Asset Architecture
About Asset Processing in Oracle Asset Tracking
About Asset-Related Processes in Oracle Asset Tracking
Running the Create Assets Interface Inventory Transactions to Fixed Asset Program
Running the Create Asset Headers in Oracle Projects - Normal Items Program
Running the Interface Move Transactions to Oracle Assets Program
About Asset Impact of a Miscellaneous Issue
About Asset Impact of Subinventory Transfers
About Asset Impact of Inter-Organizational Transfers
About Asset Impact of Physical Inventory and Cycle Count Adjustments
Case Study
Understanding the CLEI
Overview of Retirements
Associating a Fixed Asset to an Item Instance
Viewing Asset Relationships Graphically
Using Oracle Asset Tracking
Overview of Using Oracle Asset Tracking
Submitting a Request
Viewing Request Results
Requesting an Assumed Loss Rate Report
Requesting a Bill of Lading Report
Adjusting the Invoice Price Variance
Running the Interface Invoice Price Variance to Oracle Assets Program
Running the Interface Invoice Price Variance to Oracle Projects Program
Running the Generate Notification - New Fixed Assets for Install Base Tracking Program
Running the Create Reversal GL Entries for Inventory FA Items Program
Finding Personal Profile Values
Using the Google Maps Integration
Google Maps Integration Overview
Google Maps Integration with OAT
Viewing Instances on Google Maps
Using the ESRI Integration
ESRI Integration Overview
ESRI Integration with Oracle Asset Tracking
Viewing Assets Using the ESRI Map Viewer
GIS Integration: Custom Map Viewer
GIS Integration: Custom Map Viewer
Setting Up the Custom Map Viewer
Setting Up the Custom Map Viewer Profile Value

Understanding Oracle Asset Tracking

This chapter covers the following topics:

Overview of Oracle Asset Tracking

This topic group provides overviews of Oracle Asset Tracking and its components, explanations of key concepts, features, and functions, and explanation of the application's relationships to other Oracle or third-party applications.

About Oracle Asset Tracking

Oracle Asset Tracking is a fully integrated solution in the Oracle E-Business suite designed to deploy and track internal products and assets at internal or customer sites, while providing the ability to capture financial transactions with back-office automation.
With Oracle Asset Tracking, you can give users access to tracking information without allowing them access to sensitive processes related to assets and purchasing. You can also track inventory items after they have been installed and link financial transactions to the physical movement of equipment.
Oracle Asset Tracking integrates with Oracle Inventory, Oracle Purchasing, Oracle Projects with the Capital Resource Logistics (CRL) feature, Oracle Assets, Oracle Payables, and Oracle Install Base, and stores information collected from them.

Tracking Internal Products and Assets

The following diagram shows a summary of the Oracle application modules and the transactions associated with Oracle Asset Tracking.
Summary of Oracle Processes that Track Internal Products and Assets
the picture is described in the document text

About Oracle Install Base Integration

The Oracle Install Base platform uses the Service Fulfillment Manager application to integrate Oracle Purchasing, Oracle Payables, Oracle Inventory, CRL Projects, Oracle Assets, and can integrate with legacy systems to synchronize and manage material flow in a company. The Oracle Asset Tracking platform minimizes data entry by using customer-definable business rules to send messages to all other related applications to perform the appropriate update when a business event occurs.
Oracle Asset Tracking utilizes Oracle Install Base as its data repository. Every transaction that Oracle Asset Tracking tracks is recorded in the Oracle Install Base transaction table, and each record affected by such transactions is recorded in the instance and instance history tables.
You can also view asset relationships graphically by using Oracle Asset Tracking and Oracle Install Base.
All setups are done through windows in Oracle Install Base or other products, including the setups for locations and parties.
Related Topics
Viewing Asset Relationships Graphically

About Inventory Item and Asset Tracking

To track inventory items and assets, Oracle Asset Tracking must interact with several enterprise resource planning (ERP) applications. It sends to and receives messages from these applications about the status and location of the items that you want to track.
Oracle Asset Tracking provides an enterprise tracking and asset management system where all inventory, project, party, and asset-related material information is stored, providing a 360-degree view of your assets. You can locate materials anywhere in the system—in warehouses, on trucks, installed in the network, or on project sites—facilitating financial transactions using physical movements of material and equipment. In addition, Oracle Asset Tracking can provide a life-cycle history of all activity for that equipment.
An asset comprises a collection of items. The items may be trackable or not trackable. During implementation, items are designated as Oracle Asset Tracking-trackable at the master level in Oracle Inventory. Oracle Asset Tracking tracks the activity of the trackable items through inventory and projects, and into fixed assets.
In Oracle Assets you perform the Mass Additions concurrent process to create assets.
As an example of message flows involving Oracle Asset Tracking, when a field service technician enters a report that equipment has been placed into service, the deployment transaction can send a message to Oracle Asset Tracking. This message updates the status of the equipment to In Service and gives its in-service date to Oracle Assets. The asset is now ready to be created in Oracle Assets.

Functions Supported by Oracle Asset Tracking

This application supports the standard functions found in Oracle Inventory, Oracle Purchasing, Oracle Assets, and Oracle Projects enabled for CRL Financials.
Oracle Asset Tracking supports the following functions:
  • Purchase order receipt of items into Inventory
  • Purchase order receipt of items into operating projects
  • Move orders to issue an item either to a project or directly to a field location
  • Miscellaneous issue to a project or field location
  • Miscellaneous receipt from a project or field location
  • Installation and un-installation of equipment
  • In-service/Out-of-service of equipment
  • Subinventory transfers
  • Inter-organization transfers
  • Miscellaneous receipts and issues
  • Placement of assets into or out of service
  • Retirement and reinstatement of the partial or full cost of an asset
  • Asset item moves and asset item transfers
  • Physical counts
  • Internal sales order shipment

Usage Codes

Oracle Install Base uses a number of location attributes to track the physical location of an item instance. The following values are used in Oracle Asset Tracking:
  • In Inventory
  • In Process
  • In Transit
  • Installed
  • In Service
  • Out of Service

About Item Parameters in Oracle Inventory

Items are created in Oracle Inventory. To track items using Oracle Asset Tracking, you must set some parameters at the time you create the item in Oracle Inventory.
The main item parameters to set are:
  • Track in Install Base
    This is a check box parameter. When set, it enables items to be tracked by transactions in and related to Oracle Install Base and Oracle Asset Tracking.
  • Create Fixed Asset
    This parameter determines if an item is normal or depreciable. The parameter determines how an asset can be created from the item.
    If the check box is selected, then the item becomes depreciable, and the asset is created upon receipt either in Oracle Inventory or in Oracle Projects.
    If the checkbox is left unchecked, then the item is regarded as normal, and the asset is created when put in service through an Oracle Asset Tracking deployment transaction.

Normal Versus Depreciable Inventory Items

For a normal item, the asset is created after an item is put in service. The asset is created through Oracle CRL Projects based on standard inventory cost.
For a depreciable item, the asset is created when an item is received, either in Oracle Inventory or Oracle Projects. The asset is created by Oracle Asset Tracking with the purchase order cost, which can be adjusted later after the invoice is matched the purchase order.
Oracle Asset Tracking supports the following inventory transaction types for internal sales orders:
  • Sales Order Issue
  • Internal Order Direct Shipment
  • Sales Order Pick
  • Internal Order Pick
  • Internal Requisition In-Transit Receipt
  • Internal Order In-Transit Shipment

About the Messaging Architecture

The messaging architecture receives requests from external publishing systems in XML (eXtensible Markup Language) format. Based on the input requirements, the application updates the status and keeps a history of transactions for the trackable unit. Subsequently, the application publishes outgoing requests to the subscribing systems for further processing. The publishing and subscribing systems include: Install Base, Inventory, Purchasing, Payables, Assets, Projects, Workforce Management, and other legacy systems.

Understanding Inventory Integration

This chapter covers the following topics:

Overview of Understanding Inventory Integration

This topic group provides information about interaction between Oracle Asset Tracking and Oracle Inventory and discusses the functionality of transactions in Inventory.

About Item Instance and Transaction Records

When an item is initially received, typically by a purchase order, a receipt transaction occurs. The initial receipt transaction creates an instance record for the item in Oracle Asset Tracking. A receipt transaction record is associated with the item instance record. Subsequent transactions against this item will also be associated with the instance record and will compose the history for that record.

Transaction Types in Oracle Inventory

Oracle Asset Tracking supports the following inventory transactions types, for both normal and depreciable items:
  • Purchase order receipt in inventory
  • Move order and transact move order
  • Miscellaneous issue to a project
  • Miscellaneous receipt from a project
  • Miscellaneous receipt and miscellaneous issue
  • Subinventory transfer
  • Inter-organization transfer
  • Physical cycle count
Oracle Asset Tracking supports the following inventory transaction types, for normal items only:
  • Project Contract Issue
  • Return to Vendor
  • Account Issue
  • Account Alias Issue
  • Project Borrow
  • Project Transfer
  • Project Payback
  • Cycle Count Transfer
  • Physical Inv Transfer
  • Backflush Transfer
  • Account Receipt
  • WIP Component Return
  • Account Alias Receipt
  • RMA Receipt
  • PO Rcpt Adjust
  • Int Req Rcpt Adjust
  • Shipment Rcpt Adjust
  • WIP Assy Completion
  • WIP Assembly Return
  • WIP Neg Comp Issue
  • WIP Neg Comp Return
For more information, see the Oracle Install Base User's Guide.

Item Instance Creation and Update

In many transactions, item instances are created or updated. The number of item instances created depends on whether the master item in Oracle Inventory is designated to be a serialized or a non-serialized item.

Item Instance Processing in Oracle Inventory Transactions

If an item is a serialized item, then an item instance is created for each separate item. If an item is a non-serialized item, an item instance is created that depends on a number of item attributes.
The following diagram shows the factors that determine how an item instance is created or updated during the Oracle Inventory transactions that affect Oracle Asset Tracking.
Item Instance Processing in Oracle Inventory Transactions
the picture is described in the document text

Expiring an Association Between a Fixed Asset and Item Instance

Use this procedure to expire an association between a fixed asset and item instance.
Prerequisite:
Associate a fixed asset to an item.
To expire an association between a fixed asset and item instance
  1. From the Asset Tracking Super User responsibility, navigate to Assets and then select Item Instances.
  2. Query an item instance that has an associated fixed asset.
  3. Select an item from the query results.
  4. From the Action list, select Assets.
  5. Click Go.
  6. Select the asset number from which you want to expire the association.
  7. Click Expire Assets.
    A confirmation message appears indicating that assets updated successfully.

About Purchase Order Receipt into Inventory

Purchase order receipt flow is initiated by the creation of a purchase order. The items are then received into inventory against the purchase order when the shipment arrives from the vendor.
The Receipt into Inventory package validates the data against the Oracle Install Base repository and creates or update the unit record.
  • If an item is serialized, then a new instance will always be created.
  • If an item is non-serialized, then Oracle Asset Tracking searches for the existing record. The search criteria are as follows: Inventory Item, Inventory Organization, Subinventory, Units of Measure, Instance Usage Code, Revision, Inventory Locator, Lot Number (if applicable). If the exact record is found, then the record will be updated with the new quantity. If not, then a new instance will be created.
  • Every receipt builds transaction history.

Receiving Items into Asset Subinventories

Use the following procedure to receive an item into an asset subinventory. If the item is not received in asset subinventory, then expenditures items will not be created in Oracle Projects
Prerequisites
The following are the prerequisites:
  • At least one subinventory must exist
  • The item number must be defined in Oracle Inventory.
  • The purchase order must exist in Oracle Purchasing with a status of Approved.
To receive items into asset subinventories
  1. From the Inventory responsibility, navigate to Transactions, select Receiving, and then select Receipts.
    The Organizations window opens.
  2. Choose your organization from the Organizations window, and click Find.
  3. In the Find Expected Receipts window, enter criteria that identifies the items that you are receiving, such as the purchase order number.
  4. In the Receipt header, enter the packing slip number and any other pertinent information.
  5. In the Receipt lines, verify the quantity to be received.
    You may receive a partial line quantity.
  6. Verify that the destination subinventory entered on the purchase order is not depreciable.
  7. Click Lot-Serial.
  8. If the item is under lot control, then enter the equipment code (CLEI) in the Lot field.
    If the items are under serial control, then enter individual serial numbers or a range of consecutive numbers. You can also enter corresponding vendor serial numbers in the Manufacturing Serial Number field.
  9. Save.

About Move Orders

A move order transfers inventory:
  • From one stocking location to another
  • From a stocking location to a project
To create a move order, you manually create a move order requisition. After the move order requisition is approved, it becomes a move order. If the organization does not require approval, then the manual request automatically becomes a move order.
You must define certain transaction types in Oracle Inventory for move orders, and you can define other transaction types. Two examples of Oracle Inventory transaction types for move orders are as follows:
  • Asset Tracking Move Order Issue to Project: Creates a document for moving material from inventory to a project.
  • Asset Tracking Move Order Subinventory Transfer: Creates a document for moving material from one subinventory to another subinventory. For more information, see About Subinventory Transfers.
Of the two transaction types shown, the Issue to Project transaction type is a required transaction type, and the Subinventory Transfer is optional.
For more information, see Define User-definable Transaction Types in the Oracle Asset Tracking Implementation Guide.

Parts of a Move Order

A move order comprises three parts:
  • The Move Order Header holds the move order number, an optional description of the move order, and information to default to the individual move order lines.
  • The Move Order Lines are the actual move requests, including the item number, requested quantity, completed quantity, the source, and destination information.
  • The Line Details are the inventory transactions that occur to fulfill a move order line, including equipment code, serial number, quantity moved, source, and destination details (such as locators).

Move Order Approval Governed by Time-Out and Item Planner

At the organization level, three attributes—Move Order Time-out Period, Time-out Action, and Item Planner item—affect how move order requisitions are approved. If the move order requisition is not approved before the time-out period passes, then Oracle Workflow sends a reminder notice to the item planner. If the move order requisition is still not approved within a second time-out interval, then the requisition is automatically approved or rejected based on the Time-out Action setting. If no item planner is specified for the item, then the requisition line is approved automatically.

Creating a Move Order

Create a move order when you need to transfer inventory across subinventories or into a project account.
Prerequisites
  • Inventory setups such as item, subinventory definition must be complete.
  • You must have defined transaction types for move orders in Oracle Inventory.
  • If you use an Oracle Workflow process to route move order requisitions for approval, then the item must be assigned to an item planner.
To create a move order
  1. From the Inventory responsibility, navigate to Move Orders and then select Move Orders.
  2. In the Move Orders window, enter an order number in the Number field.
    If you do not insert a value, then the application populates the Number field. You can also enter a description of the order in the Description field.
  3. In the Default region, enter the following information:
    • Transaction Type: Select a transaction type.
      This is one of the transaction types for move orders which you defined as user-defined transactions in Oracle Inventory.
      Note: The transaction Issue to Project must be Project based.
      For more information, see the section "Define User-definable Transaction Types" in the chapter "Dependency Module Setup", in the Oracle Asset Tracking Implementation Guide.
    • Date Required: Enter the requested delivery date.
      Also enter Ship-to Location, and Source and Destination subinventories.
  4. Enter the following information on the lines on each of the tabs:
    • Item: The item number, item revision (if under revision control), and quantity to move.
    • Project and Task
    • Source: Source subinventory (if different from the default value), locator (if locator control is enabled), equipment code (CLEI), and serial numbers.
      If you do not know from what subinventory the item should be transferred, then click On Hand at the bottom of the window to search for material locations.
      Note: You do not have to enter Source details in the Creating a Move Order procedure. If you do not enter Source details in the Creating a Move Order procedure, you must enter them in the Transacting a Move Order procedure. See Transacting a Move Order.
    • Destination: The destination subinventory or account, if different from the default value and the destination locator for a subinventory transfer type move order.
    • Control: The move order transaction type, if different from the default value, a predefined reason code, or alphanumeric reference information.
    Note: If approval is required, then the item planner receives a Workflow notification that there are move order requisition order lines awaiting approval. The planner uses Oracle Workflow to approve the orders.
    The item planner chooses Approve or Reject for each move order requisition line. If one requisition line on a move order is rejected, then other lines of the same move order can be approved.

Transacting a Move Order

After a move order is approved, you transact the move order by performing the action described on the approved lines. Use this procedure to perform the approved transaction.
Prerequisites
The move order must be approved.
To transact a move order
  1. In the Inventory responsibility, navigate to Move Orders and then select Transact Move Orders.
  2. Locate move orders that have been approved.
  3. You can query by header, line, source, or destination information.
  4. To add details to the move order line, select the check box for each line that you wish to detail, and click Allocate.
  5. Information is automatically entered on the transaction lines of the move order, based on the inventory picking rules and transaction defaults defined within the organization.
  6. Click View/Update Allocations to view the detailed lines.
  7. You can manually update any information that is incorrect. Add missing information, such as equipment code (CLEI) and serial numbers.
  8. If you do not require a pick slip, then click Transact to execute the detailed lines.
  9. If you need to print a pick slip, then save the transaction at this point. When the pick slip is ready, return to the Transact Move Orders window, select the line or lines to be executed, and click Transact.

Creating Miscellaneous Transactions

Oracle Asset Tracking supports the miscellaneous transactions (receipts and issues) used by Oracle Inventory. Each transaction in Oracle Inventory triggers a message to Oracle Asset Tracking.
In Oracle Inventory, the value of an item quantity can be a negative number, such as when a miscellaneous issue from inventory causes the quantity of an item to fall below zero. For depreciable items, if a transaction causes a negative inventory balance, then Oracle Asset Tracking adjusts asset units in Oracle Assets to zero, but it does not set the value in Oracle Assets to a negative number.
The topics in this section are as follows:
For more information, see Oracle Inventory User's Guide: Performing Miscellaneous Transactions and Oracle Assets User Guide: Defining Locations and Defining Distributions.

About Miscellaneous Receipts

Use miscellaneous receipts to receive material without a purchase order. In addition, you may also need to enter an equipment code (CLEI) in the Lot field, or a serial number.
  • If the item is serialized, then a new instance always is created.
  • If the item is non-serialized, then Oracle Asset Tracking searches for the existing record. The search criteria are as follows: Inventory Item, Inventory Organization, Subinventory, Units of Measure, Instance Usage Code, Revision, Inventory Locator, Lot Number (if applicable). If the exact record is found, then the record is updated with the new quantity. If not, then a new instance is created.
The following table summarizes the actions performed during the processing of the Miscellaneous Receipt transaction:
Miscellaneous Receipt Transaction Processing
Serialized item Non-serialized item
Check if item instance usage is Out of Service.
If Yes, update location.
If No, create new item instance.
Always create new item instance or update existing item instance.
For a non-serialized item, Oracle Asset Tracking processes a miscellaneous receipt using the same procedures as those for a new receipt.
Note: The Miscellaneous Receipt transaction cannot be used to move the existing non-serialized item instances back to inventory.

About Miscellaneous Receipts from Projects

The Miscellaneous Receipt from Project transaction is used to transfer material from Oracle Projects back to Oracle Inventory.
You must have defined the Miscellaneous Receipt from Project transaction in Oracle Inventory as part of the implementation of Oracle Asset Tracking. For more information, see the section "Define User-definable Transaction Types" in the Oracle Asset Tracking Implementation Guide.
The main considerations for the Miscellaneous Receipt from Project transaction are as follows:
  • For a serialized item, the instance record is updated. The instance usage code changes to IN INVENTORY.
  • For a non-serialized item, a new instance is created with instance code = IN_INVENTORY. If the record exists for the same instance, then that record is updated with the appropriate quantity. The search criteria are as follows: Inventory Item, Inventory Organization, Subinventory, Units of Measure, Instance Usage Code, Revision, Inventory Locator, Lot Number (if applicable).
  • Project expenditures are reversed by running the Cost Collection Manager program from Oracle Inventory and the transaction import from Oracle Projects. This reduces the project cost with the transacted item cost.
The following table summarizes the actions performed during the processing of the Miscellaneous Receipt from Project transaction:
Miscellaneous Receipt from Project Transaction Processing
Serialized item Non-serialized item
Check if item instance is In Process.
If Yes, update location, change usage to In Inventory.
If No, error.
Check if item instance is In Process.
If Yes, and if quantity is sufficient, then deduct quantity + item expenditure from the project item instance, and add quantity to the inventory item instance.
If No, error.

About Miscellaneous Receipts from Field Location

The Miscellaneous Receipt from Field location transaction is used to receive assets from the field location.
You must have defined the Miscellaneous Receipt from Field location transaction in Oracle Inventory as part of the implementation of Oracle Asset Tracking. For more information, see the section "Define User-definable Transaction Types" in the Oracle Asset Tracking Implementation Guide.
The main considerations for the Miscellaneous Receipt from Field location transaction are as follows:
  • For a serialized item, the instance record is updated. The instance usage code changes to IN_INVENTORY.
  • For a non-serialized item, a new instance is created with instance code = IN_INVENTORY. If the record exists for the same instance, then that record is updated with the appropriate quantity. The search criteria are as follows: Inventory Item, Inventory Organization, Subinventory, Units of Measure, Instance Usage Code, Revision, Inventory Locator, Lot Number (if applicable).

Entering a Miscellaneous Receipt Transaction

Use this procedure to enter a miscellaneous receipt transaction.
To enter a miscellaneous receipt transaction
  1. Navigate to the Miscellaneous Transaction window.
  2. Enter the date and time of entry for the transaction.
    The date you can enter is controlled by the INV: Transaction Date Validation profile option. See: Oracle Inventory Profile Options.
  3. Enter a miscellaneous transaction type for the transfer. This should the transaction you set up to receive assets from field location. See: "Defining Transaction Types" in Asset Tracking Implementation Guide.
  4. Optionally, enter the source of the transaction type.
  5. Optionally, enter the general ledger account against which the material is issued or received.
  6. Optionally, indicate if inventory information should be defaulted from the serial number.

Entering the Item to Transfer

Use this procedure to enter the item to transfer.
To enter the item to transfer
  1. Choose Transaction Lines in the Miscellaneous Transaction window. The Transaction Lines Detail folder window appears.
  2. Enter the asset item that you want to receive. If you choose to default inventory information from the serial number, enter a serial number.
  3. Enter the revision for the item to issue or receive. You must enter a value in this field if the item is under revision control.
  4. Enter a subinventory. For an issue transaction, you cannot enter a subinventory that does not have Quantity Tracking turned on.
  5. Enter a locator. You must enter a value here if you established locator control for the item.
  6. Optionally, enter a lot number for the asset item. If you want to enter multiple lot numbers, complete the remaining steps, then choose the Lot/Serial button to display the Lot Entry window.
  7. Enter a unit of measure. This can be the primary unit of measure (the default) or any valid alternate unit of measure. If you enter an alternate unit of measure, then Oracle Inventory issues the quantity that you specify in this unit of measure. Oracle Inventory also converts the quantity to the primary unit of measure so that it can correctly update the on-hand quantity.
  8. Enter the quantity of the asset to receive, based on the unit of measure that you specified.
  9. If using average costing, enter the unit cost of the item to receive or issue. Leave this field blank to use the system average cost at the time of the transaction.
  10. Enter a location from where you are receiving an asset. You must enter the location field for this transaction type.
  11. Optionally, enter a reason code for the transaction. For example, you can use reason codes to allow you to mark exceptional charges to support quality data collection.
  12. Optionally, enter text that describe the transaction.
  13. Enter a general ledger account for the item to use in the transaction. You can change this account only for miscellaneous issue/receipt or user-defined transaction types.
  14. To enter lot or serial number information, choose the Lot/Serial button.
  15. Save.

About Miscellaneous Issues

For miscellaneous issues, you can enter a lot number in the Lot field and a serial number for serial-controlled and lot-controlled items.
  • If the item is serialized, then the instance record is updated to zero quantity.
  • If the item is non-serialized, then Oracle Asset Tracking searches for the existing record. The search criteria are as follows: Inventory Item, Inventory Organization, Subinventory, Units of Measure, Instance Usage Code, Revision, Inventory Locator, Lot Number (if applicable). The record is updated to the appropriate quantity.
The following table summarizes the actions performed during the processing of the Miscellaneous Issue transaction:
Miscellaneous Issue Transaction Processing
Serialized item Non-serialized item
Set quantity to zero.
(Item instance will no longer appear in item instance searches.)
Reduce the on-hand quantity.

About Miscellaneous Issues to Projects

You must have defined the Miscellaneous Issue to Project transaction in Oracle Inventory as part of the implementation of Oracle Asset Tracking. For more information, see the section "Define User-definable Transaction Types" in the Oracle Asset Tracking Implementation Guide.
The Miscellaneous Issue to Project transaction works exactly the same way as the standard Move Order.
  • For a serialized item, the instance record is updated. The instance usage code changes to IN PROCESS.
  • For a non-serialized item, a new instance is created with instance code = IN PROCESS. If the record exists for the same instance, then that record is updated. The search criteria are as follows: Inventory Item, Inventory Organization, Subinventory, Units of Measure, Instance Usage Code, Revision, Inventory Locator, Lot Number (if applicable).
The following table summarizes the actions performed during the processing of the Miscellaneous Issue to Project transaction:
Miscellaneous Issue to Project Transaction Processing
Serialized item Non-serialized item
Change location.
Set usage code to IN PROCESS.
Reduce quantity from the inventory item instance, and increase quantity for the project item instance.

About Miscellaneous Issues to Field Location

Use this transaction to issue item to a field location directly from the warehouse.
Oracle Asset Tracking marks this transaction as an IN SERVICE transaction, and the asset can be created after the transaction is complete. The asset location of the existing assets will be changed after running Interface Move Transactions to Oracle Assets program.
You must have defined the Miscellaneous Issue to Field Location transaction in Oracle Inventory as part of the implementation of Oracle Asset Tracking. For more information, see the section "Define User-Definable Transaction Types" in the Oracle Asset Tracking Implementation Guide.
For a serialized item, the instance record is updated. The instance usage code changes to IN SERVICE. For a non-serialized item, a new instance is created with instance code = IN SERVICE. If the record exists for the same instance, then that record is updated.
The search criteria are as follows: Inventory Item, Inventory Organization, Subinventory, Units of Measure, Instance Usage Code, Revision, Inventory Locator, Lot Number (if applicable).
The following table summarizes the actions performed during the processing of the Miscellaneous Issue to Field Location transaction:
Miscellaneous Issue to Field Location Transaction Processing
Serialized Item Non-Serialized Item
Change location to the specified location.
Set usage code to IN SERVICE.
Reduce quantity from the inventory item instance, and increase quantity for the in-service item instance.

About Subinventory Transfers

A subinventory transfer moves material inventory between subinventories. A subinventory is a unique physical or logical separation of material inventory, such as raw inventory, finished goods, or defective material. All material within an organization is held in one or more subinventories.
A move order initiates a subinventory transfer. Oracle Asset Tracking handles these transfers in the same manner that Oracle Inventory handles them.
The way Oracle Asset Tracking processes a subinventory transfer is based initially on whether or not the transferred item has a serial number.

About Items with a Serial Number

Oracle Asset Tracking searches the database for the From record associated with the item. This record must have an Oracle Asset Tracking usage code of IN INVENTORY. After Oracle Asset Tracking locates the record, it updates the item's subinventory in the From record.

About Items without a Serial Number

Oracle Asset Tracking searches the database for the From and To records. These records must have an Oracle Asset Tracking usage code of IN INVENTORY. After Oracle Asset Tracking locates the records, it updates the item's subinventory in both the From and To records.
  • The source instance (the subinventory instance record from which the item is transferred) and the destination instance (the subinventory instance record to which the item is transferred) is searched on the following criteria: Inventory Item, Inventory Organization, Subinventory, Units of Measure, Instance Usage Code, Revision, Inventory Locator, Lot Number (if applicable).
  • If both source and the destination records are found, then they are updated with transaction quantity. If either of the instance records is not found, then it is created.
For more information on how subinventory transfer are processed, see Oracle Inventory User's Guide:

About Inter-Organization Transfers

An inter-organization transfer moves items between organizations. This transfer can be either a direct or an in-transit transaction.

Direct versus In-Transit Transactions

In a direct transaction, a shipping organization transfers an item into a subinventory in the receiving organization. For this reason, the application treats a direct inter-organization transfer the same as a subinventory transfer.
For an in-transit transaction, the monetary value of the transferred item is deposited in an in-transit account, and the inventory account of the shipping organization receives credit for the item. Upon receipt of the transferred item, the receiving organization must perform a receipt transaction to bring the item into its inventory. The receipt transaction credits the in-transit account and debits the inventory account of the receiving organization.

Inter-Organization Transfers Tied to Oracle Inventory

Oracle Asset Tracking uses the same process that Oracle Inventory uses to transfer materials between organizations. Before items can be transferred, items must be defined and subinventories must be created in Oracle Inventory.
If the organization from which the item is being transferred does not allow negative inventory balances, then it must contain sufficient on-hand inventory for the transaction to occur.

Initial Step to Processing Inter-organization Transfers

If the inter-organization transfer is a direct transaction, then the application treats it the same as a subinventory transfer.
If the inter-organization transfer is an in-transit transaction, then the application searches the database for the From record associated with the item. This record must have a status of In Inventory or In Depreciable Inventory and a transaction status of Complete. If the item fails to meet these conditions, then it generates an error message.
There is no difference, from an Oracle Asset Tracking perspective, between a FOB Shipment or FOB Receipt type transaction.

Inter-Organization Transfers of Items with Serial Numbers

For an in-transit transfer of an item with a serial number from one organization to another, the application follows these steps:
  1. In-Transit Shipment
    The source record for the From organization and subinventory is located. Then it is updated with the To organization and the Oracle Asset Tracking usage code of IN TRANSIT. The subinventory information is removed from the record. If the transaction is successfully processed, then transaction records are created to store the transaction history
  2. In-Transit Receipt
    When the item reaches its destination, someone enters a receipt transaction for the item. The IN TRANSIT record with the To organization is located, and it is updated with the usage code IN INVENTORY.

Inter-Organization Transfers of Items without Serial Numbers

For an In-Transit transfer of an item without a serial number from one organization to another, the application follows these steps:
  1. In-Transit Shipment
    The source record for the From organization and subinventory is located, and the quantity is subtracted by the transaction quantity. An IN TRANSIT record is then created with the destination organization and transaction quantity. No subinventory information is kept in this record. If such a record already exists, then the quantity is increased by the transaction quantity.
  2. In-Transit Receipt
    When the item reaches its destination, someone enters a receipt transaction for the item. The IN TRANSIT record with the To organization is located. The quantity is subtracted with the transaction quantity. The destination record is located based on the To organization and subinventory. If the record exists, then the quantity is increased by the transaction quantity. If there is no such record, then a new destination record is created. If the transaction is successfully processed, then transaction records are created to store the transaction history.

To and From Subinventory Type Must Be Compatible

A subinventory may have a type of either asset or expense.
For Oracle Asset Tracking, the only type of item transfer allowed is the following:
  • From asset subinventory to asset subinventory
If the type of the From subinventory does not match the type of the To subinventory, then the application generates an error.

About Physical Cycle Counts

A physical inventory occurs when a person verifies that units exist physically and that the quantities match the on-hand records in Oracle Asset Tracking. Based on the results of the physical inventory, Oracle Asset Tracking supports adjustments that you make to your inventory balances. Depending on the type of inventory adjustment necessary, Oracle Asset Tracking treats these adjustments like a miscellaneous transaction. For example, if the item quantity increases after physical count, then there will be miscellaneous receipt transaction.

About Asset Handling for Internal Sales Orders

Oracle Asset Tracking performs cost and unit adjustments to assets when they are moved using internal sales orders. This handling applies to depreciable and normal items that have assets associated with them.
The integration of Oracle Asset Tracking with Oracle Assets supports the following Oracle Inventory transactions. Item definition as Depreciable or Normal must be kept at the master organization level and must not be changed at organization level.
  • Direct Inter-Organization Transfers
  • In-Transit Inter-Organization Transfers
  • Direct Internal Sales Order
  • In-Transit Internal Sales Order
In the case of in-transit shipments, item instances are in transit until they are received into a receiving organization. Such in-transit transactions interact with Oracle Assets only upon receipt of the material or item in the receiving inventory organization.
Oracle Asset Tracking does not maintain Instance-Asset links for in-transit instances.
Oracle Asset Tracking performs the following updates based on the item definition:
  • Depreciable Items: Update the fixed asset location if it is different from the source and destination location. If the asset category is different, then update the asset cost and units of the source asset and create or update the destination asset.
  • Normal Items with Assets: In case of redeployment, serialized normal items have fixed assets associated with them. If any of the inter organization transactions are performed, then these transactions are also required to interact with Oracle Assets. Update the fixed asset location if it is different from the source and destination location. If the asset category is different, then update the asset cost and units of the source asset and create or update the destination asset.
All of the inter-organization transfer and internal sales order transactions are processed by Oracle Asset Tracking-Oracle Assets integration as asset move transactions.
Typically all of the transactions and various scenarios can be broadly categorized as indicated in the following table.

Case # Shipping Org "Inventory" Usage Code Instance Serialized or Non-Serialized Receiving Org "Inventory" Usage Code Instance Serialized or Non-Serialized Actions with Oracle Asset Tracking and Oracle Assets
1 Serialized Serialized The application performs an Oracle Assets location change if the source and destination asset locations are different or if the source asset category is different from the destination asset category. Then it retires the source asset and creates a new asset in the destination organization.
2 Serialized Non-Serialized The application retires the source serialized instances. Then it creates or updates the destination asset.
3 Non-Serialized Serialized The application performs asset cost and unit adjustment on the source asset and creates serialized destination assets.
4 Non-Serialized Non-Serialized The application performs an Oracle Assets location change if the source and destination asset location are different or if the source asset category is different from the destination asset category. Then it performs negative cost adjustment on the source asset and creates or updates the destination asset.
To avoid inventory costing conflicts for assets, receive and store capitalized items in separate expense-type subinventory. In addition, keep the inventory asset flag cleared if you do not wish to create assets upon miscellaneous receipts.

Explaining Other Inventory Transactions

Assets are capitalized either at the time of receipt or after commissioning in-service. They move in and out of inventory for various reasons, such as repairs, re-deployments, or storage. Oracle Asset Tracking supports all inventory transactions for the assets. This includes the Work in Process (WIP) transactions.
If an assembly is built using a WIP standard or non-standard job, then the cost of all the non-capitalized components are collected to a single fixed asset. The capitalized components carry the value in fixed assets. If the non-component is removed from the assembly, then the cost of assembly is reduced by the current inventory cost of a component. As a result, the component is added to the inventory stock with the current inventory value, depending on the costing method used. If a capitalized component is removed then there is no financial effect on the parent or component asset.
The following table describes some inventory transactions and the action to the associated fixed asset:

Inventory Transaction Item is Depreciable Asset Has a Fixed Asset Action to the Associated Fixed Asset
WIP Component Issue
WIP Negative Component Return
Yes or No Yes Updates the fixed asset location to point to the WIP fixed asset location.
WIP Assembly Completion Yes No Creates fixed asset upon receipt into inventory based on WIP cost of the top assembly. The NBV of capitalized components will not be included in this cost.
WIP Assembly Completion No No No action
WIP Assembly Return Yes or No Yes Updates the fixed asset location of the top assembly to point to the WIP fa location.
WIP Negative Component Issue Yes or No Yes Updates the fixed asset location to point to the inventory fa location.
WIP Negative Component Issue Yes No Creates fixed asset at inventory fa location with inventory cost.
Project Contract IssueSales Order Issue Yes or No Yes Retires the fixed asset
Project Borrow
Project Transfer
Project Payback
Sales Order Pick
Cycle Count Transfer
Yes or No Yes Updates the fixed asset location to point to new sub inventory fa location.
Cycle Count Adjustments
Internal Requisition Receipt Adjustments
Shipment Receipt Adjustments
Yes Yes For positive adjustment transactions, performs unit and cost adjustments to the existing fixed assets or if fixed asset does not exists, creates fixed assets.
For negative adjustments, performs prorated negative unit and cost adjustments.
Cycle Count Adjustments
Internal Requisition Receipt Adjustments
Shipment Receipt Adjustments
No Yes For positive adjustment transactions, there is no action.
For negative adjustments, performs prorated negative unit and cost adjustments.
Lot Split
Lot Merge
Yes or No Yes No fixed asset updates are required.
RMA Receipt Yes No Creates fixed asset based on inventory cost.
RMA Receipt No Yes Updates fixed asset location to point to inventory location.
RMA Return Yes or No Yes Retires the fixes asset.

Understanding Asset Deployment

This chapter covers the following topics:

Overview of Understanding Asset Deployment

This topic group describes how to deploy assets using Oracle Asset Tracking.

About Asset Deployment

Asset deployment is a capability of Oracle Asset Tracking. The purpose of asset deployment is to signal the completion of operational tasks, to update item statuses in Oracle Install Base, and to initiate the asset creation and update processes in Oracle Projects and Oracle Assets.
Oracle Asset Tracking can be integrated with external systems. Oracle Asset Tracking provides an interface API as well as the Asset Deployment window for an external workforce management application to transmit transaction parameters to Oracle Asset Tracking.
For an overview of the asset operations and their dependence on Oracle Asset Tracking usage codes, see About Asset Processing for Normal and Depreciable Inventory Items.
From a user perspective, usage codes no longer appear. The user views operational status codes.
Asset deployment topics are as follows:

About Asset Deployment Transactions

The diagram that follows shows the life cycle flow of an item instance, with the asset deployment and Oracle application transactions that change the Oracle Asset Tracking usage codes for the item instance. Asset deployment transactions in item instance life cycle flow.
Asset Deployment Actions in Item Instance Life Cycle Flow
the picture is described in the document text

About Partial Installation and In-Service Conditions

When material is issued from inventory to a project, a cost expenditure is created in Oracle Projects that includes the quantity and the cost of material. Oracle Asset Tracking creates the appropriate expenditures in Oracle Projects after the equipment is placed in service. Further processing by Oracle Projects programs creates assets based on these expenditures.
You can capitalize some or all of the material assigned to a project. For example, assume that ten items have been issued to the project. A technician installs five and then places only three items in service. This means that only three (or a cost expenditure equal to 3 times the unit cost) are capitalized immediately. Expenditure will be capitalized only after the associated equipment (asset) is deployed in service.

Selecting the Location for the Item Instance

In all the asset deployment transactions, to accurately track an item instance, you must select the current location of the item instance.
There are a number of options that are common to all the selections for the location of an item instance.
The value for the location can be an internal site or an external party site.
When entering location information, you must first select a Location Type from the following list:
  • HZ Location
  • Internal Site
  • Party Site
If you select either HZ Location or Internal Site for the Location Type, then you must select a location into the Location field. The list of values for the Location field depends on your selection of Location Type:
  • If you select HZ Location, then the list of values for the Location field displays the Addresses as set up in the Trading Community Architecture (TCA) locations.
  • If you select Internal Site, then the list of values for the Location field shows only locations related to an enterprise organization.
If you select Party Site for the Location Type, then you must select a party into the Party field.

Using the Item Instance Deployment Page

Use this procedure to use the Item Instance Deployment page.
To use the Item Instance Deployment page
  1. Using the Asset Tracking Super User responsibility, navigate to Assets and then select Deployment.
    The Item Instance Deployment page appears.
  2. Select an action from the list.
    You can choose one of the following actions:
    • Install: You can install material issued to the project at a specific location.
      When an instance is issued to a project, the operational status code is Not Used. After you install it, the application updates the operational status code to Installed.
    • Move: You can move an item instance from one location to another.
      The operational status does not change.
    • Project Transfer: You can transfer an item instance from one project to another if the operational status is Not Used or Installed.
      Oracle Projects reverses the expenditure item from the origin project, using the Net Zero Adjustment functionality, and then creates a new expenditure item for the destination project.
    • Put Into Service: You can put an item in service if it is still in a project (operation status Not Used), Installed, or Out Of Service.
    • Retirement: You can retire an item instance operationally (the instance is expired), or both operationally and functionally (the corresponding fixed asset is also retired from the books). You can enter the removal costs and the proceeds from sales only if the item instance is capitalized.
    • Take Out Of Service: You can take an item instance out of service only if the operational status is Not Used or In Service.
    • Un-Install: You can un-install an asset if the operational status is Installed.
  3. Enter your search criteria. You can limit the search results by entering data into the following fields:
    • Item Instance
    • Item
    • Asset Number
    • Purchase Order Number
    • External Reference
    • Serial Number
    • Current Location Type
    • Operational Status
    • System
  4. Click the Go button.
    The search results appear in the lower portion of the page.
    Note: If you want to change your search criteria, then click the Clear button and enter the new criteria.
  5. To perform an action:
    1. Select the associated checkbox for a row in the results table.
      Note: You may select more than one.
    2. Click the button in the Select Object block.
      Note: The button that you see in the Select Object block is tied to the action that you selected for your search. For example, if you selected the action Move, then the Move button appears in the Select Object block.
      The page associated with the action that you selected appears, For example, if you selected the action Move, then the Move: Item Instance page appears.
  6. Update the fields for the action that you selected. The following provides an overview of each of the action detail pages.
    • Install: Item Instance
      1. Enter a value in the Source Reference Number field.
      2. Enter a date in the Source Reference Date field.
      3. Update the number in the Transaction Quantity field. The transaction quantity cannot exceed the actual quantity.
      4. Select a value from the Location Type LOV.
      5. Select a value from the Location LOV.
    • Move: Item Instance
      1. Enter a value in the Source Reference Number field.
      2. Enter a date in the Source Reference Date field.
      3. Update the number in the Transaction Quantity field. The transaction quantity cannot exceed the actual quantity.
      4. Select a value from the Location Type LOV.
      5. Select a value from the Location LOV.
    • Project Transfer: Item Instance
      1. Enter a value in the Source Reference Number field.
      2. Enter a date in the Source Reference Date field.
      3. Update the number in the Transaction Quantity field. The transaction quantity cannot exceed the actual quantity.
      4. Select a value from the To Project Number LOV.
      5. Select a value from the To Task Number LOV.
    • Put Into Service: Item Instance
      1. Enter a value in the Source Reference Number field.
      2. Enter a date in the Source Reference Date field.
      3. Update the number in the Transaction Quantity field. The transaction quantity cannot exceed the actual quantity.
      4. Enter a date in the Placed Into Service field.
    • Retirement: Item Instance
      1. Enter a value in the Source Reference Number field.
      2. Enter a date in the Source Reference Date field.
      3. Update the number in the Transaction Quantity field. The transaction quantity cannot exceed the actual quantity.
      4. Enter an amount in the Cost of Removal field.
      5. Enter an amount in the Proceeds of Sale field.
      6. Select the Operational check box, if appropriate.
      7. Select the Financial check box, if appropriate.
      8. Select an asset from the Asset Number LOV.
      9. Enter a date in the Retirement Date field.
    • Take Out Of Service: Item Instance
      1. Enter a value in the Source Reference Number field.
      2. Enter a date in the Source Reference Date field.
      3. Update the number in the Transaction Quantity field. The transaction quantity cannot exceed the actual quantity.
    • Un-Install: Item Instance
      1. Enter a value in the Source Reference Number field.
      2. Enter a date in the Source Reference Date field.
      3. Update the number in the Transaction Quantity field. The transaction quantity cannot exceed the actual quantity.
  7. Click the Apply button.
    A confirmation message appears.
  8. Click the Done button to return to the Deployment Search page.

    Understanding Field Service Integration

    Overview of Understanding Field Service Integration

    This topic provides an understanding of the interaction between Oracle Asset Tracking and Oracle Field Service, as well as the functionality of Oracle Field Service.

    About Field Service Integration

    With Oracle Field Service you can create service requests and tasks for internal assets. Oracle Asset Tracking provides Oracle Field Service with the complete service history for both customer and internal assets. When Field Service debrief transactions are captured as part of the item instance transaction history, Oracle Asset Tracking captures the associated service request and task. It also tracks the date and time an asset is in or out of service. In addition, Oracle Asset Tracking can update the operation status of a recovered asset to Out of Service. All Oracle Asset Tracking deployment transactions can be performed from Oracle Field Service. Please refer to the section About Asset Deployment for more details.
    For more information on Oracle Field Service refer to the Oracle Field Service User Guide.

    Viewing Service Request Numbers and Task Numbers

    Use this procedure to view service request numbers and task numbers in the transactions history of Oracle Asset Tracking.
    Prerequisite:
    You must have an asset with an associated service request or task number.
    To view service request numbers and task numbers
  9. From the Asset Tracking Super User responsibility, navigate to Transactions and then select View Transactions.
  10. Query the transaction for which you want to view the service request or task number.
  11. Find the service request or task number within the query results table:

    Overview of Understanding Projects Integration

    This topic provides an understanding of the interaction between Oracle Asset Tracking and Oracle Projects, as well as the functionality of Oracle Projects.

    How Purchase Order Receipts Flow into Project Transactions

    The flow of purchase order receipts starts with the creation of a purchase order. Items against the purchase order are then received into the project. The Oracle Asset Tracking purchase order receipt package validates the receipt data against the Oracle Install Base repository and creates or updates the repository instance depending upon the physical attributes of the instance.
  12. For non-serialized items, physical attributes are combinations of values for Inventory Item, Project ID, Task ID, and Instance Status. If any values of these attributes are different, then the application creates a new instance in Oracle Install Base. If these attributes match, then the application adds the new receipt to the same instance.
  13. For serialized items, Oracle Install Base always creates a new instance.
    The following figure shows the factors that determine how an item instance is created or updated during the Oracle Projects transactions which affect Oracle Asset Tracking.
    Item Instance Processing in Oracle Projects Transactions
    the picture is described in the document text
  14. During the process of creating purchase orders for expense items, that is, receipt into project, you must check the Accrue on Receipt flag in the purchase order shipment. Project information can be captured in the distribution record only when the destination type is Expense. Accrual at period end is not supported.
  15. Run the PRC Transaction Import process to create project expenditures after receipt is complete. Use the Expenditure Inquiry window in Oracle Projects to view the expenditures.
  16. For a depreciable item, an asset is created upon receipt. Therefore, the cost is transferred from Oracle Assets to Oracle General Ledger and not from Oracle Projects. To create mass additions in Oracle Assets, you must run the Create Assets – Interface Inventory Transactions to Oracle Assets concurrent program.

Receiving Items Directly into an Oracle Project

Use the following procedure to receive an item into an operating project.
Note: A depreciable item can also be received directly into a project.
Prerequisites
The associated purchase order must exist in Oracle Purchasing with a status of Approved. The purchase order line must include:
  • The project and task number referenced in the purchase order distribution.
  • A purchase order shipment, which is marked as Accrue on Receipt.
  • A purchase order distribution with the destination type Expense.
  • Items on the purchase order should have an asset category tied to them in the item definition of the organization where they are received. This asset category should be assigned to the Asset Book specified in the profile CSE: Book Type Code.
The item number must be defined in Oracle Inventory. The project must be defined with a status of Active.
To receive items directly into an Oracle Project
  1. From the Inventory responsibility, navigate to Transactions. Select Receiving and then select Receipts.
    The Organizations window opens.
  2. Choose your organization from the Organizations window, and click Find.
  3. In the Find Expected Receipts window, enter any criteria that identify the items that you are receiving such as the purchase order number and the item number, and click Find.
    The Receipt Header and Receipt Lines open to display items that match the criteria entered.
  4. In Receipt Header, enter the packing slip number and any other pertinent information.
  5. Verify that the Receipt line has a value for Deliver-to location.
    When project information has been entered on the purchase order, the Deliver-to location is defined and appears on this Receipt line.
    Note: The Deliver-to location must be set up in the Oracle Asset Tracking Locations window and have an associated fixed asset location.
  6. For serialized items, capture serial numbers in the Lot/Serial window.
  7. Click Save to receive the item into the project and commit the receipt transaction.
    The application looks for an existing record for the item. If it locates a record and the receipt transaction has processed successfully, then it updates the item record with the quantity received.
    If the application does not find an existing record, then it creates one for the receipt. The application sets the Oracle Asset Tracking usage code to In Inventory and its Oracle Install Base transaction status to Complete.

About Transaction Sources for Project Import

Transaction sources identify the source of external transactions that you import into Oracle Projects using Transaction Import. For example, you can define the transaction sourcePayroll to identify expenditure items imported from an external payroll system. Transaction Import imports the transactions and creates corresponding expenditure records in the Oracle Projects expenditure tables. The following are Oracle Asset Tracking transaction sources:
  • CSE_INV_ISSUE: Use this transaction for importing expenditures of type Issue to Project for a normal item
  • CSE_INV_ISSUE_DEPR: Use this transaction for importing expenditures of type Issue to Project for a depreciable item
  • CSE_IPV_ADJUSTMENT: Use this transaction for cost to be adjusted to the project
  • CSE_IPV_ADJUSTMENT_DEPR: Use this transaction for cost to be adjusted to the asset
  • CSE_PO_RECEIPT: Use this transaction for type Receipt into Project for a normal item
  • CSE_PO_RECEIPT_DEPR: Use this transaction for type Receipt into Project for a depreciable item
  • INVENTORY MISC: Use this transaction for miscellaneous transactions such as Miscellaneous Issue and Miscellaneous Receipt

About Expenditure Inquiry

After the expenditure records are created through Transaction Import, use the Expenditure Inquiry window to review a project's expenditure items. You can see the amount and type of expenditure items charged to a project, how much revenue has accrued for an expenditure item, and other information about the project's expenditure items. For normal items that came through inventory, the expenditures are not created until the concurrent process PRC Distribute Usage and Miscellaneous Costs is run.
For more information, see Oracle Projects Implementation Guide.

About Asset Creation

After performing the purchase order receipt, the following steps are required to create assets in Oracle Assets:
  1. Run the Oracle Projects program PRC: Transaction Import. This program interfaces the PA transaction interface data that was created during the purchase order receipt process and creates expenditure items in the projects application for the project and task specified in the purchase order distribution.
  2. Perform an Install transaction for the received item/serial using the Deployment Transactions page. The application captures the installation location information and updates the item instance with the operational status Installed.
  3. Perform an In Service transaction for the installed item/serial using the Deployment Transactions page. The application captures the date that the item is placed in service and qualifies this item/serial to be capitalized. The application item instance updates with the operational status of In Service.
  4. Verify that the Purchase order receipt transaction is accounted in sub-ledger accounting. Run the Oracle Cost Management program Create Accounting from the Cost Management - SLA responsibility for the process category Receiving.
  5. Run the Oracle Asset Tracking program Interface In-Service transactions to Oracle Projects for the project and task. This program reverses the originally created expenditure items using the net-zero adjustment functionality and recreates the expenditure items in PA transaction interface with all the attributes (item, serial, book type, asset category, location and product classification) required by the CRL process to complete the capitalization process.
    Note: Oracle Asset Tracking leverages the functionality of CRL Projects to capitalize project related expenses.
  6. Run the Oracle Projects program PRC: Transaction Import. This interfaces the newly created PA transaction interface data to expenditure items.
  7. Run the Oracle Asset Tracking program Create Asset Headers in Oracle Projects - Normal Items. This program automates the creation of a project asset. After this process is completed, you can navigate to the capital projects form and query up the project to see the project assets that have been created.
  8. Run the Oracle Projects program PRC: Interface Assets to Oracle Asset. This program ties the expenditure items that you created in step 6 to the asset headers that you created in step 7 and creates project asset lines. The project asset is ready to be interfaced to Oracle Assets.
  9. Run the Oracle Assets request set Post Mass Additions.
    This program interfaces the project asset information to Oracle Assets by creating records in FA_MASS_ADDITIONS.
  10. Run the Oracle Assets request set Post Mass Additions.
See also About Asset Processing for Normal and Depreciable Inventory Items.
The topics in this section are the following:

Running the PRC: Generate Asset Lines for a Single Project Program

Use this concurrent program to generate summary asset lines for a single project.
To run the PRC: Generate Asset Lines for a Single Project
  1. From the CRL 11i Projects responsibility, navigate to Projects and select Other, Requests, and then select Run.
  2. Choose to run a single report.
  3. In the Name field, choose PRC: Generate Asset Lines for a Single Project
  4. Click Submit.
  5. The application assigns an ID number to your request. Use the ID number to find your request in the View Request window.
Related Topics
Viewing Request Results

Running the PRC: Interface Assets to Oracle Asset Program

Use this concurrent program to send valid asset lines to Oracle Assets to become fixed assets. The process creates one mass addition line in Oracle Assets for each asset line in Oracle Projects, assigning the asset information you entered for the CIP asset to the mass addition line in Oracle Assets.
To run PRC: Interface Assets to Oracle Asset
  1. From the CRL 11i Projects responsibility, navigate to Projects and select Other, Requests, and then select Run.
  2. Choose to run a single report.
  3. In the Name field, choose PRC: Interface Assets to Oracle Asset.
  4. Click Submit.
    The application assigns an ID number to your request. Use the ID number to find your request in the View Request window.

    Understanding the Fixed Asset Architecture

    This chapter covers the following topics:
  5. Overview of Fixed Asset Architecture
  6. About Asset Processing in Oracle Asset Tracking
  7. About Asset-Related Processes in Oracle Asset Tracking
  8. Running the Create Assets Interface Inventory Transactions to Fixed Asset Program
  9. Running the Create Asset Headers in Oracle Projects - Normal Items Program
  10. Running the Interface Move Transactions to Oracle Assets Program
  11. About Asset Impact of a Miscellaneous Issue
  12. About Asset Impact of Subinventory Transfers
  13. About Asset Impact of Inter-Organizational Transfers
  14. About Asset Impact of Physical Inventory and Cycle Count Adjustments
  15. Case Study
  16. Understanding the CLEI
  17. Overview of Retirements
  18. Associating a Fixed Asset to an Item Instance
  19. Viewing Asset Relationships Graphically

Overview of Fixed Asset Architecture

This topic provides an understanding of the interaction between Oracle Asset Tracking and Oracle Assets.

About Asset Processing in Oracle Asset Tracking

Oracle Asset Tracking can interface assets directly to Oracle Assets by using concurrent programs. After an asset is created, any physical movement to the associated item automatically updates the financial records based on the synchronization flag set for the instance. This reduces the amount of manual intervention required to maintain your financial system.
For example, when a depreciable item is received, run the Create Assets: Interface Inventory Transactions to Fixed Asset program to create an asset. Now the asset is linked with the item. Suppose an item is moved to a different organization. Oracle Asset Tracking checks for necessary changes for asset location, and asset category if applicable. Accordingly, Oracle Asset Tracking makes the necessary changes to the asset, which may involve retiring an existing asset and creating a new asset in the new organization.
Oracle Asset Tracking also maintains the history of all the transactions performed. This gives you total visibility of all items and their related assets.
When Oracle Asset Tracking creates a transaction that has a financial, asset-related impact, the transaction is stored in a transaction table with an Oracle Install Base status of Pending. Later, a concurrent program reads the transaction log and processes all the transactions in sequence. The Oracle Asset Tracking concurrent program processes each transaction in the transaction table one by one. The program determines the appropriate asset record if applicable, inserts a record into the fixed asset interface table, and then changes the Oracle Install Base status to Complete. If any of these processes fails, then the status remains at the pending stage.
A user can review the asset records in the asset interface table if necessary before posting them to the asset book. For more information, refer to the section on reviewing mass additions lines in the Oracle Assets User Guide. A tieback from Oracle Assets returns the asset ID to the Oracle Asset Tracking business logic or client extension and updates the Oracle Install Base Instance-Asset assignment table.

About Asset-Related Processes in Oracle Asset Tracking

The following table shows the concurrent programs and request sets in Oracle Asset Tracking that interface with Oracle Assets to make the asset-related changes in Oracle Assets.
Processes to Create and Update Oracle Assets
Name of the Program or Report Description
Create Assets: Interface Inventory transactions to Fixed Asset This is a concurrent program with the following features:
  • Creates an asset or cost adjustment when a depreciable item is received either in Oracle Inventory or Oracle Projects
  • Creates an asset or cost adjustment when a normal item is issued to a field location directly without using projects
Create Asset Headers in Oracle Projects - Normal Items Program Note: This program was formerly called Asset Header for Normal Item Report.
This concurrent program creates an asset header for capitalized project expenditures. Asset creation is based on item, serial (if serialized item), asset category, date placed into service, and product classification.
Interface In-Service Transactions to Oracle Projects - Normal Items This concurrent program should be run after deployment transactions on a project instance. It writes records into the PA interface table PA_TRANSACTIONS_INTERFACE_ALL and changes the status of the In Service transactions to Interfaced to PA
Interface Move Transactions to Oracle Assets Note: This program was formerly called Interface Move and Misc Transactions to Fixed Assets - Report
This concurrent program processes any item moves like subinventory transfer, inter-organization transfer, miscellaneous issues, and physical inventory adjustments for which an asset already exists.
Interface Unit Adjustments to Oracle Assets - Normal Items When Oracle Purchasing receives a normal/non-serialized item into a project, a fixed asset is created. When another receipt happens for the same item into the same project this concurrent program ensures the receipt is in sync for both value and quantity. Oracle Asset Tracking and Oracle Projects adjust the existing fixed asset only when the second receipt happens within the same fixed asset accounting period of the first receipt.
The topics in this section are the following:

Running the Create Assets Interface Inventory Transactions to Fixed Asset Program

The Create Assets: Interface Inventory Transactions to Fixed Asset concurrent program processes the following transactions to create an asset for a depreciable item.
Transactions for the Create Assets Program
Install Base Transaction Source Description Install Base Transaction Status Meaning
PO_RECEIPT_INTO_INVENTORY Receipt of depreciable item into Inventory PENDING Needs further fixed asset/project accounting processing
PO_RECEIPT_INTO_PROJECT Receipt of depreciable item into Projects PENDING Needs further fixed asset/project accounting processing
Miscellaneous/Move Order Issue to an HZ Location Miscellaneous/move order issue to an HZ location PENDING Needs further fixed asset/project accounting processing
Perform the following steps after receipt of a depreciable item to create an asset:
To run the Create Assets Interface Inventory Transactions to Fixed Asset Program
  1. Run the Create Assets: Interface Inventory Transactions to Fixed Asset from Oracle Asset Tracking.
    Note: Before running this program verify that the subledger accounting program has been run for the transactions.
  2. Run Post Mass Additions from Oracle Assets.

    • For project related receipts, the billable flag is already set to NO to prevent account information from going to general ledger and thus avoid double accounting.
    • Because Ship to Location is a mandatory field on a purchase order, the corresponding fixed asset location is used to create an asset. The asset category is extracted from the item definition.
    • The fixed asset book type is used from the Oracle Asset Tracking profile option CSE:FA Book Type Code. You can now set up this profile at two levels: site and organization. This enables different organizations within the site to have their own books. The profile selects the FA book as follows:
      • If there is a different book at the site level and at the organization level, the book at the organization level is selected.
      • If there is no book set at the organization level, then the book at the site level is selected.
    • In the case of serialized item instances, a new asset is always created if the Create Unique Asset For parameter is set to For Each Serialized Instance within the Install Parameters form.
      For non-serialized item instances a new asset is created. If one exists already with identical attributes then the application updates the asset.
    • If the asset already exists for that category, then the application adjusts the cost and unit.
    • After the post mass additions program is complete, the asset number is linked to the item instance.

Running the Create Asset Headers in Oracle Projects - Normal Items Program

The Create Asset Headers in Oracle Projects - Normal Items concurrent program processes the following transactions to create an asset for normal items put in service.
Transactions for the Create Asset Headers in Oracle Projects - Normal Items Program
Install Base Transaction Source Description Install Base Transaction Status Meaning
PROJECT_ITEM_IN_SERVICE Item put in service INTERFACE_TO_PA Needs further fixed asset/project accounting processing.
Prerequisite
Perform the following steps to create assets for a normal item that has expenditures imported into projects and has been installed and put into service:
To run the Create Asset Headers in Oracle Projects - Normal Items program
  1. Run the concurrent program Interface In-Service Transactions to Oracle Projects - Normal Items.
  2. Run the concurrent program PRC: Transaction Import to reverse already created expenditures and create new ones with attributes captured from deployment.
  3. Run the concurrent program Create Asset Headers in Oracle Projects - Normal Items.
  4. Run the concurrent program PRC: Generate Asset Lines for a Single Project from Oracle Projects.
  5. Run the concurrent program PRC: Interface Asset to Oracle Assets from Oracle Projects.
  6. Run the concurrent request set Post Mass Additions from Oracle Assets.

    • An item must be issued to a project or received in the project before installing and putting it in service. Also make sure to create expenditures before installing. This is a prerequisite for asset creation. Expenditures are created by running the PRC: Transaction Import program after an issue or receipt into project that can be capitalized. The details are covered in the Projects Integration section.
    • In the case of serialized item instances, a new asset is not always created. There is a parameter setting in the Install Parameters form called Create Unique Asset For, which controls whether a new asset is created for serialized item instances. The values are Each Serialized Item Instance and Each Item. If you choose Each Serialized Item Instance, then for every serial number received a new fixed asset is created. If you choose Each Item, then serial controlled items are simply treated as non-serialized items. For non-serialized items, a new asset is created based on various attributes such as item, asset category, location, date placed into service, and product classification. Also, for non-serial items and the previously mentioned grouping, receipts made in each fixed asset period are defined in the asset book creating an unique receipt. For every fixed asset period boundary an unique asset appears.
    • If the asset already exists for that category, then the program performs cost adjustment and unit adjustment. The asset can be interfaced to Oracle Assets by running the program Interface Unit Adjustments to Oracle Assets - Normal Items.
    • A fixed asset location corresponding to the install location is used to create an asset. Asset category is extracted from the item definition.
    • The fixed asset book type is used from the Oracle Asset Tracking profile option CSE:FA Book Type Code. You can now set up this profile at two levels: site and organization. This enables different organizations within the site to have their own books. The profile selects the FA book as follows:
      • If there is a different book at the site level and at the organization level, the book at the organization is selected.
      • If there is no book set at the organization level, then the book at the site level is selected.
    • After successful completion of Post Mass Additions, the asset is created or updated for the new in-service item instance.

Running the Interface Move Transactions to Oracle Assets Program

The Interface Move Transactions to Oracle Assets concurrent program is generally run after an asset has been created and is used to update the asset-related information associated with Oracle Asset Tracking.
If the program is run, and any assets that it expects to update have not yet been created, then the update transaction information is help pending, so that it can be processed later, after the necessary asset creation program or request set has been run.
The Interface Move Transactions to Oracle Assets concurrent program processes the following transactions for each asset associated with the item instance that is transacted.
Transactions Processed by the Interface Move Transactions to Oracle Assets Program
Install Base Transaction Source Description Install Base Transaction Status Meaning
MISC_ISSUE Miscellaneous issue of item out of inventory PENDING Needs further fixed asset/project accounting processing
PROJECT_ITEM_UNSTALLED Item is Un-installed from the project PENDING Needs further fixed asset/project accounting processing
MISC_RECEIPT_FROM_PROJECT Item is moved from Projects into Inventory PENDING Needs further fixed asset/project accounting processing
SUBINVENTORY_TRANSFER Transfer of an item within the organization from one subinventory to another PENDING Needs further fixed asset/project accounting processing
INTERORG_TRANSFER Transfer of an item from one organization to the other PENDING Needs further fixed asset/project accounting processing
MOVE_ORDER_ISSUE_TO_PROJECT Item issued to the project PENDING Needs further fixed asset/project accounting processing
PROJECT_ITEM_INSTALLED Equipment Installed PENDING Needs further fixed asset/project accounting processing
PROJECT_ITEM_IN_SERVICE Equipment In-service PENDING Needs further fixed asset/project accounting processing
IN_SERVICE Asset is put in service PENDING Needs further fixed asset/project accounting processing
PHYSICAL_INVENTORY_CYCLE_COUNT Asset adjustment when the item is adjusted in inventory in physical count PENDING Needs further fixed asset/project accounting processing
ISO_SHIPMENT Item is shipped through internal order shipment PENDING Needs further fixed asset processing
OM_SHIPMENT Item is shipped through order management shipment PENDING Needs further fixed asset processing
RMA_RECEIPT Item is returned using order management PENDING Needs further fixed asset processing
Prerequisites
Generally, you must have run one of two concurrent processes depending on depreciable or normal item.
To run the Interface Move Transactions to Oracle Assets program
  1. Run the concurrent program Interface Move Transactions to Oracle Assets from Oracle Asset Tracking.
  2. Run Post Mass Additions from Oracle Assets.

    • In the case of a depreciable item, the movements listed in Table 5–4 are tracked because an asset is created upon item receipt. For a normal item, only asset item move transactions are tracked.
    • The program checks for any asset updates due to change in location. For example, when item is issued to the project, the location is changed from inventory to project location. If these locations belong to different fixed asset locations, then this change causes different distribution in the asset. Interface Move transactions to Fixed Asset process this change.
    • All the transactions are processed sequentially, because of dependence. If any dependent transaction is pending, then this transaction is skipped

About Asset Impact of a Miscellaneous Issue

For serialized items, when an item is issued out of inventory, the associated asset units and cost are both set to zero.
For non-serialized items, when an item is issued out of inventory, the associated asset units and cost are both reduced by the equivalent values in the transaction. Oracle Asset Tracking retires a field asset while processing a Miscellaneous Issue transaction.

About Asset Impact of Subinventory Transfers

When an item is transferred from one subinventory to another, the program changes fixed asset location which, in turn, changes the fixed asset distributions. The asset, however, remains the same.
In a situation where there exists more than one source record, the First-in-first-out method is adapted. If more than one destination asset record exists, then the asset period is matched to adjust the asset. When searching for the existing asset in the system, the program always looks to see if there exists a similar record under process. If it finds an exact match, then the record is skipped.
In a business rule dictates a change in location with a change in category, then you must modify the client extension. In that case, a new set asset is created for a serialized item. The original asset cost is updated to zero, and you have to retire the asset manually. Similar unit and cost adjustments are done in source and destination assets in the case of non-serialized items.

About Asset Impact of Inter-Organizational Transfers

When an item is transferred from one organization to another, the program changes fixed asset location which, in turn, changes the fixed asset distributions. The asset, however, remains the same. The transactions include IN_SERVICE, MISC_RECEIPT_FROM_PROJECT, PROJECT_ITEM_IN_SERVICE, and ISO_SHIPMENT.
  • Intra-asset: If only one source asset exists, and if the destination record has the same asset but the fixed asset location is different, then that is changed.
  • Inter-asset: If the source asset and the destination assets are different, then the program performs cost and unit adjustment for both assets.
  • If there is no destination asset, then the program creates a new asset with the transaction quantity and appropriate cost. Then the cost and unit adjustments are done for the source asset. In the case of serialized items, the asset location and category are updated if it is different in the receiving organization.
In a situation where more than one source record exists, the first-in-first-out method is adapted. If more than one destination asset record exists, then asset year is matched to adjust the asset. When searching for the existing asset in the system, the program always determines if a similar record exists under process. If it finds an exact match, then the record is skipped.
If your business rule dictates a change in location for a change in category, then you must modify the client extension. In that case, a new asset is created for a serialized item. The original asset cost is updated to zero, and you must retire the asset manually. Similar unit and cost adjustments are done in source and destination assets in the case of non-serialized items.

About Asset Impact of Physical Inventory and Cycle Count Adjustments

Depending upon the physical adjustment, a Physical Inventory and Cycle Count Adjustments transaction is treated the same as Miscellaneous Issue or Miscellaneous Receipt. For example, if an item quantity increases after a physical count, then a Miscellaneous Receipt transaction is performed, and the asset is adjusted or created accordingly.
After a Physical Inventory and Cycle Count Adjustments transaction, run the concurrent program Create Assets: Interface Inventory transactions to Fixed Asset and Interface Move Transactions to Fixed Assets - Report program. Finally, run the Post Mass Addition request set from Oracle Assets to complete the asset information update.

Case Study

The case study scenario consists of a number of item transactions, followed by the processing used to create and update the assets associated with the items.

Case Study Item Transaction Details

The following table describes the item transactions for this case study.
Case Study Item Transaction Details
Transaction Type Transaction ID Quantity Details
Receipt of Depreciable item D1 1 100 Item D1 in Organization A
Receipt of Normal item N1 2 100 Item N1 in Organization B
Inter-Organization Move 3 25 Item D1 from Org A to Org C
Receipt of Depreciable item D2 4 20 Item D2 in Organization A
Move Order Issue to Project 5 25 Item N1 from Organization B to Project P1
Equipment installed 6 15 Item N1 from Project P1 installed in field location F1
Equipment put in service 7 5 Item N1 put in service in field location F1
Equipment taken out of service 8 1 Item N1 taken out of service at field location F1
Item Move 9 1 Item N1 from field location F1 to field location F2
Equipment put back in service 10 1 Item N1 put in service in field location F2
The following shows the case study transactions related to the item organizations, project, and locations.
Case Study Transactions
the picture is described in the document text

Asset Processing Options

Oracle Asset Tracking processes three types of asset transaction, using the following processing units:

Case Study Asset Processing

  1. Run the Create Assets: Interface Inventory Transactions to Oracle Assets concurrent program. This selects transactions 1 and 4. It checks if assets already exist for items D1 and D2. If assets already exist for items D1 and D2, then the program performs unit and cost adjustments to the existing assets. Otherwise it creates new assets.
  2. Now, if you run the program Interface Move Transaction to Fixed Assets - Report, then only transaction 3 is selected and will be processed to make asset updates, assuming that an asset had been previously successfully created for item D1.
    Although transaction 10 is also an asset move, it is not selected this time. This is because Item N1 has not yet become an asset (you cannot create assets from normal items unless the items are issued to a project and put into service; or you can do a miscellaneous issue to HZ location).
  3. Run the concurrent programs available for creating assets for normal items. At this point, transaction 7 is selected and the asset header will be created. This will become an asset after running CRL programs for asset creation.
  4. Transaction 10, where the normal item N1 was put back in service in location F2, will be selected and processed only when you run the Interface Move Transactions to Fixed Assets Report program subsequently.
To ensure the proper order of the transactions, the program skips all the failed transaction records and their subsequent dependent transaction records.
For example, in the case study, assume that for some reason an asset was not created for item D1 in transaction 1 when the Depreciable Items - Asset Creation concurrent program was run.
Transaction 3 depends on transaction 1. If transaction 1 fails to create an asset, then transaction 3 will not be processed by the program Interface Move Transaction to Fixed Assets - Report.
Transaction 3 will be processed only when you perform the following processing sequence:
  1. Run the Depreciable Items - Asset Creation program, and check that you have successfully created an asset for the parent transaction 1.
  2. Run the Interface Move Transaction to Fixed Assets - Report program.

Understanding the CLEI

The Common Language Equipment Identifier (CLEI) is a vendor-specific, 10-character code. It is a standard used by the telecommunications industry for identifying and describing equipment. Because Oracle Asset Tracking captures the CLEI code in the lot field, items that have a CLEI code must be set to full lot control. If an item has no CLEI code, then it does not need lot control.
The supplier usually provides CLEI codes for the items that you purchase. When performing transactions, you can select CLEI codes from a list of values or you can enter new CLEI values directly into the Lot field.

Overview of Retirements

The process that Oracle Asset Tracking uses to retire and reinstate assets is the same as the process used in Oracle Assets. You can retire or reinstate partial or whole assets.
Before you retire an asset, you must first take it out of service. If an asset is retired, then Oracle Asset Tracking updates the status of the Instance-Asset link to Retired.
An asset must have a status of retired before it can be reinstated. An asset reinstatement reverses the operation of the Oracle Asset Tracking retirement logic. For the reinstatement, Oracle Asset Tracking updates the status of the Instance-Asset link to In Service.

Associating a Fixed Asset to an Item Instance

Use this procedure to associate an item instance to a fixed asset.
To associate a fixed asset to an item
  1. From the Asset Tracking Super User responsibility, navigate to Assets and then select Fixed Assets.
  2. Query an asset from Search page.
  3. Select an asset from the query results.
  4. From the Add Item Instances list, choose Select from Existing.
    Note: You can also create a new item instance or copy from an existing item instance, by selecting Create or Copy respectively.
  5. Click Go.
    The Search page appears.
  6. Query the item instance that you would like to associate to the fixed asset.
  7. Click Associate With Asset.
    A confirmation message appears indicating that item instances have been added to the fixed asset successfully.
    Note: You can also add an asset to an item instance from the Item Instance page by clicking the Add Assets button, which allows you to search for fixed assets to associate to the item instance.
    You can specify whether the item instance should be fully synchronized to the fixed asset by selecting the Enable Auto Update flag. When this flag is set, an item instance transaction creates an automatic update to the fixed asset. Otherwise, the fixed asset is not automatically updated.

Viewing Asset Relationships Graphically

Use this procedure to view asset relationships graphically.
  1. From the Asset Tracking Super User responsibility, navigate to Assets, and then select Item Instances.
  2. Query an asset from Search page.
  3. Select an asset from the query results.
  4. Click the View Relationship Graphically link in the Other Item Instance Details grid.
    the picture is described in the document text
  5. The Viewer opens, displaying the asset relationship in a graphical format:
    the picture is described in the document text
    Click any of the options on the right to change the graphic:

Adding Child Assets

You can also add child assets to the graphic:
  1. Click the Item Instance link at the top of the viewer page.
  2. Click the Return to Instance Search link at the bottom of the View Item Instance page.
  3. Click the Asset Update button for the item to which you want to add assets.
    If necessary, requery your results to select a different item.
  4. Click the Add Assets button.
    The Search Assets page appears.
  5. Search and select the assets that you want to add.
  6. Enter the quantity of the asset to be added.
  7. Click the Apply button.

Using Oracle Asset Tracking

This chapter covers the following topics:

Overview of Using Oracle Asset Tracking

This topic group provides process-oriented, task-based procedures for using the application to perform essential business tasks.

Submitting a Request

Use the Submit Request window to request one of the following reports and concurrent processes in Oracle Asset Tracking:

Viewing Request Results

When you request a report, Oracle Asset Tracking assigns a number to your request, runs the request, and stores the report. Use this procedure to view the report that you requested.
Prerequisites
You must request a report and save the request ID number.
To view request results
  1. Using the Asset Tracking Super User responsibility, navigate to Request and then select View.
  2. In the Find window, click Specific Request, and enter the ID number of the report that you wish to view.
  3. Click Find to retrieve the record.
  4. Click View Output to see the report online.
    If the report was completed with errors, then choose View Log to see a list of the errors that were encountered when your request was processed.
  5. To print the report, in the Menu Bar choose Tools and then select Reprint.
    Enter the number of copies to print, the printer, and the print style.
  6. Save.

Requesting an Assumed Loss Rate Report

Use this procedure to generate a list of items that have been issued to projects but have never been placed in service.
To request an assumed loss rate report
  1. Using the Asset Tracking Super User responsibility, navigate to Request and then select Run.
  2. Choose to run a single report.
  3. In the Name field, choose Assumed Loss Rate Report.
  4. Choose either Detail or Summary report type.
    The Detail type displays all individual transactions that meet your criteria. The Summary type provides only transaction totals.
  5. In the Parameters window, enter any needed information in the fields to define your search.
    • If you leave all optional fields blank, then the search returns all records across all organizations in the format that you requested.
    • Task Number: Enter the task number to further limit your search results to those items that have been issued to a particular task for a project.
    • Project Number: To limit your search results to those items that have been issued to a specific project, enter the project number here.
    • Organization: To limit your results to a particular organization, enter that organization here.
    • Inventory Item: To limit your search results to records for a specific item, enter the item number here.
  6. Click OK to close the Parameters window.
  7. Click Submit when you have finished defining the report.
  8. The application assigns an ID number to your request. Use the ID number to find your request in the View Request window.
Related Topics
Viewing Request Results

Requesting a Bill of Lading Report

Use this procedure to generate a bill of lading report, which displays the following:
  • Move order number
  • Transaction request date
  • Ship-to location name and address
  • Project number
  • Task number
  • Line item number
  • Item number
  • Item revision
  • Quantity requested and quantity shipped, both with totals for each item number
  • CLEI
  • Serial number
  • Vendor serial number
Follow these steps to generate a bill of lading.
Note: To print a bill of lading for a specific range of dates, enter a date in both the Data Required From and Data Required To fields. If you do not enter any dates in these fields, then the bill of lading report shows all move orders up to the system date.
If you enter a value for Task Number, then enter a corresponding Project Number.
To keep the report results to a manageable length, enter data for as many of the parameter fields as possible.
To request a bill of lading report
  1. Using the Asset Tracking Super User responsibility, navigate to Request and then select Run.
  2. Choose to run a single report.
  3. In the Name field, choose Bill of Lading Report.
    In the Parameters window, enter any necessary information in the fields to define your search.
    • If you leave all fields blank, then the report will include all move orders for the current day.
    • Move Order Number: To limit the report to a specific move order, enter that number here.
    • Organization Name: Limits the report to a specific organization.
    • Date From: To limits the report to all move orders generated from a specific date forward, enter that date here.
    • Date To: To limit the report to all move orders generated before a specific date, enter that date here.
    • Project Number: To limit the report to only those move orders for a specific project, enter that project number here.
    • Task Number: To limit the report to only those move orders for a particular project task, enter that task number here.
    • Location: To limit the report to only those move orders for a particular physical location, enter that location here.
  4. Click OK to close the Parameters window.
  5. Click Submit when you have finished defining the report.
    The application assigns an ID number to your request. Use the ID number to find your request in the View Request form.
Related Topics
Viewing Request Results

Adjusting the Invoice Price Variance

When assets are procured through Oracle Purchasing they are created with purchase order costs.
After the invoice is created, any cost difference must be adjusted in project accounting or fixed asset applications. For the depreciable items, the difference is adjusted in Oracle Assets. For non-depreciable items, the adjustment is done in Oracle Projects.
For both normal and depreciable items, in Oracle Payables, the invoice must be approved, and accounting must be created. Also you need to run an Oracle Payables concurrent program to interface the transaction to Oracle General Ledger before adjusting the invoice price variance.
You need to run a concurrent program to ensure that the construction cost of the project is as close to the actual cost as possible.
Two types of invoice price variance are available:
  • Invoice Price Variance in Oracle Projects
    To adjust the cost from Oracle Payables, you must bring in invoice cost from Oracle Payables into Oracle Projects and then assign attributes to new expenditures. The steps are as follows:
    1. Run the program Interface Invoice Price Variance to Oracle Projects. It creates invoice price variance data in project interface table.
    2. Run the program PRC: Transaction Import. It creates expenditure lines for the invoice price variance amount in projects.
    3. Run the program PRC: Generate Asset Lines.
    4. Run the Oracle Assets request set Post Mass Additions for the category book.
  • Invoice Price Variance in Oracle Assets
    To adjust the cost from Oracle Payables, bring the invoice cost from Oracle Payables into Oracle Assets, and then update the Mass Addition table. The steps are as follows:
    1. Run the program Interface Invoice Price Variance to Oracle Assets.
    2. Run the Oracle Assets request set Post Mass Additions for the category book.
The topics in this section are the following:

Running the Interface Invoice Price Variance to Oracle Assets Program

Prerequisites
In Oracle Payables, first approve the invoice, then create accounting for the invoice.
Run the Oracle Payables program Payables Transfer to General Ledger.
To run the Interface Invoice Price Variance to Oracle Assets program
  1. Using the Asset Tracking Super User responsibility, navigate to Request and then select Run.
  2. Choose to run a single report.
  3. In the Name field, choose Interface Invoice Price Variance to Oracle Assets program.
  4. In the Parameters window, enter the parameters: PO Number, Inventory Item, Organization, Include Zero IPV.
  5. Click OK to close the Parameters window.
  6. Click Submit when you have finished defining the report.
    The application assigns an ID number to your request. Use the ID number to find your request in the View Request window.
Related Topics
Viewing Request Results

Running the Interface Invoice Price Variance to Oracle Projects Program

Prerequisites
In Oracle Payables, first approve the invoice, then create accounting for the invoice.
Run the Oracle Payables program Payables Transfer to General Ledger.
To run the Interface Invoice Price Variance to Oracle Projects Program
  1. Using the Asset Tracking Super User responsibility, navigate to Request and then select Run.
  2. Choose to run a single report.
  3. In the Name field, choose Interface Invoice Price Variance to Oracle Projects.
  4. In the Parameters window, enter the parameters: Project Number, Task Number, Purchase Order Number, Inventory Item, and Organization.
  5. Click OK to close the Parameters window.
  6. Click Submit when you have finished defining the report.
    The application assigns an ID number to your request. Use the ID number to find your request in the View Request window.
Related Topics
Viewing Request Results

Running the Generate Notification - New Fixed Assets for Install Base Tracking Program

You can run the concurrent program Generate Notification - New Fixed Assets for Install Base Tracking, from the Asset Tracking Super User or Asset Tracking Planner responsibilities. This program generates a workflow notification for all the assets which may need an item instance created. If an asset is created in Oracle Assets and the source of the asset is not Oracle Asset Tracking, then running this program inserts a row in the staging table CSI_FA_TRANSACTIONS and generates a notification. Depending on the setup of Oracle Workflow, an email is sent to users associated to the seeded responsibilities, Asset Tracking Super User or Asset Tracking Planner. The Asset Tracking Planner responsibility has been created to simplify the process of generating and acting on the new assets workflow notifications.
Note: You can also view a notification from the Oracle Workflow worklist.
To run the Generate Notification - New Fixed Assets for Install Base Tracking program
  1. From the Asset Tracking Super User responsibility, navigate to Request and then select Run.
  2. Choose to run a single report.
  3. In the Name field, choose Generate Notification - New Fixed Assets for Install Base Tracking.
  4. Click Submit.
    The application assigns an ID number to your request. Use the ID number to find your request in the View Request window.

Running the Create Reversal GL Entries for Inventory FA Items Program

Oracle Asset Tracking enables you to capitalize assets regardless whether they are in inventory. As depreciable assets move in and out of inventory, accounting entries are generated by the Cost Manager to update the associated inventory value. The Cost Manager has no way to identify these assets as capital assets. To prevent duplication, Oracle Asset Tracking uses the Create Reversal GL Entries for Inventory FA Items program to reverse the accounting entries made by the Cost Manager.
Following is a description of how the Create Reversal GL Entries for Inventory FA Items program works:
  1. Finds unprocessed CSI transactions using the 1 value (Pending) of gl_interface_status_code column. (The CSI_TRANSACTIONS table stores all transactions related to Item Instances.)
    If there are no unprocessed transactions, then the program ends.
    Otherwise, it gets the corresponding MTL_MATERIAL_TRANSACTIONS (MMT) row for each unprocessed CSI transactions. For each inventory transaction of an item instance, a CSI_TRANSACTIONS row is created with the MMT transaction id as foreign key.
  2. After the MMT record is found, checks to determine whether any item instances are capitalized item instances.
    If there is none, the record is not processed.
    Otherwise, it will process to find the corresponding SLA entries.
  3. To ensure that there will be no other changes before proceeding any further with the SLA entries, the process looks for Final Mode SLA entries.
  4. The amount to be reversed is computed using the following formula: (Ledger Amount / quantity in MMT)multiplied by the # of capitalized item instances .
    The accounts used to generate reversal entries are the same as the original distribution entry which is being reversed.
  5. Inserts reversal entries into GL_INTERFACE, to be posted in General Ledger later.
  6. Sets the gl_interface_status_code of CSI_TRANSACTIONS to 2 (Posted). This ensures the transactions are not processed again the next time the program runs. If the program logic derives that the transaction does not need accounting reversal then the gl_adjustment_process_flag of CSI_TRANSACTIONS is updated to 3 (None). This typically is the case when the distributions are not transferable to general ledger as with some upgrade data.
Note: The process can be initiated any time. However, you must also run it after all your SLA entries have transferred to the GL, and before you close your period.
From the GL side, the Journal Import process can be run to create journal entries from the GL_INTERFACE records. After reviewing for validity, they can be posted to GL .
To run the Create Reversal GL Entries for Inventory FA Items program
  1. From the Asset Tracking Super User responsibility, navigate to Request and then select Run.
  2. Choose to run a single report.
  3. In the Name field, choose Create Reversal GL Entries for Inventory FA Items.
  4. Click Submit.
    The application assigns an ID number to your request. Use the ID number to find your request in the View Request window.

Finding Personal Profile Values

In the Find Personal Profile Values window, you can search for the personal profile values that have already been defined in other Oracle applications. Then use the Personal Profile Values window to display and make changes to your personal settings. Do not enter user values unless you require a setting that is different from the default setting.
Follow these steps to find and edit personal profile values used in the Oracle Asset Tracking application.
Prerequisites
Create profiles.
To find personal profile values
  1. Using the Asset Tracking Super User responsibility, navigate to Setup and then select Profiles.
    The Find Personal Profile Values window opens.
  2. Click [...] to open the list of values.
    The Organizations window appears.
  3. Enter any partial search mask, if you want, in the Find field, and click Find.
    The Profiles window displays the profiles for Oracle Asset Tracking.
  4. Select the profile that you want to edit, and click OK.
    The Find Personal Profile Values window displays the name of the selected profile.
  5. Click Find.
    The Personal Profile Values window opens and displays the selected profile.
  6. Enter values in the User Value column to customize the user profile.
  7. Save.

    Using the Google Maps Integration

    This chapter covers the following topics:
  8. Google Maps Integration Overview
  9. Google Maps Integration with OAT
  10. Viewing Instances on Google Maps

Google Maps Integration Overview

Oracle Asset Tracking can integrate with the web-based source map viewer of Google Maps. Oracle Asset Tracking instances can be geocoded and displayed in the map viewer based on user entered search criteria.
Note: Only those instances that have geocode information associated to them will display on the map.

Google Maps Integration with OAT

From the Asset Tracking Super User responsibility, when you select any instance icon on the map viewer using details such as asset number, description, asset group, owning department, the instance location and geocodes will display. You can also access other pages to perform the following actions:
  • Create a work order.
  • Create a work request.
  • View open work orders.
  • View open work requests.
  • View the graphical asset hierarchy for the asset.
Entering Geocodes for OAT Assets
  1. Navigate to the Asset Tracking Super User responsibility.
  2. Click the Mass Geocode Entry link.
    The Mass Asset Geocode Entry page appears.
  3. Enter an Item Instance.
    the picture is described in the document text
  4. In the Mass Entry Geocode Asset region, enter values such as:
  5. Enter values such as:
    • Latitude values for the asset:
      • Degrees - Enter a numeric value, do not use decimals, and you can enter a negative value.
      • Minutes - Do not use decimals.
      • Seconds - Enter a numeric value and you can use decimals.
      • Direction - Select N (north) or S (south)
    • Longitude values for the asset:
      • Degrees - Enter a numeric value, do not use decimals, and you can enter a negative value
      • Minutes - Do not use decimals.
      • Seconds. Enter a numeric value and you can use decimals.
      • Direction - Select E (east) or W (west)
    If the geocode information already exists for the queried instance, the information can be modified or deleted.

Viewing Instances on Google Maps

If a responsibility has the appropriate roles and security, users can view the geospatial locations of OAT instances with the map viewer functionality using Google maps.
To view instances on Google maps
  1. Navigate to the Asset Tracking Super User responsibility, and click the Item Instances link.
  2. Enter search criteria such as Item Instance, Item, and so on and click the Go button.
  3. Click the Map All button.
    The Asset Map page appears, displaying the selected assets on a Google map using a map viewer.
  4. Click an instance (balloon) icon to view instance details such as Item Instance, Description, and Item.
  5. Click the More>>> link to view additional details such as:
    • Address of where the asset is located
    • Latitude
    • Longitude
  6. You can also access these other pages from the More>>> link to perform additional actions for the selected OAT instances:
    • Create Work Order
    • Create Work Request
    If the OAT instance is also an EAM asset number, you can also view the following:
    • View Open Work Orders
    • View Open Work Requests
    • Graphical Hierarchy - to view the asset hierarchy
  7. Optionally, click the Instance Number links at the bottom of the page to view additional instance details, such as latitude and longitude.

    Using the ESRI Integration

    This chapter covers the following topics:
  8. ESRI Integration Overview
  9. ESRI Integration with Oracle Asset Tracking
  10. Viewing Assets Using the ESRI Map Viewer

ESRI Integration Overview

You can use ESRI to integration with Oracle Asset Tracking to locate and view assets on an ESRI map viewer.
Only those instances that have geocode information associated to them will display on the map.
Important: You must purchase a license to use the online or server version of the ESRI map viewer.

ESRI Integration with Oracle Asset Tracking

You must perform some setup tasks before you can integrate Oracle Asset Tracking with ESRI. See ESRI Integration, Oracle Enterprise Asset Management User's Guide.
From the Asset Tracking Super User responsibility, when you select any instance icon on the ESRI map viewer using details such as asset number, description, asset group, owning department, the instance location and geocodes will display.
To enter geocodes to map assets
Ensure that the geocode information has been entered for the assets that you want to map graphically. See Entering Geocodes for OAT Assets to enter the geocode information.

Viewing Assets Using the ESRI Map Viewer

If a responsibility has the appropriate roles and security, users can view the geospatial locations of OAT instances with the map viewer functionality using a ESRI map viewer.
To view assets using the ESRI map viewer
  1. Navigate to the Asset Tracking Super User responsibility, and click the Item Instances link.
  2. Enter search criteria such as Item Instance, Item, and so on and click the Go button.
  3. Click the Map All button.
    The ESRI map viewer page appears and the geocoded assets appear as colored icons on the map.
  4. Click an instance (colored) icon to view instance details such as Item Instance, Description, and Item.
  5. Click the vertical scroll bar to access the following actions:

    GIS Integration: Custom Map Viewer

    In addition to using Google maps or ESRI to display assets in Oracle Asset Tracking, you can also use a custom web-based HTML map viewer.
    By using this custom map viewer, you can:
  6. Display geocoded assets on a map.
  7. Display work orders on a map (work orders must be associated with geocoded assets).

Setting Up the Custom Map Viewer

You must perform some setup tasks before you can use the custom map viewer.
Prerequisites
  • You must perform the following setup tasks before using the custom map viewer to display assets, and transact work using the custom map viewer.
    1. Set up the profile value for the custom map viewer using the System Administrator responsibility.
    2. Define the CSI: Customized Mapviewer Class. See Appendix A: CSI Integration, Implementing the Custom Map Viewer, Oracle Enterprise Asset Management Implementation Guide.
    3. Enter geocode information for the assets that you want to display on the map viewer. See Entering Geocodes for OAT Assets or Entering and Viewing Geocodes Using the EAM Responsibility, Using Google Map Integration, Oracle Enterprise Asset Management User's Guide.

Setting Up the Custom Map Viewer Profile Value

Follow these steps to define the profile value to use with the custom map viewer.
  1. Navigate to the System Administrator responsibility, and access the Find System Profile Values page (System Administrator > System Profiles Values > Find System Profile Values).
  2. Perform a query to search for CSI%MAP%.
  3. Select the CSI:Mapviewer Name profile option name.
    The System Profile Values page appears.
  4. Select the Custom value in the User column.
  5. Save your work.

Oracle Product Information Management User's Guide



Using the Item Catalog

This chapter covers the following topics:

Browsing the Item Catalog and Alternate Catalogs

You can browse the hierarchically structured item and alternate catalogs from the application tree menu "Browse Catalog" link. You can also browse the item catalog, but not alternate catalogs, from the Setup Workbench. Expand and collapse levels in the hierarchy to view the current structure of the catalog. You can only browse catalogs for which you have the Catalog Viewer role.
To browse a catalog
  1. In the Items section of the Application tree menu, click the "Browse Catalog" link.
  2. In the Browse Catalog page Catalog field, select either the Item Catalog or another catalog.
  3. In the Categories field, choose to view all categories for the catalog or only the active categories.
  4. Click the Show/Hide link to search for item catalog categories by Name or Description. After entering the search criteria, click Go.
  5. To view the items associated with the item catalog category, select the item catalog category.
    All items associated with the item catalog category and its child categories are listed below.
  6. Click the focus icon next to the desired item catalog category to display it at the top level.
To perform actions on an item within a catalog category
The actions you can perform on items vary depending on whether you select a category within the Item Catalog or another catalog.
From an Item Catalog category, you can select items and perform the following actions:
  • create a new item request
  • add items to a new catalog category
  • add items to an existing catalog category
  • generate a report
  • create a change order, change request, or issue
  • change the lifecycle
  • change the item catalog category
  • compare items
  • add to the Favorites list
  • export all items in the category to a spreadsheet
  • remove items from the catalog category
From any other catalog, you can select items and perform the following actions:
  • create a new item request
  • create a change order, change request, or issue
  • generate a report
  • compare items
  • add to the Favorites list
  1. Complete the steps in To browse a catalog above, then select one or more items.
To export all items to a spreadsheet
  1. Click Export All Items to export all items in the category to a spreadsheet.
To perform all other actions
  1. In the Select Items field, select one of the following actions, then click Go.
To search or browse the item catalog from the Setup Workbench
  1. In the Applications tree menu, click the "Setup Workbench" link.
    On the Search: Item Catalog Categories page, click the Catalog Hierarchy link or the Catalog Hierarchy icon.
    Note: You can only browse the item catalog using this method.
    Tip: In the Search: Item Catalog Categories page, you can also search for item catalog categories by entering search criteria for a category name, description, or parent category.
    When you enter a search string, the wildcard character "%" is appended to the input. For example, entering "mem" enters the search string "mem%", so that the "memory" catalog category could be returned in the search results. If you wish to search for entries that end with a particular string, such as "log", you can type in "%log", and all entries ending in "log" are returned. If you do not enter a search string in the text box, an error is returned.
Related Topics
Overview of Item Catalogs, Oracle Product Information Management Implementation Guide
Overview of Catalogs, Oracle Product Information Management Implementation Guide
Assigning an Item to a Category
Copying Items with Category Assignments

Updating Item Catalog Categories

It is likely that you will need to update item catalog categories at some point--you may need to change an item catalog category so that it can be used for item creation, or modify the inactive date so that the item catalog category will no longer be used. Often, users simply need to correct a mistake or reclassify the item catalog category due to shifting relationships within the item catalog category hierarchy.
To update an item catalog category
  1. On the Search: Item Catalog Categories page, search for the item catalog category you want to update and click the corresponding link.
  2. On the Basic Information page for the item catalog category, click Update.
  3. On the Create/Edit Item Catalog Category page, enter or change the following information:
    Catalog (required)
    Defines the item catalog category name. The number of segments (and respective labels) for the item catalog category depends on how the item catalog group flexfield is defined in Oracle Inventory setup.
    Description
    Optionally enter a brief description of the item catalog category.
    Parent Item Category
    If at any time a parent item catalog category has been created for this item catalog category, then you cannot leave this field blank. In other words, once you have defined a parent for an item catalog category, you always have a parent item catalog category. Also, if a parent item catalog category has already been defined, then you can only choose the item catalog category's siblings, its sibling's children, or the current parent item catalog category, as a parent item catalog category.
    Note: For item catalog categories with versions, once the item catalog category is released, you cannot change the parent item catalog category.
    Item Creation Allowed
    Select to specify that items in the item catalog category can be created (if you do not select, the item catalog category only serves the purpose of being a placeholder in the item catalog category hierarchy). If item creation is not allowed, the item catalog category will typically specify characteristics (attribute groups, etc.) that are inherited by its descendants.
    Inactivate
    Optionally specify a date on which the item catalog category will become inactive. You cannot specify an inactive date that is later than the inactive date of an item catalog category's parent, nor can you specify an inactive date that has already passed. Thus, all children of a parent item catalog category with an inactive date should be made inactive at the same time or earlier. Making an item catalog category inactive has the following implications:
    • You cannot create items of that item catalog category or any of its descendants.
    • You cannot use that item catalog category or any of its descendants as the parent item catalog category upon creation of an item catalog category.
    Note: After you've updated an inactive date, the change propagates to all of the item catalog category's children.
  4. Click Apply.
Related Topics
Defining Item Catalog Categories, Oracle Product Information Management Implementation Guide

Assigning an Item to a Category

When you create an item, it is automatically assigned to the default mandatory item catalog and default category of the functional area in which it is created. You can override the item catalog's default category as well as manually assign the item to an unlimited number of catalogs.
To assign an item to an existing category from the item's Classifications and Categories page
This explains how you can change an item catalog category as well as assign an item to one or more existing catalog categories.
  1. In the Applications tree menu, use either the "Simple Search" or "Advanced Search" links to search for the item whose category you wish to change.
  2. Click the item's link in the search results.
  3. On the Overview page, select the Classification and Categories link.
  4. On the Classification and Categories page, click Update. After the page refreshes, click Add Assignment.
  5. Select a catalog and then a category within that catalog.
    If Enforce List of Valid Categories is enabled in the catalog definition (See: Defining Catalogs, Oracle Product Information Management Implementation Guide), then you can only choose from the list of valid categories defined for that catalog. Otherwise, you can choose any category that has the same flex field structure as the catalog.
    If Allow Multiple Item Category Assignments is disabled in the catalog definition (See: Defining Catalogs, Oracle Product Information Management Implementation Guide), then you can assign an item to only one category in the catalog. Otherwise, you can choose to assign the item to multiple categories in the catalog.
    In a hierarchical item catalog, you can only assign items to leaf categories.
    Tip: If you want to add the selected items to more than one catalog category, click Add Another Row to search for and select another catalog/category combination.
  6. Click Apply.
To add items to an existing catalog category from the Browse Catalog or Search Results page
Using this method, you can select one or more items and assign them to existing catalog categories from the Browse Catalog or Search Results page.
  1. Browse the item catalog or another catalog. Select the items within a catalog category that you want to add to an existing catalog category. See: Browsing the Item Catalog and Alternate Catalogs
    Alternatively, search for one or more items. In the Search Results page, select the items that you want to add to an existing catalog category. See: Searching for Items
  2. In the Select Items field, select the Add to Existing Catalog Category action, then click Go.
  3. The Add to Existing Category page appears. In the Catalog field, search for and select a catalog.
  4. In the Category field, search for and select a category.
  5. If you want to add the selected items to more than one existing catalog category, then click Add Another Row.
  6. If you decide not to add the items to a catalog category, you can either remove the items or remove the catalog category by selecting it, then clicking either Remove for the selected categories or Remove for the selected items.
  7. Click Apply.
To add items to a new catalog category from the Browse Catalog or Search Results page
In addition to creating new catalog categories in the Setup Workbench (see: Defining Catalog Categories, Oracle Product Information Management Implementation Guide), you can create a new catalog category from the Browse Catalog and Search Results pages and add items to it in one flow of steps.
  1. Browse the item catalog or another catalog. Select the items within a catalog category that you want to add to a new catalog category. See: Browsing the Item Catalog and Alternate Catalogs
    Alternatively, search for one or more items. In the Search Results page, select the items that you want to add to a new catalog category. See: Searching for Items
  2. In the Select Items field, select the Add to New Catalog Category action, then click Go.
  3. In the Add to New Category page, Catalog field, search for and select the catalog to which you want to add a new category.
    Caution: You can only select those catalogs for which you have the Manage Catalog privilege.
  4. The Catalog Category field appears. Enter a unique name for the new catalog category.
    Caution: If the search/list of values icon appears next to the Catalog Category field, this means that a value set is assigned to the flex structure associated with the catalog. Any new catalog category name must be a value from this value set that has not been previously used to create a catalog category.
    When you use the list of values icon to search for a value within the value set, you are able to search on all values, including the values already used to create categories. If you select a value that is already assigned to a category, an error appears only after you try to create the new category.
    To avoid this problem, select a catalog that uses free form category creation rather than one based on a value set.
  5. Optionally, enter a description for the catalog category.
  6. Optionally, enter a parent category for the new category.
    The Parent Category field only appears if the catalog's Enable Hierarchy for Categories field is set to No (see: Defining Catalogs, Oracle Product Information Management Implementation Guide).
  7. Optionally, in the Inactive On field, enter the date when you can no longer assign this catalog category:
    • As the default category of a new catalog
    • As a valid category of a catalog
    • To an item
    • As a valid category of an item catalog category
  8. Optionally, you can select any items and click Remove if you no longer want to include them in the new catalog category.
  9. Click Apply.
Related Topics
Overview of Item Catalogs, Oracle Product Information Management Implementation Guide
Overview of Catalogs, Oracle Product Information Management Implementation Guide
Browsing the Item Catalog and Alternate Catalogs
Searching for Items
Copying Items with Category Assignments

Changing an Existing Item's Item Catalog Category

Warning: Before changing an item's ICC, consider the potential loss of user defined attribute data. If attribute groups associated with the existing ICC are not associated with the new ICC, then the item's attribute data for these attribute groups will be lost once the ICC changes.
See: Associating Attribute Groups with an Item Catalog Category, Oracle Product Information Management Implementation Guide
You can change an item's item catalog category (ICC) with the following exceptions:
  • You cannot change the ICC for style items that have SKU items.
  • For style items, the new ICC must have variant attribute groups.
  • You can only change the ICC of items for which you have the Edit Item and the Change Item Status privileges.
  1. In one of the following pages, select the item(s) for which you want to change the item catalog category.
    Alternatively, you can change the ICC from the item's Overview page.
    Warning: If ICC versions are enabled, use one of the HTML interface options as described above to change an item's item catalog category rather than the Forms interface to avoid data corruption. Forms behavior has not been enhanced to support ICC versions.
  2. Select Change Item Catalog Category from either:
    • the Select Items field in the Browse Catalog or Search Results page.
    • the Actions field in the item's Overview page.
    Click Go.
  3. In the Change Item Catalog Category page, search for and select a new ICC, then click Go.
    Note: Items you selected for an ICC change do not appear in the Change Item Catalog Category page when the following conditions apply:
    • The items selected are style items with SKU items.
    • The items selected are style items and the new ICC has no variant attribute groups.
    • You do not have the Edit Item and the Change Item Status privileges for the item(s).
  4. Optionally, you can select new values for the following fields:
    • New Lifecycle
    • New Lifecycle Phase
    • New Item Status
    Any new values selected apply to all items in the list.
  5. Optionally, select any items to remove from the list of items for which you plan to change the ICC. Click Remove.
  6. Click Continue.
  7. In the Change Item Catalog Category: Review Details page, for each item in the list, enter the following field values if you did not enter these field values for all items previously.
    • New Lifecycle. Optional.
    • New Lifecycle Phase. Optional.
    • New Item Status. Required.
  8. Click Finish.
Related Topics
Browsing the Item Catalog and Alternate Catalogs
Searching for Items
Assigning an Item to a Category

Copying Items with Category Assignments

When you assign an item to another organization, the system copies the item level catalogs, organization level default catalog, and the associated categories assigned in the item master organization. For example, if you manually assign an organization item level catalog to the item in the master organization, the system does not copy over that organization item level catalog when you assign that item to another organization.
After assigning an item to another organization, you can disable the item for one or more functional areas in the new organization. However, the system does not remove the corresponding functional area's default catalog. For example, you may have set the value of the Purchased attribute to "Yes" when you defined the item in the item master organization. When you assign this item to another organization, the system copies over the "Yes" value of the Purchased attribute, and therefore assigns the default catalog of the Purchasing functional area. In the new organization, you may decide to set the value of the Purchased attribute to "No." After you disable the item for the Purchasing functional area in the new organization, the item still retains the Purchasing default catalog. You may manually delete the Purchasing catalog in the new organization.
If you copy an object with item catalogs defined at the organization level, the system assigns the new item the default categories of the mandatory catalogs, even if the original item did not have the default categories. This occurs because the system copies the values of the item defining attributes and not the item catalogs and categories themselves.

Assigning Suppliers to Items

Assigning suppliers to items enables you to assign attributes, perform actions, and make rules that only apply to that item/supplier combination. For example, if you choose not to assign suppliers to items, you can assign attributes at:
  • the master item level - all attributes defined at this level apply to the item across all organizations and all suppliers.
  • the item organization level - all attributes defined at this level apply to the item only in this particular organization.
If you choose to assign suppliers to items, you can also assign supplier sites to items. For example, a supplier manufactures an item in two locations, San Francisco and Denver (the supplier sites). The characteristics of the item differ slightly depending on which supplier site ships to your retail store (organization). In this example, you can assign attributes at the following levels, in addition to the item and item organization levels described above:
  • item supplier - all attributes defined at this level apply to this item and supplier combination.
  • item supplier site - all attributes defined at this level apply to this item and supplier site combination.
  • item supplier site organization - all attributes defined at this level apply to this item, supplier site, and your organization combination.
The following graphic depicts an item supplied to a company's retail stores, either directly to the store or through a warehouse. The suppliers can ship the item from more than one manufacturing plant (supplier site). In this scenario, a store either receives the item from it's warehouse or directly from a supplier. Supplier 1 ships to the warehouse, which then ships the item to the store, while supplier 2 ships the item directly to the store. The item attributes differ slightly, depending on which supplier, and even which supplier site, ships the item.
the picture is described in the document text
Note: Some users question how item supplier associations relate to the Approved Supplier List (ASL). The item supplier associations serve a different purpose than the Approved Supplier List. The item supplier associations can tell you which supplier and/or supplier location supply an item, but not whether the supplier is approved.
To assign a supplier and supplier site to an item
  1. In the Item Overview page, select the Associations subtab. Select Supplier and Supplier Site Assignment from the left side of the page.
  2. From the Supplier and Supplier Site Assignments page, click Assign.
  3. In the Assign Items to Suppliers: Select Suppliers page, enter at least one of the following to identify the supplier, then click Next.
    • Supplier Name
    • Supplier Number
    • DUNS Number
    • Tax Payer ID
    • Tax Registration Number
    Tip: Check the Show Supplier Sites box to narrow your search for specific suppliers and supplier sites. Checking this box enables you to enter supplier site information.
  4. In the Assign Items to Suppliers: Review Supplier Results page, select the supplier and/or the supplier sites listed. Click Next.
    This page lists the supplier and all supplier sites for the supplier.
  5. In the Assign Items : Review Results page, review supplier and supplier sites selected. Click Finish.
    If the supplier and supplier sites selected are incorrect, click Back to correct the error.
To assign a supplier site and organization to an item
The process of assigning a supplier site and organization to an item is similar to the process described above of assigning a supplier and supplier site to an item, but with one more step - assigning an organization to the item supplier site.
  1. In the Item Overview page, select the Associations subtab. Select Supplier Site Organization Assignment from the left side of the page.
  2. Assign a supplier site as described above in "To assign a supplier and supplier site to an item:".
  3. In the Assign Items to SupplierSites-Org: Select Organizations page, enter an organization code, name or hierarchy. Click Next.
  4. Review the organization selected and click Next again.
    Click Back if you want to change the organization.
  5. In the Assign Items: Review Results page, you can review the supplier, supplier site, and organization assigned to the item. Click Finish.
    Click Back if you want to change the supplier, supplier site, or organization.
To view and update item supplier, item supplier site, or item supplier site organization attributes
You can view or update a single item supplier association from both the Supplier and Supplier Site Assignments page and the Supplier Site Organization Assignment page. To update all item supplier associations at once, you must import the changes using a spreadsheet.
To view and update attributes for a single item/supplier/supplier site/organization association
  1. Navigate to either the Supplier and Supplier Site Assignments page or the Supplier Site Organization Assignment page.
  2. In the Advanced Search region, search for and select an item/supplier/supplier site/organization intersection.
  3. In the Supplier Assignment detail region, select the Attributes tab, then click Update.
  4. Enter any changes to the item/supplier/supplier site/organization intersection attributes, then click Apply.
To view and update attributes for all suppliers, supplier sites, or supplier site organizations at once
  1. Navigate to either the Supplier and Supplier Site Assignments page or the Supplier Site Organization Assignment page.
  2. Click the appropriate button:
    • Update Supplier Attributes
    • Update Supplier Site Attributes
    • Update All Attributes (on the Supplier Site Organization Assignment page)
  3. Select a display format to download, then click Export.
    Note: The display format you select must contain attributes controlled at the appropriate level. For example, if you want to update supplier site attributes, the display format must contain attributes controlled at the supplier site level.
    See Updating Existing Items Using a Spreadsheet for a detailed description of how to export, make changes, and import those changes.
To view and mass update item supplier, item supplier site, or item supplier site organization attributes
  1. For item supplier and item supplier site attributes, navigate to the Supplier and Supplier Site Assignments page. For item supplier site organization attributes, navigate to the Supplier Site Organization Assignment page. Select the supplier, supplier site, and/or organization intersection for which to view or update attributes.
  2. Click one of the following:
    • Update Supplier Attributes
    • Update Supplier Site Attributes
    • Update All Attributes - use for updating the item supplier site organization intersection attributes.
    Tip: You can update the item supplier and item supplier site attributes from the Supplier Site Organization Assignment page. For the selected item supplier site organization, click the Supplier and Supplier Site Assignment tab. All item supplier and item supplier site intersections are listed. Click the Additional Attributes icon for a particular row, then click Update.
  3. Select a display format that contains attributes controlled at the intersection level selected. Click Export.
  4. Select the application on your desktop to use for viewing the exported document. Click Next.
  5. Choose whether to open or save the exported spreadsheet document.
  6. Update the attributes, then save the spreadsheet to import later.
    See: Managing Item Imports
To view and update item-supplier formal packs
  1. Navigate to the Supplier and Supplier Site Assignments page, then select the Formal Packs tab.
  2. To update the pack type, select the Pack Type to use with the selected supplier or supplier site, then click Create Change Order.
    See: Managing the Packaging Hierarchy and Creating a SKU Packaging Hierarchy.
To view, create, and update item-supplier change orders
You can create a change order for:
  • adding or removing a supplier or specific supplier site to or from an item
  • updating item supplier, item supplier site, or item supplier site organization attributes
  1. For item supplier and item supplier site assignments and attributes, navigate to the Supplier and Supplier Site Assignments page. For item supplier site organization assignments and attributes, navigate to the Supplier Site Organization Assignment page. Select the supplier, supplier site, and/or organization intersection for which to view or update attributes.
  2. Click Create Change Order. See: Creating Change Orders
To inactivate an item supplier, item supplier site, or item supplier site organization association
Once you assign an item to a supplier, supplier site, or supplier site organization, you cannot delete this relationship. You can inactivate the relationship, though. In the (item/supplier/supplier site/organization) Assignment: Update Attributes page, change the Status attribute to Inactive.
Related Topics
Approved Supplier List, Oracle Purchasing User's Guide
Entering Suppliers Manually, Oracle Payables User's Guide
Adjusting Suppliers (Adding a New Supplier Site), Oracle Payables User's Guide
Finding Suppliers, Oracle Payables User's Guide

Searching for Items

You can perform searches using keywords that may be part of an item number, item catalog category, manufacturer, manufacturer part number, short description or long description. Keyword searches enable you to search using any or all keywords. You can enter additional keywords to be excluded from a search. For example, the keyword search for “SRAM” may return results that include all items that have “SRAM” in the item name, description, or an attribute value. A Wildcard search enables you to enter the percent (%) sign before and/or after a keyword. For example, a search using “mo%” may return “Monitor” and “Mouse,” but a search using “mon%” would return “Monitor.” A Fuzzy Search enables you to look for records that closely resemble or sound like your word(s), but are spelled differently. For example, a search for “telefone."
Keyword search options include:
  • Exact match
    Enter search criteria for a specific word.
  • Word positioning
    Search using a particular phrase such as “optical sensors relay,” or search for words near each other, such as “optical NEAR relay.”
  • Inexact match
    Search for words that sound like your word to account for common spelling and typing errors.
  • Intelligent match
    Search for an item by entering a word that is about something like a theme--for example searching by the word 'Car' can result in items such as Convertibles, Coupes, and Sedans without having the word car in the item name. You may also ignore the noise words such as 'the', 'of'. A default list of noise words (a stop list) is supplied for each European Language.
  • Non-alphanumeric characters
    You may choose to search with '-' (or other non-alphanumeric characters) as part of the item name such as AS-18947.
  • Boolean combinations
    Combine terms described above using the operators: AND, OR, and NOT.
  • Stemming search
    Search for relevant items. For example, entering the word “pen” returns results that include items like pens and pencils.
The system also enables you to search for items based on item revision attribute values. For example, if the horsepower of an engine has changed from 200 hp to 220 hp between revisions A and B, searching for an item revision with the horsepower attribute value of 220, will return only revision B.
To perform a simple item search
  1. On the Simple Search page, enter as many keywords as possible in the Keyword Search field. For example, entering "CRT Color Monitor" would return more relevant results than simply entering "Monitor." To specify that the search uses all the keywords entered, select Match all word(s) (AND). To specify that the search use any of the keywords entered, select Match any word(s) (OR).
  2. To exclude a keyword from the search, enter it in the Without Keyword(s) field. For example, entering the keywords "Flat LCD Monitor" without the keyword "black " returns all "Flat LCD Monitors" that are not black.
  3. Click Search.
    • Enter % (wildcard) before and/or after a keyword to perform a wildcard search. For example, a search for "mo%" returns Mouse and Monitor; a search for mon% returns Monitor.
    • Include "$" before the item name to perform a stemming search. This indicates that you want to search for items whose spelling is derived, or stems from the keyword. For example, a search on the keyword "$contract" could return: "contract," "contracts," "contracted," and "contracting."
    • Include "?" before the item name to perform a fuzzy search. This indicates that you want to search for items whose spelling is close to the actual item for which you are performing the search. The search engine looks for records that closely resemble the words you have entered, but that are spelled differently. The search returns results that have items with that term in either its name or description. Hence, entering the keyword "?telefone" also would return "telephone."
    • Simple Search is case-insensitive.
    As mentioned above, Item simple search supports wildcard, fuzzy and stemming search. However these different types of search are supported only in certain languages. The following table summarizes the search features and the supported languages.

    Language Wildcard (%) Fuzzy (?) Stemming ($)
    English Yes Yes Yes
    German Yes Yes Yes
    Japanese No Yes No
    French Yes Yes Yes
    Spanish Yes Yes Yes
    Italian Yes Yes Yes
    Dutch Yes Yes Yes
    Portuguese Yes Yes No
    Korean Yes No No
    Simplified Chinese No No No
    Traditional Chinese No No No
    Danish Yes No No
    Swedish Yes No No
    Finnish Yes No No
To perform an advanced search
Note the following tips and restrictions before conducting an advanced search:
  • Providing values for the indexed attributes improves performance during the search.
  • If no search criteria template is used, you must add your own criteria to be used for the search.
  • If no display format template is used, the following columns will be the default for your search results: Item, Item Catalog Category, Description, and Item Revision.
  • All Advanced Search operators are case-sensitive, except for the operator "contains".
  1. On the Advanced Search page, select an Item Catalog Category and click Go. This determines the search criteria templates that are available to use for this particular search.
    Note: You are not required to search by or select a catalog category. If you do not, the default system search criteria template appears.
    You can also optionally search by:
    • Alternate Catalog
    • Alternate Category
    • Organization
    • Revision
    To search by item revision specific attributes, select the type of Revision on which to base the search. Following are the types of revisions available:
    • All
      Searches for all (past, current and future) revisions.
    • Latest
      Searches for the most current effective revisions that are not yet implemented.
    • Production
      Searches for the revisions that are currently implemented.
  2. Select a search criteria, add or delete attributes and enter values to define your parametric search. You must include at least one indexed attribute in your search. You can select and preview a display format for the search results.
    Note: For details about how to use search criteria and display formats to assist in your advanced search, see Managing Search Criteria, Oracle Product Information Management Implementation Guide and Managing Display Formats, Oracle Product Information Management Implementation Guide.
  3. Click Search.
    The Search Results page appears.
    You can view the AML or Manufacturer Part Numbers for an item in the item search results page within the show/hide region.
To perform actions on items in the Search Results page
You can select items and perform the following actions:
  • create a new item request
  • add items to a new catalog category
  • add items to an existing catalog category
  • generate a report
  • create a change order, change request, or issue
  • change the lifecycle
  • change the item catalog category
  • compare items
  • add to the Favorites list
  • export all items in the category to a spreadsheet
  1. Complete the steps in To perform a simple item search or To perform an advanced search above, then select one or more items.
To export all items to a spreadsheet
  1. Click Export All Items to export all items in the category to a spreadsheet.
To perform all other actions
  1. In the Select Items field, select one of the following actions, then click Go.

Managing Favorite Items

The Favorite Items list provides you a mechanism for creating and managing lists of your favorite or bookmarked items. You can add items to your Favorite Item list from the Search Results page, or while browsing--there are a number of contexts from which the Favorite Items link is available. The following steps describe just one of these contexts.
To add an item to your favorite items list
  1. Navigate to the Favorite Items page by clicking the Favorite Items link in the Items section of the Applications tree menu. You can also get there by navigating to any item Search or Browse page and clicking the Favorite Items tab.
  2. On the Favorite Items page, click Add Favorite Item.
  3. On the Advanced Search page, search for item you wish to add to your favorites list.
  4. On the Search Results page, select the items you wish to add and select Add to Favorites in the Action menu and click Go. A message acknowledging the successful addition of the item to your favorites list appears at the top of the page.
To manage your favorite items list
  1. Navigate to the Favorite Items page by clicking the Favorite Items link in the Items section of the Applications tree menu. You can also get there by navigating to any item Search or Browse page and clicking the Favorite Items tab.
  2. On the Favorite Items page, click Add Favorite Item to add a new item to the list. To remove an item from your Favorite Items list, select the item and then choose Remove from the Action menu and click Go.
    • You can Export to Excel the attributes for your favorite item by selecting it and clicking Export to Excel.
    • You can compare attributes of your favorite items by selecting them and then selecting Compare from the Action menu. Each item's attributes will be listed side-by-side in a table.
    • You can change the lifecycle of an item by selecting it and then selecting Change Lifecycle from the Action menu.
    • You can change an item's catalog category by selecting it and then selecting Change Catalog Category from the Action menu.

Using Recently Visited

Clicking the Recently Visited global button (global buttons appear on all pages in the system's user interface) enables you to view a list of pages that you visited before the current page. This eases navigation throughout the user interface, as the use of your browser's Back button is not supported. The Recently Visited list provides links up to the last 20 pages visited in your current session, in order of most to least recently visited.

Creating New Items

Items are used to represent:
  • Products and services you sell
  • Resources that you maintain
  • Components that make up your products and services
Each item that you create in the catalog has several standard operational attributes that determine the behavior of the item with respect to various functions such as Purchasing, and Inventory Management. In addition to these operational attributes, the item has several user-defined attributes defined by its item catalog category. These user-defined attributes can capture item specifications and other information relevant to the product definition.
You can choose from multiple methods to create a new item:
If the item catalog category specified when creating the item requires an item request approval, proceed to Creating New Item Requests after you create the item.
To create a new item
  1. From the menu, select either Create Engineering Items or Create Production Items.
    Note: The only difference between these two menu choices is whether or not the Engineering Item box is pre-selected.
  2. On the Create Item page, enter values in the following fields:
    • Create - select New Items.
      Tip: Alternatively, you can select Copies of an Existing Item in the Create field. See: To create copies of an existing item. If you have multiple similar items to create, consider creating the first item by selecting New Items in the Create field. After this item is thoroughly defined, created, and approved (if necessary), create the remaining items by creating multiple copies of the first item.
    • Item Catalog Category - find and select an item catalog category in which to create the new item.
      Note: You can only create items within a particular item catalog category if you have the Catalog Category User role for that item catalog category.
      Warning: If ICC versions are enabled, use any of the item creation options described above to create an item rather than the Forms interface to avoid data corruption. Forms behavior has not been enhanced to support ICC versions.
    • Number of Items - enter the number of items you want to create.
    • Style Item - select Style Item if you want to create a style item with related SKUs. For more information about style items, see: Overview of Style and SKU Items.
      Note: You can only create a style item if the selected item catalog category includes at least one attribute group with variant attributes. You can only create SKUs from a style item within the style item's Overview page. See: To create SKU items from a style item:
    • GDSN Syndicated - select this box to permit synchronization with a GDSN datapool such as 1SYNC. See: Overview of the Global Data Synchronization Network, Oracle Product Information Management Implementation Guide
      Important: You cannot send data directly from Oracle Product Information Management (PIM) to GDSN since PIM only maintains the master data, but does not validate the data for GDSN. To send data to GDSN, you must build a validation or use a third party software application to perform this function.
    • Engineering Item - if a new item request is not required for the item catalog category, you have the option to check the Engineering Item checkbox. If a new item request is required, the Engineering Item check box is automatically selected and displayed as read-only. See: Creating New Item Requests
    • Select Templates - optionally, select templates to set the operational and user-defined attributes for the item. The selected templates are applied to all of the items created in the order specified. See: Defining Item Templates, Oracle Product Information Management Implementation Guide
  3. On the Create Item: Enter Number/Description page, enter the required information. Optionally, you can update the primary attribute values (for multiple items, click the Show link to view the primary attributes).
    The item catalog category definition determines the new item's generation method. The item number already appears when the item catalog category specifies that it is Sequence-generated. If the category specifies that the item number or item description is User Entered, then enter an item number or item description. A Function-generated item number or item description is generated after the item and description attributes are entered.
  4. Click Finish.
    If you created one item, the system creates the item and returns you to the item Overview page (the item workbench) where you can further define the item or change attribute values. If you created more than one item, the system notifies you that the items have been submitted for creation and provides the Concurrent Request ID.
    If the item's catalog category requires approval, a warning message appears in the item workbench stating that this item does not have an associated new item request. The item's status remains as Pending with an approval status of Not Submitted for Approval until a new item request is created and approved. See: Creating New Item Requests.
    the picture is described in the document text
Optionally, you can now update item characteristics using the item workbench subtabs:
  • Specifications
    View attributes associated with the item catalog category. You can also update or change attribute values, but, depending on your role privileges and the item's lifecycle phase, a change order may be required (see: Managing Item Specifications). You cannot add new attributes. Attribute associations with item catalog categories are performed at the administration level. For more information, see Defining Item Catalog Categories, Oracle Product Information Management Implementation Guide.
  • Revisions
    See: Creating Item Revisions
  • Attachments
    See: Managing Item Attachments
  • Organizations
    See: Enabling Organization Assignments
  • People
    See: Adding People, Oracle Product Information Management Implementation Guide
  • Associations
    See: Assigning Suppliers to Items and Managing AMLs.
    Caution: GTIN cross references are no longer supported for use with GDSN.
  • Syndication
    Oracle Product Information Management no longer supports outbound product data synchronization with customers.
To create copies of an existing item
If you are familiar with an item in the same item catalog category in which you wish to create a new item, then you can save time by creating the new item from an existing item. When you copy an item, select the attribute groups and attachment categories to copy; also choose whether or not to copy people and organizational assignments (you can add new manufacturer part numbers, but you cannot copy existing ones). You can modify the copied information to define the new item's specifications.
Note that you must have the appropriate privileges to copy the item's user-defined attributes, operational attributes, attachments, people, and organizational assignments. For example, if you wish to copy the item's attachments, you must have--at a minimum--the View Item Attachments List privilege. Likewise, if you want to copy the item's people, you must have the View Item People List privilege for the base item.
  1. Follow the same steps as described above in "To create a new item:", except in the Create field, select Copies of an Existing Item. You can then enter the item and revision to copy.
  2. In the Copy Item Details region, select the sequence in which to copy the template item details and the copied item details. Select which specific item details (such as item attribute groups, attachment categories, and people) to copy.

Creating New Item Requests

The create item process enables you to request new items through a standard approval and creation process. Using this process, companies can promote reuse of items and maintain tight controls over item/part creation, avoiding costly maintenance of duplicate items. The item request approval routing ensures that all relevant parties participate in the item's definition.
Note: If there is no item request associated with an item catalog category, then new items are created with an approval status of Approved. For items such as this, users can define the item status during item creation. If there is a new item request associated with the item catalog category, then the approval status of the item is the same as the approval status of the corresponding new item request. The default approval status of the new item request is Not Submitted for Approval. For such items, regardless of the default approval status, the item status is Pending (all status controlled flags are disabled). Only Product Lifecycle Management and PIMDL users can view items with the item status of Pending. Users cannot view these items in the Master Item window or in any other Oracle application. Users can manually update the item status after the new item request is approved.
Benefits associated with the new item request process:
  • Companies can standardize item numbers and descriptions
  • Prevents duplication and promotes reuse of item number that are functionally equivalent
  • You can automatically trigger actions based on the item creation business event. See: Item Business Events, Oracle Product Information Management Implementation Guide and Managing Business Events, Oracle Workflow Developer's Guide.
New item requests are change objects. See the Using Change Management chapter in the Oracle Product Information Management User's Guide for more information about managing change objects in general.
Prerequisites
  • Associating New Item Requests with an Item Catalog Category, Oracle Product Information Management Implementation Guide
To create a new item request
  1. Create a new item request from either the item Search Results page or the item Overview page.
    In the Search Results page, select the item(s) that you want to add to a new item request. In the Select Items field, select Create New Item Request, then click Go. Using this method, you can create a new item request that contains one or many items.
    In the Overview page, select Create New Item Request in the Actions field, then click Go. Using this method, you create a new item request for only one item, the item displayed, or you can add this item to an existing new item request in the next step.
    the picture is described in the document text
  2. In the Create New Item Request: Select New Item Request Type page, choose whether to create a new item request or to add the selected item(s) to an existing new item request.
    Click Continue.
  3. On the Create New Item Request page you can customize/edit the new item approval request.
    The following list provides additional information for some fields on this page.
    • New Item Request Name - required. Enter a descriptive name for the new item request.
    • Assigned To - the assignee is defaulted based on the item catalog category role specified in the assignment rule for new item requests.
    • Priority and Reason - use these fields to track the degree of urgency and the reason for requesting the new item.
    • Source Type and Name - use these fields to document who requested the new items.
    You can also update information in the following tabs:
    • New Items (Lines) - lists all of the items included in the new item request. You can select items and remove them from the new item request or add additional items to the request.
      Note: You can only add items that have a status of Not Submitted for Approval, Cancelled, or Rejected.
    • Dependencies and References - add change object dependencies and item reference information in these two tabs. See: Creating Relationships.
    • Workflow Approval - approval routing templates are available for routing the new item request definition/approval. Routing templates are typically defined for standard business processes associated with new item creation/approvals. You can also use the approval routing template to route the new item request to different functional groups, providing those groups the ability to participate in the creation and definition of new items. For example, the Design Engineer may be responsible for entering the item's user-defined attributes. See: Defining New Item Request Workflows, Oracle Product Information Management Implementation Guide.
      If the new item request type has more than one workflow attached to a phase, the Switch Template button appears. Click Switch Template to choose a different workflow. To view workflows associated with a different phase, use the Phase pull down list.
    • Attachments - attach any supporting files, URLs, or text. See: Adding Attachments.
    the picture is described in the document text
  4. You can submit the new item request or save it if you wish to enter additional information later.
    Submitting the NIR starts the workflow listed for the Open status. Once you submit it, you cannot add more items to it. If you save it for later, the new item request is saved with a Draft status. Upon submission, if set up, an assignment notification is sent via e-mail.
All new items requiring approval have the item status Pending. After the new item is approved, you can change the item status manually to enable the item for viewing/use outside of the system. You can also define or update its operational attributes.
To add SKUs to a new item request
First, create the SKUs as described in Creating Style and SKU Items. You can then add each SKU to a new item request individually as described above in "To create a new item request:" or you can add multiple SKUs all at once to the same new item request as described below.
  1. In the Overview page for the style item, select the associated SKUs that you want to add to a new item request. Click Add to New Item Request.
    the picture is described in the document text
    From this point on, refer to the steps in "To create a new item request:" above.
To update a new item request
Within a new item request, you can perform the following updates on each individual line item or on all line items, depending on their status and your role:
  • Remove - you can remove an item from a new item request (NIR) as long as the NIR has not been submitted for approval (the NIR status is Draft).
  • Add Items - you can add new items to a NIR when the NIR status is Draft and the item you want to add meets one of the following criteria:
    • the item is not assigned to another NIR and the item's catalog category requires a NIR.
    • if the item is assigned to another NIR, the item's status is Cancelled or Rejected.
      This action effectively copies the item from the original NIR into the NIR currently in view.
  • Update Item Attributes - you can export the item to a spreadsheet, update the attributes, and import the item. See: Mass Updating Items, Item Categories and Item Associations.
  • Add to Category - you can add approved items only to existing catalog categories.
  • Assign Items to Suppliers
    See: Assigning Suppliers to Items
  • Assign Items to SupplierSites
    See: Assigning Suppliers to Items
  • Approve - this action enables you to approve only certain lines in a NIR, while other lines may have a status of Cancelled or Rejected.
  • Reject or Cancel - you can add a rejected or cancelled line to another NIR at a later time, enabling other, approved lines to continue with the current NIR towards final approval.
  • Add to New Item Request - only available for rejected or cancelled items.
    Adding a cancelled or rejected item from one NIR to another effectively copies the cancelled or rejected item to a new NIR.
To manage a new item request from Open to Approved status
A new item request can have many workflows to complete before reaching Approved status. After each workflow is complete, you must promote the NIR to the next workflow.
  1. Navigate to the new item request's Overview page. Select the Workflow tab.
  2. If a Workflow/Approval Status is Completed and the Workflow/Approval Status of the next workflow is Not Started, then click Promote.
    the picture is described in the document text
  3. In the Promote Status: (NIR number) page, select the next status, then click Apply.
  4. The approver can approve, reject, or transfer the new item request from the Notifications page to complete the workflow or perform these actions on each NIR line item individually from the New Items page.
    Notifications Page
    the picture is described in the document text
    To navigate to the New Items page, click the New Item Request Details link in the Notifications page, then select the Lines tab.
    You can now select each new item individually and perform the actions described above in "To update a new item request:", depending on your role.
    New Items Page
    the picture is described in the document text
  5. Once you (the approver) are satisfied that each line item in the NIR is at the correct status (Approved, Rejected, or Cancelled), you must approve, reject, or cancel the entire NIR to complete the workflow.
    From the new item request's Overview page, click on the Approve/Reject link, then approve or reject the NIR.
    the picture is described in the document text
  6. In the item Overview page, the approval status should now reflect the status of the new item request, but the item status remains at Pending. If the approval status is Approved, you can now update the item status to Active.
Related Topics
Creating New Items
Associating New Item Requests with an Item Catalog Category, Oracle Product Information Management Implementation Guide
Performing Actions
Managing People and Roles
Creating Relationships
Managing Workflows
Defining Workflow Templates, Oracle Product Information Management Implementation Guide

Managing Item Imports

You can use any of the following methods to import items and item-related information:
This topic discusses importing items using the Item Open Interface. Additionally, you can import people and user attributes for items. The Open Interface program validates all data before importing it into the production tables. You can also import customer items and customer item cross references from any source using the Customer Item and Customer Item Cross Reference Interfaces.
Important: You cannot update transaction attributes using the Item Open Interface, the Microsoft® Office Excel spreadsheet, or the Import Workbench. You must update them directly. See: Defining Transaction Attributes, Oracle Product Information Management Implementation Guide.
To import items
  1. Load the Item Open Interface table (MTL_SYSTEM_ITEMS_INTERFACE) with the data you want to import.
    See:
    • Open Item Interface, Oracle Inventory User's Guide and Importing Items, Oracle Inventory User's Guide for a full description of how to import items.
    • My Oracle Support (http://metalink.oracle.com) Document ID 730164.1 for instructions on how to use the Oracle Product Information Management public APIs and sample code examples.
To import user attributes for items
  1. Load the Item User-defined Attributes Open Interface table (EGO_ITM_USR_ATTR_INTRFC) with the data you want to import. For detailed help on loading the Open Interface tables, refer to:
    • My Oracle Support (http://metalink.oracle.com) Document ID 730164.1.
    • the Integration Repository. See: Oracle Integration Repository User's Guide.
  2. Navigate to the Inventory Responsibility in Oracle Applications, and click the Inventory link. Then click the Items link
  3. Click the Import link.
  4. Click the Import Item/Item Revision User Attributes link.
    Note: The Parameters form automatically appears when you select a request that requires parameter values.
  5. After entering the values in the required parameter fields, click OK.
  6. Click Submit.
To import item people
  1. Load the Item People Open Interface table (EGO_ITEM_PEOPLE_INTF) with the data you want to import. For detailed help on loading the Open Interface tables, refer to the Oracle Manufacturing Open Interfaces and APIs manual.
  2. Navigate to the Inventory Responsibility in Oracle Applications, and click the Inventory link. Then click the Items link
  3. Click the Import link.
  4. Click the Import Item People link.
    Note: The Parameters form automatically appears when you select a request that requires parameter values.
  5. After entering the values in the required parameter fields, click OK.
  6. Click Submit.
To import customer items and customer item cross references
  1. In the Navigator menu under the Batch Import : Import Items heading, click the Import Customer Items link or the Import Customer Item Cross References link.
    For more information, see:
    • Customer Item and Customer Item Cross Reference Interfaces, Oracle Inventory User's Guide
    • Importing Customer Items, Oracle Inventory User's Guide
    • Importing Customer Item Cross References, Oracle Inventory User's Guide
Related Topics
Creating New Items
EGO_ITM_USR_ATTR_INTRFC
EGO_ITM_USR_ATTR_INTRFC Column Details
EGO_ITEM_PEOPLE_INTF
EGO_ITEM_PEOPLE_INTF Column Details
Importing Items Using a Spreadsheet
Importing Item Revisions Using a Spreadsheet
Importing Item Categories Using a Spreadsheet
Importing Item Organization Assignment Using a Spreadsheet
Importing Item People Assignment Using a Spreadsheet
Updating Existing Items Using a Spreadsheet
Updating Multi-Row Attributes in a Spreadsheet
Overview of Inbound Product Data Synchronization and Data Quality Management

EGO_ITM_USR_ATTR_INTRFC

The following table shows the columns in the EGO_ITM_USR_ATTR_INTRFC database table. For more details about the columns in EGO_ITM_USR_ATTR_INTRFC, see EGO_ITM_USR_ATTR_INTRFC Details.
EGO_ITM_USR_ATTR_INTRFC table
Column Name Data Type Required?
EGO_ITM_USR_ATTR_INTRFC    
TRANSACTION_ID NUMBER Yes
PROCESS_STATUS NUMBER Yes
DATA_SET_ID NUMBER Yes
ORGANIZATION_CODE VARCHAR2(3) Yes
ITEM_NUMBER VARCHAR2(81) Yes
REVISION VARCHAR2(30)  
ROW_IDENTIFIER NUMBER Yes
ATTR_GROUP_INT_NAME VARCHAR2(30) Yes
ATTR_INT_NAME VARCHAR2(30) Yes
ATTR_VALUE_STR VARCHAR2(150)  
ATTR_VALUE_NUM NUMBER  
ATTR_VALUE_DATE DATE  
ATTR_DISP_VALUE VARCHAR2(150)  
ATTR_UOM_DISP_VALUE VARCHAR2(25)  
ATTR_VALUE_UOM VARCHAR2(3)  
TRANSACTION_TYPE VARCHAR2 Yes
ORGANIZATION_ID NUMBER  
INVENTORY_ITEM_ID NUMBER  
ITEM_CATALOG_GROUP_ID NUMBER  
REVISION_ID NUMBER  
ATTR_GROUP_ID NUMBER  
REQUEST_ID NUMBER  
PROGRAM_APPLICATION_ID NUMBER  
PROGRAM_ID NUMBER  
PROGRAM_UPDATE_DATE Date  
CREATED_BY NUMBER(15) Yes
CREATION_DATE DATE Yes
LAST_UPDATED_BY NUMBER(15) Yes
LAST_UPDATE_DATE DATE Yes
LAST_UPDATE_LOGIN NUMBER(15)  

EGO_ITM_USR_ATTR_INTRFC Column Details

TRANSACTION_ID
The Primary Key for this table; its value must be generated from the sequence EGO_IUA_TRANSACTION_ID_S.
PROCESS_STATUS
Whether this row has yet to be processed, is currently being processed, encountered an error, or was successfully processed; its value should correspond to the following constants in EGO_ITEM_USER_ATTRS_CP_PUB: G_PS_TO_BE_PROCESSED, G_PS_IN_PROCESS, G_PS_ERROR, and G_PS_SUCCESS.
DATA_SET_ID
The identifier for a group of rows to be processed together; all rows being processed as part of a single request must share the same DATA_SET_ID, whose value must be generated from the sequence EGO_IUA_DATA_SET_ID_S.
The following column values will be validated and used to populate the ORGANIZATION_ID, INVENTORY_ITEM_ID, ITEM_CATALOG_GROUP_ID, and REVISION_ID columns.
ORGANIZATION_CODE
The organization to which the Item belongs; currently, user-defined attributes are supported only for master organizations, and the organization code is validated to ensure that it refers to a master organization.
ITEM_NUMBER
The item number (such as, concatenated segments) for the item.
REVISION
The three-letter code for the current revision of the item (only used if the attribute group is associated at the item revision level; for attribute groups associated at the item level, leave NULL).
Because the user-defined attributes framework is so flexible, its structure must be flattened out for this interface table. To understand this flattening it is useful to first define a logical attribute group row. For single-row attribute groups, the logical attribute group row is just the collection of attributes in the attribute group, but for multi-row attribute groups, each row in the attribute group is a logical attribute group row. For example, the single-row attribute group "Dimensions," with Attributes "Width" and "Height," has only one logical attribute group row, but multi-row attribute group "Orders," with attributes "Date" and "Price" has as many logical attribute group rows as there are separate orders to be recorded.
Every interface table row contains data for one attribute in a logical attribute group row, and a logical attribute group row spans as many interface table rows as there are attributes in the logical attribute group row. To keep these flattened-out logical attribute group rows in order, there is the ROW_IDENTIFIER column, which uniquely identifies each logical attribute group row (for example, all attributes with the same ROW_IDENTIFIER value will belong to the same logical attribute group row). Thus, if a multi-row attribute group has ten attributes and three rows of values (for example, three logical attribute group rows), then there will be thirty interface table rows for the attribute group and three distinct ROW_IDENTIFIER values in those thirty rows.
ROW_IDENTIFIER
The grouping identifier for a logical attribute group row; its value must be the same for all interface table rows in the logical attribute group row, and no two logical attribute group rows in the same data set may share the same ROW_IDENTIFIER value.
ATTR_GROUP_INT_NAME
The internal name of the attribute group to which the current interface table row's attribute belongs.
ATTR_INT_NAME
The internal name of the attribute for which the current interface table row holds a value.
ATTR_VALUE_STR
The value for the current interface table row's attribute if its data type is string.
ATTR_VALUE_NUM
The value for the current interface table row's attribute if its data type is number.
ATTR_VALUE_DATE
The value for the current interface table row's attribute if its data type is date. Values will be converted to and from date data types using the format specified in EGO_USER_ATTRS_DATA_PVT.G_DATE_FORMAT.
ATTR_DISP_VALUE
The value for the current interface table row's attribute (as a string, regardless of its data type) if the attribute has a value set with separate display and internal values (for example, value sets with validation type of independent or table). In all other cases, use the preceding three columns.
ATTR_UOM_DISP_VALUE
The description of the unit of measure associated with the attribute.
ATTR_VALUE_UOM
The internal value of the unit of measure associated with the attribute.
TRANSACTION_TYPE
The mode of processing for a logical attribute group row; its value should correspond to the following constants in EGO_USER_ATTRS_DATA_PVT: G_DELETE_MODE, G_UPDATE_MODE, G_SYNC_MODE (which either creates or updates, as appropriate), and G_CREATE_MODE. Note that rows will be processed in the order they were just presented (for example, deletion first, followed by updates and synchronization, with creation last), in accordance with Oracle Applications standards. Typical values of these constants are: CREATE, SYNC, UPDATE, or DELETE.
ORGANIZATION_ID
This column is for internal use, and any user-entered values are ignored.
INVENTORY_ITEM_ID
This column is also for internal use, but the user may enter the inventory item ID if known. If the inventory item ID is passed for a given item number, it will save conversion time from item number into inventory item ID; the inventory item ID will still be validated internally, because it will be used with the organization ID to find the item catalog group ID (so rows with invalid inventory item IDs will time-out during the item catalog ID fetching step).
ITEM_CATALOG_GROUP_ID
This column is for internal use, and any user-entered values are ignored.
REVISION_ID
This column is for internal use, but the user may enter the revision ID if known (and if this interface table row belongs to an attribute group that is associated at the item revision level). Doing so will save conversion time.
ATTR_GROUP_ID
This column is provided in case the user knows the attribute group ID for this interface table row's attribute group. If left blank, the attribute group internal name is used to identify the attribute group.
REQUEST_ID
This column is for internal use (to record the concurrent program request that ordered the processing of this row).
PROGRAM_APPLICATION_ID
This column is for internal use (to record the application ID of the concurrent program that processed this row).
PROGRAM_ID
This column is for internal use (to record the ID of the concurrent program that processed this row).
PROGRAM_UPDATE_DATE
This column is for internal use (to record the time the concurrent program processed this row).
The remaining columns are the standard "Who" columns, and their values must be entered when you load the interface table.

EGO_ITEM_PEOPLE_INTF

The following table shows the columns in the EGO_ITEM_PEOPLE_INTF database table. For more details about the columns in EGO_ITEM_PEOPLE_INTF, see EGO_ITEM_PEOPLE_INTF Details.
EGO_ITEM_PEOPLE_INTF table
Column Name Data Type Required?
INVENTORY_ITEM_ID NUMBER(15) No
ORGANIZATION_ID NUMBER(15) No
GRANTEE_PARTY_ID NUMBER(15) No
INTERNAL_ROLE_ID NUMBER(15) No
INTERNAL_ROLE_NAME VARCHAR2(30) No
LAST_UPDATE_DATE DATE No
LAST_UPDATED_BY   No
CREATION_DATE DATE No
CREATED_BY NUMBER(15) No
LAST_UPDATE_LOGIN NUMBER(15) No
REQUEST_ID NUMBER(15) No
PROGRAM_APPLICATION_ID NUMBER(15) No
PROGRAM_ID NUMBER(15) No
PROGRAM_UPDATE_DATE DATE No
ITEM NUMBER VARCHAR2(81) Yes
ORGANIZATION_CODE VARCHAR2(3) Yes
DISPLAY_ROLE_NAME VARCHAR2(80) Yes
GRANTEE_TYPE VARCHAR2(8) Yes
GRANTEE_NAME VARCHAR2(360) Yes
START_DATE DATE Yes
END_DATE DATE No
TRANSACTION_TYPE VARCHAR2(10) Yes
TRANSACTION_ID NUMBER(15) Yes
PROCESS_STATUS NUMBER(15) Yes
DATA_SET_ID NUMBER(15) Yes

EGO_ITEM_PEOPLE_INTF Column Details

INVENTORY_ITEM_ID
Identifier for the Inventory item on which the role is to be granted. The value is obtained from MTL_SYSTEM_ITEMS_B for a given item. This column is also for internal use, but the user may enter the inventory item ID if known. If the inventory item ID is passed for a given item number, it will save conversion time from item number into inventory item ID; the inventory item ID will still be validated internally.
ORGANIZATION_ID
The item ID and the organization ID form the unique key combination on which the role is to be granted.
GRANTEE_PARTY_ID
The person ID, group ID or part ID that gets the grant on the item ID and organization ID.
INTERNAL_ROLE_ID
The identifier of the role to be granted.
INTERNAL_ROLE_NAME
The internal role definition name; this name is unique.
LAST_UPDATE_DATE
One of the five standard "WHO" columns.
LAST_UPDATED_BY
One of the five standard "WHO" columns.
CREATION_DATE
One of the five standard "WHO" columns.
CREATED_BY
One of the five standard "WHO" columns.
LAST_UPDATE_LOGIN
One of the five standard "WHO" columns.
REQUEST_ID
The concurrent program submission request ID.
PROGRAM_APPLICATION_ID
The concurrent program application ID. This column is for internal use to record the application ID of the concurrent program that processed this row.
PROGRAM_ID
The concurrent program ID. This column is for internal use to record the ID of the concurrent program that processed this row.
PROGRAM_UPDATE_DATE
The concurrent program update date. This column is for internal use to record the time the concurrent program processed this row.
ITEM_NUMBER
The inventory item number (such as, concatenated segments) for the item. The INVENTORY_ITEM_ID is derived from the ITEM_NUMBER.
ORGANIZATION_CODE
The Inventory Organization Code. Should be one of the values in the MTL_PARAMETERS table column ORGANIZATION_CODE.
DISPLAY_ROLE_NAME
The display name for the role; this is one of the values in the FND_MENUS_VL table column USER_MENU_NAME.
GRANTEE_TYPE
The type of grantee. Has one of the following values: USER, GROUP, or GLOBAL.
GRANTEE_NAME
The name of the grantee. This name can be a user name, group name, or all users, depending on the grantee type specified (PERSON, GROUP or GLOBAL).
START_DATE
The grant start date. The grantee gains access to the item on this date.
END_DATE
The grant end date. The grantee loses access to the item on this date.
TRANSACTION_TYPE
The type of transaction. Valid values are: CREATE, SYNC, UPDATE, or DELETE.
TRANSACTION_ID
The unique identifier of the line. The value is retrieved from EGO_IPI_TRANSACTION_ID_S.
PROCESS_STATUS
Indicates the status of the line. Values are:
1 - To Be Processe, 2 - In Process, 3 - Error, 4 - Success, 5 - Warning
DATA_SET_ID
Unique identifier that indicates the subset of data to be processed (like the job ID). Each line that is newly uploaded in the interface table needs to be assigned a unique ID that is be used during the concurrent program request submission. The value is selected from the PL/SQL API: EGO_ITEM_PEOPLE_IMPORT_PKG.get_curr_dataset_id.

Importing Items Using a Spreadsheet

You can use a Microsoft Excel spreadsheet to import items into the system. Before doing so, you must first have defined import formats for the particular item catalog category you wish to use, and you must also have the appropriate version of the Excel spreadsheet installed.
You can use the same spreadsheet for multiple uploads, and also across different sessions for the same user. To upload the same spreadsheet during another session, open the spreadsheet you wish to upload, and select Upload from the Oracle menu in the menu bar. After you log in and choose the appropriate responsibility, you can immediately begin to upload this spreadsheet again.
Whenever you enter new or existing data in the spreadsheet, the Upl column displays a flag, making it easier to scan the spreadsheet and for rows that have been changed.
You can include multi-row attribute groups in your item import formats. To do so, make sure that the rows in the spreadsheet that you are using for updating multi-row attributes do not contain any attribute values other then the org code, item number, item revision (if applicable), and the user-defined multi-row attribute values. When importing sequence generated item numbers with multi-row attribute groups, use dummy strings for the item numbers, such as $$SG$$1, $$SG$$2, and so on, in the WebADI Excel field for the item number. The import program uses this dummy string to determine which row belongs to which item.
Caution: If you include values for other primary (for example, item status, or lifecycle) or single-row user-defined attributes in the same rows as the multi-row attributes, then the updates will fail.
Note: You can import items with multi-row attributes for multiple organizations during a single concurrent request.
Important: You cannot update transaction attributes using the Item Open Interface, the Microsoft® Office Excel spreadsheet, or the Import Workbench. You must update them directly. See: Defining Transaction Attributes, Oracle Product Information Management Implementation Guide.
Items uploaded to the system from a spreadsheet become, by default, Engineering items. If you wish to upload a non-Engineering item, then include an available primary attribute column called "Engineering Item Flag" in your import format. When uploading the spreadsheet, identify such items in this column by specifying the value "Yes" or "No" in this column. If you leave the column blank, the item once again defaults to an Engineering item.
Prerequisites
  • Optionally, define an import format for the item catalog category you plan to use when importing items. See: Defining Item Catalog Import Formats, Oracle Product Information Management Implementation Guide
To import items using a spreadsheet
  1. In the Applications tree menu, click the Import from Excel link.
  2. On the Import page, select the Items object and click Continue.
    Note: An import format should already be defined for items or item revisions. Item categories do not have a defined import format that is associated with an item catalog category. Instead, a predefined format is used for all item category imports. The columns in this format are identical to the interface table. Predefined formats matching the interface tables are used for item people, item organization assignment, and manufacturing part number imports, too.
  3. On the Import: Item page, select an item catalog category and then click Go. The item catalog category determines which import formats are available for use.
    Note: If you do not select an item catalog category, the default System Item Import Format is available for use. If an import format has not yet been defined for an item catalog category that you select, then the default System Item Import Format is available for use. The System Item Import Format does not appear if you select an item catalog category that already has import formats defined. Neither users nor the system administrator can modify the System Item Import Format.
  4. When the Import: Item page refreshes with the import formats available for the item catalog category, select the import format you wish to use and click Import.
    Note: If a default import format has been specified for the item catalog category, it will already be selected.
  5. On the Select Viewer page, select the version of Excel that you are using and click Next. You cannot enable or disable Reporting. Also, Language has only one choice, which is already selected.
  6. A Download window presents processing messages. Click Close when the transfer is complete. The Excel spreadsheet also opens.
  7. In the spreadsheet, primary attributes are listed first (on the left), and user-defined attributes appear after (on the right). When entering values into the spreadsheet, you must use one of the following Transaction Types:
    Sync
    If the item already exists, the spreadsheet values are used to update it. If the item does not already exist, a new one is created using the spreadsheet values. If the Sync creates a new item, then the mandatory attributes for Create are also mandatory for the Sync. If the Sync updates an existing item, then the mandatory attributes for Update are also mandatory for the Sync.
    Note: To delete an existing value in a record, enter the following data in the appropriate column of the spreadsheet:

    For field type: Enter value:
    Date 31-DEC-9999
    Character !
    Numeric 9.99E125
    If you want to retain an existing value in a record, leave it blank in the spreadsheet.
    Exception: In the user defined attributes interface table, when you want to delete an existing value in any of the following fields, use the value !. If you want to retain an existing value in a record, no entry is necessary.
    • ATTR_DISP_VALUE
    • ATTR_VALUE_STR
    • ATTR_NUM_VALUE
    • ATTR_VALUE_DATE
    Create
    A new item is created using the values entered in the spreadsheet. The following attributes are mandatory when using this transaction type:
    • Item
    • Organization Code
    • Primary Unit of Measure
    • Description
    Note: Description is a primary attribute, but appears on the right side of the spreadsheet among the user-defined attributes. It is placed here so that long descriptions will not disrupt the flow of the spreadsheet. If the description is function-generated, the system generates the description during the item creation process.
    Some attribute columns also utilize poplists and LOVs, depending on the attribute definition. You can also make updates to multi-row attributes.
    Make a note of the Result Format Usage ID at the top of the spreadsheet. You will need this ID later when you upload the spreadsheet in the system.

    • If the import format contains attributes from attribute groups that are associated with the supplier business entity, then you must enter a value in the key column Supplier Name. If the import format contains attributes from attribute groups that are associated with the supplier site or supplier site organization business entities, then you must enter a value in the key column Supplier Site as well as Supplier Name. If you need to enter a retail site, enter the retail site organization code in the existing Organization Code column.
    • When importing style and SKU item information:
      • Use the Style column to indicate if the item is a style item (Yes or No).
      • Use the Style Item column to identify the style item for an SKU item row.
      • You must define a style item before you define its child SKU items. You can define the style and SKU items within the same spreadsheet, but the new style item must be in a row above the new SKU items.
      • Variant attribute columns do not have a list of values in the spreadsheet to choose from. For style items, enter the child value set name in the variant attribute column. For SKU items, enter the variant attribute value in this column.
        For example, assign the variant attribute group Color to a style item. Color has multiple value sets: fall, winter, and spring colors. Assign the value set Fall to the style item in the variant attribute column. For an associated SKU, enter a fall color attribute value, such as brown or orange, in the same column.
    Tip: You can rename columns, wrap the column name text, or widen the columns so the column names are easier to read and understand. You must unprotect the spreadsheet before reformatting the columns.
  8. After data entry is complete, select Upload from the Oracle menu in the toolbar.
  9. In the Upload Parameters window, enter the Result Format Usage ID and check the Automatically Submit Concurrent Process box, and then click Proceed to Upload.
  10. In the Oracle Web ADI window, click Upload. After the upload process completes, a message appears with the Concurrent Request number. Make a note of this number, as you will need it later when you access the view log for the concurrent request. Click Close when the process messages complete.
  11. Return to the Applications tree menu and click the View Concurrent Requests link.
    Note: It is recommended that you review the concurrent process view log to ensure that the upload process was successful.
  12. On the View Concurrent Requests page, click the Details icon.
  13. On the Request Details page, click View Log.
  14. From the View Log, paste the URL string in a web browser to view any errors. If no errors appear, the upload was successful.
Related Topics
Creating New Items

Importing Item Revisions Using a Spreadsheet

You can use a Microsoft Excel spreadsheet to import item revisions into the system. Before doing so, you must first have defined import formats (see: Defining Item Catalog Import Formats , Oracle Product Information Management Implementation Guide)for the particular item catalog category you wish to use, and you must also have the appropriate version of the Excel spreadsheet installed.
You can use the same spreadsheet for multiple uploads, and also across different sessions for the same user. To upload the same spreadsheet during another session, open the spreadsheet you wish to upload, and select Upload from the Oracle menu in the menu bar. After you log in and choose the appropriate responsibility, you can immediately begin to upload this spreadsheet again.
Whenever you enter new or existing data in the spreadsheet, the Upl column displays a flag, making it easier to scan the spreadsheet and for rows that have been changed.
Item revisions uploaded to the system from a spreadsheet become, by default, Engineering items. If you wish to upload a non-Engineering item, then include an available primary attribute column called "Engineering Item Flag" in your import format. When uploading the spreadsheet, identify such items in this column by specifying the value "Yes" or "No" in this column. If you leave the column blank, the item once again defaults to an Engineering item.
To import item revisions using an Excel spreadsheet
  1. In the Applications tree menu, click the Import from Excel link.
  2. On the Import page, select Item Revisions and click Continue.
    An import format should already be defined for items or item revisions. Item categories do not have a defined import format that is associated with an item catalog category. Instead, a predefined format is used for all item category imports. The columns in this format are identical to the interface table.
  3. On the Import: Item Revision page, select an item catalog category and then click Go. The item catalog category determines which import formats are available for use.
    Note: If you do not select an item catalog category, the default System Item Revision Import Format is available for use. If an import format has not yet been defined for an item catalog category that you select, then the default System Item Revision Import Format is available for use. Neither users nor the system administrator can modify the System Item Revision Import Format.
  4. When the Import: Item Revision page refreshes with the import formats available for the item catalog category, select the import format you wish to use and click Import. If a default import format has been specified for the item catalog category, it will already be selected.
  5. On the Select Viewer page, select the version of Excel that you are using and click Next. You cannot enable or disable Reporting.
  6. A Download window presents processing messages. Click Close when the transfer is complete. The Excel spreadsheet also opens.
  7. In the spreadsheet, primary attributes are listed first (on the left), and user-defined attributes appear after (on the right). When entering values into the spreadsheet, you must use one of the following Transaction Types:
    Sync
    If the item revision already exists, the spreadsheet values are used to update it. If the item revision does not already exist, it is created using the spreadsheet values. If the Sync creates a new item revision, then the mandatory attributes for Create are also mandatory for the Sync. If the Sync updates an existing item revision, then the mandatory attributes for Update are also mandatory for the Sync
    Create
    A new item revision is created using the values entered in the spreadsheet. The following attributes are mandatory when using this transaction type:
    • Item
    • Organization Code
    • Revision
    • Revision Label
    • Effective Date
    Note: Description is a primary attribute, but appears on the right side of the spreadsheet among the user-defined attributes. It is placed here so that long descriptions will not disrupt the flow of the spreadsheet.
    Update
    Existing item revisions are updated using the values entered in the spreadsheet. The following attributes are mandatory when using this transaction type:
    • Item
    • Organization Code
    • Revision
    Note: To delete an existing value in a record, enter the following data in the appropriate column of the spreadsheet:

    For field type: Enter value:
    Date 31-DEC-9999
    Character !
    Numeric 9.99E125
    If you want to retain an existing value in a record, enter NULL in the appropriate column of the spreadsheet.
    Exception: In the user defined attributes interface table, when you want to delete an existing value in any of the following fields, use the value !. If you want to retain an existing value in a record, no entry is necessary.
    • ATTR_DISP_VALUE
    • ATTR_VALUE_STR
    • ATTR_NUM_VALUE
    • ATTR_VALUE_DATE
    Make a note of the Result Format Usage ID at the top of the spreadsheet. You will need this ID later when you upload the spreadsheet in the system.
    You can also make updates to multi-row attributes.
  8. After data entry is complete, select Upload from the Oracle menu in the toolbar.
  9. In the Upload Parameters window, enter the following and then click Upload.
    • Batch Name
    • Import:
      • Immediately on data load - automatically updates the Oracle Item Master table with matched data.
      • Schedule Data and Time - select the date and time to import the confirmed items or structures in the batch.
      • None - leaves the data in the Import Workbench. You can manually import the data at a later time.
    • Select whether to create a new change order, add to an existing change order, or to not create a change order.
    • Select whether to create a new item request:
      • None
      • One per Item
      • One per Item Catalog Category
  10. Click Upload. After the upload process completes, a message appears with the Concurrent Request number. Make a note of this number, as you will need it later when you access the view log for the concurrent request. Click Close when the process messages complete.
  11. Return to the Applications tree menu and click the View Concurrent Requests link.
    Note: It is recommended that you check the concurrent process view log to ensure that the upload process was successful.
  12. On the View Concurrent Requests page, click the Details icon.
  13. On the Request Details page, click View Log.
  14. From the View Log, paste the URL string in a web browser to view any errors. If no errors appear, the upload was successful.
Note: If you created a new revision containing user defined attributes defined at the item revision level and enabling the change order option, then the new revision contains the item revision user defined attributes copied from the current revision. Any changed item revision user defined attributes appear in the new revision's change order attribute change section.

Importing Item Categories Using a Spreadsheet

You can use a Microsoft Excel spreadsheet to import new, delete old, or update existing item categories in the system. Before doing so, you must also have the appropriate version of the Excel spreadsheet installed.
Whenever you enter new or existing data in the spreadsheet, the Upl column displays a flag, making it easier to scan the spreadsheet for rows that have been changed.
To import item categories using an Excel spreadsheet
  1. In the Applications tree menu, click the Import from Excel link.
  2. On the Import page, select Item Categories and click Continue.
    Item categories do not have a defined import format that is associated with an item catalog category. Instead, a predefined format is used for all item category imports. The columns in this format are identical to the interface table.
  3. On the Import: Item Catalog Categories Assignment page, click Import.
    When your spreadsheet opens, it displays the same item category columns that appear on this page, plus an old category column. Only use the old category column when updating existing item categories.
  4. On the Select Settings page, select the version of Excel that you are using and click Next.
    You cannot enable or disable Reporting. Also, Language has one choice, which is already selected.
  5. A Download window presents processing messages. Click Close when the transfer is complete. The Excel spreadsheet also opens.
    Note that the columns that appeared on the Import: Item Category Assignment page have been exported to the spreadsheet.
  6. When entering values into the spreadsheet, use the one of the following Transaction Types:
    • Create
      Creates a new item using the values entered in the spreadsheet.
    • Delete
      Deletes the item specified in the spreadsheet row.
    • Update
      Makes the changes specified to the item in the spreadsheet row.
    The following attributes are mandatory when using these Transaction Types:
    • Item
    • Organization Code
    • Catalog
    • Category
    • Old Category - mandatory for the Update transaction type only.
    Tip: You can rename columns, wrap the column name text, or widen the columns so the column names are easier to read and understand. You must unprotect the spreadsheet before reformatting the columns.
    Make a note of the Record Set ID at the top of the spreadsheet. You will need this ID later when you upload the spreadsheet to the system.
  7. After data entry is complete, select Upload from the Oracle menu in the toolbar.
  8. In the Upload Parameters window, enter the Record Set ID.
    In the Upload Processed Records menu, select Yes. If you select No, your data is sent to the user interface table only and is not processed; Consequently, debugging is not possible.
    In the Delete Processed Records menu, select No. If you select Yes, all records corresponding to the current Record Set ID are cleared from the interface table.
    Click Proceed to Upload.
  9. In the Oracle Web ADI window, wait for the Ready message and click Upload.
    Show Trace Messages is, by default, not selected. Do not change this setting unless you wish to have trace information provided via your parameters.
    Clicking Parameters enables you to modify your parameters.
    Important: When the Upload completes, a Concurrent Request Number appears in this window. Make note of this number, as you can later use it to view the results of the upload process (for example, to view whether or not the upload was successful).
  10. If you do not wish to confirm that the upload was successful, you are finished. If you wish to view the results of the upload process, return to the Applications tree menu and click the View Concurrent Requests link.
    It is recommended that you check the concurrent process view log to ensure that the upload process was successful.
  11. On the Requests page, select Completed and click Go. Look for your Concurrent Request Number to locate your process. If it does not appear, wait and repeat this step. You can also select Pending and click Go to view pending requests. Locate your process in the Results table and click the Details icon.
  12. On the Request Details page, click View Log.
  13. From the View Log, paste the URL string in a web browser to view any errors. If no errors appear, the upload was successful.

Importing Item Organization Assignment Using a Spreadsheet

You can use a Microsoft Excel spreadsheet to import item organization assignments into the system.
You can use the same spreadsheet for multiple uploads, as well as across different sessions for the same user. To upload the same spreadsheet in another session, open the spreadsheet and select Upload from the Oracle menu in the tool bar. After you log in and select the appropriate responsibility, you can begin uploading the spreadsheet again.
Whenever you enter new or existing data in the spreadsheet, the Upl column displays a flag, making it easier to scan the spreadsheet for rows that have been changed.
Important: Users can only assign items to those organizations to which they have permission. See: Overview of Roles and Role Based Security, Oracle Product Information Management Implementation Guide
Tip: You can rename columns, wrap the column name text, or widen the columns so the column names are easier to read and understand. You must unprotect the spreadsheet before reformatting the columns.
Import Item Organization Assignment Using a Spreadsheet
  1. In the Navigator page, click the Import from Excel link. This link is located under Batch Import : Import Items.
  2. In the Import page, select Item Organization Assignment and click Continue.
  3. In the Import: Item Organization Assignment page, click Import.
  4. In the Select: Viewer page, select the appropriate version of Excel and click Next.
    The Processing: Creating Document page appears. Wait until the Excel application is ready.
    The Confirmation page appears. An Excel spreadsheet opens and the Confirmation page returns to the Navigator page. Alternately, click Return to return to the Navigator page.
Enter Data in the Spreadsheet
  1. Enter the organization assignments for each item in the spreadsheet.
    Organization Code - Select your organization from the drop down list.
    Item - Enter the item number. For instance, M1000.
    Primary Unit of Measure - Enter the display name of the unit of measure. For instance, Each.
    Note the Set Process ID at the top of the spreadsheet. You will need it to upload the spreadsheet in the system.
  2. Select Upload from the Oracle menu in the tool bar.
  3. In the Upload Parameters window, enter the Set Process ID and click Upload.
  4. After upload, a message appears with the Concurrent Request number. Note this number. You will need it to verify the view log for the concurrent request. Click Close when the process messages complete.
    Tip: It is recommended that you review the concurrent process view log to ensure that the upload was successful.
View Concurrent Requests
  1. Return to the Navigator page and click the View Concurrent Requests link. This link is located under Workflow and Request.
  2. In the Requests page, click the Details icon.
  3. In the Request Details page, click View Log. If no errors are declared in the view log, the upload was successful.

Importing Item People Assignment Using a Spreadsheet

You can use a Microsoft Excel spreadsheet to import item people assignments into the system.
You can use the same spreadsheet for multiple uploads, as well as across different sessions for the same user. To upload the same spreadsheet in another session, open the spreadsheet and select Upload from the Oracle menu in the tool bar. After you log in and select the appropriate responsibility, you can begin uploading the spreadsheet again.
Whenever you enter new or existing data in the spreadsheet, the Upl column displays a flag, making it easier to scan the spreadsheet for rows that have been changed.
Import Item People Assignment Using a Spreadsheet
  1. In the Navigator page, click the Import from Excel link. This link is located under Batch Import : Item Imports.
  2. In the Import page, select Item People Assignment and click Continue.
  3. In the Import: Item People Assignment page, click Import.
  4. In the Select: Viewer page, select the appropriate version of Excel and click Next.
    The Processing: Creating Document page appears. Wait until the Excel application is ready.
    The Confirmation page appears. An Excel spreadsheet opens and the Confirmation page returns to the Navigator page. Alternately, click Return to return to the Navigator page.
Enter Data in the Spreadsheet
  1. Use one of the following Transaction Types when entering values into the spreadsheet:
    • Create
      Select this option to create a new item people assignment using the values entered in the spreadsheet.
    • Delete
      Select this option to delete an existing item people assignment.
    • Sync
      Select this option to:
      • Create an item people assignment if it does not exist in the system.
      • Update an item people assignment if it exists in the system.
    • Update
      Select this option to update an existing item people assignment using the values entered in the spreadsheet.

      • You can update the End Date only in an existing item people assignment.
      • For style and SKU items only:
        People assignments default from style to SKU items. If you make an item people assignment for a style item, this assignment automatically defaults to the style item's SKUs. However, if you change the end date of the style item, the end date of the associated SKUs does not change. You must change the end date of each SKU.
    Note the Data Set ID at the top of the spreadsheet. You will need it to upload the spreadsheet in the system.
  2. Enter values for the attributes.
    Transaction Type - Select the appropriate transaction type from the drop down list.
    Organization Code - Select your organization from the drop down list.
    Item - Enter the item number. For instance, M1000.
    Role - Select the display name of the role from the drop down list. For instance, Design Engineer.
    Type - Select the type of user from the drop down list. For instance, Group.
    Name - Enter the name of the person, group, or company. Leave the cell empty for type 'All Users.'
    Start Date - Enter the start date of the grants. Date format - mm/dd/yyyy.
    End Date - Enter the end date of the grant. Date format - mm/dd/yyyy.
  3. Select Upload from the Oracle menu in the tool bar.
  4. In the Upload Parameters window, enter the Data Set ID and click Upload.
  5. After upload, a message appears with the Concurrent Request number. Note this number. You will need it to verify the view log for the concurrent request. Click Close when the process messages complete.
    Tip: It is recommended that you review the concurrent process view log to ensure that the upload was successful.
View Concurrent Requests
  1. Return to the Navigator page and click the View Concurrent Requests link. This link is located under Workflow and Request.
  2. In the Requests page, click the Details icon.
  3. In the Request Details page, click View Log. If no errors are declared in the view log, the upload was successful.

Updating Existing Items

You can choose from two methods to update existing items. Both methods provide the same result.
  • Microsoft® Office Excel spreadsheet - use this method if any of the following apply:
    • You need time to determine the changes to make. You can save the spreadsheet and work on it later.
    • When you have less than 200 items to update.
    • You want to update many different types of item fields at once. For example, you want to update many items' attributes, organizations, and categories at the same time.
  • Mass update function - Use this method if any of the following apply:
    • Change control is necessary.
    • Your environment is characterized by many items and/or organizations.
    • You want to update certain fields for many items. Choose from the following mass update functions:
      • Update Master Item Attributes
      • Update Organization Item Attributes
      • Assign Items to Organizations
      • Assign Items to Categories
      • Unassign Items from Categories
      • Reassign Categories

Updating Existing Items Using a Spreadsheet

You can use a Microsoft® Office Excel spreadsheet to edit/update existing items. Before doing so, you must also have the appropriate version of the Excel spreadsheet installed.
Whenever you enter new or existing data in the spreadsheet, the Upl column displays a flag, making it easier to scan the spreadsheet for rows that have been changed.
Items uploaded from a spreadsheet become, by default, Engineering items. If you wish to upload a non-Engineering item, then include an available primary attribute column called "Engineering Item Flag" in your import format. When uploading the spreadsheet, identify such items in this column by specifying the value "Yes" or "No". If you leave the column blank, the item once again defaults to an Engineering item.
To update existing items, you must first search for the items, and then import the search results into the spreadsheet. Search results are limited to 200 items or less. Using this spreadsheet import/update saves you time, as the spreadsheet now contains the attributes/columns needed to update the specific items you wish to change.
To update existing items using an Excel spreadsheet
  1. In the Applications tree menu, use either of the searches (Simple or Advanced) to locate the item you wish to update.
  2. On the Search Results page, click Export All Items.
  3. On the Select Viewer page, select the version of Excel that you are using and click Next. You cannot enable or disable Reporting.
  4. An Information page and Download window present processing messages. Follow the instructions in these messages. Click Close when the transfer is complete. The Excel spreadsheet also opens. Note that all your search results have been exported to the spreadsheet.
  5. In the spreadsheet, primary attributes are listed first (on the left), and user-defined attributes appear after (on the right). When entering values into the spreadsheet, you must use one of the following Transaction Types:
    Sync
    If the item already exists, the spreadsheet values are used to update it. If the item does not already exist, a new one is created using the spreadsheet values. If the Sync creates a new item, then the mandatory attributes for Create are also mandatory for the Sync. If the Sync updates an existing item, then the mandatory attributes for Update are also mandatory for the Sync.
    Create
    A new item is created using the values entered in the spreadsheet. The following attributes are mandatory when using this transaction type:
    • Item
    • Organization Code
    • Primary Unit of Measure
    • Description
    Note: Description is a primary attribute, but appears on the right side of the spreadsheet among the user-defined attributes. It is placed here so that long descriptions will not disrupt the flow of the spreadsheet.
    Update
    Existing items are updated using the values entered in the spreadsheet. The following attributes are mandatory when using this transaction type:
    • Item
    • Organization Code
    Note: To delete an existing value in a record, enter the following data in the appropriate column of the spreadsheet:

    For field type: Enter value:
    Date 31-DEC-9999
    Character !
    Numeric 9.99E125
    If you want to retain an existing value in a record, enter NULL in the appropriate column of the spreadsheet.
    Exception: In the user defined attributes interface table, when you want to delete an existing value in any of the following fields, use the value !. If you want to retain an existing value in a record, no entry is necessary.
    • ATTR_DISP_VALUE
    • ATTR_VALUE_STR
    • ATTR_NUM_VALUE
    • ATTR_VALUE_DATE
    Important: Make a note of the Result Format Usage ID at the top of the spreadsheet. You will need this ID later when you upload the spreadsheet in the system.
  6. After data entry is complete, select Upload from the Oracle menu in the toolbar.
  7. In the Upload Parameters window, enter the following and then click Upload.
    • Batch Name
    • Import:
      • Immediately on data load - automatically updates the Oracle Item Master table with matched data.
      • Schedule Data and Time - select the date and time to import the confirmed items or structures in the batch.
      • None - leaves the data in the Import Workbench. You can manually import the data at a later time.
    • Select whether to create a new change order, add to an existing change order, or to not create a change order.
    • Select whether to create a new item request:
      • None
      • One per Item
      • One per Item Catalog Category
  8. After the upload process completes, a message appears with the Concurrent Request number. Make a note of this number, as you will need it later when you access the view log for the concurrent request. Click Close when the process messages complete.
  9. Return to the Applications tree menu and click the "View Concurrent Requests" link. It is recommended that you check the concurrent process view log to ensure that the upload process was successful.
  10. On the View Concurrent Requests page, click the Details icon.
  11. On the Request Details page, click View Log.
  12. From the View Log, paste the URL string in a web browser to view any errors. If no errors appear, the upload was successful.

Mass Updating Items, Categories and Associations

You can use the Mass Update functions to edit and update items, categories and item assignments when you want to change many items or categories and/or many organizations. Mass update item searches are not subject to the 200 item search limit like the spreadsheet option (see: Updating Existing Items Using a Spreadsheet).
Choose from the following mass update functions:
  • Update Master Item Attributes
  • Update Organization Item Attributes
  • Update Supplier Assignment Attributes
  • Update SupplierSite Assignment Attributes
  • Update SupplierSite-Org Assignment Attributes
  • Assign Items to Organizations
  • Assign Items to Categories
  • Unassign Items from Categories
  • Reassign Categories
  • Assign Items to Suppliers
  • Assign Items to SupplierSites
  • Assign Items to SupplierSite-Organizations
All mass update functions are located in the Mass Change folder/section in the navigation menu.
To mass update master item attributes
  1. From the navigation menu, in the Mass Change section, select Update Master Item Attributes.
  2. In the Update Master Item Attributes: Select Items page, use either Simple Search or Advanced Search to find the items you want to update. See: Searching for Items. The Update Master Item Attributes: Review Results page appears.
  3. Review the search results. If the search results returned the expected items, click Export. If you need to refine the search criteria, click Back.
  4. After clicking Export, the Select Viewer page appears. Select the version of Microsoft Office® Excel on your desktop.
    Follow the instructions on your screen to download the file to your desktop. Update the spreadsheet, then upload it as described in Updating Existing Items Using a Spreadsheet.
To mass update organization item attributes
  1. Navigate to the Update Organization Item Attributes: Select Items page.
  2. Use either Simple Search or Advanced Search to find the items you want to update. See: Searching for Items. The Update Organization Item Attributes: Review Results page appears.
  3. Review the search results. If the search results returned the expected items, click Next and the Select Organization page appears. If you need to refine the search criteria, click Back.
  4. Search for an organization using one of the following fields:
    • Organization Code
    • Organization Name
    • Hierarchy
    Click Next and the Update Organization Item Attributes: Review Organizations page lists all organizations matching your search criteria.
  5. Select the organizations you want to update, then click Next and the Update Organization Attributes: Review Results page appears. If you want to refine the Organization search, click Back. Otherwise, click Export.
  6. The Select Viewer page appears. Select the version of Microsoft Office® Excel on your desktop.
    Follow the instructions on your screen to download the file to your desktop. Update the spreadsheet, then upload it as described in To update existing items using an Excel spreadsheet with the following exceptions in the Upload Parameters window:
    • Enter the Batch Name
    • Select an import option:
      • Immediately on data load - automatically updates the Oracle Item Master table with matched data.
      • Schedule Data and Time - select the date and time to import the confirmed items or structures in the batch.
      • None - leaves the data in the Import Workbench. You can manually import the data at a later time.
    • Select whether to create a new change order, add to an existing change order, or to not create a change order.
To mass update supplier, supplier site, and supplier site organization assignment attributes
The process for mass updating supplier, supplier site, and supplier site organization assignment attributes is almost the same. The only difference between mass updating assignment attributes for the three different supplier business objects is the page name. For example, when mass updating supplier assignment attributes, the first page name is Update Supplier Assignment Attributes: Supplier Assignment Search. When mass updating supplier site organization assignment attributes, the first page name is Update SupplierSite-Organization Assignment Attributes: SupplierSite-Organization Assignment Search. The following steps assume that you are mass updating supplier assignment attributes.
  1. Navigate to the Update Supplier Assignment Attributes: Supplier Assignment Search page.
  2. Use either Simple Search or Advanced Search to find the items you want to update. See: Searching for Items. The Update Supplier Assignment Attributes: Review Supplier Assignment page appears.
  3. Review the search results. If the search results returned the expected items, click Export and the Select Viewer page appears. If you need to refine the search criteria, click Back.
  4. Select the version of Microsoft Office® Excel on your desktop.
    Follow the instructions on your screen to download the file to your desktop. Update the spreadsheet, then upload it as described in To update existing items using an Excel spreadsheet .
To mass assign items to organizations
  1. Navigate to the Assign Items to Organizations: Select Items page.
  2. Enter search criteria, then click Next. See: Searching for Items. The Assign Items to Organizations: Review Items page appears.
  3. Review the search results. You can filter the search results and select the items that you want to assign. If the search results returned the expected items, click Next and the Assign Items to Organizations: Select Organizations page appears. If you need to refine the search criteria, click Back.
  4. Search for an organization using one of the following fields:
    • Organization Code
    • Organization Name
    • Hierarchy
    Click Next and the Assign Items to Organizations: Review Organizations page lists all organizations matching your search criteria.
  5. Select the organization(s) you want to update, then click Next and the Assign Items to Organizations: Review Results page appears.
    If you want refine the Organization search, click Back. Otherwise, click Finish.
  6. Review the Item Organization Assignments.
    If the items selected have associated packs or structures, the Select Options region appears. Select one of the following options:
    • Assign Packs
      Enables the selected items to share their associated (common) packs across the selected organizations. See: Referencing Common Bills and Routings, Oracle Bills of Material User's Guide and Managing the Packaging Hierarchy
    • Assign Structures
      Copies or uses a common structure associated with each of the selected items across the selected organizations. See: Referencing Common Bills and Routings, Oracle Bills of Material User's Guide
    Click Back if you need to change your selected organization(s) or Finish to proceed with assigning the items to organizations.
  7. After clicking Finish, the Assign Items to Organizations: Choose Action page appears. Choose one of the following actions:
    • Apply changes to Database (This option enables you to enter changes directly into the database.)
    • Export to Excel
    Click Submit.
If you selected Apply changes to Database
  1. The Schedule Request: Schedule page appears. Choose when you would like your request to run. You can choose the following:
    • Start Date - choose as soon as possible or a specific date and time.
    • Recurrence - select Never Repeat or Repeat on a certain interval, ending at a certain date and time.
    • Apply the Interval - apply the interval based on the start or completion date and time.
    • Schedule Name - optionally select a predefined schedule from the list. Select Increment Date Parameters to set the next date.
    • Save Schedule - define and save a new schedule by entering a new Schedule Name, Description, and selecting Save Schedule.
  2. Click Next. The Schedule Request: Review page appears.
    Review the schedule parameters. Click Back if you need to change any of the parameters.
  3. Click Submit.
    A message appears, saying your request for EGO Spreadsheet Java Concurrent Program has been scheduled and giving you the Request ID.
  4. Click OK.
    The Requests page appears. From here, you can find out the details and status of your request.
If you selected Export to Excel
  1. The Select Viewer page appears. Select the version of Microsoft Office® Excel on your desktop.
    Follow the instructions on your screen to download the file to your desktop. Update the spreadsheet, then upload it as described in To update existing items using an Excel spreadsheet.
To mass assign items to suppliers, supplier sites, and supplier site organizations
The process for mass assigning items to suppliers, supplier sites, and supplier site organizations is almost the same, and very similar to mass assigning items to organizations. The only difference between assigning items to the three different supplier business objects is the page name. For example, when assigning items to suppliers, the first page name is Assign Items to Suppliers: Select Items. When assigning items to supplier site organizations, the first page name is Assign Items to SupplierSite Organizations: Select Items. The following steps assume that you are assigning items to suppliers.
  1. Navigate to the Assign Items to Suppliers: Select Items page.
  2. Enter search criteria, then click Next. See: Searching for Items. The Assign Items to Suppliers: Review Items page appears.
  3. Review the search results. You can filter the search results and select the items that you want to assign. If the search results returned the expected items, click Next and the Assign Items to Suppliers: Select Suppliers page appears. If you need to refine the search criteria, click Back.
  4. Search for a supplier using one of the following fields:
    • Supplier
    • Supplier Number
    • DUNS Number
      This field only appears when assigning items to suppliers.
    • Tax Payer ID
      This field only appears when assigning items to suppliers.
    • Tax Registration Number
      This field only appears when assigning items to suppliers.
    You can also search for supplier sites. Select Show Supplier Sites, then search for supplier sites using the following fields:
    Note: These fields automatically appear when assigning items to supplier sites or supplier site organizations.
    • Supplier Site
    • City
    • State
    • Country
    Click Next and the Assign Items to Suppliers: Review Supplier Results page lists all suppliers matching your search criteria.
  5. Select the supplier(s) you want to assign to the item(s), then click Next. The Assign Items to Suppliers: Review Results page appears.
  6. Review the item supplier assignments.
    Select a display format for export, then click Go.
    Click Back if you need to change your selected supplier(s) or Finish to proceed with assigning the items to suppliers.
  7. After clicking Finish, the Assign Items to Suppliers: Choose Action page appears. Choose one of the following actions:
    • Apply changes to Database (This option enables you to enter changes directly into the database.)
    • Export to Excel
    Click Submit.
If you selected Apply changes to Database
  1. The Schedule Request: Schedule page appears. Choose when you would like your request to run. You can choose the following:
    • Start Date - choose as soon as possible or a specific date and time.
    • Recurrence - select Never Repeat or Repeat on a certain interval, ending at a certain date and time.
    • Apply the Interval - apply the interval based on the start or completion date and time.
    • Schedule Name - optionally select a predefined schedule from the list. Select Increment Date Parameters to set the next date.
    • Save Schedule - define and save a new schedule by entering a new Schedule Name, Description, and selecting Save Schedule.
  2. Click Next. The Schedule Request: Review page appears.
    Review the schedule parameters. Click Back if you need to change any of the parameters.
  3. Click Submit.
    A message appears, saying your request for EGO Spreadsheet Java Concurrent Program has been scheduled and giving you the Request ID.
  4. Click OK.
    The Requests page appears. From here, you can find out the details and status of your request.
If you selected Export to Excel
  1. The Select Viewer page appears. Select the version of Microsoft Office® Excel on your desktop.
    Follow the instructions on your screen to download the file to your desktop. Update the spreadsheet, then upload it as described in To update existing items using an Excel spreadsheet.
To mass assign items to and unassign items from categories
The processes for mass assigning items to categories and unassigning items from categories are almost identical and following the same first three steps:
  • Select the catalog
  • Search for items
  • Review search results. Optionally, go back and search again if the results are unsatisfactory.
  • The next step differs depending on the process selected:
    • Assign Items to Categories
    • Unassign Items from Categories
  • The remaining steps are the same for both flows:
    • Find and select organizations
    • Review organization item search results. Optionally, go back and search again if the results are unsatisfactory.
    • Choose action:
      • Apply changes to the database immediately
      • Export items to change to Excel. Make changes, then upload the changes at a later time.
Caution: Only users with create/edit category privileges can create or edit category information in a catalog. A user can assign items to categories only if the user has item assignment privileges for the catalog side as well as the item. For example, a user can assign item A to category B in catalog C only if the user has item assignment privileges for the item as well as managing catalog item assignment privileges for the catalog.
  1. Navigate to one of the following mass update functions:
    • Assign Items to Categories
    • Unassign Items from Categories
    The (mass update function): Select Catalog page appears.
    Search for and select a catalog. Click Next.
  2. The (mass update function): Select Items page appears.
    Use either Simple Search or Advanced Search to find the items you want to update. See: Searching for Items
    The Assign Items to Categories: Assign Items or the Unassign Items from Categories: Unassign Items page appears.
  3. Select the items you want to assign or unassign, then choose a category. Click Assign or Unassign, then click Next.
  4. The (mass update function): Select Organizations page appears.
    Search for an organization using one of the following fields:
    • Organization Code
    • Organization Name
    • Hierarchy
    Click Next and the Assign Items to Organizations: Review Organizations page lists all organizations matching your search criteria.
  5. The (mass update function): Review Results page appears.
    Review the search results. If the search results returned the expected items, click Finish. If you need to refine the search criteria, click Back.
  6. After clicking Finish, the (mass update function): Choose Action page appears. Choose one of the following actions:
    • Apply changes to Database - use this option to directly update the database
    • Export to Excel - use this option if you want to update more than the category information or need more time to determine the updates needed.
    Click Submit.
  7. If you chose Export to Excel, the Select Viewer page appears. Select the version of Microsoft Office® Excel on your desktop.
    Follow the instructions on your screen to download the file to your desktop. Update the spreadsheet, then upload it as described in To update existing items using an Excel spreadsheet.
  8. If you chose to Apply changes to Database, then the Schedule Request: Review page appears. Submit the concurrent program.
To reassign categories
Caution: Only users with create/edit category privileges can create or edit category information in a catalog. A user can assign items to categories only if the user has item assignment privileges for the catalog side as well as the item. For example, a user can assign item A to category B in catalog C only if the user has item assignment privileges for the item as well as managing catalog item assignment privileges for the catalog.
  1. Select Reassign Categories from the menu.
    The Reassign Categories: Select Catalog page appears.
    Search for and select a catalog. Click Next.
  2. The Reassign Categories: Select Categories page appears.
    Select an origin and a destination category. Click Next.
  3. The Reassign Categories: Select Organizations page appears.
    Enter an organization code, name, or hierarchy. Click Next.
  4. The Reassign Categories: Review Organizations page lists all organizations matching your search criteria.
    Select only those organizations for which you want to reassign categories. If you need to refine the search criteria, click Back.
  5. The Reassign Categories: Review Categories page appears.
    Review the results. If the results are as expected, click Finish. If you need to refine the categories, click Back.
  6. After clicking Finish, the Reassign Categories: Choose Action page appears. Choose Apply changes to Database.
    Click Submit.
  7. The Schedule Request: Review page appears. Submit the concurrent program.

Deleting Items

You can delete or purge items from Oracle Product Information Management using deletion groups, deletion constraints, and deletion statements. Use deletion groups to specify the items that you want to delete. Deletion statements define what records to delete, for a particular deletion group, from a particular database table. Deletion constraints define the conditions when you can not delete a record from a database table. Oracle provides many predefined item deletion statements and deletion constraints, but you can also create custom deletion statements and deletion constraints. Other Oracle applications use deletion groups, statements, and constraints to delete other entities, too. For details on how to use deletion groups, statements, and constraints, see the Related Topics listed below.
The predefined item deletion statements specify that the following records are deleted, along with the master item record:
  • Item organizations
  • Item suppliers
  • Item supplier sites
  • Item organization supplier sites
  • Packaging hierarchy
  • Item associations, such as:
    • MPNs (manufacturing part numbers)
    • Related items
    • Customer item cross references
    • Source system cross references
    • Related documents
    • Cross references
    • GTIN cross references
  • Item operational and user-defined attributes, including style item variant attribute group value sets when deleting a style item.
    Note: When you delete a SKU, that particular variant attribute combination becomes available again for the style item.
Predefined item deletion constraints created specifically for Oracle Product Information Management include:
  • Delete a style item only if the style item has no associated SKUs.
  • No deletion of unapproved items allowed.
  • No deletion of a Global Trade Item Number (GTIN) registered to 1SYNC allowed.
Related Topics
Deleting Items, Bills, Routings, Components, and Operations, Oracle Bills of Material User's Guide
Deletion Constraints and Statements, Oracle Bills of Material User's Guide
Creating Custom Deletion Statements and Constraints, Oracle Bills of Material User's Guide
Item Deletion, Oracle Inventory User's Guide
Delete Items Report, Oracle Bills of Material User's Guide

Updating Multi-Row Attributes in a Spreadsheet

When creating or updating items/item revisions using a spreadsheet, you can provide values for multi-row attributes. When updating an item/item revision's multi-row attributes, you only provide the values for the multi-row attributes; you cannot make changes to the primary or single-row attributes--doing so results in errors. Further, when selecting multi-row attributes from a display format for export to a spreadsheet, select which multi-row attribute to update from the search results page. Even though you can create a display format for more than one multi-row attribute, only the data for the single, selected multi-row attribute is exported to the spreadsheet.
When updating an item multi-row attribute in a spreadsheet, you must input values for the following primary attributes for each multi-row attribute row:
  • Transaction Type (Sync)
  • Item
  • Organization Code
When updating an item revision multi-row attribute in a spreadsheet, you must input the Revision Code for each multi-row attribute row.
To create or update an item's multi-row attributes in a spreadsheet
  1. Perform steps 1-7 in the Importing Items Using a Spreadsheet procedure.
  2. In the spreadsheet, copy the row for the item (or item revision) and paste it into the next row. Then, delete the values of the primary/single row attributes in the new row. You must delete the values of the primary/single row attributes; if you do not, errors will occur.
    Note: By default, the spreadsheet is protected. To copy/paste rows, select the Tools menu, then select Protection, and then select Unprotect.
  3. Ensure that the unique key remains the same. After you have a row containing the same unique key as the item (or item revision) whose multi-row attributes you wish to update, and the primary/single row attributes are removed, you can enter values for the multi-row attributes In the following spreadsheet the unique key (Org Code and Item) in the second and third rows remain the same; the single row attributes have been deleted, and the multi-row attribute (Product Name, Impact Classification) values are provided.
    Note: To delete an existing value in a record, enter the following data in the appropriate column of the spreadsheet:

    For field type: Enter value:
    Date 31-DEC-9999
    Character !
    Numeric 9.99E125
    If you want to retain an existing value in a record, have it blank in the appropriate column of the spreadsheet.
    Exception: In the user defined attributes interface table, when you want to delete an existing value in any of the following fields, use the value !. If you want to retain an existing value in a record, no entry is necessary.
    • ATTR_DISP_VALUE
    • ATTR_VALUE_STR
    • ATTR_NUM_VALUE
    • ATTR_VALUE_DATE
    Sample Spreadsheet with Multi-Row Attribute
    the picture is described in the document text
  4. Make a note of the Result Format Usage ID at the top of the spreadsheet. You will need this ID later when you upload the spreadsheet in the systemk.
  5. After data entry is complete, select Upload from the Oracle menu in the toolbar.
  6. In the Upload Parameters window, enter the Result Format Usage ID and check the Automatically Submit Concurrent Process box, and then click Proceed to Upload.
  7. In the Oracle Web ADI window, click Upload. After the upload process completes, a message appears with the Concurrent Request number. Make a note of this number, as you will need it later when you access the view log for the concurrent request. Click Close when the process messages complete.
  8. Return to the Applications tree menu and click the "View Concurrent Requests" link. It is recommended that you check the concurrent process view log to ensure that the upload process was successful.
  9. On the View Concurrent Requests page, click the Details icon.
  10. On the Request Details page, click View Log.
  11. From the View Log, paste the URL string in a web browser to view any errors. If no errors appear, the upload was successful.

Managing Item Specifications

The specifications of an item are divided into structured and unstructured information. The structured item information is captured in the form of numerous primary and operational attributes that are enabled at the master item or item organization level and in the form of user defined and transaction attributes that are inherited from the catalog category of the item. You can also add an unlimited number of descriptions and images about an item to enrich its specification. All unstructured item information can be added as an attachment to the item.
Most of the item specification information is available at the item revision level as well, which enables you to keep track of the specification information by item revision. For information that is tracked at the revision level, you can perform all of the following actions for each item revision.
Note: You can automatically trigger actions based on an item attribute change. See: Item Business Events, Oracle Product Information Management Implementation Guide and Managing Business Events, Oracle Workflow Developer's Guide.
To update an item's detailed description, images, and primary attributes
  1. Locate the item whose description, images or primary attributes you wish to update.
    the picture is described in the document text
  2. On the item's Overview page, select Update from the Actions list and click Go.
    the picture is described in the document text
  3. Optionally, on the Update Overview page, select a template from which to copy detailed descriptions, primary attributes, and images.
  4. Optionally, update the description and long description.
  5. Optionally, select a different User Item Type and Conversions option.
    Important: The Primary UOM cannot be updated. If the lifecycle and lifecycle phase are not editable, it is because they have already been defined and are in use. If these fields are editable, it is because they have not yet been defined.
  6. Optionally, add, update or delete an image.
    • Add
      In the Images region, click Add Another Row. Provide the Sequence, a Translatable Label, and choose an attached file for the description. The Display Mode enables you to either display the contents of the image inline or as a link.
    • Update
      Update the fields in the Images region.
      Note: Files attached using Oracle's E-Business Suite are rendered inline. Files attached using Oracle Files Online are rendered as links, regardless of what is specified in the Display As list.
    • Delete
      Click the Delete icon in the image row you want to delete.
  7. Optionally, add, update, or delete a detailed description.
    • Add
      In the Detailed Description region, click Add Another Row. Provide the Sequence, Description Source, Translatable Label and choose an attached file if the Description Source is Item Attachments. The Display Mode enables you to display the contents of the file inline or as a link.
      Note: Use the Description Source list to select either an Item Attachments description or a Long Description. If you wish to select Item Attachments, then the list of values in the Attached File field is enabled. However, if you select the Long Description, then the Attached File field is disabled and the list of values returns no results. Also note that files attached using Oracle's E-Business Suite are rendered inline. Files attached using Oracle Files Online are rendered as links, regardless of what is specified in the Display Mode field.
    • Update
      Update the fields in the Detailed Description region.
    • Delete
      Click the Delete icon in the detailed description row you want to delete.
  8. Click Apply to save your changes.
To update an item's operational and user-defined attributes
When you define or update an item's operational and user-defined attributes, you update them at the item's organization and revision level, not at the master item level. If you want to update an operational or user-defined attribute across all organizations, then see: Mass Updating Items, Categories and Associations.
  1. Locate the item whose operational and user-defined attributes you want to update.
  2. Click the attribute group you want to update.
    For example, click Physical Attributes. In the Physical Attributes page, the Update button appears when:
    • a user's role has privileges to update the item and
    • the item is in a lifecycle phase where direct updates are allowed
    The Create Change Order button appears when:
    • the attribute group's change policy is set to Change Order Required and the item is in a lifecycle phase that requires change orders. See: Defining Change Policies, Oracle Product Information Management Implementation Guide
    If both the Update and the Create Change Order buttons appear, then you can choose whether to create a change order before updating the attributes or not.
    Note: Change management is not supported for the following operational attributes. You must update them using the Update button:
    • Shipping Subinventory (Sales and Order Management attribute group)
    • Receiving Subinventory (Purchasing attribute group)
    • Move Order Receipts SubInventory (Inventory/WMS attribute group)
    the picture is described in the document text
To update attributes without creating a change order
  1. Click Update.
    The Update (Attribute Group) Attributes page appears. Enter the new attribute values and units of measure, if applicable.
    the picture is described in the document text
  2. Click Apply.
To update attributes using a change order
  1. Click Create Change Order.
To update an item's transaction attributes
When you update an item's transaction attributes, you update them at the item's organization and revision level, not at the master item level.
  1. Locate the item whose transaction attributes you want to update.
  2. From the item's Overview page, click Transaction Attributes.
  3. For further instructions on how to update an item's transaction attributes, see: "To update a transaction attribute:" in Defining Transaction Attributes, Oracle Product Information Management Implementation Guide.
Related Topics
Creating Change Orders
Performing Actions

Managing Item Phases

Lifecycles enable you to model the lifecycle phases of your items in a flexible manner. You can pre-establish phase level controls that determine the behavior of an item in the different modules. You can also define a list of valid item statuses within each phase. The item status in turn controls the behavior of the item in eight functional areas. There is one lifecycle definition, which is the same for the item and the item revisions. However, an item and item revisions can be in different phases even if they are using the same lifecycle definition. It is not mandatory that an item have a lifecycle; however, if the item revisions have phases, then you must have a lifecycle defined for the item.
You can promote or demote an item from its current phase. When an item enters a new phase, based on the control factors of the new phase and status, the behavior of the item will change. For example, when you move an item from the engineering phase to the production phase, you may want to place tighter controls on changes to product specifications, since that will entail significant change management efforts and costs.
To promote an item to the next phase
  1. Locate the item that you wish to promote to the next lifecycle phase.
  2. On the item's Primary Attributes page, click the Lifecycle tab.
  3. On the Item Phases page, click Promote.
    The Promote button is available only if the item is under lifecycle control.
  4. Provide the Effective Date.
  5. Click Apply.
To demote an item to a previous phase
  1. Locate the item that you wish to demote to the previous lifecycle phase.
  2. On the item's Primary Attributes page, click the Lifecycle tab.
  3. On the Item Phases page, click Demote.
    The Demote button is available only if the item is under lifecycle control.
  4. Provide the effective date.
  5. Click Apply.
To view an item change policy
  1. Locate the item for which you wish to view the change policy.
  2. On the Item Detail page, click the Lifecycle tab.
  3. Click the "Change Policy" link.
To change the item status
  1. Locate the item for which you wish to change the status.
  2. On the item's Primary Attributes page, click the Lifecycle tab.
  3. On the Item Phases page, click the "Status" link.
  4. Click Demote.
  5. Click Change Status.
  6. Update the status and effective date.
  7. Click Apply.
To implement the phase/item status changes
  1. Locate the item for which you wish to implement the phase/item status.
  2. On the item's Primary Attributes page, click the Lifecycle tab.
  3. On the Item Phases page, click the "History" link.
  4. Click Implement.

Managing AMLs

You can associate a list of manufacturers and their corresponding part numbers with any item. You can also specify the manufacturer's approval status, preference level, and identify whether or not the first article has been completed. This list of manufacturers and part numbers is called an Approved Manufacturers List (AML). The AML for an item is often defined during the new item creation and request process. The AML is thereby reviewed and approved by all necessary people. An item AML may be updated after item creation either manually or through a change order. The item's change policy determines for each phase of an item's lifecycle whether or not an AML can be updated and if a change order is required.
For more details about item change policies, see Defining Change Policies , Oracle Product Information Management Implementation Guide.
To specify manufacturer part numbers when creating an item
  1. On the Create Item: Review Item Information page (typically the second step in the create item process), click the Manufacturer Part Number tab.
  2. When the page refreshes, click Add Another Row.
  3. In the empty fields for the row, provide the required information.
    Status
    If you know the approval status of the manufacturer and manufacturer part number, select it. Otherwise, leave this field blank.
    Preference Level
    The Preference Level indicates whether or not the manufacturer has been designated as preferred in the item catalog category. Preference Levels range from High (most desirable) to Low (least desirable). A manufacturer can have different Preference Levels for different items--this is a result of the items being in different item catalog categories. Hence, the Preference Level is specified at the item catalog category and not editable in this context.
    First Article Status
    First Article Status is a milestone that indicates whether or not a manufacturer has built and/or provided the first article.

Creating Item Revisions

Items undergo changes that you may want to track using item revisions. You can associate both structured and unstructured information with item revisions.
Note: You can automatically trigger actions based on an item revision change. See: Item Business Events, Oracle Product Lifecycle Management Implementation Guide or Oracle Product Information Management Implementation Guide and Managing Business Events, Oracle Workflow Developer's Guide.
To create an item revision
  1. Locate the item for which you wish to create a revision.
  2. On the item's Primary Attributes page, select the Revise action and click Go.
  3. On the Revise Item page, provide in the required information and click Apply.
To update an item revision
  1. Locate the item for which you wish to create a revision.
  2. On the item's Primary Attributes page, click the Revisions tab.
  3. On the Revisions page, click the revision's name link.
  4. Click Update.
  5. On the Update Revision page, update the relevant information and click Apply.

Managing Item Attachments

The specifications of an item are divided into structured and unstructured information. You can add unstructured information to the item as an attachment. Attachments include files, folders, text, and URLs. All management of item attachments occurs from the Attachments page. To navigate to this page, locate the item. On the item's Primary Attributes page, click the Attachments tab.
You can add attachments to items at the item revision level as well, enabling you to track specification information by item revision. Most tasks related to item attachments are the same as those for attachments to any other business object. For an explanation of all tasks related to attachments to any business object, see: Using E-Business Suite Attachments.
You can also use a Change Management approval and review process to control the changes to item attachments. Change Management for item attachments provides change control functionality for all types of attachments, a crucial and important piece of non-structured information about the product.
Types of attachment changes supported using a change order include:
  • adding a specific version of an attachment at the item or item revision level
  • creating a new version for an existing attachment by checking out the current version and checking in a new version.
  • changing the attached version for an existing attachment.
  • changing attachment attributes. Supported attributes include Name, Description, and Attachment Category.
  • deleting attachments.
Change control is achieved by providing a mechanism to author, track and manage changes to attachments through a change order approval and implementation process. You can:
  • Specify items and attachments that are effected in a change order.
  • Author and specify the exact changes that are desired or required to resolve an issue or change request.
  • Route the change order for approval to the appropriate people responsible for the revised item based on item roles, change desired and lifecycle of item.
Once the change order is approved, implement the changes manually or automatically on the specified implementation date.
Change Management for item attachments is supported through the Change Management functionality. User can create a change order and specify changes to the attachments of a reviewed item. There are no additional steps required in the setting up of a change order to be able to do attachment changes for a revised item.
To request review or approval of an attachment
You can request approval or a review of a file version, URL, or text using workflows. Each approval or review consists of a number of phases; you can associate a workflow approval with each phase.
The workflow lists the steps in the approval process. You can add steps to the process only if a workflow routing is associated with the particular phase. You cannot delete predefined steps. You can add additional assignees to a step, but you cannot delete predefined assignees. For more details about approvals, see Managing Workflows.
When you send a file version stored in a Oracle Universal Content Management (UCM) or Content DB content repository through a review or approval process, the same status is reflected everywhere else this file version is attached. The process is the same for both reviews and approvals, but the following steps use the request approval action to explain the process.
  1. In the Attachments page, find and select the files that you want to approve or review.
  2. In the Select Attachments field, select either Request Approval or Request Review, then click Go.
    the picture is described in the document text
  3. In the Create File Approval: Select File Approval Type page, select the file approval type from the dropdown list. Click Continue.
  4. In the Create File Approval page, enter a file approval name.
    Optionally, enter values in the following fields:
    • Description
    • Priority
    • Reason
    • Need By Date
    the picture is described in the document text
  5. In the Create File Approval page, click the Workflow Approval tab to add update, add, or delete any workflow steps. For more information about workflows, see:
    • Managing Workflows
    • Defining Workflow Templates, Oracle Product Information Management Implementation Guide
    the picture is described in the document text
  6. Click Submit.
    In the Attachments page, the status of the selected files has changed to Submitted for Approval.
To view the status of a review or approval
You can view the review or approval status of a particular attachment from the Attachments page Status column. By moving your cursor over a status icon in the Status column, you can see the status of a particular attachment. If you click on the status icon for an attachment going through the review or approval process, the system takes you to a review or approval summary page
You can also view the status of a review or approval by clicking on the Attachment Details icon in the Details column for a particular attachment. From the Details page, click either the Reviews or Approvals tab. Each tab lists all reviews or approvals associated with the attachment.
View pending attachment changes
the picture is described in the document text
You can view pending attachment changes for an item from the attachments sub-tab in the item workbench. You can select a pending change from the attachments drop-down list in the View section and view change details.

Using Item Business Events

Using Oracle Workflow, you can automatically trigger actions after the following item business events occur:
  • item creation
  • item approval
  • item creation using bulkload
  • item role change
  • item update
  • related item change
  • item revision change
  • item cross reference change
  • customer item cross reference change
  • item attribute change
  • item approved manufacturer list change
  • item catalog assignment change
  • UCCNet Global Data Synchronization (registering an item with GDSN)
  • catalog category change (creating, updating, or deleting a catalog category)
  • GTIN attribute change
  • valid category change (adding or removing a category from a catalog)
  • pre-item attribute change (event raised before changing the item attribute)
In one case, business event oracle.apps.ego.item.preAttributeChange, you can trigger actions before a business event occurs. Before changing an item attribute, you can test a proposed attribute change against your validating criteria before committing the attribute value to the database. This business event requires one extra step: checking the Raise Pre Attribute Change Event box (see: Defining Item Attributes and Attribute Groups , Oracle Product Information Management Implementation Guide). Examples of actions you can trigger include issuing notifications or launching a workflow.
Business Event Examples
The following scenarios show how subscribing to a business event can simplify business processes:
  • A business needs to notify the people involved every time an item role change occurs. The business can set up Oracle Workflow to automatically send the people involved an email each time this occurs.
  • A business maintains items in the master organization. Every time an item is created in the master organization, the business needs to copy the item into the child organizations.
For more information about setting up and subscribing to business events, see the related topics listed below.
Related Topics
Item Business Events, Oracle Product Lifecycle Management Implementation Guide or Product Information Management Implementation Guide
Managing Business Events, Oracle Workflow Developer's Guide
Defining Procedures and Functions for Oracle Workflow, Oracle Workflow Developer's Guide

Enabling Organization Assignments

Items are engineered, manufactured, and distributed by physical facilities called "organizations". To enable an organization to perform one of these functions on an item, you have to first enable the item into that organization with the appropriate attributes. Some of the attributes are modifiable at the organization level. These are called organization-level attributes.
Note: When integrating a retail system such as Oracle Retail with Oracle eBusiness Suite, you must set up the retail sites as organizations. Refer to the retail site hierarchy and create a matching organization hierarchy. Model retail site clusters as single level organization hierarchies, with one of the sites defined as a parent (a dummy role). Once the organizations are defined, you can synchronize retail site data with the organizations.
See: Setting Up Organizations, Oracle HRMS Enterprise and Workforce Management Guide
Choose from the following methods of assigning organizations to items:
  • Manually. You can manually assign organizations to items from:
    • the Item Workbench, Organizations tab. See: "To enable an item in an organization:", listed below.
    • the Mass Update menu. See: "To mass assign items to organizations:" in Mass Updating Items, Item Categories and Item Associations.
    • the Item Workbench, Configuration tab, Packs subtab. See: "To assign a pack to an organization:", listed below.
  • Automated. Use API calls initiated by a retail system such as Oracle Retail to create and maintain item organizations synchronized with retail sites. See the Oracle Integration Repository for a list of organization APIs available for use. Separate organization APIs can assign organizations to items as well as keep the organizations synchronized with retail sites if you use a retail system such as Oracle Retail.
  • Manual and automated. You can choose to automate the synchronization of some portion of the organization hierarchy and maintain the rest manually. For example, Oracle Retail has a six level site hierarchy, the top levels of which usually remain static. The majority of the changes occur at the last level, the retail sites/organizations. You could set up the initial organization hierarchy from Oracle Retail manually in eBS. Automate the creation of the site and site clusters in eBS using APIs.
Important: Only those users with access to an organization can assign items to it.
To enable an item in an organization
  1. Locate the item you wish to enable.
  2. On the item's Overview page, click the Organizations tab.
  3. On the Organization Assignments page, click Assign to Organization.
    Note: When you are viewing an item within the master organization context, you can also click Mass Assign to Organization. This button is not available within child organizations. See: "To mass assign items to organizations:" in Mass Updating Items, Item Categories and Item Associations.
    The Assign to Organization button enables you to copy the following item attribute values from the master organization context to the new organizations:
    • Status
    • Primary Unit of Measure
    • Tracking
    • Pricing
    • Secondary Unit of Measure
    • Defaulting
    • Negative Deviation Factor
    • Positive Deviation Factor
    If you want to copy more attribute values, then use the Mass Assign to Organization button.
  4. On the Update Organization Assignments page, select the Assigned checkbox in the row of each organization to which you want to assign the item. Click Assign All to assign the item to all organizations.
  5. Click Apply.
    A message appears, listing the concurrent request ID.
To assign a pack to an organization
You can assign any level in a packaging hierarchy to one or more organizations. All items below the pack item selected are assigned to the same organization(s) as the pack item.
  1. Navigate to the Packs page of an item.
    From the item's Overview page, click the Configuration tab, then the Packs subtab. The Packs page displays a list of each pack item of which this item is a member.
  2. In the bottom table that displays the pack hierarchy, select the pack item that you want to assign to one or more organizations.
  3. Click Assign Pack to Organization.
  4. In the Assign Items to Organizations: Select Organizations page, search for the organizations to select using one or more of the following fields:
    • Organization Code
    • Organization Name
    • Hierarchy
    Click Next.
  5. In the Assign Items to Organizations: Review Organizations page, select one or more organizations, then click Next.
  6. In the Assign Items to Organizations: Review Results page, review the items and the organization assignments. Click Back to change them or Finish to complete the organization assignment.
  7. in the Assign Items to Organization: Choose Action page, choose to either apply the changes to the database or to export the changes to Excel.
    Click Submit.
  8. If you chose the apply to database option, follow the next steps that appear to schedule the concurrent request, choose a report layout, and review the options you have chosen. Click Submit to schedule the concurrent request.
    If you chose the export to Excel option, follow the next steps that appear to download the changes into an Excel spreadsheet. Update the spreadsheet if necessary, then upload it as described in Updating Existing Items Using a Spreadsheet.
To change the organization context
You can change the organization context to look at item information in a different organization either from the main menu or from within the item workbench.
To change organizations from the main menu
  1. From the menu, find and select Change Organization.
To change organizations from the item workbench
  1. Navigate to the item's Overview page or to any page within the item workbench.
  2. From the Shortcuts drop down list, select Organization, then click Go.
  3. In the Choose Organization page, click the Quick Select icon next to the organization you want to select.
Alternatively, from the item's Overview page, select the Organizations tab. In the Change Organization drop down list, select an organization.
To view item organization assignments
Important: You can only view those organizations to which you have access.
  1. Navigate to the item's Overview page.
  2. Select the Organizations subtab.
    The Organization Assignments page lists all of the organizations assigned to the item.

Managing Revision Phases

Lifecycles enable you to model the lifecycle phases of your item revisions in a flexible manner. You can pre-establish phase level controls that determine the behavior of an item revision in the different modules.
You can promote or demote an item revision from its current phase. When an item enters a new phase, based on the control factors of the new phase and status, the behavior of the item revision changes. For example, when you move an item from the engineering phase to the production phase, you may want to place tighter controls on changes to product specifications, since that will entail significant change management efforts and costs.
To promote an item revision to the next phase
  1. Locate the item for which you wish to promote the item revision.
  2. On the item's Primary Attributes page, click the Lifecycle tab.
  3. On the Item Phases page, click the Revision Phases tab.
  4. On the Revision Phases page, click Promote.
  5. On the Promote Item page, provide the Effective Date.
  6. Click Apply.
To demote an item revision to the previous phase
  1. Locate the item for which you wish to demote the item revision.
  2. On the item's Primary Attributes page, click the Lifecycle tab.
  3. On the Item Phases page, click the Revision Phases tab.
  4. On the Revision Phases page, click Demote.
  5. On the Demote Item page, provide the Effective Date.
  6. Click Apply.
To implement the phase changes
  1. Locate the item for which you wish to implement phase changes.
  2. On the item's Primary Attributes page, click the Lifecycle tab.
  3. On the Item Phases page, click the Revision Phases tab.
  4. On the Revision Phases page, click "Phase History" link.
  5. Click Implement.

Viewing Item Transaction Information

Using the Oracle Transaction Viewer, you can present real-time item transaction information gathered from the entire Oracle E-Business Suite within the Item workbench. View transactions from various functional areas such as Sales, Inventory, Purchasing, Install Base, Service, Retail, and others. The Oracle Transaction Viewer, shared by Oracle Customer Data Hub, enables users to configure views of their product data across all spoke systems, providing a 360 degree transactional view of the product within a single Item Workbench tab.
Prerequisites
  • To view transactions, you must set up the Oracle Transaction Viewer for use with the Item Workbench. Set up the Transaction Viewer as described in Transactions Viewer, Oracle Customer Data Hub Implementation Concepts and Strategies White Paper at My Oracle Support (http://metalink.oracle.com, Doc ID: 312811.1), except substitute the be_code field value of IMC_TXN_BE_PARTY with the value IMC_TXN_BE_ITEM.
To view item-related transaction information
  1. Find the item for which you want to view item transaction information. See: Searching for Items.
  2. On the item's Overview page, click the Transactions tab.
    You can view transaction information under the following sections of the Transactions page.
    • Open Orders
    • Onhand Quantities
    • Open Returns
    • Open Service Requests
    • Installed Units Information
    • Open Purchasing Orders
    Important: The Transactions tab remains hidden by default but becomes visible once you seed a transaction for IMC_TXN_BE_ITEM.
    the picture is described in the document text

Generating Reports

Item reports can be generated for one or more items from Item search results, Browse Catalog category, and Item Detail pages. You can export these Item reports in various formats like Adobe Acrobat, Rich Text format, Web page, Microsoft Excel, or XML using custom report formats. You can design report formats using familiar desktop tools such as Adobe Acrobat and Microsoft Word.
Report security is consistent with search security. You can only generate reports for item objects on which you have the required role. Also, you can only export item information in the report on which you have the required role.
You can export or generate the following item-related reports:
  • Item primary and operational attribute groups
  • Item-level user defined attribute groups
  • GDSN attribute groups
Prerequisites
  • Defining Report Templates Using XML Publisher, Oracle Product Information Management Implementation Guide
To generate a report
  1. Using Item simple or advanced search, find the Items for which you want to generate the report.
  2. Select Items from the search results, and click Generate Report.
  3. Select the Report template and Output format.
  4. If you want to include images in the report, select 'Include Item Overview Images'.
    This option includes any images attached to an item's description.
  5. Upon export, the report will be generated in the required format.
    Note: You can also generate report from the Browse Catalog Category and Item detail pages.

    Using Style and SKU Items

    This chapter covers the following topics:
  6. Overview of Style and SKU Items
  7. Creating Style and SKU Items
  8. Creating a SKU Packaging Hierarchy

Overview of Style and SKU Items

You can use style items to group similar items (called SKUs or Stock Keeping Units) together. The items grouped under the style item (the SKUs) have variant attributes. For example, a retail clothing business sells a particular shirt style in multiple colors and sizes. The multiple colors represent one variant attribute group while the various sizes represent another variant attribute group. Variant attribute groups contain attributes that differentiate the item. Each unique variant combination represents a possible SKU item. A simple example that explains the use of style items with SKUs follows.
Style/SKU Example
the picture is described in the document text
The style item behaves as a model item while the SKUs behave as standard items. All business transactions occur at the SKU item level.
The SKUs can either inherit or default certain item characteristics from the style item. When a SKU inherits a characteristic from its style item, the characteristic is always controlled at the style item level. For example, you can only change an inherited item level user defined attribute such as price at the style item level. Once the price is changed, all SKUs reflect the new price. When a characteristic defaults from a style item to a SKU during SKU creation, you can change the characteristic at the SKU level later without affecting the style item. Conversely, if you change a defaulted characteristic at the style item level after SKU creation, the change does not automatically appear at the SKU level. You must manually make the change at the SKU level or use a mass update function to change the SKUs. See: Mass Updating Items, Item Categories and Item Associations. The following table lists the characteristics available to style and SKU items, as well as whether the inherit or default behavior is available for the characteristic.
Characteristics Availability and Inheritance/Defaulting Behavior
Characteristics Style Item SKU Defaulting from Style to SKU Inheritance from Style to SKU
Item level - User Defined Attributes Yes Yes Yes Yes
Item level - Retail Library defined attributes Yes Yes Yes Yes
Item level - Operational attributes Yes Yes Yes No
Variant Attribute Group Yes Yes No No
Revisions Yes Yes No No
Revision level User-defined attributes Yes Yes No No
Status Yes Yes Yes No
People/Security Yes Yes Yes No
Lifecycle Yes Yes Yes No
Retailer Sites Yes Yes Yes No
Item - Retailer Sites association attributes Yes Yes Yes Yes
Informal Pack Hierarchy Yes Yes Yes* Yes*
Formal Pack Hierarchy Yes Yes No not applicable
Structure/Bill of Material Yes Yes No No
Attachment - Item level Yes Yes Yes No
Attachment - Revision level Yes Yes No No
GTIN Yes Yes No No
Item Supplier associations Yes Yes Yes No
Change Management Yes Yes not applicable not applicable
External Transactions not applicable Yes not applicable not applicable
Related Items Yes Yes No No
Customer Item cross-reference Yes Yes No No
Manufacturer Part Number Yes Yes No No
Cross-Reference Yes Yes No No
Source System Cross-Reference Yes Yes No No
GDSN Syndicated Flag No Yes not applicable not applicable
* for user defined attributes only
The style item and it's related SKUs must have the same item catalog category (ICC). You can only change a style items' ICC if there are no related SKUs or if you change the ICC using a mass update function to change the style and related SKUs ICC at the same time. See: Mass Updating Items, Item Categories and Item Associations.
Related Topics
Creating Style and SKU Items
Creating a SKU Packaging Hierarchy

Creating Style and SKU Items

You can use the same process to create style items as you do to create standard items. Once you create the style item, you have the option to immediately begin the SKU item creation flow from the style item's Overview page. In addition, you can create style and SKU items using the following methods:
To create a style item
  1. Create an item as described in Creating New Items with the following exceptions.
  2. Select Style.
    Caution: Once you create a style item, you cannot deselect Style. You also cannot change another type of item to a style item later. You can only create style items during the item creation process.
    Note: You cannot create a GDSN Syndicated style item. The GDSN Syndicated box displays as read-only.
  3. Optionally, select one or more templates that set the operational and user-defined attributes for the item.
    Note: Each template selected is applied in the order listed. Templates applied latest override the attribute values of templates applied earlier.
  4. In the Create Item: Enter Number/Description page, enter the item and item description.
    Note: The system ignores the item number and description generation instructions specified by the item catalog category. Style item numbers and descriptions are user defined even if the item catalog category specifies 'Function Generated' or 'Inherited From Parent'.
    Enter the following attributes, keeping in mind how the values entered effect the SKU items based on this style item.
    • Variant Attributes
      The variant attribute groups listed default from the item catalog category selected. Variant attribute groups can have multiple value sets assigned to each group. For each group, select the value set to use when creating SKUs based on this style item.
      Important: You cannot select variant data types for Date, Date and Time, and Translatable Text.
    • Primary Attributes
      Select the primary attribute values that you want the SKUs to either inherit or receive the default values.
    Important: Verify that the following operational (transaction) attributes are set to No since style items are not transactable or stockable.:
    • Inventory Item
    • BOM Allowed
    • Build in WIP
    • Customer Orders Enabled
    • Internal Orders Enabled
    • Invoice Enabled
    • Transactable
    • Purchasable
    • Stockable
    • GDSN
    The default value for these attributes is No, unless a template applied in the previous step sets their value to Yes.
  5. Click Finish. The item Overview page displays.
To create SKU items from a style item
  1. Navigate to the Overview page for a style item.
  2. In the SKUs region, for each variant attribute, select the attribute value that you want to assign to the new SKU.
    Tip: If you want to create a SKU for more than one variant attribute value, then select All for one or more attributes.
  3. Click Create. The Create SKUs: Select Variants page appears.
  4. For each variant attribute, select the values for which you want to create SKUs.
    Note: You must select at least one value for each variant attribute.
  5. Click Add Selected Variants to create the list of SKUs based on the variant attributes selected.
  6. Select Outbound GDSN to GDSN-enable each SKU.
    Caution: Oracle Product Information Management no longer supports outbound product data synchronization.
    You cannot send data directly from Oracle Product Information Management (PIM) to the Global Data Synchronization Network (GDSN) since PIM only maintains the master data, but does not validate the data for GDSN. To send data to GDSN, you must build a validation or use a third party software application to perform this function.
  7. Select Engineering Item if you want to create each SKU as an engineering item.
    Leave this box blank to create the SKUs as production items.
  8. Enter an item number and description for each SKU.
    These fields already contain values if the item catalog category specifies function generated item numbers and descriptions. See: Defining Item Numbers and Descriptions, Oracle Product Information Management Implementation Guide.
  9. Optionally, click Show in the Details column to change the primary attribute values for each SKU if these values defaulted from the style item.
    If the SKU inherits the primary attribute values, then you cannot modify them.
    Caution: The system only considers SKUs with a Trade Item Unit Descriptor (TIUD ) = Each or Base Unit for pack creation. See: Creating a SKU Packaging Hierarchy
  10. Click Apply.
    You receive a message saying that a batch has been submitted for SKU Creation. the message includes a link to the concurrent request ID.
To create SKU items after a new variant attribute value is added to the value set
Using the example of a shirt style in a retail clothing business, suppose the retailer plans to introduce a new shirt color, magenta, for spring. After the new color is added to the value set, you can create new SKUs for the magenta color.
Follow the steps to create SKU items from a style item as described above. The Create SKUs: Select Variants page, SKU Combinations region has a column titled "SKU Exists". If no checkmark exists in this column for the new SKU combination, you can create the new SKU. Enter the new SKU description and item number (unless the item number is sequence generated), then click Apply.
Update all SKU item operational attributes as necessary to make them stockable and transactable. You can manually update these attributes after SKU item creation from the SKU item's Overview page or you can perform a mass update. See:

Creating a SKU Packaging Hierarchy

You can package SKUs into multiple units of individual items. For example, a packaging hierarchy for different sizes and colors of v-neck t-shirts might contain the following pack types:
  • Pallet: Item = V-MultiColorSizePallet
    • Case: Item = V-MultiColorSizeCase, Quantity = 6
      • Multipack: Item = V-MultiColorSizePack, Quantity = 2
        • Pack or Inner Pack: Item = V-WhiteMixedSizePack, Quantity = 1
          • Base Unit or Each: Item = V-WhiteSmall, Quantity = 25
          • Base Unit or Each: Item = V-WhiteMedium, Quantity = 25
          • Base Unit or Each: Item = V-WhiteLarge, Quantity = 40
        • Pack or Inner Pack: Item = V-BlueMixedSizePack, Quantity = 1
          • Base Unit or Each: Item = V-BlueSmall, Quantity = 30
          • Base Unit or Each: Item = V-BlueMedium, Quantity = 15
          • Base Unit or Each: Item = V-BlueLarge, Quantity = 25
Use the following procedure to create a packaging hierarchy containing the SKUs. In the example above, this procedure creates the pack or inner pack item that contains either the white or blue v-neck t-shirt mixture of sizes. See: Managing the Packaging Hierarchy for instructions on how to create other levels of the packaging hierarchy.
Packaging Hierarchy Example
the picture is described in the document text
To create a SKU packaging hierarchy
  1. Search for and select a style item.
  2. In the Item Catalog, Item tab, Specifications subtab, Overview page, select Create Pack Hierarchy from the Actions menu. Click Go.
  3. In the Create Pack Hierarchy page, select the SKUs that you want to include in a packaging hierarchy.
    Tip: Use the variant attribute group pulldown lists to filter your list of SKU item choices.
  4. Select the item catalog category for the new pack items.
    All new items created are assigned to this item catalog category.
  5. Select the lowest level pack type.
    The lowest level (pack type) of a packaging hierarchy is the base unit (in most cases, Each).
    Note: An item's pack type and Trade Item Unit Descriptor (TIUD) are synonymous with each other.
  6. Select Create Above under the Define Pack Hierarchy region, then click Go.
  7. For the new package level, specify the pack type, quantity, unit of measure, item attribute template, and whether the package level is an engineering item and outbound GDSN-enabled.
    The quantity and unit of measure for a package level refer to the package level just below. For example, a pack or inner pack contains 25 each.
    the picture is described in the document text
  8. Once you have finished building the packaging hierarchy, click Continue.
  9. In the Create Pack Items: Item Attribute Selection page, select the item details (such as attributes) to apply to the new pack item.
    If you selected an item attribute template for the new pack type, you can choose whether to apply the template attribute values first or the attribute values common to both the SKU and pack item catalog categories first.
    Click Continue.
    the picture is described in the document text
  10. In the Create Items: Enter Item/Description page, enter the item number and description for the new pack item, unless it is sequence or function generated. Click Finish.
    Note: You only need to enter the item number and description for the new pack item in the first row of SKU items. The system ignores any item numbers and descriptions entered in later SKU item rows..
    A concurrent request program launches to create the new pack item. You receive a concurrent request ID. After the concurrent request processes successfuly, you can search for the new pack item and view it as you would view any other item.
    the picture is described in the document text




    the picture is described in the document text






Post a Comment