Introduction

Many of our SAP BI/BW Consultants may not have OSS Id to browse SAP Notes at Market place. The following steps will show you How to download Notes without OSS Id..

Step 1: Goto t-code SNOTE in Dev system, you will get the screen like below

Step 2 : Click on Goto -->Download SAP Note

Step 3 : Enter the Note No. and Press Execute

Step 4 : At times, You may get Error in RFC connection. You can ignore this message and try again

Step 5 : Your SAP Note will be downloaded and available under SAP Notes-->New. You can refer the screen shot

These simple steps will make you to get any SAP Notes

Standardization is a key aspect of SAP BW Layered, Scalable Architecture (LSA), SAP’s best practice in Enterprise Data Warehousing. One of the ways to realize standardization in the data staging process is developing generic, reusable ABAP building blocks with a comprehensive interface.

From an Enterprise Data Warehousing perspective, the process of Data Unification can be classified as a modeling pattern. The Data Unification Services' ABAP building block and central control tables are designed to standardize and facilitate this process.

In this blog I will discuss Data Unification Services, the concept behind it and how to use it in the transformation.

I developed a working version of the Data Unification Services which I am going to share via a document. It will cover all details on creating the ABAP Objects classes, including the source code and all necessary ABAP Workbench objects.

Conceptual Overview

Data Unification in an LSA context is all about supplementing data records with administrative characteristics. Usually it concerns the following characteristics:

• Data Domain;
• Organizational Unit;
• Request ID;
• Timestamp;
• Origin.

Data Domain is related to domain partitioning or strategic partitioning and is applicable to transactional data flows. Please refer to my blogs Pattern-based Partitioning using the SPO BAdI - Part 1: Introduction and Pattern-based Partitioning using the SPO BAdI - Part 4: Use Cases for more information.

Domain partitioning is not always applicable: Data Acquisition Layer, Corporate Memory Layer and master data flows in general. In these cases it's transparent to assign data to domain 'X' (cross-domain and domainless).

Data Unification Services is positioned in the Harmonization & Quality Layer.

Figure 1: Positioning in LSA (source: SAP AG)

The following figure shows an example of an LSA compliant transactional data flow.

Figure 2: Data Unification Services in the Data Flow

The yellow callout indicates where Data Unification Services is implemented. The transformation is positioned between the Data Acquisition Layer outbound InfoSource and the Harmonization Layer Pass-thru DSO.

For other data flows it is slightly different. In master data flows the transformation is positioned between the Data Acquisition Layer outbound InfoSource and the Harmonization Layer intermediate InfoSource. In Corporate Memory flows the transformation is positioned between the Data Acquisition Layer outbound InfoSource and the Corporate Memory DSO.

Note that in all cases this transformation is exclusively used for Data Unification Services.

Control Tables

For transactional data flows the basic rule is that domain partitioning is applied. Data Unification Services needs help to be able to determine Domain and Organizational Unit automatically. Therefore we have to introduce 3 control tables.

Exclusively for transactional DataSources the following control tables have to be maintained:

• YBWUNISRC - Domain Driving Source Field DataSource;
• YBWUNIVAL - Value Assignments;
• YBWUNIREF - Reference Domain Driving Characteristic.

Table YBWUNISRC is always mandatory to be maintained for every new transactional DataSource. It is used to store the domain driving source field of the DataSource and the corresponding InfoObject.

Figure 3: Control Table - Domain Driving Source Field DataSource

Table YBWUNIVAL is used to store the value assignments. It has to be maintained less frequently since already existing value assignments can be reused. E.g. InfoObject Company Code and its characteristic values are already maintained. Every next DataSource can reuse these value assignments, there is no need to maintain them more than once. There might be a future need to maintain the entries if new Company Codes are introduced.

Figure 4: Control Table - Value Assignments

In some cases you might encounter that multiple InfoObjects are used for the same entity. In such cases it must be avoided that the value assignments are entered more than once. That is why the reference domain driving characteristic functionality was introduced. Table YBWUNIREF is used for this purpose.

Figure 5: Control Table - Reference Domain Driving Characteristic

Using Data Unification Services

Prerequisite for using Data Unification Services is the presence of the administrative characteristics in the target structure of the transformation. I.e. you have to add these characteristics to the DSO or InfoSource (depending on the data flow). The example below shows a DSO where you have to add the characteristics to the Data Fields section.

Figure 6: Adding Administrative Characteristics to DSO

The Data Unification Services building block is realized as an ABAP Objects class. One of the following public methods has to be called in the transformation (end routine or expert routine):

• EXECUTE_END - Execute Transformation End Routine;
• EXECUTE_END_X - Execute Transformation End Routine (Only Domain 'X');
• EXECUTE_EXPERT - Execute Transformation Expert Routine;
• EXECUTE_EXPERT_X - Execute Transformation Expert Routine (Only Domain 'X').

You can see in the screenshot below an example of the limited source code to be entered here.

Figure 7: Example of Data Unification Services in the Transformation

The source code can easily be inserted by using the appropriate ABAP Pattern. Click on push button Pattern, choose option Other Pattern and select the appropriate pattern in line with the type of routine (end routine or expert routine) and domain.

Figure 8: Inserting the Data Unification ABAP Pattern

The following ABAP Patterns are available:

• YBW_END_UNI - Execute Transformation End Routine;
• YBW_END_UNI_X - Execute Transformation End Routine (Only Domain 'X');
• YBW_EXPERT_UNI - Execute Transformation Expert Routine;
• YBW_EXPERT_UNI_X - Execute Transformation Expert Routine (Only Domain 'X').

All Data Unification functionality is provided by the class. The source package and/or result package are processed dynamically. The relevant information is fetched from the control tables. Any exceptions are handled appropriately: they terminate the process in a controlled way and fill the monitor log with information on the errors.

Conclusion

From an Enterprise Data Warehousing perspective, the process of Data Unification can be classified as a modeling pattern. The Data Unification Services' ABAP building block and central control tables are designed to standardize and facilitate this process.

In this blog we discussed Data Unification Services, the concept behind it and how to use it in the transformation.

I have seen a lot of posts asking for standard tables behind BW objects. I hope to clarify this with this blog. Actually an object is transported between two BW system by transporting the table entries of standard table associated with the object. Let me show you how to see the standard table behind a DSO.

1) Collect any DSO in a transport request

2) Double click on the TR to get the below screen

3) Double click on the line corresponding to the DSO or Right click on the line and press display . You will get the list of tables associated with DSO.

Thus you can get all the tables associated with the DSO. You can see the description of the table in SE11 to know what is stored in these tables and find the table you are looking for.

You can see all the tables associated with any BW object (Cube,infoobject, Multiprovider, transformation etc) by following the above technique.

Hello everyone,

I am here going to demonstrate how to use Data Mining Model of SAP BW to operate Assocation Analysis.

In order to complete this tutorial, data source CSV file which contains relevant data is needed for data extraction. Also you can create your own like this:

   Access the Data Mining Workbench.  Use TCODE RSDMWB or Double Click Data Mining Model

  The Data Mining Workbench screen appears as follows:

The workbench includes a list of Data Mining methods that can be used to analyze data, commonly stored in business applications.These methods include classification (decision trees), clustering, association analysis, approximation, and further analyses techniques such as ABC classification.

Phase 1  --- Creating an Association Model

1. Expand and Right Click Create Model,

The Create Model dialog screen appears as follows:

2. Name Model and Description, select Radio button: Manul, and accept the entry.

The Create Model XXX screen will appear as follows:

You now need to select the fields (InfoObjects) needed for your model. The fields selected will need to match those identified in the data source file shoppingdataset.csv.

3. Click    the icon to insert a row for the first InfoObject (Material).

Notice that properties (data type and length) of the InfoObject are automatically populated. The Content Type option defines how each field is to be treated within the model. There are three possible options; transaction, item and transaction weight.

4. Click    the icon  in each specific field to display all the available options and select corresponding option.

 
After completing this step the field assignment for the Association Model show appear as follows;

5. Click  Parameters  tab to set the following parameters.

Support can be used to help determine how useful a product association rule is.

Confidence (or predictability) measures how dependent a particular item.

Lift helps to identify and eliminate rules that are only generated because some of the items naturally occur very frequently, although there is no actual association between the set of leading and depending items.

The Association Model uses Leading and Dependent items. If a leading item has been purchased, what is the likelihood the following dependent items is also purchased.  If a customer purchases milk (leading item) what is the likelihood they will also purchase bread (dependent item). The relationship between leading and dependent items is not limited to one to one. The parameter Leading Depth can be set to identify the number of products to be considered together as leading items and the parameter Dependent Depth can be used to set the number of dependent items to be considered in the model’s analysis.

                   Leading Items                        Dependent Items

                   milk                                           bread

                   milk, spread                            bread

                   milk                                           bread,spread

6. Put value in the Maximum Leading Depth field, Tand in the Maximum Dependent Depth field.

7. Click return to the previous screen.

8. Click to save your model.

A message appears in the Status Bar.

9. Click to activate the model.  A log screen will appear indicating the status of each step of the model building proces

10. Click  to close this screen. Now you have successfully created Association Model

Next, I am going to use SAP GUI and run Phase 2 & 3 --- Training and Execution of the Assocation Model :

Thanks, I hope you enjoy it ! 

This guide is sort of a trick..:D

This will teach youhow to edit a transport requestthat you have already transported toQASorPROD..For example, you already seek for an approval of the TRANSPORT REQUEST that you have created..After transporting all the Infoproviders and Infoobjects that you have created, you noticed that you missed to include a single INFOOBJECT on your request..Hence, you will again seek for an approval of another transport request for that one (1) infoobject as well as re-transport all the infoproviders and infoobjects that you have already transported..

Using this trick, you need not to seek for approval for another transport request since you will be using the sameTransport Request Number..You will just edit your first transport and add that single infoobject that you have missed..

Here is the trick guyz!

1. Go to SE10 or STMS and copy the transport request number that you want to edit.

2. Go to SE38 and run the program RDDIT076. Click the EXECUTE button (near the ACTIVATE button) or press F8 to RUN.

3. Paste the Transport Request Number (from STEP 1) and click the EXECUTE button.

4. Double click the first row and edit its STATUS; change it from R to D. Click the SAVE button afterwards.

5. Do STEP 4 on the second row. You will have the screen below.

6. Go to SE10 and double click the top row of your transport request number.

7. DELETE all ROWS.

8. Go to PROPERTIES tab. Delete all rows in the ATTRIBUTE column by clicking each row then click the DELETE ATTRIBUTE button.

9. Click SAVE.

10. Include now the objects that you want to add in your existing request by clicking the OWN REQUESTS button and locate your edited transport request.

By the way, you can also use this trick if you already released the your transport request and you forgot something to include in that transport request.

Hope this will help you guyz!

Hi Users,
I wanted to share my experience which i faced recently after upgrading our system landscape to BW 7.3 from BI 7.0.

We have 3.5 datasources which are serving as targets for the 3.5 datasources in other teams systems. These are master data loadings.
The sytem landscape for those(source) teams is in BW 3.5 version.

When those teams were executing the process chains after our upgrade to BW 7.3, the loads were failing.
The error message was not much helpful. It was error code 2 - source file must be open in source system.

The source teams tried to replicate the datasources. But the moment they click on replicate datasources, the datasources would just dissapear.
This was a strange behaviour i have seen. We concluded that this would be due to  BW 3.5 and BW 7.3 versions incompatibity.

I tried to google, scn etc. but could not find much info on this behaviour.

We checked the dataflows in both the target and source systems and it was active.

Then we tried to "Activate the transfer structure for the info sources which had issue using the Program “RS_TRANSTRU_ACTIVATE_ALL”.and executed the loads
and it was succesful.

Hope this error blog gets helpful for users.

Regards
Syed Zabiullah

Armed with only ABAP development experience and hardly any BW or BPC Script Logic experience I had to consider where to start?

...SCN..of course

With my first search I found this document which was really helpful in explaining how I can use the exit framework which allows customers to use ABAP within BPC Script Logic by calling a BADI within the Script Logic.

After creating the implementation as required:

The document explained to me how to implement the BADI but obviously did not have the logic to call the BW planning sequence.

In order to do this I had to implement the BADI UJ_CUSTOM_LOGIC and wrote the code in the EXECUTE method of the implementing Class:

Logic to call the BW planning sequence

METHOD if_uj_custom_logic~execute.  DATA: ls_param             TYPE LINE OF ujk_t_script_logic_hashtable,             lv_plan_seq         TYPE rspls_seqnm,             lt_bapiret2           TYPE TABLE OF bapiret2,             lcl_area_handle    TYPE REF TO zcl_bwip_shared_area,             lcl_memory          TYPE REF TO zcl_bwip_shared_memory.  READ TABLE it_param INTO ls_param WITH TABLE KEY hashkey = 'ZPLAN_SEQ'.  IF sy-subrc EQ 0.    TRY.        CALL METHOD zcl_bwip_shared_area=>attach_for_write          RECEIVING            handle = lcl_area_handle.      CATCH cx_shm_exclusive_lock_active .      CATCH cx_shm_version_limit_exceeded .      CATCH cx_shm_change_lock_active .      CATCH cx_shm_parameter_error .      CATCH cx_shm_pending_lock_removed .    ENDTRY.    TRY.        CREATE OBJECT lcl_memory AREA HANDLE lcl_area_handle.        lcl_area_handle->set_root( lcl_memory ).        lcl_memory->set_t_param( it_param ).        lcl_area_handle->detach_commit( ).      CATCH cx_shm_error.    ENDTRY.    lv_plan_seq = ls_param-hashvalue.    CALL FUNCTION 'RSPLAPI_PLSEQ_EXECUTE'      EXPORTING        i_sequence       = lv_plan_seq
*     IMPORTING
*       E_SUBRC          =      TABLES        e_t_return       = lt_bapiret2              .  ENDIF.

ENDMETHOD.

Being the lazy developer that I am, I'm always looking for ways to make life easier for me.

I did not want to keep going to BPC to test the call to the BADI by the Script Logic, so I looked for an easier way to do my testing.

I came across another useful post in SCN which explained the use of Tx UJKT.

I then used Tx UJKT to enter and execute the following Script Logic.

*START_BADI ZPLAN_SEQ 
 ZPLAN_SEQ = /CPMB/ZGL01
ZGLPORT = $ZGLPORT$
 ZVERSION = $ZVERSION$
*END_BADI

In the above Script Logic I call the BADI using the filter 'ZPLAN_SEQ'.

I am also passing 3 parameters through to the BADI. NB: The BADI can accept any number of parameters.

The logic above in the EXECUTE method caters for calling any planning sequence with any number of parameters.

I am using a shared memory object which was available since NetWeaver 6.40.

These parameters however must still be read by the planning sequence being called.

When the planning sequence is created these parameters must be created as SAP Exit parameters.

This will then invoke the standard SAP exit for the parameter (EXIT_SAPLRRS0_001):

I then added the following code to read the saved parameters in the SAP exit:

   data: lt_param TYPE UJK_T_SCRIPT_LOGIC_HASHTABLE,       ls_param type LINE OF UJK_T_SCRIPT_LOGIC_HASHTABLE,       lcl_area_handle TYPE REF TO zcl_bwip_shared_area,       lcl_memory      TYPE REF TO zcl_bwip_shared_memory.    TRY.        CALL METHOD zcl_bwip_shared_area=>attach_for_read          RECEIVING            handle = lcl_area_handle.      CATCH cx_shm_exclusive_lock_active .      CATCH cx_shm_version_limit_exceeded .      CATCH cx_shm_change_lock_active .      CATCH cx_shm_parameter_error .      CATCH cx_shm_pending_lock_removed .    ENDTRY.    TRY.        lt_param = lcl_area_handle->root->get_t_param( ).        lcl_area_handle->detach( ).      CATCH cx_shm_error.    ENDTRY.    READ TABLE lt_param into ls_param WITH TABLE KEY hashkey = I_VNAM.    if sy-SUBRC eq 0 and i_step = 1.      wa_range-sign = 'I'.      wa_range-opt  = 'EQ'.      wa_range-low  = ls_param-HASHVALUE.      wa_range-high  = ls_param-HASHVALUE.      append wa_range to e_t_range.    endif.

This is how I managed to pass parameters from Script Logic to BADI and then execute Planning Sequence with the parameters entered for Script Logic.

Business Requirement

Move file on application server (T coade AL11) from one folder to another folder

Implementation Logic in BW

This can be achieved in BW in three different ways:

1. Using Trasnfer dataset statement
2. Using external operating system commands
3. Using function module ‘ARCHIVFILE_SERVER_TO_SERVER’

Logic

Case 1: Using Transfer Dataset statement

ABAP Code

PARAMETERS: PS_dir(50)  TYPE C ,
                            pa_dir(50)  TYPE c

                          PF_name(50) TYPE C OBLIGATORY LOWER CASE.

DATA: L_OLDFILE type localfile,
            L_NEWFILE type localfile,

                L_NEWLINE(240) type c,

Concatenate  ps_dir pf_ name  into l_oldfile.

Concatenate pa_dir pf_name into l_newfile.

OPEN DATASET  l_oldfile FOR INPUT IN BINARY MODE.

    If sy-subrc = 0.

                OPEN DATASET l_newfile FOR OUTPUT IN BINARY MODE.

                If sy-subrc = 0.

              DO.
                                READ DATASET l_oldfile INTO l_newline.
                                IF sy-subrc EQ 0.
                                              TRANSFER l_newline  TO l_newfile.
                                ELSE.
                                              if l_newline is not initial.
                                                      TRANSFER l_newline TO l_newfile.
                                              endif.
                                              EXIT.
                                ENDIF.
                ENDDO.

                Endif.

                CLOSE DATASET l_newfile.

          Else.

                Message ‘Can not open source file’ type ‘E’.

          Endif.

CLOSE DATASET l_oldfile.

DELETE DATASET  l_oldfile.

Advantages of this approach:

                Simple Process which transfers data in set of 240 characters

Disadvantages

                Data is handled while moving file

                For large files program will take more time

Case 2: Using External Operating System Command

ABAP Code

PARAMETERS: p_src TYPE sapb-sappfad,
                          p_tgt TYPE sapb-sappfad.

DATA: l_para TYPE btcxpgpar,
            l_stat(1)  TYPE c.
CONCATENATE p_src p_tgt INTO l_para SEPARATED BY space.

CALL FUNCTION 'SXPG_COMMAND_EXECUTE'
  EXPORTING
    commandname                        = 'ZMV'
    additional_parameters              = l_para

IMPORTING
  status                              = l_stat
EXCEPTIONS
  no_permission                      = 1
  command_not_found                  = 2
  parameters_too_long                = 3
  security_risk                      = 4
  wrong_check_call_interface          = 5
  program_start_error                = 6
  program_termination_error          = 7
  x_error                            = 8
  parameter_expected                  = 9
  too_many_parameters                = 10
  illegal_command                    = 11
  wrong_asynchronous_parameters      = 12
  cant_enq_tbtco_entry                = 13
  jobcount_generation_error          = 14
  OTHERS                              = 15
          .IF sy-subrc <> 0.
  MESSAGE 'Error' TYPE 'E' DISPLAY LIKE 'I'.
ELSE.
  if l_stat = 'O'.
    message ‘File Archived successfully’ type 'I'.
  endif.
ENDIF.

Advantages :

o  No file data handling

o  Time taken is less as we using system command to move file

Disadvantages:

o  We need create Operating system command in T code SM49

Case 3: Using Function module ‘ARCHIVFILE_SERVER_TO_SERVER’

ABAP Code:

PARAMETERS: p_src TYPE sapb-sappfad,
            p_tgt TYPE sapb-sappfad.

CALL FUNCTION 'ARCHIVFILE_SERVER_TO_SERVER'
  EXPORTING
    sourcepath            = p_src
  targetpath            = p_tgt* IMPORTING*  LENGTH                =
EXCEPTIONS
  error_file            = 1
  no_authorization      = 2
  OTHERS                = 3
          .IF sy-subrc <> 0.
  WRITE : 'Error in archival', sy-subrc.
ELSE.
  WRITE 'File archived successfully'.
ENDIF.

Advantages:

o  Standard Function Module is used for file archival

Disadvantages

o  File names passed to Function Module should be logical paths to file

o  How to create logical path for file is given in below link

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60e86545-9940-2d10-9f89-eb5bce1f9228?QuickLink=index&overridelayout=true&47519518718715

Introduction

From SAP BI 7.0 onwards, in DTP we have an option for semantic groups.  We have different perception about Semantic Groups in DTP and its usage. Here I am summarizing specific usage of semantic group with examples.

Case 1. Calculation on group of records

Example: I would like to provide discount to each customer based on total sales value of Customer No, Country and Product category.

Discount should be assigned to each row i.e. for each product. I am having below sample records.

Discount Criteria based on Sales value as per grouping (Customer No + Country + Product Category)

Data Upload from PSA to Standard DSO.

DTP Package size is 5 Records.

End routine is calculating total sales which are used for discount calculation of each customer based on Sales value and assigning it to each product row.

Without Semantic Group Data Upload

Total sales value and Discount amount when data loaded without semantic group is as below

Here if you notice about Customer C001 having same country and product category but Total sale is assigned as 5000 and 1000 respectively.

In such case for Product P010, customer received only 5% discount where as actually he/she should get 10%.

Similar case is for Customer C003 and product P003.

This is because Data uploaded into 2 equal packages of 5 records each, first 5 records into 1st package and rest 5 records in 2nd package.

Since in First package 5 records are as below,

Total Sales Value is calculated as below

So Discount values for first 5 rows are stored into Target DSO as below

For next 5 rows as below

With Semantic Group Data Upload

Key fields are Customer no, Country and Product category

Total sales value and Discount amount when data loaded with semantic group are as below

In this case records will be grouped based on Semantic key definition and even if there are 2 packages each will have records as below.

Records in First package grouped based on are Customer No, Country and Product Category

Records in Second package

Due to this semantic grouping we have correct values for the Total Sales and our discount values are also calculated as expected.

Please note to accommodate records as per semantic group, package size will be automatically adjusted. Hence, it will not be constant through out the load.

Case 2. Error handling

Similarly if Error handling is enabled and error DTP is available, error handling functionality will work as below based on semantic group.

Without Semantic Group Data Upload

In case there is an error in the record having product no P001 then it will go into error stack and rest of the records will be uploaded. In such case for Product P010, total sales value will be 1000 and hence discount will be 5% i.e. 50$.

Even later if we will correct first record (P001) into error stack and upload it through error DTP, Discount value will not change for record P010.

With Semantic Group Data Upload

In case there is an error in the record having product no P001 then it will go into error stack along with record having product id P010 and rest of records will be

uploaded into target. It is due to semantic definition, so even one record is having error, both records are transferred into error stack to maintain semantic grouping.

In such case, when product P001 will be corrected into error stack and error DTP will run, it will upload both records with correct total sales and discount value.

Additional Note

Here I have used only 2 cases for illustration purpose. In real life there can be more use cases as per specific needs.

Please note above example is to explain the concept of semantic groups. There can also be other ways to achieve this calculation.

Hope it will help to get better insight about semantic groups into DTP for beginners.

Finally! We can use up to 250 characters in characteristic values and up to 1 333 in texts.

You not need methods like this (http://scn.sap.com/docs/DOC-11404) any more

See SAP Note 1823174 - BW7.40 Changes and customer-specific programs for details.

We can check theList of users who used particular query in RSSDDSTAT Table.

If you install BW statastics standard providers we can check the data in  0BWTC_C10 Multiporvider .if not we can check the data in RSSDDSTAT Table.

Below are the steps :

Go to Se16

Provide theTable name as RSDDSTAT

Provide the query Name and excute

It will display the users list who used the Particular query and displays the time stamp also.

Below are the steps to  activate the BW Statistics:

·         To activate statistics goto tcode RSA1à Tools à Settings for BI Stats

·         Set stats for Query- set stats for InfoProvider    

·         Set stats for Web Template- set stats for Workbook

Below are the some tables to check the statastics

RSDDSTATAGGR              Detail Table for Aggregate Setup

RSDDSTATAGGRDEF      Detail Table of Navigation for each InfoCube/Query

RSDDSTATSTEPTP:           Type of steps

BEX, BEX3, BRCS (broadcasting), EXTN (external read), JAVA, MDX

RSDDSTATHANDLTP:     combines Handle & Step type

Helps to identify where the time is being spent

RSDDSTATWHM:            Time it takes to do a load

RSDDSTATCOND              InfoCube Compression

RSDDSTATDELE                InfoCube Deletions

RSDDSTAT_WRITE           InfoCube Writes

RSDDSTATBCACT              Business Content Activation Statistics

RSDDSTATCOND               Data on Condensing Run InfoCube

RSDDSTATEXTRACT         Time of last delta load

I thought to give some basic transport steps. how we can transports from BW Dev - Bw Quality - BW prod.

Actually this part was taken care by basis team. If we know basic steps it will be good for us.

Here i am explained how we transport a Full DTP from dev to Quality and then to prod in parts wise..

After creating the DTP, all changes may be stored in local package. So we need to collect in custom package because objects which are in local packages are not transportable.

How to capture DTP in TR(transport request):

In bw we can use Transport connection to capture changes in TR or Directly we can capture changes in TR.

DTP Was in active status., double click on DTP, from menu Go to Object Directory Entry. like below

Go to change symbol, enter ZBW(custom - package which we have) save, package  was changed, continue, on next screen
it may ask TR, click on create icon(white symbol one), There enter description of your TR, continue, automatically one TR will generated. Continue, again save DTP and activate. Your TR have activated DTP.

Go to Tx – SE10, click on display button  or press F5, you will get below screen.

Enter your TR and continue. You will get below screen. My screen shows as released and target system was BQA. When
we see this first time, you will see modifiable(in place of released).

Now we need to release transport in BW dev. Here always first need to release task(XXXX0958) if you have multiple
below 0958, in any sequence you can release them after that only we need to release TR(XXXX0957).

How to release:

Select your task, ex: here XXXX0958(child) and click on transport bus symbol, like this way release task(s) and finally release TransportXXXX0957 (Parent). Refresh the screen. All requests which are under modifiable, after release will come under released as above scree showed. Against request you will see tick mark also after released.

You can check the transport logs(red mark on above pic), on the same screen, select your request and on tool bar you will see icon for transport logs, click on it and see, you may see its as success like below.

Now we released in BW Dev environment and next step we need to import in BW Quality. i will Continue on part 2.

http://scn.sap.com/community/data-warehousing/netweaver-bw/blog/2013/06/28/bw-requests-how-to-transport-and-import-part--2

Thanks for reading

RK

Continue..

http://scn.sap.com/community/data-warehousing/netweaver-bw/blog/2013/06/28/bw-requests-how-to-transport-and-import

How to import at Quality side:

Log into BW Quality server, Tx – STMS, After that Press F5 or select transport bus symbol as shown below.

On next screen you will see three  environments which are in landscape.

Now we need to import into BW quality so double click on BQA. We will get below screen.

If you use Tx – STMS_IMPORT, You will directly come into(see) below screen.

Its already existing system, so after refresh we won’t see our request, we need to go end of the page.

As shown above,click on last page icon. Its take you end of the page. Our bw dev TR released request visible at bottom most.

If any TR was released in bw dev and in quality not yet imported then you will see that TR also bottom page.

But against that you will see one symbol. Like below arrow mark in pic.

TR which was in block box not yet imported due to some issue.

After import of bw TR. Our request will move upper side and the TR which are not imported to quality(but released from bw dev)

will bottom most with that symbol.

After refresh we will see bottom most TR which are not yet imported with that graded symbol(orange) and arrow mark.

Import starts here:

Above screen we see two transport buses. But we need to choose 2^nd one which have little orange color one.

If we choose the transport(Import All Requests, its danger one) which was in red circle, it imports all TR from source.

We need to import latest one only, so choose Import Request(Ctrl+F11, green tick mark).

After clicking on Import request we will get below screen:

On Date tab, default its selected as immediate, that’s fine.

One Execution tab my default option was Asynchronous(you can go as default on your machine).

Provide target client as per your system.

Options Tab: you can select top 5 options as below:

After choose above 3 tab options, click on continue green tick mark, next you will get message box, like below:

Click on yes,  its starts importing, You will get STMS_IMPORT Screen with truck symbol against our TR.

Means our TR was importing in process.

Keep on refresh, after finish, truck symbol will gone and you will yellow symbol there and green symbol against our TR.

After the success, we can see the transport logs as shown(part 1). Same like this way we can import in to Production also.

If we are authorize to access  Tx – STMS.

Thanks for reading..........

RK

Introduction

Scenario 1 :

At times, we will be struck while activating requests in a DSO due to some incorrect request deletions in DSO. But these requests might still exists in some database tables like RSICCONT, RSODSACTREQ etc..

Scenario 2 :

Intialization requests would have been deleted from Infopackage-->Scheduler menu. But these requests would have been existing in RSSDLINIT, RSSELDONE, RSREQDONE tables etc..

Unless, we delete these bad requests from the above tables, we will not be able to move forward. The following procedure will help us to delete the requests from the back-end. I strongly advice you to follow this procedure in extreme situations only.

Step 1: Goto the DB table in SE16

Step 2: Enter the Request Num and press execute

Step 3: Sometimes we may not have authority to delete the table entries, delete options will be disabled like below

Step 4: Select the entry and click on Spectacles button and enter /H in the command prompt and press Enter twice

Step 5 :  You will get into debug screen  and observe Code = Show, right hand side screen will have no entries

Step 6 : Double click on Code like below, then you will see an entry in the right hand side.

Step 7 : Please double click on pencil button and type DELE

Step 8 : Click on save on top of debug screen and press F8, then you will get delete entry like below. Press on it to delete the entry.

Conclusion : You can make use this procedure to delete any DB table entries. You must have a debug access to do this. Please be careful while using this procedure. You can take up this procedure in extreme situations only.

Purpose

We face various issues while working on BI 7.0 systems. I have compiled some of the important SAP Notes to help us when required.

Purpose

This is continuation of my other blog about important SAP notes in BI 7.0.

What are Cube Aggregates?

  Definition

An aggregate is a materialized, summarized and condensed view of the data in an Info Cube. An aggregate maintain the dataset of an Info Cube redundantly and persistently.

• Summarized and Condensed view refers to the condensing of the fact table of an Info cube to an aggregate table.
• An aggregate table no longer contains certain characteristics of the Info cube and has been condensed across attributes.

When We Create Aggregate on Cube?

Basic purpose of using aggregates is to make data extraction faster.

When we access the data frequently for reporting and we have huge amount of data it takes more time retrieve. If a query is frequently used for reporting and we want performance enhancement then we use aggregates on data source (at Info Cube).

• Aggregation makes data condensed and summarized so you can access the data of an Info Cube quickly when reporting.
• New data is loaded at regular interval (a defined time) using logical data packages (requests) in an aggregate. After this transaction, the new data is available for rolling up in reporting.
• Aggregates are used when we often use navigational attributes in queries or we want aggregation up to specific hierarchy levels for characteristic hierarchies. Both time-dependent attributes and time-dependent hierarchies can be used in aggregates.
• Note:

1. To find our queries frequently used and taking more time we can check RSDDSTAT_OLAP table (TCODE SE11).
2. You can use Table RSDCUBE to determine the Info Cube assigned to the aggregate using aggregate id (6digit).

Prerequisites

• The Info Cube for which we are creating aggregate must be in active state and there should not be any aggregate with same set of attributes for that Info Cube. Every aggregate must be unique.
• If you have created aggregates for an Info Cube and entered data for them, the OLAP processor automatically accesses these aggregates. When navigating, the different results are consistent. The aggregate is transparent for the end user.
• If you want to use system propose aggregates, and then you must create at least one query for the selected Info Cube. The necessary aggregates can be proposed when you start the queries and navigate in them.

Steps to create Aggregate

• Go to TCODE RSA1 and select the InfoCube in which you want to create aggregate and select Maintain Aggregates option.

• When first time we create an aggregate for an Info Cube it asks for type of aggregate.

a. Generate proposals

• The system proposes suitable aggregates. The Specify Statistics Data Evaluation dialog box appears.
• Enter Run time, from date and to date details & Choose Next.
• This will bring you to the Maintain Aggregates screen .The system displays the proposed aggregates in the right area of the Aggregates screen. 

b. Create yourself

• This will bring you to the Maintain Aggregate screen.

• Note : Aggregates are always build on Characteristics not for key figures .

• Drag all characteristic you want to include in Aggregate to write side window pane. You can add characteristics one by one as well. Following screen will appear.

• If you will select later for activation of aggregate following screen will appear where you can give date and time according to your requirement.

• After activation aggregate will show you record available for aggregation ,summarized record count ,last roll up ,last used (in query) etc. details .

This screen will give you following information also:

• Hierarchy and hierarchy level fields are used for aggregates on hierarchies.
• Valuation column will show ‘–‘and ‘+’ sign:

1. The larger the number of minus signs, the worse is the evaluation of the aggregate, "-----" means: The aggregate can possibly be deleted.
2. The larger the number of plus signs, the better is the evaluation of the aggregate, "+++++" means: The aggregate could make a lot of sense.

• Records will tell about number of records in the filled aggregate (size of the aggregate).
• Records Summarized (mean value) will tell about number of records read from source in order to create a record in the aggregate. This shows quality of the aggregate. Large value show better compression (better quality) .If it is 1 the aggregate is a copy of the Info Cube and should be deleted.
• Usage shows how often has the aggregate been used for Reporting in queries?
• Last Used shows when was the aggregate last used for Reporting? If an aggregate has not been used for a long time, it should be deactivated or deleted.

In order to increase the load performance you can follow the below guidelines:

1. Delete indexes before loading. This will accelerate the loading process.
2. Consider increasing the data packet size
3. Un check or remove the Bex reporting check box if the DSO is not used for reporting
4. If you are using abap code in the routines then optimize the code. this will increase the load performance
5. Un check the SID generation check box
6. Write optimized DSO are recommended for large set of data records since there is no SID generation in case of write optimized DSO.This improves the performance during data load.

Steps before using an Aggregate

• To use an aggregate for an Info Cube when executing a query, we must first activate it and then fill it with data.
• To use an existing aggregate select the aggregate that you want to activate and choose Activate and Fill. The system will create an active version of the aggregate.
• Once the aggregate is active you must trigger the action to fill the aggregate with data.
• The active aggregate that is filled with data can be used for reporting. If the aggregate contains data that is to be evaluated by a query then the query data will automatically come from the aggregate.
• When we create a new aggregate and activate it initial filling of aggregate table is automatically done.

Rolling Up Data into an Aggregate

a. ROLL UP

• If new data packages or requests are loaded into the Info Cube, they are not immediately available for Reporting via an aggregate. To provide the aggregate with the new data from the Info Cube, we need to load the data into the aggregate tables at a time which we can set. This process is known as ROLL UP.

b. Steps of rolling up new requests

• In the Info Cube maintenance you can set how the data packages should be rolled up into the aggregate for each Info Cube.
• In the context menu of the required Info Cube select Manage. The Info Provider Administration window appears. In the Manage Data Targets screen select tab Rollup.

• Here from selection button you can set date and time of rollup.

• You can set an event after aggregation and also create a process to run the job periodically. Selective request can be aggregate by providing request id.
• Request can be rolled up based on no of days.

• After rollup you can see the check sign in manage tab. Selecting a request for rollup will also rollup all previous requests loaded before that but not the new one .

Levels of Aggregation

• Aggregation level indicates the degree of detail to which the data of the underlying Info cube is compressed and must be assigned to each component of an aggregate (characteristics, navigation attributes, hierarchies).

Aggregation level can be

          By default, the system aggregates according to the values of the selected objects:

• '*' All characteristic values
• 'H' Hierarchy level
• 'F' Fixed value

Thank you for reading this blog .Please add your comments .

Reference(s)

1. http://help.sap.com/saphelp_nw04/helpdata/en/7d/eb683cc5e8ca68e10000000a114084/frameset.htm
2. http://help.sap.com/saphelp_nw04/helpdata/en/80/1a6791e07211d2acb80000e829fbfe/content.htm
3. http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/906de68a-0a28-2c10-398b-ef0e11ef2022?QuickLink=index&overridelayout=true

Applies to:

SAP BW 3.x & SAP BI Net Weaver 2004s.

Author Bio

Gopinath Ramalingam is working as SAP Consultant with Cognizant technology solutions

He has got experience and worked on various BW/BI/BO Implementation/Support Projects.

Scenario

When we are applying patches or in case of SAP server migration, Basis team will bring both ECC and BW System in down state. At that point of time, all the delta record will be moved to BW system ,then the BASIS team can apply the patches/migrating the server activity.

Before clearing the queue, user must locked in the SAP ECC & BW system and also suspend the jobs done by basis team .Also we need to stop the posting from the client, otherwise continuously delta update in the system

Steps to clear Outbound Queue

1. Check the LBWQ t.code and clear the outbound queue using the LBWE.

2. Go to LBWE transaction code and click the Job Control.          

Then click Start date.

Set the Print param

Select ‘Immediate’.

Click Schedule job

Click Job overview

Then check the LBWQ

Now, the queue MCEX03 has been cleared. Likewise move the queue MCEX11, MCEX12 and MCEX13 from LBWQ to RSA7.

Once all the queues clearing activity is completed, we can check on t-code LBWQ having no entries.

Steps to clear Delta Queue:

Check the RSA7 and move the data into BW System using Info Package.

Go to Info package and trigger the delta.

Now, the 2LIS_02_SCL becomes zero by default.

Likewise proceed with all the extractor. Now, all the extractor must be zero (0).

To confirm the delta queue,

Check the SMQ1 transaction code if any Queue Name start with MCEX** or Destination BWCLNT*** (i.e. your BW System name).

If any entries are available then trigger the equivalent Info package in the BW System.

Finally, our SMQ1 should not have any entries like MCEX** and BWCLNT** queue. (See below screen shot)

The below two entries are invalid posting or error record in the system and can be ignored. 

Select the queue and display the detail of the record.

Dear Team,

I would like to share an issue which I faced in my BW development.

Issue Detail:

When you run the DTP from PSA to DSO, the start routine ends with the message saying that 'Error in start routine sub routine'

and the long text says 'Call of the method START_ROUTINE of the class LCL_TRANSFORM failed; wrong type for parameter SOURCE_PACKAGE'

But when you actually debug the DTP, you would end up that control is not even going inside the method me->start_routine.

Analysis:

Since the debugging control is not going inside the start_routine, we can be pretty sure that there is no issue with the start_routine code which we have written.

The source_package and the target+package of debugging screen seems to be identical to our transformation, this leads further confusion of the issue.

Solution:

A simple switch that solves the issue is - go to RSA1, and re-activate the transformation from PSA to DSO.

This will regenerate the Transformation ID and the standard Source_package and Target_package fields.

The solution is simple, yet useful. I couldn't find this in SDN, hence thought to post.