Debugging at PSA level

Hi All,
I need to delete a few records in field "ERDAT" in PSA. I've followed the steps to get to Debugging at PSA (using SE11). Now, I've no clue how and what to do to delete the records in the debugging mode for this field. Can you guyz please help me out.
Thanks,
Regards,
G.

Hi,
1)       Go to table --> Contents --> Select the records which you want to delete
2)       Now enter /h in the transaction bar
3)       Now select the records which you want to delete and double click on it
4)       Itu2019ll take you to ABAP debugger screen, Hit F7
5)       You will see this code u201C if code = 'SHOW'   u201C
6)       Double click on the CODE , now you can see this in Field names and also Show in field contents
7)       Now Remove show and replace it with DEL (only in caps) and then click on Pencil Symbol (Change) and hit F8
8)       Now you can delete  the records by clicking in Delete Entry
Edited by: YJV on May 10, 2011 8:12 AM

Similar Messages

  • Error in psa level - Request not updated to any data target using delta

    Hi,
    This is pavan and am facing this issue any one know for below issue to solve.
    Data Flow is BW Version and Implemented in BI  7.20 version.The issue was data has come
    to psa level but from here it is not updated to infocube so for that i have tried update manually
    it is showing information that 1334 SID IS SMALLER THAN / EQUAL TO 47287 CANCELLED.
    In Process Chain DTP is not included so how can i update data to infocube with out disturbing process chain
    Regards,
    Pavan Kumar

    Hi Pavan Kumar ,
    Please log on Tcode RSRQ -then give old request number (I think in your case 1334 is old request number),
    and you will get monitor for that request then change the QM status to red after that load new request .
    Thanks
    Hanumanthu

  • ERROR IN PSA LEVEL

    *Hi Experts,*
    *This is kalyan and i am facing a issue in BI 7.20 VER from past 1 week am not able to solve.*
    *this issue is process chain scheduled daily basis and process chain getting failed failed from 01-01-2011 to till date*
    *but records available in psa level but not reached target then when i try to do schedule manullay but*
    *in data target tab it is not showing target.i have tried with process manually this option available ipsa under header tab*
    *when i choose that option it is showing this error SID 1334 is smaller than /equal to update SID of DTA ZSD_BLCO3/47287;Canceled please help me in this issue if one knows and what will be solution.*
    *Thanks In Advance,*
    *Kalyan*

    Hi
    As you told this is running in Process chain. Do you have "Update from PSA" step after this IP is completed.
    check the job log of IP load in SM37, check the error log in Job.
    If you don't have Update from PSA step in PC, include it in your PC or make the changes to IP ( change the option to  PSA and then data target in series in update tab)
    Regards,
    Venkatesh

  • Issue at PSA Level data

    Hi,
    I am trying to extract data from the 0CRM_COMPLAINTS_I into BI. I have to enhance this DS with two Z fields. I can clearly see data populated for these Z fields in RSA3 with the enhancement code.
    When I tried to get the same into BI, the data is not  being populated even at the PSA level. I tried deleting the old requests at PSA level and target level and then extracting but of no use. Instead it is showing some junk values for the Z fields at PSA.
    I am  working on BI 7.0 and CRM 5.0.
    Please let me know ASAP.
    Thanks in advance,
    Rama Murthy.

    Hi,
    you need to replicate the datasource as well as to maintain the transfer structure. In there you need to put the new fields from the right hand tab (datasource) to the left hand tab (transfer structure). Activate the transfer rules. Reload the data and you will see the new fields.
    regards
    Siggi

  • Create authentication at psa level

    Hi,
    I need to create authorisation at PSA level as the same needs to be restricted but the prob which I m facing is tat PSA is not a level of authorisation ORGIN. Hence authorisation at PSA level needs to be created, pls guie me.
    Tx

    Hi,
    First of all try to investigate if you can manage your authorization requirements using standard SAP objects. As it was suggested please consider use of Organization key (where you can store almost any field from IT 0001).
    If you think there is no other option rather than creation of custom objects, then study this guide: http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a92195a9-0b01-0010-909c-f330ea4a585c?quicklink=index&overridelayout=true
    Cheers!

  • PSA  level Errors are not displayed

    Hi friends,
        I'm using BI 7.0....up to PSA  i'm getting data  perfectly.. Even though some errors are there  i mean.. data mis match in my flatfile(for NUMC fields  I was enterd Charecter data... ... that time also.. psa level data was  showing green only.... if i upload into ODS  then only i'm getting  problem..
          but   in previous versions  it was showing  Red  (for error reacords..) in PSA level itself...
         for what reason  I'm not getting  like this.... is there  any  problem  with my procedure.. or   is this BI 7.0 feature..
    plz clarrify..
    Thanks
    babu

    Hi,
        Using the Error Handling function on the Update Parameters tab page in the scheduler, you can control the behavior of the BI system if data records with errors occur in the data flow with 3.x objects (use of transfer and update rules) when you are loading data using the PSA.
    The system checks for data records with errors:
          in the transfer rules
          in the update rules
          when data is updated to the master data tables, text tables, or hierarchy tables
          when data is updated to the InfoCube
          when checking for referential integrity within an InfoObject against the master data tables or DataStore objects on the communication structure level.
    Features
    Incorrect records arising in transfer rules, update rules, when updating to a data target, or when checking for referential integrity, are highlighted and returned to the error handler. The error handler locates the original PSA records and writes the corresponding log. This function is not yet available for updating to DataStore objects.
    Using the Error Handling function on the Update Parameters tab page in the scheduler, you can control how the system responds to incorrect data records.
    Activities
           1.      Define how the system should react to incorrect data records
    a.       No update, no reporting (default)
    If errors occur, the system terminates the update of the entire data package. The request is not released for reporting. However, the system continues to check the records.
    b.       Update valid records, no reporting (request red)
    This option allows you to update valid data. This data is only released for reporting after the administrator checks the incorrect records that have not been updated and manually releases the request (using a QM action, that is, by setting the Overall status on the Status tab page in the monitor).
    c.       Update valid records, reporting possible
    Valid records can be reported immediately. Automatic follow-up actions, such as adjusting the aggregates, are also carried out.
    With option a), the incorrect records are marked in red in the PSA maintenance. You can display the relevant error messages amodally, edit the records, and update the request manually. If it was not possible to write to the PSA (hierarchy or transfer method IDoc), an application log is written instead.
    With options b) and c), a new request that is only updated to the PSA is formed from the incorrect records. Here you can edit the records of the new request in the PSA and start the update manually.
    If errors arise when an InfoCube is updated, new requests are generated for incorrect records for each InfoCube combination. Among these requests, the incorrect records are updated to the PSA. These new requests have entered as data targets the InfoCubes for which there were incorrect records. If, for example, a record was updated to two InfoCubes by mistake, a request is generated for this record that contains both InfoCubes as data targets. In the PSA tree, the requests appear as successfully updated in the PSA. These new requests can then be triggered again for updating to the InfoCubes.
           2.      Specify the maximum number of incorrect data records that are allowed before the system terminates the load process. In the PSA, you can display the errors that have arisen up to that point. If you do not specify the maximum number of incorrect records after which termination should occur, the handling of incorrect data records is inactive and the update terminates after the first error.
           3.      Define how the BI system should react if the number of data records received by the BI system is not the same as the number of data records updated in BI.
    A difference between the number of received and updated records can occur:
             in the transfer rules
             in the update rules
             when updating
    Records are sorted, aggregated, or added.
    If you set the No Aggregation Permitted indicator, the request is deemed incorrect if the number of received records is not the same as the number of updated records.
    Regardless of this indicator, an error occurs if the number of selected records is not the same as the number of records received in the BI system.
    Result
    The monitor directs the user to the relevant error case and enables a direct navigation into the PSA or the respective error request.
    If you want to continue processing the incorrect data records in a program that you have written yourself, you can use the method GET_ERRORS of class CL_RSSM_ERROR_HANDLER. The use of this method is documented in the RS_ERRORLOG_EXAMPLE.
    More Information:
    Checking and Changing Data Using the PSA APIs
    To perform complex checks on data records, or to carry out specific changes to data records regularly, you can use delivered function modules (PSA-APIs) to program against a PSA table.
    If you want to execute data validation with program support, select Tools ® ABAP Workbench ® Development ® ABAP Editor and create a program.
    If you use transfer routines or update routines it may be necessary to read data in the PSA table afterwards.
    Employee bonuses are loaded into an InfoCube and sales figures for employees are loaded into a PSA table. If an employee’s bonus is to be calculated in a routine in the transformation, in accordance with his/her sales, the sales must be read from the PSA table.
    Procedure
           1.      Call up the function module RSSM_API_REQUEST_GET to get a list of requests with request ID for a particular InfoSource of a particular type. You have the option of restricting request output using a time restriction and/or the transfer method.
    You must know the request ID, as the request ID is the key that makes managing data records in the PSA possible.
           2.      With the request information received so far, and with the help of the function module, you can
             read RSAR_ODS_API_GET data records from the PSA table
             write RSAR_ODS_API_PUT changed data records in the PSA table.
    RSAR_ODS_API_GET
    You can call up the function module RSAR_ODS_API_GET with the list of request IDs given by the function module RSSM_API_REQUEST_GET. The function module RSAR_ODS_API_GET no longer recognizes InfoSources on the interface, rather it recognizes the request IDs instead. With the parameter I_T_SELECTIONS, you can restrict reading data records in the PSA table with reference to the fields of the transfer structure. In your program, the selections are filled and transferred to the parameter I_T_SELECTIONS.
    The import parameter causes the function module to output the data records in the parameter E_T_DATA. Data output is unstructured, since the function module RSAR_ODS_API_GET works generically, and therefore does not recognize the specific structure of the PSA. You can find information on the field in the PSA table using the parameter E_T_RSFIELDTXT.
    RSAR_ODS_API_PUT
    After merging or checking and subsequently changing the data, you can write the altered data records into the PSA table with the function module RSAR_ODS_API_PUT. To be able to write request data into the table with the help of this function module, you have to enter the corresponding request ID. The parameter E_T_DATA contains the changed data records. 
    Result
    The corrected data is now available for continued updates.
    if it helps plz assign points

  • Debugging at DTP level

    Hi,
    Friends how to do Debugging at DTP level.
    Regards.
    Asim

    Hi,
    Following are some of the techniques.
    Write Break-point in the code Start routine or in field routine you want to debug
    And execute in simulate mode which will help you in stopping at the point you need.
    Else
    Go to expert mode and select the record to be debugged ie enter the selection condition filter for debugging
    and enable check after extraction after start routine like that and search for the code written to debug
    and keep the break point over there
    Thanks,
    Arun
    Edited by: Arunkumar Ramasamy on Sep 14, 2009 9:32 PM

  • Psa level 91 records ,dtp level 0 records

    Hi friends,
    i have run the process chains daily still in yellow color infopackage run , dtp not run in psa level records are ther 91 dtp level it shows 0 records.
    errors are
    1)Process Execute InfoPackage, variant Delta Upload - 2LIS_02_SCL has status Undefined (instance )     
    2)Process Execute InfoPackage, variant Delta Upload - 2LIS_02_ITM has status Undefined (instance )     
    3)Process Generate Index, variant Generate Index for Purchasing has status Undefined (instance )     
         Process OR (Each), variant Every has status Undefined (instance )          Process Data Transfer Process, variant 2LIS_02_SCL / CPPCLNT400 ->
    4)0PUR_C01 has status Undefined (instance )Process Data Transfer Process, variant 2LIS_02_SCL / CPPCLNT400
    5)0PUR_C04 has status Undefined (instance )

    i got the same error, do u know how you fixed yours

  • PSA level issue USD is coming as USD,  for some records .

    Hello Experts ,
                           Very Good evening , I am facing one issue regarding the data load in the cube , actually I am loading data from a flat file having some 51 records ,till my PSA data is coming correct but with one modification i.e. in some records near about 16 records out of 51 one field data USD is coming like USD, means one comma (,) is automatically coming in the PSA level ,thats Y my rest of the records are not getting loded , can u please help me in this case to resolve it , waiting for the reply , and Thanks in advance .

    Open the CSV flat file in Notepad (right click on file and open with notepad) and see if there is any comma after USD.You can make correctionsin notepad version and save it.Do not open in CSV and make corrections.
    Regards,
    JB

  • How to Debug PSA level

    Hello,
    I am loading data from Application Server folder to PSA. I am getting few errors such has "Cannot convert one of the char"
    my csv file having 40,000 records its hard to find which record having invalid char so i would like to debug
    if anybody know how to debug please let me know i will assign points.
    Thanks,

    hi,
    you cannot debug inPSA, from PSA to target you simulate using the simulate update option.
    in the rsmo of the load, choose details tab, select the datapackage and right click u will find simulate update option.
    select the records, selct whether need to debug the transfer rule or update rule.
    it will directly takes you to debug screen.
    use f5,f6,f7 to execute the program.
    Remya

  • Debugging the isolation level

              Does anyone know of a way to capture the current isolation level for a given transaction,
              in particular w/ a CMP entity bean?
              I'm using the P6SPY driver to capture debug information, but I never see a call
              to Connection.setTransactionIsolation(). Therefore, I have no way to know if
              my transaction is running with Serializable level, the level I've set in my weblogic-ejb-jar.xml
              file.
              Running WLS 6.1 and JConnect 5.5.
              Thanks,
              Jim
              

              Just tried the code below. Compiles -- that id good ;)
              When I'm outside transaction I get weblogic.transaction.TxHelper.getTransaction()
              == null.
              That is to be expected.
              When I'm inside transaction the property value is null. Properties that I can
              get:
              [0] key
              weblogic.transaction.name val [EJB om.moveitonline.framewo
              [1] key weblogic.jdbc val t3://10.1.26.51:7001.
              Questions:
              a) How to get the isolation level anyway?
              b) What are the integer values for isolation levels (i.e. constants)?
              Rob Woollen <[email protected]> wrote:
              >Try this:
              >
              >Integer iso =
              >weblogic.transaction.TxHelper.getTransaction().getProperty(weblogic.transaction.TxConstants.ISOLATION_LEVEL);
              >
              >-- Rob
              >
              >
              >Jim clark wrote:
              >> Does anyone know of a way to capture the current isolation level for
              >a given transaction,
              >> in particular w/ a CMP entity bean?
              >>
              >> I'm using the P6SPY driver to capture debug information, but I never
              >see a call
              >> to Connection.setTransactionIsolation(). Therefore, I have no way
              >to know if
              >> my transaction is running with Serializable level, the level I've set
              >in my weblogic-ejb-jar.xml
              >> file.
              >>
              >> Running WLS 6.1 and JConnect 5.5.
              >>
              >> Thanks,
              >> Jim
              >
              

  • Reg: Not getting the data in PSA level

    Dear all,
    We are having 2 clients in one development server. One is for R/3 and another one is for bw.  When  i am doing the extraction for
    SD billing documents ( Setup table -13) i done the same for LBWG,LBWE. And finally i got the data into the RSA3 tc. Wheni am
    replicating the datasource in BW  side. I got the datasoruce in BW client. But when i am scheduling that datasource for infopackage i can able to find out the data.
    Errr or message:
    No data available
    Diagnosis
    The data request was a full update.
    In this case, the corresponding table in the source system does not
    contain any data.
    System Response
    Info IDoc received with status 8.
    Procedure
    Check the data basis in the source system.
    Please do the needful at the earliest.
    Thanks,
    Sankar M

    Hi Sankar,
    When you trigger the infopackage and if it shows the data available then there is no wrong in designing so First check the data at data sourcelevel in RSA3 and also at the source table
    Regards,
    Marasa.

  • RSA3 data and PSA data not matching

    Hello All,
    I am in BI7.0 and trying to Load FI_GL data usng 0FI_GL_4 DS from ECC6. I was able to install, activate all necessary standard objects that are involved. I have executed data Load from Infopackage by doing Init. with data Transfer..which went okay and now i am data upto PSA Level with everything green status. But when I noticed that in PSA Maintenance screen its showing whole lot more data..it shows 103 Datapackages transferred and lot of data records in each packages.
    In R3 side (RSA3) shows only 831 records.  IN BI7 , monitor screen shows more then 9 million records recieved.
    Could anyone tell me why this happened? Is it possible that this particular PSA already had data on it? if so How can i find and delete previous records from this PSA? please suggest...
    thanks
    dk

    Hello,
    1)The error comes if the data is wrong in the DSO.
    Something like before and after image are missing for a record and thats why change log is having some issues.
    you can check the data between new tables and PSA and see if its matching or not.
    Try to delete all the data from the PSA and the DSO.do proper mappings again especially in the keys of the DSO and then reload it.
    try to load it for a small a amount like one company code and one fiscal period.check in PSA if its matching or not from RSA3.
    2)If the data is getting loaded then there should not be a any problem with the data source.DTP could be an issue.the program is to activate the data source in BI 7 system and if the data source is already activated then you dont need this again.
    3)Rule proposal can be generated if the fields are same and have same technical name.in your case the field name are different since its datasource and DSO mappings and therefore you will have to do mappings manually.
    4)you mean RSA3??
    RSA3 displays the data from tables only in case of full mode.Also,try to do full loads till the PSA and then check for the same in RSA3 in full mode.keep the package size and number of calls maximum so that it will show you correct number of records extracted.
    RSA3 is an extractor checker and can be used for verify small amount of data,dont use it for verifying the datasource for all the drecords.
    use underlying tables if you want.
    if init is done properly then the data will be correct and you should verify it with the tables and not RSA3.
    Regards
    Ajeet

  • Unable to see the field in PSA

    HI Experts,
    Good day to ALL!
    I developed the reports every thing fine but one of the field FISTL_WP in datasource 0HR_PY_1 able to see the data in rsa3 and same field data unable to see in PSA level and  as well as RSA6 data source level  in ECC system so any one face the issue before please pass your inputs.
    Regards
    RK

    Hi,
    You can write custom program on ecc dev system T code - SE38.
    Check below code.
    Report ZROOSFIELD
    tables: ROOSFEILD.
    SELCT SINGLE * FROM ROOSFIELD WHERE OLTPSOURCE = '0HR_PY_1' AND
    OBJVERS = 'A' AND FIELD ='FISTL_WP'.
    IF SY-SUBRC = 0.
    ROOSFIELD-SELECTION ='P'.
    MODIFY ROOSFEILD.
    ENDIF.
    do the syntax check and execute it. Later check above table. you filed SELECTION will be as P.
    After that you can see at RSA6 and replicate data source to bw side. Do the rest of the things at bw side.
    Thanks

  • Master Data is NOT Loaded correctly, but  PSA has correct data

    Hi all,
        We have transported  the Master Data Attribute 0CPR_PROJEC (cProjects: Project) from DEV to QA system. There is no problem with data in DEV, but we are having the problems in QA.
        In QA, the data is BLANK for couple of Attributes (RSA1 --> Right Click  --> Maintain Master Data), but these Attributes are having the data in PSA level.
        We have verified the Transfer Rules & Update Rules and these are same in DEV and QA.
       What could be the problem, PLEASE?
    Thanks in advance.
    Regards.

    Hi Venkat,
          Could u pls tell me where u ran tha RS_TRANSTRU_ACTIVATE_ALL .so that if i get the same probs i will follow same steps
    Regards
    sneha

Maybe you are looking for