SAP Analytics Cloud Performance - Q4 release - New Story Centralized Performance DashBoard...

 SAP Analytics Cloud admins and consultants, this one’s for you!

Imagine if all your critical performance stats—BI query response times, Story durations, long-running Data Actions, Import Jobs, and large Planning Versions—were available in one view.

Automatically delivered as part our Q4 release, SAP excited to introduce a centralized performance dashboard – the SAP Analytics Cloud Performance One Pager on SAP BTP. Gone are the days of bouncing between tools to get the full picture. Both experienced admins and those new to the tools can easily access insights without navigating through multiple sources.

SAP Cloud Connector – Configuration Overview !!!

In many organizations the administration for the SAP Cloud Connector is not managed by the integration team. However, knowing which URL paths (HTTP) or RFC-enabled function modules are configured, is quite helpful.

This enhancement for the WHINT Interface Catalog is adding the capability to generate an Excel overview into SharePoint. You are able to see the following information (as in the SAPCC itself):

• Virtual and internal host name
• Protocol
• Type
• Authentication
• Description
• Resources (URL Path/RFC name or pattern)

Create a new entry for the SAP Cloud Connector itself (localhost)

WHINT IFC (Cloud)

iFlow configuration

Parameter

• Cloud Connector: http://host.scc:port (URL of the SCC)
• Proxy Type: On-Premise
• Location ID : Location ID of the SCC (optional)
• Authentication : Authentication method + Credentials

SSO (Single Sign-On) – Error Description & Resolutions !!!

SSO Unable to load GSS-API DLL 

Error Code 1 - SSO Unable to load GSS-API DLL

SNCPDLInit()==SNCERR_INIT

Unable to load GSS-API DLL

Names “sncgss.dll”

Solution 1. → Install SAP Secure Login Client

Step 1- Download SAP Secure Login client lates version: -

Go to the ONE Support Launchpad and choose Software Downloads

Support Packages and Patches By Alphabetical Index (A-Z) S SAP SECURE LOGIN CLIENT SAP SECURE LOGIN CLIENT 3.0.

Step 2- Close SAP GUI & Install SAP Secure Login Client

Step 3. Restart laptop and it should work

Choose a login certificate for authentication

Error code 2. “Choose a login certificate for authentication.”

→ Solution: Users need to login with Windows main password at least once to established connection Cause of this issue is “Trust is not established between the SAP server and the client X.509 certificate”.

Step 1. Close the GUI

Step 2. Lock laptop (WINDOW+L) → Login with Window Main password.

(Don’t login with Finger scan, PIN, Card, Other)

➔ Open GUI again and it should work.

If still an issue, please take complete PC/laptop restart.

A2210223: Server does not trust my certificate path 

→ Solution: Users need to login with Window main password at least once to established connection Cause of this issue is “Trust is not established between the SAP server and the client X.509 certificate”.

Step 1. Close the GUI

Step 2. Lock laptop (WINDOW+L) → Login with Window Main password.

(Don’t login with Finger scan, PIN, Card, Other)

➔ Open GUI again and it should work.

If still an issue, please take complete PC/laptop restart.

Secure Network layer (SNC) error

Solution: The Error due to Old Desktop shortcuts of SAP Logon Pad

Delete the SAP Logon old Shortcut from Desktop and launch application directly.

Start→Search→SAP Logon→Open

 

WSAETIMEDOUT: Connection timed out RETURN CODE: 20 

Error code 5. WSAETIMEDOUT: Connection timed out RETURN CODE: 20

Issue with Sap tool “VIM Validation Client”, & “Analysis for Microsoft Excel”

Solution: →

→Download & Install 'SAP Analysis for Microsoft Office'

Step 1- Go to the ONE Support Launchpad and choose Software Downloads and search.

Step 2. Close SAP GUI App and Install SAP Analysis for Microsoft Off

Step 3. Laptop restart → It should work.

Logon Balancing error 88: Cannot connect with message server(rc=9)

Error code 6. “Logon Balancing error 88: Cannot connect with message server(rc=9)”

Solution: →It’s not related to SSO.

(Reason: Server is not available; Check with Infra / Basis Team).

Manual Login Option 

Error code 7. Manual Login Option.

➔ Solution :- Right Click on System→ Select SNC Logon Without Single Sing -ON

User account is locked

Error code 8. User account is locked.

Solution –User is locked by Security / Basis Administrator.

No user account found in the system 

Error code 9. No user account found in the system.

Solution – Users don’t have sap account in the system.

ECC to S/4HANA Conversion STEPS...!!!

*Step 1: Assessment (SAP Note 2269324)*

- Evaluate current ECC system
- Identify customization, data volume, and integration points

*Step 2: Strategy (SAP Note 2279391)*

- Choose conversion path: brownfield, greenfield, or hybrid
- Define scope, timelines, and resources

*Step 3: Preparation (SAP Note 2287141)*

- Set up project team
- Complete ECC system maintenance
- Data cleansing and optimization

*Step 4: Software Update (SAP Note 2293511)*

- Upgrade to latest ECC EHP
- Apply necessary support packages

*Step 5: S/4HANA Readiness Check (SAP Note 2294136)*

- Run S/4HANA Readiness Check tool
- Identify potential issues

*Step 6: Data Migration (SAP Note 2300721)*

- Use Data Migration Cockpit or other tools
- Migrate data to S/4HANA

*Step 7: System Conversion (SAP Note 2305411)*

- Execute system conversion using SUM tool
- Follow SAP S/4HANA conversion guide

*Step 8: Testing and Quality Assurance (SAP Note 2310171)*

- Perform unit, integration, and user acceptance testing
- Validate data and processes

*Step 9: Cutover and Deployment (SAP Note 2315421)*

- Plan cutover
- Deploy system
- Provide end-user training

*Step 10: Post-Conversion (SAP Note 2320171)*

- Monitor system
- Address any issues
- Optimize performance

SLT Replication in a NUTShell...!!!

1. Login to SLT Development Server – SAPBASIS / f2xxxx

2. Go to LTRC and select the appropriate Configuration – In our case, ECC_PRD is the config with mass transfer ID – 29 being used for data transfer from DEV/250 to HANA AXD ECC_PRD schema.

(SLT config name and target HANA schema will be same)

3. Ensure that you selected correct MASS TRANSFER ID and select “Processing Steps” tab

4. For every request to setup SLT table transfer, we need to process all the 5 steps in sequence without FAIL

Ensure the requested tables are updated on tracker link - SLT Tracker

Step#1 – Get the list of requested tables to be SLT’d and add it here

Execute it

Perform the same step through STEP#5 until “Runtime generation module”

5. Once all the steps are complete, proceed to trigger replication for these configured tables

6. Add the requested table list and select “Start Replication”

7. Execute it to trigger the real time replication for these selected tables

8. Once the replication started, switch to tab “Data Transfer Monitor” and ensure there is no “Load/Blocked” entries on column “Blocked Processing Step”

Once all the above steps are complete, confirm the requestor that the tables are configured for SLT.