Application Development 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: 

Call Transaction In MV50AFZ1 ?

sachin_soni
Active Participant
0 Kudos

Hi Everyone,

I have a senario , where in based on user inputs before posting goods issue in delivery processing (vl02n),

I need to call a Z-Transaction and update some details in it.

Now for that i created an include for the enhancement MV50AFZ1 and tried to write Call transaction statement as follows:

call TRANSACTION zwb01.

which throws the following syntax error: "Field ZWB01 is unknown.it is neither in one of the specified tables nor defined by a data statement"

Anyone has any idea on this, can i call transaction in an exit,if yes wat is it that i am missing out here??

Thanks,

sachin

1 ACCEPTED SOLUTION

JozsefSzikszai
Active Contributor
0 Kudos

you miss the apostrophes, should look like:

CALL TRANSACTION 'ZWB01'.

On the other hand the called transaction (ZWB01) contains DB COMMIT, than you should not do this from a user exit.

6 REPLIES 6

JozsefSzikszai
Active Contributor
0 Kudos

you miss the apostrophes, should look like:

CALL TRANSACTION 'ZWB01'.

On the other hand the called transaction (ZWB01) contains DB COMMIT, than you should not do this from a user exit.

0 Kudos

hi eric,

thank you so much for replying,

you wrote":than you should not do this from a user exit" is this a must-not do or if client senario requires this we can go for it???

0 Kudos

it depends, what ZBW01 is doing, but I guess it changes something in the DB and there is a COMMIT WORK somewhere in this transaction. And this means the the LUW of the main program would be destroyed with this COMMIT (the data will be inconsistent in the DB), this is why we should never call transaction from user exits. Pls. read SAPHelp: Logical Unit of Work and you understand better

0 Kudos

even if this transaction updates some z-tables and then returns?

0 Kudos

>

> even if this transaction updates some z-tables and then returns?

exactly, in fact this is the problem itself. It will update the transaction from which it was called as well - but that transaction is only "half-ready" and this will lead to inconsistent database entries.

0 Kudos

ok eric, i think i've got your point.Will discuss the alternate possiblities with the functional

thanks for your support

points awarded