cancel
Showing results for 
Search instead for 
Did you mean: 

SAP Notes synatax error in Tranpsorts requests moved to acceptance

0 Kudos

I have 3 SAP Notes in one transport request and the Transport request is released to Acceptance/Quality. In Acceptance/Quality transport failed due to syntax error one SAP Note. I want to remove that SAP Note from that Transport request and move again only with two SAP Notes which are not creating issues. Any other alternatvive fix , please suggest.

Accepted Solutions (0)

Answers (2)

Answers (2)

Matt_Fraser
Active Contributor

Hi Rahaman,

You'll note I changed the tags on your question slightly, as the Change and Transport System is part of Software Logistics.

Once you have released a transport, you cannot make any changes to it. Instead, you should investigate why you are getting the syntax error upon import to QAS. Most likely there is a prerequisite that you are missing, something you have in DEV but in a different transport that you didn't release. You need to find out what is missing, and then export that from DEV in a new transport. Then import that new transport into QAS, and then re-import your original transport.

Cheers,
Matt Fraser
SAP Community Moderator

Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos

I agree with Matt. Removing the SAP note from going into other systems is not something I would consider but I wouldn't send a transport to other systems if it is throwing an error unless I have a solution to fix the error. If all the notes have been successfully implemented in the development system then you should check why the transport ended in error in the QAS. First check if you have a consistent landscape (patch levels). Check what the error is and see if it is due to some objects missing in the QAS. Maybe there are some transports that have not gone into the QAS. You should look for options to fix the error by bringing in the corrections from the DEV system.

>>I want to remove that SAP Note from that Transport request and move again only with two SAP Notes which are not creating issues<<

Once the transport has been release there is nothing you can do. To achieve this you'll have to reset the notes implementation in the DEV and push the transport out to QAS. Then implement the notes again, except the one with the issue, in the DEV and import the transport into QAS. This is not something I would consider when I know it is possible to fix the error.

Good luck