Adjustment required due to modification.

Hi,
We are using Travel Management ERP6.0. SAP provides a screen 9999 (User Data screen) within the dialog program SAPMP56T for customers to store or display custom fields, but this is still considered a modification. We did utilize heavily on this User Data screen (i.e. screen 9999) and include significant amount of custom processing logic (PBO, PAI) and UI onto the screen.
What is the extent to readjust the screen (including logic, UI etc) upon subsequent upgrade or patch update ? Do I have to re-do these changes every time since it may be over-written ? Anyone with similar experience ? Thank you.
Regards
Kir Chern

Since it is a modification, I would say yes, you'll have to do it after every upgrade.
Do you use the Easy Enhancement Workbench (EEWB) for this, or is there a Badi / Screen exit you should have used instead to overcome the problem of a modification??

Similar Messages

  • Activate "Value Adjustment Required Indicator" Field in FMX1

    Hi Expert
    Transaction Code FMX1/FMX2/FMX3 (Earmarked Fund Maintenance), in More Button of earmarked fund line item, there is no Indicator Field for "Value Adjustment Required" marking.
    This is the new SAP client setup. I have config field selection string and assigned. I set Opt. Entry for "_Indicator: Amount Change Only with Value Adjustment Document_" but in Earmarked Fund Maintenenace still not be appeared.
    I would like to use earmarekd fund with Value Adjustment function (FMXPM1 - FMXPM3) so I need to mark the Value Adjustment Required field in FMX1/FMX2.
    Could you please advice, how to show Value Adjustment Required indicator in Earmarked Fund Maintenenace Transaction?
    Rgds
    Ton

    Hi,
    Did you switch "IMG - Public Sector Management - Funds Management Government - Funds Management-Specific Postings - Earmarked Funds and Funds Transfers - Maintain Global Settings" indicator for value adjustment?
    Regards,
    Eli

  • Due to MODIF ID, SELECT query in START-OF-SELECTION not getting triggered

    Dear SAP Gurus,
    I'm stuck with this program, where, my program is not being executed, as in, my SELECT query in my event START-OF-SELECTION is not getting triggered. Since i hav used MODIF ID, for SELECT-OPTIONS, even after putting the entries in select-options...................when i click on the execute button, or press F8, the program still goes into the AT SELECTION-SCREEN OUTPUT event..........but i want it to goto START-OF-SELECTION event where my SELECT query is........what should i do??????????????
    Please find the notepad file having the code, n exucse me for any selection-texts absence.
    Need help from u in this issue.
    Thanks in advance.
    REPORT  ZPPR_CONVSTAT NO STANDARD PAGE HEADING.
    INCLUDE ZPPR_CONVSTAT_TOP.               " data declaration
    INCLUDE ZPPR_CONVSTAT_SEL_CRITERIA.      " selection criteria
    INCLUDE ZPPR_CONVSTAT_PBO.               " event at selection-screen output
    INCLUDE ZPPR_CONVSTAT_START_SELECTION.   " event start-of-selection
    INCLUDE ZPPR_CONVSTAT_F_START_OF_SEL.
    *&  Include           ZPPR_CONVSTAT_TOP
    TABLES  : VBUK,
              VBUP,
              VBAK,
              VBAP,
              VBEP,
              VBPA,
              TVAK,
              EKUB,
              LIKP,
              LIPS,
              MARA,
              MAKT,
              MARC,
              PLAF,
              AUFK,
              AFKO,
              AFPO,
              AFVC,
              AFVV,
              CRHD,
              PBIM,
              KNA1,
              T134,
              IOHEADER,
              IOITEM.
    TYPE-POOLS  : slis.
    TYPES : BEGIN OF ty_final,
            werks   TYPE vbap-werks,  "Plant
            auart   TYPE vbak-auart,  "Sales Order Doc. type
            erdat   TYPE vbak-erdat,  "Sales Order Creation date
            vbeln   TYPE vbak-vbeln,  "Sales Order No.
            posnr   TYPE vbap-posnr,  "Sales Order Item No.
            aedat   TYPE vbak-aedat,  "Sales Order Change Date
            kwmeng  TYPE vbap-kwmeng, "Sales Order qty.
            vdatu   TYPE vbak-vdatu,  "Requested Delivery Date
            lfimg   TYPE lips-lfimg,  "Sales Order Delivered Qty.
            matnr   TYPE vbap-matnr,  "Material ID
            arktx   TYPE vbap-arktx,  "Material Description
            strgr   TYPE marc-strgr,  "Planning Strategy
            vrkme   TYPE vbap-vrkme,  "UOM
            plnum   TYPE plaf-plnum,  "Plan Order No.
            gsmng   TYPE plaf-gsmng,  "Plan Order Qty.
            auffx   TYPE plaf-auffx,  "Plan Order Firming Indicator u2013 Qty.
            stlfx   TYPE plaf-stlfx,  "Plan Order Firming Indicator - Component
            erdat2  TYPE aufk-erdat,  "Production Order Creation Date
            aufnr   TYPE aufk-aufnr,  "Production Order No.
            prdqty  TYPE afko-gamng,  "Production Order qty.
            pckqty  TYPE lips-lfimg,  "Packed Delivered Qty.
            psamg   TYPE afpo-psamg,  "Allotted scrap
            igmng   TYPE afko-igmng,  "Confirmed Yield Qty.
            iasmg   TYPE afko-iasmg,  "Confirmed Scrap Qty
            iamng   TYPE afpo-iamng,  "Expected Yield
            wemng   TYPE afpo-wemng,  "Delivered Qty.
            altscrp TYPE c LENGTH 6,  "Allotted Scrap %
            actscrp TYPE c LENGTH 6,  "Actual Scrap %
            umrez   TYPE afvv-umrez,  "Ups (from Prd. ORD)
            ups     TYPE clobjdat-ausp1,  "Ups (from Material Master)
            crtnstl TYPE clobjdat-ausp1,  "Carton Style
            ppopr   TYPE clobjdat-ausp1,  "Pre-Printing Operation
            brdtyp  TYPE clobjdat-ausp1,  "Board Type
            lsdim1  TYPE clobjdat-ausp1,  "Layout Size u2013 Dim 1
            lsdim2  TYPE clobjdat-ausp1,  "Layout Size u2013 Dim 2
            lsgsm   TYPE clobjdat-ausp1,  "GSM
            inktyp  TYPE clobjdat-ausp1,  "Ink Type
            foiltyp TYPE clobjdat-ausp1,  "Foiling
            wintyp  TYPE clobjdat-ausp1,  "Window Type
            lamin   TYPE clobjdat-ausp1,  "Lamination
            fsvrnsh TYPE clobjdat-ausp1,  "Front Side Varnish
            bsvrnsh TYPE clobjdat-ausp1,  "Back Side Varnish
            emboss  TYPE clobjdat-ausp1,  "Embossing
            punch   TYPE clobjdat-ausp1,  "Punching
            paste   TYPE clobjdat-ausp1,  "Pasting
            oprno   TYPE afvc-vornr,      "Operation No.
            wrkcntr TYPE crhd-arbpl,      "Work Centre
            oprtxt  TYPE afvc-ltxa1,      "Operation Text
            oprqty  TYPE afvv-mgvrg,      "Operation qty.
            yield   TYPE afvv-lmnga,      "Yield
            scrap   TYPE afvv-xmnga,      "Scrap
            jobtyp  TYPE vbak-augru,      "Job Type
            prordst TYPE bsvx-sttxt,      "Production Order Status
            solinst TYPE vbup-lfsta,      "Sales Order Line Item Status
            sldprty TYPE kna1-name1,      "Sold to Party Name
            shpprty TYPE kna1-name1,      "Ship to Party Name
            shpcity TYPE kna1-ort01,      "Ship to party - City
            END OF  ty_final.
    TYPES : BEGIN OF ty_vbak,
            auart   TYPE vbak-auart,
            erdat   TYPE vbak-erdat,  "Doc creation date
            vbeln   TYPE vbak-vbeln,
            aedat   TYPE vbak-aedat,  "Doc change date
            vdatu   TYPE vbak-vdatu,  "Requested delivery date
            kunnr   TYPE vbak-kunnr,
            augru   TYPE vbak-augru,  "Job Type
            END OF ty_vbak.
    TYPES : BEGIN OF ty_vbap,
            vbeln   TYPE vbap-vbeln,
            posnr   TYPE vbap-posnr,
            werks   TYPE vbap-werks,
            matnr   TYPE vbap-matnr,
            arktx   TYPE vbap-arktx,
            kwmeng  TYPE vbap-kwmeng,
            vrkme   TYPE vbap-vrkme,
            END OF ty_vbap.
    TYPES : BEGIN OF ty_pbim,
            pbdnr TYPE pbim-pbdnr,  "Requirements Plan Number
            bdzei TYPE pbim-bdzei,  "Independent requirements pointer
            matnr TYPE pbim-matnr,
            werks TYPE pbim-werks,
            END OF ty_pbim.
    TYPES : BEGIN OF ty_pbhi,
            bdzei TYPE pbhi-bdzei,  "Independent requirements pointer
            pdatu TYPE pbhi-pdatu,  "Requirement date
            laeda TYPE pbhi-laeda,  "Date of Last Change
            END OF ty_pbhi.
    TYPES : BEGIN OF ty_ekko,
            ebeln TYPE ekko-ebeln,  "STO doc no
            bsart TYPE ekko-bsart,
            reswk TYPE ekko-reswk,  "Supplying plant
            aedat TYPE ekko-aedat,  "Doc creation date
            END OF ty_ekko.
    TYPES : BEGIN OF ty_ekpo,
            ebeln TYPE ekpo-ebeln,
            ebelp TYPE ekpo-ebelp,
            aedat TYPE ekpo-aedat,  "Doc change date
            menge TYPE ekpo-menge,
            meins TYPE ekpo-meins,
            matnr TYPE ekpo-matnr,
            txz01 TYPE ekpo-txz01,
            END OF ty_ekpo.
    TYPES : BEGIN OF ty_eket,
            ebeln TYPE eket-ebeln,
            ebelp TYPE eket-ebelp,
            eindt TYPE eket-eindt,  "Requested delivery date
            END OF ty_eket.
    TYPES : BEGIN OF ty_lips,
            vbeln TYPE lips-vbeln,
            posnr TYPE lips-posnr,
            vgbel TYPE lips-vgbel,
            vgpos TYPE lips-vgpos,
            lfimg TYPE lips-lfimg,
            END OF ty_lips.
    TYPES : BEGIN OF ty_plaf,
            plnum TYPE plaf-plnum,
            matnr TYPE plaf-matnr,
            gsmng TYPE plaf-gsmng,
            auffx TYPE plaf-auffx,
            stlfx TYPE plaf-stlfx,
            kdauf TYPE plaf-kdauf,
            kdpos TYPE plaf-kdpos,
            pbdnr TYPE plaf-pbdnr,
            END OF ty_plaf.
    TYPES : BEGIN OF ty_aufk,
            aufnr TYPE aufk-aufnr,
            erdat TYPE aufk-erdat,
            objnr TYPE aufk-objnr,
            END OF ty_aufk.
    TYPES : BEGIN OF ty_afko,
            aufnr TYPE afko-aufnr,
            gamng TYPE afko-gamng,  "Total order quantity
            gasmg TYPE afko-gasmg,  "Total scrap quantity in the order
            igmng TYPE afko-igmng,  "Confirmed Yield Qty
            iasmg TYPE afko-iasmg,  "Confirmed Scrap Qty
            aufpl TYPE afko-aufpl,  "Routing number of operations in the order
            END OF ty_afko.
    TYPES : BEGIN OF ty_afpo,
            aufnr TYPE afpo-aufnr,
            plnum TYPE afpo-plnum,
            matnr TYPE afpo-matnr,
            pgmng TYPE afpo-pgmng,  "Plan Order Qty
            kdauf TYPE afpo-kdauf,
            kdpos TYPE afpo-kdpos,
            psamg TYPE afpo-psamg,  "Allotted scrap
            iamng TYPE afpo-iamng,  "Expected Yield Variance
            wemng TYPE afpo-wemng,  "Delivered Qty
            END OF ty_afpo.
    TYPES : BEGIN OF ty_afvc,
            vornr TYPE afvc-vornr,
            aufpl TYPE afvc-aufpl,  "Routing number of operations in the order
            aplzl TYPE afvc-aplzl,  "General counter for order
            arbid TYPE afvc-arbid,  "Object ID of the resource
            ltxa1 TYPE afvc-ltxa1,
            END OF ty_afvc.
    TYPES : BEGIN OF ty_afvv,
            aufpl TYPE afvv-aufpl,  "Routing number of operations in the order
            aplzl TYPE afvv-aplzl,  "General counter for order
            umrez TYPE afvv-umrez,
            mgvrg TYPE afvv-mgvrg,
            lmnga TYPE afvv-lmnga,
            xmnga TYPE afvv-xmnga,
            END OF ty_afvv.
    TYPES : BEGIN OF ty_mdvm,
            mdkey TYPE mdvm-mdkey,
            disst TYPE mdkp-disst,
            matnr TYPE mdkp-matnr,
            plwrk TYPE mdkp-plwrk,
            END OF ty_mdvm.
    DATA :  it_final  TYPE STANDARD TABLE OF ty_final,
            it_vbak   TYPE STANDARD TABLE OF ty_vbak,
            it_vbap   TYPE STANDARD TABLE OF ty_vbap,
            it_lips   TYPE STANDARD TABLE OF ty_lips,
            it_pbim   TYPE STANDARD TABLE OF ty_pbim,
            it_pbhi   TYPE STANDARD TABLE OF ty_pbhi,
            it_ekko   TYPE STANDARD TABLE OF ty_ekko,
            it_ekpo   TYPE STANDARD TABLE OF ty_ekpo,
            it_eket   TYPE STANDARD TABLE OF ty_eket,
            it_plaf   TYPE STANDARD TABLE OF ty_plaf,
            it_aufk   TYPE STANDARD TABLE OF ty_aufk,
            it_afko   TYPE STANDARD TABLE OF ty_afko,
            it_afpo   TYPE STANDARD TABLE OF ty_afpo,
            it_afvc   TYPE STANDARD TABLE OF ty_afvc,
            it_afvv   TYPE STANDARD TABLE OF ty_afvv,
            it_mdvm   TYPE STANDARD TABLE OF ty_mdvm.
    DATA :  wa_final  TYPE ty_final,
            wa_vbak   TYPE ty_vbak,
            wa_vbap   TYPE ty_vbap,
            wa_lips   TYPE ty_lips,
            wa_pbim   TYPE ty_pbim,
            wa_pbhi   TYPE ty_pbhi,
            wa_ekko   TYPE ty_ekko,
            wa_ekpo   TYPE ty_ekpo,
            wa_eket   TYPE ty_eket,
            wa_plaf   TYPE ty_plaf,
            wa_aufk   TYPE ty_aufk,
            wa_afko   TYPE ty_afko,
            wa_afpo   TYPE ty_afpo,
            wa_afvc   TYPE ty_afvc,
            wa_afvv   TYPE ty_afvv,
            wa_mdvm   TYPE ty_mdvm.
    DATA :  it_object TYPE hum_object_t,
            wa_object TYPE hum_object,
            it_item   TYPE hum_hu_item_t,
            wa_item   TYPE vepovb,
            count1(6) TYPE n.
    DATA :  gv_objek TYPE ausp-objek.       "Put matnr for use in FM u2018CLAF_CLASSIFICATION_OF_OBJECTSu2019
    DATA : BEGIN OF it_sclass OCCURS 0.
            INCLUDE STRUCTURE sclass.
    DATA : END OF it_sclass.
    DATA : BEGIN OF it_clobjdat OCCURS 0.
            INCLUDE STRUCTURE clobjdat.
    DATA : END OF it_clobjdat.
    *&  Include           ZPPR_CONVSTAT_SEL_CRITERIA
      SELECTION-SCREEN FOR 'PLANNING STAGE'
    SELECTION-SCREEN BEGIN OF BLOCK main WITH FRAME TITLE text-001.
      PARAMETERS: mrpntdn RADIOBUTTON GROUP sel                    DEFAULT 'X' user-command flag,
                  pldord  RADIOBUTTON GROUP sel,
                  prdord  RADIOBUTTON GROUP sel.
    SELECTION-SCREEN END OF BLOCK main.
      SELECTION-SCREEN FOR 'SELECTION BY PLANT AND PLANT DATA'
    SELECTION-SCREEN BEGIN OF BLOCK plant WITH FRAME TITLE text-002.
      PARAMETERS      : p_werks   LIKE  ioheader-werks OBLIGATORY  DEFAULT '1100' MATCHCODE OBJECT H_T001W.
      SELECT-OPTIONS  : so_matnr  FOR   ioitem-matnr                              MATCHCODE OBJECT MAT1.
      PARAMETERS      : so_mtart  TYPE  t134-mtart     OBLIGATORY  DEFAULT 'ZFIN' MATCHCODE OBJECT H_T134.
      SELECT-OPTIONS  : so_plnum  FOR   ioitem-plnum                              MATCHCODE OBJECT plnum  MODIF ID pld,
                        so_aufnr  FOR   ioheader-aufnr                            MATCHCODE OBJECT orde   MODIF ID prd.
      PARAMETERS      : p_prdsta  LIKE  tj02t-txt04                                                       MODIF ID prd.
    SELECTION-SCREEN END OF BLOCK plant.
      SELECTION-SCREEN FOR 'SELECTION BY REQUIREMENT TYPE'
    SELECTION-SCREEN BEGIN OF BLOCK reqtyp  WITH FRAME TITLE text-003.
      PARAMETERS      : cb_so     TYPE AUSWL_EB AS CHECKBOX USER-COMMAND flag,
                        cb_sto    TYPE AUSWL_EB AS CHECKBOX USER-COMMAND flag,
                        cb_pir    TYPE AUSWL_EB AS CHECKBOX USER-COMMAND flag.
    SELECTION-SCREEN END OF BLOCK reqtyp.
      SELECTION-SCREEN FOR 'SELECTION BY DATE AND REQUIREMENT TYPE NOS'
    SELECTION-SCREEN BEGIN OF BLOCK dtreqtypno WITH FRAME TITLE text-004.
      SELECT-OPTIONS  : so_crtdt  FOR vbak-erdat                                                                MODIF ID gen,
                        so_vbeln  FOR vbap-vbeln                                  MATCHCODE OBJECT WTY_F4_VBAP  MODIF ID rso,
                        so_posnr  FOR vbap-posnr                                                                MODIF ID rso,
                        so_ebeln  FOR ekub-ebeln                                  MATCHCODE OBJECT MEKKM        MODIF ID rst,
                        so_ebelp  FOR ekub-ebelp                                                                MODIF ID rst,
                        so_pbdnr  FOR pbim-pbdnr                                                                MODIF ID rpi,
                        so_reqdt  FOR vbep-edatu                                                                MODIF ID gen.
    SELECTION-SCREEN END OF BLOCK dtreqtypno.
      SELECTION-SCREEN FOR 'SELECTION BY OTHER PARAMETERS'
    SELECTION-SCREEN BEGIN OF BLOCK othrparam WITH FRAME TITLE text-005.
      SELECT-OPTIONS  : so_kunnr FOR kna1-kunnr                                   MATCHCODE OBJECT debi   MODIF ID rso,
                        so_auart FOR tvak-auart                                   MATCHCODE OBJECT H_TVAK MODIF ID rso,
                        so_lfsta FOR vbup-lfsta                                                           MODIF ID rso.
    SELECTION-SCREEN END OF BLOCK othrparam.
    *&  Include           ZPPR_CONVSTAT_PBO
    *&   Event AT SELECTION-SCREEN OUTPUT
    AT SELECTION-SCREEN OUTPUT.
      IF mrpntdn = 'X'.
        LOOP AT SCREEN.
          IF ( screen-group1 = 'PLD' OR screen-group1 = 'PRD' ).
            screen-active = 0.
            MODIFY SCREEN.
          ENDIF.
        ENDLOOP.
      ELSEIF pldord = 'X'.
        LOOP AT SCREEN.
          IF screen-group1 = 'PLD'.
            screen-intensified = 1.
            MODIFY SCREEN.
          ENDIF.
          IF screen-group1 = 'PRD'.
            screen-active = 0.
            MODIFY SCREEN.
          ENDIF.
        ENDLOOP.
      ELSEIF prdord = 'X'.
        LOOP AT SCREEN.
          IF ( screen-group1 = 'PLD' OR screen-group1 = 'PRD' ).
            screen-intensified = 1.
            MODIFY SCREEN.
          ENDIF.
        ENDLOOP.
      ENDIF.
      IF ( cb_so = ' ' AND cb_sto = ' ' AND cb_pir = ' ' ).
        LOOP AT SCREEN.
          IF ( screen-group1 = 'GEN'
          OR screen-group1 = 'RSO'
          OR screen-group1 = 'RST'
          OR screen-group1 = 'RPI' ).
            screen-active = 0.
            MODIFY SCREEN.
          ENDIF.
        ENDLOOP.
      ENDIF.
      IF cb_so = 'X'.
        LOOP AT SCREEN.
          IF screen-group1 = 'RSO'.
            screen-active = 1.
            MODIFY SCREEN.
          ENDIF.
        ENDLOOP.
        IF cb_sto = ' '.
          LOOP AT SCREEN.
            IF screen-group1 = 'RST'.
              screen-active = 0.
              MODIFY SCREEN.
            ENDIF.
          ENDLOOP.
        ENDIF.
        IF cb_pir = ' '.
          LOOP AT SCREEN.
            IF screen-group1 = 'RPI'.
              screen-active = 0.
              MODIFY SCREEN.
            ENDIF.
          ENDLOOP.
        ENDIF.
      ELSEIF cb_sto = 'X'.
        IF cb_so = ' '.
          LOOP AT SCREEN.
            IF screen-group1 = 'RSO'.
              screen-active = 0.
              MODIFY SCREEN.
            ENDIF.
          ENDLOOP.
        ENDIF.
        IF cb_pir = ' '.
          LOOP AT SCREEN.
            IF screen-group1 = 'RPI'.
              screen-active = 0.
              MODIFY SCREEN.
            ENDIF.
          ENDLOOP.
        ENDIF.
      ELSEIF cb_pir = 'X'.
        IF cb_so = ' '.
          LOOP AT SCREEN.
            IF screen-group1 = 'RSO'.
              screen-active = 0.
              MODIFY SCREEN.
            ENDIF.
          ENDLOOP.
        ENDIF.
        IF cb_sto = ' '.
          LOOP AT SCREEN.
            IF screen-group1 = 'RST'.
              screen-active = 0.
              MODIFY SCREEN.
            ENDIF.
          ENDLOOP.
        ENDIF.
      ENDIF.
    *&  Include           ZPPR_CONVSTAT_START_SELECTION
    *&   Event START-OF-SELECTION
    IF mrpntdn = 'X'.
      PERFORM start_of_selection_mrpntdn.
    ELSEIF pldord = 'X'.
      PERFORM start_of_selection_pldord.
    ELSEIF prdord = 'X'.
      PERFORM start_of_selection_prdord.
    ENDIF.
    *&  Include           ZPPR_CONVSTAT_F_START_OF_SEL
    *&      Form  START_OF_SELECTION
          Subroutine for MRP NOT DONE
    FORM start_of_selection_mrpntdn.
        SELECT mdkey INTO TABLE it_mdvm FROM mdvm
                     WHERE GSAEN = 'X'
                       AND AKKEN = 'X'.
          IF sy-subrc = 0.
            LOOP AT it_mdvm INTO wa_mdvm.
              wa_mdvm-disst = wa_mdvm-mdkey(3).
              wa_mdvm-matnr = wa_mdvm-mdkey+3(18).
              wa_mdvm-plwrk = wa_mdvm-mdkey+21(4).
              MODIFY it_mdvm FROM wa_mdvm INDEX sy-index TRANSPORTING disst matnr plwrk.
            ENDLOOP.
          ENDIF.
    ENDFORM.
    *&      Form  START_OF_SELECTION
          Subroutine for PLAN ORDER CREATED
    FORM start_of_selection_pldord.
    ENDFORM.
    *&      Form  START_OF_SELECTION for PRODUCTION ORDER CREATED
          Subroutine for PRODUCTION ORDER CREATED
    FORM start_of_selection_prdord.
    ENDFORM.

    You need to mention START-OF-SELECTION explicitly in your code.
    Change your code as below:
    *& Event START-OF-SELECTION
    START-OF-SELECTION.
    IF mrpntdn = 'X'.

  • MRP Requirements due to sales order rejected

    Hi,
    I am using the strategy Assembly to order in an environment Make to Order.
    When the sales department fill out the field reason for rejection with any value the system deleted the production order even it has the status release or has notification.
    Does any one knows how to avoid this behavior in the system?
    Thanks in advanced.
    Regards,
    Isaias

    How did you handle the requirements. Because if you do not type a rejection reason the system generate another production order for the sales order after you run the MRP.
    regards,
    Isaias

  • PHP 4.4.9 installation required due to extremely serious vulnerabilities

    securitymetrics.com is requiring me to upgrade to PHP 4.4.9 because of extremely serious vulnerabilities, and there is no current patch that apple is offering.
    I am looking for some guidance as I am not sure what is required.
    I am running osx server 10.4.11
    Is there an easy place to download php 4.4.9 and install seamlessly to work with the server admin tools.

    I need to be complaint with securitymetrics.com's ever changing requirements. There are vulnerabilities they see as extremely serious. "Including : - An update of PCRE to version 7.7. - An overflow in memnstr(). - A crash in imageloadfont when an invalid font is given. - An open_basedir handling issue in the curl extension. - 'mbstring.func_overload' set in '.htaccess' becomes global."
    They scan my IP looking for vulnerabilities ensuring that it is up to standards that banks require for e-commerce. I give them no access to the computer other than to tell them the URL.
    Apple hasn't said it is or is not going to come in the next patch or updates.
    Installing customized PHP does concern me as I know I would need to configure php from the ground up and it would probably not integrate with future updates.
    Is there a place I can go to find out what is planned for the next update?

  • Adjustment required in Gross block

    Hi Gurus,
    I have one issue in asset accounting i.e Gross Block is Rs,.1000 and Acc.dep is 200 and net block is 700 this is belongs to fiscaal year 2008.  I want  do adjustment  like in Gross block 950,Acc.dep is 150 and Net block  is 700. I can adjust netblock but how to adjust Gross block with out changeing net block.
    regards,
    ssriram

    Hi
    Please check the note 50761, you need to post a write-off.
    Blaz

  • Adjustment using SPAU for Objects Without Modification Assistant

    Hi
       How to adjust Objects under Without Modification Assistant.
    For example if there is an issue with custom program or BAPI, do I have to manually edit them and adjust to old version.
    Cheers
    Senthil

    Hi,
    Tcode SPAU is for adjusting programs and Function Modules.
    http://help.sap.com/saphelp_nw04/helpdata/en/2e/6d66617d9011d396b60000e82de14a/frameset.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
    SPAU - for repository Objects Changes
    see the doc
    SPAU
    http://www.sap-img.com/bc018.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/c6/068d380be34e6ce10000009b38f842/content.htm
    http://help.sap.com/saphelp_46c/helpdata/EN/60/d6ba7bceda11d1953a0000e82de14a/content.htm
    Please find below, answers to your questions:
    1.What objects will come in SPAU and SPDD?
    Ans: All the objects which are modified, after tansporting to the current system,
    will be listed in SPAU and SPDD. SPDD contains the list of all modified Data Dictionary objects, like tables, dataelements, domains,view...etc. The rest of all the modified repository objects will be listed in SPAU.
    What happens to the modifications done in the older version when we upgrade the version? (with Modification assistant and w/o)
    Ans: After the initial upgrade happens, we have to do adjustments from SPAU/SPDD to maintain or reset the changes. That is, from the list of objects in SPAU/SPDD, you have to either carry forward the changes to the new version, by choosing the option ADOPT CHANGES (available on right click) or RESET TO ORIGINAL (available on right click).
    Will they come in these transactions?
    Ans: yes, they will be listed in these transactions, after the BASIS updgrade activity.
    And what if we apply some patches(Notes) to the system? What is the impact of these patches to the SPAU transaction?
    Ans: Patches will be supported by the version upgrade. In case of notes, we have to verify whether these notes are supported by the new version (you can go into http://www.service.sap.com/notes to verify this. Also, we have to analyze whther the code in the note is already incorporated in the new version. In this case you can ignore the chanes choosing RESET TO ORIGINAL option
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/2e/6d66587d9011d396b60000e82de14a/frameset.htm
    If you have applied any OSS notes to objects in your system, the hot package may overwrite these objects.
    SPDD is used to identify dictionary objects
    and
    SPAU (repository objects), will identify any objects where the hot package is overwriting changes you have made through OSS notes.
    You must check all objects identified in SPAU and decide whether you need to reapply the OSS note or reset the code to the original SAP Code.
    Also once the changes have been done you would see a green traffic light.
    If you double click on the modified object it will show you a split window where on the left you will have the original version and on right the modified version. So you can choose which to keep and which to reject. You may keep the modified version incases where you know that the notes will only be pakages in the next version.
    http://help.sap.com/saphelp_47x200/helpdata/en/2e/6d66647d9011d396b60000e82de14a/frameset.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/2e/6d66647d9011d396b60000e82de14a/frameset.htm
    http://www.sap-img.com/bc018.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/c6/068d380be34e6ce10000009b38f842/content.htm
    http://help.sap.com/saphelp_46c/helpdata/EN/60/d6ba7bceda11d1953a0000e82de14a/content.htm
    http://www.sap-img.com/bc018.htm
    http://www.sappoint.com/oss/spamspau.html
    http://help.sap.com/saphelp_nw04/helpdata/en/fe/4b284837bf11d5b3bf0050dae02d7c/content.htm
    http://help.sap.com/saphelp_webas620/helpdata/en/83/7a18ecde6e11d195460000e82de14a/content.htm
    http://64.233.167.104/custom?q=cache:nJasGnXhh4sJ:www.asug.com/client_files/Calendar/Upload/SAP%2520Upgrade%2520Lessons%2520Learned.ppt+spau(SAP)&hl=en&ct=clnk&cd=5&ie=UTF-8&client=pub-3723304925932908
    Also the following link is very good
    http://www.sapgenie.com/basis/starter.htm
    Regards,
    Naresh

  • Is Access in Modifications Adjustment Phase in SPDD: 4.7, SR1

    Hi,
    We are applying support packages and while in SPDD phase when we choose for "adopt modifications, it is asking for "Developer access key".
    Same prompting while clicking the "accept proposal" or "Edit Proposal" also.
    We are doing this activity in client 000 with Registered developer user ID only.
    My doubts are:
    1. Is Developer access Key required for doing Modification adjustments???
    Please through some light . . .
    Thanks

    We are using OS SunOS 5.10. We have gone through the note  525677.
    SunOS 5.10 doesn´t use /etc/system but uses projects to configure IPC shared memory.
    Did you configure /etc/project and /etc/user_attr according to
    Note 724713 - parameter settings for Solaris 10
    Markus

  • Task Due date in SharePoint 2013

    Hi All,
    we have an issue where we want some customization or possible turn around solution on SharePoint 2013. i want to know that if we are allocating any Task to any user then we have Start Date & Due Date in Task Form. Here what i want that automatically,
    after 2 Days, Due date column should be freezes/locked (No more changes in that). And if we want to change Due date then can only change 2 times & if we want to change again Due date as 3rd time then it should not allow to change at all & require some
    kind of approval from Management.

    Hello,
    For the limited number of modification of the due date, I would use an event receiver on "itemupdating"  with this kind of logic
    If (Properties.ListItem[«Due Date»] != Properties.AfterProperties[«Due Date»]) //modification of the date
    check the number of modification, if less than 3 , increment the number and continue, if 3 set
    Properties.AfterProperties[«Due Date»]) =Properties.ListItem[«Due Date»]
    here some info about creating event recivers :http://msdn.microsoft.com/en-us/library/gg252010(v=office.14).aspx (for 2010 but the same for 2013)
    Best regards, Christopher.
    Blog |
    Mail
    Please remember to click "Mark As Answer" if a post solves your problem or
    "Vote As Helpful" if it was useful.
    Why mark as answer?

  • Due date analysis for G/L account

    Hy!
    I need to make a report that makes due date analysis for G/L accounts similar to S_ALR_87012078 Due date analysis for open items
    for Account payable.
    Has any one experience with that and can help me with that?
    Regards,
    Marina

    Hi Marina,
    its a bit surprising why you require due date analysis for GL accounts as GL accounts are used for realtime posting and no credit involved. Only AR and AP accounts contain credit, so they may be even over due and thus we require ageing or due date analysis.
    If transaction is on a cash basis should be posted to GL not to Subledger. Since there is no due date system for GL posting due date is not possible which makes sense too.
    Hope this gets a better clarity for you.
    Regards
    Bharat

  • Problem with Solution Manager wanting to adjust its own instance

    I have a situation where under my landscape components --> systems in SMSY where I have a "yellow" exclamation point in a box that says "newer version exists" for my existing solution manager.  When I try to adjust, it doesn't let me select the system because they are on the same host.  Therefore, I can't do the adjustment.  What is the problem?  Any ideas how I can do this adjustment?  Thanks.  This is very important.  Thanks.,

    Thanks Ragu.  I've dug a little deeper and this is what is happening when I try to assign the Solution Manager instance to a logical component:
    I receive an "instance
    adjustment required" message for the actual solution manager instance
    itself, so I had to manually set the product and set it to leading as
    leading (even though there was no other solution manager instance).
    This means that the solution manager system itself is set to manual
    adjustment.  I've gotten it to read from the SLD, but it is still acting as though it is missing a NetWeaver ABAP Server on the same host as the Solution Manager.
    Here is what I do to get the above issue to reproduce:
    I've done more trouble shooting and found that if I go to installed product versions in the Solution Manager System and click on Clean-up Inconsistencies, I get
    the attached screenshot showing that a Product SAP NetWeaver with main instance "Application Server ABAP" is inconsistent (on the same server as the Solutiion Manager instance, the Solutioni Manager instance doesn't show up in the System landscape either). Cleaning up the inconsistency doesn't fix the problem (leaves Application Server ABAP) in place.  Meaning when I try to fix the inconsistency it won't let me.  Thanks for any help, I really need to figure this out.  Thanks.

  • How to map Due date from Jdev to show in BPM Workspace

    Hello,
    Requirement:
    Due date of the human tasks(that are set in jdev) should be visible in BPM Workspace .
    I have added due date column in BPM workspace under process tracking and observed that the column is not reflecting the due date.
    I found in a blog that we can map the variables that are required as flex fields to the systemManagedAttributes and then use them in BPM Workspace. 
    In our requirement, we have date as an input variable, for due date if i use "By Duration" and give 2 days then the date due will the "date which we will give as input+2days". So to map that due date to the systemManagedAttributes, which variables do i need to map so as to reflect the due date in workspace.
    Please suggest any other ways of reflecting the due date of human task in BPM workspace.
    Thanks,
    Sravani.

    Hi Sravani,
    I admire your innovative solution using flex fields, but there is a simpler way to show the deadlines in the Workspace's task list.
    You can simply add the "Expires" column in the Workspace for your Inbox.  That way it will automatically show your human task's deadline in the Expires column and you can avoid going the flex field route.
    Dan

  • New Finished Goods due date

    My scenario is we have a sales order which has a required due date, meaning that the FGs are required on a certain date. lets say we run the mrp and all requirments are calculated and planned orders , PRs are generated. Now, using CRP we firm the planned order dates. After we convert it into a production order.
    My question is what is the effect if we change the FG due date to an earlier date, and how does it affect the schedule? do we need to run crp again?

    Hi Timan
    in MD04 select the Planned order enter into change screen (by double clicking on it) Now enter the New finish date and remove all other dates (Start date and planned open date)
    Now click on the reshcdule button - second in the tool bar or press Shift+F6
    Now the order will be rescheduled and firmed automatically you can save it
    BR SK

  • ECC 6.0 Upgrade & changes required in programs

    In case of a version upgrade to ECC 6.0, the programs would need to be changed. Some changes in the programs would be required to meet unicode compliance, while some changes would be required due to version upgrade (constructs becoming obsolete, etc). I guess the unicode related issues could be found by using the UCCHECK transaction and then resolved by making changes and again checking using this transaction, but is there some way to find out what issues would arise due to version upgrade? (The programs work fine in the lower version which is 4.6c). One way would be to actually check the programs in runtime and then handling the issues faced. But if we don't want to test all the programs, then is there some tool, or any best practice which would minimize the chance of having issues in the programs (and might be in help in solving the issues)?

    SAMT is a transaction that will allow you to create sets for syntax check. We generally do it for Z* and Y* objects if the count does not exceed 3000.
    Batch objects are the BDCs and Conversions as explained by Hema. Earlier upgrades had more than 80% of these objects failing becuase the screens may have changed or the screen fields may be missing, screen flow changed ... But now it has reduced especially from 46c to Ecc6 upgrade. However it still warrants testing them thoroughly.
    Clones are copies of standard SAP objects in Z space and modified. These objects generally tend to have standard includes within them or the program definition may still have the original SAP name. It is tricky to find all of them but simple rules like matching name strings (eg SAPMV45A -> ZAPMV45A or Z_SAPMV45A) would help. It may vary from customer to customer depending on their naming standards.
    Standard function modules used in the program can be easily found out using SCAN command in ABAP (see my example for SCAN in code snippets). Use the list of function modules identified and pass to the program below to see if their interfaces have changed. Test all objects affected by changed interfaces.
    *& Report  YACN_FUNC_ANALYSIS
    REPORT  YACN_FUNC_ANALYSIS.
    Tables: tfdir.
    DATA: v_found TYPE c.
    DATA: v_func LIKE enlfdir-funcname.
    DATA: BEGIN OF i_import OCCURS 0.
            INCLUDE STRUCTURE rsimp.
    DATA: END OF i_import.
    DATA: BEGIN OF i_changing OCCURS 0.
            INCLUDE STRUCTURE rscha.
    DATA: END OF i_changing.
    DATA: BEGIN OF i_export OCCURS 0.
            INCLUDE STRUCTURE rsexp.
    DATA: END OF i_export.
    DATA: BEGIN OF i_table OCCURS 0.
            INCLUDE STRUCTURE rstbl.
    DATA: END OF i_table.
    DATA: BEGIN OF i_exceptions OCCURS 0.
            INCLUDE STRUCTURE rsexc.
    DATA: END OF i_exceptions.
    DATA: BEGIN OF i_doc OCCURS 0.
            INCLUDE STRUCTURE rsfdo.
    DATA: END OF i_doc.
    DATA: BEGIN OF i_source OCCURS 0,
             INCLUDE STRUCTURE RSSOURCE.
              line(256)  TYPE c,
          END OF i_source.
    DATA: BEGIN OF e_import OCCURS 0.
            INCLUDE STRUCTURE rsimp.
    DATA: END OF e_import.
    DATA: BEGIN OF e_changing OCCURS 0.
            INCLUDE STRUCTURE rscha.
    DATA: END OF e_changing.
    DATA: BEGIN OF e_export OCCURS 0.
            INCLUDE STRUCTURE rsexp.
    DATA: END OF e_export.
    DATA: BEGIN OF e_table OCCURS 0.
            INCLUDE STRUCTURE rstbl.
    DATA: END OF e_table.
    DATA: BEGIN OF e_exceptions OCCURS 0.
            INCLUDE STRUCTURE rsexc.
    DATA: END OF e_exceptions.
    DATA: BEGIN OF e_doc OCCURS 0.
            INCLUDE STRUCTURE rsfdo.
    DATA: END OF e_doc.
    DATA: BEGIN OF e_source OCCURS 0,
             INCLuDE STRUCTURE RSSOURCE.
              line(256)  TYPE c,
          END OF e_source.
    DATA: BEGIN OF i_tab OCCURS 0,
              line(71)  TYPE c,
          END OF i_tab.
    PARAMETERS: p_file LIKE rlgrap-filename DEFAULT 'D:\Documents and Settings\prakash.bhatia\Desktop\funcmods.txt'.
    START-OF-SELECTION.
      CALL FUNCTION 'UPLOAD'
       EXPORTING
      CODEPAGE                      = ' '
          filename                      = p_file
          filetype                      = 'DAT'
      ITEM                          = ' '
      FILEMASK_MASK                 = ' '
      FILEMASK_TEXT                 = ' '
      FILETYPE_NO_CHANGE            = ' '
      FILEMASK_ALL                  = ' '
      FILETYPE_NO_SHOW              = ' '
      LINE_EXIT                     = ' '
      USER_FORM                     = ' '
      USER_PROG                     = ' '
      SILENT                        = 'S'
    IMPORTING
      FILESIZE                      =
      CANCEL                        =
      ACT_FILENAME                  =
      ACT_FILETYPE                  =
        TABLES
          data_tab                      = i_tab
    EXCEPTIONS
      CONVERSION_ERROR              = 1
      INVALID_TABLE_WIDTH           = 2
      INVALID_TYPE                  = 3
      NO_BATCH                      = 4
      UNKNOWN_ERROR                 = 5
      GUI_REFUSE_FILETRANSFER       = 6
      OTHERS                        = 7
      LOOP AT i_tab.
        v_func = i_tab-line.
        select single * from tfdir where funcname = v_func.
        if sy-subrc <> 0.
          continue.
        endif.
        PERFORM get_func_details TABLES i_import
                                        i_changing
                                        i_export
                                        i_table
                                        i_exceptions
                                        i_doc
                                        i_source
                                  USING ' ' v_func.
        PERFORM get_func_details TABLES e_import
                                        e_changing
                                        e_export
                                        e_table
                                        e_exceptions
                                        e_doc
                                        e_source
                                  USING 'D02' v_func.
        WRITE:/ v_func.
        CLEAR v_found.
        IF i_import[] = e_import[].
          WRITE: 'N'.
        ELSE.
          LOOP AT i_import.
            READ TABLE e_import WITH KEY parameter = i_import-parameter.
            IF sy-subrc <> 0.
              IF i_import-optional <> 'X'.
                WRITE: 'Y'.
                v_found = 'X'.
                EXIT.
              ENDIF.
            ELSE.
              IF i_import-typ <> ' '.
                IF i_import-typ <> e_import-dbfield.
                  WRITE: 'Y'.
                  v_found = 'X'.
                  EXIT.
                ENDIF.
              ELSE.
                IF i_import-dbfield <> ' '.
                  IF i_import-dbfield <> e_import-dbfield.
                    WRITE: 'Y'.
                    v_found = 'X'.
                    EXIT.
                  ENDIF.
                ENDIF.
              ENDIF.
            ENDIF.
          ENDLOOP.
          IF v_found = ' '.
            WRITE: 'N'.
          ENDIF.
        ENDIF.
        CLEAR v_found.
        IF i_changing[] = e_changing[].
          WRITE: 'N'.
        ELSE.
          LOOP AT i_changing.
            READ TABLE e_changing WITH KEY parameter = i_changing-parameter.
            IF sy-subrc <> 0.
              IF i_changing-optional <> 'X'.
                WRITE: 'Y'.
                v_found = 'X'.
                EXIT.
              ENDIF.
            ELSE.
              IF i_changing-typ <> ' '.
                IF i_changing-typ <> e_changing-dbfield.
                  WRITE: 'Y'.
                  v_found = 'X'.
                  EXIT.
                ENDIF.
              ELSE.
                IF i_changing-dbfield <> ' '.
                  IF i_changing-dbfield <> e_changing-dbfield.
                    WRITE: 'Y'.
                    EXIT.
                  ENDIF.
                ENDIF.
              ENDIF.
            ENDIF.
          ENDLOOP.
          IF v_found = ' '.
            WRITE: 'N'.
          ENDIF.
        ENDIF.
        CLEAR v_found.
        IF i_export[] = e_export[].
          WRITE: 'N'.
        ELSE.
          LOOP AT i_export.
            READ TABLE e_export WITH KEY parameter = i_export-parameter.
            IF sy-subrc = 0.
              IF i_export-typ <> ' '.
                IF i_export-typ <> e_export-dbfield.
                  WRITE: 'Y'.
                  v_found = 'X'.
                  EXIT.
                ENDIF.
              ELSE.
                IF i_export-dbfield <> ' '.
                  IF i_export-dbfield <> e_export-dbfield.
                    WRITE: 'Y'.
                    v_found = 'X'.
                    EXIT.
                  ENDIF.
                ENDIF.
              ENDIF.
            ENDIF.
          ENDLOOP.
          IF v_found = ' '.
            WRITE: 'N'.
          ENDIF.
        ENDIF.
        CLEAR v_found.
        IF i_table[] = e_table[].
          WRITE: 'N'.
        ELSE.
          LOOP AT i_table.
            READ TABLE e_table WITH KEY parameter = i_table-parameter.
            IF sy-subrc <> 0.
              IF i_table-optional <> 'X'.
                WRITE: 'Y'.
                v_found = 'X'.
                EXIT.
              ENDIF.
            ELSE.
              IF i_table-typ <> ' '.
                IF i_table-typ <> e_table-dbstruct.
                  WRITE: 'Y'.
                  v_found = 'X'.
                  EXIT.
                ENDIF.
              ELSE.
                IF i_table-dbstruct <> ' '.
                  IF i_table-dbstruct <> e_table-dbstruct.
                    WRITE: 'Y'.
                    v_found = 'X'.
                    EXIT.
                  ENDIF.
                ENDIF.
              ENDIF.
            ENDIF.
          ENDLOOP.
          IF v_found = ' '.
            WRITE: 'N'.
          ENDIF.
        ENDIF.
       IF i_exceptions[] = e_exceptions[].
         WRITE: 'N'.
       ELSE.
         WRITE: 'Y'.
       ENDIF.
    *if I_doc[] = e_doc[].
    write: 'N'.
    *else.
    write: 'Y'.
    *endif.
       IF i_source[] = e_source[].
         WRITE: 'N'.
       ELSE.
         WRITE: 'Y'.
       ENDIF.
      ENDLOOP.
    *&      Form  get_func_details
          text
         -->P_TRG  text
    FORM get_func_details  TABLES t_import
                                  t_changing
                                  t_export
                                  t_table
                                  t_exceptions
                                  t_doc
                                  t_source
                           USING  p_trg
                                  p_func.
      CALL FUNCTION 'RPY_FUNCTIONMODULE_READ'
        DESTINATION p_trg
        EXPORTING
          functionname             = p_func
    IMPORTING
      GLOBAL_FLAG              =
      REMOTE_CALL              =
      UPDATE_TASK              =
      SHORT_TEXT               =
      FUNCTION_POOL            =
        TABLES
          import_parameter         = t_import
          changing_parameter       = t_changing
          export_parameter         = t_export
          tables_parameter         = t_table
          exception_list           = t_exceptions
          documentation            = t_doc
          SOURCE                   = t_source
    EXCEPTIONS
      ERROR_MESSAGE            = 1
      FUNCTION_NOT_FOUND       = 2
      INVALID_NAME             = 3
      OTHERS                   = 4
    ENDFORM.                    " get func details
    -Cheers

  • Component requirement date in subcontracting case

    Hello All,
    I have subcontracting PR having delivery date as 26.11.2010 and release date as 17.10.2010 and planned delivery time as 40 days. I change the PR release date to 10.10.2010 and it shows the requirement date for the components as same as 10.10.2010 which is my requirement. But when I convert PR to PO it is showing the component requirement date as 19.09.2010 and release and delivery date same as in PR. I want system should not change the component requirement date.
    How system is showing requirement date in PO as 19.09.2010? Is some one has any idea?
    Mayur Phalak

    Hi Mayur
    The requirement date for component in subcontract is Delivery date of the item minus planned delivery time -This is what SAP library says. But in your case I see a huge difference. Is your PR manually created or MRP generated?
    Have you maintained info record? Is planned delivery time is copied from info record? You can see planned delivery time in PO delivery tab. (find out which value has been copied).
    As per SAP standard when you press enter button in PO requirement date is redetermined based on planned delivery time in the PO delivery tab. So try giving Planned delivery time in PR or info record to adjust requirement date
    Write to me if you are not clear.
    Regards
    Antony

Maybe you are looking for