BW Statistics Key Figures

Hi everybody,
We installed BW statistics and now we want to work with the queries. But we do not understand all key figures. We looked for them in the BI Content but they are not listed there.
For examble the two key figures:
Short-Term / Total Time 0TCT_MC01_RK321
Long-Term / Total Time 0TCT_MC01_RK322
used in the query "Deviations in Runtimes of BI Applications" (0TCT_MC01_Q0112)
I hope you can help us.
Thankfully

Hi dear,
since these objects are restricted KF, you have to look in your query how is the basis KF and then you will be able to find some useful info on the help !
Let us know...
Bye,
Roberto

Similar Messages

Key figure values in MC$K not updated

Hi
I have a situation where I run transaction MC$K (Material Analysis: On-time delivery: statistics):
At first I had not done any config in transaction MCFC for the deviation of delivery date. So when I ran MC$K, the delivery date variance key figures showed zero (0).
Then I updated the variance intervals in transaction MCFC and reran the report. Still did not show anything for the old purchase orders, but for any new created PO/GR that that I did after my settings in transaction MCFC are taken into account.
But what if I want to see anything that was created before I did my MCFC config? For the old purchase orders that is...is there any update program I need to run for the info structure?
I am a bit new to this so please bare with me...

Hi,
Problem has been resolved by passing the 40 char length material, and location in the char combo table of BAPI.
Ex: CHARACTERISTIC_VALUE = 00000000000000000000000000000000000100600 (Should be 40 char).
CHAR_COMB_ID = 1 -
you can give any number.
Now i am facing another problem with this BAPI.......
In our planning book time periods like first two weeks in day buckets, after thet all in week buckets.
Case1: day buckts - noprob
case2: weekly buckets : suppose a week start from 17/01/2010 end with 23/01/2010. In this case i am not able to create a order on 22/01/2010.
BAPI allowing the time period start date as 17/01/2011 and end date as 23/01/2011 and its creating the oder on 20/01/2010(middle day of the week).
Can anybody suggest on this..
Thanks

Events Sales Information System - Key figures

What key figure is updated in Net incoming orders 1 and Net incoming orders 2 as defined under update group 000001. I can understand Net incoming order and Gross incoming order.........

Hi Sanjay,
In order to separate both of the key figure groups the updating process is controlled via various update groups. Update group 000001 is assigned to the key figure group for incoming order information and update group 000002 to the group of returns key figures.
Assigning the business transactions to a certain update of statistics data takes place in two steps.
In the first step, you compile certain characteristics of the business transactions such as customer, material, document type into statistics groups. In the second step, you assign the statistics groups to the various update groups.
In the special case incoming order/returns, all of the returns order types are assigned to statistics group 02 and all other order types to statistics group 01. These different statistics groups are assigned to different update groups and thus key figure groups.
You can assign an update group to certain business transactions using the Customizing function in Sales
The two types of key figure groups used in the Sales Information System are invoice values and credit memo values. These key figure groups are differentiated by the different update groups (000001/000002).
Assigning certain types of invoices to the update group 000001 and types of credit memos to update group 000002 is done automatically by the types of orders belonging to them.
Just go through the following very useful link below:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/c1/3756d5449a11d188fe0000e8322f96/frameset.htm
Hope it helps...

SIS some key figures are displaying zero value

Dear all
Following Key Figures in Standard SIS tcode like MCTE, MCTA, etc. are displaying as zero
Incoming Return
Credit Memo
Credit memos qty
Returns items
Returns Quantity
MC+6 is displaying all the key Figures as zero.
What may be the reasons
Regards
Vipin

Dear Babubala
In MC26 I am getting below warning for Incom. Returns, Gross returns, Net Returns 1, Net Returns 2, Returns items, Returns Qty
Incom. returns: Updating with date field VDATU can be set up restrictively only
Message no. M!208
Diagnosis
While updating the key figure Incom. returns the data field MCVBAP-VDATU for the period determination is used.
Updating via MCVBAP-VDATU causes a different result online as for statistic data set up. Online, MCVBAP-VDATU is filled with the current date (SY-DATLO); during set up, however, it is filled with the creation date MCVBAP-ERDAT of the item.
By using VDATU document changes you can see in the statistics that this type of 'delta updating' cannot be reproduced by a statistic data set-up. During the set-up the data is updated in different periods as in online updating, thereby causing the change history to be lost.
Procedure
Be certain that this is the type of updating you want.
In MC26 the Credit Memo Update Setting is VD Billing document and Type of Updating is A Cumulative updating
while as in Credit memo pricing procedure there is no subtotal. How to maintain it in Pricing procedure and in MC26 because in MC26 after pressing the change button the system is displaying the following message "Maintenance of SAP standard updates not allowed"
Regards
Vipin

SAP Note 0407563: Key Figure Model versus Account Model in BW

I am reviewing a document on Key Figure Model versus Account Model in BW.
There are a number of references to "SAP Note 0407563", can anyone with access to this note post it here for me to review. Sometimes some otf there links prompt for password.
Thanks in advance.

Hi,
<b>SAP Note 0407563</b>
Symptom
You would like to design a data model for SEM-BPS and you are not sure, whether to use the key figure or the account model.
You are looking for proposals for data modelling.
Additional key words
bps0, key figure, characteristic, model, data modelling, consultation
Cause and prerequisites
In the following you find a simple example by means of which the terms key figure and account model are defined.
In the example we want to assign several key figures (for example revenues) to a characteristic (for example customer), whose units (for example currency DM) are identical.A modeling option, which is called key figure model, contains all key figures in one data record.
Customer Revenue_1 Revenue_2 Revenue_3
A 10 DM 30 DM 50 DM
In the account model, on the other hand, an additional characteristic is added, which separates the revenue types.
Customer Type Revenue
A 1 10 DM
A 2 30 DM
A 3 50 DM
Advantages and disadvantages from the point of view of data modelling
You can easily add an additional revenue type in the account model, because you do not have to change the data structure.In the key figure model, on the other hand, you must add an additional key figure to the structure.It actually depends on the frequency of these changes occurring.
A data record that is to be changed by a processor, is exclusively locked by SEM-BPS for this processor.A lock that only concerns individual key figures of a data record is not possible.As a consequence the different revenue types can be changed simultaneously by different processors in the account model, wheras in the key figure model one processor automatically locks all key figures exclusively for his own use.
If you use a planning function in the account or key figure model, a different Customizing is required in general. Consequently, a conversion of the data model leads to a change of Customizing in general.
Advantages and disadvantages from the technical point of view
The transaction data is stored in the BW.Analyses have shown that the read time basically depends on the number and not on the size of the data records.In the above example you can see that by changing the key figure and account model the number of records increases by factor 3, which means that you must expect longer read times.When determining the factor you must take into account that normally not all key figures are used in every record in the key figure model.As a consequence only those records are created when changing to the account model, for which the key figures are not equal to zero.
Example:
So if in the above example the key figure Revenue_1 is not used, only two records are generated and consequently the value of the factor is also reduced to 2.
After the transaction data has been read from the BW, it is stored in the application server's memory.The amount of memory required depends, among other things, on the number and on the length of the records.The length can be influenced by the data model you choose:in the key figure model the records are longer than in the account model and therefore consume more memory for each record. Therefore, the key figure or account model will require less memory depending on the relationship between record length and number of records.
When the data model is changed, also the planning functions must be revised.Depending on the type of calculation there might be advantages for one of the models.
Example and rules of thumb
The following example contains 30 key figures, which were mapped to 3 key figures and one additional characteristic with a maximum of 10 characteristic values when you changed to the account model.In both models a price calculation between three key figures each was executed.Consider the specifications in the table as relative specifications:For the number of data records you for example find a and a*10.This means that in the second case the number of data records is larger by factor 10 than in the first case.The determination of the relationships is based on 5000 data records in the key figure model.
Example: all key figures are used (100%)
measured size      :     Key figure model, Account model
Number data records:      a      ,     a*10
Read time       :     l      ,     l*10
Price calculation:      t      ,     t*9
Data record length:      d*4      ,     d
Memory requirement :     m      ,     m*3
Example: Key figures are partially used (20%)
measured size      :     Key figure model ,Account model
Number data records :          a      ,     a*2
Read time           :     l      ,     l*2
Price calculation      :     t      ,     t*2
Data record length      :     d*4      ,     d
Memory requirement      :     m      ,     m*0,8
How are the sizes determined?
Read the related notes for details on the use of the statistics.
1. a: In the statistics of SEM-BPS or BW this value is stored when you execute a planning function. The method has the name 0-DB1.
2. l: The above statistical record also contains the execution time.
3. t: In the statistics of SEM-BPS a record is stored for the planning function.The overall runtime of the planning function contains the database time. Therefore the database time must be subtracted from the runtime of the planning function to determine t.
4. d: The data record length corresponds to the data structure length (ABAP length), which is generated for every area.The name is made up as follows:
Prefix: /1SEM/_YS_DATA_
Client: mmm
Name of the area: gggggggg
The client must always be specified with three digits, the area only in its actual length.The name for an area called 'MYAREA' which is in client 001 is for example /1SEM/_YS_DATA_001MYAREA.When you determine the length, note that there is the dictionary and the ABAP length (Transaction SE11 => Extras => Structure width => ABAP length) and that the total of the two structures contained must be determined.In the structure stated above, for example /1SEM/_YS_CHAS_001MYAREA and /1SEM/_YS_KYFS_001MYAREA are contained.The total is the length you are looking for.
5. m: After executing the planning function, start Transaction STAD and find the appropriate statistical record for the dialog step, in which you have executed the planning function.The record contains a memory specification, which is the desired value for s.
Solution
Bear in mind that the values from the example are not generally valid, but were determined from a specific example.We recommend that you determine the parameters (both the values of the variables and of the relationships) for your specific case and to use it as the basis for discussion.You should not choose too few data records, because the fixed memory consumers predominate otherwise.
Regards-
Siddhu
Message was edited by: sidhartha

About value type and key figure type

Hello Gurus,
please explan the different usage of about value type and key figure type. what is the typical values for both infoobjects ?
Many thanks,
Frank

Hi,
0METYPE is a key figure-specific info object usually used to define semantics of the individual business key figures in BW (for example, actual, commitment, plan, target values).
Its a bi specific field which is filled from extract structure field named MEASTYPE table COSR
Refer to OSS Note 523742 for how it is filled and the following link for additiona information.
http://help.sap.com/saphelp_nw70/helpdata/en/91/ddd52b9ef30645a338e28aae443807/frameset.htm
Note 523742 - BCT-CO: BW key figure model and R/3 tables for trans. data
This note provides information on the key figure model in the area of BW Content CO-OM. It also gives an overview of the DataSources for transaction data and the corresponding source tables and value fields in the R/3 System.
The key figure model for currency fields in the area of CO-OM contents affects the following info object of type key figure:
0AMOUNT Amount
The key figure itself does have any business semantics.
The semantics of the individual business key figures in BW (for example, actual, commitment, plan, target values) is determined using combinations of values for the following key figure-specific info objects (see also the account model in SEM-BPS, note 407563):
0METYPE Key figure type
0VTYPE Value type for reporting
--> 0VTDETL Details of the value type
--> 0VTSTAT Statistics indicator for the value type.
For example, using transaction SE16, the possible characteristics of the values of this InfoObject can be taken from the above-mentioned master data tables in R/3.
The business key figures on the InfoCubes of the standard BW content were defined as restricted key figures using this semantics of the key-figure-specific characteristics.
The conversion of the R/3 transaction data in the BW key figure model is carried out in the extractors using the ROMI_GET_VTYPE_AND_DETAIL function module. It primarily happens using the specified conversion tables.
The following dependencies exist for the source tables of the DataSources:
COSP_VTYPE for COSS, COSP, COVP,
COSB_VTYPE for COSB,
BPXX_VTYPE for BPGE, BPJA, BPEE
If an R/3 source record cannot be converted using these tables, it may not be extracted to BW.The application log of the R/3 DataSource transaction RSA3 contains entries for the unconverted values after the test run.(The log function for the CO-OM DataSources was considerably improved by the correction for note 523655).
The application log for the extraction runs from BW can be evaluated using transaction SLG1 (Object: RSAP, object information: RSAP_INFO)
Furthermore, the semantics of a key figure are still determined by the time characteristics and the following key-figure-specific info objects:
0CURTYPE Currency type (for more information, see note 517909),
0DB_CR_IND Debit/credit indicator (for more information, see note 065075),
0VERSION CO version
-Vikram

Key Figure Summation in DSO

Hi,
I am loading data from Cube to DSO.
In cube i have fields with 2 records below as example
f1=1 f2=2 f3=3 f4=4 and key figure k1=1
f1=1 f2=2 f3=3 f4=4 and key figure k1=1
In DSO all these f1's fields are key fields as per requirement. And when i load now i get in DSO as
f1=1 f2=2 f3=3 f4=4 and key figure k1=2
I do not want k1=2 but i want k1=1 in DSO and not sure why this is getting summed up even though i have selected overwrite in Transfer rules.
I have checked mapping and cube data. All are fine.
I just want to avoid this and do not know what to do.
A routine or formula or something else?
Please help.

Hi,
Check your DSO Design
Keep f1 ,f2, f3, f4, are in KeyFileds of DSO and Keep key figure k1 in DataFields of DSO.
Here I'm assuming that F1 to F4 are Charecteristics.And only K1 is Keyfigure. If this is the case then I hope it will work if you follw the above design.
Thanks
Reddy

Open sales orders key figure in APO

HI Gurus,
Can anyone please throw some light as to where i need to be looking in this scenario. Our BW resource extracts open sales order quantity from ECC and loads into APO DP. The issue that i'm seeing is the open sales order quantity key figure is not getting updated properly in APO. For example to begin with we have a quantity of 800 EA in the period of 12/2014 (we go by fiscal period and in this case 12 would represent September 2014), 01/2015(October 2014), 02/2015(November 2014). The customer service group has deleted the quantity completely from period 12/2014 (September 2014) in ECC. But when i look in the planning book in APO, i can still see the quantities in the periods of 12/2014, 01/2015 and 02/2015. I was expecting the quantity from the period of 12/2014 to not showup in APO as it has been deleted in ECC. Our BW resource also confirms that he has loaded it properly in APO. Where can i start looking to resolve this issue.
Thanks
Ravi

Dear Subhash, Thanks for your reply and i apologize as APO DP is new to me and i'm picking up things, can you please guide me to which tcode should i be going and checking this. Also reloading the planning area can you xplain a little more please
Okay i have checked in the tcode /SAPAPO/TSCUBE and this is setup in the process chain for us which runs once a month on the opening day of the period. I hope this is what you were referring to?
Under the key figure assignment in TSCUBE tcode, i see that the 'Add data" check box is not checked under Target area.

Change order of key figure is not working in Web report output (using WAD)

Hi,
We are using BI 7.0, release 701 and level 008. We are facing problem in WAD (web report output). When ever we do 'Select filter' for key figures and 'change the order' of key figures, it does not get reflected in new order. Though drag and drop of key figures is working.
Though same change order is working fine in Bex Analyser.
Kindly suggest some inputs.
Thanks.

Hi,
On Which Service Pack are you on?WAD has this feature of re arranging the keyfigures in BI 7.0 for SPS 14...
Regards,
Bhagyarekha.

How can i display all the Coloumns (Key Figures) in the Report's same page

Hi All,
I am currently working on the BI 7.0 reporting. In the BEx Query Designer report, I am having 13 coloumns (7 Key figures and 6 Formulas) in the report. It is now displaying 10 coloumns in the First page of report. The other 3 coloumns can be seen by clicking on the next page. But the requirement is to see coloumns in the SAME PAGE.
Are there any settings OR any other thing in the Query Designer, which can enable me to see all the coloumns on SAME page. The users are not interested in scrolling next page for 3 coloumns.
Appreciates the Quick help/Response, please.
Regards
Ramana

In Web Application Designer, for the properties of your analysis webitem under the Paging category, change parameter 'Number of Data Columns Displayed at Once' (BLOCK_COLUMNS_SIZE) to 0. This will make all columns show instead of paginating as it is doing now.

Creation of new key figure at report level depending on the month range

Dear All,
I have a requirment where user wants to see the dollar values for the Amount key figure. Data is stored in the INR value in the cube.
Exchange rate values keep on changing depending upon the quarter. For all four quarters we have four different exchange rate.
Now system has to identify the applicable exchange rate and show a new column with the USD value just beside the INR values column.
How best we can achieve this.
Thanks & Rgds,
Anup

Hi
You can have currency translation at query level for achieving this.
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/600157ec-44e5-2b10-abb0-dc9d06ba6c2f&overridelayout=true
Translation in Query
Regards
Ravi
Edited by: Ravi Naalla on Aug 17, 2009 11:56 AM

Date as a key figure

Hi Experts,
I defined date as a key figure, AAAAMMGG,Iu2019m able to view data in my ODS, but when I try to create a query data format is wrong.
Can anybody share a solution.
Thanks in advance
Namrata

Hi,
May be you are getting a number. What looks like your wrong format? If it is a number,display your figure with a formula, where you will find option to convert data to numbers and number to date.
Cheers,
Tanish

What is diffrernce between key figures and characteristics?

Hi all,
I am a newbie to SAP BI....i am doing Masters in ERP(SAP)....I have confusion about what is basic difference between key figures and characteristics?
Why do we have to define attributes in characteristics?
If any one can refer me a thread that answers my questions or explain with very lucid example I will highly appreciate it.....please answer this question as I have just spend 4-5 months studying BI and have not really implemented in the Industry but we do have access to SAP BI where we perform tutorials....
Also please let me know the links to materials where basics of BI are explained in a very simple way.....
Thanks,
Regards,
Rahul

KF is anything which can quantitatively measured: Amount, Number, Value, Price... whatever you want to measure is called Key Figure. This key figures are also called KPI (Key Performance Indicator). If you want to know the number of sales orders, the number of deliveries, the amount of deliveries... all are key figures
And to add to that, key figures are also divided into two:
Cumulative KF: Like I said, amount, value, price
Non-cumulative KF, this is different kind of key figures which shouldn't be summed up, for example: Age, Inventory, Number of Employees. When you measure this key figures, you don't add the age of every body, because that doesn't make any sense, but adding the sum of all deliveries, or adding all Sales does make sense, that is the difference between the two key figures.
Characteristics: are anything which couldn't be quantitatively measured: material, customer, plant, employee ID and so on...
Aways, in BI you measure the KF against the Key figures..
thanks.
Wond

Key Figures getting added

Hi All,
We arein a process of migrating 3.x Transfer rules and update rules to NW2004s. We are following the standard procedure of migrating the objects such that transfer rules are migrated to a transformations and so do update rules.
In on of the objects while running the loads after migrations the key figures are getting doubled. We were able to debug the standard code and figure out where addition is happening. Strange things is this is a standard SAP code generated in all the migrated objectsbut in this particular case it has generated some extra code which is adding up the key figures. I am pasting code below for your reference and will appreciate if someone can help us to resolve this.
As mentioned above the below Read statement is standard in all the TRCS transformations which are migrated from update rules. This read statement fails with sy-subrc = 4 because <_yth_TG_1>. is empty at this stage but during execution it executes the statement INSERT <_ys_TG_1> INTO TABLE <_yth_TG_1> which populates <_yth_TG_1> and in turn makes the next read statement successful which is extra in this case. There is one more Read statement which is extra in this particular case and is adding up the key figures.
===== PUT groups to target
      IF skipseg_all IS INITIAL.
        READ TABLE <_yth_TG_1>
          WITH TABLE KEY
here it is reading all the different characteristics and key figurs. eliminating this to cut short the lengthof message,
           ASSIGNING <_ys_TG_1>.
        G1_subrc = sy-subrc.
        G1_tabix = sy-tabix.
        IF G1_subrc = 0.
aggregation SUM
          <_ys_TG_1>-POS_FRE = <_ys_TG_1>-POS_FRE + G1-POS_FRE.
          <_ys_TG_1>-POS_OCC = <_ys_TG_1>-POS_OCC + G1-POS_OCC.
          <_ys_TG_1>-POS_VAC = <_ys_TG_1>-POS_VAC + G1-POS_VAC.
          <_ys_TG_1>-/BIC/ZKMOSALRY = <_ys_TG_1>-/BIC/ZKMOSALRY + G1-/BIC/ZKMOSALRY.
          <_ys_TG_1>-/BIC/ZFILFTEFX = <_ys_TG_1>-/BIC/ZFILFTEFX + G1-/BIC/ZFILFTEFX.
          <_ys_TG_1>-/BIC/ZWRKFTEPX = <_ys_TG_1>-/BIC/ZWRKFTEPX + G1-/BIC/ZWRKFTEPX.
          ls_cross-insegid      = 1.
          ls_cross-inrecord     = l_recno_SC_1.
          ls_cross-outsegid     = 1.
          ls_cross-outrecord    = <_ys_TG_1>-record.
          CALL METHOD i_r_log->add_cross_tab
            EXPORTING
              I_S_CROSSTAB = ls_cross.
        ELSE.
          ASSIGN rdsTG_1->*          to <_ys_TG_1>.
          CLEAR <_ys_TG_1>.
          MOVE-CORRESPONDING G1 TO <_ys_TG_1>.
          <_ys_TG_1>-requid    = l_requid.
          l_recno_TG_1          = l_recno_TG_1 + 1.
          ls_cross-insegid      = 1.
          ls_cross-inrecord     = l_recno_SC_1.
          ls_cross-outsegid     = 1.
          ls_cross-outrecord    = l_recno_TG_1.
          CALL METHOD i_r_log->add_cross_tab
            EXPORTING
              I_S_CROSSTAB = ls_cross.
    Record# in target = sy-tabix - if sorting of table won't be changed
          <_ys_TG_1>-record     = l_recno_TG_1.
          INSERT <_ys_TG_1> INTO TABLE <_yth_TG_1>.
          IF sy-subrc <> 0.
            CALL METHOD cl_rsbm_log_step=>raise_step_failed_callstack.
          ENDIF.
        ENDIF.      "Read table
This read statement is extra in this code and when this executes the sy-subrc becomes zero and then it adds up the key figures.
        READ TABLE <_yth_TG_1>
          WITH TABLE KEY
**This also contains the characteristics and key figures which are being update as part of the transformations
           ASSIGNING <_ys_TG_1>.
        G2_subrc = sy-subrc.
        G2_tabix = sy-tabix.
        IF G2_subrc = 0.
aggregation SUM
          <_ys_TG_1>-POS_OCC = <_ys_TG_1>-POS_OCC + G2-POS_OCC.
          <_ys_TG_1>-POS_VAC = <_ys_TG_1>-POS_VAC + G2-POS_VAC.
          <_ys_TG_1>-POS_COUNT = <_ys_TG_1>-POS_COUNT + G2-POS_COUNT.
aggregation MAX
          IF G2-POS_CTSPAN > <_ys_TG_1>-POS_CTSPAN.
            <_ys_TG_1>-POS_CTSPAN = G2-POS_CTSPAN.
          ENDIF.
          ls_cross-insegid      = 1.
          ls_cross-inrecord     = l_recno_SC_1.
          ls_cross-outsegid     = 1.
          ls_cross-outrecord    = <_ys_TG_1>-record.
          CALL METHOD i_r_log->add_cross_tab
            EXPORTING
              I_S_CROSSTAB = ls_cross.
        ELSE.
          ASSIGN rdsTG_1->*          to <_ys_TG_1>.
          CLEAR <_ys_TG_1>.
          <_ys_TG_1>-CURRENCY = G1-CURRENCY.
          MOVE-CORRESPONDING G2 TO <_ys_TG_1>.
          <_ys_TG_1>-requid    = l_requid.
          l_recno_TG_1          = l_recno_TG_1 + 1.
          ls_cross-insegid      = 1.
          ls_cross-inrecord     = l_recno_SC_1.
          ls_cross-outsegid     = 1.
          ls_cross-outrecord    = l_recno_TG_1.
          CALL METHOD i_r_log->add_cross_tab
            EXPORTING
              I_S_CROSSTAB = ls_cross.
    Record# in target = sy-tabix - if sorting of table won't be changed
          <_ys_TG_1>-record     = l_recno_TG_1.
          INSERT <_ys_TG_1> INTO TABLE <_yth_TG_1>.
          IF sy-subrc <> 0.
            CALL METHOD cl_rsbm_log_step=>raise_step_failed_callstack.
          ENDIF.
        ENDIF.      "Read table
Thanks for looking into this and will appreciate your response on this.
Regards
Raman

Have you tried the same thing by deleting the extra 'READ' statement?

Key figure issue

I am loading some data from a flat file to a cube. The file does not supply base unit of measure and currency as a field. And I have that in my info source , because of that when I run the query I am seeing the symbol "ERR" next to the key figures.
So I thought of writting a routine for the individual key figures in the update rules and the routine is :
PROGRAM UPDATE_ROUTINE.
$$ begin of global - insert your declaration only below this line -
TABLES: ...
DATA:   ...
DATA: IN    TYPE F,
      OUT   TYPE F,
      DENOM TYPE F,
      NUMER TYPE F.
DATA: DEB_CRED(2) TYPE C VALUE 'HK'.
DATA: QUOT(1) TYPE C VALUE 'B'.
constants: c_msgty_e value 'E'.
$$ end of global - insert your declaration only before this line   -
FORM compute_data_field
TABLES   MONITOR STRUCTURE RSMONITOR "user defined monitoring
USING    COMM_STRUCTURE LIKE /BIC/CSZSD_SALHIST_HDR
           RECORD_NO LIKE SY-TABIX
           RECORD_ALL LIKE SY-TABIX
           SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
CHANGING RESULT LIKE /BIC/VZSD_C03T-SUBTOT_2S
           UNIT LIKE /BIC/VZSD_C03T-STAT_CURR
           RETURNCODE LIKE SY-SUBRC
           ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update
$$ begin of routine - insert your code only below this line        -
fill the internal table "MONITOR", to make monitor entries
<b>* result value of the routine
RESULT = COMM_STRUCTURE-SUBTOT_2S.
result value of the unit
UNIT = 'USD'.</b>* if the returncode is not equal zero, the result will not be updated
RETURNCODE = 0.
if abort is not equal zero, the update process will be canceled
ABORT = 0.
$$ end of routine - insert your code only before this line         -
ENDFORM.
But now when I am loading the data , it is takin very long. I want move this code to the start routine. I have the same code for the key figures also.
I know I can get rid of the error using "NO DIM " function in BEX but I do not want the users to do that .
Thanks

Hi Jimmy,
You may in transfer rules just assign your currency to 'USD' constant. You can assign a constant to unit too (if you know it) - or assign a routine if you know the logic of the unit determination.
Best regards,
Eugene

BW Statistics Key Figures

Similar Messages

Maybe you are looking for