SAP entertainment

3.X Hierarchy Loading for Purchase Cube in SAP BI

2013-04-25T13:23:00.001-07:00

By Arun Bala Ganesan, Wipro Technologies

Introduction

In SAP BI 7.0, we’ll study how to implement a 3.X Hierarchy Loading for a Purchase Cube (0D_PU_C01)

The steps we do in this are the following:-

1. Creation of Info objects

2. Creation of Primary Key Info object (MATID)

3. Hierarchy Description – Assignment of Nodes to IOs

4. Export of Hierarchy

5. 3.X Loading of Master data – Creation of Info source

Process Description

Firstly, In RSA1 à Info Objects, we create a new Info Area (say info_area_134)

Now, we need to create characteristic & key figure info object catalog

We name it info_c & give the name of the info area as info_area_134 (default assigned), further we check the "Char" radio button afterwards

Now, we need to create Info objects inside this Char. catalog.

Name: Material ID (mat_id86) - CHAR (10)

Now Save & Activate the Info object.

The info object Material ID (mat_id86) is now active

Further we'll start maintaining Master Data for this Info object. So click the button "Maintain" or use Keyboard controls (F6)

This displays the output screen

The same way we need to create 2 more Info objects, for Material Group & Material Type.

Now, that we have created, it’s the right time for us to maintain the Master data for these info objects. So, we need to first make use of an Info object as its Primary Key (PK). This can be done using the "Attributes" tab.

Further we start maintaining the master data for the Info object catalog.

Go to, create & start creating records for the Master Data.

Now, that the key value objects is Material ID (mat_id86). So, go to Hierarchy tab. Now click on the "Maintain Hierarchy" button

This leads to a new screen à Initial Screen Hierarchy Maintenance. Here we can create a new hierarchy characteristic for the Info object. Now click on new button in the last of the row.

Enter the details, such as Hierarchy Info object name "mat_id86"

Hierarchy Name: z08_test_hier_name, and also give in the hierarchy description in short/medium/long text. Press Continue to proceed.

Inside this we now create Text Nodes using the standard buttons.

Use these standard procedures to create Text Nodes & assign it to nodes test_level1 & test_level2.

Now, in RSA WB go to the info catalog, wherein in the hierarchy tab, you can find a Hierarchy Table: /BIC/HMAT_ID86. Double click this Hierarchy table and proceed to view in SE11.

Now execute to view the data. Press F8

We can now view the IOBJNM (Info Object Name) & Node names as,

1. ROOT

2. TEST_LEVEL1

3. TEST_LEVEL2

4. M200

5. M100

6. M400

7. M300

Now, go to System à List à Save à Local File

You can export this to a local file as Spreadsheet, Rich Text Format, and HTML Format etc.

We now save it with the extension XLS

Further we can perform loading using 3.X Info source.

We now create an Info source as in the following screen shot.

Go to RSA1 à Info sources à Additional Functions à Create Info source 3.X, and assign this info source to MAT_ID86. Thus, we have created an Info provider.

The rest of the loading is same as the cube level loading as in 3.X.

Results

Thus, the 3.X Hierarchy Loading for Purchase Cube SAP in BI has been demonstrated.

Identify Query Version 7.x/3.x and Query Transport Request Details

2013-04-25T13:21:00.001-07:00

By Rahul Goyal, L&T Infotech

Applies to:

SAP Business Intelligence Datawarehouse (BW) 7.x/ 3.x.

Summary

This document will explain about a utility in SAP BW which will provide the information about the Query like Query Version (7.x/3.x) and transport request detail for query.

Introduction

This utility is a custom program in SAP BW which will provide the unique information about the Query like:

Query Version (7.x/3.x)

Transport request in which query is captured

Transport request Status (Released/Modifiable)

It will also provide the generic information about the query like Query GUID, Query Technical Name, Infoprovider Name, Object status, Query READMODE, Owner of the query, last changed by and Transport owner.

Business Scenario

User wants to know the list of 3.x query and want to migrate into 7.x

User wants to know the transport request # of the query and want to transport if it is not yet moved into Quality and Production system.

Note:

Object Status

(ACT – Active and executable, INA – Inactive and not executable, OFF - Switched off, PRO - Productive)

Transport Status

(R – Released, D - Modifiable)

Query READMODE

(A - Query to Read All Data at Once, H - Query to Read When You Navigate or Expand Hierarchies,

X - Query to Read Data during Navigation)

Writing a program

Enter transaction code SE38 to write a new program. Provide program name and say create.

Provide program description and other relevant information.

Provide package detail or $TMP.

Insert the code as mentioned below.

Sample Code

&---------------------------------------------------------------------
& Report  Z_LIST_OF_BWQUERY_DETAIL
& Author - Rahul Goyal
&---------------------------------------------------------------------
& This report in SAP BW provide the information about the Query like
& Query Version (7.x/3.x) and transport request in which query is captured,
& Transport request Status (Released/Modifiable). It will also provide the
& general information about the query like Query GUID, Query Technical Name,
& Infoprovider Name, Object status, Query READMODE, Owner of the query,
& Last changed by and Transport owner.
& This utility can be utilized in SAP BW migration project from 3.x to 7.x
&---------------------------------------------------------------------*
REPORT  Z_LIST_OF_BWQUERY_DETAIL.
TYPE-POOLS : slis.
DATA: BEGIN OF i_e070 OCCURS 0,
      trkorr    LIKE e070-trkorr,
      trstatus  LIKE e070-trstatus,
      as4user   LIKE e070-as4user,
      as4date   LIKE e070-as4date,
      obj_name  LIKE e071-obj_name,
      compuid   LIKE rsrrepdir-compuid,
      END OF i_e070.
DATA: BEGIN OF i_query OCCURS 0,
      compuid   LIKE rsrrepdir-compuid,
      infocube  LIKE rsrrepdir-infocube,
      compid    LIKE rsrrepdir-compid,
      objstat   LIKE rsrrepdir-objstat,
      readmode  LIKE rsrrepdir-readmode,
      author    LIKE rsrrepdir-author,
      lastuser  LIKE rsrrepdir-lastuser,
      version   LIKE rszcompdir-version,
      END OF i_query.
DATA: BEGIN OF i_output OCCURS 0,
      compuid   LIKE rsrrepdir-compuid,
      infocube  LIKE rsrrepdir-infocube,
      compid    LIKE rsrrepdir-compid,
      objstat   LIKE rsrrepdir-objstat,
      readmode  LIKE rsrrepdir-readmode,
      author    LIKE rsrrepdir-author,
      lastuser  LIKE rsrrepdir-lastuser,
      version(3) TYPE c,
      trstatus  LIKE e070-trstatus,
      trkorr    LIKE e070-trkorr,
      as4user   LIKE e070-as4user,
      END OF i_output.
DATA:  wa_fieldcat TYPE slis_fieldcat_alv,
       it_fieldcat TYPE slis_t_fieldcat_alv.
SELECT a~trkorr a~trstatus a~as4user a~as4date b~obj_name
      FROM e070 AS a INNER JOIN e071 AS b ON a~trkorr = b~trkorr
      INTO TABLE i_e070
       WHERE  b~pgmid = 'R3TR'
       AND  b~object = 'ELEM'.
sort i_e070 DESCENDING by as4date.
LOOP AT i_e070.
  i_e070-compuid = i_e070-obj_name(25).
  MODIFY i_e070.ENDLOOP.
SELECT a~compuid a~infocube a~compid a~objstat a~readmode a~author a~lastuser b~version
       FROM rsrrepdir AS a INNER JOIN rszcompdir AS b ON a~compuid = b~compuid
       INTO TABLE i_query
       WHERE   a~objvers = 'A'
       AND   a~comptype = 'REP'
       AND   b~objvers = 'A'.
LOOP AT i_query.
  IF i_query-version > 100.
    i_output-version = '7.X'.
  ELSE.
    i_output-version = '3.X'.
  ENDIF.

  MOVE:
     i_query-compuid  TO i_output-compuid,
     i_query-infocube TO i_output-infocube,
     i_query-compid   TO i_output-compid,
     i_query-objstat  TO i_output-objstat,
     i_query-readmode TO i_output-readmode,
     i_query-author   TO i_output-author,
     i_query-lastuser TO i_output-lastuser.

  READ TABLE i_e070 WITH KEY compuid = i_query-compuid.

  IF sy-subrc = 0.

    MOVE:
        i_e070-trstatus to i_output-trstatus,
        i_e070-trkorr  TO i_output-trkorr,
        i_e070-as4user TO i_output-as4user.

  ENDIF.

  APPEND i_output.ENDLOOP.

wa_fieldcat-fieldname = 'COMPUID'.
wa_fieldcat-ref_tabname = 'I_OUTPUT'.
wa_fieldcat-tabname = 'TAB_IOUT'.
wa_fieldcat-seltext_m = 'QUERY GUID'.APPEND wa_fieldcat TO it_fieldcat.CLEAR wa_fieldcat.

wa_fieldcat-fieldname = 'INFOCUBE'.
wa_fieldcat-ref_tabname = 'I_OUTPUT'.
wa_fieldcat-tabname = 'TAB_IOUT'.
wa_fieldcat-seltext_m = 'INFOPROVIDER'.APPEND wa_fieldcat TO it_fieldcat.CLEAR wa_fieldcat.

wa_fieldcat-fieldname = 'COMPID'.
wa_fieldcat-ref_tabname = 'I_OUTPUT'.
wa_fieldcat-tabname = 'TAB_IOUT'.
wa_fieldcat-seltext_m = 'QUERY NAME'.APPEND wa_fieldcat TO it_fieldcat.CLEAR wa_fieldcat.

wa_fieldcat-fieldname = 'VERSION'.
wa_fieldcat-ref_tabname = 'I_OUTPUT'.
wa_fieldcat-tabname = 'TAB_IOUT'.
wa_fieldcat-seltext_m = 'QUERY VERSION'.APPEND wa_fieldcat TO it_fieldcat.CLEAR wa_fieldcat.

wa_fieldcat-fieldname = 'OBJSTAT'.
wa_fieldcat-ref_fieldname = 'OBJSTAT'.
wa_fieldcat-ref_tabname = 'I_OUTPUT'.
wa_fieldcat-tabname = 'TAB_IOUT'.
wa_fieldcat-seltext_m = 'OBJECT STATUS'.APPEND wa_fieldcat TO it_fieldcat.CLEAR wa_fieldcat.

wa_fieldcat-fieldname = 'READMODE'.
wa_fieldcat-ref_tabname = 'I_OUTPUT'.
wa_fieldcat-tabname = 'TAB_IOUT'.
wa_fieldcat-seltext_m = 'READMODE'.APPEND wa_fieldcat TO it_fieldcat.CLEAR wa_fieldcat.

wa_fieldcat-fieldname = 'AUTHOR'.
wa_fieldcat-ref_tabname = 'I_OUTPUT'.
wa_fieldcat-tabname = 'TAB_IOUT'.
wa_fieldcat-seltext_m = 'OWNER'.APPEND wa_fieldcat TO it_fieldcat.CLEAR wa_fieldcat.

wa_fieldcat-fieldname = 'LASTUSER'.
wa_fieldcat-ref_tabname = 'I_OUTPUT'.
wa_fieldcat-tabname = 'TAB_IOUT'.
wa_fieldcat-seltext_m = 'LAST CHANGED BY'.APPEND wa_fieldcat TO it_fieldcat.CLEAR wa_fieldcat.

wa_fieldcat-fieldname = 'TRSTATUS'.
wa_fieldcat-ref_tabname = 'I_OUTPUT'.
wa_fieldcat-tabname = 'TAB_IOUT'.
wa_fieldcat-seltext_m = 'TR STATUS'.APPEND wa_fieldcat TO it_fieldcat.CLEAR wa_fieldcat.

wa_fieldcat-fieldname = 'TRKORR'.
wa_fieldcat-ref_tabname = 'I_OUTPUT'.
wa_fieldcat-tabname = 'TAB_IOUT'.
wa_fieldcat-seltext_m = 'TR #'.APPEND wa_fieldcat TO it_fieldcat.CLEAR wa_fieldcat.

wa_fieldcat-fieldname = 'AS4USER'.
wa_fieldcat-ref_tabname = 'I_OUTPUT'.
wa_fieldcat-tabname = 'TAB_IOUT'.
wa_fieldcat-seltext_m = 'TR OWNER'.APPEND wa_fieldcat TO it_fieldcat.CLEAR wa_fieldcat.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
  EXPORTING
*     I_INTERFACE_CHECK              = ’ ’
*     I_BYPASSING_BUFFER             =
*     I_BUFFER_ACTIVE                = ’ ’
*     I_CALLBACK_PROGRAM             = ’ ’
*     I_CALLBACK_PF_STATUS_SET       = ’ ’
*     I_CALLBACK_USER_COMMAND        = ’ ’
*     i_structure_name               =
*     is_layout                      =
    it_fieldcat                    = it_fieldcat[]*     it_excluding                   =
*     it_special_groups              =
*     it_sort                        =
*     it_filter                      =
*     is_sel_hide                    =
*     i_default                      = ’x’
*     i_save                         = ’ ’
*     is_variant                     =
*     it_events                      =
*     it_event_exit                  =
*     is_print                       =
*     is_reprep_id                   =
*     i_screen_start_column          = 0
*     i_screen_start_line            = 0
*     i_screen_end_column            = 0
*     i_screen_end_line              = 0
*     ir_salv_list_adapter           =
*     it_except_qinfo                =
*     i_suppress_empty_data          = abap_false
*   IMPORTING
*     e_exit_caused_by_caller        =
*     es_exit_caused_by_user         =
  tables
    t_outtab                       = i_output*   EXCEPTIONS
*     program_error                  = 1
*     OTHERS                         = 2
          .
IF sy-subrc <> 0.
  MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
          WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.ENDIF.

Remodeling of Info Providers

2013-04-25T13:19:00.003-07:00

By Arun Bala Ganesan, Wipro Technologies

Remodeling, a term which so obviously states something is either reset or rearranged with terms of Info providers. What must be the ideal way to modify how data is displayed? Say, we have loaded a million records into our cube, but in a dire need to modify, do some changes to accommodate some more Info objects to the existing fact or delete some repeating data / no data columns etc at dimension level. In such cases what is the handy solution? The most trusted way to resolve hiccups of this sort is to identify & remodel your Info provider either at fact/dimensions level. In this article we’ll discuss some steps to change the metadata of our Info Cube and remodel our Info Provider. But first time users must be cautious enough to use the remodeled object, and transport the same object to different system landscapes sequentially. The drawback is that, we need to ensure no inconsistency with regards to definition of the Info provider exists between different systems in our entire landscape, else objects could become non-transportable at last. A simple example for re-modeling is as below.

So whatever the changes the DW architects make, care must be taken to do a full backup of all data, followed by stopping all respective process chains. After remodeling existing InfoCube, ensure to re-activate all your transformations & restart process chains (if applicable).

Remodeling in SAP NW-BI 7.0 is applicable only for InfoCubes; not Characteristic Info objects or DSOs. The following options can be performed during a remodeling.

Add Characteristics / Key figure
Replace Characteristics / Key figure
Delete Characteristics / Key figure

There are some pre-activities to be performed too. Once a remodeling rule is scheduled, it is not allowed to modify in future; if not we must create a new remodeling rule. The best advantage is remodeling can be performed even when cube is filled with full data. The remodeling activity can be monitored also, and the requests can be either reset or restarted. Reset would be an exception, while Restart would potentially re-initiate the whole process.

So, to discuss on the early watches to be taken care, its best advised to never run remodeling for an InfoCube, while some process chains or SM37 jobs are running in parallel & take care of manually activating & restarts of the process chains once the remodelling is successful. Also, the InfoCube is locked for any loads or changes.

This activation must be performed for all objects upper & below the data flow (which would include transformation rules). Plus, data backups are a must. Aggregates existing on the cube, if any, will have to be recreated.

Deletion of Characteristics – Step by Step Example

Use T-Code: RSMRT or use ‘Re-Modeling’ in Administration tab on LHS of RSA1.

Consider the data as in the cube. Here we plan to delete the unused field Z08_DTE.

Give the remodeling rule name & description.

Choose the required options as in the figure.

Save, Check & Schedule the rule.

Click the ‘Monitor’ hot key to check the status on a periodic basis.

Click Release Job. The job which had been scheduled has run successfully.

After remodeling has been successful, we need to check & reactivate the transformations, DTPs etc. & other dependent objects associated with the InfoCube.

Addition of Characteristics

Provide the name & descriptions of new characteristics & dimension it must be included. Also, specify what mechanism the data is populated. In fact, there are 4 ways: Constant, Attribute (& of Characteristic), 1:1 Mapping with Characteristic or Customer Exit. Finally add the new characteristic to the BEx query and execute it.

Replacement of Characteristics is most similar to Addition.

Customer Exit for Remodeling Rules

Go to SE24 –or- Tools > ABAP Workbench > Development > Class Builder

Select Add characteristic, select new characteristic in which the dimension characteristic needs to be added. Select option Customer Exit, select Customer Exit and Transfer.

Use the last option to ‘Insert’ While the rule is being executed it can be monitored by clicking on the monitor button. Once the class builder is open, you can goto ‘Interface’ tab & use the Interface IF_RSCNV_EXIT. This is nothing but an structure which defines how one class behaves with other classes, also known as abstract class.

An interface can specify a set of methods, and classes that implement the interface will have to provide concrete implementations of those methods. IF_RSCNV_EXIT being the interface, we must implement the remodelling functionality via few methods (exits) Viz. IF_RSCNV_EXIT~EXIT. Once the class has been coded, we need to save & activate the method.

How to execute APD in Process Chain

2013-04-25T13:18:00.001-07:00

By Viral Shah, Tata Consultancy Services

Summary

The objective of this Article is to explain step by step guide to execute the APD through process chain because there is no process type available in BI system to execute automatically.

Information and Instruction

This document will give you the step by step guide to execute the APD through process chain because there is not process type available in BI system to execute automatically. As we know that there is no process type available and I want to execute APD after the data load completion or some fix time than this document will help you to do the same using the standard program of SAP.

Following are the important points.

Create the APD with t-code RSANWB.
Standard program name is RSAN_PROCESS_EXECUTE.
The program RSAN_PROCESS_EXECUTE is use to execute the APD (Analysis Process) in different actions.

Step By Step Solution

1. First you have to create the APD as per your Requirement through RSANWB t-code.

Please create with the proper name like I have created with “ZDISDOMEXPDAY”.

2. Then go to SE38 and go to program “RSAN_PROCESS_EXECUTE”.

Then click execute or F8. Then following screen appear.

3. Then select “A” for Version field and select the Technical name of APD for Analysis process field like “ZDISDOMEXPDAY”. And select action to be executed.

How to use BI queries in Visual Composer

2013-04-25T13:17:00.001-07:00

By Viral Shah, Tata Consultancy Services

Summary

The objective of this Article is to explain step by step guide to use the BI queries in the Visual composer with from start to end and cover all the component of the VC.

This document will give you the step by step guide to The objective of this Article is to explain step by step guide to use the BI queries in the Visual composer with from start to end and cover all the component of the VC. This is really useful for the beginners and give very clear idea about using the Queries in VC(visual composer).

Following are the important point.

Please assume that FI queries are already created.

Step By Step Solution

How to Create Model

Below figures show that how to create new model.

Go To Menu Model -> New Model
To open Existing Model go To Model -> Open Model

Give the Model name as the naming convention.
And path is by default set.
Click ok

How to Add Package

Below figures show that how to add the package.

Go to right Panel Select Package as show in figure.
Just drag and drop to the screen window.

Just rename the name of the package as naming conversion.
Click enter.
So now it creates package.

Use of customer exit Variables in BI

2013-04-25T13:16:00.002-07:00

By Venkat Suman B, IBM India

Scenario: The selection screen variable Month/year should be optional and if user inputs any value the Query should run for that selection condition else if user doesn’t input any values it should pick the dates as high = (current calmonth) and low = (current calmonth – 3 months)

Solution: create two customer exit variables one having properties not ready for input & other as ready for input. The code is written for I_STEP = 2 for not ready for input variable but calling other variable in this code.

Let’s Consider a TEST Query.

Changes to be done in Query designer

Open the query in query designer

ZVBICALL is a customer exit variable with not ready for input.

ZVBICALM is a customer exit variable with ready for input.

Save the changes.

Creation of Customer exit variables & ABAP devlopment

Go to Tcode CMOD in BI system and specify the Project name

It should consist of following enhancements

In the Components tab goto exit EXIT_SAPLRRS0_001 and INCLUDE ZXRSRU01.code should be written in this Custom Include only.

Code in Include ZXRSRU01

TRY.

    DATA : l_name TYPE seoclsname.

    IF i_step <> 3 .
      l_name = i_vnam.
    ELSE.
      l_name = i_s_rkb1d-compid.
    ENDIF.

    CALL METHOD (l_name)=>Z_IF_REPORT_VARIABLE~execute
      EXPORTING
        i_vnam        = i_vnam
        i_vartyp      = i_vartyp
        i_iobjnm      = i_iobjnm
        i_s_cob_pro   = i_s_cob_pro
        i_s_rkb1d     = i_s_rkb1d
        i_periv       = i_periv
        i_t_var_range = i_t_var_range
        i_step        = i_step
      IMPORTING
        e_t_range     = e_t_range
        e_meeht       = e_meeht
        e_mefac       = e_mefac
        e_waers       = e_waers
        e_whfac       = e_whfac
      CHANGING
        c_s_customer  = c_s_customer
      EXCEPTIONS
        again         = 1
        OTHERS        = 2.

    IF sy-subrc = 1 .
      RAISE again .
    ENDIF.
  CATCH cx_sy_dyn_call_error .ENDTRY.

Here Z_IF_REPORT_VARIABLE is an Interface which has got a method Execute

During the runtime we get variable name into l_name & step value in i_step.

So we should be creating a class same as Variable name i.e value we get in l_name.

This is the declaration of Interface Z_IF_REPORT_VARIABLE in se24 Transaction

Create class ZVBICALL in Tcode SE24

Create class ZVBICALL giving the interface name in interface tab

Automatically the method is created, now click on CODE icon to write the code.

method Z_IF_REPORT_VARIABLE~EXECUTE.

CONSTANTS: c_zvbicalM  TYPE char8 VALUE 'ZVBICALM',
            c_zvbicall  TYPE char8 VALUE 'ZVBICALL',
            cn3       TYPE tfmatage VALUE -3,
            c_sign_i Type char1 value 'I',
            c_range_opt_bt type char2 value 'BT'.
DATA: l_year         TYPE n LENGTH 4, "Holds Year
      l_month        TYPE n LENGTH 2, "Holds month
      l_s_range      TYPE rsr_s_rangesid, "Range Table of type E_T_RANGE
      l_date      TYPE sy-datum,          "Holds the date
      wa_t_range type RRRANGEEXIT.

IF I_STEP = 2.
    CASE i_vnam.
    WHEN c_zvbicall.
READ TABLE I_T_VAR_RANGE WITH KEY VNAM = c_zvbicalm TRANSPORTING NO FIELDS.

     if sy-subrc NE 0.
        CLEAR   l_s_range.

        l_year  = sy-datum(4).
        l_month = sy-datum+4(2).* this fm is going to give back the previous3thmonth

        CALL FUNCTION 'FIMA_END_OF_PERIOD_DETERMINE'
          EXPORTING
            i_date               = sy-datum
            i_months             = cn3
          IMPORTING
            e_date_end_of_period = l_date.

        CONCATENATE  l_date(4) l_date+4(2)   INTO   l_s_range-low.
        CONCATENATE  l_year    l_month       INTO   l_s_range-high.
           l_s_range-sign       = c_sign_i.
           l_s_range-opt        = c_range_opt_bt.*         l_s_var_range-VNAM       = c_zvbicalm.
*         l_s_var_range-IOBJNM     = c_z_tec0_m.
          APPEND l_s_range TO e_t_range.
   endif.
    endcase.endif.
endmethod.

There is no need to create ZVBICALM class. This is just a dummy variable for display purpose.

Executing the Query

Click on execute button

Here (*) implies mandatory fields, give values for those.

As u can see there are no values given for Variable Month/year

This is the output we get for these selection criteria.

Click on Info tab to get our selection criteria values.

The period value for TECO Month has come from variable ZVBICALL (customer exit variable) as you can see below even though Month/Year variable is empty.

ZVBICALL-low = 11.2010((current month- 3months) and ZVBICALL-high = 02.2011(current month)

Here I try to give the values same as we get from our exit variable to check if we get same output in both cases.

Since we input the values for Month/Year in selection screen we get value directly into TECO month from Month/Year variable. Check selection criteria values in Info tab

Enhancing the standard datasources in BI 7.0

2013-04-25T13:14:00.002-07:00

By Venkat Suman B, IBM India

Goto Tcode CMOD and enter the project name

Here the project name is ZBW02HDR

Select radio button Components with the project name..

Here we got four customer exits..

EXIT_SAPLRSAP_001— Transactional data

EXIT_SAPLRSAP_002 --- Master data attributes

EXIT_SAPLRSAP_003 —Master data Texts

EXIT_SAPLRSAP_004 --- Master data Hierarchies

Let’s consider the first instance EXIT_SAPLRSAP_001

Will be writing required code as per module specific as seen above

GET-BW-MACRO is a macro to fetch data from table entry for i_datasource and lc_include.

This macro calls the Function module ‘/DS1/C_BW_GET_INCLUDE_VALUES ‘ which contains the code as shown below.

/ds1/bw_mt_buva is a table holding the corresponding Include & datasource for an EXIT.

Steps to enhance a datasource

0PM_OM_OPA_1 is a Transaction datasource which has to be enhanced..

Goto Tcode RSO2

The above datasource uses a Function Module ‘BWSM_PM_GET_ORDCST’

As seen above the extraction can be done by following ways but in our case a standard function module is being used..

Checking FM ’BWSM_PM_GET_ORDCST’ in SE37

ICORDCST is the structure used which has to be appended to occupy our new fields.

This is the code for one of the datasources used for Games (Plant Maintenance)

We create a subroutine first and assign that Include name later in our code...

The below code will be common always.

case i_datasource.
  when 'Datasource name'.
    case t_inc.
      when 'include name'.
        perform datasourcename_exit_new in program saplxrsa
        tables c_t_data if found.
   endcase. endcase.

This is the include created for a subroutine

The appended fields are populating in this manner as shown above.

The entries need to be maintained in the table as shown below for the Datasources

Steps to Test the Datasource

Taking Datasource 0PM_OM_OPA_1 as an example .

Go to Tcode RSA3 to extract/test Datasource

Records are fetched in packets based on data/record calls field value above. .

Migration of BI 3.5 Modeling to BI 7.x

2013-04-25T13:12:00.002-07:00

By Shah Viral, Essar Information Technology Ltd

This document will give you the step by step guide to migrate the 3.5 modeling to new BI 7.x. We have to migrate the all the modeling to BI 7.x because the business content provide the 3.x modeling with transfer rule, update rule, info source and old (3.5) data source.

Following are the prerequisites for the migration.

Copy the info provider to Z info provider.
Copy the all the transformations Routines code to other documents as safer side. Because after migrate, all the ABAP code are shifted to OOPs code.
Please make sure that data source should migrate at the last.

Please find the Step by Step guide with screen shot.

1. First you have to copy the info provider and make another copy with Z name ( like original name 0FIGL_O02 and make it ZFIGL_O02)

Please give the Z name and also put it in the Z info area.

2. Then first we have to migrate the Update rule with Z info source. Please make a separate copy off transformation routine will require later on. Like

Interest Calculation Numerator Days 1 (Agreed) KF

PROGRAM UPDATE_ROUTINE.
*$*$ begin of global - insert your declaration only below this line  *-*
* TABLES: ...
* DATA:   ...
*$*$ end of global - insert your declaration only before this line   *-*

FORM compute_data_field
  TABLES   MONITOR STRUCTURE RSMONITOR "user defined monitoring
  USING    COMM_STRUCTURE LIKE /BIC/CS80FIAR_O03
           RECORD_NO LIKE SY-TABIX
           RECORD_ALL LIKE SY-TABIX
           SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
  CHANGING RESULT LIKE /BI0/V0FIAR_C03T-NETTAKEN
           RETURNCODE LIKE SY-SUBRC
           ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update
*
*$*$ begin of routine - insert your code only below this line        *-*
* fill the internal table "MONITOR", to make monitor entries

* result value of the routine
  IF COMM_STRUCTURE-FI_DOCSTAT EQ 'C'.
     RESULT = COMM_STRUCTURE-CLEAR_DATE - COMM_STRUCTURE-NETDUEDATE.
  ELSE.
     RESULT = 0.
  endif.
* if the returncode is not equal zero, the result will not be updated
  RETURNCODE = 0.
* if abort is not equal zero, the update process will be canceled
  ABORT = 0.

*$*$ end of routine - insert your code only before this line         *-*
*
ENDFORM.
 
Then Right click update rules , additional functions --->Create transformations

Then use Copy info Source 3.x New Info source option to make new copy of the info source

Then give the Z name for that info source which will help you to make new copy of the info source.

3. Then Map and Activated ( Most of the fields are mapped automatically )

4. Then the following screen would appear.

5. Then Right click transfer rules, additional functions --> Create transformations

Please assigned newly created info source with Use available infosource Option.

6. Then map and activated.

7. Then Right click datasource, click migrate ,click with export.

Please select only With export.

8. Now Your Migration is completed now just look at the Routine code.

Some Tips:

Do not use:
DATA:BEGIN OF itab OCCURS n,
fields...,
END OF itab.

REPLACED by
TYPES:BEGIN OF line_type,
fields...,
END OF line_type.
DATA itab TYPE TABLE OF line_type INITIAL SIZE n.

Internal tables with header lines are not allowed. Header line in an internal table is a default line that the system uses when looping through the internal table

Short forms of internal table line operations are not allowed. For example, you cannot use the syntax INSERT TABLE itab. However, you can use INSERT wa INTO TABLE itab

Transformations do not permit READ itab statement in which the system reads values from header lines.
For example, the code READ TABLE itab. is now outdated, but you could use the code READ TABLE itab WITH KEY . . . INTO wa.

Calling external subroutines using the syntax PERFORM FORM(PROG) is not allowed.
In this example, FORM is a subroutine in the program PROG.

DB Connect Usage in SAP BI 7.0

2013-04-25T13:11:00.002-07:00

By Arun Bala Ganesan, Wipro Technologies

Introduction

In SAP Net weaver BI 7.0, we’ll study how to implement DB Connect, rather than common usage of flat files. Using DB Connect, BI offers flexible options for extracting data directly into BI from tables and views in database management systems that are connected to BI using connections other than default connection.

The DB Connect enhancements to database interface allow you to transfer data straight into BI from the database tables or views of external applications. You can use tables and views in database management systems that are supported by SAP to transfer data. You use Data Sources to make the data known to BI. The data is processed in BI in the same way as data from all other sources.

It’s to be noted that SAP DB Connect only supports certain Database Management systems (DBMS)

The following are the list of DBMS

Max DB [Previously SAP DB]

Informix

Microsoft SQL Server

Oracle

IBM DB2/390, IBM DB2/400, IBM DB2 UDB

There are 2 types of classification. One is the BI DBMS & the other is source DBMS.

The main thing which is, both these DBMS are supported on their respective operating system versions, only if SAP has released a DBSL. If not, they don’t meet the requirements & hence can’t perform DB Connect.

In this process we use a Data source, to make the data available to BI & transfer the data to the respective Info providers defined in BI system. Further, using the usual data accusation process we transfer data from DBs to BI system.

Using this SAP provides options for extracting data from external systems, in addition to extracting data using standard connection; you can extract data from tables/views in database management systems (DBMS)

Loading data from SAP Supporting DBMS into BI

Steps are as follows:-

Connecting a database to Source system -- Direct access to external DB
Using Data source, the structure for table/view must be known to BI.

Process Description

Go to RSA1 à Source Systems à DB Connect à Create

Now, create the source system using

1. Logical System Name à MSSQL

2. Source System Name à MS SQL DB Connect

3. Type & Release

Now, Under DB Connect, we can see the name of our Source System (MS SQL DB Connect)

The logical DB Connect name is MSSQL

In Data sources we need to create an Application Component area to continue with the export

Goto RSA1 à Data sources à Create Application Component

After creating an Application Component Area called “ac_test_check”, we now have to create a Data source in the component area. So right click the Application component area à Create Data source (as in below figure).

The Data source name here is “ds_ac_tech”

The Source System here is the defined “MSSQL”

The type of data type data source that we have here is “Master Data Attributes”

The below screen shot describes how to perform extraction or loading using a Table/View. As the standard adapter is “Database Table” (by default), we can specify the Table/View here

Now, choose the data source from the DB Object Names.

Now, we have selected the “EMPLOYEES” as the Table/View.

Or we can choose the Table/View à “REGION”

We have 2 database fields

Region ID
Region Description

Now that the Data source has to be activated before it is loaded, we “ACTIVATE” it once.

After activation, the data records (4) are displayed. Eastern, Western, Northern & Southern

Right click the Info package DS_AC_TEST à Create Info package

We now create an Info package called “IP_DS_AC_TECH”, with Source system as MSSQL

Once done we perform a schedule on the Info package à “Start”

Now, we need to create an Info Area to create an Info provider (like Info Cube)

After creating the info cube we check for the data in the PSA by “Manage the PSA”

This can be also done using the Key controls (Ctrl + Shift + F6)

The number of records displayed: 4 No’s

Using the PSA Maintenance, we can view the following factors

Status
Data Packet
Data records
REGION ID
REGION Description

The Table/View “CUSTOMERS” is now chosen for Extraction. In the next tab we have “PROPOSAL”, which describes all the Database fields, and we have to specify the Data source fields, types & length.

Now, we create an Info package à IP_TEST_CUST

Now, go to RSA1 à Info objects à Info object (Test) à Create Info Object Catalog

Now, we can preview the Region ID & Region Description.

We now create 2 Info objects & pass the Region ID & Region Description to the 2 objects.

1. Region Description à Region2 (Region)

2. Region Description à reg_id (Region ids)

Now, these are the 2 variables created under the Info object “test2”

Ø Region (REGION2)

Ø Region ids (REG_ID)

We create Characteristic as Info Provider for the Master Data loading in the “Info Provider” section àInsert Characteristic as Info Provider

Now, we create a transformation using “Create Transformation” on the Region ids (Attributes)

We now choose the Source System after this à MSSQL à MS SQL DB CONNECT

After checking the Transformation mappings on the Region ID, we now perform a DTP Creation on the same Region ID (Attribute)

We choose the Target system (default) as Info object à Region ID à REG_ID & the Source Type asData source with the Source System à MSSQL

After this step, we proceed with creating an Info package à IP_DS_TEDDY which has the source system as MSSQL. Further we start the scheduling of the Info package. Once the info package has been triggered we can go to “Maintain PSA” & monitor the status of data in PSA

Further, we EXECUTE the DTP. And, we can monitor transfer of data from PSA à Info cube

Results

Thus, the DB Connect process has been successfully demonstrated in SAP BI 7.0

Step-by-Step tutorial to upload Master Data from Flat File (SourceSystem) to InfoObjects (Master data table)

2013-04-25T13:09:00.001-07:00

By Lakshmi MP, Perot Systems

Basic Steps of Data Flow (ETL process):

Determine the Source System (Flat File/SAP R3/WebServices etc)
Establish an interface w.r.t the Source system used
Create a Data Source – which has a structure similar to the Source structure. Consider two factors : Name of file and Structure same as Source.
Create Info Provider to transfer data from Data Source to PSA (Persistent staging Area)
Create a Target (Info Provider : InfoObjects/Info Cubes/DSO etc)
Create a Transformation rule to map Source & Target fields.
Create DTP (Data Transfer Process) to transport data stored within PSA , to the final Data Target.

Transaction Code – RSA1 : Data Warehouse Workbench

Source/Input: Create a Flat File of type CSV, with the following structure:

Customer	Language	Land	City	Name
260	EN	US	SEATTLE	JOHN
261	DE	DE	HAMBURG	SAM
262	DE	DE	WALDORF	MICHEAL

Right click on the InfoProvider column header. Select “Create InfoArea”

Enter the details – InfoArea name and Description

The InfoArea – IA for Customer appears on the InfoProvider list.

Right click on the created InfoArea and create InfoObject Catalog

Enter a suitable Name and Description for InfoObject Catalog.

Select ‘Char.’ or ‘Key Figure’ based on the type of data (Master data/ Trans. Data) needs to be created.

In this case, we are creating Master data. Hence, we need to create Characteristics InfoObject.

Select ‘Char.’

Click on Create.

The InfoObject Catalog appears right under the InfoArea created earlier.

Now, right click on the InfoObject Catalog and create Info Object.

In the pop-up for InfoObject enter Characteristic name and description.

The first Characteristic InfoObject created can be treated as a key value in the Master table to be created.

On the right window, the properties of the Characteristic ‘CUSTNO’ are visible.

In the General Tab, enter the Data Type and Length.

Note: the ‘Attribute Only’ field is not checked. This means that this Characteristic is a primary key field in the Master Data table.

If the box is checked, then it becomes an attribute of this Characteristic Key field or just another normal field in the Master data Table.

In the Business Explorer tab, no changes to be done.

Save + Activate => P tables gets created

In the Master data/texts tab,

- Check “With Master data”, to create a Master Data table, having naming convention /BIC/P<characteristic name>

- Check “With Texts”, to create a corresponding Text table for this Master Data table with two default fields – Language & Description.

Select ‘short/medium/long texts’, also ‘texts language dependent’.

- Select “Char is InfoProvider” (as our InfoObject is our target in this scenario).

- Enter the InfoArea in the box below.

In the Attribute tab, enter the fields (non-key fields) that need to be maintained within the Master Data table.

Ex: Customer Id – primary key field

Land

City

On entry of each field, hit [Enter] and in the pop-up box, select the 1^st option – “Create Attribute as Characteristic”.

Enter the Data type and the Length. [Enter]

Repeat the same for other fields too.

[Activate ] - Activate all dependent InfoObjects.

Create File Interface: Source Systems à File à Createà <New File System>

Use the existing file source system

Data Source creation/selection:

On the Navigator tab, select Data Source. Click on the ‘[X]’ button to Choose the Source System.

Choose the Source System à File à <Flat File source system name>

Right click on the header and Create Application Component.

Enter the name and description for Application Component.

Ex: Name: APC_CUSTOMER

Click ok.

The technical name of Application component APC_CUSTOMER now gets saved as => ZAPC_CUSTOMER

Right click on the Application component and create DataSource

Enter a suitable DataSource name : DS_Cust

Source System : Flatfile

Select Data Type of DataSource : Master Data attributes à as we are creating master data table.

Note:

Select Master Data Attributes, while you are uploading Master Data from file (DS1)

Select Master Data Text, while you are uploading Text Descriptions for the Master Data records (DS2)

In the right Window, you can view the Data Source properties.

General Info tab – provides information on the Data Source created

Extraction tab – provides details of file to be extracted.

In a Data source, we need to mention 2 details:

- Name of Flat File (ASCII or CSV) to be uploaded

- Structure (Layout) of the input file, mentioning the fields.

Therefore, make the following changes:

- Select name of file using F4, search for the file on you local desktop

- Header rows to be ignored = ‘1’ (if file has a header row as column titles)

= ‘0’ (if file has no header row)

- Select Data Format as – “Separated with Separator (for ex CSV)”.

Enter the Data Separator as ‘ , ‘.

Proposal tab – provides a quick view of the data in the flat file to be uploaded

Click on the ‘Load Example’ tab. The details can be viewed in the below pane.

Fields tab – provides details of all fields used to create a data structure, to map with the fields from Source file.

- In the Template Info field, enter the field names (characteristics/attributes).

- [Enter] or [Save]

- [Copy] : all properties of the characteristics ( ex: data types, length etc) are copied here.

Note: the fields 0LANGU and 0TXTSH are the standard SAP defined characteristics InfoObjects.

[Save]

[Activate]

Preview tab – gives a preview of data on flat file loaded onto a structure.

- Click on “Read Preview Data”

Info Package: An InfoPackage helps to transport data from the Data Source structures into the PSA tables. (This is similar to transfer of data from Work areas to Internal Tables in R/3 ABAP).

Rt. Click on the Data Source and Create InfoPackage.

Enter the InfoPackage name : IP_Cust

Enter a suitable Description

Select the corresponding DataSource from the list below and [Save].

On the right window, we have the InfoPackage properties:

Data Selection tab – to initiate loading of data into the infopackage

- Select “Start Data Load Immediately”

- Click on [Start].

- Then click on the [Monitor]button – next to “Process Chain Mgmt”

Or [ F6].

In the next screen, we can view the status of the data loading to PSA.

Click on the [PSA Maintenance] or [Ctrl + F8] to maintain the PSA table with the flat file values.

In the pop-up, defining the number of records per request, click OK.

This leads to the PSA display screen, with the table and the respective data in them.

Click on [Back] and come back to the DataSource screen.

Transformation: This is a rule that is defined, for mapping the source fields in the DataSource to the final Target (basically, the Info Providers from where BI extracts the reports).

In this case, our target is the InfoObject (Master data table), which has been already created.

Note: Normally, the Transformation can be created on the Data Source or the Target. Here, we are creating a Transformation on the DataSource.

Right click on DataSource à Create Transformation

In the pop-up,

For the Target of Transformation,

- Enter Object Type: InfoObject (this is our target in this scenario)

- Enter subtype of Object: Attributes (as we’re considering Master data only. Not transactional data)

- Enter the name of the InfoObject we created.

For the Source of Transformation,

- Enter Object Type: DataSource (this is our source structure)

- Enter name of Data Source used

- Enter the Source System used.

Click on OK

Note:

While uploading Master Data, select Sub-type of Object : ‘Attributes’ (IP1 for DS1)

While uploading Text desc. For this Master Data, select Subtype of Object : ‘Texts’ (IP2 for DS2)

In the next screen pop-up, we get the no. of proposals (rules) generated to map source fields with target fields. Click on Ok.

On the next window we can see a graphical representation of the mapping of Source fields to Target fields.

Save and Activate, if the mapping if done correctly.

Data Transfer Process (DTP):

The DTP is a process used to transfer data from the PSA tables, into the data Targets, based on the Transformation (mapping) rules.

DataSource à right click à Create Data Transfer Process.

In the pop-up,

- The DTP name is described as : < DataSrc/SourceSys -> InfoObject >

- DTP type : standard

- Target of DTP : Object Type : InfoObject (in this case)

Subtype of Object : Attribute

Name : < name of InfoObject >

- Source of DTP: Object Type : Data Source

DataSource : <name>

Source System: Flat file

Click on OK.

In the DTP properties window,

Extraction tab,

- Select Extraction Mode as ‘Full’.

[Save]

[Activate]

Update tab – no changes to be made

Execute tab,

- Click on [Execute] button

Click on [Refresh] until the icons in Yellow, turn Green.

Incase a Red icon appears, we need to track the error and rectify it.

Go Back.

To view the contents of the Target (Info Object), there are 2 ways:

Go to the InfoObject – CUSTNO à MasterData/Texts tab à Dbl click on the Master data table created : /BIC/P<Char name> à Table display à Execute

On Transformation/DTP à Attribute à rt.click à Manage à rt windw Contents tab à [Contents]à F8.

Text table Data Display is Language Dependent:

For Lang = ‘EN’, display corresponding Short Desc.

For Lang = ‘DE’, display corresponding Short Desc.

Observations:

In the above Master data table display,

The fields – Customer Name, Customer Land, Customer City : have been created and loaded with data as per the file.

These 3 fields have been created as a result of checking the “With Master data” for the Characteristic. The contents of the Master data are stored in the newly created transparent table /BIC/P<char. Name> Ex:

The fields – Language , Description : have been created and loaded with data as per the file.

These 2 fields have been created by default, as a result of checking the “With Text data” for the Characteristic. The contents of the Text data are stored in the newly created transparent table /BIC/T<char. Name> Ex:

Data Services within the SAP BI staging process

2013-04-25T13:05:00.000-07:00

By Bhargav Gandhi, Tata Consultancy Services

Data Services XI 3.x is the official name for the EIM (Enterprise Information Management) platform. BusinessObjects™ Data Services is the one platform for data delivery and data quality to move, integrate, and improve any type of data anywhere at any frequency. Data Services is both a platform and a product. It is the platform upon which all new EIM functionality will be based

SAP BI is the business intelligence platform from SAP.

Data Services tools can be used into the SAP BI staging process, especially for Non-SAP data, where the enhanced integration capabilities of Data Services might be required anyway.

Following is the procedure for using Data Services features into the SAP BI staging process -

Load the non-SAP data in the Data Services engine.
Perform Data Quality operations on the data in Data Services.
Load the data into SAP BI

Connecting SAP BI with Data Services

In order to allow the exchange of data and metadata between SAP BI and Data Services, we have to first establish a connection between both the systems. On the SAP BI side this is achieved by creating an External Source System and in Data Services we have to create a new Datastore....

1. Log on to the SAP BI system.

2. Start the Data Warehousing Workbench using TC RSA1 and select Modeling from the navigation area. Pick the entry Source Systems.

3. Position the cursor on the External System folder, and choose Create from the context menu as shown above.

4. Enter Logical System Name and Source System Name as shown above and hit Continue.

5. Data Services will start an RFC Server program and indicates to SAP BI that it is ready to receive RFC calls. To identify itself as the RFC Server representing this SAP BI Source System a keyword is exchanged, in the screen shot above it is "DEMO_SRC". This is the Registered Server Program, the Data Services RFC Server will register itself with at SAP. Therefore, provide the same Program ID that you want to use for the call of the RFC Server on Data Services side. All other settings for the Source System can remain on the default settings. To complete the definition of the Source System, save it.

6. Now, start the RFC Server on the Data Services side so that we can test the connection and load data from Data services to SAP BI system.

a) Open MS-DOS command prompt. (Start > Run > Type CMD & hit OK)

b) Go to the bin directory/folder for BusinessObjects Data Services. E.g . - C:\Program Files\Business Objects\BusinessObjects Data Services\bin>

c) Call the program "rfcsvr -aPROGRAM_ID -gSAP_ROUTER_STRING -xSAP_GATEWAY". The PROGRAM_ID is the keyword we used above, "DEMO_SRC" in our example. The Router-String and SAP Gateway is something the BW admins should know. As a guideline, you can open the SAP Logon Pad and try the settings there.

d) The server here is 172.17.10.162 and the System Number is 00. The router string could hence be "/H/172.17.10.162/S/3300". The /H/ stands for the hostname, the /S/ for the port number. The port number can be derived from the system number, system 00 means port 3300. Same thing with the SAP Gateway. In a standard standalone installation the value for this is sapgw00.

e) Type rfcsvr -aDEMO_SRC -g/H/172.17.10.162/S/3300 -xsapgw00 and hit Enter. It should not return anything

7. To check the connection, click on Connection Test as shown below -

8. The result would be as shown below in case of a success.

9. The newly entered 3rd party system would appear in the list of External Systems as shown below.

PoC – Loading unstructured data from Flat files into SAP BI using BusinessObjects Data Services

Let us take a sample tab delimited flat file as shown below. (Note - Sample data is placed in an excel file only for understanding purpose. In actual PoC we will be using a text file)

For the sample flat file used here, click here.

Define the SAP BI system as Datastore in Data Services

Before we start designing a job for our PoC, let us create a datastore for SAP BI system.

Open the BusinessObjects Data Services Designer.
In the Local Object Library, select the Datastore tab.
Right click and select New to create new Datastore as shown below

Type in datastore name as shown below.
Select SAP BW Target as the Datastore type. This is because we want to load data into SAP BI and hence SAP BI is the target.
Enter location/IP address of the SAP BI system server
Enter your user name and password for the SAP BI
Under Advanced section, enter Client and System Number. ( You can find system number, application server details from SAP Logon Pad > Change Item)
In our example (refer screenshot 4), enter ‘/H/’ as the router string.
Hit OK.

The new datastore BW_PoC_Target_Datastore is now available under Local Object Library as shown below.

Defining new Flat File format for our sample data

Open the BusinessObjects Data Services Designer.
In the Local Object Library, select the Formats tab
Right click on Flat Files format and select New.

You will see File Format Editor window

Select/Enter the data as given below

Type – Delimited
Name – PoC_File_Format
Root directory – Path where the sample flat file is stored (In our case it is - C:\Documents and Settings\164600\My Documents\BOBJ Data Services\BOBJ Data Services\Reference Material\PoC)
File name – In our case it is PoC1.txt. You would see a prompt to overwrite the current schema.

Hit Yes. Now, you would see your sample data in the editor window. Note that Designer automatically assigned appropriate data types based on the input data.

Under Delimiters, select Column – Tab

Click Save & Close

PoC_File_Format is now available under the Flat Files tree in the Local Object Library as shown below.

Designing job for the PoC in Data Services Designer

Click on Project menu and select New > Project.

Let us call our new project as PoC
Create new job by selecting New Batch Job from context menu(right click menu). Call it as PoC_Job1

Create a new dataflow and name it as PoC_DataFlow1.

Open the PoC_DataFlow1 workspace.
Drag PoC_File_Format to the workspace as a Source.

Let us have some validation done on the source data. Let us assume we want only those records where country is ‘IN’ (India) or ‘US’.
Drag the Validation from the Transform tab of the Local Object Library on the Data Flow workspace.

Connect source with the validation.

Double click on the Validation box
You will see Validation Transform Editor as shown below.
- Click on Country column in the Schema In section.
- Enable Validation
- Select ‘In’ radio button and enter validation criteria as ‘IN’, ‘US’.
- This indicates that records with country as either ‘IN’ or ‘US’ will pass the validation and rest would fail the validation. Passed and failed records are stored separately.

Drag the target for failed records from any of the available datastores e.g. Database, Flat Files, Excel Workbooks, BW Target, etc. In our case, I have created a target datastore for Oracle XE schema on my local machine. So I have taken a template table as a target for the failed records.

Name it as Invalid_Customer.

Connect the Validation box with target Invalid_Customer for failing records.

Now, we need SAP BI target for the records which pass the validation. We first have to create DataSource/InfoSource on the SAP BI side.

In order to create InfoSource, we need InfoObjects corresponding to our sample flat file data.

1. Log on to the SAP BI system.

2. Start the Data Warehousing Workbench using transaction Code RSA1 and select Modelingfrom the navigation area. Pick the entry InfoObjects.

3. Create the InfoObjects as per the cloumns in Flat File as shown in the following 3 screenshots.

4. Save and Activate the InfoObjects as you create them.

5. Below screenshot shows all the created InfoObjects.

Now, let us create a DataSource on the SAP BI side as a target for our sample data.

Following 3 screenshots shows that System is not allowing us to create a DataSource in a source system of type External System.

It also provides alternate way to achieve the same. It seems we cannot create BI 7.0 dataSource of type external system.

As per the method described in the earlier screenshot, we will create InfoSource 3.x. Follow the steps as given below.

Include all the InfoObjects created earlier in this InfoSource.

Save and Activate InfoSource

Click Yes, for activating all the independent transfer programs.

You would see logs on the screen as shown below. Go back.

Now, create Transfer Rules for the newly created InfoSource.

Click Yes for assigning the DataSource to InfoSource.

Save and Activate the InfoSource.

Go back and you would see the subtree similar to following.

To import the SAP BI structures, open the Datastore tab strip in the Object Library. Search for the Datastore that you have created for the SAP BI system as target (in our caseBW_PoC_Target_Datastore). Position the cursor on the Datastore name and choose Openfrom the context menu. Depending on the structures you want to use, expand the Master InfoSources or Transaction InfoSources tree.

Find your InfoSource, and open its subtree. Position the cursor on the DataSource name, and use the option Import from the context menu.

Afterwards, the DataSource will be available in the Object Library for your SAP BI system.

Open the workflow, you have created in the previous section. Open the Datastore tab strip in the Object Library. Search for the Datastore that you have created for the SAP BI system as target (in our case BW_PoC_Target_Datastore). Drag the structure to the canvas you want to load the data in the SAP BI system to. Connect the existing Validation Transform with the new target.

Double click this new target to open the Target Table Editor as shown below. Go to Options tab and select Column Comparison = Compare by position.

This is done so that even if column names do not match (InfoObject names cannot be more that 9 characters), we can still go ahead and carry out the data movement.

Validate your DataFlow.

Since the loading process has to be initiated by the SAP BI system, we have to create a batch file for the execution of the Job in Data Services. This batch file can subsequently be called by an InfoPackage in the SAP BI system.

Open the Data Services Management Console by choosing the corresponding menu entry from theTools menu.

Log in with your user credentials. In the Management Console navigate to the Administrator, and open your repository (or All Repositories) of the Batch folder.

Switch to the Batch Job Configuration tab strip and find your Job you want to schedule. Choose the option Export Execution Command.

Provide a File Name for the batch file. Leave the other settings on the default values and press theExport button.

Note

Since the maximum length of the file name entry field in the InfoPackage is limited to 44 characters, your file name entered must not exceed 40 characters (44 characters minus 4 characters for the extension .bat)

Screen would refresh confirming the successful export.

In our case following two files gets created after the export under C:\temp folder.

Before you switch to the SAP BI system, check that the RFC server is still running.

Switch to the SAP BI system you want to load the data to. Open the Data Warehousing Workbench and find your InfoSource / DataSource. Create an InfoPackage for the DataSource.

Switch to the 3rd Party Selection tabstrip. Press the Refresh Sel. Fields button to display the input fields.

Enter the File Name that you have provided in the creation of the batch file.

Switch to the Processing tab strip. Select “Only PSA” for updating the data to. Hit Save.

Switch to Schedule tab strip. Ensure “Start Data Load Immediately” is selected. Hit Start. It start executing the job designed in the Data Services using the batch file.

A message “Data was requested” would appear on completion of the job.

Click on Monitor (press F6) to check the status of the load.

Following screen shows you the status of the load.

To check whether your data has been transferred as expected, you can check the PSA for the load. From the monitor, you can choose the icon PSA Maintenance (Ctrl+F6) in the monitor to jump to the PSA display.

Click Continue.

Following screen shows the data loaded into the PSA. In our example we transferred the records, which passed all our Data Quality measures, i.e. all records which Country equal to either ‘IN’ or ‘US’. In total there are 3 records.

Records not satisfying the validation criteria i.e. records with countries other than ‘IN’ or ‘US’ are stored the template table as desired.

Screenshot below shows the failing records stored in the Oracle XE schema.

Enable the selection options for the data source fields (more than one field at a time) in the extract structure through customized program

2013-04-25T13:00:00.003-07:00

Enable the selection options for the data source fields (more than one field at a time) in the extract structure through customized program

By Anusha Vupalapathi, Target India

Summary:

This document describes step by step procedure to enable the selection options of the data source fields in the extract structure using a custom program. The input variables are data source name and respective fields (more than one field at a time).

Taking an Example:

Let us take data source 0CUST_SALES_ATTR as an example

No. of Fields in the Extract structure BIW_KNVV_S is 61.

RSA6, Display of the data source 0CUST_SALES_ATTR as with the fields in present in it.

ROOSFIELD is the table where the data source fields are maintained. Depending on the value of the Field SELECTION we can identify whether a selection with a field is possible or not.

The value for the field SELECTION of the table ROOSFIELD for the fields which are not visible in the

Data source is maintained as ‘A’.

If a request for a Datasource is scheduled in BI, selection conditions can be defined for certain fields. The property that defines whether a selection with a field is possible or necessary in BI is defined in the Datasource in the source system.

In addition, you can define the visibility of the field in BI: a field that is not visible (that is hidden) cannot be transferred to the transfer structure.

The field property also defines whether the customer can change the properties Selection and Transfer in Datasource post-processing.

Meaning of the values:

'A': Field hidden in OLTP and BI; property cannot be changed in Datasource post-processing

'M': Datasource needs a selection with this field in order to extract data (required field for generating a request); property cannot be changed in Datasource post-processing

' ': Datasource cannot select with this field; visibility can be changed in Datasource post-processing (field is currently visible, see '4')

'P': Datasource can select with this field; selection and visibility can be changed in Datasource post-processing (field is currently visible and cannot be selected, see 'X', '3')

'X': Datasource can select with this field; selection and visibility can be changed in Datasource post-processing (field is currently visible and can be selected, see 'P', '3')

'1': Pure selection field of the Datasource; selection, but not visibility, can be changed in Datasource post-processing (field cannot currently be selected, see '2')

'2': Pure selection field of the Datasource; selection, but not visibility, can be changed in Datasource post-processing (field cannot currently be selected, see '1').

'3': Datasource can select with this field; selection and visibility can be changed in Datasource post-processing (field is currently not visible and cannot be selected, see 'P', 'X')

'4': Datasource cannot select with this field; visibility can be changed in Datasource post-processing (field is currently not visible, see ' ')

Steps to enable the selection options for the data source fields (more than one field at a time) in the extract structure through customized program.

We are going to enable the fields BEGRU (Authorization Group) &ERDAT (Date on Which Record Was Created) of the Datasource 0CUST_SALES_ATTR.

Steps to be followed:

Create a program through the transaction SE38.

Program code

Write the below code in the program. Activate it and then execute.

Execute the program with the following input.

Datasource: 0CUST_SALES_ATTR

Fields: BEGRU and ERDAT.

Press F8.

After execution you would see that the value of the filed selection has been changed from ‘A’ to ‘P’.

Go to RSA6 and find the data source 0CUST_SALES_ATTR and select Change.

Put a check in the checkbox Selection if you want it to be a part of the selection in RSA3 and in the Info package and Generate the data source.

How to Enhance Standard Datasource to be used in BI System

2013-04-25T12:59:00.001-07:00

By Sarika Kotian, TCS

Prerequisites for using this material:

ABAP Knowledge
Basic familiarity with BI terminologies

Introduction:

Business intelligence (BI) mainly refers to reporting technique used in identifying, extracting and analyzing business data in SAP. It supports decision-making in business.

A DataSource is a set of fields, i.e. Structure that provide the data for a business unit for data transfer into BI.

Enhancement:

Execute Transaction ‘RSA6’.

Here, you find the list of Datasource. Navigate further by selecting the respective Datasource to get a detailed view of the same.

Here, in the detailed view, Extract Structure is the standard structure to be Enhanced.

Navigate further by selecting the Structure.

Append a ‘ZZ’ Structure through Menu->Goto->Append Structure.

List the required fields in the Append Structure.

Once the fields are appended, execute Transaction ‘RSA6’ and click on change mode and select the respective Datasource, and navigate to the detailed view, all the additional fields will appear in the field list. By Default ‘Hide’ Attribute will be selected, deselect the same for the fields to appear in the report.

Populating the Data:

Once the fields have been added, data needs to be populated. Data can be populated using Enhancement technique ‘BADI’ using standard BADI – ‘RSU5_SAPI_BADI’.

This standard BADI needs to be implemented using Transaction Code ‘ SE19’.

Enter the ‘Z’ implementation name.

Mention Short text for the implementation and click on ‘Interface’ tab.

Navigate further by selecting ‘DATA_TRANSFORM’ Method and enter the logic for populating the data.

Method ‘DATA_TRANSFORM’ has 2 essential Parameters:

· I_DATASOURCE – Can be used for conditional branching using ‘CASE’ wherein only for the respective data source the logic will be executed.

· C_T_DATA – Is a table, which contains data provided by the standard program for the standard fields of the respective structure. This Content can be further used for fetching, mapping and populating newly added fields.

Once the data has been populated, the same could be tested using Transaction Code ‘RSA3’.

Enter the Datasource name and Click on ‘Extraction’.

Select ‘ALV Grid’ to view the contents.

How to Enhance Standard Datasource to be used in BI System

2013-04-25T12:56:00.002-07:00

By Sarika Kotian, TCS

Prerequisites for using this material:

ABAP Knowledge
Basic familiarity with BI terminologies

Introduction:

Business intelligence (BI) mainly refers to reporting technique used in identifying, extracting and analyzing business data in SAP. It supports decision-making in business.

A DataSource is a set of fields, i.e. Structure that provide the data for a business unit for data transfer into BI.

Enhancement:

Execute Transaction ‘RSA6’.

Here, you find the list of Datasource. Navigate further by selecting the respective Datasource to get a detailed view of the same.

Here, in the detailed view, Extract Structure is the standard structure to be Enhanced.

Navigate further by selecting the Structure.

Append a ‘ZZ’ Structure through Menu->Goto->Append Structure.

List the required fields in the Append Structure.

Populating the Data:

Once the fields have been added, data needs to be populated. Data can be populated using Enhancement technique ‘BADI’ using standard BADI – ‘RSU5_SAPI_BADI’.

This standard BADI needs to be implemented using Transaction Code ‘ SE19’.

Enter the ‘Z’ implementation name.

Mention Short text for the implementation and click on ‘Interface’ tab.

Navigate further by selecting ‘DATA_TRANSFORM’ Method and enter the logic for populating the data.

Method ‘DATA_TRANSFORM’ has 2 essential Parameters:

· I_DATASOURCE – Can be used for conditional branching using ‘CASE’ wherein only for the respective data source the logic will be executed.

Once the data has been populated, the same could be tested using Transaction Code ‘RSA3’.

Enter the Datasource name and Click on ‘Extraction’.

Select ‘ALV Grid’ to view the contents.

Decision making process type in Process chains

2013-04-25T12:51:00.002-07:00

To Logically decide on the next step in the process chain flow( IF-THEN-ELSE), we can use option of "Decision between multiple Alternatives" Process type.
Step 1 : Choose "Decision between multiple Alternatives " Process type.Drag it to process chain window.

Step 2: We get a popu-up.Create a new decision making variant.

Step 3: Define the formula for IF. We have got formula editor for help.

We can define as many formula's as we have we options for next step.

Step 4: Each of the above IF condition is marked against a event ( options ) and they can be used in the process chain to define the next step ( to the respective option )

Decision making process type in Process chains

2013-04-25T12:51:00.001-07:00

Decision making process type in Process chains

2 comments:

Rehlow said...: Did you ever run into creating a Multiple Decision step in Development and then wanting to make a small change to it directly in Production? I can get into the step in Production, but if I try to change the Formula I get an error message about the client being closed to changes. Any ideas (besides having the client opened)? Thanks, ~Matt, fellow BW freak; 6 January 2009 09:29
justnaresh said...: obviously u have make the change in dev and transport..Its as gud as a executable program with code.; 26 February 2009 05:08

SAP FI Transaction Code Part -2

2013-04-25T12:51:00.000-07:00

FG99    Flexible G/L: Report Selection 
FGI0    Execute Report 
FGI1    Create Report 
FGI2    Change Report 
FGI3    Display Report 
FGI4    Create Form 
FGI5    Change Form 
FGI6    Display Form 
FGIB    Background Processing 
FGIC    Maintain Currency Translation Type 
FGIK    Maintain Key Figures 
FGIM    Report Monitor 
FGIO    Transport Reports 
FGIP    Transport Forms 
FGIQ    Import Reports from Client 000 
FGIR    Import Forms from Client 000 
FGIT    Translation Tool - Drilldown Report.
FGIV    Maintain Global Variable 
FGIX    Reorganize Drilldown Reports 
FGIY    Reorganize Report Data 
FGIZ    Reorganize Forms 
FGM0    Special Purpose Ledger Menu 
FGRP    Report Painter 
FGRW    Report Writer Menu 
FI01    Create Bank 
FI02    Change Bank 
FI03    Display Bank 
FI04    Display Bank Changes 
FI06    Mark Bank for Deletion 
FI07    Change Current Number Range Number 
FI12    Change House Banks/Bank Accounts 
FI12CORE   Change House Banks/Bank Accounts 
FI13    Display House Banks/Bank Accounts 
FIBB    Bank chain determination 
FIBC    Scenarios for Bank Chain Determin. 
FIBD    Allocation client 
FIBF    Maintenance transaction BTE 
FIBHS   Display bank chains for house banks
FIBHU   Maintain bank chains for house banks
FIBL1   Control Origin Indicator 
FIBL2   Assign Origin 
FIBL3   Group of House Bank Accounts 
FIBPS   Display bank chians for partners 
FIBPU   Maintain bank chains for partner 
FIBTS   Dis. bank chains for acct carry over
FIBTU   Main. bank chains for acctCarry over
FIHC    Create Inhouse Cash Center 
FILAUF_WF_CUST  Store Order: Workflow Customizing 
FILE    Cross-Client File Names/Paths 
FILINV_WF_CUST  Store Inventory:Workflow Customizing
FINA    Branch to Financial Accounting 
FINF    Info System Events 
FINP    Info System Processes 
FITP_RESPO      Contact Partner Responsibilities 
FITP_SETTINGS   Settings for Travel Planning 
FITP_SETTINGS_TREE      Tree Maintenance Current Settings 
FITVFELD        Tree 
FJA1    Inflation Adjustment of G/L Accounts
FJA2    Reset Transaction Data G/L Acc.Infl.
FJA3    Balance Sheet/P&L with Inflation 
FJA4    Infl. Adjustment of Open Items (FC)
FJA5    Infl. Adj. of Open Receivables (LC)
FJA6    Infl. Adj. of Open Payables (LC) 
FJEE    Exercise Subscription Right 
FK01    Create Vendor (Accounting) 
FK02    Change Vendor (Accounting) 
FK02CORE   Maintain vendor 
FK03    Display Vendor (Accounting) 
FK04    Vendor Changes (Accounting) 
FK05    Block Vendor (Accounting) 
FK06    Mark Vendor for Deletion (Acctng) 
FK08    Confirm Vendor Individually (Acctng)
FK09    Confirm Vendor List (Accounting) 
FK10    Vendor Account Balance 
FK10N   Vendor Balance Display 
FK10NA  Vendor Balance Display 
FK15    Transfer vendor changes: receive 
FK16    Transfer vendor changes: receive 
FKI0    Execute Report 
FKI1    Create Report 
FKI2    Change Report 
FKI3    Display Report 
FKI4    Create Form 
FKI5    Change Form 
FKI6    Display Form 
FKIB    Background Processing 
FKIC    Maintain Currency Translation Type 
FKIK    Maintain Key Figures 
FKIM    Report Monitor 
FKIO    Transport Reports 
FKIP    Transport Forms 
FKIQ    Import Reports from Client 000 
FKIR    Import Forms from Client 000 
FKIT    Translation Tool - Drilldown Report.
FKIV    Maintain Global Variable 
FKIX    Reorganize Drilldown Reports 
FKIY    Reorganize Report Data 
FKIZ    Reorganize Forms 
FKMN    
FKMT    FI Acct Assignment Model Management
FLB1    Postprocessing Lockbox Data 
FLB2    Import Lockbox File 
FLBP    Post Lockbox Data 
FLCV    Create/Edit Document Template WF 
FM+0    Display FM Main Role Definition 
FM+1    Maintain FM Main Role Definition 
FM+2    Display FM Amount Groups 
FM+3    Maintain FM Amount Groups 
FM+4    Display FM Budget Line Groups 
FM+5    Maintain FM Budget Line Groups 
FM+6    Display FM Document Classes 
FM+7    Maintain FM Document Classes 
FM+8    Display FM Activity Categories 
FM+9    Maintain FM Activity Categories 
FM+A    Display Doc.Class->Doc.Cat. Assgmt 
FM+B    Maintain Doc.Clase->Doc.Cat.Assgmt 
FM03    Display FM Document 
FM21    Change Original Budget 
FM22    Display Original Budget 
FM25    Change Supplement 
FM26    Display Supplement 
FM27    Change Return 
FM28    Transfer Budget 
FM29    Display Return 
FM2D    Display Funds Center Hierarchy 
FM2E    Change Budget Document 
FM2F    Display Budget Document 
FM2G    Funds Center Hierarchy 
FM2H    Maintain Funds Center Hierarchy 
FM2I    Create Funds Center 
FM2S    Display Funds Center 
FM2T    Change Releases 
FM2U    Change Funds Center 
FM2V    Display Releases 
FM3D    Display Commitment Item Hierarchy 
FM3G    Commitment Item Hierarchy 
FM3H    Maintain Commitment Item Hierarchy 
FM3I    Create Commitment Item 
FM3N    Commitment Items for G/L Accounts 
FM3S    Display Commitment Item 
FM3U    Change Commitment Item 
FM48    Change Financial Budget: Initial Scn
FM48_1  PS-CM: Create Planning Layout 
FM48_2  PS-CM: Change Planning Layout 
FM48_3  PS-CM: Display Planning Layout 
FM49    Display Financial Budget: Init.Scrn
FM4G    Budget Structure Element Hierarchy 
FM5I    Create Fund 
FM5S    Display Fund 
FM5U    Change Fund 
FM5_DEL    Delete fund preselection 
FM5_DISP   Display fund preselection 
FM5_SEL    Preselection Fund 
FM6I    Create Application of Funds 
FM6S    Display Application of Funds 
FM6U    Change Application of Funds 
FM71    Maintain Cover Pools 
FM72    Assign FM Acct Asst to Cover Pool 
FM78    Charact.Groups for Cover Pools 
FM79    Grouping Chars for Cover Pool 
FM7A    Display Cover Eligibility Rules 
FM7I    Create Attributes for FM Acct Asst 
FM7P    Maintain Cover Eligibility Rules 
FM7S    Display Cover Eligibility Rules 
FM7U    Maintain Cover Eligibility Rules 
FM9B    Copy Budget Version 
FM9C    Plan Data Transfer from CO 
FM9D    Lock Budget Version 
FM9E    Unlock Budget Version 
FM9F    Delete Budget Version 
FM9G    Roll Up Supplement 
FM9H    Roll up Original Budget 
FM9I    Roll Up Return 
FM9J    Roll Up Releases 
FM9K    Change Budget Structure 
FM9L    Display Budget Structure 
FM9M    Delete Budget Structure 
FM9N    Generate Budget Object 
FM9P    Reconstruct Budget Distrbtd Values 
FM9Q    Total Up Budget 
FM9W    Adjust Funds Management Budget 
FMA1    Matching: Totals and Balances (CBM)
FMA2    Matching: CBM Line Items and Totals
FMA3    Matching: FI Line Items (CBM) 
FMA4    Matching: FI Bank Line Items (CBM) 
FMAA    Matching: Line Items and Totals (FM)
FMAB    Matching: FI FM Line Items 
FMAC    Leveling: FM Commitment Line Items 
FMAD    Leveling: FI-FM Totals Records 
FMAE    Display Change Documents 
FMAF    Level Line Items and Totals Items 
FMB0    CO Document Transfer 
FMB1    Display Security Prices-Collect. 
FMBI    Use Revenues to Increase Expend.Bdgt
FMBUD005   FIFM Budget Data Export 
FMBUD006   FIFM Budget Data Import 
FMBV    Activate Availability Control 
FMC2    Customizing in Day-to-Day Business 
FMCB    Reassignment: Document Selection 
FMCC    Reassignment: FM-CO Assignment 
FMCD    Reassignment: Delete Work List 
FMCG    Reassignment: Overall Assignment 
FMCN    Reassignment: Supplement.Acct Assgt
FMCR    Reassignment: Display Work List 
FMCT    Reassignment: Transfer 
FMD1    Change Carryforward Rules 
FMD2    Display Carryforward Rules 
FMDM    Monitor Closing Operations 
FMDS    Copy Carryforward Rules 
FMDT    Display Carryforward Rules 
FME1    Import Forms from Client 000 
FME2    Import Reports from Client 000 
FME3    Transport Forms 
FME4    Transport Reports 
FME5    Reorganize Forms 
FME6    Reorganize Drilldown Reports 
FME7    Reorganize Report Data 
FME8    Maintain Batch Variants 
FME9    Translation Tool - Drilldown 
FMEB    Structure Report Backgrnd Processing
FMEH    SAP-EIS: Hierarchy Maintenance 
FMEK    FMCA: Create Drilldown Report 
FMEL    FMCA: Change Drilldown Report 
FMEM    FMCA: Display Drilldown Report 
FMEN    FMCA: Create Form 
FMEO    FMCA: Change Form 
FMEP    FMCA: Display Form 
FMEQ    FMCA: Run Drilldown Report 
FMER    FMCA: Drilldown Tool Test Monitor 
FMEURO1 Create Euro FM Area 
FMEURO2 Refresh Euro Master Data 
FMEURO3 Display Euro FM Areas 
FMEURO4 Deactivate Euro FM Areas 
FMEV    Maintain Global Variable 
FMF0    Payment Selection 
FMF1    Revenue Transfer 
FMG1    FM: Create Commitment Item Group 
FMG2    FM: Change Commitment Item Group 
FMG3    FM: Display Commitment Item Group 
FMG4    FM: Delete Commitment Item Group 
FMG5    Generate BS Objects fr.Cmmt Item Grp
FMHC    Check Bdgt Structure Elements in HR
FMHG    Generate Bdgt Struc Elements in HR 
FMHGG   Generate BS Elements f. Several Fnds
FMHH    Master Data Check 
FMHIST  Apportion Document in FM 
FMHV    Budget Memo Texts 
FMIA    Display Rules for Revs.Incr.Budget 
FMIB    Increase Budget by Revenues 
FMIC    Generate Additional Budget Incr.Data
FMIL    Delete Rules for Revs Incr. Budget 
FMIP    Maintain Rules for Revs.Incr.Budget
FMIS    Display Rules for Revs.Incr.Budget 
FMIU    Maintain Rules for Revs.Incr.Budget
FMJ1    Fiscal Year Close: Select Commitment
FMJ1_TR Settlement: Select Commitment 
FMJ2    Fiscal Year Close: Carr.Fwd Commts 
FMJ2_TR Settlement: Transfer Commitment 
FMJ3    Reverse Commitments Carryforward 
FMJA    Budget Fiscal Year Close: Prepare 
FMJA_TR Budget Settlement: Prepare 
FMJB    Determine Budget Year-End Closing 
FMJB_TR Budget Settlement: Determine 
FMJC    Budget Fiscal-Year Close: Carry Fwd
FMJC_TR Budget Settlement: Transfer 
FMJD    Reverse Fiscal Year Close: Budget 
FMLD    Ledger Deletion 
FMLF    Classify Movement Types 
FMN0    Subsequent Posting of FI Documents 
FMN1    Subsequent Posting of MM Documents 
FMN2    Subsequent Posting of Billing Docs 
FMN3    Transfer Purchase Req. Documents 
FMN4    Transfer Purchase Order Documents 
FMN5    Transfer Funds Reservation Documents
FMN8    Simulation Lists Debit Position 
FMN8_OLD   Simulation Lists Debit Position 
FMN9    Posted Debit Position List 
FMN9_OLD   Posted Debit Position List 
FMNA    Display CBA Rules 
FMNP    Maintain CBA Rules 
FMNR    Assign SN-BUSTL to CBA 
FMNS    Display CBA Rules 
FMNU    Maintain CBA Rules 
FMP0    Maintain Financial Budget 
FMP1    Display Financial Budget 
FMP2    Delete Financial Budget Version 
FMR0    Reconstruct Parked Documents 
FMR1    Actual/Commitment Report 
FMR2    Actual/Commitment per Company Code 
FMR3    Plan/Actual/Commitment Report 
FMR4    Plan/Commitment Report w.Hierarchy 
FMR5A   12 Period Forecast: Actual and Plan
FMR6A   Three Period Display: Plan/Actual 
FMRA    Access Report Tree 
FMRB    Access Report Tree 
FMRE_ARCH    Archive Earmarked Funds 
FMRE_EWU01   Earmarked Funds: Euro Preprocessing
FMRE_EWU02   Earmarked Funds: Euro Postprocessing
FMRE_SERLK   Close Earmarked Funds 
FMRP18  Clear Subsequent Postings 
FMSS    Display Status Assignment 
FMSU    Change Assigned Status 
FMU0    Display Funds Reservation Doc.Types
FMU1    Maintain Funds Reservation Doc.Types
FMU2    Display Funds Reservtn Fld Variants
FMU3    Maintain Funds Resvtn Field Variants
FMU4    Display Funds Reservation Fld Groups
FMU5    Maintain Funds Reservatn Fld Groups
FMU6    Display Funds Reservtn Field Selctn
FMU7    Maintain Funds Resvtn Field Selctn 
FMU8    Display Template Type for Fds Resvtn
FMU9    Maintain Template Type for Fds Resvn
FMUA    Dispay Fds Res.Template Type Fields
FMUB    Maintain Fds Res.Template Type Flds
FMUC    Display Funds Res. Reference Type 
FMUD    Maintain Funds Res.Reference Type 
FMUE    Display Funds Res.Ref.Type Fields 
FMUF    Maintaine Fds Rsvtn Ref.Type Fields
FMUG    Display Reasons for Decision 
FMUH    Maintain Reasons for Decisions 
FMUI    Display Groups for Workflow Fields 
FMUJ    Maintain Groups for Workflow Fields
FMUK    Display Fields in Groups for WF 
FMUL    Maintain Fields in Groups for WF 
FMUM    Display Field Selctn ->Variant/Group
FMUN    Display Field Seln->Variant/Group 
FMUV    Funds Resvtn Field Status Var.Asst 
FMV1    Create Forecast of Revenue 
FMV2    Change Forecast of Revenue 
FMV3    Display Forecast of Revenue 
FMV4    Approve Forecast of Revenue 
FMV5    Change FM Acct Asst in Fcst of Rev.
FMV6    Reduce Forecast of Revenue Manually
FMVI    Create Summarization Item 
FMVO    Fund Balance Carryforward 
FMVS    Display Summarization Item 
FMVT    Carry Forward Fund Balance 
FMVU    Change Summarization Item 
FMW1    Create Funds Blocking 
FMW2    Change Funds Blocking 
FMW3    Display Funds Blocking 
FMW4    Approve Funds Blocking 
FMW5    Change FM Acct Asst in Funds Blkg 
FMWA    Create Funds Transfer 
FMWAZ   Payment Transfer 
FMWB    Change Funds Transfer 
FMWC    Display Funds Transfer 
FMWD    Approve Funds Transfer 
FMWE    Change FM Acct Asst in Funds Trsfr 
FMX1    Create Funds Reservation 
FMX2    Change Funds Reservation 
FMX3    Display Funds Reservation 
FMX4    Approve Funds Reservation 
FMX5    Change FM Acct Asst in Funds Resvn 
FMX6    Funds Reservation: Manual Reduction
FMY1    Create Funds Commitment 
FMY2    Change Funds Commitment 
FMY3    Display Funds Precommitment 
FMY4    Approve Funds Precommitment 
FMY5    Change FM Acct Asst in Funds Prcmmt
FMY6    Reduce Funds Precommitment Manually
FMZ1    Create Funds Commitment 
FMZ2    Change Funds Commitment 
FMZ3    Display Funds Commitment 
FMZ4    Approve Funds Commitment 
FMZ5    Change FM Acct Asst in Funds Commt 
FMZ6    Reduce Funds Commitment Manually 
FMZBVT  Carry Forward Balance 
FMZZ    Revalue Funds Commitments 
FM_DL07    Delete Worklist 
FM_DLFI    Deletes FI Documnts Transferred from
FM_DLFM    Deletes all FM Data (fast) 
FM_DLOI    Deletes Cmmts Transferred from FM 
FM_EURO_M  Parameter maintenance for euro conv.
FM_RC06    Reconcile FI Paymts-> FM Totals Itms
FM_RC07    Reconcile FI Paymts-> FM Line Items
FM_RC08    Reconcile FM Paymts -> FM Line Items
FM_RC11    Select Old Payments 
FM_S123    GR/IR: Post OIs to FM Again 
FM_S201    Post Payments on Account to FIFM 
FM_SD07    Display Worklist 
FN-1    No.range: FVVD_RANL (Loan number) 
FN-4    Number range maintenance: FVVD_PNNR
FN-5    Number range maintenance: FVVD_SNBNR
FN-6    Number range maintenance: FVVD_RPNR
FN09    Create Borrower's Note Order 
FN11    Change borrower's note order 
FN12    Display borrower's note order 
FN13    Delete borrower's note order 
FN15    Create borrower's note contract 
FN16    Change borrower's note contract 
FN17    Display borrower's note contract 
FN18    Payoff borrower's note contract 
FN19    Reverse borrower's note contract 
FN1A    Create other loan contract 
FN1V    Create other loan contract 
FN20    Create borrower's note offer 
FN21    Change borrower's note offer 
FN22    Display borrower's note offer 
FN23    Delete borrower's note offer 
FN24    Activate borrower's note offer 
FN2A    Change other loan application 
FN2V    Change other loan contract 
FN30    Create policy interested party 
FN31    Change policy interested party 
FN32    Display policy interested party 
FN33    Delete policy interested party 
FN34    Policy interested party in applic. 
FN35    Policy interested party in contract
FN37    Loan Reversal Chain 
FN3A    Display other loan application 
FN3V    Display other loan contract 
FN40    Create other loan interested party 
FN41    Change other loan interested party 
FN42    Display other loan interested party
FN43    Delete other loan interested party 
FN44    Other loan interest.party in applic.
FN45    Other loan interested prty in cntrct
FN4A    Delete other loan application 
FN4V    Delete other loan contract 
FN5A    Other loan application in contract 
FN5V    Payoff other loan contract 
FN61    Create collateral value 
FN62    Change collateral value 
FN63    Display collateral value 
FN70    List 25 
FN72    List 54 
FN80    Enter manual debit position 
FN81    Change manual debit position 
FN82    Display manual debit position 
FN83    Create waiver 
FN84    Change waiver 
FN85    Display waiver 
FN86    Enter debit position depreciation 
FN87    Change debit position depreciation 
FN88    Display debit position depreciation
FN8A    Manual Entry: Unsched. Repayment 
FN8B    Manual Entry: Other Bus. Operations
FN8C    Manual Entry: Charges 
FN8D    Post Planned Records 
FNA0    Policy application in contract 
FNA1    Create mortgage application 
FNA2    Change mortgage application 
FNA3    Display mortgage application 
FNA4    Complete mortgage application 
FNA5    Mortgage application in contract 
FNA6    Create policy application 
FNA7    Change policy application 
FNA8    Display policy application 
FNA9    Delete policy application 
FNAA    Reactivate deleted mortgage applic.
FNAB    Reactivate deleted mortg. int.party
FNAC    Reactivate deleted mortgage contract
FNAD    Reactivate deleted policy applicat.
FNAE    Reactivate deleted policy contract 
FNAG    Reactivate deleted other loan applic
FNAH    Reactivate del. other loan int.party
FNAI    Reactivate deleted other loan cntrct
FNAK    Select file character 
FNAL    Reactivate deleted BNL contract 
FNAM    Reactivate deleted policy contract 
FNASL   Loans: Account Analysis 
FNB1    Transfer to a Loan 
FNB2    Transfer from a Loan 
FNB3    Document Reversal - Loans 
FNB8    BAV Information 
FNB9    BAV transfer 
FNBD    Loans-Automatic bal.sheet transfer 
FNBG    Guarantee charges list 
FNBU    DARWIN- Loans accounting menu 
FNCD    Transfer Customizing for Dunning 
FNCW1   Maintain Standard Role 
FNCW2   Transaction Release: Adjust Workflow
FNDD    Convert Dunning Data in Dunn.History
FNEN    Create Loan 
FNENALG   Create General Loan 
FNENHYP   Create Mortgage Loan 
FNENPOL   Create Policy Loan 
FNENSSD   Create Borrower's Note Loan 
FNF1    Rollover: Create file 
FNF2    Rollover: Change file 
FNF3    Rollover: Display file 
FNF4    Rollover: Fill file 
FNF9    Rollover: Evaluations 
FNFO    ISIS: Create file 
FNFP    ISIS: Change file 
FNFQ    ISIS: Display file 
FNFR    ISIS: Fill file 
FNFT    Rollover: File evaluation 
FNFU    Rollover: Update file 
FNG2    Total Loan Commitment 
FNG3    Total Commitment 
FNI0    
FNI1    Create mortgage application 
FNI2    Change mortgage application 
FNI3    Display mortgage application 
FNI4    Delete mortgage application 
FNI5    Mortgage application to offer 
FNI6    Mortgage application in contract 
FNIA    Create interested party 
FNIB    Change interested party 
FNIC    Display interested party 
FNID    Delete interested party 
FNIE    Reactivate interested party 
FNIH    Decision-making 
FNIJ    Create credit standing 
FNIK    Change credit standing 
FNIL    Display credit standing 
FNIN    Create collateral value 
FNIO    Change collateral value 
FNIP    Display collateral value 
FNK0    Multimillion Loan Display (GBA14) 
FNK1    Loans to Managers (GBA15) 
FNKO    Cond.types - Cond.groups allocation
FNL1    Rollover: Create Main File 
FNL2    Rollover: Change Main File 
FNL3    Rollover: Displ. Main File Structure
FNL4    New business 
FNL5    New business 
FNL6    New business 
FNM1    Automatic Posting 
FNM1S   Automatic Posting - Single 
FNM2    Balance sheet transfer 
FNM3    Loans reversal module 
FNM4    Undisclosed assignment 
FNM5    Automatic debit position simulation
FNM6    Post dunning charges/int.on arrears
FNM7    Loan reversal chain 
FNMA    Partner data: Settings menu 
FNMD    Submenu General Loans 
FNME    Loans management menu 
FNMEC   Loans Management Menu 
FNMH    Loans management menu 
FNMI    Loans information system 
FNMO    Loans Menu Policy Loans 
FNMP    Rollover 
FNMS    Loans Menu Borrower's Notes 
FNN4    Display general file 
FNN5    Edit general file 
FNN6    Display general main file 
FNN7    Edit general main file 
FNN8    Display general main file 
FNN9    Edit general overall file 
FNO1    Create Object 
FNO2    Change Object 
FNO3    Display Object 
FNO5    Create collateral 
FNO6    Change collateral 
FNO7    Display collateral 
FNO8    Create Objects from File 
FNO9    Create Collateral from File 
FNP0    Edit rollover manually 
FNP4    Rollover: Display file 
FNP5    Rollover: Edit File 
FNP6    Rollover: Display main file 
FNP7    Rollover: Edit main file 
FNP8    Rollover: Display overall file 
FNP9    Rollover: Edit overall file 
FNQ2    New Business Statistics 
FNQ3    Postprocessing IP rejection 
FNQ4    Customer Inc. Payment Postprocessing
FNQ5    Transact.type - Acct determinat.adj.
FNQ6    Compare Flow Type/Account Determin.
FNQ7    Generate flow type 
FNQ8    Automatic Clearing for Overpayments
FNQ9    Int. adjustment run 
FNQF    Swiss interest adjustment run 
FNQG    Swiss special interest run 
FNR0    Loans: Posting Journal 
FNR6    Insur.prtfolio trends - NEW 
FNR7    Totals and Balance List 
FNR8    Account statement 
FNR9    Planning list 
FNRA    Other accruals/deferrals 
FNRB    Memo record update 
FNRC    Accruals/deferrals reset 
FNRD    Display incoming payments 
FNRE    Reverse incoming payments 
FNRI    Portfolio Analysis Discount/Premium
FNRS    Reversal Accrual/Deferral 
FNS1    Collateral number range 
FNS4    Cust. list parameters for loan order
FNS6    Installation parameter lists 
FNS7    Loan Portfolio Trend Customizing 
FNSA    Foreign currency valuation 
FNSB    Master data summary 
FNSL    Balance reconciliation list 
FNT0    Loan correspondence (Switzerland) 
FNT1    Autom. deadline monitoring 
FNT2    Copy text modules to client 
FNUB    Treasury transfer 
FNV0    Payoff policy contract 
FNV1    Create mortgage contract 
FNV2    Change mortgage contract 
FNV3    Display mortgage contract 
FNV4    Delete mortgage contract 
FNV5    Payoff mortgage contract 
FNV6    Create policy contract 
FNV7    Change policy contract 
FNV8    Display policy contract 
FNV9    Delete policy contract 
FNVA    Create paid off contracts 
FNVCOMPRESSION  Loans: Document Data Summarization 
FNVD    Disburse Contract 
FNVI    Loans: General Overview 
FNVM    Change Contract 
FNVR    Reactivate Contract 
FNVS    Display Contract 
FNVW    Waive Contract 
FNWF    WF Loans Release: List of Work Items
FNWF_REP   Release Workflow: Synchronization 
FNWO    Loans: Fast Processing 
FNWS    Housing statistics 
FNX1    Rollover: Create Table 
FNX2    Rollover: Change Table 
FNX3    Rollover: Display Table 
FNX6    Rollover: Delete Table 
FNX7    Rollover: Deactivate Table 
FNX8    Rollover: Print Table 
FNXD    TR-EDT: Documentation 
FNXG    List of Bus. Partners Transferred 
FNXU    List of Imported Loans 
FNY1    New Business: Create Table 
FNY2    New Business: Change Table 
FNY3    New Business: Display Table 
FNY6    New Business: Delete Table 
FNY7    New Business: Deactivate Table 
FNY8    New Business: Print Table 
FNZ0    Rejections report 
FNZ1    Postprocessing payment transactions
FNZA    Account Determination Customizing 
FN_1    Table maint. transferred loans 
FN_2    Table maintenance transf. partner 
FN_UPD_FELDAUSW   Update Program for Field Selection

SAP Smartforms Development Techniques

2013-04-25T12:50:00.000-07:00

Smart Forms have been introduced in SAP Basis Release 4.6C as the tool for creating and maintaining forms. This tool allows developers to execute simple modifications to a form and the form logic by using simple graphical tools; in 90% of all cases, without any programming effort. Thus developers can get away from the robotic approach in sap script development, and produce good quality layouts at much reduced estimates.

Let us look at the steps involved in creating smartforms within the SAP system.

Start smartforms transaction, give the name of the smartform that you want to develop and click the Create button. This transaction is also called the smartform-builder.

1. The next screen has 3 sections –

Column 1 Global settings, pages and windows, window elements

Column 2 Details of each object selected in column 1

Column 3 Form painter for the developer to “visualize” each form object

2. Under the page node in the first column, click on Create => Page. Give the page name and description. Give the appropriate Next page in the General Attributes of the page. The Output Options tab is for defining the print attributes for the page.

3. Under the existing page node in the first column, click on Create => Window. Give the window name and description. Give the appropriate Next page in the General Attributes of the page. The Output Options tab is for defining the position and size of the window. The main point is to define the window type as Main or secondary depending on the need. Every page can have only ONE MAIN WINDOW and the width of the main window should be same on all the pages – height can differ.

4. Before creating the various elements in the windows, the programmer should define a smart style – this contains the various paragraphs and character sets that need to be used for the text elements, and is synonymous with the sap script style. Let us see how this is done.

a. Invoke transaction SMARTSTYLES. Enter the style name, and choose Create to create it. Activate the style after creating it and ensuring it that it is error-free.

b. The default paragraph, default tap stops, characters/inch and lines/inch, font family and font sizes should be defined in the header data of the smartstyle.

c. A paragraph format consists of defining indents, spacing, font settings, text color, tabs, numbering and outline.

d. The text flow can be defined for a paragraph, in the form of the below two attributes

i. Page protection – Enabling this prevents the paragraph from being split across pages due to a page break. If there is not enough space left on the current page to accommodate the paragraph, the entire paragraph gets pushed on to the next page

ii. Next paragraph – Enabling this links the current paragraph to the subsequent paragraph, and prevents them from splitting across pages due to a page break.

e. Character formats can be defined using the attributes Superscripting, Subscripting, Barcode, font attributes like family/size, bold/italic, underlined and color.

Lets now look at all the elements that can be created within a window on a page.

a. Text Node

i. This is used to position all the texts except addresses. To create this node, select the respective node that should have this text, and then choose Create => Text. Enter the name and description (both unique).

ii. Give the text type on the General Attributes tab, as Text element. Enter the text on the tab itself using the in-place Pc editor, or using the Text editor. Choose whether the text should start with a new paragraph, or new line, or append it directly to the end of the current paragraph. Give the proper output options to specify the style or box and shading for the text.

iii. Use the text type Include text, to point to a sapscript text that is already created in the SAP system. Point to note is that any control statements in the include text, are ignored during smartform processing.

iv. Use the text type text module to include a text module already defined in the SAP system. Use the program lines preceding the text module node to dynamically determine the text name that needs to be associated with the text module.

v. A special type of node called Address node is used to display addresses from the SAP system, in proper format. The important point is to enter the correct address type on the General attributes tab of the address node. The additional addresses box is used to specify the way in which the address needs to be displayed.

b. Printing graphics: (LOGO): Use the transaction code SE78 to import graphics into the SAP system. The transaction imports the graphics and stores it in the BDS (business transaction server). This can then be easily displayed in the form.

i. To create the graphic node, call the context menu for that node in the tree structure and choose Create=>graphic.

ii. Enter a name (LOGO) for the node and the description (Logo Graphic).

iii. On the general attributes determine whether the graphics background should be colored or a black and white.

iv. On General Attributes use the fields object - GRPAHIC, id – BMAP and name - &G_LOGO& to identify the graphic. &G_LOGO& is variable and therefore we can print company code specific logo.

c. The node type Template is used to display a table whose layout and size (number of lines and columns) is known before the runtime of the print program. A table layout needs to be be defined to determine the cell structure for each line. The cells are used to display the contents of the successor nodes of the template node. This allows the positioning of text and a graphic side by side.

i. Create a template node and maintain the attributes Width, Horizontal alignment, and Vertical alignment. Each line of the template must have a definition. To define the layout of each line, use the table control on the Template tab.

ii. To specify the lines of your template, for which the definition applies, use the columns From and To. The numbering should start with 1. The intervals in the line definition should neither overlap nor leave gaps.

iii. The Height to specify applies for all cells of this line. Specify a Width for each cell that needs to be displayed. The sum of the width values must amount to the specified Width of the template.

iv. The Name of the template line can be reused for other lines of the same template. Enter it in the Reference column of the desired lines. The system then copies the values you specified for the line height and the individual cell widths.

v. Use the Pattern box to select the desired ta

vi. The data to be displayed in the table cells should be specified in the successor nodes of the template node. Create the successor nodes under the template node.

a. It is best to create one folder node for each line, for clarity purposes. The folder node is actually used to combine related nodes.

b. For folder nodes, the input fields should be specified in the Output structure box, with the fields Line and Column. Assign each node to the cell in which the output needs to appear. Several nodes can be assigned to one cell.

c. The output sequence within the cell is determined by the sequence of the nodes in the tree

Now we have reached the step of merging data into a form during run time, since the form design is over. This data primarily comprises of

a. Data selected from database tables of the SAP system.

b. Data provided by the SAP Standard or by Smart Forms (for example, the date or the current page number).

c. Data that has been calculated or introduced in the form, for example table totals. This data is displayed using fields as placeholders in the form to determine how and where to display this data. Smart Forms provide the following possibilities to merge data into the form.

i. A form interface in which you define parameters for application data.

ii. Global definitions to define fields like internal tables, work areas.

iii. System fields whose contents are predetermined.

7. To define the form interface, use the node Global settings => Form Interface. Here the parameter names for the data to be passed should be entered. These names will be valid throughout the form; and they need not correspond to the variables names in the data retrieval program.

a. The export and import parameters can be of any data types.

b. Tables with a flat structure only can be passed on the Tables tab. While defining the fields, take care to enter the appropriate reference type. A type can be assigned using the keywords LIKE or TYPE. Double-click on the reference type to display its definition.

c. Use the local check on each tab page to check your entries for the form interface.

8. Within a form you can use the field string SFSY with its system fields. During form processing the system replaces these fields with the corresponding values. The field values come from the SAP System or are results of the processing. The various system fields that can be used in smartform development are listed below.

a. &SFSY-DATE&

Displays the date. You determine the display format in the user master record.

b. &SFSY-TIME&

Displays the time of day in the form HH:MM: SS.

c. &SFSY-PAGE&

Inserts the number of the current print page into the text. You determine the format of the page number (for example, Arabic, numeric) in the page node.

d. &SFSY-FORMPAGES&

Displays the total number of pages for the currently processed form. This allows you to include texts such as 'Page x of y' into your output.

e. &SFSY-JOBPAGES&

Contains the total page number of all forms in the currently processed print request.

f. &SFSY-WINDOWNAME&

Contains the name of the current window (string in the Window field)

g. &SFSY-PAGENAME&

Contains the name of the current page (string in the Page field)

h. &SFSY-PAGEBREAK&

Is set to 'X' after a page break (either automatic or command-controlled)

i. &SFSY-MAINEND&

Is set as soon as processing of the main window on the current page ends

j. &SFSY-EXCEPTION&

Contains the name of the raised exception. You must trigger your own exceptions, which you defined in the form interface, using the user_exception macro (syntax: user_exception <exception name >).

SAP-BODS integration using IDOCS

2013-04-25T12:49:00.002-07:00

By Praveen Addanki, HCL-AXON

1.Introduction:

Imagine you want to build a Reporting Solution, not a Data Warehouse in pure terms. So somebody opens the balance sheet report and does not like the way it looks. So a booking in SAP is created to correct it and then....he has to wait the entire night until the Data Warehouse gets refreshed. Another option would be to configure SAP so it sends all changes to the reporting database immediately. And that is what IDOCs are for.

On the downside though, to configure SAP to actually send changes is quite a challenge. If an IDOC is provided by SAP already it is not that bad, but if you want to distribute changes for data SAP never thought about, you have to write your IDOC from scratch and hook it into every single application dealing with that data.

The basic problem is the IDOC design. It is not like a database triggers that is independent from all the applications and fires no matter who and how a change happened. It is happening on application level, so there is a common ABAP call that has to be done at every single application.

Inside SAP, a couple of settings have to be made, this configuration is mandatory for both sending and receiving IDOCs. The following configurations steps are involved to send IDOCs from BODS to SAP ECC.

1.     Define Logical Systems

2.     Define RFC Destination

3.     Defining RFC Port(Transactional RFC)

4.     Define Partner Profile

Let us see in brief how to configure the above steps:

2.SAP Configuration settings:

2.1 Define Logical Systems:

Defining Logical systems is done in SAP ECC with the transaction ‘SALE’.

Note: This entire documentation refers to SAP IDES system refer the below screen shot for detail.

Enter the Transaction ‘SALE’ to define logical system and its assignment. As this confirmation doesn’t have authorization we will request basis to create it. Hence we used the following logical system as shown below.

Click on the above shown to define the logical system. The below popup come just continue

The Logical system created by basis is ‘ID3CLNT801’ as shown below.

2.2 Define RFC Destination:

Enter the transaction ‘SM59’ to configure the RFC destination in SAP ECC as shown below.

Click on TCP/IP connections as shown above and the create it.

Once the RFC created with Registered Server Program (Program ID) as ‘DI_RFC’ as shown here. With the defined program ID, configure this from BODS side from management console as shown below. Logon on to Management console and click administrator.

RFC server configuration is done as shown below.

The configured served need to be started the interface as shown below.

Now check the connection from SAP side as shown below. Click on the connection test as shown.

If the connection is fine then the following screen will appear.

2.1 Defining RFC Port (Transactional RFC):

Enter the transaction ‘WE21’ to create the Port as shown. The RFC destination will be defined here.

2.2 Define Partner Profile

And finally, we can configure SAP to route all IDOCs of a given type to DI by running the transaction "WE20". You click on "New", type in the Partner Number created in "/nsale" (we called it ID3CLNT801) and its type is "LS"....Logical System. Then you click on save.

Configure the Inbound parameters as SAP need to receive the IDOCS.

Note: From SAP if we need to send the IDOCS to BODS then configure outbound parameters, vice versa to receive the IDOCS (Inbound).

In this case it is considered to create the customer which comes from BODS; hence the configuration should be Inbound. It is shown below. Click on Add

Enter the message type “DEBMAS” and process code as ‘DEBM’, click on save.

Note: The following are the IDOC types, Message types on category wise.

General	Message types / IDoc types / BAPI
Vendor	CREMAS / CREMAS02
Customer	DEBMAS / DEBMAS03
Material master	MATMAS / MATMAS03
Accounting	Message types / IDoc types / BAPI
G/L account	GLMAST / GLMAST01
Cost center	COSMAS / COSMAS01
Cost element	COELEM / COELEM01
Cost center group	COGRP1 / COGRP01
Cost element group	COGRP1 / COGRP01
Activity type	COAMAS / COAMAS01
Activity group	COGRP1 / COGRP01
Activity price	COACTV / COACTV01
Profit center	PRCMAS / PRCMAS01
Profit center group	COGRP1 / COGRP01
Profit center account group	COGRP1 / COGRP01
Logistics	Message types / IDoc types / BAPI
Article master	ARTMAS / ARTMAS02 / RetailMaterial.Clone
Additional	MMADDI / MMADDI01 / RetailMaterial.SaveAdditionalReplicas
Product catalog	PRDCAT / PRDCAT01
Product catalog item	PRDPOS / PRDPOS01
Price list	PRICAT / PRICAT01
Assortment	ASSORTMENT / ASSORTMENT01 / Assortment.SaveReplica
Service master	SRVMAS / SRVMAS01
Characteristic	CHRMAS / CHRMAS02
Class	CLSMAS / CLSMAS03
Classification	CLFMAS / CLFMAS01
Document	DOCMAS / DOCMAS04
Purchasing info record	INFREC / INFREC01
Conditions	COND_A / COND_A01
Order book	SRCLST / SRCLST01
Change master	ECMMAS / ECMMAS01
Bill of material	BOMMAT / BOMMAT01
Document BOM	BOMDOC / BOMDOC01
Work breakdown structure	Project / PROJECT01
Human Resources	Message types / IDoc types / BAPI
PA object type person	HRMD_A / HRMD_A03
PD object types	HRMD_A / HRMD_A03

3. Sending IDOCs:

Sending an IDOC to SAP is an asynchronous task. One or many IDOCs are posted to SAP, just like inserting into a database table, and get stored in the SAP database. Later, SAP starts to process the IDOC and e.g. creates this new material record. Once the processing is done, no matter if successful or not, the status of this IDOC is updated in the SAP table EDIDC.

As a consequence, unlike with BAPIs, you get no return of the processing. Your only choice is to periodically query above status table and copy the status back into the senders table. If an immediate return code is required or the actual error message you have to use BAPIs. On the counter side, IDOCs are supposed to be faster while still running full data consistency tests.

Before sending the IDOCs we need to have SAP Data store to be created and then import the required IDOC. For our case to create the customer ‘DEBMAS06’

The data store created as referred here as ‘SAP_ECC’ shown above, then import the IDOC ‘DEBMAS06’ as shown below.

Click on import by name and give the IDOC name as shown below.

The following flat file information is required to create the customer through IDOCs. Row generator is required for input the configuration.

Flat file information as shown below.

Configuration information as shown below.

Once the Job completed check the generated IDOC by using the transaction code ‘WE02’.

Status 53 shows IDOC successfully received to SAP from BODS.

Customer (310) got created successfully by checking the transaction ‘XD03’.

SAP-BODS Integration using BAPI

2013-04-25T12:47:00.000-07:00

By Praveen Addanki, HCL-AXON

1. Introduction:

We can call SAP ERP or R/3 Remote Function Call (RFC) enabled functions, including Business Application Programming Interface (BAPI) functions, from queries inside data flows. A Remote Function Call is really what the word suggests: You call a function but it is remote rather than part of your code. This is the standard way how 3rd party’s tools access SAP, both for read and write. All RFCs meant to be used for business reasons, their function name starts with the text BAPI_XXXX like BAPI_ABSENCE_CREATE or BAPI_ABSENCE_GETDETAIL, both meant to create or display employee’s absence records in HR.

If you design data flows with BAPI calls against one version of SAP ERP or R/3, then change data stores to a later version of SAP ERP or R/3. Data Services allows this without the need to re-import the BAPI. Any new parameters added to the function call, including additional columns in table parameters, are added automatically to the call and filled with NULL values. Thus Data Services allows you to design jobs that are portable between SAP ERP or R/3 systems. After you import the metadata for an SAP ERP or R/3 function, the function is listed in the Functions category of the ERP or R/3 data store. You will also see the function in the function wizard, listed under the data store name.

Data Services supports tables as input and output parameters for SAP ERP or R/3 RFC and BAPI functions. The function import process automatically includes the metadata for tables included as function parameters.

2. BAPI Call:

After you import the metadata for an SAP ERP or R/3 function, the function is listed in the Functions category of the ERP or R/3 datastore. You will also see the function in the function wizard, listed under the datastore name. To call a BAPI depends on the requirement; here in this document we have considered an example of creating a CONTRACT using ‘BAPI_CONTRACT_CREATEFROMDATA’. For this BAPI, we need to send mandatory input and Tables parameters to create a CONTRACT.

To specify a table as an input parameter to a function, the table must be an input to a query, either as a top-level input or nested under the top-level. The table must also be available in the FROM clause of the context where you call the function. Data Services maps columns in the input schema by name to the columns in the table used as the function input parameter. You need only supply the columns that are required by the function. At validation, if Data Services encounters type mismatches between supplied columns and the function signature, it attempts to convert the given type to the expected type. For type mismatches that it cannot resolve, Data Services produces validation errors.

3. Importing the BAPI:

Note: This entire documentation refers to IDES SAP system, refer the below screen shot for detail.

The following Process indicates how to import the BAPI.

4. Processing the BAPI:

In this BAPI the mandatory importing and Tables parameters required to create a Contract are:

1.     Sales Document Type (Importing Parameter)

2.     Sales Organization (Importing Parameter)

3.     Distribution Channel (Importing Parameter)

4.     Division (Importing Parameter)

5.     CONTRACT_PARTNERS (Tables Parameter)

We can call this BAPI in a query transform and give the inputs as shown below. Before calling the BAPI create a output schema for passing the Tables parameter as shown below.

Mapping Inside the Query from the above screen shot.

Calling the BAPI inside the Query_1 as shown below.

Select the required BAPI and pass the mandatory parameters as shown below.

To pass the table’s parameter, click the arrow as shown below and map the correct schema which is defied for partners.

Double click on the query to map with the schema.

Pass the required return parameters to check the output.

As the structure belongs to NRDM, need to unnest the structure as shown below.

Finally execute the JOB to check the contract created.

As shown above the Contract ‘40000227’ has been created successfully. Check the same in the SAP system using the transaction ‘VA43’.

5. Considerations in BAPI:

Consider the following issues:

• All character values must be uppercase

• Padding values

• Assumed decimal values (QTY)

• Codes are language-specific

• Automatic type conversion

• SAP ERP or R/3 version-specific behavior

To determine the data requirements of various SAP ERP or R/3 functions, you can read the function requirements in the SAP GUI transaction screens:

• BAPI list by functional area: bapi

• BAPI and RFC source and input and output parameters: SE37

You can also determine appropriate values, such as the language-specific code values, by looking at the table where the data is ultimately stored.

6. Calling RFC’s enabled Function Module:

One solution would be to RFC-enable the function. That is a SAP provided function, I guess the better idea is to write a new function which does nothing else than calling this function and enable RFC. For example to call the Function module ‘READ_TEXT’ which was a normal function one, copy the same function module and make it RCF enabled. The following steps are required to enable the RFC.

Create a new function module in the transaction SE37 ‘ZREAD_TEXT’ and assign to function group ‘ZTEST_GRP’ as shown.

In the attributes tab make it as RFC enabled as shown below

Call the normal function module ‘READ_TEXT’ in the source code. Save it and activate it.

Now the RFC enable function module ‘ZREAD_TEXT’ is ready.

Now let us see how to call this from BODS designer.

After dragging the source and connected to query then this RFC function call is done.

In the Query edition a ‘New Function Call’ option is available as shown below and give the required importing parameters.

As we have table parameter available in this Function module, we need to normalize the schema by calling one more query as shown below.

Once the Job is executed we can see the result that has been extracted from the Function module.

SAP BUSINESS OBJECTS

2013-04-25T12:26:00.001-07:00

SAP Business Objects (a.k.a. BO, BOBJ) is a French enterprise software company, specializing in business intelligence (BI). Since 2007, it has been a part of SAP AG. The company claimed more than 46,000 customers worldwide in its final earnings release prior to being acquired by SAP.^[1] Its flagship product is BusinessObjects XI, with components that provide performance management, planning, reporting, query and analysis and enterprise information management. Business Objects also offers consulting and education services to help customers deploy its business intelligence projects. Other Business Objects toolsets enable universes (the BOBJ name for a semantic layer between the physical data store and the front-end reporting tool) and ready-written reports to be stored centrally and made selectively available to communities of password-protected usernames.

[edit]

Bernard Liautaud co-founded Business Objects in 1990 together with Denis Payre and was chief executive officer until September 2005, then became chairman and chief strategy officer until January 2008. In 1990, the first customer, Coface, was signed. The company went public on NASDAQ in September 1994, making it the first European software company listed in the United States.^{[citation needed]} In 2002, the company made Time Magazine Europe's Digital Top 25 of 2002 and were BusinessWeek Europe Stars of Europe.
History

On 7 October 2007, SAP AG announced^[2] that it would acquire Business Objects for $6.8B. As of 22 January 2008, the corporation is fully operated by SAP; this is seen as part of a growing consolidation trend in the business software industry, with Oracle acquiring Hyperion in 2007 and IBM acquiring Cognos in 2008.

Business Objects had two headquarters in San Jose, California, and Paris, France, but their biggest office was in Vancouver, BC. The company's stock was traded on both the Nasdaq and Euronext Paris (BOB) stock exchanges.

[edit]Legal

On April 2, 2007 a lawsuit from Informatica (inherited by BOBJ from the purchase of Acta Technologies in 2002) resulted in an award of $25 million in damages to Informatica forpatent infringement. The lawsuit related to embedded data flows with one input and one output. Informatica asserted that the ActaWorks product (now sold by BOBJ as part of Data Integrator), infringed several Informatica patents including U.S. Patent Nos. 6,014,670 and 6,339,775, both titled "Apparatus and Method for Performing Data Transformations in Data Warehousing." BOBJ subsequently released a new version of Data Integrator (11.7.2) removing the infringing product capability.^[3]^[4]

[edit]Timeline

1990: BusinessObjects launches Skipper SQL 2.0.x.
1994: Launches BusinessObjects v3.0 and goes public on the NASDAQ in September — the first French company listed in the United States.^[5]
1996: Enters the OLAP market and launches BusinessObjects v4.0. Bernard Liautaud named one of Business Week's "Hottest Entrepreneurs of the Year."
1997: Introduces WebI thin client, which enables shared information across an extranet.^[6]
1999: General Electric (GE) begins working with the company.^{[citation needed]} Business Objects goes public in France on the Premier Marché. Acquires Next Action Technologies.
2000: Acquires OLAP@Work for approximately $15 million^[7] and announces MDX Connect from this acquisition.^[8]
2001: SAP signs an OEM and reseller agreement to bundle Crystal Reports. Acquires Blue Edge Software.
2001: Signs up its single largest global software licensing transaction with Three formerly known as Hutchison 3G.
2002: Acquires Acta Technologies.^[9] Bernard Liautaud named to Business Week's "Stars of Europe," and the company is named one of the "100 Fastest Growing Tech Companies" by Business 2.0.^[10] Informatica files a lawsuit against Acta, claiming patent rights infringement.^[6]
2003: Acquires Crystal Decisions for $820 million.^[11] Business Objects releases Dashboard Manager, BusinessObjects Enterprise 6, and BusinessObjects Performance Manager.
2004: Debuts new combined company with the slogan, "Our Future is Clear, Crystal Clear." Launches Crystal v10 and BusinessObjects v6.5.
2005: Launches BusinessObjects XI. Acquires SRC Software, Infommersion, and Medience. Launches BusinessObjects Enterprise XI Release 2.
2006: Business Objects acquires Firstlogic, Inc and Nsite Software, Inc.
2006: Acquires ALG Software (formerly Armstrong Laing Group). Launches Crystal Xcelsius, which allows users to transform Microsoft Excel spreadsheet data into interactive Flash media files.
2007: Continuing its string of acquisitions, Business Objects acquires Cartesis and Inxight.
2007: In October, SAP AG's Chief Executive Henning Kagermann announced a $6.8 billion deal to acquire Business Objects.
2008: In January, SAP absorbs all of Business Objects' offices, and renames the entity "Business Objects, an SAP company". Following the acquisition of Business Objects by SAP, the founder and CEO of Business Objects, Bernard Liautaud, announces his resignation.
2009: Business Objects becomes a division of SAP instead of a separate company. The portfolio brand "SAP BusinessObjects" was created. All former BO employees now officially work for SAP.

[edit]Products

Common services for deployment and management of BI tools
Reporting

Query and analysis tools for self-service reporting, including DeskI (Full Client, which is being retired) and Web Intelligence (for ad-hoc reporting).

Enterprise Reporting (SAP Crystal Reports) access, format, and deliver information to large populations of users.
Data Visualization (Dashboard Design/Xcelsius) supports creation of flash dashboards and dynamic charts and graphics with data from BO XI, databases, or Excel spreadsheets.
Universe Designer: An administrator tool used to construct Universes or abstracted end-user views of the database; allows pre-defining table joins, object descriptions, and measure object behavior during aggregation. This tool is succeeded by "Information Design Tool" (IDT) in SAP BusinessObjects 4.0
Enterprise Information Management (EIM) integrates and improves data to create a trusted foundation for business decisions. Creates a basis for querying and analysis throughETL or EII.
Enterprise Performance Management (EPM) helps users align with strategy by tracking and analyzing key business metrics and goals via management dashboards,scorecards, analytics, and alerting.
InfoView web portal, which is succeeded by BI Launch pad in SAP BusinessObjects 4.0^[16]
BusinessObjects Planning and Consolidation (formerly OutlookSoft) a corporate performance management tool which runs within Microsoft Excel^[17]

On-demand BI software (Business Intelligence OnDemand), hosted on the web.

DefinitionBusiness object technology and business object programming are based on the concept of "business objects". Real world objects, for example an employee or a sales order, are modeled as business objects in business application systems, such as the R/3 System.
You can visualize the SAP Business Objects as "black boxes" that encapsulate R/3 data and business processes, thus hiding the details of the structure and implementation of the underlying data.StructureTo achieve this encapsulation, the SAP Business Objects are constructed as entities with multiple layers:

At the core of an SAP Business Object is the kernel, which represents the object's inherent data.

The second layer, the integrity layer, represents the business logic of the object. It comprises the business rules and constraints that apply to the Business Object.

The third layer, the interface layer, describes the implementation and structure of the SAP Business Object, and defines the object's interface to the outside world.

The fourth and outermost layer of a Business Object is the access layer, which defines the technologies that can be used to obtain external access to the object's data, for example COM/DCOM (Component Object Model/Distributed Component Object Model).

IntegrationAccessing Business ObjectsAs the graphic shows, the interface layer separates a Business Object's data and the applications and technologies that can be used to access it. To the outside, the SAP Business Objects reveal only their interface, which consists of a set of clearly defined methods. Applications can only access the Business Object data by the object's methods.
An application program that accesses an SAP Business Object and its data only needs the information required to execute the methods. Therefore, an application programmer can work with the SAP Business Objects and invoke their methods without having to know or consider the object's underlying implementation details.
The set of methods that is associated with a Business Object represents the object's behavior. When a method is executed on a Business Object, the method can change the object's internal state, that is, the object's data.
For example, one method that you can use on the Business Object "Employee" is to "check for the employee's existence".
All SAP Business Object types and their methods are identified and described in the Business Object Repository (BOR).
See also:Introduction to the Business Object Repository
Introduction to BAPIs
Object Types and Object InstancesEach individual Business Object belongs to a specific object class, depending on the nature and general characteristics of the object. These object classes are called object types. For example, the individual employees working in an organization are all part of the "Employee" object type.
The object types are descriptions of the actual SAP Business Objects that can exist in R/3; that is, each individual SAP Business Object is a representation, or instance, of its object type. For example, the employee with the name Charles Jones and the employee number 1234 is an instance of the "Employee" object type.
When writing object-oriented application programs, application developers identify the object types that are to be used and operated on by their programs. At runtime, the application program accesses the specific instances of the defined object types.
When an instance of a Business Object is used by an application program, the object instance responds only to the set of characteristics and methods defined for its own object type. The SAP Business Object types are defined by the following:

Object type The object type describes the features common to all instances of that object type. This includes information such as the unique name of the object type, its classification, and the data model.

Key fieldsThe key fields determine the structure of an identifying key, which allows an application to access a specific instance of the object type. The object type "Employee" and the key field "Employee.Number" are examples of an object type and a corresponding key field.

Methods
A method is an operation that can be performed on a Business Object and that provides access to the object data. A method is defined by a name and a set of parameters and exceptions, which can or must be provided by the calling program in order to use the method. BAPIs are examples of such methods.

AttributesAn attribute contains data about a Business Object, thus describing a particular object property. For example, "Employee.Name" is an attribute of the "Employee" object type.

Events
An event indicates the occurrence of a status change of a Business Object.

Interfaces
Interfaces are groups of related methods associated with an object type.

Inheritance and PolymorphismOne objective and the main benefit of object-oriented technology is software reusability.
The reuse of software code is achieved by deriving new object types from existing ones. When an object type is generated from an existing object type, the new object type is called the subtype and the existing object type is called the supertype. For example, the object type "Employee" is a subtype which has been derived from the supertype "Person". Note that "subtype" and "supertype" are sometimes referred to as "subclass" and "superclass".
A subtype inherits all the properties and methods defined for the supertype from which it descends, but can also have additional properties and methods. A subtype may also implement a different behavior for the methods inherited from the supertype. Polymorphism is the term used to describe when the same method triggers different types of behavior in different Business Object types.

Business Object type contains methods, attributes and events which give a component based view of any Business Process.

For example we have a Purchase Order business process. This process includes various small functionalities. It will have process of changing Purchase orders based upon requirements, functionality to retrieve the details of purchase order etc. Each of these functionalities is encapsulated inside a method. The method can call the function modules present in R3 system or can have there own code to execute some functionality. So if we consider Purchase Order as a Business Object then it will be identified by key field Purchase Order number. Each purchase order business object based upon key field purchase order number is different. It’s so because each purchase order is different and will contain different details.

So the methods contain business functionality. Attributes are just like properties of the Business object. For example for any purchase order Purchasing Group, Purchasing Organization etc are attributes.

Technically we can say that business object types are just like any template. At runtime we instantiate or create runtime objects for any BO (Business Object) type based upon the key fields we pass. Two runtime Business objects of same BO type are different from each other based upon the key fields we pass. So the key field is the differentiating factor for two or more runtime business objects of same BO type.

To Browse for BO open tcode SWO2 (Path -> Tools ->ABAP Workbench->Overview->Business Object Browser).

You can expand the nodes and can check various business objects in BOR. You can double click on the BO node and it will take you to BO display (SWO1).

1 Working with Business Object in our programs

For creating a Business Object and its attributes there are many already existing tutorials. So in this tutorial we will not discuss creation of BO and its attributes.

1.1 To create instance of a BO

To create an instance of BO we need to have the key fields of that BO. Key fields will be used to uniquely identify the BO. We can use the FM 'SWO_CREATE' to create an instance of BO in any report program.

DATA:
    i_objtype TYPE swo_objtyp,
    i_objkey TYPE swo_typeid,
    object TYPE swo_objhnd.

i_objtype = <Business Object>
i_objkey = <BO key>

CALL FUNCTION 'SWO_CREATE'
  EXPORTING
    objtype = i_objtype
    objkey  = i_objkey
  IMPORTING
    object  = object.

The variable ‘object’ will hold runtime instance of the object type.

The other way is to use the macros defined in include <cntn01>

INCLUDE <cntn01>.

DATA:
    i_objtype TYPE swo_objtyp,
    i_objkey TYPE swo_typeid,
    object TYPE swc_object.

*Create instance of Object type
swc_create_object object  i_objtype i_objkey.

Internally the macro calls the FM SWO_CREATE. So you can either go for direct FM call or the macro call.

1.2 Container

Basically the term Container is used with reference to Business Objects and Workflows. The Container actually holds import and export parameters associated with any method of Business Object at runtime. When ever we are calling any method of Business Object we need to populate container for import parameters and after the method gets executed it returns the values (export parameters) in Container.

Business Object container is technically of type SWCONT structure.

Here ‘ELEMENT’ will be name of the variable/internal table which container holds and ‘VALUE’ will have corresponding value. For multi line variable or internal tables, the container will hold multiple values with same element name.

1.2.1 Lets take an example to check what Container is

For example let’s create a Business Object ‘ZSWE1’ with only one method ‘READ’. We will discuss the creation of BO in very brief.

Key field will be Purchase Order number (EKKO_EBELN) for BO.

Method READ will take Purchase Order number as input and will give all the Purchase Line items in it in an internal table.

Step 1 : Create BO ZSWE1 for test purpose. You can give it any name.

Step 2 : Now create a method READ

Save the method. Now we will create the parameters of the method.

Import Parameters	PurchaseDocument	EKKO-EBELN
Export Parameter	ITEM	EKKO-EBELP (multi line)

PurchasingDocument will be a import parameter of type EKKO_EBELN.

ITEM will be a export parameter of type EKKO_EBELP and will be a multi line variable(internal table )

Save the method and then Click on the Program button to implement the method. In the method just read all ebeln (Purchase line items) corresponding to PO number into internal table ITEM and pass it on to container in the method. Check the snapshot below.

Check the whole code of the BO program here.

*****           Implementation of object type ZSWE1                *****
INCLUDE <OBJECT>.
BEGIN_DATA OBJECT. " Do not change.. DATA is generated
* only private members may be inserted into structure private
DATA:
" begin of private,
"   to declare private attributes remove comments and
"   insert private attributes here ...
" end of private,
  BEGIN OF KEY,
      PURCHASINGDOCUMENT LIKE EKKO-EBELN,
  END OF KEY.
END_DATA OBJECT. " Do not change.. DATA is generated

BEGIN_METHOD READ CHANGING CONTAINER.
DATA:
      PURCHASINGDOCUMENT TYPE EKKO-EBELN,
      ITEM TYPE EKPO-EBELP OCCURS 0.
  SWC_GET_ELEMENT CONTAINER 'PurchasingDocument' PURCHASINGDOCUMENT.

  select ebelp into table item from ekpo
  where ebeln = PURCHASINGDOCUMENT.

  SWC_SET_TABLE CONTAINER 'Item' ITEM.
END_METHOD.

Step 1 : Save the changes and make the status of the BO to implemented for testing purpose. Also generate the BO.

Step 2 : Now let’s test the BO. For this put a break point in the method READ at the select query. Also take any PO number which will have multiple line items. You can check EKKO and EKPO tables. In my case I am taking PO ‘4200000017’. In my R3 system this particular PO contains 4 line items in EKPO table. Let’s put a break point and check the method.

Step 3 : Execute the BO with key ‘4200000017’

Execute the method with import parameter as ‘420000017’

It will take you to debugging mode. Now check the container.

In debug mode before the select statement the CONTAINER will hold only import variable

Now execute the last statement in the method and see the contents of CONTAINER (just before exiting the method.

So we have seen how the CONTAINER holds values while we are working with Business Objects at runtime.

1.2.2 Some common macros defined in include <CNTN01> for working with Containers

Functionality	Macro
To write a single line variable in Container	SWC_SET_ELEMENT
To read a single line variable from Container	SWC_GET_ELEMENT
To write a multi line variable or internal table in Container	SWC_SET_TABLE
To read a multi line variable or internal table from Container	SWC_GET_TABLE
To clear the container	SWC_CLEAR_CONTAINER

Further you can check the include <CNTN01> for more macros. Also check the macros. These macros call some specific function modules that you can use directly in your code.

1.3 Calling a BO Method/Attribute in report programs

We can create a instance of BO method using FM 'SWO_CREATE' or macro ‘SWC_CREATE_OBJECT’.

First of all lets consider a BO 'BUS1001006' (StandardMaterial). We will call the method ‘DISPLAY’. For this we will instantiate the BO with key ‘ZSHUKSWE20’( material number).

To call a method or attribute of any BO we can use the FM 'SWO_INVOKE'. We have to take care while we call this FM. Suppose if we want to call an attribute defined in the method, then we need to populate the import parameter ACCESS with ‘G’. If we need to call the method of the BO then we need to populate the import parameter ACCESS with ‘C’.

Lets create a report program and check step by step. We will fetch details of attribute “MATERIALTYPE” of BO 'BUS1001006'

*&---------------------------------------------------------------------*
*& Report  ZSWET_BO1
*&
*&---------------------------------------------------------------------*
*& To get attributes of BO instance in report
*&
*&---------------------------------------------------------------------*

REPORT  zswet_bo1.

PARAMETERS: p_busobj(10) TYPE c DEFAULT 'BUS1001006',
            p_key(70) TYPE c DEFAULT 'ZSHUKSWE20' ,
            p_attr(32) TYPE c DEFAULT 'MATERIALTYPE',
            p_access TYPE c DEFAULT 'G'. "To call method put 'C'
DATA:
    i_objtype TYPE swo_objtyp,
    i_objkey TYPE swo_typeid,
    i_element TYPE swo_verb.

DATA object TYPE swo_objhnd.
DATA verb TYPE swo_verb.
DATA return TYPE swotreturn.
DATA lt_container TYPE STANDARD TABLE OF swcont.
DATA line TYPE swcont.

i_objtype = p_busobj.
i_element = p_attr.
i_objkey = p_key.

*  Instantiate the business object. i.e give it a key and create it.
CALL FUNCTION 'SWO_CREATE'
  EXPORTING
    objtype = i_objtype
    objkey  = i_objkey
  IMPORTING
    object  = object.

* Return attribute.
CALL FUNCTION 'SWO_INVOKE'
  EXPORTING
    access    = p_access
    object    = object
    verb      = i_element
  IMPORTING
    return    = return
    verb      = verb
  TABLES
    container = lt_container.
* The attribute value is in the container returned from FM.
IF return-code = 0.
  LOOP AT lt_container INTO line.
    WRITE: / 'Attribute MATERIAL TYPE is : ',
              line-value.
  ENDLOOP.
ENDIF.

Lets execute the report and see the output:

Now lets see how to call a method of BO. The Method DISPLAY will display the material passed in BO container.

*&---------------------------------------------------------------*
*& Report  ZSWET_BO1
*&
*&---------------------------------------------------------------*
*& To call method with import parameters
*&
*&---------------------------------------------------------------*

REPORT  zswet_bo1.
* Get an attribute of a business object.

PARAMETERS: p_busobj(10) TYPE c DEFAULT 'BUS1001006',
            p_key(70) TYPE c DEFAULT 'ZSHUKSWE20' ,
            p_attr(32) TYPE c DEFAULT 'DISPLAY',
            p_access TYPE c DEFAULT 'C'. "To call method put 'C'
DATA:
    i_objtype TYPE swo_objtyp,
    i_objkey TYPE swo_typeid,
    i_element TYPE swo_verb.

DATA object TYPE swo_objhnd.
DATA verb TYPE swo_verb.
DATA return TYPE swotreturn.
DATA lt_container TYPE STANDARD TABLE OF swcont.

i_objtype = p_busobj.
i_element = p_attr.
i_objkey = p_key.

*To call the method we need to populate the Container of the
*BO with importing parameters
CALL FUNCTION 'SWC_ELEMENT_SET'
  EXPORTING
    element   = 'MATERIAL'
    field     = p_key(18)    "Material Number
  TABLES
    container = lt_container
  EXCEPTIONS
    OTHERS    = 1.

*Instantiate the business object. I.e give it a key and create it.
CALL FUNCTION 'SWO_CREATE'
  EXPORTING
    objtype = i_objtype
    objkey  = i_objkey
  IMPORTING
    object  = object.

* To call the Method of the BO.
CALL FUNCTION 'SWO_INVOKE'
  EXPORTING
    access    = p_access
    object    = object
    verb      = i_element
  IMPORTING
    return    = return
    verb      = verb
  TABLES
    container = lt_container.

The Output will be:-

Lets see an example below on How to Call the methods using the macros defined in include <CNTN01>.

*&----------------------------------------------------------------*
*& Report  ZSWET_BO1
*&
*&----------------------------------------------------------------*
*& Using macros defined in CNTN01 include. To call method of BO
*& For reference check FM DNO_DB_APPENDIX_INSERT
*&----------------------------------------------------------------*

REPORT  zswet_bo1.

INCLUDE <cntn01>.

* Get an attribute of a business object.
PARAMETERS: p_busobj(10) TYPE c DEFAULT 'BUS1001006',
            p_key(70) TYPE c DEFAULT 'ZSHUKSWE20',
            p_attr(32) TYPE c DEFAULT 'DISPLAY',
            p_access TYPE c DEFAULT 'C'. "To call method put 'C'
DATA:
    i_objtype TYPE swo_objtyp,
    i_objkey TYPE swo_typeid,
    i_element TYPE swo_verb.

DATA: gv_mat TYPE swc_object.

i_objtype = p_busobj.
i_element = p_attr.
i_objkey = p_key.

*Define container
swc_container container.

*Create instance of Object type
swc_create_object gv_mat i_objtype i_objkey.

**gv_mat will contain instance of the BO

*To clear a continer
swc_clear_container container.

*Now to call a method fill up container with import parameters for method
swc_set_element container 'MATERIAL' p_key(18). "'MATERIAL' ->import parameter

*For container of type table use swc_set_table.

***If any more import parameter are there for the object then populate them
***also using swc_set_element and swc_set_table
*In this case no more import parameters

*To call a method stored in p_attr
swc_call_method gv_mat p_attr container.

*If there are any export parameter, then CONTAINER will have the values
*and we can read from container

The Output will be:-

1.4 To trigger an Event of BO

We can use the FM ‘SWE_EVENT_CREATE’ to raise an event in any report program. An explicit commit work is required after the FM call to trigger the event, other wise event will not be raised.

*&---------------------------------------------------------------*
*& Report  ZSWET_BO1
*&
*&---------------------------------------------------------------*
REPORT  zswet_bo1.

INCLUDE <cntn01>.

* Get an attribute of a business object.
PARAMETERS: p_busobj(10) TYPE c DEFAULT 'BUS1001006',
            p_key(70) TYPE c DEFAULT 'ZSHUKSWE20'.
DATA:
    i_objtype TYPE swo_objtyp,
    i_objkey TYPE swo_typeid.

i_objtype = p_busobj.

i_objkey = p_key.

*Define container
swc_container container.

*To clear a continer
swc_clear_container container.

*You can populate the Container if required

*To generate event
CALL FUNCTION 'SWE_EVENT_CREATE'
  EXPORTING
    objtype           = i_objtype
    objkey            = i_objkey
    event             = 'CREATED'
  TABLES
    event_container   = container
  EXCEPTIONS
    objtype_not_found = 1
    OTHERS            = 2.
IF sy-subrc <> 0.
  " MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
  "         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4
  "         RAISING OBJTYPE_NOT_FOUND.
ENDIF.

COMMIT WORK.

Just triggering an event does not makes any sense until and unless a proper event receiver id is linked to the event. This event receiver can be a FM or can be any workflow. Event linkage can be done in SWE2 or SWETYPV transactions.

SAP WEBDYNPRO

2013-04-25T12:17:00.001-07:00

WebDynpro is a great modeling environment whitch stores the user-interface details in the form of metadata. We can write less code and fix bugs in a shorter time with lesser effort. It increases a programmer’s productivity by manifolds.

Webdynpro is nothing but one framework for developement of user interface for use with SAP NetWeaver.It support programming for different platform such as JAVA ,ABAP,.NET .

In case of JAVA webdynpro comes with extensive design tool .Thease tools are based upon Eclipse framework ans SAP’s NWDS

Technical Definition : WebDynpro is a client-independent programming model used for developing sophisticated user interfaces for web based business applications.

History: The name WebDynpro , Dynpro means Dynamic Program it is SAP’s Legacy technology for interactive UI’s.It is to Combine High Interactivity (dynamic GUI) and Zero Installation.

What are the naming conventions to be followed while developing Web Dynpro applications?

Web Dynpro context names should use only the characters A..Z, a..z, 0..9, _ . Digits can be used only from 2nd position. The JAVA naming conventions can be followed but avoid using unicode characters to keep the names simple. However one should avoid using the prefixes wd, WD or IWD since these are the prefixes used during generation of internal coding entities.

Basic Concepts

1. View – is the central logical layout element in the Web Dynpro application.It is responsible for the presentation logic and for the browser layout.

Description of a visible screen area
Contains and lays out controls (aka widgets)
Defines actions (i.e. relevant input on controls by the user), which trigger event handling

2. Controller – active part of web dynpro application,handles the data flow between the model and the view in both directions

Performs event handling
Each component has a component controller
Each view has a view controller
Custom controllers may be added for further structuring

3. Model – is the interface to the back end systm and is responsible for providing data to the entire application.

Represents the data in the backend

4. Component

Reusable UI program package
Mostly contains views, often uses models
Communicates with other components via component interfaces

5. Application

Something runnable (from client application, i.e. web browser)
Identified by URL
Running an application means starting a component, navigating” to an initial view in an initial window.

6. Windows

Single UI unit representing a component’s user Interface/View Composition needed for embedding purposes.

7. Context

A controller contains a context which holds the data. The data flow between the contexts is referred to as context mapping..

Web Dynpro is the SAP NetWeaver programming model for user interfaces and provides support when developing the Web representation of business applications. The Web Dynpro model is based on the Model View Controller paradigm, and has the following features that build on the classic dynpro model:

· Clear separation of business logic and display logic

· Uniform metamodel for all types of user interfaces

· Execution on a number of client platforms.

· Extensive platform independence of interfaces

Structure

In Web Dynpro, each user interface is always made up of the same basic elements (such as UI elements or events triggered by the user). These basic elements are declared using Web Dynpro tools. The event handling is programmed in separate source code areas which are executed automatically at runtime when the event is triggered.

Metamodel Concept

When creating a Web Dynpro application, you use the Web Dynpro tools to describe the properties and functions of the application. The data created in this way is stored in tables as metadata. At a later time, the necessary source code, which is executed at runtime, is created from this metadata. Therefore, the metadata itself is independent of the rendering technique used at runtime.

Graphical Development Tools

To support this declarative concept, the SAP NetWeaver Developer Studio contains a range of Web Dynpro tools. You can therefore generate a large proportion of a Web Dynpro application using the tools provided, without having to create your own source code. This applies to the following parts of the application:

· Data flow between the front end and back end

· Layout of the user interface

· Properties of user interface elements

The Web Dynpro tools enable you to create source text areas manually within generated source texts. These areas are not changed if the source code is regenerated.

Separation of Business Logic and Display Logic

Implementing Web Dynpro enables you to clearly separate business logic and display logic. A Web Dynpro application runs on the front end and has local or remote access to the back end system via a service. This means that the display logic is contained in the Web Dynpro application, while the business logic and the persistence of the business objects run in the back end system. The following options are currently available for connecting Web Dynpro applications and the back end system:

· An interface generated using adaptive RFC, through which BAPIs of an SAP system can be called

· An interface for calling Web services

· A self-generated interface

The source code required for connecting the Web Dynpro application can be generated from a UML definition of the Web Dynpro interface. A UML definition can be imported into the Web Dynpro tools as an XML file.

Implementation of the Model View Controller Paradigm

Every Web Dynpro application is structured according to the Model View Controller paradigm:

· The model forms the interface to the back end system and thus enables the Web Dynpro application access to data.

· The view is responsible for the representation of the data in the browser.

· The controller lies between the view and the model. The controller formats the model data to be displayed in the view, processes the user entries made by the user, and returns them to the model.

The creation of applications using Web Dynpro is structured in Web Dynpro components. The following sections provide a detailed description of the most important parts of a Web Dynpro component.

Prerequisites
SAP NetWeaver Application Server 7.0 for Java is required to use these resources. In most cases, it is sufficient that you have installed Sneak Preview SAP NetWeaver Edition from SDN.

Disclaimer
SAP code or applications samples and tutorials are NOT FOR PRODUCTION USE. You may not demonstrate, test, examine, evaluate or otherwise use them in a live operating environment or with data that has not been sufficiently backed up. You may not rent, lease, lend, or resell SAP code or application samples and tutorials.

Basic & General
Componentization
Backend Access - Model
Designing User Interfaces
SAP Interactive Forms by Adobe
Specials

Basic & General

Creating a Hello World in Web Dynpro Java

This tutorial is a version of the popular “Hello World” program. You will write a very simple Web Dynpro application that places the text “Welcome to Web Dynpro” on the user’s browser.

Creating Your First Web Dynpro Application
This tutorial is more than a Hello World, it demonstrates some basic concepts. It gives you a starting point for handling navigation, mapping contexts and binding data.

The ready-to-use project is available here.

Componentization

Talking about componentization in the Web Dynpro environment, this term can stand for have two different things:
On the one hand developing in a team with Web Dynpro Development Components in the NWDI, on the other hand structuring your Web Dynpro project using Web Dynpro Components inside.

Component-based Development from Database Table to Web Dynpro using NWDI
This tutorial shows how to create a complete application based on database persistence, EJB, Web service and Web Dynpro Java. You will define different types of Development Components (DC) in the SAP NetWeaver Development Infratructure (NWDI) such as Dictionary project, Library project or EJB module project. Finally you will use the Adaptive Web Service Model in a Web Dynpro Java DC to build the user interface.

Web Dynpro Componentization
This tutorial provides a set of local Web Dynpro DCs illustrates how to design component-based Web Dynpro applications using separate Web Dynpro DCs. In a simple application we demonstrate how to embed the visual interface of a Web Dynpro component into a parent component within one single Web Dynpro DC. Another advanced application demonstrates how to apply the model-view-controller (MVC) paradigm on a DC level for logically structuring large-scale Web Dynpro applications. One root component embeds two separate user interface components, both of which use a single model component in referencing mode. The lifecycle of the UI and the model components are managed by the root component. This scenario is based on three separate Web Dynpro DCs.

The ready-to-use Web Dynpro Development Components can be downloaded here.

Note: This Readme describes how to import the local Web Dynpro DCs into the SAP NetWeaver Developer Studio.

Use components in bigger Web Dynpro projects (Wiki)
This section wants to give you some hints on how to migrate from a "one-component-only" application to an application that uses components.

Backend Access - Model

Accessing ABAP Functions using the Adaptive RFC Model
This example demonstrates how to create, implement, deploy and run a basic Web Dynpro application that accesses persistent data from a remote SAP backend system. To read the business data, the application makes use of existing functions in the form of readable BAPIs. The Web Dynpro framework generates for each BAPI that is needed a corresponding Java proxy class. All generated classes define an adaptive RFC model and are treated as part of the Web Dynpro project.

Designing User Interfaces

Designing User Interfaces with Web Dynpro
This tutorial helps you get familar with the different layout options you have to structure UI elements on a view. It explains some standards & guidelines.

The ready-to-use project is available here.

Working with Tables
This tutorial explains the basic functions of the Table UI element, e. g. creating the necessary UI elements, binding the data and mapping the context. Additionally it provides some additional features like sorting, displaying details in a form, calculating the totals and deleting rows.

Creating Trees
This Web Dynpro tutorial teaches you how to construct a recursive and loadable tree in Web Dynpro. It can also be used to understand how to implement a tree structure inside a table using the TreeByNestingTable UI element.

Uploading and Downloading Files
In this tutorial you learn how to download and upload files within Web Dynpro applications running on SAP NetWeaver 7.0 (2004s) by utilizing the new dictionary type Resource and its related Web Dynpro APIs IWDResource and WDResourceFactory. In contrast to the dynamic type modification of a binary context attribute in SAP NetWeaver 04, the new dictionary simple type Resource yields a fully declarative, zero coding data transport of download and upload resources between Web Dynpro client and controller context on server side.

The ready-to-use project is available here.
Additionally there is an initial project (starting point) here.

How to Use Web Dynpro Popup Menus
You learn how to add a popup menu to a Tray UI element, how to declare menu item events and how to disable or enable menu action items by programmatically disabling or enabling the associated action objects within action event handlers.

The ready-to-use Web Dynpro DCs are available here.

Note: This Readme describes how to import the local Web Dynpro DCs into the SAP NetWeaver Developer Studio.

Using Gantt/Network UI Element (Wiki)
To run a JNet or a JGantt in a Web Dynpro for Java application, you have to follow the steps described below. This example does not describe how to build the xml file for a Gantt or for a Network, it focuses on the Web Dynpro part. This example explains how to bind a Gantt UI element and its data source to the context. This works exactly the same way for the Network UI element.

SAP Interactive Forms by Adobe

eLearning Series
The 11-part series on SAP Interactive Forms by Adobe, produced by the SAP NetWeaver RIG team, provides an overview of forms technology, its integration points with SAP NetWeaver Application Server, technical components and architecture, use cases, how to design and run a form, and much more.

Relevant parts for Web Dynpro Java are:

Specials

Exporting Table Data Using On-Demand Streams (Wiki)
How to download data from a table using the on-demand resource streaming technique in NetWeaver 7.0 combined with a ToolBarLinkToURL-UI-Element to open the Excel resource instantly. This technique does not require opening a Web Dynpro popup window with a LinkToURL-UI-element pointing to a cached Excel resource. This sample application is implemented in two separate components: a reusable service component for Excel export and a client component displaying table data.

Developing an International Web Dynpro Application
In this tutorial, the task is to develop an international Web Dynpro application that is available in English and German. As an example, we will use a car rental application that displays different texts, depending on the booking. You will also learn to use Simple Types and Message Pool.

SAP Lock objects

2011-06-15T04:51:00.001-07:00

Lock Objects The R/3 System synchronizes simultaneous access of several users to the same data records with a lock mechanism. When interactive transactions are programmed, locks are set and released by calling function modules (see Function Modules for Lock Requests). These function modules are automatically generated from the definition of lock objects in the ABAP Dictionary.

Structure of a Lock Object The tables in which data records should be locked with a lock request are defined in a lock object together with their key fields. When tables are selected, one table (the primary table) is first selected.

Further tables (secondary tables) can also be added using foreign key relationships (see also Conditions for Foreign Keys). Lock Arguments The lock argument of a table in the lock object consists of the key fields of the table.

The lock argument fields of a lock object are used as input parameters in the function modules for setting and removing locks generated from the lock object definition. When these function modules are called, the table rows to be locked or unlocked are specified by defining certain values in these fields. These values can also be generic. The lock argument fields therefore define which subset of the table rows should be locked.

The simplest case of a lock object consists of exactly one table and the lock argument of the table is the primary key of this table. Several tables can also be included in a lock object. A lock request therefore can lock an entire logical object, and not only a record of a table. Such a logical object can be for example a document comprising an entry in a header table and N entries in a position table. Locks can also be set from programs in other systems with the corresponding interfaces if the lock object was defined with RFC authorization.

A lock mode can be assigned for each table in the lock object. This mode defines how other users can access a locked record of the table. Table SFLIGHT in the flight model contains all the scheduled flights of a carrier. Field SEATSMAX contains the number of seats available. Field SEATSOCC contains the number of seats already booked. If a booking is made for a customer (by a travel agency or sales desk), you must check whether there are enough seats available. The number of seats booked is incremented when the booking is made.

This mechanism must ensure that two sales desks do not make the same booking at the same time and that the flight is not overbooked. This can be done by creating lock object ESFLIGHT. Only the table SFLIGHT must be included in this lock object. The flight can then be locked (with the function modules generated from the lock object) when booking. If another sales desk also wants to book seats for this flight, the lock will prevent the flight from being overbooked.

Example for Lock Objects When booking flights (see Flight Model) it is important to prevent flights from being overbooked. For this reason, you have to lock the particular flight as well as all the bookings existing for this flight during processing. You can do this with lock object E_BOOKING. The flights are recorded in table SFLIGHT and the bookings for the flights in table SBOOK.

The two tables are linked with a foreign key. Lock object E_BOOKING must therefore contain table SFLIGHT as primary table and table SBOOK as further table. The lock argument of table SFLIGHT thus contains the fields MANDT, CARRID, CONNID, and FLDATE. The lock argument of table SBOOK thus contains the fields MANDT, CARRID, CONNID, FLDATE, BOOKID and CUSTOMID. Select exclusive lock mode, that is the locked data can only be displayed and edited by one user. When the lock object is activated, the following function modules are generated from its definition: ENQUEUE_ E_BOOKING (set locks) ENQUEUE_ E_BOOKING (release locks) These function modules can now be linked to ABAP programs. The following example shows how function module ENQUEUE_ E_BOOKING is called. With this call, flight LH 400 on Nov. 29,1998 is exclusively (lock mode E) locked in table SFLIGHT together with all the bookings entered in table SBOOK for this flight (since the initial value 0 is transferred for BOOKID and CUSTOMID). The lock is sent to the update program (_SCOPE = ‘2’). If there is a lock conflict, another attempt is made to set the lock after a certain time (_WAIT = ‘X’). The set locks can be removed by calling the function module DEQUEUE_E_BOOKING as follows: The existing exclusive lock entries for flight LH 400 are deleted in table SFLIGHT and the bookings for this flight are deleted in table SBOOK. The request to delete the lock entries is passed on to the update program (_SCOPE = ‘3’). Function Modules for Lock Requests Activating a lock object in the ABAP Dictionary automatically creates function modules for setting (ENQUEUE_<lock object name>) and releasing (DEQUEUE_<lock object name>) locks.

The generated function modules are automatically assigned to function groups. You should not change these function modules and their assignment to function groups since the function modules are generated again each time the lock object is activated. Never transport the function groups, which contain the automatically generated function modules. The generated function modules of a lock object could reside in a different function group in the target system.

Always transport the lock objects. When a lock object is activated in the target system, the function modules are generated again and correctly assigned to function groups. Parameters of the Function Modules Field Names of the Lock Object The keys to be locked must be passed here. A further parameter X_<field> that defines the lock behavior when the initial value is passed exists for every lock field <field>. If the initial value is assigned to <field> and X_<field>, then a generic lock is initialized with respect to <field>. If <field> is assigned the initial value and X_<field> is defined as X, the lock is set with exactly the initial value of <field>.

Parameters for Passing Locks to the Update Program A lock is generally removed at the end of the transaction or when the corresponding DEQUEUE function module is called. However, this is not the case if the transaction has called update routines. In this case, a parameter must check that the lock has been removed. Parameter _SCOPE controls how the lock or lock release is passed to the update program (see The Owner Concept for Locks). You have the following options: · _SCOPE = 1: Locks or lock releases are not passed to the update program. The lock is removed when the transaction is ended. · _SCOPE = 2: The lock or lock release is passed to the update program. The update program is responsible for removing the lock. The interactive program with which the lock was requested no longer has an influence on the lock behavior. This is the standard setting for the ENQUEUE function module. · _SCOPE = 3: The lock or lock release is also passed to the update program. The lock must be removed in both the interactive program and in the update program. This is the standard setting for the DEQUEUE function module. Parameters for Lock Mode A parameter MODE_<TAB> exists for each base table TAB of the lock object. The lock mode for this base table can be set dynamically with this parameter. The values allowed for this parameter are S (read lock), E (write lock), X (extended write lock), and O (optimistic lock). The lock mode specified when the lock object for the table is created is the default value for this parameter. This default value can, however, be overridden as required when the function module is called. If a lock set with a lock mode is to be removed by calling the DEQUEUE function module, this call must have the same value for the parameter MODE_<TAB>. Controlling Lock Transmission Parameter _COLLECT controls whether the lock request or lock release should be performed directly or whether it should first be written to the local lock container. This parameter can have the following values: · Initial Value: The lock request or lock release is sent directly to the lock server. · X: The lock request or lock release is placed in the local lock container. The lock requests and lock releases collected in this lock container can then be sent to the lock server at a later time as a group by calling the function module FLUSH_ENQUEUE. Whenever you have lock mode X (extended write lock), locks should not be written to the local lock container if very many locks refer to the same lock table. In this case, there will be a considerable loss in performance in comparison with direct transmission of locks. Behavior for Lock Conflicts (ENQUEUE only) The ENQUEUE function module also has the parameter _WAIT. This parameter determines the lock behavior when there is a lock conflict. You have the following options: · Initial Value: If a lock attempt fails because there is a competing lock, the exception FOREIGN_LOCK is triggered. · X: If a lock attempt fails because there is a competing lock, the lock attempt is repeated after waiting for a certain time. The exception FOREIGN_LOCK is triggered only if a certain time limit has elapsed since the first lock attempt. The waiting time and the time limit are defined by profile parameters. Controlling Deletion of the Lock Entry (DEQUEUE only) The DEQUEUE function module also has the parameter _SYNCHRON. If X is passed, the DEQUEUE function waits until the entry has been removed from the lock table. Otherwise it is deleted asynchronously, that is, if the lock table of the system is read directly after the lock is removed, the entry in the lock table may still exist. Exceptions of the ENQUEUE Function Module · FOREIGN_LOCK’: A competing lock already exists. You can find out the name of the user holding the lock by looking at system variable SY-MSGV1. · SYSTEM_FAILURE: This exception is triggered when the lock server reports that a problem occurred while setting the lock. In this case, the lock could not be set. If the exceptions are not processed by the calling program itself, appropriate messages are issued for all exceptions. Reference Fields for RFC-Enabled Lock Objects The type of an RFC-enabled function module must be completely defined. The parameters of the generated function module therefore have the following reference fields for RFC-enabled lock objects:

WRITE OPTIMISED DSO

2011-03-22T04:20:00.001-07:00

Write Optimized DSO
The concept of Write Optimized DSO was introduced in BI-7.0. Write Optimized DSO unlike Standard DSO has only one relational table, i.e. Active Table and moreover there is no SID generated in Write Optimized DSO, and hence loading the data from Data Source to Write Optimized DSO takes less time and acuires less disk space.
Business Case :
Require Data storage for storing detailed level of data with immediate reporting or further update facility. No over write functionality required.
Limitation of Standard DSO
-          A standard DSO allows to store detailed level of information, However, activation process is mandatory.
-          Reporting or further update is not possible until activation is completed.

Write Optimized DSO - Properties
-          Primarily designed for initial staging of source system data
-          Business rules are only applied when the data is updated to additional Info Providers.
-          Stored in at most granular form
-          Can be used for faster upload
-          Records with the same key are not aggregated ,But inserted as new record, as every record has new technical key
-          Data is available in active version immediately for further Processing
-          There is no change log table and activation queue in it.
-          Data is saved quickly.
-          Data is stored in it at request level, same as in PSA table.
-          Every record has a new technical key, only inserts.
-          It is Partitioned on request ID (automatic).
-          It allows parallel load, which saves time for data loading.
-          It can be included in Process chain, and we do not need activation step for it.
-          It supports archiving.
Write-Optimized DSO - Semantic Keys
Semantic Key identifies error in incoming records or Duplicate records .
Semantic Keys protects Data Quality such that all subsequent Records with same key are written into error stack along with incorrect Data Records.
To Process the error records or duplicate records , Semantic Group is defined in DTP.
Note : if we are sure there are no incoming duplicate or error records, Semantic Groups need not be defined.

Write Optimized DSO-  Data Flow
1.     Construct Data Flow model.
2.     Create Data source
3.     Create Transformation
4.     Create Info Package
5.     Create DTP
Write-Optimized-Settings
If we do not check the Check Box "Do not Check Uniqueness of Data ", the data coming from source is checked for duplication, i.e, if the same record (semantic keys) already exist in the DSO, then the current load is terminated.
If we select the check box , Duplicate records are loaded as a new record. There is no relevance of semantic keys in this case.

When Write Optimized DSO is Recommended ?
-          For faster data load., DSOs can be configured to be Write optimized
-          When the access for Source system is for a small duration.
-          It can be used as a first Staging layer.
-          In cases where delta in Data Source is not enabled, we first load data into Write Optimized DSO and then delta load can be done to Standard DSO.
-          When we need to load large volume of data into Info Providers, then WO DSO helps in executing complex transformations.
-          Write Optimized DSO can be used to fetch history at request level, instead of going to PSA archive.
Write Optimised DSO - Functionality
-          It contains only one table, i.e. active data table (DSO key: request ID, Packet No, and Record No)
-          It does not have any change log table and activation queue.
-          Every record in Wrtite Optimized DSO has a new technical key, and delta in it works record wise.
-          In Wrtite Optimized DSO data is stored at request level like in PSA table.
-          In Wrtite Optimized DSO SID is not generated.
-          In Wrtite Optimized DSO Reporting is possible but it is not a good practice as it will effect the performance of DSO.
-          In Wrtite Optimized DSO BEx Reporting is switched off.
-          Wrtite Optimized DSO can be included in Info Set or Multiprovider.
-          Due to Wrtite Optimized DSO performance is better during data load as there is no Activation step involved. The system generates a unique technical key
-          The technical key in Wrtite Optimized DSO consists of the Request GUID field (0REQUEST), the Data Package field (0DATAPAKID) and the Data Record Number field (0RECORD).
Write-Optimized DSO-Points to Remember
Points to Remember :-
-          Generally Write Optimized DSO is not prefered for reporting, but If we want to use it for reporting then it is recommended to defina a semantic in order to ensure the uniqueness of the data.
-          Write-optimized DSOs can force a check of the semantic key for uniqueness when data is stored.
-          If this option is active and if duplicate records are loaded with regard to semantic key, these are logged in the error stack of the Data Transfer Protocol (DTP) for further evaluation.
-          If we need to use error stack in our flow then we need to define the semantic key in the DSO level.
-          Semantic group definition is necessary to do parallel loads.
Write-Optimized DSO - Reporting
If we want to use write-optimized DataStore object in BEx queries(not preferred):
it is recommended to
1.     Have a semantic key and
2.     Ensure that the data is unique.
Here the Technical key is not visible for reporting, so it looks like any regular DSO

Write-Optimized DSO-Useful OSS Notes
-          OSS 1077308   : In a write-optimized DSO, 0FISCVARNT is treated as a key, even though it is only a semantic key.
-          OSS 1007769 : Parallel updating in write-optimized DSO
-          OSS 966002    : Integration of write-opt DSO in DTP error stack
-          OSS 1054065 : Archiving supports.

SAP FEW Questions with Answers

2011-03-22T00:15:00.000-07:00

SAP entertainment

3.X Hierarchy Loading for Purchase Cube in SAP BI

Results

Identify Query Version 7.x/3.x and Query Transport Request Details

Applies to:

Summary

Introduction

Business Scenario

Writing a program

Sample Code

Remodeling of Info Providers

How to execute APD in Process Chain

Summary

Information and Instruction

Step By Step Solution

How to use BI queries in Visual Composer

Summary

Step By Step Solution

Use of customer exit Variables in BI

Enhancing the standard datasources in BI 7.0

Migration of BI 3.5 Modeling to BI 7.x

DB Connect Usage in SAP BI 7.0

Introduction

Process Description

Results

Step-by-Step tutorial to upload Master Data from Flat File (SourceSystem) to InfoObjects (Master data table)

Data Services within the SAP BI staging process

Enable the selection options for the data source fields (more than one field at a time) in the extract structure through customized program

Enable the selection options for the data source fields (more than one field at a time) in the extract structure through customized program

How to Enhance Standard Datasource to be used in BI System

How to Enhance Standard Datasource to be used in BI System

Decision making process type in Process chains

Decision making process type in Process chains

Decision making process type in Process chains

2 comments:

SAP FI Transaction Code Part -2

SAP Smartforms Development Techniques

SAP-BODS integration using IDOCS

By Praveen Addanki, HCL-AXON

1.Introduction:

2.SAP Configuration settings:

SAP-BODS Integration using BAPI

1. Introduction:

2. BAPI Call:

3. Importing the BAPI:

4. Processing the BAPI:

6. Calling RFC’s enabled Function Module:

SAP BUSINESS OBJECTS

[edit]Legal

[edit]Timeline

[edit]Products

1 Working with Business Object in our programs

1.1 To create instance of a BO

1.2 Container

1.2.1 Lets take an example to check what Container is

1.2.2 Some common macros defined in include <CNTN01> for working with Containers

1.3 Calling a BO Method/Attribute in report programs

1.4 To trigger an Event of BO

SAP WEBDYNPRO

Structure

Metamodel Concept

Graphical Development Tools

Separation of Business Logic and Display Logic

Implementation of the Model View Controller Paradigm

Basic & General

Componentization

Backend Access - Model

Designing User Interfaces

SAP Interactive Forms by Adobe

Specials

SAP Lock objects

WRITE OPTIMISED DSO

SAP FEW Questions with Answers

how to find out what TCODE that is used by the ABAP Program

How To Merge Several Transport Requests into One Transport Request

Restrict Local Object Access

Transporting Table Entries From One Client To Another Client

How To Create Program Package In SAP