Loading

How to create a Blinking Indicator in Xcelsius

Posted by SAP BI-BO on Sunday, September 4, 2011

1 Comment

ABAP : Implicitly Enhancement Point

Posted by madhu on Friday, July 15, 2011

Restricting To Update Vendor Number In MIGO for cross company purchase order

Requirement

We had a requirement that ………..
When doing the initial Goods Receipt of a purchased or subcontracted good, the vendor field on the batch master (MCH1-LIFNR) should be populated with the relevant vendor number.
If this batch at a later stage is once more part of a Goods Receipt – by a cross company purchase order, the vendor field should NOT be updated. The initial vendor number should be kept.
Suppose A: Vendor for company ABC and B and C are plant for ABC.
Suppose Plant B of ABC has order one material from A , in that case in MCH1 table , A will be updated as Vendor .

Read More >>

No Comments

SAP BI Share Knowledge For All Range of Topics

Posted by SAP BI-BO

If you want to share your SAP knowledge or get help from SAP experts worldwide on any type of topics then visit on the following forum.

SAP Forum for all Range of Topics
Your comments are valuable inputs for us-

No Comments

Beginners Guide to Xcelsius: Part 2

Posted by SAP BI-BO

No Comments

Xcelsius and Web Intelligence using XWIS

Posted by SAP BI-BO

No Comments

Interview Questions and Answers for SAP BI

Posted by madhu on Thursday, June 2, 2011

1. How to use Virtual K.F/Char. ?
   Ans : This “virtual” characteristic is getting a value assigned at query runtime and must not be loaded with data in data target. Therefore, no change to existing update rules.
   The implementation can be divided into the following areas:
   1. Create of InfoObject [Key Figure / Characteristics] and attach the InfoObject to the InfoProvider.
 2. Implementation of BADI RSR_OLAP_BADI (Set filter on Infoprovider while defining BADI implementation)
   3. Adding the InfoObject into the Query.
2. Query Performance Tips :
   Ans :
   i. Don’t show too much data in initial view of report output
   ii. Limit the level of hierarchies on initial view
   iii. Always use Mandatory variables
   iv. Utilize filters based on InfoProviders 
   v. Suppress Result rows if not needed
   vi. Eliminate or Reduce Not logic in query selection
3. DataStore Objects :
Ans      : Standard DSO – Max. 16 key fields can be created.

Read More >>

No Comments

To populate filds dynamically in query

Posted by madhu

Requirement
Our requirement was , we were having one Ztable in Ecc and from Ecc we were fetching all the data upto standard dso in BI , and from some other source we are having data up to cube .In our flow we were having 4 ds including the above Ztable.
All flow were independent.Like DS-WOP DSO-Std.DSO-CUBE , on top of all 3 cube we were having one Multiprovider, and we were having our query , but even though Ztable flow was there in that flow but we dnt add the dso of Ztable flow in our Multiprovider.all the above flow were having profit center and Company code as key field , based on company code user was expecting all the Key figures from the Ztable but their intention was those KF IOs sd not be there in query .In that table around 20 KFS were there (User was not bother about the performance, also ).Company code was Mandatory and Single value in our selection, also currency was constant that is USD.
To achive this what I did , I have created one data source for that Ztable and loaded data upto standard DSO.
den Have created 20 formula variable processing type user exit .
and was achived the requirement .the sample code for one formula variable as follow .

Read More >>

No Comments

Program to Download all the IOS and Ruletypes for a particular transformation ID

Posted by madhu

Requirement:
We have developed this program to down load all the info objects fields and rule types into Excel sheet to compare the objects between two server, our aim was everything sd be sync between both the server.
This program will be helpful in many area.
The program follows below.

*&---------------------------------------------------------------------*
*& Report ZY_DATA_DOWNLOAD_TRANS
*& Author:Madhusmita Jena
*& Date:17/05/2011
REPORT ZY_DATA_DOWNLOAD_TRANS.
*tables:RSTRANFIELD,
* RSTRANRULE.

Read More >>

No Comments

How to check whether the query is already migrated to BI

Posted by madhu

To check whether the query is already migrated to BI .By the field VERSION in table RSZCOMPDIR table we can identify .
go to the table RSZCOMPDIR , there go to field COMPID , give your query name and execute .
if in version field if value is <100
the query is a 3.X query. If it is more than 100 query has been migrated to 7.X version.

No Comments

Delta Update Methods in Logistic

Posted by SAP BI-BO on Tuesday, May 10, 2011

We have three delta update methods in Logistic.


Direct Delta: With this update mode, the extraction data is transferred with each document posting directly into the BW delta queue. In doing so, each document posting with delta extraction is posted for exactly one LUW in the respective BW delta queues.


Queued Delta: With this update mode, the extraction data is collected for the affected application instead of being collected in an extraction queue, and can be transferred as usual with the V3 update by means of an updating collective run into the BW delta queue. In doing so, up to 10000 delta extractions of documents for an LUW are compressed for each DataSource into the BW delta queue, depending on the application.


Un-serialized V3 Update: With this update mode, the extraction data for the application considered is written as before into the update tables with the help of a V3 update module. They are kept there as long as the data is selected through an updating collective run and are processed. However, in contrast to the current default settings (serialized V3 update), the data in the updating collective run are thereby read without regard to sequence from the update tables and are transferred to the BW delta queue.

No Comments