There are four types of Requests
1. Local request
2. Change request
3: Transport of copies
4. Workbench request
Local Request : -
Local request are those requests which resides on same box and can not transportable to other SAP R/3 systems. These kind of request are of only workbench types.
Change/Customizing Request: are generally for system customizing activities that you’d do in SPRO.
Change request are those which made in Development systems and then transported to other SAP R/3 systems like production or Quality Assurance.
The change request are of two types
a. Customizing change request
b. Workbench change request
A request for defining / customizing settings. The customizing request are of two types
1. Client dependent
2. Client independent
Workbench Change request are generally for things you would create in the ABAP workbench. This is primarily code or custom objects.
A request for carrying out development work in the ABAP Workbench.
A user will be able to create or modify an object only if he has opened a change request.
Entering objects in change requests ensures that all changes made are registered.
Transport of copies:
A transport of copies will move the latest version of an object included to the system of your choice, but will not assume that you want to move it to production. Therefore, it transports a “copy” of the object but assumes that its final destination is only the system that you are moving it to. A normal transport on the other hand would assume it’s going to the system that you’re moving it to (QA) and all other systems downstream from it. (Production)
Also for this reason, we can move all the transports of copies we want and we won’t see them affect the downstream system. (Production) They will only affect the system that we move them into. You will still be opening a single Customizing or Workbench request to move your changes to production, but you will only be releasing these requests when you know you are ready to move. For unit testing in QA you will be moving Transport of Copies until you are satisfied with what you have. At this time, you will release your original change request and move it into QA for final User Acceptance testing. By doing this, you will be using a single transport for your
change that will ultimately go to production.
Sometimes we get a requirement to release some Transport Requests (TR) to different landscape for further development or testing purpose. However, at times we may need to have those TR again in original system for making changes.
In order to do this, SAP has provided a facility called “Transport of Copies”. We can create the transport of copies and add those released TR into it and then continue with our changes.
This can also be use for other purpose such as when you want to test the software changes in one system without having them transported automatically to other systems in your transport track.
.
1. Local request
2. Change request
3: Transport of copies
4. Workbench request
Local Request : -
Local request are those requests which resides on same box and can not transportable to other SAP R/3 systems. These kind of request are of only workbench types.
Change/Customizing Request: are generally for system customizing activities that you’d do in SPRO.
Change request are those which made in Development systems and then transported to other SAP R/3 systems like production or Quality Assurance.
The change request are of two types
a. Customizing change request
b. Workbench change request
A request for defining / customizing settings. The customizing request are of two types
1. Client dependent
2. Client independent
Workbench Change request are generally for things you would create in the ABAP workbench. This is primarily code or custom objects.
A request for carrying out development work in the ABAP Workbench.
A user will be able to create or modify an object only if he has opened a change request.
Entering objects in change requests ensures that all changes made are registered.
Transport of copies:
A transport of copies will move the latest version of an object included to the system of your choice, but will not assume that you want to move it to production. Therefore, it transports a “copy” of the object but assumes that its final destination is only the system that you are moving it to. A normal transport on the other hand would assume it’s going to the system that you’re moving it to (QA) and all other systems downstream from it. (Production)
Also for this reason, we can move all the transports of copies we want and we won’t see them affect the downstream system. (Production) They will only affect the system that we move them into. You will still be opening a single Customizing or Workbench request to move your changes to production, but you will only be releasing these requests when you know you are ready to move. For unit testing in QA you will be moving Transport of Copies until you are satisfied with what you have. At this time, you will release your original change request and move it into QA for final User Acceptance testing. By doing this, you will be using a single transport for your
change that will ultimately go to production.
Sometimes we get a requirement to release some Transport Requests (TR) to different landscape for further development or testing purpose. However, at times we may need to have those TR again in original system for making changes.
In order to do this, SAP has provided a facility called “Transport of Copies”. We can create the transport of copies and add those released TR into it and then continue with our changes.
This can also be use for other purpose such as when you want to test the software changes in one system without having them transported automatically to other systems in your transport track.
.
No comments:
Post a Comment