Académique Documents
Professionnel Documents
Culture Documents
��ϸ�ĵ����������ôϲ��ERP100��Ϊʲô���Ѹ��ռ
˿ 佨 b � � ERP100 ?
CONTENTS
--------
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.
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
13. UNABLE TO RUN INITIAL MASS COPY ON TAX BOOK. NO CALENDAR ASSOCIATED?
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
------
Answer
------
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.
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
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]
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:
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
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.
1) The Mass Addition lines has a Prorate convention which does have gaps in
the periods.
2) Fiscal year was not set up.
Answer
------
2) Query Prorate Convention form and ensure the periods do not have any gaps.
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.
ORDER BY PERIOD_COUNTER;
Answer
------
Once you run the depreciation you can see the list of books.
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
------
Also, verify that the format of the new calendar period names match the
previous calendar periods.
Problem Description
-------------------
You are in Oracle Assets and you are running depreciation. It fails with the
following errors:
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.
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.
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]
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.
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.
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]
Called_FN FA_RETIREMENTS.INITIALIZE
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)
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 = <LV_Category_Id>
and <LV_Date_Placed_In_Service> between start_dpis and
nvl(end_dpis,<LV_Date_Placed_In_Service>);
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.
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';
------------------------------------------------------------------ |
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.
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.