MB_DOCUMENT_BADI - SAP R/3 release upgrade from 4.7.1 to ECC 6

Once finished upgrading from SAP R/3 4.7.1 to SAP ECC 6, from SPAU I see that there was no problem on the implementations of this BAdI. But when I tried the transaction, where this BAdi was implemented in, I realized that my implementations were not working. In addition, from SE19, I see that these implementations are active, so why they aren't working?
I think that there are some problem in BAdI implementations when upgrading SAP release, but I don't know how to solve my problem and turn on my implementations.
Thanks,
Luca

Hi Sunny,
i continued with the option - without ADD ON.
So, this mount point and ADD ON dvd issues are over.
In the next screen, i have to specify the xml file and place the packages under EPS/in. I have done that accordingly and now i get a new error - No matching SAINT package for 'SAP_APPL' found.
Any ideas where i have done wrong?
Thanks,
Mohan.

Similar Messages

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

SQ03, user group removed after release upgrade from 4.6C to ECC6

Dear All,
I have a problem about user group - transaction code SQ03.
After the release upgrade from 4.6C to ECC6 the user group, that I created in the old system, are not present in quality and production environment.
In the development environment there is the user group but doesn't contain the queries that I created in the old environment.
How can I solve this issue?
Can I recover all missing queries?
(moreover I can access to the old environment)
Thanks in advance.
Regards

Hi
Please refer to the SAP note 1278056 and 1278115 - PDS Display: F4-characteristic values are not selectable. Hope this will resolve your issue.
Regards,
JB

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

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.

Regarding Upgradation From 4.6 C To ECC 6.0-Urgent

Hi all
can anybody let me know what is procedure to upgrade the SAP From 4.6 C To ECC 6.0 from MM and CIN point of view
--is Up gradation is just like an implementation or Enhancement process
any help would be appreciable
thanks in Advance
Edited by: JAM SAP on Feb 27, 2008 8:47 AM

Upgrading project mostly involves testing with the existing system with the new system.SAP already released the release notes for this Upgrading ECC 6.0.
(1). YOu have to do unit test/Integration test/Regression test in your new system based on the business process documents prepared for your present system.
(2). You mostly encounter Interface issues(If exist)/Authorization issues/Enhanced naming issues/Usage issues.
(3). In 46C you have to do external configuration for CIN.However In ERP 2005, It is already in built.Hence Knowledge of CIN will be more than sufficient to manage the CIN issues.
(4). More over you must be very confident in the business process.Unless you will receive many UAT issues.
(5). I strongly advice you based on my experience, Whenever you do unit test and Integration test, use your user id to.When you do regression testing, get the user id from user copy all the roles from the user id and create new id.Using this new id you do the Regression testing.This will avoid many problems.
(6). Another Imprtant big issue is patch work infomation.After release of 46C, SAP released many patches for 46C.However these patches are all not updated in to your present 46C system.These patches are already in in built in ECC 6.0, hence you will get diff.result when you do testing.If such a case, advice the user about the patch work, and proceed. In most of my cases , SAP enjoyed with 46C without patch scenario, but in ECC6.0 they started to complain, b'cas the new patches.
(7).Give me your mail id ,I will send you the release notes.
(8).Note down my forum discussion to know about the some of the issues.
Hopefully it will be helpful, Let me know, If you need more Information.Thanks
Reward If useful!

Tehnical upgrade from 4.6C MDMP to ECC 6.0 using CU &UC approach

Hi SAP Experts,
We are embarking on a project for Technical upgrade from SAP R/3 4.6C MDMP system to ECC 6.0 using the CU & UC approach for our Asian operations (comprising of India, Japan, Taiwan & Singapore).
Please share with me the Best Practices you followed in your projects, checklists, DOs, DONTs, typical problems you encountered and the possible safeguards, any other useful information, etc.
Since very little information is available from Organizations who have used this upgrade successfully, I am raising this in SDN to share your experiences during the Technical upgrade.
All useful information will be surely awarded with suitable points.
Looking for your invaluable inputs which will be a BIG help for our project.
Best regards,
R.Rajaraman

Pls go thru the below mentioned notes and its related notes
Note 928729 - Combined Upgrade & Unicode Conversion (CU&UC) FAQ
Note 73606 - Supported Languages and Code Pages
Note 79991 - Multi-Language and Unicode support of SAP applications
Note 959698 - Twin Upgrade & Unicode Conversion FAQ

SAP PI 7.3 Upgrade from SAP PI 7.11

Dear all,
Just a small clarification on PI 7.3 upgrade.
In the document, Decision making factors when moving to SAP NetWeaver Process Integration 7.3 - Upgrade or New
Installation with Phase-out, it is mentioned that
If you plan on taking advantage of the performance benefits of the Advanced Adapter Engine
Extended (AEX), please be aware that there is no upgrade path to move your existing PI to a
java-only AEX. This includes the AAE (Advance Adapter Engine) available with PI 7.1 and PI
7.11. The AAE is the runtime for the AEX but the AEX is more than just the AAE and the AAE
*cannot be upgraded to an AEX*
The second exception is if you are planning on moving scenarios to the AEX that you currently have
running on the AAE. This will require a new installation of the AEX (as stated earlier, the AAE cannot
be upgraded to an AEX) and a change to the configuration of the AAE scenarios
I am just littel bit confused with above statments. My case is as below.
We have SAP PI 7.1 EHP 1 (i.e) SAP PI 7.11 with ABAP and AAE. Most of our interfaces are in AAE and now planning to upgrade to PI 7.3 with both stack (i.e) ABAP and Advanced adapter engine Extended.
My questions are,
1) Can we upgrade our PI to PI 7.3 with both stacks? i don't want to install a new system
2) the above two points are valid if we want to have java only AEX. am i correct

Found out:)

Upgrade from 4.6C to ERP ECC 6.0

Hi,
Help!!! I'm running the prepare the first time and encountered this problem during the Kernel extract. I received this message from '/usr/sap/put/EXTRKRN.LOG'
1 ETQ201XEntering upgrade-phase "EXTRACTKRN_PRE" ("20061016131342")
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '', GwService = ''
4 ETQ399 Environment variables:
4 ETQ399   =<null>
4 ETQ399   auth_shadow_upgrade=0
1EETQ204 Upgrade phase "EXTRACTKRN_PRE" aborted with severe errors
Ramon

Hi Ramon,
The major source of information should be the joblog of the job running APYSAP. During the upgrade this should be the joblog of the SAPup job.
When trying to reproduce by hand make sure you have
- SAPUP *LIB in your library list and an
- empty target directory '/usr/sap/put/exe'.
If you want you can frame your APYSAP call with STRO4TRC and ENDO4TRC from the 700 kernel library (add SAP700DEV to your libl only for the call of xxxO4TRC and remove it afterwards). Specify a trace id as a name, your job and qinter as the subsystem.
HTH,
Thomas

Upgrade from R/3 46C to ECC 6.0 (ERP 2005)

Hello,
We want to know the version of the kernel that has to be installed to begin with the upgrade. We have the 46D version already installed, do we have to update the kernel to 46D_EXT (is it the latest?) ?
Thanks in advance,
Pablo

Hello,
if you install the latest Oracle Client you can use 4.6D with Oracle 10g. Our configs work well with this client-kernel pair.
You can find the documentation at http://service.sap.com/instguides "/other documentation/Database upgrades/Oracle: Upgrade to Oracle Database 10g Release 2 (10.2): UNIX"
Best regards
Tamá

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

Old workflow behaving differently in upgrade from 4.6 C to ECC 6.0

We are facing an issue in the workflow . Old and existing workflows before the upgrade have different paths then the new workflow in the ECC6.
Means , the same workflow when started from scratch is working fine , but when the old workflows are copied and run (the way which client is testing or you can say this way they do their work), then the workflow takes a different path. All the forks ,events,if clause are appearing as the last steps in the workflow grapic.
Now my point is, that in upgrade there should not be any major change happened in SAP, seems that we may be missing some step to be performed after upgrade or during upgrade forits standrad as well as custom worflows.

Hello,
I've never done the upgrade myself, but judging from what I've read it's very very important that you try to complete as many workflow instances before the upgrade. That doesn't help you much, but maybe others will take note.
All you can do is search for your particular problem. Are there any error messages in the workflows?
regards
Rick Bakker
Hanabi Technology

Upgrade from 4.6 c to Ecc 6.0

Hi all,
We have R/3 on 4.6c with windows 2000 on 32 bit with Sqlserver 2000, we are planning to upgrade to Ecc6.0 and windows to windows 2003 with 64bit and sqlserver 2000 to sqlserver 2005
Can you plz guide me the the process of doing things like
which one i have to do like 32bit to 64 bit or windows to 2003 then bit upgrade then DB .
I have done upgrade on 4.7 to Ecc 6.0 does 4.6c upgrade to Ecc 6.0 is the same process...
Plz suggest...
Thanks,
Subhash.G

Hi all,
We have 4.6c and windows 2000 32 bit and sql server 2000 32 bit on 64 bit hardware.
On the same if we want to upgrade windows 2003 to 64 bit then sql server 2005 64 bit and 4.6c to ECC 6.0 what is the approach.
I have one approch please guide if i am wrong.
For OS Upgrade:
There is no approach to upgrade 32 bit windows 2000 to 64 bit windows 2003, we have Install the 2003 from scrath.
For Sqlserver:
We can use attach/detach methods, we have to install sqlserver 2005 64 bit with correct collation Bin2 and attach the DB .
For SAP upgrade:
Install the 4.6c or restore the file system , since we have the DB , replace the kernel with 4.6D 64 bit then do the upgrade.
Please correct the approach if it's wrong.
Thanks,
Subhash.G

Urgent - steps need to done, when MS SQL upgraded from 2000 to 2005

SQL server is upgraded from MS SQL 2000 to MS SQL 2005.
Please let me know the steps ned to be performed at XI .

hi satya kiran,
check the below blogs,
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c90ecf8d-0d01-0010-4aa3-e6fc4da46bb3
The process to perform the migration you describe is relatively easy. While note 799058 is relevant, you should first have a look at the System Copy Guide, which applies to your system. These guides can be found on SAP Service Marketplace:
Release & Upgrade Info  Installation & Upgrade Guides  SAP NetWeaver  SAP NetWeaver 7.0 (2004s)
Click on Installation, a new window opens. Check section Installation - SAP NetWeaver Systems
You will see links to system copy guides for Service Release1 and Service Release 2, and separate entries for ABAP only systems, Java only systems and double stacks.
For example: the SR2 guide for ABAPJava has the title: System Copy for SAP - Systems Based on SAP - NetWeaver 7.0 SR2 - ABAPJava
Each of this guides has a brief chapter on copying a MSSQL database. Please carefully read the guide and the SAP notes it refers to. The overall procedure for an ABAP only system will look like this:
1. Apply note 600027 (change SQL Server collation) to your existing SQL2000 database. You HAVE to perform this step before moving the database to the new hardware.
2. Prepare your new servers (Windows, SQL2005 installation following the SAP guidance on collation et cetera).
3. Detach the SQL2000 database from your old system, copy the datafiles to the new machine and attach the database to the new SQL2005 server.
4. Follow the system copy guide and run sapinst to install the SAP central instance and configure the database.
Copying the Java stack is a little bit complicated, because you have to create an export of your Java data on your old system first. This is explained in great detail in the system copy guide.
SAP 4.6C on SQL 2005
Note: reward points if solution found helpfull
Regards
Chandrakanth.k

MB_DOCUMENT_BADI - SAP R/3 release upgrade from 4.7.1 to ECC 6

Similar Messages

Maybe you are looking for