Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

How to speed up SAP full imports?

aro
Regular Contributor
Regular Contributor

Hello team,

our customer has a large number of SAP systems where the full import takes a very long time.

Overview:
- Each SAP system has its own "Security Systems" and an (one) "Endpoint".
- With a full import, the following tables are imported for all SAP systems:
 USR02,USER_ADDR,USRACL,TSTC,TSTCT,AGR_AGRS,AGR_TEXTS,AGR_DEFINE,AGR_USERS,USORG,UST04,UST10C,UST10S,UST12,AGR_1252,AGR_1251


I have now made some tests with 3 SAP systems:

Test "single-threaded"

Import jobs of the type "Application Data Import (Single Threaded)" created for all 3 SAP systems and all triggered at 7 a.m. today.
Result:
The imports are executed in order. First the import for the first system starts and runs through (in an hour and a few minutes). Only then does the second import start, etc.
Total running time: 4:17 hours

Test "Multi-Threaded"

Import jobs of the type "Application Data Import (Multi Threaded)" created for all 3 SAP systems and all triggered at 12 noon today.
Result:
All imports are started at the same time and an import takes between 3:15 and 4:31 hours.
Total running time: 4:31 hours

 

We need to run full imports (weekly) for 50 SAP systems. This includes several large SAP systems with a runtime of more than 6 hours per SAP system (as "single-threaded").

How to speed up SAP imports? What is best practice in such a case?

 

1 REPLY 1

sai_sp
Saviynt Employee
Saviynt Employee

@aro One good practice would be to split up the 50 systems evenly across 7 days of the week. You can use the 'Application Import Job Multi Threaded' and can run jobs together. Single threaded is sequential and might be time consuming as you would have to put it in a trigger chain. Instead schedule 3 systems to start at the same time and then the next 3 systems. I would also suggest to run the bigger SAP system imports during the weekends.

example: Monday 7am - 12pm you can run 3 systems, 12pm - 5pm 3 systems, 5pm - 10pm 3 systems 

over a span of 5-6 days you can cover all 50. 

Note: the above is only an example. You can set the frequency based on your requirement.

 

One other question I have - are all the 50 SAP systems going to be used for SOD? If not, you can considering skipping data from the tables AGR_1252, AGR_1251. Saviynt uses data from these tables only for SOD evaluation. If there is no SOD, you can considering importing

USR02,USER_ADDR,USRACL,TSTC,TSTCT,AGR_AGRS,AGR_TEXTS,AGR_DEFINE,AGR_USERS,USORG,UST04,UST10C,UST10S,UST12