Schedule Initial Load

Context

The initial load replication option has a master program /SMFND/DSF_DRIVER_PROG that needs to be scheduled as a background job with the required variant (using transaction SM36 or SE38) . The key fields of the variant are:

Mobile Application: SAP_ASSET_CENTRAL_INTEGRATION
Data Store ID: SACI_INITIAL_LOAD

All the active schedules of the data store are processed in the defined sequence.

The authorization object required to run the migration program is as follows:

Authorization Object	Authorization Attribute	Value
/SMFND/A01	/SMFND/APP	SAP_ASSET_CENTRAL_INTEGRATION
/SMFND/A01	ACTVT	16

Caution

During the initial load process, all the transaction queues are handled by the tRFCs and registered to the destination “NONE”. If the destination is not registered in the transaction code SMQS (queue scheduler), then all the available work processes can be utilized, leading to any of the following:

Timeout issue or memory issue in the ERP system
Heavy load on asset central foundation system

The destination “NONE”' should be registered in the transaction code SMQS (queue scheduler). Also, ensure to set the value Max. Conn. (Maximum Number of Connections) as per general recommendation (25% of total dialog work processes but should not exceed the threshold of 40 for an optimized load in the asset central foundation system). The field maximum number of connections determine the number of work processes that can be utilized during the initial load run. Refer to the SAP Notes 1403974 Information published on SAP site

, 1250813

, 726148

for more details on work processes utilization and SMQS.