IDOC extensions during Upgrade from Ver 4.6 to ECC 6.0

We are working on an Upgrade project wherein we are going from Ver. 4.6 to ECC 6.0. Can you guide us what all we need to do with the IDOC extensions alerady implimented in ver 4.6 in order to confirm them good with ECC 6. Also to be noted, we are making the new system and all the customer developments Unicode compatible.
Thank you!!

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

Similar Messages

Idoc problem during upgrade from 4.0 to 4.6c

Hi All,
Currently we are upgrading our system from 4.0 to 4.6c.
We uses Basic idoc type DELVRY01:it has so many segments which have new definition now in 4.6c, for example segment E1EDL20:- new definition of this segemnt has 3 new extra fields in 4.6c.
Now due to it, whenever we are creating an idoc in 4.6c it comes with extra fields in them.
But after upgrade we want our idoc fields to be same as it was in 4.0.
How we can do it i.e creating an idoc in 4.6c but using the same segment definition used in 4.0.
Thanking in advance.
Nazir.

Hi Martin,
Thanks for the reply.
I even put the Seg Rel as 40A in partner profile, but after idoc creation it comes with extra fields only.
Is there anyother setting that needs to be change ?
Nazir.

Can we activate Classic General Ledger in ECC6.0 during upgrade from 4.6C

Dear SAP Gurus,
Greetings
My Client's technical team had upgraded their system from 4.6C to ECC6.0 and they had activated classic GL instead of New GL. And they had also activated classic withholding tax in place of Extended Withholding tax.
They are facing some error during posting of transactions (like generation of excise invoices, posting of WHT transactions, etc.) I told that it can be a reason of not activating New GL.
Is my understanding correct...?? Can we activate classic GL during upgrade from 4.6C to ECC6.0...??
In case of a new client built (with ECC6.0), can we activate the classic GL instead of the New GL..??
Does the system will work correctly in the long run if they had activated classic GL and classic WHT...??
Please clarify. Thanks in advance for your time and efforts
Regards,
Chaps
P.S. Points will be awarded for answers !!

Hi,
I think that you should read long text of OSS note 999614 carfully and you are
aware of the fact that you will have additional migration efforts in
case you need to migrate to new G/L later on.
In case you are convinced that this is the best way please feel free
to deactivate new G/L as described in note 999614.
Please make sure that you deactivate new G/L in all clients of your
new system in case there were already client copies done.
Yes this is possible and I would not automatically assume that
error during posting of transactions are due to New GL not being activated.
Note 756146 documents the issue and possible repercussions
of using Classic GL.
In the case of a new installation the new G/L accounting
is active by default in ERP. In principle, the use
of the classic GL is also possible for new customers, however,
SAP does not recommend it since this requires an additional
migration expense in later years.
Regards,
Aidan

Issue with VO extension after upgrading from 11i to R12

Hi All,
We are facing issue with VO extension after upgrading from 11i to R12(12.1.3).
Most of the cases we are facing issue as given below,
oracle.apps.fnd.framework.OAException: oracle.jbo.AttributeLoadException: JBO-27022: Failed to load value at index 21 with java object of type java.lang.Boolean due to java.sql.SQLException.
Please help me out to resolve this issue.
Any help/suggestion will highly appreciate.
Thanks & Regards,
Sunita

Hi Gyan,
Thanks for the response.
There is one attribute has added in VO query.
In VO.xml file ViewAttribute definition is as given below,
<ViewAttribute
Name="DisplayApproveButton"
IsUpdateable="false"
IsQueriable="true"
IsPersistent="false"
Type="java.lang.Boolean"
ColumnType="NUMBER"
AliasName="DisplayApproveButton"
Expression="xxh_invoice_approval_pkg.check approval(invoice_id)"
SQLType="BIT" >
</ViewAttribute>
Thanks & Regards,
Sunita

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.

BI 7.0: Source System upgrade from R/3 Enterprise to ECC 6.0

Background:
I am relatively new to BW team and will be going through my 1st source system upgrade.
We currently have BI 7.0 SPS 17 connected to source system R/3 Enterprise EP1.
We are upgrading to the source system to ECC 6.0.
In Development and QA Environments:
we will have access to both old (R/3 Enterpirse) and the new (ECC 6.0) source systems.
We have a opportunity to compare the BW Objects, data flow and data loading from
both source systems.
In Production, however, we will just upgrade over 3 days downtime.
One Question that comes to mind in this regard...
What sort of things, we should be checking for before and after upgrade in Dev/QA and in Prod environments and what tools are available that can help the analysis and validation process ?
Some of the suggestions that were given to me include following points.
Before Upgrade:
1 Check data, taking pre images of it for testing with post upgrade.
2. Perform proper analysis of Source system related BW objects.
- A complete listing of actively used Datasources,.. etc.
3. Make delta queues empty,
Make sure that all existing deltas are loaded into BW.The last request delta must not deliver any data and must be green in the monitor.
4. Stop Process chains from BI (remove from schedule) and collection runs from R/3 side
After Upgrade:
1 After the OLTP upgrade, refer to note 458305 and other notes that are relevant to the actual upgrade
(depending on the R/3 system release / R/3 plug-in to BI plug-in compatibility).
2. Check logical system connections. Transactions SMQS, RSMO and SM59, If no access, then we can use Program RSRFCPIN_NEW for RFC Test.
3. Check and/or Activate control parameters for data transfer. SBIW ---> General Settings --->
Maintain Control Parameters for Data Transfer
http://help.sap.com/saphelp_nw70/helpdata/EN/51/85d6cf842825469a51b9a666442339/frameset.htm
4. Check for Changes to extract structures in LBWE Customizing Cockpit
- OSS Notes 328181, 396647, 380078 and 762951
5. Check if all the required transfer structures are active. See OSS Note 324520 for mass activation.
7. Check if all Source system related BW Objects are active - Transfer rules, Communication rules, update rules,DTPs,..etc.
Below is a link for some useful programs in this regard.
https://www.sdn.sap.com/irj/scn/wiki?path=/pages/viewpage.action&pageid=35458
6. Test all important datasources using RSA3 and check for OLTP Datasources changes .
As soon as BW notices that the time stamp at the DataSource in the OLTP is newer than the one in the transfer structure, it requests replication of the DataSource and activation of the transfer structure. Transfer the relevant DataSources only if required, and transfer only the ones that have changed (RSA5 -> Delta).
7. Create Data flow objects (trnasfer rules, infopackages, trnasformations, DTPs) for the Replicate
new/changed datasources,if needed.
8. Check all CMOD enhancements.
If we are using a customer exit with the extractor in the OLTP, see Note 393492.
7. Check for unicode (all custom programs or Function Modules for DataSources)
5. Check all the queues in RSA7, start delta runs and test data consistency.
For delta problems:In the BW system, start the 'RSSM_OLTP_INIT_DELTA_UPDATE' program for the DataSource and the source (OLTP) system for which the init selections are then transferred from BW into the ROOSPRMSC and ROOSPRMSF tables in the source system so that the delta can continue.
9. Take back up of data posted during upgrade for contingency planing.
10. Run the entire set of process chains once if possible and let it pick up no data or the usual master data.
Since we have lot of experts in this forum, who have probably gone through such scenario many times, i wanted to request you to Please Please advise if i have stated anything incorrectly or if i am missing additional steps, OSS Notes, important details...

Thanks Rav for your detailed post and very helpful contribution by posting all the information you had regarding the upgrade.
We have similar scenario -
We are upgrading our source system from 4.7 to ECC 6.0. We have our BI system with BI 7.0 at support pack 19 (SAPKW70019).
Our strategy in ECC deployment ->
In development we copied our old DEV 4.7 system DXX to new ECC system DXY (new system ID).
In production we are going to use same system PRXX upgraded from 4.7 to ECC.
Now we are in testing phase of ECC with all interfaces like BI in Dev.
My questions are below ->
How can we change/transfer mapping of all our datasources in Dev BW system BID to new ECC dev system DXY (Eg. Logical system LOGDXY0040) from Old dev system DXX (Eg. Logical system LOGDXX0040). We donot want to create new datasources or change all transfer rules/Infosources for old BW3.x solutions on our BI.
Also in new ECC sourcesystem copy we see all datasources in Red in RSA7 transaction. Do we need to initialize again all the datasources from our BW BID system.
Is there any easy way for above scenario ?
Please let me know if you have any further helpful information during your ECC 6.0 upgrade connecting to BI 7.0 system.
I have found some other links which have some pieces of information regarding the topic -
Upgrade R/3 4.6C to ECC 6.0 already in BI 7.0
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/sap-r3-migration-and-sap-bw-version-1744205
BI 7.0: Source System upgrade from R/3 Enterprise to ECC 6.0
Re: ECC 6.0 Upgrade
Re: Impact of ECC 6.0 upgrade on BI/BW Environment.
ECC 5.0 to ECC 6.0 upgrade
Thanks
Prasanth

Upgrade from 4.6 B to ECC 6.0

Hi Gurus,
Well and I would like to inform to our gurus that currently we are in the Phase of upgrading form 4.6 B to ECC 6.0
I this regarding, can any one of our Guru's guide me regarding the following doubts.
1. How to do Upgrade from 4.6 B to ECC 6.0?
2. If you have any documents in this regard?
3. Do you have any documentation for ECC 6.0?
I request you to kindly forward the information to mail id: [email protected]
Thanks with regards,
Bala

Hi,
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.
Please assign points if it useful.
Regards
Ravinah Boni

Error while generating JAR files during upgrade from 11.5.9 to 11.5.10

Hi,
We are getting the following issue after applying 11.5.9 CU2 patch set during the process of upgrade from 11.5.9 to 11.5.10.
- 3171663: 11.5.9 Oracle E-Business Suite Consolidated Update 2
Executing: /u01/app/tinst/tinstcomn/util/java/1.6/jdk1.6.0_18/bin/java -Djava.security.egd=file:/dev/urandom sun.security.tools.JarSigner -keystore ******** -storepass ******** -keypass ******** -sigfile CUST -signedjar /u01/app/tinst/tinstcomn/java/oracle/apps/fnd/jar/fnddssgraphgui.jar.sig /u01/app/tinst/tinstcomn/java/oracle/apps/fnd/jar/fnddssgraphgui.jar.uns CUSTOMER
ERROR: JarSigner subcommand exited with status 1
No standard output from jarsigner
JarSigner error output:
Exception in thread "main" java.lang.NoClassDefFoundError: sun/security/tools/JarSigner
Caused by: java.lang.ClassNotFoundException: sun.security.tools.JarSigner
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Could not find the main class: sun.security.tools.JarSigner. Program will exit.
Can you please advice regarding this issue....????
Regards,
Sreenivasulu.

Please see these docs.
Generate Jar File causes NoClassDefFoundError sun/security/tools/JarSigner [ID 393306.1]
Generating Jar Files Fails with a NoClassDefFoundError: sun/security/tools/JarSigner Error [ID 801014.1]
Thanks,
Hussein

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

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.

Impacts on MRS and MAM during upgradation from ECC 5.0 to 6.0

Hi Gurus,
I would like to know the impacts on MRS and MAM during the upgradation from ECC 5.0 to 6.0. The version of MRS we are using is MRSS 500, and the version of MAM is 3.0. please let me know your valuable comments.
Thanks in advance.
Regards
Satish

HELLO,
Search the form you will get few links.
Also many companies have gone technical upgradation , but not functional upgradation.
Thanks
RK

ABAP Code Changes During Upgrade from 4.7C to ECC6

Hi all,
I'm in process of collecting information for our next upgrade.
We are on 4.7C and are planning to upgrade to ECC6. We wanted to know what changes shall be required on ABAP side during this upgrade. e.g. certain ABAP commands which are obselete, few tables , few fucntional modules being obselete.
Any specific functional areas/transcation codes being obselete which in turn would make Uer Exit redudant etc.....
Could somebody please help me out with some info regarding this upgrade? Some links or any hint you can give would help me a lot. (Whether technical or functional..all very welcome!).
Thanks in advance
Moderator message: topic too broad to be answered in a forum thread, many people had to go through this, please search for available information/documentation.
Edited by: Thomas Zloch on Jun 14, 2011 9:31 AM

Hi ,
I too got an error of this type .
The resolution is as follows :
login as user SAP<SID> in the oracle database .
SQL> drop tabel <tablename>;
Restart the upgrade from PARMVNT_SHD phase.
Regards
Ratnajit

SPAU / SPDD Transport During Upgrade from 4.6C to ECC 6.0

We are currently upgrading R/3 4.6C to ECC 6.0 SR2. During the DEV upgrade, we performed Dictionary Objects adjustments before ACT 7.00 and SPAU adjustments at the end of the upgrade. All the adjustments are collected in a transport.
I read in another thread that we will have to choose 'SELECT FOR TRANSPORT' button in SPAU and not release it. Then, continue with the upgrade. And in the same thread, it is also mentioned that DDIC object modifications should not be handled through transports.
Now, my question is, if I have collected the SPAU adjustments in a transport and continued with the upgrade without choosing the 'SELECT FOR TRANSPORT' button, can I do it after I complete the upgrade before I continue with QAS upgrade? Will the upgrade still automatically detect the transports and move them? And, my other question is, if DDIC modifications are not supposed to be dealt through transports, how else should they be worked upon?
Your response ASAP will be rewarded properly.
Thank you.

Nick, thank you for the reference. Even though I had gone through this note before, I couldn't apply this note because, this note was refering to "R3up" which, I guess, is no more used. "SAPup" is the program currently in use. Also the location mentioned in the note to execute "R3up" is "//usr/sap/put/exe" but, "SAPup" is located under "//usr/sap/put/bin/". So, I am not sure if there is any new notes refering to this. One other question I have with regards to this note is, one of the arguments for the command R3up is, "REL". For SPDD, the note suggests to use target release. And for SPAU, the note suggest to use the release mentioned in the DDIC activation phase.
In my case, I am upgrading from 4.6D (kernel) to 700 (kernel). The DDIC activation shows ACT_700. So, I am sure I would use "700" as value for "REL" for SPDD. But, am I supposed to use "46D" for SPAU? or should I use "700"?
Thank you.

LONGPOST.LOG Errors during Upgrade from 4.6C to ECC 6.0

Dear all,
We have received the below errors during our upgrade from 4.6C to ECC 6.0.
Basically we have received three types of errors:
1.
4PETG065 RSUPGDEC: Table/structure "BAPE_VBAK" (component "SD-SLS" ) enhanced illegally: Error "2"
2.
A2PESEEF_BADI 103 BAdI implementation "/IRM/BADI_SDDOCFLOW" must still be migrated
A2PESEEF_BADI 103 BAdI implementation "ZOTC218E_1" must still be migrated
A2PESEEF_BADI 103 BAdI implementation "ZZ_MG_MASS_NEWSEG" must still be migrated A2PESEEF_BADI 103 BAdI implementation "ZOTC218E_1" must still be migrated
A2PESEEF_BADI 103 BAdI implementation "ZOTC218E_1" must still be migrated
3.
3PETG447 Table and runtime object "/SSF/DHEAD" exist without DDIC reference ("Transp. table")
3PETG447 Table and runtime object "/SSF/DTAB" exist without DDIC reference ("Transp. table")
3PETG447 Table and runtime object "/SSF/PTAB" exist without DDIC reference ("Transp. table")
Can anyone help us how to solve this issues.
Thanks & Regards
Senthil

Hi,
Senthil following are ans to ur questions
1. After the SPAU remediation is completed, should I manually release the transport or should I start the upgrade and the upgrade will release that transport?
Ans : Once your SPAU remediation is completed you should release the requests and then start the upgrade of the DEV system.
2. How do we import this SPDD & SPAU transport in the QA and PRD, I mean at what stage of the upgrade we need to specify/ include this transport?
Ans : Now when you start the QA or PRD upgrade at that time you come across a phase during PREPARE called ADJUSTPRP.
Refer following note for further information --
SAPNote 124522 - Importing a modification adjustment in 2nd upgrade
3. Suppose the QA & PRD has more objects to adjust than our Dev box, and this transport will not take care of the delta objects, so in that case how should we remediate, we need to create an other transport request in QA and then it will become two transports?
Ans : First of all this should not be the scenario where you have more modified objects than that in DEV. As all the modfications should take place in DEV first and then should be transported to QA and then PRD. But in such case what you can do is complete the upgrade of QA system and then you are still having 14 days to complete the SPAU objects. So you can make another request which can be transported as a post upgrade activity once the upgrade is completed in production. For SPDD you will have to take care of the SPDD objects if there are different than those in DEV during the ACT_700 phase only or else you might risk data.
This is the reason why SAP always asks you to follow a proper transport path.
4. If our dev box has more objects for remediation than our QA & PRD, then will these objects be also imported into the QA & PRD box?
Ans : Yes, thats why you should be very sure about the SPAU objects that you have found in DEV. You need to compare the objects with QA and PRD and then only make the modifications.
I hope i have answered all your queries.
Regards,
Suhas

ZSearch Help: will it remain during upgradation from ECC6 to higher version

Hi,
During upgarde from ECC6 to higher versions, will zserach help be moved to higher version automatically or will it be removed and I have to create ZSearch Help again in the higher version.
What about the ZTable, will it be there in higher version or I need to create it again in the higher version.
Thanks,
Priyanka.

Hello Priyanka
Upgrading your SAP system will <b>not affect</b> your Z-objects <b>directly</b>.
However, if your Z-objects reference (i.e. use) SAP standard objects that are changed (or, rarely, are deleted) during upgrading then you may have to adjust your Z-objects. Therefore, keep your (automatic) test scripts available (e.g. eCATT) and run them immediately after the upgrade has been finished.
Regards
Uwe

IDOC extensions during Upgrade from Ver 4.6 to ECC 6.0

Similar Messages

Maybe you are looking for