SAP Resources

Below are Common SAP BASIS Administation tasks and transaction codes for them.

Using the transaction code CTBW_META we can easily create rquired infoobjects, transfer rules, infosources all in one go for a given datasource. This is usefull while creating custom generic extractors on with not common fields. It saves us time and effort to be spent on creating each indivitual infoobject manually. Below are step by step instructions with screenshots on using this transaction code. 

We need to enhance SAP standard or custom extractors extractors when the required fields are not available in the standard datasource. Datasouces (Extractors) can be enhanced using two methods.

1. User Exit
2. BADI

In user exist method you right the logic for extracting new fields in an exit function module. This approach has some drawbacks like transport dependency, messier code etc. This is the old approach. SAP has recently (couple of years ago?) introduced BADIs to alleviate the drawbacks of user exits. Using BADIs will allow developers to write object oriented code for extractor logic. SAP recommends BADIs over user exits. 

In SAP BW 7.3 we have a new wizard to migrate entire data flow from 3.X to 7.X. Prior to BW 7.3 we have to migrate each object seperately. In 7.3 we can migrate entire dataflow to 7.0, the wizard also modifies the process chain to 7.0 flow. (i.e it adds the DTPs automatically to the process chain). 

Below are step by step instructions to create BW index on an infocube.

1. Go to transaction code RSDDV (Check out BWA transaction codes)

2. Select the infocube (enter the cube into the text field at the bottom if you don't find the cube in th elist) and click on create 'BIA Index' as shown below.