EXIT_SAPLEBND_001 release strategy won´t trigger

[Former Member]

Dear Experts,

I need some hint on this one:

I am setting a release strategy with classification for purchase requisitions

using some characteristics in my class that are  based on values

read into the fields CEBAN-USRC1  and CEBAN-USRC2.

The fields are filled in EXIT_SAPLEBND_001, INCLUDE ZXM06U13.

Everything is working fine so far, strategies are picked.

Just when I try to enhance the code to check if there has been a Purchreq

for identical material within the last 30 days, then the strategy won´t be picked,

although while debugging the values are filled into the corresponding fields

(of I_CEBAN and E_CEBAN).

The strategy itself does not trigger though, somewhere the values get lost.

My code is as follows:

The picking of the relesae strategy won´t work if marked, commented code

is active.

Cheers, Rafael.

[Former Member]

Hi,

Based on your code it looks like the I_CEBAN-USRC2 is expected to "space" only as if you are right that commented code do not make it triggered, it can lead to only one logical conclusion.

1. I_CEBAN-GSWRT is Less Than 1000

2. Select from EBAN is successful( SY-SUBRC = 0 )

3. LS_FRG-ZZBER contains some value other than space.

Check in the debugging and then tally it with the customizing for the characteristic value set for the trigger condition for the release strategy.

R

[Former Member]

Hello Dear R,

thanks for your reply.

In fact after activating the commented code I get the expected values for both USRC1 and USRC2.
like this: (While Debugging).

If I_ceban-gswrt > 1000.

--> USRC1 is not space.

      USCR2 is not space.

If Iceban-gswrt < 1000.

--> USRC1 is not space.

      USCR2 is SPACE.

But at the end the fields are not used for release strategy Determination.

This way it does not pick.

Regards

Rafael

[Former Member]

Hi Rafael,

Ok Fair enough. Lets take step backward. The exit is called from the below place. May be you want to check in debug mode what happens to the highlighted part.

R

[Former Member]

Hi R,

yes indeed,

the exit is called up from the place as described by you. (Some lines up at line 73).

Then debugger goes throuh the exit. And both fields get correctly filled.

Then Debugger gets back to the very spot mentioned by you. handing values over to CEBAN.

*CEBAN is initial. Therefore it steps over this spot.

After that I do not find another place where CEBAN could change values to initial.

cheers

Raf

[Former Member]

Hiya,

Can you also check at the end of FM what value E_RESET flag has got. Maybe try to debug step by step after this FM also . It must have been issuing some messages if it is not processing it.

R

[Former Member]

Hi R,

well it seems not to hit that line wit e_reset.

Intresting is why it works without the marked code.

The code does only Change here in the exit.

The values are assigned correctly.

cheers

raf

[Former Member]

Hi R,

thankyou very much for supporting me.

This morning everything came clear to my eyes.

1. strategy was both values were filled AND value > 1000.

2. strategy was first  field filled, 2nd field = space AND value < 1000,

so I had to I impement a third rel. strategy for the case

both fields filled AND value < 1000.

cheers

raf