Pre-activities in source system before export

[Former Member]

Hello  Experts,

Please share reason why following activities needs to be done before export:-

1) No switching of operating modes takes place while a system is being copied

2)  No upgrade-prepare is performed

3) No incremental conversion is in progress

4) No canceled or pending update requests should be in the system.

Thanks

S.BASIS

[madasamy_arunachalam · Accepted solution]

Hi

As a System Admin (or say BASIS Consultant/Admin in SAP environment),  need to follow the best practise guidelines and or procedure to ensure that activity is completed without any error/issue so that the new system is in usable condition by/for the business team (or whoever).

The points you have raised were well documented by SAP to ensure, the process is completing smoothly and the source system is ready for export or system copy and target system is in consistency. Refer below for your queries;,

i) Ops Mode : Export/import task is very much process oriented either dialog or background (or update) – For the task to complete, the work process to be stayed the same type until this task is completed otherwise, it get cancelled & entire activity will be jeopardy in status.

ii) No upgrade-prepare – refer below;

iii) No incremental conversion – Before start of export, the upgrade or export tool (SUM?) will   check the system or database for its consistency. If tool find something ugly at these check, the phase get failed & that means error step (left over earlier run?) can’t be over ride.

iv) No Cancel/pending update : This is again very much important for system consistency, otherwise no use for such activity.

v) Also remove table entries from QCM* table, it is temporary table entry , it is not required on target system.

To successful completion of export or upgrade or system copy, refer SAP standard document for more details; Hope this clarifies your doubt...

Best regards

Swami

[Former Member · Accepted solution]

Hello  Swami,

Thanks  for your response. Could you pls help to understand:-

Ops Mode : Export/import task is very much process oriented either dialog or background (or update) – For the task to complete, the work process to be stayed the same type until this task is completed otherwise, it get cancelled & entire activity will be jeopardy in status.

Thanks

S.Basis

[madasamy_arunachalam · Accepted solution]

Hi

Refer below for details;

When operation modes are switched (based on the definition from its time table), the work processes (WP) are redistributed in the active instance.

This means, when WP used as a dialog process (DIA), it can be switched for use as a background process  (BGD) or vice-versa, i.e. depends on the WP type defined in Operation mode.

While switching Ops Mode, WP may not be switched immediately instead WP is set to be switched when next possible ( if WP is busy in its current status, with either DIA or BGD) but this switch is more risk and or possible to get into error mode while system (means, WP) is busy with its export or upgrade activity. So SAP advise to deactivate Ops. Mode switch.

Best Regards

Swami

[Former Member]

Hello  Swami,

One more.. query..as we know, application is down during export and R3load,R3ldctl etc.. tools are used during export-import.

Then, where is WP comes in picture...

Thanks

S.Basis

[madasamy_arunachalam]

Hi

Until now SAP kept option to select "Manual Option" to stop the system, stop system is required to get data consistency;

But for test or test system export, you can still run without stopping SAP instance & in this case, you have to ensure OPs mode is switched off...

After all, it is one individual to follow the SAP Best Practice to minimize the error or just going on his/her own way... Hope this clarifies;

Regards

Swami

[Reagan]

Hello

Please share reason why following activities needs to be done before export:-

Taking a consistent export of the source system is vital for a system copy whether it is for a homogeneous or heterogeneous system copy.

As the above mentioned steps do make changes to the underlying database hence the suggestion.

Regards

RB

[former_member188883]

Hi ,

This is to ensure that no pending activities exists in the source system which is planned to be exported.

Such pending activities may create hindrances and issues during the database export and it will be difficult to identify the root cause of the issue.

For eg: If there are any pending updates in the system for which no action is taken, this pending update will get lost during the migration leading to loss of data. Hence before the migration corrective action to such pending updates needs to be taken.

Hope this helps.

Regards,

Deepak Kori

[Former Member]

Hello Deepak,

Thanks for  explanation as always.  Really, it clear my doubts.

Thanks

S.Basis