jump to navigation

Checklist for Developing BI Objects February 10, 2012

Posted by Ajay in SAP BW.
1 comment so far

 Checklist for Developing BI Objects

What you need to check…

Developing the data model:

  Is the data model clear, integrated and consistent?
  Have you structured your system in a data warehouse layer architecture? Have you adhered to the recommendations for data modeling?

Developing InfoObjects:

  Are you planning to develop new characteristics?

Characteristics should be reusable, where possible. If you just need a new description for an existing characteristic, create the new characteristic as a reference to the existing characteristic.

  Do you need a special key figure to count the occurrences of a characteristic?

Using time characteristics:

  If you are using 0CALDAY in an InfoProvider, you should also include the higher-level time characteristics in the InfoProvider (for example, 0CALWEEK, 0CALMONTH, 0CALQUARTER, 0CALYEAR).
  If you are using 0FISCVARNT and 0CALDAY in an InfoProvider, you should also include 0FISCPER and 0FISCYEAR.

Developing InfoSources:

  Do the InfoSources only contain InfoObjects that are technically relevant or relevant for analysis and reporting?

Developing InfoProviders:

  Are you using DataStore objects? You should use DataStore objects if you need the history or analysis of an individual record. InfoCubes, on the other hand, can be aggregated and therefore have better performance.
  Are you using InfoSets with time-dependent master data? In this case, you should not define queries with time intervals.
  Are you using MultiProviders? Make sure that all the characteristics you want to use in the query are contained in all the individual InfoProviders.

Defining the load process:

  Have you defined transformation rules so that master data can be read? With reverse postings for delta-enabled DataSources, note that master data should not be read in the transformation rule for an InfoCube. The system can only process reverse postings upon reading master data correctly in the transformation rules for a DataStore object.
  Are you using process chains? You should use process chains to perform each load and further processing process.




Attribute Change run February 7, 2012

Posted by Ajay in SAP BW.
add a comment

1. Goto SE37 –> Run RSDDS_AGGR_MOD_STATE_GET > If I_DIFF* value / has any entries, your Attribute Change run was not successful.

2. Check if there’s any entries. If so, goto SE37 > RSDDS_AGGR_MOD_CLOSE & clear collision

3 Goto SE38 > Run RSDDS_AGGREGATES_MAINTAIN > Give IOB name (CIO infoobject not Nav) > Run the change run.

Protected: SAP BW STEP BY STEP February 7, 2012

Posted by Ajay in SAP BW.
Enter your password to view comments.

This content is password protected. To view it please enter your password below:

Data type and length of field in DB system ORA have been changed January 27, 2012

Posted by Ajay in SAP BW.
add a comment

SAP BW error : Data type and length of field ‘XXXX’ in DB system ‘XXXXXXX ORA have been changed.

The ods is getting data from Oracle.

I found out that data type for the column has been changed in oracle from varchar2(120 byte) to varchar2(120 char).

change the column in Oracle : CAST(USER_filed AS VARCHAR2(120)) .

Now data load is successful.

Bex transport request is not available or not suitable. November 14, 2011

Posted by Ajay in SAP BW.
add a comment

Refer to : http://forums.sdn.sap.com/thread.jspa?messageID=10021347#10021347

Refer to SAP Help: http://help.sap.com/saphelp_nw04s/helpdata/en/38/5ee7377a98c17fe10000009b38f842/frameset.htm