HI Ingadave,
Your existing transport requests changed to be local ones because the the corresponding package(development class) of the included objects in the requests is not assigned to available transport layer.
The package(development class) of the objects must have the transport layer which is associated with the transport route. If it does not have the from and to system defined, the request will be saved into a local change request.To export a object, some rules must be fulfilled. The object must be in a package(development class), which belongs to a transportable transport layer.The source system need also a destination system, otherwise the request will be a local (independent of the transport layer).
So to change the local reqeusts to be transportable ones, you should change the transport layer for the correpsonding pacakges.
For details informations, please refer to the following notes:
28967 Developments are entered in local requests
32394 Change object development class allocation
I am afraid that there is no way to do a mass update to re-point all the transport requests to the new transport target...
As mentioned in note 28967, package(development class) definations are maintained on table TDEVC. The value of field PDEVCLASS is the corresponding transport layer assigned to the package(develpment class). Please check what is the active tranport layer currently on your system, and try to change the value correspondingly. After that objects included in this package(development class) will change to be transportable, and the corresponding transport request will change to transportable ones automatically.
With Best Regards
Julia
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.