Step by Step Procedure to Extract Data from R/3 to BI 7.0 using Query

This article demonstrates a step-by-step process for doing generic extraction from R3 into BI using Infoset query. It also describes the creation of User Groups,Infoset query and BI objects like InfoObjects, DTP, Transformations and also includes the steps to install Objects from BI Content.
click here

Virtual KeyFigures/Characteristics

Need for Virtual KF

When we need to commit values during query execution and if the syntax is too complex to introduce it in CKF/RKF/Formula; and in a scenario where we don’t want to go for Data Provider remodeling to introduce a new KF

This will make the report more flexible and dynamic.

Virtual Key Figure will be defined inside the data provider as metadata and won’t contain any physical value.

How to create one?

Same ways as you create any other basic KF or characteristics.

Goto RSA! ->  Select InfoObjects -> Select your Catalogue -> Create a new Keyfigure/Char -> Description/Technical name define it as a virtual KF/Char -> Save it -> Goto to your infoProvider-> Insert the newly created KF -> Goto your Query Designer introduce the new object

In normal case you need to implement a BADI to insert values to virtual KF.

Check Links below;

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e051fda8-71a9-2a10-ac9e-8d17414a8c8c

http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/3506

SAP BW 3.5 Function Details

This document can be used as a handbook for understanding SAP BW 3.5 objects/functionalities. Click the link below
SAP_BW_3.5_Functoin_Detail

Inconsistent ODS/Infocube during data updation

Back in 2007 I faced an issue with inconsistent ODS object. We were not able to activate some queue requests, And considering data reloading was a herculean task.

The error message was similar to one below;

“DSO XXX inconsistent; request REQU_XXX only exists in RSODSACTREQ”

“ODS Activation failed with status :5”

We faced a similar scenario today, that’s why I thought about noting this down. You will get ample material in internet explaining about this.

One solution is to delete the request from request queue (manage screen) and also from the table RSODSACTREQ (Activation table of M-requests to change-log requests) and try to activate the data in ODS.

Or

Use Transaction RSRV (Analysis and repair for BI objects) -> All Elementary Tests-> ODS Objects -> Check the Status of the Generated Program of a Data Store Object -> give  ODS name->Execute.

 If it fails, then click Correct Error Tab & execute again. Check once more and activate ODS object

Sales and Distribution - Tables and Structures

Sales Document
VBAK Sales Document - Header Data
VBKD Sales Document - Business Data
VBUP Item Status
VBAP Sales Document - Item Data
VBPA Partners
VBFA Document Flow
VBEP Sales Document Schedule Line
VBAKUK Sales Document Header and Status Data
VBUK Header Status and Administrative Data
VBBE Sales Requirements: Individual Records

SD Delivery Documemt
LIPS Delivery Document item data
LIKP Delivery Document Header data

Billing Document
VBRK Billing:Header data
VBRP Billing:Item data

Material Master
MARA General Material Data
MVKE Sales Data for Material
MARC Plant Data for Material
MARD Storage Location Data for Material

Customer Master
KNA1 General Data
KNB1 Customer Master (Company Code)
KNB4 Customer Payment History
KNB5 Customer master (dunning data)
KNBK Customer Master (Bank Details)
KNBW Customer master record (withholding tax types)
KNKA Customer Master Credit Mgmt.
KNKK Customer Master Credit Control Area Data (credit limits)
KNVA Customer Master Loading Points
KNVD Customer master record sales request form
KNVH Customer Hierarchies
KNVI Customer Master Tax Indicator
KNVK Customer Master Contact Partner
KNVL Customer Master Licenses
KNVP Customer Master Partner Functions
KNVS Customer Master Shipping Data
KNVT Customer Master Record Texts for Sales
KNVV Customer Master Sales Data
KLPA Customer/Vendor Link

Pricing
KOMK Pricing Communications-Header - Structure
KOMP Pricing Communication Item - Structure
KONV Conditions (Transaction Data)
KONP Conditions (Item)

Output
NAST Message Status

SD Shipping Unit
VEKP Shipping unit item (Content)
VEPO Shipping Unit Header

Delivery Due Index - item
VBUP: Item status
VBAP: Sales document: Item data
VBKD: Sales document: Business Data
VEBA: Contract
VBLB: Forecast delivery schedules
VBEP: Sales document: Schedule line
VBBE: Individual requirements
VBBS: Summarized requirements
VBUV: Incompletion log
VBFA: SD document flows
VBPA: Partner
JSTO: PP status
NAST: Output
STXH: Texts: Header
STXL: Texts: Lines
KONV: Conditions

SALES - header
VBUK: Header status and administrative data
VBAK: Sales document: Header data
VBKD: Sales document: Business Data
VAKPA: Partner index
VEDA: Contract
VBPA: Partner
VBUV: Incompletion log
VBFA: SD document flows
VMVA: Matchcodes
STXH: Texts: Header
STXL: Texts: Line
NAST: Output
JSTO: PP status

Sales activities
VBKA Sales activity
VBUV: Incompletion log
VBPA: SD document: Partner
SADR: Address
VBFA: SD document flows
NAST: Output
STXH: Texts: Header
STXL: Texts: Lines

Logical database:
AK V: Sales documents

Bill of Material (BOM)
MAST Material assignment to BOM
EQST Equipment assignment to BOM
KDST Sales order assignment to BOM
DOST Document assignment to BOM
STST Standard object assignment to BOM
TPST Functional location assignment to BOM
STKO BOM header data
STZU Time-independent STL data
STAS BOM item selection
STPO BOM item data
STPU BOM sub-item data

Material
MARA General material data
MAKT Short texts
MARM Conversion factors
MVKE Sales data (for each sales organization and distribution channel)
MLAN Sales data (for each country)
MAEX Export licenses
MARC Plant data
MBEW Valuation data
MLGN Warehouse management inventory data
MLGT Warehouse management inventory type data
MVER Consumption data
MAPR Pointers for forecast data
MARD Storage location data
MCH1 Cross-plant batches
MCHA Batches
MCHB Batch stocks
KNMTK Header table
for increased performance
KNMT Data table

Logical databank for material master
CKM Material master
MSM Material master

Customer
KNA1 Customer master, general information
KNVK Contact person
KNVV Customer master, sales area
KNVA Unloading points
KNVI Tax indicators
KNVP Partner functions
KNVD Documents
KNVL Licenses
KNVS Shipping data

Sales and Distribution (SD)
VBFA Document flow (alg.)
VTFA Flow shipping documents

Sales order
VBAK Header data
VBAP Item data
VBPA Partners in sales order
VBKD Sales district data
VBEP Data related to line items, delivery lines

Billing document
VBRK header data
VBRP Item data

Shipping
VTTK Shipment header
VTTP Shipment item
VTTS Stage in transport
VTSP Stage in transport per shipment item
VTPA Shipment partners
VEKP Handling Unit - Header Table
VEPO Packing: Handling Unit Item (Contents)

Delivery
LIKP Delivery header
LIPS Delivery item

Pricing
KONH Conditions header
KONP Conditions items
KONV Procedure ( billing doc or sales order)
KOND contracts
VEDA Contract data

orginal link

SAP GUI 7.20 Download

This is a new release for SAP GUI compatible with Windows7 and Office2010. Please click the link and download the file directly.


The new SAP GUI release comes with a number of useful new features:
- Support for Windows 7 operating system & Office 2010 package (32bit version)
- SAP Logon: Hierarchical organization of items in an explorer like view and a tree like view.
- SAP Logon: With release 7.20, an administrator can define a central saplogon.ini which can be merged into the local user specific saplogon.ini.
- Options Dialog: Almost all options have been merged into a new user friendly dialog that replaces Tweak SAP GUI and the old options dialog.
- Security Enhancements: A set of maintainable security rules which allow administrators and users to prevent unwanted access to the client PCs from SAP systems have been defined.
- Animated Focus Frame: Improved visualization of the focus and its movement across the screen.
- High Contrast Theme for SAP Signature Design: Improved visual design for users with visual impairments, based on the successful SAP Signature Design.
- Better organization of local data: Downloaded files, traces, scripts and other local objects are stored in different folders (roaming and local) according to Windows standards.

Besides this SAP GUI for Windows 7.20 is fully compatible with older SAP GUI releases.

Since SAP GUI for Windows 6.20 will be out of maintenance as of 1st of January 2011 and SAP GUI for Windows 7.10 will be out of maintenance as of 13th of April 2011 we recommend to start planning the upgrade to release 7.20 as soon as possible.

Download link

Infopackage dynamic selection routine

This will explain , how to give dynamic selection for periodic loading using infopackages.
After creating an infopackage go to "Data Selection" tab. Give Type - 6 Abap Routine for the required selection criteria. Here I am loading the data with selection "Previous Month" (0calmonth).

Give a description and click enter. It will move to the Scheduler routine screen.


Enter the code as below (highlighted).

*$*$ begin of routine - insert your code only below this line *-*
data: l_idx like sy-tabix.
read table l_t_range with key
fieldname = 'CALMONTH'.
l_idx = sy-tabix.
*....
l_t_range-low = sy-datum(6) - 1.
l_t_range-high = sy-datum(6) - 1.
modify l_t_range index l_idx.

p_subrc = 0.

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

Save this.

This will make the month range to previous month . "l_t_range" table is of type structure RSSDLRANGE (contains Sign, Option, Low, High). We need to populate these fields to pass range dynamically.