In such cases you may expect a lot of changes to the existing functionalities and thus creation of multiple change (transport) requests for the same object. Even sometimes poor development may cause rework on the activity already performed. This results in poor requirement gathering and blueprinting activity due to lack of time, thus resulting into actual requirement visibility at the time of testing when users see the actual output in the system. Nowadays with volatile market situations, high business expectations and budget constraints companies are trying to reduce project/ release timelines. However with this approach we are just able to reduce the unnecessary transports only during initial development activities. If in this way transports are used, we are manually able to minimize the possible number of unnecessary TRs in the system. He can then finally release the main change request to move to quality system and subsequently to production. Releases of all the tasks indicate the transport owner, completion of the change. As a member releases his/her task, objects move to the higher level and get consolidated in the change (transport) request.
This indicates completion of his/her part of the work. Once a member completes his/ her activities, is needed to release the assigned task. For this reason SAP provides second level called task. This in turn may require several employees (members) to work on accomplishing the complete change. This means an object container with its owners name for completion of a logically complete activity.
This change (transport) request follows two level hierarchy:Īs per standard SAP, a change (transport) request must have a unique owner. Let us start the discussion with one of the most basic things that an SAP consultant uses while working in SAP system- Transports.Ī transport request is a request carrying changes done in the system also called as change request, in technical terminology. Imagine completing an average six month SAP project or a big release cycle which includes several development activities with more than 50% reduction in transports (than the normal project or release cycle) moving to production yet executing everything same as in a normal SAP project.
0 kommentar(er)
