How To Upgrade

  • November 2019
  • PDF

This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA


Overview

Download & View How To Upgrade as PDF for free.

More details

  • Words: 2,109
  • Pages: 12
Upgrade Guidelines

Enteg Infotech Pvt. Ltd.

Version 1.0 2.0

Date 01.10.2997

Author Development Team

Reviewer Enteg

Comments

This document describes the procedure to be followed during upgrade for Specific Object

1

Upgrade Guidelines

1. OBJECT TYPE : SOBJ Transaction used to test and upgrade : SWO1. How to check ? a) b) c) d) e) f)

Go to transaction SWO1 Enter the object name and click on DISPLAY button Click on the application toolbar CHECK( CTRL + F2). Check for any errors . If no errors Generate the object. Also compare the object with the older version

2. OBJECT TYPE : SXCI Transaction used to test and upgrade : SE19. How to check ? a) b) c) d)

Go to transaction SE19 Click the radiobutton CLASSIC BADI. Enter the object name and click on display Check for any errors .

3. OBJECT TYPE : IDOC Transaction used to test and upgrade : WE19. How to check ? a) Go to transaction WE19. b) Click on the application toolbar CHECK (CTRL+F2). c) Analyse the errors. 4. SPAU OBJECTS Transaction used to test and upgrade : SPAU How to check? a) Go to transaction SPAU. b) In SPAU screen , you find check boxes under “ modification objects and enhancements” . If you check the check box “ with modification assistant “ You will find the objects that will be provided with a modification assistant 2

Upgrade Guidelines

c) d) e)

f) g)

To make the necessary changes if required.If you check the check box “ without Modification assistant” and execute you will find the objects that will not be provided with any assistance , in case you want to change the code to the code that existed in the previous version. check the check box “ with modification assistant” and execute. You will see a tree structure with FUNCTION GROUPS , INCLUDES, PROGRAMS at the nodes. Under each of these categories you may find other subobjects like for example under function group you may find function modules. Display the versions of the object and compare the active version (The code contains the additions that done in new sytem) to the previous version ( code will be as in old system). compare the code and where ever differences exist analyse and check if any SAP NOTE and user-exits applied in the previous version does not exist in the new version. To include the changes that exist in the previous system that does not exist in the New system you need to adopt modification. Double click on the symbol beside the subobject . If a green square symbol exists you can make changes automatically. If a yellow triangle symbol exists you will find a split screen which will allow you to do the modifications. If a red circle exists you need to do the modifications manually.

5) OBJECT TYPE : IOBJ Transaction used to test and upgrade : RSA1. How to check? a) b) c) d)

Go to transaction RSA1 . Click on Infoobjects and find for the specified infoobject. Double click the object to check if it is active Also perform a syntax check( CTRL + F2) to check the characteristic and key figures.If any error exists report to the customer before making the changes.

6) OBJECT TYPE : ISMP Transaction used to test and upgrade : RSA1. How to check? Note: Here we need to check if the DATASOURCE is present in the correct source system and if it is active and syntactically correct. a) Go to transaction RSA1 . b) Click on Datasource and choose the source system from the “ choose source system” application toolbar. c) Search for the datasource and check if it is active and syntactically correct. d) Report the syntax errors, inactive objects and not found objects to the customer before taking any further action.

3

Upgrade Guidelines

7) OBJECT TYPE : OSOA Transaction used to test and upgrade : RSA3. How to check? a) Go to transaction RSA3. b) Put the specified datasource in the input box for datasource. c) Click on Extraction or Execute button (F8). Check if the extraction is happening if not analyse the reason for extraction not happening and report to the customer. 8) OBJECT TYPE : ISTD Transaction used to test and upgrade : RSA1. How to check? a) b) c) d)

Go to transaction RSA1. Click on Infosource and search for the specified infosource. Check if the communication structure and transfer structure in the infosource are active. Report to the customer regarding any inactive communication structure or transfer structure and check if the source system and datasource are mentioned in the transfer structure.

9) OBJECT TYPE : PROG Transaction used to test and upgrade : SE38. How to check? a) b) c) d) e)

Go to transaction SE38 Enter the program. Check the syntax and rectify any syntax errors. Activate the program and try executing the program Report to the customer for any errors in the program

10)OBJECT TYPE : SHPL Transaction used to test and upgrade : SE11.

How to check? a) Go to transaction SE11 4

Upgrade Guidelines

b) Click on the radio button “ search help” enter the object name and click display c) Check the syntax and rectify any syntax errors. d) Activate the object if not activated . 11)OBJECT TYPE : PARA ( SPA / GPA PARAMETER) 12)OBJECT TYPE : VIEW Transaction used to test and upgrade : SE11. How to check? a) b) c) d)

Go to transaction SE11 Click on radiobutton “ VIEW” and enter the object name and click display Check the object(CTRL + F2) for any errors and warnings . Check the Development class of the object.

13)OBJECT TYPE : SHIP

( INFOPACKAGE)

Transaction used to test and upgrade : SE11. How to check? a) b) c) d)

Go to transaction RSA1 Click the global find and click on the check box “ infopackages” In the “ find “ box put the object name and click on search Check if the object exists.

14) OBJECT TYPE: FUGR a) b) c) d)

Go to transaction se80. Enter the function group name. Check the extended syntax check. Rectify if any errors are there and in obsolete statements check for obsolete function module error and make documents before correction and after correction with clear description.. e) Activate the Function group. f) Report to the customer for any errors in the Function group. 15)OBJECT TYPE: SXSD (BADI (Defn)) a). Go to transaction se18. b). Enter the object name in BADI Name and do display c). In Menu implementation -> overview select an implementation object to check. d). Navigate thru implementing class, there check the syntax and activate the object. e). Step d should be executed for all the implementation object exist in Overview. f). Report to the customer for any errors in the Function group.

5

Upgrade Guidelines

16) OBJECT TYPE: SSFO a) Go to Transaction smartforms. b) Do the syntax check and rectify if any Errors. c) Activate it 17) OBJECT TYPE: AUTH a) Go to Transaction se20. b) Check the Existence of given Authorization field object c) For Authorization class and object go to transaction se21. ********************************************************************* 18) AREA : INFOAREA Path : RSA1 -> Modeling->Infoprovider . Things to be checked : Existence of infoarea . 19)CLAS : Class (ABAP Objects) Path : SE24 . Things to be checked : Activation 20)CUBE : INFOCUBE Path : RSA1 -> Modeling-> Infoprovider . Things to be checked : Activation of Infocube . 21)DEST : Open Hub Destination Path : RSA1 -> Metadata Repository -> local object -> Open Hub Destination 22)IDOC : Basic type Path : WE30 . 23)IOBJ : InfoObject . Path : RSA1 -> Modeling - > Infoobjects Things to be checked : Activation 24)ISET : InfoSet . 6

Upgrade Guidelines

Path : RSA1-> Modeling->Infoprovider . Things to be Checked : Activation . 25)ISFS : DataSource Replica Path : RSA1 -> Modeling -> Datasources Things t be checked : Activation . 26)ISIP : InfoPackage Path : RSA1 -> Modeling -> InfoSources Things to be checked : existence . 27)ISMP : Transfer Rule Path : RSA1 -> Modeling -> Infosources -> select Requires Transfer Rule -> Extra  Object Directory Entry -> Transfer Rule . Things to be checked : Saved and Active . 28)ISTD : InfoSource transaction Data Path : RSA1 -> Modeling -> Infosources Things to be Checked : Activation . 29)APCO : Application Component Path : RSA1 -> Modeling -> Infosources . Things to be Checked : Existence . 30)CMOD : Customer Exit . Path : TCODE -> CMOD . Things to Be checked : Existence and Active status . 31)CTRT : Currency Translation Type Path : RSA1 -> Metadata repository -> Currency Translation Type Things to Be checked : Existence and Active status . 32)DEVC : Package .

7

Upgrade Guidelines

Path : TCODE : SE80 . Things To Be Checked : Existence and Active status of All Objects in the Package . 33)DSIG : InfoPackage Groups (SAP Delivery) . Path : RSA1 -> Modeling -> Infosources -> click on Show Infopackage Group (Button is on right hand Panel below Application Toolbar ). Things To Be Checked : Existence and Active status . 34)DOMA : Domain Path : SE11 -> Domain . Things to Be Checked : Active Status . 35)DTEL : Data Element Path : Data Element . Things to be checked : active status . 36)FUGR : Function Group . Path : SE37 -> GOTO -> Fuction Groups -> Display Function Groups . Things to Be Checked : Active Status . 37)IOBC : InfoObject catalog Path : RSA1 - > Modeling -> Infoobject . Things to Be checked : Existence and Active status 38) ISCS : Communication structure . Path : RSA1 -> Modeling -> Infosources -> select Requires Infosource -> Extra  Object Directory Entry -> Infosource . Things To Be Checked : Active status . 39)ISTS : Transfer Structure . Path : Path : RSA1 -> Modeling -> Infosources -> select Requires Infosource ->Extra -> Object Directory Entry -> transfer Structure . Things To Be Checked : Active status . 8

Upgrade Guidelines

40)MPRO : Multi Provider . Path : RSA1 -> Modeling -> Infoprovider . Things to be Checked : Active Status . 41)MSAG : Message Class . Path : SE91 . Things to be Checked : Active Status . 42)NROB : Number Range Objects Path : SNRO . Things to be Checked : Active Status . 43)ODSO : ODS Object. Path : RSA1 -> Modeling -> Infoprovider . Things to be Checked : Active Status . 44)OSOA : DataSource (Active version ) Path : RSA1 -> Modeling ->Datasource . Things to be Checked : Active Status . 45)QVIW : Transport Object for BW Query View . Path : RSA1 -> Metadata repository -> Query View Things to Be checked : Existence and Active status . 46) RRCA : BW: RRI InfoCube Recipient Path : RSA1 -> Metadata repository -> BW: RRI InfoCube Recipient Things to Be checked : Existence and Active status . 47) RSPC : Process chain . Path : RSA1 -> Metadata repository -> Process Chain . Things to Be checked : Existence and Active status . 48)SICF : ICF Service . 9

Upgrade Guidelines

Path : TCODE -> SICF . Things to Be checked : Existence and Active status . 49)SPOK : INFOSPOKE . Path : RSA1 -> Metadata repository -> Infospoke . Things to Be checked : Existence and Active status . 50)SXCI : Business Add-Ins – Implementations . Path : SE19 . Things to Be checked : Existence and Active status . 51)TABL : table . Path : SE11 . Things to Be checked : Existence and Active status . 52)TMPL : BW Web Templates . Path : RSA1 -> Metadata repository -> BW Web Templates. Things to Be checked : Existence and Active status . 53) TOBJ : Definition of a Maintenance and Transport Object Path : SE56 . Things To be Checked : Existence and Active status . 54)TRAN : Transaction . Path : SE93 . Things To be Checked : Existence and Active status . 55)TTYP : Table Type . Path : SE11 -> datatypes -> table type . Things To be Checked : Existence and Active status . 56)WAPA : BSP (Business Server Pages) Application .

10

Upgrade Guidelines

Path : SE80 . Things To be Checked : Existence and Active status . 57)SPFL : Profile parameter Path : TCODE : RSPFPAR Things to be checked : Existence , the value of User-defined value and System Default value should be same in the old system and new system .

11

Upgrade Guidelines

12

Related Documents

How To Upgrade
November 2019 22
Upgrade
May 2020 16
Upgrade
May 2020 17