Oracle Fa Troubleshooting Guide

Oracle Assets Troubleshooting Guide for Setup - Calendars(ҳ 1) - Oracle ERP Oracle ERP �ĵ � � � � � / � � � � � � � � - Erp100 � �̳ � � S AP|Oracle ERP|JDE|BAAN| � � � � | � � � | � � |SAGE|NetSuite| � � � � � � � � | MBS|Exact ERP|IFS|WebErp| � � �ſƼ � � � E RP| � � � � ERP| � � � � � � | � � | � İ � |Lotus - Powered by Discuz! ArchiverErp100 � �̳ 's Archiver ERP100 � � � � ‫�ٷ‬QQȺ���������˴�� ��ϸ�ĵ����������ôϲ��ERP100��Ϊʲô���Ѹ��ռ ˿ 佨 b � � ERP100 ? Erp100 � �̳ » Oracle ERP » Oracle ERP �ĵ � � � � � / � � � � � � � � Oracle Assets Troubleshooting

»

Guide for Setup - Calendars � ��ĺ� ������ 2007/10/13 21:42 Oracle Assets Troubleshooting Guide for Setup - Calendars [font=Courier]Oracle Fixed Assets --------------------TROUBLE SHOOTING GUIDE ---------------------16-APR-2001 CONTENTS -------1.

UNABLE TO POST BATCHES IN FA - PERIOD NAMES ARE DIFFERENT?

2.

DEPRECIATION ERRORS WITH APP-00988 ORACLE ERROR 1403 IN FAZGTFF CAUSE: FAZGTFF FAILED DUE TO ORA-01403: NO DATA FOUND APP-47685 UNABLE TO GET INFORMATION FROM FA_CALENDAR_PERIODS.

3.

DEP :: APP-47670 UNABLE TO VALIDATE DEPRECIATION PERIOD

4.

CANNOT SEE THE BOOK NAME IN LOV WHEN YOU TRY TO RUN THE ASSET ADDITIONS REPORT.

5.

ERROR APP-00988 ORACLE ERROR 1403 IN GET_DATE WHILE MASS ADDITION POSTING.

6.

NO VALUES IN LOV FOR THE PERIOD WHILE RUNNING THE REPORTS LIKE FAS540.rdf, COST DETAIL REPORT AND COST SUMMARY REPORT.

7.

APP-47422 FAXASSET DEFINE PRORATE DATE FOR DATE PLACED IN SERVICE

8.

DEPRECATION FAILS WITH

9.

APP-47984 IN FAZCCP AND ORA-01403 IN FAZGTCP.

APP-988,ORA-1 UNIQUE CONSTRAINT IN CALENDARS.

10. APP-FND-01564: ORACEL ERROR 1403 IN FADGBI APP-OFA-47131 UNABLE TO GET CURRENT FISCAL YEAR. 11. APP-00988 ORACLE ERROR 1 IN FAENICP APP-48154 MODULE END OF FISCAL YEAR ENDED WITH ERRORS 12. TRYING TO RETIRE AN ASSET FROM THE ASSET WORKBENCH AND GETTING THE FOLLOWING ERROR MESSAGE.

APP-48301 Unknown server side error. Please contact your system administrator Called_FN= FA_RETIRE_PKG.INITIALIZE Called_FN FA_RETIREMENTS.INITIALIZE SQLERRM=ORA-01403 :No data found 13. UNABLE TO RUN INITIAL MASS COPY ON TAX BOOK.

NO CALENDAR ASSOCIATED?

14. USEFUL DIAGNOSTIC SCRIPTS QUESTIONS & ANSWERS ------------------1.

UNABLE TO POST BATCHES IN FA - PERIOD NAMES ARE DIFFERENT :

Problem Description ------------------You are trying to post journal entries in General Ledger (GL) that originated in Fixed Assets (FA) when you encounter the following error: APP-08081: The period for this journal has not been defined. Explanation ----------The application must be able to match the period name in the batch with the GL period name. In this case the FA calendar periods have different names than the GL periods. Answer -----To change the period name: 1. 2. 3. 4. 5. 6. 7. 8. 9.

Navigate to General Ledger\Journals\Enter. In the Find Journals form fill in the Source field with "Assets". Click on Find button. Place cursor in batch with the wrong period name. Click on Review Journals button. In the Journals form, click on More Actions button. In the More Actions form, click on Change Period button. If the Change period button is grayed out, see (A) below. In the Change Period form, place cursor in the To Period and pop up the periods from which to select. 10. Select the GL period to which you wish to post. Save. If the Change Period button is grayed out: 1. 2.

Unfreeze the journal source. Navigate: Setup/Journal/Sources

3. 4. 5. 6. If you

Query all sources with blind query (Ctrl F11). Look for Assets in the Name column. Uncheck the Freeze Journals checkbox. Save and return to previous steps to change the period. want to change future defined periods in Fixed Assets.

Answer -----To change unused period names: Navigate: Setup\Asset System\Calendars Query the calendar in question. Scroll to the last period. From the Main menu select: Edit/Delete Record Continue to delete as far back as necessary (or to where transactions have been entered for the period) Re-enter the periods deleted with the correct name. The suffix is still controlled by the calendar type (fiscal, calendar, none) If type none, the entire period name can be modified. References --------Article-ID: [/font][url=https://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=1017983.1 02&blackframe=1][font=Courier][color=#0000ff]Note 1017983.102[/color][/font][/url] [url=https://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=1015195.102&blac kframe=1][font=Courier][color=#0000ff]Note 1015195.102[/color][/font][/url][font=Courier] contains a solution to change the unused period names so future batches will post automatically. 2.

DEPRECIATION ERRORS WITH APP-00988 ORACLE ERROR 1403 IN FAZGTFF CAUSE: FAZGTFF FAILED DUE TO ORA-01403: NO DATA FOUND APP-47685 UNABLE TO GET INFORMATION FROM FA_CALENDAR_PERIODS.

The SQL statement being executed at the time of the error was:and was executed from the file . APP-47685: Error: Unable to get information from FA_CALENDAR_PERIODS table Cause:

You have a database problem.

Action: Contact your system administrator. Error: function Error: function Error: function Asset ID 100359

fazcff returned failure (called from faxcde) faxcde returned failure (called from fadmlp) fadmlp returned failure (called from faddep) (100359) -> ** FAILED **

Answer -----Run the attached scripts in the "Trouble Shooting Guide" to find out whether

there are any missing periods in the calendars and fiscal year. You have to have 12 periods in a calendar if you are using a 12 period calendar. Resolution: SETUP ALL PERIODS FOR CURRENT AND NEXT FISCAL YEARS. References: ----------[/font][url=https://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=102739.1& blackframe=1][font=Courier][color=#0000ff]Note 102739.1[/color][/font][/url] [font=Courier]3.

DEP - APP-47670 UNABLE TO VALIDATE DEPRECIATION PERIOD

Cause :

When you create a new book in Fixed Assets, Oracle Assets creates 2 rows in fa_deprn_periods. One row that reflects the period prior to the first period in the book you just created. And the second row reflects the current open period for the book. But sometimes the system will fail to insert the prior period row which will cause this problem. The [/font][url=https://metalink.oracle.com/metalink/plsql/showdoc?db=Bug&id=1120926.] [font=Courier][color=#0000ff]Bug 1120926.[/color][/font][/url][font=Courier] Answer: ------If you are missing the one row you have to manually insert the row after getting the necessary information from the script 1. script1: select book_type_code,period_name,period_counter,period_num,fiscal_year, period_open_date,period_close_date,calendar_period_open_date, calendar_period_close_date from fa_deprn_periods where book_type_code='&book'; script2: Insert into fa_deprn_periods (BOOK_TYPE_CODE, PERIOD_NAME, PERIOD_COUNTER, FISCAL_YEAR, PERIOD_NUM, PERIOD_OPEN_DATE , PERIOD_CLOSE_DATE, DEPRECIATION_BATCH_ID, RETIREMENT_BATCH_ID, RECLASS_BATCH_ID, TRANSFER_BATCH_ID, ADDITION_BATCH_ID, ADJUSTMENT_BATCH_ID, DEFERRED_DEPRN_BATCH_ID, CALENDAR_PERIOD_OPEN_DATE, CALENDAR_PERIOD_CLOSE_DATE, CIP_ADDITION_BATCH_ID, CIP_ADJUSTMENT_BATCH_ID, CIP_RECLASS_BATCH_ID, CIP_RETIREMENT_BATCH_ID, CIP_REVAL_BATCH_ID, CIP_TRANSFER_BATCH_ID, REVAL_BATCH_ID, DEPRN_ADJUSTMENT_BATCH_ID) values('<>', '<>', <>, <>,<>,to_date( '<> 00:00:00', 'DD-MON-YYYY HH24:MI:SS'),to_date( '<> 00:00:00', 'DD-MON-YYYY HH24:MI:SS'), 0, 0,

0, 0, 0, 0, 0, to_date( '<> 00:00:00', 'DD-MON-YYYY HH24:MI:SS'), to_date( '<> 00:00:00', 'DD-MON-YYYY HH24:MI:SS'), 0, 0, 0, 0, 0, 0, 0, 0); / If you have an MRC installation you have to run the following scripts #1 and if one row is missing then you have to execute the script #2 in order to insert the necessary row in fa_mc_deprn_periods table too. script #1 select SET_OF_BOOKS_ID,book_type_code,period_name,period_counter,period_num, fiscal_year,period_open_date,period_close_date,calendar_period_open_date, calendar_period_close_date from fa_mc_deprn_periods where book_type_code='&book'; Script #2 insert into fa_mc_deprn_periods( SET_OF_BOOKS_ID, BOOK_TYPE_CODE, PERIOD_NAME, PERIOD_COUNTER, FISCAL_YEAR, PERIOD_NUM, PERIOD_OPEN_DATE , PERIOD_CLOSE_DATE, DEPRECIATION_BATCH_ID, RETIREMENT_BATCH_ID, RECLASS_BATCH_ID, TRANSFER_BATCH_ID, ADDITION_BATCH_ID, ADJUSTMENT_BATCH_ID, DEFERRED_DEPRN_BATCH_ID, CALENDAR_PERIOD_OPEN_DATE, CALENDAR_PERIOD_CLOSE_DATE, CIP_ADDITION_BATCH_ID, CIP_ADJUSTMENT_BATCH_ID, CIP_RECLASS_BATCH_ID, CIP_RETIREMENT_BATCH_ID, CIP_REVAL_BATCH_ID, CIP_TRANSFER_BATCH_ID, REVAL_BATCH_ID, DEPRN_ADJUSTMENT_BATCH_ID) values(

values('<<SET OF BOOKS ID>>','<>', '<>', <>,<>,<>, to_date( '<> 00:00:00', 'DD-MON-YYYY HH24:MI:SS'), to_date( '<> 00:00:00', 'DD-MON-YYYY HH24:MI:SS'), 0, 0, 0, 0, 0, 0, 0, to_date( '<> 00:00:00', 'DD-MON-YYYY HH24:MI:SS'), to_date( '<> 00:00:00', 'DD-MON-YYYY HH24:MI:SS'), 0, 0, 0, 0, 0, 0, 0, 0); 4.CANNOT SEE THE BOOK NAME IN LOV WHEN YOU TRY TO RUN THE ASSET ADDITIONS REPORT. Answer -----Most of the time this issue is due to missing prior period rows in fa_deprn_periods table after creating new book. Try the solution from #4. 5. ERROR APP-00988 ORACLE ERROR 1403 IN GET_DATE WHILE MASS ADDITION POSTING. Error: function fazccp returned failure (called from get_date) APP-47022 Mass Addition ID: 11828 ==> ** FAILED ** APP-47010 Error: Failed to get Prorate Date and Depreciation Start Date Cause: You have a database problem. APP-00988 ORACLE error 1403 in fazgtcp APP-47984 Cache: Error retrieving row from FA_CALENDAR_PERIODS table Cause: You have a database problem. The probable reasons for this problem are: 1) The Mass Addition lines has a Prorate convention which does have gaps in the periods. 2) Fiscal year was not set up. Answer -----1) Query the Prorate Conventions from prepare mass addition screen. 2) Query Prorate Convention form and ensure the periods do not have any gaps. Also check the following scenario. 1) Query the Mass Addition line in the Prepare Mass Additions form and note

the category and DPIS defined for that mass addition line. 2) Query the Asset Category form and note the Prorate Convention assigned to the

category. 3) Query Prorate Convention form and ensure the DPIS on the mass addition line exists in a prorate period, extend the calendar to include this date if necessary.

6. NO VALUES IN LOV FOR THE PERIOD WHILE RUNNING THE REPORTS LIKE FAS540.rdf, COST DETAIL REPORT AND COST SUMMARY REPORT. It checks whether the depreciation has been run at least once by using the following SQL statement. SELECT PERIOD_NAME, PERIOD_NAME VALUE, PERIOD_NAME DESCRIPTION, NVL('N', 'N'), NVL(TO_NUMBER(NULL), -1), NULL, NVL('Y', 'Y'), NVL(TO_CHAR(TO_DATE(NULL), 'J'), 0), NVL(TO_CHAR(TO_DATE(NULL), 'J'), 0) FROM FA_DEPRN_PERIODS WHERE (BOOK_TYPE_CODE = '<>' AND PERIOD_COUNTER > (SELECT MIN(DP2.PERIOD_COUNTER) FROM FA_DEPRN_PERIODS DP2 WHERE DP2.BOOK_TYPE_CODE = '<>')) ORDER BY PERIOD_COUNTER; Answer -----Once you run the depreciation you can see the list of books. 7.

APP-47422 FAXASSET DEFINE PRORATE DATE FOR DATE PLACED IN SERVICE

You are entering an asset Navigate: Assets/Asset Workbench/Quick Additions The placed in service defaults to today's date. When you move past the field, you get the following error message. APP-47442 You must define a prorate date for this date placed in service. Problem Explanation -------------------The next fiscal year and calendar periods for the prorate convention must be defined if you are adding an asset in this period using a following month convention or any prorate convention that maps to a date for which the fiscal year or calendar is not set up. Answer -----1. Set up the next fiscal year

Navigate / Setup / Asset System / Fiscal Years 2. Set up the next calendar period Navigate / Setup / Asset System / Calendars Also, verify that the format of the new calendar period names match the previous calendar periods. 8.

DEPRECATION FAILS WITH

APP-988,ORA-1 UNIQUE CONSTRAINT IN CALENDARS.

Problem Description ------------------You are in Oracle Assets and you are running depreciation. following errors:

It fails with the

At beginning of End of Fiscal Year program Date: 12-JUL-2000 10:33:38 Fiscal Year: 2000 Fiscal Year 2000 is shorter than calendar year Fiscal Year 2001 is shorter than calendar year APP-00988 ORACLE error 1 in faenicp Cause: faenicp failed due to ORA-00001: unique constraint (FA.FA_CALENDAR_PERIODS_U1) violated. The SQL statement being executed at the time of the error was: insert into fa_calendar_periods(calendar_type,start_date,end_date, peri and was executed from the file FAEOFY.LPC. Error: Unable to insert calendar period records Cause: You have a database problem. Action: Contact your system administrator. Error: function faenicp returned failure (called from faeofy) APP-48154 Module End of Fiscal Year ended with error Error: function faeofy returned failure (called from FADEPR) Responsibility = Fixed Assets Manager GUI Navigation = Depreciation/Run GUI Process Name = FADEPR (Depreciation) Explanation ----------When the final depreciation for a fiscal year is run, the depreciation program checks to see that the next fiscal year and calendar have been set up. If the next fiscal year or calendar have not been set up, the program will attempt to create the next year's calendar based on prior year information. If the next fiscal year's calendar is setup incorrectly, depreciation will fail as noted above. This error is most common with non-standard monthly calendars such as 5-4-4, 4-4-5 and 13-month. Answer ------

1. Check the calendar periods for gaps between the To Date and the From Date between periods. Remove any gaps between periods. Gaps in calendar periods for a fiscal year are not allowed. GUI Navigation Path: Asset Manager/Setup/Asset System/Calendars Can run this SQL in order to get calendar information. select to_char(start_date,'DD-MON-YYYY HH24:MI:SS'), to_char(end_date,'DD-MON-YYYY HH24:MI:SS') from fa_calendar_periods where calendar_type = '&calendar' 2. Compare the calendar's From Date for the first calendar period and the To Date of the last period in the calendar's year to the From Date and the To Date of the Fiscal Year. GUI Navigation Path: Asset Manager/Setup/Asset System/Fiscal Years 3. Review the Fiscal Year and confirm that there are no gaps in that year between the prior and the next Fiscal Year Calendar. 4. Verify that all periods have been created in the calendar for the corresponding fiscal year. References ---------[/font][url=https://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=115179.1& blackframe=1][font=Courier][color=#0000ff]Note 115179.1[/color][/font][/url] [font=Courier]9.

APP-47984 IN FAZCCP AND ORA-01403 IN FAZGTCP.

Answer -----You need to setup the calendar as far back as the oldest date placed in service or you could possibly have gaps or overlaps of dates in your calendar. 10.

APP-FND-01564: ORACEL ERROR 1403 IN FADGBI APP-OFA-47131 UNABLE TO GET CURRENT FISCAL YEAR.

Answer -----If you are running depreciation for a period in the current fiscal year, you must define the fiscal calendar for the next fiscal year as well. After completing this step, you should re-submit Depreciation and it should then complete successfully. Because of increased functionality in Oracle Assets Release 11i, it is necessary to define the fiscal calendar at least one year in advance of the current fiscal period for which you are running depreciation. This is due to checks in the code to get the next fiscal year start and end dates (before the current fiscal year is closed) to calculate remaining lives and fiscal year differentials for formula-based depreciation methods. This check is made by book_type_code, regardless of whether you are actually using the formulabased depreciation methods.

References ----------[/font][url=https://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=108280.1& blackframe=1][font=Courier][color=#0000ff]Note 108280.1[/color][/font][/url] [url=https://metalink.oracle.com/metalink/plsql/showdoc?db=Bug&id=1298004][font=Co urier][color=#0000ff]Bug 1298004[/color][/font][/url] [font=Courier]11. APP-00988 ORACLE ERROR 1 IN FAENICP APP-48154 MODULE END OF FISCAL YEAR ENDED WITH ERRORS Answer -----The program is attempting to create next year's calendar based on the prior year information, or the calendar is already setup but is setup with gaps in the dates. References ---------See [/font][url=https://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=115179.1& blackframe=1][font=Courier][color=#0000ff]Note 115179.1[/color][/font][/url] [font=Courier]12. TRYING TO RETIRE AN ASSET FROM THE ASSET WORKBENCH AND GETTING THE FOLLOWING ERROR MESSAGE. APP-48301 Unknown server side error. Please contact your system administrator Called_FN= FA_RETIRE_PKG.INITIALIZE Called_FN FA_RETIREMENTS.INITIALIZE SQLERRM=ORA-01403 :No data found Solution Description -------------------The root cause of problem is that FAXASSET accepted an asset with a "date place in service" that is older than its depreciation calendar for the asset book. You should initially setup all calendar periods from the period corresponding to the oldest date placed in service to the current period. The oldest date placed in service is determined by the 'System Control' options. Navigation: ----------Setup:Asset System:System Controls (Oldest Date Placed in Service) A validation check was created on the FAXASSET.fmb (Asset Workbench) form and is included in Fixed Assets patchset E. Explanation ===========

The following statement causes APP-48301 in retirements: SELECT retirement_prorate_convention use_stl_retirements_flag, stl_method_code, stl_life_in_months INTO X_Ret_Prorate_Convention, X_Use_STL_Retirements_Flag, X_STL_Method_Code, X_STL_Life_In_Months FROM fa_category_book_defaults WHERE book_type_code = X_Book_Type_Code and category_id = and between start_dpis and nvl(end_dpis,); Where the LV_Date_Placed_In_Service in this case was 31-JAN-95 References ---------FA User guide p 9-25, [/font][url=https://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=106718.1& blackframe=1][font=Courier][color=#0000ff]Note 106718.1[/color][/font][/url] [font=Courier]13. UNABLE TO RUN INITIAL MASS COPY ON TAX BOOK AND ENDS WITH FOLLOWING ERRORS. APP-00988 ORACLE error 1403 in famci Previous Messages (for SupportPurposes) APP-00406 No message explanation found for message '&MESSAGE' Error:Initial Mass Copy failed to obtain book controls information Answer -----This could be due to period mismatch between your CORP and TAX book. An initial mass copy into a tax book in 2000(For example) would require that there is a corporate period of the same period. Reference the User's Guide for release 11, chapter 7, 1 thorugh page 11, which explains both initial mass copy and periodic mass copy. The calendar was defined way back, but there were no actual depreciation periods for those time frames. (When assets are added to a particular period, it has to be opened and defined. After additions, activities, etc. are performed in a corporate book, depreciation is performed for that book and should close that period. Then, the mass copy is performed and the activities are copied into the tax book which is open for the period the corp book was just closed for. After successful mass copy, the tax book depreciation is run for that period and it is closed.) Use the following SQL to find out both open and closed periods in CORP book and TAX book. select period_counter,period_name

from fa_deprn_periods where book_type_code = '&book'; 14.

USEFUL DIAGNOSTIC SCRIPTS

------------------------------------------------------------------ | Script #1: To get the book control info ------------------------------------------------------------------ | select fab.book_type_code,fab.deprn_calendar,fab.prorate_calendar, fab.fiscal_year_name, fab.deprn_status,fab.current_fiscal_year from fa_book_controls fab where fab.book_type_code='&book' and fab.book_type_code IN (select book_type_code from fa_deprn_periods where period_close_date IS NULL); ------------------------------------------------------------------ | Script #2: To get the info from deprn_periods ------------------------------------------------------------------ | select book_type_code,period_name,period_counter,period_num,fiscal_year, period_open_date,period_close_date,calendar_period_open_date, calendar_period_close_date from fa_deprn_periods where book_type_code='&book' order by 3; ------------------------------------------------------------------ | Script #3: To get the calendar information ------------------------------------------------------------------ | select calendar_type,start_date,end_date,period_num,period_name from fa_calendar_periods where calendar_type='&calendertype' order by 2; ------------------------------------------------------------------ | Script #4: To get the fiscal year name ------------------------------------------------------------------ | select calendar_type,description,period_suffix_type, number_per_fiscal_year,fiscal_year_name from fa_calendar_types where calendar_type='&calendertype'; ------------------------------------------------------------------ | Script #5: To get the FY info from fa_fiscal_year ------------------------------------------------------------------ | select fiscal_year_name,fiscal_year,start_date,end_date from fa_fiscal_year where fiscal_year_name='&fyname' order by 2;

NOTE 1: BEFORE APPLYING ANY OF THE DATA FIX SCRIPT FROM ANY SOLUTIONS, PLEASE CONTACT SUPPORT GROUP FOR AUTHENTICITY AND ACCURACY OF THE FIXES IN ORDER TO AVOID FURTHER DATA CORRUPTIONS SINCE DATAFIXES/SOLUTIONS MIGHT ADDRESS TO ONE SPECIFIC SCENARIO. NOTE 2: PLEASE MAKE SURE TO APPLY ANY OF THE DATA FIXES FROM ANY SOLUTIONS FIRST IN THE TEST INSTANCE AND CHECK THE ACCURACY OF THE DATA AFTER THE DATA FIX. [b]*** *** [/b] Help us improve our service. If you have any comments or questions regarding the solution as documented in this Note (or ANY other questions related to Oracle Assets), please post on the Oracle Assets Technical Forum at the following URL: http://metalink.oracle.com/metalink/plsql/for_main.fetchForum?p_forum_id=73&p_afte r_post=N&p_forum_scope=a&p_forum_time=7 The FA Forum is monitored on a daily basis by Oracle Support Services (OSS), and response time is generally within 24 hours. Thank you for using MetaLink [/font]

ҳ: [1] � ����汾: Oracle Assets Troubleshooting Guide for Setup - Calendars Powered by Discuz! Archiver 7.0.0

© 2001-2009 Comsenz Inc.