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: 

RFC with CHANGING parameter

Former Member
0 Kudos

Hi All,

When creating an RFC, if i add a parameter in CHANGING tab, it is giving an Information message that `CHANGING is not allowed in RFC`. Is it true ?

If yes, that what is the alternative to pass a parameter which can be changed from SAP as well as the Other system using the RFC.

Thanks,

Best regards,

Prashant

1 ACCEPTED SOLUTION

former_member223537
Active Contributor
0 Kudos

Hi,

User enters MATNR on screen-other application, RFC is called. If field STATUS is blank(will be blank for 1st RFC call), then data would be validated and MATERIAL related data is sent back with value in STATUS as 01(success) else appropriate error message no. is sent.

Other application will check If STATUS NE 01, then error message description is fetched locally by the application and displayed on screen else the material related data is displayed on screen. User would click on confirm. Again the same BAPI would be called. If validations are fine, then COMMIT work would be done.

So the purpose is that, data is fetched in 1st RFC call and displayed on screen. Then user would click confirm and then same RFC would be called.

COMMIT WORK should not be executed for the 1st call to RFC but later it should be executed.

Best regards,

Prashant

3 REPLIES 3

Former Member
0 Kudos

Prashant,

RFC's cannot have parameters that can be changed.

There is not work around for the same.

However, I really don't see a need as well.

Can you explain your requirement?

Regards,

Ravi

former_member223537
Active Contributor
0 Kudos

Hi,

User enters MATNR on screen-other application, RFC is called. If field STATUS is blank(will be blank for 1st RFC call), then data would be validated and MATERIAL related data is sent back with value in STATUS as 01(success) else appropriate error message no. is sent.

Other application will check If STATUS NE 01, then error message description is fetched locally by the application and displayed on screen else the material related data is displayed on screen. User would click on confirm. Again the same BAPI would be called. If validations are fine, then COMMIT work would be done.

So the purpose is that, data is fetched in 1st RFC call and displayed on screen. Then user would click confirm and then same RFC would be called.

COMMIT WORK should not be executed for the 1st call to RFC but later it should be executed.

Best regards,

Prashant

0 Kudos

Prashant,

I still can't see the need where the data is being changed.

You are only changing the status field in the application where the BAPI is being called, right?

I can't see a situation, where you pass data in a specific field and that data needs to be changed by SAP.

If at all that is the case, then have a separate export parameter and get the new value for the field in that parameter.

Regards,

Ravi