Trigger Point not triggering upon setting the USER STATUS via BAPI

[Former Member]

Hello,

Our functional consultant had set up the trigger point at Operation level of a Production order. USAGE is 00001 with function "Insert reference operation set" upon user status being RWRK. The trigger point shall insert new operations.

We have a front end webdynpro UI from where user will confirm operation by operation in the shop floor.

Test case: When we fail the operation, we have to set the user status to E0001(which is REWRK).

I am using a BAPI STATUS_CHANGE_EXTERN to update the user status. User Status gets updated successfully but the trigger point is not triggering as a result, the new operations are not getting inserted. But when I come into CO02 and set the User status check box for RWRK and go back to Operation view screen, trigger point seems to be triggering as I can see the new operations gets inserted.

We are not sure what we are missing in the config. Any clues please?

Thanks,

Kiran    

[former_member189817]

Hi

     When we use BAPI to perform the business transaction It will not consider the settings from Customization or Master data.Everything we need to do instruct system to craete it.Try to create / Insert Rework operation using other BAPI.

Regards,

Velmurugan S

[Former Member]

Hi,

The trigger point works in dialog. Popup screens are called to determine operation numbers if necessary. I am not sure but I don't think it will work in background. I am familiar with this kind of discrepancy in behaviour in SAP functions. It should work if you change the user status in a confirmation transaction such as CO11N. In CO11N it is not possible to directly change the user status however you can make cause of variance, entered in confirmation, determine a user status.

Regards.

[sjeevan]

It only means BAPI is not working as a standard transaction (CO02 in your case) would work. You need to look for OSS notes,

Check out the one below, also search more with key word STATUS_CHANGE_EXTERN

Note 847081 - PPCO0001: STATUS_TABLE and STATUS_TABLE_OLD are identical

[Former Member]

Hi Jeevan,

I have searched OSS notes and reviewed many of them but didn't find any which can address my issue.

I shall review your note and get back.

Thanks,

Kiran    

[Former Member]

Hi Jeevan,

The note changes are already in our system. We are at ECC6.0, 702 for SAP_APPL.

Thanks,

Kiran    

[sjeevan]

Like Özgen said, some functions work only in dialog mode, recently there was a thread in which the poster had the same problem.

http://scn.sap.com/message/11086668#11086668

So, the solution would be instead of using the BAPI, try the BDC method.

[Former Member]

Hi Jeevan,

I have to set the status in ABAP Proxy. I am not sure of the problems in calling a BDC from proxy. Is there a way to avoid BDC and just fire the trigger points upon setting the USER status using above function module?

Thanks,

Kiran

[Former Member]

Any clues please.

[Former Member]

Any clues please.

[sjeevan]

Kiran,

You may have to post this question in ABAP forums, then you may get reply from someone who worked on ABAP Proxies.

[Former Member]

Hi Jeevan,

My idea is not to go with BDC. How to initiate the trigger points upon setting the USER status using above function module?

Thanks,

Kiran