Performance issue on Fiscal period.

HI all,
I have multiprovider built on an infoset.The infoset is built on 3 stadard ODS(0FIGL_O02,0PUR_O01,0PUR_DS03).The user is running the report by Company code and Fiscal Period.
The Company Code and Fiscal period is available only for FI-GL ODS.The purchasing os has only Fiscal Variant time characterstic.When i am trying to runt he report,its taking unusually long time to run.
How should i resolve this performance issue?
1)will getting Fiscal period into Purchasing ods help improve the performance.If so can anyone please give me step by step procees.As this is very urgent.
2) Or should i take any other method to improve the performance.Th FI-GL already has secondary indexes on it.
Please advise.
Message was edited by:
sap novice

Duplicate post:
Performance issue on AFPO
Performance issue on AFPO

Similar Messages

Filter issue in fiscal period (urgent).

Hi all
I am facing issue on fiscal period in Query.
Please find the case and guide me to solve this issue.
Case: I am using 0fiscper in my report.
when we try to keep filter on on 0fiscper in Bex Analyser
It is working fine for SIngle value and Between.
But It is giving Following Error for Lessthan, Lessthan Equal, Greate than and Greater Equal.
Error:
Program error in class SAPMSSY1method: UNCAUGHT_EXCEPTION
An exception with the type CX_SY_CONVERSION_NO_NUMBER occured but was neither han...
The Argument 'Z4200801'can not be interpreted as number.
Thanks
sreelatha

did u unknowingly change some settings
if u login to rsa1---> infoobject
find ofiscper and then click change
go to business explorer tab and check for various setting related to
filter values at query definition, query execution etc.
try this and let us know.

Performance issue - APEX hanging periodically

We have several hundred users that use our APEX applications and every now and then we are experiencing a freeze where an attempt to navigate or submit from a page results in a lengthy wait, sometimes for up to five minutes. During this time, we have been able to use terminal services to log in to the DB Server and the CPU is quiet and all appears to be fine.
Our network folks tell us all is fine and the DBA has looked for problems and apparently there are no problems so we are at a loss at what to do or where to look.
We've had a few errors in the error log but these are related to favicon images, a few 500s but these don't match up with the outage times and a few days ago an error due to "server ran out of threads" so we raised the ThreadsPerChild setting from 50 to 100 and restarted the http server. Sadly the problem appeared again today and twice (to our knowledge) we and presumably some other users experienced outages of 3-4 minutes twice.
If anyone can suggest something we can do to try and identify what is causing this we'd be very grateful.
Oracle 10.2 Windows
2003 Server
APEX 3.1.1

Hi Phil,
1. Apache access does appear to match up - I've had a look and the activity seems fine, several lines are present per second generally and then we lose three minutes - there is just a gap with nothing captured.Having a three minutes gap in the Apache access logs strongly points to a network/server issue. I think you should ask your network/apache admins to enable some tracing to find out why the requests are not coming through to the Apache server.
3. No, we do see a 251 THINK_TIME associated with a 2.98 ELAPSED_TIME. How is this interpreted?The THINK_TIME is a on the fly calculated value based on the time between the current and the previous request for that user and session id. Only the ELAPSED_TIME is relevant. It shows you how long it took to process the request in the APEX framework.
Regards
Patrick
My Blog: http://www.inside-oracle-apex.com
APEX Plug-Ins: http://apex.oracle.com/plugins
Twitter: http://www.twitter.com/patrickwolf

Cube Refresh Performance Issue

We are facing a strange performance issue related to cube refresh. The cube which used to take 1 hr to refresh is taking around 3.5 to 4 hr without any change in the environment. Also, the data that it processes is almost the same before and now. Only these cube out of all the other cubes in the workspace is suffering the performance issue over a period of time.
Details of the cube:
This cube has 7 dimensions and 11 measures (mix of sum and avg as aggregation algorithm). No compression. Cube is partioned (48 partitions). Main source of the data is a materialized view which is partitioned in the same way as the cube.
Data Volume: 2480261 records in the source to be processed daily (almost evenly distributed across the partition)
Cube is refreshed with the below script
DBMS_CUBE.BUILD(<<cube_name>>,'SS',true,5,false,true,false);
Has anyone faced similar issue? Please can advise on what might be the cause for the performance degradation.
Environment - Oracle Database 11g Enterprise Edition Release 11.2.0.3.0
AWM - awm11.2.0.2.0A

Take a look at DBMS_CUBE.BUILD documentation at http://download.oracle.com/docs/cd/E11882_01/appdev.112/e16760/d_cube.htm#ARPLS218 and DBMS_CUBE_LOG documentation at http://download.oracle.com/docs/cd/E11882_01/appdev.112/e16760/d_cube_log.htm#ARPLS72789
You can also search this forum for more questions/examples about DBMS_CUBE.BUILD
David Greenfield has covered many Cube loading topics in the past on this forum.
Mapping to Relational tables
Re: Enabling materialized view for fast refresh method
DBMS CUBE BUILD
CUBE_DFLT_PARTITION_LEVEL in 11g?
Reclaiming space in OLAP 11.1.0.7
Re: During a cube build how do I use an IN list for dimension hierarchy?
.

Issues with statistical modeling in calendar months vs 13 fiscal periods

In our demand planning, we plan at the fiscal period level (13 fiscal periods across a year - not matching with calendar months or year). We are having issues (strange results) trying to run the statistical modeling at the fiscal period level versus the calendar month level. Is there a way to run the stat modeling over fiscal periods rather than calendar months? Can we run stat modeling over a specific date range rathn than including the current month?

Hi Stephen, I guess I can assume the following:
1) In the master forecast profile, you have maintained the period indicator and the fiscal year variant
2) You are choosing a forecast strategy in univariate profile (?) that makes use of seasonality, and you are trying to maintain the number of periods in a season as 13 (in our case, our periods are custom, but there are still 12 periods, so different from your case)
3) Your history horizon in master forecast profile is more than the number of periods in the season i.e. history has more than 13 periods of data
If above things are already done and you still face issue when you try to use 13 periods in a season, looks to me like a SAP bug, and it would be best to raise an OSS message to SAP.

FIscal Period Issue

Hi All,
I need to create variable for fiscal year/period but in my data source don't have fiscal period field. my data source is 2lis_04_p_arbpl. So please could anyone tell me how to solve this issue it's urjent.
Thanks & Regards,
Rajesh.

Hi Rajesh,
Create variable on the top of Fiscal year/period -- this holds the fiscal period only.
You said you are having Fiscal year/period field right which is nothing but fiscal period.
if you want to extract the data for fiscal period follow the below steps...
if fiscal period is not part of you data source -- you can add the Fiscal year/period field in DSO/IC and map the date field from the source the conversion will be taken care automatically while loading the data.
enter fiscal variant as constant - V3 or 01 -- as this is not used in your reports ....
You can use 0ACT_START -- actual start date ... or check with functional team...
Regards
KP

Issue creating planning query on cube partitioned by fiscal period

I have a cube that is partitioned by fiscal period (0FISCPER). This requires that there is a constant value for fiscal year variant (0FISCVARNT). When I try to create an agg level on this cube 0FISCVARNT is automatically pulled into the agg level. However, because 0FISCVARNT is set to a constant value it is not available in query designer to add into a planning query...as such, I cannot create a planning query on this cube.
I can repartition the cube (i.e. remove the partitioning), but does anyone know of any other work arounds?
Thanks.

We resolved this.

Fiscal Period and Calmonth issue in SSM 7.0

In Fiscvar V3 Where Fiscal Year is not from Jan to Dec but April to Mar, PAS not reading Fiscal Period correctly.
Workaround suggested is to Create BWFISCPERINFO document in PAS under the model and mention periodicity as
MONTHLY
2009001 200904
which means ist Fiscal Period of 2009 = 4th Month(april) of 2009.
The BW Query with oFiscper as Time Dimension is not importing data beyond March 2009 while BW Query
with 0Calmonth is populating upto current month of July 2009. What could be reason for this anaomaly in data import ?
M Akhtar

Good day M Akhtar,
I would suggest rechecking your BW Query with oFiscper to make sure that you have set the fiscal period to start in March and not set the data to be imported to only be March. It may be that your current settings are only bringing in the data for March.
Regards,
Bob

QUERY PERFORMANCE AND DATA LOADING PERFORMANCE ISSUES

WHAT ARE QUERY PERFORMANCE ISSUES WE NEED TO TAKE CARE PLEASE EXPLAIN AND LET ME KNOW T CODES...PLZ URGENT
WHAT ARE DATALOADING PERFORMANCE ISSUES WE NEED TO TAKE CARE PLEASE EXPLAIN AND LET ME KNOW T CODES PLZ URGENT
WILL REWARD FULL POINT S
REGARDS
GURU

BW Back end
Some Tips -
1)Identify long-running extraction processes on the source system. Extraction processes are performed by several extraction jobs running on the source system. The run-time of these jobs affects the performance. Use transaction code SM37 Background Processing Job Management to analyze the run-times of these jobs. If the run-time of data collection jobs lasts for several hours, schedule these jobs to run more frequently. This way, less data is written into update tables for each run and extraction performance increases.
2)Identify high run-times for ABAP code, especially for user exits. The quality of any custom ABAP programs used in data extraction affects the extraction performance. Use transaction code SE30 ABAP/4 Run-time Analysis and then run the analysis for the transaction code RSA3 Extractor Checker. The system then records the activities of the extraction program so you can review them to identify time-consuming activities. Eliminate those long-running activities or substitute them with alternative program logic.
3)Identify expensive SQL statements. If database run-time is high for extraction jobs, use transaction code ST05 Performance Trace. On this screen, select ALEREMOTE user and then select SQL trace to record the SQL statements. Identify the time-consuming sections from the results. If the data-selection times are high on a particular SQL statement, index the DataSource tables to increase the performance of selection (see no. 6 below). While using ST05, make sure that no other extraction job is running with ALEREMOTE user.
4)Balance loads by distributing processes onto different servers if possible. If your site uses more than one BW application server, distribute the extraction processes to different servers using transaction code SM59 Maintain RFC Destination. Load balancing is possible only if the extraction program allows the option
5)Set optimum parameters for data-packet size. Packet size affects the number of data requests to the database. Set the data-packet size to optimum values for an efficient data-extraction mechanism. To find the optimum value, start with a packet size in the range of 50,000 to 100,000 and gradually increase it. At some point, you will reach the threshold at which increasing packet size further does not provide any performance increase. To set the packet size, use transaction code SBIW BW IMG Menu on the source system. To set the data load parameters for flat-file uploads, use transaction code RSCUSTV6 in BW.
6)Build indexes on DataSource tables based on selection criteria. Indexing DataSource tables improves the extraction performance, because it reduces the read times of those tables.
7)Execute collection jobs in parallel. Like the Business Content extractors, generic extractors have a number of collection jobs to retrieve relevant data from DataSource tables. Scheduling these collection jobs to run in parallel reduces the total extraction time, and they can be scheduled via transaction code SM37 in the source system.
8). Break up your data selections for InfoPackages and schedule the portions to run in parallel. This parallel upload mechanism sends different portions of the data to BW at the same time, and as a result the total upload time is reduced. You can schedule InfoPackages in the Administrator Workbench.
You can upload data from a data target (InfoCube and ODS) to another data target within the BW system. While uploading, you can schedule more than one InfoPackage with different selection options in each one. For example, fiscal year or fiscal year period can be used as selection options. Avoid using parallel uploads for high volumes of data if hardware resources are constrained. Each InfoPacket uses one background process (if scheduled to run in the background) or dialog process (if scheduled to run online) of the application server, and too many processes could overwhelm a slow server.
9). Building secondary indexes on the tables for the selection fields optimizes these tables for reading, reducing extraction time. If your selection fields are not key fields on the table, primary indexes are not much of a help when accessing data. In this case it is better to create secondary indexes with selection fields on the associated table using ABAP Dictionary to improve better selection performance.
10)Analyze upload times to the PSA and identify long-running uploads. When you extract the data using PSA method, data is written into PSA tables in the BW system. If your data is on the order of tens of millions, consider partitioning these PSA tables for better performance, but pay attention to the partition sizes. Partitioning PSA tables improves data-load performance because it's faster to insert data into smaller database tables. Partitioning also provides increased performance for maintenance of PSA tables for example, you can delete a portion of data faster. You can set the size of each partition in the PSA parameters screen, in transaction code SPRO or RSCUSTV6, so that BW creates a new partition automatically when a threshold value is reached.
11)Debug any routines in the transfer and update rules and eliminate single selects from the routines. Using single selects in custom ABAP routines for selecting data from database tables reduces performance considerably. It is better to use buffers and array operations. When you use buffers or array operations, the system reads data from the database tables and stores it in the memory for manipulation, improving performance. If you do not use buffers or array operations, the whole reading process is performed on the database with many table accesses, and performance deteriorates. Also, extensive use of library transformations in the ABAP code reduces performance; since these transformations are not compiled in advance, they are carried out during run-time.
12)Before uploading a high volume of transaction data into InfoCubes, activate the number-range buffer for dimension IDs. The number-range buffer is a parameter that identifies the number of sequential dimension IDs stored in the memory. If you increase the number range before high-volume data upload, you reduce the number of reads from the dimension tables and hence increase the upload performance. Do not forget to set the number-range values back to their original values after the upload. Use transaction code SNRO to maintain the number range buffer values for InfoCubes.
13)Drop the indexes before uploading high-volume data into InfoCubes. Regenerate them after the upload. Indexes on InfoCubes are optimized for reading data from the InfoCubes. If the indexes exist during the upload, BW reads the indexes and tries to insert the records according to the indexes, resulting in poor upload performance. You can automate the dropping and regeneration of the indexes through InfoPackage scheduling. You can drop indexes in the Manage InfoCube screen in the Administrator Workbench.
14)IDoc (intermediate document) archiving improves the extraction and loading performance and can be applied on both BW and R/3 systems. In addition to IDoc archiving, data archiving is available for InfoCubes and ODS objects.
Hope it Helps
Chetan
@CP..

How to Improve performance issue when we are using BRM LDB

HI All,
I am facing a performanc eissue when i am retriving the data from BKPF and respective BSEG table....I see that for fiscal period there are around 60lakhs records. and to populate the data value from the table to final internal table its taking so much of time.
when i tried to make use of the BRM LDB with the SAP Query/Quickviewer, its the same issue.
Please suggest me how to improve the performance issue.
Thanks in advance
Chakradhar

Moderator message - Please see Please Read before Posting in the Performance and Tuning Forum before posting - post locked
Rob

ICR Performance issue

Hi,
We are facing performance issues in ICR process (003) while data selection and in data assignment,
our client has problem for some company codes having large number of open items for that we wanted to use seperate selection process check box for that company's which no of open items in FBIC032 and also we have selected Minimize no of RFC calls in FBIC010.
when we try to select the seperate selection processs check box for one of the company code with large number of open items we are getting the following errors
1. Company VUL/0001: RFC destination None : No company code assigned.Message No FB_ICRC106
2. Comapny EAB/0002 : RFC destination Q18CLNT100: Error in RFC connection: Error when opening an RFC connection
Message no FB_ICRC105.
How to fix this issue to increase the performance of ICR process , please help.
Thanks in advance
Sri.

Hello Sri,
ICR selects open items based on the posting date (BUDAT) and the clearing date (AUGDT). The standard functionality does not consider the "baseline date for due date calculation" (ZFBDT).
In ICR customizing you specified a fiscal year variant. This in combination with the fiscal year and period you provide on the selection screen gives you a key date for open item selection.
Example:
Fiscal year variant K4 (calendar year)
Fiscal year 2010
Period 012
>> Key date for open items: 31 December 2010
>> Select documents from BSID and BSIK for the customer/vendor accounts where trading partners are maintained with a posting date <= 31 December 2010
AND Select documents from BSAD and BSAK for the customer/vendor accounts where trading partners are maintained with a posting date <= 31 December 2010 and a clearing date > 31 December 2010 (i.e. they were still open on 31 Dec 2010 but were cleared in the meantime).
Best regards,
Ralph

Performance issues with 0CO_OM_WBS_1

We use BW3.5 & R/3 4.7 and encounter huge performance issues with 0CO_OM_WBS_1? Always having to do a full load involving approx 15M records even though there are on the average 100k new records since previous load. This takes a longtime.
Is there a way to delta-enable this datasource?

Hi,
This DS is not delta enabled and you can only do a full load. For a delta enabled one, you need to use 0CO_OM_WBS_6. This works as other Financials extractors, as it has a safety delta (configurable, default 2 hours, in table BWOM_SETTINGS).
What you should do is maybe, use the WBS_6 as a delta and only extract full loads for WBS_1 for shorter durations.
As you must have an ODS for WBS_1 at the first stage, I would suggest do a full load only for posting periods that are open. This will reduce the data load.
You may also look at creating your own generic data source with delta; if you are clear on the tables and logic used.
cheers...

Performance issues with Oracle EE 9.2.0.4 and RedHat 2.1

Hello,
I am having some serious performance issues with Oracle Enterprise Edition 9.2.0.4 and RedHat Linux 2.1. The processor goes berserk at 100% for long (some 5 min.) periods of time, and all the ram memory gets used.
Some environment characteristics:
Machine: Intel Pentium IV 2.0GHz with 1GB of RAM.
OS: RedHat Linux 2.1 Enterprise.
Oracle: Oracle Enterprise Edition 9.2.0.4
Application: We have a small web-application with 10 users (for now) and very basic queries (all in stored procedures). Also we use the latest version of ODP.NET with default connection settings (some low pooling, etc).
Does anyone know what could be going on?
Is anybody else having this similar behavior?
We change from SQL-Server so we are not the world expert on the matter. But we want a reliable system nonetheless.
Please help us out, gives some tips, tricks, or guides
Thanks to all,
Frank

Thank you very much and sorry I couldnt write sooner. It seems that the administrator doesnt see the kswap going on so much, so I dont really know what is going on.
We are looking at some queries and some indexing but this is nuts, if I had some poor queries, which we dont really, the server would show pick right?
But he goes crazy and has two oracle processes taking all the resources. There seems to be little swapping going on.
Son now what? They are all ready talking about MS-SQL please help me out here, this is crazy!!!
We have, may be the most powerful combinations here. What is oracle doing?
We even kill the Working Process of the IIS and have no one do anything with the database and still dose two processes going on.
Can some one help me?
Thanks,
Frank

Performance Issue For Opening And Closing Balance In FBL1N/3N/5N

Dear experts,
                    I Am Having Requirement to Bring Opening And Closing Balance In FBL1N, FBL3N, FBL5N.
For This requirement I Used BADI : FI_ITEMS_CH_DATA~CHANGE_ITEMS, below is my Code For FBL1N, And I've Done the same For 3N/5N...With Related BAPI
*   IF SY-TCODE = 'FBL1N'.
*    LOOP AT ct_items INTO gs_items.
*      CALL FUNCTION 'RP_CALC_DATE_IN_INTERVAL'
*        EXPORTING
*          date      = gs_items-budat
*          days      = '01'
*          months    = '00'
*          signum    = '-'
*          years     = '00'
*        IMPORTING
*          calc_date = lv_date.
*      CALL FUNCTION 'BAPI_AP_ACC_GETKEYDATEBALANCE'
*        EXPORTING
*          companycode        = gs_items-bukrs
*          vendor             = gs_items-konto
*          keydate            = lv_date
**   BALANCESPGLI       = ' '
**   NOTEDITEMS         = ' '
** IMPORTING
**   RETURN             =
*        TABLES
*          keybalance         = lv_obal.
*      CALL FUNCTION 'BAPI_AP_ACC_GETKEYDATEBALANCE'
*        EXPORTING
*          companycode        = gs_items-bukrs
*          vendor             = gs_items-konto
*          keydate            = gs_items-budat
**   BALANCESPGLI       = ' '
**   NOTEDITEMS         = ' '
** IMPORTING
**   RETURN             =
*        TABLES
*          keybalance         = lv_cbal
*      READ TABLE lv_cbal INTO gs_cbal INDEX 1.
*      gs_items-cbal = gs_cbal-lc_bal.
*      READ TABLE lv_obal INTO gs_obal INDEX 1.
*      gs_items-obal = gs_obal-lc_bal.
*      MODIFY ct_items FROM gs_items TRANSPORTING obal cbal.
*      CLEAR: gs_items,gs_obal,gs_cbal.
*    ENDLOOP.
*   ENDIF.
So, Above Code Causing Me the Performance Issue, Kindly Suggest Me the Solution..
Regards,
uday.

Hi Uday,
I am sending you the code i used for the creation a Zreport based on FBL5N. Please check if it can of any help.
*& Report ZFBL5N                                                      *
REPORT zfbl5n_new .
TABLES : bsid,knc1,lfc1.
TYPE-POOLS: slis.
TYPES: BEGIN OF ty_bsid,
          bukrs TYPE bsid-bukrs,
          kunnr TYPE bsid-kunnr,
          belnr TYPE bsid-belnr,
          buzei TYPE bsid-buzei,
          bldat TYPE bsid-bldat,
          blart TYPE bsid-blart,
          bschl TYPE bsid-bschl,
          shkzg TYPE bsid-shkzg,
          dmbtr TYPE bsid-dmbtr,
          augdt TYPE bsid-augdt,
          augbl TYPE bsid-augbl,
          zuonr TYPE bsid-zuonr,
          sgtxt TYPE bsid-sgtxt,
          zfbdt TYPE bsid-zfbdt,
          zterm TYPE bsid-zterm,
          zbd1t TYPE bsid-zbd1t,
          zbd2t TYPE bsid-zbd2t,
          zbd3t TYPE bsid-zbd3t,
          kkber TYPE bsid-kkber,
          bstat TYPE bsid-bstat,
          umskz TYPE bsid-umskz,
        END OF ty_bsid.
TYPES: BEGIN OF ty_bsik,
         bukrs TYPE bsik-bukrs,
          lifnr TYPE bsik-lifnr,
          belnr TYPE bsik-belnr,
          buzei TYPE bsik-buzei,
          bldat TYPE bsik-bldat,
          blart TYPE bsik-blart,
          bschl TYPE bsik-bschl,
          shkzg TYPE bsik-shkzg,
          dmbtr TYPE bsik-dmbtr,
          augdt TYPE bsik-augdt,
          augbl TYPE bsik-augbl,
          zuonr TYPE bsik-zuonr,
          sgtxt TYPE bsik-sgtxt,
           zfbdt TYPE bsik-zfbdt,
*         KKBER TYPE bsik-kkber,
          zterm TYPE bsik-zterm,
           zbd1t TYPE bsik-zbd1t,
          zbd2t TYPE bsik-zbd2t,
          zbd3t TYPE bsik-zbd3t,
          bstat TYPE bsid-bstat,
          umskz TYPE bsid-umskz,
        END OF ty_bsik.
TYPES: BEGIN OF ty_final,
          belnr TYPE bsid-belnr,
*         buzei TYPE bsak-buzei,
          bldat TYPE bsid-bldat,
          blart TYPE bsid-blart,
          chq TYPE bsid-zuonr,
          debit TYPE bsid-dmbtr,
          credit TYPE bsid-dmbtr,
          txt TYPE bsid-sgtxt,
          date TYPE bsid-zfbdt,
          kkber TYPE bsid-kkber,
          zterm TYPE bsid-zterm,
          augbl TYPE bsid-augbl,
          augdt TYPE bsid-augdt,
          flag TYPE c,
        END OF ty_final.
TYPES : BEGIN OF gs_openbal,
          bukrs TYPE bapi3007_2-comp_code,
          kunnr TYPE bapi3007_2-customer,
          dmbtr TYPE bapi3007_2-lc_amount,
         END OF gs_openbal.
DATA: it_bsid TYPE STANDARD TABLE OF ty_bsid,
       it_bsik TYPE STANDARD TABLE OF ty_bsik,
       it_final TYPE STANDARD TABLE OF ty_final.
DATA: wa_bsid TYPE ty_bsid,
       wa_bsik TYPE ty_bsik,
       wa_final TYPE ty_final.
DATA: w_days TYPE t5a4a-dlydy,
       w_month TYPE t5a4a-dlymo,
       w_year TYPE t5a4a-dlyyr,
       w_date TYPE p0001-begda,
       w_name1 TYPE kna1-name1,
       w_ort01 TYPE kna1-ort01,
       w_lifnr TYPE kna1-lifnr,
       w_dmbtr1 TYPE bsid-dmbtr,
       w_dmbtr2 TYPE bsid-dmbtr,
       w_dmbtr3 TYPE bsad-dmbtr,
       w_dmbtr4 TYPE bsad-dmbtr,
       w_opbal TYPE bsid-dmbtr,
       w_credit TYPE bsik-dmbtr,
       w_debit TYPE bsik-dmbtr,
       w_clobal TYPE bsik-dmbtr,
       w_credit1 TYPE bsik-dmbtr,
       w_debit1 TYPE bsik-dmbtr,
       w_clobal1 TYPE bsik-dmbtr.
DATA: ld_yrper LIKE rwcoom-fiscper,
       kunnr LIKE kna1-kunnr,
       x_norm TYPE c,
       x_park,
       x_apar,
       x_merk,
       ok_code(4),
       wa_x001 LIKE x001,
       return LIKE bapireturn,
       line_count LIKE sy-loopc,
       number_of_records TYPE i,
       xindex LIKE sy-tabix,
       open LIKE knc1-um01s,
       temp(20),
       close LIKE knc1-um01s,
       gjahr LIKE bsid-gjahr,
       period LIKE bkpf-monat,
       f(1),
       v_char(2),
       closec(20),
       openc(20),
       debit LIKE bapi3007_2-lc_amount,
       credit LIKE debit.
DATA : v_dmbtr LIKE bsid-dmbtr.
*DATA : tot_debit LIKE t_ar-debit,
*       tot_credit LIKE t_ar-credit.
DATA : t_kna1 LIKE kna1 OCCURS 1 WITH HEADER LINE,
        t_knb1 LIKE knb1 OCCURS 10 WITH HEADER LINE.
DATA ibsid LIKE bsid OCCURS 0 WITH HEADER LINE.
DATA ibsad LIKE bsad OCCURS 0 WITH HEADER LINE.
DATA ibsik LIKE bsik OCCURS 0 WITH HEADER LINE.
DATA ibsak LIKE bsak OCCURS 0 WITH HEADER LINE.
DATA : it_fieldcat_alv   TYPE slis_t_fieldcat_alv,
        wa_fieldcat_alv     TYPE slis_fieldcat_alv,
        is_layout_alv TYPE slis_layout_alv,
        wa_layout_alv TYPE slis_layout_alv,
        it_list_top_of_page TYPE slis_t_listheader,
        it_events TYPE slis_t_event,
        wa_events TYPE LINE OF slis_t_event.
DATA : BEGIN OF ibukrs OCCURS 0,
           bukrs LIKE t001-bukrs,
          END OF ibukrs.
DATA : BEGIN OF ikunnr1 OCCURS 0,
          kunnr LIKE knc1-kunnr,
         END OF ikunnr1.
DATA : BEGIN OF ikunnr OCCURS 0,
           kunnr LIKE knc1-kunnr,
           bukrs LIKE t001-bukrs,
           lifnr LIKE lfc1-lifnr,
          END OF ikunnr.
DATA: it_sort TYPE slis_t_sortinfo_alv,
       wa_sort TYPE slis_sortinfo_alv.
DATA:    r_bschl TYPE RANGE OF bschl,
          wa_bschl LIKE LINE OF r_bschl.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
PARAMETERS : p_kunnr TYPE bsid-kunnr OBLIGATORY,
              p_bukrs TYPE bsid-bukrs OBLIGATORY.
SELECT-OPTIONS: so_budat FOR bsid-budat .
SELECTION-SCREEN END OF BLOCK b1.
SELECTION-SCREEN BEGIN OF BLOCK b2 WITH FRAME TITLE text-002.
PARAMETERS : p_normal AS CHECKBOX,
              p_spl    AS CHECKBOX,
              p_vendor AS CHECKBOX.
SELECTION-SCREEN END OF BLOCK b2.
PERFORM get_data.
PERFORM process_data.
*PERFORM calculate_openbal. " Commented by anish
PERFORM calculate_open_bal.
PERFORM calculate_closing_bal.
PERFORM build_catalog_sort USING it_sort.
PERFORM reuse_alv_events_get .
PERFORM display_data.
*&      Form GET_DATA
*       text
* --> p1        text
* <-- p2        text
FORM get_data .
   SELECT bukrs kunnr belnr buzei bldat blart bschl shkzg dmbtr augdt augbl zuonr sgtxt zfbdt zterm zbd1t zbd2t zbd3t kkber
     bstat umskz FROM bsid
     INTO TABLE it_bsid
     WHERE bukrs = p_bukrs
      AND kunnr = p_kunnr
      AND budat IN so_budat.
   SELECT bukrs kunnr belnr buzei bldat blart bschl shkzg dmbtr augdt augbl zuonr sgtxt zfbdt zterm zbd1t zbd2t zbd3t kkber
    bstat umskz FROM bsad
    APPENDING TABLE it_bsid
    WHERE bukrs = p_bukrs
     AND kunnr = p_kunnr
     AND budat IN so_budat.
   SELECT SINGLE name1 ort01 lifnr FROM kna1
     INTO (w_name1 , w_ort01 , w_lifnr)
     WHERE kunnr = p_kunnr.
   IF p_vendor IS NOT INITIAL.
     SELECT bukrs lifnr belnr buzei bldat blart bschl shkzg dmbtr augdt augbl zuonr sgtxt zfbdt zterm zbd1t zbd2t zbd3t
     bstat umskz   FROM bsik
     APPENDING TABLE it_bsik
     WHERE bukrs = p_bukrs
       AND lifnr = w_lifnr
       AND budat IN so_budat.
     SELECT bukrs lifnr belnr buzei bldat blart bschl shkzg dmbtr augdt augbl zuonr sgtxt zfbdt zterm zbd1t zbd2t zbd3t
     bstat umskz FROM bsak
    APPENDING TABLE it_bsik
    WHERE bukrs = p_bukrs
      AND lifnr = w_lifnr
      AND budat IN so_budat.
   ENDIF.
   SORT it_bsid BY bschl.
   DELETE it_bsid WHERE bschl = '04'.
   DELETE it_bsid WHERE bschl = '07'.
   DELETE it_bsid WHERE bschl = '17'.
   DELETE it_bsid WHERE bschl = '34'.
   DELETE it_bsid WHERE bschl = '27'.
   DELETE it_bsid WHERE bschl = '37'.
   SORT it_bsik BY bschl.
   DELETE it_bsik WHERE bschl = '04'.
   DELETE it_bsik WHERE bschl = '07'.
   DELETE it_bsik WHERE bschl = '17'.
   DELETE it_bsik WHERE bschl = '34'.
   DELETE it_bsik WHERE bschl = '27'.
   DELETE it_bsik WHERE bschl = '37'.
ENDFORM.                    " GET_DATA
*&      Form PROCESS_DATA
*       text
* --> p1        text
* <-- p2        text
FORM process_data .
   DATA:okay       TYPE c VALUE space.
   w_month = '00'.
   w_year = '00'.
   SORT it_bsid BY bldat .
   LOOP AT it_bsid INTO wa_bsid.
     PERFORM check_item_ok USING p_normal
                                  p_spl
                                  p_vendor
*                               x_park
                                  wa_bsid
                            CHANGING okay.
     CHECK okay = 'X'.
     wa_final-belnr = wa_bsid-belnr.
     wa_final-bldat = wa_bsid-bldat.
     wa_final-blart = wa_bsid-blart.
     wa_final-txt = wa_bsid-sgtxt.
     wa_final-kkber = wa_bsid-kkber.
     wa_final-zterm = wa_bsid-zterm.
     wa_final-augbl = wa_bsid-augbl.
     wa_final-augdt = wa_bsid-augdt.
     wa_final-flag = 'C'.
     IF wa_bsid-blart = 'DZ'.
       wa_final-chq = wa_bsid-zuonr.
     ENDIF.
     IF wa_bsid-shkzg = 'S'.
       wa_final-debit = wa_bsid-dmbtr.
     ELSEIF wa_bsid-shkzg = 'H'.
       wa_final-credit = wa_bsid-dmbtr.
     ENDIF.
     w_credit = w_credit + wa_final-credit.
     w_debit = w_debit + wa_final-debit.
****** Net due date
     IF wa_bsid-zbd1t IS NOT INITIAL.
       w_days = wa_bsid-zbd1t.
     ELSEIF wa_bsid-zbd2t IS NOT INITIAL.
       w_days = wa_bsid-zbd2t.
     ELSEIF wa_bsid-zbd3t IS NOT INITIAL.
       w_days = wa_bsid-zbd3t.
     ENDIF.
     IF w_days IS INITIAL.
       wa_final-date = wa_bsid-zfbdt.
     ELSE.
       CALL FUNCTION 'RP_CALC_DATE_IN_INTERVAL'
         EXPORTING
           date      = wa_bsid-zfbdt
           days      = w_days
           months    = w_month
           signum    = '+'
           years     = w_year
         IMPORTING
           calc_date = w_date.
       wa_final-date = w_date.
     ENDIF.
     APPEND wa_final TO it_final.
     CLEAR: w_days , w_date , wa_final .
   ENDLOOP.
   IF it_bsik IS NOT INITIAL.
     CLEAR: w_days , w_date.
     SORT it_bsik BY bldat.
     LOOP AT it_bsik INTO wa_bsik.
       wa_final-belnr = wa_bsik-belnr.
       wa_final-bldat = wa_bsik-bldat.
       wa_final-blart = wa_bsik-blart.
       wa_final-txt = wa_bsik-sgtxt.
*    wa_final-kkber = wa_bsik-kkber.
       wa_final-zterm = wa_bsik-zterm.
       wa_final-augbl = wa_bsik-augbl.
       wa_final-augdt = wa_bsik-augdt.
       wa_final-flag = 'V'.
       IF wa_bsik-blart = 'DZ'.
         wa_final-chq = wa_bsik-zuonr.
       ENDIF.
       IF wa_bsik-shkzg = 'S'.
         wa_final-debit = wa_bsik-dmbtr.
       ELSEIF wa_bsik-shkzg = 'H'.
         wa_final-credit = wa_bsik-dmbtr.
       ENDIF.
       w_credit1 = w_credit1 + wa_final-credit.
       w_debit1 = w_debit1 + wa_final-debit.
******* Net Due date
       IF wa_bsik-zbd1t IS NOT INITIAL.
         w_days = wa_bsik-zbd1t.
       ELSEIF wa_bsik-zbd2t IS NOT INITIAL.
         w_days = wa_bsik-zbd2t.
       ELSEIF wa_bsik-zbd3t IS NOT INITIAL.
         w_days = wa_bsik-zbd3t.
       ENDIF.
       IF w_days IS INITIAL.
         wa_final-date = wa_bsik-zfbdt.
       ELSE.
         CALL FUNCTION 'RP_CALC_DATE_IN_INTERVAL'
           EXPORTING
             date      = wa_bsik-zfbdt
             days      = w_days
             months    = w_month
             signum    = '+'
             years     = w_year
           IMPORTING
             calc_date = w_date.
       ENDIF.
       wa_final-date = w_date.
       APPEND wa_final TO it_final.
       CLEAR: wa_final.
     ENDLOOP.
   ENDIF.
ENDFORM.                    " PROCESS_DATA
*&      Form DISPLAY_DATA
*       text
* --> p1        text
* <-- p2        text
FORM display_data .
   wa_fieldcat_alv-fieldname = 'BELNR'.
   wa_fieldcat_alv-tabname = 'IT_FINAL'.
   wa_fieldcat_alv-seltext_l = text-003.
   wa_fieldcat_alv-outputlen = '11'.
   APPEND wa_fieldcat_alv TO it_fieldcat_alv.
   CLEAR wa_fieldcat_alv.
   wa_fieldcat_alv-fieldname = 'BLDAT'.
   wa_fieldcat_alv-tabname = 'IT_FINAL'.
   wa_fieldcat_alv-seltext_l = text-004.
   wa_fieldcat_alv-outputlen = '13'.
   APPEND wa_fieldcat_alv TO it_fieldcat_alv.
   CLEAR wa_fieldcat_alv.
   wa_fieldcat_alv-fieldname = 'BLART'.
   wa_fieldcat_alv-tabname = 'IT_FINAL'.
   wa_fieldcat_alv-seltext_l = text-005.
   wa_fieldcat_alv-outputlen = '02'.
   APPEND wa_fieldcat_alv TO it_fieldcat_alv.
   CLEAR wa_fieldcat_alv.
   wa_fieldcat_alv-fieldname = 'CHQ'.
   wa_fieldcat_alv-tabname = 'IT_FINAL'.
   wa_fieldcat_alv-seltext_l = text-006.
   wa_fieldcat_alv-outputlen = '09'.
   APPEND wa_fieldcat_alv TO it_fieldcat_alv.
   CLEAR wa_fieldcat_alv.
   wa_fieldcat_alv-fieldname = 'DEBIT'.
   wa_fieldcat_alv-tabname = 'IT_FINAL'.
   wa_fieldcat_alv-seltext_l = text-007.
   wa_fieldcat_alv-outputlen = '15'.
   wa_fieldcat_alv-do_sum = 'X'.
   APPEND wa_fieldcat_alv TO it_fieldcat_alv.
   CLEAR wa_fieldcat_alv.
   wa_fieldcat_alv-fieldname = 'CREDIT'.
   wa_fieldcat_alv-tabname = 'IT_FINAL'.
   wa_fieldcat_alv-seltext_l = text-008.
   wa_fieldcat_alv-outputlen = '15'.
   wa_fieldcat_alv-do_sum = 'X'.
   APPEND wa_fieldcat_alv TO it_fieldcat_alv.
   CLEAR wa_fieldcat_alv.
   wa_fieldcat_alv-fieldname = 'TXT'.
   wa_fieldcat_alv-tabname = 'IT_FINAL'.
   wa_fieldcat_alv-seltext_l = text-009.
   wa_fieldcat_alv-outputlen = '50'.
   APPEND wa_fieldcat_alv TO it_fieldcat_alv.
   CLEAR wa_fieldcat_alv.
   wa_fieldcat_alv-fieldname = 'DATE'.
   wa_fieldcat_alv-tabname = 'IT_FINAL'.
   wa_fieldcat_alv-seltext_l = text-010.
   wa_fieldcat_alv-outputlen = '12'.
   APPEND wa_fieldcat_alv TO it_fieldcat_alv.
   CLEAR wa_fieldcat_alv.
   wa_fieldcat_alv-fieldname = 'KKBER'.
   wa_fieldcat_alv-tabname = 'IT_FINAL'.
   wa_fieldcat_alv-seltext_l = text-011.
   wa_fieldcat_alv-outputlen = '04'.
   APPEND wa_fieldcat_alv TO it_fieldcat_alv.
   CLEAR wa_fieldcat_alv.
   wa_fieldcat_alv-fieldname = 'ZTERM'.
   wa_fieldcat_alv-tabname = 'IT_FINAL'.
   wa_fieldcat_alv-seltext_l = text-012.
   wa_fieldcat_alv-outputlen = '13'.
   APPEND wa_fieldcat_alv TO it_fieldcat_alv.
   CLEAR wa_fieldcat_alv.
   wa_fieldcat_alv-fieldname = 'AUGBL'.
   wa_fieldcat_alv-tabname = 'IT_FINAL'.
   wa_fieldcat_alv-seltext_l = text-013.
   wa_fieldcat_alv-outputlen = '15'.
   APPEND wa_fieldcat_alv TO it_fieldcat_alv.
   CLEAR wa_fieldcat_alv.
   wa_fieldcat_alv-fieldname = 'AUGDT'.
   wa_fieldcat_alv-tabname = 'IT_FINAL'.
   wa_fieldcat_alv-seltext_l = text-014.
   wa_fieldcat_alv-outputlen = '17'.
   APPEND wa_fieldcat_alv TO it_fieldcat_alv.
   CLEAR wa_fieldcat_alv.
   wa_fieldcat_alv-fieldname = 'FLAG'.
   wa_fieldcat_alv-tabname = 'IT_FINAL'.
   wa_fieldcat_alv-tech = 'X'.
   APPEND wa_fieldcat_alv TO it_fieldcat_alv.
   CLEAR wa_fieldcat_alv.
   CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
    EXPORTING
      i_callback_program             = sy-repid
      is_layout                      = wa_layout_alv
      it_fieldcat                    = it_fieldcat_alv
*   IT_EXCLUDING                   =
*   IT_SPECIAL_GROUPS              =
      it_sort                        = it_sort
      it_events                      = it_events
      i_save                            = 'A'
     TABLES
       t_outtab                       = it_final
    EXCEPTIONS
      program_error                  = 1
      OTHERS                         = 2
   IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
   ENDIF.
* CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
*    EXPORTING
*      i_callback_program                = sy-repid
*     i_callback_top_of_page            = 'TOP_OF_PAGE'
*      is_layout                         = wa_layout_alv
*      it_fieldcat                       = it_fieldcat_alv
*      it_sort                           = it_sort
***   I_DEFAULT                         = 'X'
**      i_save                            = 'A'
***   IT_EVENTS                         =
*     TABLES
*       t_outtab                          = it_final
*    EXCEPTIONS
*      program_error                     = 1
*      OTHERS                            = 2
* IF sy-subrc <> 0.
*** MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
***         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
* ENDIF.
ENDFORM.                    " DISPLAY_DATA
*&      Form TOP_OF_PAGE
*       Header at top of page.
FORM top_of_page.
   SKIP 1.
   WRITE: AT 35 'Account Statement from' , so_budat-low , 'to' , so_budat-high.
   SKIP 2.
   WRITE: AT /5 'CUSTOMER:' , p_kunnr.
   WRITE: AT 35 'Name:' , w_name1.
   WRITE: AT /5 'Company:' , p_bukrs.
   WRITE: AT 35 'City:' , w_ort01.
   SKIP 1.
   WRITE: AT /5 'Opening Balance as on' , so_budat-low , '   ' , w_opbal LEFT-JUSTIFIED.
   SKIP 2.
ENDFORM.                    "TOP_OF_PAGE
*&      Form END_OF_PAGE
*       Footer at End of page.
FORM end_of_page.
   SKIP 2.
   IF so_budat-high IS NOT INITIAL.
     WRITE: AT 5 'Closing Balance as on' , so_budat-high , '   ' , w_clobal LEFT-JUSTIFIED.
   ELSE.
     WRITE: AT 5 'Closing Balance ' , w_clobal LEFT-JUSTIFIED.
   ENDIF.
ENDFORM.                    "end_of_page
*&      Form CALCULATE_OPENBAL
*       text
* --> p1        text
* <-- p2        text
FORM calculate_openbal .
   DATA:v_gjahr       TYPE bsid-gjahr.
   DATA: v_period LIKE t009b-poper,v_monat LIKE t001-periv.
   CALL FUNCTION 'FI_PERIOD_DETERMINE'
          EXPORTING
               i_budat        = so_budat-low
               i_bukrs        = p_bukrs
*           I_PERIV        = ' '
*           I_GJAHR        = 0000
*           I_MONAT        = 00
*           X_XMO16        = ' '
          IMPORTING
               e_gjahr        = v_gjahr
*            e_monat        = v_monat
               e_poper        = v_period.
   IF sy-subrc NE 0.
   ENDIF.
   DATA: f_date LIKE sy-datum.
   CALL FUNCTION 'FIRST_DAY_IN_PERIOD_GET'
     EXPORTING
       i_gjahr = v_gjahr
       i_monmit = 00
       i_periv = 'V3'
       i_poper = v_period
     IMPORTING
       e_date   = f_date.
   period = v_period - 1.
   gjahr = v_gjahr.
   DATA wa_kna1 LIKE kna1.
   CALL FUNCTION 'READ_KNA1'
     EXPORTING
       xkunnr         = p_kunnr
     IMPORTING
       xkna1          = wa_kna1
     EXCEPTIONS
       key_incomplete = 1
       not_authorized = 2
       not_found      = 3
       OTHERS         = 4.
   IF sy-subrc <> 0.
     MESSAGE w023(zwww).
     CALL SCREEN 0010.
   ENDIF.
   MOVE-CORRESPONDING wa_kna1 TO t_kna1.
   APPEND t_kna1.
   SELECT kunnr FROM kna1 INTO TABLE ikunnr1
     WHERE kunnr = p_kunnr.
   SELECT bukrs FROM t001 INTO TABLE ibukrs
    FOR ALL ENTRIES IN t_knb1
    WHERE bukrs = t_knb1-bukrs.
   LOOP AT ikunnr1.
     LOOP AT ibukrs.
       ikunnr-kunnr = ikunnr1-kunnr.
       ikunnr-bukrs = ibukrs-bukrs.
       READ TABLE t_kna1 WITH KEY kunnr = ikunnr1-kunnr.
       ikunnr-lifnr = t_kna1-lifnr.
       APPEND ikunnr.
     ENDLOOP.
   ENDLOOP.
   DELETE ikunnr WHERE bukrs NE p_bukrs.
   LOOP AT ikunnr.
     CLEAR: knc1,lfc1,f.
     IF NOT ( ikunnr-kunnr IS INITIAL ) AND NOT ( p_vendor IS INITIAL ).
       SELECT SINGLE * FROM lfc1
              WHERE gjahr = gjahr AND bukrs = ikunnr-bukrs
                                  AND lifnr = ikunnr-lifnr.
     ENDIF.
     SELECT SINGLE * FROM knc1
       WHERE gjahr = gjahr AND bukrs = p_bukrs
             AND kunnr = p_kunnr.
     IF sy-subrc = 0.
       CASE period .
         WHEN 12.
           open = knc1-umsav +
           knc1-um01s - knc1-um01h + knc1-um02s - knc1-um02h +
           knc1-um03s - knc1-um03h + knc1-um04s - knc1-um04h +
           knc1-um05s - knc1-um05h + knc1-um06s - knc1-um06h +
           knc1-um07s - knc1-um07h + knc1-um08s - knc1-um08h +
           knc1-um09s - knc1-um09h + knc1-um10s - knc1-um10h +
           knc1-um11s - knc1-um11h + knc1-um12s - knc1-um12h.
           IF NOT ( lfc1 IS INITIAL ).
             open = open + lfc1-umsav +
             lfc1-um01s - lfc1-um01h + lfc1-um02s - lfc1-um02h +
             lfc1-um03s - lfc1-um03h + lfc1-um04s - lfc1-um04h +
             lfc1-um05s - lfc1-um05h + lfc1-um06s - lfc1-um06h +
             lfc1-um07s - lfc1-um07h + lfc1-um08s - lfc1-um08h +
             lfc1-um09s - lfc1-um09h + lfc1-um10s - lfc1-um10h +
             lfc1-um11s - lfc1-um11h + lfc1-um12s - lfc1-um12h.
           ENDIF.
         WHEN 11.
           open = knc1-umsav +
           knc1-um01s - knc1-um01h + knc1-um02s - knc1-um02h +
           knc1-um03s - knc1-um03h + knc1-um04s - knc1-um04h +
           knc1-um05s - knc1-um05h + knc1-um06s - knc1-um06h +
           knc1-um07s - knc1-um07h + knc1-um08s - knc1-um08h +
           knc1-um09s - knc1-um09h + knc1-um10s - knc1-um10h +
           knc1-um11s - knc1-um11h.
           IF NOT ( lfc1 IS INITIAL ) .
             open = open + lfc1-umsav +
             lfc1-um01s - lfc1-um01h + lfc1-um02s - lfc1-um02h +
             lfc1-um03s - lfc1-um03h + lfc1-um04s - lfc1-um04h +
             lfc1-um05s - lfc1-um05h + lfc1-um06s - lfc1-um06h +
             lfc1-um07s - lfc1-um07h + lfc1-um08s - lfc1-um08h +
             lfc1-um09s - lfc1-um09h + lfc1-um10s - lfc1-um10h +
             lfc1-um11s - lfc1-um11h.
           ENDIF.
         WHEN 10.
           open = knc1-umsav +
           knc1-um01s - knc1-um01h + knc1-um02s - knc1-um02h +
           knc1-um03s - knc1-um03h + knc1-um04s - knc1-um04h +
           knc1-um05s - knc1-um05h + knc1-um06s - knc1-um06h +
           knc1-um07s - knc1-um07h + knc1-um08s - knc1-um08h +
           knc1-um09s - knc1-um09h + knc1-um10s - knc1-um10h .
           IF NOT ( lfc1 IS INITIAL ) .
             open = open + lfc1-umsav +
             lfc1-um01s - lfc1-um01h + lfc1-um02s - lfc1-um02h +
             lfc1-um03s - lfc1-um03h + lfc1-um04s - lfc1-um04h +
             lfc1-um05s - lfc1-um05h + lfc1-um06s - lfc1-um06h +
             lfc1-um07s - lfc1-um07h + lfc1-um08s - lfc1-um08h +
             lfc1-um09s - lfc1-um09h + lfc1-um10s - lfc1-um10h.
           ENDIF.
         WHEN 9.
           open = knc1-umsav +
           knc1-um01s - knc1-um01h + knc1-um02s - knc1-um02h +
           knc1-um03s - knc1-um03h + knc1-um04s - knc1-um04h +
           knc1-um05s - knc1-um05h + knc1-um06s - knc1-um06h +
           knc1-um07s - knc1-um07h + knc1-um08s - knc1-um08h +
           knc1-um09s - knc1-um09h .
           IF NOT ( lfc1 IS INITIAL ) .
             open = open + lfc1-umsav +
             lfc1-um01s - lfc1-um01h + lfc1-um02s - lfc1-um02h +
             lfc1-um03s - lfc1-um03h + lfc1-um04s - lfc1-um04h +
             lfc1-um05s - lfc1-um05h + lfc1-um06s - lfc1-um06h +
             lfc1-um07s - lfc1-um07h + lfc1-um08s - lfc1-um08h +
             lfc1-um09s - lfc1-um09h.
           ENDIF.
         WHEN 8.
           open = knc1-umsav +
           knc1-um01s - knc1-um01h + knc1-um02s - knc1-um02h +
           knc1-um03s - knc1-um03h + knc1-um04s - knc1-um04h +
           knc1-um05s - knc1-um05h + knc1-um06s - knc1-um06h +
           knc1-um07s - knc1-um07h + knc1-um08s - knc1-um08h.
           IF NOT ( lfc1 IS INITIAL ) .
             open = open + lfc1-umsav +
             lfc1-um01s - lfc1-um01h + lfc1-um02s - lfc1-um02h +
             lfc1-um03s - lfc1-um03h + lfc1-um04s - lfc1-um04h +
             lfc1-um05s - lfc1-um05h + lfc1-um06s - lfc1-um06h +
             lfc1-um07s - lfc1-um07h + lfc1-um08s - lfc1-um08h .
           ENDIF.
         WHEN 7.
           open = knc1-umsav +
           knc1-um01s - knc1-um01h + knc1-um02s - knc1-um02h +
           knc1-um03s - knc1-um03h + knc1-um04s - knc1-um04h +
           knc1-um05s - knc1-um05h + knc1-um06s - knc1-um06h +
           knc1-um07s - knc1-um07h .
           IF NOT ( lfc1 IS INITIAL ) .
             open = open + lfc1-umsav +
             lfc1-um01s - lfc1-um01h + lfc1-um02s - lfc1-um02h +
             lfc1-um03s - lfc1-um03h + lfc1-um04s - lfc1-um04h +
             lfc1-um05s - lfc1-um

Performance issue in DB need help with analysing this ADDM report

Hi,
My environment:
Os: RHEL5U3 / 11.1.0.7 64 bit / R12.1.1 64 bit
Issue:
Few days are am facing serious of performance problem in our Production instance. Normally the issue will occur 5 to 10 minutes occasionally per day. At the time of issue we not able to access the EBS application its taking time to load. But backend all the oracle, listener and apps services are up and running. No locks at table and session level. Cpu and memory usage is normal.
We have monitored using "Enterprise Manager" for this issue and we found the wait session present more in Active session tab. At this time EBS application is not able access its loading too time. After some time the in Active session tab the wait session came normal and when we try to access the EBS application its working fine.
We try to find the cause of the issue by running addm report. But am not able to understand what its says. Kindly suggests me
ADDM Report for Task 'TASK_42656'
Analysis Period
AWR snapshot range from 14754 to 14755.
Time period starts at 17-APR-12 11.00.22 AM
Time period ends at 17-APR-12 12.00.33 PM
Analysis Target
Database 'PRD' with DB ID 1789440879.
Database version 11.1.0.7.0.
ADDM performed an analysis of instance PRD, numbered 1 and hosted at
advgrpdb.advgroup.ae.
Activity During the Analysis Period
Total database time was 18674 seconds.
The average number of active sessions was 5.17.
Summary of Findings
Description Active Sessions Recommendations
Percent of Activity
1 Top SQL by DB Time 3.43 | 66.33 5
2 Buffer Busy 2.52 | 48.81 5
3 Buffer Busy 1.39 | 26.81 2
4 Log File Switches .91 | 17.56 1
5 Buffer Busy .56 | 10.87 2
6 Undersized SGA .38 | 7.37 1
7 Commits and Rollbacks .28 | 5.42 1
8 Undo I/O .18 | 3.53 0
9 CPU Usage .13 | 2.57 1
10 Top SQL By I/O .11 | 2.21 1
Findings and Recommendations
Finding 1: Top SQL by DB Time
Impact is 3.43 active sessions, 66.33% of total activity.
SQL statements consuming significant database time were found.
Recommendation 1: SQL Tuning
Estimated benefit is 1.59 active sessions, 30.8% of total activity.
Action
Investigate the SQL statement with SQL_ID "a49xsqhv0h31b" for possible
performance improvements.
Related Object
SQL statement with SQL_ID a49xsqhv0h31b.
SELECT R.Conc_Login_Id, R.Request_Id, R.Phase_Code, R.Status_Code,
P.Application_ID, P.Concurrent_Program_ID, P.Concurrent_Program_Name,
R.Enable_Trace, R.Restart, DECODE(R.Increment_Dates, 'Y', 'Y', 'N'),
R.NLS_Compliant, R.OUTPUT_FILE_TYPE, E.Executable_Name,
E.Execution_File_Name, A2.Basepath, DECODE(R.Stale, 'Y', 'C',
P.Execution_Method_Code), P.Print_Flag, P.Execution_Options,
DECODE(P.Srs_Flag, 'Y', 'Y', 'Q', 'Y', 'N'), P.Argument_Method_Code,
R.Print_Style, R.Argument_Input_Method_Code, R.Queue_Method_Code,
R.Responsibility_ID, R.Responsibility_Application_ID, R.Requested_By,
R.Number_Of_Copies, R.Save_Output_Flag, R.Printer, R.Print_Group,
R.Priority, U.User_Name, O.Oracle_Username,
O.Encrypted_Oracle_Password, R.Cd_Id, A.Basepath,
A.Application_Short_Name, TO_CHAR(R.Requested_Start_Date,'YYYY/MM/DD
HH24:MI:SS'), R.Nls_Language, R.Nls_Territory,
R.Nls_Numeric_Characters, DECODE(R.Parent_Request_ID, NULL, 0,
R.Parent_Request_ID), R.Priority_Request_ID, R.Single_Thread_Flag,
R.Has_Sub_Request, R.Is_Sub_Request, R.Req_Information,
R.Description, R.Resubmit_Time, TO_CHAR(R.Resubmit_Interval),
R.Resubmit_Interval_Type_Code, R.Resubmit_Interval_Unit_Code,
TO_CHAR(R.Resubmit_End_Date,'YYYY/MM/DD HH24:MI:SS'),
Decode(E.Execution_File_Name, NULL, 'N', Decode(E.Subroutine_Name,
NULL, Decode(E.Execution_Method_Code, 'I', 'Y', 'J', 'Y', 'N'),
'Y')), R.Argument1, R.Argument2, R.Argument3, R.Argument4,
R.Argument5, R.Argument6, R.Argument7, R.Argument8, R.Argument9,
R.Argument10, R.Argument11, R.Argument12, R.Argument13, R.Argument14,
R.Argument15, R.Argument16, R.Argument17, R.Argument18, R.Argument19,
R.Argument20, R.Argument21, R.Argument22, R.Argument23, R.Argument24,
R.Argument25, X.Argument26, X.Argument27, X.Argument28, X.Argument29,
X.Argument30, X.Argument31, X.Argument32, X.Argument33, X.Argument34,
X.Argument35, X.Argument36, X.Argument37, X.Argument38, X.Argument39,
X.Argument40, X.Argument41, X.Argument42, X.Argument43, X.Argument44,
X.Argument45, X.Argument46, X.Argument47, X.Argument48, X.Argument49,
X.Argument50, X.Argument51, X.Argument52, X.Argument53, X.Argument54,
X.Argument55, X.Argument56, X.Argument57, X.Argument58, X.Argument59,
X.Argument60, X.Argument61, X.Argument62, X.Argument63, X.Argument64,
X.Argument65, X.Argument66, X.Argument67, X.Argument68, X.Argument69,
X.Argument70, X.Argument71, X.Argument72, X.Argument73, X.Argument74,
X.Argument75, X.Argument76, X.Argument77, X.Argument78, X.Argument79,
X.Argument80, X.Argument81, X.Argument82, X.Argument83, X.Argument84,
X.Argument85, X.Argument86, X.Argument87, X.Argument88, X.Argument89,
X.Argument90, X.Argument91, X.Argument92, X.Argument93, X.Argument94,
X.Argument95, X.Argument96, X.Argument97, X.Argument98, X.Argument99,
X.Argument100, R.number_of_arguments, C.CD_Name,
NVL(R.Security_Group_ID, 0), NVL(R.org_id, 0) FROM
fnd_concurrent_requests R, fnd_concurrent_programs P, fnd_application
A, fnd_user U, fnd_oracle_userid O, fnd_conflicts_domain C,
fnd_concurrent_queues Q, fnd_application A2, fnd_executables E,
fnd_conc_request_arguments X WHERE R.Status_code = 'I' And
((R.OPS_INSTANCE is null) or (R.OPS_INSTANCE = -1) or
(R.OPS_INSTANCE =
decode(:dcp_on,1,FND_CONC_GLOBAL.OPS_INST_NUM,R.OPS_INSTANCE))) And
R.Request_ID = X.Request_ID(+) And R.Program_Application_Id =
P.Application_Id(+) And R.Concurrent_Program_Id =
P.Concurrent_Program_Id(+) And R.Program_Application_Id =
A.Application_Id(+) And P.Executable_Application_Id =
E.Application_Id(+) And P.Executable_Id =
E.Executable_Id(+) And P.Executable_Application_Id =
A2.Application_Id(+) And R.Requested_By = U.User_Id(+) And R.Cd_Id
= C.Cd_Id(+) And R.Oracle_Id = O.Oracle_Id(+) And Q.Application_Id =
:q_applid And Q.Concurrent_Queue_Id = :queue_id And (P.Enabled_Flag
is NULL OR P.Enabled_Flag = 'Y') And R.Hold_Flag = 'N' And
R.Requested_Start_Date <= Sysdate And ( R.Enforce_Seriality_Flag =
'N' OR ( C.RunAlone_Flag = P.Run_Alone_Flag And (P.Run_Alone_Flag =
'N' OR Not Exists (Select Null From Fnd_Concurrent_Requests Sr
Where Sr.Status_Code In ('R', 'T') And Sr.Enforce_Seriality_Flag =
'Y' And Sr.CD_id = C.CD_Id)))) And Q.Running_Processes <=
Q.Max_Processes And R.Rowid = :reqname And
((P.Execution_Method_Code != 'S' OR
(R.PROGRAM_APPLICATION_ID,R.CONCURRENT_PROGRAM_ID) IN
((0,98),(0,100),(0,31721),(0,31722),(0,31757))) AND
((R.PROGRAM_APPLICATION_ID,R.CONCURRENT_PROGRAM_ID) NOT IN
((510,40112),(510,40113),(510,41497),(510,41498),(530,41859),(530,418
60),(535,41492),(535,41493),(535,41494)))) FOR UPDATE OF
R.status_code NoWait
Rationale
SQL statement with SQL_ID "a49xsqhv0h31b" was executed 4686 times and
had an average elapsed time of 1.2 seconds.
Rationale
Waiting for event "buffer busy waits" in wait class "Concurrency"
accounted for 85% of the database time spent in processing the SQL
statement with SQL_ID "a49xsqhv0h31b".
Rationale
Waiting for event "log file switch (checkpoint incomplete)" in wait
class "Configuration" accounted for 9% of the database time spent in
processing the SQL statement with SQL_ID "a49xsqhv0h31b".
Recommendation 3: SQL Tuning
Estimated benefit is .56 active sessions, 10.91% of total activity.
Action
Investigate the SQL statement with SQL_ID "5d7957yktf3nn" for possible
performance improvements.
Related Object
SQL statement with SQL_ID 5d7957yktf3nn.
UPDATE ICX_SESSIONS SET TIME_OUT = :B2 WHERE SESSION_ID = :B1
Rationale
SQL statement with SQL_ID "5d7957yktf3nn" was executed 266 times and had
an average elapsed time of 7.6 seconds.
Rationale
Waiting for event "buffer busy waits" in wait class "Concurrency"
accounted for 86% of the database time spent in processing the SQL
statement with SQL_ID "5d7957yktf3nn".
Rationale
Waiting for event "log file switch (checkpoint incomplete)" in wait
class "Configuration" accounted for 7% of the database time spent in
processing the SQL statement with SQL_ID "5d7957yktf3nn".
Finding 2: Buffer Busy
Impact is 2.52 active sessions, 48.81% of total activity.
Read and write contention on database blocks was consuming significant
database time.
Recommendation 1: Application Analysis
Estimated benefit is 1.42 active sessions, 27.44% of total activity.
Action
Trace the cause of object contention due to SELECT statements in the
application using the information provided.
Related Object
Database object with ID 34562.
Rationale
The SELECT statement with SQL_ID "a49xsqhv0h31b" was significantly
affected by "buffer busy" waits.
Related Object
SQL statement with SQL_ID a49xsqhv0h31b.
SELECT R.Conc_Login_Id, R.Request_Id, R.Phase_Code, R.Status_Code,
P.Application_ID, P.Concurrent_Program_ID, P.Concurrent_Program_Name,
R.Enable_Trace, R.Restart, DECODE(R.Increment_Dates, 'Y', 'Y', 'N'),
R.NLS_Compliant, R.OUTPUT_FILE_TYPE, E.Executable_Name,
E.Execution_File_Name, A2.Basepath, DECODE(R.Stale, 'Y', 'C',
P.Execution_Method_Code), P.Print_Flag, P.Execution_Options,
DECODE(P.Srs_Flag, 'Y', 'Y', 'Q', 'Y', 'N'), P.Argument_Method_Code,
R.Print_Style, R.Argument_Input_Method_Code, R.Queue_Method_Code,
R.Responsibility_ID, R.Responsibility_Application_ID, R.Requested_By,
R.Number_Of_Copies, R.Save_Output_Flag, R.Printer, R.Print_Group,
R.Priority, U.User_Name, O.Oracle_Username,
O.Encrypted_Oracle_Password, R.Cd_Id, A.Basepath,
A.Application_Short_Name, TO_CHAR(R.Requested_Start_Date,'YYYY/MM/DD
HH24:MI:SS'), R.Nls_Language, R.Nls_Territory,
R.Nls_Numeric_Characters, DECODE(R.Parent_Request_ID, NULL, 0,
R.Parent_Request_ID), R.Priority_Request_ID, R.Single_Thread_Flag,
R.Has_Sub_Request, R.Is_Sub_Request, R.Req_Information,
R.Description, R.Resubmit_Time, TO_CHAR(R.Resubmit_Interval),
R.Resubmit_Interval_Type_Code, R.Resubmit_Interval_Unit_Code,
TO_CHAR(R.Resubmit_End_Date,'YYYY/MM/DD HH24:MI:SS'),
Decode(E.Execution_File_Name, NULL, 'N', Decode(E.Subroutine_Name,
NULL, Decode(E.Execution_Method_Code, 'I', 'Y', 'J', 'Y', 'N'),
'Y')), R.Argument1, R.Argument2, R.Argument3, R.Argument4,
R.Argument5, R.Argument6, R.Argument7, R.Argument8, R.Argument9,
R.Argument10, R.Argument11, R.Argument12, R.Argument13, R.Argument14,
R.Argument15, R.Argument16, R.Argument17, R.Argument18, R.Argument19,
R.Argument20, R.Argument21, R.Argument22, R.Argument23, R.Argument24,
R.Argument25, X.Argument26, X.Argument27, X.Argument28, X.Argument29,
X.Argument30, X.Argument31, X.Argument32, X.Argument33, X.Argument34,
X.Argument35, X.Argument36, X.Argument37, X.Argument38, X.Argument39,
X.Argument40, X.Argument41, X.Argument42, X.Argument43, X.Argument44,
X.Argument45, X.Argument46, X.Argument47, X.Argument48, X.Argument49,
X.Argument50, X.Argument51, X.Argument52, X.Argument53, X.Argument54,
X.Argument55, X.Argument56, X.Argument57, X.Argument58, X.Argument59,
X.Argument60, X.Argument61, X.Argument62, X.Argument63, X.Argument64,
X.Argument65, X.Argument66, X.Argument67, X.Argument68, X.Argument69,
X.Argument70, X.Argument71, X.Argument72, X.Argument73, X.Argument74,
X.Argument75, X.Argument76, X.Argument77, X.Argument78, X.Argument79,
X.Argument80, X.Argument81, X.Argument82, X.Argument83, X.Argument84,
X.Argument85, X.Argument86, X.Argument87, X.Argument88, X.Argument89,
X.Argument90, X.Argument91, X.Argument92, X.Argument93, X.Argument94,
X.Argument95, X.Argument96, X.Argument97, X.Argument98, X.Argument99,
X.Argument100, R.number_of_arguments, C.CD_Name,
NVL(R.Security_Group_ID, 0), NVL(R.org_id, 0) FROM
fnd_concurrent_requests R, fnd_concurrent_programs P, fnd_application
A, fnd_user U, fnd_oracle_userid O, fnd_conflicts_domain C,
fnd_concurrent_queues Q, fnd_application A2, fnd_executables E,
fnd_conc_request_arguments X WHERE R.Status_code = 'I' And
((R.OPS_INSTANCE is null) or (R.OPS_INSTANCE = -1) or
(R.OPS_INSTANCE =
decode(:dcp_on,1,FND_CONC_GLOBAL.OPS_INST_NUM,R.OPS_INSTANCE))) And
R.Request_ID = X.Request_ID(+) And R.Program_Application_Id =
P.Application_Id(+) And R.Concurrent_Program_Id =
P.Concurrent_Program_Id(+) And R.Program_Application_Id =
A.Application_Id(+) And P.Executable_Application_Id =
E.Application_Id(+) And P.Executable_Id =
E.Executable_Id(+) And P.Executable_Application_Id =
A2.Application_Id(+) And R.Requested_By = U.User_Id(+) And R.Cd_Id
= C.Cd_Id(+) And R.Oracle_Id = O.Oracle_Id(+) And Q.Application_Id =
:q_applid And Q.Concurrent_Queue_Id = :queue_id And (P.Enabled_Flag
is NULL OR P.Enabled_Flag = 'Y') And R.Hold_Flag = 'N' And
R.Requested_Start_Date <= Sysdate And ( R.Enforce_Seriality_Flag =
'N' OR ( C.RunAlone_Flag = P.Run_Alone_Flag And (P.Run_Alone_Flag =
'N' OR Not Exists (Select Null From Fnd_Concurrent_Requests Sr
Where Sr.Status_Code In ('R', 'T') And Sr.Enforce_Seriality_Flag =
'Y' And Sr.CD_id = C.CD_Id)))) And Q.Running_Processes <=
Q.Max_Processes And R.Rowid = :reqname And
((P.Execution_Method_Code != 'S' OR
(R.PROGRAM_APPLICATION_ID,R.CONCURRENT_PROGRAM_ID) IN
((0,98),(0,100),(0,31721),(0,31722),(0,31757))) AND
((R.PROGRAM_APPLICATION_ID,R.CONCURRENT_PROGRAM_ID) NOT IN
((510,40112),(510,40113),(510,41497),(510,41498),(530,41859),(530,418
60),(535,41492),(535,41493),(535,41494)))) FOR UPDATE OF
R.status_code NoWait
UPDATE ICX_SESSIONS SET LAST_CONNECT = SYSDATE WHERE SESSION_ID = :B1
Recommendation 1: Schema Changes
Estimated benefit is .03 active sessions, .62% of total activity.
Action
Consider rebuilding the TABLE "APPLSYS.FND_LOGIN_RESP_FORMS" with object
ID 34651 using a higher value for PCTFREE.
Related Object
Database object with ID 34651.
Rationale
The UPDATE statement with SQL_ID "cqc5crhxxt36t" was significantly
affected by "buffer busy" waits.
Related Object
SQL statement with SQL_ID cqc5crhxxt36t.
UPDATE FND_LOGIN_RESP_FORMS FLRF SET END_TIME = SYSDATE WHERE
FLRF.LOGIN_ID = :B2 AND FLRF.LOGIN_RESP_ID = :B1 AND FLRF.END_TIME IS
NULL AND (FLRF.FORM_ID, FLRF.FORM_APPL_ID) = (SELECT F.FORM_ID,
F.APPLICATION_ID FROM FND_FORM F, FND_APPLICATION A WHERE F.FORM_NAME
= :B4 AND F.APPLICATION_ID = A.APPLICATION_ID AND
A.APPLICATION_SHORT_NAME = :B3 )
Symptoms That Led to the Finding:
Wait class "Concurrency" was consuming significant database time.
Impact is 2.53 active sessions, 48.87% of total activity.
Finding 4: Log File Switches
Impact is .91 active sessions, 17.56% of total activity.
Log file switch operations were consuming significant database time while
waiting for checkpoint completion.
This problem can be caused by use of hot backup mode on tablespaces. DML to
tablespaces in hot backup mode causes generation of additional redo.
Recommendation 1: Database Configuration
Estimated benefit is .91 active sessions, 17.56% of total activity.
Action
Verify whether incremental shipping was used for standby databases.
Symptoms That Led to the Finding:
Wait class "Configuration" was consuming significant database time.
Impact is .91 active sessions, 17.63% of total activity.
Finding 5: Buffer Busy
Impact is .56 active sessions, 10.87% of total activity.
A hot data block with concurrent read and write activity was found. The block
belongs to segment "ICX.ICX_SESSIONS" and is block 243489 in file 36.
Recommendation 1: Application Analysis
Estimated benefit is .56 active sessions, 10.87% of total activity.
Action
Investigate application logic to find the cause of high concurrent read
and write activity to the data present in this block.
Related Object
Database block with object number 37562, file number 36 and block
number 243489.
Rationale
The SQL statement with SQL_ID "5d7957yktf3nn" spent significant time on
"buffer busy" waits for the hot block.
Related Object
SQL statement with SQL_ID 5d7957yktf3nn.
UPDATE ICX_SESSIONS SET TIME_OUT = :B2 WHERE SESSION_ID = :B1
Rationale
The SQL statement with SQL_ID "326up1aym56dd" spent significant time on
"buffer busy" waits for the hot block.
Related Object
SQL statement with SQL_ID 326up1aym56dd.
UPDATE ICX_SESSIONS SET LAST_CONNECT = SYSDATE WHERE SESSION_ID = :B1
Recommendation 2: Schema Changes
Estimated benefit is .56 active sessions, 10.87% of total activity.
Action
Consider rebuilding the TABLE "ICX.ICX_SESSIONS" with object ID 37562
using a higher value for PCTFREE.
Related Object
Database object with ID 37562.
Symptoms That Led to the Finding:
Wait class "Concurrency" was consuming significant database time.
Impact is 2.53 active sessions, 48.87% of total activity.
Finding 6: Undersized SGA
Impact is .38 active sessions, 7.37% of total activity.
The SGA was inadequately sized, causing additional I/O or hard parses.
The value of parameter "sga_target" was "4096 M" during the analysis period.
Recommendation 1: Database Configuration
Estimated benefit is .12 active sessions, 2.33% of total activity.
Action
Increase the size of the SGA by setting the parameter "sga_target" to
4608 M.
Symptoms That Led to the Finding:
Wait class "User I/O" was consuming significant database time.
Impact is .7 active sessions, 13.57% of total activity.
Hard parsing of SQL statements was consuming significant database time.
Impact is .13 active sessions, 2.51% of total activity.
Contention for latches related to the shared pool was consuming
significant database time.
Impact is 0 active sessions, .03% of total activity.
Wait class "Concurrency" was consuming significant database time.
Impact is 2.53 active sessions, 48.87% of total activity.
Finding 7: Commits and Rollbacks
Impact is .28 active sessions, 5.42% of total activity.
Waits on event "log file sync" while performing COMMIT and ROLLBACK operations
were consuming significant database time.
Recommendation 1: Host Configuration
Estimated benefit is .28 active sessions, 5.42% of total activity.
Action
Investigate the possibility of improving the performance of I/O to the
online redo log files.
Rationale
The average size of writes to the online redo log files was 163 K and
the average time per write was 68 milliseconds.
Symptoms That Led to the Finding:
Wait class "Commit" was consuming significant database time.
Impact is .28 active sessions, 5.42% of total activity.
Finding 8: Undo I/O
Impact is .18 active sessions, 3.53% of total activity.
Undo I/O was a significant portion (26%) of the total database I/O.
No recommendations are available.
Symptoms That Led to the Finding:
The throughput of the I/O subsystem was significantly lower than
expected.
Impact is .08 active sessions, 1.46% of total activity.
Wait class "User I/O" was consuming significant database time.
Impact is .7 active sessions, 13.57% of total activity.
Finding 9: CPU Usage
Impact is .13 active sessions, 2.57% of total activity.
Time spent on the CPU by the instance was responsible for a substantial part
of database time.
Recommendation 1: SQL Tuning
Estimated benefit is .13 active sessions, 2.57% of total activity.
Finding 10: Top SQL By I/O
Impact is .11 active sessions, 2.21% of total activity.
Individual SQL statements responsible for significant user I/O wait were
found.
Recommendation 1: SQL Tuning
Estimated benefit is .11 active sessions, 2.22% of total activity.
Action
Run SQL Tuning Advisor on the SQL statement with SQL_ID "b3pnc5yctv2z5".
Related Object
SQL statement with SQL_ID b3pnc5yctv2z5.
INSERT INTO ZX_TRANSACTION_LINES_GT( APPLICATION_ID ,ENTITY_CODE
,EVENT_CLASS_CODE ,TRX_ID ,TRX_LEVEL_TYPE ,TRX_LINE_ID ,LINE_CLASS
,LINE_LEVEL_ACTION ,TRX_LINE_TYPE ,TRX_LINE_DATE
,LINE_AMT_INCLUDES_TAX_FLAG ,LINE_AMT ,TRX_LINE_QUANTITY ,UNIT_PRICE
,PRODUCT_ID ,PRODUCT_ORG_ID ,UOM_CODE ,PRODUCT_CODE ,SHIP_TO_PARTY_ID
,SHIP_FROM_PARTY_ID ,BILL_TO_PARTY_ID ,BILL_FROM_PARTY_ID
,SHIP_FROM_PARTY_SITE_ID ,BILL_FROM_PARTY_SITE_ID
,SHIP_TO_LOCATION_ID ,SHIP_FROM_LOCATION_ID ,BILL_TO_LOCATION_ID
,SHIP_THIRD_PTY_ACCT_ID ,SHIP_THIRD_PTY_ACCT_SITE_ID ,HISTORICAL_FLAG
,TRX_LINE_CURRENCY_CODE ,TRX_LINE_CURRENCY_CONV_DATE
,TRX_LINE_CURRENCY_CONV_RATE ,TRX_LINE_CURRENCY_CONV_TYPE
,TRX_LINE_MAU ,TRX_LINE_PRECISION ,HISTORICAL_TAX_CODE_ID
,TRX_BUSINESS_CATEGORY ,PRODUCT_CATEGORY ,PRODUCT_FISC_CLASSIFICATION
,LINE_INTENDED_USE ,PRODUCT_TYPE ,USER_DEFINED_FISC_CLASS
,ASSESSABLE_VALUE ,INPUT_TAX_CLASSIFICATION_CODE ,ACCOUNT_CCID
,BILL_THIRD_PTY_ACCT_ID ,BILL_THIRD_PTY_ACCT_SITE_ID ,TRX_LINE_NUMBER
,TRX_LINE_DESCRIPTION ,PRODUCT_DESCRIPTION ,USER_UPD_DET_FACTORS_FLAG
,DEFAULTING_ATTRIBUTE1 ) SELECT :B4 ,:B3 ,:B2
,PRL.REQUISITION_HEADER_ID ,:B1 ,PRL.REQUISITION_LINE_ID ,'INVOICE'
,NVL(PRL.TAX_ATTRIBUTE_UPDATE_CODE,'UPDATE') ,'ITEM'
,NVL(PRL.NEED_BY_DATE, SYSDATE) ,'N' ,NVL(PRL.AMOUNT,
PRL.UNIT_PRICE*PRL.QUANTITY) ,PRL.QUANTITY ,PRL.UNIT_PRICE
,PRL.ITEM_ID ,(SELECT FSP.INVENTORY_ORGANIZATION_ID FROM
FINANCIALS_SYSTEM_PARAMS_ALL FSP WHERE FSP.ORG_ID=PRL.ORG_ID)
,(SELECT MUM.UOM_CODE FROM MTL_UNITS_OF_MEASURE MUM WHERE
MUM.UNIT_OF_MEASURE=PRL.UNIT_MEAS_LOOKUP_CODE) ,MSIB.SEGMENT1
,PRL.DESTINATION_ORGANIZATION_ID ,PV.PARTY_ID ,PRH.ORG_ID
,PV.PARTY_ID ,PVS.PARTY_SITE_ID ,PVS.PARTY_SITE_ID
,PRL.DELIVER_TO_LOCATION_ID ,(SELECT HZPS.LOCATION_ID FROM
HZ_PARTY_SITES HZPS WHERE HZPS.PARTY_SITE_ID = PVS.PARTY_SITE_ID)
,(SELECT LOCATION_ID FROM HR_ALL_ORGANIZATION_UNITS WHERE
ORGANIZATION_ID=PRH.ORG_ID) ,PRL.VENDOR_ID ,PRL.VENDOR_SITE_ID ,NULL
,NVL(PRL.CURRENCY_CODE, :B9 ) ,NVL2(PRL.CURRENCY_CODE, PRL.RATE_DATE,
SYSDATE) ,NVL2(PRL.CURRENCY_CODE, PRL.RATE, :B8 )
,NVL2(PRL.CURRENCY_CODE, PRL.RATE_TYPE, :B7 )
,FC.MINIMUM_ACCOUNTABLE_UNIT ,NVL(FC.PRECISION, 2) ,NULL
,DECODE(PRL.TAX_ATTRIBUTE_UPDATE_CODE, 'CREATE',
NVL2(PRL.PARENT_REQ_LINE_ID, ZXLDET.TRX_BUSINESS_CATEGORY, NULL),
NULL ) ,DECODE(PRL.TAX_ATTRIBUTE_UPDATE_CODE, 'CREATE',
NVL2(PRL.PARENT_REQ_LINE_ID, ZXLDET.PRODUCT_CATEGORY, NULL), NULL )
,DECODE(PRL.TAX_ATTRIBUTE_UPDATE_CODE, 'CREATE',
NVL2(PRL.PARENT_REQ_LINE_ID, ZXLDET.PRODUCT_FISC_CLASSIFICATION,
NULL), NULL ) ,DECODE(PRL.TAX_ATTRIBUTE_UPDATE_CODE, 'CREATE',
NVL2(PRL.PARENT_REQ_LINE_ID, ZXLDET.LINE_INTENDED_USE, NULL), NULL )
,DECODE(PRL.TAX_ATTRIBUTE_UPDATE_CODE, 'CREATE',
NVL2(PRL.PARENT_REQ_LINE_ID, ZXLDET.PRODUCT_TYPE, NULL), NULL )
,DECODE(PRL.TAX_ATTRIBUTE_UPDATE_CODE, 'CREATE',
NVL2(PRL.PARENT_REQ_LINE_ID, ZXLDET.USER_DEFINED_FISC_CLASS, NULL),
NULL ) ,DECODE(PRL.TAX_ATTRIBUTE_UPDATE_CODE, 'CREATE',
NVL2(PRL.PARENT_REQ_LINE_ID, ZXLDET.ASSESSABLE_VALUE, NULL), NULL )
,DECODE(:B6 , 'REQIMPORT', PRL.TAX_NAME,
DECODE(PRL.TAX_ATTRIBUTE_UPDATE_CODE, 'CREATE',
NVL2(PRL.PARENT_REQ_LINE_ID, ZXLDET.INPUT_TAX_CLASSIFICATION_CODE,
NULL), NULL ) ) ,NVL((SELECT PRD.CODE_COMBINATION_ID FROM
PO_REQ_DISTRIBUTIONS_ALL PRD WHERE PRD.REQUISITION_LINE_ID =
PRL.REQUISITION_LINE_ID AND ROWNUM = 1), MSIB.EXPENSE_ACCOUNT )
,PV.VENDOR_ID ,PVS.VENDOR_SITE_ID ,PRL.LINE_NUM ,PRL.ITEM_DESCRIPTION
,PRL.ITEM_DESCRIPTION ,(SELECT 'Y' FROM DUAL WHERE :B6 = 'REQIMPORT'
AND PRL.TAX_NAME IS NOT NULL) ,PRL.DESTINATION_ORGANIZATION_ID FROM
PO_REQUISITION_HEADERS_ALL PRH, PO_REQUISITION_LINES_ALL PRL,
ZX_LINES_DET_FACTORS ZXLDET, PO_VENDORS PV, PO_VENDOR_SITES_ALL PVS,
MTL_SYSTEM_ITEMS_B MSIB, FND_CURRENCIES FC WHERE
PRH.REQUISITION_HEADER_ID = :B5 AND PRH.REQUISITION_HEADER_ID =
PRL.REQUISITION_HEADER_ID AND ZXLDET.APPLICATION_ID(+) = :B4 AND
ZXLDET.ENTITY_CODE(+) = :B3 AND ZXLDET.EVENT_CLASS_CODE(+) = :B2 AND
ZXLDET.TRX_LEVEL_TYPE(+) = :B1 AND ZXLDET.TRX_LINE_ID(+) =
PRL.PARENT_REQ_LINE_ID AND PV.VENDOR_ID(+) = PRL.VENDOR_ID AND
PVS.VENDOR_SITE_ID(+) = PRL.VENDOR_SITE_ID AND
MSIB.INVENTORY_ITEM_ID(+) = PRL.ITEM_ID AND MSIB.ORGANIZATION_ID(+) =
PRL.ORG_ID AND FC.CURRENCY_CODE(+) = PRL.CURRENCY_CODE AND
NVL(PRL.MODIFIED_BY_AGENT_FLAG, 'N') = 'N' AND NVL(PRL.CANCEL_FLAG,
'N') = 'N' AND NVL(PRL.CLOSED_CODE, 'OPEN') <> 'FINALLY CLOSED' AND
PRL.LINE_LOCATION_ID IS NULL AND PRL.AT_SOURCING_FLAG IS NULL
Rationale
SQL statement with SQL_ID "b3pnc5yctv2z5" was executed 3 times and had
an average elapsed time of 138 seconds.
Rationale
Average time spent in User I/O wait events per execution was 137
seconds.
Symptoms That Led to the Finding:
Wait class "User I/O" was consuming significant database time.
Impact is .7 active sessions, 13.57% of total activity.
Additional Information
Miscellaneous Information
Wait class "Application" was not consuming significant database time.
Wait class "Network" was not consuming significant database time.
Session connect and disconnect calls were not consuming significant database
time.
The database's maintenance windows were active during 100% of the analysis
period.
Regards
Athish

Few days are am facing serious of performance problem in our Production instanceFor production issues, please log a SR.
Was this working before? If yes, any changes been done recently?
Do you have the statistics collected up to date?
Please see these docs.
AutoInvoice Performance Issue When Processing Tax [ID 1059275.1]
R12 : System Hangs When Attempting To Save Blanket Release After Applying Patch 11817843 [ID 1333336.1]
Thanks,
Hussein

Performance issue on Fiscal period.

Similar Messages

Maybe you are looking for