Quantcast
Channel: SCN : Document List - SAP Business Warehouse
Viewing all 1574 articles
Browse latest View live

Adding New info object to info cube Which have data.

$
0
0

This will be simple one but may be helpful..

 

My cube have data as shown below.

 

My cube designed screen.

 

Now am planned to add 0customer to Entity Dim.

Go to RSA1, Administration-->Re modelling tab,

Take you to the below screen.

 

 

Give the remodeling rule name and target on which you want add info obj. click on create, its gave a pop uo box to enter description.enter the required description and click on transfer. in below screen click on + symbol(add an operation to list)

 

 

Click on that , Below screen will popup.

 

 

here we can see all options which we want add/delete, for adding we not pass values using 4 options as show above. time being am using constant value.

after filling the required options here, click on Transfer. next save and Click on check. there is an option impact analysis, by adding/deleting if we want know the any impact, clik on it , it shows you.

After this check options , you can schedule, it will adjust the all necessary changes in cube dimension.

 

Next screen will come with start later and start immediately. choose as you want. but choosing here as start immediately.

 

after choosing immediately,

 

you can see below message, then go with monitor or job log.

as we see in pic. after the success of this job, you can see added filed in your target.

 

See my cube have added info obj in IC_EVA3.

By adding new obj, DTP was deactivated, so make it active and use usual.

My doc - purpose is too add info object to target which have data.

 

Information:

Remodeling purpose is just add or delete info object from cube which have data.

For added info object need historical data then drop whole data from cube and reload from source.

If you won't need histocal data then droping data from cube was not needed. Thru delta loads now onwards data will be filled for added info object.

 

Thank you all.


SAP NetWeaver BW Application Lifecycle Management (ALM)

$
0
0
eim301_pic1.JPG

Upgrade/Migration/Implementation/Systemcopy -
SAPNetWeaver Business Warehouse 7.3 and Higher

On this page, you can find various information about upgrade, migration and implementation of SAPNetWeaver BW 7.3 and higher, including the enablement for SAP HANA. For information about lower releases, see  SAP NetWeaver Business Warehouse? 7.0 and lower - exclusively.

 

Content

 

eim300_pic3.JPG

SAP Business Intelligence Architecture

With the new possibilities in SAP NetWeaver BW 7.30, In-Memory technologies SAP BWA and SAP HANA, as well as further updates to the SAP BusinessObjects platform and SAP BusinessObjects Data Services, this must-read presentation illustrates synergies in combination with the SAP Business Intelligence solution portfolio. Sybase core technologies, such as Replication, Databases and Mobility, can be used very efficiently together with the existing SAP BusinessObjects product portfolio.

 

eim301_pic2.JPG

BW Technical and Functional Upgrade

 

BLOG: Software Update Manager (SUM): introducing the tool for software maintenance

BLOG: Good News - Easier Modeling of the SEM Add-On in Solution Manager

 

ASU Toolbox (incl. BW Specific Content) and BW Upgrade pre/post Task List
With the ASU (application specific upgrade) toolbox, customers get one single truth for all pre/post upgrade steps regarding the technical upgrade to SAP NetWeaver BW 7.0x  and all following releases.
More detailed information about the ASU toolbox can be found in note 1000009. This tool has been available since 2008 (see the TechEd Presentation and the new Upgrade to SAP NetWeaver BW 7.30 Presentation) has been enhanced and now allows application specific and technical resources to work together for a successful upgrade to SAP NetWeaver BW 7.30
With SAP NetWeaver 7.30 JAVA, the Functional Unit Configuration UI (former CTC BI-JAVA Template) is available.
New:
Together with the BW Housekeeping Task List,there are also additional Task Lists available to simplify preparation of the application-specific part.
Implement the following SAP Note to enable usage of task list SAP_BW_BEFORE_UPGRADE via transaction STC01
(contains manual report ZNOTE_1734333_PRE_70x/ZNOTE_1734333_PRE_70x, and NO automated steps applied with SNOTE)

 

The Presentation Teched 2012 - Session EIM301  illustrates the complete Upgrade process.

 

Immediately after the upgrade to SAP NetWeaver BW 7.3x Note 1720495 (Invalid deimplementation of obsolete notes by SNOTE tool)should be applied.

 

With the release of SAP NetWeaver BW 7.30 new and innovative capabilities have been added to SAP's EDW premium solution. SAP NetWeaver BW 7.30 as the backbone for a successful usage of SAP BusinessObjects Platform and SAP Business Warehouse Accelerator - BWA is the heart of the SAP Business Intelligence Architecture. The updated presentation SAP NetWeaver 7.0x - Upgrade to SAP NetWeaver 7.30 ABAP BW (full version with complete technical details) provided you with must-know delta information to quickly and effective upgrade to SAP NetWeaver 7.30 BW including existing information from the resources of this page and the updates for SAP NetWeaver 7.30 EhP1 (7.31).

 

See also the changes to the existing BEx Versions 3.5 and 7.x after Upgrade to NetWeaver BW 7.30 or 7.31
Be sure to read these Notes prior to the technical Upgrade in order to prevent any unwanted incompatibilities or unforeseen changes.

 

eim301_pic3.JPG

BW ABAP and BI-JAVA Installation

The Software Provisioning Manager 1.0 (SWPM) can be used to install all SAP NetWeaver 7.30 based instances onwards.

 

See SAP NetWeaver BW Installation/Configuration (also on HANA). This document also includes the complete SAP NetWeaver BW basis customizing settings, together with an example configuration of the System Parameter. The guidance raises no claim to completeness.
New: It is now possible to install the ABAP CI as well on the HANA Appliance!
     Overview - SAP HANA and SAP NetWeaver AS ABAP o... | SAP HANA

 

See all SAP First Guidance Documents here -BW on SAP HANA First Guidance Collection

 

With the release of SAP NetWeaver 7.30 all previous J2EE stacks are now synchronized in one platform. BI JAVA 7.30 is still available with the usage type BI-JAVA to connect to an existing SAP NetWeaver BW 7.30 stack for the classical usage of BEx Web or the native dashboards (former Xcelsius). The presentation SAP NetWeaver 7.30 – BI JAVA Implementation shows the new SAP NetWeaver 7.30 installation and configuration options with the functional unit configuration UI (former CTC BI-Java Template) All informations are also valid vor SAP NetWeaver 7.30 EhP1 (7.31)

 

SAP NetWeaver 7.0 - Deinstalling Java Add-In (also valid for SAP NetWeaver 7.30 JAVA Add-In)
The separation of the doublestack (ABAP and JAVA in one instance) into two separate stacks is a SAP recommendation. An option available since SAP NetWeaver BW 7.0 is the deinstallation of the Java Add-In with SAPInst. This presentation provides details and guidance about the process to prepare for upgrade to SAP NetWeaver BW 7.30, concentrating on the ABAP stack.

 

As a successor for most scenarios, we offer the combined export of the Java system, deinstallation of the Java Add-In and installation of a new Java system using the dual-stack split tool available as part of the SL toolset 1.0 (SP5). For more information, see "Dual-Stack Split".

 

If you are running SAP NetWeaver 7.30 JAVA Add-In you can use the software provisioning manager 1.0 (SWPM) as part of the SL toolset for the deinstallation process, as this always contains the latest software components (Note 1680045). Note that the dual split process is not supported for SAP NetWeaver 7.30 systems (Note 1655335)

 

With SAP NetWeaver 7.3x JAVA the Functional Unit Configuration UI (former CTC BI-JAVA Template) is available

 

In Advance check the WebAS/SSO Settings after the Upgrade to NetWeaver 7.3x. The settings are almost identical to NetWeaver BW 7.0x

 

eim300_pic1.JPG

Migration to BW on HANA

DMO is an option of SUM (Software Update Manager) for a combined update and migration: update an existing SAP system to a higher Software Release and migrate to SAP HANA database including the unicode conversion of the source database. The procedure is only available for systems based on AS ABAP, hence the executable SAPup is used in background. DMO migrates from an existing relational database type (“anyDB”) to SAP HANA. Software Update Manager (SUM) is the tool for system maintenance: Release upgrades, EHP implementation, applying SP stacks.

 

 

To reduce downtime for your production landscape, one of the recommended migration paths of SAP NetWeaver Business Warehouse (SAP NetWeaver BW) to SAP NetWeaver BW on SAP HANA comprises a system copy of your SAP NetWeaver BW system. The system copy procedure of SAP NetWeaver BW systems and landscapes is complex for a number of reasons however. A large number of configuration settings are involved for example (such as connections and delta queue handling for data loading), as well as system copy scenarios of SAP NetWeaver BW (each with different landscape aspects) that have to be handled as part of every system copy, regardless of whether the system copy is part of the migration to SAP HANA or you want to perform regular system copies of your SAP NetWeaver BW landscape.

 

To achieve this, SAP NetWeaver Landscape Virtualization Management offers preconfigured "task lists" used by the ABAP task manager for lifecycle management automation.
You can also enable SAP NetWeaver BW powered by SAP HANA to “go productive” with parallel operation of your existing production system, both connected to the same back-end systems. This is achieved with a special and unique automated solution for delta queue cloning and synchronization on production systems.
SAP Note 886102 (SMP login required) thus becomes obsolete. Using the post-copy automation for SAP NetWeaver BW (BW PCA) in the migration process of SAP NetWeaver BW to SAP NetWeaver BW on SAP HANA, this process can be shortened by weeks and becomes easier, faster and more reliable.

 

The Presentation Teched 2012 - Session EIM300  illustrates the Migration to BW on HANA from an end-to-end perspective.

 

 

eim301_pic5.JPG

BW System Copy

 

Since Release 7.30 SP05, it is now possible to perform a heterogenous system copy (incuding unicode migration) to migrate existing systems based on SAP NetWeaver BW 7.30 SP05 and higher to SAP NetWeaver BW on HANA (HDB) based systems.
With this major step forward, a new procedure called "Post Copy Automation (BW PCA)" now supports customers with what can often be complex post-steps before and after the homogenous/heterogenous BW system copy. This presentation is the delta information to the existing document "SAP NetWeaver 7.0 - BW Systemcopy ABAP" shown above. The technical Improvements with the leaner data model provides advantages with BW on HANA too.
To ease this generic step of BW system copy, a new procedure called "BW Post Copy automation (BW PCA)" is available, which supports customer now in the complex pre and post steps during the homogeneous/heterogeneousBW system copy (information from the SAP ALM group) procedure.
Please note that these procedure can be used independently from your BW and Database Version starting fromNetWeaver 7.0x

 

We distinguish between two use cases explained in the FaQ for BW-PCA:
- initial copy based on an existing original BW system and connected BW source systems
  Task Lists - SAP_BW_COPY_INITIAL_PREPARE (BW systems only) andSAP_BW_BASIS_COPY_INITIAL_CONFIG
- refresh of an existing system based on an existing BW system and connected BW source systems
  Task List - SAP_BW_BASIS_COPY_REFRESH_CONFIG

 

The following Notes are the pre-requisites for the use cases (included in 7.01 SP14 and higher):
Updating to the minimum level of the mentioned Support Stacks is recommended to minimize the manual effort.

 

For both cases the BW-PCA Tasklists support the Customer together with the software provisioning manager 1.0 (SWPM) in these software lifecycle management tasks. BW-PCA is embedded in the SAP NetWeaver Landscape Virtualization Management

 

eim301_pic4.JPG

 

BW Housekeeping Tasks

 

In this session, you will learn about various housekeeping activities that should be part of the operational concept of your Enterprise Data Warehouse. These housekeeping activities will support you in removing unwanted and unneeded data as well as unused metadata. Scheduling these activities regularly in the system will ensure optimum utilization of system resources while at the same time increasing the overall system performance.

 

New: SAP First Guidance - BW Housekeeping and BW-PCA

 

(contains manual steps ZNOTE_1829728_PRE_70x/ZNOTE_1829728_PRE_73x, and automated steps applied with SNOTE)
The newly released Housekeeping Task List (Pre/Post Steps) allows you to automate mandatory tasks prior to upgrade/migration with DMO to ensure the quality of the migration process and the health of your BW System.

 

Apply the following Notes in advance and run the tasks in advance to ensure smooth implementation of the BW Housekeeping Task List.
(contains manual steps ZNOTE_1767420, and automated steps applied with SNOTE)
To solve the problem with the endless loop on the last task, apply the following Note:

 

eim300_pic2.JPG

Event Presentations

 

Navigating and Networking at SAP TechEd => Live from TechEd Amsterdam, Replay from 05.11.2013, 18.00 Uhr

 

 

eim301_pic6.JPG

 

References/Experiences/DSAG

This is a collection of ressources from the SAP SCN Network and it´s content is not reflecting the findings from this Document of future Upgrade and Enhanchements.
See how the german customer Kärcher upgraded their BW System Landscape (Three System plus Sandbox) within 8 weeks including BI-IP and BIA. It is still a good reference from the project perspective

 

See Dr. Berg's Upgade to 7.30 Experience. This is a overview Presentation based on 2011 findings.
See the Doc - SAP BW 7.3 Promising Features This is a very nice overview based on the 2012 findings.
Recent Blog - SAP BW 7.3 Upgrade Issues and Solutions is based on 2013 findings, esspecially application side.
DSAG Forum: "Upgrade NetWeaver BW 7.3x" => (DSAG-ID requested) share you experience with other DSAG members.

 

SAP BW 7.3: How to trigger BW process chains from ECC

$
0
0

In this document I will comment how to trigger BW process chain from ECC, for example to update a particular report. I hope it can help to someone who has to perform this process in the future.

 

According to the requirements, the user - after executing certain transactions in ECC - should be able to trigger a load in BW and see the reports updated with this new information.

 

To do this, we will create an ad-hoc transaction in ECC (ZBW_UPDATE_REPORTS) with an associated program (ZBW_TRIGGER_EVENT). A dynpro where the user will be able to select the business area he wants to update will be displayed in this transaction. After selecting this area, "Execute" button is pressed and the program is launched. This program calls a BW function (ZFM_TRIGGER_EVENT) passing as parameter the event associated with the selected area. Finally, this function will be responsible for triggering the event (ZECC_EVE01) and starting to run the appropriate load chain (TR_DT).

 

ECC SIDE

 

Step 1. Create the transaction in SE93. This transaction will have associated the program that we will create in the next step.

1.png


2.png

 

Create Dialog Transaction:

3.png

 

Step 2. Create an executable program in t-code SE38. In this transaction the user will select the Area of reports that he wants to update.

4.png

 

Global Data:

5.png

 

PBO-Modules:

6.png

 

PAI-Modules:

7.png

 

FORM-Routines:

8.png

Note: SLBWD200 is the name of our SAP BW system.

 

Fill the Text Symbols and Selection Texts:

9.png


10.png

 

Step 3. The dynpro looks like this:

11.png

 

BW SIDE

 

Step 4. Create an event in tcode SM64 for each of the different loads we want throw. In our case: ZECC_EVE01 (for Treasury area) and ZECC_EVE02 (for Consolidation area).

12.png

 

Step 5. We associate to each chain the corresponding event. In our example we plan the  load chain of Treasury (TR_DT) to run after event: ZECC_EVE01.

13.png

Note: it is important to plan and activate the chain and check “Periodic job”.

 

Step 6. Create the function module (in our case ZFM_TRIGGER_EVENT). This function will call the function  BP_EVENT_RAISE which will raise the event received as parameter.

14.png

 

Import:

15.png

 

Step 7. Finally, just after executing the transaction from ECC side, the BW Process Chain is thrown:

16.png

 

17.png

 

Best regards,

Carlos

Schedule a Process chain on specific weekdays

$
0
0

Requirement:


In a week, process chain should load the records only on specific weekdays ? How to schedule it?

Here in this example, the chain should run only on wednesday  and thursday of a week?


Solution :


Here there is no need of creating an ABAP program or a factory calender. A simple formula in the Process chain will suffice the above requirement.


By this we can minimize the dependency of ABAP. Also we are not going to create a factory calender which is specifically to this particular process chain.


If there is any other chain which needs to be schedule only on Friday and Saturday, again we need to go for creating a factory calender. So instead a simple formula and the Decision Process type will solve this type requirement.


Step by step Navigation:


1. Go to RSPC, click on Create. Give the technical name & Description of the process chain  and click on Continue as highlighted below.

2014-01-17 11_13_16-Process Chain Maintenance Planning View.png

2 . Create a start variant for the process chain. Click on Create. Give the technical name & Description of the Start Variant and click on Continue.

2014-01-17 11_14_17-Process Chain Maintenance Planning View.png

3. Schedule the process chain for daily execution as shown below. Save the variant

2014-01-17 11_16_25-Start Time.png

4. Now the start variant is created. Click on Continue.2014-01-17 11_18_04-Process Chain Maintenance Planning View.png

5. Now drag & drop the Decision process type which is under General services as highlighted below.

2014-01-17 11_18_29-Process Chain Maintenance Modified Version_ PC for Wed & Thur.png

6. After that click on Create

2014-01-17 11_19_07-Process Chain Maintenance Modified Version_ PC for Wed & Thur.png

7. Give the technical name & description for the Decision Process type and Click on Continue.

2014-01-16 11_48_55-Process Chain Maintenance Modified Version_ PC chain test.png

8. The following Screen will appear. Click on Create under Formula column.

2014-01-16 11_53_20-Process Maintenance_ Decision Between Multiple Alternatives.png

9. Here  in this example the chain has to run on every Wednesday and Thursday of a week.

For this purpose, use the system variable " SYST-FDAYW "

 

The formula should look as below:
2014-01-16 11_55_33-Form.png

To schedule for any weekday, you can refer :


 

SYST-FDAYW0Sunday
SYST-FDAYW1Monday
SYST-FDAYW2Tuesday
SYST-FDAYW3Wednesday
SYST-FDAYW4Thursday
SYST-FDAYW5Friday
SYST-FDAYW6Saturday


Then Check the formula and click on Back button (F3).


10.  Following screen will appear. Here we have to specify the event. Click on the search button under the Event column as shown below.

2014-01-16 11_57_44-Process Maintenance_ Decision Between Multiple Alternatives.png

11.  Select the OPTION 02. This will make the chain to execute successfully only on WED and THUR based on the defined formula and click on check and save.
2014-01-16 12_00_28-Event Selection.png

12.  Finally the formula should look as below.

2014-01-16 12_01_01-Process Maintenance_ Decision Between Multiple Alternatives.png

13.  The Process chain is created. You can build the remaining as per your data flow.

2014-01-17 12_27_48-Process Chain Display Active Version_ PC chain test.png

 

This chain is a daily schedule. But it will run only on Wednesday and Thursday. Remaining days the chain will fail at the Decision Process type. It wont cause any issues.


** Feedback & Suggestions are welcome. Thanks.


-- KRPK


User ID changes in SAP BW

$
0
0

1. Purpose of Development

The User ID Changes done for Harmonization of User ID project will have a direct impact on all BW users who has created Queries, Workbooks or Settings for Information Broadcasting. This development is for updating the Old User IDs with the New User IDs in the relevant tables.

Reasons for this Impact are explained below.


Queries:


Some queries are visible only to some users or Queries created by user cannot be changed or displayed by other users:

  

    This is because of restriction in the authorization object S_RS_COMP1. This can be solved by changing the values of RSOWNER field in RSZCOMPDIR table.

Workbooks:


  1. 1. When a workbook is created and saved it will be saved in the Favorites of the User.
  2. 2. If the user assigns it to the role, then the other user with this role will have the complete access to this workbook.
  3. 3. If the user did not assign this to the role, then we can copy the favorites of the old user to make the workbook accessible. All the favorites are stored in the table SMEN_BUFFC.
  4. 4. To copy the favorites we can either change the contents of the above table or use the regular way of downloading and uploading the favorites.


  Information Broadcasting:

 

When a setting for the Information broadcasting is created, a background job with the user name will be created and ABAP program RSRD_BROADCAST_STARTER will be triggered with the same user name. This program will access the table for the authorization user mentioned in the table RSRD_SETT_NODE_A.

       Due to this process, we have to change the user in the background job and the authorization user. Background user can be changed using TBTCP and the authorization user can be changed in the table RSRD_SETT_NODE_A.

 

Before doing the changes in the user ID we will have to implement the above mentioned changes so that there is not much effect on BW users after their ids are changed. We will have to design ABAP programs accordingly so that the required changes could be done in the standard tables mentioned above. Logic which needs to be implemented is discussed below.


2. Program Logic

As per the cases given above we have different logics to be implemented for smooth processing of user id changes.


Changing the created user ID of queries:

  • A file with mapping between Old User IDs and New User IDs should be maintained.
  • Upload this file in to the internal table.
  • Select all the entries from the RSZCOMPDIR table where the Old User IDs from the file is equal to the RSOWNER field data.

    

 

 

  • Overwrite the Old User IDs with the New User IDs available in the file in the table RSZCOMPDIR table.

 

Updating the user ID for Information Broadcasting :

  • A file with mapping between Old User IDs and New User IDs should be maintained.
  • Upload this file in to the internal table.

    

Updating Table RSRD_SETT_NODE_A:

 

  • Select all the entries from the RSRD_SETT_NODE_A table where ID field is equal to ‘DI_AUTH_USER’.

 

 

 

  • Update the value in the field VALUE with the New User ID which will be available from the file.

 

Updating Table RSRD_SETTING:

 

  • Select all the values from RSRD_SETTING table.
  • Update the fields OWNER and LASTCHANGEBY with the New User IDs.

 

 

 

Updating Table TBTCP:

  • Concatenate ‘SE’ with the SETTING_ID from the RSRD_SETT_NODE_A table (Data in the internal table can be used).
  • Select JOBNAME and JOBCOUNT from the table TBTCO table where JOBNAME is equal to the concatenated value of the SETTING_ID and JOBLOG field is blank.

 

 

 

  • Select SDLUNAME and AUTHCKNAM from TBTCP table where JOBNAME is equal to TBTCO-JOBNAME and JOBCOUNT is equal to TBTCO-JOBCOUNT.
  • Update the values of SDLUMANE and AUTHCKNAME with New User IDs.

 

Copying the Favorites across the User IDs for Workbooks:


Method 1:

  • Download the favorites using the Program RSFAVODL.
  • Upload the file back from the new User ID using Program RSFAVOUL.

 

Method 2:

  • A file with mapping between Old User IDs and New User IDs should be maintained.
  • Select all the data from the SMEN_BUFFC table where UNAME is equal to the Old User IDs in the file.

 

  • Update the Old User IDs with the New User IDs.

 

SAP BI:Loading Multiple files through flat files data source on a single go

$
0
0

We got a situation, were to load multiple files on a single go from legacy systems, below are the steps that are followed and with mandatory updates:

 

 

Mandatory updates:

 

1. The multiple files structure should be same.

2. The files should be derived from one common application server path.

3. time interval between files to be taken care.

 

Step 1:

 

Check the files structure, we received following input in our application server,

 

Untitled1.png

 

Step 2 :

 

we will be receiving 40+ files at same time,which should be automated in an single go.

 

Untitled2.png

 

Step 3:

 

We deployed a Change routine in info pack, which collates all the files into a single file and processed into BI server.

Untitled3.png

 

Step 4:

 

Use the below routine,

 

Local TYpes Declaration

 

 

TYPES: BEGIN OF ty_final,

         vendor   TYPE char10,

         loctype  TYPE char2,

         upc      TYPE char18,

         qty      TYPE char17,

         buom     TYPE char3,

*         fsv_site TYPE char4,                                  "Mod-001

       END OF ty_final.

 

 

*BEGIN OF DELETION- Mod-001

*       BEGIN OF ty_file2,

*         vendor   TYPE char10,

*         loctype  TYPE char2,

*         fsv_site TYPE char4,

*       END OF ty_file2.

*END OF DELETION- Mod-001

 

 

* Local Constants declaration

  CONSTANTS: c_filepath1 TYPE rsfilenm VALUE '/interfaces/',

             c_filepath2 TYPE rsfilenm VALUE '/inbound/GMII036',

             c_file      TYPE char30    VALUE

             'I1306_GENTRAN_SAPBI_FSV_AVAIL_',

             c_slash      TYPE char1    VALUE '/',

             c_file_extn  TYPE char4    VALUE '.txt',

             c_file_ext   TYPE char4    VALUE '.DAT',

             c_file_ext1  TYPE char4    VALUE '.DAT',

             c_prefix     TYPE char16   VALUE 'FSV_FINAL_',

             c_x          TYPE char1    VALUE 'X',

*BEGIN OF DELETION- Mod-001

*             c_comma      TYPE char1    VALUE ',',

*             c_file2      TYPE char20   VALUE 'FSV_SITE_EXTRACT.txt',

*             c_tab        TYPE char1    VALUE

*              cl_abap_char_utilities=>horizontal_tab,

*END OF DELETION- Mod-001

             c_cntl       TYPE char4    VALUE 'CNTL'.

 

 

* Local Internal tables declaration

  DATA: li_final      TYPE STANDARD TABLE OF string,

        li_target     TYPE STANDARD TABLE OF ty_final.

*        li_file2      TYPE STANDARD TABLE OF ty_file2.         "Mod-001

 

 

* Local Work Area declaration

  DATA: rec_filedat        TYPE string,

        rec_filechar(4096) TYPE c,

        rec_final          TYPE ty_final,

*        rec_file2          TYPE ty_file2,                      "Mod-001

        rec_target         TYPE ty_final.

 

 

* Local Variables declaration

  DATA: l_v_dir       TYPE dirname_al11,

        l_v_file      TYPE string,

        l_v_finalpath TYPE rsfilenm,

        l_v_name      TYPE string,

        l_v_rectype   TYPE char4,

        l_v_flag      TYPE char1,

        l_v_cntrl     TYPE char4,

        l_v_date      TYPE char6,

        l_v_time      TYPE char6,

        l_v_dd        TYPE char2,

        l_v_mm        TYPE char2,

        l_v_yy        TYPE char2,

        l_v_datum     TYPE char6,

        l_v_input     TYPE string,

        l_v_tabix     TYPE sy-tabix.

 

 

* Get the File Directory

  CONCATENATE c_filepath1 sy-sysid c_filepath2 INTO l_v_dir.

* Append timestamp to file name

  CONCATENATE c_file sy-datum c_file_ext INTO l_v_input.

 

 

    CLEAR: l_v_file.

    CONCATENATE l_v_dir l_v_input INTO l_v_file

                SEPARATED BY c_slash.

 

 

* Reading the Application File

    OPEN DATASET l_v_file FOR INPUT

                IN TEXT MODE ENCODING DEFAULT.

    IF sy-subrc NE 0.

      CLEAR: l_v_file, l_v_input.

* Append timestamp to file name

       CONCATENATE c_file '20130729' c_file_ext1 INTO l_v_input.

       CONCATENATE l_v_dir l_v_input INTO l_v_file

                SEPARATED BY c_slash.

 

 

* Reading the Application File

    OPEN DATASET l_v_file FOR INPUT

                IN TEXT MODE ENCODING DEFAULT.

    ENDIF.

    IF sy-subrc EQ 0.

      DO .

        READ DATASET l_v_file INTO rec_filedat.

        IF sy-subrc <> 0.

 

 

          EXIT.

        ELSE.

* Moving string variable values to char variable

          MOVE rec_filedat TO rec_filechar.

 

 

*Validating date in the control record

          l_v_cntrl = rec_filechar+0(4).

          IF l_v_cntrl = c_cntl .

            CLEAR l_v_flag.

            l_v_date = rec_filechar+4(6).

            l_v_time = rec_filechar+10(6).

 

 

*Splitting SY-DATUM into YYMMDD format

            l_v_dd = sy-datum+6(2).

            l_v_mm = sy-datum+4(2).

            l_v_yy = sy-datum+2(2).

            CONCATENATE l_v_yy

                        l_v_mm

                        l_v_dd

                        INTO l_v_datum.

 

 

            IF l_v_date NE l_v_datum.

             l_v_flag = c_x.

            ELSE.

              clear l_v_flag.

            ENDIF.

          ELSEIF l_v_flag IS INITIAL.

* Consolidating the file(s) contents

            APPEND rec_filedat TO li_final.

            CLEAR rec_filedat.

          ENDIF.

        ENDIF.

      ENDDO.

      CLOSE DATASET l_v_file.

    ENDIF.

 

 

  CLEAR l_v_file.

  DELETE li_final INDEX 1.

  IF li_final IS NOT INITIAL.

 

 

    LOOP AT li_final INTO rec_filedat.

* Moving string variable values to char variable

      CLEAR rec_filechar.

      MOVE rec_filedat TO rec_filechar.

 

 

      l_v_rectype = rec_filechar+0(4).

*processing input file to form the target file in required format

      CASE l_v_rectype.

        WHEN 'AV01'.

          rec_final-vendor = rec_filechar+9(5).

          CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'

            EXPORTING

              input  = rec_final-vendor

            IMPORTING

              output = rec_final-vendor.

        WHEN 'AV05'.

          rec_final-loctype  = rec_filechar+5(2).

          CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'

            EXPORTING

              input  = rec_final-loctype

            IMPORTING

              output = rec_final-loctype.

        WHEN 'AV10'.

          rec_final-upc  = rec_filechar+4(8).

          CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'

            EXPORTING

              input  = rec_final-upc

            IMPORTING

              output = rec_final-upc.

          rec_final-qty  = rec_filechar+12(16).

          APPEND rec_final TO li_target.

*       WHEN OTHERS.

      ENDCASE.

    ENDLOOP.

  ENDIF.

  CLEAR rec_final.

 

 

  IF li_target IS NOT INITIAL.

 

 

*BEGIN OF DELETION - Mod-001

*reading second input file 'FSV_SITE_EXTRACT.TXT'

*    CONCATENATE l_v_dir c_file2 INTO l_v_file

*                                  SEPARATED BY c_slash.

** Reading the Application File

*    OPEN DATASET l_v_file FOR INPUT

*                IN TEXT MODE ENCODING DEFAULT.

*    IF sy-subrc EQ 0.

*      DO .

*        READ DATASET l_v_file INTO rec_filedat.

*        IF sy-subrc <> 0.

*

*          EXIT.

*        ELSE.

** Moving string variable values to char variable

*          CLEAR rec_filechar.

*          MOVE rec_filedat TO rec_filechar.

*          SPLIT rec_filechar AT c_tab

*           INTO rec_file2-vendor

*                rec_file2-loctype

*                rec_file2-fsv_site.

*

*          CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'

*            EXPORTING

*              input  = rec_file2-vendor

*            IMPORTING

*              output = rec_file2-vendor.

*

*          CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'

*            EXPORTING

*              input  = rec_file2-loctype

*            IMPORTING

*              output = rec_file2-loctype.

*

*          APPEND rec_file2 TO li_file2.

*          CLEAR rec_file2.

*        ENDIF.

*      ENDDO.

*    ENDIF.

*END OF DELETION - Mod-001

 

 

    CLOSE DATASET l_v_file.

    CLEAR l_v_file.

*Look up for FSV_SITE in LI_FILE2 and adding to LI_TARGET

*    SORT li_file2 BY vendor loctype.                           "Mod-001

 

 

    CLEAR l_v_name.

    CONCATENATE c_prefix sy-datum c_file_extn INTO l_v_name.

    CONCATENATE l_v_dir c_slash l_v_name  INTO l_v_finalpath .

** Write the Application server file with the consolidated Content(s)

    OPEN DATASET l_v_finalpath FOR OUTPUT

                IN TEXT MODE ENCODING DEFAULT.

    IF sy-subrc EQ 0.

      CLEAR rec_filedat.

      LOOP AT li_target INTO rec_final.

        CLEAR : rec_filedat.

*                rec_file2.                                     "Mod-001

*BEGIN OF DELETION - Mod-001

*      READ TABLE li_file2 INTO rec_file2

*        WITH KEY vendor  = rec_final-vendor

*                 loctype = rec_final-loctype BINARY SEARCH.

*      IF sy-subrc = 0.

*        rec_final-fsv_site = rec_file2-fsv_site.

*        endif.

*END OF DELETION - Mod-001

        CONCATENATE rec_final-vendor

                    rec_final-loctype

                    rec_final-upc

*                    rec_final-fsv_site                         "Mod-001

                    rec_final-qty

                    rec_final-buom

                    INTO rec_filedat.

 

 

        TRANSFER rec_filedat TO l_v_finalpath.

        CLEAR rec_filedat.

      ENDLOOP.

      CLOSE DATASET l_v_finalpath.

    ENDIF.

    p_filename = l_v_finalpath.

    CLEAR: l_v_finalpath.

    REFRESH: li_target,li_final.

  ENDIF.

** Clearing used internal tables, work areas and variables

 

 

*....

  p_subrc = 0.

*$*$ end of routine - insert your code only before this line         *-*

endform.

 

 

This is Just an example, you can modify your code,based upon your requirements and inputs.

Data Extraction from data services to BW

$
0
0

Data Extraction from data services to BW

 

 

Data from data services cannot be loaded to BW,If data source is BI 7.x compatible.In such situations we need to create 3.x data source by following steps
to do data load from Business objects data services into BI 7.1 data flow.

 

 

Goto RSA1 -> select infosources in Modeling of Administrative work bench

 

P1.png

 

 

Right click on Application Component and select Additional Functions - > Create InfoSources 3.x

P2.png

 

 

Technical name and Long description of the info source needs to be given as below

 

P3.png

 

 

The fields needs to be loaded into BW data source from Data services needs to be given as an infosource fields

 

 

P4.png

 

 

After entering fields that needs to loaded from Data services click enter and Activate

 

P5.png

 

 

 

After creating Info source, Right click on info source and select Additional functions -> Create Transfer Rules

 

P6.png

 

 

Give the source system as Data services source system name

 

P7.png

 

 

Clicks enter and activate the Transfer rules and data source created.

 

P8.png

 

 

 

Once data source is created from BI side, the structure needs to be replicated in Data services to load data from Data services.








Adding New info object to info cube Which have data.

$
0
0

This will be simple one but may be helpful..

 

My cube have data as shown below.

 

My cube designed screen.

 

Now am planned to add 0customer to Entity Dim.

Go to RSA1, Administration-->Re modelling tab,

Take you to the below screen.

 

 

Give the remodeling rule name and target on which you want add info obj. click on create, its gave a pop uo box to enter description.enter the required description and click on transfer. in below screen click on + symbol(add an operation to list)

 

 

Click on that , Below screen will popup.

 

 

here we can see all options which we want add/delete, for adding we not pass values using 4 options as show above. time being am using constant value.

after filling the required options here, click on Transfer. next save and Click on check. there is an option impact analysis, by adding/deleting if we want know the any impact, clik on it , it shows you.

After this check options , you can schedule, it will adjust the all necessary changes in cube dimension.

 

Next screen will come with start later and start immediately. choose as you want. but choosing here as start immediately.

 

after choosing immediately,

 

you can see below message, then go with monitor or job log.

as we see in pic. after the success of this job, you can see added filed in your target.

 

See my cube have added info obj in IC_EVA3.

By adding new obj, DTP was deactivated, so make it active and use usual.

My doc - purpose is too add info object to target which have data.

 

Information:

Remodeling purpose is just add or delete info object from cube which have data.

For added info object need historical data then drop whole data from cube and reload from source.

If you won't need histocal data then droping data from cube was not needed. Thru delta loads now onwards data will be filled for added info object.

 

Thank you all.


SAP NetWeaver BW Application Lifecycle Management (ALM)

$
0
0
eim301_pic1.JPG

Upgrade/Migration/Implementation/Systemcopy -
SAPNetWeaver Business Warehouse 7.3 and Higher

On this page, you can find various information about upgrade, migration and implementation of SAPNetWeaver BW 7.3 and higher, including the enablement for SAP HANA. For information about lower releases, see  SAP NetWeaver Business Warehouse? 7.0 and lower - exclusively.

 

Content

 

eim300_pic3.JPG

SAP Business Intelligence Architecture

With the new possibilities in SAP NetWeaver BW 7.30, In-Memory technologies SAP BWA and SAP HANA, as well as further updates to the SAP BusinessObjects platform and SAP BusinessObjects Data Services, this must-read presentation illustrates synergies in combination with the SAP Business Intelligence solution portfolio. Sybase core technologies, such as Replication, Databases and Mobility, can be used very efficiently together with the existing SAP BusinessObjects product portfolio.

 

eim301_pic2.JPG

BW Technical and Functional Upgrade

 

BLOG: Software Update Manager (SUM): introducing the tool for software maintenance

BLOG: Good News - Easier Modeling of the SEM Add-On in Solution Manager

 

ASU Toolbox (incl. BW Specific Content) and BW Upgrade pre/post Task List
With the ASU (application specific upgrade) toolbox, customers get one single truth for all pre/post upgrade steps regarding the technical upgrade to SAP NetWeaver BW 7.0x  and all following releases.
More detailed information about the ASU toolbox can be found in note 1000009. This tool has been available since 2008 (see the TechEd Presentation and the new Upgrade to SAP NetWeaver BW 7.30 Presentation) has been enhanced and now allows application specific and technical resources to work together for a successful upgrade to SAP NetWeaver BW 7.30
With SAP NetWeaver 7.30 JAVA, the Functional Unit Configuration UI (former CTC BI-JAVA Template) is available.
New:
Together with the BW Housekeeping Task List,there are also additional Task Lists available to simplify preparation of the application-specific part.
Implement the following SAP Note to enable usage of task list SAP_BW_BEFORE_UPGRADE via transaction STC01
(contains manual report ZNOTE_1734333_PRE_70x/ZNOTE_1734333_PRE_70x, and NO automated steps applied with SNOTE)

 

The Presentation Teched 2012 - Session EIM301  illustrates the complete Upgrade process.

 

Immediately after the upgrade to SAP NetWeaver BW 7.3x Note 1720495 (Invalid deimplementation of obsolete notes by SNOTE tool)should be applied.

 

With the release of SAP NetWeaver BW 7.30 new and innovative capabilities have been added to SAP's EDW premium solution. SAP NetWeaver BW 7.30 as the backbone for a successful usage of SAP BusinessObjects Platform and SAP Business Warehouse Accelerator - BWA is the heart of the SAP Business Intelligence Architecture. The updated presentation SAP NetWeaver 7.0x - Upgrade to SAP NetWeaver 7.30 ABAP BW (full version with complete technical details) provided you with must-know delta information to quickly and effective upgrade to SAP NetWeaver 7.30 BW including existing information from the resources of this page and the updates for SAP NetWeaver 7.30 EhP1 (7.31).

 

See also the changes to the existing BEx Versions 3.5 and 7.x after Upgrade to NetWeaver BW 7.30 or 7.31
Be sure to read these Notes prior to the technical Upgrade in order to prevent any unwanted incompatibilities or unforeseen changes.

 

eim301_pic3.JPG

BW ABAP and BI-JAVA Installation

The Software Provisioning Manager 1.0 (SWPM) can be used to install all SAP NetWeaver 7.30 based instances onwards.

 

See SAP NetWeaver BW Installation/Configuration (also on HANA). This document also includes the complete SAP NetWeaver BW basis customizing settings, together with an example configuration of the System Parameter. The guidance raises no claim to completeness.
New: It is now possible to install the ABAP CI as well on the HANA Appliance!
     Overview - SAP HANA and SAP NetWeaver AS ABAP o... | SAP HANA

 

See all SAP First Guidance Documents here -BW on SAP HANA First Guidance Collection

 

With the release of SAP NetWeaver 7.30 all previous J2EE stacks are now synchronized in one platform. BI JAVA 7.30 is still available with the usage type BI-JAVA to connect to an existing SAP NetWeaver BW 7.30 stack for the classical usage of BEx Web or the native dashboards (former Xcelsius). The presentation SAP NetWeaver 7.30 – BI JAVA Implementation shows the new SAP NetWeaver 7.30 installation and configuration options with the functional unit configuration UI (former CTC BI-Java Template) All informations are also valid vor SAP NetWeaver 7.30 EhP1 (7.31)

 

SAP NetWeaver 7.0 - Deinstalling Java Add-In (also valid for SAP NetWeaver 7.30 JAVA Add-In)
The separation of the doublestack (ABAP and JAVA in one instance) into two separate stacks is a SAP recommendation. An option available since SAP NetWeaver BW 7.0 is the deinstallation of the Java Add-In with SAPInst. This presentation provides details and guidance about the process to prepare for upgrade to SAP NetWeaver BW 7.30, concentrating on the ABAP stack.

 

As a successor for most scenarios, we offer the combined export of the Java system, deinstallation of the Java Add-In and installation of a new Java system using the dual-stack split tool available as part of the SL toolset 1.0 (SP5). For more information, see "Dual-Stack Split".

 

If you are running SAP NetWeaver 7.30 JAVA Add-In you can use the software provisioning manager 1.0 (SWPM) as part of the SL toolset for the deinstallation process, as this always contains the latest software components (Note 1680045). Note that the dual split process is not supported for SAP NetWeaver 7.30 systems (Note 1655335)

 

With SAP NetWeaver 7.3x JAVA the Functional Unit Configuration UI (former CTC BI-JAVA Template) is available

 

In Advance check the WebAS/SSO Settings after the Upgrade to NetWeaver 7.3x. The settings are almost identical to NetWeaver BW 7.0x

 

eim300_pic1.JPG

Migration to BW on HANA

DMO is an option of SUM (Software Update Manager) for a combined update and migration: update an existing SAP system to a higher Software Release and migrate to SAP HANA database including the unicode conversion of the source database. The procedure is only available for systems based on AS ABAP, hence the executable SAPup is used in background. DMO migrates from an existing relational database type (“anyDB”) to SAP HANA. Software Update Manager (SUM) is the tool for system maintenance: Release upgrades, EHP implementation, applying SP stacks.

 

 

To reduce downtime for your production landscape, one of the recommended migration paths of SAP NetWeaver Business Warehouse (SAP NetWeaver BW) to SAP NetWeaver BW on SAP HANA comprises a system copy of your SAP NetWeaver BW system. The system copy procedure of SAP NetWeaver BW systems and landscapes is complex for a number of reasons however. A large number of configuration settings are involved for example (such as connections and delta queue handling for data loading), as well as system copy scenarios of SAP NetWeaver BW (each with different landscape aspects) that have to be handled as part of every system copy, regardless of whether the system copy is part of the migration to SAP HANA or you want to perform regular system copies of your SAP NetWeaver BW landscape.

 

To achieve this, SAP NetWeaver Landscape Virtualization Management offers preconfigured "task lists" used by the ABAP task manager for lifecycle management automation.
You can also enable SAP NetWeaver BW powered by SAP HANA to “go productive” with parallel operation of your existing production system, both connected to the same back-end systems. This is achieved with a special and unique automated solution for delta queue cloning and synchronization on production systems.
SAP Note 886102 (SMP login required) thus becomes obsolete. Using the post-copy automation for SAP NetWeaver BW (BW PCA) in the migration process of SAP NetWeaver BW to SAP NetWeaver BW on SAP HANA, this process can be shortened by weeks and becomes easier, faster and more reliable.

 

The Presentation Teched 2012 - Session EIM300  illustrates the Migration to BW on HANA from an end-to-end perspective.

 

 

eim301_pic5.JPG

BW System Copy

 

Since Release 7.30 SP05, it is now possible to perform a heterogenous system copy (incuding unicode migration) to migrate existing systems based on SAP NetWeaver BW 7.30 SP05 and higher to SAP NetWeaver BW on HANA (HDB) based systems.
With this major step forward, a new procedure called "Post Copy Automation (BW PCA)" now supports customers with what can often be complex post-steps before and after the homogenous/heterogenous BW system copy. This presentation is the delta information to the existing document "SAP NetWeaver 7.0 - BW Systemcopy ABAP" shown above. The technical Improvements with the leaner data model provides advantages with BW on HANA too.
To ease this generic step of BW system copy, a new procedure called "BW Post Copy automation (BW PCA)" is available, which supports customer now in the complex pre and post steps during the homogeneous/heterogeneousBW system copy (information from the SAP ALM group) procedure.
Please note that these procedure can be used independently from your BW and Database Version starting fromNetWeaver 7.0x

 

We distinguish between two use cases explained in the FaQ for BW-PCA:
- initial copy based on an existing original BW system and connected BW source systems
  Task Lists - SAP_BW_COPY_INITIAL_PREPARE (BW systems only) andSAP_BW_BASIS_COPY_INITIAL_CONFIG
- refresh of an existing system based on an existing BW system and connected BW source systems
  Task List - SAP_BW_BASIS_COPY_REFRESH_CONFIG

 

The following Notes are the pre-requisites for the use cases (included in 7.01 SP14 and higher):
Updating to the minimum level of the mentioned Support Stacks is recommended to minimize the manual effort.

 

For both cases the BW-PCA Tasklists support the Customer together with the software provisioning manager 1.0 (SWPM) in these software lifecycle management tasks. BW-PCA is embedded in the SAP NetWeaver Landscape Virtualization Management

 

eim301_pic4.JPG

 

BW Housekeeping Tasks

 

In this session, you will learn about various housekeeping activities that should be part of the operational concept of your Enterprise Data Warehouse. These housekeeping activities will support you in removing unwanted and unneeded data as well as unused metadata. Scheduling these activities regularly in the system will ensure optimum utilization of system resources while at the same time increasing the overall system performance.

 

New: SAP First Guidance - BW Housekeeping and BW-PCA

 

(contains manual steps ZNOTE_1829728_PRE_70x/ZNOTE_1829728_PRE_73x, and automated steps applied with SNOTE)
The newly released Housekeeping Task List (Pre/Post Steps) allows you to automate mandatory tasks prior to upgrade/migration with DMO to ensure the quality of the migration process and the health of your BW System.

 

Apply the following Notes in advance and run the tasks in advance to ensure smooth implementation of the BW Housekeeping Task List.
(contains manual steps ZNOTE_1767420, and automated steps applied with SNOTE)
To solve the problem with the endless loop on the last task, apply the following Note:

 

eim300_pic2.JPG

Event Presentations

 

Navigating and Networking at SAP TechEd => Live from TechEd Amsterdam, Replay from 05.11.2013, 18.00 Uhr

 

 

eim301_pic6.JPG

 

References/Experiences/DSAG

This is a collection of ressources from the SAP SCN Network and it´s content is not reflecting the findings from this Document of future Upgrade and Enhanchements.
See how the german customer Kärcher upgraded their BW System Landscape (Three System plus Sandbox) within 8 weeks including BI-IP and BIA. It is still a good reference from the project perspective

 

See Dr. Berg's Upgade to 7.30 Experience. This is a overview Presentation based on 2011 findings.
See the Doc - SAP BW 7.3 Promising Features This is a very nice overview based on the 2012 findings.
Recent Blog - SAP BW 7.3 Upgrade Issues and Solutions is based on 2013 findings, esspecially application side.
DSAG Forum: "Upgrade NetWeaver BW 7.3x" => (DSAG-ID requested) share you experience with other DSAG members.

 

SAP Netweaver BW Operations

$
0
0

Upgrade/Migration/Implementation - SAPNetWeaver Business Warehouse 7.0 and lower

 

For information regarding an higher release than SAP NetWeaver Business Warehouse 7.3 please consult the SAP NetWeaver BW Operations - Upgrade/Migration/Implementation 7.3 page

 

 

Architecture and Tools

CTC for BI-JAVA

To connect the existing ABAP stack to the new installed JAVA stack there is an automatic connection wizard available via CTC (central template configuration) for BI-Java. This reduces the implementation effort from days to minutes and helps to reduce the TCO for the SAP NetWeaver BW usage dramatically. More detailed information about the usage and pre requisites can be found in the note 983156.

An overview of the improvements within the SAP NetWeaver Software Lifecycle Management including the ASU toolbox and the CTC for BI-JAVA can be found here: News and Updates with SPS 14 SAP NetWeaver BW.

 

 

Technical / Functional Upgrade to SAP NetWeaver BW 7.0x

With the presentation SAP NetWeaver 7.0 - Upgrade to SAP NetWeaver 7.0 ABAP BW you get all insides about the pre and post steps necessary for a successful upgrade of the NetWeaver ABAP stack. The content was used for the creation of the XML based input file for the ASU toolbox for BW. You will also find best practice procedures, tips and tricks and useful background information about the upgrade process, and might call it the "BW Upgrade Bible".

 

To enable SSO/SSF on the ABAP stack or enhance the web capabilities with HTTPS the presentation SAP NetWeaver 7.0 - Settings for WebAS tells you everything to prepare the ABAP stack for the java connection like EP or Integrated Planning (BI-IP).

 

The SMTP functionality is used for various applications together with BW 7.0x such as Information Broadcasting for web templates or process chains. To enable all features together with BW 7.0x, you should get familiar with the basis functions and implementation such as secure email and encryption.

and read the presentation SAP NetWeaver 7.0 - Settings for SMTP

 

With NetWeaver 7.0 the JAVA stack was introduced for a wide audience of users especially the SAP NetWeaver BW users. Installation- and master guides are often not enough to make the right implementation decisions. With the presentationSAP NetWeaver 7.0 - Implementing Java for BW

you can find the right way for your SAP NetWeaver 7.0 JAVA implementation to enable all new features for SAP NetWeaver BW ("functional upgrade").

 

One of the biggest challenges is the connection between the ABAP and JAVA stack to enable the new SAP NetWeaver BW 7.0 features. The presentation SAP NetWeaver 7.0 - Setting up BEx Web - Short Track shows you the detailed usage and the pre requisites of the CTC for BI-JAVA and the effort which was taken to improve the TCO for SAP NetWeaver BW in the area of Software Lifecycle Management. Additional information helps you to identify unwanted system outages.

 

SAP NetWeaver 7.0 - Frontend

With the BEx Suite there where also new frontend components introduced. With the presentation SAP NetWeaver 7.0 - Frontend you will also get the news for the usage of the mayor SAP GUI 7.10 release. With the upcoming month SAP introduces the new Signature Design for all frontend components. A sneak preview can be found here: New visual Design in Frontend

 

Lifecycle Management with SAP NetWeaver BW 7.0x

SAP NetWeaver 7.0 - ERP and BI in one System - MCOS Scenario

With NetWeaver 04 and above you can use ERP and BW in one System called MCOS (multiple components - one system) scenario. This is also visible in the new Solution Manager 4.0 with the usage of the inbuilt NetWeaver BW capabilities. This presentation gives you also some concepts for the deployment options and some technical remarks for the implementation.

 

SAP NetWeaver 7.0 - BW Systemcopy ABAPupdated July 2013!

A complete overview about the systemcopy process with the recommended export/import method provided with the SAPInst application including all pre and post step's for a successful BW systemcopy e.g. as a milestone prior to an technical upgrade.

To improve the Performance during the BDLS run including in the BW-PCA task list esspecially on Oracle database, implement the following Notes:

Note 932975 - Oracle statistics for RFC tables

Note 1020260 - Delivery of Oracle statistics (Oracle 10g, 11g)

These Notes improving the BDLS run, when the LOGSYS is referenced in the BDLS tables

Note 1894679 - Avoiding the conversion of BW DataSources by BDLS

Note 1915498 - P32; DTP: BDLS does not convert DTPH LOGSYS entries

 

With BW-PCA the above Description is obsolete, as well as the very comprehensive Note 886102.
Please refer to the following Presentation - Automation of BW system copy configuration

 

SAP NetWeaver 7.0 - BI Systemcopy JAVA

With the introduction of the java implementation there is also the demand for system copies for java systems. This process can differ from the Abap process and these differences are collected with this presentation. The post steps after the copy refer to the presentation Setting up BEx Web - Short Track and How to change the CTC settings

 

SAP NetWeaver 7.0 - Implementing ABAP for BW

For the successful NetWeaver 7.0 implementation Abap for BW these guidelines are a mandatory step to have an overview of the relevant notes and the right tuning and performance settings from the first day. You can also use these guidelines to review existing NetWeaver BW implementation for their system setup.As a jumpstart you can also download an example configuration which can be easily adapt to other OS/DB combinations here: SAP/Oracle profiles. Please see also note 1044441 for more details.

 

SAP NetWeaver 7.0 - Customizing BW and BPC

This checklist is showing all steps for a successful BW basis customizing which is valid for the usage of NetWeaver BW 7.0x and the new BPC 7.0 solution based on NetWeaver 7.01 (EhP 1). This content will be used to create an automatic CTC template for these manual steps.

 

 

Relevant Notes

 

Event Presentations

 

Worldtour 2009 - Implementing SAP NetWeaver EhP1 - Best Practice

One of the requirements to implement all new SAP BusinessObjects senarios like the improved usage of the SAP BusinessObjects portfolio or the new innovative combined Search Solution require the update/implementation of the recent for all customers released SAP NetWeaver 7.0 Enhanchement Package 1 (EhP1). In this session you will get on one hand all new benefits with EhP1 for your SAP BI Solution and on the other hand Best Practice insights for the fast and disruptive update to EhP1 to enable the next level of SAP BusinessObjects product portfolio integration.

 

TechEd 2008 Berlin - Upgrade to SAP NetWeaver BI 7.0 with new innovative Tools

The new and updated two hour lecture shows the latest upgrade possibilities provided with the ASU toolbox and the CTC for BI-JAVA in a complete detailed slide deck with the current innovations and outlook with the SAP NetWeaver EhP1.

 

TechEd 2007 Munich - Best Practice for Upgrade NetWeaver 7.0 BI

The two hour lecture introduces the new upgrade possibilities provided with the ASU toolbox and the CTC for BI-JAVA in a complete detailed slide with the current features at this time.

 

DSAG 2007 Frankfurt - Functional Upgrade NetWeaver 7.0 BI (Java)

This one hour session held at the DSAG congress November 2007 focus on the functional upgrade (SAP NetWeaver JAVA installation and configuration) and reflects the current SAP strategy for running the JAVA stack together with SAPNetWeaver BW 7.0 ABAP.

Repair Full load problem fix for datasource 0CSM_CASE_ATTR ::

$
0
0

Applies to:

SAP NetWeaver Business Warehouse (formerly BI). This has been tested and working fine on SAP BI 7.0 version.

Applicable for other BW versions as well.

 

 

Summary :

This document will help to understand the steps one can take in order to fix the issue related with the datasource - 0CSM_CASE_ATTR (Case Management: Case (GUID)). This is a necessary point to be performed if you have freshly installed the datasource in the BW system. The datasource is enabled to fetch delta records.

 

 

Author: Arpit Khandelwal.

Company: Accenture Services Pvt. Ltd.

 

 

Author Bio:


apk.PNG

 

Arpit Khandelwal is a SAP BI Consultant currently working with Accenture Services Private Limited. He has 2.7 years of experience in  BW/BI implementation and support projects. He has been particularly involved in SAP BW Archiving Activities. Major area of work involves with the extraction of R/3 data from LO and FI datasources.



Basic Scenario ::


Freshly installed datasource - 0CSM_CASE_ATTR (Case Management: Case (GUID))is available in your BW system.

You have run the RSA3 extractor in R/3 side and tried to pull the data through repair full load on BW side but records are not matching.


Number in records in RSA3:: 70,936


s1.png


Number of records in Infoobject loaded on Repair Full ::  13,228


s2.png




Functional & Technical Aspect ::


The bug in the standard extractor program of this datasource does not allows the data to be loaded correctly through the Repair Full option. This needs to be fixed by instaling the support packages provided by the SAP OSS - 996360 - Case Extractor not able to pull more than 1 data package . If the BW version is not supported by this OSS, then we need to use the SAP OSS - 1159696 - Not able to get the data using case type from case extractor.

 

 

The 2nd OSS message also gives us an option to add one more field to the RSA3 extractor - CHANGE_Time field.


If user wants to extract the data using CHANGE_TIME, please do the below steps.

1. Execute rsa2 transaction

2. Input Data source(ex:0CSM_CASE_ATTR) and click on change button

3. Click on fields tab

4. Locate "CHANGE_TIME" field. Change the property value to "X"from "P".

5. Save the changes.


s3.JPG


s1.JPG



You need to install the Note in your source system (R/3) development --> acceptance --> production to make this load work correctly.

After installing the correction note , the data was loaded correctly.


Number in records in RSA3:: 62,140


s2.png


Number of records in Infoobject loaded on Repair Full ::  62,140

 

s4.png

 

 

Reference Sources ::

 

Note 996360 - Case Extractor not able to pull more than 1 data package

 

Note 1159696 - Not able to get the data using case type from case extractor

 

Time desync of data loading from data source - 0CSM_CASE_ATTR

SAP NetWeaver Business Warehouse 7.4

$
0
0

Picture2.jpg

This page provides  information,  about the new functionalities provided with SAP NetWeaver Business Warehouse 7.4 in general and the new functionalities of SAP NetWeaver BW powered by SAP HANA provided with SAP NetWeaver Business Warehouse 7.4 - SP 05

 

 

SAP NetWeaver BW 7.4 SP05 is released!

Read the information on the Support Package page for SAP NetWeaver BW 7.4

 

 

General Availability Care Program for SAP NetWeaver BW 7.4 SP05

For SAP NetWeaver BW 7.4 Support Package 05, we offer the SAP general availability care (GAC) program. Via the SAP GAC program, SAP reaches out to the first customers who receive SAP’s new solution for Business Warehouse and who want to implement one of the key topics listed below. With your active participation, you help SAP to gain early feedback from the productive usage of the latest software which may serve as a basis for further improvements. At the same time, SAP would like to engage with productive customers who are interested in a collaboration regarding marketing and communication activities for the new functionalities provided

 

Overview SAP BW 7.4 SP05 on SAP HANA and further Roadmap

SAP NetWeaver BW on SAP HANA continues to be the  cornerstone of SAP’s strategic vision for enterprise data warehousing providing organizations a solid data foundation to capture, store, transform and manage data in a scalable, enterprise-ready data warehouse. And as new challenges arise in the market (exploding data volumes, new data sources, the need for real-time information access, etc), SAP BW on HANA continues to evolve in order to meet the growing challenges imposed on IT by these ever changing market forces. The release of SAP BW running on SAP HANA is a great example of how SAP BW has evolved to ensure organizations continue to leverage  their investment in SAP BW to meet these new  challenge.

See this presentation to learn what SAP is doing next to evolve SAP BW on SAP HANA with the SAP BW 7.4., SP 05 on HANA

 

Key Features

  • Enhanced Data Modeling
    • Common Eclipse based Modeling Tools
    • BW/HANA Smart Data Access providing the logical EDW
    • Easy integration of external data models with Open ODS Layer
    • Further reduce data layers in BW via Operational Data Provisioning
    • New Composite Provider
  • Push down further processing logic to HANA
    • BW Analytic Manager
    • HANA  Analysis Processes
    • BW Transformations
    • PAK (Planning Application Kit) – Pushing down more planning semantics
  • Converged planning solutions (i.e. BPC unified)


Recommendations:

 

  • Apply SAP NetWeaver BW 7.4 with SP02 for Embedded Use Case scenarios only
  • For EDW Use Case scenarios: Start only with SAP NetWeaver BW 7.4 SP05
  • Start with SAP NetWeaver BW 7.31 prior to SAP NetWeaver BW 7.4 SP05

 

Additional Information:

 

Picture1.jpgPositioning of SAP NetWeaver Business Warehouse powered by SAP HANA and SAP HANA Live for SAP Business Suite

 

 

272475_l_srgb_s_gl.jpg  Roadmap for SAP NetWeaver BW on SAP HANA - One slider

 

 

273949_l_srgb_s_gl.jpgSAP NetWeaver 7.4  BW ABAP Support Packages Schedule and Implications

Data Records movement from MCEX --> RSA7 via V3 job ::

$
0
0

Applies to:

SAP NetWeaver Business Warehouse (formerly BI). This has been tested and working fine on SAP BI 7.0 version.

Applicable for other BW versions as well.

 

 

Summary :

This document will show how the MCEX queues are cleared by the V3 jobs and move the data to RSA7 (Bw Delta Queue).

 

 

Author: Arpit Khandelwal.

Company: Accenture Services Pvt. Ltd.

 

 

Author Bio:


apk.PNG

 

Arpit Khandelwal is a SAP BI Consultant currently working with Accenture Services Private Limited. He has 2.7 years of experience in  BW/BI implementation and support projects. He has been particularly involved in SAP BW Archiving Activities. Major area of work involves with the extraction of R/3 data from LO and FI datasources.



Basic Scenario ::


Basically the new system which has been handed to you has lot of data already in MCEX queues. This data needs to be pulled in BW system after the loading of Historical data via set-up tables.



Initially, we have the following records in SMQ1 (Outbound Queue).


111.png

 

To run the V3 job, go to LBWE ; click on Job Control.


112.JPG


Click on Start Date.

 

113.JPG


Select the next option as per requirement. In our case, we went for immediate.

 

114.JPG


Check and save the setting. Now click on Print Parameters option and assign the Local Printer for the printing.

It will show a warning but you can click to proceed ahead.


115.JPG




Click on Schedule job to schedule the V3 job. In our case, it was done for Plant Maintenance flow (17).

Showing the three phases of the job run to showcase the movement of data from MCEX queue to RSA7 queue.


Phase 1::


116.png


Phase 2::


117.png


Phase 3 ::


118.png

 

Through observing the three phases we come to know that MCEX queue will be always receiving some amount of data anytime because user postings are not stopped in the system.


When the V3 job is initiated, it will start with that moment for the number of records in the MCEX queue and start pulling the records from the MCEX queue to RSA7 queue.


Once the job gets completed, there will be gradual rise in the LUW's available in the RSA7 by the data moved from the MCEX queue which in turn will keep the MCEX queue not overloaded. Ultimately, the data from RSA7 can be moved to BW (through delta loads).

Load Non Legacy System data to BW system using Flat File(.CSV) , make available for Reporting and Automate whole Process !

$
0
0

OVERVIEW : This Document provides you the solution for,  how you can use non legacy data to SAP BW system using Multiple Flat file and automate the whole process.

 

design overview :

 

 

design overview.GIF

 

Step 1 : create a Report Program using SE38 , a user interface screen using ABAP for single or multiple File.

 

  Code  For genrating Selection Screen:

***********************************************************************************************************************************

SELECTION-SCREEN BEGIN OF BLOCK DATA1 WITH FRAME TITLE TEXT-001.

 

SELECTION-SCREEN: BEGIN OF LINE.
SELECTION-SCREEN COMMENT 1(20) TEXT-002.
PARAMETERS P_SFILE TYPE RLGRAP-FILENAME.
SELECTION-SCREEN POSITION 74.
SELECTION-SCREEN PUSHBUTTON (5) BUT2 USER-COMMAND MUL VISIBLE LENGTH 8.
SELECTION-SCREEN PUSHBUTTON (15) W_BUT USER-COMMAND CLK .
SELECTION-SCREEN: END OF LINE.

 


SELECTION-SCREEN: BEGIN OF LINE.
SELECTION-SCREEN POSITION 25.
SELECTION-SCREEN COMMENT 1(20) TEXT-003.
PARAMETERS: P_TFILE  LIKE SAPB-SAPPFAD LOWER CASE OBLIGATORY MODIF ID A  DEFAULT C_APP_PATH.
SELECTION-SCREEN: END OF LINE.

 

SELECTION-SCREEN: BEGIN OF LINE.
SELECTION-SCREEN COMMENT 1(20) TEXT-004.
PARAMETERS: P_EVENT TYPE BTCUEV-EVENTID OBLIGATORY MODIF ID B DEFAULT C_EVENT_NAM.
SELECTION-SCREEN: END OF LINE.

 

SELECTION-SCREEN: BEGIN OF LINE.
SELECTION-SCREEN COMMENT 1(20) TEXT-005.
PARAMETERS: P_CHAIN TYPE RSPC_CHAIN MODIF ID C OBLIGATORY DEFAULT C_PROC_NAM.
SELECTION-SCREEN: END OF LINE.

 

SELECTION-SCREEN END OF BLOCK DATA1.

 


SELECTION-SCREEN BEGIN OF BLOCK DATA2 WITH FRAME TITLE TEXT-006 .
SELECTION-SCREEN BEGIN OF LINE .
SELECTION-SCREEN COMMENT 01(31) W_CAP  .
SELECTION-SCREEN COMMENT 40(5)  W_RED   MODIF ID R.
SELECTION-SCREEN COMMENT 46(5)  W_AMBER MODIF ID Y.
SELECTION-SCREEN COMMENT 53(5)  W_GREEN MODIF ID G.
SELECTION-SCREEN PUSHBUTTON (15) REFRESH USER-COMMAND REFRESH MODIF ID F.
SELECTION-SCREEN END OF LINE .

 

SELECTION-SCREEN END OF BLOCK DATA2 .

***********************************************************************************************************************************

Front screen.png

 

User can upload either single file or multiple file .

 

Code For Single Value input :

 

***********************************************************************************************************************************
* This code is for to browse single file from the Local machine *

***********************************************************************************************************************************

  AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_SFILE.

  CLEAR IS_FILE_NAMES[].

  CALL METHOD CL_GUI_FRONTEND_SERVICES=>FILE_OPEN_DIALOG
    EXPORTING
      INITIAL_DIRECTORY       = 'C:Temp'
      MULTISELECTION          = 'X'
    CHANGING
      FILE_TABLE              = IS_FILE_NAMES[]
      RC                      = W_SUBRC
    EXCEPTIONS
      FILE_OPEN_DIALOG_FAILED = 1
      CNTL_ERROR              = 2
      ERROR_NO_GUI            = 3
      OTHERS                  = 4.
  IF SY-SUBRC  <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
  ENDIF.

  LOOP AT IS_FILE_NAMES INTO WA_TS_FILE_NAMES.
    P_SFILE = WA_TS_FILE_NAMES.
    CONDENSE  P_SFILE .
  ENDLOOP.

  CLEAR IS_FILE_NAMES[].

  REFRESH IS_FILE.

***********************************************************************************************************************************

Single or multiple selection.png

 

  For multiple selection you need to create a new screen using table control like below . I tried with select-option but it didnt work for me  so created new screen.

 

Code For Multiple Selection :

 

***********************************************************************************************************************************

* This code is for to browse multiple file from the Local machine * 

***********************************************************************************************************************************

 

 

AT SELECTION-SCREEN .

 
CLEAR W_OK_CODE.
  W_OK_CODE
= SY-UCOMM.

 
CASE W_OK_CODE .
   
WHEN 'BACK'.
     
LEAVE TO SCREEN 0.
   
WHEN 'RETURN'.
     
LEAVE TO SCREEN 0.
   
WHEN 'EXIT'.
     
LEAVE PROGRAM.
 
ENDCASE.


 
IF SSCRFIELDS-UCOMM EQ 'MUL'.
   
PERFORM MUL_ENTRIES.
 
ENDIF.


 
IF SSCRFIELDS-UCOMM EQ 'REFRESH'.
   
PERFORM PC_STATUS_CHECK.
 
ENDIF.

 

 

FORM MUL_ENTRIES .

 
REFRESH CONTROL 'TAB3' FROM SCREEN 9000.
 
CALL SCREEN 9000 STARTING AT 25 2.

ENDFORM.     

 

*screen code.

 

PROCESS BEFOREOUTPUT.

 
LOOP AT   IS_FILE
      
INTO WA_IS_FILE
      
WITH CONTROL TAB3
      
CURSOR TAB3-CURRENT_LINE.

   
MODULE SET_LINE_INPUT.

 
ENDLOOP.



PROCESS AFTER
INPUT.



 
LOOP AT IS_FILE .

   
FIELD WA_IS_FILE-FILENAME
  
MODULE TAB3_MODIFY ON REQUEST.

 
ENDLOOP.

 
MODULE USER_COMM.




PROCESS
ON VALUE-REQUEST.
 
FIELD WA_IS_FILE-FILENAME MODULE INPUT_FILE.

 

 

 

MODULE SET_LINE_INPUT OUTPUT.
  TAB3
-LINES = 20.ENDMODULE

 

 

CONTROLS: TAB3 TYPE TABLEVIEW USING SCREEN 9000.

MODULE TAB3_CHANGE_TC_ATTR OUTPUT.

EndModule.

 

MODIFY TABLEMODULE TAB3_MODIFY INPUT.

 
CLEAR WA_TS_FILE_TEM.
  WA_IS_FILE_TEM1
= WA_IS_FILE.

 
READ TABLE IS_FILE INTO WA_TS_FILE_TEM INDEX TAB3-CURRENT_LINE.
 
IF SY-SUBRC = 0 .

   
MODIFY IS_FILE
     
FROM WA_IS_FILE
     
INDEX TAB3-CURRENT_LINE.
 
ELSE.

*    APPEND wa_IS_FILE_TEM1 to IS_FILE .
 
ENDIF.

ENDMODULE.   

 

 

 

MODULE USER_COMM INPUT.

 
SORT IS_FILE BY FILENAME.
 
DELETE ADJACENT DUPLICATES FROM IS_FILE[] COMPARING FILENAME.

 
CASE SY-UCOMM.

   
WHEN 'F_OK'.
     
LEAVE TO SCREEN 0.
   
WHEN 'ONLI'.
     
LEAVE TO SCREEN 0.
   
WHEN 'ECAN'.
     
REFRESH IS_FILE.
     
LEAVE TO SCREEN 0.

 
ENDCASE.

ENDMODULE.                

 

 

MODULE INPUT_FILE INPUT.

 
DATA : G_CURR_LINE LIKE SY-STEPL.

 

*---Reading table line number---*

 
CALL FUNCTION 'DYNP_GET_STEPL'
   
IMPORTING
      POVSTEPL       
= G_CURR_LINE
   
EXCEPTIONS
      STEPL_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.
 
ENDIF.

 
CLEAR IS_FILE_NAMES[].

 

CALL METHOD CL_GUI_FRONTEND_SERVICES=>FILE_OPEN_DIALOG
     
EXPORTING

*    WINDOW_TITLE            =

*    DEFAULT_EXTENSION       =

*    DEFAULT_FILENAME        =

*    FILE_FILTER             =
        INITIAL_DIRECTORY      
= 'C:Temp'
        MULTISELECTION         
= 'X'
     
CHANGING
        FILE_TABLE             
= IS_FILE_NAMES[]
        RC                     
= W_SUBRC

*    USER_ACTION             =
     
EXCEPTIONS
        FILE_OPEN_DIALOG_FAILED
= 1
        CNTL_ERROR             
= 2
        ERROR_NO_GUI           
= 3
       
OTHERS                  = 4.
 
IF SY-SUBRC  <> 0.

* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

*            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 
ENDIF.


 
LOOP AT IS_FILE_NAMES INTO WA_TS_FILE_NAMES.

    P_SFILE
= WA_TS_FILE_NAMES.


    WA_IS_FILE
-FILENAME = WA_TS_FILE_NAMES.
   
CONDENSE  WA_IS_FILE-FILENAME.
   
TRANSLATE WA_IS_FILE-FILENAME TO UPPER CASE.


   
APPEND WA_IS_FILE TO IS_FILE .

 
ENDLOOP.


ENDMODULE.                 " INPUT_FILE  INPUT

 

 

 

***********************************************************************************************************************************

  multiple selection screen.png

 

Step 2 : Click on Check button to check flat files error. If there any error in any file then it will display in ALV grid display and ask user to correct file and load it again.

 

*Code For Error ALV Display

****************************************************************************************************************************

* This code will create ALV log to display error in specific format * 

***********************************************************************************************************************************

*  TS_TAB_ERROR  conatins Error document which will be filled according to validation

* field catalog

 

   REFRESH IS_FIELDCATALOG.

  IS_FIELDCATALOG-FIELDNAME   = 'FUNCTIONAL_AREA'.
  IS_FIELDCATALOG-SELTEXT_M   = 'FUNCTIONAL_AREA'.
  IS_FIELDCATALOG-COL_POS     = 0.
  APPEND IS_FIELDCATALOG TO IS_FIELDCATALOG.
  CLEAR  IS_FIELDCATALOG.


  IS_FIELDCATALOG-FIELDNAME   = 'COSTCENTER'.
  IS_FIELDCATALOG-SELTEXT_M   = 'COSTCENTER'.
  IS_FIELDCATALOG-COL_POS     = 1.
  APPEND IS_FIELDCATALOG TO IS_FIELDCATALOG.
  CLEAR  IS_FIELDCATALOG.

  IS_FIELDCATALOG-FIELDNAME   = 'COST_ELEMENT'.
  IS_FIELDCATALOG-SELTEXT_M   = 'COST_ELEMENT'.
  IS_FIELDCATALOG-COL_POS     = 2.
  APPEND IS_FIELDCATALOG TO IS_FIELDCATALOG.
  CLEAR  IS_FIELDCATALOG.

  IS_FIELDCATALOG-FIELDNAME   = 'COMPANY_CODE'.
  IS_FIELDCATALOG-SELTEXT_M   = 'COMPANY_CODE'.
  IS_FIELDCATALOG-COL_POS     = 3.
  APPEND IS_FIELDCATALOG TO IS_FIELDCATALOG.
  CLEAR  IS_FIELDCATALOG.

  IS_FIELDCATALOG-FIELDNAME   = 'FISCAL_YEAR'.
  IS_FIELDCATALOG-SELTEXT_M   = 'FISCAL_YEAR'.
  IS_FIELDCATALOG-COL_POS     = 4.
  APPEND IS_FIELDCATALOG TO IS_FIELDCATALOG.
  CLEAR  IS_FIELDCATALOG.

  IS_FIELDCATALOG-FIELDNAME   = 'LOCAL_CURRENCY'.
  IS_FIELDCATALOG-SELTEXT_M   = 'LOCAL_CURRENCY'.
  IS_FIELDCATALOG-COL_POS     = 5.
  APPEND IS_FIELDCATALOG TO IS_FIELDCATALOG.
  CLEAR  IS_FIELDCATALOG.

  IS_FIELDCATALOG-FIELDNAME   = 'BAL_LC'.
  IS_FIELDCATALOG-SELTEXT_M   = 'Balance LOCAL'.
  IS_FIELDCATALOG-COL_POS     = 6.
  APPEND IS_FIELDCATALOG TO IS_FIELDCATALOG.
  CLEAR  IS_FIELDCATALOG.

  IS_FIELDCATALOG-FIELDNAME   = 'GROUP_CURR_KEY'.
  IS_FIELDCATALOG-SELTEXT_M   = 'GROUP CURR KEY'.
  IS_FIELDCATALOG-COL_POS     = 7.
  APPEND IS_FIELDCATALOG TO IS_FIELDCATALOG.
  CLEAR  IS_FIELDCATALOG.

  IS_FIELDCATALOG-FIELDNAME   = 'GROUP_CURR'.
  IS_FIELDCATALOG-SELTEXT_M   = 'Balance in Group Curr'.
  IS_FIELDCATALOG-COL_POS     = 8.
  APPEND IS_FIELDCATALOG TO IS_FIELDCATALOG.
  CLEAR  IS_FIELDCATALOG.

 

 

 

 

DATA LO_W_PROGRM TYPE SYREPID.

  LO_W_PROGRM = SY-REPID.

  CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      I_CALLBACK_PROGRAM     = LO_W_PROGRM
      I_CALLBACK_TOP_OF_PAGE = 'TOP_OF_PAGE'
      IT_FIELDCAT            = IS_FIELDCATALOG[]
    TABLES
      T_OUTTAB               = TS_TAB_ERROR
    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.

 

 

 

 

 

 

***********************************************************************************************************************************

 

 

Error log.png

 

Step 3 : if All files are correct, no Error in records then user will click on execute button to load the data in application server and After loading data program will trigger process chain . once the data is load to application server after that data will be loaded to DSO and cube by process chain.

 

Load Data to application server

 

Code :

 

********************************************************************************************************************************

* Using this code we can load data to applicaiton server and further we will load to PSA * 

***********************************************************************************************************************************

 

 

  FORM LOAD_DATA_APP .


  DATA: LO_FILENAME      TYPE  STRING , "FILEEXTERN,
        LO_FILELINE      TYPE RSDS_CHAR1000.
  DATA: LO_FINAL         TYPE STRING,
        LO_PATH          TYPE STRING.
  DATA: LO_MESS(60).



  DATA : LO_EXCEP1 TYPE REF TO CX_ROOT,
         LO_TEXT TYPE CHAR100.

******************************************************************************************
**fetching file path

******************************************************************************************

  CLEAR : LO_PATH,
          W_FINAL1.


  LO_PATH = 'Application File Path'.

W_FINAL1 = 'Application File'

  TRANSLATE  W_FINAL1 TO UPPER CASE.

  CLEARLO_FINAL,
          LO_FILENAME.


  CONCATENATE LO_PATH W_FINAL1 INTO LO_FINAL SEPARATED BY '/'.

  LO_FILENAME = LO_FINAL.


**********************opening data file.******************************

  TRY.

      OPEN DATASET LO_FILENAME FOR OUTPUT IN TEXT MODE ENCODING DEFAULT MESSAGE LO_MESS .
      IF SY-SUBRC EQ 0.

        UNASSIGN <FS_IS_TEXT_DATA>.

        LOOP AT  TS_TEXT_DATA ASSIGNING <FS_IS_TEXT_DATA>.

          LO_FILELINE = <FS_IS_TEXT_DATA>.

          TRANSFER LO_FILELINE TO LO_FILENAME.


        ENDLOOP.

      ELSE.

        MESSAGE 'File Path issue To Unix Directory' TYPE 'I' DISPLAY LIKE 'E'.
        LEAVE TO SCREEN 0.

      ENDIF.


* Close data set.
      CLOSE DATASET LO_FILENAME.

    CATCH CX_ROOT INTO LO_EXCEP1.

      CALL METHOD LO_EXCEP1->IF_MESSAGE~GET_TEXT
        RECEIVING
          RESULT = LO_TEXT.

      MESSAGE LO_TEXT TYPE 'I' DISPLAY LIKE 'E' .

      LEAVE TO SCREEN 0.


  ENDTRY.



ENDFORM.        

 

 

 

***********************************************************************************************************************************

 

 

Trigger Process Chain :

Code

***********************************************************************************************************************************

 

   DATA:
      LO_EVENTID   TYPE BTCEVENTID,
      LO_EVENTPARM TYPE BTCEVTPARM,
      LO_SERVER    TYPE BTCSERVER.


  CLEAR LO_EVENTID.

  LO_EVENTID 'Write Event ID'.  {Event id which will Trigger Process Chain}

  CALL METHOD CL_BATCH_EVENT=>RAISE
    EXPORTING
      I_EVENTPARM           = LO_EVENTPARM
      I_SERVER              = LO_SERVER
      I_EVENTID             = LO_EVENTID
    EXCEPTIONS
      EXCPT_RAISE_FAILED    = 1
      EXCPT_RAISE_FORBIDDEN = 3
      EXCPT_UNKNOWN_EVENT   = 4
      EXCPT_NO_AUTHORITY    = 5
      OTHERS                = 6.


  IF SY-SUBRC = 0.
    MESSAGE 'Process has been succesfully Triggerd' TYPE 'I' DISPLAY LIKE 'S'.
    CALL TRANSACTION 'TCODE'.
  ENDIF.

 

 

 

***********************************************************************************************************************************

 

 

 

 

 

GEC_NGCF_LOAD.JPG

 

Step 4 : Load data to datasource and DSO

 

DSO data.GIF

By This way We can Automate the Whole Process and Data can be load to DSO and cube .

 

Non Legacy data will be available for BW reporting purpose.

RC12 & ABAP Short Dump ASSIGN_TYPE_CONFLICT & SYNTAX_ERROR during DTP Load & Transports

$
0
0

This article is based on SAP BI 7.30 version with support package 5.

 

Sometimes we would encounter ABAP short dumps during transports or during data load through DTP's for new developments or for changes in the existing developments.

 

Uncaught_Exception.jpg

These errors occur when the Infocube & DSO are changed & without recollecting the related transformations.  There are 2 possibilities which would occur

  1. ) Your transport might fail with RC12  throwing error “Uncaught_Exception” with an exception as “CX_RS_PROGRAM_ERROR” and the program which is terminated as “CL_RSO_TLOGO_PERSISTENCY======CP”.
  2. ) Your transport is successful and data load through DTP fails with the error “Assign_Type_Conflict”.

The reasons for these are that

  1. ) when the Infocube or DSO is changed, the program(new metadata) which is generated get’s updated with the time & date and the logic. The generated program in source is different to the one in target. So when you transport these changes of only the data target’s without the transformations(these transformations does not include the changes done to the Infocube), the program gets updated in the target system. But the transformations in the target system are still pointing to the old generated program (this is orphaned metadata). This is when you would get a data load error “Assign_Type_Conflict” through DTP load.

During Data Load:


During Data Load.jpg

During Transports:

During Transports.jpg

 

The way to rectify this is using the SAP Note 1627236 which I have given below in a simpler format.

 

In a gist:

  1. ) Delete the inconsistencies in the transformations using function module in the source system.
  2. ) Re-Collect the transformations in a new transport.
  3. ) Delete the inconsistencies in the transformations using function module in the target system.
  4. ) Transport the newly collected objects to the target system.

In detail:

  1. ) Run the function module “RSTRAN_ROUT_RSFO_CHECK” using SE38 in the source system. SE38a.jpg
  2. ) Copy the technical ID of the transformation which is causing error and paste it in the function module. RSTRAN 1.jpgRSTRAN 2.jpg
  3. ) Run the program for the the transformation  with both “M” & “A” object versions with the option “Simulate” selected.
  4. ) If there is no error then you would get a message  as RSTRAN 3.jpg else it will display the error message.
  5. ) Once running the program with “Simulate” option is complete, run it with “Repair_W” option checked for both “A” & “M” options. Choose option “Yes”. If it asks for a transport then collect it else after this step is done, collect the transports again in a new transport.RSTRAN 4.jpgRSTRAN 5.jpgRSTRAN 6.jpg
  6. Note: The steps given above have to be done exactly the same way in target system before doing the transports
  7. If there are multiple transformations, it’s good to collect each of them in a separate transport along with their DTP's. This helps in identifying the transformation which is throwing error(if in case you get the error again).
  8. Once the above steps are complete in the target system, transport the requests from source to target system.
  9. So as to cross check, when you re-do the steps above you would get the msg RSTRAN 3.jpg.

 

 

Related SAP Notes: 1627236, 18013091913191.


Featured Content for SAP NetWeaver Business Warehouse

$
0
0

Establish a Rock Solid Enterprise Data Warehouse for a Single Version of the Truth

http://www.sap.com/pc/analytics/data-warehousing/software/netweaver-business-warehouse/index/_jcr_content/sublevelfeature/image.sapimage.jpg/1344607637196.jpgCapture, store, and consolidate your vital information with our enterprise data warehouse platform, SAP NetWeaver Business Warehouse (SAP NetWeaver BW). Tightly integrate your warehousing capabilities for a single version of the truth, decision-ready business intelligence, and accelerated operations. Supercharge your data warehouse environment with SAP NetWeaver BW powered by SAP HANA. Leverage reliable data acquisition, business modeling, and analytic capabilities. Extend your applications to reach more business users with minimal IT effort. Reduce total cost of ownership by automating design and development processes

 

Listen to Dr. Vishal Sikka, Member of the SAP Executive Board!

In this interview from SAP Teched in Bangalore, he is talking about SAP NetWeaver BW on SAP HANA. Watch this video from SAPTechEd India showfloor. January 2013

 

Good News - Easier Modeling of the SEM Add-On in Solution Manager

Recently the following option was made available for the usage of the SEM component on top of an existing AP NetWeaver BW  system starting from release SAP NetWeaver 7.0. Now you can define the SEM component as a "normal" Add-On on top of the SAP NetWeaver BW system. This makes the creation of the stack.xml for the usage of the software update manager and the database migration option not anymore a big hurdle. Read more... November 2013

Overview SAP BW 7.4 SP5 on SAP HANA and further Roadmap

SAP NetWeaver BW on SAP HANA continues to be the  cornerstone of SAP’s strategic vision for enterprise data warehousing providing organizations a solid data foundation to capture, store, transform and manage data in a scalable, enterprise-ready data warehouse. And as new challenges arise in the market (exploding data volumes, new data sources, the need for real-time information access, etc), SAP BW on HANA continues to evolve in order to meet the growing challenges imposed on IT by these ever changing market forces. The release of SAP BW running on SAP HANA is a great example of how SAP BW has evolved to ensure organizations continue to leverage  their investment in SAP BW to meet these new  challenge.

See this presentation to learn what SAP is doing next to evolve SAP BW on SAP HANA with  SAP BW 7.4., SP 5 on SAP HANA. October 2013

 

The Support Package Stack 10 for SAP NetWeaver 7.3 is released!

See BW specific information on the page SAP NetWeaver 7.3  BW ABAP Support Packages - NewsSeptember 2013

 

SAP EDW Positioning

Check out this presentation that is positioning EDW based on the SAP Real-Time data platform by Lothar Henkes. August  2013

 

Scale Out - Best Practices

Check out this latest comprehensive overview on the delta information for scale out implementations by Marc Hartz. Jun  2013

 

See also  the Recently Featured Content for SAP NetWeaver BW..

HowTo create an ABAP process type with a return code (red/green) for use in a process chain in BW 7.x

$
0
0

Introduction

Various customers have asked me how they could integrate the execution of an ABAP program followed by a return code (red/green) inside a process chain in SAP BW 7.x. This document describes the steps that have to be performed to allow for this functionality.

 

Audience

SAP BW Administrators / Developers.

 

Table of Contents

Introduction

Audience 

Table of Contents

1. Creation of the process type

2. Integration of the process type

 

1. Creation of the process type

This chapter describes the steps to create the new process type that allows for the integration of an ABAP program with a return code (red/green) inside a process chain.

 

Step 1: Log on to the BW system.

 

Step 2: Execute transaction <RSPC>.

 

Step 3: Open/Display a process chain.

 

Step 4: Go to the menu <Settings><Maintain Process Types>.

 

RSPC - Settings - Maintain Process Types.jpg

 

Step 5: Select the entry where the process type equals <ABAP>.

 

Step 6: Go to the menu <Edit><Copy As>.

 

RSPC - Settings - Maintain Process Types - Copy As.jpg

 

Step 7: Apply the settings as shown in the picture below and press <Enter>.

 

Process Type ZABAP.jpg

Step 8: Save the new process type.

 

Process Type ZABAP - save.jpg

 

2. Integration of the process type

This chapter describes the steps that are required to integrate the new process type in a process chain.

 

Step 1: Log on to the BW system.

 

Step 2: Execute transaction <SE38> and enhance the program for which you want to raise a return status Green "MESSAGE i000(zz)" or Red (MESSAGE i000(zz)) as shown in the example below.

ZABAP_RETURNCODE_SAMPLE.jpg

 

Step 3: Open the process chain in which you want to include the new process type.

 

Step 4: Double-click the <ABAP Program with return Status> process type and fill out the required fields as shown in the picture below.

 

ZABAP_RETURNCODE_SAMPLE - Create.jpg

 

Step 5: Enter the program name and set the properties for the ABAP program.

ZABAP_RETURNCODE_SAMPLE - Define.jpg

 

 

Step 6: Add the additional steps for the process chain in case of 'Green' or 'Red'.

 

ZABAP_RETURNCODE_SAMPLE - process chain view.jpg

SAP First Guidance - SAP-NLS Solution with Sybase IQ

$
0
0

This “SAP First Guidance” document should help to quickly implement the new released option to store historical BW data on an external IQ Server for System Performance of Preparation of a migration to BW powered by HANA. Please Note that the SAP-NLS Solution can be used with all supported Database Versions supported by SAP NetWeaver BW 7.3x. The Existence of SAP HANA is not necessary. The document is “work in progress” and not intended to be exhaustive, but it contains everything to successfully implement the SAP-NLS Solution with Sybase IQ. For more Information please contact roland.kramer@sap.com.

View this Document

SAP First Guidance - BW Housekeeping and BW-PCA

$
0
0

The system copy procedure of SAP NetWeaver BW systems and landscapes is complex for a number of reasons however. There are a large number of configuration settings (such as connections and delta queue handling for data loading) and system copy scenarios of SAP NetWeaver BW (each with different landscape aspects) for example that have to be handled as part of every system copy, regardless of whether the system copy is part of the migration to SAP HANA or if you want to perform regular system copies of your SAP NetWeaver BW landscape.

View this Document

Implementation - BW on HANA Export/Import

$
0
0

This First Guidance document should help to quickly implement either a fresh SAP NetWeaver BW on SAP HANA installation or an export of an existing system with any DB export. As the technical installation steps are the same the guidance should make an own created customer specific documentation obsolete and is the complementary documentation to the existing e2e guide for migration SAP NetWeaver BW on SAP HANA. This Version adds a Chapter for the System Export Preparation and Reflects the latest Changes for BW 7.30/7.31, HANA 1.0 SP05 and the SL toolset 1.0

View this Document

Viewing all 1574 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>