Technical Upgrade from R/3 4.6 to ECC 6.0
Hi all i have a query regaring system upgrade:
Currently i have 2 systems R/3 4.6: Development(D1), Quality(Q1).
Now this systems needs to be upgraded to ECC 6.0.
First the D1 is going to be copied to a new development(D2).
Then D2 will be upgraded to ECC 6.0.
Here a unicode check and other required modification (code compatibility) to
all the customizing and workbench objects is to be done.
Now a copy of Q1 is to be done in new Quality(Q2).
My requirement is to determine all the transported requests from D1 to Q1 and
then transport the same from D2 to Q2 so that the unidcode complaint objects are transported and they overwrite in the new quality system.
Is this process feasible? If yes, How?
Please suggest.
Hi Himansu,
I am making the assumption that you will as the final step upgrade your production to ECC 6.0 and then transport the Unicode corrected ABAP's from your Q2 environment into Prod, and then D2 and Q2 will become your new production support path while D1 and Q1 is removed. Is this assumption correct?
If so, then the next assumption for your plan is your reason for doing this is to keep the production support path D1->Q1->P1 intact while you are performing the upgrade and Unicode program testing in D2 and Q2.
I am also assuming that you are not doing a unicode upgrade/conversion at the same time, you are just making the code Unicode compliant to prepare for a future Unicode upgrade.
If so your plan will work just fine. To say it a little differently, here are the steps
1. Copy D1 to D2
2. Upgrade D2 to ECC 6.0
3. Run UCCHECK to test your code for compliance and to identify objects that need remediation
4. Fix the code that need fixing, and put it in transports with Q2 as your target system
5. Copy Q1 to Q2
6. Upgrade Q2 to ECC 6.0
7. Transport the converted code from step #4 to Q2
8. Perform thorough acceptance testing of the converted code
Now you can plan for your production cutover. While the above steps occurred, you either had a freeze on any changes to the production landscape, or you manually captured changes that was done in D1 in D2. The upgrade project is complex in itself and will need significant user testing assuming that it is only a technical upgrade with no additional or modified functionality.
If your D2 and Q2 was kept in sync, you can now upgrade your P1 system to ECC 6.0 (no need to copy), and configure your transport routes so that D2 and Q2 are now the new production support systems, then you transport the items in step #4 above from Q2 to the upgraded P1.
Regards
John
[SAP Unicode|http://www.sapunicodeupgrade.com|SAP Unicode]
Similar Messages
-
Technical upgrade from 4.6C MDMP system to ECC 6.0 using CU & UC approach
Hi SAP Experts,
We are embarking on a project for Technical upgrade from SAP R/3 4.6C MDMP system to ECC 6.0 using the CU & UC approach for our Asian operations (comprising of India, Japan, Taiwan & Singapore).
Please share with me the Best Practices you followed in your projects, checklists, DOs, DONTs, typical problems you encountered and the possible safeguards, any other useful information, etc.
Since very little information is available from Organizations who have used the CU & UC upgrade approach successfully, I am raising this in SDN to share your experiences during the Technical upgrade.
All useful information will be surely awarded with suitable points.
Looking for your invaluable inputs which will be a BIG help for our project.
Best regards,
RajaramHello Rajaram!:
It's a very big project, that you have to do in a lot of steps........
If you want sent me a email with the problems and you want.
Regards,
Alfredo. -
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,
DhawalHi 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. -
Issues during technical upgrade from 4.6c to ecc 6.0
Hi
We are doing a technical upgrade from 4.6C to ECC 6.0. Some transactions in QM module when tested in ECC 6.0 test client give a abap termination message (or dump) and certain transactions like qs42,46, qa18, qs34 etc do not get executed (error = no entry foound for......) and similarly in PP-PI module transactions like C203 have similar problems, even though master data does exist. What should I look for? Can somebody pl. give details on configuration checks and the OSS notes from a functional point of view for a technical upgrade?
For certain transactions I get the error message - "Central system of distribution SM-P06CLNT430_TRUSTED is unreachable RFC destination SM_P06CLNT430_Trusted does not exist" - what does this mean?
thanks
BEHi,
1. Have you done successfull installation from 4.6C to ECC 6.0 at the time of PrePare ans SAPUP?
2. Check SP' for QM and PP-PI modules from http://service.sap.com/sp-stacks.
3. Configure RFC connections correctly, SM_<SID>CLNT<No>_Trusted automatically created, not manually.
http://service.sap.com/notes --> search for RFC trusted connections for Ecc 6.0
http://service.sap.com/upgrade.
Regards,
Srini Nookala -
Technical Upgrade from XI 3.0 to PI 7.1
Hi,
My client is going for Technical Upgrade from XI 3.0 to PI 7.1 not fresh installation. They are asking for How best we can achieve this. I have gone through Decision making document and upgrade document from SAP. Apart from which please provide me the valuable Inputs like what measures we need to take care before and after upgrade as an XI developer. In our project about 90% of interfaces are having java mapping. will there be any changes to be done after upgrade.
I already gone through below link
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/8085e299-718c-2a10-de94-928f62b763ce
https://www.sdn.sap.com/irj/scn/elearn?rid=/library/uuid/40a0868a-9d40-2b10-8cb4-8e0c53b56655&overridelayout=true
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40a0868a-9d40-2b10-8cb4-8e0c53b56655
Thanks in advance
Venkateshyou can use this document as your base - http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/8085e299-718c-2a10-de94-928f62b763ce?quicklink=index&overridelayout=true
do an upgrade from XI 3.0 to PI 7.1
java mappings will still continue to work.
But you might have to modify some graphical mapping, java proxies and modules if any -
Technical upgrade from 4.6c to 6.0ecc with unicode conversion
Hi Experts,
Can you explain me technical upgrade from 4.6c to 6.0ecc with Unicode conversion.
if u got any notes pls send it to [email protected]
vijayCheck these links. Search SDN with Term "Upgradation" you will get lot of links
http://help.sap.com/saphelp_nw04/helpdata/en/16/4b3c88170e11d6999d00508b6b8b11/frameset.htm
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f0f9f37c-be11-2a10-3baf-d5d7de5fb78d
http://www.sdn.sap.com/irj/sdn/wiki?path=/display/unicode/system%2blandscape%2bconversion
http://www.sdn.sap.com/irj/sdn/wiki?path=/display/unicode/project%2bplanning%2b-%2bmdmp%2bsystem
http://www.sdn.sap.com/irj/sdn/wiki?path=/display/unicode/communication%2binterfaces
Message was edited by: Jason Lax (Removed link to deleted content) -
Upgrade from R/3 4.7 to ECC 5.0
Hello Everyone
This is my very first post on SDN. I am going to do an upgrade from R/3 4.7 to ECC 5.0. Can anyone please tell me how do I start and procede, this will be my very first upgrade and I definitely need help!!!. I will be really thankful if anyone can give me any suggestions as to how to procede with the planning and then the actual upgrade. What documentation from the service.sap.com should I follow???........PLS help!!!Dear Mir,
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 -
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.0Hi 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 -
Upgrade from R/3 4.6C to ECC 6.00 : languages
Hi,
We're trying to upgrade from SAP R/3 4.6C to ECC 6.00 under NT environment, having Oracle as database. During the preparation phase, we got the following error, and in our current SAP system R/3 we have 2 additional languages NL and FR (EN and DE are already in), can you please explain why this phase is blocking in this step, and if I continue I've to do a full language import, thanks in advance.
The following language(s) could not be updated yet:
- French for component EA-APPL
- French for component EA-DFPS
- French for component EA-FINSERV
- French for component EA-GLTRADE
- French for component EA-HR
- French for component EA-IPPE
- French for component EA-PS
- French for component EA-RETAIL
- French for component ECC-DIMP
- French for component ERECRUIT
- French for component FI-CA
- French for component FI-CAX
- French for component FINBASIS
- French for component INSURANCE
- French for component IS-CWM
- French for component IS-H
- French for component IS-M
- French for component IS-OIL
- French for component IS-PS-CA
- French for component IS-UT
- French for component LSOFE
- French for component PI_BASIS
- French for component SAP_ABA
- French for component SAP_AP
- French for component SAP_APPL
- French for component SAP_BASIS
- French for component SAP_BW
- French for component SAP_HR
- French for component SEM-BW
- French for component ST-PI
- Dutch for component EA-APPL
- Dutch for component EA-DFPS
- Dutch for component EA-FINSERV
- Dutch for component EA-GLTRADE
- Dutch for component EA-HR
- Dutch for component EA-IPPE
- Dutch for component EA-PS
- Dutch for component EA-RETAIL
- Dutch for component ECC-DIMP
- Dutch for component ERECRUIT
- Dutch for component FI-CA
- Dutch for component FI-CAX
- Dutch for component FINBASIS
- Dutch for component INSURANCE
- Dutch for component IS-CWM
- Dutch for component IS-H
- Dutch for component IS-M
- Dutch for component IS-OIL
- Dutch for component IS-PS-CA
- Dutch for component IS-UT
- Dutch for component LSOFE
- Dutch for component PI_BASIS
- Dutch for component SAP_ABA
- Dutch for component SAP_AP
- Dutch for component SAP_APPL
- Dutch for component SAP_BASIS
- Dutch for component SAP_BW
- Dutch for component SAP_HR
- Dutch for component SEM-BW
- Dutch for component ST-PI
Please mount another Language Disk for these language(s).
If you do not have further Language Disk(s), you may
continue, but the languages mentioned above will be lost
after the upgrade. A full language import has to be
performed after the upgrade to reinstall the language(s).
? continue
? cancelHi Markus,
I've introduce the following information:
> MOUNT POINT 07 = S:\export\Data\CDLAN2
> MOUNT POINT 01 = S:\export\Data\KN_WINDOWS_X86_64_AUPG
> MOUNT POINT 06 = S:\export\Data\CDLAN1
> MOUNT POINT 05 = S:\export\Data\CD3
> MOUNT POINT 03 = S:\export\Data\CD1
> MOUNT POINT 08 = S:\export\Data\UMN_WINDOWS_X86_64
> MOUNT POINT 02 = S:\export\Data\KN_WINDOWS_X86_64
> MOUNT POINT 04 = S:\export\Data\CD2
And in mount point 06/07 we have the languages.
The content of the trace file is:
here's the complete trace:
2007/07/05 16:35:01 *****************************
2007/07/05 16:35:01 Checking directories ...
2007/07/05 16:35:01 Searching for Data Carrier labeled AOXUPGR
Adding path: S:\export\Data\KN_WINDOWS_X86_64_AUPG
2007/07/05 16:35:01 Working on S:\export\Data\KN_WINDOWS_X86_64_AUPG ... no matching label
Adding path: S:\export\Data\KN_WINDOWS_X86_64
2007/07/05 16:35:01 Working on S:\export\Data\KN_WINDOWS_X86_64 ... no matching label
Adding path: S:\export\Data\CD1
2007/07/05 16:35:01 Resolving directory structure below S:\export\Data\CD1
Adding path: S:\export\Data\CD1\UPG1
Adding path: S:\export\Data\CD1\UPG2
Adding path: S:\export\Data\CD1\UPG3
Adding path: S:\export\Data\CD1\UPG4
Adding path: S:\export\Data\CD1\UPG5
Adding path: S:\export\Data\CD1\UPG6
2007/07/05 16:35:01 Directory structure below S:\export\Data\CD1 resolved
2007/07/05 16:35:01 Working on S:\export\Data\CD1 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG1 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG2 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG3 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG4 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG5 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG6 ... no matching label
Adding path: S:\export\Data\CD2
2007/07/05 16:35:01 Resolving directory structure below S:\export\Data\CD2
Adding path: S:\export\Data\CD2\UPG7
Adding path: S:\export\Data\CD2\UPG8
Adding path: S:\export\Data\CD2\UPG9
Adding path: S:\export\Data\CD2\UPG10
Adding path: S:\export\Data\CD2\UPG11
Adding path: S:\export\Data\CD2\UPG12
2007/07/05 16:35:01 Directory structure below S:\export\Data\CD2 resolved
2007/07/05 16:35:01 Working on S:\export\Data\CD2 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG7 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG8 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG9 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG10 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG11 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG12 ... no matching label
Adding path: S:\export\Data\CD3
2007/07/05 16:35:01 Resolving directory structure below S:\export\Data\CD3
Adding path: S:\export\Data\CD3\UPG13
Adding path: S:\export\Data\CD3\UPG14
Adding path: S:\export\Data\CD3\UPG15
Adding path: S:\export\Data\CD3\UPG16
2007/07/05 16:35:01 Directory structure below S:\export\Data\CD3 resolved
2007/07/05 16:35:01 Working on S:\export\Data\CD3 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD3\UPG13 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD3\UPG14 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD3\UPG15 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD3\UPG16 ... no matching label
Adding path: S:\export\Data\CDLAN1
2007/07/05 16:35:01 Resolving directory structure below S:\export\Data\CDLAN1
Adding path: S:\export\Data\CDLAN1\LANG1
Adding path: S:\export\Data\CDLAN1\LANG2
Adding path: S:\export\Data\CDLAN1\LANG3
Adding path: S:\export\Data\CDLAN1\LANG4
2007/07/05 16:35:01 Directory structure below S:\export\Data\CDLAN1 resolved
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN1 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN1\LANG1 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN1\LANG2 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN1\LANG3 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN1\LANG4 ... no matching label
Adding path: S:\export\Data\CDLAN2
2007/07/05 16:35:01 Resolving directory structure below S:\export\Data\CDLAN2
Adding path: S:\export\Data\CDLAN2\LANG5
Adding path: S:\export\Data\CDLAN2\LANG6
2007/07/05 16:35:01 Directory structure below S:\export\Data\CDLAN2 resolved
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN2 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN2\LANG5 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN2\LANG6 ... no matching label
Adding path: S:\export\Data\UMN_WINDOWS_X86_64
2007/07/05 16:35:01 Working on S:\export\Data\UMN_WINDOWS_X86_64 ... no matching label
Regards,
A.Kamel -
Major considerations for the Upgrade from R/3 4.6c to ECC on HR Part.
Hi Experts,
We are doing an upgrade from SAP R/3 4.6c to ECC 6.0
What would be the impact on Personnel Administration and Organizational Management submodules of HR? and the major worries abt ESS and MSS. Currently my client is using ESS and MSS in portal that can retrieve the data from the Backend 4.6c system. while doing upgrade is there any prerequisites i need to met or is there any post upgrade activities for HR or is there Any dependencies?
Because there is a complete architecutre difference for ESS and MSS in both versions, so how can i manage the things without data inconsistencies?
Responses would be heighly appreciated.
Regards,
SriniHi Experts,
We are doing an upgrade from SAP R/3 4.6c to ECC 6.0
What would be the impact on Personnel Administration and Organizational Management submodules of HR? and the major worries abt ESS and MSS. Currently my client is using ESS and MSS in portal that can retrieve the data from the Backend 4.6c system. while doing upgrade is there any prerequisites i need to met or is there any post upgrade activities for HR or is there Any dependencies?
Because there is a complete architecutre difference for ESS and MSS in both versions, so how can i manage the things without data inconsistencies?
Responses would be heighly appreciated.
Regards,
Srini -
Technical Upgrade from 4.6c to Ecc 6.0
Hello All.
We have upgraded the system from 4.6c to ECC 6.0.
We have got SPAU list and Unicode(UCCCHECK) program list.We have shortage of time to resolve both the list.
I have few questions.
1) Do we need to resolve UCCCHECK list first or SPAU list.
2) How we can modify programs,tables in SPAU list.
Could you please give Some step by step need to perform in SPAU list.
3)How we can convert UCCCHEK list
Could you please give STEP by STEP procedure and transaction code.
Thanks in Advance
MuthuHi Muthu,
Please [check this link|http://help.sap.com/saphelp_nw04/helpdata/EN/83/7a18ecde6e11d195460000e82de14a/content.htm].Do the same with SPDD too.
SPAU has to be done before going for the UCCHECK of custom objects.
Thanks,
Sai -
Technical upgradation from 4.6c to ecc6.0 without unicode
Hi all,
Now i am working in Upgradation Project from 4.6c to ECC6.0.so our system is upgraded to ECC6.0(new development) and i am trying to run transaction KES2 ,but this trnsaction is giving short dump to me.
why because in newer version some tables like T280 are added and is not exist in older version.
i took access key for one include to comment out which all these extra tables are added but while i am clicking on change button it gives one message like "this include is forbidden by SAP*".
Please help me out in this case.
Points will be rewarded for helpfull answers.
Thanks and Regards
Samitdifference between 4.7 and ecc 6.0
Reward points please.. -
Upgrade from SAP 4.7 EE to ECC 6 while working with CRM 4.0
Hi All,
Presently we are using R/3 version 4.7 EE with CRM 4.0 and now we are planning to upgrade R/3 4.7 to ECC.6.0. My question is, are there any problems working on CRM 4.0 with ECC 6.0 and what are the limitation we face when we work on CRM 4.0 with ECC 6.0 ?. Please provide some inputs on this ASAP.
Thanks in advance,
J M.Hi,
There is no problem to work on CRM 4.0 with ECC 6.0.
I am using from long time CRM 4.0 with ECC6.0
BR,
Darshan.. -
Problem with Java Script after upgrade from BW 3.5 to BI7
Dear Colleagues,
We're facing the issue with Java Script after upgrade of BW 3.5 to BI7.
Just after update we checked the basic functionality and it occured that some of web templates that use Java Script don't work. They generate seelction screen, but after selection the screen becomes blank without any error messages.
We're currently stucked since web templates weren't converted to BI7 version so they should work exactly as before the upgrade.
We compared the Java code with other environment that was not upgraded - it's perfectly the same.
The only explanation that comes to my mind is that some Java Script settings on the server level were changed during the upgrade but I have no idea where I can check that.
Thanks in advance for any suggestions,
Andrzej BobulaHi Deepu,
Thanks, it was great to read your reply and then few minutes later talk to you live on SDN Day!
Unfortunately, http cache clean-up did not help. But there is another funny thing I found - for exactly the same 3.5 webtemplate html code returned from WebAS 3.5 was different then from 7.0.
Unfortunately, this editor does not allow to paste complete code, even in CODE brackets, but here are main differences:
<b>3.5</b>
if (navigator.appName == "Microsoft Internet Explorer")
<frame src="/sap/bw/BEx?SAP-LANGUAGE=E&PAGENO=1&REQUEST_NO=1&CMD=GET_TEMPLATE"
name="Content">
and
<b>7.0</b>
if (navigator.appName.indexOf("Microsoft Internet Explorer")!=-1)
<frame src="/sap/bw/BEx?SAP-LANGUAGE=E&PAGENO=8&REQUEST_NO=0&CMD=GET_TEMPLATE"
name="Content" 0nLoad="javascript:loadTitle()">
(I intentionaly put 0 i/o o in 0nLoad, otherwise Forum's editor does not accept the text.
How about SAP's claim that technical upgrade from 3.x to 7.0 changes nothing?
Regards,
Vitaliy -
Upgrade from 4.6c to ecc 6.0
Hi,
We are doing a technical upgrade from 4.6c to ecc 6.0 without activating New GL. As a functional consultant, what should i look for? I know that we need to test the business processes and check Z programs but anything specific, plzz let me know.
What changes should be made in Asset Accounting?
Regards
SatyaThanks for the reply.
What are the changes made in Asset accounting after upgrading?
I heard of RBE tool...how is it used for FI?? (u check for the mostly used transactions or what??)
Anyone, plzz answer..waiting for ur replies
Regards
Satya
Maybe you are looking for
-
Window Position & Prefs "Gone"
Every time I start up or restart, any window position, size, view etc info is gone, and I get a view very different than what I had set. I have tried to delete the Finder plist, but it did not help. I did notice something extremely weird as well. I n
-
Runtime OS command before Message processing
Hi all, I have a scenario where the input file from a particular FTP server has to be moved to XI server and then process the message from there. For this I am trying to use "Runtime OS command before Message processing" My problem is that how do I d
-
Monitor resolution & increasing font size
I am a pc user swithcing to mac... I have an external non-apple monitor whose native resolution is 1400 x 900, so I have set the mac to that resolution. 1) does the mac have a "native" resoltuion, or is any option offered "native"? 2) More importantl
-
No name for ok_code in element list
Subscreen 0111 is made available by enhancement MEREQ001. I am adding more fields, and I also want to read the ok_code in the PAI. There is no name assigned to the ok_code in the element list. I would like to add a name here, but it is not editable,
-
Precisely control position of prompts
I have 4 different prompts I am using on a dashboard for date, region, salesgroup and salesrep. I have placed the prompts on the left side of my dashboards but the prompts will not align. I want each prompt to be the same length within the prompts se