Purpose of ST02, ST03, ST04

hi,
Whats the Purpose of ST02, ST03, ST04. and what exactly we can do witg these T-codes
Regards
Ganesh

Hi Ganesh,
This transactions are statistic transactions, ST02 show you the memory utilization and buffers, ST03/ST03N show you the performance of the processes, ST04 is the SQL Server Database Monitor.
Hope this help!
Juan
Please reward with points if helpful

Similar Messages

  • Performance analysis  in tcode st02, st03, st04, st06

    what performance analysis we will do in tcode st02, st03, st04, st06. I want to know the in detail calculation.
    Thanks.
    Rohit

    Hi,
    Buffer: The first column shows the names of the buffers:
    Four ABAP repository buffers.
    The program, CUA, screen, and calendar buffers.
    The table buffers.
    Hit Ratio:
              A hit is when an object (such as a table, screen, or program) in the buffer is accessed. If the object has to be read from the database, the buffer access fails.
    Allocated Size:
            The allocated size is measured in KB. It is different from the available buffer size because a part of the size is used for buffer management.
    Freespace :    
            Freespace is important for analyzing the buffer size. The space remaining in the buffer is displayed in KB and percentage of the available buffer size.
    Number of Directories:
                 Even though there is freespace in the buffer, objects may not always be loaded into the buffer because there are no more free directories. The Buffers Monitor displays the number of directories available for the buffer, and the number and percentage free. The buffer directories point to the location of the objects that are located in the buffer.
    Swapping:
                    When a buffer has insufficient freespace or free directories, it has to swap objects out of the buffer in order to load a new object. The column Swap shows how many objects have been swapped out since system startup.
    Database Accesses
                          When an object cannot be read from the buffer, the database has to be accessed. The number ofdatabase accesses is displayed in the last column of this screen.

  • ST02 / ST03 Troubleshooting

    Dear Experts,
    do you have any guidline or checklist on what to do if there are swaps problems on ST02 or Response Time Problems on ST03?
    Thanks a lot for any help!
    Regards,
    Marc

    Hi Marc,
    Swaping happens if the data is not availabel in various buffers as it needs to access the database for the rquired data. there are various parameters which needs to be taken care of. Please check the values of the parameters if required finetune them.
    Program:abap/buffersize
    GenericKey:zcsa/table_buffer_area Bytes
    Entries: zcsa/db_max_buftab
    SingleRecord Size: rtbb/buffer_length
    Screen:zcsa/presentation_buffer_area Bytes
    CUA rsdb/cua/buffersize
    Table Definition Size is determined by the number of entries
    Entries: rsdb/ntab/entrycount
    Field Description Size: rsdb/ntab/ftabsize
    Entries: 2 * rsdb/ntab/entrycount + 1
    Initial Records
    Size: rsdb/ntab/irbdsize
    Entries: 2 * rsdb/ntab/entrycount + 1
    ShortNameTAB
    Size: rsdb/ntab/sntabsize
    ST03 performance problem
    Check which component (CPU/Dialog/Batch etc) is taking more time and then you have take appropriate actions
    1) I would suggest to Investigate the select statements more closely. Discover which tables and indexes they are using transaction ST04 > detailed analysis tab. if index are not there consider creating indexes.
    2) Execute / check update statistics.
    3)find the ZTcodes and Zprograms which are taking more time and you have to work with ABAP and Fuctional teams to stream line the programs and Tcodes.
    Thank you,
    Shyam

  • Performance Transactions

    Hai All,
    I am Farooq, the only individual for a Company working on ABAP from about 3 months. Please let me know all the details with Transactions of Performance Tuning, SQL Trace, & different other Traces.
    Now I have come across <b>ST01, ST02, ST03, ST04, ST05, ST06, ST07, ST11, ST14, ST20, ST22, ST30, ST33, ST35, ST36, ST37, ST62</b>. I am hardly aware of anything in these. I know little about <b>ST05</b> only & very interested to learn much more.
    May be explaining all these may take much time & is not Possible here. So its OK even if U take your own time & send across any documents or mails to my ID, "[email protected]" when u r free. I would be very thankful to U. <b>THANKS a lot in advance.</b>
    Best Regards & wishes.
    Farooq

    Hi Farooq
    There is SDN link <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5d0db4c9-0e01-0010-b68f-9b1408d5f234">Performance tuning SAP R/3 and Oracle DB</a>
    It is a very good document discussing about tools provided by R/3 and fine tuning R/3 access with Oracle DB.
    Further: The SAP online help (http://help.sap.com/saphelp_47x200/helpdata/en/14/6d1c370c468b7be10000009b38f936/frameset.htm) provides comprehensive details about the other tools such as:
    Debugger
    Runtime Analysis
    Coverage Analyzer
    Runtime Monitor
    Hope this helps
    Cheers!!
    Harsha

  • Performance Transactions & Details

    Hai All,
    I am Farooq, the only individual for a Company working on ABAP from about 3 months. Please let me know all the details with Transactions of Performance Tuning, SQL Trace, & different other Traces.
    Now I have come across  <b>ST01, ST02, ST03, ST04, ST05, ST06, ST07, ST11, ST14, ST20, ST22, ST30, ST33, ST35, ST36, ST37, ST62</b>. I am hardly aware of anything in these. I know little about <b>ST05</b> only & very interested to learn much more.
    May be explaining all these may take much time & is not Possible here. So its OK even if U take your own time & send across any documents or mails to my ID, "[email protected]" when u r free. I would be very thankful to U. <b>THANKS a lot</b> in advance.
    Best Regards & wishes.
    Farooq

    Farooq,
    You can use SE30 for doing run time analysis of what is going on in the program which part has taken how much time .
    What is the data base time and what is program run time all details are available in this transaction.
    Using ST05 u can identfy which table is taking time to query, What index it is using .. by this we can decide to do secondary indexing in the table .
    At times it will also be neceesary from Basis side to re-build the index, re-build the statistics tables which will also improvise the performance .
    I will send u doucment  on performance tuning for programming.
    Regards
    R. Ramvelu
    [email protected]

  • St02-03-04-06 how to interpret?

    Hello,
    in the tcode st02 st03n st04 and st06, there are many voices.
    But which of them are most important for a quick bottleneck analyze?

    For Bottleneck Analysis..in short i check this way.
    SM50 - WP status ( Find what is creating the block) A quick analysis would give its a SPACE [DB issue or at OS level issue]
    If its OS go to -> ST06 (FileSys)(Memory) used at times
    If its DB go to -> ST04  (State on disk - DB02)and Lock Wait situtations.
    ST03N is utilised for User - Tcoide analysis and other stuff which is discussed at length in many threads.
    Ifits an SAP (Application level) issue..then jump to ST22 and SM21 (My best frds)
    Hope the inputs are helpful in some sense to make up your mind. Also awaiting inputs from others on their views
    Br,
    Sri
    Awards points if helpful.

  • SWAP - ST02

    Hi Gurus, I am doing daily monitoring for a server.  Right in ST02 t-code i have some issue which i dont know how to resolve it.
    One of the buffer which is Table Definition buffer directory is getting filled and increase day by day.
    Buffer               HitRatio % Alloc. KB Freesp. KB % Free Sp. Dir. Size FreeDirEnt % Free Dir   Swaps    DB Accs
    Table definition     99.69    4,924           8      0.21         20,000      40             0.20         0          0      74,946
    Day by day the directory size is just keep increasing. I dont have confident to tune-up the parameter setting in Production system. Even when i checked the Program buffer free directory size is 0.40% at the moment. I also have monitor that occuring in the program buffer day by day. From yesterday until today the swap that was occured was 24560 swaps. So i need your guideline what to do next in regards to this. I would sincerely appreciate your kind guidance and help.
    Thank You.

    Hi
    Go through following links for ST02 & ST03 in sap help portal. it will give you fair idea of memnory management and work load analysis.
    [Link1|http://help.sap.com/saphelp_nw70/helpdata/EN/02/96263e538111d1891b0000e8322f96/content.htm]
    [Link2|http://sap.ittoolbox.com/groups/technical-functional/sap-basis/high-rollwait-time-1514656?cv=expanded]
    [Link3|http://help.sap.com/saphelp_nw70/helpdata/EN/95/8a393c3ab01224e10000000a11405a/content.htm]
    Regards
    Uday

  • Performance - Where the problem is ?

    Hi All,
    I'm in urgent need to find out system performance.
    I need to outline the various components of the response time with data and interpret the results to outline where the problem is?
    How can i do this.. Please provide me some suggestions...
    Expecting your valuable replies.
    Thanks
    Cheenu

    Hello,
    The bottle neck could be at the Os,DB or R/3 level.
    The performance analysis can be started from st03/st03n.
    Check the dialog response time here.Under this you can also see if the DB response time is high or the OS time.
    Depending on htis you have navigate to st02 or st04.
    ST02-->check for the buffer,swaps & shared memory.
    ST04-->check for the DB cache, DB buffer quality.
    Also you can use transactions sm50,sm66 incase your system is slow.It will show if the system is overloaded.
    Hope this helps.
    Regards,Prasanna

  • Weekly response time of workproces

    hi
    1.how to check weekly  response time of a particular work process?
    2. does abap program which is usually developed by our abapers is client specific or cross client?

    Hi Ramesh,
    ABAP programs are cross client. They are repository objects!!!.
    Dont know if it is possible to check repsonse time of a process as such. Yes you can do an performance analysis of dialog/background,update WPs etc. as a bunch but individual process analysis in terms of weekly data.. I have no idea. Anyways it makes sense to do this analysis for type of workprocess and not a workprocess in itself. It is not as if a workprocess is performing well you are going to replace it with something new :-). For system performance analysis ST02,ST03,ST03N,ST04 and ST06 are best transactions though check ST03 and ST03N in your case of process response time analysis. May be you will find historical details of an individual work process using ST03N. Wish u luck.
    Please award points for useful info.
    Regards.
    Ruchit.

  • SAP daily checking

    hi all
    I'm assigned by my boss to create SAP daily check (Critical section)
    Need your suggestion what to check
    I already put DB13, DB14, ST02, ST03
    but I need in detail, for example.. on ST02 the program buffer should not > 10.000
    My friend said I have to put the log file in OS system also, but I don't know what log and where is the path?
    and what to check inside the log?
    Also, my boss concern about free space, he told me to aware about the free space.
    So, what filesystem should I check everyday? /oracle/SID/oraarch, /usr/sap/trans? and??
    thanks in advance
    regards,
    Della

    Hi Rosa,
    Tcode sm12 used for lock management .With this you are able to determine which locks are being used currently.You can detect and correct problems by deleting locks that you no longer want. You can also later analyze the cause of lock table overflows using the History .
    In tcode sm12 you can see which type the lock object is with the help of Lock mode.Where S: shared lock, E: exclusive lock, X: exclusive and not cumulative, O: optimistic lock. Again from Table name column you are able to know in which row of the table are locked.From Lock argument column you are able to see the argument (key field) of the lock entry.
    Lock entry with Blue color means that the locks have already been transferred to the update task (see also The Owner Concept), with the result that the backup flag is set. These locks are also rewritten to the lock table when the enqueue server is restarted.Black means that the lock (still) belongs to the dialog owner. The backup flag is not set.By double-clicking a lock entry, you can display detailed information, including the host name and number of the SAP System in which the lock was generated.Rosa remember never delete a lock when you are unsure and/or don't know what is this lock for.If you delete a lock without proper justification may be it generate an inconsistence.Locks are put on table and / or table entries when a process needs exclusive access to this DB table and/or record. Removing this lock could let for example another process to change the same data while the process is still running thus generating inconsistence.
    Always try to match a lock with a process in SM66, a background Job in SM37, a DB session, in ST04 / detailed analysis / sessions or a user logged in with AL08/SM04.
    If you have identified from where does the lock come, then first try to kill the job, then the related process, then kick the user out (best would be to ask him what is he doing) and finally the DB session.
    Usually one of this action will remove the lock cleanly.If it is not the case, deleting a lock in SM12 would be the very last option.
    The ABAP Dumps will occur with respective of the problem.If you got the error. check the error name and serach in.
    http://service.sap.com/notes.
    Few of the most frequently occuring dumps are :
    1) TIME_OUT : this happens due to longer dialog execution time for a user compared to the parameter settings. We can ask the user to run the report in batch jobs instead of dialog. we can ask the user to reduce the search criteria if he is using one.
    2) RAISE_EXCEPTION : This is due to error in exception handling of the abap program. If its a customer report we can ask the developer to modify code or if its a sap report we can raise issue with sap
    3) DBIF_SQL_ERROR: this happens due to various problems with database.
    suppose user is trying to write duplicate entries to the tables then it occurs, if there is problem with the datafile then also it occurs. you have to read the details of the error.
    4) TSV_NEW_PAGE_ALLOCATION_FAILED: Error due to not enough extended memory to run the report. This happens during high memory usage time, We can ask the user to run the report during less load and also to reduce the input criteria which will in turn reduce the processing memory required for the internal table.
    or we need to increase the extended memory parameters.
    5) MEMORY_NO_MORE_PAGING: happens due to not enough space in paging area. Can be solved by increasing the paging file parameter value.
    6) LOAD_PROGRAM_ERROR: this error happens if during runtime any of the repository objects are changed by means of transport. We can ask the user to rerun the program.

  • System log analysis

    Logwatch is old, arcane, difficult to modify, seemingly abandoned upstream, and written in Perl.  I haven't found a decent substitute that addresses all of these shortcomings, so I started hacking up my own: http://tam.hiddenrock.com/projects/cyclops.  It's still rough, but I think it's ready for public consumption.  I'd appreciate it if you would check out the README and TODO, beat on it, let me know how it breaks, point out better Python practices, and suggest improvements.
    Thanks!

    Hi,
    the correct transaction code for reading system log is <u><b>sm21</b></u> ...
    other usefull transactions for system checks :
    DB02 : table and indexes and monitor
    DB04 : DB performance monitor
    DB12 : Backup logs
    DB16 : overview of database check messages
    st02, st03 and st04 can also be usefull ...
    these are all helpfull systemcheck transactions ... Quite usefull to have as an SAP BW specialist ..
    hope this would help !
    best regards,
    Davy

  • How to avoid spaces in csv file at the time of spooling

    Hi all,
    I am spooling 30 query results into one CSV file ,I am getting two empty rows for each query.
    Can any one suggest me how to avoid these spaces.
    Thanks & Regards,
    P Prakash
    this is the script i am using to generate csv file .
    SET linesize 12000
    SET pagesize 10000
    SET pause off
    SET termout off
    SET feed off
    SET head off
    SPOOL c:\tes111.csv replace
    SELECT 'ISA01,ISA02,ISA03,ISA04,ISA05,ISA06,ISA07,ISA08,ISA09,ISA11,ISA12,ISA13,ISA14,ISA15,ISA16,GS01,GS02,GS03,GS04,GS05,GS06,GS07,GS08,ST01,ST02,ST03,BHT01,BHT02,BHT03,BHT04,BHT06,trnsctn_segment_count,included_trnsctn_sets_count,included_fnctnl_groups_count,input_acknwldgmnt_sid'
    FROM DUAL;
    SELECT ptr.athrztn_infrmtn_qlfr
    || ','
    || ptr.athrztn_infrmtn
    || ','
    || ptr.scrty_infrmtn_qlfr
    || ','
    || ptr.scrty_infrmtn
    || ','
    || ptr.intrchng_sndr_idntfr_qlfr
    || ','
    || ptr.intrchng_sndr_idntfr
    || ','
    || ptr.intrchng_rcvr_idntfr_qlfr
    || ','
    || ptr.intrchng_rcvr_idntfr
    || ','
    || ptr.intrchng_date
    || ','
    || ptr.intrchng_cntrl_stndrds_idntfr
    || ','
    || ptr.intrchng_cntrl_vrsn_nmbr
    || ','
    || ptr.intrchng_cntrl_nmbr
    || ','
    || ptr.acknwldgmnt_rqstd_indctr
    || ','
    || ptr.usg_indctr
    || ','
    || ptr.cmpnt_elmnt_sprtr
    || ','
    || ptr.fnctnl_idntfr_code
    || ','
    || ptr.aplctn_sndr_code
    || ','
    || ptr.applctn_rcvr_code
    || ','
    || ptr.fnctnl_grp_crtn_date
    || ','
    || ptr.fnctnl_grp_crtn_date
    || ','
    || ptr.grp_cntrl_nmbr
    || ','
    || ptr.rspnsbl_agncy_code
    || ','
    || ptr.vrsn_rls_indstry_idntfr_code
    || ','
    || ptr.trnsctn_set_idntfr_code
    || ','
    || ptr.trnsctn_set_cntrl_nmbr
    || ','
    || ptr.implementation_guide_vrsn_name
    || ','
    || ptr.hierarchical_structure_code
    || ','
    || ptr.trnsctn_set_purpose_lkpcd
    || ','
    || ptr.sbmtr_trnsctn_idntfr
    || ','
    || ptr.trnsctn_set_creation_date
    || ','
    || ptr.trnsctn_type_code
    || ','
    || ptr.trnsctn_segment_count
    || ','
    || ptr.included_trnsctn_sets_count
    || ','
    || ptr.included_fnctnl_groups_count
    || ','
    || ia.input_acknwldgmnt_sid
    || ','
    FROM pa_transaction_request ptr, input_acknwldgmnt ia, input_batch_file ibf
    WHERE ptr.input_acknwldgmnt_sid = ia.input_acknwldgmnt_sid
    AND ia.input_batch_file_sid = ibf.input_batch_file_sid
    AND ibf.original_file_name =
    'HIPAA.165760000.20110518I001.278_GC04-3.dat';
    SELECT 'pa_rqst_sid,NM01,NM02,NM108,NM109'
    FROM DUAL;
    SELECT pr.pa_rqst_sid
    || ','
    || pr.entity_idntfr_lkpcd
    || ','
    || pr.entity_type_qlfr
    || ','
    || pr.payer_idntfctn_code_qlfr
    || ','
    || pr.payer_idntfctn_code
    || ','
    FROM pa_request pr,
    pa_transaction_request ptr,
    input_acknwldgmnt ia,
    input_batch_file ibf
    WHERE pr.pa_trnsctn_rqst_sid = ptr.pa_trnsctn_rqst_sid
    AND ptr.input_acknwldgmnt_sid = ia.input_acknwldgmnt_sid
    AND ia.input_batch_file_sid = ibf.input_batch_file_sid
    AND ibf.original_file_name =
    'HIPAA.165760000.20110518I001.278_GC04-3.dat';
    SELECT 'meta_data_cid,data_value,iteration_number,Created_by,modified_by'
    FROM DUAL;
    SELECT prs.meta_data_cid
    || ','
    || prs.data_value
    || ','
    || prs.iteration_number
    || ','
    || prs.created_by
    || ','
    || prs.modified_by
    || ','
    FROM pa_request pr,
    pa_transaction_request ptr,
    input_acknwldgmnt ia,
    input_batch_file ibf,
    pa_request_situational prs
    WHERE pr.pa_rqst_sid = prs.pa_rqst_sid
    AND prs.stnl_target_table_cid = 100
    AND prs.target_table_sid = pr.pa_rqst_sid
    AND pr.pa_trnsctn_rqst_sid = ptr.pa_trnsctn_rqst_sid
    AND ptr.input_acknwldgmnt_sid = ia.input_acknwldgmnt_sid
    AND ia.input_batch_file_sid = ibf.input_batch_file_sid
    AND ibf.original_file_name =
    'HIPAA.165760000.20110518I001.278_GC04-3.dat';
    SELECT 'NM101 ,NM103,NM104,NM105,NM108,NM109,PER02,PER04,PER05,PER06,PER07 ,PER08'
    FROM DUAL;
    SELECT pr.pa_rqst_sid
    || ','
    || prpl.pa_rqst_x_prvdr_lctn_sid
    || ','
    || prpl.rqstr_entity_idntfr_lkpcd
    || ','
    || prpl.last_name
    || ','
    || prpl.first_name
    || ','
    || prpl.middle_name
    || ','
    || prpl.idntfr_type_cid
    || ','
    || prpl.prvdr_lctn_iid
    || ','
    || prpl.rqstr_contact_name
    || ','
    || prpl.cmnctn_nmbr_1
    || ','
    || prpl.cmnctn_nmbr_2
    || ','
    || prpl.cmnctn_nmbr_type_lkpcd_1
    || ','
    || prpl.cmnctn_nmbr_type_lkpcd_2
    || ','
    || prpl.cmnctn_nmbr_type_lkpcd_3
    FROM pa_request_x_provider_location prpl,
    pa_request pr,
    pa_transaction_request ptr,
    input_acknwldgmnt ia,
    input_batch_file ibf
    WHERE prpl.pa_rqst_sid = pr.pa_rqst_sid
    AND pr.pa_trnsctn_rqst_sid = ptr.pa_trnsctn_rqst_sid
    AND ptr.input_acknwldgmnt_sid = ia.input_acknwldgmnt_sid
    AND ia.input_batch_file_sid = ibf.input_batch_file_sid
    AND ibf.original_file_name =
    'HIPAA.165760000.20110518I001.278_GC04-3.dat'
    AND prpl.pa_prvdr_type_lkpcd = 'RR';
    SELECT 'meta_data_cid,data_value,iteration_number,Created_by,modified_by'
    FROM DUAL;
    SELECT prs.meta_data_cid
    || ','
    || prs.data_value
    || ','
    || prs.iteration_number
    || ','
    || prs.created_by
    || ','
    || prs.modified_by
    || ','
    FROM pa_request_x_provider_location prpl,
    pa_request pr,
    pa_transaction_request ptr,
    input_acknwldgmnt ia,
    input_batch_file ibf,
    pa_request_situational prs
    WHERE prpl.pa_rqst_sid = prs.pa_rqst_sid
    AND prs.stnl_target_table_cid = 102
    AND prs.target_table_sid = prpl.pa_rqst_x_prvdr_lctn_sid
    AND prpl.pa_rqst_sid = pr.pa_rqst_sid
    AND pr.pa_trnsctn_rqst_sid = ptr.pa_trnsctn_rqst_sid
    AND ptr.input_acknwldgmnt_sid = ia.input_acknwldgmnt_sid
    AND ia.input_batch_file_sid = ibf.input_batch_file_sid
    AND ibf.original_file_name =
    'HIPAA.165760000.20110518I001.278_GC04-3.dat'
    AND prpl.pa_prvdr_type_lkpcd = 'RR';
    -- 4. Subscriber
    NM103 Name Last or Organization Name
    NM104 Name First
    NM108 Identification Code Qualifier
    NM109 Identification Code
    DMG02 Date Time Period birth date
    DMG03 Gender Code
    SELECT ' NM103,NM104,NM108,NM109,DMG02,DMG03'
    FROM DUAL;
    SELECT prxm.last_name
    || ','
    || prxm.first_name
    || ','
    || prxm.idntfr_type_cid
    || ','
    || prxm.mbr_idntfr
    || ','
    || prxm.birth_date
    || ','
    || prxm.gender_lkpcd
    || ','
    FROM pa_request_x_member prxm,
    pa_request pr,
    pa_transaction_request ptr,
    input_acknwldgmnt ia,
    input_batch_file ibf
    WHERE prxm.pa_rqst_sid = pr.pa_rqst_sid
    AND pr.pa_trnsctn_rqst_sid = ptr.pa_trnsctn_rqst_sid
    AND ptr.input_acknwldgmnt_sid = ia.input_acknwldgmnt_sid
    AND ia.input_batch_file_sid = ibf.input_batch_file_sid
    AND ibf.original_file_name =
    'HIPAA.165760000.20110518I001.278_GC04-3.dat';
    -- 5. Subscriber Situational Info
    NM102 Entity Type Qualifier
    NM105 Name Middle
    NM107 Name Suffix
    REF01 Reference Identification Qualifier
    REF02 Reference Identification
    N301 Address Information
    N302 Address Information
    N401 City Name
    N402 State or Province Code
    N403 Postal Code
    N407 Country Subdivision Code
    SELECT 'meta_data_cid,data_value,iteration_number,Created_by,modified_by'
    FROM DUAL;
    SELECT prs.meta_data_cid
    || ','
    || prs.data_value
    || ','
    || prs.iteration_number
    || ','
    || prs.created_by
    || ','
    || prs.modified_by
    || ','
    FROM pa_request_x_member prxm,
    pa_request pr,
    pa_transaction_request ptr,
    input_acknwldgmnt ia,
    input_batch_file ibf,
    pa_request_situational prs
    WHERE prxm.pa_rqst_sid = pr.pa_rqst_sid
    AND pr.pa_trnsctn_rqst_sid = ptr.pa_trnsctn_rqst_sid
    AND ptr.input_acknwldgmnt_sid = ia.input_acknwldgmnt_sid
    AND ia.input_batch_file_sid = ibf.input_batch_file_sid
    AND prs.stnl_target_table_cid = 101
    AND prs.target_table_sid = prxm.pa_rqst_x_mbr_sid
    AND ibf.original_file_name =
    'HIPAA.165760000.20110518I001.278_GC04-3.dat';
    -- 6. Patient Event Level
    TRN02 Reference Identification
    TRN03 Originating Company Identifier
    TRN04 Reference Identification
    UM01 Request Category Code
    UM02 Certification Type Code
    UM03 Service Type Code
    UM04-1 Facility Code Value
    UM04-2 Facility Code Qualifier
    UM06 Level of Service Code
    UM07 Current Health Condition Code
    UM08 Prognosis Code
    UM09 Release of Information Code
    UM10 Delay Reason Code
    SELECT 'TRN02,TRN03,TRN04,UMO1,UMO2,UM04_1,UM04_2,UM06,UM07,UM08,UM09,UM10,'
    FROM DUAL;
    SELECT prd.patient_event_tracking_number
    || ','
    || prd.orginating_company_identifier
    || ','
    || prd.trace_assigning_entity_idntfr
    || ','
    || prs.rqst_ctgry_lkpcd
    || ','
    || prs.rqst_crtfctn_type_lkpcd
    || ','
    || prs.x12_pa_srvc_type_code
    || ','
    || prs.facility_type_code
    || ','
    || prs.unfrm_blng_facility_type_code
    || ','
    || prs.srvc_rqd_lkpcd
    || ','
    || prs.current_health_cndtn_lkpcd
    || ','
    || prs.prognosis_lkpcd
    || ','
    || prs.rls_of_info_lkpcd
    || ','
    || prs.delay_reason_lkpcd
    || ','
    FROM pa_request_service prs,
    pa_request pr,
    pa_transaction_request ptr,
    input_acknwldgmnt ia,
    input_batch_file ibf,
    pa_request_detail prd
    WHERE prs.pa_rqst_sid = pr.pa_rqst_sid
    AND pr.pa_trnsctn_rqst_sid = ptr.pa_trnsctn_rqst_sid
    AND ptr.input_acknwldgmnt_sid = ia.input_acknwldgmnt_sid
    AND ia.input_batch_file_sid = ibf.input_batch_file_sid
    AND pr.pa_rqst_sid = prd.pa_rqst_sid
    AND ibf.original_file_name =
    'HIPAA.165760000.20110518I001.278_GC04-3.dat';
    --Patient Event Level situational information
    SELECT 'meta_data_cid,data_value,iteration_number,Created_by,modified_by'
    FROM DUAL;
    SELECT prs.meta_data_cid
    || ','
    || prs.data_value
    || ','
    || prs.iteration_number
    || ','
    || prs.created_by
    || ','
    || prs.modified_by
    || ','
    FROM pa_request_service prsv,
    pa_request pr,
    pa_transaction_request ptr,
    input_acknwldgmnt ia,
    input_batch_file ibf,
    pa_request_situational prs
    WHERE prsv.pa_rqst_sid = pr.pa_rqst_sid
    AND pr.pa_trnsctn_rqst_sid = ptr.pa_trnsctn_rqst_sid
    AND ptr.input_acknwldgmnt_sid = ia.input_acknwldgmnt_sid
    AND ia.input_batch_file_sid = ibf.input_batch_file_sid
    AND prs.stnl_target_table_cid = 103
    AND prs.target_table_sid = prsv.pa_rqst_srvc_sid
    AND ibf.original_file_name =
    'HIPAA.165760000.20110518I001.278_GC04-3.dat';
    ---Diagnosis
    HI01 Health Care Code Information
    HI01-1 Code List Qualifier Code
    HI01-2 Industry Code
    HI01-3 Date Time Period Format Qualifier
    HI01-4 Date Time Period
    SELECT 'HI01_1,HI01_2,HI01_3'
    FROM DUAL;
    SELECT prd.pa_diagnosis_type_lkpcd
    || ','
    || prd.diagnosis_iid
    || ','
    || prd.from_date
    || ','
    FROM pa_request_x_diagnosis prd,
    pa_request pr,
    pa_transaction_request ptr,
    input_acknwldgmnt ia,
    input_batch_file ibf
    WHERE prd.pa_rqst_sid = pr.pa_rqst_sid
    AND pr.pa_trnsctn_rqst_sid = ptr.pa_trnsctn_rqst_sid
    AND ptr.input_acknwldgmnt_sid = ia.input_acknwldgmnt_sid
    AND ia.input_batch_file_sid = ibf.input_batch_file_sid
    AND ibf.original_file_name =
    'HIPAA.165760000.20110518I001.278_GC04-3.dat';
    -- Request detail
    TRN02 Reference Identification
    TRN03 Originating Company Identifier
    TRN04 Reference Identification
    SELECT 'TRN02,TRN03,TRN04'
    FROM DUAL;
    SELECT prd.patient_event_tracking_number
    || ','
    || prd.orginating_company_identifier
    || ','
    || prd.trace_assigning_entity_idntfr
    || ','
    FROM pa_request_detail prd,
    pa_request pr,
    pa_transaction_request ptr,
    input_acknwldgmnt ia,
    input_batch_file ibf
    WHERE prd.pa_rqst_sid = pr.pa_rqst_sid
    AND pr.pa_trnsctn_rqst_sid = ptr.pa_trnsctn_rqst_sid
    AND ptr.input_acknwldgmnt_sid = ia.input_acknwldgmnt_sid
    AND ia.input_batch_file_sid = ibf.input_batch_file_sid
    AND ibf.original_file_name =
    'HIPAA.165760000.20110518I001.278_GC04-3.dat';
    -- ambulance Transaportation
    CR101 Unit or Basis for Measurement Code
    CR102 Weight
    CR103 Ambulance Transport Code
    CR104 Ambulance Transport Reason Code
    CR105 Unit or Basis for Measurement Code
    CR106 Quantity
    CR109 Description
    CR110 Description
    SELECT 'CR101,CR102,CR103,CR104,CR105,CR106,CR109,CR110'
    FROM DUAL;
    SELECT pat.weight_uom_code
    || ','
    || pat.patient_weight
    || ','
    || pat.amblnc_transport_type_lkpcd
    || ','
    || pat.amblnc_transport_rsn_lkpcd
    || ','
    || pat.distance_uom_code
    || ','
    || pat.trnsprtn_distance
    || ','
    || pat.round_trip_purpose_desc
    || ','
    || pat.stretcher_purpose_desc
    || ','
    FROM pa_request_ambulance_transport pat,
    pa_request pr,
    pa_transaction_request ptr,
    input_acknwldgmnt ia,
    input_batch_file ibf
    WHERE pat.pa_rqst_sid = pr.pa_rqst_sid
    AND pr.pa_trnsctn_rqst_sid = ptr.pa_trnsctn_rqst_sid
    AND ptr.input_acknwldgmnt_sid = ia.input_acknwldgmnt_sid
    AND ia.input_batch_file_sid = ibf.input_batch_file_sid
    AND ibf.original_file_name =
    'HIPAA.165760000.20110518I001.278_GC04-3.dat';
    -- 2000F SV1
    SV101-1 Product/Service ID Qualifier Change values
    SV101-2 Product/Service ID Need to change label to Procedure Code.
    SV101-3 Procedure Modifier No change required to PA screen
    SV101-4 Procedure Modifier No change required to PA screen
    SV101-5 Procedure Modifier No change required to PA screen
    SV101-6 Procedure Modifier No change required to PA screen
    SV101-7 Description No change required to PA screen. Will map to the Remarks field on the Screen
    SV102 Monetary Amount
    SV103 Unit or Basis for Measurement Code
    SV104 Quantity
    SV107 Composite Diagnosis Code Pointer
    SV107-1 Diagnosis Code Pointer
    SV107-2 Diagnosis Code Pointer
    SV107-3 Diagnosis Code Pointer
    SV107-4 Diagnosis Code Pointer
    SV111 Yes/No Condition or Response Code
    SV120 Level of Care Code
    SELECT 'TRN_Reference_Identif,TRN_Originating_CMP_Identif,TRN_Reference_IdentiReference Identiff,Reference_Identif,Reference_Identification,Reference_Identif,Product/Service_ID_Qualifier,Product/Service_ID,Procedure_Modifier,Procedure_Modifier,Procedure_Modifier,Procedure_Modifier,Description'
    FROM DUAL;
    SELECT prp.srvc_trace_nmbr_1
    || ','
    || prp.trace_asgn_enty_adtnl_idntfr_1
    || ','
    || prp.trace_asgn_enty_adtnl_idntfr_1
    || ','
    || prp.trace_asgn_enty_adtnl_idntfr_2
    || ','
    || prp.prvs_rvw_athrztn_nmbr
    || ','
    || prp.prvs_administrative_rfrnc_nmbr
    || ','
    || prp.x12_code_list_qlfr_lkpcd
    || ','
    || prp.procedure_iid
    || ','
    || prp.mdfr_code
    || ','
    || prp.mdfr2_code
    || ','
    || prp.mdfr3_code
    || ','
    || prp.mdfr4_code
    || ','
    || prp.drug_desc
    || ','
    FROM pa_request_procedure prp,
    pa_request_service prs,
    pa_request pr,
    pa_transaction_request ptr,
    input_acknwldgmnt ia,
    input_batch_file ibf
    WHERE prp.pa_rqst_srvc_sid = prs.pa_rqst_srvc_sid
    AND prs.pa_rqst_sid = pr.pa_rqst_sid
    AND pr.pa_trnsctn_rqst_sid = ptr.pa_trnsctn_rqst_sid
    AND ptr.input_acknwldgmnt_sid = ia.input_acknwldgmnt_sid
    AND ia.input_batch_file_sid = ibf.input_batch_file_sid
    AND ibf.original_file_name =
    'HHIPAA.165760000.20110518I001.278_GC04-3.dat';
    SV2 SV201 Product/Service ID
    SV2 SV202 Composite Medical Procedure Identifier
    SV2 SV202-1 Product/Service ID Qualifier
    SV2 SV202-2 Product/Service ID
    SV2 SV202-3 Procedure Modifier
    SV2 202-4 Procedure Modifier
    SV2 SV202-5 Procedure Modifier
    SV2 SV202-6 Procedure Modifier
    SV2 SV202-7 Description
    SV2 SV202-8 Product/Service ID
    SV2 SV203 Monetary Amount
    SV2 SV204 Unit or Basis for Measurement Code
    SV2 SV205 Quantity
    SV2 SV206 Unit Rate
    SV2 SV209 Nursing Home Residential Status Code
    SELECT 'Product/Service ID,Product/Service ID Qual,Product/Service ID,Product Modifier,Product Modifier,Product Modifier,Product Modifier,Description,Unit Rate,'
    FROM DUAL;
    SELECT prp.revenue_iid ||','||
    prp.x12_code_list_qlfr_lkpcd ||','||
    prp.procedure_iid ||','||
    prp.mdfr_code ||','||
    prp.mdfr2_code ||','||
    prp.mdfr3_code ||','||
    prp.mdfr4_code ||','|| prp.drug_desc ||','||
    prp.srvc_line_rate ||','
    FROM pa_request_procedure prp,
    pa_request_service prs,
    pa_request pr,
    pa_transaction_request ptr,
    input_acknwldgmnt ia,
    input_batch_file ibf
    WHERE prp.pa_rqst_srvc_sid = prs.pa_rqst_srvc_sid
    AND prs.pa_rqst_sid = pr.pa_rqst_sid
    AND pr.pa_trnsctn_rqst_sid = ptr.pa_trnsctn_rqst_sid
    AND ptr.input_acknwldgmnt_sid = ia.input_acknwldgmnt_sid
    AND ia.input_batch_file_sid = ibf.input_batch_file_sid
    AND ibf.original_file_name =
    'HIPAA.165760000.20110518I001.278_GC04-3.dat';
    -- 2000F SV3
    SV301 Composite Medical Procedure Identifier
    SV301-1 Product/Service ID Qualifier
    SV301-2 Product/Service ID
    SV301-3 Procedure Modifier
    SV301-4 Procedure Modifier
    SV301-5 Procedure Modifier
    SV301-6 Procedure Modifier
    SV301-7 Description
    SV301-8 Product/Service ID
    SV302 Monetary Amount
    SV304 Oral Cavity Designation
    SV304-1 Oral Cavity Designation Code
    SV304-2 Oral Cavity Designation Code
    SV304-3 Oral Cavity Designation Code
    SV304-4 Oral Cavity Designation Code
    SV304-5 Oral Cavity Designation Code
    SV305 Prosthesis, Crown or Inlay Code
    SV306 Quantity
    SV307 Description
    select 'Product/Service ID Qual,Product/Service ID,Procedure Modifier,Procedure Modifier,Procedure Modifier,Procedure Modifier,Description,Oral Cavity Designation Code,Oral Cavity Designation Code,Oral Cavity Designation Code,Oral Cavity Designation Code,ProsthesisCrown Inlay Code,Description' from dual;
    SELECT prp.x12_code_list_qlfr_lkpcd
    || ','
    || prp.procedure_iid
    || ','
    || prp.mdfr_code
    || ','
    || prp.mdfr2_code
    || ','
    || prp.mdfr3_code
    || ','
    || prp.mdfr4_code
    || ','
    || prp.drug_desc
    || ','
    || prp.oral_cavity_dsgntn2_cid
    || ','
    || prp.oral_cavity_dsgntn3_cid
    || ','
    || prp.oral_cavity_dsgntn4_cid
    || ','
    || prp.oral_cavity_dsgntn5_cid
    || ','
    || prp.prosthesis_crown_inlay_code
    || ','
    || prp.remark
    || ','
    FROM pa_request_procedure prp,
    pa_request_service prs,
    pa_request pr,
    pa_transaction_request ptr,
    input_acknwldgmnt ia,
    input_batch_file ibf
    WHERE prp.pa_rqst_srvc_sid = prs.pa_rqst_srvc_sid
    AND prs.pa_rqst_sid = pr.pa_rqst_sid
    AND pr.pa_trnsctn_rqst_sid = ptr.pa_trnsctn_rqst_sid
    AND ptr.input_acknwldgmnt_sid = ia.input_acknwldgmnt_sid
    AND ia.input_batch_file_sid = ibf.input_batch_file_sid
    AND ibf.original_file_name =
    'HIPAA.165760000.20110518I001.278_GC04-3.dat';
    -- 2000F TOO pending Prakash to Write
    --Tooth Information
    SELECT 'Industry Code,Tooth Surface,TOO03-1_Tooth Surface Code,TOO03-2_Tooth Surface Code,TOO03-3_Tooth Surface Code,TOO03-4_Tooth Surface Code,'
    FROM DUAL;
    SELECT prp.tooth_number_cid
    || ','
    || prp.tooth_surface_cid
    || ','
    || prp.tooth_surface2_cid
    || ','
    || prp.tooth_surface3_cid
    || ','
    || prp.tooth_surface4_cid
    || ','
    || prp.tooth_surface5_cid
    || ','
    FROM pa_request_procedure prp,
    pa_request_service prs,
    pa_request pr,
    pa_transaction_request ptr,
    input_acknwldgmnt ia,
    input_batch_file ibf
    WHERE prp.pa_rqst_srvc_sid = prs.pa_rqst_srvc_sid
    AND prs.pa_rqst_sid = pr.pa_rqst_sid
    AND pr.pa_trnsctn_rqst_sid = ptr.pa_trnsctn_rqst_sid
    AND ptr.input_acknwldgmnt_sid = ia.input_acknwldgmnt_sid
    AND ia.input_batch_file_sid = ibf.input_batch_file_sid
    AND ibf.original_file_name =
    'HIPAA.165760000.20110518I001.278_GC04-3.dat';
    --tooth SItuational  Information
    select 'Monetary Amount,Quantity' from dual;
    SELECT prpt.rqst_prcdr_amt||','|| prpt.rqst_prcdr_units||','
    FROM pa_rqst_prcdr_transaction prpt,
    pa_request_procedure prp,
    pa_request_service prs,
    pa_request pr,
    pa_transaction_request ptr,
    input_acknwldgmnt ia,
    input_batch_file ibf
    WHERE prpt.pa_rqst_prcdr_sid = prp.pa_rqst_prcdr_sid
    AND prp.pa_rqst_srvc_sid = prs.pa_rqst_srvc_sid
    AND prs.pa_rqst_sid = pr.pa_rqst_sid
    AND pr.pa_trnsctn_rqst_sid = ptr.pa_trnsctn_rqst_sid
    AND ptr.input_acknwldgmnt_sid = ia.input_acknwldgmnt_sid
    AND ia.input_batch_file_sid = ibf.input_batch_file_sid
    AND ibf.original_file_name =
    'HIPAA.165760000.20110518I001.278_GC04-3.dat';
    -- pa_rqst_prcdr_x_prvdr_lctn
    select 'pa_rqst_prcdr_sid,pa_rqst_x_prvdr_lctn_sid' from dual;
    SELECT prppl.pa_rqst_prcdr_sid||','|| prppl.pa_rqst_x_prvdr_lctn_sid||','
    FROM pa_rqst_prcdr_x_prvdr_lctn prppl,
    pa_request_procedure prp,
    pa_request_service prs,
    pa_request pr,
    pa_transaction_request ptr,
    input_acknwldgmnt ia,
    input_batch_file ibf
    WHERE prppl.pa_rqst_prcdr_sid = prp.pa_rqst_prcdr_sid
    AND prp.pa_rqst_srvc_sid = prs.pa_rqst_srvc_sid
    AND prs.pa_rqst_sid = pr.pa_rqst_sid
    AND pr.pa_trnsctn_rqst_sid = ptr.pa_trnsctn_rqst_sid
    AND ptr.input_acknwldgmnt_sid = ia.input_acknwldgmnt_sid
    AND ia.input_batch_file_sid = ibf.input_batch_file_sid
    AND ibf.original_file_name =
    'HIPAA.165760000.20110518I001.278_GC04-3.dat';
    -- error Details
    --Header level error details
    SELECT 'pa_rqst_sid,pa_error_nmbr,pa_error_sid,reject_reason_lkpcd,follow_up_action_lkpcd,aaa_segment_loop_nmbr,run_nmbr,'
    FROM DUAL;
    SELECT prre.pa_rqst_sid
    || ','
    || pe.pa_error_nmbr
    || ','
    || pe.pa_error_sid
    || ','
    || ped.reject_reason_lkpcd
    || ','
    || ped.follow_up_action_lkpcd
    || ','
    || ped.aaa_segment_loop_nmbr
    || ','
    || prre.run_nmbr
    || ','
    FROM pa_request pr,
    pa_transaction_request ptr,
    input_acknwldgmnt ia,
    input_batch_file ibf,
    pa_request_run_error prre,
    pa_error pe,
    pa_error_detail ped
    WHERE pr.pa_trnsctn_rqst_sid = ptr.pa_trnsctn_rqst_sid
    AND ptr.input_acknwldgmnt_sid = ia.input_acknwldgmnt_sid
    AND ia.input_batch_file_sid = ibf.input_batch_file_sid
    AND pr.pa_rqst_sid = prre.pa_rqst_sid
    AND prre.pa_error_sid = pe.pa_error_sid
    AND pe.pa_error_sid = ped.pa_error_sid
    AND ibf.original_file_name =
    'HIPAA.165760000.20110518I001.278_GC04-3.dat';
    ---Line Level Error Details
    SELECT 'pa_rqst_sid,pa_error_nmbr,pa_error_sid,reject_reason_lkpcd,follow_up_action_lkpcd,aaa_segment_loop_nmbr'
    FROM DUAL;
    SELECT pr.pa_rqst_sid
    || ','
    || pe.pa_error_nmbr
    || ','
    || pe.pa_error_sid
    || ','
    || ped.reject_reason_lkpcd
    || ','
    || ped.follow_up_action_lkpcd
    || ','
    || ped.aaa_segment_loop_nmbr
    || ','
    FROM pa_request pr,
    pa_transaction_request ptr,
    input_acknwldgmnt ia,
    input_batch_file ibf,
    pa_request_service prs,
    pa_request_procedure prp,
    pa_request_procedure_run_error prpre,
    pa_error pe,
    pa_error_detail ped
    WHERE pr.pa_trnsctn_rqst_sid = ptr.pa_trnsctn_rqst_sid
    AND ptr.input_acknwldgmnt_sid = ia.input_acknwldgmnt_sid
    AND ia.input_batch_file_sid = ibf.input_batch_file_sid
    AND pr.pa_rqst_sid = prs.pa_rqst_sid
    AND prs.pa_rqst_srvc_sid = prp.pa_rqst_srvc_sid
    AND prp.pa_rqst_prcdr_sid = prpre.pa_rqst_prcdr_sid
    AND prpre.pa_error_sid = pe.pa_error_sid
    AND pe.pa_error_sid = ped.pa_error_sid
    AND ibf.original_file_name =
    'HIPAA.165760000.20110518I001.278_GC04-3.dat';
    SPOOL off
    SET head on
    SET feed on
    SET termout on
    SET pause on

    833560 wrote:
    Hi all,
    I am spooling 30 query results into one CSV file ,I am getting two empty rows for each query.
    Can any one suggest me how to avoid these spaces.
    Thanks & Regards,
    P Prakash
    this is the script i am using to generate csv file .
    SET linesize 12000
    SET pagesize 10000
    SET pause off
    SET termout off
    SET feed off
    SET head off
    SPOOL c:\tes111.csv replace
    SELECT 'ISA01,ISA02,ISA03,ISA04,ISA05,ISA06,ISA07,ISA08,ISA09,ISA11,ISA12,ISA13,ISA14,ISA15,ISA16,GS01,GS02,GS03,GS04,GS05,GS06,GS07,GS08,ST01,ST02,ST03,BHT01,BHT02,BHT03,BHT04,BHT06,trnsctn_segment_count,included_trnsctn_sets_count,included_fnctnl_groups_count,input_acknwldgmnt_sid'
    FROM DUAL;
    SELECT ptr.athrztn_infrmtn_qlfr
    || ','
    || ptr.athrztn_infrmtn
    || ','
    || ptr.scrty_infrmtn_qlfr
    || ','
    || ptr.scrty_infrmtn
    || ','
    || ptr.intrchng_sndr_idntfr_qlfr
    || ','
    || ptr.intrchng_sndr_idntfr
    || ','
    || ptr.intrchng_rcvr_idntfr_qlfr
    || ','
    || ptr.intrchng_rcvr_idntfr
    || ','
    || ptr.intrchng_date
    || ','
    || ptr.intrchng_cntrl_stndrds_idntfr
    || ','
    || ptr.intrchng_cntrl_vrsn_nmbr
    || ','
    || ptr.intrchng_cntrl_nmbr
    || ','
    || ptr.acknwldgmnt_rqstd_indctr
    || ','
    || ptr.usg_indctr
    || ','
    || ptr.cmpnt_elmnt_sprtr
    || ','
    || ptr.fnctnl_idntfr_code
    || ','
    || ptr.aplctn_sndr_code
    || ','
    || ptr.applctn_rcvr_code
    || ','
    || ptr.fnctnl_grp_crtn_date
    || ','
    || ptr.fnctnl_grp_crtn_date
    || ','
    || ptr.grp_cntrl_nmbr
    || ','
    || ptr.rspnsbl_agncy_code
    || ','
    || ptr.vrsn_rls_indstry_idntfr_code
    || ','
    || ptr.trnsctn_set_idntfr_code
    || ','
    || ptr.trnsctn_set_cntrl_nmbr
    || ','
    || ptr.implementation_guide_vrsn_name
    || ','
    || ptr.hierarchical_structure_code
    || ','
    || ptr.trnsctn_set_purpose_lkpcd
    || ','
    || ptr.sbmtr_trnsctn_idntfr
    || ','
    || ptr.trnsctn_set_creation_date
    || ','
    || ptr.trnsctn_type_code
    || ','
    || ptr.trnsctn_segment_count
    || ','
    || ptr.included_trnsctn_sets_count
    || ','
    || ptr.included_fnctnl_groups_count
    || ','
    || ia.input_acknwldgmnt_sid
    || ','
    FROM pa_transaction_request ptr, input_acknwldgmnt ia, input_batch_file ibf
    WHERE ptr.input_acknwldgmnt_sid = ia.input_acknwldgmnt_sid
    AND ia.input_batch_file_sid = ibf.input_batch_file_sid
    AND ibf.original_file_name =
    'HIPAA.165760000.20110518I001.278_GC04-3.dat';
    SELECT 'pa_rqst_sid,NM01,NM02,NM108,NM109'
    FROM DUAL;
    Hi ,
    Save your query in a file and execute that file
    SQL>@a.aqlHope this helps
    Regards,
    Achyut

  • Statistics in BW

    Hi gurus.. i want to know if is possible to know this:
    1) how much users access to a particular query..
    2) how much times a users logon to the system
    Is it possible to do from a transaction code ?¿? (suim , st02, st03.. etc)
    I see inthe business content that we have an infocube for this..but i preffer to do only this 2 statistics in BW and think that is more easy to do from a transaction code.. i hope you help me!
    Ty.
    .- Neo -.

    Thanks Rahul, the problem is that i preffer the way of some transaction, because the acitve the infocubes for Statistics from Business Content is more work for us(process chains.. load more data.. new profiles and roles) and this cubes has a lot of details that i don´t need and never will be used.
    If this is the only way...i think that i will do it.. but i preffer alternative ways for do it.
    Thanks for response it.
    -. Neo .-

  • Unable to  drill down and see the options in  DBACOCKPIT

    Hi All;
    I am unable to drill down any of the options in DBA COCKPIT.i am able to view st03,st04 and database backup is fine even in db13.Let me know what can be done to to do configuration of DBA COCKPIT and if i click configuration am unable to do anything with active and inactive systems
    Below is the error am getting::
    Object CL_DB6_SYS: Method call GET_FIRST_AVAILABLE_SYSTEM failed with return code = System not found.
    Message no. DB6PM001
    Regards
    Ram

    Hi, Make sure you have the latest DBA Cockpit Collection version installed via transaction => snote.
    1456402 DBA Cockpit Correction Collection SAP Basis 7.02 / 7.30
    regards

  • Dumping on refreshing the Infosource tree.

    Hello all,
    After replicating the datasources, when i try to refresh the "Infosource Tree", it is trowing the runtime error(Dump)
    1. This dump is happening only on my machine(client)
    2. All other machines connecting to the server are not having this kind of problem.
    in ST22.. What happend is given in German as follows.
    "Die maximale Größe eines internen Modus ist auf 2GB beschränkt. Eine     detaillierte Beschreibung der Problematik findet man im Hinweis 548845.  Dieser Laufzeitfehler ist plattformunabhängig und kann nicht durch       Tunen der Speicher-Profilparameter vermieden werden."
    and the direct tranlation into english:
    "The maximum size of an internal mode is limited to 2GB.  One finds a detailed description of the problem in the reference 548845.  This run time error is platform independent and cannot be avoided not by Tunen of the memory profile parameters."
    Could you please tell me, why it is happening only on my machine, not on others. I hope this problem is not depending on the GUI.
    Regards,
    Ravi

    Hi Ravi,
    but did you read the OSS Note ?
    "Reason and Prerequisites
    The runtime error "SYSTEM_IMODE_TOO_LARGE" is triggered if a user context or, more specifically, an internal session tries to use more than 2 GB of main memory. The restriction to 2 GB stems from the fact that signed 32-bit variables were frequently used. With unsigned 32-bit variables, memory sizes may be as much as 4 GB.
    Solution
    As of SAP_BASIS 6.20 Support Package 38, internal sessions can be larger than 2 GB and even larger than 4 GB on 64-bit hardware. In addition, the buffers for database tables and some other buffers can also be set larger than 2 GB and 4 GB, respectively. The Support Package has been available since the end of March 2004. The Support Package requires the 6.20 Kernel Patch Level 1269 or higher. Runtime error SYSTEM_IMODE_TOO_LARGE then no longer occurs. As of SAP_BASIS 6.40, the function is included without any additional Support Packages. For Releases 4.6B to 6.10, such a patch cannot be made available so the restriction to 2 GB still applies.
    We therefore recommend that you consider the following if the "SYSTEM_IMODE_TOO_LARGE" runtime error occurs:
    o  Are you using the application as intended? For example, a memory bottleneck may occur if you select too much data.
    o  Does the memory consumption of the application depend on Customizing parameters whose settings may be inadequate?
    o  Is the application program economical in its use of memory? For example, you must explicitly delete the contents of an internal table (FREE statement) before you can reuse the memory. This is significant, particularly if transactions are running for a long time. Furthermore, you can only use the garbage collector to release objects (class instances) and dynamically generated data objects if they can no longer be accessed using references; you must delete the corresponding reference variables. To examine this question, create a problem message under the component responsible for the application program, if you have not already done so.
    The "Memory Inspector" is a tool that may be used to analyze the memory consumption of ABAP programs. This tool is available with SAP_BASIS 6.40 and with SAP_BASIS 6.20 Support Package 29. Among other things, the "Memory Inspector" displays ranked lists of large internal tables, strings and dynamically generated (data) objects. Furthermore, the tool displays dependencies between individual objects; this permits an analysis as to why certain objects cannot be released by the garbage collector. For information about analyzing the memory consumption (also for earlier releases), see Note 649327.
    For Releases 4.6B to 6.10, you can use a profile parameter that is not globally released to increase the maximum size of an internal session from 2 GB to 4 GB. However, most monitoring tools are unable to correctly display values over 2 GB; this applies to Transactions sm04, sm50, st02, st03, se30, the memory consumption display in the debugger, some outputs in trace files and some other locations within the system.
    SAP can therefore only provide limited support for any internal sessions over 2 GB. If customers increase the maximum size of an internal session from 2 GB to 4 GB, they do so at their own risk. SAP shall not be held responsible for errors caused by internal modes over 2 GB. We cannot guarantee that no other errors than those mentioned here will occur. The problem that occurs in both the 32-bit Kernel and the IBM iSeries if an internal session consumes more than 3.4GB is solved as of the Patch delivered in Note 833336. At present, however, we are not aware of any other errors that would seriously impair productive use of the application. We can provide the name of the profile parameter as well as information regarding the use of the profile parameter on request. For this, create a problem message with the BC-ABA-LA component. As of SAP_BASIS 6.20 Support Package 38 and SAP_BASIS 6.40, the profile parameter is no longer required and should be deleted from the profile, otherwise there is an upper limit of 4 GB.
    The "SYSTEM_IMODE_TOO_LARGE" runtime error occurs regardless of the operating system platform and configuration of the memory areas. In particular, you cannot avoid this error by changing memory profile parameters such as ztta/roll_extension and abap/heap_area_nodia.
    In Releases 4.6B to 6.10, 64-bit hardware is utilized in such a way that an application server can have a larger number of user contexts at the same time. In addition, various buffers (for instance program buffers, buffer for database tables) may now be up to 2 GB each.
    The restriction of internal sessions to 2 GB was introduced when the aforementioned problems occurred; the restriction exists since the 4.6D Kernel Patch 1286 and the 6.20 Kernel Patch 368."
    Hope it helps!
    Bye,
    Roberto

Maybe you are looking for