SPDD issue

Hi All,
I need help regarding SPDD Adjustment Transport Request .
Now we are doing SPDD for Production system but the problem is
While adjusting the standard objects It asks for Transportable CTS but for any Z-includes or Z-objects created at this phase It is asking for LOCAL CTS .
Now the problem is We are unable to Merge both the CTS into One u2026because type is different ( We need one CTS for SPDD).
My Question is Why it is asking for Local CTS for Z-objects in Production System ..
Thanks
Bobby

Hi Bobby,
check whether i have answered your questions.
"While adjusting the standard objects It asks for Transportable CTS but for any Z-includes or Z-objects created at this phase It is asking for LOCAL CTS . "
A) If your Z* objects are under local packages then it will create local tranport. Make sure you are saving in the right transportable package (i.e ZPKG ).
"Now the problem is We are unable to Merge both the CTS into One u2026because type is different ( We need one CTS for SPDD)."
A) You cannot merge because you saved the Z* objects changes to local transport.
"My Question is Why it is asking for Local CTS for Z-objects in Production System .."
A) Check your Zobjects package i.e under which pkg your are saving. check in tcode:se80 to get more details of the Zobject you saved or check the attributes of the Z objects.
Once you are able to fix this local transport to Transportable request you can merge the transports.
regards,
Vamshi.

Similar Messages

SPDD issues

Hi All,
We are in the process of upgrade from 4.7 to ECC 6.0.
We got a warning modification adjustment without modification assistant . We are not able to get the fix for it now.
It is a warining with BNKA table . The warning message shows that issue is related to Technical settings. I have checked technical settings for BNKA table in the both source and target systems in upgrade . I dont find any difference so we are planning to proceed with upgrade now with out applying any adjustments at this point of time . Please let me know If we proceed with upgrade now with out modification adjustment made Is it possible to make changes at later stage >
Regards,
Reddy

If you don't do those adjustments now, the same error will popup again in your production upgrade.
I suggest doing the adjustment (just step in and save), create a transport of that and use that transport for the production so your production upgrade won't stop at the same place.
Markus

SPDD - Technical setting issue on BNKA table

Hi All,
We are in the process of 4.7 to ECC 6.0 upgrade.
Please see the SPDD screen shot
http://docs.google.com/Doc?id=dctrtng5_0dqxqcw
In this what can we do with the issue related to BNKA table. It shows it is a warning with Technical setting.
I have verified with source system version of BNKA table technical settings with the upgrade shadow system BNKA table technical settings . I dont find any difference .
Please let me know what can i do .
Regards,
Reddy

Hi ,
Thanks for reply.
Please find the technical settings in my system
Data class APPL0 Master data, transparent tables
Size category 2 Data records expected: 8.000 to 32.000
and buffering not allowed
I checked both systems- sanpit system and the shadow system verified is there any changes in technical settings ... I dont find any changes in this ...
But in the screenshot of SPDD it is showing as warning under without modification adjustments.
If it is a warning can we ignore this and can add this to transport . or what is suggested ..
I dont find any difference in both technical settings ... give me some idea..
Cheers,
Reddy

Issues during upgrade - SPDD

Hi,
We are doing the upgrade from SAP R3 4.6C to ERP 6.0, during SPDD phase we are getting errors while adjusting table VBAP. If you go to tcode SE14 there it is not allowing us to activate and adjust database. While activating the table it throws the error message as "Table VBAP could not be activated - E- Table VBAP ( error adjusting the database)"
Thanks in advnace.

Hi,
Have you compared as what changes were made to the VBAP in 4.6C.
Also can you tell what is the long text of the message.
regards,
Atish

Issues during SPDD - Urejent

Hi,
We are doing the upgrade from SAP R3 4.6C to ERP 6.0, during SPDD phase we are getting errors while adjusting table VBAP. If you go to tcode SE14 there it is not allowing us to activate and adjust database. While activating the table it throws the error message as "Table VBAP could not be activated - E- Table VBAP ( error adjusting the database)"
Thanks in advnace.

You will need to find out, why it can´t be activated, you will get lots of subsequent errors if you ignore that.
Markus

Upgrade issue

Hi Experts,
I am upgrading my system to EHP5. While running phase MAIN_SHDRUN/ACT_UPG the upgrade stops and does not proceeds further. Below are the logs generated:
>> 2011/02/09 08:44:24 START OF PHASE MAIN_SHDRUN/ACT_UPG
running G:\EHPI\abap\exe\tp.exe pf=G:\EHPI\abap\bin\SHADOW.TPP checkimpdp RE2
>>>> Repository modifications <<<<
You must now include your repository modifications in the new SAP import.
6 modified objects are found to be adjusted and 0 objects are automatically
maintained by import of an adjustment transport bound to this procedure.
CAUTION: It is impossible to keep these modifications after you have
confirmed this query!
If you want to adjust your repository, please proceed as follows:
Logon to the shadow instance as user DDIC in client 000 on server
    mb3ap1023 instance: 01
Set the System Change option with transaction SE06.
Create users for modification adjustment by copying user DDIC with
    transaction SU01.
Logon to the shadow instance as ordinary user and make adjustments with
    transaction SPDD. Refer to the manual for further information.
01) * Adjustments made, continue with procedure
02) - Continue without adjustments
03) - Exit this program
: Adjustments made, continue with procedure
Collecting adjustments ...
Collection done - creating cofile ...
running G:\EHPI\abap\exe\tp.exe pf=G:\EHPI\abap\bin\ACTUPG.TPP put RE2
=> Received signal Ctrl C from keyboard and exited at 20110209220536
Got interrupt. When you restart SAPehpi all currently running subprocesses
will be checked. It is strongly recommended to wait for
these processes (which is the default behaviour).
The above logs say that while upgrading it recieved ctrl C. Now I dont know how it received ctrl C. Also it always stops at 22:05 pm only.
Please help in resolving the above issue.
Thanks,
RJ

Hi,
My Upgrade has again got stucked in Pre- Processing step, in MAIN_SHDRUN/ACT_UPG phase.
The error which I am getting is :
DSU Execution error:
Unable to execute the SDT request ABAP operation pre-execute on hostname mb3ap1023 instance 00 Pre-Uptime execution of the ABAP upgrade request ABAP has failed Error from unit observer Tool connector failed with FATAL ERROR: Missing id in line ' "15228" SFX;20110219203107;20110220033916;"Another SAPehpi (started first)";"SAPehpi":dw' . Connection to SAPup could not be established, see following messages. Could not connect to host mb3ap1023 on port 4240. java.net.ConnectException: Connection refused: connect java.net.ConnectException: Connection refused: connect
Please help me in resolving the above issue.
Thanks,
RJ

Help required in running SPAU and SPDD transactions for post upgrade

Hi All,
We are doing a system upgrade to EHP1.
We need help in SPAU and SPDD runs and why are they required in upgrade activity.
Kindly respond.
Thanks in advance
Regards
Rashmi

Hi Rashmi,
SPDD and SPAU are modification adjustments that you need to adjust after upgrade. This is a situation where the upgrade has to enhance some structures and elements that was available in previous version (probably 3.x). The system can not determine whether to overwrite the structures or to retain the old version. If the structures are custom structures, the system might overwrite any enhancements that you have done. In this kind of situations, the system puts any such structures and elements that it can not make a decision into these 2 lists. SPDD is for dictionary objects and SPAU is for configurations. You have to fix all the issues that are produced in these transactions. You need to first fix the ones in SPDD list and then the SPAU list. Once you drill down in those lists, it asks you to take actions like "change it", "keep the old version" or "ignore the changes" (I think these are the options). You need to chosse these options based on your analysis and turn all the yellow and red ones into green. Hope this gives you some idea.
Thanks and Regards
Subray Hegde

ABAP related issues in 4.7 to ECC 6.0 Upgrade

Hi All,
We are in the process of upgrade of SAP 4.7 non unicode to ECC 6.0 non unicode system .
Please let me know what are the things we need to check& what are the issues related to ABAP will encounter in this process.
Please provide the touch points which we need to take care.
Regards,
Reddy

Hi
While doing Upgrade 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
and 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.
check 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
Regards
Anji

Regarding custom objects in SPDD

Hi Experts,
I am working for an upgrade project from 4.6C to ECC 6.0. I need some clarifications regarding use of SPDD.
1. Will the SPDD list only the standard objects or will it display the custom objects also?
2. If SPDD is not going to display the custom objects, Can you throw light on how to work with custom objects like custom tables.
For Example, If there is a change in the length of domain or data element used in a custom table during the upgrade, Is there any standard program or transaction to list or handle all such cases instead of doing it manually.

HI,
refer this link,
[http://help.sap.com/saphelp_nw04/helpdata/EN/2e/6d66617d9011d396b60000e82de14a/content.htm]
[Re: issue on upgrad spdd]
[http://help.sap.com/erp2005_ehp_04/helpdata/EN/2e/6d66587d9011d396b60000e82de14a/frameset.htm]
Thanks
sarves

4.6C to ECC 6.0 upgrade - Issue with Virsa Compliance Calibrator

The issue is that phase IS_SELECT during the PREPARE is not detecting VIRSA as an add-on. This of course will result in VIRSA not being upgraded and the system will be unstable ( note 989368 ). Also, I can't choose to delete the add-on either.
We installed the compliance calibrator before SAP purchased VIRSA. So, the tool was installed through transports, not SAINT. I assume this is why phase IS_SELECT is not seeing the tool.
Any ideas?
-Scott

Received a reply from SAP. Since VIRSA was installed through STMS the IS_SELECT phase will not see the add-on. I had to do the ECC 6 upgrade as normal and then install VIRSA 4.0 for SAP 700 systems through SAINT.
I had to clear SPDD and SPAU as much as possible for /VIRSA/* objects. However, there were six objects I could not clear. This did not cause any issues.
Notes 1006083 and 985617 are needed for this procedure.
Thanks for all the suggestions.
-Scott

SPDD - Modifications

Hi All,
We are in the process of upgrade from 4.7 to ECC 6.0.
Please find the screenshot of the SPDD transaction
http://docs.google.com/Doc?id=dctrtng5_0dqxqcw
In the deleted objects it shows that there is a table named
/RWD/NOTESLINK
when i try to create this table it populating an error message "/RWD/" namespace doesnot exist.
but when i check tables in se11 with "/RWD/* " then i am able to get 17 table entries.
If we check for no of table entries on source system it shows 18 entries.
It mean do we need to create it ? if it is not allowing us to create because of the namespace "/RWD/" does not exist then what can we do ... Is there any possibility we can ignore this for now and can proceed with upgrade work or do we need to fix this then only we can proceed our updage work ?
Please suggest me what can we do on this.
Cheers,
Reddy

Ignore the issues and go further with upgrade

SPDD - Technical settings

Hi All,
We are in the process of 4.7 to ECC 6.0 upgrade.
Please see the SPDD screen shot
http://docs.google.com/Doc?id=dctrtng5_0dqxqcw
In this what can we do with the issue related to BNKA table. It shows it is a warning with Technical setting.
I have verified with source system version of BNKA table technical settings with the upgrade shadow system BNKA table technical settings . I dont find any difference .
Please let me know what can i do .
Regards,
Reddy

It seems the changes to technical settings are reverted back but there is an entry in the log which populated this warning message so we went forward with ACT_XXX phase of upgrade.

SPDD question

Hi,
I have a question on spdd modification
When I adjusted SPDD modification, I followed SAP proposal and created a structure ZAA as include structure,
But there is a warning on this structure(enhancement category), I ignored this warning in SPDD modification. and the request of SPDD hasn't be transported to QA system , because
I adjusted SPDD on QA again,I will do it on PRD again.
The problem is:
1: After DEV system Upgrade, we are doing some syntax correction, also, I want to correct these two structures's warning, but these two structures are locked by user (SPDD user ) and client 000.
so I cann't correct these two structures.
How should I do on these issue.
(Not only DEV, but also QA and PRD)...
2: In Standard spdd flow, is it necessary to correct the add-on table's syntax warning:enhancement category (This add-on table is created in spdd phase)??
3: If I correct the warning(enhancement category) of question 2 after upgrade ,is there any impact?
Best Regards,

Hi Harry,
Correction of these Warnings is not required. If you release the request in DEV you should be able to correct these structures again. Then you can transport them to QA and PRD. Let me know if this helps.
Thanks,
Sai

SPAU SPDD Transport Strategy for following Upgrades

Hello All,
We are doing CUUC from 4.7 NUC to ECC 6 Ehp4 UC
After completing our Upgrade from 4.7 NUC to ECC 6 NUC in the original host, I stopped the Upgrade tool at the point when it asks for SPAU adjustements in Post Processing Step, did the Unicode Conversion in which we built the Target ECC 6 UC System in a separate host (host: ecctemp).
So,
1. The Upgrade Directory and ECC 6 NUC System resides on the first host.2. The Second host(ecctemp) contains only the ECC 6 UC System.
3. We started our SPAU activities in the ECC 6 UC System after CUUC process completed.
4. Now, with SPDD & SPAU activities getting completed. I want the 2 Transports to be used for rest of the Upgrades.
How do I go about this?
1. I cannot run 'SELECT FOR TRANSPORT' or run the commands as per 68678 in the ECC 6 NUC System as thats where I didnot do SPAU.
2. I cannot even run the commands as per 68678 in the host ecctemp, becuase there is no upgrade directory here.

Hi,
You can add SPDD transport on your non-unicode system in umodauto.lst file and take this file to your quality system (also data file and cofile). So, when you will start upgrade on your quality system then upgrade tool will first read this umodauto.lst file and it will prompt you on the screen to has this transport as SPDD transport. And upgrade tool will then import this SPDD request.
For SAPU, you can simply move data file and cofile from your final system to quality system. And once your quality system will be ready after upgrade and UC conversion then you can simple import this transport from STMS. This will solve your issue.
Thanks
Sunny

How to handle delta SPDD & SPAU adjustments in the 2nd Upgrade QA & PRD

Dear all,
We have successfully upgraded our development box and we have made the SPDD changes into a single transport requests and also the SPAU requests in a different requests.
Our ABAP team has made the SPDD adjustments comparing the objects with production and QA.
Now when we upgrade our QA box we have included the SPDD & SPAU transports and now we found that we have about 8 extra objects that needs to be modified manually in SPDD phase? out of 79 objects 71 is adjusted my out SPDD transports and it has left out 8 more objects.
These 8 objects were never shown in SPDD phase of our development box.
Can you please suggest us, like how to handle these delta objects, so that we won't phase the same issue when we move to production. (offcourse we will do 2-3 dry runs before going to production)
I have read the below note, but it is for the older version (without shadow instance)
Note 124522 - Importing a modification adjustment in 2nd upgrade
Thanks &
Regards
Senthil

1.If you have choosen strategy resource-minimized, they are adjusted during downtime before the ABAP Dictionary is activated.
copy the cofiles and datafiles in the respective directories. List all the requests in umodauto.lst.
In PREPARE phase ADJUSTPRP the following screen appears
For automatically maintaining your modification in your ystem during the upgrade transport request from earlier upgrades are searched in the umoauto.lst in directory /usr/sap/trans/bin..
The file could not be read
There are several reason why this may be correct
eg: 'this is your first upgrade' or 'your system is not modified'.
Did you expect a list of transports being found?
->Confirm a list of transports to be included in the upgrade
Select Yes & OK
Click on Yes to include the transport
Click Yes to stop the ACT_700 phase and check the results of SPDD
2.You can add additional requests to umodauto.lst
3. Regarding why its how in QA.? Reasons could be
1modification could have been done only in QA
2)Are the DEV and QA are on the same kernel & SP level's

SPDD issue

Similar Messages

Maybe you are looking for