Automate

Hello to the community,

I am facing an unexpected issue with the error in subject.

I have recorder a GUI script for RECN transaction in one of our Non Production SAP systems.

This script is working fine in all our Non Production SAP system but throws the error in subject very early in the script when executed in Production system.

To my understanding the SAP systems (non prod - prod) are technically identical hence I am unable to get my head around this and am hoping the community might shed some light.

Looking forward to hearing communities' ideas.

Note: I have restricted access to Production SAP system hence my usual workaround of re-recording a failing script in the system the issue occurs, is against the current authorisation policy.

Hi Rodion

This is not my area of expertise.  A couple of general things you could check:

• did you record using GUI scripting?  If so, does prod allow SAP scripting?  You'd have to ask your Basis team.
• are the tcode settings in non-prod and prod identical?  Sometimes tcodes have pop-ups and/or defaults that aren't the same between SAP systems and cause the script to throw an error.  The key would be where in the script is this happening?  Can you run in debug mode?

Hope that gives you a few ideas,

Sigrid

Hello to the community,

I am facing an unexpected issue with the error in subject.

I have recorder a GUI script for RECN transaction in one of our Non Production SAP systems.

This script is working fine in all our Non Production SAP system but throws the error in subject very early in the script when executed in Production system.

To my understanding the SAP systems (non prod - prod) are technically identical hence I am unable to get my head around this and am hoping the community might shed some light.

Looking forward to hearing communities' ideas.

Note: I have restricted access to Production SAP system hence my usual workaround of re-recording a failing script in the system the issue occurs, is against the current authorisation policy.

Hello Sigrid,

Thank you for your comments. Please find my replies below:

• did you record using GUI scripting? - Yes. If so, does prod allow SAP scripting? - Yes. You'd have to ask your Basis team.
• are the tcode settings in non-prod and prod identical? - Yes. Sometimes tcodes have pop-ups and/or defaults that aren't the same between SAP systems and cause the script to throw an error. - No differences between the systems. The key would be where in the script is this happening? - It happens in the first field of the script that is supposed to be updated as per the data sheet. Can you run in debug mode? - I don't see any additional information in debug mode for this kind of error but will arrange one and update.

Hi Rodion

This is not my area of expertise.  A couple of general things you could check:

• did you record using GUI scripting?  If so, does prod allow SAP scripting?  You'd have to ask your Basis team.
• are the tcode settings in non-prod and prod identical?  Sometimes tcodes have pop-ups and/or defaults that aren't the same between SAP systems and cause the script to throw an error.  The key would be where in the script is this happening?  Can you run in debug mode?

Hope that gives you a few ideas,

Sigrid

Hello to the community,

I am facing an unexpected issue with the error in subject.

I have recorder a GUI script for RECN transaction in one of our Non Production SAP systems.

This script is working fine in all our Non Production SAP system but throws the error in subject very early in the script when executed in Production system.

To my understanding the SAP systems (non prod - prod) are technically identical hence I am unable to get my head around this and am hoping the community might shed some light.

Looking forward to hearing communities' ideas.

Note: I have restricted access to Production SAP system hence my usual workaround of re-recording a failing script in the system the issue occurs, is against the current authorisation policy.

Hello,

Update: Debug mode does not show anything additional to the script throwing the error and cancelling the run.

Happy to hear any thoughts on this.

Hello Sigrid,

Thank you for your comments. Please find my replies below:

• did you record using GUI scripting? - Yes. If so, does prod allow SAP scripting? - Yes. You'd have to ask your Basis team.
• are the tcode settings in non-prod and prod identical? - Yes. Sometimes tcodes have pop-ups and/or defaults that aren't the same between SAP systems and cause the script to throw an error. - No differences between the systems. The key would be where in the script is this happening? - It happens in the first field of the script that is supposed to be updated as per the data sheet. Can you run in debug mode? - I don't see any additional information in debug mode for this kind of error but will arrange one and update.

Hi Rodion

This is not my area of expertise.  A couple of general things you could check:

• did you record using GUI scripting?  If so, does prod allow SAP scripting?  You'd have to ask your Basis team.
• are the tcode settings in non-prod and prod identical?  Sometimes tcodes have pop-ups and/or defaults that aren't the same between SAP systems and cause the script to throw an error.  The key would be where in the script is this happening?  Can you run in debug mode?

Hope that gives you a few ideas,

Sigrid

Hello to the community,

I am facing an unexpected issue with the error in subject.

I have recorder a GUI script for RECN transaction in one of our Non Production SAP systems.

This script is working fine in all our Non Production SAP system but throws the error in subject very early in the script when executed in Production system.

To my understanding the SAP systems (non prod - prod) are technically identical hence I am unable to get my head around this and am hoping the community might shed some light.

Looking forward to hearing communities' ideas.

Note: I have restricted access to Production SAP system hence my usual workaround of re-recording a failing script in the system the issue occurs, is against the current authorisation policy.

Hello to the community,

I am facing an unexpected issue with the error in subject.

I have recorder a GUI script for RECN transaction in one of our Non Production SAP systems.

This script is working fine in all our Non Production SAP system but throws the error in subject very early in the script when executed in Production system.

To my understanding the SAP systems (non prod - prod) are technically identical hence I am unable to get my head around this and am hoping the community might shed some light.

Looking forward to hearing communities' ideas.

Note: I have restricted access to Production SAP system hence my usual workaround of re-recording a failing script in the system the issue occurs, is against the current authorisation policy.

Hello to the community,

I am facing an unexpected issue with the error in subject.

I have recorder a GUI script for RECN transaction in one of our Non Production SAP systems.

This script is working fine in all our Non Production SAP system but throws the error in subject very early in the script when executed in Production system.

To my understanding the SAP systems (non prod - prod) are technically identical hence I am unable to get my head around this and am hoping the community might shed some light.

Looking forward to hearing communities' ideas.

Note: I have restricted access to Production SAP system hence my usual workaround of re-recording a failing script in the system the issue occurs, is against the current authorisation policy.

Hello Rodion,

GUI scripting mode scripts are notorious for being over sensitive and breaking. I have seen examples where if someone's excel data file was sized different, the script would through that error. The equivalent of Studio GUI scripting mode in SAP directly is called "SAP script recording and playback". I would suggest trying this out and seeing if it still fails. SAP Script recording and playback  The recording will be a VBS file. If it works in SAP, you can compare the VBS (I would save and open in notepad to review the code) with the Studio script mapping. If it fails using that, it will fail in Studio.

I choose to use BAPIs/RFMs instead. 

Hello to the community,

I am facing an unexpected issue with the error in subject.

I have recorder a GUI script for RECN transaction in one of our Non Production SAP systems.

This script is working fine in all our Non Production SAP system but throws the error in subject very early in the script when executed in Production system.

To my understanding the SAP systems (non prod - prod) are technically identical hence I am unable to get my head around this and am hoping the community might shed some light.

Looking forward to hearing communities' ideas.

Note: I have restricted access to Production SAP system hence my usual workaround of re-recording a failing script in the system the issue occurs, is against the current authorisation policy.

Hello Shelby,

Thank you for the suggestion above.

I have encountered the same error and at the same stage of the script execution by using the "SAP script recording and playback".

The behaviour of the script erroring only in Production Client and running smoothly in all others seems to be uniform across Winshuttle and SAP script recording and playback. Hence, I am assuming that there may be some sort of technical difference between the Production Client and the rest. I am inclined to raise this with SAP as I am unable to spot any functional difference from my end.

As per your comment above, you choose to use BAPIs/RFMs instead; are you using those in combination with scripting or standalone?

Kind regards

Rodion P.

Hello Rodion,

GUI scripting mode scripts are notorious for being over sensitive and breaking. I have seen examples where if someone's excel data file was sized different, the script would through that error. The equivalent of Studio GUI scripting mode in SAP directly is called "SAP script recording and playback". I would suggest trying this out and seeing if it still fails. SAP Script recording and playback  The recording will be a VBS file. If it works in SAP, you can compare the VBS (I would save and open in notepad to review the code) with the Studio script mapping. If it fails using that, it will fail in Studio.

I choose to use BAPIs/RFMs instead. 

Hello to the community,

I am facing an unexpected issue with the error in subject.

I have recorder a GUI script for RECN transaction in one of our Non Production SAP systems.

This script is working fine in all our Non Production SAP system but throws the error in subject very early in the script when executed in Production system.

To my understanding the SAP systems (non prod - prod) are technically identical hence I am unable to get my head around this and am hoping the community might shed some light.

Looking forward to hearing communities' ideas.

Note: I have restricted access to Production SAP system hence my usual workaround of re-recording a failing script in the system the issue occurs, is against the current authorisation policy.