Migrating BADI from 4.7 to ECC 6.0

Dear Gurus,
We r migrating from SAP 4.7 to ECC 6.0
We have one BADI - ME_PROCESS_PO_CUST where we have made changes according to the requirement
After upgrading to ECC 6.0. This BADI is not working even though it is in active mode.
Any specific procedure for BADIs during upgrade
Please let me know how to make it work ?
Rgds,
Saurabh

hi Saurabh,
did you got solution
pls let me know that, we have same problem...
thanks in advance.

Similar Messages

Migrating BADI defn during Upgrade to ECC 6

Hi All,
During Upgrade from 4.6C to ECC 6 , we are encountering a BADI Definition in SPAU list.Please let me know the procedure to handle this. Is it the same way as we migrate Classic BADI to ECC 6.0 New BAdI->Enhancement Implementation?
Thanks
Vasuki

Can you specify which BADI is giving you a problem.
Regards,
Suhas

Migrated BADI Implementation not triggering in ECC 6.0

Hi Experts,
Need your urgent assistance how to deal with migrated BADI implementation which is not triggering in ECC 6.0. This is for PO (ME_PROCESS_PO_CUST). In the original version (4.6) it was working fine. But when this is migrated to ECC 6.0, it's not firing. Please help to trigger this one in ECC 6.0.
Points will be awarded and thanks in advance,
LM

Hi LM,
Can you just paste the code in the BADI.(The method in which code is there)
Is this BADI implemented and in the Active status.
Check in SE19 if the implementation exist or not?
There may be chances that some condition is not met which can trigger this BADI. Have you read the documentation of the BADI?
Regards,
Atish

Data Migration from Legacy system to ECC systems via ETL through SAP PI

Hi All,
I wanted to know if we can migrate the data from Legacy systems to ECC systems via PI.
What I understand is there is ETL tool is used to extract the data from legacy system, and what client is looking to load that data via PI?
Can we do that ? I am concerned because this will involve mass data?
If I have to use PI , I see option of PROXY / IDOC /FILE as receiver in ECC system (take the data from ETL)?
Can somebody has done this earlier , please share the approach.
Thanks,
Pushkar Patel

Hi ,
I require few details from you.
1. What ETL tool you are using, If Informatica, it already have PowerConnect to connect to SAP. So you can create source and Target Structure and also you can use RFC's to send data to R/3. Else, for other ETL tools, can you prepare RFC's or any other way to send data to R/3. let me know the tool.
2. Does R/3 contains the master data tables? If yes, then try to use LSMW for Mass upload of data to tables.
If your client don't want to use either of these options please elaborate, what is the case.
Regards
Aashish Sinha

HR Payroll Data Migration from 4.6C to ECC Upgrade

Hi
We are going to Upgrade our 4.6c R/3 system which includes HR to ECC6.
After this upgrade we going to start the Data migration of all data inclduing HR payroll from 4.6c to ECC.
1).Can anybody advise what are the options for loading Payroll data from 46c to ECC ..? After Payroll data migration we must be able to see all the Payroll results from the previous system.
2) is there any standard programs availble for Payroll data migration ..?
Also if anybody have any info/links on Payroll/HR data migration please help to advise.
Thanks a lot for your info/Time.,
Edited by: Dp on Apr 3, 2008 11:41 PM

Hi Somar,
I could not find the mentioned post "HR Upgrade". Please let me know the details of the "HR Upgrade" details which need to be kept in mind during upgrading R/3 4.7 to ECC 6.0
Yes, we have got the list of "Modification Objects" using the SPAU. Please confirm that during our upgrade, we just need to work on these objects which were changed/repaired by us according to our business need.
And, apart from that, please let me know should I need to worry about any OSS notes specific to 4.7, which is not applied to our system and got released after the ECC 6.0 Enhancement Release 3.
I understand that if we have a system that has the Patch and SP level as in our production system and do the upgrade to ECC 6.0 all the HR functionalities will be automatically taken care. Please confirm.
Thanks in advance for your help.
Regards,
Vijay

Migration from 4.7 to ECC 6.0 - Deactivate Update of Classic General Ledger

My client has migrated from 4.7 to ECC 6 version. In the ealier version we had a report developed in FI Module, which was created as a local object.
Now when we are trying to activate the same development in ECC 6.0 and I am trying to use the dynamic selections option of this report, system is throwing an error and taking to this customisation node :
Fin Accounting Global Settings (New)->Tools ->Deactivate Update of Classic General Ledger (GLT0).
Can I know the implications of this option ? Can I deselect the check boxes mentioned in this node ? What could be the consequences ?
Please guide me.
Thanks
Ravi

Hi
GLTO is the table that used to get updated with the totals prior to ECC 6.0 (in 4.7).
After migrating into ECC 6.0 the GLTO is no more valid and the new table FAGLFLEXT replaces GLTO.
SAP also recommends to deactivate the update of GLTO via Fin Accounting Global Settings (New)->Tools ->Deactivate Update of Classic General Ledger (GLT0) once you have establised that the new GL is working correctly.
I dont foresee any consequences of deactiavting GLTO if the new GL has been activated in your new client and you are sure that the NEW GL is working correctly.
Good Luck
Hari
null

Migration of Cost Centre Hierarchy from 4.7 to ECC.0

Hi Gurus
Our client is upgrading from 4.7 to ECC 6
Now currently we have a standard hierarchy in Legacy system and multiple alternate hierarchies.
I would request your suggestions on the best way to be able to combine and modify the Hierarchies outside Legacy System before uploading into ECC.
I could find an IDOC COGRP01 which can create cost centre groups which requires data in a particular format.
Best Regards
Varun

Hi Varun
Choice is yours! Whether you modify it in the Source system 4.7 version and then transfer it to ECC or you move it as it is to ECC and then modify it in ECC
you will have to choose between the two
Regards
Ajay M

Could I migrate scheduled jobs from 4.6C to ECC 6?

Hi experts,
I need to copy all background jobs from 4.6C to ECC 6? Is there a tools supported by SAP?

Dennis,
Does it work?
Regards,
Faisal

BADI for MIGO transaction in ECC 6.0

Hi All,
We are upgrading our SAP R3 from 4.6c to ECC 6.0.
In the new system, Transaction SE18 now has two options
1. Enhancement spot
2. BAdI Name
When I display my BADI MB_DOCUMENT_BADI
Attributes tab shows BAdI migrates to enhancement spot MB_GOODSMOVEMENT
When I display Enhancement spot Technical details Tab shows Enhancement Implementation Status shows "Initial".
We have implemented this BADI in our 4.6c version. And its triggering when I run MIGO transaction.
In the new system BADI is not triggering when I run the MIGO.
Above is the only difference I found in the new system when compared with our old system settings.
Can any one suggest me what all the things I need to take care to get working this BADI
Thanks,
Satish

Hi satish,
Pls check here,
http://www.esnips.com/doc/e06e4171-29df-462f-b857-54fac19a9d8e/ppt-on-badis.ppt
http://www.esnips.com/doc/10016c34-55a7-4b13-8f5f-bf720422d265/BADIs.pdf
http://www.esnips.com/doc/43a58f51-5d92-4213-913a-de05e9faac0d/Business-Addin.doc
http://www.esnips.com/doc/1e10392e-64d8-4181-b2a5-5f04d8f87839/badi.doc
http://www.esnips.com/doc/3b7bbc09-c095-45a0-9e89-91f2f86ee8e9/BADI-Introduction.ppt
Cheers
Hareesha k

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

Asset query execution performance after upgrade from 4.6C to ECC 6.0+EHP4

Hi,guys
I am encounted a weird problems about asset query execution performance after upgrade to ECC 6.0.
Our client had migrated sap system from 4.6c to ECC 6.0. We test all transaction code and related stand report and query.
Everything is working normally except this asset depreciation query report. It is created based on ANLP, ANLZ, ANLA, ANLB, ANLC table; there is also some ABAP code for additional field.
This report execution costed about 6 minutes in 4.6C system; however it will take 25 minutes in ECC 6.0 with same selection parameter.
At first, I am trying to find some difference in table index ,structure between 4.6c and ECC 6.0,but there is no difference about it.
i am wondering why the other query reports is running normally but only this report running with too long time execution dump messages even though we do not make any changes for it.
your reply is very appreciated
Regards
Brian

Thanks for your replies.
I check these notes, unfortunately it is different our situation.
Our situation is all standard asset report and query (sq01) is running normally except this query report.
I executed se30 for this query (SQ01) at both 4.6C and ECC 6.0.
I find there is some difference in select sequence logic even though same query without any changes.
I list there for your reference.
4.6C
AQA0FI==========S2============
Open Cursor ANLP                                    38,702 39,329,356 = 39,329,356      34.6     AQA0FI==========S2============   DB     Opens
Fetch ANLP                                         292,177 30,378,351 = 30,378,351      26.7    26.7 AQA0FI==========S2============   DB     OpenS
Select Single ANLC                                  15,012 19,965,172 = 19,965,172      17.5    17.5 AQA0FI==========S2============   DB     OpenS
Select Single ANLA                                  13,721 11,754,305 = 11,754,305      10.3    10.3 AQA0FI==========S2============   DB     OpenS
Select Single ANLZ                                   3,753   3,259,308 = 3,259,308       2.9     2.9 AQA0FI==========S2============   DB     OpenS
Select Single ANLB                                   3,753   3,069,119 = 3,069,119       2.7     2.7 AQA0FI==========S2============   DB     OpenS
ECC 6.0
Perform FUNKTION_AUSFUEHREN     2     358,620,931          355
Perform COMMAND_QSUB     1     358,620,062          68
Call Func. RSAQ_SUBMIT_QUERY_REPORT     1     358,569,656          88
Program AQIWFI==========S2============     2     358,558,488          1,350
Select Single ANLA     160,306     75,576,052     =     75,576,052
Open Cursor ANLP     71,136     42,096,314     =     42,096,314
Select Single ANLC     71,134     38,799,393     =     38,799,393
Select Single ANLB     61,888     26,007,721     =     26,007,721
Select Single ANLZ     61,888     24,072,111     =     24,072,111
Fetch ANLP     234,524     13,510,646     =     13,510,646
Close Cursor ANLP     71,136     2,017,654     =     2,017,654
We can see first open cursor ANLP ,fetch ANLP then select ANLC,ANLA,ANLZ,ANLB at 4.C.
But it changed to first select ANLA,and open cursor ANLP,then select ANLC,ANLB,ANLZ,at last fetch ANLP.
Probably,it is the real reason why it is running long time in ECC 6.0.
Is there any changes for query selcection logic(table join function) in ECC 6.0.

Upgrade from 4.0B to ECC 6.0 on iSeries

Last time we were looking at an upgrade to ECC 5.0, we were told we would have to do an upgrade to 4.6C first and then a migration to Unicode. I have now had 2 consultants tell me that is not necessary - basically that we can go straight from 4.0B to ECC 6.0. Methinks they don't know naything about the iSeries but I've been wrong before (once or twice). Can someone give me the definitive answer here? (or a reference to the definitive OSS note) Do we need to go to 4.6C and do the Unicode migration first or not? Thanks - Rick

Hi Rick,
unfortunately I have to tell you, that your consultants and the postings above are WRONG ;-((
The general guide is correct for everything except iSeries and your guide is a "basis guide only" => it does not cover 4.6C that would be the "in between release" for you.
You have to upgrade to 4.6C first (on EBCDIC) - then you have to do a codepage conversion on 4.6C level to ASCII. Then you can upgrade to ECC 6.0 that is ONLY provided in ASCII or Unicode but NOT in EBCDIC !!!!
I don't know where this is exactly documented (there are "millions" of places) - perhaps the SAP collegues do have an easy idea here ...
What should you do ?
You should thing on a 3-4 days downtime and do all in one step - ugly, but in my eyes the only useful solution. We did this several times in such situations => it is reliable and supported from SAP.
Regards
Volker Gueldenpfennig, consolut.gmbh
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

Transactions missing in Role After Upgrade from 4.6c to ECC 6.0

Hello Friends,
I did multiple searches on this question but it was unsuccessful. We are upgrading from 4.6c to ECC 6.0. We are testing roles to make sure the migrate properly.
Irrespective of su25. There are transactions that are not obsolete and are missing in ECC 6.0
For example if I have a role called FIROLE. Which has 20 tcodes in 4.6c. When we upgrade to ECC 6.0 8 tcodes will be missing. This is not because the tcodes become obsolete.
What is the best way to approach this. Should we be testing each role?
Thanks!

Hello Imran,
transactions can be 'obsolete' also if they still exist.....
If the application developers create new functionality, new look,.... in new transactions but still let the 'old' ones in the system.
Just think about the ME2*-transactions..... The developer can decide, that such new transactions should replace the old ones after upgrade in the roles or let the old ones as they are.
You can get an overview about replaced/obsolete transactions by reviewing table PRGN_CORR2 (make sure, that you have the latest version, according to [SAP Note 991377|https://service.sap.com/sap/support/notes/991377] !!!). SU25 gets its information from that table.
b.rgds, Bernhard

HR Upgrade from 4.6c to ECC 6.0

Hi,
I am currently about to start a HR Upgrade project from 4.6c to ECC 6.0. Does anyone have the checklist of activities to be followed during upgrade process or any plan for upgrade process in detail. Anyone involved in upgrades pls do send across.
Regards
Jyothi

Hi,
We have recently upgraded from 4.6C to ECC 5.0. Checklist would be like...during upgrade you need to clear SPAU, there you may get cought in Schema, Rule, Functions,,you need to check there. Also check all User exits & BADI's.
After upgrade you need to check all user defined variants properly since some screen might have changed during upgrade. Also check WT characteristics, since some standard WT charactersistics have been changed.
Apart from this, there was no major issue in our upgrade. It went on smooth.
Hope this helps.
Thanks,
Sarika.

DB2 Connect Server appear after Migrating DB2 from v8.2 to v9.5

I migrated the database software of SAP ECC 5.0 System from DB2 v8 fixpak 17 to DB2 v9.5 fix pack 4. After I installed the SAP DB2 licenses, I noticed that a new product "DB2 Connect Server" remained in 'Trail' status.
Product name:                     "DB2 Connect Server"
License type:                     "Trial"
Expiry date:                      "01/02/2010"
Product identifier:               "db2consv"
Version information:              "9.5"
I did not select this product during the installation of Enterprise Server Edition.
Do I need to remove the product "DB2 Connect Server"?
Is there any problem with let the product "DB2 Connect Server" expired?
Will the following command remove the product?
db2licm -r db2consv
Thanks in advance!

Dear Sameer,
DB2 Connect Server is independent component whose purpose is to connect applications to data.
DB2 Connect provides connectivity to mainframe and midrange databases from Linux, UNIX, and Windows based platforms. You can connect to DB2® databases on OS/390 and z/OS, iSeries, VSE, and VM. You can also connect to non-IBM databases that comply with the Distributed Relational Database Architectureu2122 (DRDA®).
If you are not having any scenarios (in you system landscape) to use DB2 server/client Connectivity to mainframe/mid-range databases, then you can remove that product by executing db2licm -r db2consv
If your DB2 connect Server license is already expired, and you are not able to remove it, then following workaround will be helpful.
Workaround may be:
1. db2stop
2. Adjust your system clock at some point in past when this license was still trial.
3. db2licm -r db2consv
You can get some useful information about DB2 connect role in SAP landscape in this document[ Streamlining DB2 Connect for SAP|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/207c5c32-51ea-2a10-c7bc-bcfca74552d5&overridelayout=true].
Regards,
Bhavik G. Shroff

Migrating BADI from 4.7 to ECC 6.0

Similar Messages

Maybe you are looking for