SPDD transaction

Hi friends,
       i have adjusted data elements option in spdd.While adjusting data element icon nas changed to (adjustment in complete or needs confirmation).can anyone suggest how to complete adjustment.
Regards
sekar

SPDD transaction code flow  
http://help.sap.com/saphelp_nw04/helpdata/en/2e/6d66617d9011d396b60000e82de14a/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/2e/6d66587d9011d396b60000e82de14a/frameset.htm
Regards

Similar Messages

  • Difference between SAPU and SPDD Transactions ?

    Hi
    What is the difference between SAPU and SPDD Transactions ?
    Thanks In advance
    Sri.

    Hi,
    SPDD Deals with Data Dictionary objects and
    SPAU Deals with Progams.
    Check the link for more information
    http://www.saptechies.com/spau-and-spdd/
    Hope this info will help you.
    Rewards points if useful.
    With Regards,
    K K V

  • 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

  • Doubt in SPDD Transaction

    Hi All,
    When I click on the yellow traffic light corresponding to a paticular dictionary object in the SPDD Tcode, I am getting a screen where I need to accept proposal or Do not accept Proposal.
    I am confused as to what I should be doing here .
    Please could someone guide me as to how I should proceed .
    Regards,
    Sushanth H.S.

    Hi
    There are 2 tables(open and Closed Items)  in FI for Account Payables and Account Receivables and GL accounts
    1.Account payables: BSIK is Open Items and BSAK is Closed items
    2.Account Receivables; BSID and BSAD for OPEN and closed items
    3/GL accounts :  BSIS and BSAS  for Open and Closed Items
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • Regd SPAU and SPDD!!!

    Hi,
    I am involving in technical upgradation. I am getting the list of programs from my onsite persons and just correcting the programs and sending them the modified ones. But I want to know where exactly SPAU and SPDD transaction codes comes into picture. I never check these two tcodes while modifications. I have modified lot of pgms as of now. But I want to know about these transaction codes. Can any one tell me how and when can I use these two tcodes?
    Thanks in advance.

    Hi Ramesh,
    When you modify any SAP Standard object it get a modification tag marked to it.
    This modification tag is considered while you are upgrading and the complete list of modified objects is identified by SAP into 2 parts.
    1. Data dictonary objects
    2. ABAP Program (includes Executable programs, Includes, FM, etc..)
    1. SPDD - Data dictonary objects are displayed in DDIC. This is done by BASIS guys while installations only.
    Reason: If the dictonay structure is not updated before you execute the programs they might give you a run-time dump.
    2. SPAU - Programs are later listed seperately. These objects are to be checked and adjusted later after the installation of the upgrade version is complete.
    Hope this explanation is enough for you. If you want some specific info do let me know.
    Regards,
    Kunjal

  • Please explain we what SPDD and SPAU are??

    Can somebody elaborate me on what SPDD and SPAU transactions are??

    hi rahul,
    During an upgrade or the import of an Support Package, existing objects of the SAP standard are overwritten with the objects redelivered. To help the customer retain the objects modified in a previous release, SAP provides all modified objects which are redelivered (in an upgrade or Support Package) in the upgrade adjustment of transactions SPAU and SPDD. These transactions allow customers to enter their modifications into the corresponding new objects being delivered at upgrade. The Modification Assistant supports this process of adopting customer modifications.
    In the past, all objects modified by a customer and delivered again by SAP, an IBU or an SAP partner, had to be manually re-modified during an upgrade. Now, modifications are either automatically adopted or the system provides you with an assistant for adjusting your modifications to the newly upgraded configuration.
    In general, objects altered using the Modification Assistant can now be automatically accepted into the upgraded system if the modifications undertaken in the original version do not directly overlap those made in the customer version. If collisions occur between the two versions at upgrade (naming collisions, or if SAP has deleted an object modified by a customer), the system offers support during the upgrade, which means that a semi-automatic adjustment is made. In some cases, however, you may still have to manually adjust objects using ABAP Workbench tools.
    Objects modified according to the old system used prior to the advent of the Modification Assistant must be manually maintained after an upgrade has been run.
    Use transactions SPDD and SPAU during an upgrade to select these objects and modify them manually.
    Transaction SPDD allows you to adjust modifications to ABAP Dictionary objects during an upgrade.
    Transaction SPDD
    Transaction SPAU allows you to adjust programs, function modules, screens, interfaces, documentation, and text elements after an upgrade.
    plz reward if useful..

  • SPAU - SPDD

    Hi Experts,
    I'm in the middle of an upgrade from ECC 5.0 to ECC 6.0 SR2, and I have some doubts regarding SPAU and SPDD transactions, I have already read the guides but I can find the answer that clear for this: Should I run it before the UPGRADE or is it only AFTER the upgrade is complete ??? Is there any note that answers that so its official I dont have to run it but after the upgrade is complete?
    Best Regards,
    RT

    Hi,
    Transaction SPDD allows you to adjust modifications to ABAP Dictionary objects during an upgrade.
    Transaction SPAU allows you to adjust programs, function modules, screens, interfaces, documentation, and text elements after an upgrade.
    During SAPUp, a phase comes in ACT_700 which suggests that you must now include your repository modifications in the new SAP import.
    It will tell the number of modified objects found to be adjusted and how many have been adjusted automatically.
    Then it will ask if you want to make adjustments to ABAP dictionary Objects?
    Do not continue.
    Adjust your repostory.
    Please proceed as follows - Logon to the shadow instance as user DDIC in client 000.Server: 64r3dev  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.
    After adjustments, continue with the upgrade.
    During SPAUINFO phase, you will get following message.
    Besides the adjustments in transaction SPAU your upgrade is completed now and productive operation is possible.All SPAU activities can be performed without SSCR for a period of 14 days after you first entered this phase.Do  n o t  continue with SAPup if you plan to use the result of the adjustments for any subsequent SAP system.
    Exit now and restart SAPup, after SPAU has been finished.
    This is all about the SPDD and SPAU.
    For more information, on SPDD and SPAU,
    use the following link.
    https://wiki.sdn.sap.com/wiki/display/HOME/ERP2005+Upgrade
    Reward if helpfull
    Regards,
    Imran

  • 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

  • Adjustment in SPDD?

    Hi Friends,
    We have upgraded SAP 4.6 to ECC 6.0.
    In SPDD transaction there are two objects to adjust now.
    The objects are.
    => without Modifiction Assistant
                  -> Structures
                        -> /SAPDMC/LSSCREEN
                             * Structure Fields                        OHLIGER
                  -> Domains
                            * /SAPDMC/LS_FILENAME             KUNZT
    Here the objects are displaying in Yellow color light.
    When i clicked on first one its showing the fileds and Accept Proposal, Edit Proposal buttons.
    when i clicked on Accept Proposal, Its showing a dialog box like
    Append for table /SAPDMC/LSSCREEN
    Name of append ZALSSCREEN
    And i clicked Continue. Then its showing one mesg like Structure /SAPDMC/LSSCREEN cannot be enhanced(creating new fields is not possible)
    I am getting confusion.
    Even i saw the difference in 4.6 and ECC 6.0.
    In 4.6c this structure contains more fileds. In ECC 6.0 they removed some fields in this structure.
    In 4.6 it caontains 182 fields. In ECC 6.0 it contains 150 fields.
    Now when i clicked on Accept Proposal, the removed fields are appending into ECC 6.0 under ZALSSCREEN structure in table /SAPDMC/LSSCREEN.
    I want just reset to original. I.e ECC 6.0 structure.
    How to set to original. plz any helps will be appreciate.
    Regards,
    Shankar.

    Hi,
    as you said in 4.6c they have appened a structure to the standard, right.
    now defently this should also be appended to the new version.right.
    you are telling that you dont want appeneded structure.
    just reset it to original.
    even if you are facing problem while doing the same, refresh it and do it again. it will solve.
    but adopt modifications is the right one for this.
    they might be using the appened z structure some where, if it is not reflecting in new version, it would be a problem, right.
    ALL THE BEST.
    Thank U,
    Jay....

  • What to do with Deleted objects in SPDD

    Hi ,
    I am shashidar Motoori.  Currently working in an upgradation project  from 4.6 C to Ecc 6. 
    I am an ABAP developer.  When I run SPDD transaction I saw some objects are in " Deleted Objects".  What to do with these objects.  .Please help me in this

    Hi Shashidar.
    You can go for more information to the follow Sap note:
    [Note 510138 - SPDD/SPAU - Processing of deleted DDIC objects|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=510138]
    Best Regards.

  • Step by step procedure for Upgrade to ECC6.0

    Hi,
    I gained a lot from this forum . Can someone please mail me at
    [email protected]
    step by step procedure for upgrade .
    Will award full points for helpful documents..
    With regards,
    Mrinal

    SAP defined a roadmap for upgrade.
    1) Project Preparation
    Analyze the actual situation
    Define the objectives
    Create the project plan
    Carry out organizational preparation for example identify the project team
    2)Upgrade Blueprint
    The system and components affected
    The mapped business processes
    The requirements regarding business data
    3)Upgrade Realization -- In this phase the solution described in the design phase is implemented in a test environment. This creates a pilot system landscape, in which the processes and all their interfaces can be mapped individually and tested on the functional basis.
    4)Final Preparation for Cutover -- Testing, Training, Minimizing upgrade risks, Detailed upgrade planning
    5)Production Cutover and Support
    The production solution upgrade
    Startup of the solutions in the new release
    Post processing activities
    Solving typical problems during the initial operation phase.
    SAP expects at least 2 to 3 months for Upgrade and that again depends on project scope and complexity and various other factors.
    STEPS IN TECHNICAL UPGRADE
    •     Basis Team will do the prepare activities. (UNIX, BASIS, DBA).
    •     Developer need to run the Transaction SPDD which provides the details of SAP Standard Dictionary objects that have been modified by the client. Users need to take a decision to keep the changes or revert back to the SAP Standard Structure. More often decision is to keep the change. This is mandatory activity in upgrade and avoids data loses in new system.
    •     After completing SPDD transaction, we need to run SPAU Transaction to get the list of Standard SAP programs that have been modified.  This activity can be done in phases even after the upgrade. Generally this will be done in same go so that your testing results are consistent and have more confident in upgrade.
    •     Run SPUMG Transaction for Unicode Conversion in non-Unicode system. SPUM4 in 4.6c.
    •     Then we need to move Z/Y Objects.  Need to do Extended programming check, SQL trace, Unit testing, Integration testing, Final testing, Regression Testing, Acceptance Testing etc.,
    The main Category of Objects that needs to be Upgraded is –
    •     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
    Also refer to the links -
    http://service.sap.com
    http://solutionbrowser.erp.sap.fmpmedia.com/
    http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
    http://www.id.unizh.ch/dl/sw/sap/upgrade/Master_Guide_Enh_Package_2005_1.pdf
    Hope this helps you.

  • Regarding 4.6c to ECC 6.0

    Hi,
    We are starting the upgradition from 4.6C to ECC6.0,as a ABAP er what changes i need to do could you explain me with transaction codes
    what is unicode and what is the neccessity of unicode for upgradtion
    Regards
    Raghava

    Hi,
    When an upgrade has been carried on a system, large number of data dictionary & repository objects get affected in the newer version.
    1. You have to start with identifying the objects which have undergone a change. So run the transaction SPDD which provides the details of SAP Standard Dictionary objects that have been modified by the client. Users need to take a decision to keep the changes or revert back to the SAP Standard Structure. More often decision is to keep the change. This is mandatory activity in upgrade and avoids data loses in new system. Following links contains necesary documentation on SPDD.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/2e/6d66617d9011d396b60000e82de14a/content.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/2e/6d66647d9011d396b60000e82de14a/content.htm
    2. After completing SPDD transaction, we need to run SPAU Transaction to get the list of Standard SAP programs that have been modified. This activity can be done in phases even after the upgrade. Generally this will be done in same go so that your testing results are consistent and have more confident in upgrade.
    Check the below link. It elaborates on adjusting repository objects.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/c8/61ec66e33611d1954b0000e82de14a/content.htm
    3. Also check whether the custom programs have been copied properly. Remove any obsolete statements. Also replace the obsolete function modules. Function modules like WS_UPLOAD & DOWNLOAD have become obsolete in ECC 6.0.
    4. In case of BDC, compare the screen with the older version. There is a possibility that few fields would have missed out. You may have to do some tweking in the program too. Same is the case with sap scripts.
    5. Also make sure that the objects are unicode compatible.
    Check out the below links for a detailed explanation in Unicode.
    http://help.sap.com/saphelp_nw04/helpdata/en/62/3f2cadb35311d5993800508b6b8b11/content.htm
    http://www.sapdb.org/7.4/htmhelp/db/74d038d35e11d5994400508b6b8b11/content.htm
    Hope this helps you.
    (If your question is answered, please mark the thread as answered)
    Regards
    Sayee

  • What are the consultant roles in Upgradation or migration project

    Hello ,
    Would you please any dody help me to provide the role & responsibilities of consultant in SAP upgradation or migration project.Thanks.
    Regards,
    Sampally

    Dear Sampally,
    SAP defined a roadmap for upgrade.
    1) Project Preparation
    Analyze the actual situation
    Define the objectives
    Create the project plan
    Carry out organizational preparation for example identify the project team
    2)Upgrade Blueprint
    The system and components affected
    The mapped business processes
    The requirements regarding business data
    3)Upgrade Realization -- In this phase the solution described in the design phase is implemented in a test environment. This creates a pilot system landscape, in which the processes and all their interfaces can be mapped individually and tested on the functional basis.
    4)Final Preparation for Cutover -- Testing, Training, Minimizing upgrade risks, Detailed upgrade planning
    5)Production Cutover and Support
    The production solution upgrade
    Startup of the solutions in the new release
    Post processing activities
    Solving typical problems during the initial operation phase.
    SAP expects at least 2 to 3 months for Upgrade and that again depends on project scope and complexity and various other factors.
    STEPS IN TECHNICAL UPGRADE
    • Basis Team will do the prepare activities. (UNIX, BASIS, DBA).
    • Developer need to run the Transaction SPDD which provides the details of SAP Standard Dictionary objects that have been modified by the client. Users need to take a decision to keep the changes or revert back to the SAP Standard Structure. More often decision is to keep the change. This is mandatory activity in upgrade and avoids data loses in new system.
    • After completing SPDD transaction, we need to run SPAU Transaction to get the list of Standard SAP programs that have been modified. This activity can be done in phases even after the upgrade. Generally this will be done in same go so that your testing results are consistent and have more confident in upgrade.
    • Run SPUMG Transaction for Unicode Conversion in non-Unicode system. SPUM4 in 4.6c.
    • Then we need to move Z/Y Objects. Need to do Extended programming check, SQL trace, Unit testing, Integration testing, Final testing, Regression Testing, Acceptance Testing etc.,
    The main Category of Objects that needs to be Upgraded is –
    • 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
    Also refer to the links -
    http://service.sap.com
    http://solutionbrowser.erp.sap.fmpmedia.com/
    http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
    http://www.id.unizh.ch/dl/sw/sap/upgrade/Master_Guide_Enh_Package_2005_1.pdf
    Hope this helps you. Please let me know in case of any specific queries.
    Regards,
    Rakesh

  • ECC 5.0 to ECC 6.0 upgrade - role of anABAper

    Hi all,
    Im an ABAper previously worked on SRM and R/3 modules MM and PP.Now i will be working on an upgrade project for ECC 5.0 to ECC 6.0.
    As an ABAPER what should I know to work on an upgrade project?What are the different Technical things I should know.
    I have previosuly worked on BADi's and reports.

    Hi Ram,
    Initially it is teh SPDD and SPAU phase.
    SPDD  contains the list of all modified standard Data Dictionary objects, like tables, search helps, dataelements, domains,view etc.  You have to go to SPDD transaction, click on execute, you get teh following list :
    With Modification Assistant
    Without Modification Assistant
    Deleted Objects
    Expand them.
    click on each object and press on 'Version' in the tool bar, and in the next screen select the current version and previous  version. you can see few differences between the two versions. Now you have analyse and take a call on whethere you have to 'RESET TO ORIGINAL' or 'ADOPT MODIFICATIONS'
    SPAU will contain the modified standard repository objects.
    Go to SPAU transaction as repeat as mentioned above.
    You have to analyse each oject well and then decide which of the two you would choose 'RESET TO ORIGINAL' or 'ADOPT MODIFICATIONS'
    Here you can find more info :
    http://wiki.sdn.sap.com/wiki/display/ERP6/SPAU+Corrections
    You can search in Google or SDN for many links on the topic.
    http://lmgtfy.com/?q=spdd+sdn
    You can find few  documents here
    You might also find this helpful
    http://www.sapdb.info/sap-ecc6-upgrade/

  • Upgrade from 46c to ECC

    Hi,
    Can you please explain me the complete procedure to be followed and precautions to be taken for upgrading SPAU(program,func groups,data elements,tables,structures, etc) objects, SPDD objects and custom objects(programs,func grps etc..) from 4.6c to ECC version.
    Thanks,
    Laks.

    Hi ,
            The Precautions are .
    1 .SPDD transaction should be executed 14 days before the upgrade .
    2 .SPAU transcation should be executed after the Upgrade.
    3 .Maximum error in SPAU can be resolved using Basis and Function Consultant support .
    4 Maximum errors are in BDC,Sapscript ,Userexits which deal with standrad transaction .
    5 .Also take care about The Unicode errors.
    6 .For Unicode Use Transaction UCCHECK and SCOV.
    Please reward if useful .

Maybe you are looking for