Transports from ECC 5.0 to ECC 6.0

Hello,
We are considering using transports from the 5.0 system to make configuration changes in the 6.0 system (and even some workbench items). Besides, the obvious issues with conflicting configuration, is there a technical reason why they should not attempt this? I look for notes to know it, and there are the note NOTE 1090842, but there are no answer for transports between realese ECC 5.0 to ECC 6.0. Do you know if it is a special case?
Thanks in advance for your answer,
Xènia

Hello,
This is always a bad idea.
However, if you feel like that, I only recommend it if you are transporting Z objects that you know perfectly. This way you can make corrections at the very moment the potential problem happens. Before the import, please compare both objects, in release 5.0 and 6.0, and look for the differences. Plan what would happen if the 5.0 object replaces the 6.0 one.
Don't do it with standard objects.
Regards
Francisco

Similar Messages

Adding Transports from Buffer to Transport Que after DB refresh ECC 5.0

I recently completed a database refresh of our QA system in ECC 5.0. While trying to add transports from the buffer to the transport que, I receive the following.
Transport files for request T01K960494 must still be transferred. The transport exists in our Development instance and before the refresh the transport existed in the QA instance.
Brand new transports are imported into QA without issue.
Has anyone experience this issue and do you have a resolution?
Thanks
David

Hi David,
I wouold check for the cofile & datafile. If this is missing, he is right - otherwise he has a wrong state in his mind ...
Regards
Volker Gueldenpfennig, consolut.gmbh
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

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

Data Retractors from BPC 7.5 to ECC 6.0

We are looking for customers who can share infomation that have successfully built automated data retractors from BPC 7.5 to ECC 6.0.
There is one whitepaper titled "How to... Retract data from BPC 7.5 NetWeaver to SAP ERP Cost Center Accounting, Part I" posted back in July of 2010?
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c029accf-6d95-2d10-79aa-cc291180bf73
This document is a template that has some assumptions built into it for it to work. I know customers will have different requirements, but I would like any comments from anyone who is "Live" with this. How long it took to develop and any issues that you encountered? How often do you run the retractor?
We are also looking at moving parts of the budget in BPC back into Cost Based PA. Can anyone share their experience in creating this retractor (interface) as well?
Thanks in advance,
Steve Boening

Hi
Go through eh below link for Best Practices
http://help.sap.com/bp_hcmv1600/HCM_US/HTML/master_data.htm
[Risk Factors|http://www.informatica.com/INFA_Resources/article_sap_netweaver_mag_data_migration.pdf]
[Different Methods|http://www.sap-img.com/general/what-are-the-methods-to-migrate-data-from-a-legacy-system-to-sap.htm]
[Best Practices|http://partners.netapp.com/go/techontap/NGS_migration.pdf]
Regards
Pavan

Best Practice in Upgrade from ECC 5.0 to ECC 6.0

Dear All,
Can someone help in looking for Best practice in Upgrade from ECC 5.0 To ECC 6.0 Project from Functional FI and CO Side.
Thanks

Moved to a different forum.

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.

ECC Upgrade from ECC 5.0 to ECC 6.0 EHP4 - impact on XI 3.0

Hi,
We are palnning for upgrade our ECC System from ECC 5.0 to ECC 6.0 EHP4. We do not have any plan of upgrade on XI, which is on XI 3.0.
After ECC upgrade please provide the impact on XI 3.0 ?
Will XI 3.0 able to work with ECC 6.0 without any change or any change is required in the XI configuration level, please specify?
Thanks.

>>Will XI 3.0 able to work with ECC 6.0 without any change or any change is required in the XI configuration level, please specify?
As far as I know, no change is required in XI configuration.
Regards,
Praveen Gujjeti.

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!

Transfer of Pricing Conditions from SRM 5.0 to ECC (Extended Classic)

Hi All,
I am currently doing an enhancement on a copy of function module B46B_DPO_TRANSFER and the implementation of BBP_DRIVER_DETERMINE BAdI that will call the copied FM to transfer the pricing conditions from SRM 5.0 to ECC since in standard only net price is being transferred to ECC.
During the creation of PO, everything is ok. All conditions are transferred to ECC.
But we are encountering problems in the replication from SRM to ECC when changes are done in the PO during deleting or inserting a condition to an item. Our problem is in figuring out what will trigger us to use Change types U, I, E, D in populating the CHANGE_ID field in POCOND table that will be used in BBP_PO_INBOUND function module.
During creation of PO, I have set POCOND-CHANGE_ID = 'I' on all conditions to be transferred.
When there are modifications on a PO, I have set POCOND-CHANGE_ID = 'U' and I am encountering problem when new conditions are inserted to an item since it will not be displayed (which I believe in this case, POCOND-CHANGE_ID should be 'I'), and when deleting a condition to an item.
I would like to ask, if there is an indicator that a condition will be inserted to an item for us to assign POCOND-CHANGE_ID = 'I', and for us to assign POCOND-CHANGE_ID = 'D' when a condition will be deleted.
By the way, I used FM BBP_PD_PO_GETDETAIL (exporting: E_PRIDOC) to get the PO conditions to be transferred and have checked E_PRIDOC-DEL_IND to check if a condition will be deleted. Unfortunately, it is not working on the deletion since it seems that DEL_IND field is not being populated if a condition will be deleted.
Many thanks,
Kezia
Edited by: Kezia Layug on Mar 3, 2009 4:24 PM

Hi All,
I am currently doing an enhancement on a copy of function module B46B_DPO_TRANSFER and the implementation of BBP_DRIVER_DETERMINE BAdI that will call the copied FM to transfer the pricing conditions from SRM 5.0 to ECC since in standard only net price is being transferred to ECC.
During the creation of PO, everything is ok. All conditions are transferred to ECC.
But we are encountering problems in the replication from SRM to ECC when changes are done in the PO during deleting or inserting a condition to an item. Our problem is in figuring out what will trigger us to use Change types U, I, E, D in populating the CHANGE_ID field in POCOND table that will be used in BBP_PO_INBOUND function module.
During creation of PO, I have set POCOND-CHANGE_ID = 'I' on all conditions to be transferred.
When there are modifications on a PO, I have set POCOND-CHANGE_ID = 'U' and I am encountering problem when new conditions are inserted to an item since it will not be displayed (which I believe in this case, POCOND-CHANGE_ID should be 'I'), and when deleting a condition to an item.
I would like to ask, if there is an indicator that a condition will be inserted to an item for us to assign POCOND-CHANGE_ID = 'I', and for us to assign POCOND-CHANGE_ID = 'D' when a condition will be deleted.
By the way, I used FM BBP_PD_PO_GETDETAIL (exporting: E_PRIDOC) to get the PO conditions to be transferred and have checked E_PRIDOC-DEL_IND to check if a condition will be deleted. Unfortunately, it is not working on the deletion since it seems that DEL_IND field is not being populated if a condition will be deleted.
Many thanks,
Kezia
Edited by: Kezia Layug on Mar 3, 2009 4:24 PM

Request for PO attachment replication from SRM 4.0 to ECC 5.0 in Extended C

Hi All,
I want to replicate the Purchase Order Item Level attachment from SRM 4.0 to ECC 5.0 in Extended Classic Scenario.
Please let me know the procedure for the same like related BADIs in SRM and ECC.
Could you please send any documents related to Document Manage System to my gmail id sudarsan.srm ?
Best Regards,
Sudarsan

Hi All,
I did the following Steps to replicate PO Attachments from SRM 4.0 to ECC 5.0 in Extended Classic Scenario as per OSS Note 1057932:
Step 1: I activated BAdI BBP_CREATE_PO_BACK~Fill_PO_INTERFACE in SRM System and added the following Code
CV_ATTACH_TRANSFER_ACTIVE = 'X'
CV_ATTACH_BE_STORAGE_CAT = 'DMS_C1_ST'
CV_ATTACH_BE_DOC_TYPE = 'SRM'.
Step 2: I created Doc Type SRM in ECC5.o with the help of DC10 Tr Code.
Step 3: I maintained Data Carrier Type PC entry with the help of DC20 Tr Code in ECC 5.0 and default ebtries for Front End Computer Details. (I crsoss checked Storage Category DMS_C1_ST in ECC5.0, it is available).
Step 4: I maintained all the details (document Types) for PC Carrier Type with the help of DC30 as per OSS Note.
Then I tested the PO attachment replication scenario. I could not find the attachment in ECC5.0 in PO (ECC5.) which available in SRM PO (SRM 4.0)
Kindly guide me or suggest me is there any additional settings required to transfer PO attachment from SRM to ECC5.0
Thanks a lot in adavance.
Thanks,
Koyya

Upgrade from ECC 5.00 to ECC 6.00

We are planning upgradation from ECC 5.00 to ECC 6.00. What will be the role of FICO consultant in detail.

check the customization setting after upgrade
run a Unit Test and Integration Test.
run the Report developed

UPGRADE STEPS FROM ECC 5.0 TO ECC 6.00

Hi,
Can anyone of you help me in the upgrade steps (Process) from ECC 5.0 to ECC 6.0.
Thanks in Advance.
Ram

Hello Ramesh ,
Apart from this also download and have a look on look the Upgrade guide .
URL to Download :
www.thespot4sap.com/upgrade_guide_v2.pdf
Regards ,
Santosh Karadkar

Right SAPup version for upgrade from ECC 5.0 to ECC 6.0

Dear Expert!
I am upgrading from ECC 5.0 to ECC 6.0 , but i have a erro, with SAPup tool, I don't know to select right SAPup version, please show me about that, thank you very much!
Tru Hang

Hi,
As anil you have to download the Upgrade guide, therer you could see the clear information -about SAPup.
they have mentioned the issues with SAPup and they have asked us to use new SAPup version due to the issues of Old SAPup version.
have a look at the below notes
821032 Corrections for SAPup release 7.00
1056649 Corrections for SAPup release 7.10
48184 Upgrade: Stopping a running R3up or SAPup
1070771 Do not use SAPup version 7.00/2, build 24.094 !
You can see lots of threads in SDN lot of threads talks about SAPup issues.
-Srini

Does for upgrade from ecc 5.0 to ecc 6.0 we have to pay money for that

Hi All
Does for upgrade from ecc 5.0 to ecc 6.0 we have to pay money to SAP for that.

hi,
asking or teling ?
I think you need not as long as you are with official support . However please contact sap official support in you region

Upgrade from ECC 5.0 to ECC 6.0 FICO

Hi,
Can anyone provide me the configuration documents with regard toUpgrade from ECC 5.0 to ECC 6.0 in FICO or brief the steps to be done. Plz do reply me at the earliest.
my email ID: [email protected]
thanks
suresh arya

Hi suresh,
1.Activate the New General Ledger Accounting by a single click on the clock icon
2.You will reach to change view "activation of New GL A/cg" detail screen and tick the checkbox and save.
3. After activation of New General Ledger Accounting, you exit the IMG screen When you re-enter , you find that a new node is added Financial Accounting (New)
4.After activation of New General Ledger Accounting , a new sub node appears in the IMG structure.
This sub node is Define Segment
The menu path is:
SAP Customizing IMG ---> Enterprise Structure -
> Definition ---> Financial Accounting ---> Define Segment
In this IMG activity, you define your segments.
If you then define your profit centers, you can enter an associated segment in the master record of a profit center. The segment is then derived from the assigned profit center during posting.
5.Activation has created a new field in Profit Center Master Record : the SEGMENT
6.Leading and Non- Leading Ledgers
In General Ledger Accounting , you can use several Ledgers in parallel. This allows you to produce financial statements according to different accounting principles. A ledger uses several dimensions from the totals table it is based upon. When defining Ledgers , one must be defined as the Leading Ledger . The Leading Ledger is based on the same accounting principles as that of the consolidated financial statements. It is integrated with all subsidiary ledgers and is updated in all company codes. This means that it is automatically assigned to all company codes. In each company code, the Leading Ledger receives exactly the same settings that apply to that company code : the currencies, the fiscal year variant and posting period variant .
You must designate one of your ledgers as the Leading Ledger. It is not possible to designate more than one ledger as the leading ledger.
The menu path is :
SAP Customizing IMG -
> Financial Accounting ( New ) -
> Financial Accounting Basic Settings (New) -
> Ledgers -
> Ledger -
> Define Ledgers for General Ledger Accounting
Clicking on the checkbox identifies one of your ledgers as the Leading Ledger.
7. Activation of Non Leading Ledgers
Non Leading Ledgers are parallel ledgers to the Leading Ledger . They can be based on local accounting principle, for example. You have to activate a non- Leading Ledger for individual company codes. Non- Leading Ledgers can have different fiscal year variants and posting period variants per company code to the Leading Ledger of this company code.
The menu path is :
SAP Customizing IMG -
> Financial Accounting ( New ) -
> Financial Accounting Basic Settings (New) -
> Ledgers -
> Ledger -
> Define and Activate Non Leading Ledgers
8.Assign scenarios to ledgers
A Scenario combines Customizing settings from different business views. Each business view specifies which posting data is transferred from different application components in General Ledger Accounting, such as cost Center update or Profit Center update .You assign the desired scenarios to your ledgers. For each ledger, you define which fields are filled with posting data from other application components.
SAP delivers a number of scenarios in the standard system. It is not possible to create additional scenarios.
The menu path is:
SAP Customizing IMG -
> Financial Accounting ( New ) -
> Financial Accounting Basic Settings (New) -
> Ledgers -
>Fields -
> Display Scenarios for General Ledger Accounting.
9. Cost of sales accounting
Cost of sales accounting is a way to create a profit and loss statement (P&L) for a company by comparing the revenues to the costs or expenses incurred to obtain these revenues.
The expenses are mainly divided by functional area such as:
Manufacturing
Administration
Sales
Research and Development
We can activate Cost of Sales Accounting by the following menu path :
SAP Customizing IMG -
> Financial Accounting ( New ) -
> Financial Accounting Basic Settings (New) -
> Ledgers -
>Ledger------> Activate Cost of Sales Accounting
I hope this helps you
Assign points if useful
Regards
Genie

Transports from ECC 5.0 to ECC 6.0

Similar Messages

Maybe you are looking for