HR module upgrade 4.6c to ECC 6.0

Hi Experts,
I would like to know how is SAP HR module upgrade from 4.6c to ECC 6.0 different from other modules?.
Whether there are any specific tools needed to upgrade HR Module?.
I was part of successful upgrades from 4.5b,4.6c to ECC 6.0 where HR module was not involved.
Best Regards,
Krishna

Hi NK,
You can go through this link:
http://solutionbrowser.erp.sap.fmpmedia.com/Default.aspx
Cheers,
D_F

Similar Messages

Recommandations for upgrading from 46C to ECC 6.0

Hello
Our SAP system landscape is actually in 46c and is only composed of 3 servers with almost 40 users declared (25 actives) on production system. Modules FI/CO HR MM are actually implemented.
We plan to upgrade the system to ECC 6.0 between March and August of 2009. The evaluation of the upgrade should begin as soon as possible. Do you think it can be possible to realise the upgrade alone, without the help and expertise of a SAP consultant? Do you think the delay for preparing the upgrade is suffisant?
Thank you.

As suggested earlier, refer to Master and technological guides for reference.
also for information, the upgrade can fall under any below scenarios.
1. Strategic Business Improvement
Focus on functionality extension and improvement
Enablement of new and optimized business processes and scenarios based on new ERP core functionality
2. Functional/Retrofit Upgrade
New functionality to be implemented as part of the upgrade, modification clearing
Focus on reduction of system complexity
3. Technical Upgrade
Focus on pure technology upgrade
Retain functionality used
Review Usage of custom developments
As per the requirement. knowledge and experience the decision can be made.

Need knowledge on sap upgrade 4.7 to ecc 6.0 in abap reports and sap query

please give me some ideas and useful links on sap upgrade 4.7 to ecc 6.0 in abap reports and sap query

Hi Jaya,
Not very clear with your question.
Are you looking for changes in areas od ABAP reports & SAP query when we upgrade SAP from 4.7 to ECC 6.0 ??
If the response is YES, then please refer to SAP solution browser www.sapsolutionbrowser.com
Define source release and target release .
You will get module wise details on new features for target release.
Hope this helps.
Regards,
Deepak Kori

Upgrade 4.7 to ECC 6.O (FI/CO)

Dear All,
Can please someone suggest what are the best approach or step should be taken care while upgrade 4.7 to ECC 6.0 from FI and CO prospective, is any best practice available in that context .
Thanks for Help.
N
Moderator: Please, search SDN

Hi,
basically you focus on ECC 6 has new gl ledger concept which is different for 4.7
version in the folloiwng manner & Tax structure also. In ecc6.0 its different form 4.7.
1. It enables Business area posting - Segment reporting made easy
2. Profit centre accounting is through new GL
3. Split of entry to post assets and liabilities to respective profit centres. (Balance sheet items)
4. Enables commitment of FM

Function module does not exist in ECC 6.0

Hi All,
These two below function module does not exist in ECC 6.0 but exist in 4.6.Could you please let me know replacement of these two's.
FI_DOCUMENT_ARCH_READ_SINGLE
CHECK_IBAN_ACTIVE
Thanks
Mohit

Hi,
Thanks for your reply.Could you please give me example that how to use it.
Thanks
Mohit

Error in upgrade from 46c to ecc 6.0

hi experts,
we are facing an error at the time of upgrade from 46c to ecc 6.0 in the phase JOB_RSUPGAIMEXE.
did anyone face this error anytime during upgrade on windows plotform?
Please let us know your comments..
regards
raghu

Hello,
Can you please look in the /put/log directory and copy the error from the appropriate log file. You should find a log file with a name similar the to upgrade phase that is causing the error.
Thanks
N.P.C

SAP Security Upgrade 4.6C to ECC 6.0

Hello Gurus,
we are upgrading our systems to ECC 6.0 from 4.6C.
in SU25 step, do i need to manually go into every role and find the differences in Field values ?
there are more than 2500 roles and its becoming tedious task.
Is there any easy or other procedure available for the same ?
Regards,
Chaitanya

There are many tricks you can use to shave a role upgrade down to about 2 day's work, but day 1 is during the implementation design way back when to consider upgrades much later on...
Just knowing that you have 18k roles and 2500 turned red in step 2a is not enough infos to give you any efficient advice (I am not talking about your time... ;-).
What is however obvious is that between 2a and 2c there is 2... ah...?!?! That is your next closest catalyst, but dont hit the "accept SAP data" button unless you have not done any changes in SU24!
Some other key figures for upgrades are:
- Number of roles with distinctly different menus.
- Number of changed auths which are not copies.
- Number of manual auths needing manual adjustments.
- Obsolete and disabled objects.
- Security patches for unnoticed missing auth-checks.
- Cut-over, development freeze and parallel maintenance time period.
Cheers,
Julius

Upgraded our system from ECC 6 to 6.04 (EHP4).

Dear All,
We have upgraded our system from ECC 6 to 6.04 (EHP4).
There are many request in old development server which are in local request now .
We want to transport those requests to new development server which is upgraded one.
Can any one let me know is there any standard way of transporting these requests from old Development system (6)to new one(6.04).
Thanks
Anuradha

Hi Sahil,
Looks like latest EHP installer concentrate more on downtime minimize strategy. We have only 3 options available as follows.
1. Standard resource use
2. High resource use
3. Manual selection
Please take a look at below thread. Let's see what other experts comment on this.
/thread/1458520 [original link is broken]
Thanks,
Siva Kumar
Edited by: Siva Kumar Arivinti on Nov 19, 2011 7:57 PM

SAP R/3 System analysis before upgrade 4.6C -- SAP ECC 6.0

Hello!
Before the upgrade from R/3 4.6C to ECC 6.0 I would like to execute SAP R/3 system analysis.
The following functions should be included in this program:
- detailed analysis of system modifications (effort driver and risk factor during an Upgrade)
- comparison against a SAP ERP 6.0 reference system
- extension SAP tools, including RBE and conflict lists (SPAU/SPDD)
- syntax analysis of program code with respect of adjustement need
- quality control of own development
- control of amount of transports within different company areas
- control of user information, such a user type, logon date, etc.
- basic control, whether a sufficient authorization concept is available
- Identification of objects that should be considered for the archiving in oder to decrease the db-size
My question are:
- which tasks can be convered with SAP standard transactions what are the names of the transactions?
- which effort do I investigate for these tasks?
Thank you very much!
regards

Dear Thom,
To know the functionality changes u can refer http://solutionbrowser.erp.sap.fmpmedia.com/
http://www.sap.com/solutions/business-suite/erp/pdf/BWP_ERP2006_Upgrade.pdf
http://service.sap.com/releasenotes and http://service.sap.com/upgrade for functional changes.
Need to consider the following things:
For Reportsits custom developed program so unless there is any kind of change in requirement from the client regarding the layoutnothing needs to be changedI think it will work fine in ECC 6.0 toexcept few things may needs to be changed..so you need to discuss whether they want the reorts as it is right nowor want to change the layout (adding some new info/fields etc) of any reportso u need to modify the program for thoseand estimate accordinglyfor a medium complexitys Report dev it takes approx 9 pd (FRSTDSCoding+Unit Testing)so to modify it will be less than that (depending upon the scope of changes)
Now say for Batch Inputs(interface/Data Migration) using BDCyou need to see how many BDCs are thereagain if the field lengths and layouts are not changingthen no need to change anything (except the main thing..you need to change the obsolete function modulesthere are some in 4.6 c like for data upload ws_upload_*** is there 4.6C but obsolete in ECC6.0there are some new with enhanced functionality so you need to modify the BDCsand many cases it happens that the whole transaction screen changes for processin that case better to develop new BDCsso you have to consider those parameterlook into and estimate accordinglymodifying a BDC should not take more than 1 PD
Now say for Formsthere was no Smart form in 4.6Cform printer was there..though the same option is there in ECC 6.0 too..but better to go for/should go for Smart formin that caseits complete new devso estimate accordinglya medium complexitys form should take 8 PD (FRSTDSCoding+Unit Testing)you can take it as 10 PD tooeven if client wants to keep it is as it was in older versionyou have to redevelop the layout in ECC 6.0 againas form printer is even client dependentmaximum you can copy the program associated with that form in the new version tooand your effort will be savedagain you have to consider if clients wants to change the layout too
Now for enhancementso in that case u need to see individual casesfor a medium complexity enhancement it should take max 15 PD (FRSTDSCoding+Unit Testing)
One more important thing is that the Unicode Compatibilitythis needs to be done.needs to change the code (variable name) accordingly.also Version management tool is used for the standard programs
Also pls find the following forums:
Re: Data Migration from 4.6C to ECC 6.0
List of transations supported in SAP 4.6c and not in ECC6.0
Re: Upgradation from 4.6C to ECC 6.0
Re: what's the advantage to upgrade 4.6c to ECC5.0...
RE: Help required regarding to upgrade from R/3 4.6c to mySAp ERP 2005
Upgrade batch inputs from 4.6C to mySAP ERP 2005
/thread/317225 [original link is broken]
Upgrade from SAP R/3 to ECC 6.0
Hope it will help you.
Thanks,
Atin
Reward points if it helps.

Error in SAP Upgrade 4.6C to ECC 6.0 in CONFLICT_CHECK Phase

Hi All,
I am doing an SAP Upgrade frm SAP 4.6C SR2 to ECC 6.0 SR2. When it enters the CONFLICT_CHECK we are facing the following error. i am performing this on Production system. Your immediate help is highly appreciated.
#---- MASKING file CONFLCHK.LOG from E:\usr\sap\put\log
#---- TIME: 20091212095249
1 ETQ201XEntering upgrade-phase "CONFLICT_CHECK" ("20091212094722")
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '22', GwService = 'sapgw22'
4 ETQ399 Environment variables:
4 ETQ399   dbs_ora_schema=SAPR3
4 ETQ399   auth_shadow_upgrade=0
4 ETQ399 (trc) R3upExtendedInclusion: TRUE (default)
4 ETQ399 (trc) R3upExtendedInclusion: TRUE (default)
2 ETQ160 Starting conflict check
4 ETQ010 Date & Time: 20091212094722
4 ETQ230 Starting RFC Login to: System = "CPA", GwHost = "DERSHASKFI140", GwService = "sapgw22"
4 ETQ359 RFC Login to: System="CPA", Nr="22", GwHost="DERSHASKFI140", GwService="sapgw22"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "SPDA_CONFLICT_CHECK" by RFC
2EETQ360 RFC of "spda_conflict_check" failed:
2EETQ361 code/exception : SYSTEM_FAILURE
2EETQ362 key             : RFC_ERROR_SYSTEM_FAILURE
2EETQ364 message         :
2EETQ399 SQL error 1654 occurred when accessing table OCSCMPLOBJ                    .
4 ETQ359 RFC Login to: System="CPA", Nr="22", GwHost="DERSHASKFI140", GwService="sapgw22"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "SPDA_CONFLICT_CHECK" by RFC failed (error-status "-2")
4 ETQ239 Logging off from SAP system
4 ETQ010 Date & Time: 20091212094903
4 ETQ010 Date & Time: 20091212094903
Hemanth

Hi,
> 2EETQ399 SQL error 1654 occurred when accessing table OCSCMPLOBJ
Have you checked tablespace have sufficient space ?
Thanks
Sunny        .

Problem with Upgrade 4.6C to ECC 6.0

Hi Experts,
after the upgrade from relase 4.6C to ECC 6.0, some Function Modules have the following error:
"In EXPORT/IMPORT and ASSERT... FIELDS, "IS_OUTPUTDATA" cannot be a reference nor can it contain references..." where IS_OUTPUTDATA is a exporting parameter (not table) and it is declared type SSFCRESCL (standard structure):
*" IMPORTING
*" VALUE(VBELN) TYPE VBELN
*" VALUE(KUNNR) TYPE KUNNR
*" EXPORTING
*" VALUE(IS_OUTPUTDATA) TYPE SSFCRESCL
*" VALUE(TOTBYTES) TYPE I
*" VALUE(PDF_BIN) TYPE XSTRING
How can I resolve the problem?
Thanks a lot and sorry for my bad english.
Umberto

Hi,
 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 SAP Service Marketplace at the Upgrade Info Center at http://service.sap.com/upgrade
The specific documents regarding to the Upgrade to ERP can be found in : http://service.sap.com/upgrade-erp
Reward points
Regards

Ability to patch SAP by Module within Core R/3 ECC

A couple of years ago, SAP came out with a statement that in future releases we'd have the ability to 'patch' and / or 'upgrade' the core R/3 modules separately
For example -
You could patch the SD module only
We're on NW2004 ECC 5.0 and I sure don't see this ability to exist - still see the APPL, BASIS, HR support packs without any regard for a specific module (other than HR)
Thoughts anyone?

Hi Doreen,
sorry to tell you, but this was perhaps a good "sales gag", but the way is more ore less going the other way around:
This is not possible right now and not "forseeable" at least not for "SD" or "FI" in an ECC system. Perhaps in future for BW in an ERP system. But even this is unlikely because of the basis & kernel dependcies.
Because of the support package stacks (if you like them or not) - the idea of SAP is totally the other way around, because they found out, that only this way it "stays more or less" maintainable ...
Regards
Volker

Anyone having issues upgrading RFC apps from ECC 5.0 to ECC 6.0 ?

We are having issues upgrading our simple RFC app from ECC 5 to ECC 6.
we are using the librfc32u.dll ( 710_Rel) to make a simple call to return MARD table entries.
Runs great in our 5.0 system.
When we run against our 6.0 environment with the same dll, we get garbage back in the table results... (escape characters ).
We have tried downloading the latest 7.0 librffc* ( standard an u ) . We recompiled to embrace both unicode and non-unicode. ( fyi our 6.0 environment is unicode ) . All attempts have failed to date.
Has anyone else experienced issues trying to upgrade their rfc applications?

david, were you able to fix this issue? i have a similar issue. we are upgrading from 4.6c to ecc 6.0. we use a c# program that connects thru sap connector for .net v2.0. it calls a rfc function module, it connects and passes some data, but not all data to the rfc.
any help would be appreciated.
thanks.

Upgrading from 46C to ECC 7.0

Guys,
My company is going to upgrade R/3 46C to ECC 7.0 later this year. From the development (ABAP programs, any ABAP objects) standpoint, any suggestions on preparation, or what can be done in our current 46C environment to ensure a smooth transition from 46C to ECC (unicode, obsolete ABAP syntax, etc)? Also any idea and recommendation on planning the upgrade, as well as things to watch out for are welcome.
Thanks,
Yan.

First ECC 7.0 does not exist, so you will be upgrading to ECC 6.0. And yes, you can start by doing a start for any calls to WS_UPLOAD and WS_DOWNLOAD. You will need to change these calls to call the GUI_UPLOAD or GUI_DOWLOAD function modules.
Other syntax issues will need to be handled after the upgrade, like using the ECODING extension on all OPEN DATASET statements.
Regards,
Rich Heilman

Warning codes generated in UCCHECK - Technical Upgrade - 4.0b to ECC 6.0

Hi SDN'ers ,
I am currently working on Technical Upgrade project from 4.0 b system to ECC 6.0 system . I am facing a
problem relating to the analysis of the warnings displayed whehn we run the UCCHECK for the client inventory by
checking the "Display lines that cannot be analyzed statically" option under the Selection-screen block
"Statements that cannot be analyzed statically" .Based on the warning codes generated during UCCHECK, they can
be classified into 12 different categories given below in the list ( Viz. ABB,MESSAGEG!C,MESSAGEG!D......MESSAGEG!P).The same are given below in the end
I want to know
- Which are the warning codes which need resolution so that the program does not encounter any runtime
errors or during Integration testing ?
- Do all the offset related errors (For example ;variable A = B+offset(length)
or variable A+offset(length) = B ) need resolution so that the program gives no runtime error.
- Also, do all statements where length is calculated using STRLEN also need changes ? I have seen offset length related warnings come under MESSAGEG!M warning code.
The objective of this is to make sure that the upgraded system ECC 6.0 in Australia ,when rolled out to
non-English speaking geographies in APAc such as Malaysia,Japan or China would only need translations and no ABAP Coding effort even when using languages such as Japanese which have double byte characters.
S.No. Error Code Message
1 ABB Syntax Check Aborted
 ABB Total
2 MESSAGEG!C check at runtime. at runtime.
 statement because of untyped or generic operands. It can only carry out this
 The system could not perform a static convertibility check on the current
 MESSAGEG!C Total
3 MESSAGEG!D out this check at runtime. It can only carry out this check at runtime.
 to a table line because of untyped or generic operands. It can only carry out
 The system could not perform a static check on convertibility from a work area
 MESSAGEG!D Total
4 MESSAGEG!E check at runtime. at runtime.
 defined by a "DATA" statement. .
 statement because of untyped or generic operands. It can only carry out this
 Field "ELEMENTN" is unknown. It is neither in one of the specified tables nor
 The system could not perform a static comparability check on the current
 MESSAGEG!E Total
5 MESSAGEG!F operand "<FELD1>" for the current statement. .
 MESSAGEG!F Total
6 MESSAGEG!G current statement on incompletely typed operand "<DATA>". .
 MESSAGEG!G Total
7 MESSAGEG!H for the incompletely typed operand "<S>". . - - - - - - - - -
 The system cannot perform a static check on a character-type field data type
 MESSAGEG!H Total
8 MESSAGEG!I incompletely-typed operand "<A>" in the current statement. .
 The system cannot perform a static check on a character-type data type for the
 MESSAGEG!I Total
9 MESSAGEG!J "<%_1_SYSINI>" in the current statement to check whether the operand can be
 The system cannot perform a static check on incompletely-typed operand "VALUE"
 MESSAGEG!J Total
Early response wil be highly appreciated.

Hi Karthik
>
> 1) SPDD adjustments are done in which phase? PREPARE or UPGRADE?
>
SPDD is done in Upgrade ->Phase ACT_700
> 2) Are here special cases where the adjustments need to be done before running the UPGRADE phase?
>
At ACT_700 phase stop the upgrade and take a backup of the DB and the PUT<DIR> before starting the SPDD activity.
Make sure there are no pending tp request. Either release them or delete them.
All phase need to be completed successfully in PREPARE, before starting UPGRADE
Cheers
Shaji
Edited by: Shaji Jacob on May 5, 2008 9:23 PM

HR module upgrade 4.6c to ECC 6.0

Similar Messages

Maybe you are looking for