Error: Source RSDS DS_CA_CLIFID DBW_150 does not exist

Double check, the whether datasource is ISFS or RSDS.

If it is ISFS (3.x), (u can see a small 'Square' infront of datasource technical name), then also check in DEV.

To make it RSDS (7.0)... In dev system (RSA1--> Modeling --> DataSources --> BI --> BI logical System) ... right lick datasource --> migrate ... 'with export' ... and transport this to target system.

http://help.sap.com/saphelp_nw04s/helpdata/EN/43/5fc0680a876b7de10000000a422035/content

How to Delete the DTP in yellow status

Change the request to RED and delete it.
still if same problem exists ...
you can run the following program in SE38:
RSBKDTPDELETE
Just enter the technical name of the DTP and execute.

 There won't be any feedback but when you go back to RSA1 and refresh it won't be there.  This deletes the DTP not the request.

When this request is in yellow status and not able to change / delete the request, its actually in a pseudo status and it is a bug in the program. This request sits in table RSBKREQUEST with processing type as 5 in data elements USTATE, TSTATE and this 5 is actually "Active" status which is obviously wrong.

All we need is, ask the basis person to change the status to 3 in both these data elements and then it allows to reload the delta. Once the delta is successfully loaded, you can delete the previous bad request even though it is still in yellow. Once the request is deleted, the request status gets updated as "4" in table RSBKREQUEST.

Delete the error request when we cannot delete the request in Manage “ in DSO

By HP Pampana

When we get an error requests while loading the data into DSO. Usually we delete the error request in DSO manage screen and again we repeat the load. Some times,  it is not allowed to delete the request in the DSO manage screen.

Below are the steps to delete the Error Request :
To delete the request first we have to delete the request from the following tables:
RSICCONT, RSMONICP, RSODSACTUPDTYPE, RSODACTREQ.

Goto SE16 Transaction:  Provide the Table Name
Copy the Error Request number  from the manage screen of the DSO  and Proivide for “RNR” field and Execute.  Now delete the logs of the request from the table .Repeat the procedure for the remaining tables.

Once you delete the logs from the tables for that particular request and  now you can  delete the request from the DSO .

How to Debug a Field Routine

Goto table rsupdinfo, enter the name of your InfoProvider in the InfoCube column( example the name of the DSO is ZSTCDelvr) then copy the value of the field UPDATE PROGRAM, goto transaction SE38 type GP + value of the field update program (example the value of the update program is 403KECEKTAH39XDX6XCWW816U, type GP403KECEKTAH39XDX6XCWW816U in SE38) execute and you can access the routine and place breakpoints here (search the field with routine) instead of manually placing it in the routine

then

> Right Click in the InfoProvider then select a record

> Click Monitor

> Details -> Processing -> Data Package and Click

> Simulate Update

Load from Infoprovider by Transformation - Source: Query

If you mark "query as infoprovider" in RSRT query properties, you can use it as infoprovider.

Please see the following link for restrictions: http://help.sap.com/saphelp_nw73/helpdata/en/4b/c347cd494650e9e10000000a15822b/frameset.htm

Issue: Navigation Attribute not displaying in Report

Solution:

Run this program

RSDDTREX_SINGLE_TABLE_INDEXRSDDTREX_SINGLE_TABLE_INDEX and enter the SID table.  Execute and try executing the report again.

SID Generation Options in DSO

If you are on BW 7.3x you have 3 options ...

Create SID's

1) During reporting  - if you select this option in future if you build any reports on top of this DSO at the time of reporting SIDs will be generated

2) During Activation - this setting is what u have for Standard DSO

3) Never Create SIDs - this will never create SIDs.

How to remove ‘*’ from Bex Report.

Go to SPRO-->SAP Netweaver-->Business Intelligence-->Settings for Reporting and Anlysis-->General settings-->Presenting the numeric value in the Business Explorer-->For mixed values, remove * and keep it blank and save it Or Tcode RSCUSTV4.

 

Early delta Intailization

With this option data can be written to the delta queue during an initialization request.   It avoids the downtime required when you initialize your LO extractors - it creates a delta queue for taking in new records while the init is being carried out instead of creating the delta queue after the init is successful. This option is not able with all the DataSources. 

Go to SE16 --> table name as ROOSOURCE

In the next screen give the data source name and execute.  If field ZDD_ABLE in the result has value X, then data supports for early delta initialization.  If it has space, then it doesn't support.

Steps for Early delta Initialization

1.Initialize Early delta in the BI system.

2. Go and fill setup tables

3. Do a full load to BI

4. Run delta job in R/3 (LBWE)

5. Run delta job in BI Info package