Understanding Cycle Counts for Production Controlled Items
A cycle count is the item-based method of counting inventory. You record data, such as item numbers, descriptions, and locations, on printed inventory count sheets, which you later use to update the online inventory records.
The cycle count process maintains information for production controlled items. The Production Number field appears in the detail grid of the Cycle Count Entry - Production Number and Cycle Count Detail - Production Number forms.
You set the Print Production Number Inventory Details processing option on the Print tab of the Select Items for Count program (R41411) to include production number information in the report.
When entering cycle count results, you cannot record quantities if the on-hand quantity in the F41021T table exceeds the on-hand quantity of the item in the F41021 table. The system provides an error message if the quantity entered for a production number is greater than the quantity in the F41021 table.
You must complete the Secondary Quantity field if the item you are cycle counting is set up with dual units of measure in the item master record.
The JD Edwards EnterpriseOne software provides transaction processing capability within the Cycle Count Entry program (P4141) for production controlled items. With the implementation of transaction processing for production controlled items, the system controls updates for the Cycle Count Transaction File (F4141) and Cycle Count Transaction Tag File (F4141T) tables from the Cycle Count Entry form. This ensures that both tables are in-sync at all times.
Transaction processing ensures data integrity for specific programs and tables. If a database error or server failure occurs while the system is committing records to the database, you must roll back all table updates related to the transactions from the database so that the system can maintain data integrity. Transaction processing enables the system to store data in a queue until issuing a commit command, at which time the system moves the data to the corresponding table.
The system creates boundaries for each process that is covered by transaction processing. A transaction boundary includes all data elements that constitute a transaction. When a database error or server failure occurs, the system generates a work flow message indicating that the system has returned to its original state before the failure occurred.