RFC Client Interface upgrade from 4.6c to ECC 6.0

We're currently using BODI v.6.1, and have an existing Client Interface using SAP 4.6c.
They now updgraded their system to ECC 6.0, and we're now having problem in connecting to that R/3 system, wherein the password logon being locked everytime we connect on it.
We have checked the release notes for BODI 6.1 and have SAP R/3 Enterprise (4.7) as it limitation.
I have also browsed that that for BODI 11.7, it could support SAP ECC 6.0 via ABAP, BAPI and IDOC
noting: Please note that this support is available on Data Integrator 11.7 only and not Rapid Marts. Check your Rapid Marts documentation to get the latest support information for that product.
Is there anyway we could connect the systems (BODI 6.1 to SAP ECC 6.0) in Client Interfaces?
Or this is really a versioning limitation?
Thanks in advance for your help.

Hi wdhaen,
Thanks for the reply.
Currently, we're trying to test this using our other BODI environment with v.11.7 running on it. We still can't connect in SAP R/3 when creating the datastore but I found this thread and successfully connected the datastore by changing the password to all CAPS.
(http://www.forumtopics.com/busobj/viewtopic.php?t=120167).
However, in the configuring the RFC client in the admin console, we still have an error:
Connect error...BODI-300116: Error connecting to CRM_CHAR_TEST1. Error: Connect to SAP gateway failed Connect_PM TPNAME=CRM_CHAR_TEST1, GWHOST=193.236.26.4, GWSERV=SAPGW00 LOCATION CPIC (TCP/IP) on local host ERROR internal error (this retcode should be handled by caller of NI-layer) TIME Wed May 13 17:15:28 2009 RELEASE 620 COMPONENT NI (network interface) VERSION 36 RC -8 MODULE nixx.c LINE 511 COUNTER 6 . For detailed error information, please see the log. RFC Client will try connecting to CRM_CHAR_TEST1 in the background. To stop trying to connect from the background, perform 'Shutdown'.
Any suggestion on this? Thanks!

Similar Messages

Upgrade from 4.6C to ECC 6.0 - change text of infotype 0002 screen

Hello Guru,
My client is upgrading from 4.6C to ECC 6.0. In 4.6C the field RUFNM text in infotype screen for 0002 is "Know As" where in ECC 6.0 is now "Nickname". The field is P0002-RUFNM? If I want to change the text in ECC 6.0 from 'Nickname' to "Know As". What is the best option? Modify the screen? or change the Data element? or any better way?
Thanks

Hi Bob,
To change the Field Text, Data Element would be the better option.
Good Luck
Om

Information on impact on interfaces due to upgrade from 4.7 to ECC 6.0

Hi friends,
We are upgrading from 4.7 to ECC 6.0. We have some interfaces with the SAP system in our current version.I need information on which of these interfaces will be affected due to Upgrade of the system to ECC 6.0
Mentioned below is the list
SAP R/3 --- CRM 5.0
SAP R/3 --- Xi PAY
SAP R/3 --- Vertex
SAP R/3 --- TEKRF
SAP R/3 --- Virsa
SAP R/3 --- WTX
SAP R/3 --- SOLMAN
It would be really helpful if you can just provide the initial impact analysis for these interfaces due to upgrade.Points will be rewarded.
Thank in advance.
Regards,
Pawan.

Hi
there are several oss-notes available which explain how to transfer your text customizing to the new procedure. This happens if you are uppgrading from a release 4.6c or lower. If you are already in 4.7, there should be no problem with text determination.
Regards
Rauno

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

Performance issue after Upgrade from 4.7 to ECC 6.0 with a select query

Hi All,
There is a Performance issue after Upgrade from 4.7 to ECC 6.0 with a select query in a report painter.
This query is working fine when executed in 4.7 system where as it is running for more time in ECC6.0.
Select query is on the table COSP.
SELECT (FIELD_LIST)
        INTO CORRESPONDING FIELDS OF TABLE I_COSP PACKAGE SIZE 1000
        FROM COSP CLIENT SPECIFIED
        WHERE GJAHR IN SELR_GJAHR
          AND KSTAR IN SELR_KSTAR
          AND LEDNR EQ '00'
          AND OBJNR IN SELR_OBJNR
          AND PERBL IN SELR_PERBL
          AND VERSN IN SELR_VERSN
          AND WRTTP IN SELR_WRTTP
          AND MANDT IN MANDTTAB
        GROUP BY (GROUP_LIST).
   LOOP AT I_COSP      .
     COSP                           = I_COSP      .
     PERFORM PCOSP       USING I_COSP-_COUNTER.
     CLEAR: $RWTAB, COSP                          .
     CLEAR CCR1S                         .
   ENDLOOP.
ENDSELECT.
I have checked with the table indexes, they were same as in 4.7 system.
What can be the reson for the difference in execution time. How can this be reduced without adjusting the select query.
Thanks in advance for the responses.
Regards,
Dedeepya.

Hi,
ohhhhh....... lots of problems in select query......this is not the way you should write it.
Some generic comments:
1. never use SELECT
                   endselect.
   SELECT
into table
   for all entries in table
where.
   use perform statment after this selection.
2. Do not use into corresponding fields. use exact structure type.
3. use proper sequence of fields in the where condition so that it helps table go according to indexes.
    e.g in your case
          sequence should be
LEDNR
OBJNR
GJAHR
WRTTP
VERSN
KSTAR
HRKFT
VRGNG
VBUND
PARGB
BEKNZ
TWAER
PERBL
sequence should be same as defined in table.
Always keep select query as simple as possible and perform all other calculations etc. afterwords.
I hope it helps.
Regards,
Pranaya

Upgrade from 4.7C to ECC 6.0

Hi Gurus,
I am going to do a functional upgrade from 4.7C to ECC 6.0 (classic GL, not new GL). Can someone please list me the steps that I need to do to achieve the upgrade.
I would be very grateful and would assign points as a gesture of appreciation.
Thanks
Chandan

If you are not going to implement new g/l, then all you have to do is test if all the transactions that the client is using are wokring fine in ECC 6.0 or not.Do the unit testing and integration testing and get business sign off.
Assign points if helpful

Table Enhancement Category during upgrade from 4.7 to ECC 6.0

When our sandbox was upgraded from 4.7 to ECC 6.0, Basis had the ABAP developers change the Enhancement Category on about 400 tables, some of which were custom tables. The enhancement category was previously u2018not classifiedu2019 on these tables.
Is this really necessary? Has anyone not changed the enhancement categories on tables that were flagged during the upgrade? Also, what happens if we select the wrong enhancement category?

Jane,
This is what SAP says,
Short Text
Enhancement Category Selection
Definition
Structures and tables that were defined by SAP in the ABAP Dictionary can be enhanced subsequently by customers using Customizing includes or append structures. The enhancements do not only refer to structures/ tables themselves, but also to dependent structures that adopt the enhancement as an include or referenced structure. Append structures that only take effect at the end of the original structure can also cause shifts - in the case of dependent structures - even within these structures.
You must select an enhancement category for the following reason: In programs where there is no active Unicode check, enhancements to tables and structures can cause syntax and runtime errors during type checks and particularly in combination with deep structures.
In programs where there is an active Unicode check, statements, operand checks, and accesses with an offset and length are problematic - for example, if numeric or deep components are inserted into a purely character-type structure and the structure thus loses its character- type nature.
Depending on the structure definition, the radio buttons allowed in the dialog box are ready for input. Choose one of the possible enhancement categories:
Cannot be enhanced
The structure must not be enhanced.
Can be enhanced or character type
All structure components and their enhancements must be character-type (C, N, D, or T). The original structure and all enhancements through Customizing includes or through append structures are subject to this limitation.
Can be enhanced or character-type or numeric
The structure and its enhancement must not contain any deep data types (tables, references, strings).
Can be enhanced in any way
The structure and its enhancement may contain components whose data type can be of any type.
Not classified
This category can be chosen, for example, for a transition status; however, it must not be chosen for creating structures.
The rules for defining the enhancement category result implicitly from the structure setup and the classification of the types used. These rules are as follows:
If the object contains at least one numeric type or a substructure or component (field has a structure/table/view as its type) that can be enhanced numerically, the object can no longer be enhanced character-type, but is itself, at most, enhanceable character-type or numeric.
If the object contains a deep component (string, reference, or table type), or it contains a substructure or component that is marked as enhanceable in any way, then the object itself is enhanceable in any way.
If the object does not contain any substructure or component that is marked as enhanceable, you can select cannot be enhanced. If the structure has not yet been enhanced, you can choose the category cannot be enhanced in any case.
If you are creating new tables and structures in the ABAP Dictionary, the system proposes the category can be enhanced in any way as standard value for the classification of the enhancement options. If the developer chooses a more restrictive classification than can be enhanced in any way for a particular structure, then only the classification levels that adhere to the rules above are allowed. It is not possible to choose an enhancement option of a structure that is more restrictive than the classification resulting immplicitly from the structure setup and from the classification of the types used. Therefore, only the allowed categories are proposed for selection in the maintenance user interface.
If a structure depends on one or several other structures, the smallest category is chosen as implicit classification (in the order cannot be enhanced < can be enhanced and character-type < can be enhanced and character-type or numeric < can be enhanced in any way). This classification is greater than or less than the category in the other structures and also greater than or the same as the category that results from the actual setup in the original structure itself.

Steps to follow in Upgrade from 4.7 to ECC 6.0

Hi ,
As part of Upgrade from 4.7 to ECC 6.0 , Basis team completed Prepare module.
Now Prepare module report says there are some modifications need to be done .
Do i need to make the changes to the adjustments populated in SPDD/ SPAU transaction code before basis team goes for Upgrade ?
If changes are applied to the modifications populated in SPDD / SPAU. How i need to transport these objects ?
Please let me know the steps need to take in transport of these objects .
Cheers,
Reddy

Dear,
Transaction SPDD allows you to adjust modifications to ABAP Dictionary objects during an upgrade, the upgrade will stop at the begin of ACT_700 phase, so you can logon to shadow instance and perform the adjustments in SPDD.
About transaction SPAU that allows you to adjust programs, function modules, screens, interfaces, documentation, and text elements after an upgrade.
You have the option to include the SPDD request from previous upgrade,
The PREPARE includes the ADJUSTPRP phase for this purpose. In this
phase, the system searches the global transport directory for comparison
requests from previous upgrades and offers these for inclusion in the
upgrade. If you do not have this request, you may go ahead with the upgrade
and the proceed with the SPDD / SPAU adjustments during the upgrade.
Please refer to the following SAP Notes for more details:
68678 Exporting modification adjustment for 2nd upgrade
610311 Importing a modification adjustment in 2nd upgrade
124522 Importing a modification adjustment in 2nd upgrade
I hope this helps.
Lucio Rodrigues

Re : Roles of Functional Consultant in upgradation from 4.6b to ECC 6.0

Hi
I need the Roles of Functional Consultant and Technical Consultant in upgradation from 4.6b to ECC 6.0.
Thanks
Anto

Dear Anto,
In Technical SAP,Upgrade from 4.6 to 6.0- the role of any fucntional consultant would involved integrated with the technical Consultant.
The phase starts with the technical Patches apply to the latest stack level which will done by the BASIS Consultants.
Once the System preparation is happened, the next phase is with SPDD phase, Thru this transaction the dictionary Objects-Database elements, database tables and structures of teh latest system can be
compared with the old system.
This results in the version modification results between the old and New versions. During this phase the involvement of the Functional Consultant needed for the tech guy, to identify the functional chnages between the two version (Old and New). Which helps for him either to Reset to Original(ie., adopting the new one) or Adopt Modification in previous system(ie., adopting to older functionality)
Once this is done, the System Upgradation will be done by the BASI, the system will be replaced with new system. At teh end of this phase SPAU phase starts, which inturn reults with version difference in the field namely, Programs, Reports, Screens, Messages, Notes an Function Modules. Here too the involvement of functional consultant neede to determine either reset to original or to go with Adopt modification from the older design, as explained earlier.
At teh end of the, moreover the functional consultant role involved in testing the Entire processes and transactoin in the system for system dump and bugs, in necessity to correct teh same and results with nil errors in production client.
Also the Zprograms invloved in the older versions, needs to be examined for the actual need, and to be justified with adoption in the newer version or by adopting to the updated functionality in the newer version.
Hope this may give better clarity in the involvement of the Functional Consultant in the Updgrade project.
Njoy SAP
Regards,
-Saravanaganesh

Roles of Functional Consultant in upgradation from 4.6b to ECC 6.0.

Hi
I need the Roles of Functional Consultant and Technical Consultant in upgradation from 4.6b to ECC 6.0.
Thanks
Anto

In Technical SAP,Upgrade from 4.6 to 6.0- the role of any fucntional consultant would involved integrated with the technical Consultant.
The phase starts with the technical Patches apply to the latest stack level which will done by the BASIS Consultants.
Once the System preparation is happened, the next phase is with SPDD phase, Thru this transaction the dictionary Objects-Database elements, database tables and structures of teh latest system can be
compared with the old system.
This results in the version modification results between the old and New versions. During this phase the involvement of the Functional Consultant needed for the tech guy, to identify the functional chnages between the two version (Old and New). Which helps for him either to Reset to Original(ie., adopting the new one) or Adopt Modification in previous system(ie., adopting to older functionality)
Once this is done, the System Upgradation will be done by the BASI, the system will be replaced with new system. At teh end of this phase SPAU phase starts, which inturn reults with version difference in the field namely, Programs, Reports, Screens, Messages, Notes an Function Modules. Here too the involvement of functional consultant neede to determine either reset to original or to go with Adopt modification from the older design, as explained earlier.
At teh end of the, moreover the functional consultant role involved in testing the Entire processes and transactoin in the system for system dump and bugs, in necessity to correct teh same and results with nil errors in production client.
Also the Zprograms invloved in the older versions, needs to be examined for the actual need, and to be justified with adoption in the newer version or by adopting to the updated functionality in the newer version.
Hope this may give better clarity in the involvement of the Functional Consultant in the Updgrade project.

Interview questions on upgrades from 4.7 to ECC

Hi,
Can any one please post some potential areas/questions that will be asked for upgrade projects from 4.7 to ECC6.0
Points will be awarded.
Thanks

Hi Frank,
this is good question, why because sap upgrades from 4.6b to ecc 6.0 is very risky.
take one example , in 4.5b , me21n application having 620 screen where as in ecc 6.0 having 9000 screen . that time we will take care of it.
check the obsolete function modules , 4.5b , having ws_upload, ws_download.... use cl_gui_frontend_services , under these having differnt type of methods.
once you change the code in ecc , go to tranx : SLIN check the error where it is exact.

Error during Upgrade from 4.6c to ECC 6.0

Hi All,
We are facing an error when upgrading from 4.6c to ECC 6.0. We are facing this error on the table COEP - runtime object inconsistancy. What we found is there is ERP upgrade has created new extra fields in the table. In log file the error is specified as : Duplicate Field name, But we not able to find the duplicate field name in the table. Please kindly help as early as possible. The upgrade process is stuck.
Regards
Anil Kumar K

Hi Anil,
Is this issue fixed? Can i know how you fixed it?
replied to your message Re: How to adopt the index changes during upgrade.
Thanks,
Somar

Unicode error while upgrading from 4.6 to ECC 6.0

Dear All,
I am getting unicode errror while upgrading from 4.6 to ECC 6.0, when iam trying to open downloaded file in excel.
In debugging, error occurs while executing statment "CALL METHOD OF obj_ex_sheet " in the code given below:
FORM open_downloaded_file_in_excel            *
FORM open_downloaded_file_in_excel.
DATA:
    lv_ole_books       TYPE ole2_object,
    lv_ole_sheets      TYPE ole2_object,
    lv_subrc           LIKE sy-subrc,
    lv_title(70)       TYPE c,
    lv_text1(70)       TYPE c,
    lv_text2(70)       TYPE c.
start excel
CREATE OBJECT obj_ex_sheet      'EXCEL.SHEET'.
IF sy-subrc NE 0.
    lv_subrc = sy-subrc.
    FREE OBJECT obj_ex_sheet.
    PERFORM error_handling_ms_excel USING lv_subrc.
ENDIF.
CALL METHOD OF obj_ex_sheet     'Application' = obj_ex_app.
IF sy-subrc NE 0.
    lv_subrc = sy-subrc.
    FREE OBJECT obj_ex_app.
    FREE OBJECT obj_ex_sheet.
    PERFORM error_handling_ms_excel USING lv_subrc.
ENDIF.
SET PROPERTY OF obj_ex_app 'Visible' = 1.
open data file: main file
CALL METHOD OF obj_ex_app        'Workbooks' = lv_ole_books.
CALL METHOD OF lv_ole_books      'Open'       = obj_ex_wbook
    EXPORTING #1 = gv_filename
              #2 = 2
              #3 = 0
              #4 = 1
              #5 = 0
              #6 = 0
              #7 = 1.
IF sy-subrc NE 0.
    lv_subrc = sy-subrc.
    FREE OBJECT obj_ex_wbook.
    FREE OBJECT obj_ex_app.
    FREE OBJECT obj_ex_sheet.
    PERFORM error_handling_ms_excel USING lv_subrc.
ENDIF.
FREE OBJECT lv_ole_books.
CALL METHOD OF obj_ex_wbook      'Worksheets' = lv_ole_sheets.
CALL METHOD OF lv_ole_sheets     'Item'       = obj_ex_wsheet
    EXPORTING #1 = 1.
FREE OBJECT lv_ole_sheets.
GET PROPERTY OF obj_ex_wsheet    'UsedRange' = obj_ex_usedrange.
CALL METHOD OF obj_ex_usedrange 'AutoFormat'
    EXPORTING #1 = 18.
SET PROPERTY OF obj_ex_wsheet    'Name'       = sy-tcode.
FREE OBJECT obj_ex_usedrange.
PERFORM free_ole_objects.
CALL FUNCTION 'FLUSH'
       EXCEPTIONS
            OTHERS = 0.
ENDFORM.
regards,
Divya

hi,
In the OPEN DATASET STATEMENT ADD THE ENCODING ADDITION IN TEXT MODE.
Regards,
Balakumar.G
Reward Points if helpful.

Top-Down Distribution - tcode KE28 (release upgrade from 4.6 to ECC 6.0)

All,
we are performing a release upgrade from 4.6 to ECC 6.0 and we have a problem with the tcode KE28.
The variant already set up in the system don't match with the selection fields present in the screen, and the following message is shown:
Message no. KG346
The variant does not adhere to the current Customizing setup
We have saved the variant again, and no problem are present, but the error message refers also to Customizing setup.
Is there a section in the Customizing where it is possible set up the field to show in the initial screen or the new fields (All Valuation Views, Legal Valuation View and Profit Center Valuation View) are due to the release upgrade?
If yes, do you know the transaction/path?
Thanks in advance for your collaboration.
Regards,
Jody Mancini.

Hi Satish,
Now i am sending some URL for Functional upgrade
May be those are all useful toyou
https://www.sdn.sap.com/irj/scn/wiki?path=/display/erp6/transactionsChangedinECC6.0
http://solutionbrowser.erp.sap.fmpmedia.com/Default.aspx
https://www.sdn.sap.com/irj/scn/wiki?path=/display/erp6/
Regards
Surya

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

RFC Client Interface upgrade from 4.6c to ECC 6.0

Similar Messages

Maybe you are looking for