SAP BPC 10 NW MEGA ELITE ENABLEMENT

BPC Transports and Backups

Exercise4a – Create a transport
Exercise4b – Take a backup
Overview of the Business Case

In this exercise we will be transporting and backing up the BPC Environments used during the training course. Since
we don’t have another system available for you to transport into, we will just be setting up and creating the transport,
releasing it, and then locating the actual transports on the file system. Additionally, we will show you how to take a
backup of your BPC Environment as well. You can download the individual environment transports and or backups to
your laptops during class so that you can import them again later in your own system.

There are two ways to move Environments within your landscape.

In Exercise 1, we will show you how to use the standard BPC Transport Procedure which has been integrated to work
within the normal BW Transport Architecture.

In Exercise 2, we will show you how to use the BPC Backup and Recovery Tool which is delivered with BPC via
transaction UJBR.

Using the normal transport procedure is the best practice for moving BPC Environments Objects between your Dev,
QA, and Production systems. This procedure is recommended because it can be audited and controlled from within
the BW Transport Mechanism itself. This is the standard way to move objects within systems which have been
connected via the transport framework. Note that you cannot move Master Data or Transactional Data with this
standard procedure. This is strictly for usage in a Dev/QA/Prod landscape and loading Master Data or Transactional
Data into these downstream systems must be done separately through the normal Business procedure that has been
set up.

Using the backup and recovery procedure can be advantageous in certain situations, namely if you want to move an
entire Environment (along with Master Data and Transaction Data) to another BPC 10 system which has not been
connected via the transport framework. Typically, the B&R mechanism is used to move environments to sandboxes
which are not connected to the normal transport framework. In addition, these backups can be sent to SAP Support or
Development to be restored internally on their systems for further analysis of the actual Customer Environments. We
do not recommend using the B&R procedure during a normal customer implementation of BPC 10 using Dev/QA/Prod
– in that scenario you would always use the delivered transport mechanism to control how your objects are sent to
downstream systems.

Exercise 4a: Set up a Transport for the BPC Environments

of your choice
This exercise starts with you logging into the SAP Back End system through SAP GUI and creating a transport
of a BPC Environment of your choice. Once you have successfully created your transport, you will then
release it and locate the actual transport files on the Server File System. You have the option of importing
these files later to another BPC 10, SP4 system at your own leisure.

This exercise is broken out into five major activities:

-Log onto SAP GUI and go to the Transport Organizer

-Select the Environment you want to transport and choose the objects you want to leave out (or in)
-Create the transport
-Release the transport
-Locate the actual transport file on the Server File System

1. Log onto SAP GUI (shortcut located on the Desktop of your Cloud’s Remote Desktop)

2
2. Enter username: BPC_XX pwd: Welcome!

3. Enter transaction code /nRSA1 as follows:

4. Click on the button labeled: "Transport Connection":

5. In the left hand column, click on SAP Transport, then click on Object Types:
6. In the middle column, find the choose "More Types" and expand the "Environment" type:
7. Double click "Select Objects" and a list of BPC Environments available for transport should pop up:
NOTE: In this exercise we are choosing the Environment BPCB_XX (from the BW Session) but you are free to
choose whichever Environment you wish.

8. Select the BPC Environment BPCB_XX and click "Transfer Selections":

 9. In the right hand column, you should see a list of the objects belonging to this Environment that are to be
transported:

10. Select the objects to be transported by selecting or deselecting the corresponding object. For example, you can
right click on the root node in the tree display (BPCB_XX) and choose "Transport All Below" as shown in the
screenshot:
NOTE: In this example we will be transporting everything listed, however as of BPC 10NW you can now choose
to transport only the granular objects of your choice.
11. After you have selected which objects you wish to transport, click on the Truck Icon to create the transport:

12. The system will prompt you to locate a "Customizing Request" to put the transported objects into. In the next few
steps we will create one. Click the New Icon (Create Request):

13. Name the request something useful as follows and click on the Save Icon:
14. The original Prompt should now have your new Request filled in as follows. Click on the Continue Icon:

15. The system should now have inserted all of the objects from the list into your Transport Request. You can view
the individual object logs and messages in the bottom window:
16. Now that you have created the transport request containing the BPC Environment you wish to transport, you
need to Release it so that you can locate the actual transport file on the Operating System.
NOTE: Before you release a Transport Request, the objects will stay locked inside it until you actually do release
the request. This is intended behavior and the system will not actually write the Transport to the Operating
System until you have done so.

Make sure you have set the Environment Status to "Offline" before releasing your transport:

17. To release a Transport Request, you can use a few different transactions. In this example exercise, we will be
using the transaction "SE09" to find the request and then release it. Go to Transaction SE09 and click the
Display Button at the bottom:
18. Find the Transport Request (Type Customizing) that you created in the previous steps:
NOTE: Your screen may differ from the screenshot below. It may be that you have a different set of transports
under your user in your particular Cloud Server. The exact list is not really important for this exercise, only that
you can find the Transport Request that you already created in the previous steps:

19. Expand the Transport Request list to view all of the different objects that are included in it:

20. To Release the transport you need to release all of the underlying Tasks first (in this case there is only one Task
beneath the main Transport Request). Right-Click on the Customizing Task beneath the main Transport
Request and select "Release Directly" as follows:

Right click on the

"Underlying Task" first –
which is below the main
Transport Request...
21. Now do the same action for the main Transport Request. Click on the main Transport Request and select
"Release Directly" as follows:

Right click on the main

Transport Request next –
which is above the
underlying Task...

22. The system should show you another screen with the log of the Release action. You can hit the refresh button
until the release action is finished (please disregard the actual transport request number in this screenshot since
it may be different from yours anyways):

23. A successful transport release with no errors should look as follows (please disregard the actual transport
request number in this screenshot since it may be different from yours anyways):
NOTE: If you get errors when releasing the request, you can view the logs by clicking on the Document Icon as
follows:

For this particular example, clicking on the log results show the following:

In this case, we see that the error is due to the BPC Environment not being in status "Offline" before releasing
the transport. Go to the BPC Administration Console, set the BPC Environment to "Offline" and then release
your transport again:
 Once released, the Transport Request log will show you all the errors associated with it in a historical time sorted
fashion. In this case, we see that the Export was Successfully Completed as the last step:

24. Once the Transport Request has been released you can then find the actual Transport files which are written to
the File System of the Server Operating System. These Transport files are automatically stored in a default
location on the server which we will show to you in the next few steps. It is these files which are then
automatically copied to downstream servers (such as a QA or Production Server in the same system landscape)
by the BW Transport Framework.

Open up a file browser on the Cloud Server Operating System and navigate to the S: Drive as shown in the
following Screenshot:

NOTE: We have installed the ABAP server on the S: Drive in this Cloud but the drive location may be different
depending on your particular landscape.
25. The SAP Application Server is always installed in a root folder named "usr". The entire SAP Application Server
file structure is located inside this folder. Navigate to the following default location for Transports:

S:\usr\sap\trans

NOTE: This is the SAP Application Server "trans" directory. For simplicity, we will only be finding our transport
files just created in the previous steps. To better understand how the "trans" directory functions within an SAP
Landscape you should take an appropriate Basis education course offered by SAP or talk to a Basis Consultant
who can help explain it to you.

26. Transports always come in two files. A Header file, and a Data file. Each of these files are stored within two
different folders inside the trans directory. These folders are named "cofiles" (for the Header file) and "data" (for
the Data file):

15
 Inside the cofiles folder, you will notice a few files beginning with the letter "K"
Inside the data folder, you will noticed a few files beginning with the letter "R"
These are commonly referred to as "K files" or "R files" when talking about SAP Transports.

Now locate the K and R files for the transport you just created in the previous steps. You can save these files to
test an import to another system later.

27. Open the cofiles folder and find the "K file" that has the same Transport Request Number which was shown to
you when you created your transport. In this exercise, we created a Transport Request that was named
"Transport of BPCB_XX Environment" and it had the Transport Request Number "CSAK900041":

NOTE: When viewing a Transport Request Number from SAP GUI, it always starts with the SID (System ID) of
the system you created it on followed by the letter "K" (referring to the Header file). However, when viewing a
Transport Object/File on the Operating System, the SID (System ID) is moved to the file extension… so in our
example, the Operating System files will be named K900041.CSA (for the Header file) and R900041.CSA (for
the Data file). If your Transport Request was successfully created and released, you should find both of your
files in the "cofiles" and "data" folders:
Exercise 4b: Use the Backup and Recovery Tool to take a
Backup of your Environment
In this exercise we will be using the BPC Backup and Recovery tool (transaction UJBR) to take a backup of a
BPC Environment of your choice. You will choose various options for your backup and execute it. Once the
backup has completed, you will locate the backup files on the Server File System. You have the option of
restoring this backup later to another BPC 10, SP4 system at your own leisure.

This exercise is broken out into four major activities:

-Log onto SAP GUI and go to the Backup and Recovery Tool
-Select the Environment you want to backup and choose the options accordingly
-Run the backup
-Locate the backup files on the Server File System

1. Log onto SAP GUI (shortcut located on the Desktop of your Cloud’s Remote Desktop)

2. Enter username: BPC_XX pwd: Welcome!

3. Enter transaction code /nUJBR as follows:

 4. In the Backup & Recovery Utility Interface, you can choose to make the following settings for an Environment of
your choice. In this example exercise, we are using the BPCB_XX Environment, and we are going to include the
Master Data and Transaction Data in the backup. We will save the backup file to the following location:
"S:\EPMTraining\BPCBackups". The values shown here may vary of course depending on your particular
Implementation Scenario. The idea of the exercise is to show you how easy it is to take a backup of the
Environments you have been working with during this training course:

NOTE: To save the file to the Application Server, you can Execute the program in the Background. To save the
file to your laptop, you would need to Execute the program in the Foreground and be connected to this server
with SAP GUI on your laptop.

5. Execute the Backup Job by clicking on the Execute Icon as follows: (You should see a message in the bottom
left hand corner of the screen saying the background job was submitted)

18
6. To view the log of the backup, enter transaction SM37:

7. Enter the name of the Job just started (BPC_BACKUP_BPCB_XX) and click the Execute Button:

8. Verify that the backup finished successfully by noting the Status "Finished":
 9. Locate the backup files on the Operating System of the Cloud Server by navigating to the correct file path you
used in step 4 (S:\EPMTraining\BPCBackups):

10. You can take additional Backups of the other Environments of the class as well, but keep in mind that the bigger
the Environment and the more Transaction Data or Master Data that it contains, the longer the Backup will take.
© 2010 by SAP AG.
All rights reserved. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services
mentioned herein as well as their respective logos are trademarks or registered tradem arks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other
Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered tradem arks of Business
Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves
informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for
informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to
the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

21