EBS:AR 创建会计科目请求效率低的解决步骤
来自于Metalink 的解答:
Please ensure the following has been done.
Please follow Doc ID 791049.1 : R12 SLA/FAH: How to Improve Performance in @ Subledger Accounting & Financials Accounting Hub and verify whether customer is you are on latest patches, and optimal setting on Parameters .
Ensure you have done all of the following:
1.
a] You must run "Gather Schema Statistics" for AR and XLA (I will verify the logs and outputs of these reports)
b] Please check profile option "SLA: Diagnostics Enabled" should be set to No at all trhe levels including the User Level
c] System Administrator -> Requests -> Run. Submit the concurrent request "Purge Concurrent Request and/or Manager Data" specifying with 'Count' mode using the following parameter:
Entity=All
Mode=Count
Mode Value=5000
Report =Yes
Purge other =Yes
d] From Responsibility: 'System Adminstrator'.
Concurrent:Program > Define.
Query for program with short name XLAACCPB.
If there is no value in Options, try adding '-Xmx2048M' in the Options field and save the record.
Retest the issue.
e]
As System Administrator: Navigate to Concurrent->Program->Define
Query up the report with short name XLAACCPB
Add a parameter named ScalableFlag:
Value Set: yes_no
Default Value: Yes
Select check boxes Enable and Required
Do not select the check box Displayed, or users could turn this off at runtime.
Token needs to be ScalableFlag (this is a case sensitive value).
2.
The latest SLA/FAH Performance patches as of date as documented in DOC ID 791049.1should be applied including the Patch 13543605 .
3.
SQL> truncate table xla.XLA_DIAG_SOURCES
SQL> truncate table xla.XLA_DIAG_EVENTS
SQL> exec DBMS_STATS.DELETE_TABLE_STATS ('AR', 'AR_XLA_LINES_EXTRACT');
SQL> exec DBMS_STATS.DELETE_TABLE_STATS ('XLA', 'XLA_EVENTS_GT');
4.Ensure The following profile options are set to atleast these values
Concurrent: OPP Processing Timeout =80000
Concurrent: OPP Response Timeout=8000
5.
Please retest the issue after all teh above steps and advice results.
Please follow Doc ID 791049.1 : R12 SLA/FAH: How to Improve Performance in @ Subledger Accounting & Financials Accounting Hub and verify whether customer is you are on latest patches, and optimal setting on Parameters .
Ensure you have done all of the following:
1.
a] You must run "Gather Schema Statistics" for AR and XLA (I will verify the logs and outputs of these reports)
b] Please check profile option "SLA: Diagnostics Enabled" should be set to No at all trhe levels including the User Level
c] System Administrator -> Requests -> Run. Submit the concurrent request "Purge Concurrent Request and/or Manager Data" specifying with 'Count' mode using the following parameter:
Entity=All
Mode=Count
Mode Value=5000
Report =Yes
Purge other =Yes
d] From Responsibility: 'System Adminstrator'.
Concurrent:Program > Define.
Query for program with short name XLAACCPB.
If there is no value in Options, try adding '-Xmx2048M' in the Options field and save the record.
Retest the issue.
e]
As System Administrator: Navigate to Concurrent->Program->Define
Query up the report with short name XLAACCPB
Add a parameter named ScalableFlag:
Value Set: yes_no
Default Value: Yes
Select check boxes Enable and Required
Do not select the check box Displayed, or users could turn this off at runtime.
Token needs to be ScalableFlag (this is a case sensitive value).
2.
The latest SLA/FAH Performance patches as of date as documented in DOC ID 791049.1should be applied including the Patch 13543605 .
3.
SQL> truncate table xla.XLA_DIAG_SOURCES
SQL> truncate table xla.XLA_DIAG_EVENTS
SQL> exec DBMS_STATS.DELETE_TABLE_STATS ('AR', 'AR_XLA_LINES_EXTRACT');
SQL> exec DBMS_STATS.DELETE_TABLE_STATS ('XLA', 'XLA_EVENTS_GT');
4.Ensure The following profile options are set to atleast these values
Concurrent: OPP Processing Timeout =80000
Concurrent: OPP Response Timeout=8000
5.
Please retest the issue after all teh above steps and advice results.
优质生活从拆开始