SAP Environment Compliance – BW Implementation Guide

Applies to

Development and support based on SAP BI 7.0 and EC 3.0

Summary

This document provides step by step guide on how to configure the SAP Environment Compliance as a source system of BW system.

Author:        Lakdawala Ashish

Company:    IBM

Created on: 15th April 2014

Version:        1.0


Introduction

Sap Environment compliance application is implemented with SAP Netweaver web dynpro with database in order to store all the data. In addition to this, application provides an extraction layer which extracts data out of the database with functionality to transfer the data into the SAP-BW. The extraction layer is a java based framework which uses JDBC in order to communicate with the database. It is responsible for interaction with the BW as well as transfer the data from database to BW. Following drawing shows the graphical picture of the technical composition of SAP Environmental Compliance and the interaction between the components application, database and Business Warehouse.

/wp-content/uploads/2014/04/1_433494.jpgPlease note that the extraction layer of the application has bi-directional (read and write) access regarding the database but it can only transfer data from the application (database) into the Business Warehouse. It is not possible to import data from the Business Warehouse into the application (database). This document provides step by step guide on how to configure the EC as a source system of BW system.

Prerequisites

Below list of minimum SP level for each component is required before the installation of the EC BI Content.

SAP BW Version

Recommended Service Pack Level

SAP_BW: 700

SP17, SAPKW70017

BI_CONT: 703

SP5, SAPKIBIIP5

SAP_BASIS: 700

Installation

SAP EC BI Content need to be installed via the Add-On Installation Tool (TCode – SAINT).

/wp-content/uploads/2014/04/2_433495.jpg


Namespace

The required Namespaces are automatically installed after successful installation of the EC Bi Content.

Namespace for TDAG-BW objects are

  • /TDAG/ – Namespace for Technical Data objects
  • /B123/ – Namespace for generated Technical Data objects

In addition to creating the namespaces it is necessary to flag the two new namespaces as modifiable in TA SE03. Because all delivered BW objects in these namespaces have to be activated and this is only possible if the namespaces are marked as modifiable in the customer system.

To do this follow below steps:

  1. Go to SE03
  2. Select “Set System Change options”

    /wp-content/uploads/2014/04/3_433508.jpg

  3. Find the namespaces /B123/ and /TDAG/ and set them to “modifiable”

/wp-content/uploads/2014/04/4_433509.jpg

EC RFC Setup

Log into the (http://<host>:<port>/nwa/destinations) as SAP NetWeaver Admin and Navigate to the SOA Management.

/wp-content/uploads/2014/04/5_433510.jpg

Under the Technical Configuration tab click on Destinations.

/wp-content/uploads/2014/04/6_433511.jpg

Here you need to set up the BW RFC connection to the ERP System.

  1. Set up connection. Enter the ERP System name as destination (Example “BW”). Set up the destination details.

Click on Create and provide Connection and Logon data details as required.

/wp-content/uploads/2014/04/7_433512.jpg

/wp-content/uploads/2014/04/8_433513.jpg/wp-content/uploads/2014/04/9_433517.jpg

    After finishing the destination setup you can test the connection pinging the ERP destination system.

/wp-content/uploads/2014/04/11_433518.jpg

/wp-content/uploads/2014/04/12_433519.jpg

     2.  Set up a second connection to ERP. Enter the ERP System name plus PROVIDER as destination name. (Example “BW PROVIDER”). Use the same setup detail as per above connection.

/wp-content/uploads/2014/04/13_433520.jpg

After finishing the Destination setup the next step is to set up the JCO RFC Providers.

Navigate in NWA to Configuration Management -> Infrastructure -> JCO RFC Provider

/wp-content/uploads/2014/04/14_433521.jpg

In this view create a JCO RFC Destination

/wp-content/uploads/2014/04/15_433522.jpg

Enter as Program ID “XEM” and Provide Host and Gateway Service details.

/wp-content/uploads/2014/04/16_433523.jpg

Enter in the next Step the RFC Destination Name like the step 2 destination “ERP Name + Provider” (Example: “BW PROVIDER”)

/wp-content/uploads/2014/04/18_433524.jpg

/wp-content/uploads/2014/04/19_433525.jpg

/wp-content/uploads/2014/04/20_433529.jpg

After successful set up of JCO RFC Destinations, Go to EC application server.

Login to EC Portal (http://<host:port>/irj) with admin user.

Navigate to EC Plant Compliance –> Configuration –> Integration –> RFC Configuration.

Assign the new created Destination as a “BW System JCo Connection”.

Click on Save and Restart Extractors.

/wp-content/uploads/2014/04/21_433530.jpg

Next it is necessary to activate the RFC connection between the application and the Business warehouse. Therefore we have to configure the BW Property “bw.extractor.progid” (EC Plant Compliance à Configuration à Integration à BW Properties) in order to link the application and the Business Warehouse by using the same program identifier.

/wp-content/uploads/2014/04/22_433531.jpg

BW Maintain Source System XEM

In order to Create EC as a source system of BW, Go to RSA1 and Create Source System under External System and connection type TCP/IP.

Provide Logical System Name and Description As required and Make sure you have provided Type and Release “XEM020”.

/wp-content/uploads/2014/04/23_433538.jpg

Use Program ID “XEM”. The program ID of the source system has to be identical to the program ID customized at EC Configuration -> Integration -> BW Properties (property bw.extractor.progid).

/wp-content/uploads/2014/04/24_433539.jpg

To verify if the source system is created correctly, call Transaction code WE20 and check if the Partner Profile – Partner Type Logical System is created with EC. If this is not the case, visit Transaction code RSA1 and select Source Systems. Left click on the EC Source System and select the option Restore. When the restoring of the Source System is done, call Transaction code WE20 again and check if the Partner Profile is active and created correctly.

After completion of all above described procedure and preparation, all BI-Content objects required for SAP EC are automatically installed which can be activated from business content.

Related Information

SAP Environment Compliance Implementation Guide

https://help.sap.com/saphelp_ec30/SAPEC30_en.pdf

To report this post you need to login first.

4 Comments

You must be Logged on to comment or reply to a post.

  1. John Barrero

    Hi Ashish,

    It’s very useful your guide, thank you for sharing this knowledge. I have a question regarding the step regarding the bw.extractor.progid parameter. This parameter doesn’t appear in my system. Do you know how I can include this parameter? because the EC screen doesn’t permit to create new lines.

    I greatly appreciate your answer.

    Regards,

    John Barrero

    (0) 
  2. Flavio Rasseli

    Hi Ashish! Great post!

    I have created some custom extractors, as per note “2029338 – Developing own BI extractors in SAP Environmental Compliance” and, after deploying the DCs to the WebAS Java and restarting the extractors in the Configuration of EC, the extrators are registered (I can see the log of them been registered but nothing else), but the BW team says they cannot find the new InfoProviders in their side.

    Do you know if there is anything else that need to be done beyond the note mentions?

    Thank you!

    (0) 

Leave a Reply