Part #: E21884-04, July 2013
This document provides delta information from Oracle E-Business Suite Release 12.1.3 to Value Chain Planning Cumulative Patch 12.1.3.9, Patch 16974659.
The information included in this document assumes that you have already installed Oracle Inventory Optimization Release 12.1.3, according to the relevant instructions in the following documents:
Note: This document - especially Section 5, Known Issues - may be updated after initial release. Any changes are listed in Section 6, Change Record. If you print this document, periodically check to ensure you have the most recent version.
The latest version of this document is available from the following locations:
In Release 12.1.3, Oracle Inventory Optimization has added or changed the following features since its last release. For a complete list of new features within Oracle E-Business Suite Release 12.1.3, refer to Document 561580.1, Release Content Document.
Feature Name | Description |
---|---|
Enhanced Budget Constraints (Release 12.1.3) |
Prior to this release, IO did not have the ability to ensure integer valued safety stock solutions within input budget constraints. A new heuristic ensures integer valued safety stocks while respecting input budget constraints. This new heuristic is enabled by setting the profile option "MSR: Budget Heuristic" to Yes. The default value is No. A few points about the new heuristic:
|
Oracle Inventory Optimization and Asset Intensive Planning (Release 12.1.3.7) |
The purpose of this functionality is to enable Inventory Optimization to compute safety stock for consumables and rebuildables that will be required for maintenance in an asset intensive industry. To support asset intensive planning, Inventory Optimization was modified to perform the following:
|
Warehouse Capacity Constraints |
Oracle Inventory Optimization has added a new IO constraint set to implement warehouse capacity. These warehouse constraints are considered as hard constraints when combined with budget or capacity constraints. They are considered as soft constraints when combined with service level constraints. These constraints are defined either at the organization level or at the category org. level, depending on the value you specify for the profile option MSO: Warehouse Capacity Granularity. |
Accounting for Cycle Inventory in Safety Stock Calculation |
You can achieve your target service levels with lower safety stock quantities when you have cycle inventories. This implies that the actual service levels could be higher in the early time buckets of a cycle than the service level in the later time buckets. Consequently to achieve a target average service level during the cycle a lower safety stock inventory could be required in a cycle inventory system. |
Enforcing Group Service Level Targets |
Oracle Inventory Optimization (IO) currently allows specifying target service levels at multiple levels. It picks the most granular target applicable for an item-organization and interprets that as the target for those item-organizations. Customers often track service levels at more aggregate levels. For example, where there are several member variants within a particular product category, they may want to track the service level for the product category as a whole rather than for each item variant. In release 12.1.3.9, Oracle Inventory Optimization has been enhanced to support enforcing service levels at a Group (Category or Category-Demand Class) level. When a planner specifies a service level target at a Group level, the planner can also specify whether the target should be applied at the group level, or for the individual item-organizations within the group. If the planner chooses the former, IO will ensure that service levels are met at the group level, and individual item-organizations below it may exceed or fall short of the target service level. If the planner chooses the latter, each item-organization will be planned to attain the target service level. This feature applies only to Enforce Service Level plans. |
Using Negative Binomial Distribution in Inventory Optimization |
In release 12.1.3.9, you can instruct Inventory Optimization to use the Negative Binomial distribution as the forecast error distribution for items with high variability intermittent demands when calculating safety stock levels. This is achieved by using the following new profile option, MSR: Variance to Mean Threshold for Use of Negative Binomial Distribution. |
This section provides information on the following topics:
The consolidated documentation patch for Oracle E-Business Suite Release 12.1.3 is Patch 9239095. For the product families that are included in Release 12.1.3, the consolidated documentation patches are listed below:
Patch | Product Family |
---|---|
Patch 9400185 | Applications Technology (ATG_PF) |
Patch 9403775 | Customer Relationship Management (CC_PF) |
Patch 9403767 | Financials (FIN_PF) |
Patch 9401789 | Human Resources (HR_PF) |
Patch 9403759 | Procurement (PRC_PF) |
Patch 9403770 | Projects (PJ_PF) |
Patch 9403704 | Supply Chain Management (SCM_PF) |
Patch 9403751 | Value Chain Planning (SCP_PF) |
We strongly recommend the installation of these patches.
In addition, the following Oracle Inventory Optimization documentation is available as part of the Online Documentation Library on My Oracle Support (formerly MetaLink) and Oracle Technology Network for this release:
Documentation patches and Adobe Acrobat PDFs are cumulative; they include updated documentation for all Oracle Inventory Optimization 12.1.3 changes.
The following technical documentation is available:
The EBS Data Model Comparison Report lists the database object definition changes between two Oracle E-Business Suite releases to help users to preview the database object definition changes before upgrading their instances from one release to another and understand the impact of the database object changes that may affect the customization or business flows.
For more information about the EBS Data Model Comparison report, see Document 1290886.1, EBS Data Model Comparison Report Overview.
The EBS ATG Seed Data Comparison Report lists the differences between two Oracle E-Business Suite releases by documenting the seed data changes delivered by the product data loader files (.ldt extension) based on the ATG loader control files (.lct extension). This report enables advanced users to review changes prior to an upgrade.
For more information about the EBS ATG Seed Data Comparison Report, see Document 1327399.1, EBS ATG Seed Data Comparison Report.
The EBS File Comparison Report provides a comprehensive comparison of file system artifacts between different Oracle E-Business Suite releases for important file types. As part of Oracle E-Business Suite upgrade planning, this report helps customers to get a clear idea of what is different in a new release (additions, removals and modifications for Oracle E-Business Suite delivered files). The report also covers some special artifacts that span the file system and database (for example, Oracle E-Business Suite delivered Oracle Application Framework (OAF) personalizations, Oracle Application Framework (OAF) based pages, Oracle Business Intelligence Publisher reports and so on).
For more information about the EBS File Comparison Report, see Document 1446430.1, EBS File Comparison Report Overview.
The Oracle Integration Repository is a compilation of information about the service endpoints displayed by the Oracle E-Business Suite of applications. It provides a complete catalog of Oracle E-Business Suite's business service interfaces. The tool enables users to easily discover and deploy the appropriate business service interface for integration with any system, application, or business partner.
The Oracle Integration Repository is shipped as part of Oracle E-Business Suite. As your instance is patched, the repository is automatically updated with content appropriate for the precise revisions of interfaces in your environment.
You can navigate to the Oracle Integration Repository through Oracle E-Business Suite Integrated SOA Gateway.
Refer to Document 561580.1, Release Content Document for information about the features and enhancements for Oracle E-Business Suite Release 12.1.3.
There are no relevant white papers for this product in this release.
In Release 12.1.3, Oracle Inventory Optimization has added or changed the following features since its last release. For a complete list of new features within Oracle E-Business Suite Release 12.1.3, refer to the Document 561580.1, Release Content Document.
Use this section to access the following delta information for each feature:
This release provides the following new features and enhancements:
Description |
Prior to this release, IO did not have the ability to ensure integer valued safety stock solutions within input budget constraints. A new heuristic ensures integer valued safety stocks while respecting input budget constraints. This new heuristic is enabled by setting the profile option "MSR: Budget Heuristic" to Yes. Tthe default value is No. A few points about the new heuristic:
|
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
New, Changed, Obsolete Components |
This section lists the components that were added, changed, or made obsolete for this feature in Oracle Inventory Optimization in Release 12.1.3. These components may include the following: forms, windows, reports, C programs, SQL*Loader programs, workflows, alerts, tables, or APIs. New Windows or PagesThere are no new windows or pages that are associated with this feature. Changed Windows or PagesThere are no changed windows or pages that are associated with this feature. Obsolete Windows or PagesThere are no obsolete windows or pages that are associated with this feature. New ReportsThere are no new reports that are associated with this feature. Changed ReportsThere are no changed reports that are associated with this feature. Obsolete ReportsThere are no obsolete reports that are associated with this feature. New WorkflowsThere are no new workflows that are associated with this feature. Changed WorkflowsThere are no changed workflows that are associated with this feature. Obsolete WorkflowsThere are no obsolete workflows that are associated with this feature. New AlertsThere are no new alerts that are associated with this feature. Changed AlertsThere are no changed alerts that are associated with this feature. Obsolete AlertsThere are no obsolete alerts that are associated with this feature. New Public APIsThere are no new public APIs that are associated with this feature. Changed Public APIsThere are no changed public APIs that are associated with this feature. Obsolete Public APIsThere are no obsolete public APIs that are associated with this feature. New ProgramsThere are no new programs that are associated with this feature. Changed ProgramsThis table lists the changed programs.
Obsolete ProgramsThere are no obsolete programs that are associated with this feature. New TablesThere are no new tables that are associated with this feature. Changed TablesThere are no changed tables that are associated with this feature. Obsolete TablesThere are no obsolete tables that are associated with this feature. New ViewsThere are no new views that are associated with this feature. Changed ViewsThere are no changed views that are associated with this feature. Obsolete ViewsThere are no obsolete views that are associated with this feature. New Business Intelligence Publisher ComponentsThere are no new Business Intelligence Publisher Components that are associated with this feature. Changed Business Intelligence Publisher ComponentsThere are no changed Business Intelligence Publisher Components that are associated with this feature. Obsolete Business Intelligence Publisher ComponentsThere are no obsolete Business Intelligence Publisher Components that are associated with this feature. New SQL Loader FilesThere are no new SQL loader files that are associated with this feature. Changed SQL Loader FilesThere are no changed SQL loader files that are associated with this feature. Obsolete SQL Loader FilesThere are no obsolete SQL loader files that are associated with this feature. New FlexfieldsThere are no new flexfields that are associated with this feature. Changed FlexfieldsThere are no changed flexfields that are associated with this feature. Obsolete FlexfieldsThere are no obsolete flexfields that are associated with this feature. New Profile OptionsThis table lists the new profile options.
Changed Profile OptionsThere are no changed profile options that are associated with this feature. Obsolete Profile OptionsThere are no obsolete profile options that are associated with this feature. |
||||||||||
Implementation Considerations |
New and Changed Setup StepsThere are no new or changed setup steps for this feature. Upgrade ConsiderationsThere are no upgrade considerations for this feature. SizingThere are no sizing considerations for this feature. Table Space ConsiderationsThere are no table space considerations for this feature. Performance ConsiderationsThere are no performance considerations for this feature. XMLDB UsageThere are no XMLDB usages for this feature. Load BalancingThere is no load balancing information for this feature. New Bulk InterfacesThere are no new bulk interfaces for this feature. |
||||||||||
Customizations and Extensions |
Customizations and extensions are not possible for this feature. |
||||||||||
Minimum Level Requirements |
There are no minimum level requirements for this feature. |
||||||||||
Technology Stack Incompatibilities |
There are no technology stack incompatibilities for this feature. |
||||||||||
Technical Architecture Considerations |
There are no technology architecture considerations for this feature. |
||||||||||
Troubleshooting Tips |
Make sure you check the profile option is correctly defined:
|
Return to New and Changed Features
Description |
The purpose of this functionality is to enable Inventory Optimization to compute safety stock for consumables and rebuildables that will be required for maintenance in an asset intensive industry. To support asset intensive planning, Inventory Optimization was modified to perform the following:
For more information, refer to Oracle Inventory Optimization User's Guide Supplement. |
||||||
---|---|---|---|---|---|---|---|
New, Changed, Obsolete Components |
This section lists the components that were added, changed, or made obsolete for this feature in Oracle Inventory Optimization in Oracle E-Business Suite Release 12.1.3.7. These components may include the following: forms, windows, reports, C programs, SQL*Loader programs, workflows, alerts, tables, or APIs. Any new, changed, or obsolete components of any of these types are listed below. Changed Windows or PagesThis table lists the changed windows and pages.
|
||||||
Implementation Considerations |
New and Changed Setup StepsThere are no new or changed setup steps for this feature. Upgrade ConsiderationsThere are no upgrade considerations for this feature. SizingTablespace ConsiderationsThere are no tablespace considerations for this feature. Performance ConsiderationsXMLDB UsageThere are no XMLDB usages for this feature. Load BalancingThere is no load balancing information for this feature. New Bulk InterfacesThere are no new bulk interfaces for this feature. |
||||||
Customizations and Extensions |
Customizations and extensions are not possible for this feature. |
||||||
Minimum Level Requirements |
There are no minimum level requirements for this feature. |
||||||
Technology Stack Incompatibilities |
There are no technology stack incompatibilities for this feature. |
||||||
Technical Architecture Considerations |
There are no technology architecture considerations for this feature. |
||||||
Troubleshooting Tips |
There are no troubleshooting tips for this feature. |
Return to New and Changed Features
Description |
Oracle Inventory Optimization has added a new IO constraint set to implement warehouse capacity. These warehouse constraints are considered as hard constraints when combined with budget or capacity constraints. They are considered as soft constraints when combined with service level constraints. These constraints are defined either at the organization level or at the category org. level, depending on the value you specify for the profile option MSO: Warehouse Capacity Granularity. For more information, refer to Oracle Inventory Optimization User's Guide Supplement. |
||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
New, Changed, Obsolete Components |
This section lists the components that were added, changed, or made obsolete for this feature in Oracle Inventory Optimization in Release 12.1.3. These components may include the following: forms, windows, reports, C programs, SQL*Loader programs, workflows, alerts, tables, or APIs. New Windows or PagesThis table lists the new windows and pages.
New Profile OptionsThis table lists the new profile options.
Changed ProgramsThis table lists the changed programs.
|
||||||||||||||||
Implementation Considerations |
New and Changed Setup StepsPerform the following when using the Warehouse Capacity Constraints feature:
Upgrade ConsiderationsYou can use instruct the system to constrain the IO plan with the total warehouse capacity or the storage capacities of different storage types within the warehouse. This attribute is used as the time horizon for calculating the Average Demand. Average Daily Demand for a Planning Bucket = Sum of item's independent and dependent demands from the start of the planning bucket to the Safety Stock Days working days after the start of the planning bucket, divided by Safety Stock Days. To model the warehouse capacity granularity you can use a new profile option MSR: Warehouse Capacity Granularity. Valid values are:
For more information, refer to Setting Up Warehouse Constraints in the Oracle Inventory Optimization User's Guide Supplement. SizingThere are no sizing considerations for this feature. Table Space ConsiderationsThere are no table space considerations for this feature. Performance ConsiderationsThere are no performance considerations for this feature. XMLDB UsageThere are no XMLDB usages for this feature. Load BalancingThere is no load balancing information for this feature. New Bulk InterfacesThere are no new bulk interfaces for this feature. |
||||||||||||||||
Customizations and Extensions |
Customizations and extensions are not possible for this feature. |
||||||||||||||||
Minimum Level Requirements |
There are no minimum level requirements for this feature. |
||||||||||||||||
Technology Stack Incompatibilities |
There are no technology stack incompatibilities for this feature. |
||||||||||||||||
Technical Architecture Considerations |
There are no technology architecture considerations for this feature. |
||||||||||||||||
Troubleshooting Tips |
There are no troubleshooting tips for this feature. |
Return to New and Changed Features
Description |
You can achieve your target service levels with lower safety stock quantities when you have cycle inventories. This implies that the actual service levels could be higher in the early time buckets of a cycle than the service level in the later time buckets. Consequently to achieve a target average service level during the cycle a lower safety stock inventory could be required in a cycle inventory system. For more information, refer to Oracle Inventory Optimization User's Guide Supplement. |
||||||
---|---|---|---|---|---|---|---|
New, Changed, Obsolete Components |
This section lists the components that were added, changed, or made obsolete for this feature in Oracle Inventory Optimization in Release 12.1.3. These components may include the following: forms, windows, reports, C programs, SQL*Loader programs, workflows, alerts, tables, or APIs. New Profile OptionsThis table lists the new profile options.
|
||||||
Implementation Considerations |
New and Changed Setup StepsThere are no new or changed setup steps for this feature. Upgrade ConsiderationsTo enable the ability to calculate safety stock with respect to cycle stock you need to set the profile option MSR: Include Cycle Inventory in Safety Stock Calculations in your personal profile values. Valid values are:.
SizingThere are no sizing considerations for this feature. Table Space ConsiderationsThere are no table space considerations for this feature. Performance ConsiderationsThere are no performance considerations for this feature. XMLDB UsageThere are no XMLDB usages for this feature. Load BalancingThere is no load balancing information for this feature. New Bulk InterfacesThere are no new bulk interfaces for this feature. |
||||||
Customizations and Extensions |
Customizations and extensions are not possible for this feature. |
||||||
Minimum Level Requirements |
There are no minimum level requirements for this feature. |
||||||
Technology Stack Incompatibilities |
There are no technology stack incompatibilities for this feature. |
||||||
Technical Architecture Considerations |
There are no technology architecture considerations for this feature. |
||||||
Troubleshooting Tips |
There are no troubleshooting tips for this feature. |
Return to New and Changed Features
Description |
Oracle Inventory Optimization (IO) currently allows specifying target service levels at multiple levels. It picks the most granular target applicable for an item-organization and interprets that as the target for those item-organizations. Customers often track service levels at more aggregate levels. For example, where there are several member variants within a particular product category, they may want to track the service level for the product category as a whole rather than for each item variant. Oracle Inventory Optimization has therefore been enhanced to support enforcing service levels at a Group (Category or Category-Demand Class) level. When a planner specifies a service level target at a Group level, the planner can also specify whether the target should be applied at the group level, or for the individual item-organizations within the group. If the planner chooses the former, IO will ensure that service levels are met at the group level, and individual item-organizations below it may exceed or fall short of the target service level. If the planner chooses the latter, each item-organization will be planned to attain the target service level. This feature applies only to Enforce Service Level plans. |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
New, Changed, Obsolete Components |
This section lists the components that were added, changed, or made obsolete for this feature in Oracle Inventory Optimization in Release 12.1.3. These components may include the following: forms, windows, reports, C programs, SQL*Loader programs, workflows, alerts, tables, or APIs. New Windows or PagesThere are no new windows or pages that are associated with this feature. Changed Windows or PagesThis table lists the changed windows and pages.
Obsolete Windows or PagesThere are no obsolete windows or pages that are associated with this feature. New ReportsThere are no new reports that are associated with this feature. Changed ReportsThere are no changed reports that are associated with this feature. Obsolete ReportsThere are no obsolete reports that are associated with this feature. New WorkflowsThere are no new workflows that are associated with this feature. Changed WorkflowsThere are no changed workflows that are associated with this feature. Obsolete WorkflowsThere are no obsolete workflows that are associated with this feature. New AlertsThere are no new alerts that are associated with this feature. Changed AlertsThere are no changed alerts that are associated with this feature. Obsolete AlertsThere are no obsolete alerts that are associated with this feature. New Public APIsThere are no new public APIs that are associated with this feature. Changed Public APIsThere are no changed public APIs that are associated with this feature. Obsolete Public APIsThere are no obsolete public APIs that are associated with this feature. New ProgramsThere are no new programs that are associated with this feature. Changed ProgramsThis table lists the changed programs.
Obsolete ProgramsThere are no obsolete programs that are associated with this feature. New TablesThere are no new tables that are associated with this feature. Changed TablesThere are no changed tables that are associated with this feature. Obsolete TablesThere are no obsolete tables that are associated with this feature. New ViewsThere are no new views that are associated with this feature. Changed ViewsThere are no changed views that are associated with this feature. Obsolete ViewsThere are no obsolete views that are associated with this feature. New Business Intelligence Publisher ComponentsThere are no new Business Intelligence Publisher Components that are associated with this feature. Changed Business Intelligence Publisher ComponentsThere are no changed Business Intelligence Publisher Components that are associated with this feature. Obsolete Business Intelligence Publisher ComponentsThere are no obsolete Business Intelligence Publisher Components that are associated with this feature. New SQL Loader FilesThere are no new SQL loader files that are associated with this feature. Changed SQL Loader FilesThere are no changed SQL loader files that are associated with this feature. Obsolete SQL Loader FilesThere are no obsolete SQL loader files that are associated with this feature. New FlexfieldsThere are no new flexfields that are associated with this feature. Changed FlexfieldsThere are no changed flexfields that are associated with this feature. Obsolete FlexfieldsThere are no obsolete flexfields that are associated with this feature. New Profile OptionsThere are no new profile options associated with this feature. Changed Profile OptionsThere are no changed profile options that are associated with this feature. Obsolete Profile OptionsThere are no obsolete profile options that are associated with this feature. |
||||||||||
Implementation Considerations |
New and Changed Setup StepsCheck the "Enforce at Aggregate Level" option if service level targets are to be met at a Category / Category-Demand Class level instead of individual item-org level. Upgrade ConsiderationsIf you are upgrading to 12.1.3.9 and do not wish to enforce the service levels at an aggregate level, make sure that the Plan Option "Enforce at Aggregate Level" is not selected. SizingThere are no sizing considerations for this feature. Table Space ConsiderationsThere are no table space considerations for this feature. Performance ConsiderationsThere are no performance considerations for this feature. XMLDB UsageThere are no XMLDB usages for this feature. Load BalancingThere is no load balancing information for this feature. New Bulk InterfacesThere are no new bulk interfaces for this feature. |
||||||||||
Customizations and Extensions |
Customizations and extensions are not possible for this feature. |
||||||||||
Minimum Level Requirements |
There are no minimum level requirements for this feature. |
||||||||||
Technology Stack Incompatibilities |
There are no technology stack incompatibilities for this feature. |
||||||||||
Technical Architecture Considerations |
There are no technology architecture considerations for this feature. |
||||||||||
Troubleshooting Tips |
Issue: Items have Projected Service Levels below target. Probable Cause: This is possible if service levels are enforced at aggregate level. In this case, service levels are achieved at the group level, but individual items under the group may be above or below target. Solution: None. Issue: Aggregate Service level target not met. Probable Cause: Items under the group may have different targets; in which case the more granular targets are met. Solution: If group service level targets are to be enforced, do not specify service level targets for items under it unless really required. |
Return to New and Changed Features
Description |
In release 12.1.3.9, you can instruct Inventory Optimization to use the Negative Binomial distribution as the forecast error distribution for items with high variability intermittent demands when calculating safety stock levels. This is achieved by using the a new profile option, MSR: Variance to Mean Threshold for Use of Negative Binomial Distribution. |
||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
New, Changed, Obsolete Components |
This section lists the components that were added, changed, or made obsolete for this feature in Oracle Inventory Optimization in Release 12.1.3. These components may include the following: forms, windows, reports, C programs, SQL*Loader programs, workflows, alerts, tables, or APIs. New Windows or PagesThere are no new windows or pages that are associated with this feature. Changed Windows or PagesThere are no changed windows or pages that are associated with this feature. Obsolete Windows or PagesThere are no obsolete windows or pages that are associated with this feature. New ReportsThere are no new reports that are associated with this feature. Changed ReportsThere are no changed reports that are associated with this feature. Obsolete ReportsThere are no obsolete reports that are associated with this feature. New WorkflowsThere are no new workflows that are associated with this feature. Changed WorkflowsThere are no changed workflows that are associated with this feature. Obsolete WorkflowsThere are no obsolete workflows that are associated with this feature. New AlertsThere are no new alerts that are associated with this feature. Changed AlertsThere are no changed alerts that are associated with this feature. Obsolete AlertsThere are no obsolete alerts that are associated with this feature. New Public APIsThere are no new public APIs that are associated with this feature. Changed Public APIsThere are no changed public APIs that are associated with this feature. Obsolete Public APIsThere are no obsolete public APIs that are associated with this feature. New ProgramsThere are no new programs that are associated with this feature. Changed ProgramsThis table lists the changed programs.
Obsolete ProgramsThere are no obsolete programs that are associated with this feature. New TablesThere are no new tables that are associated with this feature. Changed TablesThere are no changed tables that are associated with this feature. Obsolete TablesThere are no obsolete tables that are associated with this feature. New ViewsThere are no new views that are associated with this feature. Changed ViewsThere are no changed views that are associated with this feature. Obsolete ViewsThere are no obsolete views that are associated with this feature. New Business Intelligence Publisher ComponentsThere are no new Business Intelligence Publisher Components that are associated with this feature. Changed Business Intelligence Publisher ComponentsThere are no changed Business Intelligence Publisher Components that are associated with this feature. Obsolete Business Intelligence Publisher ComponentsThere are no obsolete Business Intelligence Publisher Components that are associated with this feature. New SQL Loader FilesThere are no new SQL loader files that are associated with this feature. Changed SQL Loader FilesThere are no changed SQL loader files that are associated with this feature. Obsolete SQL Loader FilesThere are no obsolete SQL loader files that are associated with this feature. New FlexfieldsThere are no new flexfields that are associated with this feature. Changed FlexfieldsThere are no changed flexfields that are associated with this feature. Obsolete FlexfieldsThere are no obsolete flexfields that are associated with this feature. New Profile OptionsThis table lists the new profile options.
Changed Profile OptionsThere are no changed profile options that are associated with this feature. Obsolete Profile OptionsThere are no obsolete profile options that are associated with this feature. |
||||||||||
Implementation Considerations |
New and Changed Setup StepsThe profile option "MSR: Variance to Mean Threshold for Use of Negative Binomial Distribution" can (optionally) be set so that IO can use either a Poisson distribution or a Negative Binomial distribution as the forecast error distribution, depending on the profile value. Upgrade ConsiderationsIf you are upgrading to Inventory Optimization 12.1.3.9, you can use Negative Binomial distribution as the forecast error distribution while calculating safety stocks for items with intermittent demand and high variability. SizingThere are no sizing considerations for this feature. Table Space ConsiderationsThere are no table space considerations for this feature. Performance ConsiderationsThere are no performance considerations for this feature. XMLDB UsageThere are no XMLDB usages for this feature. Load BalancingThere is no load balancing information for this feature. New Bulk InterfacesThere are no new bulk interfaces for this feature. |
||||||||||
Customizations and Extensions |
Customizations and extensions are not possible for this feature. |
||||||||||
Minimum Level Requirements |
There are no minimum level requirements for this feature. |
||||||||||
Technology Stack Incompatibilities |
There are no technology stack incompatibilities for this feature. |
||||||||||
Technical Architecture Considerations |
There are no technology architecture considerations for this feature. |
||||||||||
Troubleshooting Tips |
Issue: Safety Stock values calculated in IO appear wrong. Probable Cause: Wrong safety stock calculation method chosen due to wrong settings. Solution: Verify that the profile "MSR: Variance to Mean Threshold for Use of Negative Binomial Distribution" and the item attribute "Intermittent Demand" have been set correctly. |
Return to New and Changed Features
Oracle Inventory Optimization utilizes Oracle E-Business Suite Diagnostics, a tool to help standardize data gathering and troubleshooting. This tool (product code IZU) is delivered within the maintenance pack, and consists of two components:
Note: If no role is assigned using RBAC, and the "Application Diagnostics" responsibility is directly assigned to users (for example, via the System Administrator Users form), then all Diagnostics tabs open for those users. However, in the Diagnose tab, tests do not appear under any application except HTML platform, and users can neither run tests nor configure inputs for any other application.
Complete RBAC setup details for diagnostics are available through My Oracle Support Document 167000.1.
It is highly recommended that following the successful installation of Oracle E-Business Suite Release 12.1.3 for Oracle Inventory Optimization, the following actions are taken:
After installation, review Document 783319.1, the diagnostic catalog, to identify other helpful tests that you can use for maintaining a healthy environment.
For questions about Oracle E-Business Suite Diagnostics or any issues using this tool, consult Document 235307.1, FAQ, in My Oracle Support for the latest answers and discussion.
E-Business Suite Diagnostics Quick Reference
My Oracle Support Document | Title | Purpose |
---|---|---|
Document 167000.1 | Installation Guide |
Use this note to download the latest Diagnostics patch. Follow the installation instructions to eliminate common installation and usage problems. A link to how to set up RBAC security for Oracle E-Business Suite Diagnostics is included. |
Document 235307.1 | FAQ |
Do you have a problem installing Diagnostics? Do you have a question about how Diagnostics works and what it can do for you? This Note is a great first-line resource to getting the information that you need. |
Document 342459.1 | Overview | The Overview highlights Oracle E-Business Suite Diagnostics, and what this tool can do for you and your E-Business Suite applications. |
Document 421245.1 | Overview | This Note lists all tests that are available for Release 12. |
Document 368109.1 | Pre-production test sets |
Tests that are grouped together (known as test sets) by a product family, designed to aid in verifying that all included applications are set up correctly. Designed to detect missing or incorrect setup and prevent corruption before implementation or usage of applications. |
Document 232116.1 | Training | Viewlets and presentations, explaining the various aspects of Oracle E-Business Suite Diagnostics. |
My Oracle Support Diagnosibility Community | Diagnosibility link | This is an open forum to discuss Oracle E-Business Suite Diagnostics, and is monitored by the Oracle E-Business Suite Diagnostics development team. |
Oracle Inventory Optimization uses the common diagnostics features in Oracle E-Business Suite. This enables users and system administrators to use a centralized set of options to control logging level, as well as output destination. To run diagnostics, use the following profile options:
Setting the log level to Statement produces detail logging of code execution. To reduce the size of the output and make it more manageable, you can use msr% as a module to restrict messages to those coming from Oracle Inventory Optimization code.
The preceding profile options can be turned on at the user, function, responsibility, or site level. It is preferable, however, to set profiles at the user level to restrict the overhead they add to the system. If issues are experienced, logging profiles should be set at the user level experiencing the issue. For authorization servlet-related issues, you must set the diagnostics profile at the user level to ANONYMOUS.
To diagnose user interface issues, you can use the filter iby%,fnd.framework%,jbo% and set the diagnostics go-to screen by clicking the Diagnostics Global button. To enable this functionality, you must set the following profile option:
The FND: Diagnostics profile option controls whether the Diagnostics button is rendered. It also controls the display of the About this Page link.
For system issues, such as exceptions, timeouts, or unexpected behavior, you can turn on logging, based on where you are experiencing the issues, as follows:
You can also capture additional information about the system by printing the report from the About this Page link, as well as from the jsp: /OA_HTML/jsp/fnd/fndversion.jsp.
For more information on Logging, see the Oracle Applications System Administrator's Guide Documentation Set and the Oracle Applications Developer's Guide in the Release 12.1.3 Documentation Library.
Return to Diagnostics and Logging
There are no known issues for this product.
Date | Description of Change |
---|---|
July 2013 | Initial publication |
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your beta trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.
This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Software License and Service Agreement, which has been executed and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.