Download - 6618655 change mgmt

System Administration Made Easy 17–1

&KDSWHU��&KDQJH�0DQDJHPHQW�

&RQWHQWV�

Table Maintenance (Transaction SM31) .............................................................17–2

Change Control .....................................................................................................17–9

Managing SAP Notes............................................................................................17–9

Change Control (Managing Transports) ...........................................................17–12

Transporting Objects..........................................................................................17–15

Chapter 17: Change Management

Table Maintenance (Transaction SM31)

Release 4.6A/B 17–2

7DEOH�0DLQWHQDQFH��7UDQVDFWLRQ�60��

If no transaction is available to maintain a table, it can be directly maintained using transaction SM31.

Use this method if, and only if, there is no transaction to maintain the table. Directly maintaining a table circumvents all edits and validations in the system.

When a change is made directly to a table and the table is saved, the change is immediate. There is no “undo” function.

&UHDWLQJ�DQ�(QWU\�LQ�WKH�7DEOH��60��

� *XLGHG�7RXU�

1RWH� This procedure shows how to create new entries in the Prohibited Password table, USR40.

1. In the Command field, enter transaction SM31 or SM30 and choose Enter (or from the menu bar, choose System → Services → Table maintenance → Extended table maintenance).

2. In Table Views, enter the table name (for example, USR40).

3. Choose Maintain.

3

2




4. If the table you are changing is client-independent, this dialog box appears.

Choose .

Client independent changes will affect all clients on a system, not just the client on which you are working.

5. Choose New entries.

4

5




6. In Password (the field name that appears depends on the table selected), enter the new entry (for example, january).

7. Choose Save.

If the client is not configured to record changes for transport, this screen does not appear.

8. If this screen appears, create a request by choosing .

9. In Short description, enter text that

describes what change you are making to the table and why you are making the change.

10. Choose Save.

6

7

9

10

8




11. Record the request number. This number is needed to transport the table changes to the other systems.

12. Choose .

13. The message in the status bar

indicates that the entries have been saved.

14. Choose Back.

15. Here you see the new entry

january in the table.

16. Choose Back.

12

14

13

15

11

16




'HOHWLQJ�DQ�(QWU\�IURP�D�7DEOH��60��


1. In the Command field, enter transaction SM31 or SM30 and choose Enter (or from the menu bar, choose System → Services → Table maintenance → Extended table maintenance).

2. Enter the table name (for example, USR40).

3. Choose Maintain.

4. If the table is client-independent this

window appears.

Choose .

Client-independent changes affect all clients on a system, not just the client you are working in.

3

2

4




5. Navigate to the password by scrolling up or down to go through the table or choose

Position to go directly to the entry.

6. Select the password to delete (for example, password).

7. Choose .


indicates that the password was deleted.

9. Choose Save.

10. Choose .

5a

6

7

10

9

8

5

5




11. In Short description, enter text about the change you are making to the table and why.

12. Choose Save.

13. Record the request (transport)

number.

This number is needed to transport the table changes to the other systems.

14. Choose .


indicates the change was saved.

11

12

14

15

13


Change Control


&KDQJH�&RQWURO�

Change control is the managing of the changes, modifications and customizing made to your system. This control allows you to be aware of and control what changes are made. These change must be made in a controlled manner, because uncontrolled changes are a recipe for disaster.

The process is: < Managing the changes: � SAP notes that are applied to the system. � Authorization process for moving the changes from one system to another.

< Making the changes to the R/3 System. < Moving the changes from one system to another. The SAP training class BC325 (Software Logistics) covers change management and transports. Also see Software Logistics by Sue McFarland.

0DQDJLQJ�6$3�1RWHV�

:KDW�

SAP notes were formerly known as OSS notes.

Managing SAP notes means tracking the notes that you have reviewed and applied. These notes are release and configuration specific and may (or may not) relate to your system’s configuration. Some of these notes may actually be specific to individual systems in your environment.

:K\�

There are several reasons to track SAP notes that are applied to your system: < If a problem arises, SAP may ask if a specific note has been applied.

If you do not have a record of what notes you have applied, then you must manually investigate your system. This process can be difficult and time consuming.

< When the system is upgraded, for conflict resolution, you need to know what notes have been applied.

You must know what notes: � Are included in the upgrade, so you can go back to SAP standard code � May need reapplying because they are not included in the upgrade


Managing SAP Notes


+RZ�

< Document all SAP notes applied to your system(s), and specify which system and instance to which it is applied.

< Document all code changes with the SAP note number that applies.

This documentation is important especially if a program is changed by an upgrade or support package. It helps you determine if your code change is included in the upgrade or patch and, therefore, whether the program can revert back to “SAP standard.”

< In addition to a high-level tracking table, detailed records should be kept on the individual notes. The record should include the problem to be fixed, objects changed, release in which the note was fixed (important for upgrades), and other applied or recommended notes (see sample form in chapter 12).

< Document all SAP notes that are “noted” and do not require actual changes to be made to the system (for example, procedural or informational notes).

< Document SAP notes that have not been applied to your systems.

There may be cases in which you review a note and determine that it does not apply. You should document the reason(s). If SAP asks why a specific note was not applied, you will have an answer.

6DPSOH�)RUPV�

General Note Record

Note # Description Noted DEV QAS PRD

12345 xxx 11/06/98 11/15/98 11/30/98

36987 yyy 2/06/99 2/13/99 2/28/99


Managing SAP Notes


Detailed Online Service System Note Record

Note – Applied

Note # :

Short text:

Module:

Problem to solve:

Objects changed:

Fixed in release:

Comments:

Other notes applied with this problem:

Applied to:

System Client Transport number Date imported or applied

Return code

Sign off/Initial

DEV 100

110

QAS 200

210

PRD 300


Change Control (Managing Transports)


&KDQJH�&RQWURO��0DQDJLQJ�7UDQVSRUWV��

:KDW�

Change control is the process of managing changes, modifications and customizing made to the system and the transport of those changes through the pipeline from the development to the test system, and finally to the production system. One of the most important change management tasks involves notifying the appropriate people of the changes and getting their approvals.

:K\�

Because R/3 is an integrated system, there are items that may impact many other modules or groups. If, for example, a change is made to a module which impacts other modules, and this change is done without the knowledge of the appropriate people, a process may cease to function. If something stops functioning in the production system, business may stop until the problem is resolved.

In the past, most application systems were independent, so changes in one system were insulated from the other systems. Because of this independence, users may not be used to consulting with other organizations when making changes to what they consider “their” systems.

In change control, there is a review and approval process. You should not make a change and apply it to the system without a review and approval of the changes. These changes apply to changes to SAP objects and system configuration.

+RZ�

The following steps demonstrate a change control process: 1. Document all code, configuration, and other changes. 2. Test by:

< Developer < Functional analyst

3. Get the following signoffs (see sample Transport Request Form on page 14) By all functional groups: < Review and be aware of changes that might affect their functional areas. < If needed, perform additional tests by and with other functional groups, where there

is possible interaction from the change.




Operations review < Review any changes that may affect the operations staff < Schedule new jobs < Program error or problem procedure

Document the program restart procedure. Is it “safe” for the operator to restart the job, if it fails or hangs?

4. Verify the change in the target system Change control should also contain a recovery plan that includes: < What to do if the import to the production system creates a problem? < How to roll back? Will it be possible to roll back? < Will a problem require a database restore?

A transport cannot be “undone.”




Sample Transport Request Form

Request to Transport

Transport number:

Transport title/description:

Objects:

SAP Notes Applied: (SAP note form required for each note)

Effect on other functional areas:

Special transport instructions:

Specific order Need quiet time: Yes/No

Request for transport by:

Tested by:

Functional area review and approval:

FI MM Computer Operations

SD

Approved for transport by:

Transport details:

System Client Date Start time End time Return code

Sign off/ Initial

QAS 200

210

PRD 300


Transporting Objects


7UDQVSRUWLQJ�2EMHFWV�

7UDQVSRUWV�LQWR�WKH�3URGXFWLRQ�6\VWHP�

:KDW�

A transport is the mechanism that R/3 uses to move changes: < Within a system from one client to another client < From one system to another system on the same client < From one system to another system and from one client to another client

:KHQ�

Complete the transport in the production system during a “quiet” period (for example, Sunday afternoon or evening) when users are not logged on the system.

Ideally, a full system backup should have been completed before transports are imported.

:K\�

During a transport, objects may be overwritten. If an object is being used in the target system when a transport is performed, the transport may cause inconsistent results or terminate the transaction. In the worst case scenario, a transport may “break” the production system and you will need to restore the system.

+RZ�

Transports are only done when necessary (when you have a transport that needs to be moved). You may also have the occasional “emergency” transport that must be moved at a time other than at your normal weekly transport time.

7UDQVSRUWLQJ�2EMHFWV�

The transport system has been significantly changed in Release 4.x. (It used to be known as Correction and Transport System.) It is still CTS, but is now called the Change and Transport System; In CTS are the Transport Management System (TMS) and Change and Transport Organizer (CTO).

The purpose of transports is to move objects and configuration from one system to another in the production pipeline. This pipeline is defined in a three-system landscape as systems comprising development to quality assurance to production. A transport starts in the development system, is transported to the quality assurance system where is tested, and finally into the production system.

To transport objects, use one of the following methods: < Transport Management System (TMS) < Operating system (OS)

Transports are taught in BC325 (Software Logistics).




706�0HWKRG�

The TMS method uses a new transaction, STMS, to perform the transports.

Benefits: < The user does not have to go into the operating system to do the transport. < The user selects the transport from a GUI to do the import.

There is no risk of incorrectly typing the wrong command or transport number. < Because the import is done from within R/3, there is no need to physically go down to

the server or use a “remote connection” (for NT) to the server to do the import. < The transport route can be specific to clients.

With one export, the TMS system is set up to import into several combinations of system and client as defined in the transport route. (This functionality is new in Release 4.6.)

< Transport requests can be grouped into projects, and the transport request selected and moved by these projects. This grouping reduces the chances of transporting the wrong transport request when there are many activities and projects going on. (This functionality is new in Release 4.6.)

< Advanced quality assurance prevents transports from being imported into the production system until they are released after successful testing in the quality assurance system. (This functionality is new in Release 4.6.)

< The import of transport requests can be scheduled. You no longer have to manually import the transport requests or write scripts to do the import. (This functionality is new in Release 4.6.)

706�GRFXPHQWDWLRQ�

The TMS documentation (including configuration) can be found on the R/3 online documentation by choosing Help→ SAP Library → Basis Components → Change and Transport System (BC-CTS) → BC-Transport Management System.

2SHUDWLQJ�6\VWHP�0HWKRG�

The operating system (OS) method requires you to go down to the OS level to execute the transport program (tp) at the command line.

Disadvantages:

< The user must go into the operating system to do the transport.

This action is a security issue in companies that restrict which employees can have this level of access.

< The import is done from the command line.

There is the risk of incorrectly typing and importing the wrong transport.




6WDQGDUG�7UDQVSRUW�3URFHVV�

This section describes the standard transport process from your development system to your production system.

The following steps are part of your company’s change management process:

1. Obtain proper authorization to transport the objects.

Obtaining this authorization is the responsibility of the person who requests the transport move. The required authorizations and approval process differ based on the company. Some companies require the approval of only one person, while other companies require the approval of numerous people.

A major purpose of the approval process is to give other functional groups a “heads up” as to what you are moving.

If the move affects any of the functional groups, and they know about it, they can take the appropriate action: review, test, etc. If necessary, your transport is delayed until the affected functional groups are satisfied. This way, there will not be problems related to your transport.

2. Define other necessary transport management related information, such as: < Who to contact in case of problems

The person doing the transport typically is not a programmer. If there is a problem with the transport, that person will need assistance to determine what failed.

< What recovery process to follow if the transport fails < Who will test the transport in the target system to determine that it works as

intended < The transport number < The source system < The target system(s) < Relationship to other transports, such as sequence order, etc.

For more information, see chapter 12.

3. Use transactions SE01, SE09, or SE10 as necessary to release the transport.

First release the task, then release the request (or transport).

The TMS (normal) import and one of the OS import options, tp import all, will import all transports in the import buffer. The assumption is that all objects released into the import buffer have been tested and approved for transport into the target system. If you use either method, it is important to not release the objects until they have been tested and approved for transport.

Up to, and including Release 4.5, in a three-system landscape, once the transport is imported into the quality assurance system, it is added into the production system import buffer, and there is no “second release” out of the quality assurance system.

4. Import the request into the target system.




5. Check the transport log.

,PSRUWLQJ�WKH�(QWLUH�,PSRUW�%XIIHU�

If you import the entire import buffer, everything in the buffer will be imported into the target system, regardless of whether all the transports are ready. The problem with importing the entire buffer is that the various transports may be in different stages of testing. Some may be finished, while others may still be in the process of being tested. An “import all” imports all the objects in the buffer, regardless of whether they are ready to be transported.

A new feature in Release 4.6 is the Advance Quality Assurance. In this feature, the requests imported into the quality assurance system must be approved in this system to be transported to the production system. This process helps prevent the “accidental” transport of a request that has not completed quality assurance testing in this system. This change is an important change management enhancement and should be used by everyone with a standard three-system landscape.

Before Release 4.6, when a transport was imported into the quality assurance system, it was automatically added to the import buffer of the production system. Therefore, an “import all” would import everything, ready or not.

To manage the import buffer in the: < Source system, do not release the transport until the testing is complete. < Production system: � Using the TMS method, use “preliminary import” to select the individual transport

to import. � Using the TMS method, use the project method to manage the transport requests. � Using the OS method, import the requests (transports) individually. � Do an “import all” only when the entire buffer is ready to be imported.

6SHFLDO�7UDQVSRUWV�IURP�6$3�

Special manual transports fix specific problems, add features, or add functionality from third-party software vendors. U.S. customers can download the transport files from SAPSERV4. These files are usually a single file that you have to unpack using the CAR program. The downloading and unpacking procedure is described in chapter 22.

1. Get the files from SAP or the delivery media, such as a CD.

Two files (sometimes there is a third file) are normally combined as a set (for example, K174511.P30, R174511.P30, and D174511.P30).

2. Copy the files into the appropriate transport directories:

a. Copy files beginning with “K” into: < NT <drive>:\usr\sap\trans\cofiles

\\<host>\sapmnt\trans\cofiles < UNIX /usr/sap/trans/cofiles

b. Copy files beginning with “R” and “D” into:




< NT <drive>:\usr\sap\trans\data \\<host>\sapmnt\trans\data

< UNIX /usr/sap/trans/data � 1RWH� “D” files do not always exist.

3. Add the special transport to the import buffer (process described in 17–25 and 17–34).

4. Import the transport (process described in 17–27 and 17–34).

5HOHDVLQJ�D�5HTXHVW��7UDQVSRUW��

To release a request:

1. Release all tasks associated with the request.

2. Release the request.


1. In the Command field, enter transaction SE10 and choose Enter (or from the SAP standard menu, choose Tools → Accelerated SAP → Customizing → SE10-Customizing Organizer).

2. In User, enter the user ID of the person who owns the Request.

3. Verify that the following categories are selected: < Customizing < Workbench < All clients

4. To verify the Request status: < Select Modifiable. < As an option, you may deselect

Released. Over time the released list will be large.

5. Choose Display.

5

2

4

3




6. Select the task to release.

7. Choose .

8. Document the content of the

transport.

9. Choose Save.

10. A message appears on the message line indicating the task was released.

11. Choose Back.

9

10

11

7

6




12. A message indicates that the task was released into the specified request.

All of the tasks associated with a request must be released, before the request can be released.

The next step is to release the request.

5HOHDVLQJ�WKH�5HTXHVW�

1. Select the request.

2. Choose .

3. If this window appears, select

Release and export.

4. Choose .

1

2

12

3

4




5. As the export is running the line “In process Requires update” appears.

6. Choose .

7. When the export is finished, the

above message changes to a status message.

8. Check the export return code and text message.

This screen shows that the export Ended OK and has a return code of 0.

9. Check the test import return code and text message.

This screen shows that the import Ended OK and has a return code of 0.

The return codes are: < 0 – Successful < 4 – Warnings occurred < 8 – Performed with errors < 12+ - Transport was terminated

A return code of 8 or higher is a failed transport.

10. Choose Back.

5

6

9

7, 8

10




11. A message appears indicating that the request was released and exported.

12. The request is now in the Released

section.

You can see this request only if you selected to view released requests in step 1 of releasing a task.

,I�7KHUH�,V�D�3UREOHP�

If there is a problem, review the transport log. For more information, see the transport log later in this chapter.

12

11




706�0HWKRG�RI�7UDQVSRUWLQJ�

7KH�0DLQ�706�6FUHHQ�


1. In the Command field, enter transaction STMS and choose Enter (or from the SAP standard menu, choose Tools → Administraton → Transports → STMS-Transport Management System).

2. The Transport Management System (TMS) screen appears.

This is the transaction that all the following TMS processes will start from.




To access TMS’s online documentation, choose:

1. SAP Library → Basis Components → Change and Transport System (BC-CTS) → BC-Transport Management System

2. BC-Transport Management System

Under BC-Transport Management System, there are five major topics: < Configuring TMS < Performing Transports < Approving or Rejecting Requests < Special Transport Workflow < Troubleshooting

$GGLQJ�D�6SHFLDO�7UDQVSRUW�LQWR�WKH�,PSRUW�%XIIHU�


Adding a special transport into the import buffer is usually not done. The release process adds the transport into the appropriate input buffer. This task is only performed for special transports that are downloaded from SAPSERV4 or received via CD.

3UHUHTXLVLWH�

The transport files have been moved into the appropriate directories.

1. From the TMS screen, choose .

1




2. Position cursor on the <SID> of the R/3 System to which you want to add the transport.

3. Choose .

4. From the menu bar, choose

Extras → Other requests → Add.

5. Enter the transport number.

6. To continue, choose .

7. Choose Yes.

2

5

6

7

3

4




8. The special transport is now in the system buffer.

8VLQJ�706�WR�,PSRUW�D�7UDQVSRUW�5HTXHVW�



1

8




2. Select the <SID> of the system into which the request will be imported.

3. Choose .

4. From this screen, you have two

options: < Preliminary Import

to selectively import requests one at a time.

< Import All to import all the requests in the queue for the selected system.

�

,PSRUW�D�6HOHFWHG�5HTXHVW�

1. Select the request you wish to import.

2. Choose .

3

2

1

2




3. Enter the Target client.

4. Choose .

5. The Options tab is where you select

special import options.

These options correspond to the unconditional codes used when transporting at the OS level.

6. Choose Yes.

3

6

4

5

5




7. The import process begins and may run for a while. You can monitor the progress of the import by watching the process indicators.

8. The Request number now appears

with a green check, indicating that it was imported as a “preliminary import.”

,PSRUW�$OO�5HTXHVWV�

1. At this point, all the requests shown in the input buffer will be imported and indicated in the Request column.

2. Choose .

2

1

8

7




3. Enter the target client number.

4. Choose .

5. Choose Yes.

6. To refresh the screen, periodically

choose .

7. When completed, the message Import queue is empty appears.

8. Choose Back.

5

3

4

6 8

7




�

&KHFN�WKH�7UDQVSRUW�/RJ�



2. Select the <SID> of the R/3

System for which you want to check the transport log.

3. From the menu bar, choose Goto → TP system log.

2

3

1




4. Choose (or from the menu bar, choose Syslog → Refresh).

5. Check the final return code: < 0 (Successful) < 4 (Warning) < 8 (Error) < 12 (Fatal)-6

Anything other than a 0 or 4 is considered a failed transport.

6. From the menu bar, choose GoTo → Transport steps (this was formerly known as alog).

7. From this screen, you can verify

the request number and the return code for that request.

8. The return code (indicated in column RC) is the same as in step 5 above.

By using TMS to review the transport logs, the inconsistency encountered in the OS method of viewing the transport log does not occur. The inconsistency is when the tp return code (received when the import is done) does not match the return code in the transport log. The following line would appear in the above screen:

Request SID S RC

ALL SAS S 0008

5

7

4

8

6




26�0HWKRG�RI�7UDQVSRUWLQJ�

$GGLQJ�D�6SHFLDO�7UDQVSRUW�,QWR�WKH�,PSRUW�%XIIHU�

Adding a special transport into the import buffer is normally not done. This task is only performed for special transports that are downloaded from SAPSERV4 or received via CD.

3UHUHTXLVLWH�

< The transport files have been moved into the appropriate directories. < You must be on the target system (PRD).

1. Go to the transport program directory: < NT: <drive>:\usr\sap\trans\bin < UNIX: /usr/sap/trans/bin

2. Load the transport into the import buffer with the following command:

tp addtobuffer <transport> <target sid>

tp addtobuffer P30K174511 DEV

Where the: < Target system is DEV < File is K174511.P30 < Transport number is P30K174511 < The transport number is derived from the transport file number, where the first three

characters are the file extension (P30), and the rest of the name is the base name of the file (K174511).

3. Import the transport.

,PSRUWLQJ�WKH�7UDQVSRUW��

3UHUHTXLVLWH�

< You must be on the target system. < For NT, on the target system, you must have mapped a drive to the shared directory

(\sapmnt) on the source system (for example, where drive S: is mapped to \\devsys\sapmnt).

+RZ�

1. Go to the transport directory.

NT: <drive>:\trans\bin

UNIX: /usr/sap/trans/bin

2. Test your connection to the target system with the following command:

tp connect <target sid>

tp connect prd




3. Enter the transport command. < To specify an individual transport, enter:

tp import <transport> <target sid> client=<target client>

tp import devk900023 prd client=100

Where the: � Transport number is devk900023 � Target system is PRD � Target client number is 100

< To import the entire import buffer, enter:

tp import all <target sid>

tp import all prd

You may be instructed in an SAP note or by the SAPNet hotline to use Unconditional codes or U codes. These are special program option switches that the tp program uses during the import process.

< In NT, use QuickSlice, an application included with the NT resource kit, and the CPU activity in the NT Performance Monitor to monitor the import process. After a few times, you will recognize the activity pattern of a transport.

< In UNIX, use the utilities top or xload to monitor the import process.

1. Record the start and finish time for the transport on the transport log or the transport form.

2. Check the exit code.

If you receive an exit code of 8 or higher, the import failed. You must resolve the problem and reimport the transport. If you get a return code of 8, there is a known condition where this return code does not match the transport log. This condition is described in Checking the Transport Log section below.

3. Check the transport log (see below).

&KHFNLQJ�WKH�7UDQVSRUW�/RJ��7UDQVDFWLRQ�6(��

:K\�

The transport log indicates why a transport failed.

+RZ�

The information in this chapter is only a portion of the first half of the process, that is, determining if the transport succeeded or failed. The second half of the process, investigating why the transport failed, is not covered. If the transport involves an object such as an ABAP program or SAPscript layout, you will need the assistance of your programmers to determine why it failed and how to fix it.




After the transport is completed, check the transport’s exit code: < 0 = OK < 4 = Warning < 8 = Error < 12 = Severe Error

If you receive an exit code of 8 or higher, the import failed. You must resolve the problem and re-import the transport.

The transport could still have failed even if you did not receive a failed return code. The final test is to verify in the target system that the transport arrived properly. The developer and functional area owner are responsible for this verification.

&KHFNLQJ�WKH�7UDQVSRUW�/RJ�


1RWH��You must check the transport log from the transaction that released the transport (SE09 or SE10).

1. In the Command field, enter transaction SE10 and choose Enter (or from the SAP standard menu, choose Tools → Accelerated SAP → Customizing → SE10-Customizing Organizer).

2. Under Category, select: < Customizing < Workbench < All clients

3. Under Request status: < Deselect Modifiable. < Select Released.

4. Enter a date range in the Last changed From and To fields to limit the amount of requests to review.

5. Choose Display.

4

2

3

5




6. Select the request.

7. Choose .

8. On the Import line, check the return

message and code: < 0 – Successful < 4 – Warnings occurred < 8 – Performed with errors < 12+ – Transport was terminated

A return code of 8 or higher is a failed transport.

9. If you see a warning in step 8, choose display log for the line with the warning.

6

7

8

9




10. Choose to drill down for additional details.

11. The status bar indicates how many levels you have drilled down.

You may run into a rare inconsistency between the return code in this log and the return code when you ran the import program tp. This condition occurs when the tp program ends with a return code 8 (Error) and the log above shows a maximum return code of 4 (Warning). This inconsistency is caused by a step in the import that is not associated with the transport number (in the example RW6K9000079). Thus when the log is reviewed, the maximum return code of 4 [(and not 8) (Warning)] appears. However, it is still a failed transport.

The TMS method does not have this inconsistency.

10

11

Download - 6618655 change mgmt

Top Related