cancel
Showing results for 
Search instead for 
Did you mean: 

Things to check in SAP SD module after system refresh

Former Member
0 Kudos

Hello, I need to know the follwoing

1) as far as my understanding goes, in system refresh the production data (transaction and matser data) is copied to quailit client including  tables from production. Is this correct ? is all the config also copied from prod to quality ?

2) If a TR (transport request for any config change ) is moved from Dev to quality before system refresh. Then after system , do we need to move the TR again from dev to quality ?

3) what all things need to be checked in ECC from SD point of veiw  aftre system is refreshed. Do batch jobs need to be checked for in quaility ?

regards

Pamela

Accepted Solutions (0)

Answers (7)

Answers (7)

Former Member
0 Kudos

Hi Pamela,

Refresh Activity is the key area which we do to ensure the consistency of production and quality.

1) as far as my understanding goes, in system refresh the production data (transaction and matser data) is copied to quailit client including  tables from production. Is this correct ? is all the config also copied from prod to quality ?

Ans:All the config/transactional and master data also will get copied from production to quality.

2) If a TR (transport request for any config change ) is moved from Dev to quality before system refresh. Then after system , do we need to move the TR again from dev to quality ?

Ans:Yes you need to move the transport from development to quality again as now the quality is just replica of production and you will not have any changes in quality which are not moved to production.

3) what all things need to be checked in ECC from SD point of veiw  aftre system is refreshed. Do batch jobs need to be checked for in quaility ?

Ans:There are not many things to be checked from SD side.But you need to have a list of transports which are not yet moved to production and check whether there are required or not.and depending on that once refresh is done the changes needs to re transported again to quality.No need to check about batch jobs.

Thanks and Regards,

Radhev Rishi.

Jelena
Active Contributor
0 Kudos

Radhev, all this information has already been given in the posts above (please make sure to read through before posting), but regarding this piece:


check whether there are required or not

It is up to each SAP customer how they handle it, but most customers have a policy that everything released from DEV has to be moved up through the QA to PRD. The transports don't just "go away" if they are not re-imported into QA. The changes will still remain in the DEV system, which could compromise its integrity.

But, as I've mentioned, every customer handles it differently and some circumstances also might call for different measures. I would be very careful advising on such matters in general.

Jelena
Active Contributor
0 Kudos

Oh Pamela, have to say I admire your ability to ask questions that seem basic yet are incredibly complex. It is important to clarify whether we are indeed talking about the 'system refresh' or 'client copy'. These are two rather different things but get confused frequently.

1. In general - yes, master data, transaction and configuration tables are copied. However, it is possible to exclude specific tables at least during the client copy (not sure about system refresh). For example, once our hosting provider decided to exclude VBRP table.

2. Yes

3. Technically, as TW pointed out, nothing specific should be required. It's a good practice to have some kind of a checklist of post-refresh activities. Ours includes items mentioned above (printers, background jobs, disable emails, some connections, etc.). But this should be already taken care of before the system is made available to the functional specialists.

As long as you can logon and the system is up and running, it is unlikely there is any issue (e.g. number range is a common problem) that you could discover by doing some kind of quick check. We do run a few transactions (such as VA03, VA05, etc.) but it's a formality that we don't spend more than a few minutes on.

P.S. Please refer to this blog to avoid adding this discussion to your impressive list of unanswered questions. Thank you.

former_member182378
Active Contributor
0 Kudos

Jelena,

You mentioned number range is a common problem, please elaborate on this.

tw

Jelena
Active Contributor
0 Kudos

Hi TW, there are many SAP notes on the subject, this is just one of them: 36139  - CC-INFO: Number range problems with the client copy

If memory serves, in SD specifically this usually has something to do with number range buffering. To resolve it usually we just need to repeat the same action few times until the buffered numbers run out and it gets to the next available number. Then it works fine. It happens about once a year where I work.

patrick_g1
Active Participant
0 Kudos

Hi,

  from my experience following points should be considered too:

  1. Reschedule MMPV (MM periode) Job in Q System.
  2. Deactivate SAP printers if there is no remark liek (TEST) printed on documents out of Q system.
    1. Why this: If you print a test documetn out of Q system with refreshed data and the docuemtn is equal to productive system it might happen that the document will result in real process steps like deliveries etc.

I hope this is also a small help.

Mit freundlichen Grüßen / Kind regards / Meilleures salutations

Patrick

former_member182378
Active Contributor
0 Kudos

Patrick,

good point about printing documents in QAS, we generally donot print any document from QAS, if really needed for testing, we change the printer name in the (specific) condition record Or if time is 3, then we can do this change of printer name in the transaction document itself.

tw

Bernhard_SAP
Employee
Employee
0 Kudos

moved to SD

ravi_kumar100
Active Contributor
0 Kudos

Hi,

To add to the above comments:

Those SMS and automatic mail triggering settings have to be checked and stopped ,else there will be SMS and Email trigger for every OTC cycle tests performed in Quality System.

Regards,

SRK

former_member182378
Active Contributor
0 Kudos

Pamela,

1. Yes, configurations will also be copied from production to quality.

Quality system will become a copy (mirror image) of production system i.e. transaction data, master data and configuration, workbench - so everything will be copied to quality.

2. Yes, what was in quality and not in production, will no more be in quality after the refresh. It needs to be reimported to quality.

3. No checks needed.

TW

Former Member
0 Kudos

Hello TW,

thanks for the reply. So only thing we need to do is to re-import TR from dev to qual( which were not in prod).

another question is how to ensure that after system refresh , system is workign fine from SD  point of view.

how do we ensure that  TVARVC variants are ok as earlier before refersh, Z tables are ok etc ? Should we run two-three sales cycle ?

regards

Pamela

former_member182378
Active Contributor
0 Kudos

Pamela,

If client wants a confirmation, then you need to test the relevant scenarios in quality.

As mentioned before, all the data from production will be copied in to quality including custom table data etc.

tw

Former Member
0 Kudos

HI Pamela

When refresh activity is done and Production copy is taken in quality.

We consider the following points

1. TR back-up has to be taken as these may have to be re-imported in quality for DEV.

2. Batch jobs will be erased so may need to create new batch jobs.

3. Current setting/transaction in Quality will not be present.

If any point post here.

Thanks and regards

Kiran Nazare

Former Member
0 Kudos

Hello Kiran,

why TR's again need to be imported again from Dev to Quality ?

secondly why Batch jobs are erased in quality ?

regards

Pamela