Professional Documents
Culture Documents
Sap BPC 10 Transport Guide
Sap BPC 10 Transport Guide
Transport Process:
Source System
1. Make source Environments to be transported have been set offline
2. Enter RSA1 --> Transport Connection --> Object Types --> More Types --> Environment --> Double
click Selection
4.
4. After you collect all objects you wish to transport, click the Transport Objects button. In pomp up dialog
you generate or enter a transport request. Then click OK.
6.
Target System
7. Set the target Environments offline
8. Enter STMS to refresh the transport request and import
9. Verify the transport log to ensure the transport is performed successfully by entering SLG1 and input UJ in
OBJECT and UJT in SUBOBJECT field. In External ID field you can enter the Environment name if you like.
Performance Consideration:
If you encounter performance issues during transport, you can refer to the following notes to help you out.
1. Increase performance and avoid TIME_OUT: 1795221 - Transport failed with TIME_OUT dump - BPC
NW 10.0
2. Note 1826141 - Transport cost too much memory and time when exporting
Shortcuts:
If you are looking for some utilities to help you faster your operations you can refer to the below information.
1. Setting Offline: Using SE16 --> Table UJ0_PARAM_APP --> Enter Environment ID and Field
AVAILABLEFLAG, then change the fetched Value to 0 to make the environment offline.
2. You can set the target global parameter to ensure automatic environment offline. However, if is not
recommended be utilized in Production system.
3. If your transportation failed somehow, you can perform the report UJT_AFTER_FAIL_PROCESS to
make a quick clean in target before follow up re-transport. This report can also be used to help re-activate
ENVIRONMENTSHELL (by unchecks the Failed Only option).
Reminders:
1. Work Status Settings in Environment level will not be imported according to current design. For details
see 1817597 - Environment-level work status are not transported in BPC NW 10. This may lead to some
inconsistency state. If you have the issue of setting work status in target system after transport, you need
to apply workaround as elaborated in 1823062 - EPM-BPC-NW - Invalid Work Status information after
transport.
2. If you would like to ensure the model technical names consistent within transport landscape, you have
to specify the model level parameters ENABLE_FIXED_CUBENAME in all systems for all models you
would like to keep technical names consistent.
Dinesh Veluru
Apr 10, 2015 7:42 PM
Hi Ning,
transport document is very helpful.
there is a small correction in the first screenshot the "Object Types" should be selected from "SAP Transport"
drop down instead from "XML"> "export" dropdown .
if we select the object types from export drop down then it will not allow to transport.
Thanks,
Dinesh.V
Ivan Blatnik
Sep 23, 2014 11:16 AM
I noticed that Audit settings are not transported. Has this to be redone on all systems?
Thank you
Ivan
Matteo Vannini
Apr 9, 2014 2:09 PM
I'm trying to manually collect the environment, but I can not find under the node Model -> Configuration all
parameters entered from SPRO.
I can see only BPC_STATISTICS and COMMENT.
In particular I would try to understand how I can collect "ENABLE_FIXED_CUBENAME".
Thanks.
Matteo
Aamer Kaleem in response to Kenneth Murray on page 6
Aug 29, 2013 7:14 AM
Yes its mandatory to bring ENV offline
otherwise ur transport req fails
Thanks
Aamer
Kenneth Murray