Technical upgarde from ECC5 to ECC6 EHP4

Dear All,
We are having technical upgarde from ECC5 to ECC6 EHP4. I have have some queries as client what need to be check after upgarde.When golive cahke is done what are check list apar from system is up and running.
Please sugegst
Regards,
Kumar

SAP offers a pre-golive check before actual go-live by logging into your system and doing some important checks as per the requirement for technical or functional go-live check...
So, you want SAP to do pre-golive check, just open up the connection between SAP and your sap system, at the same time, a connection from Solman to SAP too..maintaining the connection details in secure area
You have to open a message in component XX-SER-TCC to find out if your installation is scheduled for a Go-Live check which is conducted by SAP and itu2019s partners.
Go-Live Functional Upgrade Analysis u2013 ideally 6 months before Golive u2013 basically checks your hardware requirement , will it be able to accommodate the increase in the functionalities caused by the Go-Live, also some parameter recommendations to fine-tune your system.
Go-Live Functional Upgrade Verification u2013 This is normally 2 months after the Go-live which is to see eu2019thing is fine after the upgrade.
Then you have normal Earlywatch session , each installation is entitled for 2 free earlywatch session in a year, in this performance tuning is done for your system, hardware,memory, I/0 bottlenecks are identified.
Reports of all these sessions carried out by SAP is then sent to you in form a MS-Word document and you can follow the guidelines mentioned and call up SAP or mail the person who has done the session for you for any clarifications.
Usually once a session is scheduled.
SAP will contact you to open the connections for them, so that they can prepare the system before the actual session takes place , in which they see , if SDCC version is good enough so that they can download the data from your system into their internal system on which they carry out the analysis
Refer to https://websmp208.sap-ag.de/earlywatch

Similar Messages

CU&UC from ECC5 to ECC6 Ehp4

Hi,
We are planning to run a CU&UC from a NUC ECC5.00 system to UC ECC6 Ehp4/NW 7.01 and need to check if this is supported.
I have trawled through OSS/SDN etc and cannot see anything to say that it is not, but an OSS message placed regarding the supportability said that this is not possible as "ECC6 EHP4 SR1 Media is available as UNICODE ONLY, so you
will not be able to perform 'normal' CU&UC using 'EHP4 ready"
There is a NUC 7.01 kernel available, so I am not sure what SAP mean by this??
Regards,
Mark

Hi 'Basis Team',
The original question was "We are planning to run a CU&UC from a NUC ECC5.00 system to UC ECC6 Ehp4/NW 7.01 and need to check if this is supported." is pretty clear I think.
What muddied the water is a reply from SAP to an OSS message placed asking the above question where they say that this is not possible as there are no NUC ABAP loads delivered after ECC6 SR3.
This reply goes against all SAP doco that we have read, and as you say, you have done the same CU&UC that we are tring to achieve.
BTW, which upgrade kit did you use? The Ecc6 Ehp4 Ready SRx one??
Cheers,
Mark

Upgrade from ecc5 to ecc6 old data like PRD640_1 is still there

Dear All,
we have resent   upgrade from ecc5 to ecc6 and i have some quires regarding the datafile.
In sapdata1 -4 i see all old data like PRD640_1 i still there .Please suggest it is ok or it should not be there in the sapdata.
in db02 tablespace
PSAPEL701D
PSAPEL701I
PSAPPRD
PSAPPRD640
PSAPPRD701
PSAPPRDUSR
PSAPTEMP
PSAPUNDO
PSAPUNDO2
SYSAUX
SYSTEM
There is once more thing when i am extend the table from brtools for
BR*Tools main menu 2 - Space management 1 = Extend tablespace 3 ~ Tablespace name (tablespace) ... []
1 - BRSPACE profile (profile) ...... [initPRD.sap]
2 - Database user/password (user) .. [/]
3 ~ Tablespace name (tablespace) ... [PSAPPRDUSR]
4 - Confirmation mode (confirm) .... [yes]
5 - Scrolling line count (scroll) .. [20]
6 - Message language (language) .... [E]
7 - BRSPACE command line (command) . [-p initPRD.sap -s 20 -l E -f tsextend -t
PSAPPRDUSR]
c
c
Options for extension of tablespace PSAPPRDUSR (1. file)
1 * Last added file name (lastfile) ....... [L:\ORACLE\PRD\SAPDATA4\PRDUSR_4\PR
DUSR.DATA4]
2 * Last added file size in MB (lastsize) . [460]
3 - New file to be added (file) ........... [L:\oracle\PRD\sapdata4\prdusr_5\pr
dusr.data5]
4 # Raw disk / link target (rawlink) ...... []
5 - Size of the new file in MB (size) ..... [460]
6 - File autoextend mode (autoextend) ..... [yes]
7 - Maximum file size in MB (maxsize) ..... [500]
8 - File increment size in MB (incrsize) .. [20]
9 - SQL command (command) ................. [alter tablespace PSAPPRDUSR add da
tafile 'L:\oracle\PRD\sapdata4\prdusr_5\prdusr.data5' size 460M autoextend on ne
xt 20M maxsize 500M]
BR0259I Program execution will be continued...
BR1049W Not enough free space in L:\oracle\PRD\sapdata4\prdusr_5 for total maxim
um size of all database files of tablespace PSAPPRD located on this disk volume,
missing at least 741702.647 MB
BR1049W Not enough free space in L:\oracle\PRD\sapdata4\prdusr_5 for total maxim
um size of all database files of tablespace PSAPPRD640 located on this disk volu
me, missing at least 137942.647 MB
BR1049W Not enough free space in L:\oracle\PRD\sapdata4\prdusr_5 for total maxim
um size of all database files of tablespace PSAPPRDUSR located on this disk volu
me, missing at least 13522.647 MB
BR0668I Warnings or errors occurred - you can continue to ignore them or go back
to repeat the last action
Please suggest what is right configuration and how to sol ther error in brtools.
Regards,
Kumar

Hello Kumar9,
if I understoon correctly your last reply, you have doubts if PSAPPRD640 should exist at all, correct?
Please do the following:
1) Check any object assigned to this tablespace PSAPPRD640
2) If any object occupied to PSAPPRD640 then reorganise to new tablespace
If any object not occupied to PSAPPRD640 then check the table entry
   a)TAORA for tablespace PSAPPRD640(if exist delete)
   b)IAORA for tablespace PSAPPRD640(if exist delete)
3) If above done then drop the tablespace through BRTools.
Best regards,
Tomas Black

SAP extract to Excel changed after migration from ECC5 to ECC6

Hi everyone,
This issue is about getting a proper table when displaying SAP reports in Excel. When extracting to Excel, the data base is presented with summary yellow lines whereas we would rather have a regular table without subtotal. This issue appeared when the system was migrated from ECC5 to ECC6. Please notice that one of the user has currently a proper display. Do you know which parameter shall we change?
Thanks!
Stan B.

There are some default setting in the parameters,
Like
RPO0 - User Settings
From FI transactions you can change ti your default settings
Have a look to:
FIT_ALVC X FI Line Items: ALV Grid Control
With KSB1 I see it direct without sub totals and saving.
Click on spreatsheet
Select All Available formats
Select EXCEL (In Existing XXL Format)

Recommended upgrade method from ECC5 to ECC6 for lowest production downtime

Hello everybody,
I've been looking through multiple documents concerning a system upgrade and I am still unable to figure out the recommended method for upgrading a system with minimum downtime.
My scenario requires that tests as rigid as possible will be performed and that development will be halted for the shortest time possible , therefore development must be continued after the initial upgrade.
We are currently debating the required way to do this - what should be done with the change requests that currently reside in the DEV system, in which steps the incomptabilities are fixed and so on.
I've decided that I'll share my thoughts with you and maybe you guros will be able to point out mistakes in the methodology.
1. ECC 5 Production System is copied aside, lets call this system EPC
2. Change requests from DEV ECC5 are copied to this EPC System.
3. EPC system is upgraded to ECC6.
4. Bugs and incomptabilities such as unicode incomptabilities are fixed and merged in a change request
This ends the preperation step and in my opinion is sort of a preperation step.
During the whole preparation step, which to my estimate could take at least one month, development in the original system must be continued, so this is my main trouble.
What is the recommended procedure from here?
I assume that another production must be done on the day of the actual upgrade start, then the fixes from the previous preperation system are copied to this actual ECC6 Production, but I am rather lost as far as it goes to having an ECC6 Dev with most current change requests.
I would appreciate any hints and help,
thanks in advance,
Eli.

Ok, your idea of having a production copy for development and tests is a good upgrade strategy, we have done this twice due high quantity of developments and configuragion changes but I don´t see why you wrote " copy change requests from DEV to EPC " your whole configuration, programs, etc, are already in EPC once you copy the system.
In this scenario every change made in DEV ECC 5.0 must be also replicated and tested in EPC 6.0 because you cannot use the change requests from 5.0 in 6.0 once in productive upgrade, let me list the global steps:
1.- Homogeneous system copy from PRD to EPC, you will get a working test platform
2.- Upgrade EPC to 6.0
3.- Developers and functionals will do all respective changes and generate chage requests.
Once EPC is ready
4.- Upgrade DEV system to 6.0 transport change requests created in EPC to upgraded DEV, from this point you should only do emergency changes using Q&A system.
5.- Upgrade Q&A system, transport change requests from DEV, no changes are permited from now until PRD is upgraded.
6.- Do all tests very carefully
7.- Upgrade PRD transport change requests
Then you are ready. the downtime can be tune trough EPC, DEV and Q&A systems so you can determine what you shoud do to assure the shortest method.
I recomend you to use the downtime minimized upgrade method and from every upgrade take a deep look at the upgrade report generated after the whole process is completed.

Transporting BAPI from ECC5 to ECC6 - FM definition isn't avail at target

Hi
I have a BAPI developed in ECC5 System - ZBAPI_TEST, under a function group - ZFG_TEST within a package - ZPKG_TEST.
All these objects are assigned to the same TR number.
I have released, generated Co/Data Files and moved these TR (Co/Data Files) to ECC 6 System.
The associated structures are available in ECC6 System - where the Function Module name is present - BUT NO SOURCE CODE!!!
Is there any special rules we need to follow while transporting a BAPI from one system to other?
Thx
Rich

Please check if the the two includes also have activated and moved or not.
if yes try a re transport.

PC00_M14_CDTA ECC5 to ECC6 Upgrade Missing Selection Field

Hi All,
Found out Selection Field of (Pay date) during Upgrade from ECC5 to ECC6 on TCODE : PC00_M14_CDTA.
More information you can refer to below print screen.
Thank in advance for advice.
Trevor Wong.

This has been replaced by "Requested Execution Date". Here is the standard hlpe for this:
Requested Execution Date on Which the Payment Is to Be Made
Use
In this field, you can enter a date on which the bank is to execute a payment. The date is transferred together with the payment information to Financial Accounting (FI), where the payment is executed.
You can use the date to override the default setting or the date determined by implementing the Business Add-In (BAdI) Change of Requested Execution Date for the Payments (HRDME_B_ REGUH_DUE_DATE).
In many countries, the system date is used as the default value for the execution date. In some countries, the payment date of the payroll period is used.
Dependencies
The following sequence applies to determining the execution date:
1. The defined default value is used as the execution date.
2. If the BAdI HRDME_B_ REGUH_DUE_DATE is implemented, the execution date is determined using this BAdI.
3. If a date is entered on the selection screen of the preliminary program, this overrides the default value or the value determined by the BAdI.

Technical difference between ECC5.0 and ECC6.0

Hi everyone,
Can anybody tell me whats is the Technical difference between ECC5.0 and ECC6.0.
I am doing upgrade from ECC5.0 to ECC6.0 in Retail.
Regards,
Divya

Dear Divya,
When it is a technical upgrade from a lower version to ECC6.0, many objects like includes, Function modules, reports, OSS notes, DDIC objects, BDC/Print programs, SAP scripts, screens will get affected due to the upgradation. So we need to check with all these objects.
u2022 We will encounter short dumps while executing certain programs. This may be due to the usage of obsolete function modules or Unicode errors.
u2022 The BDCs in the upgraded version will become defective as many of its screen field names will be changed during version change.
u2022 Program texts of many programs will be lost. They have to be restored.
u2022 In case of tables, enhancement category has to be provided.
u2022 There is a possibility of losing the variants during upgradation. So care should be taken to retain them before upgradation.
u2022 ECC6.0 is case sensitive, so many of the interface programs will fail to transfer (FTP) files between systems. These objects have to be changed so that the commands passed to the external system be UPPERCASE.
So a developer should be aware of the following:
u2022Unicode programming is followed in ECC6.0. So we need to be aware of it to rectify certain Unicode errors which are likely to occur.
u2022You have to run the transactions SPAU & SPDD to check for list of standard & custom objects that needs modification in the upgraded version.
Check the below link to find more details on usage of SPAU & SPDD transactions
http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
u2022Should be aware of the objects that have become obsolete in ECC6.0. They have to be replaced by appropriate ones.For eg.:
--> The WS_* function modules have been replaced by GUI_* FMs in ECC6.0 as WS_* FMs have become obsolete from 4.7
-->Tables like TVARV & TTREX have been replaced by TVARVC & TTREXN respectively in ECC6.0.
u2022In case of tables, we need to specify the Enhancement category.
u2022Due to upgradation, we will lose out some variants. So we should take a back-up before proceeding with the upgradation.
u2022In case of BDC programs, some field names will be changed. So they have to be named appropriately.
Please check with the below links for more details:
SAP Upgrade guide:
http://www.thespot4sap.com/upgrade_guide_v2.pdf#search=%22upGRADE%20STEPS%20-%20SAP%22
From ABAP's perspective, the following link helps you:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5ac31178-0701-0010-469a-b4d7fa2721ca
For technical upgrade inputs:
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
Hope this helps you.
Regards,
Rakesh

Follow up activities after SAP (CU&UC) upgrade from SAP 4.6c to ECC6 EHP4

Dear Friends
We have completed SAP (CU&UC) upgrade from SAP 4.6c to ECC6 EHP4.
We refereed the upgrade guide for follow activities and we required confirmation before performing the activities.
Could you please help us what needs to be done immediately after upgrade.
Regards,
Bharathi

Dear Nils,
Thanks for the support.
Yes, we are following the same document 'CUUC46C_to_NW701SP07' for unicode conversion after the upgrade from the note 928729.
Please suggest us in that document which are the steps should be carried out after ECC6.0 EHP4 upgrade,
1. Preparation
2. Unicode Preconversion Phase in SAP Basis 4.6C
3. Upgrade Process
4. Unicode Conversion Phase
5. Unicode Conversion Completion Phase
6. SAP Notes
Regards,
Bharathi

Data migration from ECC5.0 to ECC6.0

Hi All,
Is there a standard SAP utility to migrate the data from ECC5.0 to ECC6.0? Assumption is that all the standard fields and the transactions are same. Good example for this case is standard material master, Purchase order, purchase info record etc.
Currently I am planning to extract the data from source system (using custom program or table download etc...) and upload the data into target system (using LSMW, eCATT, BDC etc...).
Is there a standard way to load the data into target system without extraction and upload? Please let me know.
Thanks
Nagarajan

ALE Customizing
1)     IMG > Application Link Enabling (ALE) > Sending and Receiving > logical systems > Define Logical System: name it XXXXXX
2)     IMG > Application Link Enabling (ALE) > Sending and Receiving > Systems in Network > Asynchronous Processing > Assigning Ports > Define Port: name it XXXXXX   Description: Files for Migration to YYY
The port need to be defined beneath FILE
The IDOC record types for SAP Release 4.x need to be selected
A physical directory is needed. One must be able to map this directory with the Windows explorer to copy the file to the network or local drive.
Function module: EDI_PATH_CREATE_CLIENT_DOCNUM
In order to prevent unprocessed files being overwritten, you use function modules which generate file or directory names dynamically, that is to say, at runtime.
3)     IMG > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Cross-Application Settings > Global Organizational Units > Cross-System Company Codes
a)     Cross-System Company Codes
b) Assign Cross-System Company Code to Chart of Accounts
c) Assign Company Code to Cross-System Company Code
Cross-system company codes are used in the distribution in financial accounting. There is exactly one central system for each cross-system company code in the distributed environment. One company code has to be assigned to this cross-system company code on each system involved in the distribution.
When sending an IDoc with company code-dependent data, the company code is replaced with the cross-system company code in all company code fields.
4)     IMG > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Maintain Distribution Model and Distribute Views
Here we need a distribution model
     Structure: model view (call it XXXXXX)
               Sending system (AAAAAA)
                    Receiving system (XXXXXX)
5)     IMG > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Predefined ALE Business Processes > Logistics > Master Data Distribution > Proposal for distribution model: Customer and vendor masters
(Beside of customers and vendors, we need to add the message type BOMMAT for material bill of materials and MATMAS for material master to to the distribution model, probably manually in step 4. Depending on further requests for automatic migration the one or other message type may need to be added later )
6)     IMG > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Partner Profiles and Time of Processing > Maintain Partner Profile Manually
Partner profile type/Partner type: LS logical system
Partner profile/Partner number: XXXXXX
Details at Post Processing agent
Typ: US user
Agent: JJJJJ
Lang: EN
Outbound parameters
Message type:     ADDR2MAS
               ADR3MAS
               ADRMAS
               MATMAS
               CREMAS
               DEBMAS
Details per message type like this:
Receiver port: XXXXXXX Output mode: Collect Idocs and Do not start subsystem
IDOC type:      for     ADDR2MAS   use      ADR2MAS02
               ADR3MAS          ADR3MAS02
               ADRMAS          ADRMAS02
               MATMAS          MATMAS03
               CREMAS          CREMAS03
               DEBMAS          DEBMAS05
Activate syntax check
7)     Authorization needed to execute Transactions:
BD12 Send Customers
BD14 Send vendors
BD10 Send material
BD30 Send bill of material
Depending on future migration requests for other objects we may need some more.

Real Estate Management Upgrade from Ecc5.0 to Ecc6.0

HI Gurus
Can any body guide me what all upgrade issues from Functional Prospective are there in Real Estate Management from Ecc5.0 to Ecc6
Thanks and regards
Ramarao

Hi,
Pleae use the link http://solutionbrowser.erp.sap.fmpmedia.com to find out the newer functionalitites as per SAP product release modulewise.
Hope this helps you.
Rgds
Manish

Technical upgrade from 4.7 to ECC 6.0

Experts,
1.We need to make Technical upgrade in HR from 4.7 to ECC 6.0 with OM,PA, -ve Time,Payroll, Recruitment (other Modules also upgraded).Kindly let us know what will haeepen for the following .
A.Configrations in SPRO
B.Previous database (Cluster table for previous Time and payroll run)
C.Master data of employees which is stored in Infotypes
2.Also Kindly let us know is there anything we need to take care after moving from 4.7 to 6.0

Hi Kumar,
Basically there needs to be a Transport established between 4.7 and ECC6.00 Version . You can create Transport request for those tables whose value remain same in 4.7 nad ECC6.00 But for tables having changes you need to create the Configuration.
1 more method applied by organization is a client copy of tables.
My suggestion would be like this :
1. Compare and Update Tables (from Configuration Handbook)
Pay Frequency
Define Period Modifiers
V_T549R
Define Date Modifiers
V_T549L
Check Payroll Accounting Area
V_T549A
Pay Scale Structure
Define EE Subgroup Grouping for PCR and Collective Agreement Provision (CAP)
V_503_B
Check Pay Scale Type
V_T510A
Check Pay Scale Area
V_T510G
Check Assignment of Payscale Structure to Enterprise Structure
V_001P_C
Define Default for Pay Scale Data
Feature - TARIF
Setup payroll period for Collective Agreement Provision
V_T510W
Revise Pay Scale Groups and Levels
V_T510
Enterprise Structure for Wage Type Model
T539A
Feature - LGMST
Revise Default Wage Types
V_T539A - already tested
Define Valuation of Base Wage Types
V_T539J
Legacy Data Transfer
T558B
T558D
Define Periods for import
T558B - already tested
Rates of Pay
T512W
Pay Scale Allowance Group
V_T7INA1
Assign Pay Scale Groupings for Allowances
V_T7INA3
Define Basic Codes
V_T7INB4
Statutory
Define Trust Details for Provident Fund
V_T7INF1
Assign Company Rates for Provident Fund
V_T7INF5
Define PF Trust Validity Period
V_T7INF7
Maintain Contribution Details for Provident Fund
Feature: 40EPF
V_T7INF3
Define Contribution Type for Statutory rates for Provident Fund
V_T7INF3 - already tested
Employees' State Insurance
V_511P_B
V_T511P
Maintain Number of Working Days in a Month
V_511K_B
V_T511K
Define Personnel Area and Subarea Groupings for ESI
V_T7INE1
Assign ESI Groupings for Personnel Area and Subarea
V_7IN0P_ESI
Maintain Contribution Rates for ESI
V_T7INE3
Assign Universal Contribution Groupings for Universal Contribution Type
V_T7INOP_ALL
Assign slab code for Universal Contribution Grouping
V_T7INU1
Assign Slab code and other parameters for each state of a universal type
V_T7INU3
Assign contribution Value for each slab
V_T7INU5
Maintain Eligibility Details for Superannuation
Feature - 40SAN
Tax and Professional Tax
Define Professional Tax Grouping Details
V_T7INP1
Maintain Method and Form Layout for Ptax Groupings
T596F
Maintain Re-Computation Behaviour of Tax related
Feature - 40MWT
Maintain Schema for Exemption on Medical Reimbursement / Insurance
V_T7INT9
Maintain Schema for Exemption of Child education and hostel allowance
V_T511K - already tested
V_T7INT9 - already tested
Bonus Act
T511K - already tested
T511P - already tested
One Time Bonus Tax
Copy Wage Types
V_T7INT9 - already tested
V_T7INA9
Define Compensation Area Feature
Feature - CAREA
Assign organizational assignment to Compensation Groups
Feature - CMGRP
Maintain Variant for Payroll Simulation
Feature - 16CVA
Maintain Payslip Variant
Feature - 16EVA
HRA/CLA/LTA
Define Accomodation Types
V_T7INT7
Company Loans
Maintain Loans Grouping
Feature - 40LGR
Mantain Loans Eligibility Checks and Limits
Feature - 40 LGR - already tested
Banking
Setup House Banks
V_T012
Bank Account
V_T012K
Define Sending Banks
Feature - DTAKT
Check Text Keys for Payment Transactions
V_T520S
General Ledger
Define Employee Grouping Account Determination
Feature - PPMOD
Define Symbolic Accounts
V_T52EK
V_T52EZ
2. Compare and Update Genaral Tables
1     T512W
2     T511K
3     T511P
4     TCURR
5     T030
2a. Compare and Update Additioanl PY-IN Tables
1     T7INTN TAN Number Maintainence
2     T7INA1 Pay scale grouping for allowances
3     T7INA3 Associating pay parameters to pay scale grouping
4     T7INA5 Wage type model for pay scale grouping for allowances
5     T7INA7 Reimbursements Allowances and Perks - base slabs
6     T7INA9 Reimbursement allowances perks - eligibility and calculation
7     T7INAA Salary year for pay scale grouping for allowances
8     T7INB1 Basic Wages
9     T7INB4 Basic Codes
10     T7INB5 Basic Codes for Allowance Groups
11     T7INB7 Basic slabs
12     T7INB8 Appraisal Criteria
13     T7INB9 Increment criteria
14     T7INC1 Car types master
15     T7INC3 Type and age eligibility for car schemes(COCS/OYCS)
16     T7INC5 Perk valuation for cars
17     T7INC7 Amount and number eligibility for car schemes(COCS/OYCS)
18     T7INC9 Conveyance allowance eligibilty
19     T7INCA Codes for Conveyance types
20     T7IND1 Dearness allowance consumer price index master
21     T7IND3 Dearness allowance consumer price index value
22     T7IND5 Dearness allowance basic slab details
23     T7IND7 Dearness allowance calculation rules
24     T7IND9 Dearness allowance consumer price index slabs
25     T7INE1 Personnel area / subarea grouping for employees' state ins.
26     T7INE3 Employees' state insurance contribution rates
27     T7INF1 Trust Master
28     T7INF3 Statutory rates for Provident fund
29     T7INF5 Company rates for Provident Fund
30     T7INF7 Trust details
31     T7ING1 Gratuity Details Maintenance
32     T7ING3 Gratuity ID Maintenance
33     T7ING5 Gratuity ID and Related Wage Types
34     T7INI0 Investment category limits
35     T7INI2 Investment technical description and text
36     T7INI4 Investment details
37     T7INI5 Sub section description
38     T7INI7 Sub section limit
39     T7INI8 Sub division description
40     T7INI9 Sub division details
41     T7INIA Deduction wage type for Sec 88
42     T7INIC Deduction wage type for Sec 80
43     T7INJ1 Section 24 Deduction Details Maintenance
44     T7INJ3 HR-IN: Loans Eligibility checks and limits
45     T7INJ5 HR-IN: Loans Dusbursement Schedule
46     T7INJ6 HR-IN : Loan Tranche Disbursement: Text for Events Code
47     T7INL1 Leave validation for LTA
48     T7INO1 One day salary deduction
49     T7INP1 Professional tax grouping details
50     T7INP3 Method and form layout for states
51     T7INP4 Professional tax slab amounts
52     T7INR1 Housing code for taxation
53     T7INR3 Percentage/amount for housing related constant
54     T7INR5 Housing related statutory constants for taxation
55     T7INR7 Codes for Housing Types
56     T7INR9 City category for housing type
57     T7INS1 Superannuation Details Maintenance
58     T7INS3 Superannuation ID
59     T7INS5 Superannuation-Wagetype Details
60     T7INT1 Slab codes for taxation
61     T7INT3 Taxation slabs
62     T7INT5 Personnel subarea grouping for Tax
63     T7INT7 Tax codes for tax exemptions
64     T7INT9 Taxability of wage types
65     T7INU1 State for Universal Grouping
66     T7INU3 Slab Codes for States
67     T7INU5 Contribution Value for Each Slab
68     T7INW1 Personnel area/subarea grouping for LWF
69     T7INW3 Labour welfare fund rates
70     T7INY1 Recovery of rounding off amounts
71     T7INZ1 Factor for retiral benefits
72     T7INZ3 Period of notice codes
3. Compare Payroll Schemas
1     Compare ECC5- to ECC6 standard schemas
2     Compare ECC5- to ECC6 customised schemas
4. Compare Personnel Calculation Rules (PCR)
1     Compare ECC5- to ECC6 standard PCR's
2     Compare ECC5- to ECC6 customised PCR's
B. Payroll Process
1     Generic Payroll Process
1.1     Simulate Payroll
1.2     Release Payroll
1.3     Start Payroll
1.4     Check result
1.5     Corrections
1.6     Remuneration statement
1.7     Simulate and test FI/CO postings
1.8     Simulate and Test Preliminary DME
1.9     Run Preliminary DME Program
2     Create a live posting run and create FI documents
C. Regression Testing (Variance Monitor)
1     Compare Payroll Results
Create a Excel with these contents and fill them up by saying the percentage of similarity and completetion.
Please let me know if this is usefull
Regards,
Prabha

Issues during technical upgrade from version 4.6C to ECC 6.0

Dear All,
We have done a technical upgrade from version 4.6C to ECC 6.0 and encountered following issues -
In the t-code ABZE (acquisition with in house production) there is a check-box for reversal posting on screen with version 4.6C. However, this field is missing in ECC 6.0. Why so?
In the report s_alr_87012327, there is a field "only with creation block" in version 4.6C. However, this field is missing in ECC 6.0. Why so?
Request to kindly suggest the alternative to carry out the same in ECC 6.0.
Thanks in advance.
Regards,
Dhawal

Hi Akshya,
Please find answers below.
1) 4.6c is NON-UNICODE system, Can I upgrade it into ECC 6.0 UNICODE system?
Yes you can.
If you are on a single code page system then you can give a gap between your uprade and unicode conversion. There is no problem with the singlecode upgrade and conversion.
But if your system is MDMP then you will have to do the CUUC method that is both upgrade and unicode conversion together. Though you can give a gap and sign an disclaimer with SAP it is still not recomended way.
2) 4.6c does not have any ITS system installed. If we upgrade it to ECC6.0 ABAP only, then Can I activate WAS internal ITS?
Yes you can activate it.
3) 4.6c does not have any JAVA stack. When I upgrade it to ECC 6.0, can I upgrade it to dual stack (ABAP+JAVA)? If yes, then how?
After the upgrade and unicode conversion you can install the java stack.
Regards,
Ravi.

Technical Upgarde of SRM5 to SRM7

Hi All,
We need to upgrade our SRM system from SRM5 to SRM7 only technical upgrade.
I want to know the below things incase of Technical upgrade from SRM5 to SRM7.
1. What are aspects to be identified from the ABAPer point iof view.
2. List of ABAP Objects involved in the upgradation process
3. High level overview of Technical upgarde
If anyone have any documents or links on the Technical Upgrade of SRM5 to SRM7 system,
please reply to the thread.
Thanks a lot in advance.

Hi,
1. What are aspects to be identified from the ABAPer point iof view. - SRM 7.0 uses lot of new technologies for example ABAP Webdynpro, OOPS based PDO architecture layer, Meta data for filed and action control, process controlled workflow, portal..etc. You should consider these.
2. List of ABAP Objects involved in the upgradation process
Not sure if I understand the question. may be you should explain it a bit more.
3. High level overview of Technical upgarde
Please refer to upgrade master guide at
<<https://websmp209.sap-ag.de/~sapdownload/012002523100012366712008E/HELPX_UPGRADE_MASTER_GUIDE.pdf>>
Best regards,
Mradul

Diff between R/3 ECC5 and ECC6

Dear All,
Can someone please enlighten me about the diff between R/3 ECC5 and ECC6?
Thanks,
Ashish

May be there are lot of differences but broadly:
the Inclusion of Netweaver Components happened from 4.t to ECC5.0 and ECC 6.0
In ECC 5.0 the component versions of netweaver are of different versions but in ECC6.0 all componet versions of netweaver are same and latest.
Unicode is another important thing for ECC6.0 and 5.0
AP ECC 5.0 is part of SAP ERP 2004---- which runs on SAP NetWeaver 2004
SAP ECC 6.0 is part of SAP ERP 2005 (mySAP 2005)--- runs on SAP NetWeaver 2004S
Main difference is application components and availability of new features.
for new features/changes in core modules like FI, MM etc.. e.g GL function is new in ECC 6.0..
For Functionality Differences between the SAP Versions.
http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
http://www.id.unizh.ch/dl/sw/sap/upgrade/Master_Guide_Enh_Package_2005_1.pdf
To find the changed transactions between SAP versions pls check the table PRGN_CORR2.
also refer,
http://www.id.unizh.ch/dl/sw/sap/upgrade/Master_Guide_Enh_Package_2005_1.pdf
Also Pl. follow the link for difference between ECC 6 & ECC 5.0
Release Info:
ECC 6.0:
http://help.sap.com/saphelp_erp2005/helpdata/en/43/68805bb88f297ee10000000a422035/frameset.htm
ECC 5.0:
http://help.sap.com/saphelp_erp2004/helpdata/en/c6/feda40ebccb533e10000000a155106/frameset.htm
http://solutionbrowser.erp.sap.fmpmedia.com/
regards,
srinivas
<b>*reward for useful answers*</b>

Technical upgarde from ECC5 to ECC6 EHP4

Similar Messages

Maybe you are looking for