Oracle Inventory provides the following flexfields:

  1. System Items
  2. Item Catalogs
  3. Item Categories
  4. Stock Locators
  5. Account Aliases
  6. Sales Orders
  7. Service Items

Depending on your system’s setup, Inventory may also use some or all of the following
flexfields provided by other Oracle products:

  • Accounting (Oracle General Ledger)
  • Sales Tax Location (Oracle Receivables)
  • Territory (Oracle Receivables)

1. System Items
You can use the System Items Flexfield (also called the Item Flexfield) for recording and reporting your item information. You must design and configure your Item Flexfield before you can start defining items.

Owner Oracle Inventory
Flexfield Code MSTK
Table Name MTL_SYSTEM_ITEMS
Number of Columns 20
Width of Columns 40
Dynamic Inserts Possible No
Unique ID Column INVENTORY_ITEM_ID
Structure Column ORGANIZATION_ID

All Oracle Applications products that reference items share the Item Flexfield and support multiple-segment implementations. However, this flexfield supports only one structure.
You must set up your OE: Item Flexfield profile option to specify the Item Flexfield structure that you will use for your Oracle applications.
Users can also set up the OE: Item Flexfield Entry Method profile option to specify your preferred method of entry for this flexfield.
You can optionally use the item flexfield to default item information for invoice, debit memo, and credit memo lines or you can enter your own line information.
2. Item Catalogs
This key flexfield supports only one structure.

Owner Oracle Inventory
Flexfield Code MICG
Table Name MTL_ITEM_CATALOG_GROUPS
Number of Columns 15
Width of Columns 40
Dynamic Inserts Possible No
Unique ID Column ITEM_CATALOG_GROUP_ID
Structure Column None

 3. Item Categories
You must design and configure your Item Categories Flexfield before you can start defining items since all items must be assigned to categories. You can define multiple structures for your Item Categories Flexfield, each structure corresponding to a different category grouping scheme. You can then associate these structures with the categories and category sets you define.

Owner Oracle Inventory
Flexfield Code MCAT
Table Name MTL_CATEGORIES
Number of Columns 20
Width of Columns 40
Dynamic Inserts Possible No
Unique ID Column CATEGORY_ID
Structure Column STRUCTURE_ID

4. Stock Locators
You can use the Stock Locators Flexfield to capture more information about stock locators in inventory. If you do not have Oracle Inventory installed, or none of your items have locator control, it is not necessary to set up this flexfield.
 
Owner Oracle Inventory
Flexfield Code MTLL
Table Name MTL_ITEM_LOCATIONS
Number of Columns 20
Width of Columns 40
Dynamic Inserts Possible Yes
Unique ID Column INVENTORY_LOCATION_ID
Structure Column ORGANIZATION_ID

If you keep track of specific locators such as aisle, row, bin indicators for your items, you need to configure your Stock Locators Flexfield and implement locator control in your organization.
This key flexfield supports only one structure.

 
5. Account Aliases
This key flexfield supports only one structure.
 

Owner Oracle Inventory
Flexfield Code MDSP
Table Name MTL_GENERIC_DISPOSITIONS
Number of Columns 20
Width of Columns 40
Dynamic Inserts Possible No
Unique ID Column DISPOSITION_ID
Structure Column ORGANIZATION_ID
 
6. Sales Order
The Sales Order Flexfield is a key flexfield used by Oracle Inventory to uniquely identify sales order transactions Oracle Order Management interfaces to Oracle Inventory.

Owner Oracle Inventory
Flexfield Code MKTS
Table Name MTL_SALES_ORDERS
Number of Columns 20
Width of Columns 40
Dynamic Inserts Possible Yes
Unique ID Column SALES_ORDER_ID
Structure Column None

Your Sales Order Flexfield should be defined as Order Number, Order Type, and Order Source. This combination guarantees each transaction to Inventory is unique. You must define this flexfield before placing demand or making reservations in Oracle Order Management.

You must set up the OM: Source Code profile option to determine the source code you will use in for the third segment of this flexfield to guarantee that each transaction is unique. (Oracle Inventory defaults the value of the OM: Source Code profile option to ‘ORDER MANAGEMENT’.)
For your value sets, you must use Dynamic Inserts. The Validation Type should be None. Value Required should be Yes to improve performance of concurrent programs. The value set must be alphanumeric. The value set maximum size must be 40.
You should set the Required field to Yes in the Validation Information region when enabling the flexfield segments. Setting this field to Yes, improves performance when updating existing demand or reservations by guaranteeing that Oracle Order Management always supplies a value.
Set Right-justify Zero-fill Numbers to No so sales order numbers are not padded with zeros.
Oracle Inventory defines a unique ID for each order in MTL_SALES_ORDERS based on this flexfield. The Inventory unique ID, as opposed to the Order Management unique ID, is used throughout Oracle Manufacturing applications.

7. Service Items

The following table lists details for this key flexfield.

Owner Oracle Service
Flexfield Code SERV
Table Name MTL_SYSTEM_ITEMS
Number of Columns 20
Width of Columns 40
Dynamic Inserts Possible No
Unique ID Column INVENTORY_ITEM_ID
Structure Column ORGANIZATION_ID

The Service Item flexfield uses the same table as the System Item Flexfield. However, you can set up your segments differently with the Service Item Flexfield.

The Oracle E-Business Suite products provide many key flexfields as integral parts of the products.

Note: Do not modify the registration of any key flexfield supplied with Oracle E-Business Suite. Doing so can cause serious application errors.

Key Flexfields by Flexfield Name

Here is a table listing many of the key flexfields in Oracle E-Business Suite, ordered by the name of the key flexfield.

Name Code Owning Application
Account Aliases MDSP Oracle Inventory
Accounting Flexfield GL# Oracle General Ledger
Activity Flexfield FEAC Enterprise Performance Foundation
AHL Route AHLR Complex Maintenance, Repair, and Overhaul
Asset Key Flexfield KEY# Oracle Assets
Bank Details KeyFlexField BANK Oracle Payroll
CAGR Flexfield CAGR Oracle Human Resources
Category Flexfield CAT# Oracle Assets
Competence Flexfield CMP Oracle Human Resources
Cost Allocation Flexfield COST Oracle Payroll
Grade Flexfield GRD Oracle Human Resources
Item Catalogs MICG Oracle Inventory
Item Categories MCAT Oracle Inventory
Job Flexfield JOB Oracle Human Resources
Location Flexfield LOC# Oracle Assets
Oracle Service Item Flexfield SERV Oracle Inventory
People Group Flexfield GRP Oracle Payroll
Personal Analysis Flexfield PEA Oracle Human Resources
Position Flexfield POS Oracle Human Resources
Public Sector Budgeting BPS Oracle Public Sector Budgeting
Sales Orders MKTS Oracle Inventory
Sales Tax Location Flexfield RLOC Oracle Receivables
Soft Coded KeyFlexfield SCL Oracle Human Resources
Stock Locators MTLL Oracle Inventory
System Items MSTK Oracle Inventory
Territory Flexfield CT# Oracle Receivables
Training Resources RES Oracle Learning Management

You use the flexfield code and the owning application to identify a flexfield when you call it from a custom form.

Note: that the following flexfields are single-structure seeded key flexfields: Account Aliases, Item Catalogs, Oracle Service Item Flexfield, Stock Locators, and System Items.

Key Flexfields by Owning Application

Here is a table listing many of the key flexfields in Oracle E-Business Suite, ordered by the application that “owns” the key flexfield. Note that other applications may also use a particular flexfield.

Owner Name Code
Oracle Assets Asset Key Flexfield KEY#
Oracle Assets Category Flexfield CAT#
Oracle Assets Location Flexfield LOC#
Oracle Complex Maintenance, Repair, and Overhaul AHL Route AHLR
Oracle Enterprise Performance Foundation Activity Flexfield FEAC
Oracle General Ledger Accounting Flexfield GL#
Oracle Human Resources CAGR Flexfield CAGR
Oracle Human Resources Competence Flexfield CMP
Oracle Human Resources Grade Flexfield GRD
Oracle Human Resources Job Flexfield JOB
Oracle Human Resources Personal Analysis Flexfield PEA
Oracle Human Resources Position Flexfield POS
Oracle Human Resources Soft Coded KeyFlexfield SCL
Oracle Inventory Account Aliases MDSP
Oracle Inventory Item Catalogs MICG
Oracle Inventory Item Categories MCAT
Oracle Inventory Sales Orders MKTS
Oracle Inventory Stock Locators MTLL
Oracle Inventory Oracle Service Item Flexfield SERV
Oracle Inventory System Items MSTK
Oracle Learning Management Training Resources RES
Oracle Payroll Bank Details KeyFlexField BANK
Oracle Payroll Cost Allocation Flexfield COST
Oracle Payroll People Group Flexfield GRP
Oracle Public Sectory Budgeting PSB Position Flexfield BPS
Oracle Receivables Sales Tax Location Flexfield RLOC
Oracle Receivables Territory Flexfield CT#

Tables of Individual Key Flexfields in Oracle E-Business Suite

The following sections contain a table for individual key flexfields in the Oracle E-Business Suite. These tables provide you with useful information, including:

  • Which application owns the key flexfield
  • The flexfield code (used by forms and routines that call a flexfield)
  • The name of the code combinations table
  • How many segment columns it has
  • The width of the segment columns
  • The name of the unique ID column (the CCID column)
  • The name of the structure ID column
  • Whether it is possible to use dynamic insertion with this key flexfield

Many of these key flexfield sections also contain information on the uses and purpose of the flexfield, as well as suggestions for how you might want to implement it at your site.

Account Aliases

The following table lists details for this key flexfield.

Owner Oracle Inventory
Flexfield Code MDSP
Table Name MTL_GENERIC_DISPOSITIONS
Number of Columns 20
Width of Columns 40
Dynamic Inserts Possible No
Unique ID Column DISPOSITION_ID
Structure Column ORGANIZATION_ID

This key flexfield supports only one structure.

Accounting Flexfield

The following table lists details for this key flexfield.

Owner Oracle General Ledger
Flexfield Code GL#
Table Name GL_CODE_COMBINATIONS
Number of Columns 30
Width of Columns 25
Dynamic Inserts Possible Yes
Unique ID Column CODE_COMBINATION_ID
Structure Column CHART_OF_ACCOUNTS_ID

The Accounting Flexfield is fully described in the Oracle General Ledger documentation.

Asset Key Flexfield

The following table lists details for this key flexfield.

Owner Oracle Assets
Flexfield Code KEY#
Table Name FA_ASSET_KEYWORDS
Number of Columns 10
Width of Columns 30
Dynamic Inserts Possible Yes
Unique ID Column CODE_COMBINATION_ID
Structure Column None

Oracle Assets uses the asset key flexfield to group your assets by non-financial information. You design your asset key flexfield to record the information you want. Then you group your assets by asset key so you can find them without an asset number.

Warning: Plan your flexfield carefully. Once you have started entering assets using the flexfield, you cannot change it.

Bank Details KeyFlexField

The following table lists details for this key flexfield.

Owner Oracle Payroll
Flexfield Code BANK
Table Name PAY_EXTERNAL_ACCOUNTS
Number of Columns 30
Width of Columns 60
Dynamic Inserts Possible Yes
Unique ID Column EXTERNAL_ACCOUNT_ID
Structure Column ID_FLEX_NUM

The Bank Details KeyFlexfield [sic] holds legislation specific bank account information. The Bank Details structure that you see is determined by the legislation of your Business Group.
Localization teams determine the data that is held in this flexfield. Each localization team defines a flexfield structure that allows you to record the bank account information relevant to each legislation.
If you are using a legislation for which a Bank KeyFlexfield structure has been defined you should not modify the predefined structure.

Warning: You should not attempt to alter the definitions of the Bank Details Flexfield which are supplied. These definitions are a fundamental part of the package. Any change to these definitions may lead to errors in the operating of the system.
It is possible that Oracle Human Resources will use the other segments of this flexfield in the future. Therefore, you should not try to add other segments to this Flexfield. This may affect your ability to upgrade the system in the future.
Consult your Oracle Human Resources National Supplement for the full definition of your Bank Details Flexfield.

Category Flexfield

The following table lists details for this key flexfield.

Owner Oracle Assets
Flexfield Code CAT#
Table Name FA_CATEGORIES
Number of Columns 7
Width of Columns 30
Dynamic Inserts Possible No
Unique ID Column CATEGORY_ID
Structure Column None

Oracle Assets uses the category flexfield to group your assets by financial information. You design your category flexfield to record the information you want. Then you group your assets by category and provide default information that is usually the same for assets in that category.

Warning: Plan your flexfield carefully. Once you have started entering assets using the flexfield, you cannot change it.

Cost Allocation Flexfield

The following table lists details for this key flexfield.

Owner Oracle Payroll
Flexfield Code COST
Table Name PAY_COST_ALLOCATION_KEYFLEX
Number of Columns 30
Width of Columns 60
Dynamic Inserts Possible Yes
Unique ID Column COST_ALLOCATION_KEYFLEX_ID
Structure Column ID_FLEX_NUM

You must be able to get information on labor costs from your payrolls, and send this information to other systems. Payroll costs must of course go to the general ledger. Additionally, you may need to send them to labor distribution or project management systems.
The Cost Allocation Flexfield lets you record, accumulate and report your payroll costs in a way which meets the needs of your enterprise.

Grade Flexfield

The following table lists details for this key flexfield.

Owner Oracle Human Resources
Flexfield Code GRD
Table Name PER_GRADE_DEFINITIONS
Number of Columns 30
Width of Columns 60
Dynamic Inserts Possible Yes
Unique ID Column GRADE_DEFINITION_ID
Structure Column ID_FLEX_NUM

Grades are used to represent relative status of employees within an enterprise, or work group. They are also used as the basis of many Compensation and Benefit policies.

Item Catalogs

The following table lists details for this key flexfield.

Owner Oracle Inventory
Flexfield Code MICG
Table Name MTL_ITEM_CATALOG_GROUPS
Number of Columns 15
Width of Columns 40
Dynamic Inserts Possible No
Unique ID Column ITEM_CATALOG_GROUP_ID
Structure Column None

This key flexfield supports only one structure.

Item Categories

The following table lists details for this key flexfield.

Owner Oracle Inventory
Flexfield Code MCAT
Table Name MTL_CATEGORIES
Number of Columns 20
Width of Columns 40
Dynamic Inserts Possible No
Unique ID Column CATEGORY_ID
Structure Column STRUCTURE_ID

You must design and configure your Item Categories Flexfield before you can start defining items since all items must be assigned to categories.
You can define multiple structures for your Item Categories Flexfield, each structure corresponding to a different category grouping scheme. You can then associate these structures with the categories and category sets you define.

Job Flexfield

The following table lists details for this key flexfield.

Owner Oracle Human Resources
Flexfield Code JOB
Table Name PER_JOB_DEFINITIONS
Number of Columns 30
Width of Columns 60
Dynamic Inserts Possible Yes
Unique ID Column JOB_DEFINITION_ID
Structure Column ID_FLEX_NUM

The Job is one possible component of the Employee Assignment in Oracle Human Resources. The Job is used to define the working roles which are performed by your employees. Jobs are independent of Organizations. With Organizations and Jobs you can manage employee assignments in which employees commonly move between Organizations but keep the same Job.
You use the Job Flexfield to create Job Names which are a unique combination of segments. You can identify employee groups using the individual segments of the Job whenever you run a report or define a QuickPaint.

Location Flexfield

The following table lists details for this key flexfield.

Owner Oracle Assets
Flexfield Code LOC#
Table Name FA_LOCATIONS
Number of Columns 7
Width of Columns 30
Dynamic Inserts Possible Yes
Unique ID Column LOCATION_ID
Structure Column None

Oracle Assets uses the location flexfield to group your assets by physical location. You design your location flexfield to record the information you want. Then you can report on your assets by location. You can also transfer assets that share location information as a group, such as when you move an office to a new location.

Warning: Plan your flexfield carefully. Once you have started entering assets using the flexfield, you cannot change it.

People Group Flexfield

The following table lists details for this key flexfield.

Owner Oracle Payroll
Flexfield Code GRP
Table Name PAY_PEOPLE_GROUPS
Number of Columns 30
Width of Columns 60
Dynamic Inserts Possible Yes
Unique ID Column PEOPLE_GROUP_ID
Structure Column ID_FLEX_NUM

The People Group flexfield lets you add your own key information to the Employee Assignment. You use each segment to define the different groups of employees which exist within your own enterprise. These may be groups which are not identified by your definitions of other Work Structures.

Personal Analysis Flexfield

The following table lists details for this key flexfield.

Owner Oracle Human Resources
Flexfield Code PEA
Table Name PER_ANALYSIS_CRITERIA
Number of Columns 30
Width of Columns 60
Dynamic Inserts Possible Yes
Unique ID Column ANALYSIS_CRITERIA_ID
Structure Column ID_FLEX_NUM

The Personal Analysis Key Flexfield lets you add any number of Special Information Types for people. Each Special Information Type is defined as a separate flexfield structure for the Personal Analysis Flexfield.
Some common types of information you might want to hold are:

  • Qualifications
  • Language Skills
  • Medical Details
  • Performance Reviews
  • Training Records

Each structure can have up to 30 different segments of information.

Position Flexfield

The following table lists details for this key flexfield.

Owner Oracle Human Resources
Flexfield Code POS
Table Name PER_POSITION_DEFINITIONS
Number of Columns 30
Width of Columns 60
Dynamic Inserts Possible Yes
Unique ID Column POSITION_DEFINITION_ID
Structure Column ID_FLEX_NUM

Positions, like Jobs, are used to define employee roles within Oracle Human Resources. Like Jobs, a Position is an optional component of the Employee Assignment. However, unlike Jobs, a Position is defined within a single Organization and belongs to it.
Positions are independent of the employees who are assigned to those positions. You can record and report on information which is directly related to a specific position rather than to the employee.

Sales Orders

The following table lists details for this key flexfield.

Owner Oracle Inventory
Flexfield Code MKTS
Table Name MTL_SALES_ORDERS
Number of Columns 20
Width of Columns 40
Dynamic Inserts Possible Yes
Unique ID Column SALES_ORDER_ID
Structure Column None

The Sales Orders Flexfield is a key flexfield used by Oracle Inventory to uniquely identify sales order transactions Oracle Order Management interfaces to Oracle Inventory.
Your Sales Orders Flexfield should be defined as Order Number, Order Type, and Order Source. This combination guarantees each transaction to Inventory is unique.
You must define this flexfield before placing demand or making reservations in Oracle Order Management.

Sales Tax Location Flexfield

The following table lists details for this key flexfield.

Owner Oracle Receivables
Flexfield Code RLOC
Table Name AR_LOCATION_COMBINATIONS
Number of Columns 10
Width of Columns 22
Dynamic Inserts Possible Yes
Unique ID Column LOCATION_ID
Structure Column LOCATION_STRUCTURE_ID

The Sales Tax Location Flexfield is used to calculate tax based on different components of your customers’ shipping addresses for all addresses in your home country.

Oracle Service Item Flexfield

The following table lists details for this key flexfield.

Owner Oracle Service
Flexfield Code SERV
Table Name MTL_SYSTEM_ITEMS
Number of Columns 20
Width of Columns 40
Dynamic Inserts Possible No
Unique ID Column INVENTORY_ITEM_ID
Structure Column ORGANIZATION_ID

The Service Item flexfield uses the same table as the System Item Flexfield. However, you can set up your segments differently with the Service Item Flexfield.

Soft Coded KeyFlexfield

The following table lists details for this key flexfield.

Owner Oracle Human Resources
Flexfield Code SCL
Table Name HR_SOFT_CODING_KEYFLEX
Number of Columns 30
Width of Columns 60
Dynamic Inserts Possible Yes
Unique ID Column SOFT_CODING_KEYFLEX_ID
Structure Column ID_FLEX_NUM

The Soft Coded KeyFlexfield holds legislation specific information. The Soft Coded KeyFlexfield structure that a user will see is determined by the legislation of the Business Group.
Localization teams determine the data that is held in this flexfield. Each localization team defines a flexfield structure and uses qualifiers to define the level at which each segment is visible. Segments can be seen at business group, payroll or assignment level. The type of information that is held in this key flexfield varies from legislation to legislation.
If you are using a legislation for which a Soft Coded KeyFlexfield structure has been defined you should not modify the predefined structure.

Stock Locators

The following table lists details for this key flexfield.

Owner Oracle Inventory
Flexfield Code MTLL
Table Name MTL_ITEM_LOCATIONS
Number of Columns 20
Width of Columns 40
Dynamic Inserts Possible Yes
Unique ID Column INVENTORY_LOCATION_ID
Structure Column ORGANIZATION_ID

You can use the Stock Locators Flexfield to capture more information about stock locators in inventory. If you do not have Oracle Inventory installed, or none of your items have locator control, it is not necessary to set up this flexfield.
If you keep track of specific locators such as aisle, row, bin indicators for your items, you need to configure your Stock Locators Flexfield and implement locator control in your organization.
This key flexfield supports only one structure.

System Items (Item Flexfield)

The following table lists details for this key flexfield.

Owner Oracle Inventory
Flexfield Code MSTK
Table Name MTL_SYSTEM_ITEMS
Number of Columns 20
Width of Columns 40
Dynamic Inserts Possible No
Unique ID Column INVENTORY_ITEM_ID
Structure Column ORGANIZATION_ID

You can use the System Items Flexfield (also called the Item Flexfield) for recording and reporting your item information. You must design and configure your Item Flexfield before you can start defining items.
All Oracle E-Business Suite products that reference items share the Item Flexfield and support multiple-segment implementations. However, this flexfield supports only one structure.

Territory Flexfield

The following table lists details for this key flexfield.

Owner Oracle Receivables
Flexfield Code CT#
Table Name RA_TERRITORIES
Number of Columns 20
Width of Columns 25
Dynamic Inserts Possible Yes
Unique ID Column TERRITORY_ID
Structure Column None

You can use the Territory Flexfield for recording and customized reporting on your territory information. Territory Flexfields are also displayed in the Transaction Detail and Customer Detail reports in Oracle Receivables.

References

NOTE:1050253.1 – How Do I Qualify for Access to Oracle Business Accelerator for Business Intelligence Applications?
NOTE:1050267.1 – Training Requirements for Oracle Business Accelerator for Business Intelligence Applications
NOTE:409133.1 – How Do I Qualify for Oracle Business Accelerator Access for E-Business Suite?
NOTE:604885.1 – How to Attach Screen Shot of My OBA Training Completion Certificate?
NOTE:760414.1 – How Do I Qualify for Access to Oracle Business Accelerator for Agile?
NOTE:789175.1 – How Do I Qualify for Access to Oracle Business Accelerator for Supply Chain Planning with Demantra?
NOTE:793268.1 – How Do I Qualify for Access to Oracle Business Accelerator for Oracle Transportation Management?
NOTE:1144664.1 – How Do I Qualify for Oracle Business Accelerator Access for JD Edwards EnterpriseOne?

Setups to be done:

     1. Create Purchase Item and Org level check in
         a) Purchasing tab : Enable Use Approved Supplier and List Price
         b) General planning tab : Enable Consigned
         c) Costing tab: Enable Costing and Inventory asset value
         d) Assigned to Specific org.
  1. Supplier is defined as well as Supplier Site
    a) Ship to and Bill to : Purchasing
    c) Pay on: use
    d) Invoice summary level : Consumption advice
  2. Inventory set up :
    a) INV: Setup Transaction → Consigned /VMI Consumption. 
    1) Consigned tab is checked.
    2) Transaction type: Subinventory Transfer
    3) From Subinventory : Expense Subinventory
    4) To Subinventory : Asset Subinventory
    5) Owning party and other details has been specified.
  3. Create and Approved BPA
    a) Create Blanket agreement ans the BPA has been Approved
    b) Agreement number has been attached to ASL attribute
    c) Consigned from supplier has been selected.
    d) Zero days as billing cycle.
  4. Receipts has been performed in expense Subinventory
    – Receipt routing : Direct delivery
    – No accounting impact has been taken place.
  5. Receive it at the expense SI mentioned
    – The location field is not mandatory (normally for a direct receipt) as it a consigned material.
  6. Consigned transaction has been performed
    – Transfer to regular.
    – Subinventory selected has expense Subinventory
    – Owning party has been defaulted
    – Qty has been specified
  7. I can see that line has been split in on-hand qty and also the accounting impact is correct.
    – The line would have got split into two indicating both our material and the party’s material.
  8. Create consumption advice request has been processed.
  9. Now the problem is when I perform consigned transaction the item should be transferred from expense sub inventory to Asset Subinventory(FG in my case) automatically but i can’t see this happening
    (goods are not transfer to asset sub inventory has I set in my consignment setup) and also I need to ship the goods from here.
  10. Profile : INV: Allow Expense to Asset Transfer = Yes.
  11. Run the concurrent Pay on Receipt Auto Invoice
    – again add it your request group
    – with a transaction source of “ERS_AND_USE” for our inventory receipt number. – This will take the data from the “Consumption Advice” and populate the interface tables of Oracle payable Responsibility.
    – Pay on receipt will also automatically spawn the child concurrent “Payables Open Interface Import” for pulling the data from the interface table to the Base table of Oracle payable Responsibility.
  12. Switch resp to Payable and enquire the creation of unvalidated, distributed Invoice
    – [Nav: Invoices=> Inquiry=> Invoices] for our supplier. Check the balance owed to him also [a button in the bottom of the inquiry form].
  13. Validate the Invoice and create accounting
    – Creation of liability owed to the supplier.
    – Check for funds available in the bank and make a full payment from our internal bank in our payment document and make final accounting.
    – This will facilitate passing of the accounting entries to Cash Management for re-conciliation and manual adjustments,
    – If necessary before posting to General Ledger.
Cycle counting is the periodic counting of individual items throughout the course of the year to ensure the accuracy of inventory quantities and values. Accurate system on-hand quantities are essential for managing supply and demand, maintaining high service levels, and planning production.
You can perform cycle counting instead of taking complete physical inventories, or you can use both techniques side-by-side to verify inventory quantities and values.
Inventory supports serialized cycle counting, and the following modules discuss the

Tasks Involved

  • Define a cycle count for the organization or subinventory level.
  • Automatically schedule item counts using ABC count frequencies.
  • Manually schedule counts for the following inventory control details:
      • items, or specific revisions, lots
      • subinventories or specific locators
  • Generate daily, weekly, or period count requests and lists based on your schedule.
  • Approve, reject, or request recounts for cycle count adjustments based on approval
  • Import cycle count entries from external systems.
  • Export cycle count entries to external systems.

Overview of ABC Analysis

Defining and Maintaining a Cycle Count

A combination of parameters constitutes a cycle count header, identified by the cycle count name. You use this name to identify any activity pertaining to this cycle count.
You can define and maintain an unlimited number of cycle counts in Oracle Inventory. For example, you can define separate cycle counts representing different sets of subinventories in your warehouse.

Prerequisites

  • Define ABC Classes.
  • Define your workday calendar.
  • When determining cycle count classed based on ABC analysis, you must compile an ABC analysis and assign you compiled items to ABC classes.

To define a new cycle count:

1. Navigate to the Cycle Count Summary folder window by selecting Cycle Counts on the menu and choose New to open the Cycle Counts window.

  1. Enter a unique name for the cycle count.
    1. Enter the workday calendar to use for this cycle count.
    2. Inventory uses this calendar to determine the days on which to automatically schedule cycle counts.
  2. Enter the general ledger account to charge for cycle count adjustments.

To enter control and scope information for your cycle count:

  1. Select the Control, Scope tabbed region.
    1. Enter the Count Controls:
      • Optionally, enter the date on which the cycle count becomes inactive. As of this date, you cannot generate schedules or perform any counting activities for this cycle count.
      • Enter the number of workdays that can pass after the date the count request was generated, before a scheduled count becomes a late count.
      • Enter the sequence number to use as the starting number in the next count request generator. The count sequence number uniquely identifies a particular count and is used in ordering the cycle count listing.
  • Determine whether you can enter counts for items not scheduled to be counted (Unscheduled Entries).
  • Determine whether to display system on-hand quantities during count entry.
    1. Determine whether Inventory automatically assigns a status of Recount to out-of-tolerance counts and includes them in the next cycle count listing.
    2. If you turn this option on, navigate to the Maximum field and enter the maximum number of times Inventory can generate an automatic recount request. Once this number is reached the adjustment must be approved or rejected.
  1. Determine the subinventories to include in the cycle count.

If you choose Specific subinventories, you can navigate to the Subinventory region and select the subinventories to include in the cycle count.

To enter serial number control and autoschedule information:

  1. Navigate to the Serial Control, Schedule tabbed region.
  2. Select the count option to determine whether to exclude serialized items from the cycle count (Not Allowed), create one count request for each serial number (One Per Request), or create multiple serial details in a count request (Multiple Per Request).
  3. Select the detail option:

Quantity and Serial Numbers: Serial number and quantity are required and are validated when entering adjustments.
Quantity Only: Serial number entry is optional if the count quantity matches the system quantity, regardless of whether the serial numbers match. If you do not enter serial numbers, the count is marked as completed, and no adjustments are performed. If you do enter serial numbers, both quantity and serial numbers are validated when determining whether adjustments are required.
4. Select the adjustment option:
Adjust if Possible: If a discrepancy exists between the count quantity and system quantity or if the entered serial numbers do not correspond to the serial numbers already in the specified location, then the system will attempt to make adjustments if the adjustment variance and value are within tolerances. These adjustments consist of receipts and issues of the appropriate serial numbers to and from the specified location and are applicable only to instances in which new serial numbers or shipped serial numbers are counted.
Review All Adjustments: No automatic adjustments are attempted.

  1. Select the discrepancy option to indicate whether an adjustment is attempted when a count includes a serial number already assigned to the same item elsewhere in the system.
  2. Determine whether to automatically schedule this cycle count.

If you turn automatic scheduling on, enter the following information:
Frequency: Indicate whether to schedule cycle counts Daily, Weekly, or By period. Inventory uses this information, along with the count frequency of each cycle count class, when performing automatic cycle count scheduling. The value you enter here dictates the window of time within which you can enter counts against a schedule bucket.
Schedule Interval Example
If you choose weeks as your schedule interval, Inventory schedules a week’s worth of counts each time the automatic scheduler executes. You then have that week to complete all these counts. On the other hand, if you choose days, Inventory schedules only that one day’s counts, and you need to complete those counts on that given day.
Last Date: Inventory displays the last date this cycle count was automatically scheduled.
Next Date: Inventory displays the first workday for the next schedule interval when this cycle count is scheduled. You can enter a later date in this field if you want to override the automatic schedule and skip one or more intervals. If your schedule interval is Weekly or By period, the date you enter must be the first workday of the period for which you want to generate schedule requests.
Next Schedule Date Example
Assume your schedule interval is Weekly and you last ran your schedule on Monday, March 20. Your calendar workdays were specified as Monday through Friday. When you ran your schedule on March 20 the Next Scheduled Date was set to March 27. You know that during the week of March 27 you are doing a physical inventory so you do not wish to do cycle counting. You can set Next Scheduled Date to April 3, the first weekday of the following next week. Inventory does not generate any cycle count requests for the week of March 27-31, and when you schedule counts on April 3, Inventory generates requests only for the week of April 3-7.
7. Optionally, determine whether to automatically generate requests to count items with an on-hand quantity of zero.
To define adjustments and ABC information:
1. Navigate to the Adjustments, ABC tabbed region.
2. Determine when approval is required for adjustments:
Never: Inventory automatically posts adjustment transactions where entered counts differ from system balances.
If out of tolerance: Inventory does not automatically post adjustment transactions for counts outside a specified approval tolerance. You must approve such adjustments before posting.
Always: You must approve all cycle count adjustments, regardless of tolerance levels, before Inventory can post any of them.
3. If you choose to require approval for adjustments If out of tolerance, enter positive and negative tolerances.
Qty Variance: Enter the percentage variances of count quantity to on-hand quantity beyond which adjustments are held for approval.
Adjustment Value: Enter the adjustment values beyond which adjustments are held for approval.
Hit/Miss Analysis: Enter the percentage variances of count quantity to on-hand quantity beyond which Inventory considers a count entry a miss for hit/miss reporting.
4. Optionally, enter ABC initialization or update information:

  • Group: Enter the ABC group name on which to base the cycle count item initialization or update.
    • Option: Choose one of the following options:
      • None: Do not change to the list of cycle count items.
      • (Re)initialize: Use the ABC group you specified to load all items and their ABC assignments into the list of items to include in your cycle count. If you already had items defined for your cycle count, this action deletes existing information and reloads the items from the ABC group.
      • Update: Use the ABC group you specified to insert new cycle count items.
    • If you chose the update option:
      • Indicate whether to update classes. If an item’s ABC class assignment in the ABC group you specified is different from the cycle count class this item is assigned, Inventory updates the cycle count class for the item with the ABC assignment in the specified ABC group.
      • Indicate whether to delete unused item assignments that are no longer referenced in the specified ABC group.
5. Save your work.

To enter ABC classes to include in your cycle count:

1. To define cycle count items:

Overview of Material Pickwaves,

Customizing the Presentation of Data in a Folder,

Defining Cycle Count Classes

You can enter ABC classes to include in your cycle count. You can also enter approval and hit/miss tolerances for your cycle count classes.

To define cycle count classes:

  1. Navigate to the Cycle Count Summary folder window.
  2. Select a cycle count and choose Open.
  3. In the Cycle Counts window choose Classes. The Cycle Count Classes window appears.
  1. Enter the name of the ABC class to use to define your cycle count classes.
  2. Enter the number of times per year you want to count each item in this class.
  3. Optionally, enter positive and negative tolerances. If you do not enter tolerances, Inventory uses the values you entered in the Cycle Counts window.

Quantity %: Enter the percentage variances of count quantity to on-hand quantity
beyond which adjustments are held for approval.
Adjustment Value: Enter the adjustment values beyond which adjustments are held
for approval.
Hit/Miss %: Enter the percentage variances of count quantity to on-hand quantity beyond which Inventory considers a count entry a miss for hit/miss reporting. Note that the hit/miss percentage is based on the first count of an item, not recounts.
7. Save your work.

Cycle Count Items

You need to load items into your cycle count before you can schedule or count them. There are two methods you can use to do this. The first is to specify an existing ABC group from which to load your items. Oracle Inventory automatically includes all items in the ABC group you choose in your cycle count. Inventory also copies the ABC classes for that ABC group into the current cycle count classes and maintains the same classifications for the included items. You can then change the classifications of your items for your cycle count independent of the ABC classes.
Once you have generated your list of items to count from an ABC group, you can periodically refresh the item list with new or reclassified items from a regenerated ABC group. Using the Cycle Counts window, you can choose whether to automatically update class information for existing items in the cycle count based on the new ABC assignments. You can also choose to have any items that are no longer in the ABC group automatically deleted from the cycle count list. Any new items are added.
The second method of maintaining the cycle count item list is to manually enter, delete, or update the items you want included/excluded using the Cycle Count Items window. You may want to use this form to load all your items for a cycle count, or to simply add items as they are defined in the system rather than recompiling your ABC group and doing a complete reinitialization of your cycle count items.

Defining Control Group Items

When you choose the items to include in your cycle count, you can specify which items make up your control group. When you generate automatic schedules you can indicate whether to include items in your control group as a control measure.

Defining Cycle Count Items

Use the Cycle Count Items window to add items to your cycle count or to update certain attributes for existing cycle count items. You can schedule, generate count requests for, and count only those items that are included in this list.
You can also view all items included in a cycle count as a result of initializing from an ABC analysis.

To enter or update cycle count items:

  1. Navigate to the Cycle Count Summary folder window.
  2. Select a cycle count and choose Open.
  3. In the Cycle Counts window choose Items. The Cycle Count Items window appears.
  1. Enter the ABC class to which this item belongs. You can only choose from those classes you assigned to your cycle count in the Cycle Count Classes window.
  2. Enter the item to assign to your cycle count.
  3. If you are using automatic scheduling, indicate whether this is a control group item. When you generate schedules you can indicate whether to include control group items.
    1. Optionally, enter positive and negative quantity variances of count quantity to on-hand quantity beyond which adjustments may be held for approval.
    2. If you enter a value in this field, Inventory uses it instead of the tolerance specified (if any) for the class to which the item belongs, or instead of the tolerance specified (if any) for the cycle count header.
  4. Save your work.

Cycle Count Items,

Cycle Count Scheduling

Automatic Scheduling

Oracle Inventory uses the number of items in each cycle count class, the count frequency of each class, and the workday calendar of your organization to determine how many and which items you need to count during the scheduling frequency.
In order for Inventory to perform automatic scheduling you must:

  • Set the Cycle Count Enabled item attribute to Yes for the items you want to include in the cycle count.
  • Enable automatic scheduling when you define your cycle count.
  • Request the schedule using the Generate Automatic Schedule Requests window.

Each time the auto scheduler runs, it schedules counts only for the schedule interval you defined for the cycle count header. So if your schedule interval is weeks, Inventory schedules all items that need to be counted on all of the workdays in the current week. If your schedule interval is days, then Inventory only schedules those items that are due for counting on the current date.

Manual Scheduling

You can manually schedule counts in addition to, or instead of those generated with automatic scheduling. You can request counts for specific subinventories, locators, and items, and set the count for any inventory date. For example, you could enter a request to count item A wherever it can be found in subinventory X. Or you could request to count all item quantities in subinventory Y, locator B-100.
Since manually scheduled counts have no impact on automatically scheduled counts, you can potentially count some items more frequently than you had initially planned.

Physical Location Scheduling

You can use this feature to execute location-based cycle counting. You first need to generate a schedule for counting each subinventory and locator. You then need to enter the schedule requests for each locator, specifying the schedule date.

Generating Automatic Schedules

You can submit a program for automatic generation of schedule requests.

To generate automatic schedules:

  1. Navigate to Cycle Counts Summary folder window or the Cycle Counts window.
  2. Select a cycle count and choose Cycle Count Scheduler from the Tools menu. The Cycle Count Scheduler Parameters window appears.
  3. Indicate whether to include items belonging to the control group in the list of items for which to generate schedule requests.
  4. Choose OK to submit the request to the concurrent manager.

You can schedule an item or location for cycle counting at any time. You may manually schedule cycle counts to supplement your automatic schedules. You use this feature to achieve item-based or location-based cycle counting.

Entering Manual Schedule Requests

To manually schedule cycle count requests:

1. Navigate to the Manual Schedule Requests window or choose the Schedule button on the Cycle Counts Summary folder window.

  1. Enter the cycle count name you are scheduling.
  2. Select the item or location (subinventory) for counting.

You can manually schedule specific items by entering values in different combinations of the item, revision, lot, serial number, subinventory, and locator fields.
If you do not enter an item, you must enter a subinventory. Inventory schedules a count of all items stocked in this subinventory. If you enter an item and a subinventory, Inventory schedules the item to be counted only in this subinventory.

  1. Enter the date on which Inventory is to schedule the count you have specified. The date you enter cannot be before today’s date and must be a valid workday as defined by the workday calendar for your cycle count.
  2. Indicate whether to generate count requests for this item, revision, lot, serial number, subinventory, or locator combination even if the system on-hand quantity is zero. This may be useful in performing exception-based counting to verify that the actual on-hand quantity is indeed zero.
  3. Save your work.

Count Requests

After you have successfully scheduled your counts, you can submit the process to generate count requests. This process takes the output of the automatic scheduler and your manual schedule entries, and generates a count request for each item number, revision, lot number, subinventory, and locator combination for which on-hand quantities exist. These count requests are ordered first by subinventory and locator, then by item, revision, and lot. Oracle Inventory assigns a unique sequence number to each count request that can be used for reporting, querying, and rapid count entry.
Because the count requests are derived from the state of on-hand balances at the time the Generate Cycle Count Requests process is run, you should wait to run it until you
Note: When you schedule an item to be counted using manual scheduling, some schedule requests may have overlapping count requirements. The count request generator does not create duplicate count requests, but instead cross-references one count request back to each associated schedule request.

Count Request for Items with Zero Count

By default Inventory does not automatically generate requests to count items with an on-hand quantity of zero. To include such items:

  • Define all sourcing details and inventory controls for the item. For example, if an item is under predefined locator control, be sure it is assigned to a subinventory
  • Select the Generate Zero Counts option when you define your cycle count.

The count request generation process then automatically creates a count request. If a quantity is found and counted, an adjustment is made.
At count entry, you may receive a warning message stating, “Zero count, no adjustment performed.” Inventory generates this warning if it cannot find all levels of inventory control defined for the item. In this situation, enter the count, but no adjustment is performed. To make an adjustment and update the missing information, enter an unscheduled count using either the Cycle Count Entries or Approve Adjustments window.

Generating Count Requests

To submit a request set to perform a full cycle count:

  1. Navigate to Cycle Counts Summary folder window or the Cycle Counts window.
    1. Choose Perform Full Cycle Count from the Tools menu. The set includes the following processes and report:
      • Generate automatic schedule requests: Enter parameters for cycle count to use and indicate whether to include control items.
      • Generate cycle count requests: Enter parameters for cycle count to use.
      • Cycle count listing: Enter parameters for cycle count to use, start and end dates, recounts, and subinventory to count.
  2. Choose Submit.

To submit the program to generate cycle count requests:

1. Navigate to Cycle Counts Summary window or the Cycle Counts window.

2. Choose Generate Count Requests from the Tools menu to submit the process to the concurrent manager.

Requesting the Cycle Count List

After you generate count requests you can submit the request for the Cycle Count Listing report. This report lists all counts that you need to perform within a given date range.

To request a cycle count list:

    1. Navigate to Cycle Counts Summary folder window or the Cycle Counts window.
    2. You can also navigate to the ABC and Counting Reports window to submit the
  1. Choose Cycle Count Listing Report from the Tools menu.
  2. Enter start and end dates for the list. Inventory reports counts falling on the start date through the end date.
  3. Enter the specific subinventory for which to report scheduled counts.
  4. Indicate whether the cycle count list includes only recounts or scheduled counts and recounts.
  5. Choose OK to submit the request to the concurrent manager.

Entering Cycle Counts

You can use the same window to enter counts of items requested via automatic or manual cycle count scheduling. If unscheduled count entries are allowed for your cycle counts, you can enter those also.
Oracle Inventory automatically queries up all count requests for which you have not yet entered a count. You can use flexible search criteria to specify the group of count requests for which you want counts entered to speed up the count entry process. For example, you can specify a range of count request sequences assigned to one person so they can be entered in the same order they were printed on the count sheet.

To select the cycle count to use:

  1. Navigate to the Cycle Count Entries window from the menu or choose Counts from the Cycle Counts Summary folder window.
    1. Enter the name of the cycle count for which to enter counts.
    2. This information is provided if you navigate from the Cycle Counts Summary folder window, and the Find button is not available
  2. Enter the date the cycle count was performed. This field automatically defaults to the current date, you can modify it if necessary.
  3. Enter the name of the employee who performed the cycle count. This field automatically defaults to the current user, you can modify it if necessary.
    1. Enter the general ledger account to which to charge adjustments from this cycle count. The default is the adjustment account you entered while defining your cycle count.
    2. Inventory performs a cycle count adjustment by creating a material transaction for the quantity and sign (plus or minus) of the adjustment. The transaction debits or credits the adjustment account depending on the direction of the transaction.
  4. Display the count requests you want to enter.

You can choose the Find button to query all open count requests. If you choose not to query all open requests, you can either:

  • Enter counts individually by entering existing sequence numbers. When you enter an existing sequence number the details for that request display. You only need to enter the quantity counted.
  • Use the find feature on the Query menu to query a subset of count requests matching the search criteria you enter. You can search by any combination of count sequences, item, revision, subinventory, locator, or lot. You can also indicate whether to include recounts.

To enter scheduled counts:

  1. Select the Count tabbed region.
    1. Enter the count quantity for the item. Inventory uses this quantity with the specified unit of measure to determine the value of the cycle count adjustment. If the item is under dual unit of measure control, then the secondary UOM and quantity are supplied automatically when you enter the primary quantity.
    2. Note: When you perform a recount, the quantity field on the adjustments tab is populated with the previously entered count.
  2. Save your work.

To enter unscheduled counts:

  1. Navigate to the Cycle Count Entries window from the menu.
  2. Choose the Find button and select No. This enables you to enter items and counts manually.
  3. Enter the item for which you are entering counts.
  4. If your item is under revision control, enter the revision for which you are entering counts.
  5. Enter the subinventory for which you are entering counts. You can enter only subinventories that track quantity on hand.
  6. If this item is under locator control, enter the locator for which you are entering counts.
  7. If you have Oracle Warehouse Management installed, and you are working with a warehouse management enabled organization.
  1. If you have Oracle Warehouse Management installed, and you are working with a warehouse management enabled organization. This is not populated automatically when the count is requested.
  2. If the item is under lot control, enter the lot for which you are entering counts.
    1. For serial control items, enter the serial number.
    2. If you specified Multiple Per Request as the Count option and Quantity and Serial Numbers as the Detail option in the Cycle Counts window, you must enter serial number information in the Cycle Count Serial Number Details window as described in the next task below. If you selected Quantity Only as the Detail option, you must use the Cycle Count Serial Number Details window only if there is a quantity mismatch.
  3. Enter the count UOM. Inventory displays the primary unit of measure for the item as the default. If the item is under dual unit of measure control, then the system also displays the secondary UOM.
    1. Enter the quantity in the quantity field. If the item is under dual unit of measure control the quantity in the secondary unit of measure is supplied automatically.
    2. Important: You may receive a warning message stating, “Zero count, no adjustment performed.” You can and should enter the quantity for reporting purposes, but no adjustment to on-hand quantity is performed. To make the adjustment enter an unscheduled count using either this window or the Count Adjustment Approvals Summary window.
  4. Save your work.

To enter serial number detail information:

1. Select the Serial button to open the Cycle Count Serial Number Details window.
If you specified Multiple Per Request as the Count option and Quantity and Serial Numbers as the Detail option in the Cycle Counts window, you must use this window to enter serial detail information. You must also use this window if you selected Quantity Only as the Detail option and there is a quantity mismatch.
This window displays the serial numbers on hand for the current count sequence from the Cycle Count Entries window, with check boxes to indicate whether the serial number is present in this count and present in the system. You can use the All Present and All Missing buttons to set the Present check boxes globally, or you can check or uncheck the Present check boxes. You also can enter additional serial numbers, but the total number of serial numbers checked present must equal the count quantity. The system also displays the cost group information for each serial number if you are in a Warehouse Management organization.
The Cancel button clears all your entries in this window and returns you to the Cycle Count Entries window.
2. When you have completed your entries, select the Done button to record your entries and return to the Cycle Count Entries window.

To enter optional count reference information:

  1. Select the Count Reference tabbed region.
  2. Enter a transaction reason for the cycle count transaction.
  3. Enter any further reference details pertaining to this count record.
  4. Enter the name of the employee who performed the cycle count, if it is different from the one entered in the Count Defaults region.
  5. Enter the date and time the cycle count was performed, if it is different from the one entered in the Count Defaults region.

To view current item adjustment information:

  1. Select the Adjustments tabbed region.
  2. View information for primary and secondary UOM, primary and secondary count quantity, primary and secondary system quantity, variance quantity, variance value, and variance percentage.

This region is available only if you turned the Display System Quantity option on when you defined your cycle count header. The System Quantity field displays the quantity on hand, and the Variance Qty field displays the proposed adjustment quantity based on the actual count quantity you enter. If you choose not to display system quantities, you enter and save your counts not knowing whether you are generating any adjustments, and if so, whether the counts are out of tolerance.

To enter optional container information:

If you have Oracle Warehouse Management installed, and you are working with a warehouse management enabled organization

  1. Select the Container Details tabbed region.
  2. View information for item, Parent LPN, Outermost LPN, Container Item, Revision, Cost Group, Lot Number, and Serial Number.
  3. Enter the Outermost LPN in which the material counted resides. This is not populated automatically when the count is requested.

To enter preapproved counts:

  1. Navigate to the Cycle Counts Summary folder window.
  2. Choose Enter Preapproved Counts from the Tools menu.

Since this functionality overrides the approval process it is usually available only to managers and employees with a certain function security.
3. In the Preapproved Count Entries window, query or enter the count information.
The counts you enter are automatically approved without regard to adjustment
tolerances or defaults set for the cycle count. Adjustments are made if applicable.

Approval Options and Tolerances

Approval Tolerances

You can set cycle counting tolerance values at three different levels:

  • Item Attributes window
  • Item Class Definition
  • Cycle Count Header

When determining if approvals are required, the system first checks the item attributes. If no tolerances are defined, the system checks the item class definition. If there are no tolerances defined on the item class definition, the system checks the cycle count header for tolerance values.
Oracle Inventory supports two types of cycle count approval tolerances. For each type, you can specify a positive and a negative limit. When a particular cycle count entry results in an adjustment that exceeds any one of these limits, you have a cycle count adjustment that exceeds approval tolerances. Based on the approval option you choose when you define your cycle count, this adjustment is either posted automatically or held for approval.

Quantity Variance Tolerance

The quantity variance tolerances a user-defined limit for the difference between the actual cycle count quantity and the system tracked on-hand quantity. You express positive and negative quantity variance tolerances as percentages of the system on-hand quantity.
You enter these percentages when you define your:

  • Cycle Count header
  • Cycle Count Classes
  • Cycle Count Items

Inventory uses any percentages you define at the cycle count item level first. If you do not have any defined for an item, it uses the tolerances defined for that item’s cycle count class. If you do not have any defined for the class, it uses the tolerances at the cycle count header level. If you have no tolerances defined for the header, Inventory assumes that there is no limit to the approval tolerance.

Adjustment Value Tolerance

The adjustment value tolerance is a user-defined limit for the total value of a cycle count adjustment. The adjustment value is calculated as:
adj value = (count qty – system on-hand qty) x current item cost
The adjustment value tolerance is expressed as positive and negative amounts in your ledger currency. An adjustment value is out of tolerance if it falls outside of these amounts.
You enter these tolerances when you define your cycle count header and cycle count classes. Inventory uses the values you define at the cycle count class level first. If you do not have any defined for an item’s class, it uses the values at the cycle count header level. If you have no tolerances defined for the header, Inventory assumes that there is no limit to the approval tolerance.

Examples of Quantity Variance and Adjustment Value Tolerances

The following table shows possible values for quantity variance and adjustment value tolerances for an item in a cycle count: The following table shows four different count scenarios for the same item and the tolerances that each different scenario violates:

Item Attributes
Value
Item Standard Cost
$10.00
Positive Quantity Variance Tolerance
5%
Negative Quantity Variance Tolerance
10%
Positive Adjustment Value Tolerance
$200
Negative Adjustment Value Tolerance
$250
System on-hand quantity
Count Quantity
Quantity Variance
Adjustment Quantity
Adjustment Value
Tolerance Exceeded
100
106
+6%
+6
+$60
Positive Quantity Variance
100
88
-12%
-12
-$120
Negative Quantity Variance
100
122
+22%
+22
+$220
Positive Quantity Variance and Positive Adjustment Value
100
73
-27%
-27
-$270
Negative Quantity Variance and Negative Adjustment Value

Hit/Miss Tolerances

The hit/miss tolerance is similar to the quantity variance tolerance in that it is also a user-defined limit for the difference between the system tracked on-hand quantity and the actual cycle count quantity. You express positive and negative hit/miss tolerances as percentages of the system on-hand quantity. A count is considered a “hit” if it is within these tolerances, and a “miss” if it is outside them. The hit/miss tolerance is used to evaluate the accuracy of your cycle counting procedures rather that the actually accuracy of inventory.
You enter hit/miss tolerance percentages when you define your cycle count header and when you define your cycle count classes. Inventory uses the percentages you define at the cycle count class level first. If you do not have any defined for an item’s class, it uses the tolerances at the cycle count header level. If you have no tolerances defined for the header, Inventory assumes that there is no limit to the hit/miss tolerance, and all variances are therefore “hits” regardless of the size.
Inventory uses these tolerances to generate the Cycle Count Hit/Miss Analysis report.

Measurement Errors

Negative and positive measurement errors are also user-defined limits for the difference between the cycle count quantity and the system tracked on-hand quantity. Inventory does not make any adjustments to an item whose cycle count quantity differs from the system tracked on-hand quantity by less than the measurement error. Because of this, measurement errors implicitly override any approval tolerances you specify.
You specify measurement errors when you define or update an item. Use measurement errors with extreme caution since they actually prevent cycle count adjustments from taking place. You would typically use this feature on an exception basis for items you cannot accurately count. For example, if you visually check the level of bolts in a bin to estimate the quantity, or you use their weight to approximate the quantity, you might want to allow for measurement errors. Therefore, if your system tracked on-hand quantity for the bolts in that bin is within an acceptable range, you do not perform a

Count Adjustments and Approvals

Once you enter and save your cycle counts, Oracle Inventory determines whether any adjustments need to be made depending on the approval options and tolerances you set

Automatic Recounts

If you turned the Automatic Recount option onwhen you defined your cycle count, Inventory automatically submits recount requests for items that are outside the limits of the approval tolerances you specify. Inventory submits recounts as many times as necessary, limited by the maximum automatic recounts you specify for the cycle count. After you reach the maximum number of recounts, Inventory holds the count for approval. Any count request with the Recount status automatically appears on the next cycle count listing.
You can also manually request recounts when you are approving adjustments. The count request for which you want a recount is also automatically included in the next cycle count listing.
Important: When generating the cycle count listing, you must include a from date far enough back to include the recount’s original count date, or it is not on the report.

Approving Cycle Counts Held for Approval

Employees with access to the Count Adjustments Approvals Summary window can query, request the recount of, or approve cycle counts pending approval. When you select the Find button, you can query all counts or only those pending approval. You can then approve adjustments, recount an item in question, reject the count or take no action until further investigation.

Cycle Count Adjustments Reserved Serial Items

If you need to perform negative adjustments for reserved serial quantities during a cycle count, the system displays a messages that pending reservations exist and the adjustment requires approval. If you make final adjustments then the system removes the corresponding reservations.

Approving Cycle Count Adjustments

Use the Count Adjustment Approvals Summary window to approve cycle count adjustments held for approval, to recount an item, or to reject the adjustment. Inventory determines which counts need approval by using the approval tolerances you enter while defining your cycle count.
You can use flexible search criteria to specify the cycle count adjustments you want to review or approve.

Selecting Information to Review or Approve

To select the cycle count for which to approve adjustments:

  1. Navigate to the Count Adjustment Approvals Summary window by selecting Approve Counts on the menu, or by choosing the Approvals button in the Cycle Counts Summary folder window.
    1. Enter the name of the cycle count for which to approve or enter counts.
    2. This information is provided if you navigate from the Cycle Counts Summary folder window.
  2. Optionally change information in the Approval Defaults region. Inventory provides default values for the Date, Approver, and the Adjustment Account that will be used when you later enter approval actions and adjustments.
  3. Query item information for the selected count:

If you navigated from the menu, select the Find button to query records. You are prompted to either query all records or query only counts pending approval.
If you have navigated from the Cycle Counts Summary folder window, you can use the Find feature on the Query menu to open the Find Approvals window, where you can query a subset of counts matching the search criteria you enter. You can search by any combination of count sequences, item, revision, subinventory, locator, or lot. You can also search for counts with a particular status including
uncounted, pending approval, recount, rejected, or completed.

Viewing Cycle Count Summary Information

You can view a variety of current item information to help determine whether to approve an adjustment. Select from the following tabbed regions:

  • Adjustment: View information for the count adjustment primary and secondary units of measure, primary and secondary variance quantity, variance value, variance percentage, and primary and secondary system quantity.
  • Item Details: View information for revision, lot, serial number, unit of measure, and primary and secondary adjustment quantity.
  • Item Location: View information for subinventory, locator, primary and secondary units of measure, primary and secondary adjustment quantity, and if you have Oracle Warehouse Management installed, cost group and parent LPN.
  • Container Details. If you have Oracle Warehouse Management installed, and you are working with a warehouse management enabled organization
  • Reason, Reference: View or update the transaction reason and reference information. You can also view the primary and secondary units of measure and primary and secondary adjustment quantity.
  • Count: View information for primary and secondary units of measure, primary and secondary count quantity, counter, and count date.
  • Count Status, Class: View information for the sequence number, count status, and cycle count class.
  • Approval: View information for date approved and approver.

Approval Actions and Adjustments

For items appearing in the Approval Actions, Adjustments region, you can approve, request a recount, or reject cycle count entries that are pending approval. You can also approve or reject any count for which a recount has already been requested. You can reject any cycle count request that has not yet been counted. Finally, you can display count history information or open the Count Adjustment Approvals window.

To approve a count check:

1. Select Approved to approve the selected count entry and post the adjustment to the transaction manager for processing.

To reject a count check:

1. Select Rejected to reject the selected count record. An adjustment is not posted. No further processing of this count entry takes place.

To request a recount check:

1. Select Recount to process a recount request for the selected count request. An adjustment is not posted.

To display count history information:

1. Select the Count History button to open the Count History window for the current item. For the current item, this window displays count and variance information for the current, prior, and first counts. If the number of recounts is more than three only the system displays only the first count, prior count, and the current count in the Count History window.

To open the Count Adjustment Approvals window:

1. Select the Open button to open the Count Adjustment Approvals window for the current line. This window is a combination block which you can use to view and enter approval and adjustment information for the current line instead of using the Count Adjustment Approvals Summary window.

Serialized Cycle Counting

Cycle counting of serial items takes place within the standard cycle counting functionality in Inventory; however, the following sections discuss additional considerations specific to serialized cycle counting.

Defining Cycle Counts

All cycle counts are defined in the Cycle Counts window.
Four options set in this window govern the handling of serial controlled items:

Count

  • Not Allowed: Serialized items are excluded from the cycle count.
  • One Per Request: A separate count request is generated for each serial number.
  • Multiple Per Request: Serial numbers for the same item/location are grouped in one count request.

Detail

  • Quantity and Serial Numbers: Serial number and quantity are required and are validated when entering counts.
  • Quantity Only: Serial number entry is required if the count quantity does not match the system quantity. Serial number entry is optional if the count quantity matches the system quantity, regardless of whether the serial numbers match. If you do not enter serial numbers, the count is marked as completed, and no adjustments are performed. If you do enter serial numbers, both quantity and serial numbers are validated when determining whether adjustments are required

Adjustment

  • Review All Adjustments: No automatic adjustments are attempted. Serialized items that require adjustment must go to an approver for review
  • Adjust if Possible: If a discrepancy exists between the count quantity and system quantity or if the entered serial numbers do not correspond to the serial numbers already in the specified location, then the system will attempt to make adjustments if the adjustment variance and value are within tolerances, as long as serial uniqueness constraints are not violated. These adjustments consist of receipts and issues of the appropriate serial numbers to and from the specified location and are applicable only to instances in which new serial numbers or shipped serial numbers are counted.

If the adjustment quantity or value for a serialized item falls outside the specified tolerances, the item is sent for recount or approval, just like a non-serialized item.

Discrepancy

  • Allow Discrepancies: When a count includes a serial number already assigned to the same item elsewhere in the system, an adjustment is created if it would be within tolerances. No adjustment is ever allowed for counts including serial numbers already assigned to another item.
  • Do not Allow Discrepancies: Adjustments are not made for items not found in the specified location.

Scheduling and Generating Count Requests

Scheduling now includes serial numbers, as does the cycle count generation. If the Count option in the cycle count definition is set to One per Request, then one count request is created for each serial number for the item in a specific location. If the Count option is set to Multiple per Request, then one count request is created for all serial numbers in the specified item locations.
For the zero count generation of serial numbers, the only way to get a meaningful zero count entry for a serial number is to specify the serial number in the Manual Schedule zero count requests are created for serial controlled items, but they will not have a serial number tied to them.

Entering Cycle Counts

How you enter cycle counts depends on the Count and Detail option settings in the count definition. When the Count option is set to One Per Request and the Detail option is set to Quantity Only, the count request itself contains the serial number, and you enter a count quantity of either present or missing. When the Count option is set to Multiple Per Request and the Detail option is set to Quantity and Serial Numbers, the Serial Number field in the count request is disabled, and you must use the Cycle Count Serial Detail window to specify whether the serial number is present. If you selected Quantity Only as the Detail option, you must use the Cycle Count Serial Number Details window if there is a quantity mismatch.
On-hand quantities for serial numbers are retrieved when count requests are queried. Thus, it is possible to have count requests for serial numbers with an on-hand quantity of zero. If you mark the serial number as present, then you will need to make an adjustment.

Approving and Adjusting Counts

The approval process for serialized items differs from that for non-serialized items. Serial numbers that are misplaced (at a different location or for a different item) cannot be adjusted.
Counts in which there is a misplaced serial number are sent for approval, regardless of whether the adjustment variances fall within tolerance if discrepancies are allowed. However, if a count entry contains a serial number found in another location, the count request cannot be approved until the discrepancy is corrected. You can make the correction manually in the Transaction window, or you can cycle count the other location (performing an issue, adjustment transaction) and then recount the first location.
For serial numbers that do not appear in the cycle count request but are entered by the counter, adjustment transactions are considered receipts. These receipt transactions are allowed for the serial states where the unit is defined but never used and where the unit has been issued out of stores. For serial numbers that appear in the count request but are not marked as present by the counter, adjustment transactions are considered issues. These issue transactions are allowed for the serial state where the unit is received into stores. Count requests whose serial adjustments fall into these two categories may have adjustment transactions performed against them and may complete normally.

Purging Cycle Count Information

To purge cycle count information:

  1. Navigate to the Cycle Counts Summary folder window.
  2. Select a cycle count.
  3. Choose Purge Cycle Count from the Tools menu. The Purge Cycle Count Parameters window appears.
  4. Indicate whether this is a full cycle count purge including the header, cycle count items, schedule requests, and count requests, or this is a historical cycle count purge of schedule requests and count requests on or before the historical purge date.
  5. Enter the date for the purge. Oracle Inventory deletes schedule requests and count requests on or before this date.
  6. Choose OK to submit the request to the concurrent manager.

Cycle Count Open Interface

You can import cycle count entries from external systems into Oracle Inventory using the Cycle Count Entries Open Interface. You can also export cycle count requests with this interface to external systems.
To export cycle count entries:
1. Navigate to the Export Cycle Count Entries window.

  1. Select a cycle count header.
    1. Choose Find.
    2. The window displays all cycle count entries that belong to the selected cycle count header.
  2. Select the records you want to export or choose Select All from the Tools menu to select all the records.
  3. Choose Export to export cycle count entries to the open interface.

To unexport a cycle count entry:

  1. Select the record you want to unexport.
  2. Choose Unexport.

To inquire about or update cycle count entries:

1. Navigate to the Inquiry/Update Cycle Count Entries Open Interface window. The Find Interface Cycle Count Entries window appears.
  1. Enter search criteria to query cycle count entries for which you want to view or update cycle count entry information. Choose Find to start the search and display the information in the Inquiry/Update Cycle Count Entries Open Interface window.
  2. In the Processing tabbed region, view or update the following information: Item: The item number. Action: Choose one of the following options: Validate: Validate cycle count header, sequence, and org ID. Choose this option only

if you use the open interface API. Create: Create an unscheduled cycle count entry. Simulate: Simulate the open interface process without committing the entry. This
option displays errors found during processing. Process: Process the entry. Status: The cycle count status. Incomplete: The open interface process is incomplete. Process completed: The open interface process is complete. Simulated: The entry was processed but not committed. Group ID: The identification number for entries submitted in batch mode. Interface ID: The interface table identification number. Header ID: The cycle count header identification number.
Cycle Count Header: The name of the cycle count header. Entry ID: The cycle count entry identification number. Process Mode: Choose one of the following options:Online: Process open interface online. Background: Process open interface in the background. Request ID: The concurrent request identification number generated during
background processing.
Process Status: Ready: The entry is ready for processing. Not Ready: The entry is not ready for processing. Note: This field is not updatable.
Valid Status: Yes: The entry is valid. No: The entry has errors and is not valid. Note: This field is not updatable.
Lock Status: Yes: The entry is locked by another user. No: The entry is not locked by another user. Note: This field is not updatable.

  1. In the Count tabbed region, view or update the following information: Sequence: The cycle count sequence. This field is not updatable. Count Qty: The count quantity in the primary unit of measure. UOM: The primary unit of measure Secondary Count Qty: The count quantity in the secondary unit of measure. Secondary UOM: The secondary unit of measure. Count Date: The cycle count date. Counter: The name of the employee who performed the cycle count. Reference: Reference information about the cycle count. Reason: The transaction reason. Interface ID: The interface table ID number. This field is not updatable.
  2. In the Item Stocking tabbed region, view the following information: Rev: The revision number (if the item is under revision control).

Subinventory: The subinventory. Locator: The locator (if the item is under locator control).Lot Number: The lot number (if the item is under lot control).Serial Number: The serial number (if the item is under serial control).Adjustment Account: The general ledger account charged for the cycle count. Interface ID: The interface table identification number. Cost Group: The cost group associated with the item. Cost group information is
available only if you are in a Warehouse Management enabled organization.
Parent LPN: The LPN that contains the items to count. LPN information is available only if you are in a Warehouse Management enabled organization. Outermost LPN: The outermost LPN if the LPNs are nested. LPN information is
available only if you are in a Warehouse Management enabled organization.
6. Save your work.

To delete cycle count entries:

  1. Select the cycle count entries you want to delete.
  2. Choose Delete.

To submit cycle count entries to the open interface:

  1. Select the cycle count entries you want to submit to the open interface.
  2. Choose Submit.

To view errors for an entry:

  1. Select a cycle count entry.
  2. Choose Errors. The Cycle Count Entries Interface Errors window lists the error date and an explanation of the error.

To open cycle count entry header information:

  1. Select a cycle count entry.
  2. Choose Open. This window shows information about the individual item.

Cycle Counting Reports

You can use a number of reports to help you during the process of cycle counting and to analyze and report the results of cycle count transactions. You can submit a concurrent request for these reports from the Tools menu in most of the cycle counting windows as well as from the Submit Requests window.

Cycle Count Schedule Requests Report

This report shows all schedule requests for a specified time period. It includes both manually and automatically scheduled items.

Cycle Count Listing

This report lists all of the items currently due for cycle counting, including their revision, lot number, subinventory and locator information. You can use this report as the document you give to the employees performing the cycle counts. Since the report leaves a blank line for the counter’s name, the count date, and the actual count quantity, the counter can use this listing to write down and report his cycle count results.

Cycle Count Open Requests Listing

This report shows count requests where no counts have been entered, or count entries where you have requested a recount. You can optionally report on late counts, where no counts have been entered and the due date for the count entry is before the date of the

Cycle Count Unscheduled Items Report

This report shows those items that are currently not scheduled to be counted and were last scheduled a period of time in the past that is longer than expected, as dictated by the count frequency of the class to which the item belongs. For example, if item XYZ belongs to class A, and you count class A 52 times a year, you would expect item XYZ to be scheduled once a week. If item XYZ was last scheduled two weeks before the date you run the Cycle Count Unscheduled Items Report, it appears on the report.
You primarily use this report as an auditing tool. If you correctly set up your scheduling and counting, and are always current in your count, Oracle Inventory should not find any unscheduled items to report. However, if you do not run the auto scheduler as frequently as it needs to run, or if concurrent manager problems prevent its execution, you may fall behind in your count schedules.

Cycle Counts Pending Approval Report

This report shows those counts that were entered and are currently pending approval. The supervisor with the authority to approve cycle count adjustments would typically run this report regularly to monitor the approval queue.

Cycle Count Entries and Adjustments Report

This report shows all cycle count entries for a specified time period. It analyzes the number of cycle count transactions you make against an item, and the number of units you actually adjust. The report also calculates the value, in your ledger currency, of the adjustments to inventory.

Cycle Count Hit/Miss Analysis

This report shows, for each cycle count class, the total number of count entries and the number of counts outside the limits of the user-specified hit/miss tolerances. The report also calculates the overall accuracy percentages broken down by cycle count class and subinventory. This report is based on the first count only, not recounts.

Import Cycle Count Entries from Open Interface

This process allows you to import cycle count entries open interface records into the database.
Purge Cycle Count Entries Open Interface Data
This process allows you to purge all cycle count entries from the open interface.
Print Cycle Count Entries Open Interface Data
This process allows you to print cycle count entries open interface data.