Posts

Exploring SAP Program RS_ABAP_SOURCE_SCAN and Its Usage

-
Image
SAP program RS_ABAP_SOURCE_SCAN is a powerful tool designed for advanced search functionality within ABAP source codes. This utility is especially useful for developers and system administrators who need to locate specific pieces of code, identify usages of particular statements or functions, and perform complex code analysis across the entire SAP system. Here’s an overview of its key features and practical applications. Key Features Comprehensive Search Capabilities:  Keyword Search : RS_ABAP_SOURCE_SCAN allows you to search for specific keywords or strings within ABAP programs. This can include function modules, methods, classes, and more. Example of How It Helped In a recent project, we were faced with the task of locating a hardcoded value within our ABAP codebase. This hardcoded value was causing issues, and we needed to identify all instances of it quickly to make the necessary adjustments. Using the RS_ABAP_SOURCE_SCAN program, we were able to scan all the programs and effi...
Post a Comment
Read more

SUM Upgrade - 2EEPU133 Errors occurred during post-handling "RS_AFTER_IMPORT" for "*" "L"

-
Problem : During the SUM upgrade post-processing phase, you may encounter one of the following errors: 2EER9001 InfoCube "2CCSRHUEUTAXCLS" does not exist or 2EER7501XStart of the after-import method &3"RS_ELEM_AFTER_IMPORT" for object type(s) &1"ELEM" (&2" ") or 2EER9118 Error activating element "00O2TPKRL6FA91MDUN07O9MZB" Solution: 1. Follow SAP Note 2948252 - S/4 HANA 1709: Errors with activation of query elements (ELEM). 2. Find the attached file 'Z_DELETE_INCONSISTENT_COMP'. 3. Create a Z* report, copy the text from the attached file, save and activate. 4. Execute the report in order to delete the inconsistent objects from the system. 5. Continue the upgrade procedure.
Post a Comment
Read more

SUM Upgrade - Phase MAIN_SHDRUN/ACT_UPG - DDL Source could not be activated

-
 Solution :  This issue can be resolved as follows: Follow SAP Note - 2895585 - DD: Activation of DDLS P_USERADDRESS002 fails in Upgrade or Update To activate P_USERADDRESS when applying SPs with SUM using a shadow instance: Logon to the shadow system with user DDIC Open transaction SDDLAR, select "DDL Source" in "Repair Tools" and press "Activate" Enter P_USERADDRESS and execute with F8
Post a Comment
Read more

User/Role/Auth/Profile comparisons across the systems/internal

-
 SAP Transaction: S_BCE_68001432 Notes: This transaction is useful for comparing one or more users, roles, or authorizations across different systems.
Post a Comment
Read more

Health Check settings for SAP Web dispatcher using AWS Application load balancer

-
Image
This post explains the health check configuration for an SAP Web Dispatcher located behind an AWS Load Balancer. Configure the health check to use the following path: /sap/public/ping
1 comment
Read more

502 Bad Gateway - Sap Web Dispatcher as a target used in AWS Load Balancer

-
Image
  Issue:  A 502 Bad Gateway error occurs for any request sent to a SAP Web Dispatcher that sits behind an AWS Application Load Balancer. Solution:  Check the target group defined in the AWS load balancer for the SAP Web Dispatcher and ensure the correct protocol version is configured. You will need to switch between HTTP1 and HTTP2 depending on your version.  
Post a Comment
Read more

Test SAML SSO to HANA connection failed in Central Management Console (CMC)

-
Image
The environment in test is BOBJ - 4.2 SP3 HANA - 2.0 SP5 Method used : File based Trust store Several blogs and SAP Notes were used as a starting point for setting up SSO between SAP BusinessObjects and the HANA DB. https://blogs.sap.com/2020/03/22/sap-bi-platform-saml-sso-to-hana-database/ There's an SNote which provides documentation . Configure SAML SSO to HANA according to 1900023 - How to setup SAML SSO to HANA from BI. Based on my experience and all tests, the following pre-requisites are required. 1. Public URLs has to be setup to access XS admin page/Wdisp for the tenant DB 2. SSL is not mandatory. 3. HANA parameters to point to the correct Trustkeystore 4.FW to be open for the required ports. Despite all the configuration, the test connection in CMC always resulted in ""Connection Failed: The test of the HANA SSO ticket used to log onto the HANA DB has failed due to: [10]: authentication failed. (FWM 02133)" error." This appears to be a bug in the CMC...
Post a Comment
Read more