Upgrade 4.6 to ECC6

Hello Gurus,
Do anyone can tell me something about migration datas from CO-PA (characteristics, value fields...) 4.6 in ordere to integrate these in ECC6 when the New Ledger will not be active?
Thanks

Hi
Please review these notes
961410 Add. info. on upgrading to SAP ECC 6.0 SR2 ABAP
960269 FCOM_COEP_ENHANCE: Short dump COMPUTE_INT_PLUS_OVERFLOW
913971 Add. info. on upgrading to SAP ERP Central Component 6.0 SR1
826092 Add. info. on upgrading to SAP ERP Central Component 6.0
790616 KALE: After upgrade line item display COEP is incorrect
937389 COEP Line item display incorrect after upgrade
Regards,
Somar

Similar Messages

Guidelines to reduce downtime during upgradation R/3 to ECC6

hi all........
Here we implemented SAP R/3 4.6 in the year 2005.
Now we are planning to upgrade our system to ECC6 unicode .
We are planning to upgrade our Production and Development system to SAP
ERP6 EHP4.As part of the upgradation; we had setup a test system with the
following details:
Sun Fire 480R (UltraSparc III + 1.05GHz x 4 processor)
Memory 16 GB and Storage : Sun CSM 200 SATA HDD
SAP R/3 4.71, single code pages 1100, Oracle 9.2.0.8.0, Solaris 9
Test system with 1.2TB data copied from Production System.
We have upgraded the test system using CU&UC method ( Upgrade Guide SAPERP6.0 EHP4 SR1 Abap ). It took 2 days downtime for full upgradation and 8 days for Unicode conversion.
Requirement :
To Upgrade the current systems without any additional hardware to SAP
ERP6 EHP4 Unicode.
As a part of the above, the cluster has to be upgraded to Sun cluster
3.2, and operating system to Solaris10 (5.10)
We are having the following queries:
1. With only 1.3 TB data, we feel, the down time of 10 days is not
realistic.Though we had not deviated from the above mentioned upgrade
guide, what could be the reasons for this down time of 10 days?what arethe affecting factors? Kindly suggest the ways by which we can get
reduced downtime . The referred Notes are (784118, 855772, 952514,
936441, 954268, 864861 ) still we are unable to pin point the reason. Abreak up of this down time is given below for reference.
2. Are there any alternate approved upgradation methods to reduce
downtime in our present set up? (details of present set up is given below)
3. How to calculate the down time with reference to(sapnote:857081) to in
our setup
Current Production System Details :
System : Sun Fire V890
Processor : 1.5GHz UltraSPARC IV+ processors -- 8no.s
Memory : 64 GB
Storage : Sun Storagetek 6180: HDD FCAL(16 no.s x 450 GB)
15,000-rpm 4 Gb/sec 4GB data cache (Storage connected to server using FC
cable)
SAP : R/3 4.71 single code pages 1100
Database : Oracle 9.2.0.8 data-size is around 1.3 TB
OS : Solaris 9 (5.9)
Cluster : Sun cluster 3.1
Network : 1GB ethernet (1000BASE-SX)
Architecture : Application and database server on Same system
SAP Development system specification same as the above with 187 GB data
size. PRD and DEV systems are on cluster; PRD failover to DEV system.
The time taken for test upgrade - brief details:
1. Kernel upgraded 6.20 to 6.40 (2hours)
2. Oracle Upgrade to 10.2.0.4.0 (3.30 hours)
3. SAP UPGRADE Preparation-Apply support packages (18 hours)
4. Downtime Phase and Pre-Processing and Finalization Phase (20 hours)
5. Unicode Conversion-Taking DB Export 109GB(Almost 10% of total DB
size)(98 hours)
6. Installation of unicode system using export (95 hours)
Looking forward to hear from you.
Best Regards,
Rajeesh K.P

Hi .......
i am very sorry for late reply...............................
The time taken for test upgrade - brief details:
1. Kernel upgraded 6.20 to 6.40 (2hours)
2. Oracle Upgrade to 10.2.0.4.0 (3.30 hours)
3. SAP UPGRADE Preparation-Apply support packages (18 hours)
4. Downtime Phase and Pre-Processing and Finalization Phase (20 hours)
5. Unicode Conversion-Taking DB Export 109GB(Almost 10% of total DB
size)(98 hours)
6. Installation of unicode system using export (95 hours)
2 days downtime means the sum of time used for above 4 activities ..........................
as you suggested we can do the same 4 different down times......................
Unicode Conversion-Taking DB Export 109GB(Almost 10% of total DB size) is taking a continuous down time
of 98 hours (4.5 days ) (Activity 5)+ installation of Unicode system using the Unicode export is taking 95 hours 4.5 days
(Activity 6)
i think the we have to do activity 5 & 6 in a single stretch with out users, so it will take a continuous down time of 9 Days
With this in mind I have a few questions for you to clear a little bit more all the problem.
Q:1 Did you use more parallel jobs during Downtime than default? and I mean real Downtime where the SAP system is taken down
No.we have used default number (3 ) of parallel jobs during downtime
Did the system allow you to use ICNV (incremental converssion) for some tables?
yes we may use ICNV
Can you separate the Unicode conversion to a different weekend? or is a must for some business reason?
Yes , we can separate the Unicode conversion to a different weekend , it will not affect our business
Did you save the post download Report so you can see what are the most time consuming phases?
i am not so clear about this question , we have made an activity chart with time duration as per the test upgrade. Or how we can save the post download report from the system
Looking forward to hear from you.
Best Regards,
Rajeesh K.P

Runtime Error in HR module t-code PPOCE [upgraded 4.7 to ECC6]

HI Gurus!
at my client site , we have upgraded 4.7 to ECC6. Now functional consultants are testing the system.When HR consultant working on PPOCE t-code ,the patch no of SAP HR - 0007. its giving runtime error.
Runtime Errors CREATE_DATA_UNKNOWN_TYPE
Except.     CX_SY_CREATE_DATA_ERROR          Date and Time                    19.08.2008     14:42:44
Short text
CREATE DATA: The specified type "HRP1680" is no valid data type.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLRHDB" had to be terminated because it has come across a statement that unfortunately cannot be executed.
Error analysis :An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_CREATE_DATA_ERROR', was not caught in
procedure "FILL_I777D" "(FORM)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the exception would occur, the current program is terminated.
The reason for the exception is:
The dynamically specified type "HRP1680" at CREATE DATA is no valid data type.
The type is either unknown or an object type.
Missing RAISING Clause in Interface
Program     SAPLRHDB
Include     LRHDBF00
Row     177
Module type (FORM)
Module Name FILL_I777D
Trigger Location of Exception
Program     SAPLRHDB
Include     LRHDBF00
Row     308
Module type(FORM)
Module Name     FILL_I777D
Source Code Extract
Line          SourceCde
278          **                HEADER   = FI_HEADER                    "ANDBCEK008264
279          **           TABLES                                       "ANDBCEK008264
280          **                FIELDTAB = FI_TAB                       "ANDBCEK008264
281          **           EXCEPTIONS                                   "ANDBCEK008264
282          **                OTHERS   = 4.                           "ANDBCEK008264
283          *                                                         "ANDBCEK008264
284          *      CALL FUNCTION 'DDIF_FIELDINFO_GET'                 "ANDBCEK008264
285          *           EXPORTING                                     "ANDBCEK008264
286          *                tabname        = fi_tabname              "ANDBCEK008264
287          **               FIELDNAME      = ' '                     "ANDBCEK008264
288          **               LANGU          = SY-LANGU                "ANDBCEK008264
289          **               LFIELDNAME     = ' '                     "ANDBCEK008264
290          **               ALL_TYPES      = ' '                     "ANDBCEK008264
291          *           IMPORTING                                     "ANDBCEK008264
292          *                x030l_wa       = fi_header               "ANDBCEK008264
293          **               DDOBJTYPE      =                         "ANDBCEK008264
294          **               DFIES_WA       =                         "ANDBCEK008264
295          **          TABLES                                        "ANDBCEK008264
296          **               DFIES_TAB      =                         "ANDBCEK008264
297          *          EXCEPTIONS                                     "ANDBCEK008264
298          *               not_found      = 1                        "ANDBCEK008264
299          *               internal_error = 2                        "ANDBCEK008264
300          *               OTHERS         = 3.                       "ANDBCEK008264
301          *
302          *      IF sy-subrc EQ 0.
303          *        i777d-tbtab_tabof = fi_header-tablen - tabnr_intlen.
304          *        i777d-pnnnn_tabof = i777d-tbtab_tabof - 8.
305          *      ENDIF.
306
307          *      ASSIGN char TO <any_field> CASTING TYPE (fi_tabname). "ANDDDIF
>>>>>                create data anyfield type (fi_tabname).                "ANDUNI
309                assign anyfield->* to <any_field>.                     "ANDUNI
310
311          *     we need a character view of <any_field> !!!            "ANDUNI
312                assign <any_field> to <char_field> casting type c.     "ANDUNI
313
314          *      DESCRIBE FIELD <any_field> LENGTH tablength            "ANDDDIF
315          *                                 IN BYTE MODE.               "ANDDDIF
316
317                DESCRIBE FIELD <char_field> LENGTH tablength           "ANDUNI
318                                            IN CHARACTER MODE.         "ANDUNI
319
320                <i777d>-tbtab_tabof = tablength - tabnr_intlen.        "ANDDDIF
321                <i777d>-pnnnn_tabof = <i777d>-tbtab_tabof - 8.         "ANDDDIF
322
323             ENDIF.
324              IF <i777d>-ext_infty NE space.                             "VWMEXT
325                READ TABLE i77id
326                     WITH KEY infty = <i777d>-infty
327                     BINARY SEARCH.
i have check the table HRP1680 in SAP4.7c but in ECC 6 it is not there. So i have create that table. Is it Info-type? or i have apply OSS notes.
regards
Rahul
Edited by: rahul deshmukh on Aug 20, 2008 11:52 AM

Hello,
I receive the same error when trying to change records of an infotype. Did you find a solution to this problem? I know your message is from 2008, but maybe you remember what you did to solve it
Thank you!
Iuliana

Upgrade from 46c to ECC6.0 : Java or Java-AddIn ?

Hello
Can you explain me what is the difference between Java and Java-AddIn as proposed in evaluation phsae of an upgrade from 46c to ECC6.0?
Thank You.

Hi Alain,
But if we implement a JavaAddin solution today, do you think it will be possible to create a Java instance later to create a Portal solution ?
If you implement a java addin today then you can use later for portal solution.
Regards,
Anil

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

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

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

Upgrade 4.6C to ECC6.0 IT0000 can't be overviewed, can only be displayed..

dear all,
we are currently in the process of upgrade from 4.6C to ECC6.0
and we found this minor issue in the submodule PA:
using tcode pa20/pa30 we can not see any record of IT0000 Actions using 'overview'
but the all the detail actions can be displayed..
this is only happen in IT0000
other infotypes can be overviewed and can be displayed as normal.
anyone ever gone through the same issue?
we have updated patch for SAP HR : SP 32 and EA 7.
the authorization is SAP ALL.
looking forward to hearing from you.
best regards,
dhenny muliawaty (pei pei)

dear JLJ
we're still on the upgrade process. i can only share with you our current condition and the lesson learnt.
we have copy production, upgraded from 4.6C to ECC6.0
and we did not face authorization issue or any other main issues in HR cause we have not yet implemented the submodules e-recruitment/ESS/other sub modules that are being enhanced in ECC6.0
our technical team did the oracle database upgrade + 4.6C upgrade to ECC6.0 right away directly after the oracle database upgrade. TST production is considered ok. we only have some minor configurations to be done.
next when our tech team upgrade the oracle database to ver. 10 in R/3 4.6C production system, and there's a time lag (interval) where our 4.6C production system not directly upgraded to ECC6.0 after the oracle database upgrade done.
and current condition - production database oracle upgraded, the R/3 4.6C Prod has not yet being upgrade to ECC6.0,
R/3 4.6C production face the authorization issue (not HR module, but other modules)
we need to check and apply sap notes/release to solve some errors in 4.6C production system and related modules settle the authorization issue. current progress is still on the technical abap preparation and functional testing.
it's been scheduled the next step - tech team will upgrade the production system from to ECC6.0 within next week. we hope all will be ok.
from this experience, my suggestion is that you need to make sure basis team have implemented sap support packages module related/ enhancement packages- latest updated one in your 4.6C system, then you also needs to check sap release notes implemented related with your module.
would you share the steps have been done in upgrading your production system in detail?
thanks and best regards,
dhenny muliawaty (pei pei)

Workflow Upgrade 4.6C to ECC6 - manual settings during Cutover

Hello Guys,
We are upgrading to ECC 6 from 4.6C and we are on release 701 & support pack SAPKB70106.
I would like to know which are the "Manual activities" that needs to done during cutover and WHEN should these should be done (eg. before ECC6 upgade, or after ECC6 upgrade but before config/dev transports, or after config/dev transports).
I have looked on few SDN threads and found the following info. Please correct me or add extra info if i have missed something:
1. Configure RFC destination & WF user info in Transaction SWU3.
2. Run Transaction SWU_OBUF to clear the runtime buffers before users start Testing.
I assume rest of changes would be imported with transports, but i have read through lot of SDN threads that all custom Workflow definitions needs to be ACTIVATED in each system (DEV - QAS- PRD) and custom BOR objects needs be REGENERATED in each system (DEV - QAS- PRD). Also, do I have manually set the agent assignement for Customer Task as GENERAL TASK in each system? Are above stated 3 steps needs to be manually done in each system or transports take care of them ? I am bit confused. Could anybody please advise me regarding the Manual Task/activities that needs to done in each system during cutover during WF upgrade from 4.6 C to ECC6.
Thanks for posting excellent stuff regarding the Workflow Upgrades on SDN. It really helped me in resolving most of my issues.
Thanks in advance
Kind Regards
Sam

Helli Viji,
Thanks for the information. I still have some doubts.
Yes , as you have mentioned there are many other mandatory settings in Transaction SWU3 that needs to be maintained in each system. I hope these settings are imported with the Customizing tranport request created in DEV or Do we have to maintain these manually just in case of Upgrade.
For transporting the Agent assignment from one system to another, can we use Transaction RE_RHMOVE30 ? Or this functionality do not works when upgrading to ECC 6 from 4.6 C.
Is there any other activity I am missing that needs to done during Cutover when upgrading from 4.6C to ECC 6 with regard to Workflows.
Thanks
Regards
Sam.

Problem with FIELD SYMBOL upgrading from 46c to ECC6.0

Hi people... i'm having big trouble making an upgrade from 4.6c to ECC6.0 with this portion of code of Z's programm.
In the line
ASSIGN (w_field) TO <fs_field>.
i don't see any assigment, so <fs_field> remains empty, when enters into firts IF conditions it is TRUE, then go into second IF condition, it is FALSE, and finally assing
<fs_field> = '/'.
, at this point i have a DUMP telling me MOVE_TO_LIT_NOTALLOWED_NODATA
I'm try any way of definition, assigment, but always i have a DUMP.
Someone can give a hand with this issue!
Thanks in advance!!!
This is the full code from the FORM with the problem.
*       FORM GRABA                                        *
* --> VALUE(P_TABLE)                                  *
FORM graba USING value(p_table) TYPE c.
DATA:
    w_field(60),
    w_dd03l TYPE dd03l.
FIELD-SYMBOLS <fs_field>.
CLEAR w_flag.
CASE p_table.
    WHEN 'BGR00'.
      d_bgr00-group = w_batin.
      d_bgr00-mandt = sy-mandt.
      d_bgr00-usnam = sy-uname.
      d_bgr00-xkeep = 'X'.
      d_bgr00-nodata = '/'.
      d_bgr00-stype = 0.
      TRANSFER d_bgr00 TO w_fname.
    WHEN 'BBKPF'.
      LOOP AT gt_dd03l INTO w_dd03l WHERE tabname EQ p_table.
        CONCATENATE
            'd_'
            w_dd03l-tabname
            w_dd03l-fieldname
          INTO w_field.
        ASSIGN (w_field) TO <fs_field>.
        IF <fs_field> IS INITIAL OR <fs_field> EQ '/'.
          IF w_dd03l-fieldname EQ 'TBNAM'.
            <fs_field> = p_table.
          ELSE.
            <fs_field> = '/'.
          ENDIF.
        ELSE.
          w_flag = 'X'.
        ENDIF.
      ENDLOOP.
      TRANSFER d_bbkpf TO w_fname.
    WHEN 'BBSEG'.
      LOOP AT gt_dd03l INTO w_dd03l WHERE tabname EQ p_table.
        CONCATENATE
            'd_'
            w_dd03l-tabname
            w_dd03l-fieldname
          INTO w_field.
        ASSIGN (w_field) TO <fs_field>.
        IF <fs_field> IS INITIAL OR <fs_field> EQ '/'.
          IF w_dd03l-fieldname EQ 'TBNAM'.
            <fs_field> = p_table.
          ELSE.
            <fs_field> = '/'.
          ENDIF.
        ELSE.
          w_flag = 'X'.
        ENDIF.
      ENDLOOP.
      TRANSFER d_bbseg TO w_fname.
ENDCASE.
ENDFORM.
Edited by: Matt on Dec 15, 2008 5:03 PM - Made subject more informative

Gentlemen:
The problem around this statement:
ASSIGN (w_field) TO <fs_field>
is explained as follows:
1. In ABAP language, there are two ways for assigning a new value to a field-symbol.
- Sentence: ASSIGN (values) TO <my_field_symbol>.
In this case, the <my_field_symbol> receives from (w_field) the data type and value content of this variable. So, we keep that a FSymbol is assigned and, at the same time, receives an initial value.
- Sentence: <my_field_symbol> = '/' or <my_field_symbol> = my_var.
In this way, we only pass the content of the variable next to = sign. But before this, the field-symbol must had been assigned (using ASSIGN statement), in another case, the compiler raises an exception.
Following the example of Federico... I think he tried to assign a field like this (please, supose the program imports the structure of a database table with a standard function, into a internal table which is looped by the work area w_field ):
- If w_field contains 'BKPF-WERKS', so sentence ASSIGN will affect the field symbol, passing to this the data type and current content of table field BKPF-WERKS.
- If w_field contains 'BKPF-.INCLUDE': *the column .INCLUDE obviously is not associated with a data type... so our statement ASSIGN... TO... never pass any data type or value to our field-symbol. So that, this field is never initialized properly, and when inmmediately you try to execute something like this: <my_field_symbol> = '/', the game (program) is over.. XD
I hope this post was helpful for anyone...
Best Regards!!
RRG
ABAPer(u) - EVOLution

Upgrading ECC5.0 to ECC6.0 and Internet Sales ISA4.0 CRM4.0

We are performing a technical upgrade of ECC5.0 to ECC6.0 and we are seeking confirmation and instructions for connecting our existing ISA4.0 system to ECC6.0. I have searched OSS and SDN and queried our SAP account manager for some confirmation and documentation on ISA4 and ECC6.0 compatability
Any advice, confirmation and documentation on connecting Internet Sales version 4.0 component to ECC 6.0 is greatly appreciated.
Here are the details of our ISA4 system
Kind regards
ISA System
sap.com      SAP-JEE      6.40 SP9 (1000.6.40.9.0.20041119045409)
sap.com      com.sap.mw.jco       (6.4009.00.0000.20041026130530.0000)
sap.com      com.sap.security.dbschema       (6.4009.00.0000.20041115123517.0000)
sap.com      crm.b2b       (400.200904212104)
sap.com      crm.b2b_lanl       (400.200904221705)
sap.com      crm.b2c       (400.1020060105115443.0000)
sap.com      crm.mcm       (400.1020060105115443.0000)
sap.com      crm.shopadmin       (400.1020060105115443.0000)
sap.com      crm.trexr3       (400.1020060105115443.0000)
sap.com      IAIKSecurityFS       (1.3.12)
sap.com      isacoreddic       (400.1020060105115443.0000)
JDK 1.4.2_11-b06
TREX6.1
Windows 2003 (x86) 5.2
Warm regards
Lee Lewis

When an incorrect password is entered, the expected message:
"Name or password is incorrect (Please repeat logon) "
is displayed. When the correct password is entered, this message is displayed:
"Error in user administration"
No error messages are logged during the login attempt, only the following:
Message , Datasource
Feb 9, 2010 12:03:54 PM                     bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][actionxecution]='end' [actionclass]='com.sapmarkets.isa.isacore.action.b2b.LoginAction' [path]='/b2b/reallogin' [forward]='/b2b/login/login.jsp' [exectime]='94' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
Feb 9, 2010 12:03:54 PM                     bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][jcofunctionexecution]='end' [funcname]='BAPI_USER_GET_DETAIL' [ashost]='sapsbx' [sysid]='SBX' [exectime]='31' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
Feb 9, 2010 12:03:54 PM                     bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][jcofuncionexecution]='begin' [funcname]='BAPI_USER_GET_DETAIL' [ashost]='sapsbx' [sysid]='SBX' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
Feb 9, 2010 12:03:54 PM                     bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][jcofunctionexecution]='end' [funcname]='SUSR_LOGIN_CHECK_RFC' [ashost]='sapsbx' [sysid]='SBX' [exectime]='15' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
Feb 9, 2010 12:03:54 PM                     bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][jcofuncionexecution]='begin' [funcname]='SUSR_LOGIN_CHECK_RFC' [ashost]='sapsbx' [sysid]='SBX' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
Feb 9, 2010 12:03:54 PM                     bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][jcofunctionexecution]='end' [funcname]='RFC_SYSTEM_INFO' [ashost]='sapsbx' [sysid]='SBX' [exectime]='0' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
Feb 9, 2010 12:03:54 PM                     bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][jcofuncionexecution]='begin' [funcname]='RFC_SYSTEM_INFO' [ashost]='sapsbx' [sysid]='SBX' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
Feb 9, 2010 12:03:54 PM                     bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][actionxecution]='begin' [actionclass]='com.sapmarkets.isa.isacore.action.b2b.LoginAction' [path]='/b2b/reallogin' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
Feb 9, 2010 12:03:54 PM                     bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][actionxecution]='end' [actionclass]='com.sapmarkets.isa.isacore.action.DetermineBrowserVersionAction' [path]='/b2b/login' [forward]='/b2b/reallogin.do' [exectime]='15' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]
Feb 9, 2010 12:03:54 PM                     bbtracing.isa.runtime [SAPEngine_Application_Thread[impl:3]_34] Debug: [(J2EE3718900)ID3718950DB871103440658474576End|?][actionxecution]='begin' [actionclass]='com.sapmarkets.isa.isacore.action.DetermineBrowserVersionAction' [path]='/b2b/login' , 52 [Server 0 0_37189:D:\usr\sap\SSD\JC00\j2ee\cluster\server0\apps\sap.com\crm.b2b_lanl\servlet_jsp\b2b_lanl\root\WEB-INF\logs\isaruntime.log]

Programming changes when upgrading 4.6c to ecc6

Hello ,
May I know what are all the changes to be done to the programs when upgrading from 4.6c to ecc6?
Thanks

hi,
there is a big list of dos and dont.....
some errors are:
Syntax Error:
REPORT/PROGRAM statement missing, or program type is INCLUDE.
Unicode Error
Upload/Ws_Upload and Download/Ws_Download are obsolete, since they are not
Unicode-enabled; use the class cl_gui_frontend_services
Syntax error
TEXT E00 is not defined in text pool of ZSTEXTEM in the
original language E
Error message in ABAP Objects if the following syntax is used:
NEW-PAGE PRINT ON NO DIALOG.
Correct syntax:
DATA pripar TYPE pri_params,
arcpar TYPE arc_params.
CALL FUNCTION 'GET_PRINT_PARAMETERS'
IMPORTING out_parameters = pripar
out_archive_parameters = arcpar
NEW-PAGE PRINT ON NO DIALOG
PARAMETERS pripar
ARCHIVE PARAMETERS arcpar.
The list continues................ do a google or search for documentations
ags.

Holiday calender & upgrade 4.5B to ECC6.0

Hi
There is some option to display a holiday calender in 6.0 as 4.5b ? Only a design.
Thanks,

dear JLJ
we're still on the upgrade process. i can only share with you our current condition and the lesson learnt.
we have copy production, upgraded from 4.6C to ECC6.0
and we did not face authorization issue or any other main issues in HR cause we have not yet implemented the submodules e-recruitment/ESS/other sub modules that are being enhanced in ECC6.0
our technical team did the oracle database upgrade + 4.6C upgrade to ECC6.0 right away directly after the oracle database upgrade. TST production is considered ok. we only have some minor configurations to be done.
next when our tech team upgrade the oracle database to ver. 10 in R/3 4.6C production system, and there's a time lag (interval) where our 4.6C production system not directly upgraded to ECC6.0 after the oracle database upgrade done.
and current condition - production database oracle upgraded, the R/3 4.6C Prod has not yet being upgrade to ECC6.0,
R/3 4.6C production face the authorization issue (not HR module, but other modules)
we need to check and apply sap notes/release to solve some errors in 4.6C production system and related modules settle the authorization issue. current progress is still on the technical abap preparation and functional testing.
it's been scheduled the next step - tech team will upgrade the production system from to ECC6.0 within next week. we hope all will be ok.
from this experience, my suggestion is that you need to make sure basis team have implemented sap support packages module related/ enhancement packages- latest updated one in your 4.6C system, then you also needs to check sap release notes implemented related with your module.
would you share the steps have been done in upgrading your production system in detail?
thanks and best regards,
dhenny muliawaty (pei pei)

Procedure for upgrade 4.6 to ecc6

Hi,
Can someone please tell me the steps for how to upgrade the
R/3 4.6 to ecc6
Thanks
Asif

Hi Asif,
As per your OS,Database combination and the to the target upgrade release download the appropriate upgrade guides from http://service.sap.com/instguides.
Thanks and Regards,
-Bijesh.

Upgradation 4.6B to ECC6

Hi,
can i get any info (Doc or URL) which gives any information on the Bussiness adavantages ECC6 offers(in MM\WM point of view) for a client who is using 4.6B.
As i need to prepare the solution proposal any info on the topic would be very useful.
Thanks in Advance,
Raghu

Hi Priyanka,
this information is useful....but these are changes from 4.6 to ECC6. as the technical upgrade is done these functions can be used.What i precisely want to know is the functional bussiness advantages in ECC6, which will influence the client to go for Functional Upgrade also

Upgrade from 46C to ECC6.0

Hello All.
I'm upgrading a 4.6C SAP release to ECC 6.0
OS: Windows 2003 EE - 32bit
DB: DB2 UDB 8 FP10
The upgrade procedure hangs in the phase PARMVNT_XCNV with the following error:
3 ETP379X12:52:48: activating Nametab "TPRI_PAR":
2 ETP399   >> Name of inactive nametab to read : DDXTT~
2 ETP399   >> Format of inactive nametab to read: 5.0
3 ETP355Xstatements:
3 ETP399 ALTER TABLE "TPRI_PAR"
3 ETP399 ALTER COLUMN "PARAMLIST" set data type SAPDB6VARCHAR(000512)
3 ETP399
2WETP000 12:52:48: Retcode 1: error in DDL statement for "TPRI_PAR                      " - repeat
2EETP345 12:53:00: Retcode 1: SQL-error "-104-SQL0104N An unexpected token "data_type" was found f
2EETP345 ollowing "TYPE". Expected tokens may include: "VARCHAR". SQLSTATE=42601" in DDL stateme
2EETP345 nt for "TPRI_PAR                      "
2 ETP399 -
DB-ROLLBACK() -
2EETP334 12:53:00: error in DDL, nametab for "TPRI_PAR" not activated
Any one can help?
Thanks Everybody,
Marco

Hi Frank.
We encounter the same issue during the upgrade phase PARCONV_UPG:
3 ETP379X20:19:11: activating Nametab "TERRF":
2 ETP399   >> Name of inactive nametab to read : DDXTT
2 ETP399   >> Format of inactive nametab to read: 5.0
3 ETP355Xstatements:
3 ETP399 ALTER TABLE "TERRF"
3 ETP399 ALTER COLUMN "DATA" set data type SAPDB6VARCHAR(001700)
3 ETP399
2WETP000 20:19:11: Retcode 1: error in DDL statement for "TERRF                         " - repeat
2EETP345 20:19:23: Retcode 1: SQL-error "-104-SQL0104N An unexpected token "data_type" was found f
2EETP345 ollowing "TYPE". Expected tokens may include: "VARCHAR". SQLSTATE=42601" in DDL stateme
2EETP345 nt for "TERRF                         "
2 ETP399 -
DB-ROLLBACK() -
2EETP334 20:19:23: <b>error in DDL, nametab for "TERRF" not activated</b>
3 ETP379X20:19:23: activating Nametab "VZFZE":
3 ETP355Xstatements:
3 ETP399 ALTER TABLE "VZFZE"
3 ETP399 ALTER COLUMN "XVAR700" set data type SAPDB6VARCHAR(001000)
3 ETP399
2WETP000 20:19:23: Retcode 1: error in DDL statement for "VZFZE                         " - repeat
2EETP345 20:19:35: Retcode 1: SQL-error "-104-SQL0104N An unexpected token "data_type" was found f
2EETP345 ollowing "TYPE". Expected tokens may include: "VARCHAR". SQLSTATE=42601" in DDL stateme
2EETP345 nt for "VZFZE                         "
2 ETP399 -
DB-ROLLBACK() -
2EETP334 20:19:35: <b>error in DDL, nametab for "VZFZE" not activated</b>
2 ETP301 -
Regards,
Marco

UPGRADE ASSISTANT QUESTIONS for ECC6.0???????911

I have used upgrade assistant in the past for 4.6C and 4.7 upgrades and had no problems. I am having trouble getting the assistant to work through the internet browers. I need help with a couple of questions:
First: Do I need do a prepare and SERVER option like I had in the past with R3UP?
Second: Is there anything special that needs to be done for ports 4239,4240,4241. I can reach my server through the internet of some of the ports that R3 uses.
It seems the java is not recognizing my i5 server and I am not sure where the disconnect is.
This is the error I am receiving when I try to start the upgrade assistant:
ERROR: Unable to load resource: http://sapdev:4239/ua/uagui.jnlp

<?xml version="1.0" encoding="utf-8"?>
<jnlp spec="0.2 1.0" codebase="http://SAPDEV.SWIRECC.COM:4239/ua" href="uagui.jnlp">
<information>
    <title>Upgrade Assistant</title>
    <vendor>SAP AG</vendor>
    <description kind="short">SAP Upgrade Assistant</description>
    <icon href="http://SAPDEV.SWIRECC.COM:4239/ua/pics/sdtgui_big.gif"/>
</information>
<security>
    <all-permissions/>
</security>
<resources>
    <j2se version="1.4+"/>
    <jar href="uagui.jar" main="true" download="eager"/>
</resources>
<application-desc main-class="UaGui">
     <argument>-host</argument>
     <argument>SAPDEV.SWIRECC.COM</argument>
     <argument>-port</argument>
     <argument>4241</argument>
</application-desc>
</jnlp>

Usually it's done like
- PREPARE
- exchange SAPup with the newest version
- add your application fix <application>_FIX to /usr/sap/put
- $JAVA_HOME/bin/java -cp /usr/sap/put/ua/ua.jar UaServer
- give an administrator password
After that the UA should listen on port 4239
You can verify that on the machine via
netstat -tn | grep -i LISTEN | grep 4239
Also check that you have either no proxy or add the box' name to the exception list of the browser (because Java uses that exception list too).
Markus

Upgrade 4.6 to ECC6

Similar Messages

Maybe you are looking for