Integrity Report
Integrity Report
Integrity Report
By
Natarajan Duraisamy
w.r.t
JD Edwards OneWorldXe/Enterprise One/ WorldSoft
Table of Contents
1. Introduction
1.1 Objectives
1.2 Target Audience
2. Additional Information
3. Integrity Report (R41544) Illustration
3.1 Columns Data
3.2 Report (R41544) Output-Example
4. Issues, Causes and Resolutions
5. How to Resolve ? An Issue Demo
5.1 Running the Report R41544
5.2 Report (R41544) with Discrepancies
5.3 ASOF File Integrity (R41760) -Example
5.4 Item Ledger As of Record Generation (R41542)
5.5 ASOF File Integrity (R41760) -Example
5.6 Report (R41544) without Discrepancies
6. References
1. Introduction
Inventory is the basis of Supply Chain Management. Companies move inventory within and
among their facilities.
As we are aware that ERP being an integrated system, for an item, maintaining integrity
between Running Balance and the summary of transactions due to processes such as
Inventory Transactions, Procurement, Sales and Distribution, Manufacturing etc where
inventory plays a major role, is necessary.
Data consistency is a necessity to ensure balancing of inventory transactions with financial
records of any organization
1.1 Objectives
To Identify integrity problems in Inventory management within JDE.
To Solve identified integrity problems in Inventory management within JDE.
To find out the possible causes of integrity problems
To know about the risk involved with not running the integrity report
Be able to run the integrity report
1.2 Target Audience
This white paper intends to guide a JD Edwards Functional Consultant quickly and simply
resolve the issues related to Item Balance/Item ledger integrity. Further, some guide lines are
also mentioned to identify the causes of the integrity problems. The paper would be found
useful by a JD Edwards Technical consultant also to gain insights into the general logic and
mapping of this Integrity report.
2. Additional information
When should you run Integrity reports?
Integrity reports are an integral part of the JD Edwards
system. You should run them:
During implementation to test the legacy data moved into the JDE system
Up gradation from one version to another version of JDE
Migration from one ERP Package to another.
Before Purging and Archiving.
Periodically, Necessary.
Daily, if necessary
Why should you run integrity reports?
Running the integrity reports helps you to
Ensure that the system function correctly and tables/ files remain in balance .
Correct any integrity problem in a timely and efficient manner.
Locate data inconsistencies.
What do the standard integrity reports provide?
Most of the standard integrity reports provide information that is current at the time that
you run them. That is, they have no as of capability. Exceptions to this are some of the
Accounts payable to general ledger and Accounts receivable to general ledger.
Item Balance/Item Ledger Integrity (R41544) report displays discrepancies for both quantity
and amount between the Item Location F41021 and Item Ledger F4111 tables, in
combination with the Item As Of F41112 table.
The report displays summary lines that represent specific totals by:
Branch /Plant
Second Item number
Location
Lot number
Unless you set the processing option to print all records, a blank
report or without Variance indicates that no discrepancies exist.
Item ledger quantity and amount are from combination of F4111 and F41112 tables.
Item Balance quantity (On Hand) is from F41021 table.
Quantities are in Primary Unit of Measure.
Item Balance amount is by multiplying quantity with unit cost from F4105 table at the
time you run the report.
Variance is Item balance minus Item ledger.
Percentage variance is derived by (Item Balance-Item Ledger)/Item Balancex100
Branch/ Plant, Second Item number, Location and Lot Number are from F41021 table
Causes
1.
2.
3.
4.
1.
2.
3. Item balance is greater or 1.
less than Item ledger even
though As Of Processing is
done.
2.
Resolutions
As of processing is not
1.
done.
GL date for transactions 2.
in Item ledger is missing.
Tables update failure
during transaction.
3.
SQL might be executed.
4.
As of processing is to be
done.
GL date for transactions
in item ledger should be
available.
Executing SQL for
tables update failure.
Avoiding executing SQL
Transactions in item
1. Report cant be run As
ledger might be in future
of Date
GL date.
2. Executing SQL
Tables update failure
for tables update failure.
during transaction
Issues
Causes
Resolutions
1.
2.
As of processing is not
done.
No transactions for
current period when
you run the report.
1.
2.
3.
1. As of processing is not
done properly
2. Incomplete process
3. Tables update failure
during transaction.
1. As of processing is to be
done
2. Process like work order
is to be completed
The report displays those items for which As Of Processing is not done.
The report will be blank if As Of Processing is done for the item. Here report displays records of
Item number-short 60011 before doing As Of Processing.
It is not necessary to run this report but it is better to run to ensure that the records in item
ledger have been generated to Item As of File F41112.
The data displayed are not related to the complete transactions which are used for demo on
upcoming pages. Just an Example.
For this Report:
Processing Option: NIL
Data Selection:
1.
Business Unit=M30
2.
Item Number-Short=60011
Data selection can be as per the requirement.
Inventory transactions are done in Current period so that during AS Of Generation, Balance
from previous year can be carry forwarded to the current year.
Transaction for future date (Highlighted) is also done. But you may notice that transaction is not
counted for Integrity which also shows this report will run as on date
6. References
JD Edwards E-Guide
Case studies from JDE Projects