SAP connector failing after upgrade to v24.4 from v24.2

[PeterRaja]

Hi Team,

We are using SAP type connector to import SAP data to Saviynt via import job which is failing after upgrade to v24.4 from v24.2. We are getting log error as below,

Any help should be be highly appreciated. Thanks in advance.

"2024-09-02T06:14:14.439+00:00","ecm","domain.FlatViewJobcontrolController","http-nio-8080-exec-42-4v8p8","DEBUG","The running job list is []"
"2024-09-02T06:14:14.006+00:00","ecm-worker","","null-7plkn",""," com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: No RFC authorization for function module RFC_METADATA_GET. (Remote shortdump: RFC_NO_AUTHORITY in system [PS4|XXXXXXXXXX.sap.abc.fr|00])"

"2024-09-02T06:14:18.284+00:00","ecm","domain.FlatViewJobcontrolController","http-nio-8080-exec-34-4v8p8","DEBUG","Before fetching jobEnddate and SavResponse from EcmImportJob first element from qrtzTriggerDataList : [job_name:SapImportJob, job_group:DATA, trigger_name:ACCESS-AzureAD, trigger_group:GRAILS_JOBS, next_fire_time:4070945700000, CRON_EXPRESSION:0 15 10 * * ? 2099, TRIGGER_STATE:WAITING]"
"2024-09-02T06:14:18.284+00:00","ecm","domain.FlatViewJobcontrolController","http-nio-8080-exec-34-4v8p8","DEBUG","After fetching jobEnddate and SavResponse from EcmImportJob first element from qrtzTriggerDataList : [job_name:SapImportJob, job_group:DATA, trigger_name:ACCESS-AzureAD, trigger_group:GRAILS_JOBS, next_fire_time:4070945700000, CRON_EXPRESSION:0 15 10 * * ? 2099, TRIGGER_STATE:WAITING, SAVRESPONSE:null, prev_fire_time:null]"
"2024-09-02T06:14:18.284+00:00","ecm","domain.FlatViewJobcontrolController","http-nio-8080-exec-34-4v8p8","DEBUG","totalData 68"
"2024-09-02T06:14:18.288+00:00","ecm","domain.FlatViewJobcontrolController","http-nio-8080-exec-34-4v8p8","DEBUG","The running job list is []"
"2024-09-02T06:14:18.001+00:00","ecm-worker","","null-7plkn","","remote: "
"2024-09-02T06:14:18.001+00:00","ecm-worker","","null-7plkn","","remote: ======================================================================== "
"2024-09-02T06:14:18.001+00:00","ecm-worker","","null-7plkn","","remote: "
"2024-09-02T06:14:18.001+00:00","ecm-worker","","null-7plkn","","remote: You have reached the free storage limit of 10 GiB on one or more "
"2024-09-02T06:14:18.001+00:00","ecm-worker","","null-7plkn","","remote: projects. To unlock your projects over the free 10 GiB project "
"2024-09-02T06:14:18.001+00:00","ecm-worker","","null-7plkn","","remote: limit, you must purchase additional storage. You can't push to your "
"2024-09-02T06:14:18.001+00:00","ecm-worker","","null-7plkn","","remote: repository, create pipelines, create issues, or add comments. To "
"2024-09-02T06:14:18.001+00:00","ecm-worker","","null-7plkn","","remote: reduce storage capacity, you can delete unused repositories, "
"2024-09-02T06:14:18.001+00:00","ecm-worker","","null-7plkn","","remote: artifacts, wikis, issues, and pipelines. "
"2024-09-02T06:14:18.001+00:00","ecm-worker","","null-7plkn","","remote: "
"2024-09-02T06:14:18.001+00:00","ecm-worker","","null-7plkn","","remote: ======================================================================== "
"2024-09-02T06:14:18.001+00:00","ecm-worker","","null-7plkn","","remote: "
"2024-09-02T06:14:18.001+00:00","ecm-worker","","null-7plkn","","To gitlab.com:saviynt/cloud-ops/customer-customizations/sigplc/sigplc-prod-support-eks.git"

Regards,

Peter

[NM]

Hi @PeterRaja , as per logs you have reached db storage limit.

Raise a ticket with saviynt as you encountered the issue after upgrade.

[rushikeshvartak]

Its seems target sap has been upgraded. Check with sap team

The SAP connector is trying to call the RFC_METADATA_GET function module to retrieve metadata, but the SAP user account being used by the connector lacks the necessary RFC authorization to execute this function. This is likely due to changes in security settings or authorization roles after upgrading to Saviynt version 24.4.

Steps to Resolve:

1. Check SAP User Authorization:
• Log in to the SAP system with the user credentials used by the Saviynt connector.
• Use transaction code SU53 to check for missing authorizations after attempting to run the job. This transaction will show what authorizations the user is lacking.
2. Grant Required RFC Authorization:
• The SAP user needs the necessary authorization to execute the RFC_METADATA_GET function module. This is typically part of the S_RFC authorization object in SAP.
• Assign the appropriate RFC authorization, such as:
• S_RFC with RFC_TYPE = FUGR (Function group) and RFC_NAME = SYSTorS*` to allow execution of necessary SAP standard function groups.
• You might also need to check for specific authorization objects related to your SAP environment