Upgrade Project: CRM Function Groups

Hi All,
The Function groups like "CRM_ISALES_SOLDTO" which was present in SRM 3.0 is replaced in SRM 5.0.
I am currently on an upgrade project anr there are several Z FM's which gives a call to the FM's under this function group. Since they are unavailable in new system, all these Z FM's are showing syntax error.
Please let me know if there is any replacement made by SAP for the above Function Group or FM's under it?
Thanks
Sangharsh

Hi
Incase nothing suits you, then you need to go for Custom Z function modules in this case.
Take help of ABAP resources and create Z function modules, referring to the Standard Function modules in your old SRM 3.0 Version.
Also, raise an OSS message with SAP on this at the earliest.
Regards
- Atul

Similar Messages

Some problems about Upgrad project

Dear,
    I have some question for Upgrade project.shi
P1: in form ZSD_EXPORT_FECO, check texts, Windows F005 has an error :
     /: AND &V55EFECO-REMA_TEXT2& = ' '
               Unknown command
       I dont know how to correct it.
P2: in program ZFUMSV00, the source code is   sy-repid    = 'RFUMSV00'.
     In 700 version, it checks error: the field sy-repid cant be changed.
     But, in 46c version, it is OK.
        I dont know how to correct it.

Hi
check this doc
While doing Upgrade You have to aware of all related program like BDC's , Screens related errors and all dictionary related problems.
Some function modules may become obsolete, and some screens will change
and some new fields will be added in the new versions etc.
Also take care of SPAU and SPDD tcodes.
You should be able to know about Unicode concept in sap.
check this
http://www.thespot4sap.com/upgrade_guide_v2.pdf#search=%22upGRADE%20STEPS%20-%20SAP%22
also chk these 2 notes in service.sap.com
Technical Upgrade is only a version upgrade without any functionality changes.
The objects that are needed to be upgraded are:
Includes
Function Groups / Function Modules
Programs / Reports
OSS Notes
SAP Repository Objects
SAP Data Dictionary Objects
Domains, Data Elements
Tables, Structures and Views
Module Pools, Sub Routine pools
BDC Programs
Print Programs
SAP Scripts, Screens
User Exits
You can refer to the below links for more information on technical upgrade:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/07/upgradeFROMR3TOmySAPERP-PARTII&
https://wiki.sdn.sap.com/wiki/display/profile/UPGRADEFROMR3TOmySAPERP-PARTIII
http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/2e/6d66647d9011d396b60000e82de14a/content.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5ac31178-0701-0010-469a-b4d7fa2721ca
Regards
Anji

Upgradation project details in technical

Hi,
I need the brief details regarding upgradation project i.e. from one version to another version. Please provide the Technical (ABAP) details...
Thanks in advance.
Regards,
Kittu.

hi Kishore,
Upgrading SAP is something that all companies have to face on a periodic basis.
In a technical upgrade, you merely upgrade the SAP system and adjust any existing userexits and configuration only as necessary (e.g. the introduction of Lean WM - warehouse management - gave Business Sponsors the choice to implement Lean WM with it's relatively minor changes or use the old configuration without any negative impact).
The objects that are needed to be upgraded are:
Includes
Function Groups / Function Modules
Programs / Reports
OSS Notes
SAP Repository Objects
SAP Data Dictionary Objects
Domains, Data Elements
Tables, Structures and Views
Module Pools, Sub Routine pools
BDC Programs
Print Programs
SAP Scripts, Screens
User Exits
You can refer to the below links for more information on technical upgrade:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/07/upgradeFROMR3TOmySAPERP-PARTII&
https://wiki.sdn.sap.com/wiki/display/profile/UPGRADEFROMR3TOmySAPERP-PARTIII
http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/2e/6d66647d9011d396b60000e82de14a/content.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5ac31178-0701-0010-469a-b4d7fa2721ca
Hope this is helpful, Do reward.

What is done in upgrade projects ?

hi,
does any one know what is to be done to upgrade from one version to other version ???
for example if u want to upgrade from 5.0 to 6.0 what is the responsibility of the functional guy
thanks
madhan
rewards for sure

Dear Madhan,
STEPS IN TECHNICAL UPGRADE
Basis Team will do the prepare activities. (UNIX, BASIS, DBA).
Developer need to run the Transaction SPDD which provides the details of SAP Standard Dictionary objects that have been modified by the client. Users need to take a decision to keep the changes or revert back to the SAP Standard Structure. More often decision is to keep the change. This is mandatory activity in upgrade and avoids data loses in new system.
After completing SPDD transaction, we need to run SPAU Transaction to get the list of Standard SAP programs that have been modified. This activity can be done in phases even after the upgrade. Generally this will be done in same go so that your testing results are consistent and have more confident in upgrade.
Run SPUMG Transaction for Unicode Conversion in non-Unicode system. SPUM4 in 4.6c.
Then we need to move Z/Y Objects. Need to do Extended programming check, SQL trace, Unit testing, Integration testing, Final testing, Regression Testing, Acceptance Testing etc.,
The main Category of Objects that needs to be Upgraded is
Includes
Function Groups / Function Modules
Programs / Reports
OSS Notes
SAP Repository Objects
SAP Data Dictionary Objects
Domains, Data Elements
Tables, Structures and Views
Module Pools, Sub Routine pools
BDC Programs
Print Programs
SAP Scripts, Screens
User Exits
Please visit the following links:
http://service.sap.com/erp
http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional prespective)
http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
For Functionality Differences pls refer to the below site -
http://solutionbrowser.erp.sap.fmpmedia.com/
After opening the site, please select the Source Release Version which is 4.6 b Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0
Select the Solution Area like Financials, Human Capital Management, Sales....
Select module like MM, PP, SD, QM.....
Click on Search
Then it displays the Release Version and the Delta Functionality. which can be downloaded to a word document if required.
and also check the release notes of ECC 6.0 in service.sap.com.
Hope this helps you.
Do award points if you found them useful.
Regards,
Rakesh
P.S. you can send me a mail at my mail id [email protected] for any specific details

What do you mean by changing a Function Group in upgradation projects

Hi ABAPers,
I am new to upgradation project will any one help me in understanding the concepts like.
1) what do you mean by changing a Function Group in upgradation projects
2) what is the relation b/w the Maintenance view and function group
3) what happens when we regenerate the table maintenance in se11
4) how can i restore the changes that have done to FG after regenerating
5) Suggest me is there any Tcode or procedure to see the code in Remote system (like how we compare the versions of remote system)
Could you please help me ..
Any relevant docs you can send it to [email protected]
Thanks in advance..

Hello Smriti,
          Exploding a BOM means to display all the components and sub-components for a BOM in a particular transaction (eg) VA01,CO01,ME22N etc..
You can use the SAP FM's depend on the Functionality:
CS_BOM_EXPLOSION               General BOM explosion
CS_BOM_EXPLOSION_EQUI          BOM explosion - initial screen: equipment
CS_BOM_EXPLOSION_MAT           BOM explosion (old version); as of 3.0, use CS_BOM_EXPL_MAT_V2
CS_BOM_EXPL_EQU_V2             BOM explosion for equipment
CS_BOM_EXPL_KND_V1             BOM explosion for material
CS_BOM_EXPL_MAT_V2             BOM explosion for material
CS_BOM_EXPL_PSP_V1
CS_BOM_EXPL_TPL_V1             BOM explosion for functional location
CSS7                           Explode BOM (Document)
CS_BOM_EXPL_DOC_V1             BOM explosion: document sub-assemblies
CS_BOM_EXPL_GNRL2_V1           General BOM explosion: document sub-assemblies
CSSO
CS_SO_MODE_BOM_EXPLOSION
As per Garet in response to your question better talk to the Functional team to get the better underatanding for your requirement.
Check the below link for more details on BOM:
http://sap-img.com/sap-sd/what-is-bom-referring-to-sap-sd.htm
Thanks,
Greetson

Role of a functional consultant in an upgrade project

Hello friends,
My client is planning for an upgrade of 4.7 to ECC 6.0.
Could you pls give me some info regarding the Role of a functional consultant in an upgrade project.
Naveen

The role of a functional consultant in an Upgrade depends on the scope of the project.
whether it is a Technical Upgrade or a Functional Upgrade.
Following would be some of responsibilities -
Coordinate with Client Business/Functional Team to identify critical business processes, understand the functionality of the custom developments
Overall Test Planning, Preparation of Test Plans, test scripts and executing Unit and Integration testing
Providing clarifications for functional related issues during UAT
It is is functional upgrade analyze which custom functionalities can be retired and which can be brought back to standard.
Prepare a POC on the recommended new functionalities on how these would be useful for the Client.
Training the Client super users
Preparing training documents
Analyzing the obsolete transacations and modifying the documents with the new transactions
Hope this helps you.

SAP MM Functional Consultant's role in a Upgrade Project from 4.6C to 6.0

Hi Guys,
I will be thrown into a SAP Upgrade Project. I would appreciate if someone could shed some light on what a SAP MM Functional Consultants role would be in this kind of Project.
I would appreciate a comprehensive guide where it includes role within each stage of the ASAP methodology for Upgrades.
Thanks guys.

> I will be thrown into a SAP Upgrade Project. I would appreciate if someone could shed some light on what a SAP MM Functional Consultants role would be in this kind of Project.
- defining the core processes
- test and customize them
- release the customizing transports for production
> I would appreciate a comprehensive guide where it includes role within each stage of the ASAP methodology for Upgrades.
Since each project is different and each system has a different customizing/configuration it's not possible to generate a step-by-step guide what you have to do. The requirements are usually defined by the business.
Your project leader should be able to give you a project plan (e. g. by using Solution Manager Upgrade Project) where you can get an idea based on the system you're going to upgrade.
Markus

Upgrade - Green Question mark in SPAU for Function Group

Hi,
I am facing a problem while doing upgrade to ECC 6.0.
There is a function group KYPR which has 2 function modules showing Green Question Mark.
REPORT_DIRECTORY_MAINTAIN
     REPORT_IMPORT_FOR_TRANSPORT
I tried running the background program SAPRUPGM
as suggested by SAP, but that does not solve the problem.
Also looked at some of the notes, but not able to find any appropriate solution.
Any help is appreciated.
Regards
Vinod

did you check the forum, there are many answers ? [http://www.sdn.sap.com/irj/scn/advancedsearch?query=spaugreenquestion+mark#sdn_content_category_value_forums]
Could you tell us what you tried ? (what about OSS connection test, etc.)

Function group issue in upgrade plz help very urgent

hi gurus,
plz help me
in a big trouble.
deadline is today.
when i activated the function group i found this error in an include
LSVARCLS
and when i clicked to this field it took me to another include
LSVARTOP
here i found
data: f4_params type onf4_event_parameters_type.
FYI:
types: begin of onf4_event_parameters_type.
types: c_fieldname     type lvc_fname.
types: cs_row_no       type lvc_s_roid.
types: cr_event_data   type ref to cl_alv_event_data.
types: ct_bad_cells    type lvc_t_modi.
types: c_display       type char01.
types: end of onf4_event_parameters_type.
data: f4_params type onf4_event_parameters_type.
error is :
Field "F4_PARAMS-C_FIELDNAME" is unknown. It is neither in one of the
specified tables nor defined by a "DATA" statement . . . . . . . . . .
thanks in advance

FUNCTION-POOL ZVAR MESSAGE-ID DB.
TABLES:
        TADIR,                         " Entwicklungsklasse
        TRDIR,                         " Reportcatalog
        LDBD,                          " logical databases
        VARID,                         " variant properties
        RSVAVA,                        " Variable data in
                                       " variants( sy-datum)
        RSVAR,                         " new RALDB structure
        RSVARDESC,                     " Report, Variante, Dynnr
        VARIT,                         " variants texts
        VARIS,                         " screennr per variant
        DD23T,                         "
        DFIES,                         "DD-Schnittstelle, get_field
        TPARAT,                        "Texte zu Memory-Ids
        TVARUVN, "#EC NEEDED
        SSCRFIELDS,
        t000.
DATA CHOOSE like sy-ucomm value 'PICK'.
DATA G_STATUS like sy-pfkey.
*Includes für Icons
INCLUDE .
Include für Symbole
INCLUDE .
*Equates für SSCR
INCLUDE RSDBCOM2.
*Typen für dynamische Selektionen, verwendet bei RS_REFRESH_...DYNAMICAL
TYPE-POOLS: RSDS, SYLDB, sydb0.
data: GS_TOOLBAR           TYPE STB_BUTTON.
include lsvarcls.
Key um unnoetige Datenbankzugriffe zu vermeiden
DATA: BEGIN OF CHECK_KEY,
      REPORT LIKE RSVAR-REPORT,
      VARIANT LIKE RSVAR-VARIANT.
DATA: END OF CHECK_KEY.
key für get_description
*DATA: old_key LIKE check_key.
CATALOG OF VARIANTS, OLD STRUCTURE. WILL BE DELETED BY FIRST
CALL OF VARIANTS OUT OF FUNCTIONPOOL SVAR.
INFORMATION WILL BE TRANSFERED TO VARID AND VARIT.
DATA: VARCAT LIKE RSVARC OCCURS 20 WITH HEADER LINE.
TEXT (=> VARIT)
DATA: VARCATT LIKE RVART OCCURS 20 WITH HEADER LINE.
SAVE INFORMATION ABOUT VARIANTS
DATA: BEGIN OF SAVEINFO OCCURS 20,
         NAME      LIKE RVARI-NAME,
         NUMB      LIKE RVARI-NUMB,
         PROTECTED LIKE RVARI-PROTECTED,
         FIELDTEXT LIKE RSVAR-FIELDTEXT,
         KIND      LIKE RVARI-KIND,
         TYPE      LIKE RVARI-TYPE,
         VTYPE     LIKE RVARI-VTYPE,
         VNAME     LIKE RVARI-VNAME,
       appendage I= Matchcode, C=Checkbox etc
         APPENDAGE LIKE RSVAR-INVISIBLE,
         VARIS(1),                     " TVARV, FUBAU
       N= Ausgeblendet von Report,X ausgeblendet in Variante
         INVISIBLE,
         USER,
         MEMORYID LIKE RSSCR-SPAGPA,
       nur auf einem Bild vorhanden
         GLOBAL,
         NO_IMPORT,
         SPAGPA,
         NOINTERVALS,
         OBLIGATORY LIKE RSVAR-OBLIGATORY,
         RADIO,
     END OF SAVEINFO.
DATA: BEGIN OF SAVEINFO_DYN OCCURS 10,
        TABLENAME LIKE RSDSTABS-PRIM_TAB,
        FIELDNAME LIKE RSDSTABS-PRIM_FNAME,
        FIELDTEXT LIKE RSVAR-FIELDTEXT,
        TYPE      LIKE RVARI-TYPE,
        VTYPE     LIKE RVARI-VTYPE,
        VNAME     LIKE RVARI-VNAME,
        VARIS(1),
        PROTECTED LIKE RVARI-PROTECTED,
        GLOBAL(1).
DATA: END   OF SAVEINFO_DYN.
data: saveinfo_sav like saveinfo occurs 0 with header line.
data: saveinfo_dyn_sav like saveinfo_dyn occurs 0 with header line.
key for import of variants from VARI
DATA: BEGIN OF $RKEY,
        REPORT LIKE RSVAR-REPORT,
        VARIANT LIKE RSVAR-VARIANT,
      END OF   $RKEY.
vari
DATA: L_VARI LIKE RVARI OCCURS 20 WITH HEADER LINE.
%_SSCR
DATA SELCTAB LIKE RSSCR OCCURS 20 WITH HEADER LINE.
DATA GLOB_SUBMODE(2).
DATA LOC_SUBMODE(2).
screenfields
DATA: XCODE(4).
DATA: FCODE(4)      TYPE C,
      FUNC(4)       TYPE C.
DATA: BEGIN OF INFO OCCURS 20,
        FLAG,
        OLENGTH TYPE X,
        LINE LIKE RSVAR-INFOLINE,
      END OF INFO.
DATA: VALUTAB LIKE RSPARAMSL OCCURS 40 WITH HEADER LINE.
Zur allgemeinen Verwendung
FIELD-SYMBOLS: .
DATA ILLEGAL_CHAR.                     " Wrong sign in variant
copy
DATA: VARIANT2 LIKE RSVAR-VARIANT,
      VARIANT1 LIKE RSVAR-VARIANT.
*list of parameters and select-options, screenobjects
DATA: L_SELOP LIKE VANZ OCCURS 20 WITH HEADER LINE.
DATA: L_SELOP_NONV LIKE VANZ OCCURS 20 WITH HEADER LINE."nonv = non visi
DATA: L_PARAMS LIKE VANZ OCCURS 20 WITH HEADER LINE.
DATA: L_PARAMS_NONV LIKE VANZ OCCURS 20 WITH HEADER LINE.
DATA: SCREENOBJECTS LIKE VANZ OCCURS 20 WITH HEADER LINE.
list of all variants concerning one report
DATA: BEGIN OF VARI_LIST OCCURS 40,
            MARKFIELD LIKE RSVAR-MARKFIELD,
            VARIANT   LIKE RSVAR-VARIANT,
            TEXT      LIKE RVART-VTEXT,
            ENAME     LIKE RSVARC-ENAME,
            AENAME    LIKE RSVARC-AENAME,
            PROTECTED LIKE RSVARC-PROTECTED,
            ENVIRONMT LIKE RSVARC-ENVIRONMT,
            XFLAG1    LIKE VARID-XFLAG1.
DATA: END OF VARI_LIST.
*Variablen für das Blättern auf den Dynpros 1303 und 306.
DATA: VARI_LIST_SCROLL LIKE SY-STEPL VALUE '1'.
DATA: SAVE_OKCODE(4).
table for Dynpro 306 (delete variants)
DATA: BEGIN OF H_VARILIST OCCURS 30,
            MARKFIELD LIKE RSVAR-MARKFIELD,
            FLAG1     LIKE RSVAR-FLAG1,
            FLAG2     LIKE RSVAR-FLAG2,
            FLAG3     LIKE RSVAR-FLAG3,
            VARIANT LIKE RSVAR-VARIANT.
DATA: END OF H_VARILIST.
CONSTANTS: C_PDLIST_WIDTH TYPE I VALUE '24',
           C_VARILIST     TYPE I VALUE '10'.
DATA: CATTOP LIKE SY-TABIX VALUE '3'. "lines top-of-page in CATALOG.
*data: listtop like sy-tabix value '3'. "lines top-of-page in Delete
"vari
DATA: PRINT_ALL_VAR.                   "alle Varianten drucken
DATA: PRINT_CAT_VAR.                   "Katalog drucken
Systemumgebung
DATA ENVIRONMENT.                      " S: SAP, C: Customer
Dynpro 320
DATA : TEXT0(59).
*Tables and fields for fitting variants
*table of variants which must be fitted
DATA: BEGIN OF FIT_VAR OCCURS 50,
       VARIANT LIKE RSVAR-VARIANT,
       FLAG(1).                        " flag = 'X' => Variante can't be
DATA: END OF FIT_VAR.                  "fitted.
DATA: BEGIN OF SINGLE_OPTIONS OCCURS 8,
       OPTION(2),
        TEXT(18).
DATA: END OF SINGLE_OPTIONS.
variants which contain variables
internal table, per line select-options and parameters which
use variables
DATA: BEGIN OF VARIVAR OCCURS 20,
        SELNAME     LIKE RSSCR-NAME,
        SELTEXT     LIKE RSVAR-FIELDTEXT,
        KIND        LIKE RVARI-KIND,
        TYPE        LIKE RVARI-TYPE,
        VTYPE       LIKE RSVAR-VTYPE,
        VTEXT       LIKE RSVAVA-VTEXT,
        FB,
        TVARV,
        VNAME       LIKE RSVAR-VNAME,
        OPTION      LIKE RSVAR-OPTION,
        SIGN(1),
        INFO_TABIX LIKE SY-TABIX,
        DATES_TABIX LIKE SY-TABIX,
        USER,
        MEMORYID LIKE TPARA-PARAMID,
     END   OF VARIVAR.
DATA: BEGIN OF VARIVAR_DYN OCCURS 20,
        TABLENAME LIKE RSDSTABS-PRIM_TAB,
        FIELDNAME   LIKE RSDSTABS-PRIM_FNAME,
        KIND        LIKE RVARI-KIND,
        TYPE        LIKE RVARI-TYPE,
        VTYPE       LIKE RSVAR-VTYPE,
        VTEXT       LIKE RSVAVA-VTEXT,
        FB,
        TVARV,
        VNAME       LIKE RSVAR-VNAME,
        OPTION      LIKE RSVAR-OPTION,
        SIGN(1),
        INFO_TABIX LIKE SY-TABIX,
        DATES_TABIX LIKE SY-TABIX,
     END   OF VARIVAR_DYN.
DATA: VARIDATE_S LIKE RSVARIVAR OCCURS 20 WITH HEADER LINE.
Tabelle der möglichen Datumsberechnungen für Variablen in Varianten
Parameter
DATA: VARIDATE_P LIKE RSVARIVAR OCCURS 20 WITH HEADER LINE.
table of possible TVARV-variables (parameters)
DATA: TVARV_P LIKE TVARV OCCURS 20 WITH HEADER LINE.
table of possible TVARV-variables (select-options)
DATA: TVARV_S LIKE TVARV OCCURS 20 WITH HEADER LINE.
description of fields VARIDATES
DATA: FIDESC_DATES LIKE RSVBFIDESC OCCURS 5 WITH HEADER LINE.
description of fields TVARV
DATA: FIDESC_TVARV LIKE RSVBFIDESC OCCURS 5 WITH HEADER LINE.
description of fields OPTION
DATA: FIDESC_OPTION LIKE RSVBFIDESC OCCURS 5 WITH HEADER LINE.
description of fields OPTION
Feldtabelle für DYNP_VALUES_READ/UPDATE
DATA DYNPFIELDS LIKE DYNPREAD OCCURS 50 WITH HEADER LINE.
*desctab
DATA: DESCTAB LIKE RSBREPI OCCURS 20 WITH HEADER LINE.
*Hilfsfelder für Übergabeparameter
DATA:G_SUBRC LIKE SY-SUBRC,
     L_RC LIKE SY-SUBRC.
*Hilfsfelder für Sperren
DATA: G_ENQSUB LIKE SY-SUBRC.
*Hilfsfeld für mandantenabhängiges Löschen von Varianten
DATA: DEL_ALL_VAR. "=X alle Mandanten, =' ' nur aktueller Mandant
select variant form list.
DATA: BEGIN OF VARIANT_TABLE OCCURS 30,
      VARIANT LIKE RSVAR-VARIANT,
      TEXT LIKE VARIT-VTEXT,
      ENVIR LIKE VARID-ENVIRONMNT,
      ENAME LIKE VARID-ENAME,
      AENAME LIKE VARID-AENAME,
      aedat like varid-aedat,
      MLANGU LIKE VARID-MLANGU,
      protected like varid-protected,
      SELSCREEN(80).                  "<= 20 Bilder
DATA: END OF VARIANT_TABLE.
DATA: CALL_FLAG.                             "screen 305.
DATA: MODE_FLAG.
Print variants screen 308
DATA: PRINT_LIST LIKE RSREPVAR OCCURS 30 WITH HEADER LINE.
parameters in variables
DATA: BEGIN OF VARIVDAT OCCURS 5,
            SELNAME LIKE RVARI-NAME.
            INCLUDE STRUCTURE RSINTRANGE.
DATA: END OF VARIVDAT.
DATA: VARIVDAT_WORK LIKE VARIVDAT OCCURS 10 WITH HEADER LINE.
DATA:EXC_SUBC LIKE SY-SUBRC.
DATA: BEGIN OF LDB_VARIVAR OCCURS 10,
               MARKFIELD LIKE RSVAR-MARKFIELD,
               VTEXT     LIKE RSVARIVAR-TEXT,
               VTYPE     LIKE RSVAR-VTYPE.
DATA: END OF LDB_VARIVAR.
*generate subroutinepool
DATA: BEGIN OF REPDAT_TAB OCCURS 40,
         LINE(72),
      END OF REPDAT_TAB.
*Tabelle zur Übergabe der alten Selektionswerte wenn sich
*Parameter oder Select-Options geändert haben.
*Wird von rs_variant_obsolet benötigt.
DATA: OLD_SELECTIONS LIKE RSPARAMSL OCCURS 20 WITH HEADER LINE.
*Flag für Aufruf aus QUERY und Report-Writer.
*Reportname auf Einstiegsbild nicht sichtbar (not_visible = x)
DATA: NOT_VISIBLE.
*Varianten für Query
DATA: QUERY_SYSVAR.
*Einstiegsbild mit anderem Titel aufrufen.
DATA: N_TITLE(40).
*F4 Hilfe RS_VARIANT_CATALOG mit anderem Titel aufrufen
DATA: G_TITLE like sy-title.
*Unterscheidung auf Listdynpro (hauptsächlich 307)
DATA: CALLER(4).
*sy-subrc Felder für Import und Export.
DATA: EXP_SUBRC LIKE SY-SUBRC,
      IMP_SUBRC LIKE SY-SUBRC.
*Tabellen für dynamische Selektionen
DATA: DYNSEL_DESC LIKE RSDYNBREPI OCCURS 5 WITH HEADER LINE.
DATA: DYNS_FIELDS LIKE RSDSFIELDS OCCURS 5 WITH HEADER LINE.
DATA: DYNSEL_VALUE LIKE RSSELDYN OCCURS 5 WITH HEADER LINE.
*tabellen für matchcodeselection
DATA: BEGIN OF MC_DESC OCCURS 5,
             NAME    LIKE RSSCR-NAME,
             ID      LIKE MCPARAMS-MCID,
             OBJECT(10),
             S_STRING LIKE MCPARAMS-STRING,
             D_TEXT   LIKE DD23T-MCTEXT,
             FROM     LIKE VANZ-FROM,
             TO       LIKE VANZ-TO.
DATA: END   OF MC_DESC.
*Tabelle für Umsetzung dynamische Selektionen
*flag = space -> umgesetzt
*flag = G     -> Variante z.Z gesperrt
*flag = I     -> Fehler beim Import
DATA: BEGIN OF CHANGED_VARIANTS OCCURS 10,
               NAME LIKE RSVAR-VARIANT,
               FLAG.
DATA: END OF CHANGED_VARIANTS.
*Feld für Ikonen auf Dynpros.
DATA: IKON(8).
*Konstanten für Ikonen
CONSTANTS: POP_WARNING(8) VALUE '@1A@',
           POP_ERROR(8) VALUE '@1B@',
           POP_INFO(8) VALUE '@19@',
           POP_COPY(8) VALUE '@14@',
          c_icon_enter_more(15) value 'ICON_ENTER_MORE',
           C_ICON_DISPLAY_MORE(17) VALUE 'ICON_DISPLAY_MORE'.
DATA: MORE_ICON LIKE RSSELINT-OPTI_PUSH.
*Konstanten für Variante ändern, Werte oder Attribute
CONSTANTS: C_VAL VALUE 'V'.
Interne Tabelle für Transport
DATA: BEGIN OF REP_VAR OCCURS 10,
        MARKFIELD.
        INCLUDE STRUCTURE $RKEY.
DATA: END   OF REP_VAR.
DATA: REP_VAR_CURSOR LIKE SY-INDEX VALUE 0.
Tabelle für RS_SELOPT_INFO -> BBS
DATA: DEFAULTS LIKE RSPARAMSL OCCURS 10 WITH HEADER LINE.
Tabelle für Werteanzeige Tvarv.
DATA: TVARVTAB LIKE TVARV OCCURS 10 WITH HEADER LINE.
SUBTY-Equates
INCLUDE RSDBCSTY.
Textfeld für Dynpro 317.
DATA: TEXT(4).
Konstante für Namenskonvention Systemvariante
CONSTANTS: SYS_VNAME(4) VALUE 'SAP&'.
CONSTANTS: CUS_VNAME(4) VALUE 'CUS&'.
Flag für Systemvariante gewünscht.
DATA: C_SYSVAR.
data vari_mandt like sy-mandt.
data sysvar_mandt like sy-mandt value '000'.
Check für Systemvariante
DATA: SYSVAR_FLAG.
Flag für Entwicklungsklasse , Werte Y oder N (aus get_devcalss)
DATA: NON_LOCAL VALUE 'Y'.
DATA: TABIX LIKE SY-TABIX.
*Strutur für freie Abgrenzungen.
DATA: VARIDYN LIKE RSVARIDYN OCCURS 10 WITH HEADER LINE.
DATA: VDATDYN LIKE RSVDATDYN OCCURS 10 WITH HEADER LINE.
DATA: VARIVDAT_DYN LIKE RSVDATDYN OCCURS 10 WITH HEADER LINE.
DATA: BEGIN OF VARIVDAT_DYN_WORK OCCURS 10,
         TABLENAME LIKE RSVARIDYN-TABLENAME,
         FIELDNAME LIKE RSVARIDYN-FIELDNAME.
         INCLUDE STRUCTURE RSINTRANGE.
DATA: END OF VARIVDAT_DYN_WORK.
CONSTANTS: NO_IMPORT VALUE SPACE.
Teilt IM/EXPORT_VARIANT_STATIC mit, welche übergebeneb Objekte
im/exportiert werden sollen.
DATA: BEGIN OF IMEX,
          VARI,
          DYNS,
        END   OF IMEX.
Tabelle für Selektionsbildnummern
DATA: DYNNR LIKE RSDYNNR OCCURS 10 WITH HEADER LINE.
DATA: BEGIN OF CHOOSE_DYNNR OCCURS 10,
        MARKFIELD.
        INCLUDE STRUCTURE RSDYNNR.
DATA: END OF CHOOSE_DYNNR.
Sichern vom Selektionsbild, RSVAR_VARIANTT zurücksetzen
DATA: FLAG_FIRST.     "#EC NEEDED
DATA: FLAG_PROTECTED. "#EC NEEDED
Daten für CALL SELECTION SCREEN Varianten
DATA: HIDE_FLAG.
DATA: LINE_NUMBER LIKE SY-TABIX.
DATA: VARISCREENS LIKE RSDYNNR OCCURS 10 WITH HEADER LINE.
data: variscreens_sav like rsdynnr occurs 10 with header line.
DATA: FLAG_1000.
DATA: DYNNR_TFILL LIKE SY-TFILL.
DATA: VARISCREENS_TFILL LIKE SY-TFILL.
DATA: DMORE_ICON(40).
DATA: BEGIN OF GLOBAL_OBJECTS OCCURS 10,
          NAME LIKE RSSCR-NAME,
      END   OF GLOBAL_OBJECTS.
DATA: BEGIN OF DYN_TAB OCCURS 10,
            DBFIELD LIKE RSSCR-DBFIELD,
      END   OF DYN_TAB.
CONSTANTS: C_P_COLUMN TYPE I VALUE 38,
           C_I_COLUMN TYPE I VALUE 41,
           C_N_COLUMN TYPE I VALUE 44,
           C_S_COLUMN TYPE I VALUE 47,
           C_W_COLUMN TYPE I VALUE 50,
           C_M_COLUMN TYPE I VALUE 53,
           C_O_COLUMN TYPE I VALUE 56,
           MAX_WIDTH_ATTR TYPE I VALUE 77.
CONSTANTS: MAX_WIDTH_SELVAR TYPE I VALUE 57.
DATA: FLAG_NOIMPORT.
DATA: CURR_STATUS(4).
DATA: SCREEN_TITLES LIKE RSSCRITLE OCCURS 10 WITH HEADER LINE.
RANGES V_RANGE FOR VARID-VARIANT OCCURS 10.
DATA: FLAG_ALL_SCREENS.
CONSTANTS: C_LOW TYPE I VALUE 34,
           C_HIGH TYPE I VALUE 58,
           C_TO   TYPE I VALUE 54,
           C_OUTPUT_LENGTH TYPE I VALUE 26,
           C_DISPLAY_LENGTH TYPE I VALUE 87,
           C_DISPLAY_LENGTH_ATTR TYPE I VALUE 104,
           C_DISPLAY_LENGTH_CAT TYPE I VALUE 118,
           C_NO VALUE '0',
           C_DYNNR LIKE SCREEN-NAME VALUE 'RSVAR-DYNNR',
           C_ICON_MORE LIKE SCREEN-NAME VALUE 'DMORE_ICON',
           C_SCREEN_1000 LIKE SY-DYNNR VALUE '1000'.
DATA: BELONGING_DYNNR LIKE RSDYNNR OCCURS 10 WITH HEADER LINE.
DATA: PREFIX(20).
DATA: D_320_TEXT(35).
DATA: OLD_VARI LIKE RSVAR-VARIANT.
DATA: L_SUBMODE LIKE GLOB_SUBMODE.
DATA: ICON_1(40), ICON_2(40), ICON_3(40).
DATA: FLAG_ICON_1, FLAG_ICON_2, FLAG_ICON_3.
DATA: FLAG_CALLED_FROM_SELSCREEN.
DATA: VARIVAR_TEXT LIKE RSVAVA-VTEXT.
DATA: VARIVAR_KIND LIKE RSSCR-KIND.
DATA: LIST_LINE LIKE SY-LILLI.
DATA: MOD_LINE LIKE SY-LILLI.
DATA: G_SP TYPE SYLDB_SP.
DATA: G_RANGE TYPE RSDS_RANGE,
      G_FRANGE TYPE RSDS_FRANGE,
      G_RSDSSELOPT LIKE RSDSSELOPT.
DATA: G_ILL_CHAR.
DATA: FLAG_CHANGE_VARIANT.
DATA: EXIT_FLAG.
DATA: COMP_NODI_NAME LIKE RSSCR-NAME.
DATA: EXCLUDE LIKE RSEXFCODE OCCURS 0 WITH HEADER LINE.
hidefelder für Attributebild.
DATA: HIDE(10).
Feldbeschreibung aufgeklappt oder zugeklappt
DATA: STATE(4).
DATA: NO_DISPLAY_VISIBLE TYPE BOOLEAN VALUE 'F'.
DATA: READ_LINE LIKE SY-INDEX.
CONSTANTS: C_COLLAPSE(4) VALUE 'COLL',
           C_EXPAND(4)   VALUE 'EXPA',
           C_TRUE VALUE 'T',
           C_FALSE VALUE 'F'.
CONSTANTS: CAT_LINE_SIZE TYPE I VALUE '127'.
DATA: G_EXPOREP TYPE SY-REPID.
DATA: SUBSCREENPROG LIKE SY-REPID,
      SUBSCREENDYNNR LIKE SY-DYNNR.
data: g_subc like trdir-subc.
data: status_for_subscreens.
Data for subscreen processing
data: begin of g_subscreen,
        ucomm type syucomm,
        submode(2),
        total type i,
        current type i,
        exclude type rsexfcode occurs 0,
        rkey type rsvarkey,
        variscreens type rsdynnr occurs 0,
        sscr type rsscr occurs 0,
     end   of g_subscreen.
INCLUDE SVARSELO.
Daten für ALV-GRID
data:
GT_TOOLBAR_EXCLUDING TYPE UI_FUNCTIONS,
GRID1                TYPE REF TO CL_GUI_ALV_GRID,
GRID2                TYPE REF TO CL_GUI_ALV_GRID,
alv_fieldcat         TYPE LVC_T_FCAT WITH HEADER LINE,
EVENT_RECEIVER1      TYPE REF TO CL_EVENT_RECEIVEr1,
selected             value 'X',
alv_layout           TYPE LVC_S_LAYO,
alv_STABLE type LVC_S_STBL,
ROW_TABLE            TYPE LVC_T_ROW        WITH HEADER LINE,
alv_container_1      type REF TO CL_GUI_CUSTOM_CONTAINER,
alv_container_2      type REF TO CL_GUI_CUSTOM_CONTAINER.
constants: c_search value 'S'.

4.6 C to ECC 6.0 Upgrade Project Timeline Sheet in MPP format

Dear all,
We are now proposing our customer for the 4.6c to ECC 6.0 Upgrade.
Our customer is currently in 4.6c/oracle 9i/HPUX 11 i. He wants to move to ECC 6.0.
If you have the project timeline for the above Technical Upgrade, can you pl send it to me.
If you don't have in MPP format atleast send me the Work Breakdown structure with timelines.
I shall modity the same to our customer and submit
Thanks & Regards
Senthil
[email protected]

Preparation Phase* 6 days
Kick Off Meeting 1 day
Upgrade Project Procedures Preparation 1 day
Prepare Upgrade Project Plan 1 day
Technical Requirements Assessment 3 days
Assess Training needs of Key-users & End-users 1 day
Prepare Detailed Basis Activity List for DEV, QA & PRD 1 day
Business Blueprint Phase 6 days
Develop System Landscape Upgrade Plan 1 day
Functional Requirement Checklist 1 day
ABAP Development check list 1 day
Develop detailed Training Procedures & Documentation for Key Users & End Users 1 day
Identify Testing Scope & Scenarios 1 day
Identify Authorizations Conversion to Roles for SAP ECC 6.0 2 days
Develop Documents as per Basis Activity List 1 day
Develop Authorization Matrix for Activity Groups to Roles Conversion 2 days
Prepare Upgrade Deliverables Checklist 1 day
Realization Phase 28 days
Installation of Solution Manager 3.2 System 1 day
Creation of New Development System for Upgrade Project (Homogenous System Copy - PRD) 2 days
Upgrade to AIX & Oracle 10g, SAP ECC 6.0 on New Development Server 3 days
Upgrade Frontend Software 4 days
Perform SPAU & SPDD Corrections 5 days
Perform ABAP Development & Corrections 10 days Perform Authorizations Conversions and corrections after upgrade 8 days
Perform Upgrade Testing for each Application Module 7 days
Perform Unit & Integration Testing 6 days
Perform Training to Key Users & End Users (Generic & Specific) 3 days
Upgrade to AIX, Oracle 10g, SAP ECC 6.0 on Quality System 1 day
Homogenous System Copy of PRD to New Quality & Upgrade to AIX, Oracle 10g & SAP ECC 6.0 2 days Perform Testing in Quality System 3 days
Testing by end users on Quality System 1 day
Production Realization & Go-Live Phase 6 days
Upgrade to Production System Operating System to AIX (after close of business hours - 23:00) 1 day
Oracle Upgrade to 10g (after close of business hours - 23:00) 1 day
SAP Release Upgrade to ECC 6.0(Downtime Minimized - Downtime occurs in non-business hours) 2 days
User Acceptance Testing 1 day
Production System Go-Live 1 day
Post Go-Live Support 14 days
Post Go-Live Support 14 days Note: This is high level plan subject to change during Business Blue Print Phase 0 days
This is taken from a post in Ittoolbox, May be this is generic. Hope you can tailor this to meet your requirements.

Experts pls guide me function group problem

Hi Experts
plz help me i have an issue regarding a function group
i m in a upgrade project from 4.6c to 6.0
in 4.6 there is a function group named svar we made a copy of it an did som customisation for our use
in ecc 6.0 SAP have made some major changes in svar
as zvar is also calling one of the include of svar which is LSVARCLS so it is affecting our zvar too
what i want
i want to keep all my customisations of 4.6 and also want to add the new functionality added by sap in the newer version
i heard a term called regeneration of zvar which is for this purpose only
so experts plz tell me what is this regeneration ?
does it exists?
if it exist how i can do it
thanx in advance

Hi Anit,
The best way in such cases is copy the standard program once again lets say ZVAR1.
Now identify the diffences between SVAR (Old version) and ZVAR and include all those changes in ZVAR1 and use ZVAR1.
Reward points if useful.
Regards,
Atish

Upgrade from CRM 4.0 sp6 to CRM 2007

We are in the process of upgrading our sandpit from CRM 4.0 sp 6 to CRM 2007 as part of an overall CRM upgrade project. The technical upgrade phase went fine we now have the sandpit running some of the standard delieved business roles etc. My question is with respect to my original customizing:
- what customizing/configuration needs to be redone
- what needs to be adjusted.
- what is no longer relevant
Is there any documentation out there that deals with addressing this topic. Can anyone share their experiences.
We have a number of different Web based interaction centers some dealing with order taking in place in our original installation.
Thanks in advance
Eddie

Eddie,
The rule of thumb is the following:
- All UI based modifications/configurations/enhancements done in the lower release, must be redone in the new release. Classic example is you removed fields from a screen or added new fields. You also lose all your UI work done in CRM 40.
- All non-UI based config/development that is in the business layer of the system should be fine, and may need some minor adjustments, but you should be able to keep this. You probably though will have to redo some of your IC config as there were functional changes between releases. I don't think however you will find that the configuration adjustments to take a lot of time
- The old PCUI/IC webclient and SAP GUI applications(for data entry) are no longer relevant.
Take care,
Stephen

System error: Error when copying parameter function group CR01

Dear friends
I am getting the above error while doing the Backflushing in REM.
It occurs when backflushed quantity is issued ,and while confirming the
ACTUAL ACTIVITES above error occurs..........
We have upgrade the system from SAP 4.7 to ECC6.0.
It is giving some error in CRM system but we don't have CRM system.......
Message displayed is as below..................
System error: Error when copying parameter function group CR01
     Message no. CR085
Diagnosis
     Internal error.
Procedure
     Repeat the transaction.
     If the error occurs and you have a CRM System connected to your ERP
     System, the document may have been archived in the CRM System.
     If the error occurs again, inform your system administrator. If the
     error cannot be corrected, call the SAP Hotline directly. Describe which
     steps preceeded the error.
Thanks& Regards
Sandeep
Message was edited by:
        Sandeep Bhowmick

Hi Sandeep
Standard R/3 does not allow backflush without any operation. You need to have an operation to do a backflush.Error message CR 085 is issued because there is no operation in the routing of the material backflushed. System should issue an error when no operations are found in routing. Although, error message CR 085 is not correct, more appropriate message RM 824 for this a program correction is requried check note (691161).
Regards
Prasad
Reward if useful

Going live check for SAP upgrade projects

Hello,
I am interested in "going live check" service and procedures for my upgrade projects. May I find any documentation? Do I have to pay for it?..
Thanking you in advance and a happy new years!
Kind regards
Nilüfer Çalışkan

Hi Nilufer,
The following Input as follows :
Source : http://www.thespot4sap.com/upgrade_guide_v2.pdf
This service is included as part of your annual maintenance fee.
The underlying concept of the SAP GoingLive Functional Upgrade Check is
to ensure smooth operation of your mySAP.com solution by taking action
proactively, before severe technical problems occur.
The GoingLive Functional Upgrade Check is made up of three sessions
(Planning, Analysis and Verification)two sessions (Planning and Analysis)
before the upgrade and the other (Verification) after the upgrade.
Planning Session: This session should be performed as much in advance as
possible when the upgrade is first being considered.
Analyses compatibility for the target release with regards to connected
systems in the Solution Landscape, OS version, DB version, installed Add-
Ons, Plug-ins, Country Versions, and so on.
Analysis Session: It is generally performed two months before the
production upgrade (consider lead time for hardware procurement).
The focus is on resource planning and system configuration.
There is a high-level hardware plausibility check (this is not a hardware
sizing exercise).
Potential resource bottlenecks are identified.
Necessary changes will be recommended to prepare the system for the
productive use of the new release.
38 SAP Upgrade Guide | Simplifying Your Upgrade
Verification Session: Generally performed four to six weeks after the
production upgrade, and the recommendation from the analysis session
implemented.
Comparison of performance with results prior to upgrade
Recommendations on configuration and optimization
More information and ordering . For more information, see the GoingLive
Functional Upgrade Check web page at:
<b>http://service.sap.com/goinglive-fu</b>
To order a GoingLive Functional Upgrade Check, contact SAP Customer Care
Center at least eight weeks prior to the planned upgrade of your production
system.
For customers of value-added resellers (VARs) such as CBS customers in the
US, special conditions apply. Contact your VAR.
Remote Upgrade Service
Remote Upgrade Service is a technical upgrade that is performed by SAP
remote consultants. Pricing is based on the complexity of the customers
environment.
SAP performs the technical upgrade of your system, allowing you to focus on
the functional and training side of the upgrade. You are still responsible for
resolving object conflicts.
See SAP Notes 106447 and 84044.
The Remote Upgrade Service is an attractive option for CBS sized customers
with small or non-existent mySAP Technology group.
For more information see the Remote Upgrade Service web page at:
http://service.sap.com/remoteupgrade
Resources
The following list shows some of the resources you can use as you prepare for
your upgrade of SAP. These resources include:
Your installation partner
Customers and others you have networked with at customer functions and
conferences such as:
ASUG
Hope this Info helps you.
<i>Advanced New Year wishes.</i>
Br,
Sri
Award points for helpful answers

Prerequisites for Upgrade Project

Hi Folks,
Being im a functional consultant - I woudl like to know the activities involved in CRM Upgrade project from 4 to 7.
I will be looking forward for the Prerequisites activites which needed to take care before starting the project.
Thanks in Advance
Amrita.

Hi Amrita,
We need to carry out a set of activites before kicking off the upgrade project from CRM 4.0 to CRM 7.0.
We need to validate whether the current 4.0 system is an unicode or non-unicode system and then plan for the conversion of the system to unicode as SAP CRM 7.0 only supports unicode format.
Please find below the links which would give you more information on the CRM upgrade from 4.0 to 7.0.
Comparision of functional areas can be found in CRM Master Upgrade Guide : https://websmp109.sap-ag.de/crm-inst
Gude for upgrade tasks can be found under : http://wiki.sdn.sap.com/wiki/display/CRM/General+Documents ( Link : SAP CRM 4.0 upgrade to 7.0 Guide for typical upgrade tasks )
Please let me know if you are looking out for any furhter specific information.
Best Regards,
Vamsi.

Upgrade Project: CRM Function Groups

Similar Messages

Maybe you are looking for