Assigning ITS Files to Change Requests in R/3 
When you add Internet Transaction Server (ITS) files to ITS source control in the R/3 System for the first time, you must assign them to a change request.
At subsequent check-ins, the system remembers the relevant change request and automatically replaces the files. You don’t need to specify a change request each time.
If you release a change request for transport, you must create a new change request and reassign the files to it. If you fail to do this, the files cannot be checked out (or in) by other users.
Prerequisites
You must
add the files to ITS source control.Procedure
To assign new files to a change request in the R/3 System:
You can make generic entries here.
You see a list of objects for the service.
You see the Change Request Query dialog.
Result
The R/3 System creates a change request and assigns the files. You can now
check the files out and modify them.
When the R/3 System releases a change request that includes ITS files, it does not check the status of the files. Therefore, it is possible to release a transport for which files are still checked out. If this happens, you cannot check the objects back in until you create a second change request and assign the objects to it.