HANA XS Administration

Hallo together,
i started a project in my company with SAP HANA two weeks ago.
There's one point i'm not able to handle and the documentation and/or google could not help me.
So i hope that somebody here can give me a solution.
Currently i'm trying to establish a connection to an external webservice also running in my intranet.
To check my settings i wanted to look into XS Administration Page that can be accessed by /sap/hana/xs/admin/
but got the error: Request execution failed due to missing privileges.
So i asked our administrator to grant me access and i got all sap.hana.xs.admin.roles:xxx that are available.
But i still get the same error with the missing privileges.
Now my question: What i need to do to get access to the XS Administration Page?
I tried to disconnect / connect to the HANA instance, restarted HANA studio, refreshed the whole repository...but nothing helps.
Thanks a lot for you help.
Kind regards
Adam Glodek

Problem solved.
Digging into Google, SAP support pages and developer guides for several days does not give any useful result.
I've started to try updating _SYS_XS schema manually by using my "sensations" and solved the problem.
Execute the following SQL script from SQL console:
UPDATE "_SYS_XS"."RUNTIME_CONFIGURATION" SET Configuration= '{"authentication": {"method": "Form"}}' where PACKAGE_ID=''
Then restart xsEngine by rightclick on hana system->Administration->Configuration->daemon.ini->xsengine ->set instance number of host to 0 (if it is 1)-> set instance number to 1 again
This worked for me. I finally got the authentication form back again.
I suppose the problem is about choosing "Public" (No authentication required) from xs/admin page either intentionally or accidentally. After you choose this option and restart xsengine then it is not possible to see your xs admin page again. Because you select public, it is not asking authentication. But that does not mean you will be allowed to access publicly to web admin interface because of privilages. When you select public, web admin interface is not asking authentication and gives "Request execution failed due to missing privileges" error forever. You have to fix it manually by updating the _SYS_XS schema. That means you can change No public->public from xs admin page but cannot do the reverse public->No public from xs admin page because it will not be working anymore.
Hope it helps someone out there.

Similar Messages

  • SAP HANA XS Administration Tool Missing

    The SAP HANA XS Administration Tool seems to be missing from our HANA AWS instance. The various roles associated with XS Administration are also missing.
    The best theory I can come up with is that it has something to do with our upgrade path. Version 52 was originally installed in August.  We upgraded to Version 69 in February.
    I've scanned the release notes and it looks like the tool may have been introduced in SPS06.
    Did we miss something during the Version 69 upgrade?  If so, does anyone know how to fix this?

    Hi Michael,
    Maybe you can try to import the DU manually. Open your SAP HANA Studio, File -> Import -> SAP HANA Content -> Delivery Unit -> Choose your SAP HANA system, then select the file like the following. Hope it will help.
    Best regards,
    Wenjun

  • SAP HANA Database Administration Issues

    Hello Gurus,
    I would like to know and understand the most common or frequently faced major issues by SAP HANA Administrators.
    Shirish.

    Hi Shirish,
    You should start by reading below blog from Andy:
    http://scn.sap.com/community/hana-in-memory/blog/2013/05/27/andy-silvey--sap-hana-command-line-tools-and-sql-reference-examples-for-netweaver-basis-administrators
    Regards,
    Vivek

  • Problems in creating RLANG stored procedure in HANA studio

    Hi,
    While I am creating a stored procedure (using .hdbprocedure file) in HANA studio with language as RLANG, I am getting an error message like this: "It is not supported to use another language than sqlscript".
    I have the following setting configured.
    HANA System -> Administration -> Configuration ->indexserver.ini -> repository -> sqlscript_mode = UNSECURE
    Any clues will be appreciated.
    Best Regards
    Surya

    HI Raj,
    This happens even for the empty procedure as following
    PROCEDURE "IDMANALYTICS_OPER"."idmanalytics.hana.db.hdbprocedures::MC_ROLEMINING_CLUSTERING_R" ( )
      LANGUAGE RLANG
      SQL SECURITY INVOKER
      READS SQL DATA AS
    BEGIN
      Write your procedure logic
    END;
    The procedure that I wanted to write is following.
    PROCEDURE MC_ROLEMINING_CLUSTERING_R(IN rolemining_input "_SYS_BIC"."idmanalytics.hana.db.views/MC_ROLEMINING_VINPUT",
      IN params "IDMANALYTICS_DB"."idmanalytics.hana.db.hdbtables::MC_ROLEMINING_PARAMETER",
      OUT result MC_ROLEMINING_CLUSTERS_TYPE,
      OUT result_hierarchy MC_ROLEMINING_HIERARCHY_TYPE,
      OUT result_userorder MC_ROLEMINING_USERORDER_TYPE
    LANGUAGE RLANG AS
    BEGIN
      noofclusters <- params$INT_VALUE[1];
      simindex <- params$DOUBLE_VALUE[2];
      distancemethod="jaccard"
      clusteringmethod="complete"
      usercol <- rolemining_input$USER_ID
      privcol <- rolemining_input$PRIV_ID
      #--generate user-permission matrix from user-permission table
      uptable <- data.frame(users = usercol, privileges = privcol)
      uniqueusers <- sort(unique(uptable$users))
      uniqueprivileges <- sort(unique(uptable$privileges))
      upmatrixdata <- vector()
      index <- 0
      for(i in uniqueusers )
      for(j in uniqueprivileges) {
      row_to_find <- data.frame(users=i, privileges = j)
      if(duplicated(rbind(uptable, row_to_find))[nrow(uptable)+1]){
      upmatrixdata <- append(upmatrixdata, 1, after = index)
      else {
      upmatrixdata <- append(upmatrixdata, 0, after = index)
      index <- index +1
      upmatrix <- matrix(
      upmatrixdata ,
      nrow = length(uniqueusers),
      ncol = length(uniqueprivileges),
      byrow = TRUE,
              dimnames = list(
              uniqueusers,
                  uniqueprivileges
      #--apply hierarchical clustersing
      require(vegan)
      distance<-vegdist(upmatrix,method=distancemethod)
      clusters<-hclust(distance,method=clusteringmethod)
      #--fill clusters for given h and k
      if(noofclusters > 0){
      userclusters<-cutree(clusters,k=noofclusters)
      tempresult <- as.data.frame(userclusters)
      result <- data.frame(USER_ID=row.names(tempresult), CLUSTER_ID=tempresult$userclusters)
      if(noofclusters <= 0 & simindex >= 0){
      userclusters<-cutree(clusters,h=simindex)
      tempresult <- as.data.frame(userclusters)
      result <- data.frame(USER_ID=row.names(tempresult), CLUSTER_ID=tempresult$userclusters)
      #--fill role hierarchy
      clusters_merge <- as.data.frame(clusters$merge)
      clusters_height <- clusters$height
      clusters_order <- clusters$order
      result_hierarchy <- data.frame(HEIGHT=clusters_height, V1=clusters_merge$V1, V2=clusters_merge$V2)
      #--fill user order
      clusters_order <- clusters$order
      result_userorder <- data.frame(USERORDER=clusters_order)
    END;

  • SAP HANA Web-based Development Workbench Privileges

    I can get into and use the SAP HANA web-based development workbench as the SYSTEM user, but I cannot as other users.
    http://localhost:8005/sap/hana/xs/ide/editor/
    Currently as any other user, I get the following error: "Request execution failed due to missing privileges"
    What are the appropriate privileges that need to be set in SAP HANA Studio to access the web based IDE?
    Currently, just messing around with the privileges in SAP HANA Studio, if I set the following application privileges, I can at least log in as another user besides SYSTEM.
    However, I cannot get any of the files to display in the editor portion of the SAP HANA web-based development workbench. A possibly related error in the log console: "13:10:12 >> Error in WebSocket Connection to backend."
    I found this thread discussing the same issue I believe, but the solution I would imagine is not correct: HANA XS Administration | SAP HANA
    Thanks,
    Kevin

    Hi Fernando,
    Thanks for the suggestion. That seemed to work, though it is strange that it is not one of the *.xs.* application privileges. So, just to be clear, here are the application privileges I have now in order to use the web based IDE:
    Thanks,
    Kevin

  • Lumira Server Error

    We have successfully installed Lumira Server in a DEV environment.  I am able to see Analytical views which I created from my browser but when I attempt to publish from the client I receive the following error:
    Error - The dataset could not be published to SAP Lumira Server because publishing to the SAP HANA layer failed.  Reason is ''. (HDB 11009)
    We followed all the steps in the guide
    http://help.sap.com/businessobject/product_guides/vi01/en/lumS115_user_en.pdf
    We're raise a ticket but I'm just curious if anyone has seen this issue before.

    I still thinking about a security issue:
    Before users can publish content to SAP HANA, they must be assigned specific
    privileges and roles. These roles and privileges are also required for
    retrieving data from SAP HANA. Use the SAP HANA Studio application to assign
    user roles and privileges. For information on administrating the SAP HANA
    database and using SAP HANA Studio see SAP HANA Database – Administration Guide.
    For information on user security, see the SAP HANA Security Guide (Including SAP
    HANA Database Security).
    The user account used to log into the HANA system
    from Lumira must be assigned to the "MODELING" role (in HANA).
    Note:
    This action can only be performed by a user with ROLE_ADMIN
    privileges on the SAP HANA database. When an SAP Visual Intelligence user
    logs into the SAP HANA system, the internal _SYS_REPO account must:
    • Be granted the SELECT SQL Privileges.
    • Have the Grantable to others option selected on the (SAP Visual Intelligence) user's schema.
    To configure _SYS_REPO for the SAP Visual Intelligence user
    If an account for the Lumira user is already defined in the SAP HANA system:
    1. From the system connection in the SAP HANA Studio Navigator window, go to Catalog > Authorization > Users.
    2. Double-click the _SYS_REPO account.
    3. Under the SQL Privileges tab, click the + icon, enter the name of the user's schema, and click OK.
    4. Choose SELECT and the corresponding Yes under Grantable to others.
    5. Click Deploy or Save.
    Tip:
    You can also open an SQL editor in SAP HANA Studio and run
    the following SQL statement:
    GRANT SELECT ON SCHEMA <user_account_name> TO _SYS_REPO WITH GRANT OPTION
    If your user has this rights, I dont have an additional idea up to now

  • Xs engine throws "No successful authentication possible"

    Hi,
    I'm a new to HANA & SAP platform, I've launched my HANA instance in AWS and i'm trying to create xsjs application, I've built the application and it's deployed in HANA box. i've followed the procedure specified in below URL.
    https://help.hana.ondemand.com/help/frameset.htm?3762b229a4074fc59ac6a9ee7404f8c9.html
    everything is fine till step 9, now i need to deploy the application and check the response. As stated in this step, i launched the URL(https://<database instance><account>.<host>/sap/hana/xs/admin/) and modified the configuration as specified below.
    9. Enable SAML
    Enable SAML if you are using a productive SAP HANA instance. Otherwise, you can omit this step.
    Procedure
    Start the SAP HANA XS Administration Tool: http://<database instance><account>.<host>/sap/hana/xs/admin/
    On the XS Applications page, select your application in the tree on the left.
    In the SECURITY panel, make sure that the Public (no authentication required) radio button is not selected. To make changes, choose Edit.
    In the AUTHENTICATION panel, choose Edit, then select SAML in the dropdown box and SAPID in the SAML Identity Provider field.
    Save your settings.
    For some reason, i couldn't add SAPID in SAML identify provider(which is step 4) and i saved the configuration; but now after doing the above changes till step 3 in XS admin console, i'm receving "No successful authentication possible" when the page is refreshed.
    i'm using http://<Elastic ip>:8000, when i run this page im getting "Xs engine running" default screen, but if i navigate to
    http://<Elastic ip>:8000/sap/hana/xs/admin/ i'm receiving "No successful authentication possible" error.
    Please guide me to get rid off this issue now.
    Thanks,
    Siva.

    Any help here will be much appreciated..

  • Conflicting dependency when installing ABAP in Eclipse Kepler

    I have installed SAP HANA Studio Version: 1.0.48 Build id: 201301130825 (372847)
    I downloaded and installed "eclipse-standard-kepler-SR2-win32-x86_64"
    I am following the instruction in "ADT_740_installation.pdf"
    I try to add the components through http://download.eclipse.org/releases/kepler but get a conflict error.
    Here is the log:
    Cannot complete the install because of a conflicting dependency.
      Software being installed: EMF Edit Data Binding 1.3.0.v20140203-1126 (org.eclipse.emf.databinding.edit.feature.group 1.3.0.v20140203-1126)
      Software currently installed: SAP HANA Studio 1.0.48.201301130825 (com.sap.ndb.studio.product 1.0.48.201301130825)
      Only one of the following can be installed at once:
        EMF Common 2.9.0.v20130528-0742 (org.eclipse.emf.common 2.9.0.v20130528-0742)
        EMF Common 2.8.0.v20120606-0717 (org.eclipse.emf.common 2.8.0.v20120606-0717)
        EMF Common 2.9.2.v20131212-0545 (org.eclipse.emf.common 2.9.2.v20131212-0545)
        EMF Common 2.9.1.v20130827-0309 (org.eclipse.emf.common 2.9.1.v20130827-0309)
      Cannot satisfy dependency:
        From: SAP HANA Studio 1.0.48.201301130825 (com.sap.ndb.studio.product 1.0.48.201301130825)
        To: com.sap.ndb.studio.sdk.feature.feature.group [1.0.48.201301130825-8C8FFYPFFCaPDZQgLvCvm8I]
      Cannot satisfy dependency:
        From: SAP HANA Studio - SDK Feature 1.0.48.201301130825-8C8FFYPFFCaPDZQgLvCvm8I (com.sap.ndb.studio.sdk.feature.feature.group 1.0.48.201301130825-8C8FFYPFFCaPDZQgLvCvm8I)
        To: org.eclipse.emf.common [2.8.0.v20120606-0717]
      Cannot satisfy dependency:
        From: EMF Edit Data Binding 1.3.0.v20140203-1126 (org.eclipse.emf.databinding.edit 1.3.0.v20140203-1126)
        To: bundle org.eclipse.emf.edit [2.9.0,3.0.0)
      Cannot satisfy dependency:
        From: EMF Edit Data Binding 1.3.0.v20140203-1126 (org.eclipse.emf.databinding.edit.feature.group 1.3.0.v20140203-1126)
        To: org.eclipse.emf.databinding.edit [1.3.0.v20140203-1126]
      Cannot satisfy dependency:
        From: EMF Edit 2.9.0.v20130610-0406 (org.eclipse.emf.edit 2.9.0.v20130610-0406)
        To: bundle org.eclipse.emf.common [2.9.0,3.0.0)
      Cannot satisfy dependency:
        From: EMF Edit 2.9.0.v20130902-0605 (org.eclipse.emf.edit 2.9.0.v20130902-0605)
        To: bundle org.eclipse.emf.common [2.9.0,3.0.0)
      Cannot satisfy dependency:
        From: EMF Edit 2.9.0.v20140203-1126 (org.eclipse.emf.edit 2.9.0.v20140203-1126)
        To: bundle org.eclipse.emf.common [2.9.0,3.0.0)

    Hi Felix,
    something did not work out as expected here and I dont know what caused it.
    Yesterday when in HANA studio I went over Window->Open Perspective->Other  the option 'ABAP' was available. Today it is not there anymore. I tried to reinstall exactly as indicated above in my original post, but it failed with the log below.
    What is going on here? This is chaos.
    Your original request has been modified.
      "EMF Data Binding" is already installed, so an update will be performed instead.
    Cannot complete the install because of a conflicting dependency.
      Software being installed: EMF Data Binding 1.3.0.v20140203-1126 (org.eclipse.emf.databinding.feature.group 1.3.0.v20140203-1126)
      Software currently installed: SAP HANA Answers 1.500.0.201407081111 (com.sap.ndb.studio.answers.feature.feature.group 1.500.0.201407081111)
      Only one of the following can be installed at once:
        EMF Data Binding 1.3.0.v20140203-1126 (org.eclipse.emf.databinding.feature.jar 1.3.0.v20140203-1126)
        EMF Data Binding 1.2.0.v20120608-0554 (org.eclipse.emf.databinding.feature.jar 1.2.0.v20120608-0554)
      Cannot satisfy dependency:
        From: SAP HANA Answers 1.500.0.201407081111 (com.sap.ndb.studio.answers.feature.feature.group 1.500.0.201407081111)
        To: com.sap.ndb.studio.bi.feature.feature.group 1.0.0
      Cannot satisfy dependency:
        From: SAP HANA Studio - Modeler Feature 1.0.48.201301130825-8l8eFc1FOCvUs3z0KVs7gcjUwKKf (com.sap.ndb.studio.bi.feature.feature.group 1.0.48.201301130825-8l8eFc1FOCvUs3z0KVs7gcjUwKKf)
        To: com.sap.ndb.studio.feature.feature.group [1.0.48.201301130825-8k8YFZMFG0V1LdvJJeajhgxWmha2]
      Cannot satisfy dependency:
        From: SAP HANA Studio - Administration Feature 1.0.48.201301130825-8k8YFZMFG0V1LdvJJeajhgxWmha2 (com.sap.ndb.studio.feature.feature.group 1.0.48.201301130825-8k8YFZMFG0V1LdvJJeajhgxWmha2)
        To: org.eclipse.emf.databinding.feature.group [1.2.0.v20120608-0554]
      Cannot satisfy dependency:
        From: EMF Data Binding 1.2.0.v20120608-0554 (org.eclipse.emf.databinding.feature.group 1.2.0.v20120608-0554)
        To: org.eclipse.emf.databinding.feature.jar [1.2.0.v20120608-0554]
      Cannot satisfy dependency:
        From: EMF Data Binding 1.3.0.v20140203-1126 (org.eclipse.emf.databinding.feature.group 1.3.0.v20140203-1126)
        To: org.eclipse.emf.databinding.feature.jar [1.3.0.v20140203-1126]

  • What TCP/UDP ports are required for Sunray to communicate withSunray server

    Hi,
    Our Sunray appliances and Sunray servers are setting in two different VLANs. For there is no ACL applied between both the VLANs, but we are plannin g to place ACL between these two VLAN for security reason. Do any have a list of ports require for Sunrays to communicate with the Sunray server.
    Thanks for the Help
    Moe Hans
    Network Administrator
    Kwantlen Polytechnic University
    Surrey, BC
    [email protected]

    [http://wikis.sun.com/display/SRSS4dot2/Ports+and+Protocols]

  • HCP - XS Engine not available

    Hi Gururs,
    I have a SAP HANA Cloud Platform Innovation Pack and I am doing some configuration as per Using a Productive SAP HANA Instance. I have following questions:
    1) In my account HANA XS engine is not enabled. ( See screenshot below). How I can enable the same.
    2) If I compare my trial account with innovation pack account, I found that HANA Instances are not coming in the innovation pack. I could easily create the HANA instance in the trial accountm however, same is not true for innovation pack account. Is there any additional configuration we need to make it available.
    3) Since the above options are not coming, because of that I am also not able to create the Database Administrator User. The options ( Development Tools section to create Database user.) are not available to create database administrator as per the standard help.
    4) I created a database schema in Cockpit and created a system by adding the trial instance of the same in Eclipse or Hana studio. When I try to create a Repository content it is giving me Authorization error - Insufficient Privileges (Execute on REPOSITORY_REST)
    Any help will be highly appreciated.
    Thanks!

    Log onto the cockpit on the production landscape and choose HANA Instances.
    In the Development Tools section, click Database User.In the dialog box that appears, a message confirms that you do not yet have a database user.
    Choose Create User.Your user (identical to your SCN user) and initial password are displayed. You must change the initial password when you first log onto an SAP HANA system, such as the SAP HANA Web-based Development Workbench.Note that your database user is assigned a minimal set of roles. This allows you to log onto the SAP HANA Web-based Development Workbench, but not the SAP HANA XS Administration tool.
    To log onto the SAP HANA Web-based Development Workbench and change your initial password now (recommended), copy your initial password and then close the dialog box.
    NoteYou do not have to change your initial password immediately. You can open the dialog box again later to display both your database user and initial password. Since this poses a potential security risk, however, you are strongly advised to change your password as soon as possible.
    In the Development Tools section, click SAP HANA Web-based Development Workbench.
    On the SAP HANA logon screen, enter your database user and initial password.
    Change your password when prompted. You are responsible for choosing a strong password and keeping it secure. SAP cannot provide forgotten passwords.

  • No suitable SAP HANA system configured in Administration Console

    Hi All,
    I have been trying to attach my HANA system to BW on HANA system to create CompositeProviers and such. However, even if  my HANA system is logged on and running fine in HANA Studio, when I try to attach it to BW system I am getting "No suitable SAP HANA system configured in Administration Console" error message.
    I am also following the link below to attach a system.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a0c5d872-fb76-3110-f288-bf714be4a406?QuickLink=index&…
    Has anyone have idea why I am getting this error? Or what else sould I do no to receive this error?
    Thanks a lot.

    Hi Zahid Yener,
    I have seen the following in an different forum..
    Could you please have a look into this:
    Before you assign HANA system to a BW project you have to add the HANA system of the BW system to Systems View of the SAP HANA Administration Console perspective:
    *) Change the perspective to the SAP HANA Administration Console
    *) Right-Click in the Systems view and execute the context menu function Add System...
    *) Add the HANA system of the BW system (you can find the host and instance information of the HANA DB on the status window in the BW system)
    When the HANA system is now added you can then go back to the BW Modeling perspective and attach the HANA system to the BW project. Maybe you are not logged in to the SAP HANA system after you have attached it. Then please execute F5 (refresh).
    BR
    Prabhith

  • HANA administration guide for SP06 and certification refrences

    Hello ALL
    I am writing my HANA SP06 (HANATECH_131SP06) on July  and preparing HA 200
    Please share HANA Administration Guide for SP06 link and other reference links
    Thanks,
    Sankar

    Hi RajiTh R s,
    The training material for SAP Education courses is not available for download anywhere (legally).
    Good news is that you do not need it.
    Most topics that are covered by the exam are clearly explained in the SAP HANA Administration Guide.
    For all the ins and outs about the exam, see my blog SAP Certified Support Associate: SAP HANA - by the SAP HANA Academy.
    Success,
    Denys

  • Sap hana administration guide for sps07

    I want sap hana administration guide for sps07. Can some one share the document if they have already downloaded it earlier ?

    Hi Anju,
    There is a link to older versions of HANA documentation on this page:  SAP HANA Platform – SAP Help Portal Page
    In the intro section, see the last line: 
    Note: The full documentation set for this and older support package stacks of the SAP HANA platform is available on SAP Service Marketplace .
    Cheers,
    Jody

  • Create a public access site to see the documents which are created by administrator

    Hi ,
    I am new to the sharepoint. I would like to create a public facing sharepoint 2013 site .
    Main requirement is Administrator must login to site and create a documents in library.  Those documents must visible to everyone. So that site must be public facing. 
    Please let me know step by step how to resolve it as I am new to this.
    Regards,
    Raj

    Hi,
    From your description, my understanding is that you want to let all users have permission to access a document.
    The first method you could create a public facing site with method below:
    1.      
    You should change settings in CA and your site. You could refer to this article:
    http://blog.cloudshare.com/2012/10/15/how-to-enable-anonymous-access-to-a-sharepoint-2013-site/.This is a video for you:
    How to make your SharePoint 2013 site a public facing website?
    https://www.youtube.com/watch?v=SnOmtE1x8JM
    2.      
    Add your document into the home page: Click gear icon -> edit page -> INSERT tab in the Ribbon -> Web Part -> select your document -> Save.
    The second method you could accomplish your requirement via manage your document permission:
    1.      
    Enter your document library.
    2.      
    Click Library Setting in the Ribbon.
    3.      
    Click
    Permissions for this document library under Permissions And Management section.
    4.      
    Click Stop Inheriting Permissions in the Ribbon.
    5.      
    Click Grant Permissions in the Ribbon.
    6.      
    Enter everyone and choose view only as the screenshot below.
    7.      
    Then users can access this document library via its URL(in my case it is:
    http://sp/sites/sharepoint2013/Shared%20Documents/Forms/AllItems.aspx).
    Best Regards
    Vincent Han
    TechNet Community Support

  • PSA no deletion SAP BW on HANA Rev 61

    Hi,
    PSAs are not getting deleted for some of the datasources due to error loads and multiple runs. System is SAP BW on HANA Rev 61.
    The previous job failure was not corrected  and the subsequent job was started based on the process chain schedule and that one as well failed. This has happened 2 times. Now the PSA table says it has duplicate entries and it is not dropping when we try to delete manually or through program.
    Whenever we try to delete the PSA, the SAPLSDB2 program runs and is stuck in SM51. St22 error log says
    SQL error "-10807" while accessing table "/BIC/B0000674001".
    65        l_s_data TYPE /BIC/B0000674001.
    66 *---1363526 Increasing the security to check the number of records inserted in PSA table
    67 *---is actually equal to data in l_t_data or p_t_data.
    68  DATA: l_rollback TYPE rs_bool,
    69        l_count TYPE i.
    70  l_rollback = RS_C_FALSE.
    71 *---1363526
    72
    73  APPEND LINES OF p_t_data TO l_t_data.
    74
    75  CLEAR: l_s_data.
    76  l_s_data-partno = p_partno.
    77
    78  MODIFY        l_t_data
    79  FROM          l_s_data
    80  TRANSPORTING  partno
    81  WHERE        request = p_requestid.
    82
    83
    >>>  INSERT      /BIC/B0000674001
    85  FROM TABLE  l_t_data
    86  ACCEPTING DUPLICATE KEYS.
    87 *---1363526
    88  DESCRIBE TABLE l_t_data LINES l_count.
    89  IF l_count NE sy-dbcnt.
    90    l_rollback = RS_C_TRUE.
    91  ENDIF.
    92 *---1363526
    Category              ABAP Server Resource Shortage
    Runtime Errors        DBIF_RSQL_SQL_ERROR
    Except.                CX_SY_OPEN_SQL_DB
    Date and Time          10.08.2014 11:28:01
    |Short text                                                                                        |
    |    SQL error "-10807" while accessing table "/BIC/B0000674001".                                  |
    |What happened?                                                                                    |
    |    Database error text: "System call 'recv' failed, rc=145:Connection timed out"                |
    |What can you do?                                                                                  |
    |    Please make a note of the actions and input which caused the error.                          |
    |    -                                                                                            |
    |                                                                                                  |
    |    To resolve the problem, contact your                                                          |
    |    SAP system administrator.                                                                    |
    |                                                                                                  |
    |    Using transaction ST22 for ABAP dump analysis you can see and                                |
    |    administrate termination messages and retain them for longer periods.                        |
    |    Please make a note of the actions and input which caused the error.                          |
    |    -                                                                                            |
    |                                                                                                  |
    |    To resolve the problem, contact your                                                          |
    |    SAP system administrator.                                                                    |
    |                                                                                                  |
    |    Using transaction ST22 for ABAP dump analysis you can see and                                |
    |    administrate termination messages and retain them for longer periods.                        |
    |Error analysis                                                                                    |
    |    An exception occurred that is explained in detail below.                                      |
    |    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught                |
    |    in                                                                                          |
    |    procedure "INSERT_ODS" "(FORM)", nor was it propagated by a RAISING clause.                  |
    |    Since the caller of the procedure could not have anticipated that the                        |
    |    exception would occur, the current program is terminated.                                    |
    |    The reason for the exception is:                                                              |
    |    Database error text: "System call 'recv' failed, rc=145:Connection timed out"                |
    |How to correct the error                                                                          |
    |    Internal call code.........: "[RSQL/INSR//BIC/B0000674001 ]"                                  |
    |    Please check the entries in the system log (Transaction SM21).                                |
    |    You may able to find an interim solution to the problem                                      |
    |    in the SAP note system. If you have access to the note system yourself,                      |
    |    please use the following search criteria:                                                    |
    |                                                                                                  |
    |        "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"                                                |
    |        "GP4PWAW7JG4VX23SSK75NF4776C" bzw. "GP4PWAW7JG4VX23SSK75NF4776C"                          |
    |        "INSERT_ODS"                                                                              |
    |    If you cannot solve the problem yourself, please send the                                    |
    |    following documents to SAP:                                                                  |
    |                                                                                                  |
    |    1. A hard copy print describing the problem (short dump).                                    |
    |      To obtain this, select "System->List->Save->Local File (unconverted)"                      |
    |      on the current screen.                                                                    |
    |                                                                                                  |
    |    2. A suitable hardcopy printout of the system log.                                            |
    |      To obtain this, call the system log with Transaction SM21                                  |
    |      and set the time interval to 10 minutes before and 5 minutes after                        |
    |      the short dump. In the display choose "System->List->Save->                                |
    |      Local File (unconverted)"                                                                  |
    |                                                                                                  |
    |    3. If the programs are your own programs or modified SAP programs,                            |
    |      supply the source code.                                                                    |
    |      To do this, choose "More Utilities->Upload/Download->Download" in the                      |
    |      Editor.                                                                                    |
    |                                                                                                  |
    |    4. Details regarding the conditions under which the error occurred                            |
    |      or which actions and input led to the error.                                              |
    |    You may able to find an interim solution to the problem                                      |
    |    in the SAP note system. If you have access to the note system yourself,                      |
    |    please use the following search criteria:                                                    |
    |                                                                                                  |
    |        "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"                                                |
    |        "GP4PWAW7JG4VX23SSK75NF4776C" bzw. "GP4PWAW7JG4VX23SSK75NF4776C"                          |
    |        "INSERT_ODS"                                                                              |
    |    If you cannot solve the problem yourself, please send the                                    |
    |    following documents to SAP:                                                                  |
    |                                                                                                  |
    |    1. A hard copy print describing the problem (short dump).                                    |
    |      To obtain this, select "System->List->Save->Local File (unconverted)"                      |
    |      on the current screen.                                                                    |
    |                                                                                                  |
    |    2. A suitable hardcopy printout of the system log.                                            |
    |      To obtain this, call the system log with Transaction SM21                                  |
    |      and set the time interval to 10 minutes before and 5 minutes after                        |
    |      the short dump. In the display choose "System->List->Save->                                |
    |      Local File (unconverted)"                                                                  |
    |                                                                                                  |
    |    3. If the programs are your own programs or modified SAP programs,                            |
    |      supply the source code.                                                                    |
    |      To do this, choose "More Utilities->Upload/Download->Download" in the                      |
    |      Editor.                                                                                    |
    |                                                                                                  |
    |    4. Details regarding the conditions under which the error occurred                            |
    |      or which actions and input led to the error.                                              |
    |    The exception must either be prevented, caught within proedure                                |
    |    "INSERT_ODS" "(FORM)", or its possible occurrence must be declared in the                    |
    |    RAISING clause of the procedure.                                                              |
    |    To prevent the exception, note the following:                                                |
    |System environment                                                                                |
    |    SAP Release..... 730                                                                          |
    |    SAP Basis Level. 0006                                                                        |
    |                                                                                                  |
    |    Application server... "pkghnp"                                                                |
    |    Network address...... "10.83.240.20"                                                          |
    |    Operating system..... "SunOS"                                                                |
    |    Release.............. "5.10"                                                                  |
    |    Hardware type........ "sun4u"                                                                |
    |    Character length.... 16 Bits                                                                  |
    |    Pointer length....... 64 Bits                                                                |
    |    Work process number.. 4                                                                      |
    |    Shortdump setting.... "full"                                                                  |
    |                                                                                                  |
    |    Database server... "vsyexhann01"                                                              |
    |    Database type..... "HDB"                                                                      |
    |    Database name..... "HNP"                                                                      |
    |    Database user ID.. "SAPHNP"                                                                  |
    |                                                                                                  |
    |    Terminal.......... " "                                                                        |
    |                                                                                                  |
    |    Char.set.... "C"                                                                              |
    |                                                                                                  |
    |    SAP kernel....... 720                                                                        |
    |    created (date)... "Mar 21 2012 09:58:29"                                                      |
    |    create on........ "SunOS 5.10 Generic_141444-09 sun4us"                                      |
    |    Database version. "SQLDBC 1.00.61.0380109 "                                                  |
    |                                                                                                  |
    |    Patch level. 201                                                                              |
    |    Patch text.. " "                                                                              |
    |                                                                                                  |
    |    Database............. "HDB 1.0"                                                              |
    |    SAP database version. 720                                                                    |
    |    Operating system..... "SunOS 5.10, SunOS 5.11"                                                |
    |                                                                                                  |
    |    Memory consumption                                                                            |
    |    Roll.... 0                                                                                    |
    |    EM...... 100555392                                                                            |
    |    Heap.... 0                                                                                    |
    |    Page.... 0                                                                                    |
    |    MM Used. 75424248                                                                            |
    |    MM Free. 25123904                                                                            |
    |User and Transaction                                                                              |
    |    Client.............. 330                                                                      |
    |    User................ "BIREMOTE"                                                              |
    |    Language key........ "E"                                                                      |
    |    Transaction......... " "                                                                      |
    |    Transaction ID...... "53E66CC9405502F9E10000000A53F03E"                                      |
    |                                                                                                  |
    |    EPP Whole Context ID.... "CEED21FC7C3EC04FA3C0D0912FE05A37"                                  |
    |    EPP Connection ID....... 00000000000000000000000000000000                                    |
    |    EPP Caller Counter...... 0                                                                    |
    |                                                                                                  |
    |    Program............. "GP4PWAW7JG4VX23SSK75NF4776C"                                            |
    |    Screen.............. "SAPMSSY1 3004"                                                          |
    |    Screen Line......... 2                                                                        |
    |    Debugger Active..... "none"                                                                  |
    |Server-Side Connection Information                                                                |
    |    Information on caller of Remote Function Call (RFC):                                          |
    |    System.............. "SP1"                                                                    |
    |    Installation number " "                                                                      |
    |    Database release... 620                                                                      |
    |    Kernel release...... 640                                                                      |
    |    Connection type 3 (2=R/2, 3=ABAP system, E=external, R=reg. external)                        |
    |    Call type.......... "synchronous and transactional type T (emode 0, imode 0)"                |
    |    Inbound TID.........." "                                                                      |
    |    Inbound queue name..." "                                                                      |
    |    Outbound TID........."0A53F03E141153E6C6641A65"                                              |
    |    Outbound queue name.." "                                                                      |
    |                                                                                                  |
    |    Client#............. 330                                                                      |
    |    User................."BIWREMOTE"                                                              |
    |    Transaction......... " "                                                                      |
    |    Call program........."SAPLERFC"                                                              |
    |    Function module "ARFC_DEST_SHIP"                                                              |
    |    Call destination.. "HNP330"                                                                  |
    |    Source server....... "pkgapp2_SP1_03"                                                        |
    |    Source IP address "10.83.240.59"                                                              |
    |                                                                                                  |
    |    Additional information on RFC logon:                                                          |
    |    Trusted relationship." "                                                                      |
    |    Logon return code....0                                                                        |
    |    Trusted teturn code..0                                                                        |
    |                                                                                                  |
    |    Note:                                                                                        |
    |    - For Releases < 4.0, information on the RFC caller is not available.                        |
    |    - The installation number is provided from Release > 700                                      |
    |    Transaction......... " "                                                                      |
    |    Call Program........."SAPLERFC"                                                              |
    |    Function Module..... "ARFC_DEST_SHIP"                                                        |
    |    Call Destination.... "HNP330"                                                                |
    |    Source Server....... "pkgapp2_SP1_03"                                                        |
    |    Source IP Address... "10.83.240.59"                                                          |
    |                                                                                                  |
    |    Additional information on RFC logon:                                                          |
    |    Trusted Relationship " "                                                                      |
    |    Logon Return Code... 0                                                                        |
    |    Trusted Return Code. 0                                                                        |
    |                                                                                                  |
    |    Note:                                                                                        |
    |    - For Releases < 4.0, information on the RFC caller not available.                            |
    |    - The installation number is available from caller Release > 700                              |
    |Information on where terminated                                                                  |
    |    Termination occurred in the ABAP program "GP4PWAW7JG4VX23SSK75NF4776C" - in                  |
    |    "INSERT_ODS".                                                                                |
    |    The main program was "SAPMSSY1 ".                                                            |
    |                                                                                                  |
    |    In the source code you have the termination point in line 84                                  |
    |    of the (Include) program "GP4PWAW7JG4VX23SSK75NF4776C".                                      |
    |    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in                  |
    |    procedure "INSERT_ODS" "(FORM)", but it was neither handled locally nor                      |
    |    declared                                                                                    |
    |    in the RAISING clause of its signature.                                                      |
    |                                                                                                  |
    |    The procedure is in program "GP4PWAW7JG4VX23SSK75NF4776C "; its source code                  |
    |    begins in line                                                                              |
    |    23 of the (Include program "GP4PWAW7JG4VX23SSK75NF4776C ".                                    |
    |Source Code Extract                                                                              |
    |Line |SourceCde                                                                                  |
    |  54|* leave further processing because data is not consistent                                  |
    |  55|                                                                                            |
    |  56|  IF l_inconsistency_found = rs_c_true.                                                    |
    |  57|    p_subrc = 77.                                                                          |
    |  58|    EXIT.                                                                                  |
    |  59|  ENDIF.                                                                                    |
    |  60|                                                                                            |
    |  61|                                                                                            |
    |  62|                                                                                            |
    |  63|                                                                                            |
    |  64|  DATA: l_t_data TYPE ty_t_data,                                                            |
    |  65|        l_s_data TYPE /BIC/B0000674001.                                                    |
    |  66|*---1363526 Increasing the security to check the number of records inserted in PSA table    |
    |  67|*---is actually equal to data in l_t_data or p_t_data.                                      |
    |  68|  DATA: l_rollback TYPE rs_bool,                                                            |
    |  69|        l_count TYPE i.                                                                    |
    |  70|  l_rollback = RS_C_FALSE.                                                                  |
    |  71|*---1363526                                                                                |
    |  72|                                                                                            |
    |  73|  APPEND LINES OF p_t_data TO l_t_data.                                                    |
    |  74|                                                                                            |
    |  75|  CLEAR: l_s_data.                                                                          |
    |  76|  l_s_data-partno = p_partno.                                                              |
    |  77|                                                                                            |
    |  78|  MODIFY        l_t_data                                                                    |
    |  79|  FROM          l_s_data                                                                    |
    |  80|  TRANSPORTING  partno                                                                      |
    |  81|  WHERE        request = p_requestid.                                                      |
    |  82|                                                                                            |
    |  83|                                                                                            |
    |>>>>>|  INSERT      /BIC/B0000674001                                                              |
    |  85|  FROM TABLE  l_t_data                                                                      |
    |  86|  ACCEPTING DUPLICATE KEYS.                                                                |
    |  87|*---1363526                                                                                |
    |  88|  DESCRIBE TABLE l_t_data LINES l_count.                                                    |
    |  89|  IF l_count NE sy-dbcnt.                                                                  |
    |  90|    l_rollback = RS_C_TRUE.                                                                |
    |  91|  ENDIF.                                                                                    |
    |  92|*---1363526                                                                                |
    |  93|                                                                                            |
    |  94|                                                                                            |
    |  95|*---1363526                                                                                |
    |  96|  IF sy-subrc NE 0 OR l_rollback = RS_C_TRUE.                                              |
    |  97|*  Insert not successful - rollback changes                                                |
    |  98|    CALL FUNCTION 'DB_ROLLBACK'.                                                            |
    |  99|*---1363526                                                                                |
    |  100|    p_subrc = 13.                                                                          |
    |  101|  ENDIF.                                                                                    |
    |  102|                                                                                            |
    |  103|ENDFORM.                    "INSERT_ODS                                                    |
    |    isShmLockId  = 0                                                                              |
    |    isUsed      = 1                                                                              |
    |    isCtfyAble  = 1                                                                              |
    |    hasScndKeys  = 0                                                                              |
    |    hasRowId    = 0                                                                              |
    |    scndKeysOutdated = 0                                                                          |
    |    scndUniKeysOutdated = 0                                                                      |
    |    ----- Shareable Table Header Data -----                                                      |
    |    tabi        = 0xFFFFFFF1DD5E8E58                                                            |
    |    pgHook      = 0x0000000000000000                                                            |
    |    idxPtr      = 0x0000000000000000                                                            |
    |    id          = 11    (0x0000000B)                                                            |
    |    shmTabhSet  = 0x0000000000000000                                                            |
    |    refCount    = 0    (0x00000000)                                                            |
    |    tstRefCount  = 0    (0x00000000)                                                            |
    |    lineAdmin    = 4    (0x00000004)                                                            |
    |    lineAlloc    = 4    (0x00000004)                                                            |
    |    shmVersId    = 0    (0x00000000)                                                            |
    |    shmRefCount  = 1    (0x00000001)                                                            |
    |    rowId        = 18446744073709551615                                                          |
    |    scndKeyAdmin = 0x0000000000000000                                                            |
    |    0A53F03E141153E6C6641A65HNP330                          00000001SENDED  RSAR_TRFC_DATA_RECEIVE|
    |    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
    |    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
    |    3433433433333343433334334453332222222222222222222222222233333333544444225545555445445455444454|
    |    0153603514115356366411658E0330000000000000000000000000000000000135E454002312F4263F4141F2535965|
    |    0030004100350033004600300033004500310034003100310035003300450036004300360036003400310041003600|
    |PROG                                                                                              |
    |    SAPLERFC                                                                                      |
    |    0000000000000000000000000000000000000000                                                      |
    |    0000000000000000000000000000000000000000                                                      |
    |    5454454422222222222222222222222222222222                                                      |
    |    310C526300000000000000000000000000000000                                                      |
    |    005300410050004C004500520046004300200020002000200020002000200020002000200020002000200020002000|
    |%_DUMMY$$                                                                                        |
    |                                                                                                  |
    |    0000                                                                                          |
    |    0000                                                                                          |
    |    2222                                                                                          |
    |    0000                                                                                          |
    |    0020002000200020                                                                              |
    |NUMBER_OF_FUNCTION_MODULES                                                                        |
    |    1                                                                                            |
    |    0000                                                                                          |
    |    0001                                                                                          |
    |    00000001                                                                                      |
    |SUPPORTABILITY_INFO-DEBUG_CONTEXT_ID                                                              |
    |                                                                                                  |
    |    0000000000000000000000000000000000000000                                                      |
    |    0000000000000000000000000000000000000000                                                      |
    |    2222222222222222222222222222222222222222                                                      |
    |    0000000000000000000000000000000000000000                                                      |
    |    0020002000200020002000200020002000200020002000200020002000200020002000200020002000200020002000|
    |SPACE                                                                                            |
    |                                                                                                  |
    |    0                                                                                            |
    |    0                                                                                            |
    |    2                                                                                            |
    |    0                                                                                            |
    |    0020                                                                                          |
    |SCREEN                                                                                            |
    |                                                                                                  |
    |    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
    |    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
    |    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222|
    |    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
    |    0020002000200020002000200020002000200020002000200020002000200020002000200020002000200020002000|
    |No.      4 Ty.          FUNCTION                                                                |
    |Name  ARFC_DEST_SHIP                                                                              |
    |SENDER_ID                                                                                        |
    |    pkgapp2_SP1_03                                                                                |
    |    00000000000000000000000000000000                                                              |
    |    00000000000000000000000000000000                                                              |
    |    76667735553533222222222222222222                                                              |
    |    0B71002F301F03000000000000000000                                                              |
    |    0070006B00670061007000700032005F005300500031005F0030003300200020002000200020002000200020002000|
    |SUPPORTABILITY_INFO                                                                              |
    |    ########                                        ##  #                                        |
    |    000000000000000000000000000000000000000000000000000000                                        |
    |    000000000000000000000000000000000000000000000000000000                                        |
    |    000000002222222222222222222222222222222222222222002220                                        |
    |    000000000000000000000000000000000000000000000000000000                                        |
    |    0000000000000000000000000000000000200020002000200020002000200020002000200020002000200020002000|
    |UNIT_ID                                                                                          |
    |    ################                                                        

    Hi Siddartha,
    That option is not working.
    Thanks

Maybe you are looking for