Welcome to the Transport & CLM (Content Lifecycle Management) lesson for

SAP BusinessObjects Planning and Consolidation 10.0, version for SAP

NetWeaver.
1
After completing this lesson, you will be able to perform the actions listed
above.
2
This Transport topic describes the new improved granular transport feature
which allows you to transport almost all components individually utilizing the
standard NW transport framework. This topic also describes how to configure
and run the transports via SAP GUI.
3
Transport Policy:
Is to move the content of environments across a landscape. For example,
transporting an Environment from a development system to a test system then
to a production system.
For performance reasons during transport, the application checks the objects
that exist in the target system and only transports objects that have changed.
Granular object transport behavior:
Granular transport mode means transporting the changes associated with an
Environment without having to transport the entire Environment (In BPC 7.5
NW, the only option is to transport entire Appset).
That is transporting the individual components such as dimensions, dimension
members, applications, work status settings, report, and so on separately.
Besides, transporting one or more Environments at a time is also possible.
Full integration with CTS:
Granular transport in BPC10 is done by the transport UI integrated with BW.
4
With BPC 10 it is much easier to limit what the transport should include,
which reduces the transport times significantly compared to BPC 7.5 NW.
The big problem with BPC 7.5 NW is that the transport is collecting and
bringing over way too many objects into the next system, which takes a long
time to eventually create the needed change list.
Transport only the objects which are needed.
No need of maintaining separate transport process strategy for BPC objects.
As it is fully integrated into NW CTS, easy for system administrators to do
maintenance/scheduling jobs along with other NW objects.
Can use the standard NW transport debugging tools for better error analysis.
5
Transports Prerequisites:
All these Prerequisites are performed in the backend NW System.
As the BPC 10 transport process is integrated to NW transport framework, all
standard NW transport framework prerequisites need to be completed
before.
CTS Configuration:
SAP NetWeaver includes the Change and Transport System (CTS), which is
a tool that helps to organize development projects in the ABAP Workbench
and in Customizing, and then transport the changes between the SAP
systems of a system landscape.
Create User ALEREMOTE using SU01 transaction.
Create an RFC destination to allow the import method to be executed in the
correct client. Otherwise it is executed in client 000. Use transaction
RSTPRFC to create the destination for this client.
6
In this mode, if a transported object exists in the target system, it is modified
with the changes from the source system. If it does not exist, it is created.
These are the Environment objects which support Normal Mode of Transport.
Compared to BPC 7.5 NW, where only complete Environment transport is
possible, this is a big improvement.
7
In this mode, the objects which are explicitly mentioned for deletion are
deleted.
These are the only Environment objects which support Deletion Mode of
Transport.
8
Dependency Check:
In order to transport successfully, make sure that the dependent objects exist either in target
system or transport request. For example, application Appl1 dependents on dimension Dim1, so
to transport Appl1, make sure Dim1 has already existed in target system or Dim1 has been
collected in the transport request, otherwise, transport Appl1 will fail.
During Transport creation process:
Get dependent entity check means transport framework will check the existing of these
dependent entities, transport framework will raises warning message of missing these
dependent entities when release transport request. User can continue to do transport through
selecting continue with warning message. If the dependent entities have already existed in
target system, transport will succeed otherwise transport will fail.
During Import process:
Dependency check during import means this dependency check is executed during importing.
If this type of dependency check fails, roll back will happen on the single entity (corresponding
to transport granularity) that encounters error during transport and it will not affect other entities.
During Data Checked process:
Data checker is executed after importing. Roll back will not be executed at this step. Error or
warning message will be returned back when there are issues during this step.
Note: Besides these three types of dependency check, transport framework will check the
existence of Environment info when release transport request, if Environment Info has not been
collected in transport request, warning message of missing Environment Info will be returned
back by transport framework even if the Environment Info has not been set as the dependent
entity.
9
10
Transport Steps:
This is a big change/improvement in BPC 10, where a standard NW transport
UI is used instead of its own BPC transport UI (UJBPCTR transaction in BPC
7.x versions)
Log on to the Source NetWeaver System (Backend), enter transaction RSA1
and choose the Transport Connection tab in left column to start the transport
process.
11
Transport Steps:
This is the standard BW transport process and now BPC objects are included
to this framework itself.
In the left column, under SAP Transport group, choose Object Types.
In the middle column BPC objects are found under More Types group.
Choose >Environment and double-click Select Objects to choose a new
Environment for transports.
Already selected/transported Environments are visible under Environment
group itself for future transports.
12
Transport Steps:
All the Environments in the system are displayed here, select the one which
need to be transported.
Click the Transfer Selections button to go to the selection screen.
13
Transport Steps:
This is the new granular transport feature which allows to select only the
required objects for transports rather transporting entire
Environment/Environment for all small changes.
Be sure to select only the objects which you need to transport.
Note: Before transporting make sure that the Environment is offline in both
Source and Target systems so as to not allow any further changes during
Transport. Transport will not be successful (will get error message) if it is not
offline.
14
Transport Steps:
Once all the required Transport objects have been created, create a
customizing request to include these transport objects and release it for
transport.
According to the transport route configuration (prerequisite) the import
process starts automatically. If not, using transaction>STMS import can be
triggered manually.
Note: All the BW objects are not really transported into target system. Actually
they are generated in target system when meta data object is transported.
Same for virtual info provider, when BPC application is transported with GRC
integration flag on in source system, virtual provider is generated accordingly in
the target system.
15
Deletion Mode:
This process is almost same like the Normal mode except the step to choose
the BPC Deletion type instead of Environment type.
Note: If deletion fails for an object, the changes for that object are not made in
the target system. The object in the target system remains unchanged. This
does not affect the deletion of other objects in the target system
16
Debugging Transport Issues:
The Log reports the successful completion of a transport request, as well as
warnings and errors encountered during the transport.
To find only the transport logs specific to BPC, use the transaction SLG1 and
in the Object field enter UJ and in the Subobject field enter UJT. Click the
execute button.
Messages, like the Environment status not offline; cannot export/import
transport request, appear which guides you to the exact source of the issue.
This CLM (Content Life Cycle Management) topic describes the new process of
maintaining and shipping the application content across the Ecosystem.
17
Content Lifecycle Management (CLM) aims to deliver a reusable software
component that helps SAP customers to leverage application content
developed by the ecosystem.
CLM helps content providers to establish a common channel for delivering the
application contents and their subsequent changes in terms of content
packages.
For customers using those packages, CLM makes it possible to analyze the
contents from different vendors in a manageable way and keep the contents
that fit closer to their business.
18
Every customer demands a solution for content
Differentiator against competition
Enables Best Practice and Application delivering through content
Enables scaling, fast and more flexible go to market
Customers can reduce the implementation effort
Customers have access to dramatically more expertise from the partner
ecosystem (as partners can create, package and ship content)
Customers can reduce costs and speed deployment by upgrading content --
fix only the delta
19
Main components of CLM are Content Groups and Packages.
Content Groups features:
Extract and package a content group. Compare content group versions and
deploy a content group directly to an application system. Filter the content
group and view history of Content Group.
Packages features:
Export a package as a zip file to make it accessible across system
landscapes. Import a package and subsequently deploy the content to a
target application system. View history of Packages.
20
SAP with its vast knowledge base of different solution areas creates content
by industry.
Vendors / Partners having some specialized knowledge in some areas create
content by industry.
Customers themselves based on the project scope and specific requirements
create content themselves.
21
BPC and CLM Roles Assignment:
BPC roles on CLM server: Assign these roles to the CLM user
/POA/CLM_BPC_USER CLM actions
SAP_QAP_RFC_DESTINATIONS trust system
SAP_BPC_BTCH_JOB background job
CLM roles on BPC server: Assign these roles to the BPC user
SAP_BPC_CLM_EXPORT extraction
SAP_BPC_CLM_IMPORT deployment
SAP_QAP_RFCACL_DEVELOPER remote function call
SAP_QAP_RFC_DESTINATIONS trust system
CLM RFC Destination:
Using transaction SM59 create a RFC destination for CLM under ABAP
Connections section.
CLM System Configuration:
In CLM server using transaction simgh complete the configuration.
22
23
CLM Process Flow: This is a scenario between Vendor and Customer content
handover.
Vendor creates a Package after editing the Content Group and once the
Package is locked without any further changes required, it is exported to the
customer.
Customer imports the Package and compares the Content groups with
existing ones and once satisfied deploys it with or without any customization
according to their business scope.
24
CLM Process Steps:
Launch CLM from the system (where CLM installed) by Transaction Code
NWBC(need role /POA/CLM_BPC_USER)
After logon, click Manage Content Groups to start working with CLM
You should now be able to perform the actions listed above.
25
26