The audience for this note is someone with developer level knowledge.
Across EnterpriseOne system, many routines/applications adds/updates Item Cost File (F4105) but currently there is no Ledger/History File of Item Cost changes. So this document is to explain possible way to determine the change against a Item Cost File (F4105) table.
Q1> What is usual way to gt history of inventory change?
Item Ledger File/Cardex (F4111) contains information on any changes in Item Cost File (F4105). For existing item/branch/location/lot combination, update is to take place against Item Cost File (F4105) and insert is to take place against Item Ledger File/Cardex (F4111). So any information updated in Item Cost File (F4105) will be repeated in Item Ledger File/Cardex (F4111). For this reason, the history of cost change can be traced by reading Item Ledger File/Cardex (F4111).
Note:
Currently there is no standard table to hold Item Cost History/Ledger.
There is no batch application enables users to extract cost change information based on Item Ledger File/Cardex (F4111).
Q2> Can we implement JDE Interoperability 'JDEIC' to write F4105Z1 for auditing purpose?
This table will get written only when you add/change data through Item Cost Revision (P4105) application so it does not audit any change made.
Existing logic of Item Cost Revision (P4105) writes Unedited Transaction (F4105Z1) table only when Processing Option parameter of running version is 'JDEIC' for item #1. Enter the transaction type for the interoperability transaction in 'Interop' tab of P4105.
Currently there are two events (Add Grid Rec to DB - After and Update Grid Rec to DB-After) which have routines to insert/update data into F4105Z1 through Business Function B4101310 - WriteF4105Z1OutboundCost (Write F4105Z1 Outbound Cost).
Since Item Cost can be updated through any inventory related transaction and for transactions which inventory interface is 'Y' or 'D', the information captured through P4105 is not sufficient to audit any change made through Interactive/Batch applications.
Note: For detail on how table F4105Z1 for inbound transaction, refer E1: 41: Inbound Inventory Item Cost Interoperability (Doc ID 1340092.1).
Q3> Are there any list of applications which may update/add data into F4105?
First of all, refer <Document 1074030.1> - E1: 40: Cost and Price Update in Inventory Transaction (P4112/P4113/P4114/P4105/P4106).
Below table shows list of applications which may update/insert data into F4105:
P40G30 - Grower Harvest and Weigh Tag Receipt Operations
If Costing Method is '07 - Standard Cost' and Stocking Type is 'M - Manufacturing' F30026 - Item Cost Component Add-Ons and F300261 - Item Cost Component Detail will be written.
Q4> Will it be possible to audit all above listed applications?
Usual way to make it work is CFR Audit (Refer to E1: CFR11: Auditing Tool (21 CFR Part 11) (Doc ID 636234.1) Guides and MTRs, which will write information (for example, audit table for F4105 is A4105) for all the actions (Add, Update and Delete).
Another way can be table trigger to write (possibly) F4105Z1 table.
Note:
In making use of CFR audit it is made up of three different files:
F4105: Source File to audit
A4105: Metadata for what kind of column to write in writing Target File
F4105_ADT: This table will contain columns of F4105 and A4105
Audit Table F4105_ADT will be written through Native Table Trigger in DB
Oracle does NOT recommend to implement Table Trigger as this implementation increase overhead supposed multiple applications have to access F4105 and update/add data frequently
Oracle is NOT responsible for any performance degrade or record locking resulted from implementing additional auditing routine against table F4105
Oracle recommends to check cost change through F4111 - Cardex and/or F0911 - General Ledger
To discuss information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the JDE1 Distribution Community.
To look at upcoming or archived Advisor Webcasts please see Advisor Webcast Details (Doc ID 548764.1) if your topic is not currently scheduled please suggest it.