topic Re: FM in background task with function module that was not remote enabled. in Application Development and Automation Discussions

FM in background task with function module that was not remote enabled.

dave_szurszewski — Mon, 22 Feb 2016 00:49:16 GMT

Hello All,

Code was moved to production that was calling a non remote enabled FM in background task. By the time the error was caught over 15000 abends occurred. These 15000 background calls are now in tables ARFCSSTATE and ARFCSDATA but cannot be processed successfully. We plan to set the offending function module to remote function and transport. My question is, since it is a few days since these calls went into error what affect does it have on the logical unit of work? is it possible we will be updating with old data?

Thanks in advance, Dave

Re: FM in background task with function module that was not remote enabled.

paul_bakker2 — Mon, 22 Feb 2016 01:07:18 GMT

Hi,

Yes, you will be updating with old data - of course! But that may not be a bad thing, if the abends stopped all subsequent updates as well.

You might want to replicate these types of errors in Test (I assume the abends also happen there) and see what happens when you try to re-execute the ARFC updates after the fix.

It's amazing that this FM issue wasn't noticed in the Test system. Or was a transport missed when it moved to Production?

cheers

Paul

Re: FM in background task with function module that was not remote enabled.

dave_szurszewski — Mon, 22 Feb 2016 12:33:05 GMT

Hi Paul,

Yes, it was amazing. This occurred due to flawed test scenarios. The call to the in background task FM was in material master enhancement spot. transactions MM01 and MM02, also BAPI_MATERIAL_SAVEDATA runs through the same enhancement.

Testers ran MM01 and MM02 these completed without error, the background call abended but is not apparent to the user. They moved to production and a mass update program that calls BAPI_MATERIAL_SAVEDATA was used to update 15000 materials. High number of abends catches everyones attention! The program and all calls to BAPI_MATERIAL_SAVEDATA completed without error. Now we have 15,322 entries that the system is trying to process!

We are setting up the scenario in the Test system and verifying results prior to moving the fix to Production. I will post our results

Regards, Dave

Re: FM in background task with function module that was not remote enabled.

RaymondGiuseppi — Mon, 22 Feb 2016 13:15:25 GMT

Well checking SM58, ST22, WE06 and SM21 during integration tests is not a bad idea, no alert management in system, and nobody checked that final data was wrong in database, no test scenario writing activity?

Then it depends on what you tried to do in the theorically RFC enabled FM, if that's just new records (e.g. add some plant to material) or filling customer table then no problem, else some data may no longer be changed or have already been changed with more recent value, e.g. once movement or purchase order is created on material reference.

Regards,

Raymond

Re: FM in background task with function module that was not remote enabled.

dave_szurszewski — Tue, 23 Feb 2016 13:09:09 GMT

Setting function module remote enabled resolved the issue. As the FM was used to update a few characteristics in classification based on basic data fields there was no issue with incorrect or old data. we have maintenance reports that were used to correct the data.

Regards, Dave