BPC transports - how about data?

[Former Member]

Hi,

when we tranport the appset from Dev to Qa all the relavant objects and files (transformation, conversion) are moved to target system thats fine but how about the data?

i read in a document that no masters and transactions are taken care we have to load them in the target system, this methodology is fine if we have the data flow built to perform the data load.

however what if the users maintain certain entries manually? is there a way to move these entries as well to target system? Certain dimension entries are managed manually in our project and it will be difficult to maintain these entries each time in all the systems. So is there a way to handle this?

Regards

[Former Member]

Folks,

Well for all those who need the dev data to be available in Qa then simply copy the xml files from Adminapp folder in dev to similar Adminapp folder in Qa.Well to copy you have the option to download the files to your desktop and then upload again in designated destination.

All the best.

[esjewett]

Hi,

You are correct that there is currently no delivered way to transport master data. This is in keeping with SAP's general transport approach and avoids a host of potential issues since master data control procedures are usually much more lax in Dev than in Prod.

You could keep master data offline, and then use the data manager package available to load master data from a flat file.

If it is worth it for your project, you could consider creating a load process that you can run whenever you do a transport, using the master data automation white-paper available at [https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/00380440-010b-2c10-70a1-e0b431255827].

Otherwise, manual parallel maintenance of master data is the way to go.

Ethan

[Former Member]

Hi Ethans,

thanks for your reply.

if i try to summarise your answer we mean to say here is the data however needs to be either created manually or automated to fill the dimensions. Correct me if iam wrong.

also how about the file service? all the folders and files associated with the appset are transported automatically ? or is there a manual intervention?

because what is observed is when we have transported the appset from dev to qa some of the xml files were not copied.so is this normal ? or we need to manually copy the folder/files from destination to target?

what is your suggestion/recommendation, inputs on the same

Regards

[Former Member]

Hi,

We have moved the appset from dev to qa through standardhe BPC transport methodology and as i said we were able to send all the relevant dimensions, conversion files, transformation files into target system.

Iam just wondering about data? Yes i agree that we can push the data for the masters and transaction through the methods of automation of data load process avialable in BPC.

Also we have to agree upon that all the data required for BPC cannot be brought from BI certain dimension members require data to be maintained manually in member excel so in these scenarios how the data part can be handled?

is there a way how we can manage the data as well without having to manually copy the member id from dev and copy the same in dimension id in qa.

some one throw some light on this.

Regards

[Former Member]

Hi,

We have moved the appset from dev to qa through standardhe BPC transport methodology and as i said we were able to send all the relevant dimensions, conversion files, transformation files into target system.

Iam just wondering about data? Yes i agree that we can push the data for the masters and transaction through the methods of automation of data load process avialable in BPC.

Also we have to agree upon that all the data required for BPC cannot be brought from BI certain dimension members require data to be maintained manually in member excel so in these scenarios how the data part can be handled?

is there a way how we can manage the data as well without having to manually copy the member id from dev and copy the same in dimension id in qa.

some one throw some light on this.

Regards

[pravin_datar]

Typically, in SAP implementations, the master and transaction data are not transported up the landscape through transports. The transport mechanism is for transporting configuration and not data. The data should be sourced from the the respective object/process in the landscape. Also typically, the data in DEV is maitained to do say unit testing of the configuration and generally is not a high quality data whereas the data in QA system is of much better quality since in many cases the integration testing and/or acceptance testing is done there. Having said that, there is a little advantage is transferring the low quality DEV data to high quality QA data, let alone PROD. Hence the occassions that require such data transfer up the landscape are infrequent in typical SAP implementations. However in your case, if you must transfer data automatically, then you can export data from one system and import it in another system. If you have to automate this process then you may have to create custom process chains. However you may want to evaluate the need to do so in the first place.

Regards

Pravin

[Former Member]

Hi Pravin,

Thanks for the response.

Well the documentation available all over the web says the same.Infact for copying the data we have copied the xml files from Adminapp folder in file service in Dev to the similar folder in QA.

anyway thanks Pravin for the time in responding to this query.

have a great day.

Regards