Hi Nitin,
Please find below, a detailed notes on SAP transport system i.e. managing change requests, tasks.
The Change and Transport System (CTS) is a tool that helps you to organize development projects in the ABAP Workbench and in Customizing, and then transport the changes between the SAP Systems in your system landscape.
The Correction and Transport System
Changes created in the development system must somehow be moved, then incorporated into the test system, then subsequently moved and incorporated into the production system. The SAP Correction and Transport System (CTS) serves this purpose and is the vehicle by which SAP moves objects such as programs, screens, configurations or security settings from one system to the next.
Additionally, the CTS ensures consistency between systems by maintaining log entries for any attempted or completed activities. If used correctly, the CTS creates an effective and standardized procedure for managing and recording changes made to the system while providing an excellent mechanism for integrating either newly created objects or existing objects that have been altered to meet the customer’s needs.
The CTS system is actually made up of various components which allow for the movement of objects and help to maintain comparable and up-to-date changes from one system to the next.
Overview of Task, Change Request :
TASK:
Corrections are recorded in tasks and transported using the change requests. It can control changes to internal components of the system that includes data dictionary objects, ABAP/4 programs, screens, CUA definitions, and documentation.
The task can register and can keep the documentation of all the changes to the system objects. Once the objects are locked the system prevents parallel changes to the system objects. For existing objects, the system ensures that only a single original copy of each object exists. The previous version of an object can be restored and two versions of the objects can be compared.
The CTS system asks for a change request number (if the recording is on in that client) whenever a customizing change is done or a new object is created with a development class other than $TMP (local object development class).
A task is automatically created under a change request. User has to release the task first to release the change request. The user can be able to create or modify the object only after he or she opened a task. Opening a task registers the change with the system. Once the user releases a task, the objects in task get transferred to the change request.
After the unit testing in customizing master client is completed, a task is released to its change request using transaction code SE01.
After a task is released, it can no longer be modified. If the user wants to modify the same objects, which were included in the released task, he has to create a new task. A task can not be deleted after it is released. The attributes also can not be changed. All the objects in the tasks should have a development class other then $TMP(local objects development class); otherwise those objects can not be transported.
You need to take the following steps to release a task:
Select a task
Press the release icon
Then the user is going to see a large editor for the documentation. Provide a good documentation about the task and save it.
Now the task will be released
Verify that the task is released by looking at the log for the task or if you refresh the SE09 or SE10 screen then the task can be found in released section of that screen.
Important Tips: A task can not be released if it is empty, user does not have the proper authorization, the objects are not locked properly and the objects are not locked in another task or change request. Some objects can be manually added to a task. When creating a change request and task, the user should create the right type of request (CUST or SYST). Changes to customizing objects belong to CUST and Changes to client independent and ABAP/4 development workbench belong to SYST category. If a task is already released then the objects of that task or change request can be easily added to the new one by selecting include template from file menu in SE01, SE09 or SE10.
Change Requests:
After a task is released, the objects are moved to a change request. Using the change requests the sap objects get transported from one system to another. There are four categories of change requests: Transportable, Customizing, Local and Not assigned. Change requests containing SYST type changes and CUST type changes belong to transportable category. Only client dependant changes or CUST type changes belong to Customizing category. If the change request contains ‘Local Objects’, then it belongs to Local category. If the change request is created manually through Workbench Organizer and no repository object is assigned to it then that belongs to ‘Not assigned’ category.
After the task is released, if the task does not have a change request then a window pops asking for one as following:
User has to choose from either existing requests category or new request category. It is very important for the user to know that he should not select a change request that is already released. As we have seen before, in a development team usually the team leaders assign the tasks to the developers. After the work is done, developers release their tasks to the change request created by the team leader. To release the change request, select the request and then select the release button in the toolbar..
It is recommended that the users should describe the purpose and status of the development with every change request. This gives complete change documentation for all the developments and the changes made to the system. After the change requests are released, the new versions for those objects are created in the version database of the system. The cycle goes on for every change request created for every change made to the objects. The version database helps the user the compare the old version with the new version and restoring a particular version in case it is necessary.
Important tips:
A transport can be created manually through SE01 and different types of objects can be directly added to the editor to get transported to the target system. Also a released change request or task can be included as a template in that transport.
REWARD POINTS IF HELPFUL
Regards
Sai
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.