Use this program to print a register of cost discrepancies entered in the Cost Discrepancy Entry (ICE610) program. If any cost discrepancies have been entered, but not posted, you must run the Cost Discrepancy Register before you can close the GL or IC period. All records post to the GL period based on the register date. The GL account numbers come from the receipt record (ICRCPT) so they post to the same accounts as the original receipt. The GL Update writes journal entries for the cost discrepancy from the receipt as well as any disbursements from that receipt. Note that default GL account numbers are not assigned by this register.
At the top of the screen, warehouses with discrepancies are displayed and the first warehouse in this list is displayed by default in the warehouse prompt.
Any time you run the Cost Discrepancy Register, you must continue to re-run this program until there no records available. Processing in the Cost Discrepancy Register may automatically generate additional cost discrepancies. These automatically generated cost discrepancies are not completed until the next time the Cost Discrepancy Register run. Always run this register repeatedly until no additional records are generated.
You can:
GL Summary
The GL Summary includes the line level information: document type, document number, Receipt / Invoice / Shipment number, Line Number, Component Line, Item and a flag indicating if the item is a Serial / Lot item. This information is posted through to the GL Journal and can be view from Source Doc button the GL Journal Inquiry program.
IC receipt and disbursement files
GL account numbers are written to IC receipt and disbursement files during registers. Cost Discrepancy Entry is only allowed on receipts that are post-register processing. Running the Cost Discrepancy Entry Register for receipts which have ‘open’ disbursement documents that are not yet run through their own register does not show GL account information on the Cost Discrepancy Register output. Costs on ‘open’ disbursement documents can be updated by the cost discrepancy register, and, when the ‘open’ documents have their own register run, the associated docs, having already had their costs updated through the Cost Discrepancy Entry Register, update GL on their own register.
Outputs with no cost difference
Records can be written to the cost discrepancy file when an over-shipment is filled by an incoming receipt. Additionally, factored cost discrepancy entry may be involved. These are two types of output that show no cost difference on the first page of the Cost Discrepancy Register. Running the register clears such records.
When an overshipment (OS) receipt is resolved by an incoming receipt, the OS receipt record is removed and a Cost Discrepancy Entry record is written. Since the received cost did not exist at the time of the OS, now the cost is the same as the receipt that resolved that OS. Any change to the cost of that receipt (making the cost different than the disbursement document, such as the sales order) will have that disbursement document's cost updated with the receipt cost during the Cost Discrepancy Entry Register.
For example: A new item is entered, and before any receipts occur that new item is sold, an OS record is written. Then, once a receipt for that new item comes in, the OS record is removed and the sold quantity is accounted for from that incoming receipt. To handle potential cost changes, a Cost Discrepancy Entry record is written and “Created by Processing Overshipment” is displayed on the first page of the Cost Discrepancy Entry Register. The received cost has not changed. The sold item’s cost, if different from the receipt’s cost and not manually changed by the user at entry, would need to be updated with that incoming resolving receipt’s cost when the Cost Discrepancy Entry Register is run.
Update and report-only modes
The Cost Discrepancy Register runs in report-only mode by default. The Reports Only check box is checked by default. You must un-check the Reports Only check box to run in update mode. If a locked distribution record is encountered during the report-only output, a message containing the document number and the cost discrepancy which will be skipped, is displayed. Make a note of any locked documents during report-only output allows for resolution before the Cost Discrepancy Register is run in update mode.
When output is report-only mode no files are updated in the system. The costs presented are the unchanged costs. When output is run updating costs, the values presented may be already updated values. The costs presented may be the changed cost instead of the pre-change cost. For example, if a receipt having disbursements associated has a cost change, then the disbursement summary page showing that receipt will show the original receipt cost in report-only mode, and show the changed, or updated, cost when run and updating costs.
When output is report-only mode, the register number displayed in the output header is 0000. If using Unform Document Archiving, all report-only mode output that is sent to Unform is stored under the 0000 register number.
Special-order temporary items
Special-order Temporary items are included in cost discrepancy processing for the Cost Discrepancy Entry and Cost Discrepancy Register programs.
If a temporary item is entered in Order Entry as a special order, then the temporary item is to be received on a tied special-order PO or transfer. During Order Confirmation, a tied disbursement record is created, against which any cost discrepancy entry can be successfully applied. Cost discrepancy entry and register for this type of special-order temporary item updates cost for both the receipt and the disbursement of that special-order temporary item.
Serial / Lot items are processed by adjusting the line level cost of the usage documents (if used) and the receipt layer cost(s). The cost update will be performed at the lowest level first, and then applied back up the document lines, based on the setting for Sales Order Static Control F/M-> Serial / Lot Cost method. If Averaged Actual is used, the lot costs will be averaged and applied to the serial / lot item layer cost.