hello, friend.
actually, you can search for subjects like this in the threads archive. you will be pleasantly surprised to find that there are already many threads with similar issues and that you can find answers to even more otherwise unrealized questions. and you don't have to wait for anyone to reply.
it looks like the issue is urgent for you, and this is why i am attaching this feed from Sadhu Kishore, which was posted some time ago... (if he replies to your thread, you may choose to award him points).
"Hi,
The transport workflow provides a framework for transporting enhancements or new developments of existing business functions in a system landscape. It provides a direct connection between development and transport administration. The transport workflow manages the transport process, determines the user for each individual step automatically, and then displays an interface which they can use to perform the task directly.
It is an efficient method of transporting a selected number of requests into a group of transport targets, and uses clearly defined approval steps to ensure the quality of your target systems. The requests can be transportable change requests, Customizing requests, relocation transports or transports of copies. The transport targets do not need to be located on defined transport routes. However, the transport workflow can involve some risks, caused by the dependencies between transport requests:
Import sequence
It is important that you import requests in the correct order, so that development work is up-to-date in the target system.
Incompleteness
It is important that the functions transported in the transport proposal are complete; otherwise errors may occur in the import system.
A request is not imported, but it contains an important data element. You use another request to transport a table that references this data element. Since the referenced data element does not exist in the target system, activation errors will occur when you import the second request.
The transport workflow is a generic workflow. Its ability to process the transport route configuration in TMS enables it to adapt itself to any system landscape. This means you can transport multiple requests into multiple targets, even if these targets are not located on the transport routes.
This reduces the amount of work for the transport administrator significantly. The automated nature of the workflow also reduces the likelihood of errors during transports.
You can use the transport workflow in two different ways.
Transport workflow as a transport strategy
If you have production systems in your landscape that can only accept approved transports, we recommend that you use the transport workflow to organize and coordinate the transport process.
To do this, set Workflow-controlled transports as your transport strategy and configure the transport workflow.
When you release a transport request, the transport workflow starts automatically and the screen Create Transport Proposal appears. The requests are then released implicitly when the transport proposal is sent to the transport administrator.
Special transport workflow (mass transports)
You can use the special transport workflow to make transports that do not follow the defined transport routes or that take place outside the normal transport schedule (part of the mass transport strategy). These transports may be corrections made in the development system that have to be transported into the production system without delay.
To use the special transport workflow, set Mass transports as your transport strategy and configure the transport workflow."
thanks. you have been most generous.
regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.