How to resolve the transport errors RC 12 and RC 8 in a specific scenario

Issue:

When transporting objects from Development to Test Servers, the transport gets cancelled (RC=12) or ends with errors (RC=8) with the following messages-

If transporting BEx objects like query elements: error message:
  • Invalid Objects: ‘After Import’ terminated (see long text). Error Current imported l_th_trkorr_import_all has 2 (lines) in TP command fatal error
  • Error (000) in TP command Returncode of trkorr trkorr_no_1
  • Errors occurred during post-handling RS_AFTER_IMPORT for ELEM L
  • The errors affect the following components: BW-WHM-MTD (Metadata Repository)
  • Error activating element

Continue reading “How to resolve the transport errors RC 12 and RC 8 in a specific scenario”

How to resolve the ERROR DBMAN 305: Error in reading the data of the InfoProvider

The issue is generally encountered when a query is executed in SAP BW. The query throws this error and does not display any data.

Issue:

Query based on a multiprovider is executed. Below error message is displayed:

Continue reading “How to resolve the ERROR DBMAN 305: Error in reading the data of the InfoProvider”

How to do Remodeling of Infocube using customer exit option

Remodeling is a new feature added in NW04s BI 7.0 version of SAP BW. It enables to change the structure of an Infocube that is already loaded with data.

Using remodeling a characteristic can be simply deleted or added/ replaced with a constant value, value of another InfoObject (in the same dimension), with value of an attribute of another InfoObject (in the same dimension) or with a value derived using Customer exit.

Similarly, a key figure can be deleted, replaced with a constant value or a new key figure can be added and populated using a constant value or a Customer exit.

Assume, you have an InfoCube for Sales which is already loaded with data. Assume, there is an InfoObject ZCUST_DOB which maintains Customer’s date of birth.

The Business requirement is, the InfoCube should contain Age of the customer also. For remodeling of InfoCube with an extra InfoObject for age, first create an InfoObject ZCUST_AGE and start Remodeling process for cube as follows. The new InfoObject ZCUST_AGE added to the cube will be filled by the remodeling rule which will calculate the values based on the values of ZCUST_DOB for each data record.

Continue reading “How to do Remodeling of Infocube using customer exit option”

ABAP in BW Data load Processes

Learn step by step approach of writing start routine, field routine and end routine in BW transformations.

Learn about ABAP routine filters in DTP and info packages and use of OLAP variables as Filters.

Access the ebook on Amazon at amazingly low prices.

 

BW Development Standards

The ebook details on Standards and Guidelines for BW implementation projects.

This ebook includes following topics which are very helpful for a BW Developer-

BW Development Standards Part 1: Architecture – BW System architecture, generic guidelines

BW Development Standards Part 2: LSA – LSA and LSA++ Differences, Referential Integrity, Data Acquisition layer, Business Transformation Layer and Reporting Layer

BW Development Standards Part 3: Data Modeling in Multiproviders and Infocubes – Fact table design, master data design, navigational attributes, modeling guidelines for attributes and hierarchies, design choices and their performance effects

BW Development Standards Part 4: Master data modeling – Options for modeling attributes

BW Development Standards Part 5: Transports – General Transport guidelines, object grouping and sequencing, collecting objects, changing and transporting Infoproviders, handling transport errors
BW Development Standards Part 6: BW Accelerator (BWA) – How BIA effects query processing, BI accelerator standards, adding new data to BIA index via process chain, Implications to InfoCube Management of Using the BI Accelerator

BW Development Standards Part 7: Reporting Guidelines – Querying, Report Template, Report Elements (SAP Business Explorer Elements), Reporting Authorizations

SAP BW Front­End Usage Standards and Guidelines – Chart Designer in Web App Designer, Nested Web Templates (Web Template Web Item), Adhoc Query Designer, Mass Maintenance of Web Templates

BW Development Standards Part 8: Data Extraction Technology

BW Development Standards Part 9: Process chain Standards and Guidelines

BW Development Standards Part 10: Flat File Management Guidelines

Designing and Building Secondary Indexes on DataStore Objects

BW Data Retention / Archival and Space Management Guidelines

SAP BW Back-End Usage Standards and Guidelines – Write ­Optimized DataStore Objects

SAP BI Business Content

Get in Amazon at amazingly low prices.

How to write BW Customer exit to enhance BEx variables

Here I will site an example of how to enhance a BEx variable using BW customer exit.

More details and insightful examples can be accessed in my ebook BEx variable enhancement by Customer Exit.

Display only two years of data in the BEx query

Scenario: Displaying only two years data in the BEx query based on the system date. The BEx query is based on a cube having 5 years of data.

Method:

Create a variable for calday or any time characteristic present in the cube.

I am taking 0calday as an example. SAP provides standard variables also to serve the same purpose. Here I will create a customer exit variable to illustrate the method.

Let the variable name is VAR2

This variable should be Interval value and mandatory.

There is no user input required when the query is accessed. Hence the BEx variable should not be “Ready for Input”.

Based on the system date, an Interval of two years will be calculated. For example, if system date is 24th Feb, 2017, the BEx query should display 2016 and 2017 data.

Drag and drop this variable in the filter section of the query.

Save the query.

Now go to the CMOD transaction and select your project. The project is generally provided by the client and should not be created by the developer. Click Display.

Click on the “components” button and then double click on the Function exit EXIT_SAPLRRS0_001

Double click on Include file name to go into the coding area.

Write the following code: Continue reading “How to write BW Customer exit to enhance BEx variables”

Qlikview not able to fetch all data from Multiprovider

There is a scenario which I encountered recently in my project where Qlikview was not able to see complete data from the Multiprovider from SAP BW.

The Multiprovider consisted of few standard DSOs with the setting : “SID generation during Activation” and “Set Quality Status to OK automatically” checkbox checked. Thus, even though all the settings are in place, the Qlik was not able to see all the data in the raw layer.

Continue reading “Qlikview not able to fetch all data from Multiprovider”

Issue: Error in generating export datasource / DSO cannot be activated

After system copy of Production to development system, there are many issues related to Basis team. One of the issues is DSO not getting activated and throwing error while creating new ones or activating the already existing ones.

If this happens, contact basis team as it is a source system RFC issue. This happened in our case. You might get the same error in many other scenarios but here I am discussing the error due to source system RFC issue.

Continue reading “Issue: Error in generating export datasource / DSO cannot be activated”

How2BW series ebooks

How2BW series ebooks are unique in their own way, as these contain crisp information needed for a BW Developer rather than being like long boring textbooks.

These books have illustrative examples along with screen shots and code snippets. You can go through the samples and see the table of contents for getting an insight of the content it contains.

Write an email to how2bw@gmail.com for giving any feedback, suggestions or if you have any questions.

SAP BW Development Standards

BEx Variable Enhancement by Customer Exit

ABAP in SAP BW Data Load Processes

Data Source Enhancement in SAP BW

SAP BODS Step by Step

How to derive fiscal period from calday in transformation

In many scenarios, client business has a different fiscal year than the standard calendar year (Jan to Dec)

For example, let client XYZ has a July to June fiscal year. This will be saved as fiscal year variant in the table T009 in the system-

fv

Here H1 is the fiscal year variant which takes the year as July to June.

Now suppose we are loading calday from source to target. Source does not have fiscal period but target is having fiscal period.

Continue reading “How to derive fiscal period from calday in transformation”