問題記錄_FA_APP-OFA-48392 Error When Adding a New Asset in the Asset Workbench

APP-OFA-48392 Error When Adding a New Asset in the Asset Workbench [ID 275200.1]
		修改时间 04-DEC-2008     类型 PROBLEM     状态 PUBLISHED

Applies To

Oracle Assets - Version: 11.5.9
This problem can occur on any platform.
FAXASSET - Asset Workbench 

Symptoms

When adding a new asset in Asset Workbench, in the Assignments window, when 
clicking Done, an error message appears: 

APP-OFA-48392: Unable to get the concurrent request status using procedure.

Cause

Invalid depreciation run status showing as 'Submitted'.

Fix

Change the Status to 'Error', resubmit Run Depreciation and let it complete
normally, rollback depreciation, then enter new assets.

1) Refresh a TEST instance with the Production data when experiencing this issue.

2) Run this update:

update fa_book_controls
set deprn_status = 'E'
where book_type_code = '&book'
and deprn_status = 'S';
commit;

3) Resubmit Run Depreciation WITHOUT Close Period option.

4) Rollback Depreciation.

Always TEST results prior to implementing in a Production database.

---

IMPORTANT
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 on MetaLink. 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!

問題記錄_FA_Create Accounting ERROR MESSAGE NUMBER:95937

Symptoms
----------------------------------------------------------------------------------------------------------------
於固定資產模組下，執行創建會計請求(Create Accounting)後，檢視輸出的報表(Subledger Accounting Program Report)，內容顯示錯誤訊息：

Message Number:
95937
Message:
There are either non-accountable events existing in the system, or events which could not be processed because no data could be found on transaction objects. Please enable the profile option SLA: Enable Diagnostics,create accounting again, and run the report Transaction Objects Disagnostics to identify the problem.


Cause
----------------------------------------------------------------------------------------------------------------
造成此錯誤的原因主要分為兩項：
1.Oracle Patch Needed.
2.Unprocessed Records Exists(Orphan Records).


其中Patch是在Oracle Support查詢時，幾乎所有的資料都顯示要打這個Patch:8738842。另外在查詢會計事件的時候，也發現了有未處理並沒有產生分錄的事件(Accounting Events)。
經過Reproduce後，基本上確認是用戶手動新增固定資產後，又手動將其資產刪除，造成Orphan Records所引起的錯誤。


Solution
----------------------------------------------------------------------------------------------------------------
1)先執行Apps Check(可略過)：
Please run the Diagnostics: Apps Check program for Oracle Assets

If the program doesn't exist, please add the program as follows
Sysadmin > Security > Responsibility > Request

Query the request as follows
Group - All reports
Application - Assets

And add the Diagnostics: Apps Check as follows
Type - Program
Name - from the list of value select Diagnostics: Apps Check
Application - Oracle Order Management

Save the changes. Now you can run the Diagnostics: Apps Check with
Assets as Parameter


依自身系統環境進行參數輸入，並檢查輸出的報表。


2)檢查下列Query：
Select bug_number, creation_date from ad_bugs where bug_number IN('8738842');


Select owner,object_name,object_type, status From all_objects Where status = 'INVALID' And object_name LIKE 'FA%';


3)在固定資產模組下查詢到未處理並沒有分錄的事件(Inquiry->Subledger Accounting->Accounting Events)。


4)執行下列Query檢查分錄事件表單(Table)，可依情況自行修改一些ID參數：
SELECT xlt.ledger_id,
xlt.valuation_method,
xe.event_id,
xlt.entity_id,
xe.event_type_code,
xe.event_status_code,
xlt.transaction_number,
xe.event_date
FROM xla_events xe,
xla.xla_transaction_entities xlt
WHERE xe.entity_id = xlt.entity_id
AND xe.application_id = xlt.application_id
AND xlt.source_application_id = 140
AND xlt.entity_code = 'TRANSACTIONS'
AND xe.event_status_code <> 'P'
AND NOT EXISTS (SELECT fth.transaction_header_id
FROM fa_transaction_headers fth
WHERE fth.transaction_header_id = xlt.source_id_int_1);


5)備份及刪除表單中的Orphan Events
To implement the solution, please execute the following steps:

1. Ensure that you have taken a backup of your system before applying the recommended solution.

2. Run the following scripts in a TEST environment first:

a. Create table to list down the orphan records.

CREATE TABLE fa_orphan_events AS
SELECT xlt.ledger_id,
xlt.valuation_method,
xe.event_id,
xlt.entity_id,
xe.event_type_code,
xe.event_status_code,
xlt.transaction_number,
xe.event_date
FROM xla_events xe,
xla.xla_transaction_entities xlt
WHERE xe.entity_id = xlt.entity_id
AND xe.application_id = xlt.application_id
AND xlt.source_application_id = 140
AND xlt.entity_code = 'TRANSACTIONS'
AND xe.event_status_code <> 'P'
AND NOT EXISTS (SELECT fth.transaction_header_id
FROM fa_transaction_headers fth
WHERE fth.transaction_header_id = xlt.source_id_int_1);

b. Create Backup tables

CREATE TABLE xla_transaction_entities_bk
AS SELECT * FROM xla_transaction_entities xte
WHERE xte.application_id = 140
AND EXISTS (
SELECT xe.entity_id
FROM xla_events xe,fa_orphan_events oe
WHERE xe.event_id = oe.event_id
AND xe.entity_id = xte.entity_id
AND xe.application_id = 140);

CREATE TABLE xla_events_bk
AS SELECT * FROM xla_events xe
WHERE EXISTS (
SELECT oe.event_id
FROM fa_orphan_events oe
WHERE xe.event_id = oe.event_id)
AND xe.application_id = 140;


c. Delete the unwanted orphan records



DELETE FROM xla_transaction_entities xte
WHERE xte.application_id = 140
AND EXISTS (
SELECT oe.entity_id
FROM fa_orphan_events oe
WHERE oe.entity_id = xte.entity_id);

DELETE FROM xla_events xe
WHERE xe.application_id = 140
AND EXISTS (
SELECT oe.event_id
FROM fa_orphan_events oe
WHERE xe.event_id = oe.event_id);

COMMIT;

3. If you are satisfied with the results, issue a commit.

4. Confirm that the data is corrected when viewed in the Oracle Applications.

You can do this by running Sub-ledger Period Close Exception Report.

5. If you are satisfied that the issue is resolved, migrate the solution as appropriate to other environments.


6)再次執行Create Accounting請求，並確認錯誤訊息解除。

問題記錄_OFA_R12 APP-OFA-48392 Unable to Get The Concurrent Request Status Using Procedure FND_CONCURRENT.GET_REQ

Problem Description: When add a new asset till to the final step, the error request(R12 APP-OFA-48392 Unable to Get The Concurrent Request Status Using Procedure FND_CONCURRENT.GET_REQ) would be popup.

I find out the [ID 199678.1] in metalink resources, and the case just like what we happened, then I follow the steps to slove this problem.

It's what done about PL/SQL code below.
SQL> update fa_book_controls
SQL> set deprn_request_id = NULL,
SQL> deprn_status = 'E'
SQL> where deprn_status = 'S'
SQL> and book_type_code = '&book_type_code';

But it still doesn't work, we can't add new asset record. And I re-run depreciation then popup an Error winows, messeage below:
APP-OFA-48398: Program exited with errors:
ORA-00054:resource busy and acquire with NOWAIT specified
Error:function FA_CHK_BOOKSTS_PKG.faxlck returned failure
A mass transaction is pending for this book. please complete it and try again. Failed to obtain lock on FA_BOOK_CONTROLS row for book &book_type_code.
Error:function FA_CHK_BOOKSTS_PKG.faxlc returned failure
Error:function FA_CHK_BOOKSTS.faxcbs returned failure
Module CHECK_BOOK_STATUS ended with error
Error:function FA_CHK_BOOKSTS_PKG.faxcbsx returned failure

---------------------以下是回覆---------------------

Comments
--------
=== ODM Action Plan ===

Please provide the following results:

1.Please run the Diagnostics: Apps Check program for Oracle Assets and upload the output to this SR.
Sysadmin > Security > Responsibility > Request
Query the request as follows:
Group - All reports
Application - Oracle Assets

Now add the Diagnostics: Apps Check as follows
Type - Program
Name - from the list of value select Diagnostics: Apps Check
Application - Order Management
Save the changes.
Now you can run the Diagnostics: Apps Check with Assets as Parameter

2. Please run the following select script to identify any locks for FA (Fixed Assets) objects and upload the result:

SELECT *
FROM v$locked_object a , all_objects b
WHERE a.object_id = b.object_id
AND b.object_name like 'FA%';

3. Run the query below and upload the result:

select book_type_code, mass_request_id,
deprn_status,deprn_request_id from FA_BOOK_CONTROLS
where book_type_code = '&book';

------------------分隔線---------------------

Comments
--------
Hello,

Your issue has been transferred to me now. I will be helping on the same.

The Depreciation status is 'S'. Please go through Note 567038.1 where you will find the complete datafix. Please appy that datafix and provide us feedback.

Regards,

-------------------解決方案------------------

When attempting to run depreciation got APP-OFA-48397 Program exited with errors [ID 567038.1]

Modified 04-DEC-2008     Type PROBLEM     Status PUBLISHED

In this Document
  Symptoms
  Cause
  Solution
  References

Applies to:

Oracle Assets - Version: 11.5.10

This problem can occur on any platform.

Symptoms

When attempting to to run depreciation for the books 

the following error message appears in the form 

ERROR 

----------------------- 

APP-OFA-48397 Program exited with errors 

unable to get the concurrent request status using procedure 

FND_CURRENT.GET_REQUEST_STATUS 

Module CHECK_BOOK_STATUS ended with error 

Cause

The DEPRN_STATUS in the FA_BOOK_CONTROLS table was incorrectly set 

to 'S' after a failed depreciation run. 

Solution

Verify the book status -

SQL> select book_type_code, deprn_request_id, mass_request_id, deprn_status
SQL> from fa_book_controls
SQL> where book_type_code = '&book_type_code';

Please log an iTAR for guidance on the following steps:

If the deprn_status is anything other that 'S', DO NOT PROCEED with resetting
the status.

Check to make sure there are no records in FA_DEPRN_DETAIL and FA_DEPRN_SUMMARY
tables.

1. get the period_counter.

SQL> select period_counter
SQL> from fa_deprn_periods
SQL> where book_type_code = '&book_type_code'
SQL> and period_close_date is null;

The period_counter is the current period counter number associated with the
period you are trying to run depreciation for, and the book_type_code is the
name of your Asset Book.

2. Check the FA_DEPRN_DETAIL and FA_DEPRN_SUMMARY tables for records :

SQL> select count(*)
SQL> from fa_deprn_summary
SQL> where book_type_code = '&book_type_code'
SQL> and period_counter = &period_counter
SQL> and deprn_amount is not null;

SQL> select count(*)
SQL> from fa_deprn_detail
SQL> where book_type_code = '&book_type_code'
SQL> and period_counter = &period_counter
SQL> and deprn_amount is not null;

If the step 2 return rows 0 rows then run the following script

SQL> update fa_book_controls
SQL> set deprn_request_id = NULL,
SQL> deprn_status = 'E'
SQL> where deprn_status = 'S'
SQL> and book_type_code = '&book_type_code';

NOTE: Never under any circumstances update the deprn_status to 'C' for
'Complete'.

3.If the SQL in step 2 returns rows follow the below steps

This task should be performed by the System Administrator/DBA:
To implement the solution, please execute the following steps:
A) Take backup of depreciation tables:

create table FA_DEPRN_DETAIL_bkp as select * from FA_DEPRN_DETAIL
where PERIOD_COUNTER=
and book_type_code='&&book';

create table FA_DEPRN_SUMMARY_bkp as select * from FA_DEPRN_SUMMARY
where PERIOD_COUNTER=
and book_type_code='&&book';

B)Delete the lines that where inserted by depreciation process:
1. delete from FA_DEPRN_DETAIL
where PERIOD_COUNTER=
and book_type_code='&&book';

2. delete from FA_DEPRN_SUMMARY
where PERIOD_COUNTER=
and book_type_code='&&book';

commit;

C) Then update depreciation status in FA_BOOK_CONTROLS:
update fa_book_controls
set deprn_request_id = NULL,
mass_request_id = NULL,
deprn_status = 'E'
where deprn_status = 'S'
and book_type_code='&&book';
commit;

D) Submit depreciation again.

References

NOTE:438507.1 - Unable To Run Depreciation Or To Rollback Depreciation. Fail To Get Lock On FA_BOOK_CONTROLS

NOTE:199678.1 - Depreciation Ends with Error in FND_CONCURRENT.GET_REQUEST_STATUS

 Related

Products

• Oracle E-Business Suite > Financial Management > Assets & Real Estate > Oracle Assets

Errors

APP-OFA-48397

業務_OFA_關閉期間(關帳)

1)進入「資產管理超級用戶」的權限。

2)進入「折舊->執行折舊」。

3)彈出執行折舊視窗。

4)選取帳本及期間，並且勾選關閉期間，執行。

5)執行後會觸發一個請求組。

6)待請求完成後即關閉此期間，並且將無法重新開啟。