Key issues involved while technical upgrade of 4.6c to ecc 6

Hi Guru's
Will anyone share the key issues and time consuming activities involved in tech upgrade project from 4.6 c to ecc 6 at different stages.
Mail me [email protected]
Reward full points for the answer
Regards,
Venkat

Dear Venkatesh ,
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

Similar Messages

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
BE

Hi,
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 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

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
Muthu

Hi 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 Upgrade & Testing

We are doing technical upgrade from 4.6C to ECC 6.0.
After we are through with the SPDD and SPAU modificaitons in the development environment, do we need to Functional Unit Test (by unit test, I mean complete fucntionality test) in there for all the objects in these SPAU and SPDD lists?
Or is there any other way I can get all the programs tested. I am asking cause we have about 3000 objects in the SPAU list and we need to work on the modifications within a span of 3-4 weeks only!
Any help is appreciated.

Hello Anand,
When upgrading from 4.6c to ECC 6 I would recommend complete functional unit test for all your company's business processes. This should include some kind of regression testing to ensure that existing functionality still works as well as the functionality that may have changed as indicated by the objects on the SPAU and SPDD lists.
Having said that I understand the reality of a short implementaion time. You may need to narrow your testing focus to just critical business processes. Or you could use SPAU to identify where major changes have occured. Either way this is not a support pack but a major upgrade and testing will be extensve.
I know that this is not a great help. Hope the upgrade goes well.
Regards
Greg Kern,

Technical Upgrade without Unicode

Hello,
Is it possible to do a technical upgrade from 4.70 to ecc 6.0 without doing the unicode conversions? we are trying to do a cost efficient way of doing an upgrade.
thanks.

I executed UCCHECK. The result shows:
Check a Program Set for Syntax Errors in Unicode Environment
Could not determine program name:
FUGR                                        GRWT                          SAP         SAP
Could not determine program name:
PROG                                        MLDB                          SAP         SAP
There are only 2 errors. Why is this so when I checked SYSTEM->STATUS under unicode is says NO.
Is there an error? thanks.

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
Satya

Thanks 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

What are the key points to beconsider while upgrading from 4.7 to ECC 6.0

hai
What are the key points to beconsider while upgrading from 4.7 to ECC 6.0
please provide sufficient material
points will be rewarded
regards
v.sridhar

Hi Sridhar,
Please visit the following links:
http://service.sap.com/erp
http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional perspective)
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, and 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.
When you are upgrading from 4.6C to ECC6
Nothing major, follow the same process you'd follow if you were updating PI service packs in R/3 or enhancing data sources. Empty queues in RSA7 and lbwq. Also empty setup tables through lbwg as the upgrade doesn't like it if these tables contain data. This is all on the R/3 side (although you empty RSA7 by running each delta TWICE in BW).
To transfer queues from lbwq to rsa7, execute jobs through LO cockpit (lbwe).
Some of your data sources could also be using sm13 instead of lbwq, so do check it out as well.
For installing ECC 6.0 you required a solution manager key. With out solution manager key you cannot install ECC6.0.
For ECC 6.0 is called net weaver component here you have ABAP+JAVA stack.
ECC6.0 supports UNCODE.
For installing 4.6 you don't require solution manager key. It only having ABAP stack.
4.6C supports NONUNICODE.
Major difference is ECC6 is netwear product having WASJAVA+ABAP
secondly support unicode apart from this we have other diff. you can get form master guide from service.sap.com/instguides.
Please go through the link that is shown here and if there is any doubts then feel free to ask.
Major difference is ECC6 is net weaver product having WASJAVA+ABAP
secondly support Unicode apart from this we have other diff. you can get from master guide from service.sap.com/instguides
For installing ECC 6.0 you required a solution manager key. With out solution manager key you cannot install ECC6.0.
For ECC 6.0 is called net weaver component here you have ABAP+JAVA stack.
ECC6.0 supports UNCODE.
For installing 4.6 you don't required solution manager key. It only having ABAP stack.
4.6C supports NONUNICODE.
Please also Refer sdn thread and make a small search where u can find lot of information Reg this
olution Browser would give the differences (Features):
http://solutionbrowser.erp.sap.fmpmedia.com/ Give source and target versions.
Release Info:
ECC 6.0:
http://help.sap.com/saphelp_erp2005/helpdata/en/43/68805bb88f297ee10000000a422035/frameset.htm
Refer below and search for posts on this topic on sdn
There are so many differences between the version in different objects
I
These are the some of the settings that are differed in the two versions and in that two objects
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/
Upgrade from 4.6c to 6.0 ECC
upgrade from 4.7 to ecc 6.0
Please Do Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

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.

Authorization issue after technical upgrade

We just completed an uprade to BI 7.0 SP 15. We only want to complete a technical upgrade and use the old security model.
We have found that when users run queries against multi-providers they aren't authorized. BEX states that the user doesnt have access.
Should our old authorizations work with the old model against multi-providers?

In theory yes ..
Some Analysis ..
from the S_RS_COMP
goto RSECADMIN >Analysis>Execution as User -->enter the user name you are executing the query
Check box -->with Log option
select RSRT option
hit start transaction button ,it should show you the authoriztion errors with authorization objects missed.
if not
again RSECADMIN>Analysis>Error Logs-->check with the latest time stamp for that particular user and analyse the authorization issues
Hope it Helps
Chetan
@CP

Technical Upgrade Query Issue .

Dear ,
We are updating our system from ECC4.7 to ECC 6.0 .
I come across the issue that Queries are not updated in system .
Some of the queries I have resolved by going in transaction SQ01 simply by acivating it and execute but in some of the
objects query name does not exist in old system but report execute there .
In new system 6.0 this not even executing . What the problem that not able to identified .
For example :
Query is this : AQFKSYSTQV000015ZPODET========
Query name is : ZPODET
This is not exist in both the system but its running fine in old system .
Please suggest any solution for this if u have any .
Rgds Aryan
Edited by: Aryan@sap on Nov 11, 2009 10:59 AM

Hi,
This is the most common issue faced during the Upgrades.
1) First go to SE37 and execute the FM: RSAQ_GENERATE_PROGRAM by entering the Query name and the User group.
2) You can get the link for SAP Query and User groups from the table AQLQCAT(local areas) and AQGQCAT(global areas)
3) Finally after the query is generated, you will get the program name as output of the FM.
4) Check this program exists in SE38.
If you want to generate more queries try writing a simple report using the above logic....
OR Simply go to SQ01 and try to generate each query from the menu->Query>More Functions->Generate Program
The same process needs to be done in all the systems(old/new/dev/quality/prod systems)
For your help, AQFKSYSTQV000015ZPODET======== the name of query and user group can be determined as:
First 4 char : system specific
Next 12 Char : User Group
Next 12 Char : Query name.
Wherever names are less than 12 chars then the = are added.
Hope this helps
Regards
Shiva

What r the steps that involve while v r using DBCONNECT AND UDCONNEC

Hi All,
What r the steps that involve while v r using DBCONNECT AND UDCONNECT AND IN WHICH DIFFERENT SCENARIOS V USE THEM.
REGARDS
KK

Hi,
To Configure UD Connect on the J2EE Server for JDBC Access to External Databases;
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/58f4db47-0501-0010-a2bf-ff01b150fdff
To create Driver on JDBC side
http://help.sap.com/saphelp_nw70/helpdata/en/b0/6e62f30cbe9e44977c78dbdc7a6b27/frameset.htm
Configuring the BI Java Connectors
http://help.sap.com/saphelp_nw70/helpdata/en/43/e35b3315bb2d57e10000000a422035/frameset.htm
Then to extract data use this...
Before you can transfer data from UD Connect sources into BI, you have to generate the metadata (the information about the source object and source object elements) in BI, in the form of a DataSource with a function module for extraction.
If your dataflow is modeled with objects based on the old concept (InfoSource 3.x, transfer rules 3.x, update rules 3.x), you can generate a DataSource 3.x for transferring data into BI from a database source system.
Prerequisites
You have modeled the InfoObjects that you want to use in the InfoSource and the data target or InfoProvider according to the UD Connect source object elements.
Note the following background information:
Using InfoObjects with UD Connect
Data Types and Their Conversion
Using the SAP Namespace for Generated Objects
Procedure
You are in the Modeling InfoSource tree of the Administrator Workbench. First create in InfoSource and activate the communication structure. Then generate the generic DataSource using the wizard in the InfoSource maintenance.
1. Choose InfoSources ® Your Application Component ® Context Menu (right mouse click) ® Create InfoSource.
2. Select the type of the InfoSource.
3. Under InfoSource, enter the technical name of the InfoSource, and assign a description and choose Continue.
The system creates an InfoSource and shows it in the InfoSource tree under your application components.
4. In the context menu of the InfoSource, choose Change .
The communication structure maintenance screen appears.
5. Using the previously modeled InfoObjects, create the communication structure (see Communication Structure).
6. Save and activate your communication structure
7. In the dialog box that follows you will be asked whether you wish to activate the dependent transfer program. Choose No.
8. In the InfoSource menu, choose Extras ® Create BW DataSource with UD Connect.
You get to the dialog box where you can assign a UD Connect source object to a DataSource and then generate the DataSource with the extractor. The fields for the DataSource are already being displayed in the table on the left side of the screen. The fields have the same name as the InfoObjects that you have used in the InfoSource.
9. Select the RFC Destination for the J2EE Engine.
Make sure that the local server is running. If the local server is running and you cannot open the table for RFC destinations, start the local server again.
10. Choose the UD Connect Source in which the data that you wish to access is located.
All available sources that are connected to the J2EE Engine are provided for selection in the input help. n instances are available per adapter.
11. Select the UD Connect Source Object.
All available source objects that are available in the selected UD Connect source are provided for selection in the input help. Source objects can be multi-dimensional storage or relational objects.
The system generates the name of the DataSource in the namespace 6B.
The DataSource is then replicated in BI.
The myself system is assigned to the InfoSource as source system as well as the DataSource.
The system generates a proposal for the transfer rules.
Since the DDIC structure and the function module are located in the SAP namespace, the following entries can be requested during generation:
Developer and object key or
Developer key or
Object key and
Transport request
If you do not make the requested entries, the generated infrastructure is not usable.
14. Change or complete the transfer rules as needed. For example, if a source object element is not assigned to a unit InfoObject, you can determine a constant for the unit, such as EUR for 0LOC_CURRCY (local currency).
15. Save and activate your transfer rules.
Recognizing Manual Entries
You can enter and change the RFC Destination, UD Connect Source and UD Connect Source Object manually. In order to validate these entries and the ones that depend on them, choose Recognize Manual Entries. For example, if you change the selected RFC destination, all of the field contents (US Connect Source, UD Connect Source Object, list of the source object elements) are invalid. If you choose Recognize Manual Entries, the dependent field contents are initialized and have to be maintained again.
Result
You have created the InfoSource and DataSource for data transfer with UD Connect. In the DataSource overview for the myself system, you can display the DataSource under the application components Non-Assigned Nodes.
When modeling InfoObjects in BI, note that the InfoObjects have to correspond to the source object elements with regard to the type description and length description. For more information about data type compatibility, see Data Types and Their Conversion.
The following restrictions apply when using InfoObjects:
Alpha conversion is not supported
The use of conversion routines is not supported
Upper and lower case must be enabled
These InfoObject settings are checked when they are generated.
Based on the large number of possible UD Connect sources, the most diverse data types are possible in the output system. For this reason, a compatibility check is made at the time of generation of the UD Connect DataSource that is based on the type information supplied by the source systems. This attempts to decrease the probability of errors during the extraction process.
(Refernce:SAP Notes)
Hope this helps,
regards
CSM Reddy

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]

Terminus 9pt font issue in Konsole after upgrade

I have a slightly weird font issue in Konsole following a bunch of upgrades today. Basically, at the beginning of the command line and the beginning of subsequent words on that line, the very first character sort of flashes and gets truncated if it is one of several letters. Very narrow characters are not affected (e.g. i) but most are (e.g. n, g, m, r etc.). Once I press enter, the characters look perfectly normal - the issue only occurs on the line being edited and while I am entering or within words as opposed to spaces. Moreover, it only occurs for the first letters of words. Subsequent letters look fine. Once a space is typed following the first word, the character looks normal unless and until I type another letter or return to edit the first word. If I type "cat" it will be a truncated c; at "cat " all looks fine; then "cat c" and the first c is truncated; "cat cat " all is well; "cat c" with the cursor moved back over the second c and the second c rather than the first is truncated.
Any thoughts as to what I should check? I'm using the infinality stuff from AUR. I updated that last night. However, I don't _think_ I saw the issue today until after upgrading the kernel. Here are the last entries from pacman.log:
[2012-04-06 00:46] Running 'pacman -U gcc-gcj-4.7.0-1-x86_64.pkg.tar.xz'
[2012-04-06 00:46] upgraded gcc-gcj (4.6.3-1 -> 4.7.0-1)
[2012-04-06 00:46] Exited with code 0
[2012-04-06 00:46] Running 'pacman -U pdftk-1.44-6-x86_64.pkg.tar.xz'
[2012-04-06 00:46] upgraded pdftk (1.44-5 -> 1.44-6)
[2012-04-06 00:46] Exited with code 0
[2012-04-06 00:58] Running 'pacman -U freetype2-infinality-2.4.9-1-x86_64.pkg.tar.xz'
[2012-04-06 00:58] ==> Infinality environment variables are located in the file /etc/profile.d/infinality-settings.sh. Change it according to your taste.
[2012-04-06 00:58] ==> Fontconfig files have moved to fontconfig-infinality package which should be installed and configured separately.
[2012-04-06 00:58] ==> For best experience, install either Windows, Apple or Google fonts. More information is available at http://www.infinality.net.
[2012-04-06 00:58] upgraded freetype2-infinality (2.4.8-5 -> 2.4.9-1)
[2012-04-06 00:58] Exited with code 0
[2012-04-06 00:58] Exited with code 0
[2012-04-06 01:01] Running 'pacman -U lib32-freetype2-infinality-2.4.9-1-x86_64.pkg.tar.xz'
[2012-04-06 01:01] upgraded lib32-freetype2-infinality (2.4.8-5 -> 2.4.9-1)
[2012-04-06 01:01] Exited with code 0
[2012-04-06 01:06] Running 'pacman -U dpkg-1.16.2-1-x86_64.pkg.tar.xz'
[2012-04-06 01:06] upgraded dpkg (1.16.1.2-2 -> 1.16.2-1)
[2012-04-06 01:06] Exited with code 0
[2012-04-06 01:06] Exited with code 0
[2012-04-06 03:15] Running 'pacman -Syu'
[2012-04-06 03:15] synchronizing package lists
[2012-04-06 03:15] starting full system upgrade
[2012-04-06 03:16] upgraded util-linux (2.21-6 -> 2.21.1-2)
[2012-04-06 03:16] upgraded kmod (7-1 -> 7-2)
[2012-04-06 03:16] upgraded udev (181-5 -> 181-9)
[2012-04-06 03:16] upgraded bluez (4.99-1 -> 4.99-2)
[2012-04-06 03:16] upgraded filesystem (2012.2-2 -> 2012.2-4)
[2012-04-06 03:16] upgraded laptop-mode-tools (1.60-1 -> 1.60-2)
[2012-04-06 03:16] upgraded libgpod (0.8.2-3 -> 0.8.2-4)
[2012-04-06 03:16] upgraded libmtp (1.1.2-1 -> 1.1.2-2)
[2012-04-06 03:16] upgraded lm_sensors (3.3.2-1 -> 3.3.2-2)
[2012-04-06 03:16] upgraded mkinitcpio (0.8.5-1 -> 0.8.6-2)
[2012-04-06 03:16] upgraded pcmciautils (018-2 -> 018-4)
[2012-04-06 03:16] upgraded syslog-ng (3.3.4-4 -> 3.3.4-5)
[2012-04-06 03:16] upgraded system-config-printer-common (1.3.9-1 -> 1.3.9-2)
[2012-04-06 03:16] upgraded tzdata (2012b-3 -> 2012c-1)
[2012-04-06 03:16] upgraded udisks (1.0.4-2 -> 1.0.4-3)
[2012-04-06 03:16] Exited with code 0
[2012-04-06 20:23] Running 'pacman -Syu'
[2012-04-06 20:23] synchronizing package lists
[2012-04-06 20:23] starting full system upgrade
[2012-04-06 20:27] upgraded chromium (18.0.1025.142-1 -> 18.0.1025.151-1)
[2012-04-06 20:27] upgraded foomatic-db (1:4.0.7_20110707-1 -> 1:4.0.15_20120406-1)
[2012-04-06 20:27] upgraded foomatic-filters (1:4.0.7_20110707-1 -> 1:4.0.15_20120406-1)
[2012-04-06 20:27] upgraded foomatic-db-engine (1:4.0.7_20110707-1 -> 1:4.0.15_20120406-1)
[2012-04-06 20:27] upgraded foomatic-db-nonfree (1:4.0.7_20110707-1 -> 1:4.0.15_20120406-1)
[2012-04-06 20:27] upgraded gnutls (3.0.17-1 -> 3.0.18-1)
[2012-04-06 20:27] >>> Updating module dependencies. Please wait ...
[2012-04-06 20:27] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2012-04-06 20:27] ==> Building image from preset: 'default'
[2012-04-06 20:27] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2012-04-06 20:27] ==> Starting build: 3.2.14-1-ARCH
[2012-04-06 20:27] -> Parsing hook: [base]
[2012-04-06 20:27] -> Parsing hook: [udev]
[2012-04-06 20:27] -> Parsing hook: [autodetect]
[2012-04-06 20:27] -> Parsing hook: [pata]
[2012-04-06 20:27] -> Parsing hook: [scsi]
[2012-04-06 20:27] -> Parsing hook: [sata]
[2012-04-06 20:27] -> Parsing hook: [resume]
[2012-04-06 20:27] -> Parsing hook: [filesystems]
[2012-04-06 20:27] -> Parsing hook: [usbinput]
[2012-04-06 20:27] -> Parsing hook: [fsck]
[2012-04-06 20:27] ==> Generating module dependencies
[2012-04-06 20:27] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2012-04-06 20:27] ==> Image generation successful
[2012-04-06 20:27] ==> Building image from preset: 'fallback'
[2012-04-06 20:27] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2012-04-06 20:27] ==> Starting build: 3.2.14-1-ARCH
[2012-04-06 20:27] -> Parsing hook: [base]
[2012-04-06 20:27] -> Parsing hook: [udev]
[2012-04-06 20:27] -> Parsing hook: [pata]
[2012-04-06 20:27] -> Parsing hook: [scsi]
[2012-04-06 20:27] -> Parsing hook: [sata]
[2012-04-06 20:27] -> Parsing hook: [resume]
[2012-04-06 20:27] -> Parsing hook: [filesystems]
[2012-04-06 20:27] -> Parsing hook: [usbinput]
[2012-04-06 20:27] -> Parsing hook: [fsck]
[2012-04-06 20:28] ==> Generating module dependencies
[2012-04-06 20:28] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2012-04-06 20:28] ==> Image generation successful
[2012-04-06 20:28] upgraded linux (3.2.13-1 -> 3.2.14-1)
[2012-04-06 20:28] upgraded linux-docs (3.2.13-1 -> 3.2.14-1)
[2012-04-06 20:28] upgraded linux-headers (3.2.13-1 -> 3.2.14-1)
[2012-04-06 20:28] >>> Updating module dependencies. Please wait ...
[2012-04-06 20:28] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2012-04-06 20:28] ==> Building image from preset: 'default'
[2012-04-06 20:28] -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts.img
[2012-04-06 20:28] ==> Starting build: 3.0.27-1-lts
[2012-04-06 20:28] -> Parsing hook: [base]
[2012-04-06 20:28] -> Parsing hook: [udev]
[2012-04-06 20:28] -> Parsing hook: [autodetect]
[2012-04-06 20:28] -> Parsing hook: [pata]
[2012-04-06 20:28] -> Parsing hook: [scsi]
[2012-04-06 20:28] -> Parsing hook: [sata]
[2012-04-06 20:28] -> Parsing hook: [resume]
[2012-04-06 20:28] -> Parsing hook: [filesystems]
[2012-04-06 20:28] -> Parsing hook: [usbinput]
[2012-04-06 20:28] -> Parsing hook: [fsck]
[2012-04-06 20:28] ==> Generating module dependencies
[2012-04-06 20:28] ==> Creating gzip initcpio image: /boot/initramfs-linux-lts.img
[2012-04-06 20:28] ==> Image generation successful
[2012-04-06 20:28] ==> Building image from preset: 'fallback'
[2012-04-06 20:28] -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts-fallback.img -S autodetect
[2012-04-06 20:28] ==> Starting build: 3.0.27-1-lts
[2012-04-06 20:28] -> Parsing hook: [base]
[2012-04-06 20:28] -> Parsing hook: [udev]
[2012-04-06 20:28] -> Parsing hook: [pata]
[2012-04-06 20:28] -> Parsing hook: [scsi]
[2012-04-06 20:28] -> Parsing hook: [sata]
[2012-04-06 20:28] -> Parsing hook: [resume]
[2012-04-06 20:28] -> Parsing hook: [filesystems]
[2012-04-06 20:28] -> Parsing hook: [usbinput]
[2012-04-06 20:28] -> Parsing hook: [fsck]
[2012-04-06 20:28] ==> Generating module dependencies
[2012-04-06 20:28] ==> Creating gzip initcpio image: /boot/initramfs-linux-lts-fallback.img
[2012-04-06 20:28] ==> Image generation successful
[2012-04-06 20:28] upgraded linux-lts (3.0.26-1 -> 3.0.27-1)
[2012-04-06 20:28] Exited with code 0
[2012-04-06 20:29] Exited with code 0
I'm using Terminus (TTF) in size 9 in Konsole. This hasn't been changed for quite a while.
Any suggestions on how best to troubleshoot this? Is it possible that I need to rebuild some other AUR packages associated with the infinality ones but which haven't actually been updated? Or is it likely to be to do with something else in the list?
EDIT: It only seems to be some fonts at some sizes e.g. Monaco 8pt is OK but Terminus 9pt isn't; Terminus 10pt is OK; etc.
Last edited by cfr (2012-04-07 00:18:15)

Applications/Font Book and validate your fonts.

Issue in AD connector upgrade from 9.1.1.7.0 to ICF based 11.1.1.5.0 in OIM11gR2 PS1

Hi,
I am facing issue while AD upgrade from 9.1.1.7.0 to 11.1.1.5.0(ICF) in OIM11gR2 PS1 environment in Linux environment.
In the last step where we need to select the connector objects to be upgraded, issue is for AD User ( Process form and definition) and AD Group (Process form).
The issue is related to the IT Resource Definition and it says, "Error: Could not resolve dependency. AD Server [ITResourceDef]".
In the preceding steps- for process forms field, process definition tasks and IT resource mapping, I am retaining/add everything ( all the existing tasks, fields, parameters).
Can anyone help me on this? or if anyone has peform the upgradation of AD from 9.1.1.7 to 11.1.1.5 (ICF), can they tell me the steps to do or anything about the above error?
Thanks
Piyush

That's tricky because their are usually huge changes between two connector versions if Oracle says that it cannot be upgraded.
In other words you would require study of these changes and try to simulate it by yourself in your Dev. Or identify the customizations in your past environment and then redo (as you suggested yourself). The second option is a bit difficult but clean.
Thanks
Sunny

Key issues involved while technical upgrade of 4.6c to ecc 6

Similar Messages

Maybe you are looking for