help needed on FM

[former_member224404]

Hi Guys,

I have created a FM which actually updates operation user status of an service order(IW31). It basically calls

FM STATUS_CHANGE_EXTERN.

Now my FM is getting called from a FM which is RFC enabled. And this RFC enabled FM is called from a

legacy system.

Now the problem is when I test my FM it updates

the operation status properly. But when legacy system

calls that RFC FM then operation status is not updated.

Could you guys help me on this.

Mainak

[former_member224404]

Hi Guys,

I have created a FM which actually updates operation user status of an service order(IW31). It basically calls

FM STATUS_CHANGE_EXTERN.

Now my FM is getting called from a FM which is RFC enabled. And this RFC enabled FM is called from a

legacy system.

Now the problem is when I test my FM it updates

the operation status properly. But when legacy system

calls that RFC FM then operation status is not updated.

Could you guys help me on this.

Mainak

[Former Member]

Hello,

Make sure that the FM is remote enabled and also the username password are valid.

cheers,

Sushil Joshi

[Former Member]

Hi,

Firstly in ATTRIBUTES tab of function module

select RFC Enable Function module button ( Remote Enabled).

And still getting the same error then im sorry that I Cant help you exactly so kindly look into this link..

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2043985f-014c-2a10-a0ba-d081e09e...

and

http://searchsap.techtarget.com/tip/0,289483,sid21_gci786084,00.html

Hope it may help you.

Regards

Narin Nandivada

[Former Member]

Hello Mainak,

Read the FM documentation for the FM:

FU STATUS_CHANGE_EXTERN

____________________________________________________

Short Text

Set User Status

Functionality

User status is set or deleted.

Notes

The status change is first executed in the internal buffer only and is written to the database later using a "COMMIT WORK".

If the message handler is active, no error messages or exceptions are triggered. Instead an appropriate message is written in the message handler.

Parameters

CHECK_ONLY

CLIENT

OBJNR

USER_STATUS

SET_INACT

SET_CHGKZ

NO_CHECK

STONR

Exceptions

OBJECT_NOT_FOUND

STATUS_INCONSISTENT

STATUS_NOT_ALLOWED

Function Group

Looks like the Logic is Handling using the COMMIT work at later point of time. So In your RFC Wrapper FM do a commit work / call BAPI Transaction_commit and try.

Thanks,

Greetson

[former_member224404]

Thanks