Sap Bpc 10 Transport Guide

7
Generated by Jive on 2015-06-12+02:00 1 Ning He: SAP BPC 10 Transport Guide Posted by Ning He Mar 27, 2013 Many partner friends and customers consult about the efficient and correct way to perform BPC 10 transport recently. As in BPC 10 the transport mechanismhas been significantly fine-tuned compared with previous versions with a lot of behavioral changes, I drafted this transport guide to help partners or customers to facilitate BPC transport process. The version I am demonstrating is BPC 10 SP9 Patch 1. CLM part is not covered. Any comments or suggestions are very welcome. Prerequisites Check: The following prerequisite checks are highly recommended before transport, especially for the first transport: 1. Ensure “Automatic Recording of Changes” has been set in source system otherwise the transport request generation dialog won’t pomp up when you package your selected transport objects. You need to perform the following: 1. a. Transaction SCC4 in source system, select the client where BW is installed and click Display. 2. b. Set the option Changes and Transports for Client-Specific Objects to Automatic Recording of Changes 3. c. After the change is applied and saved, reopen RSA1 and attempt to collect the objects and create the transport request again. 2. The BPC version and patch level in source system and in target system need to be equal. 3. Make sure the Planning and Consolidation installation guide is followed to configure the transport RFC destination. Check transaction RSTPRFC that the right user has been assigned to handle the post- processing of the import. You can refer note 1817817 if you want to know more details about BPC RFC connections. 4. Run report UJA_DATA_CHECKER and enter Environment name to check if the environments in source and in target (if exist) are consistent to avoid unnecessary transport issues. 5. It is NOT best practice to assign task profiles or data access profiles directly to users from design aspect. Furthermore, if you do so you may receive error during transport with error message “Member XXX does not exist in dimension YYY”. 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”

description

Tp Guide

Transcript of Sap Bpc 10 Transport Guide

  • Generated by Jive on 2015-06-12+02:001

    Ning He: SAP BPC 10 Transport Guide

    Posted by Ning He Mar 27, 2013Many partner friends and customers consult about the efficient and correct way to perform BPC 10 transportrecently. As in BPC 10 the transport mechanismhas been significantly fine-tuned compared with previousversions with a lot of behavioral changes, I drafted this transport guide to help partners or customers tofacilitate BPC transport process. The version I am demonstrating is BPC 10 SP9 Patch 1. CLM part is notcovered. Any comments or suggestions are very welcome.

    Prerequisites Check:The following prerequisite checks are highly recommended before transport, especially for the first transport:

    1. Ensure Automatic Recording of Changes has been set in source system otherwise thetransport request generation dialog wont pomp up when you package your selectedtransport objects. You need to perform the following:1. a. Transaction SCC4 in source system, select the client where BW is installed and click Display.2. b. Set the option Changes and Transports for Client-Specific Objects to Automatic Recording of

    Changes3. c. After the change is applied and saved, reopen RSA1 and attempt to collect the objects and

    create the transport request again.2. The BPC version and patch level in source system and in target system need to be equal.3. Make sure the Planning and Consolidation installation guide is followed to configure the transport RFC

    destination. Check transaction RSTPRFC that the right user has been assigned to handle the post-processing of the import. You can refer note 1817817 if you want to know more details about BPC RFCconnections.

    4. Run report UJA_DATA_CHECKER and enter Environment name to check if the environments in sourceand in target (if exist) are consistent to avoid unnecessary transport issues.

    5. It is NOT best practice to assign task profiles or data access profiles directly to users fromdesign aspect. Furthermore, if you do so you may receive error during transport with errormessage Member XXX does not exist in dimension YYY.

    Transport Process:Source System

    1. Make source Environments to be transported have been set offline2. Enter RSA1 --> Transport Connection --> Object Types --> More Types --> Environment --> Double

    click Selection

  • Ning He: SAP BPC 10 Transport Guide

    Generated by Jive on 2015-06-12+02:002

    3. Choose the Environment then click Transfer Selection.

    4. Choose the Objects that you are about to transport

  • Ning He: SAP BPC 10 Transport Guide

    Generated by Jive on 2015-06-12+02:003

    There are some remarks here: For best practice, master data is seldom transported from DEV to either QAS or PRD, however till

    now, it is suggested to transport the Time Dimension Member for the first transport. From experience,static dimension members (not imported from BW Info Provider or external systems) can betransported to shorten preparation phase however users must be aware of the possible inconsistencyit may bring. You can uncheck the Dimension Member if you do not want to transport master data.

    BPF templates will be collected here only if it is validated deployed. Configurations only need to be transported if you really intend to do so. Environment Level Work Status will NOT be transported. See section Reminder.

  • Ning He: SAP BPC 10 Transport Guide

    Generated by Jive on 2015-06-12+02:004

    4. After you collect all objects you wish to transport, click the Transport Objects button. In pomp up dialogyou generate or enter a transport request. Then click OK.

    6. Enter SE09 and release your transport request.

    Target System7. Set the target Environments offline8. Enter STMS to refresh the transport request and import9. Verify the transport log to ensure the transport is performed successfully by entering SLG1 and input UJ inOBJECT 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 - BPCNW 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 FieldAVAILABLEFLAG, then change the fetched Value to 0 to make the environment offline.

  • Ning He: SAP BPC 10 Transport Guide

    Generated by Jive on 2015-06-12+02:005

    2. You can set the target global parameter to ensure automatic environment offline. However, if is notrecommended be utilized in Production system.

    3. If your transportation failed somehow, you can perform the report UJT_AFTER_FAIL_PROCESS tomake a quick clean in target before follow up re-transport. This report can also be used to help re-activateENVIRONMENTSHELL (by unchecks the Failed Only option).Reminders:

    1. Work Status Settings in Environment level will not be imported according to current design. For detailssee 1817597 - Environment-level work status are not transported in BPC NW 10. This may lead to someinconsistency state. If you have the issue of setting work status in target system after transport, you needto apply workaround as elaborated in 1823062 - EPM-BPC-NW - Invalid Work Status information aftertransport.

    2. If you would like to ensure the model technical names consistent within transport landscape, you haveto specify the model level parameters ENABLE_FIXED_CUBENAME in all systems for all models youwould like to keep technical names consistent.

    3. It is encouraged to include neither BPC generated objects such as Multiproviders/VirtualCubes norcustomized BW objects in the BPC transport request. If you do need get customized objects transported, theyshould be transported after BPC transports have been done and the models are stabilized on target (due to thepossible change of the dimension attribute after transport).

  • Ning He: SAP BPC 10 Transport Guide

    Generated by Jive on 2015-06-12+02:006

    SAP China ConsultingBAS Team ManagerNing17525 Views Tags: bpc, bpc_10, transport, bpc_10_nw, business_planning_and_consolidation, bpc_transport,bpc_transport_guide

    Dinesh VeluruApr 10, 2015 7:42 PMHi 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 BlatnikSep 23, 2014 11:16 AMI noticed that Audit settings are not transported. Has this to be redone on all systems?

    Thank youIvan

    Matteo VanniniApr 9, 2014 2:09 PMI'm trying to manually collect the environment, but I can not find under the node Model -> Configuration allparameters 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 6Aug 29, 2013 7:14 AMYes its mandatory to bring ENV offlineotherwise ur transport req fails

    ThanksAamer

    Kenneth Murray

  • Ning He: SAP BPC 10 Transport Guide

    Generated by Jive on 2015-06-12+02:007

    Jul 8, 2013 7:26 PMHi, Would anyone know if it is really necessarcy to bring the environment offline if I am just transportingreports? Thanks

    Aamer KaleemJun 7, 2013 3:26 PMHi,

    When trying to access the "Increase performance and avoid TIME_OUT: 1795221 - Transport failed withTIME_OUT dump - BPC NW 10.0" sap note we are getting an error message saying "Document is notreleased"

    ThanksAamer