To piggyback on to Gigi's question - please refer to the below document from Oracle- 664721.1
******************************************************
This document was previously published as Customer Connection Solution 201077651
Goal
Understanding the P0010 company names and numbers application
Solution
Issue:
Frequently Asked Questions Regarding Company Names and Numbers
Question 1
A user changes period number and this not being reflected (receiving PBCO error) for the thin-client user (JAS or Terminal Server). How should this issue be addressed?
Resolution:
Answer 1
The current period is held in table F0010. This is a cached table (held in memory) because this information is used so often. The cached table list is held in the table F98613. PBCO is handled by our master business function B0900049 F0911FSEditLine which calls function X0903 EditDate. For JAS or Terminal Server the X0903 function is executed at the Enterprise Server so this is handled by callobject kernel cache.
Please review if resetting server callobject kernel cache refreshes the holds the latest period number.
From an Admin workstation (logged into non-J environment) with OneWorld/EnterpriseOne installed
1. Go to the "System Administration Tools" (GH9011) Menu.
2. Start up the "Work with Servers" (P986116|ZJDE0001) Application.
3. Place the focus on (highlight) the "Data Source" where Call Object Kernel is running that is going to have its cache cleared.
4. From the Row Menu choose "Reset Cache".
5. Choose Database
6. The user must log off EnterpriseOne from the thin client and then back on to a new session.
WORKAROUND:
As an alternative the user does have the option to remove it from being cached by using application P98613 and deleting the entry which removes it from being cached, but we caution this will affect performance.
As of Tools Release 8.97.2.2 and 8.98.0.1 the client will be able to do this from a web client using the same application P986116 "Work with Servers". Each of these tools releases should be available in late 2008.
SAR 8848719 TR 8.97.2.2
SAR 8829753 TR 8.98.0.1
Unfortunately this still requires a user to have access to a "technical" application... which many financials users do not have. The only alternative to remove F0010 as a cached table from P98613.
Below is a more technical explanation of the process
Question 1. Will the data in table F0010 - Company Constants be cached?
Question 2. Which cache does it read in actual transaction?
Question 3. Can we define our own Service Cache and Database Cache?
Question 4. Where can we find information on Database Caching and Service Cache?
Question 5. Are there full list of tables for these caching?
Question 6. What's the common error we may get owing to uncompleted Cache refreshing which are related with data of F0010?
Question 7. How to refresh these caching?
Question 8. How to debug when the issue appears to be caused by F0010 data?
Question 9. In programing how does it makes use of these caching data?
Solution
Answer 1. F0010 - Company Constant Tables are to be cached for both JAS (Client) and Logic Server(Server). We may call it Service Cache and Database Caching respectively.
Answer 2. It depends on what kind of issue you are getting. In case the issue is related with Currency Information it will come from Service Cache as Currency Decimal has to be handled at Presentation level along with F0013 - Currency, F0025 - Ledger Type and so on. If the issue is not related with Currency Code then most likely the issue may be coming from Server Database Caching, as the thin client environment DEFAULT BSFN is mapped to Server through OCM mapping. In this case, the request for table F0010 will be performed through BSFN(s), therefore it has to read Cache in Server (Database Cache)
Answer 3. Yes, ideally you can define your own cache but it may cause problem. The reason is that JDE API will determine whether to read cache table or physical table so this has to be work with actual C code we have.
Answer 4. You may be able to find Cache information as below,
A. Database Caching
1. Log on WebDev/WebAdvmin client
2. (Fast Path) P98613 - Work with Database Caching
B. Service Cache
: Do not change defined values/tables as it may cause unexpected result in running certain applications. You can get this information from \System_JAR\com\jdedwards\database\services\serviceobj\ in your JAS to check the tables which are member of ServiceCache
Answer 5. The tables defined can be different from E1 Release and E1 Tools Release. Below are general tables which data are to be cached.
A. Database Caching
F0004 User Defined Code Types
F0005 User Defined Codes
F0006 Cost Center Master
F0007 Work Day Calendar
F0008 Date Fiscal Patterns
F0010 Company Constants
F0012 Automatic Accounting Instructions
F0013 Currency Codes
F0014 Payment Terms
F00144 Installment Payment Terms
F0015 Tax Rules
F0025 Ledger Type Master File
F0026 Job Cost Constants
F01138 AB Data Permission List Definitions
F069016 Payroll Tax Area Profile
F069036 Payroll Transaction Cross Reference
F069056 Establishment Constant File
F069086 Payroll Corporate Tax Identification
F069096 Payroll General Constants
F069106 Union Benefits Master
F069116 Payroll Transaction Constants
F069226 Unemployment Insurance Rates
F07901 Pre-Payroll DBA Calculation Control Table
F0901 Account Master
F1609 Cost Management Constants
F1690 Enables Tables by Application
F17001 Service Warranty Constants Table
F1724 Service Contract Coverage
F1725 Service Contract Services
F1752 Case Types
F1753 Case Priority
F1790 Product Family/Model Master
F1793 S/WM Line Type Constants
F3009 Job Shop Manufacturing Constants
F40039 Document Type Master
F40070 Preference Master File
F40073 Preference Hierarchy File
F4008 Tax Areas
F4009 Distribution/Manufacturing Constants
F40095 Default Locations/Printers
F40203 Order Activity Rules
F40205 Line Type Control Constants File
F4070 Price Adjustment Schedule
F4071 Price Adjustment Type
F4095 Distribution/Manufacturing - AAI Values
F41001 Inventory Constants
F41002 Item Unit of Measure Conversion Factors
F41003 Unit of Measure Standard Conversion
F48091 Billing System Constants
F7306 Quantum Sales and Use Tax Constants
F95922 Permission List Relationship Table
F99410 OneWorld System Control File
FF30L011 Line Design Control Parameters
FF30L012 Kanban Control Parameters
FF34S003 DFM Planning Parameters
R31410 Order Processing
B. Service Cache (Refer 650630.1 - E1: FDA: Tables Cached by JDBJ (8.95 and higher))
F0004 User Defined Code Types
F0005 User Defined Codes
F0005D User Defined Codes - Alternate Language
F0010 Company Constants
F0013 Currency Codes
F0025 Ledger Type Master File
F0092 Library Lists - User
F00941 Environment Detail - OneWorld
F0111 Address Book - Who's Who
F9500001 CFR Configuration Table
F95921 Role Relationship Table
F9861 Object Liberian - Status Detail
And below is a list of groupings for service cache :-
* abfullname
* bootstrap
* cfrconfig
* company
* currency
* datadictionary
* ledgertype
* ocm
* omw
* packagelookup
* pathcode
* role
* security
* seviceobj
* setid
* spec
* tablelookup
* udc
Answer 6. To determine this observe the BSFN which issue error. If the error is coming from BSFNs,
B0000069 - RetrieveLedgerTypeCurrencyRetrieveLedgerTypeCurrency
B0000095 - FormatCompany
B0000128 - RetrieveCompanyCurrencyCodeRetrieveCompanyCurrencyCode
B0000130 - RetrieveCompanyFromBusUnitRetrieveCompanyFromBusUnit
B0000198 - GetCurrencyCodeandDecimalsGetCurrencyCodeandDecimals
B0000399 - CurrencyDecimalShiftCurrencyDecimalShift
the error may appear "Record Invalid" "Fetch From table failed" depending on the application you are running. This is usually caused by Service Cache in Server
Whereas if the error is issued by other BSFNs Database caching may have problem. The error can be vary like this example Current Period Number may be computed wrongly.
Some example can be,
A. Issue is related with Currency Code: Service cache has to be refreshed
B. Issue is related with other than Currency Code: Database Cache has to be refreshed
7. The way refresh cache can be vary in general,
A. Database Caching
1. Log on FAT(WebDev/WebAdvmin) client
2. (Fast Path) WSJ - work with Server(P986116)
3. Highlight the logic Server and (Row Exit) Reset Cache which is calling [Reset Cache]
4. Tick 'Database' then click OK this will flush database caching
B. Service Cache
1. Log on to WebSAW or Server Manager depends on the tools release you are on
2. Look for JAS instance
3. In Runtime Metrics Section, click 'JDBJ Database Caches'
4. Select "JDBj Service Caches" then (push button) Clear Cache to flush Service Cache
5. Verify that Cache Size is initialized into zero
Answer 8. Whenever there is any issue on F0010 table, try to capture jasdebug.log in JAS and jdedebug.log in Logic Server. To handle data for both database level and presentation level, some BSFN will be running in JAS others are running in your logic server though by default DEFAULT BSFN is mapped to Server through OCM mapping for J* Environment. Some BSFNs are to be running in Local(JAS) as you can find the defintion from LocalLogicCatalogLocalLogicCatalog.xml (OAS: OAS: \\JAS\Release\system\OC4J\j2ee\home\applications\webclient.ear\webclient\WEB-INF\classes).
Answer 9. If JDE BSFN is to read cache JDE API JDB_FetchKeyed will be issued from a certain BSFN.
References
NOTE:650630.1 - E1: FDA: Tables Cached by JDBJ (8.95 and higher)
NOTE:663754.1 - E1: JAS: Intermittent "Record Invalid" error happens on web clients
Keywords:
Inquiry
System Code: 09
Program IDs: P0010
Release:
Xe, ERP8.0, 8.9, 8.10, 8.11, 8.11 SP1, 8.12, 9.0
