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.

Similar Messages

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

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.

Structure SI_BBSEG not found during upgrade from 4.6C to ECC 6.0

Hi
We are upgradingour SAP system from 4.6c to ECC 6.0 and we are having an issue while generating the programs, error says '.INCLUDE SI_BBSEG ' not found. It seems like structure SI_BBSEG was not created by SAP'. How would i resolve this issue? i couldnt find any OSS note on this. Please advice.
thank you,
- A

Anil
SI_BBSEG is Include structure of BBSEG & comes already included in it as std SAP. (u can see it in SE11 >> BBSEG)
It does not exist till you want to enhance BBSEG & add your custom fields. Normally those fields will be added to Std SAP screens as custom enhancements . You can go to SE11 & double click; it will ask Do you want to create ?
What is the process you are following for moving Enhancements from 4.6 to ECC6 (user Exits, screen exits) ? If this SI_BBSEG exists in old system, then there must be std screen enhanced which uses the fields of this structure. There could be some programs too which are using this structure while creating FI Documents using std BAPI. recomended that these should move to ECC6 together.
If you have not enhanced BBSEG in 4.6 then refer note : 590977

HR Objects in SPAU during upgrade from 4.6C to ECC 6.0

Hello,
We are in the process of upgrading and have come to the point in SAPup where we need to address all customizations in SPAU. There were several HR objects displayed (both logical and physical info objects), and from what I have been reading, there should be no HR objects listed. I followed the instructions in OSS note 519678 to remove unnecessary HR objects from table SMODILOG using program H99PDSY_REPAIR_SMODILOG. This did remove quite a few, but I am still left with some.
Can anyone provide information on what I should do to resolve this issue. I thought that maybe, the information that HR objects should not be in SPAU could be wrong, so I attempted to reset one object to original. When I did this, it prompted me to create a new "customizing" transport request, when all of the other objects related to SPAU were put into a "workbench" transport. I also understand that there should only be one transport for all SPAU adjustments, so this further makes me believe these objects should not be showing up.
Thank you,
Leeanna

Hello Leeanna,
Apply this note. and execute the mentioned report, this deletes all the HR objects
Note 634146 - SPAU: Objects from the customer namespace in SPAU

M_vmvah missing during upgrade from 4.6C to ECC 6.0

Hi,
After upgrading, our Z programs are having compilation errors due to missing table m_vmvah. Is there any replacement table for m_vmvah in ECC 6.0? Thanks.
Regards,
Abner

1. Call transaction SMQ1 and check whether all queues in all clients (client = '', queue name 'MCEX') have been processed. To process the queues, start the collective run report for each application in the displayed clients. If you no longer need the data in the BW system, deactivate the relevant extraction queues and DataSource in the LO cockpit (transaction LBWE) and delete the queue entries in transaction SMQ1.
2. If you use the V3 update that is not serialized (usually only for application 03): Start collective run report RMBWV303. Then check the update orders in transaction SM13. If there are incorrect update orders in transaction SM13, correct the orders and then start the collective run report again. If you no longer require the update orders, you can delete them. There may be inconsistencies between tables VBMOD and VBHDR. For further information about this, see Notes 652310 and 67014.
3. Before the upgrade, delete the contents of the setup tables. Execute report RMCEX_SETUP_ENTRIES to find out which setup tables still contain entries. You can use transaction LBWG to delete the contents of the setup tables for all clients.
Unfortunately the check that the system carries out during the upgrade or when you import a Support Package does not display all affected applications. Therefore, Note 1083709 provides a check report that you can use to determine all affected applications and tables or queues.

Find button issue in tool bar during upgrade from 4.6c to ECC 6

Hi All,
I came across one issue during the upgarde.
In new system ECC 6:
When i run the transaction IW51 then give the notification type SE(service notificaton) and then hit enter key.
It leads to next screen there enter the value in the FUNCTIONAL lOCATION field some ex 9000004 and
opposite to that field there is a structure list icon.
Clicking that icon it leads to a structure list.
My issue is: the FIND button and FIND NEXT button are disabled in the menu bar.I need the both buttons to be active
When i seen in old system i.e 4.6c
FIND button and FIND NEXT button are active.
I made little change in the new system in include MIHIXF82 as shown below.
SET PF-STATUS 'MAIN' ."EXCLUDING gt_excl_tab.
I commented the EXCLUDING gt_excl_tab.
Now FIND button and FIND NEXT button is active but when i click the FIND button there is no pop up is displayed.
Usually pop up is displayed when we click FIND button in that we can enter the value which we have to find out.
Regards
Jai
Edited by: Jayanth16 on Jan 28, 2010 8:07 AM

Hi,
In that program gui status MAIN is used.
When i see that gui status and in FUNCTION KEYS the FIND button and FIND NEXT button
the function codes are in orange color.Remaing BACK,EXIT,and CANCEL button function code are in white color.
Whether the orange color indicates is in inactive mode?
If so how can i activate those Function codes?
Regards
Jai

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

BW specific task during R/3 upgradation from 4.7 to ECC 6.0

Hi Everybody,
We are planning R/3 upgrade from 4.7 to ECC 6.0. We are using BW 3.5 . So, Can anybody share BW 3.5 specific task during pre-upgrade as well as post-upgrade for ECC Upgrade.
Thanks & Regards,
Sushant N. Tiwarekar

Hello ALex,
There is not a must to upgrade also your solman 3.2 when you upgrade your satellites, only consider if you need the solman diagnostic or not and also that the new functionality in solman 4.0.
Which system is unicode, the satellite?
There is also not problems having a non-unicode solman with unicode satellites and the other, having a unicode-solman "linked" to unicode-satellites.
Hope this helps,
Dolores

Issues during technical upgrade from 4.6c to ecc 6.0

Hi
We are doing a technical upgrade from 4.6C to ECC 6.0. Some transactions in QM module when tested in ECC 6.0 test client give a abap termination message (or dump) and certain transactions like qs42,46, qa18, qs34 etc do not get executed (error = no entry foound for......) and similarly in PP-PI module transactions like C203 have similar problems, even though master data does exist. What should I look for? Can somebody pl. give details on configuration checks and the OSS notes from a functional point of view for a technical upgrade?
For certain transactions I get the error message - "Central system of distribution SM-P06CLNT430_TRUSTED is unreachable RFC destination SM_P06CLNT430_Trusted does not exist" - what does this mean?
thanks
BE

Hi,
1. Have you done successfull installation from 4.6C to ECC 6.0 at the time of PrePare ans SAPUP?
2. Check SP' for QM and PP-PI modules from http://service.sap.com/sp-stacks.
3. Configure RFC connections correctly, SM_<SID>CLNT<No>_Trusted automatically created, not manually.
http://service.sap.com/notes --> search for RFC trusted connections for Ecc 6.0
http://service.sap.com/upgrade.
Regards,
Srini Nookala

Steps to follow in Upgrade from 4.7 to ECC 6.0

Hi ,
As part of Upgrade from 4.7 to ECC 6.0 , Basis team completed Prepare module.
Now Prepare module report says there are some modifications need to be done .
Do i need to make the changes to the adjustments populated in SPDD/ SPAU transaction code before basis team goes for Upgrade ?
If changes are applied to the modifications populated in SPDD / SPAU. How i need to transport these objects ?
Please let me know the steps need to take in transport of these objects .
Cheers,
Reddy

Dear,
Transaction SPDD allows you to adjust modifications to ABAP Dictionary objects during an upgrade, the upgrade will stop at the begin of ACT_700 phase, so you can logon to shadow instance and perform the adjustments in SPDD.
About transaction SPAU that allows you to adjust programs, function modules, screens, interfaces, documentation, and text elements after an upgrade.
You have the option to include the SPDD request from previous upgrade,
The PREPARE includes the ADJUSTPRP phase for this purpose. In this
phase, the system searches the global transport directory for comparison
requests from previous upgrades and offers these for inclusion in the
upgrade. If you do not have this request, you may go ahead with the upgrade
and the proceed with the SPDD / SPAU adjustments during the upgrade.
Please refer to the following SAP Notes for more details:
68678 Exporting modification adjustment for 2nd upgrade
610311 Importing a modification adjustment in 2nd upgrade
124522 Importing a modification adjustment in 2nd upgrade
I hope this helps.
Lucio Rodrigues

Re : Roles of Functional Consultant in upgradation from 4.6b to ECC 6.0

Hi
I need the Roles of Functional Consultant and Technical Consultant in upgradation from 4.6b to ECC 6.0.
Thanks
Anto

Dear Anto,
In Technical SAP,Upgrade from 4.6 to 6.0- the role of any fucntional consultant would involved integrated with the technical Consultant.
The phase starts with the technical Patches apply to the latest stack level which will done by the BASIS Consultants.
Once the System preparation is happened, the next phase is with SPDD phase, Thru this transaction the dictionary Objects-Database elements, database tables and structures of teh latest system can be
compared with the old system.
This results in the version modification results between the old and New versions. During this phase the involvement of the Functional Consultant needed for the tech guy, to identify the functional chnages between the two version (Old and New). Which helps for him either to Reset to Original(ie., adopting the new one) or Adopt Modification in previous system(ie., adopting to older functionality)
Once this is done, the System Upgradation will be done by the BASI, the system will be replaced with new system. At teh end of this phase SPAU phase starts, which inturn reults with version difference in the field namely, Programs, Reports, Screens, Messages, Notes an Function Modules. Here too the involvement of functional consultant neede to determine either reset to original or to go with Adopt modification from the older design, as explained earlier.
At teh end of the, moreover the functional consultant role involved in testing the Entire processes and transactoin in the system for system dump and bugs, in necessity to correct teh same and results with nil errors in production client.
Also the Zprograms invloved in the older versions, needs to be examined for the actual need, and to be justified with adoption in the newer version or by adopting to the updated functionality in the newer version.
Hope this may give better clarity in the involvement of the Functional Consultant in the Updgrade project.
Njoy SAP
Regards,
-Saravanaganesh

Roles of Functional Consultant in upgradation from 4.6b to ECC 6.0.

Hi
I need the Roles of Functional Consultant and Technical Consultant in upgradation from 4.6b to ECC 6.0.
Thanks
Anto

In Technical SAP,Upgrade from 4.6 to 6.0- the role of any fucntional consultant would involved integrated with the technical Consultant.
The phase starts with the technical Patches apply to the latest stack level which will done by the BASIS Consultants.
Once the System preparation is happened, the next phase is with SPDD phase, Thru this transaction the dictionary Objects-Database elements, database tables and structures of teh latest system can be
compared with the old system.
This results in the version modification results between the old and New versions. During this phase the involvement of the Functional Consultant needed for the tech guy, to identify the functional chnages between the two version (Old and New). Which helps for him either to Reset to Original(ie., adopting the new one) or Adopt Modification in previous system(ie., adopting to older functionality)
Once this is done, the System Upgradation will be done by the BASI, the system will be replaced with new system. At teh end of this phase SPAU phase starts, which inturn reults with version difference in the field namely, Programs, Reports, Screens, Messages, Notes an Function Modules. Here too the involvement of functional consultant neede to determine either reset to original or to go with Adopt modification from the older design, as explained earlier.
At teh end of the, moreover the functional consultant role involved in testing the Entire processes and transactoin in the system for system dump and bugs, in necessity to correct teh same and results with nil errors in production client.
Also the Zprograms invloved in the older versions, needs to be examined for the actual need, and to be justified with adoption in the newer version or by adopting to the updated functionality in the newer version.
Hope this may give better clarity in the involvement of the Functional Consultant in the Updgrade project.

Requirements for upgradation from 4.7 to ECC 6.0

Hi Guru's,
Can anybody explain what are the steps required for upgradation from 4.7 to ECC 6.0, technically and functionally. If any body have documents regarding the same, please share.Full marks will be awarded.thanx in advance....

Hi
You have to aware of all related program like BDC's , Screens related errors and all dictionary related problems.
Some function modules may become obsolete, and some screens will change
abnd some new fields will be added in the new versions etc.
Also take care of SPAU and SPDD tcodes.
You should be able to know about Unicode concept in sap.
chk this
http://www.thespot4sap.com/upgrade_guide_v2.pdf#search=%22upGRADE%20STEPS%20-%20SAP%22
also chk these 2 notes in service.sap.com
Technical Upgrade is only a version upgrade without any functionality changes.
The objects that are needed to be upgraded are:
Includes
Function Groups / Function Modules
Programs / Reports
OSS Notes
SAP Repository Objects
SAP Data Dictionary Objects
Domains, Data Elements
Tables, Structures and Views
Module Pools, Sub Routine pools
BDC Programs
Print Programs
SAP Scripts, Screens
User Exits
You can refer to the below links for more information on technical upgrade:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/07/upgradeFROMR3TOmySAPERP-PARTII&
https://wiki.sdn.sap.com/wiki/display/profile/UPGRADEFROMR3TOmySAPERP-PARTIII
http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/2e/6d66647d9011d396b60000e82de14a/content.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5ac31178-0701-0010-469a-b4d7fa2721ca
Reward points if useful
Regards
Anji

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

Similar Messages

Maybe you are looking for