ColorWarePC factor.

what i'm wndering, is if i color my iphone using Colorwarepc (colorwarepc.com) apple will still help me with questions, software problems, etc.

maxim,
Please refer below document.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90b58cfe-6ae8-2b10-7b87-e83ebbc5be45?quicklink=index&overridelayout=true
Does it work if you are using *Factor = Using/Total ?
It might be user script is missing somthing so please check document and follow that guide.
I hope it will help you.
James Lim

Similar Messages

ISE 1.2 Guest Portal Profiling Certainty Factor not Increase

Hi I have configure ISE 1.2 Guest Portal and check for profiling which device login but I found that endpoint profile not match after user succesful authenticate
Profiling Configure and Endpoint Detail in attachment below

Hi salodh
as you can see in attach file all profiling are configure correctly and condition should be match according to User-Agent Contain Andriod (profile3.png) and Certainty Factor must increase (profile2.png) in this case but Total Certainty Factor still 0 in endpoint profile (profile1.png)

Factoring based on Gross pay

Dear Experts,
We have a bit complex scenario regarding mid month joining and separation proration. Its like, Gross salary is reduced by the total absence amount.
Formula is like: {Prorated Housing (Housing/30days x no.of days no worked)/Hourly Rate (Basic/195) + Total no. of hours not worked}/195 * Gross salary.
I have been able to segregate this proration calculation of basic and housing by using factor 1 and 3 respectively and both individually has been reduced as per the formula given above i.e. Prorated Housing (Housing/30days x no.of days no worked), Hourly Rate (Basic/195 x number of hours worked).
Now issue is how we can achieve this reduction on Gross salary scenario with our reduction factors, which is basically assigned wagetype wise in Pr.class 10.

Hi Promod,
Yes i can try by reducing directly /101, but issue is here, how we can achieve the reduction formula like
{Prorated Housing (Housing/30days x no.of days not worked)/Hourly Rate (Basic/195) + Total no. of hours not worked}/195 * Gross salary.
Prorated Housing (Housing/30days x no.of days not worked)/Hourly Rate (Basic/195)= This is basically calculating absence hours for housing + basic which is again being added with Actual absence hours.
Please help
Regards
Tandrima

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.

PF not Factorizing Correctly

Hi,
I am facing problem in PF Calculations.
For Mid month joined employees, PF was not calculating properly. So I had applied SAP Note 1116277 - Inconsistency in case of mid-month joining and separation.
Still there is problem.
Employee Having Basic-3300
Date of Joining -17.01.2012
/111 EPF Basis -1,596.77
Output should be 12% of 1596.77= 191.6
But system is factorizing the Basic again and generating
/3FL PF Basis fo0101 -773.00
and then its generating PF as 12% of this
/3F1 Ee PF contr0101 -93.00
Thus its Factorizing it twice for Mid Month Joined employees.
Please suggest how to solve it as the calculations are happening in INEPF.
Thankyou in Advance.
Regards,
Saureb

Please check the contribution rates in V_T7INF3
Raghu

Sharepoint 2010 permission The following factors also affect the level of access for

hello,
In my development server ,suddently from no where all users ,even full control group users
cannot able to add or edit any list or any content.
The following factors also affect the level of access for user1(domain\user1)
Deny
Manage Permissions
Create and change permission levels on the Web site and assign permissions to users and groups.
Deny
Create Subsites
Create subsites such as team sites, Meeting Workspace sites, and Document Workspace sites.
Deny
Manage Web Site
Grants the ability to perform all administration tasks for the Web site as well as manage content.
Deny
Add and Customize Pages
Add, change, or delete HTML pages or Web Part Pages, and edit the Web site using a Microsoft SharePoint Foundation-compatible editor.
Deny
Manage Lists
Create and delete lists, add or remove columns in a list, and add or remove public views of a list.
Deny
Apply Themes and Borders
Apply a theme or borders to the entire Web site.
Deny
Apply Style Sheets
Apply a style sheet (.CSS file) to the Web site.
Deny
Override Check Out
Discard or check in a document which is checked out to another user.
Deny
Manage Personal Views
Create, change, and delete personal views of lists.
Deny
Add/Remove Personal Web Parts
Add or remove personal Web Parts on a Web Part Page.
Deny
Update Personal Web Parts
Update Web Parts to display personalized information.
Deny
Add Items
Add items to lists and add documents to document libraries.
Deny
Edit Items
Edit items in lists, edit documents in document libraries, and customize Web Part Pages in document libraries.
Deny
Delete Items
Delete items from a list and documents from a document library.
Deny
Create Groups
Create a group of users that can be used anywhere within the site collection.
Deny
Use Self-Service Site Creation
Create a Web site using Self-Service Site Creation.
Deny
Approve Items
Approve a minor version of a list item or document.
Deny
Delete Versions
Delete past versions of a list item or document.
Deny
Create Alerts
Create alerts.
Deny
Manage Alerts
Manage alerts for all users of the Web site.
Deny
Edit Personal User Information
Allows a user to change his or her own user information, such as adding a picture.
For all the users this happened ,How i need to fix this issue
please help.
thanks

Take a look at the user policy settings for the web application. I suspect someone has added a User Policy that covers the user which denies all these permissions. The User Policy at the web app level is the only place where you can deny permissions.
But that setting applies to every site collection in the web application and takes precedence over every other setting.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Scrap factors and Production order

Hi all
I am using scrap factors in the Material Master which is used as a component in the production order. When I create a production order the component requirement qty is inflated by the scrap factor. Then I do a CO15 and put in the actual qty of component used. Is there a standard report PP or CO where it shows the planned required qty( as in BOM with no scrap), planned required qty ( with scrap) and the actual qty?
thanks a lot

Hi,
Not sure if you can get all 3 in a std report. But in COOIS, when you run the report with List option as component you can get the requirement qty & withdrawn qty.
To my knowledge you would have to go for a Z report.
Regards,
Vivek

Output/Input Scale Factor

I have a high resolution stage used for a scanning application. I'm using a pci-7344 to control the stage. The system is marginally stable with kp=1 and various values set for ki and kd. I have found several posts with the same issue:
http://forums.ni.com/t5/Motion-Control-and-Motor-Drives/tuning-servo-system/m-p/139507/highlight/tru...
http://forums.ni.com/t5/Motion-Control-and-Motor-Drives/Is-there-any-way-to-drcease-the-open-loop-ga...
http://forums.ni.com/t5/Motion-Control-and-Motor-Drives/MAX-Reducing-Encoder-Resolution/m-p/1030934/...
http://forums.ni.com/t5/Motion-Control-and-Motor-Drives/7344-PID-proportional-gain-1-but-actuator-st...
It is apparent that the gain needs to be set below one and the only current solutions (decrease encoder resolution or decreasing the output limits) are both unacceptable. Encoders aren't free (and in my case extremely difficult to replace) and I want my stage to run as fast as possible.
Many other modern controllers allow the input and/or the output of the PID loop to be scaled (even if it's only by factors of two for non floating point dsp's) for exactly this reason. This allows one to arbitrarily place the optimal kp value within the allowable integer range (i.e. 1<kp<32768). Is there a way to do this on ni controllers? If not is there a propper place to request features?

Unfortunately you can't scale the input or output of the PID loop. I am attaching two links below that discuss how to tune the servo motor and also where you can make product suggestions. I'm sorry I don't have better news for you, but please post your ideas to the idea exchange below so our developers can look at them. Thank you!
A Simple Method for Servo Motor Tuning
NI Idea Exchange
Mychal F
Applications Engineer
National Instruments

What factors should be taken into account for Custom Exceptions

hi,
I just want to know that What factors should be taken into account for making Custom Exceptions.
any examples will appreciated.
regards,
vjoy

Do you want this to be checked exception? If so extend it from Exception or subclass of it. If it is unchecked exception (not forced by javac to be caught by callers), then extend it from RuntimeException or subclass of it. Exceptions are serializable objects and so have serialVersionID field. Also, to allow for exception chaining, define a constructor that accepts "cause" (http://java.sun.com/j2se/1.4.2/docs/guide/lang/chained-exceptions.html)

Multi-factor Authentication?

Multi-factor authentication will soon be mandatory for
several of my applications. I need to know if CF has any built-in
functionality, either stock or via custom tags, to handle any of
the common multi-factor tools. How are other people handling this?
:-)

Huh, i'm sorry, I found the answer just after the questioning... :)
Known Issues:
* Windows Authentication for Terminal Services is still not supported for
Windows Server 2012 R2From:https://pfweb.phonefactor.net/install/6.3.0.17465/release_notes.txt
www.sccmfaq.ch

Apple ID - Two Factor Authentication (and why I stopped using it)

The Apple devices I use every day consist of the following:
2009 MacBook Pro 17" (home)
iPhone 6 (home)
2012 MacBook Pro Retina (work)
My home devices are all logged in using my Apple ID as usual, and my work laptop uses a Apple ID specific to work, but with my personal Apple ID logged in for iMessage and FaceTime (pretty standard, I presume, for people with full-time work laptops they can bring home, etc.). Now, since I have multiple devices which are constantly syncing everything back and forth, whether it be something as simple as my contacts or as delicate and near and dear to my heart as my photo collection, I felt that maybe I should use two factor authentication for my home Apple ID, just to be on the safe side. I recognize that the two factor authentication only protects iMessage and FaceTime currently, but I implemented it with hopes that someday they will incorporate everything about iCloud and other services synced between Apple devices that you would assume should be covered by a two factor authentication update/overhaul.
I liked this idea very much, as I use two factor for almost everything I can, but things started to fall apart one day when I had to switch to a temporary work laptop and decided to log in to iMessage with a new app specific password, as you would need to on a new device (unless you wrote down the original iMessage password, which is a terrible thing to do). When I went to create my new iMessage password for work laptop B, I decided to revoke work laptop A's iMessage password while it went in for repairs. This wasn't so bad until something seemed funny about my phone, as it was asking for me to log into iMessage again. Now, I had created a separate password for work laptop A's iMessage when I first logged in a while back, as well as a separate password for the temporary work laptop B so it didn't interfere with my other generated passwords. Apparently this didn't matter.
I continued and created a new app password for my phone, but when I got home, wouldn't you know it, I had to log into iMessage on my home laptop again as well. I had to create a new password for that, which seemed to work for a while, but then I was prompted to enter my iMessage password on my phone again once I revoked my home laptop's iMessage password. Not following? No, me either. It seemed to me that creating separate app specific passwords for me to use across my devices didn't stay as separate as I thought they should, but instead they somehow seemed to be dependent on one another. Since I had a frustrating time trying to activate iMessage again on my iPhone and laptops on multiple occasions while this was happening, I decided to disable two factor authentication altogether.
I suppose I should ask a question here, so here goes: has anyone else encountered this horrific two factor authentication/app specific password management issue for their own account? Have you been able to resolve it, and if so, any helpful suggestions? Thanks!

I had also thought that initially, but after turning it on, I went to sign into iMessage with my Apple ID and regular Apple ID password, but it prompted me to create an app specific password to sign in since I had two factor authentication on, as it wouldn't let me use my regular Apple ID password to log in (which I could use to log in for everything else but iMessage and FaceTime). It was nice since I was prompted to provide a code sent to an Apple device of my choosing when signing into the Apple ID management site or iCloud.com, but forcing me to create app specific passwords for iMessage and FaceTime is kind of ridiculous and frustrating. Maybe there's a way to have two factor authentication without the need for app specific passwords? Or if not, then perhaps that would be a great option to present users when turning that feature on.

OBIEE 11g "WITH SAWITH0 AS" subquery factoring clause in the generated sql

I've observed that the OBIEE 11g generates in the query log physical query using the WITH (sub-query factoring) clause to make the generated sql elegantly readable. This is great! Thanks for the developers. However I have some questions about this.
__Background__
Oracle Database' default behaviour is that if you have only one sub-query in the WITH section, it executes it as an in-line view and does not materialize it before the main sql is executed. If you have more than one, by default the database engine materializes all of them in the order of the definition. In some cases this can completely blow up the SGA and make the query never ending. To divert this behaviour you can apply two hints that work both in inline views and in sub-queries as well: /*+ MATERIALIZE */ and /*+ INLINE*/, however Analytics 11g does not seem to have hint capabilities at the logical table level, only at physical table level.
If we go with the current defaults, developers not aware of this feature can bump into serious performance issues for the sake of some syntax candy at the generated sql level, I'm afraid.
__Questions__
* Is it possible to turn the Analytics server not to use WITH but use inline views instead?
* Is there any way to sneak in some hints that would put the /*+ INLINE */ hint to the appropriate place in the generated sub-queries if needed
* Does the Oracle Database have any initialization parameter that can influence this sub-query factoring behavior and divert from the default?

The WITH statement is not added to make the query more elegant, it's added for performance reasons. If your queries take long to run then you may have a design issue. In a typical DWH DB SGA needs to be seriously increased since the queries ran are much larger and complex than on an OLTP DB. In any case you can disable the WITH statement in the Admin Tool by double clicking on your database object on the physical layer and going to the Features tab. The feature is called WITH_CLAUSE_SUPPORTED.

How to manage variable conversion factor in UOM to order unit

Hi,
We have a material whose base unit is PC unit price is 8 Euro / PC
Order unit is Box now we do not have a standard conversion factor.
Means sometimes vendor send 8 pc/ Box ,10 pc /Box and 12 pc /Box
so when we create Material master and enter order unit as Box in purchasing view system ask for conversion rate
if we do not enter any the value in PC field its taking 1 Box =1 PC as default.
Example: Now while creating PO say we order for 10 box.(at this point we do not know exact conversion rate)
and in the conditions we maintain price against PC .system calculate.
Now when we receive the material then we actually know how much QTy we receive in SKU (PC) but that field is blur (no input) in 101 mvt type.
One more thing In MIGO we can enter the Qty in PO Price Unit say we enter 80 PC
system only creates stock value posting (80 * 8 =640 Euro ) but the stock qty in MMBE is still 10 piece ( from 1:1 conversion with box)
Please suggest how we can handle this variable conversion rate.
So that we can enter correct Qty in the time of GR ( MIGO ).
Thanks in advance.

Hi,
Thanks for the valuable Input.
For our material base unit is PC order unit is Box.
Say we main a conversion factor 10 PC =1 Box ( a default value) in MM01
And we order 10 Box. but when we receive we found that vendor send 12 pc per Box so total 120 pc
[ Po price unit is in PC in condition details]
Now in MIGO we cannot modify that Qty ( from 100 to 120 in PC)
SO you are suggesting here we receive 12 box in MIGO. so that actual qty in PC is correct..
Thanks again

How to find factors of number?

I have a prime number program set up that finds prime numbers and to find two prime numbers beyond the number inputed. I also want to find the factors of the number inputed. I am brain freezed on finding the factors. For example I want to display 20 = 2 x 2 x 5, and for prime numbers I want to display 7 = 7. The factors will be displayed in label.
I already have the first factor, but how do you continue to add factors to the string, that is going to be put into the label? I think it is a for loop in a for loop but not sure how to work it out??????
here is my factor method
private void factor(long value)   //bring in number from user
          long firstVal;
          String output = value + " = ";
               for (long a = 2; a < 12; a += 1)
                    if (value % a == 0)
                         firstVal = value / a;
                         output = output + a + "x";
     }//factor-thanks

Well that was to illustrate the point so that the person asking question can take correct direction.
But you don't want to use your brain at all right.
Then here is the code
import java.math.*;
import java.util.*;
public class DirectSearchFactorization {
private long max = 0;
private Vector trialDivisors = null;
private long nDivisions = 0;
// Constructor
public DirectSearchFactorization (long max) {
    this.max = max;
    // The trial divisors include all primes <= sqrt (n).
    // The trial divisors must also contain at least one
    // value such that d(k) >= sqrt (n).
    int sqrtn = (int) Math.ceil (Math.sqrt (max));
    trialDivisors = SieveOfEratosthenes.getPrimes (sqrtn);
    trialDivisors.addElement (new Long (sqrtn));
public long getNumDivisions () {
    return nDivisions;
// Get prime factors
public Vector getPrimeFactors (long n) {
    if (n > max) {
      String s = n + " > " + max;
      throw new IllegalArgumentException (s);
    Vector factors = new Vector ();
    nDivisions = 0;
    // Step 1
    int k = 0;
    long divisor;
    Long divisorObj;
    long quotient;
    long remainder;
    // Step 2
    while (n > 1) {
      // Step 3
      divisorObj = (Long) trialDivisors.elementAt (k);
      divisor = divisorObj.longValue ();
      quotient = (long) Math.floor (n / divisor);
      remainder = n % divisor;
      nDivisions++;
      // Step 4
      if (remainder == 0) {
        // Step 5
        factors.addElement (new Long (divisor));
        n = quotient;
      else {
        // Step 6
        if (quotient > divisor) {
          k++;
        else {
          // Step 7
          factors.addElement (new Long (n));
          break;
    return factors;
import java.util.*;
public abstract class SieveOfEratosthenes {
public static Vector getPrimes (int upTo) {
    int size = upTo + 1;
    boolean [] flags = new boolean[size];
    Vector primes = new Vector ();
    double limit = Math.sqrt (size);
    // Set flags
    for (int i = 2; i < size; i++) {
      flags[i] = true;
    // Cross out multiples of 2
    int j = 2;
    for (int i = j + j; i < size; i = i + j) {
      flags[i] = false;
    // Cross out multiples of odd numbers
    for (j = 3; j <= limit; j = j + 2) {
      if (flags[j]) {
        for (int i = j + j; i < size; i = i + j) {
          flags[i] = false;
    // Build list of primes from what is left
    for (int i = 2; i < size; i++) {
      if (flags) {
primes.addElement (new Long (i));
return primes;
User Interface
import java.awt.*;
import java.awt.event.*;
import java.applet.Applet;
import java.util.*;
// The applet tests the DirectSearchFactorization class
public class FactorizationApplet extends Applet {
private Button factorButton = null;
private Label numberLabel = null;
private TextField numberTextField = null;
private Label numDivisionsLabel = null;
private TextField numDivisionsTextField = null;
private Label factorsLabel = null;
private TextField factorsTextField = null;
private DirectSearchFactorization dsf = null;
private static final long MAX = 500000;
// Override Applet methods
public void init () {
Panel panel = new Panel ();
panel.setLayout (new GridLayout (3, 2));
numberLabel = new Label ("Number to Factor <= " + Long.toString (MAX));
panel.add (numberLabel);
numberTextField = new TextField ("387921", 25);
panel.add (numberTextField);
factorsLabel = new Label ("Prime Factors");
panel.add (factorsLabel);
factorsTextField = new TextField ("", 25);
factorsTextField.setEditable (false);
panel.add (factorsTextField);
numDivisionsLabel = new Label ("Number of Divisions");
panel.add (numDivisionsLabel);
numDivisionsTextField = new TextField ("", 25);
numDivisionsTextField.setEditable (false);
panel.add (numDivisionsTextField);
add (panel);
factorButton = new Button ("Factor");
add (factorButton);
dsf = new DirectSearchFactorization (MAX);
public void paint (Graphics g) {
public boolean action (Event e, Object arg) {
if (e.target == factorButton) {
factor ();
repaint ();
return true;
else {
return false;
private void factor () {
long n = 0;
factorsTextField.setText ("");
try {
n = Long.parseLong (numberTextField.getText ());
if (n <= MAX) {
Vector factors = dsf.getPrimeFactors (n);
factorsTextField.setText (factors.toString ());
numDivisionsTextField.setText (Long.toString (dsf.getNumDivisions ()));
} catch (Exception e) {
System.out.println (e.toString ());
// Run as application
public static void main (String[] args) {
// Create frame to house the applet
Frame frame = new Frame ("Factorization into Primes");
// Create an instance of the applet
FactorizationApplet app = new FactorizationApplet ();
// Add it to the center of the frame
frame.add (app, BorderLayout.CENTER);
frame.setSize (450, 150);
// Listen for window closing event
frame.addWindowListener (new WindowAdapter () {
public void windowClosing (WindowEvent e) {
System.exit (0);
// Call the applet methods
app.init ();
app.start ();
// Set the frame visible
frame.setVisible (true);

Two Factor Authentication on Windows Server 2008 R2

We have a small 2008 R2 Active Directory environment with 2 domain controllers and 13 member servers. We have no additional features such as an RDP gateway or Federation Services - just a plain AD setup. We now have a requirement from our client to have
a two factor authentication solution for each time we logon to any server, either using RDP or locally. We only have 4 admins that ever logon to these servers - we do not have any "regular" users.
Is there anything out there that would work in this environment without having to modify our AD (at least nothing major)?
Thanks

Hi,
You may consider smart card:
Smart Card Overview
http://technet.microsoft.com/en-us/library/hh831433.aspx
Understanding Requirements for Connecting to a Remote Desktop Gateway Server
http://technet.microsoft.com/en-us/library/cc770519.aspx
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

ColorWarePC factor.

Similar Messages

Maybe you are looking for