SAP Business Intelligence TR strategy

By SAP BAU BI Team

1

Introduction BI Delivery note

What is Transport Note (TN)

Transport Note is a request form submitted by a developer for promoting a TR / configuration between SAP BI source and target systems. TN encompasses all the necessary details including Project / CR / Incident along with requestor and business approver details.

Key benefits: TR reference and tracking: - Each TR tagged with respective Project / CR/ Incident, which provides an insight about changes included in the TR. - Flexible to handle delivery of solution by excluding all relevant TR from TN in case of any. Configurations info along with ABAP transports: - Most of BI transports need pre requisite steps to be performed prior to import any TR, like data source replication data deletions, initialisations etc. - In lieu of BI pre requisite steps most of the TR may result in object corruption / TR failures. - As TN contain both manual and ABAP transports, TR movement will be handled more effectively.

Key advantages
Return codes across the landscape: - TN provides TR RC information across the landscape within in single template. - TN provides quick insight about solution movement through TR movement and keeps update developer for further investigations in case of unexpected RC.

Reusability of the existing objects / Data model: - Objects which are part of new projects will be subjected to BAU team review and provision for suggestions to reuse existing objects / model (in case of any). - By increasing the usage of existing objects / model, data growth and redundancy will be assured. Gateway review : - TN approvals will proof the impact of data deletions / re initialisation over other data models. - Avoids potential conflict objects movement between different projects / CR. - Provides over view about documentation availability related to TR and or solution. - Output of DN can be feed into Governance meetings in order to prioritize business needs, in case of any conflict objects identified.

Review and Approval process

Quality movement:

1.

Developer creates a TNQ including manual and Automate transport requests with appropriate sequence and submit for BAU BI system owner approvals. BAU BI architect will validate TNQ with respective to the following : a. Impact on existing data model / live solution b. Naming conventions and manual steps

2.

and subjected to approve / reject TNQ (with justification, in case of any). 3. Developer will have to re submit TNQ with missing information / steps and submit for approval (in case of rejection).

4.

Based on BAU BI architect approval developer will share TNQ details with Basis team for solution movement (Dev Quality).

5. In case of any new TR need to fix any bugs during functional testing (in Quality) a TNQ should be amended / created for new set of transports and submit for BAU BI architect approval.

Review and Approval process

Pre production movement:

1. 2.

For pre production movement, a separate TNR will be submitted by developer with TR information. Step 2 and 4 will be applied till TNR gets approved by BAU BI Architect. Developer / project teams will share approved TNR with Basis team for solution movement (subjected to Business sign off).

Production movement:

1.

For production movement, a separate TNP will be submitted by development team with TR information and step 2 and 4 will be applied till TNP gets approved by BAU BI Architect. Developer / project teams will share approved TNR with Basis team for solution movement (subjected to Business sign off). TNQ 2 working days TNR - 2 working days

2.

SLA for BAU BI validations:

1. 2.

3.

TNP 2 working days