Oracle Inventory Documentation Updates
Defining Kanban Pull Sequences
The Supply Days field has been renamed Safety Stock Days, and the value entered in this field is now used along with the Lead Time in the kanban calculation.
See: Defining Kanban Pull Sequences.
See: Oracle Master Scheduling/MRP and Oracle Supply Chain Planning Documentation Updates.
Transaction Managers
The paragraphs describing Resource cost transaction and Material cost transaction have been removed. They are replaced by the following paragraph, titled Cost manager:
The cost manager uses background processing for resource transaction costs from Oracle Work in Process and material transaction costs from both Inventory and Work in Process. The cost manager determines whether your organization is using standard or average costing, and invokes the correct worker accordingly.
See: Transaction Managers and Defining Costing Information.
Oracle Inventory Profile Options
The INV: Capable to Promise profile option now has three values: Enable Product Family ATP and CTP, Enable Product Family ATP, and Enable ATP.
See: Oracle Master Scheduling/MRP and Oracle Supply Chain Planning Documentation Updates.
We added the INV:Product Family Item Template Name profile option, used to select the default Product Family Item Template.
See: Oracle Inventory Profile Options and Oracle Bills of Material Documentation Updates.
Serialized Cycle Counting
In the Approving and Adjusting Counts section, the second paragraph currently reads as follows:
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.
Instead, it should read as follows:
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. In this situation, if the Adjustment option in the Serial Control, Schedule alternative region is set to Adjust if Possible and the Discrepancy option in the same region is selected, you are prompted to let Inventory automatically perform an issue out of the original location into the new location. If you refuse this option, 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. See: Defining and Maintaining a Cycle Count.
See: Serialized Cycle Counting.
Defining and Maintaining a Cycle Count
The first paragraph currently reads as follows:
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.
Instead, it should read as follows:
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. Once you generate a cycle count against a header and save it, you cannot change the serial count options.
See: Defining and Maintaining a Cycle Count.
Approving Cycle Count Adjustments
In the Approval Actions and Adjustments section, The step To Approve a Count Check has been modified by the following addition:
When a count entry contains a serial number found in another location, if the Adjustment option in the Serial Control, Schedule alternative region is set to Adjust if Possible and the Discrepancy option in the same region is selected, you are prompted to let Inventory automatically perform an issue out of the original location into the new location. The adjustment cannot be approved until the discrepancy is corrected. If you refuse this option, 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. See: Defining and Maintaining a Cycle Count.
See: Approving Cycle Count Adjustments.
Item Category Flexfield Structures
The second paragraph currently reads as follows:
When you install or upgrade Oracle Inventory or Oracle Purchasing, Oracle provides two category flexfield structures by default: Item Categories and PO Item Category.
Instead, it should read as follows:
Oracle provides the following item category flexfield structures:
See: Item Category Flexfield Structures.
