cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Refresh SAP sourcing environment

Former Member
0 Kudos
197

Hello Experts,

We have an urgent need to refresh our  QA sourcing systems

with Production Sourcing data. We have reffered to note 1594214

for the same.

However few things are not clear from the note.

Do we need to restore full database backup to the target system or

should we be exporting importing CLM data only?

Following are the details of our environments from fcisystem.properties:

========================================================

Production

popdb.owner=SAPSR3DB

popdb.tablespace=PSOURCING

popdb.indexspace=PSOURCING

popdb.blobspace=PSOURCING

======================================================

Quality

================================================================

popdb.owner=SAPSR3DB

popdb.tablespace=PSOURCING

popdb.indexspace=PSOURCING

popdb.blobspace=PSOURCING

==============================================================

The SAP note doesn't provide enough clarity on what

should be the steps to refersh SAP sourcing systems especially when the schema of Netweaver and CLM are same (SAPSR3DB).

Have any one encountered this problem and get past to it? Any help/inputs are highly appreciated.

Thanks,

Nishit

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

The Installation guide stats that Sourcing should be installed to its own schema. It seems that in this case it has been installed to the NetWeaver SAPSR3DB schema which complicates writebacks as all of the associated NetWeaver information with it.

Here's the outline of an approach that I would consider.

  1. Discuss with the NW team if they can recover the NW data alone and then separate out the Sourcing and NW data.
  2. Copy the entire schema to a new schema so the NW data is safe in the original schema. Then work with the new schema as the “sourcing” schema. In this case the NW data in new schema will be useless.
  3. Use the NW backup tool to see if the NW data will be backed-up without the sourcing data being backed up. Then export that somehow into its own schema to keep things separate.

Paul