SAP BI Sales Analysis Configuration Document

SALES ANALYSIS Configuration Document

Table of Contents

 

1      Part-1: Organisation Structure 3

2      Part-2: Global Settings 3

3      Part-3: Final Config Settings 3

3.1.1     Customising for extractors 3

3.1.2     Logistics Extract Structures Customizing Cockpit 4

3.1.3     Set Application Active Indicator 4

3.1.4     Deleting BW Setup Data_ 5

3.1.5     Setup Sales Data_ 6

3.1.6     Replicating DataSources 6

3.2       Activating Business Content 7

3.2.1     Assigning Source System for Activation_ 7

3.2.2     Activating Business Content: InfoObject Catalogs 8

3.2.3     Activating Business Content: InfoCubes 8

3.2.4     Loading Data_ 10

3.2.5     Loading Transaction Data_ 11

 

1      Part-1: Organisation Structure

2      Part-2: Global Settings

3      Part-3: Final Config Settings

3.1.1      Customizing for the Extractors

	Config-ID and Title:	Define settlement profile
	Organization/Area:	SALES ANALYSIS
	ERP Responsible:	BW Team
		File Name:	Sales_Analysis_Config.doc
Responsibility:	BW Team	Status:	Open / Closed

Enhancement

You need to perform the following steps:-

1.     First identify the DataSorce in which enhancement has to be done.

2.     Append  the respective fields to Extract Structure.

3.     Edit DataSources and Application Component Hierarchy.

4.     Required Changes in User Exits.

Following enhancement has been done for V_SD_C03

1.     Obtain Cycle wise Week

Following Changes or activities has been done for enhancement.

1.     Appended ZZCALWEEK MC11VA0ITM, MC11VA0HDR, MC12VC0ITM, MC12VC0HDR, MC13VD0ITM, MC13VD0HDR

2.     The DataSource has opened in edit mode and removed the HIDE check.

Enahancement in Transfer Rule

a.   For Storage Location

Included the field in the communication structure and altered the transfer rules for the 2 item info sources(2LIS_11_VAITM,2LIS_12_VCITM).

3.     Created ZBW_TR project for below mentioned Exits.

·         EXIT_SAPLRSAP_001

·         EXIT_SAPLRSAP_002

·         EXIT_SAPLRSAP_003

·         EXIT_SAPLRSAP_004

4.     User Exit EXIT_SAPLRSAP_001 has modified for the required fields.

Use

If you want to transfer data from a source system into a BW using a Business Content DataSource, then you have to first transfer the data in the source system from the D version into the active version (A version).

This activity is also required for the use of InfoCube Sales Analysis ( V_SD_C03). If you performed it already you do not have to do it again. In that case you can skip this chapter.

Procedure

This step has to be carried out in the R/3 system.

SAP R/3 – role menu	Transfer Business Content DataSources
Transaction code	RSA5

1.     On the Installation of DataSource from Business Content view expand the node SAP-R/3 (SAP Application Components), mark the relevant DataSources (see table below) and choose Select Sub-tree +/- .

2.     Once you have selected all required DataSources and nodes choose Trans. DataSources from the application toolbar.

3.     If a dialog box appears requesting the user to enter a development class enter the appropriate development class and choose Save.

4.     Choose Back.

Relevant DataSources

Path	Relevant DataSources
SD à SD-IO	All DataSources as per Annexure-Master Data
SD	2LIS_11_VAITM
SD	2LIS_11_VAHDR
SD	2LIS_12_VCITM
SD	2LIS_12_VCHDR
SD	2LIS_13_VDITM
SD	2LIS_13_VDHDR

3.1.2      Logistics Extract Structures Customizing Cockpit

Carry out the following steps in SAP R/3.

Procedure

1.     To customize the logistic extract structures, choose:

SAP R/3 Role Menu	Logistics Extract Structures Customizing Cockpit
Transaction code	LBWE

2.     Expand the nodes Logistics applications  ® 11: SD Sales BW à Extract structures.

3.     For all DataSources transferred in previous step, click on Inactive in column Update of the line containing the extract structure.

If the system prompts you for a customizing request enter the appropriate customizing request or create a new one.

4.     In the column Update Mode of the line containing the Sales Application 11: SD Sales the entry should be Queued Delta. If this is not the case click on the entry. On the Select Update Mode dialog box select Queued Delta and choose Continue.

5.     On the Notifications MCEX 167 dialog box choose Continue.

6.     Choose Back twice.

7.     Repeat steps 2-6 for 12: LE Shipping BW and 13 SD Billing BW

Result

You have activated the update of the extract structures.

Transaction data will be written into the extract structures from now on.

3.1.3      Set Application Active Indicator

This step has to be carried out in SAP R/3.

Procedure

This is a cross-client operation. If it has been done for the same system before, just skip this section.

SAP R/3 – role menu	Set Application Active Indicator
Transaction code	BF11

1.     Mark the checkbox on the BW application line.

2.     Save the change.

3.1.4      Deleting BW Setup Data

Carry out the following steps in the SAP R/3.

Procedure

1.     To delete the setup data, choose:

SAP R/3 – role menu	Deleting BW Setup Data
Transaction code	LBWG

2.     Enter the relevant application number 11.

3.     Choose Execute

4.     Confirm the warning message with Yes.

5.     Repeat Steps 2-4 for application numbers 12 and 13

6.     Choose Back.

3.1.5      Setup Sales,Shipping,Billing Data

This step has to be carried out in the SAP R/3.

Procedure

1.     To setup the Sales data, choose:

SAP R/3 – role menu	Setup sales data
Transaction code	OLI7BW

2.     On the Statistical Setup of Info structures from purchasing documents screen, make the following entries:

Field	Entry
Name of run	Any name
New run	X
Date of Termination	Enter a date in the future (e.g. tomorrow)
Time of termination	Time in the future

3.     Choose Execute.

4.     On the Information dialog box confirm the message with Continue.

5.     Choose Back twice.

6.     To setup the Delivery data, choose:

SAP R/3 – role menu	Setup Shipping Data
Transaction code	OLI8BW

3.     On the Statistical Setup of Info structures from purchasing documents screen, make the following entries:

Field	Entry
Name of run	Any name
New run	X
Date of Termination	Enter a date in the future (e.g. tomorrow)
Time of termination	Time in the future

7.     Choose Execute.

8.     On the Information dialog box confirm the message with Continue.

9.     Choose Back twice.

10.  To setup the Billing data, choose:

SAP R/3 – role menu	Setup Billing Data
Transaction code	OLI9BW

4.     On the Statistical Setup of Info structures from purchasing documents screen, make the following entries:

Field	Entry
Name of run	Any name
New run	X
Date of Termination	Enter a date in the future (e.g. tomorrow)
Time of termination	Time in the future

11.  Choose Execute.

12.  On the Information dialog box confirm the message with Continue.

13.  Choose Back twice.

3.2      Replicating DataSources

This activity has to be carried out in SAP BW.

Procedure

1.     To replicate the DataSources from the source systems, choose:

SAP BW – role menu	Replicating DataSources for R/3 System
Transaction code	RSA13

2.     On the Administrator Workbench: Modeling screen:

a.     Select your R/3-Source System in the right hand window.

b.    From the context menu choose Replicate DataSources.

3.2.1      Activating Business Content

3.2.1.1      Assigning Source System for Activation

Use

When you activate Business Content, DataSources from source systems are assigned to InfoSources in BW. If you do not select a source system, all source systems are automatically assigned. If you have several source systems, this may take a lot of time because also transfer rules have to be activated for each DataSource from each source system.

However, an assignment of a DataSource to an InfoSource may not be necessary for all existing source systems.

Assign only the source systems you need to load data from for the Business Content Objects that you are going to activate.

You can subsequently change the selection you made.

Procedure

To assign a source system, choose:

SAP BW Role Menu	Assigning Source System for Activation
Transaction Code	RSORBCT

Then carry out the following steps:

1.     In the Administrator Workbench: Business Content view choose Edit ® Source System Assignment.

2.     In the Choose source system by default? dialog box select the checkbox in the column Default assignment in the row containing the source systems you need to load data from.

3.     Choose Continue.

Result

By assigning the source systems, you limit the assignment to the DataSources from the assigned source systems only. This reduces the time for activation.

3.2.2      Activating Business Content: InfoObject Catalogs

Use

Carry out the following steps in SAP BW.

Procedure

1.     To activate the relevant InfoObject Catalogs in business content, choose:

SAP BW – role menu	Replicating DataSources for R/3 System
Transaction code	RSORBCT

2.     On the Administrator Workbench: Business Content screen:

a.     At the top of the right frame, choose Grouping and select In Data Flow Before.

b.    At the top of the right frame, choose Collection mode and select collect automatically.

c.     In the left frame, select Object types.

d.    In the middle frame, expand InfoObject Catalog and double-click Select Objects.

e.     On the Input help for Metadata dialog box.

i.      Select the following InfoObject catalogs:

-         0SD_CHA01

-         0SD_KYF01

      For multiple selection use the Ctrl-Key.

ii.     Choose Transfer selections.

f.     If a dialog box Exceeded runtime when collecting objects appears choose Continue.

g.    At the top of the right frame, choose Install and select Install in Background.

h.     In the Install Business Content in the Background dialog box choose Yes.

i.      In the information dialog box choose Continue.

j.      Choose Back.

3.2.3      Activating Business Content: InfoCubes

This activity has to be carried out in the BW system.

Procedure

1.     To activate the InfoCubes in the Business content, choose:

SAP BW – role menu	Activating Business Content: InfoCubes
Transaction code	RSORBCT

2.     On the Administrator Workbench: Business Content screen:

a.     At the top of the right frame, choose Grouping and select In Data Flow Before.

b.    At the top of the right frame, choose Collection mode and select Collect Automatically.

c.     In the left frame, select Object types.

d.    In the middle frame, expand the InfoCube and double-click Select Objects.

e.     In the Input help for Metadata dialog box:

i.      Select the InfoCube 0SD_C03 (Purchasing Data).

ii.     Choose Transfer selections.

iii.    If a dialog box Exceeded runtime when collecting objects appears, choose Continue.

f.     At the top of the right frame, choose Install and select Install in Background .

g.    If a new screen appears choose Transfer all without dialog.

h.     A monitor section appears. Choose Back.

Result

You have started a background job in order to activate the Business Content. Check the status of the background job using transaction SM37.

Make sure that the current job has finished successfully before you proceed on with the activation of further objects.

3.2.4      Loading Data

Carry out the following steps in SAP BW.

Use

The master data from the source system is loaded in to SAP BW. If there is no master data in the source systems, just skip to the next activity.

Procedure

1.     To load master data, choose:

SAP BW – role menu	Loading Master Data
Transaction code	RSA12

2.     Look for the InfoSources using Find In Subtree Function. You will find your corresponding Source System below each InfoSource where DataSources are assigned.

3.     Select the Source System below the InfoSource and choose Create Info Package from the context menu.

a.     In the Create InfoPackage dialog box you can see all assigned DataSources.

b.    Make the following entries:

Field	Entry
InfoPackage description	Any name

c.     Select one DataSource.

d.    Choose Save

4.     On the Scheduler (Maintain InfoPackage) screen:

a.     If you want to load master data hierarchies choose the Hierarchy Selection tab. Otherwise proceed with step b.

On the Hierarchy Selection tab make the following changes:

                                          i.    Click Available Hierarchies from OLTP.

                                         ii.    Choose the hierarchies you want to upload by clicking the radio box.

                                        iii.    Tick the checkbox of the selected hierarchies

b.    Choose the Update parameters tab and make the following entries:

Field	Entry
Initialize Delta Process	X

c.     Choose the Schedule tab and make the following entries:

Field	Entry
Start data load immediately	X

d.    Choose Start (Execute) on Schedule tab.

3.2.4.1   Relevant Characteristics

The following characteristics are used in the Infocube V_SD_C03. Check which one of them you need for your analysis. Then load master data attributes/ texts hierarchies for the InfoSources (with the same name as the characteristic ) that you need.

0COMP_CODE	Company Code
0DISTR_CHAN	Distribution Channel
0DOC_CATEG	Sales Document Category
0PLANT_ATTR	Plant (Attributes)
0PLANT_TEXT	Plant (Texts)
0SALESORG	Sales Organization
0SALES_GRP	Sales group
0SALES_OFF	Sales Office
0VERSION	Version
0DIVISION	Division
0MATERIAL_ATTR	Material (Attributes)
0MATERIAL_TEXT	Material (Texts)
0SHIP_POINT	Shipping point
0CUSTOMER_ATTR	Customer (Attributes)
0CUSTOMER_TEXT	Customer (Text)

If you want to continue with the next activity, do not leave the transaction.

3.2.5      Loading Transaction Data

Use

Transaction data from a source system is loaded into SAP BW. If there is no data in the source systems, complete this activity later and go to the next activity.

Procedure

1.     To load transaction data, choose:

SAP BW – Role menu	Loading Transaction Data
Transaction code	RSA12

2.     On the Administrator Workbench: Modeling screen, perform the following activities for InfoSource 2LIS_11_VAITM,2LIS_11VAHDR,2LIS_12_VCITM,2LIS_12_VDHDR,2LIS_13_VDITM,2LIS_13VDHDR.

a.     Select the Source system below the InfoSource.

b.    From the context menu choose Create InfoPackage.

c.     In the Create InfoPackage dialog box: Make the following entries:

	Entry
InfoPackage description	Enter a description

d.    Select the DataSource you want to upload data from.

e.     Choose Save.

3.     On the Scheduler (Maintain InfoPackage) screen:

a.     Choose the Processing tab and make the following entries:

Field	Entry
PSA and then into data targets (Package by Package)	X

b.    Choose the Data targets tab and make the following entries:

Field	Entry
Select Data Sargets- Videocon Purchasing V_SD_C03	X

c.     Choose the Update parameters tab. Here you have the following options for the update mode:

Update Mode	Description
Initialize Delta Process	A full update requests all data that corresponds to the selection criteria you determined in the Scheduler. If you load data the first time and you want to load all existing data into BW, choose update mode Full update

List the differences between BW 3.5 and BI 7.0 versions.

These are all the difference between 3.5 and 7.0 version

SAP BW 7.0 is called SAP BI and is one of the components of SAP NetWeaver 2004s. There are many differences between them in areas like extraction, EDW, reporting, analysis administration and so forth. For a detailed description, please refer to the documentation given on help.sap.com.

1. No Update rules or Transfer rules (Not mandatory in data flow)
2.Instead of update rules and Transfer rules new concept introduced called transformations.
3. New ODS introduced in additional to the Standard and transactional.
4. ODS is renamed as DataStore to meet with the global data warehousing standards.
And lot more changes in the functionalities of BEX query designer and WAD etc.
5. In Infosets now you can include Infocubes as well.
6. The Re-Modeling transaction helps you adding new key figures and characteristics and handles historical data as well without much hassle. This facility is available only for info cube.
7. The BI accelerator (for now only for infocubes) helps in reducing query run time by almost a factor of 10 - 100. This BI accl is a separate box and would cost more. Vendors for these would be HP or IBM.
8. The monitoring has been improved with a new portal based cockpit. Which means you would need to have an EP guy in your project for implementing the portal ! :)
9. Search functionality has improved!! You can search any object. Not like 3.5
10. Transformations are in and routines are passe! Yes, you can always revert to the old transactions too.


*In 3.5 the dataflow will be like this,
Source System-->Datasource-->PSA-->Transfer Rules-->Info SOurce-->update Rules---> Data Target

In 7.0 the dataflow like this,
Source System-->Datasource-->PSA-->Transformation(Data Transfer Process) --> Data Target

*In BI7.0 ,BI ACCELERATOR will be there to handle a huge volume of data handling process

*In BW 3.5 the INFOSET can be created by use of ODS and INFOOBJECT .

In BI 7.0 the INFOSET can be created by use of ODS, INFOCUBE and INFO OBJECT .

*In BW 3.5 PSA is optional, by use of this we can load data or directly we can move data to datatarget.

In BI 7.0 PSA is must , by use of this only we can move data.

*In BW 3.5 we are using Start routine, Transfer Routine, Update routine, Conversion routine, Return Table

In BI 7.0 these are the routines used, Start routine, End routine, Expert routine

SAP CRM Technical course class room training and online training

SAP CRM Technical Training : SAP CRM technical Course content

Topics:

• Overview of sap CRM.
• What are the major modules in sap CRM?
• What is Business Partners
• Basic understanding
• BP types
• Roles and relationships
• Tables
• CRM profile management.
• Transaction
• Organization management.
• Different application in sapcrm.
• CRM ORDERS & Docflow
• One Order Framework
•  
• BSP logic programming in web request
• IC Web Client.
• BOL structure
• Query Structure
• Genil model browser and Genil BOL browser
• Genil and BOL Programming
• Web User Interface (Web UI)
• Componentization with CRM 7.0 (Component Workbench)
• Creation of web pages
• Views / View sets /Windows
• Controllers - Component and custom
• Developing a Custom Component
• HTMs coding for table/form and empty view
• Runtime repository structures.
• Navigation links.
• Repository.XML
• Transaction Launcher
• EEWB and AET
• Middleware Basics

SAP CO online and class room training

Submodule	Topics
General Controliing	Concept of controllling
	Organizational structure
	Controlling Area
	Assignment of company  code to controlling area
	Versions
	No. of ranges for controlling documents
	Integration with FI with CO
Cost Element accounting	Cost element group
	Primary cost element
	Secondary cost element
	posting to cost element
	Cost element categories
	Automatic Creation of Primary and Secondary Cost Elements
	Manual Reposting of Costs
	Manual Reposting of Revenues
	Repost Line Items
cost center Accounting	Activate Cost Center Accounting in Controlling Area
	Define Standard Hierarchy
	Define Cost Center Categories
	Create Cost Centers
	Activate Inactive Cost Centers
	Delete Inactive Cost Centers
	Define Cost Center Groups
	Define Cost Elements for Activity Allocation
	Create Activity Types
	Define Activity Type Groups
	Maintain Statistical Key Figures
	Maintain Statistical Key Figure Groups
	Cost center Planning
	Activity Planning
	Primary cost  allocation
	secondary cost allocation
Internal order	concept of Internal order
	Type of Internal order
	Order type
	creation of orders
	Important field in order master data
	settlement profile
	allocation structure
	Distribution Rule
	Planning of Internal order
	Actual cost posting to Internal order
	Transfer of cost from IO or to IO
	Settlement  Rule
	Settlement of Internal order
	Internal order Report
Profit center Accounting	Defination of Profit center
	Controlling Area Settings
	Define Profit Center Standard Hierarchy in Controlling Area
	Profit center group
	Dummy profit center
	Creation of Profit center
	Posting to profit center
	Derivation of profit center
	Reports for Profit centers
	Activate Inactive Profit Centers
	Delete Inactive Profit Centers
	Assign Default Profit Center to Accounts
Product costing	Product Cost Planning
	Basic Settings for Material Costing
	Maintain Overhead Cost Elements
	Define Costing Sheets
	Define Overhead Keys
	Define Overhead Groups
	Define Cost Component Structure
	Material Cost Estimate with Quantity Structure
	Define Costing Variants
	Material Cost Estimate Without Quantity Structure
	Cost Object Controlling
	Bills of Material
	Costing Run
	OH Calculation
	Maintain OH Rates
Profitability segment	Concept of Operating concern
	Concept of Proftitablity segment
	Concept of characterstics
	Concept of value fields
	Define characterstics & Value fields
	Maintain Assignment of SD Conditions to CO-PA Value Fields
	Transfer of Billing Documents
	Define PA Transfer Structure for Settlement
	Assign PA Transfer Structure to Settlement Profile
	Posting of COPA document
	COPA Report
Other concepts	Integration with PS module
	Integration with PP Module