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

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

  • 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

  • Data load error  in PSA

    hellow gurus
    i have run the data load for 2lis_02_scl  at  psa level..
    but when i went to RSMO
    i m seein
    Transfer ( Idoc and TRFC) : error occured
    Reuest IDoc : application documented posted
    Info Idoc1: Sent not arrived ,Data Passed to port Ok
    how to resolve this error
    thanks
    points wil be assigned as my gesture
    Regards
    Rahul

    Hi,
    Check SM58 and BD87 for pending tRFCs/IDOCS and execute them manually.
    Transact RFC error
    tRFC Error - status running Yellow for long time (Transact RFC will be enabled in Status tab in RSMO).
    Step 1:  Goto Details, Status get the IDoc number,and go to BD87 in R/3,place the cursor in the RED IDoc entroes in tRFC
    queue thats under outbound processing and click on display the IDOC which is on the menu bar.
    Step 2: In the next screen click on Display tRFC calls (will take you to SM58 particular TRFC call)
    place the cursor on the particular Transaction ID and go to EDIT in the menu bar --> press 'Execute LUW'
    (Display tRFC calls (will take you to SM58 particular TRFC call) ---> select the TrasnID ---> EDIT ---> Execute LUW)
    Rather than going to SM58 and executing LUW directly it is safer to go through BD87 giving the IDOC name as it will take you
    to the particular TRFC request for that Idoc.
    OR
    Go into the JOB Overview of the Load there you should be able to find the Data Package ID.
    (For this in RSMO Screen> Environment> there is a option for Job overview.)
    This Data Package TID is  Transaction ID in SM58.
    OR
    SM58 > Give * / user name or background  (Aleremote) user name and execute.It will show you all the pending TRFC with
    Transaction ID.
    In the Status Text column you can see two status
    Transation Recorded and Transaction Executing
    Don't disturb, if the status is second one Transaction Executing. If the status is first one (Transation Recorded) manually
    execute the "Execute LUWs"
    OR
    Directly go to SM58 > Give * / user name or background  (Aleremote) user name and execute. It will show TRFCs to be executed
    for that user. Find the particular TRFC (SM37 > Req name > TID from data packet with sysfail).select the TrasnID (SM58) --->
    EDIT ---> Execute LUW
    IDOCS Process Manually 
    http://help.sap.com/saphelp_nw04s/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b815e43d711d1893e0000e8323c4f/content.htm
    &messageID=2311994
    Thanks,
    JituK

  • Removal of error from psa

    hi friends
    can any one tell me how can we remove an error from psa
    thanks in advance
    with regards
    kalyan

    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.
    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.
           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.

  • 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

  • Error in PSA with special characters

    Hello,
    I'm having a problem with sprecial characters in PRD system.
    This happen with standard extractor for Confirmations in SRM module, 0BBP_TD_CONF_1.
    I have 5 records with error in PSA. The field that have the error is 0bbp_delref and it has the text: “GUIA ENTREGA Nº2”.
    The error message says that field OBBP_DELREF has special characters that are not supported by BW.
    The field is char 16 and in spro I have the characters:
    QWERTYUIOPASDFGHJKLǪNºZXCVBM/~^´`* '()"#$%&!?.-0123456789«»<>
    In QUA, I created confirmations with this text and it worked fine and the characters in SPRO are the same.
    Any idea?
    Thanks and best regards,
    Maria

    Hi Maria,
    There will be no issue with update rules as the issue is with Data..
    ALL_CAPITAL should resolve your issue, .otherwise try individually executing those spl characters in RSKC..
    have you tried in SPRO...
    Check in this table RSALLOWEDCHAR in SE11 and find what all characters allowed(permitted)  in PRD system...
    please go through the above mentioned blog once
    Thanks,
    Sudhakar.

  • Error: Current patch level of database is unknown. Use latest dbpatch build

    hi,
    I am applying EP6SP2 CM&COLL patch 5 DBPATCH.
    current portal version: version=6.0.2.29.0
    current C&COLL version: CM_COLL version=60 SP2 Patch 5
    Before applying this patch, i applied CM&COLL patch 4 hotfix 8 and the DBPATCH included in tht. Now, after applying CM&COLL patch 5, i tried to apply DBPATCH which comes with CMOLL patch5 SAR file. My database is oracle database. While applying this patch i encountred following error:
    <i>
    Current database version: SP2.CM.SPs
    ERROR: Error: Current patch level of database is unknown. Use the latest dbpatch build
    java.lang.Exception: Error: Current patch level of database is unknown. Use the latest dbp
    atch build.
            at com.sapportals.wcm.tool.dbpatch.Database.getPatchList(Database.java:48)
            at com.sapportals.wcm.tool.dbpatch.DBPatch.patch(DBPatch.java:66)
            at com.sapportals.wcm.tool.dbpatch.DBPatch.main(DBPatch.java:26)
    </i>
    Now according to SAP Note 761224, they asked us to use updated DBPATCH attached to this note. But currently there are only 3 files attached of MSSQL. I want the updated ORACLE_DBPATCH files.
    rgds,
    Nilz

    Hi,
    i m thru. i raised the question in OSS. They rectified the mistake and attached dbpatch_oracle.zip to SAP note 761224.
    rgds,
    Nilz

  • "****Error from PSA****" error message when loading InfoCube

    Hi all,
    I am getting the following error message when loading transaction data to an InfoCube.
    ***Error from PSA***
    This is not MD or Hierarchies (like previous messages in the forum)
    Please advise.
    Thanks,
    Miki

    Hi Miki,
    Before just loading data into the infocube. Catchup PSA table and see the data into it.
    Then u may find the solution.
    But as ronald said this shouldnot be the complete error statement.
    bye.

  • Gets error "-17502; System Level Exception" while running the custom Step in NI TestStnad 2010

    I have a custom teststand step which works like For loop in TestStand. Previously I was using LV 2009 and NI TestStand 4.2.1 and this step was working fine. Recently I upgraded my system to LV 2010 and TestStand 2010, since that it is not working.
    When I run the step it gives error "-17502; System Level Exception". I have attached error screenshot.
    I am using NIFlowControl.dll in this step.
    Please do the needful.
    Attachments:
    System Levle Exception error.JPG ‏25 KB

    The source code for NIFlowControl.dll ships with TestStand. Did you perhaps
    1) modify the code and rebuild this dll in teststand 4.2.1, but did not move your changes into the 2010 version and recompile the 2010 version?
    Or
    2) Move your 4.2.1 version of this dll to 2010 in which case it might be missing important code that exists only in the 2010 version. It's best to redo your code changes to the 2010 version and recompile that if needed.
    Also ideally your modified version of NIFlowControl.dll should be located in the teststand public directory rather than the program files directory.
    -Doug

  • Account determination error at billing level

    Hi,
    for Account determination error at billing level
    i checked the line item level for the material by highlighting the item, then GO TO > ITEM > ITEM DETAILS. here 5 line items are there , 4 line items have same "Acct asgnmt grp" and 1 line item is different at order level. i gess this is the problem if am wrong please correct me.
    thanks
    Edited by: pandu123 on May 26, 2011 2:24 AM
    Edited by: pandu123 on May 26, 2011 2:32 AM

    Hi Pandu
    A/c deterimation error. 1st you check in customer master sales area data billing tab page with account assingment and go to material master u select particular material see in sales organization 2 tab with account assignment. and go to T.Code VKOA check the combination which is assiged A/c assingmnet group of customer and matrial account assingment group. If it is not come goto VFX3 and specify the customer execute and click on RELEASE FLAG. If it is error go to log see the digonsis.
    Kind Regards
    Chandra Mouli A

  • Error in MB31 level

    hi everybody
    i have an error at MB31 level
    This particular error occured while doing MTO scenario, system says "GR quantity is greater than Confirmed quantity for the last transaction" though i gave the lesser quantiy also system shows the same error, can anyone help in this regard
    thanks for all

    Check your production order (CO02, CO03), click on the blue status icon "i" to see the status and if it's TECOed. Only if the necessay confirmations have been done, can receipt be carried out.

  • Error in Trace Level: could not create BPE proxy for message, no XML objec

    Hi
        We are doing a scenario of File to RFC using BPM and I am getting this errror in Tcode SXMB_MONI.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    <!--  Call Adapter
      -->
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="<b>BPE_ADAPTER</b>">UNKNOWN_MESSAGE</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack><b>No object type found for this message; check the activation of the corresponding process</b></SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    And getting this error in Trace level
    <b>could not create <b>BPE</b> proxy for message, no XML object definition found for message EB32BB50610A11DC9648001321CB837D</b>
    Why this error occurs?
    What could be in error?
    Thanks in advance
    Regards
    Sami Qureshi

    Hi Sami,
    Check if thse threads can help u,
    Error in BPE Adapter
    BPM - BPE_ADAPTER errors
    BPE Adapter Error
    Exeception during execution error
    ***********Reward points if helpfull************

  • 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

  • Error:ID=2011;LEVEL=1] InhouseDocReader doSyntaxCheck() offset[239]

    Dear SAP experts,
    I am getting this error in my File Sender Communication Channel,
    Error: javax.resource.ResourceException: --- Conversion of synchronous request from module chain ended with errors ---[Error:ID=2011;LEVEL=1] InhouseDocReader doSyntaxCheck() offset[239]: message structure error : segment CTA is not on the right position. DESCRIPTION: InhouseDocReader Warning: A Segment whitch does not match with the inputstructure was found during the syntax check and no other segment with a small error was found.
    The message is a D96A_SLSRPT edifact message.
    Are there any error in the message structure?
    Kindly advise.
    Fred

    Hi Fred,
    I refered your problem in the sites,as i got this answer:
    Read it,may it helps you to solve the problem
    although the SAP note tells that you only need to install the plugin till R3 4.6 you must install it for a 4.7 R3 as well.
    It is only automatically available with WebAs 6.40 R/3 systems.
    We had the same problem with our 4.7 R3 but after installing the WP-PI 6.00 everything worked fine.
    Be sure that users which should have access later to the UWL have sufficient backend rights. There are several RFC rights they need to have. (e.g. RFC rights for function groups SYST and SWK1)
    Reward points if this helps
    Regards
    Vani.

Maybe you are looking for

  • Application frame not working plus other issues Illustrator CC Mac

    Running Illustrator CC on a Mac. I'm missing the maximize, minimize, and close buttons in the top left corner. I have an "Ai" symbol in the top left, which I thought was only on the PC version? All my tools disappear when I turn on application frame.

  • Help needed - MBP keeps restarting.

    So today I turned my Macbook on and I was browsing the Internet and suddenly the screen turned grey and it began to load for a few seconds and then showed my home screen as if Id just opened my computer - all windows that I had opened a second ago we

  • Prerequisites  for satellite sysetm to be added in Solotion manager

    Hi Everyone, i want to add a system in solution manger  I just want to know the prerequisites  for satellite system.   The backend system to be connected is R/3 4.7 on Informix. (620 - SP60) Root Cause Analysis/ SMD ,Work Center, E-2-E has to be conf

  • TM poor performance especially in mail

    I have used TM a couple of times when in mail and the performance is dreadfully slow. When in mail with a mailbox highlighted, I enter TM. It goes to the TM interface fine, but when I select a date, it takes about 2 min to get there. I can then resto

  • Feature Request: Lights Out Mode / tagging display.

    Problem: "Lights out" mode hides tags - need to enable option to allow tags to be seen during lights out mode. I love editing down photos to selects in lightroom, I love using the (L) LightsOut Mode to set the screen(s) to black. however, when I do s