5728725, 126 Pa Document §25402.1 Copyright(c) 2023, Oracle Al rights reserved, Oracle Confidential E1: 41: As Of Processing (P4111 / P41112 / R41760 / R41540 / R41542) (Doc ID 625402.1) In this Document Purpose Introduction Details Populating the Item ASOF (F41112) file Online Inquiries AS OF Batch Reporting and Reconciliation Frequently Asked Questions References JD Edwards EnterpriseOne Inventory Management - Version XE and later Information in this document applies to any platform. Introduction The Item ASOF (F41112) file contains records As Of each fiscal period for every unique combination of the following: Branch Plant. Location Lot G/L Class Code Fiscal Year This fle can be used to generate batch and online reporting for records As Of a specific date. It can also be used to store ‘summary information for clients who purge records from the Item Ledger (F411) file. To accomplish this, the As Of file must exist and a partial generation must be run before purging Item Ledger (F4111) records, This functionality is used for the following: + Keep accurate balance forward records from year to year. + Compare and reconcile your inventory balance for different fiscal periods. + Access information about the quantity and cost of an item in any location, + Speeds up access to item ledger, This document provides details on As Of Processing including how to populate the table, updating balance forward records, online inquiries, As Of Reporting and frequently asked questions, Populating the Item ASOF (F41112) file The Item ASOF (F41112) file Is primarily populated by the Item Ledger As Of Record Generation program (R41542). The Direct As OF Entry (P41112A) can also accomplish this. Item Ledger (F4111) records are included in Item ASOF (F41112) records according to their G/L Date in addition to other keys. hitps1/support oracle, comlepmositaces/DocumentDispay?_acl ct-state=uwaB6jrwg_BO08id=625402.1 ve5728725, 126 Pa Document §25402.1 Before running As Of Processing (R41542), Item Ledger entries will normally have the Posted Code (F4111.1PCD) set to Blank (not posted). The Item As Of Process will read Item Ledger (F4111) records which have a blank in the Posted Code (IPCD) and once those values have been added to the balances in the Item As Of (F41112) file, they will be changed to a Posted Code to "Y" (posted). The item ledger As Of regeneration (also called Complete Regeneration) should be run first; it will create records in the Item ASOF (F41112) file using every relevant record in the Item Ledger (F411) file. This program (Complete Regeneration version) will not be needed again unless fiscal date patterns are changed. The Complete Regeneration cannot be run if any records have been purged from the Item Ledger (F4111) file, this would create inaccurate and incomplete As Of records. The Data Selection for the Complete or Full Regeneration includes IPCD not equal to'S' and 'X., This allows the file to be completely rebuilt, Also note that any records that were manually added through Direct As OF Entry (P41112A) will not be included in the regeneration. Important: When using report R41542 for a complete regeneration, all existing records from table F41112 will be purged regardless of the data selection. The data selection will be used only to regenerate the new records into F41112 table. It is recommended that the complete regeneration is run once for the first fiscal year with inventory activity (with F4111 records) for all items. 41542 should run in batches, with data selection over separate fiscal years. This will ensure that balance forwards will be restored for each fiscal year The Generation (also called a Partial Generation) program is intended to update the Item ASOF (F41112) file with information from new records entered into the Item Ledger (F4111) file. The system uses the field IPCD (inventory journal posted code) to determine which records in the Item Ledger (F411) have already been accounted for in the Item ASOF (F41112) file. The Data Selection for the Partial Generation includes IPCD not equal to’, , and 'Y'. There are four valid values for the IPCD field: + The Y indicates a record which has already been included in the Item ASOF (F41112) file, using a version of the Item Ledger As Of Record Generation (R41542) UBE. ‘+ ‘The S is used for sales order lines, which have been Ship Confirmed (P4205) but not run through Sales Update (R42800) (assuming inventory is relieved at Ship Confirm). When Sales Update (R42800) Is run, the IPCD field will be set to blank, when the process is run again, the record will be selected and a 'Y' will be put into the IPCD field + ‘The X indicates transactions which do not affect balance information, such as lot, hold releases, or scraps from work orders, ‘+ The" (blank value) is most common, used for new records in the Item Ledger (F411) which have not yet been included in the Item ASOF (F41112) file. If records have been purged from the Item Ledger (F411) table, or if the user is not sure whether a purge has been run, use the Partial Generation, Updating Balance Forward Records for Inactivity in the Fiscal Year To include records of prior year activity, run the As Of Updating (R41548) UBE after the Item Ledger As Of Record Generation (R41542) program. The As Of Updating (R41548) UBE searches for an item record in the Item ASOF (F41112) table and then determines whether a corresponding record exists for the next year. Ifa record does not exist for that year, the program inserts a record, carrying forward the cumulative amounts and quantities. The program continues to fill in any gaps until processing is complete for the year specified in the processing options. Note: This processing option should be populated with the year for which you want to create balance forward records: 1. Enter the fiscal year (four digits -- e.g. 1999) through which the file is to be updated. If left blank, the current year will default. Entry of an invalid year will prevent the program from executing tps eupport oracle. comlepmestaces/DocumentDisplay?_acf.tt-elate=uwadéjrng_9008h 2185728725, 126 Pa Document §25402.4 Note: If you observe that the totals on R41548 are wrong, then ensure that the UOM has not been changed. The Direct As Of Entry (P41112A) program is primarily used to input inventory balances for years before a JDEdwards EnterpriseOne solution was implemented. Entering information using this program will NOT create any journal entries. Once data is entered with this program, the complete regeneration (R41542) program should NOT be used because all information entered in the Direct As Of Entry (P41112A) program will be lost. Note: In extreme cases, the Direct As Of Entry (P41112A) program can be used to update Item ASOF (F41112) records. No editing of values will be done, and no audit trail or history will exist, Further, these changes will NEVER be picked up if tthe complete regeneration is run. Processing Overview: The Item ASOF (F41112) file is primarily a summarization of amounts (currency) and quantities. It contains 14 fields which correspond to our standard 14 G/L periads (defined by fiscal date patterns) and represents net change in amount or quantity for that period. It also contains a cumulative amount and cumulative quantity field. These contain the cumulative amounts and quantities from the PRIOR fiscal year (the sum of the cumulative amounts or quantities and the period buckets from the prior fiscal year Item ASOF (F41112) record). ‘+ INNQO1 - INNQ14 - The net change for a specific G/L period, stored in primary unit of measure, Represents the sum Of all transactions which occurred in the period. + INAO4 - INA14 - The net change in amount (currency) for a specific G/L period, Representing the sum of all transactions, which occurred in the period. + INCUMA - The cumulative amount (currency) from the prior fiscal year's record. + INCMQT - The cumulative quantity from the prior fiscal years stored in primary unit of measure. The sum of INCMQT and INNQO1 through INNQ14 from the previous year's record. + IPCD (in F4111) - These are the four valid values for the posted code field: 'Y, 'S', x’, and ' (blank), See Details. Juantities are stored in primary unit of measures (UOM). Online Inquiries There are two As Of online inquiries, off menu 64122: + The Item Ledger (Cardex) (P4111) + The Item Ledger (Running Balance) (P4112) These programs will use information from the Item ASOF (F41112) and the Item Ledger (F411) files. Item Ledger Inquiry (P4111) - Cardex This online inquiry is primarily used to view the Item Ledger (F411) file. Dates, Document Types, Branch/Plant, Lot, and Location criteria can narrow inquiries. This inquiry has the following characteristics: ‘+ It will display documents based on transaction date. + It will display the most current through oldest transactions. + Sales Orders which have been Ship Confirmed (P4205) but not run through Sales Update (R42800) will have a posted code of $ and a blank G/L date. + Work orders which have been issued materials or completed but not run through the post program will have a posted code of $ and a blank G/L date. ‘+ The header area of this screen displays the quantity on hand (from the Item Location (F41021) file) and the value of this inventory (cost in the Item Cost (F4105) multiplied by the quantity on hand). Running Balance (P4112) The running balance inquiry differs only slightly from the item ledger inquiry. This inquiry has the following characteristics: se tps eupport oracle. comlepmestaces/DocumentDisplay?_acf.tt-elate=uwadéjrng_9008h5728725, 126 Pa Document §25402.1 It displays document based on their G/L dates. It will display the oldest through the most current transactions. Sales Orders which have been Ship Confirmed (P4205) but not run through Sales Update (R42800). Clients who relieve inventory at Ship Confirm (P4205) (UDC 40/IU) will not display because the Item Ledger (F411) record does not contain a G/L date. + Work orders which have been issued material or completed but have not been run through the post will not be displayed. AS OF Batch Reporting and Reconci Several reports are included on the As Of menu (64122) to facilitate reconciliation of financial information with the Item Ledger (F411) file. 1, Item ASOF Table Integrity (R41760) Report 2, Item Ledger Detail Print (R41540) 3. G/L by Object Account (R09421) 4, Item Ledger By G/L Class Code (R41541) 5. Trial Balance By Object Report (R094121) ‘TYpically, the Item Ledger Detail Print (R41540) and the G/L by Object Account (R09421) are compared; also the Item Ledger By G/L Class Code (R41541) and Trial Balance By Object Report (RO94121) are grouped together. The second pairing would be a more high level check, and could be considered a precursor to the first. Reconciliation between the pairs can be time consuming; the narrowest possible data selection, and use of the summarization processing options for the financial reports may speeds the process, These reports should be run as close to the same time as possible as daily operations can change their output. Recondiliation may be impossible for reports run at different times. Item ASOF Table Integrity (R41760) Report The Item ASOF Table Integrity Report (R41760) compares the data in the F411 Item Ledger and the Item As Of (F41112) table, If items in the Cardex (F4111) do not have corresponding records in Item As Of (F41112) records, errors will appear indicating that records are missing, This often occurs at the first of a new fiscal year when the Item As Of (F41112) records for the new Fiscal Year have not been brought forward from prior Fiscal Year, This can be resolved by running As Of Updating (R41548) to generate new Item As Of (F41112) Balance Forward records for the prior year In addition to detecting missing Item As Of (F41112) records, the Item ASOF Table Integrity (R41760) report will also point ‘out variances between the Cardex (F411) data and the corresponding Item As Of (F41112) period balances for quantity or dollar amounts. ‘These types of variances can be corrected by using the Direct As Of Entry (P41112A) to correct the period balances for quantity and amount to agree with the Item Ledger (F4111) details, Item Ledger Detail (R41540) Report hitps1/support oracle, comlepmositaces/DocumentDispay?_acl ct-state=uwaB6jrwg_BO08id=625402.1 485728725, 126 Pa Document §25402.1 This detail report provides 2 review of item(s) transactions over a period of time determined by processing options. Item Ledger (F411) records with a blank G/L Date will not appear on this report (e.g. Ship Confirmed (P4205) orders that have not been through Sales Update (R42800) but have relieved inventory) ‘The Item ASOF (F41112) and Item Ledger (F4111) will be used to obtain a beginning balance As Of the from date. Detailed transactions within the date range are from the Item Ledger (F411) and the report will calculate an ending balance based on the ending date. Totals will be produced in the following order: + Location/Lot + G/L Category Code + Item) + Warehouse (Cost Center or Branch Plant) + Grand report total *The beginning balance is in primary unit of measure and the detailed transactions are in the transaction unit of measure. Item Ledger G/L Class Code (R41541) Report (Typically paired with the Trial Balance By Object Report (R094121) for high level checking) This summary report provides a high level total of the balance in each Item ASOF (F41112) record. The processing options allow the selection of a specific fiscal year and period, or the current period and year will default from the company constants, Totals will be displayed by: 1. Cost Center 2. G/L Category Codes “This report does NOT use the Item Ledger (F411) at all. The data sequence should NOT be changed. G/L by Object Account (R09421) Report (Typically paired with the Item Ledger Detail Print (R41540) for a detailed reconciliation) This detail report provides G/L detail information from the Account Ledger (FO911) file, Its included on this menu for reconciliation purposes. This report would most likely be compared with the Item Ledger Detail Print (R41540). This would allow the user to check if detail accounting entries match detail Item Ledger (F411) records. This report will provide G/L detailed sequenced by: 1. Company 2. Object 3. Subsidiary And totaled by: 1. G/L period 2. G/L Account 3. Object 4. Company Trial/Balance by Object Account (RO94121) Report (Typically paired with the Item Ledger By G/L Class Code (R41541) for high level check) This summary report provides trial balance information (from the Account Master (F0901), and Account Balance (F0902) files, hitps1/support oracle, comlepmositaces/DocumentDispay?_acl ct-state=uwaB6jrwg_BO08id=625402.1 seDocument §25402.1 and possibly including calculation using the Account Ledger (F0911) file). It is included on this menu for reconciliation Purposes. *Note: Only posted amounts will show on this report. This may cause discrepancies with the Item Ledger By G/L Class Code (R41541) if all batches have not been posted. Frequently Asked Questions Question 1: Item ASOF (F41112) file shows negative cumulative amounts for several items. What causes this? ‘Answer 1: Cost method Weighted Average Cost (02) was being used and the quantity on hand was allowed to go negative, The Weighted Average Cost method does not support on hand quantities going negative. A potential workaround to fix the 41112 records would be to run the As-Of Entry (P41112A). Question 2: ASOF Generation (R41542) was launched in test environment and it ran for 2 days on 5.5 mi records. In PD, can the report be run by fiscal year? Answer 2: Itis better to run the report by fiscal year; run it for 2009, then run R41548 to insert a record into 2010, then run 41542 for 2010, then R41548, and so on. Question 3: We are changing our date pattern from fiscal to calendar, but not restating past history in the G/L, Do we need to regenerate the ASOF file (F41112) after the date pattern has been changed? Does the new date pattern impact the ASOF file? Why would it if the ending cumulative balance at year end will be the starting balance for the new year- P1? Answer 3: No, Complete Regeneration is not required. If you change the Fiscal Date Pattern and the FY runs from 1/1/2007, you will not get any variances in the Item Ledger/Balance Integrity Report (R41544) because the balance will be carried forward correctly, Only buckets will be changing as explained below when changing the Fiscal Date Pattern, So you will not get any variance in integrity report. When the date pattern is changed, the period number also changes and it will post the new records into the buckets corresponding to the new date pattern but it will not affect the transactions already posted as they are not picked up again for posting The ASOF File (F41112) maintains the quantity and amount by period number and if we change the date pattern, the period ‘number also changes accordingly and hence there will be a miss match between the bucket and the actual transaction date for ld transactions and it doesn't affect the carry forwarded balance. Question 4: Our ASOF (F41112) file is a large size and we want to purge some prior years. Can we do this, without issues? Answer 4: The ASOf (F41112) File should not be purged. The reason for that is, F41112 contains the summarized data of the Cardex (F411) which is very important for Integrity of various applications and reports. Question 5: The UOM of an item was changed after ASOF Generation (R41542) was run, variances have been detected for the item since then. Why is that happening and how to correct it? ‘Answer 5: Changing the primary UOM after ASOF Generation (R41542) has been run can cause issues since the ASOF File (F41112) does not have a UOM field, Basically when regenerate processing option is set to blank, it will take all records in the Cardex (F4111) with IPCD = blank and add it to the corresponding ASOF (F41112) record and it does not consider Unit of Measure because everything in the Cardex is in primary. If primary is changed after ASOF has been run, issues arise. Test in a test environment and run Complete Regeneration. This might take a while to run depending upon the number of records in the Cardex. This cleans out ALL records from the ASOF (F41112) regardless of data selection. It dears out every year, every item lot/location and recalculates. hitpsisupport race. co lopmosfacesiDocumentDisplay?_adf.ctt-state=uwadéjrng_9008h5728725, 126 Pa Document §25402.4 Note: The UOM of an item should not be changed after there are transactions for that item, Question 6: To change the G/L Class of an item that is already in inventory, what is the process and impact in Finance as well as in Inventory? ‘Answer 6: Changing G/L Class involves Item Master (F4101), Item Branch (F4102) and Item Location (F41021) tables, which ‘one to change depends of the transaction that needs to be affected by the G/L Class and by the Inventory Cost Level, Sales Price Level and Purchase Price Level that the item uses in the Item Master (P4101). Note: The change will take effect for newly created transactions and all history details and Cardex remain as the original G/L Class assigned. As Of file (F41112) will be updated with two records assigned with different G/L Classes. Different G/L Account will be assigned, per the G/L Class setup in the respective AAI tables. It is recommended to not have frequent changes to the G/L Cass as this may result in integrity issues with the existing data, Backup and thorough testing is highly recommended prior the change is made effective. The system will maintain two different closing balances at the As Of File (F41112) due to the different G/L Class assigned, as G/L Class is part of the primary key fields of F41112. To consolidate the closing balance for the two different G/L Class, manual data patching or customization is required as there is no standard functionality to perform the consolidation, The impact in the consolidation may result in integrity issues due to inconsistency in the balance matching to their respective transactions (sales, purchasing, inventory movement, Cardex, etc). This will also affect the financial account balance if different accounts have been assigned to the two different G/L Classes. Question 7: When opening Running Balance (P4112) from the fast path, how is the fiscal year defaulted Answer 7: 11, When user has a default B/P defined, the system verifies the respective company from FO006 for the B/P, then checks tthe beginning fiscal year for the company. It then populates the respective fiscal year in P4112 based on the company's beginning fiscal year 2, If user does NOT have a default B/P, the system checks for default company's (00000) beginning fiscal year and opulates the fiscal year in P4112 based on the default company's beginning fiscal year Question 8: When should the R41548 be run? Answer 8: R41548 should be run when correcting F41112 historical gaps for years in which there is no item activity. In addition, it can optionally be run over all items at the beginning of a new fiscal year to create new BF records, Question 9: When running the Item AS Of Integrity Report (R41760) in the middle of the current month there are integrity variances showing, only for records in the current period of the current fiscal year. Why is that occurring? Answer 9: The Item As Of Integrity Report (R41760) compares data in the Item As Of Table (F41112) period fleld with data in the Item Ledger (F4111) table, which includes posted and unposted transactions. The variances are appearing because the unposted transactions in the Item Ledger (F4111) table are being included in the comparison. After running the As Of Generation (R41542) against the item, the Item Ledger (F411) Posted (IPCD) code was changed from blank to Y, Running Item As Of Integrity Report (R41760) immediately after As Of Generation (R41542) produced a blank report showing no variances. Question 10: What are the cases where Cumulative Amount becomes negative although the Quantity is zero or positive? ‘Answer 10: If the Extended Cost field has zero decimal and Unit Cost fields has values with decimals, rounding can cause such an error, For example, hitpsisupport race. co lopmosfacesiDocumentDisplay?_adf.ctt-state=uwadéjrng_9008h5728725, 126 Pa Document §25402.1 Quantity Cost Unit Cost*Q Extended Cost (Rounded to zero decimal) 385.0000 245.176 943927600 94393 -100,0000 245.176 -24517.6000 -24518 -100,0000 245.176 -24517.6000 -24518 -100,0000 245.176 -24517.6000 -24518 -85,0000 245.176 -20839,9600 -20840 Total 0 a ‘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. JD Edwards has active communities in My Oracle Support Community (MOSC) where an expansive network of Oracle ‘Support experts, customers, and partners from across the globe collaborate on questions, best practices, and solutions, Use the links below to go directly to the search option or Ask a Question option in the Distribution community. ‘Search in the E1 Distribution Community © 13-4 Question inthe 1 Distribution Community NNOTE:1367799,2 - Information Center: JD Edwards EnterpriseOne Inventory Product NNOTE:548764.1 - Advisor Webcast Details NOTE:625402.1 - Et: 41: As OF Processing (P4111 / P41112 / R41760 / R41540 / R41542) NNOTE:1367801,2 - This document has been replaced with more recent information on this topic. Please refer to more recent documentation, Didnt find what you are looking for? hitps1/support oracle, comlepmositaces/DocumentDispay?_acl ct-state=uwaB6jrwg_BO08id=625402.1 ory