Post Upgrade Step "Adjust custom development"

Hello all:
Based on your BI 3.x to 7.0 upgrade experience, I wanted some insight on the post upgrade step "Adjust custom development per note 857904". Can you please share how you handled this, any details of activities done here...any tips?
Thanks,
Pravin

Hi Pravin,
Hope this helps you - 
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881 - you can use this checklist for 2004s too!
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0d7c290-0201-0010-bbaa-d8f8af341796
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a1a0eb43-0b01-0010-23aa-908cc4eaabcd
Bye...

Similar Messages

  • ASU-process POST Upgrade Step on SQL database

    Hi All,
    To check this message in the right format kindly click on reply first then click on quote original icon ("").
    I am performing an upgrade from R/3 4.7 to ERP 6.0 SR3, while doing upgrade sapup asking me To perform the manual application specific post upgrade step.
    This phase says to run ASU toolbox by using tx /n/asu/upgrade. when i run this tx is show the below list of steps to be performed with showing severity level of some as optional and many as obligatory.
    Task List                                                                                Severity     SAP R/3 release frm     SAP R/3 release to
    IS-OIL Application Test 600                                                 Optional          
    KP06xx: Termination SYNTAX_ERROR                                                 Obligatory     470                           500
    CGPL: Entries are blank after upgrade                                                Obligatory          
    Error handling of task group execution                                Optional          
    Mobile device cannot confirm TO after release upgrade     Obligatory     470                         600
    Mobile device doesn't find transfer orders after upgrade     Obligatory     470                          600
    Grantee Management - Upgrade from EA-PS 2.00 to ECC 600     Obligatory          
    Convert customizing for warehouse funds ctr scenarios     Optional          
    Various problems classification commitment items (class type     Obligatory          
    Unauthorized error messages udring fiscal year change/reassi     Obligatory          
    RFFMUDX1 migrates incomplete budgeting tables                          Obligatory          
    Non-7bit-ASCII character used for BCS key figures             Obligatory          
    Changes in TKEDR for /ISDFPS/RFFMDISTDERIVALE          Obligatory          
    BCS - Tool for Deleting Obsolete Derivation Strategies     Obligatory          
    BCS Syntax Error on Upgrade from EA-PS 2.00 to ECC 600     Obligatory          
    Migration to ERP 6.0 (EA-PS 6.00)                                         Obligatory          
    Migration EA-PS 2.00 to ERP 5.0 (EA-PS 5.00)                      Obligatory          
    Missing initialization of new fields in table ANLZ                  Obligatory     46C                       470
    Activating VMC for the Internet Pricing and Configurator     Obligatory          
    Customer specific BSEG-fields not transferred                  Optional          
    Conversion of report headers in drilldown-reporting            Optional                                   600
    IBase: Upgrade to Release 4.6C and higher                         Optional     46C                         600
    ZSAPRCKML_COGS: Upgrade to release 4.7 or higher     Optional     46C                      470
    Conversion of CO-Total-Tables                                              Obligatory     46C                      500
    Conversion of CO-line-item table COEP                                Obligatory     46C                       600
    New General Ledger, problems in CO-documents                 Obligatory                               500
    No receivers found in allocations                                          Obligatory     46C                        470
    Conversion Of New Process Parameter Long Texts For Search     Optional     110                       600
    Migration of process parameters in recipe management     Optional     110                        600
    FAQ new depreciation calculation                                        Optional                                600
    Upgrading to SAP R/3 47x200 and SAP ECC 500 with RMGMT     Obligatory     100                       500
    Reloading Table T512W                                                        Optional          
    Converting Short Texts                                                         Obligatory          
    Migrating Data                                                                         Optional     4.7     
    Activating SAP ECC Extensions                                          Optional          
    I am not sure about which steps I have to perform, I am a bit confused.. because some are optional and some are not relevant to my release (as target or source release is different from mine). and also few things are not applied in my envirnoment hence those steps are also not relevant.
    Please suggest me, how to proceed and what to do. please guide if i skip this step now and later  on I apply latest SP than still I need to do all this.
    Regards
    Vinay

    Hi All,
    I also faced a similar issue during upgrade. Some useful findings.
    1. Only super user can access this /n/ASU/START
    2. All the obligatory executable tasks are automatically performed by the system automatically during upgrade.      SAPADM. Only errors (if any) are to be corrected.
    3. Some of the tasks are only to go through some SAP notes as a precaution before upgrade.
    4.  Execute all the checks /n/ASU/UPGRADE
    5. This surely can be skipped, but not advisable.
    regards,
    Amit

  • Upgrade step ASU-process post upgrade step

    Hi All,
    To check this message in the right format kindly click on reply first then click on quote original icon ("").
    I am performing an upgrade from R/3 4.7 to ERP 6.0 SR3, while doing upgrade sapup asking me To perform the manual application specific post upgrade step.
    This phase says to run ASU toolbox by using tx /n/asu/upgrade. when i run this tx is show the below list of steps to be performed with showing severity level of some as optional and many as obligatory.
    Task List                                                                                Severity     SAP R/3 release frm     SAP R/3 release to
    IS-OIL Application Test 600                                                 Optional          
    KP06xx: Termination SYNTAX_ERROR                                                 Obligatory     470                           500
    CGPL: Entries are blank after upgrade                                                Obligatory          
    Error handling of task group execution                                Optional          
    Mobile device cannot confirm TO after release upgrade     Obligatory     470                         600
    Mobile device doesn't find transfer orders after upgrade     Obligatory     470                          600
    Grantee Management - Upgrade from EA-PS 2.00 to ECC 600     Obligatory          
    Convert customizing for warehouse funds ctr scenarios     Optional          
    Various problems classification commitment items (class type     Obligatory          
    Unauthorized error messages udring fiscal year change/reassi     Obligatory          
    RFFMUDX1 migrates incomplete budgeting tables                          Obligatory          
    Non-7bit-ASCII character used for BCS key figures             Obligatory          
    Changes in TKEDR for /ISDFPS/RFFMDISTDERIVALE          Obligatory          
    BCS - Tool for Deleting Obsolete Derivation Strategies     Obligatory          
    BCS Syntax Error on Upgrade from EA-PS 2.00 to ECC 600     Obligatory          
    Migration to ERP 6.0 (EA-PS 6.00)                                         Obligatory          
    Migration EA-PS 2.00 to ERP 5.0 (EA-PS 5.00)                      Obligatory          
    Missing initialization of new fields in table ANLZ                  Obligatory     46C                       470
    Activating VMC for the Internet Pricing and Configurator     Obligatory          
    Customer specific BSEG-fields not transferred                  Optional          
    Conversion of report headers in drilldown-reporting            Optional                                   600
    IBase: Upgrade to Release 4.6C and higher                         Optional     46C                         600
    ZSAPRCKML_COGS: Upgrade to release 4.7 or higher     Optional     46C                      470
    Conversion of CO-Total-Tables                                              Obligatory     46C                      500
    Conversion of CO-line-item table COEP                                Obligatory     46C                       600
    New General Ledger, problems in CO-documents                 Obligatory                               500
    No receivers found in allocations                                          Obligatory     46C                        470
    Conversion Of New Process Parameter Long Texts For Search     Optional     110                       600
    Migration of process parameters in recipe management     Optional     110                        600
    FAQ new depreciation calculation                                        Optional                                600
    Upgrading to SAP R/3 47x200 and SAP ECC 500 with RMGMT     Obligatory     100                       500
    Reloading Table T512W                                                        Optional          
    Converting Short Texts                                                         Obligatory          
    Migrating Data                                                                         Optional     4.7     
    Activating SAP ECC Extensions                                          Optional          
    I am not sure about which steps I have to perform, I am a bit confused.. because some are optional and some are not relevant to my release (as target or source release is different from mine). and also few things are not applied in my envirnoment hence those steps are also not relevant.
    Please suggest me, how to proceed and what to do. please guide if i skip this step now and later  on I apply latest SP than still I need to do all this.
    Regards
    Vinay
    Edited by: Vinay Paul on Sep 11, 2009 10:11 PM

    Hi All,
    I also faced a similar issue during upgrade. Some useful findings.
    1. Only super user can access this /n/ASU/START
    2. All the obligatory executable tasks are automatically performed by the system automatically during upgrade.      SAPADM. Only errors (if any) are to be corrected.
    3. Some of the tasks are only to go through some SAP notes as a precaution before upgrade.
    4.  Execute all the checks /n/ASU/UPGRADE
    5. This surely can be skipped, but not advisable.
    regards,
    Amit

  • Post upgrade step for EP

    HI Friends,
    I have upgraded my EP from 6.0 to 7.0 successful with all component. ALos i am getting login screen. SO what are post upgrade step for EP.
    Thanks,
    Regards,
    Sachin

    HI ,
    System restart
    run the SICK verify the installation check
    Check developer traces on the operating system. Log on to
    Check the installed license and profile configuration (RZ10 and PFCG)
    confirm the  operation modes
    Perform a client copy
    Check the status of the SAP Web AS Java and the user SAPJSF
    Check the rdisp/j2ee_start profile parameter
    Check the current state of SAP Web AS Java using transaction SMICM
    SAP Load Generator
    Start SAP Load Generator (SGEN)
    Regards,

  • Error on Oracle 11gR2 RAC database Post upgrade step

    [Upgrade the Oracle Clusterware Configuration|http://docs.oracle.com/cd/E11882_01/server.112/e23633/afterup.htm] Problem Description:
    O.S Version: HP-UX B.11.31 U ia64
    It is upgrading of Oracle RAC 2 node database from 11.1.0.7.0 to 11.2.0.3.0
    I receive following error while perfoming the post upgrade step
    indba1 racdb> srvctl upgrade database -d racdb -o /app/oracle/product/11.2.0.3/db
    PRCD-1231 : Failed to upgrade configuration of database racdb to version 11.2.0.3.0 in new Oracle home /app/oracle/product/11.2.0.3/db
    PRKC-1136 : Unable to find version for database with name racdb
    Actually I am performing the step "Upgrade the Oracle Clusterware Configuration" whill getting the error.
    When I tried on below;
    indba1 racdbp> srvctl upgrade database -d racdb -o /app/oracle/product/11.2.0.3/db
    PRCD-1231 : Failed to upgrade configuration of database racdb to version 11.2.0.3.0 in new Oracle home /app/oracle/product/11.2.0.3/db
    PRKC-1136 : Unable to find version for database with name racdb

    Output from Oracle 11.1.0.7 Home:
    oracle@indba1:/app/oracle/product/11g/db_1 $ srvctl config database -d racdb
    PRKR-1001 : cluster database racdb does not exist
    PRKO-2005 : Application error: Failure in getting Cluster Database Configuration for: racdb
    Output from Oracle 11.2.0.3 Home:
    oracle@usfsdba1:/app/oracle/product/11.2.0.3/db $ srvctl config database -d racdb
    PRKR-1001 : cluster database racdb does not exist
    PRKO-2005 : Application error: Failure in getting Cluster Database Configuration for: racdb

  • Upgrading Oracle Text - Post upgrade step 10.2 to 11.2

    I already upgraded my 10.2.0.4 database to 11.2.0.1 and have to do post upgrade steps. In step 39 of Manual guideline (837570.1) is not clear for me. If some one can explain further would be appriciated. When i check my source ORACLE_HOME/ctx/admin/ctxf102.txt or ctxf102.sql
    Step 39
    Upgrading Oracle Text
    Copy the following files from the previous Oracle home to the new Oracle home:
    * Stemming user-dictionary files
    * User-modified KOREAN_MORPH_LEXER dictionary files
    * USER_FILTER executables
    To obtain a list of the above files, use:
    $ORACLE_HOME/ctx/admin/ctxf<version>.txt
    $ORACLE_HOME/ctx/admin/ctxf<version>.sql
    where version is 920,101,102
    For instance, if upgrading from 10.2.0
    *1. For dictionary files check*
    *$ORACLE_HOME/ctx/admin/ctxf102.txt*
    *2. Execute the script as database user SYS,SYSTEM, or CTXSYS*
    *$ORACLE_HOME/ctx/admin/ctxf102.sql*
    If your Oracle Text index uses KOREAN_LEXER which was deprecated in Oracle 9i and desupported in Oracle 10g Release 2, see below Note for further information on manual migration from KOREAN_LEXER to KOREAN_MORPH_LEXER.
    Note 300172.1 Obsolescence of KOREAN_LEXER Lexer Type

    Hi Srini
    Thank you very much. now i got it.
    Oracle asked me to identify the CTXCAT indexes with KOREAN_LEXER execute the following query as user CTXSYS: if nothing return then i can skip this step.
    SELECT idx_name
    FROM ctxsys.ctx_indexes
    WHERE idx_type = 'CTXCAT'
    AND idx_name IN
    (SELECT ixo_index_name
    FROM ctxsys.ctx_index_objects
    WHERE ixo_class = 'LEXER'
    AND ixo_object = 'KOREAN_MORPH_LEXER ');
    SELECT isl_index_owner,isl_index_name,isl_language
    FROM CTXSYS.ctx_index_sub_lexers
    WHERE isl_object = 'KOREAN_MORPH_LEXER';

  • Post upgrade step

    please tell me post upgrade step of R12.1.3
    we restore backup of r12.1.3
    please tell us post upgrade step
    on rhel 5.4
    Edited by: user9376205 on May 11, 2011 12:06 AM

    please tell me post upgrade step of R12.1.3What post upgrade steps you are referring to?
    All the steps are documented in MOS doc.
    Oracle E-Business Suite Release 12.1.3 Now Available
    http://blogs.oracle.com/stevenChan/2010/08/ebs_1213_available.html
    we restore backup of r12.1.3
    please tell us post upgrade stepIf you restore the files, why you need post upgrade steps?
    Thanks,
    Hussein

  • Post-upgrade?

    Do i have to do post upgrade steps using DBUA or it will be done by the utility.
    Thanxs in advance

    I don't think you need to. The post-upgrade scripts are only required when choosing to do the upgrade manually.

  • Upgrading PeopleSoft and Risks with Custom Development

    My company's parent is on PS 8.8, and is trying to bring my company into their system. To do this, they are going to have to do a lot of custom development surrounding labor-based project costing.
    From some of the PeopleSoft developers, I am hearing that it is risky to develop on this older platform, and then upgrade to version 9.1, because some of the customization will not carry over well and will need to be re-written. Their boss insists that this is an exaggeration, and it should not be a concern.
    Can someone please tell me what the pitfalls are of doing heavy custom development on an older version with plans to upgrade in the immediate future?
    Thank you so much.

    Hi Alexandra,
    I'll give you the details of attaching an application log to BPEM which are (Let say) gnerated by a Transaction.
    Step 1: Define Business Process Area
    Step 2: Define Business process code
    step 3: Define Transaction attached to this Business Process Code
    Step 4: Run transaction EMMA to view it.
    I can write all the customizing for this here also however i would recommond a link which contains the cookbook of implementing BPEM.
    Go to :
    SAP service market place->sap for utilities->product information->Business Process Exception Management->cookbook & Guidelines->BPEM Cookook
    <https://websmp101.sap-ag.de/solutions>
    In this document go to the Section 4 (Customizing) here you can see all the steps in detail with example to set up the system for attaching an Application log with BPEM.
    In case if you face some problem, revert.
    Please assign the point.
    Amit

  • Post Processing Steps after Support Package Stack Application

    I'm curious if anyone has any guidelines for post processing steps (or pre-processing) when applying Support Package Stacks to their Development Infrastructure (Developmend Workplace and the Central NWDI Server).  We have just upgraded a couple of developers local engines and developer studio to SP stack 19 from SP stack 14 and are experiencing some problems.  We also applied the J2EE stack and appropriate SCA files to the NWDI server.
    After the support packs it looks like our DTR files are gone (when reimporting configuration via Developer Studio the SC's are there but there are no DC's inside of them).  Additionally, it looks like we have to manually reimport the newest versions of SAP_BUILDT, SAP_JTECHS, and SAP-JEE.  Another thing is that old Local Web Dynpro DC's are now complaining about class path problems and different versions of files.  We followed the documentation for applying SP19 exactly as the documentation says for a Java Development Usage type.  Is there a checklist or something that anyone has for steps to perform after the application of the support packs?

    I think I'm missing something.  Now I see the code and DC's inside the DTR.  However, when I try to import into NWDS no DC's come in (the software components exist, but no DC's in them).  Additionally, the CBS web ui reports that my software components do not contain any DC's even though I see them in the DTR.  What things can I look at to determine what I'm missing here?
    Thought I'd add some more info..after applying the support packs, we imported the new SAPBUILD, SAP_JTECH, and SAP_jee SCA'S into our track as we required some functionality from the newer build SCA.  We also reimported our old archives back into the system by manually checking them in assuming this would fix the problem with us not seeing the source in the NWDS or the DTR.  After the import, the CBS no longer sees our custom DC's, but the DTR does (both in active and inactive ws).  When importing the dev configuration into the NWDS our custom DC's no longer appear, but SAP's standard SCA's do.
    Message was edited by:
            Eric Vota

  • What are the post instalation steps?

    hi,
    i am fresher in SAP.anybody plz send me postinstalation steps.
    regards,
    jana

    Hi All,
    Rewards if useful.
    Post Installation Steps For ECC 5.0
    What are the post installation steps after I have installed the Central Instance and Database instance?
    Initial Consistency Check
    SM28
    1.      Logon to the newly refreshed SAP system and run transaction SM28
    2.      Ensure that no errors are reported.  Otherwise, take the necessary steps to correct the problems.
    Edit Batch Jobs
    1.      Set the fields as follows
    Job name: RDDIMPDP*
    User name: *
    Job Status: Released and Ready checked off, all others unchecked
    Fr:  01/01/0001
    To:  12/31/9999
    Or after event: *
    2.      Press <F8> to execute the query
    3.      Highlight the first job in the list and press the <CTRL>+<F11> to change the job.
    4.      Examine the Exec Target field.
    a.      If the box is empty, press <F3> to exit
    b.      If the box is not empty, then clear out the contents so the field is blank and press <CTRL>+<S> to save
    5.      Repeat Steps 3 and 4 for each additonal job listed.
    Workbench Organizer Reconfiguration
    1.      Logon on to client 000 of the newly refreshed system with DDIC.
    SE06
    1.      Select the Database Copy or migration option
    2.      Press the Post-installation Processing button.
    3.      When prompted Do you want to re-install the CTS?, press the Yes button
    4.      When prompted for the Source System of Database Copy?, make sure that the <SID> of the production system is selected.  Press the checkmark button to continue.
    5.      When prompted Change originals from PRD to QUA?, press the Yes button
    6.      When prompted Delete TMS Configuration?, press the Yes button
    7.      When prompted Delete old TMS configuration?, press the Yes button
    8.      When prompted Delete Old Versions of transport routes?, press the No button
    TMS Configuration
    1.      Logon on to client 000 of the newly refreshed system.
    STMS
    1.      Upon starting STMS, a windows with the title TMS: Include System in Transport Domain should be displayed
    2.      The information on this screen is automatically filled out from information provided during the SAP installation and should be correct.  If it correct, then enter a description for the system and press <CTRL>+S to save.  Otherwise, press the Other configuration button  and manually configure.
    3.      From the Overview menu, select Transport Routes
    4.      From the Configuration menu, select Adjust with Controller
    5.      Press the Yes button when prompted if you want copy the transport routes from the controller.
    Import Printers
    1.      Logon on to the production client of the newly refreshed system. 
    STMS
    2.      Press <F5> to go to the import Overview.
    3.      Double click on the <SID> of the newly refresh system
    4.      From the Extras menu select Other Requests, then Add.
    5.      In the Transp. Request box, enter the transport number containing the printer definitions that was exported.  Press <Enter> to save.
    6.      Select the transport that was just added to the queue and press <CTRL>+<F11> to start the import.
    7.      In the Target client box, enter the productive client of the newly created system.  Press <Enter> to save.
    8.      Press the <Yes> button to start the transport.
    Client Configuration
    SCC4
    1.      From the Table view menu, select Display -> Change
    2.      When warned that the table is cross-client, press the checkmark button.
    3.      Double click on one of the non-system clients (i.e. not client 000, 001 or 066)
    4.      Define client as follows:
    Client role:  Test
    Changes and transports for client-specific object:  Changes without automatic recording
    Client-independent object changes:  Changes to repository and cross-client customizing allowed
    Protection: Client copier and comparison tool:  Protection level 0
    Restrictions when starting CATT and eCATT:  eCATT and CATT allowed
    5.      Press <CTRL>+S to save.
    6.      Repeat steps 4 through 6 for any additional clients
    Set System Change Option
    SE06
    1.      Press the System Change Option button.
    2.      Set the global setting to Modifiable
    3.      From the Edit menu, select Software Components Modifiable
    4.      From the Edit menu, select Namespaces Modifiable
    5.      Press <CTRL>+S to save.
    Import Users
    STMS
    1.      Press <F5> to go to the Import overview
    2.      Double click on the <SID> of the newly refreshed system.
    3.      Press <F5> to refresh the list of transports
    4.      Locate the transport in the list containing the user exports done before the start of the refresh.
    If the transport is NOT in the list, then from the Extras menu, select Other requests then Add.   Enter the transport number and press <Enter>.  Then press the Yes button to add the transport.
    5.      Highlight the transport and press the Import request icon .
    6.      At the client import screen, enter the target client and then press the Import button
    7.      Press <Enter> to confirm that the import will proceed
    SCC7
    1.      Run the Post Client Import Processing
    2.      The transport number should be the same as that of the transport started in STMS
    3.      Schedule the job to run in the background.  Do NOT schedule it to run immediately.  We need to modify the job before it can be released.
    4.      Press <CTRL>+S to save.
    SM37
    1.      Set the fields as follows
    Job name: CLIENTIMPORT*
    User name: *
    Job Status: All options checked
    Fr:  01/01/0001
    To:  12/31/9999
    Or after event: *
    2.      Highlight the job that was created by SCC7 and press <CTRL>+<F11> to modify the job.
    3.      Press the Step button.
    4.      Select the RSCLXCOP line and press <CTRL><SHIFT><F7> to modify that step.
    5.      In the User box, enter the background user for that particular system (i.e BGDUSER, SAPBATCH, BATCHSAP).
    6.      Press <CTRL>+S to save the changes
    7.      Press <F3> to go back to the main job screen.
    8.      Press the Start condition button.
    9.      Press the Immediate button.
    10.     Press <CTRL>+S to save the changes
    11.     Press <CTRL>+S again to save all the changes to the job.
    12.     Job will start immediately once saved.  Press <F8> to refresh the list of jobs
    13.     Continue to press <F8> every once in a while to update the status of the job.  Do not continue until the job is completed sucessfully.
    SCC4
    1.      From the Table view menu, select Display -> Change
    2.      When warned that the table is cross-client, press the checkmark button.
    3.      Double click on one of the non-system clients (i.e. not client 000, 001 or 066)
    4.      Set the Protection to Protection level 1
    5.      Press <CTRL>+S to save.
    6.      Repeat steps 3 through 5 for any additional clients
    Deleting Source System Profiles
    RZ10
    1.      From the Utilities menu, select Import Profiles then Of Active Servers. 
    (Note:  All application servers of the target system must be started)
    2.      If the Display Profile Check Log screen is displayed, press <F3> to leave this screen.
    3.      Select the Profile field and press <F4> to bring up a list of profiles.
    4.      From the list select one of the profiles associated with the source production system.
    5.      From the Profile menu, select Delete, then All versions, then of a profile.
    6.      When prompted, press the Yes button to delete all version of the profile
    7.      When prompted to delete the file at the operating system level, press the No button.
    8.      Repeat steps 3 through 7 for all additional profiles associated with the source system
    Reconfigure Operation Modes
    RZ04
    1.      From the Operation Mode menu, select Timetable
    2.      Select Normal Operation and press the Change button.
    3.      Highlight 00:00 in the left hand column and press the Delete Assignment button
    4.      If all the assignments are not deleted, then highlight the start time of the outstanding assignment and press the Delete Assignment button.
    5.      Once all the assignments are deleted, press <CTRL>+S to save.
    6.      If warned about an empty timetable, press the checkmark button and then press Yes to save the empty timetable.
    7.      Press <F3> to go back to the main RZ04 screen.
    8.      Right click on one of the listed Operation modes and select Delete
    9.      Press the Yes button to confirm the deletion.
    10.     Repeat steps 8 through 9 for any additional operation modes
    11.     Press <F5> to create a new operation mode.
    12.     Enter a name and short description for the operation mode
    13.     Press <CTRL>+S to save.
    14.     Press <F6> to create a new Instance
    15.     From the Settings menu, select Based on current settings, then New Instances, then Set
    16.     Press <F3> to go back to the main RZ04 screen.
    17.     Press the Yes button to save
    18.     From the Operation Mode menu, select Timetable
    19.     Select Normal Operation and press the Change button.
    20.     Highlight the 00:00 at the top and press <F2>
    21.     Highlight the 00:00 at the bottom and press <F2>
    22.     Press the Assign button.
    23.     Press <F4> to select the operation mode created above.
    24.     Press <CTRL>+S to save.
    Delete Update Failures
    SM13
    1.       Set the fields as follows
    Client:  *
    User: *
    From data: 01/01/0001
    From time: 00:00:00
    2.      Press <Enter> to display the list of outstanding update requests
    3.      If ALL the outstanding update requests have a status of ERR, then it is safe to delete these requests by pressing <F5> to select all records, then selecting the Update Records menu, then Delete.
    4.      Press the Continue button to confirm the deletion.
    Delete Batch Input Sessions
    SM35
    1.      From the Edit menu, select Select All
    2.      Press <Shift>+<F2> to delete all the batch input sessions.
    3.      Press the checkmark button to confirm
    4.      Press the Yes button to start the delete.
    Reorganize Spool
    SPAD
    1.      From the Administration menu select Clean-up Spool
    2.      Check all check boxes and enter 0 for minimum age
    3.      Press the Execute button
    4.      Once complete, press <F3> twice to get back to the main SPAD screen
    5.      From the Administration menu select Check Consistency
    6.      Press the Delete All button.
    SP12
    1.      From the TemSe database menu, select Consistency check
    2.      When the check is complete, press the Delete All button. 
    Delete Invalid Background Control Objects
    SM61
    1.      Press <F8> to switch in to change mode
    2.      Press the Cleanup List button.
    Restrict Outgoing Email and Faxes
    SCOT
    1.      Double click on the green Fax entry
    2.      From the Supported Address Types area, press the Set button that is beside Fax
    3.      In the Address area, ADJUST AS NECESSARY
    4.      Double click on the green SMTP entry
    5.      From the Supported Address Types area, press the Set button that is beside Internet
    6.      In the Address area, ADJUST AS NECESSARY
    Adjust RFC connections.
    SM59
    1.      Expand the TCP/IP connections section
    2.      Double click on the first entry listed
    3.      Check the gateway host and gateway server to make sure it points to the appropriate NON-PRODUCTION system.  
    Make changes as necessary.
    4.      Press the Test Connection button to test the connection
    5.      Press Press <CTRL>+S and then <F3> to save and return to the list of RFCs.
    6.      Repeat steps 1 through 5 for each additional RFC connection
    Convert Logical Systems
    Under no circumstances perform this procedure on a Production system
    BDLS
    1.      When warned to read the documentation, press the checkmark button.
    2.      In the Old logical system name box, press <F4>.
    3.      Select one of the production Logical System names that needs be changed (i.e. WIIPRD400)
    4.      In the New logical system name, enter what that logical system name should be called on this newly refreshed system (i.e.WIITRN400)   Note: Ignore Error/Warning about duplicate system by clicking on the check mark.
    5.      De-select the Test Run and Existence check on new names in tables options
    6.      From the Program menu, select Execute in background
    7.      Press the checkmark button when asked to select a spool device
    8.      Press the Immediate button when asked for the schedule
    9.      Press <Ctrl>+S to save
    10.     Use SM37 to monitor the job
    11.     When job is complete, repeat steps 2 through 10 for any additional logical system names that need to be changed.
    Adjust Logical Systems names
    SALE
    1.      Expand Sending and Receiving Systems, then Logical Systems
    2.      Click on the execute icon beside Define Logical System
    3.      Press the checkmark button to confirm that the change is cross client
    4.      …
    Allow Certains Settings to be modifiable
    (Refer to Note 356483 for more Details)
    SM54
    1.      Enter V_T001B in the Table/View box.
    2.      Select the Generated Objects option.
    3.      Press the Create/Change button.
    4.      Enter any access keys if requested
    5.      Change the Recording routine to no, or user, recording routine.
    6.      Press <Ctrl>+S to save
    7.      Press <Enter> if warned that you are changing a function group that doesn't belong to you.
    8.      You are prompted for transport.  Create a new local transport.
    9.      Repeat steps 1 through 8 for the following objects.  You can specify the same transport you created above.
    V_T001B_GL
    V_T093B_01
    V_T093B_02
    BSI Configuration (R3 HR Systems only)
    SM59
    1.      Expand TCP/IP Connections
    2.      Highlight BSI70-US-TAX and press the Change button
    3.      Change the program field to
    <hostname>\sapmnt\<SID>\SYS\EXE\RUN\TF60SERVER.EXE
    4.      Double check the target host and gateway point to the correct server
    5.      Press <CTRL>+S to save
    6.      Press the Test connection button to test.  If the connect is not successful, take the necessary steps to resolve the issue.
    SE38
    1.      In the Program field, enter RPUBTCU0
    2.      Press <F8> to execute
    3.      Select option BSI version 7.0
    4.      Press <F8> to execute
    5.      BSI should return tax calculations.  If there are errors, take the necessary steps to resolve.
    Reconfigure DB13 schedule
    DB13
    1.      Using the print out created before the refresh, recreate the DB13 calendar.
    Client Configuration
    SCC4
    1.      From the Table view menu, select Display -> Change
    2.      When warned that the table is cross-client, press the checkmark button.
    3.      Double click on one of the non-system clients (i.e. not client 000, 001 or 066)
    4.      Define clients as follows depending on client role
    Development
    Client role:  Customizing
    Changes and transports for client-specific object:  Automatic recording of changes
    Client-independent object changes:  Changes to repository and cross-client customizing allowed
    Protection: Client copier and comparison tool:  Protection level 0
    Restrictions when starting CATT and eCATT:  eCATT and CATT allowed
    Quality Assurance
    Client role:  Test
    Changes and transports for client-specific object:  No changes allowed
    Client-independent object changes:  No Changes to repository and cross-client customizing allowed
    Protection: Client copier and comparison tool:  Protection level 0
    Restrictions when starting CATT and eCATT:  eCATT and CATT allowed
    Training
    Client role:  Education
    Changes and transports for client-specific object:  No changes allowed
    Client-independent object changes:  No Changes to repository and cross-client customizing allowed
    Protection: Client copier and comparison tool:  Protection level 0
    Restrictions when starting CATT and eCATT:  eCATT and CATT allowed
    Sandbox
    Client role:  Test
    Changes and transports for client-specific object:  Changes without automatic recording
    Client-independent object changes:  Changes to repository and cross-client customizing allowed
    Protection: Client copier and comparison tool:  Protection level 0
    Restrictions when starting CATT and eCATT:  eCATT and CATT allowed
    5.      Press <CTRL>+S to save.
    6.      Repeat steps 4 through 6 for any additional clients
    Set System Change Option
    Skip this section of the system is a Development or Sandbox System.
    SE06
    1.      Press the System Change Option button.
    2.      Set the global setting to Not Modifiable
    3.      Press <CTRL>+S to save.
    Release Background Jobs
    Currently, all background jobs, except for system standard jobs have been placed on hold (status scheduled).
    Rewards if useful.
    Regards,
    Pherasath

  • Upgrade steps Details for 9.2.0.8 to 11.2.0.3 Database

    Support,
    We have one requirement from our client like "Upgrade the Database from 9.2.0.8 to 11.2.0.3". They are asking only the DB upgrade except Application.
    Our Current Database is running in Solaris OS and DB is an 9.2.0.8 and Application is an 11.5.10.2.
    I am going to follow the below documents for the Database Upgrade process using DBUA for First Iteration,
    Interoperability Notes Oracle EBS 11i with Oracle Database 11gR2 (11.2.0.3) (Doc ID 1585577.1)
    Interoperability Notes Oracle EBS 11i with Oracle Database 11gR2 (11.2.0) (Doc ID 881505.1)
    In the above documents they mentioned the steps related to the 11g new home installation and upgrade process but before starting the process what are all the things i have to check it in my current Database and Applications.
    Because i have clear idea on what we have to do in the new Oracle Home 11g and the Upgrade process but still have some confusion on the Pre-Upgrade Steps in current database.
    Kindly suggest me what are the details i have to collect and check in my Current Database or provide any proper Oracle documents for the Database Pre-Upgrade Process.
    Thanks in advance,
    Vijay.

    Vijay,
    We would suggest you advice your customer to upgrade to 11.2.0.4 instead on 11.2.0.3
    Interoperability Notes Oracle EBS 11i with Oracle Database 11gR2 (11.2.0) (Doc ID 881505.1)
    https://blogs.oracle.com/stevenChan/entry/11_2_0_4_database
    Preparing to Upgrade Oracle Database can be found at http://docs.oracle.com/cd/E11882_01/server.112/e23633/toc.htm
    You would also need to refer to:
    How To Get The Proper Environment Set To Run Adbldxml.pl When Upgrading To 11g/11gR2? (Doc ID 1310854.1)
    11i: ad_parallel_compile: Ora-01031: Insufficient Privileges in adadmin / re-create grants and synonyms for APPS schema after upgrade from 10gR2 to 11gR2 (Doc ID 1148264.1)
    Note: Please note that we have a dedicated forum for EBS questions -- https://forums.oracle.com/community/developer/english/e-business_suite
    Thanks,
    Hussein

  • SU25 Upgrade Step

    Hello Experts -  We just upgrade BW sytem from NW Enhancement Pack 7.0, SP-7 to NW EHP 7.1, SP Stack 7.
    1)My question is do we need to do SU25- Upgrade step? I was in a impression that we do this step only for release upgrades.
    2) Last time when we did R/3 4.6 to ECC 6.0 upgrade, I saw Yellow lights turned on many of our business and IS roles. Is this normal ?
    I performed all steps per SU25, and had to fix all roles to turn off yellow lights.
    Anyways back to my question 1, will you please let me know your thoughts?
    Thanks Much.

    Roles generally only add authorizations for objects in checks.
    SU24 (with upgrade and SP data via step 3) generally only add documentation (check indicators) and proposals (check/maintain) so the development system is "leading" in that respect and you have already done this in the step 2 tasks.
    But... there is a special case for collisions: namely when SAP proposes a "no check" indicator for an object.
    My advise: Create a transport request and collect the proposals in them until a "no check" appears. Have one central transport for it and release it after correcting the roles which are impacted by the context specific check. Good luck with that in your custom developments...
    In the rare case that you want to activate the check again for that transaction or SAP did, you must ensure that the role transports go through first.
    For other scenarios of accepting all SAP's proposals it makes no difference so you can send the transports through afterwards, as long as you are not opening roles in PROD etc and have not maintained SU22 (a big "no no") nor SU24 in PROD directly.
    Your friends here are the USOB_CD* tables and another obscure one - the name of which I cannot remember at the moment.
    Cheers and good luck with the upgrade,
    Julius

  • Need help in post-installation steps of the PDK

    Hello,
    I have installed Java PDK 6.9 instead of 6.2.
    At the post-installation steps I need to:
    <i>The example iViews in the Portal Development Kit connect to a SAP System with the system alias PDK_R3_BACKEND.
    To run these examples you must define a system object for a test SAP System in your system landscape and assign the following aliases:
    1. PDK_R3_BACKEND Reference to a R/3 system of your custom landscape.
    2. PDKDummySystem Reference to provided system OBN-3. PDKDummySystem.
    WebDynpro Reference to provided system WebDynpro.</i>
    My question is: When I create this System, which type template should it be and which configuration besides the above aliases should it have?
    Roy

    Hey Aviad,
    Yes I did, in my case I've installed PDK SP 9 over SP2 which is prohibited. If this is your case as well do the following:
    1) From the Undeployment tab of the SDM select the com.sap.pct.pdk..
    components.
    2) Using the Archive remover tool which can be accessed from
    System Administration > Support > Portal Runtime > Administration
    Console > Archive Remover --> Remove the portal applications with prefixcom.sap.pct.pdk...
    3) Navigate to Content Administration > Portal content > Content
    Provided by SAP > Platform Add-Ons > Developer Content
    and remove all the contents below this folder.
    4) Restart the server
    After this you can deploy the SP9 business package using the SDM.
    Hope it helps,
    Roy

  • Secure custom developer programs and transactions

    Hi Guys,
    I am given a task in my company to maintain authority check for all costom developed programs and transaction.
    In combination TADIR, TRDIR & TSTC i found more then 1000 transactions and 1500 programs custom developed.
    So now I am having difficulty in finding authority check at program level for all the custom programs and transactions. I tried to use RSABAPSC but this gives for each program/ transaction.
    Can you guys help me to find a best way to get the list for the whol transactions and good approach to complete the task at ace and good way.
    Please comment your best practices and approaches for this.
    Let me know if you guys need any more information from me to make the above more clear.
    Thanks.

    Hi Amit
    I do not think you will find any relevant standard report/functionality in the SAP System, that could scan your Z-Report and find out if it's correctly secured with authorizations checks. Many of those checks could hide in called functionmodules, Methods etc.
    And you still have need to define and check each SAP report for your companies specific security requirement.
    With 1000/1500 Z-transactions/reports, my guess is, that a lot of them might be obsolete, never used, temp programs for dataloads etc. So mayby you do not have to focus on all of them, so I think that my approach would be, to try to limit the number of report that I needed to investigate thoroughly, and then take the reports one by one.
    The steps involved would be something like:
    1. Find out which of your Z-reports/T-codes thats actually used. You should be able to se that in SM20(if you have activated the secure audit log with the correct filters), ST03N etc. Report/T-codes that are not used could be locked in SM01.
    2. Investigate the used reports one by one, Check the Source-Code, do an Authorisation trace etc - Remember that if your Z-Report used BAPI and other SAP Standard functionality, Or if i reads from at DATASET etc.. you might not be able to spot the Authority-check statement in your source code
    3. Implement and test the relevant and requirered additional authorization check
    4. Document in SU24
    5. Adjust the roles
    And your ready for test.
    And yes I know,,,  It can be a hugh job, but I do not think that you can find a quick-fix for this.
    Regards
    Morten Nielsen

Maybe you are looking for