You are on page 1of 15

Extraction from R/3 (Business Content ) into SAP BW

Extraction from Business Content (R/3) into SAP BW


Example(Materials Management: Purchasing Groups)
(2LIS_02_S011)
Steps in SAP R/3 Side
1. Logon to SAP R/3 System

2. Install the Required Data Source for Business Content Data Source
Enter T Code: RSA5
Or SBIW
Expand Business Content Data Source
Click on Execute icon
Expand SAP R/3
Expand MM
Expand MM-IO
Select 2LIS_02_S011

Note: To display the Extract Structure for this Data Source, double click on the Data
Source. Displays the Extract Structure (S011BIWS).
Direct Access: D (Virtual Access not possible/ Direct Access Possible)
Delta Update: Checked Checkbox, i.e Supports Delta Update

Click on Back or F3

Place the cursor on the Data Source (2LIS_02_S011),


click on the Transfer Data Source Button

Message: Carry out Repairs?


Yes
Click on Back or F3 (Easy Access Screen)

3. Check the data in Data Source using Extractor Checker


Enter T Code: RSA3
Data Source Name: 2LIS_02_S011 #Enter#
Displays the fields
Note: To display the maximum no. of records in the Data Source
Data Records/Calls: set to 500 from 100 (Default)
(i.e. No. of records in Data Packet)
Display Extractor Calls: set to 40 from 10 (Default)
(i.e No. of data packets)
Click on Extraction button
Message: Data Source contains 2014 records.
Select Display List Button or Output List icon
Click on Back or F3

Steps in SAP BW Side

4. Logon to SAP BW

5. Make sure that SAP R/3 Source System exists in SAP BW


Enter TCode: RSA13 #Enter#

6. Replicate the Data Source from SAP R/3 to SAP BW


6.1 Display the Application Component Hierarchy
Double Click on R/3 Source System

Expand BW Data Source


Expand R/3 Source System
Expand SAP R/3 Application Component
Expand Material Management
Select the Data Source Purchasing Groups (2LIS_02_S011)

Note: If the Data Source is already assigned to an Info Source, no need to do


anything.
(- to + icon)

#Select# the + icon


Message: Do u really want to delete assignment? Yes
Click on Back or F3
Now Observe the - symbol
#Select# the Data Source
Context Menu
#Select# Replicate Data Source

#Select# Refresh Tree

7. Assing Info Source to Data Source


#Select# your Data Source
Context Menu

Select Assign Info Source


Info Source Assignment:#Select# Content (Business Content) (2LIS_02_S011)
Application Proposal (2LIS_02_S011)
Others
Continue

7.1 Installing Characteristic and Key Figures Info Objects


Maintain Required Grouping options
#Select# Grouping button
#Select# Only Necessary Objects
7.2 Install the Characteristic, Key Figure Info Object Catalogs
#Select# Info Objects under Business Content Menu
#Expand# Supply Chain Management
#Expand# Purchasing (0MMPUR)
Select Char. Info Object Catalog ()MMPUR_CHA01) (Purchasing Char.s)
Drag and drop into Collected Objects panel
// Shows Window; Close
Select Key Figure Info Object Catalog ()MMPUR_KYF01) (Purchasing KFs)
Drag and drop into Collected Objects panel

Select Install and Match CheckBoxes for


MM Purchasing Groups
MM Char.s
MM Key Figures

Select Source System Assignment button


#Select# Your R/3 Source System
Continue

Select Collection Mode


#Select# Collect Automatically

Select Activate and Install Button


#Select# Install

Note: Repeat the Activation process until the selected Objects are are installed and
activated without errors.

Note: To Verify if the installed completely


#Select# Modeling (Purchasing Groups)
Observe the + icon, then the Assignment and Activation completed
Click on the + icon
// Observe the Status: Active and Transfer Rules: Active
Click on Back or F3

8. Install the Required Info Cube from Business Content


#Select# Business Content
#Select# Data Target
#Expand# Supply Chain Management
#Expand# Purchasing (0MMPUR)

Maintain Required Grouping

#Select# Grouping button


#Select# Only Necessary Objects

Select Purchasing Group (0PUR_C04) (target for Info Source)


Drag and drop into Collected Objects

#Select# Source System Assignment


#Select# Your R/3 Source System
Continue

#Select# Collection Mode


#Select# Automatically

In Collect Objects
Purchasing Groups select Install and Match Checkboxes

Click Activate and Install


#Select# Install

Select Info Providers Modeling


Click on Refresh Tree

Click on Find icon, Search for Info Cube (0PUR_C04)

9. Create Update Rules on the Info Cube using Info Source


#Select# your Info Cube 0PUR_C04

Context Menu
#Select# Create Update Rules
Check Info Source Radio Button (2LIS_02_S011) #Enter#
#Select# Activate

Click on Back or F3

10. Show Data Flow or Display Graphics


#Select# Your Info Cube
Context Menu
#Select# Show Data Flow
// Displays Data Flow graphic
Close the Window.

11. Schedule/Load Data


11.1 Create Info Package
Select Info Source Modeling
Find for 2LIS_02_S011
#Expand# Your Application Component MM or
#Expand# Purchasing
#Expand# Purchasing Groups
#Select# R/3 Source System
Context Menu
#Select# Create Info Package

Description: Info Package for Purchasing Groups


#Select# the Data Source Purchasing Groups
Continue
#Select# Processing Tab
Check the radio button PSA and then into Data Targets (Package by Package)
// To display the graphic select ? icon

#Select# Data Targets Tab


#Select# Select Data Target (Radio Button)
Check the Checkbox Update Data Target

#Select# Update Tab


Check the Radio button Full Update

Select Schedule Tab


Check the Radio Button Start data load immediately

Click on START button

12. Monitor the data


#Select# the Monitor icon
12.1 Check the data in the PSA
Place the cursor on the Request Status
Click on the PSA Maintenance icon
Continue
// Displays the data extracted from R/3 to BW

Click on Back or F3

12.2 Check the data in the Info Cube


#Select# Manage Data Targets icon
#Select# Your cube
#Click# Contents button
#Click# Fields selection for output
#Select# Required Char.s for Dimensions
Check the required Char.s
Execute
Execute
// Displays the data in the Info Cube

Common Tables used by SAP MM


Below are few important Common Tables used in Materials Management Modules:
EINA Purchasing Info Record- General Data
EINE Purchasing Info Record- Purchasing Organization Data
MAKT Material Descriptions
MARA General Material Data
MARC Plant Data for Material
MARD Storage Location Data for Material
MAST Material to BOM Link

MBEW Material Valuation


MKPF Header- Material Document
MSEG Document Segment- Material
MVER Material Consumption
MVKE Sales Data for materials
RKPF Document Header- Reservation
T023 Mat. groups
T024 Purchasing Groups
T156 Movement Type
T157H Help Texts for Movement Types
MOFF Lists what views have not been created
A501 Plant/Material
EBAN Purchase Requisition
EBKN Purchase Requisition Account Assignment
EKAB Release Documentation
EKBE History per Purchasing Document
EKET Scheduling Agreement Schedule Lines
EKKN Account Assignment in Purchasing Document
EKKO Purchasing Document Header
EKPO Purchasing Document Item
IKPF Header- Physical Inventory Document
ISEG Physical Inventory Document Items
LFA1 Vendor Master (General section)
LFB1 Vendor Master (Company Code)
NRIV Number range intervals
RESB Reservation/ dependent requirements

T161T Texts for Purchasing Document Types

Tcodes:

RFQ to Vendor - ME41


Raising Quotation - ME47
Comparison of Price - ME49
Creation of PO - ME21N
Goods Receipt - MIGO
Invoice (Bill PAssing) - MIRO
Goods Issue - MB1A
Physical Inventory - MI01( Create doc)
MI04 (Enter Count)
MI07 (Post)

AP Event Processing
July 3rd, 2008 Posted in BASIS, Configuration

An SAP event is a flag that is created by using transaction SM62 View and
Maintain Background Events. The commonest use of Events is to trigger jobs.
Events can be triggered from the Operating System or from within SAP either
within ABAP programs and Function modules or from Transaction SM64.

Create an Event in transaction SM62. Select the Maintain radio button next to User
Event Names and execute. This will present tyou with the Edit User Events screen.
You can add change or delete user events from here.

To use this Event as a trigger, create a job via transaction SM36. You specify the
Event that will trigger this job using the Start Condition button. On the Start
Condition screen, select option AFTER EVENT. The After Event fields will open for
input. Fill these in and Save.

You can see which jobs are waiting for events by looking at table BTCEVTJOB (via
transaction SE16). This is the systems way of keeping track of which jobs are in the
queue waiting for an event to occur. The EVENTID column contains those Events
that will submit a Job. You should see several System Events here.

Now, once the event is triggered this newly created job will execute. The event can
be triggered via transaction SM64 or from the Operating System (see below).

To get the event triggered from the Operating System, log into the <sid>adm user
id (at the Operating System level) level and go to directory
/usr/sap/<sid>/SYS/exe/run. Note that in the Unix / Linux implementations, there is

an alias cdexe that will get you there as well. Run the SAPEVT executable as
follows :

sapevt <event_name> -t pf=<instance_profile_directory_and_name>


nr=<sys_number>

Example:

sapevt roberts_test -t pf=/usr/sap/DEV/SYS/profile/DEV_DVEBMGS00_server001


nr=00

This will raise the event, and cause the job scheduled within SAP to execute. Once
the job has executed the SAP event that was in the table BTCEVTJOB will disappear.

Every time a Background Job is run, an entry is created in table TBTCO. This
contains entries such as JOBNAME, EVENTID, EVENTPARM, JOBCLASS etc. This
means that once youve found your job name in this table (using SE16) you can
double click on its entry and see that it was executed via an event.

RSPC_MIGRATE_INFOPACKAGE_GROUP(to convert infopackage group to a process


chain)

RSPC_MIGRATE_EVENT_CHAIN ( to convert an event chain to a process chain)

I have not tried the event chain stuff, but you can go to SE37 and type in
RSPC_MIGRATE_INFOPACKAGE_GROUP. Do a single test (F8) and put in the technical
name of your InfoPackage group. It will then pop up for you to enter a name and
description for the new process chain. Further you will have to go into RSPC and
actiavte this process chain. I think it would have been simpler to click on process
chain maintenance from within the InfoPackage group.

a) There are only 3 ways you can trigger an event


1) Run transaction SM64
2) Call the function BP_RAISE_EVENT from within a program.
3) Run the program "sapevt" at OS level

You can Create a Event in the SM62


but you need to raise this event in a program using the function BP_RAISE_EVENT
The following example may help:
eventid = 'ZYPAYEVNT'.(name of the event)
eventparm = 'SUCCESS'.(identification of the event)
FORM RAISE_EVNT.

CALL FUNCTION 'BP_EVENT_RAISE'


EXPORTING
EVENTID = EVENTID
EVENTPARM = EVENTPARM
TARGET_INSTANCE = ' '
EXCEPTIONS
BAD_EVENTID = 1.

ENDFORM. " RAISE_EVNT


Once an event is created, you can schedule

background jobs to wait for the event to be triggered. Syntax and arguments
passed to the sapevt program can be found in the SAP documentation.