Changing Objects in the Non-Original System
You should only modify objects outside of their original system in urgent cases. These changes later have to be made to the originals as well, so twice as much work is involved.
In particular, you should avoid modifying SAP standard objects.
Inconsistencies may also occur, if the modified objects do not match the new standard. In both cases, you have to make time-consuming adjustments.
- When you save your changes, the request query screen appears. The procedure is the same as for original objects; you can either select an existing request or create a new one.
- If necessary, a repair is created for you or an unclassified task is classified as a repair.
The name of the object is added to the object list of the repair. From this point onwards, the object is locked by the change request and only users with tasks in the request are allowed to edit the object. In addition to this, the repair flag is set for the corresponding object to prevent the object from being overwritten by imports into the system.
When the object is edited again by any of these users, the request query screen no longer appears. The object is, however, added to the repair of the user involved, if it has not already been entered there.
Users working together on a change request constitute a development team working on the same project.