Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Executing transaction that starts with slash (/) using command field

ffs
Explorer
9,027

Hello,

When I try to execute a transaction that starts a slash (/) on command field, for example “/transaction,” it give me the following error: "This function is not possible"- Message no. 00127. It seems that the system automatically interprets it as a function and do not tries, after it concludes that is not a function, that it may be a transaction code.

If I submit "/n/transaction" it is executed normally.

My question is: Does anybody know a way for me to program a workaround? I have a set of transaction codes that starts with / that I wanted to be able to execute in the command field.

Thank you in advance.

1 ACCEPTED SOLUTION
Read only

VeselinaPeykova
Active Contributor
3,746

I cannot understand why /nTCODE is unacceptable in your case - I have been using transactions starting with '/' for the past 9 years and not even end users object to this /n addition (well, they use favorites for most of the long and hard to memorize codes, but still). Usually, when I explain to users that there is a system limitation and prove to them that favorites are more useful for them in many cases, they accept this.

There is a sap note which explains the reason behind this behaior: 598688 - Misleading OK code entries and mentions another option - instead of '/n' to use '=', for example, I could type =/BEV1/EMS in the command field and the transaction will be executed.

3 REPLIES 3
Read only

VeselinaPeykova
Active Contributor
3,747

I cannot understand why /nTCODE is unacceptable in your case - I have been using transactions starting with '/' for the past 9 years and not even end users object to this /n addition (well, they use favorites for most of the long and hard to memorize codes, but still). Usually, when I explain to users that there is a system limitation and prove to them that favorites are more useful for them in many cases, they accept this.

There is a sap note which explains the reason behind this behaior: 598688 - Misleading OK code entries and mentions another option - instead of '/n' to use '=', for example, I could type =/BEV1/EMS in the command field and the transaction will be executed.

Read only

3,746

Hello Veselina,

I am not saying that is not acceptable – is not a question of being acceptable or not – I just think that if it is possible to have transaction that start with a slash, then the system should not automatically discard the possibility that the user might what to submit a slash transaction code without the prefix “/n or =”.

Nonetheless, I don’t want a “fix” rather a workaround.


Thank you for your input and for the sap note, I hadn’t read/found that one.

Read only

3,746

You've got a workaround. Prefix your transaction with /n

Thread locked.