Rating Calculation

How do calculate the rating for postal reply and anybody give some sample calculation ?

Hi Prakash,
When we have to pick up values from different columns for the final calculation, go for Value Determination BADI enhancement.
If it is from the same column, we can see the final result using the sap standrad functionalities.
Thanks!
Regards,
Chetan

Similar Messages

Help with Risk Rating calculation

I'm trying to understand the risk rating calculation on an IPS4240 sensor. From what I can tell, it looks like there are some additional parameters added to the equation that are not easy to determine. It looks like the ARR (Attack Relevancy Rating) and/or WLR (Watch List Rating) are making changes (i.e. being added to the RR), but I cannot find any values for these. Are there default values for ARR that the system uses? What about the WLR, can that be viewed anywhere?
Any help is appreciated.
Thanks,
Pat

Hi Pat,
I guess below is what you are looking for:
http://www.cisco.com/web/about/security/intelligence/ipsmit.html
It says the below:
"Attack Relevancy Rating: The Attack Relevancy Rating (ARR) is an IPS-generated value that indicates if the attack target may be vulnerable to an event-specific attack. This information is normally gathered through passive operating system identification but can also be defined by a user or gathered through integration with the Cisco Security Agent Management Console. If the operating system of the targeted device is unknown, there is no change to the risk rating. However, if the targeted device operating system is discovered to be relevant, the risk rating increases by 10 in both Inline and Promiscuous modes. If the targeted device operating system is found to be irrelevant, the risk rating in Promiscuous mode is reduced by 10, and no change occurs in Inline mode."
Let me know if this clears things up.
Thanks and Regards,
Prapanch

How to mass copy old rating and weightage to new appraisal documents in OSA

Hello experts,
As a part of annual appraisal process, we have incorporated some new logics in terms of rating calculation and elements in the same templates. But those logics are not being copied in already triggered documents whose goals/objects are approved by manager during mid year.
Now we are planning to trigger new documents for all those employees, but can any one suggest how to copy those approved goals and objectives in new documents? As my client doesnot want to go through the goal setting process again .
Please suggest if any BADI or ABAP program we can use for the same.
Regards
Tandrima

implement a fix enhancement (HRHAP00_ENHANCE_FIX) to add the old approved elements to the new document. And tehn have value determinations (HRHAP00_VAL_DET) to fill these added elements with the correct content.
Regards and Groetjes,
Maurice Hagen

Partition Pruning vs Partition-Wise Join

Hi,
I am not sure if this is the right place for this question, but here it goes.
I am in a situation where in the begining I have to join two big tables without any where clauses. It is pretty much a Caretsian Product where a criteria meets (Internal Code), but I have to join all rows. (Seems like a good place for Partition-Wise Join).
Later I only need to update certain rows based on a key value (Customer ID, Region ID). (Good candidate for Partition Pruning).
What would be the best option. Is there a way to use both?
Assume that following:
Table 1 has the structure of
Customer ID
Internal Code
Other Data
There are about 1000 Customer ID. Each Customer ID has 1000 Internal Codes.
Table 2 has the structure of
Region ID
Internal Code
Other Data
There are about 5000 Region ID. Each Region ID has 1000 Internal Codes(same as Table 1).
I am currently thinking of doing a HASH PARTITION (8 partitions) on Customer ID for Table 1 and HASH PARTITION (8 partitions) on Region ID for Table 2.
The initial insert will take a long time, but when I go to update the joined data based on specific Customer ID, or Region ID atleast from one Table only one Partition will be used.
I would sincerely appreciate some advice from the gurus.
Thanks...

Hi,
I still don't understand what it is that you are trying to do.
Would it be possible for you to create a silly example with just a few rows
to show us what it is that you are trying to accomplish?
Then we can help you solve whatever problem it is that you are having.
create table t1(
   customer_id   number       not null
,internal_code varchar2(20) not null
,<other_columns>
,constraint t1_pk primary key(customer_id, internal_code)
create table t2(
   region_id number not null
,internal_code varchar2(20) not null
,<other_columns>
,constraint t2_pk primary key(region_id, internal_code)
insert into t1(customer_id, internal_code, ...) values(...);
insert into t1(customer_id, internal_code, ...) values(...);
insert into t2(region_id, internal_code, ...) values(...);
insert into t2(region_id, internal_code, ...) values(...);
select <the rating calculation>
   from t1 join t2 using(internal_code);

Global Correlation Risk Delta

Hi,
I'm currently working on Tuning a pair of IPS modules in ASA's. We are currently in Promiscous and tuning/filtering to ensure we don't block any valid traffic when making the switch to inline.
We are using the new 7.0.1 code and getting the global correlation / reputation data - works great & rocks.
When viewing the events - there is a paramater - "Global Correlation Risk Delta" -- Could someone explain to me what that is?
I understand how it adjusts the RR based on reputation & have the chart (including it for those who do not have it - got it from a networkers prezo). However I am having a hard time figuring out what Global Correlation Risk Delta is/means/does...anyone know?
Thanks,
Brad

Here is a basic description.
Without Global Correlation (versions prior to 7.0, or version 7.0 with the feature turned off) all alert triggerings will have a Risk Rating calculated.
How a Risk Rating is calculated is explained in the following White Paper on cisco.com:
http://www.cisco.com/en/US/prod/collateral/vpndevc/ps5729/ps5713/ps4077/prod_white_paper0900aecd806e7299.html
Now with version 7.0 when Global Correlation is enabled there is now a new parameter added to the Risk Rating calculation ( + Global Correlation Risk Delta )
The Global Correlation Risk Delta is either 0 or a positive value and so can keep the Risk Rating the same, or raise the Risk Rating, but will not decrease the Risk Rating.
The Global Correlation Risk Delta is calculated based on both the Attacker IP address, and the Initial Risk Rating ( The Initial Risk Rating is the Risk Rating calculated without the Global Correlation Risk Delta).
When Global Correlation is enabled in version 7.0 the sensor will download a Reputation Database from the cisco servers. This reputation database contains lists of Public IP Addresses that have been known to be sources of attacks in the past. With that database a Negative Reputation Score is determined for each Address in the database. The Negative Reputation Score could range anywhere from a -0.5 to a -10. If only a few atttacks have been seen from the address, the score may be only slightl negative in the -0.5 - -3 range. The worst offending Attacker IP Addresses could have negative scores in the -8 to -10 range.
That Reputation Database is only for Public IP Addresses. So Private IP Addresses (addresses used only with NAT/PAT and are not Internet routable) will not exist in the Reputation Database.
If the attacker IP Address is a Private IP Address, or is a Public IP Address that is NOT in the Reputation Database, then the sensor will automatically set the Global Correlation Risk Delta to 0.
When added into the Original Risk Rating, the Risk Rating winds up the same (no change).
So Global Correlation has no effect on Private IP Addresses, or Public IP Addresses that do NOT have Negative Reputation.
It is only when the Attacker is from a Public IP Address with Negative Reputation that the Global Correlation Risk Delta is calculated.
Internally the sensor has a formula to calculate what that Delta should be.
The inputs to that formula are the Negative Reputation Score for the Atttacker IP, Original Risk Rating, as well as some proprietary variables for fine tuning the formula.
All of these are inputs to the formula, and the one output is the Delta.
The Delta is then Added to the Initial Risk Rating and results in a Higher Risk Rating.
The chart from your first post is a result of plugging in the highest 20 possible Risk Ratings, and 20 possible negative Reputation scores, and uses the original proprietary variable settings, and shows you what the formula will output as the Global Correlation Risk Delta.
So this should be used as just an example.
The formula will still be used for Risk Ratings lower than 80 that are not shown on the chart, and will also be used for Negative Reputation Scores that are not neatly rounded to a 0.5 number.
Also the proprietary variables are also subject to change, as we continue to fine tune the formula.
So the chart you've posted is a good example of the type of Deltas that the formula can output.
Because of this calculated Delta being added to the Risk Rating, the same attack coming from a known Negative Reputation Public Address will wind up with a Higher Risk Rating than the same attack coming from a Private IP Address (or even the same Public Address when not using Global Correlation).
The sensor then has features for how it can then make use of the Risk Rating.
And I will talk about this in the next post. I am limited by the number of characters in a single post or I would have put it into this post.

Error in formula while using CASE

Hi all ,
First of all is there any limit on how many WHEN and THEN we can use in a CASE statement?
I'm trying to use the following CALCULATION in DISCO plus and getting the following error.
Error in formula: ambiguous or duplicate item names - Inventory rating
Calculation:
case when Inventory Rating = '20' then 0
when Inventory Rating = '21' then 2
when Inventory Rating = '22' then 4
when Inventory Rating = '23' then 6
when Inventory Rating = '24' then 8
when Inventory Rating = '25' then 10
when Inventory Rating = '26' then 18
when Inventory Rating = '27' then 26
when Inventory Rating = '28' then 34
when Inventory Rating = '29' then 42
when Inventory Rating ='30' then 50
when Inventory Rating ='31' then 58
when Inventory Rating = '32' then 66
when Inventory Rating = '33' then 74
when Inventory Rating = '34' then 82
when Inventory Rating ='35' then 90
when Inventory Rating= '36' then 92
when Inventory Rating = '37' then 94
when Inventory Rating = '38' then 96
when Inventory Rating = '39' then 98
when Inventory Rating >'40’ then 100
when Inventory Rating ='N' then 0
else null
end
Thanks

Hello
Let's look at your error first. Discoverer is informing you that you may have 2 items called Inventory Rating either in the folders you are using or in your calculations and it doesn't know which one you want. If you do have this issue then one way to overcome it would be to create yourself a new calcultion called with a unique name and push the real item in there then alter your CASE statement. The other way would be to edit every line of your CASE statement, highlight Inventory Rating and then paste the correct item over it.
As for a limit, there is a limit of 255 arguments in a CASE statement. Look here: http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/expressions004.htm
You also have to be careful adding another argument using = following an argument using > or <. This is because the CASE statement works in sets and as each argument is processed, all data meeting that criteria is removed from the data being compared in the next argument.
Please look at this, taken from the end of your code:
when Inventory Rating >'40’ then 100
when Inventory Rating ='N' then 0
else null
end
An Inventory Rating of 'N' is greater than '40' so these will be assigned 100. I would recommend you switch the position of these 2 arguments so that the last part of your calculation looks like this:
when Inventory Rating ='N' then 0
when Inventory Rating >'40’ then 100
else null
end
Hope this helps
Best wishes
Michael

E-mail Campaign Execution

Hello,
I have executed a E-mail Campaign , with a target group having 25 BP's. All Bp's have the same mail Id, as this was test scenario.
The probelm is, this campaign gets executed unstoppably and the the person with this mail id gets 25 mails everyday.
How can I stop this. Pls treat this request as urgent.
Thanks & Regards,
Raju

Hello Raju,
You could look at the tables CRM_SVY_DB_SV, CRM_SVY_DB_SVS and CRM_SVY_RE_ANSW.
In the survey builder you could maintain rating values for responses from the input field and text field type in the expert mode.However, since the rating of input fields is problematic as a program cannot value the contents of a user-defined text field. Therefore, input fields were excluded from the rating calculation.
There is no standard source document which would give a list of CRM tables except a few use case design document that was shared to me by community members which I could share with you.
Please award points in case the answers were satisfactory.
Thanks

Tax (VAT) being calculated on sales invoices where products are zero rated?

Hi
We are in the process of testing v. 12.1.2 (upgrading from v. 12.0.4).
We are producing sales invoices of zero rated products. However, tax is being calculated on these products. Have checked the item set up and the item is definately set to UK zero fiscal classification.
Is there somewhere in customer set up and/or tax administrator I can check to see if any of our set up is incorrect?
Regards
Jon

When I tested this for the Customer I was able to calculate sales tax on an A/R invoice even when the BP was set to Exempt. I just want to make sure the system is functioning correctly. If I need to change the BP from Exempt to Tax Liable in order to be able to charge tax in some cases then I will do so.
Also, I was told by another SAP consultant the the ONLY thing SAP looks at when deciding to calculate tax was the Ship to address tax code, which does not seem to be the case.
Don

Exclude specific songs from factoring into auto calculated Album Rating?

I really like using the calculated (empty star) Album Rating system, however I was wondering if there was a way to exclude some songs on an album from being averaged into the Album Rating. My reasoning for this is that I don't want intros/outros/skits or bonus tracks to bring the overall rating of an album down (there are many albums in my library that drop down a star rating because of bonus tracks that I don't really like, but wish to keep a part of the album for collection purposes). Is there anyway to make this happen? Thanks.

You do have a very complex looking site and may need several tables in mysql to handle all that data. If you knew to phpmysql I would suggest taking a look at this tutorial it will help get you started in understanding how to $_GET info from a database and also how to $_POST data to a database. I am no expert just learning myself and I found this very helpful. This is the link http://www.adobe.com/devnet/dreamweaver/articles/first_dynamic_site_pt1.html
There are also many tutorials on Youtube to help build a CMS Content Management Site I would suggest the following: -
http://www.youtube.com/user/phpacademy
http://www.youtube.com/user/betterphp
http://www.youtube.com/user/flashbuilding
And many more on my channel here
http://www.youtube.com/user/Whisperingonthewind
CMS's are easier to maintain, add edit and delete content.
I have also recently bought a Book by David Powers Training from the Source very helpful.
Anyway hope you get it sorted.

Error in Proportional Factor Calculation Program

Hi ,
I have developed an ABAP Program to calculate Proportional Factor(PF) as below.
Generally,to calculate the PF for a period , we need to use transaction /sapapo/sdp94 to create a profile .After doing that , to calculate PF we need to go transaction /sapapo/mv8v .
Now,the given program has three options :-
1)Create : To create the selection-ID by taking areabasepackRS as name of the selection-ID . Here we need to give the excel sheet that is used to load data into /sapapo/mc8v to calculate PF.
2)Calculate PF : This option is used to calculate proportional factor.
   Now if we try to calculate PF ,I get an error message saying there are no
   plannable characteristic combinations .
3) Delete : This option is used to delete the selection profile.
I am getting an error in this program which I have explained with the document attached in this mail .
Please could anyone help me out with this .
The program is as below:-
<b>report ZRSNORMS_PPF
       no standard page heading line-size 255.</b>
*include bdcrecx1.
INCLUDE ZAPO_DATA_DECLARATION_PPF.
INCLUDE Z_APO_FORMS_PPF.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file1.
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
   EXPORTING
     program_name        = syst-repid
DYNPRO_NUMBER       = SYST-DYNNR
     field_name          = p_file1
STATIC              = ' '
MASK                = ' '
    CHANGING
      file_name           = p_file1
EXCEPTIONS
MASK_TOO_LONG       = 1
OTHERS              = 2
IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
start-of-selection.
PERFORM READ_DATA TABLES I_PROFILE
                           I_EXEL
                           IT_PROFILE_NAME
                    USING P_FILE1
                    CHANGING W_SUBRC.
PERFORM SAVE_SELECTION TABLES I_EXEL
                                IT_SAVE_SEL
                                IT_PROFILE_NAME.
IT_GRP-OBJNAM = 'ZRSBASPCK'.
APPEND IT_GRP.
LOOP AT IT_GRP INTO W_GROUP.
    APPEND W_GROUP TO IT_GROUP.
ENDLOOP.
G_PAREAID = 'ZRSPAHPC'.
G_MVIEW = 'ZRSPAHPC'.
G_COUNT = 0.
IF CREATE = 'X'.
LOOP AT IT_SAVE_SEL INTO W_SEL_SAVE.
    IF W_SEL_SAVE-IOBJNM = '9AVERSION' AND SY-TABIX > 1.
      G_COUNT = G_COUNT + 1.
      READ TABLE IT_PROFILE_NAME INDEX G_COUNT.
      G_NAME = IT_PROFILE_NAME-F_NAME.
      CALL FUNCTION '/SAPAPO/MCPSH_SELECTION_SAVE'
        EXPORTING
IV_SELID                       =
IV_FLG_USED_FOR                =
          IV_PAREAID                     = G_PAREAID
         IV_MVIEW                       = G_MVIEW
         IV_SEL_DESCRIPTION             = G_NAME
         IT_SELECTION                   = IT_SEL_SAVE
IT_OBJECTS                     =
         IT_SEL_GROUP                   = IT_GROUP
IV_POPUP_SEL_DESCRIPTION       =
IMPORTING
EV_SELID                       =
EV_SEL_DESCRIPTION             =
EXCEPTIONS
DUPLICATE_SELECTION            = 1
MULTIPLE_SELECTION             = 2
INCONSISTENT_DATABASE          = 3
DUPLICATE_DESCRIPTION          = 4
INVALID_DESCRIPTION            = 5
NO_PERMISSION                  = 6
SELID_INVALID                  = 7
OTHERS                         = 8
      IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      CLEAR IT_SEL_SAVE[].
      APPEND W_SEL_SAVE TO IT_SEL_SAVE.
    ELSEIF W_SEL_SAVE-IOBJNM = '9AVERSION' AND SY-TABIX = 1.
      APPEND W_SEL_SAVE TO IT_SEL_SAVE.
    ELSE.
      APPEND W_SEL_SAVE TO IT_SEL_SAVE.
    ENDIF.
ENDLOOP.
G_COUNT = G_COUNT + 1.
READ TABLE IT_PROFILE_NAME INDEX G_COUNT.
G_NAME = IT_PROFILE_NAME-F_NAME.
CALL FUNCTION '/SAPAPO/MCPSH_SELECTION_SAVE'
    EXPORTING
IV_SELID                       =
IV_FLG_USED_FOR                =
      IV_PAREAID                     = G_PAREAID
     IV_MVIEW                       = G_MVIEW
     IV_SEL_DESCRIPTION             = G_NAME
     IT_SELECTION                   = IT_SEL_SAVE
IT_OBJECTS                     =
     IT_SEL_GROUP                   = IT_GROUP
IV_POPUP_SEL_DESCRIPTION       =
IMPORTING
EV_SELID                       =
EV_SEL_DESCRIPTION             =
EXCEPTIONS
DUPLICATE_SELECTION            = 1
MULTIPLE_SELECTION             = 2
INCONSISTENT_DATABASE          = 3
DUPLICATE_DESCRIPTION          = 4
INVALID_DESCRIPTION            = 5
NO_PERMISSION                  = 6
SELID_INVALID                  = 7
OTHERS                         = 8
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IV_GROUP = 'ZRSBASPCK'.
LOOP AT IT_SEL_SAVE INTO w_confirm_sel.
    APPEND w_confirm_sel TO it_confirm_sel.
ENDLOOP.
CALL FUNCTION '/SAPAPO/MSDP_SH_OBJ_LIST_BUILD'
    EXPORTING
      IV_PAREAID           = G_PAREAID
     IV_MVIEW             = G_MVIEW
    IV_DVIEW             =
    IV_FROMDATE          =
    IV_ENDDATE           =
    IV_NO_POPUPS         =
IMPORTING
    ET_SH_OBJECTS        =
EXCEPTIONS
    INVALID_INPUT        = 1
    INTERNAL_ERROR       = 2
    OTHERS               = 3
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CLEAR IT_SEL_SAVE[].
ENDIF.
if calc_ppf = 'X'.
PERFORM CALC_PPF TABLES I_EXEL
                          BDCTAB
                          IT_PROFILE_NAME.
ENDIF.
if del_prof = 'X'.
LOOP AT I_EXEL.
concatenate i_exel-area I_EXEL-BASE INTO DEL_NAME.
SELECT SINGLE * FROM /SAPAPO/TS_SELKO INTO IT_TS_SELKO
WHERE SEL_DESRCIPTION = DEL_NAME.
DEL_PROFILE = IT_TS_SELKO-SELECTIONID.
CALL FUNCTION '/SAPAPO/MCPSH_SELECTION_DELETE'
EXPORTING
    IV_SELID                    = DEL_PROFILE
IV_FLG_CONFIRM_TRANS        = 'X'
EXCEPTIONS
NO_ENTRY                    = 1
NO_AUTHORITY                = 2
DELETION_NOT_POSSIBLE       = 3
OTHERS                      = 4
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDLOOP.
ENDIF.
<b>INCLUDE   ZAPO_DATA_DECLARATION_PPF .</b>
types: t_ts_selpo type /sapapo/ts_selpo.
TYPES: BEGIN OF T_EXEL,
       PROF_DATFRM TYPE DATS,
       PROF_DATTO TYPE DATS,
       FORCAST_FROM TYPE DATS,
       FORCAST_TO TYPE DATS,
       AREA(60),
       BASE(60),
       POPID(60),
       RATING(60),
       RS(60),
       END OF T_EXEL.
types: begin of t_profile,
       obj(30),
       val(60),
       end of t_profile.
TYPES: begin of t_profile_name,
       f_name(60),
       end of t_profile_name.
DATA: G_COUNT TYPE I VALUE 0.
*TYPES: T_SAVE_SEL LIKE IT_SELECTION.
data: w_subrc TYPE sy-subrc,
      I_TS_SELPO TYPE Table of t_ts_selpo with header line,
      I_EXEL TYPE Table of t_EXEL with header line.
DATA: IV_GROUP TYPE /SAPAPO/IOBJNM.
DATA: IT_PROFILE_NAME TYPE TABLE OF T_PROFILE_NAME WITH HEADER LINE.
data: i_profile type table of t_profile with header line.
*/sapapo/ts_iobj_selection_tab.
data: IT_SEL_SAVE TYPE /sapapo/ts_iobj_selection_tab,
      w_SEL_SAVE type /SAPAPO/TS_IOBJ_SELECTION.
DATA: IT_CONFIRM_SEL TYPE /SAPAPO/SH_SEL_RANGE_TAB,
      W_CONFIRM_SEL TYPE /SAPAPO/SH_SEL_RANGE_STR.
TYPES: BEGIN OF T_SAVE_SEL,
       IOBJNM(30),
       SIGN,
       OPTION(2),
       LOW(60),
       HIGH(60),
       END OF T_SAVE_SEL.
DATA: IT_SAVE_SEL TYPE TABLE OF T_SAVE_SEL WITH HEADER LINE.
TYPES: BEGIN OF T_GRP,
      OBJNAM(30),
      END OF T_GRP.
DATA: IT_GRP TYPE TABLE OF T_GRP WITH HEADER LINE.
DATA DECLARATION FOR FUNC MODULE **************
DATA: IT_GROUP TYPE /SAPAPO/TS_GROUP_BY_TAB,
      W_GROUP TYPE /SAPAPO/TS_GROUP_BY_STR.
DATA: G_PAREAID TYPE /SAPAPO/TS_PAREAID,
      G_MVIEW TYPE /SAPAPO/PB_MVIEW,
      G_NAME TYPE /SAPAPO/TS_SEL_DESCR.
BDC TABLES ***************************
DATA: bdcdata LIKE bdcdata OCCURS 0 WITH HEADER LINE.
DATA: it_messtab LIKE bdcmsgcoll OCCURS 0 WITH HEADER LINE.
DATA : BDCTAB like BDCDATA occurs 0 with header line.
DATA : w_file type string.
****************BDC ERROR TAB ***************************
DATA : xcount1 TYPE i,
       xstat TYPE i,
       xmsgv1 LIKE balm-msgv1,
       xmsgv2 LIKE balm-msgv2,
       xmsgv3 LIKE balm-msgv3,
       xmsgv4 LIKE balm-msgv4,
       xmessage(80) TYPE c.
DATA : BEGIN OF t_errlog OCCURS 0,
        sno TYPE i,
        message(80) TYPE c,
        END OF t_errlog.
DATA: DEL_PROFILE TYPE /SAPAPO/SELECTIONID2,
      DEL_NAME(60).
************DUPLICATE NAME TAB **************************
DATA: IT_NOT_PROCESSED TYPE TABLE OF /SAPAPO/TS_SELPO WITH HEADER LINE.
DELETE TAB *****************************
DATA: IT_TS_SELKO TYPE TABLE OF /SAPAPO/TS_SELKO WITH HEADER LINE.
SELECTION-SCREEN : BEGIN OF BLOCK b1.
parameters: p_file1 TYPE rlgrap-filename.
parameters: create type c radiobutton group g1,
            calc_ppf type c radiobutton group g1,
            del_prof type c radiobutton group g1.
SELECTION-SCREEN END OF BLOCK b1.
Include           Z_APO_FORMS_PPF
*& Include           Z_APO_FORMS_PPF
*&      Form READ_DATA
      text
     -->P_I_PROFILE text
     -->P_I_EXEL text
     -->P_IT_PROFILE_NAME text
     -->P_P_FILE1 text
     <--P_W_SUBRC text
FORM READ_DATA TABLES   P_I_PROFILE STRUCTURE I_PROFILE
                         P_I_EXEL STRUCTURE I_EXEL
                         P_IT_PROFILE_NAME STRUCTURE IT_PROFILE_NAME
                USING    P_P_FILE1
                CHANGING P_W_SUBRC.
DATA : iexcel LIKE zexcel_read OCCURS 0 WITH HEADER LINE,
         G_DATE TYPE DATS.
data: l_name(60).
CLEAR p_w_subrc.
CALL FUNCTION 'ZALSM_EXCEL_TO_INTERNAL_TABLE'
    EXPORTING
      filename    = p_p_file1
      i_begin_col = 1
      i_begin_row = 1
      i_end_col   = 62
      i_end_row   = 50000
    TABLES
      intern      = iexcel.
   EXCEPTIONS
     inconsistent_parameters = 1
     upload_ole              = 2
     OTHERS                  = 3.
IF sy-subrc <> 0.
    p_w_subrc = 0 .
endif.
   MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
           WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
LOOP AT iexcel WHERE row > 1.
    IF iexcel-col = '0001'.
    PERFORM CONVERT_DATE CHANGING G_DATE iexcel-value.
    p_i_EXEL-PROF_DATFRM = G_DATE.
    ENDIF.
    IF iexcel-col = '0002'.
    PERFORM CONVERT_DATE CHANGING G_DATE iexcel-value.
      p_i_EXEL-PROF_DATTO = G_DATE.
       ENDIF.
    IF iexcel-col = '0003'.
    PERFORM CONVERT_DATE CHANGING G_DATE iexcel-value.
      p_i_EXEL-FORCAST_FROM = G_DATE.
    ENDIF.
    IF iexcel-col = '0004'.
    PERFORM CONVERT_DATE CHANGING G_DATE iexcel-value.
      p_i_EXEL-FORCAST_TO = G_DATE.
    ENDIF.
    IF iexcel-col = '0005'.
      p_i_EXEL-AREA = iexcel-value.
      p_i_profile-obj = 'ZRSAREA'.
      p_i_profile-VAL = iexcel-value.
      append p_i_PROFILE.
      clear p_i_PROFILE.
    ENDIF.
    IF iexcel-col = '0006'.
      p_i_EXEL-BASE = iexcel-value.
      p_i_profile-obj = 'ZRSBASPCK'.
      p_i_profile-VAL = iexcel-value.
         append p_i_PROFILE.
      clear p_i_PROFILE.
    ENDIF.
    IF iexcel-col = '0007'.
      p_i_EXEL-POPID = iexcel-value.
      p_i_profile-obj = 'ZRSPOPULN'.
      p_i_profile-VAL = iexcel-value.
         append p_i_PROFILE.
      clear p_i_PROFILE.
    ENDIF.
    IF iexcel-col = '0008'.
    p_i_EXEL-RATING = iexcel-value.
    ENDIF.
    IF iexcel-col = '0009'.
      p_i_EXEL-RS = iexcel-value.
      p_i_profile-obj = 'ZRSCUSTMR'.
      p_i_profile-VAL = iexcel-value.
      append p_i_PROFILE.
      clear p_i_PROFILE.
    ENDIF.
    at end of row.
      append p_i_EXEL.
      clear p_i_EXEL.
    endat.
endloop.
loop at P_I_EXEL.
concatenate P_I_EXEL-AREA P_I_EXEL-BASE INTO L_NAME.
P_it_profile_name-f_name = l_name.
append P_it_profile_name.
ENDLOOP.
ENDFORM.                    " READ_DATA
*&      Form CONVERT_DATE
      text
     <--P_G_DATE text
     <--P_IEXCEL_VALUE text
FORM CONVERT_DATE CHANGING P_G_DATE
                            P_IEXCEL_VALUE.
                            CALL FUNCTION 'CONVERT_DATE_TO_INTERNAL'
EXPORTING
    DATE_EXTERNAL                  = p_iexcel_value
ACCEPT_INITIAL_DATE            =
IMPORTING
   DATE_INTERNAL                  = p_g_date
EXCEPTIONS
DATE_EXTERNAL_IS_INVALID       = 1
OTHERS                         = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " CONVERT_DATE
*&      Form SAVE_SELECTION
      text
     -->P_I_EXEL text
     -->P_IT_SAVE_SEL text
     -->P_IT_PROFILE_NAME text
FORM SAVE_SELECTION TABLES   P_I_EXEL STRUCTURE I_EXEL
                              P_IT_SAVE_SEL STRUCTURE IT_SAVE_SEL
                              P_IT_PROFILE_NAME STRUCTURE IT_PROFILE_NAME.
DATA: L_PAREAID(40).
loop at p_i_exel.
p_it_save_sel-iobjnm = '9AVERSION'.
p_it_save_sel-SIGN = 'I'.
p_it_save_sel-OPTION = 'EQ'.
p_it_save_sel-LOW = '000'.
APPEND P_IT_SAVE_SEL.
CLEAR P_IT_SAVE_SEL.
p_it_save_sel-iobjnm = 'ZRSAREA'.
p_it_save_sel-SIGN = 'I'.
p_it_save_sel-OPTION = 'EQ'.
p_it_save_sel-LOW = P_I_EXEL-AREA.
APPEND P_IT_SAVE_SEL.
CLEAR P_IT_SAVE_SEL.
IF NOT P_I_EXEL-BASE IS INITIAL.
p_it_save_sel-iobjnm = 'ZRSBASPCK'.
p_it_save_sel-SIGN = 'I'.
p_it_save_sel-OPTION = 'EQ'.
p_it_save_sel-LOW = P_I_EXEL-BASE.
ENDIF.
APPEND P_IT_SAVE_SEL.
CLEAR P_IT_SAVE_SEL.
IF NOT P_I_EXEL-POPID IS INITIAL.
p_it_save_sel-iobjnm = 'ZRSPOPULN'.
p_it_save_sel-SIGN = 'I'.
p_it_save_sel-OPTION = 'EQ'.
p_it_save_sel-LOW = P_I_EXEL-POPID.
APPEND P_IT_SAVE_SEL.
CLEAR P_IT_SAVE_SEL.
ENDIF.
IF NOT P_I_EXEL-RS IS INITIAL.
p_it_save_sel-iobjnm = 'ZRSCUSTMR'.
p_it_save_sel-SIGN = 'I'.
p_it_save_sel-OPTION = 'EQ'.
p_it_save_sel-LOW = P_I_EXEL-RS.
APPEND P_IT_SAVE_SEL.
CLEAR P_IT_SAVE_SEL.
ENDIF.
write 'hi'.
*CLEAR P_IT_SAVE_SEL[].
ENDLOOP.
*submit
ENDFORM.                    " SAVE_SELECTION
*&      Form CALC_PPF
      text
     -->P_I_EXEL text
     -->P_BDCTAB text
     -->P_IT_PROFILE_NAME text
FORM CALC_PPF TABLES   P_I_EXEL STRUCTURE I_EXEL
                        P_BDCTAB STRUCTURE BDCTAB
                        P_IT_PROFILE_NAME STRUCTURE IT_PROFILE_NAME.
DATA: PERIOD_FROM TYPE /SAPAPO/BASIS_VON_BIS,
      PERIOD_TO TYPE /SAPAPO/BASIS_VON_BIS,
      TRANSFER_FORM TYPE /SAPAPO/TARGET_VON_BIS,
      TRANSFER_TO TYPE /SAPAPO/TARGET_VON_BIS,
      SEL_PROFILE TYPE /SAPAPO/SEL_TXT.
DATA: SEL_NAME(60).
DATA : L_TEMP TYPE SY-DATUM,
       L_TEMP1 TYPE SY-DATUM,
       L_TEMP2 TYPE SY-DATUM,
       L_TEMP3 TYPE SY-DATUM.
LOOP AT P_I_EXEL.
L_TEMP0(2) = P_I_EXEL-FORCAST_FROM6(2). "passed date
L_TEMP2(2) = P_I_EXEL-FORCAST_FROM4(2). "passed Month
L_TEMP4(4) = P_I_EXEL-FORCAST_FROM0(4). "passed year
L_TEMP10(2) = P_I_EXEL-FORCAST_TO6(2). "passed date
L_TEMP12(2) = P_I_EXEL-FORCAST_TO4(2). "passed Month
L_TEMP14(4) = P_I_EXEL-FORCAST_TO0(4). "passed year
L_TEMP20(2) = P_I_EXEL-PROF_DATFRM6(2). "passed date
L_TEMP22(2) = P_I_EXEL-PROF_DATFRM4(2). "passed Month
L_TEMP24(4) = P_I_EXEL-PROF_DATFRM0(4). "passed year
L_TEMP30(2) = P_I_EXEL-PROF_DATTO6(2). "passed date
L_TEMP32(2) = P_I_EXEL-PROF_DATTO4(2). "passed Month
L_TEMP34(4) = P_I_EXEL-PROF_DATTO0(4). "passed year
PERIOD_FROM = L_TEMP2.
PERIOD_TO = L_TEMP3.
transfer_form = L_TEMP.
TRANSFER_TO = L_TEMP1.
concatenate P_I_EXEL-AREA P_I_EXEL-BASE INTO SEL_NAME.
SEL_PROFILE = SEL_NAME.
perform bdc_dynpro      using '/SAPAPO/RMDP_SHARE_VERSION_M' '1000'.
perform bdc_field       using 'BDC_CURSOR'
                              'BPAREAID'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ONLI'.
perform bdc_field       using 'PAREAID'
                              'ZRSPAHPC'.
perform bdc_field       using 'FLG_AREA'
                              'X'.
perform bdc_field       using 'BPAREAID'
                              'ZRSPAHPC'.
perform bdc_dynpro      using '/SAPAPO/RMDP_SHARE_MANAGER' '1000'.
perform bdc_field       using 'BDC_OKCODE'
                              '=UCOMM1'.
perform bdc_field       using 'BDC_CURSOR'
                              'Z_DATE-HIGH'.
perform bdc_field       using 'B_VER'
                              '000'.
perform bdc_field       using 'B_KENN'
                              '9AVCORHIST'.
perform bdc_field       using 'B_DATE-LOW'
                              PERIOD_FROM.
perform bdc_field       using 'B_DATE-HIGH'
                              PERIOD_TO.
perform bdc_field       using 'VERSION'
                              '000'.
perform bdc_field       using 'Z_DATE-LOW'
                              transfer_form.
perform bdc_field       using 'Z_DATE-HIGH'
                              TRANSFER_TO.
perform bdc_field       using 'FLG_ONE'
                              'X'.
perform bdc_dynpro      using '/SAPAPO/RMDP_SHARE_MANAGER' '1000'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ONLI'.
perform bdc_field       using 'BDC_CURSOR'
                              'SEL_TXT'.
perform bdc_field       using 'SEL_TXT'
                               SEL_PROFILE.
perform bdc_dynpro      using '/SAPAPO/RMDP_SHARE_MANAGER' '1000'.
perform bdc_field       using 'BDC_OKCODE'
                              '/EE'.
perform bdc_dynpro      using '/SAPAPO/RMDP_SHARE_VERSION_M' '1000'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ONLI'.
perform bdc_field       using 'BDC_OKCODE'
                              '/EE'.
perform bdc_field       using 'BDC_CURSOR'
                              'PAREAID'.
*perform bdc_transaction using '/SAPAPO/MC8V'.
SELECT SINGLE * FROM /SAPAPO/TS_SELKO INTO IT_TS_SELKO
WHERE SEL_DESRCIPTION = sel_NAME.
if sy-subrc = 0.
call transaction '/SAPAPO/MC8V'
         using bdctab
         mode 'A'
         update 'L'
         messages into it_messtab.
describe table it_messtab lines xcount1.
read table it_messtab index xcount1.
LOOP AT it_messtab WHERE msgtyp = 'E'
                                 OR msgtyp = 'A'.
            MOVE It_messtab-msgv1 TO xmsgv1.
            MOVE It_messtab-msgv2 TO xmsgv2.
            MOVE It_messtab-msgv3 TO xmsgv3.
            MOVE It_messtab-msgv4 TO xmsgv4.
      CALL FUNCTION 'MESSAGE_PREPARE'
        EXPORTING
         LANGUAGE                     = sy-langu
          msg_id                       = It_messtab-msgid
          msg_no                       = It_messtab-msgnr
         MSG_VAR1                     = xmsgv1
         MSG_VAR2                     = xmsgv2
         MSG_VAR3                     = xmsgv3
         MSG_VAR4                     = xmsgv4
       IMPORTING
         MSG_TEXT                     = xmessage
       EXCEPTIONS
         FUNCTION_NOT_COMPLETED       = 1
         MESSAGE_NOT_FOUND            = 2
         OTHERS                       = 3
      IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      MOVE sy-tabix TO t_errlog-sno.
      MOVE xmessage TO t_errlog-message.
            APPEND t_errlog.
            CLEAR t_errlog..
          ENDLOOP.
CLEAR BDCTAB[].
CLEAR SEL_NAME.
CLEAR P_I_EXEL.
endif.
ENDLOOP.
ENDFORM.                    " CALC_PPF
*&      Form bdc_dynpro
      text
     -->P_0424   text
     -->P_0425   text
FORM bdc_dynpro USING PROGRAM DYNPRO.
CLEAR bdcTAB.
bdcTAB-program = program.
bdcTAB-dynpro   = dynpro.
bdcTAB-dynbegin = 'X'.
APPEND bdcTAB.
ENDFORM.                    " bdc_dynpro
*&      Form bdc_field
      text
     -->P_0494   text
     -->P_TRANSFER_FROM text
FORM bdc_field USING FNAM FVAL.
CLEAR bdcTAB.
bdcTAB-fnam = fnam.
bdcTAB-fval = fval.
APPEND bdcTAB.
ENDFORM.                    " bdc_field

Hi,
As I have not been able to attach the document, I will explain the problem in full as below:-
Business scenario - Consider a factory having 5 different customers (which is known as Customer_rs). We need to supply stock to each of them based on their past consumption. So to forecast this, we calculate a factor known as proportional factor based on the data we have for previous months.
So to calculate the PF for a period, we need to create a profile in /sapapo/sdp94 .
After creating the profile, the profile can be seen by clicking on SPD94 and going to selection-screen button .
Then to calculate PF , we need to go to transaction /sapapo/mv8v .
Here we will have to give the selection id that was saved in SDP94.
All this process has to be automated and a program has been created to do this.
A description of how the program works is as given below.
When we try to calculate the proportional factor with this program , the following error is obtained :-
There are no plannable characteristic combinations.
We are passing the same parameters that were passed by the SDP94 transaction to the standard function module for saving the selection ids. This is shown in the below screenshots.
In spite of this we are getting the error.
Now to delete the selection ids,click on delete option in the program .
But the problem is even if we click on delete , the PPF data will be stored in the database inspite of deleting the selection profiles .
Please can anyone help me out with this .
Regards,
Sushanth H.S.
                                                                                Now we will have to give the selection description
Now the profile can be seen by going to SDP94 and clicking on selection profile button.
Now to calculate PF, go to transaction /sapapo/mv8v
Click on execute and give following inputs
This will forecast the PF for the period 01.09.2007 to 21.02.2007 based on data from 21.04.2007 to 20.05.2007
Click on other settings
Here we will have to give the selection id that was saved in SDP94.
Click on execute.
All this process has to be automated and a program was created to do this.
A description of how the program is given below.
Program zrsnorms_ppf
Execute.
Give file path of excel sheet.
Execute.
This will create the selection id by taking areabasepackRS as name of id.
This is the excel sheet that is used to load data into /sapapo/mc8v to calculate the PF.
Upon executing, the ids have been created
The new selection ids can be seen by going to /sapapo/sdp94
And clicking on selection profile.
Parameters passed to standard function module in order to save the selection id.
Now if we try to calculate PF using the program, the following happens
When executed,
BDC is called to input data to transaction /sapapo/mc8v to calculate ppf.
An error screen is generated with the message There are no plannable characteristic combinations.
We are passing the same parameters that were passed by the SDP94 transaction to the standard function module for saving the selection ids. This is shown in the below screenshots.
In spite of this we are getting the error.
When IV_POPUP_SEL_DESCRIPTION is passed, a popup will be displayed where the selection description will have to be entered. I am passing the same selection description here as is picked by the program.( H3HPCDEL00110096, H3HPCDEL00110063)
To avoid this, we need to go to SDP94 and after going to selection window, we need to save the selections as shown in the following screenshots.
Select the selection id one by one.
Click on save selection
Click on save.
Do the same for all ids created by the program.
Now if we try to calculate the PF using the program, it is seen to work
So what needs to be done is that we need to avoid going to SDP94 in order to save the selections after the ids are created by the program.
How the Program works
Se38
Program zrsnorms_ppf
Execute.
Give file path of excel sheet.
Execute.
This will create the selection id by taking areabasepackRS as name of id.
The new selection ids can be seen by going to /sapapo/sdp94
And clicking on selection profile.
Now the selection has to be saved. For that, follow the following procedure.
Click on selection window.
Click on load selection.
Select the ids.
Select and then press save.
Do the same for every id.
Only then can proportional factor be calculated.
Now go to program and select Calc_ppf, with filepath to excel sheet as the sel_ids will be pulled from the excel.
When executed,
BDC is called to input data to transaction /sapapo/mc8v to calculate ppf.
Now go to sdp94 and load the selection
Click on load data.
And make sure, data view is TDP_VIEW_PROP as shown
PPF will be shown for the period chosen in the excel sheet.
Now to delete the selection ids.
Go to the program and give file path of the excel sheet and execute.
The selection profiles will be deleted as shown.
But PPF data will be stored in the database inspite of deleting the selection profiles. And ppf can be shown by selecting the basepack and the sales area.
Click load data.
Business scenario - Consider a factory having 5 different customers (which is known as Customer_rs). We need to supply stock to each of them based on their past consumption. So to forecast this, we calculate a factor known as proportional factor based on the data we have for previous months.
So to calculate the PF for a period, we need to create a profile in /sapapo/sdp94
How it is done in standard transaction /SAPAPO/SDP94
Important pushbuttons and their functions
Click on selection window.
Give the selections
Click on save selection
A break-point has been set in the standard program to show what all parameters are being passed to the standard function module /SAPAPO/MCPSH_SELECTION_SAVE used to save the selection
Now we will have to give the selection description
Now the profile can be seen by going to SDP94 and clicking on selection profile button.
Now to calculate PF, go to transaction /sapapo/mv8v
Click on execute and give following inputs
This will forecast the PF for the period 01.09.2007 to 21.02.2007 based on data from 21.04.2007 to 20.05.2007
Click on other settings
Here we will have to give the selection id that was saved in SDP94.
Click on execute.
All this process has to be automated and a program was created to do this.
A description of how the program is given below.
Program zrsnorms_ppf
Execute.
Give file path of excel sheet.
Execute.
This will create the selection id by taking areabasepackRS as name of id.
This is the excel sheet that is used to load data into /sapapo/mc8v to calculate the PF.
Upon executing, the ids have been created
The new selection ids can be seen by going to /sapapo/sdp94
And clicking on selection profile.
Parameters passed to standard function module in order to save the selection id.
Now if we try to calculate PF using the program, the following happens
When executed,
BDC is called to input data to transaction /sapapo/mc8v to calculate ppf.
An error screen is generated with the message There are no plannable characteristic combinations.
We are passing the same parameters that were passed by the SDP94 transaction to the standard function module for saving the selection ids. This is shown in the below screenshots.
In spite of this we are getting the error.
When IV_POPUP_SEL_DESCRIPTION is passed, a popup will be displayed where the selection description will have to be entered. I am passing the same selection description here as is picked by the program.( H3HPCDEL00110096, H3HPCDEL00110063)
To avoid this, we need to go to SDP94 and after going to selection window, we need to save the selections as shown in the following screenshots.
Select the selection id one by one.
Click on save selection
Click on save.
Do the same for all ids created by the program.
Now if we try to calculate the PF using the program, it is seen to work
So what needs to be done is that we need to avoid going to SDP94 in order to save the selections after the ids are created by the program.
How the Program works
Se38
Program zrsnorms_ppf
Execute.
Give file path of excel sheet.
Execute.
This will create the selection id by taking areabasepackRS as name of id.
The new selection ids can be seen by going to /sapapo/sdp94
And clicking on selection profile.
Now the selection has to be saved. For that, follow the following procedure.
Click on selection window.
Click on load selection.
Select the ids.
Select and then press save.
Do the same for every id.
Only then can proportional factor be calculated.
Now go to program and select Calc_ppf, with filepath to excel sheet as the sel_ids will be pulled from the excel.
When executed,
BDC is called to input data to transaction /sapapo/mc8v to calculate ppf.
Now go to sdp94 and load the selection
Click on load data.
And make sure, data view is TDP_VIEW_PROP as shown
PPF will be shown for the period chosen in the excel sheet.
Now to delete the selection ids.
Go to the program and give file path of the excel sheet and execute.
The selection profiles will be deleted as shown.
But PPF data will be stored in the database inspite of deleting the selection profiles. And ppf can be shown by selecting the basepack and the sales area.
Click load data.

Calculated Field is Disable while using PowerPivot to access multiple sheet column in a single pivot,

Hi,
I am trying to add a calculated field in my power pivot table to show the percentage on the basis of 2 columns, please let me know why this is not appearing and how can i fix it.
Any other way if i can add a calculated field in the pivot table will be very helpful.
Thanks
Aman

Thanks KR for the response,
Yes I loaded multiple tables in the data model and using PoewrPivot ,
i have a rating column, in that i have 0,1,2,3,4,5 rating numbers and we call it "Total expected occurrence",
a single person can get same rating multiple times, if a person is getting >=4 rating no. we call it "Occurrence >= 4". now i have to find out the total
count of "Occurrence >=4" for a particular person from "Total expected occurrence" column,
once will get the net "Occurrence >=4" for everyone, it should divide
"Occurrence >=4"/ "Total expected occurrence" to take out the percentage of rating 4 for a particular person
Best Wishes,
Aman verma

Javascript - Working with Dates, Selection Boxes & Pro-Rated Amounts to Calculate Costs

Hi, I'm looking for some help. I'm new to Javascript and working off my limited knowledge. Below are three (3) items I need help figuring out.
---JavaScript 1: Today---
I have a Document Level Javascript that gets the current date and automatically enters it into a field. Below is the example:
var f = this.getField("Today");f.value = util.printd("mm/dd/yyyy", new Date());
Problem: Each time I open the PDF, the date gets updated.
Need: I would like for the date to only be updated if the field is blank (empty).
---JavaScript 2: Registration Fee---
On this same form (application) I would like to calculate TWO costs. The first cost is mandatory registration cost, however the amount is prorated based on the month the application is filled out. Below is the pro-rated amounts based on the remaining months in the year:
Months Remaining     Fee
          12                       $15.00
          11                       $13.75
          10                       $12.50
          9                         $11.25
          8                         $10.00
          7                         $8.75
          6                         $7.50
          5                         $6.25
          4                         $5.00
          3                         $3.75
          2                         $2.50
          1                         $1.25
Note: The cost per month is $1.25. You are required to pay for the current month plus any remaining months.
So let's assume that you fill the application out in May 15th (05/18/2013). There are eight (8) months remaining in the year [May - Dec], so the pro-rated cost is $10.00 (See chart above).
For this calculation, I need to create a Document Level Javascript that would get the date from the field we used above called "Today" and calculate the "Registration Fee" based on the pro-rated amount. Then I would enter the cost into two fields (Dollars & Cents) as "10 00". (See below).
Form Example: $ [Text Field - Combo 2 characters] . [Text Field - Combo 2 characters] ---> "$ 10 . 00"
---JavaScript 3: Subscription Fee---
The next fee is an optional fee for a magazine subscription. On the form, the user will check a box (Named: "Subscription") if they want to subscribe to this magazine. This is similar to the example above in that the costs is based on a pro-rated amount. Below is the pro-rated amounts based on the remaining months in the year:
Months Remaining               Fee
          12                       $12.00
          11                       $11.00
          10                       $10.00
          9                         $9.00
          8                         $8.00
          7                         $7.00
          6                         $6.00
          5                         $5.00
          4                         $4.00
          3                         $3.00
          2                         $2.00
          1                         $0.00
Note: The cost per month is $1.00. Unlike the previous example, you are ONLY required to pay for the remaining months.
So let's assume that you fill the application out in May 15th (05/18/2013). There are eight (7) months remaining in the year [Jun - Dec], so the pro-rated cost is $7.00 (See chart above).
For this calculation, I need to create a Document Level Javascript: If the user checks a box (Named: "Subscription") requesting the subscription, then get the date from the field we used above called "Today" and calculate the "Subscription Fee" based on the pro-rated amount. I would enter the cost into two fields (Dollars & Cents) as "10 00". (Same as above).
Thanks,
Stephen

Two questions:
1. For "function calculateRegistrationFee", how do I format the return value into 2 parts in order to populate the different fields below. Let's use this example, see screen shot below:
2. For "function calculateSubscriptionFee", how do I format the return value into 2 parts (like question 1) & adjust for check box variable. If the user checks a box (named: "Subscription") requesting the subscription, then calculate cost. Else cost is $0.00. See screen shot:
Thanks,
Stephen

Confirmation on Calculation of

Hi
I would like to confirm for SPA B1 2007BB, in a marketing document, the calculation of Tax (shown on the bottom right) is based on the Document Total or is the summation of Tax Amount for each individual row?
For Example, there is 2 rows with the below amount:
Tax Code is 7% rated.
Row 1 - Unit Price 158761.8, Qty 1, Total (LC) 158761.8
Row 2 - Unit PRice 15876.18, Qty - 1, Total (LC) -15876.18
Thank you
Regards
Siew Yuen

HI,
Calculation of the Tax in the bottom right corner of the document is always based on the summation of the tax amounts in individual rows. Because if you define multiple rows with different tax codes then it cant calculate the total tax correctly by calculating it on the total doument total. That's why, the tax amount is calculated on summation of individual rows tax amount.
Regards.
ShriX.

Vendor Quality Rating

Hi QM Experts,
My client is calculating Vendor Quality Rating based on following Formula
QR = ( (Q1Q2X1Q3X2Q5X3Q6X4+Q7X5)/Q ) *100
QR = Quality Rating
Q1 = Quantity Accepted
Q2= Quantity Accepted with Deviation
Q3= Quantity Accepted with Rectification
Q4 = Quantity Rejected
Q5= Field Failure
Q6= In process rejection due to material defect from vendor
Q7= Customer Notification about Quality problem
Q = (Q1Q2Q3Q4Q5Q6Q7)
X1= 0.8 Factor
X2=0.75
X3=0.5
X4=0.65
X5=0.6
Please help me how to map the above in SAP
Regards,
Raj

Hi Kaushik
Thanks for your quick response,
I have already posted the formula, anyhow once again I will post it.
QR = ( (Q1Q2X1Q3X2Q5X3Q6X4+Q7X5)/Q ) *100
QR = Quality Rating
Q1 = Quantity Accepted
Q2= Quantity Accepted with Deviation
Q3= Quantity Accepted with Rectification
Q4 = Quantity Rejected
Q5= Field Failure
Q6= In process rejection due to material defect from vendor
Q7= Customer Notification about Quality problem
Q = (Q1Q2Q3Q4Q5Q6Q7)
X1= 0.8 Factor
X2=0.75
X3=0.5
X4=0.65
X5=0.6
Regards,
Raj

REGARDING VENDOR QUALITY RATING

Hi All
My client wants vendor quality rating
for this i maintend quality score in clint data maintened score procedure and assing it to inspection type
define the formula for quality rating in functional modul for Q score procedure
is this suficient or i m missing some thing pls tell me
regards
Sachin

HI
endor Evaluation for Purchasing
Define the weighting keys in SM30 - V_T147J.
Weighting keys 01 and 02 are defined in the standard system. You combine the following
weighting shares for the standard main criteria:
Main criterion     Key 01 Key 02
Price                   1      5
Quality                 1      5
Delivery                1      2
Gen. service/support    1      1
Ext. service provision 1      2
Define the criteria in SM30 - V_T147G - Double click on the line items
In this step, you define the criteria by which the system computes scores for vendors and
specify whether the scores for the subcriteria are computed manually, semi-automatically, or
automatically.
You can also store your own methods of computation for the scores for subcriteria in the
form of user exits. The enhancement MM06L001 is available for this purpose.
Define the scope of list in SM30 - V_T147M - Double click on the line items
Define Purchasing Organization data for vendor evaluations in transaction OMGL.
An example :-
How the system calculates the score for the automatic subcriteria
"On-Time Delivery Performance"?
The system uses the statistics-relevant delivery date in the purchase order
(Items -> Delivery Schedule) and the goods receipt date to calculate date variances.
You use the statistics-relevant delivery date, for example, if you know that the vendor
will not deliver the material as scheduled on September 15 but on September 30. Enter the
delivery date as September 30, but enter the statistics-relevant delivery date as
September 15.
In calculating the score for on-time delivery performance, the system will then not use
the actual delivery date, but the statistics-relevant delivery date. This has a negative
effect on the score for this goods receipt.
However, materials planning and control uses the realistic delivery date (September 30)
which the vendor will actually adhere to.
The system considers only goods receipts against purchase orders and scheduling agreements
into stores and the release of GR blocked stock into stores. In the standard system, these
are the movement types 101 and 105.
Minimum Delivery Percentage - OMGL in the On-time delivery section
If you do not want a vendor to receive a very good score if he delivered the goods on time,
but did not deliver the required quantity, you can maintain a minimum delivery percentage
in Customizing.
Assume you set the Min. del. perc. parameter to 60% and the vendor delivers the goods on
time, but only 55% of the ordered quantity. Although the goods receipt is punctual, it is
not included in the calculation of the vendoru2019s score for on-time delivery performance. So
that the non-scoring of the on-time delivery performance criterion in this case does not
bring an unfair advantage in comparison with a poor score, the vendor is awarded a low score
for quantity reliability. On-time delivery performance is thus always to be seen in
conjunction with quantity reliability.
Standardizing Delivery Date Variance - OMGL in the On-time delivery section
To rate delivery date variances in days, maintain the Std.del.time var. parameter.
If you assign a lower standard value, this means that relatively low date variances produce
high percentage variances. If you set a higher standard value, this results in a relatively
low percentage variance:
The Std.del.time var. parameter has the value 20. The goods receipt took place on Nov. 27;
the statistical delivery date was Nov. 15. There is thus a difference of 12 days.
The system calculates the percentage variance as follows:
12 / 20 x 100 = 60
If the Std.del.time var. parameter had the value 60, the variance would be 20%
(12 / 60 x 100 = 20).
If you do not maintain this parameter, the system calculates the delivery time variance via
the firm zone in the case of scheduling agreements, and via the order date and the
statistics-relevant delivery date in the case of purchase orders.
With regrds
Yashodhan

Rating Calculation

Similar Messages

Maybe you are looking for