SAP BW Activate and fill aggregates

In order to speed the activation for aggregates, follow the procedure:


1. Make a search of the cube
2. Righ click and chose “Manage”
3. Go to “Performance” tab and click in “Refresh Statistics” button

Monitor this backaground job in SM37 and once this job finish, you can start with the aggregates activation.


Go to “Roll up” tab and click in “Aggregates” button


Select all the Aggregates on the right side as showed below

Click in the match icon “Activate and fill”


The next window will appear

Click in the green arrow to “Fill aggregate”

Chose option  “Now” to start immediately
Then a job is scheduled

Close the window.

SAP BW Sales Analysis Cockpit

This scenario describes the necessary activities in order to be able to analyze sales data from SAP R/3 in the SAP Business Warehouse in an integrated web cockpit, Sales Analysis Cockpit.

InfoCubes

• Customer (Technical Name: 0SD _C01 )
• Sales: Overview (Technical Name: 0SD_C03 )
• Delivery service (Technical Name: 0SD_C04)
• Offers/Orders (Technical Name: 0SD_C05 )
• Activities, Opportunities, Sales Orders (Technical Name: 0CSALMC01)
• FIAR: Transaction Data (Technical Name: 0FIAR_C02)

Key Points

• Plan/actual sales comparison
• Quotation pipeline
• Analysis of all accounts payable data (transaction figures)
• Sales revenue by sales representative in both chart and table format, overview and detail overview
• Alerts on sales decrease and delivery delay
• Large variety of reports in sales revenue, delivery service, profitability analysis, and quota arrangement.

SAP BW Scenario Financial Accounting Analysis

InfoCubes

·         Accounts Receivable: Line Items, Payment History, Transaction Data

·         Accounts Payable: Line Items, Transaction Data

·         General Ledger: Transaction Figures, Financial Statements

·         Asset Accounting: Annual Values, Period Values

·          Accounts Receivable: Line Items, Payment History, Transaction Data

Key Points

·         Analysis of all accounts receivable data (transaction figures, line items, payment history)

·         Analysis of all accounts payable data (transaction figures, line items)

·         Analysis of all the transaction data from the general ledger, financial statement items in detail

·         Analysis of the annual and period values from asset accounting

SAP BW Cross-Functional Analysis: Financial and Sales Data

The scenario Cross-Functional Analysis: Financial and Sales Data describes all the necessary activities to built up a report that analyzes data from financial accounting and sales and distribution. With the detailed description easy enhancement of the report according to individual customer requirements is possible, for example: include more or other characteristics, other key figures, break down in other intervals, and so on.

Key Points

·         Analyzing financials key figures

·         Drilling down key figures from sales to the level of the following characteristics: Sales Organization, Distribution Channel, Division, Sold-to Party, Bill-to Party, Billing Document Number, Sales Group, Sales Employee, Sales District., Sales Office

·         Analyzing the structure of receivables

·         Revenue for the current year broken down by due date for net payment in intervals: already paid items, total balance of open items, already overdue items, intervals 16 - 30 days, 31 - 45 days, 46 - 60 days, 61 - 90 days, 91 -120 days, > 120 days

Scenario Booking Billing Backlog Analysis

Key Points

·         Combination of various information from different sales documents for a complete overview on open sales orders and deliveries

·         Analyzing values and quantities backlog in sales orders and deliveries with goods issues posted

·         Drill down of analysis to the level of single sales order items, materials, customers, shipping points as well as sales organisation, distribution channel and division

SAP BW Analyze Controlling data from SAP R/3

InfoCubes

·         CO-OM-CCA: Costs and Allocations - technical name: 0CCA_C11

·         CO-OM-CCA: Costs and Allocations (by Activity Type)- technical name: 0CCA_C02

·         CO-OM-CCA: Activity Type Quantities and Prices- technical name: 0CCA_C04

·         CO-OM-CCA: Statistical Key Figures - technical name: 0CCA_C03

·         CO-PC-OBJ: Cost Object Controlling - technical name: 0PC_C01

·         CO-PC: Product Cost Planning - All Cost Estimates - technical name: 0COPC_C08

·         CO-PC: Product Cost Planning - Released Cost Estimates - technical name: 0COPC_C09

·         Transaction Data (Profit Centers) - technical name: 0PCA_C01

·         Statistical Key Figures (Profit Center) - technical name: 0PCA_C02

Key Points

·         Analysis of full costs on cost centers (plan, target, actual, etc.)

·         Analysis of information on the origin of the costs (allocation partner such as material number, cost center, and so on)

·         Analysis of costs broken down into cost components or costs by activity type (fixed and variable costs)

·         Analysis of activity quantities (plan, actual, target, scheduled activity, capacity)

·         Analysis of activity prices (plan and actual)

·         Analysis of statistical key figures on cost centers (plan, actual)

·         Analysis of transaction that was uploaded from the source system/s data for all product cost collectors and orders.

·         Analysis of the values of the cost components of the cost component split for all existing material cost estimates, broken down into fixed/variable costs, level/lower-level costs, and costing date

·         Analysis of the cost components of the cost component split for released material cost estimates in the view relevant to valuation, by fixed and variable costs, level/lower-level costs, and period. Hence it contains only the cost estimates that explain the standard prices of the materials in the particular period analysis of activity quantities (plan, actual, target, scheduled activity, capacity)" Analysis of the cost components of the cost component split for released material cost estimates in the view relevant to valuation, by fixed and variable costs, level/lower-level costs, and period. Hence it contains only the cost estimates that explain the standard prices of the materials in the particular period analysis of activity quantities (plan, actual, target, scheduled activity, capacity)

·         Analysis of the period totals for profit and loss accounts and balance sheet accounts from Profit Center Accounting (PCA), which were loaded from the affiliated source system(s)

·         Analysis of all statistical key figures from Profit Center Accounting (PCA), which are loaded from the affiliated source system(s) 

SAP BW How to push data from PSA to ODS

1. Go to PSA
2. Make a search of the IP that you  need, for example: 2LIS_12_VCSCL_DELTA
3. Right click and chose “Schedule the update”

Make sure the data target is selected in the “Data targets” tab

Go to “Schedule” tab and click in “Start” botton to start the load

Click in the green arrow to continue 

Click in the back green arrow and continue with the next request, following the same procedure.


Once you finish, don’t forget to activate data in ODS:
1. Make a search of the ODS
2. Righ click and chose “Activate data in ODS”

A screen like next is going to appear

Click the “Start” botton and close the window
A Background job is going to be schedule for this.

SAP BW How to activate aggregates for COPA 1. Once COPA ran 2. Open the system 3. Make a search of the cube YGTFCPA01 4. Righ click and “Manage” 5. Go to “Environment” option from the menu and chose “Automatic request processing” 6.The following window will appear Check the option “Roll up data in the aggregate” and save it Click in the little paper Click in save botton to continue Run statistics Go to performance tab and click in “Regresh Statistics” button A job is going to be created Continue Monitor the job created in SM37 Once this job finish Go to “Roll up” tab and click in “Aggregates” button. Select all the aggregates Click in the match button “Activate and Fill”

How to activate aggregates for COPA


1. Once COPA ran
2. Open the system
3. Make a search of the cube YZNNNZ
4. Righ click and “Manage”
5. Go to “Environment” option from the menu and chose “Automatic request processing”
6.The following window will appear

Check the option “Roll up data in the aggregate” and save it


Click in the little paper

Click in save botton to continue

Run statistics
Go to performance tab and click in “Regresh Statistics” button


A job is going to be created

Continue
Monitor the job created in SM37


Once this job finish
Go to “Roll up” tab and click in “Aggregates” button.


Select all the aggregates

Click in the match button “Activate and Fill”

Click green arrow to continue

Click “Now”
A batch job was now schedule
Monitor the job 

SAP BW How to change the owner of a job

To change the owner of a job:


Select a modifiable job to change:

From the top pulldown menu select JOB -> CHANGE
Select the step with the user ID that needs to be changed

From the menu,  select STEP -> CHANGE

You can now edit the user and change to BW_ADMIN
Check and Save
Exit and save the job.

SAP BW Activate and fill aggregates

In order to speed the activation for aggregates, follow the next procedure:


1. Make a search of the cube
2. Righ click and chose “Manage”
3. Go to “Performance” tab and click in “Refresh Statistics” button


Monitor this backaground job in SM37 and once this job finish, you can start with the aggregates activation.


Go to “Roll up” tab and click in “Aggregates” button


Select all the Aggregates on the right side as showed below


Click in the match icon “Activate and fill”

Click in the green arrow to “Fill aggregate”

Chose option  “Now” to start immediately
Then a job is scheduled

Close the window.

SAP BW Activation of M records from ODS object terminated

Info Package: XYZ 


Failure Message: Activation of M records from ODS object YGHJJ terminated


Resolution: Delete bad request from data target and reran request


Steps for resolving issues:


• Go to Monitor screen to check the failed record and click on it to see the Header:


Double click on data target in the above screen to go to the data target:


• Double click takes you to the “Manage Data Target” screen, click on Request tab and look for the records in red and delete them:


Reran Request:


• Go to the following screen and double click on Data Target:


• Following screen comes up and click on Start:

SAP BW Change run failed with error - No change run is possible

Change run failed with error:


Report RSDDS_AGGREGATES_MAINTAIN completed with errors or As master data is loaded for 0MAT_ST_LOC, no change run is possible


All Master Data should be release by the time that chain run starts, in this case the Master Data was locked and that’s why the chain run failed.


1. Make a search of Master Data 0MAT_ST_LOC and delete the lock.


2. Go to Hierarchy /Attribute Changes for reporting window and click on the  “Stop” button.  


3. Click on “SubseqProcessing” button and copy the parameters in notepad before to deleting them.   
4. Don’t click on trash button, just delete them manually and click the green arrow button to continue.


We are removing these events because we don’t want to start again “Transaction Data” which is the subsequent event.


5. Click on “Selection” button and copy the parameter in the Event field  to note pad then click in the “Immeditate” button and unchecked the option “Periodic job” and save it. 

6. Click on “Execute” button.
7. Monitor the job in SM37.


Once Hierarchy /Attribute Changes for reporting ran successfully you have to put the parameters back. 


Click “Selection” button  and chose “After Event” button and type in Event field the following: YCHGRUN_GT_CHG_RUN_CHAIN.
Make sure the “Periodic job” check box is checked  and Save it.


Click “Execute” button to schedule the “Periodic Job” and you will see a new scheduled job.

SAP BW Process chain not starting

Go to SU01 and change these parameters for your background user (ALEREMOTE or something similar...)

You can find this option in SU01 on the Logon data tab > User Type.

Just go to RSA1 -> Environment -> global settings and change the user id to the current loggin ID. Remember u should have authorization to schedule the background job.

Replacement path: - processing type is used in a variable when you wish to get a value from attributes of another character or from a query. 

Example: - if you wish to display the age of a customer in your report which will not be in the cube. I mean Age is attribute of customer and not part of the cube. But each transaction record in the cube is assigned with a customer field. So...If we want to get this value into our report... We create a variable on customer with replacement path and use its attribute AGE. So when you use this variable in your query for any thing you get the age of the customer associated with that transaction data.

SAP BW Roll up Copa Aggregates

Problem
The issue previously was that roll up jobs were getting cancelled due to lock by attribute change run.

Investigation/Resolution

• Checking for Running or Terminated Change Run

1. Check running WP's in SM51/SM66

Thus when a change run starts a BTC WP starts several dialog WP's. When an attribute job is cancelled only the BTC job is cancelled the dialog WP's continue until complete or time out (7200 secs)

Within SM66 we identified a WP that was locking XYZ, we attempted to cancel this however it had almost reached time limit so cancelled automatically.


2. Function Module: RSDDS_AGGR_MOD_STATE_GET was run to ensure there were no activate attribute change runs.

a. The function module RSDDS_AGGR_MOD_STATE_GET displays the status of change run.
E_MOD_IN_PROGRESS should have no value,
E_CNSID should be 0.
If not you have to delete the flag to start another change run)

b. The function module RSDDS_AGGR_MOD_CLOSE deletes the flag for an "active" change run etc

To ensure that this was successive the change run monitor should be checked for the below message (as per update by Slava in IM2615265 ):

Please make sure that you have "No Change Run active" message when run RSDDS_CHANGERUN_MONITOR report.

• Roll Up Aggregates

After the above steps, the requests for XYZ& XYZ100 were successfully rolled up without any issue.

SAP BW Change run failed with error “Rollup for InfoCube XYZ terminated”

Change run failed with error “Rollup for InfoCube  XYZ terminated”:

IF the rollups are running, no change run is possible.

Deactivate the aggregates for XYZ

Click on manage

Go to Roll up tab and click on “Aggregates” button

Select all the aggregates 

Click on Deactivate button

      

Fix Change Run

1. Go to Hierarchy /Attribute Changes for reporting window and click on the  “Stop”

2. Click on “SubseqProcessing” button and copy the parameters in notepad before to deleting them.   

3. Don’t click on trash button, just delete them manually and click the green arrow button to continue.

4. We are removing these events because we don’t want to start again “Transaction Data” which is the subsequent event.

 5. Click on “Selection” button and copy the parameter in the Event field  to note pad then click in the “Immeditate” button and unchecked the option “Periodic job” and save it. 

6.  Selection

7. Click on “Execute” button.

8. Monitor the job in SM37.

9. Once Hierarchy /Attribute Changes for reporting ran successfully you have to put the parameters back. 

10. Click “Selection” button  and chose “After Event” button and type in Event field the following: 

11. Make sure the “Periodic job” check box is checked  and Save it.

12. Click “Execute” button to schedule the “Periodic Job” and you will see a new scheduled job.

Run the Statistics refresh

Run the aggregates for the same cube

SAP BW 8YGTDS_C30 Archive Process overdue

Error: Archive process overdue


Solution:

In the monitor, details tab, right mouse click on the red data packet and manual update

Some times, the system will let you update manual when right click on the data packet which is red. Some times, the message popup and said can not update request, it is in a data target. Then follow as below.

Double click on the data target. Eg. YGTDS_C32.

In the Manage Data Target, select the request and click delete button.

When the request is deleted,  arrow back to the monitor.

In the Details tab, right click the packet and click manual update.  Usually all data packet will be process in the background and turn green.

SAP BW Maintanance problems

S.No	Error	Explanation	Solution
1	ODS Activation problem	Though the ODS is active and data is available in the active table. Sometimes the data loaded data into ODS is not available for reporting	Right click on ODS and choose Activate the ODS data.
2	Bad records in PSA	When Illegal characters are loaded	Correct the illegal characters
3	ODS to cube load failure	Though during the built of ODS if we set under settings ‘update data targets automatically’, sometimes the data is not available to the target cube.	Right click on ODS Object and choose ‘Update data into data target’
4	Loading data using process chains	When load is in progress using process chains to a particular data source. If a user tries to create a record to that data source then the load gets stooped.
5	Error message when processing in business information warehouse	The result of this step is short dump.	Load the data from PSA.
6	Definition	After crating the ODS, when we try to activate the ODS it will not get activated because of problem in RFC	Rectify the problem in RFC destination
7	RFC connection check failed	When transferring the data from one level of ODS to next level of ODS, the data will not be transferred to second level ODS	In monitor under details check in subsequent processing and check for RFC connection problem and rectify the problem.

SAP BW tRFC log error message for the function RSAR_TRFC_DATA_RECEIVED

The log file provides the details required:

Caller                           RFC-BIW

Function module         RSAR_TRFC_DATA_RECEIVED

Target system             EB8PRBW102

Date                            08.03.2006

Time                            15:07:36

Status text                   Programs not generated for InfoSource 0COORD_TYPE_

                                                                                                                               

Double click on the Status text field to get the full message

Tasks to perform

Check the InfoSource on the target system

Transaction RSA1 --> Modelling --> InfoSources

Use the search function to locate the required InfoSource.

In this case the InfoSource is inactive and so needs to be activated. Inform the BW Administrator, who in turn should inform the BW developer.

SAP BW Scheduling an InfoPackage

Transaction RSA1 --> InfoSources

·        Select the InfoSource that you want to load data to
·        Expand on the InfoSource to obtain the Source System
·        Expand on the Source System to view the available InfoPackages
·        Select the InfoPackage to schedule
·        Right mouse-click on the InfoPackage
·        Select Schedule

On the Scheduler (Maintain InfoPackage) screen you can change the settings for the InfoPackage ( e g restrict the range of data) if you wish.

·        Select the tabstrip 'Schedule'

·        Select 'Start data load immediately'

·        Press pushbutton  'Start'

A job will now be launched to perform the data loading.

On the BW system you can see the data loading job in the Job overview screen.

And on the Source system you can also see the data loading job

You can get more information about the success or otherwise of the InfoPackage, by using the BW monitor.

RSA1 --> Monitoring --> Monitor

Note that the Request corresponds to the job name (prefixed by BI) on the source system.

SAP BW Background Jobs

In the Job log (SM37) you often see background jobs which have name that begin with 'BI'. The job name is typically generated, and has a format of BI followed by 25 or more characters.

BI_REQD

Example          BI_REQD3LC9UIZZBQU2G6SI6YE6PSHHB

Run by            The background RFC user

Purpose           Part of a data extract from the source system

                        On the source system you would see a job with a name of the format                     BIREQU... to accompany this data extraction job.

BIREQU

Example          BIREQU_3LC9OEL78TWUZEPQR97U7FBSV

Run by            An end user

Purpose           You can see this in the table RSREQICODS

                        This table is a monitor for the saving of the updated IC and ODS per                      request

                        The request number in this table is always REQU.

                        This job is a data load job from the ODS to a cube.

BI_BOOK

Example          BI_BOOK3LIC88JNNG7SEXZP36ZJTIFJM

Run by            The background RFC user

Purpose           Part of a data extract from the source system

BI_DELR

Example           

Run by            An end user

Purpose           This job deletes data from the ODS.

BI_ODSA

Example         

Run by            The background RFC user

Purpose

BI_NEW_

Example         

Run by            An end user

Purpose           This job is used to reconstruct a data target.

BI_COMP

Example         

Run by         An end user

This job is used to compress an InfoCube

BI_AGGR

Example         

Run by        An end user

Purpose      This job is used to roll-up an InfoCube

BI_STRU

Example         

Run by                       

Purpose      These are change runs