cancel
Showing results for 
Search instead for 
Did you mean: 

During Contract Creation via ME31K, exit M06E0005 is not getting triggered

Former Member
0 Kudos

When I am trying to do role assignment via exit M06E0005 for Contract Release (Transaction: ME31K) exit is not getting triggered.

Release Codes code has been maintained with work flow option '9'.

Please let me know any pre-requisite is there for the same.

Accepted Solutions (0)

Answers (4)

Answers (4)

0 Kudos

Even if this one is old - for me it would have been helpful to find the correct answer here. Problem is not caused by M06E0005, but by the exit before M06E0004 / EXIT_SAPLEBND_002. You have to assign e_cekko to i_cekko completely within the exit:

e_cekko = i_cekko.

See also:
https://launchpad.support.sap.com/#/notes/2565597
https://launchpad.support.sap.com/#/notes/371667

Maybe someone needs this in future 🙂

JL23
Active Contributor
0 Kudos

Have you debugged ME_REL_GET_RESPONSIBLE_EKKO

or ME_REL_GET_RESPONSIBLE

What is the program doing at statement or does it not even reach this statement?

* Ermittlung über User-exit
WHEN '9'.
CALL CUSTOMER-FUNCTION '005'       
Former Member
0 Kudos

Is there anyone who can solve this issue?

JL23
Active Contributor
0 Kudos

of course must the exit be active - it may sound obvious, but some hundred questions in the community are already evident that this is not known by all.

And you must also have a release strategy which matches with the values from your document. Do you see a release strategy when you click the green flag in ME33K after you saved the document?

Former Member
0 Kudos

Exit is already been activated under SMOD and assigned to a project in CMOD and it has been coded also. Release strategy is also matches with the value of Contract document.

Release strategy flag is yellow, how ever in SWI2_FREQ I can see that WS200000079 workflow has been triggered already but without any agent as agen suppose to be determined from EXIT.

JL23
Active Contributor
0 Kudos

this rather sounds like it went through the exit but could not determine an agent, did you debug or just assumed it did not go through the exit because no agent was assigned?

Is this a brand new customizing and a brand new document, or was an existing strategy changed?

Former Member
0 Kudos

I have put breakpoint inside exit and tried to debug it in change mode. Debug point is not triggering. How ever agent has been very much hard coded over here that agent should be determined.

However same exit is getting triggered during PO creation and agent is getting determined successfully.