An export datasource is created when you want to use an info provider to load data to another targets which may reside in the same system or different system. An export datasource is created by default for a DSO. But its not the case for cubes. Below I will discuss one such scenario where I created and transported an export datasource.
You want to load data from cube in one system to a cube in another system. Let’s say that the source system is a SAP BW system with id SRD and target system is another BW system with system id TGD
SRD – SRT – SRP (Source system landscape)
TGD – TGT – TGP (Target system landscape)
Now there is a cube in SRD system which has data. This data needs to be get loaded to a cube in TGD system based on certain filters and conditions. And this has to finally move to the production systems (SRP and TGP)
The way to do this is first to request for a TR (transport request) in both SRD and TGD systems.
Continue reading “How to transport an Export Datasource”
Sometimes while transporting changes from Dev to Quality system or from Quality to Production system, the TR fails with RC 12 error. This is a critical error which does not depend on the contents of the TR. There may be many scenarios leading to this error, I have mentioned one of them in my earlier post, this post is about one more such cases where I encountered this error-
Root Cause Analysis-
In this case, there was table space issue in the quality system and hence while transporting the changes, incomplete objects were transported resulting in a dump in the quality system and TR failing with RC=12 error-
Below is the screenshot of the error that we got in the TR-
Below is the screen shot of the dump which we were getting in the quality system-
We asked basis team to check the tablespace in the quality system. They extended the tablespace of the table mentioned in the error log/ short dump. The TR was then moved successfully.
Hope this helps..
Recently I came across a scenario where I was not able to delete an inactive transformation while doing development.
I created dso and loaded the data. Then I observed that the dso should have different infoobjects. In order to correct the dso, I deleted the data first. Then I added the new info objects and activated the dso.
The dso was activated successfully. However, the transformation and dtp became inactive. I deleted the dtp successfully.
I went to edit the transformation and it showed warnings like – rule is invalid. I pressed continue and after couple of warnings, I got a dump as shown below- Continue reading “Transformation not getting deleted in RSA1”
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”
The issue is generally encountered when a query is executed in SAP BW. The query throws this error and does not display any data.
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”
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”
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”
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-
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”
The flat file loaded to BW must be in csv format. If the file has calendar day in the format MM/DD/YYYY or MM.DD.YYYY or DD/MM/YYYY or DD.MM.YYYY, the file gets loaded but PSA shows the incorrect date as
YY.YY.MMDD or something like that.
To ensure that the date is correctly loaded to BW, we need to make some settings in the flat file data source to handle the date formats entered by the user in the file.
Continue reading “How to load the csv file having date in MM/DD/YYYY format”
The sales order status should appear correctly in the BI reports after the daily refresh.
Otherwise the order qty will appear for example under both open and billed and the total order qty will hence show doubled in the sales report.Or, it may happen that the processed orders are not shown in the report.
You will encounter many tickets in SAP BW relating to order status issues. Mostly the tickets will be high priority (either P1 or P2)
In my experience, I have encountered a scenario where order status is a time independent navigational attribute of sales document.
Thus order status was a part of sales order master data.
Technically, status was residing in ‘X’ table of the info object sales order in the back-end BW database.
The business scenario was like below-
- There was a process chain updating the master data of the sales order and rolling these values to BW accelerator.
- Then, the delivery and billing transaction process chains were running. This transaction data was also loaded to BW accelerator.
- When the BI reports were run, the order status shown was not correct or the processed orders were not shown at all in the report.
Continue reading “Sales Order Status not updating in BW system with BWA”