6618655 change mgmt

Download 6618655 change mgmt

Post on 05-Dec-2014

825 views

Category:

Business

0 download

Embed Size (px)

DESCRIPTION

 

TRANSCRIPT

  • 1. &KDSWHU &KDQJH 0DQDJHPHQW&RQWHQWVTable Maintenance (Transaction SM31) .............................................................172Change Control .....................................................................................................179Managing SAP Notes ............................................................................................179Change Control (Managing Transports) ...........................................................1712Transporting Objects..........................................................................................1715System Administration Made Easy 171
  • 2. Chapter 17: Change ManagementTable Maintenance (Transaction SM31)7DEOH 0DLQWHQDQFH 7UDQVDFWLRQ 60
  • 3. 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
  • 4. *XLGHG 7RXU1RWH 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. 2 3 Release 4.6A/B 172
  • 5. Chapter 17: Change Management Table Maintenance (Transaction SM31)4. If the table you are changing is client-independent, this dialog box appears. Choose . 4 Client independent changes will affect all clients on a system, not just the client on which you are working.5. Choose New entries. 5System Administration Made Easy 173
  • 6. Chapter 17: Change ManagementTable Maintenance (Transaction SM31)6. In Password (the field name that appears depends on the table selected), enter the new entry (for 7 example, january).7. Choose Save. 6 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 . 89. In Short description, enter text that describes what change you are making to the table and why you 9 are making the change.10. Choose Save. 10 Release 4.6A/B 174
  • 7. Chapter 17: Change Management Table Maintenance (Transaction SM31)11. Record the request number. This number is needed to transport the table changes to the other systems.12. Choose . 11 1213. The message in the status bar indicates that the entries have been saved. 1414. Choose Back. 1315. Here you see the new entry january in the table.16. Choose Back. 16 15System Administration Made Easy 175
  • 8. Chapter 17: Change ManagementTable Maintenance (Transaction SM31)HOHWLQJ DQ (QWU IURP D 7DEOH 60
  • 9. *XLGHG 7RXU1. 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. 2 34. If the table is client-independent this window appears. Choose . 4 Client-independent changes affect all clients on a system, not just the client you are working in. Release 4.6A/B 176
  • 10. Chapter 17: Change Management Table Maintenance (Transaction SM31)5. Navigate to the password by scrolling up or down to go through the table or choose 5a Position to go directly to the entry.6. Select the password to delete (for 7 example, password).7. Choose . 5 6 58. The message in the status bar indicates that the password was deleted. 99. Choose Save. 810. Choose . 10System Administration Made Easy 177
  • 11. Chapter 17: Change ManagementTable Maintenance (Transaction SM31)11. In Short description, enter text about the change you are making to the table and why. 1112. Choose Save. 1213. Record the request (transport) number. This number is needed to transport the table changes to the other systems. 1314. Choose . 1415. The message in the status bar indicates the change was saved. 15 Release 4.6A/B 178
  • 12. Chapter 17: Change Management 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 systems 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.

View more