Inconsistent Function Group in QA, but OK in DEV: missing include for FM.

[josgabriel_martnez]

Hi all,

A friend of mine has this problem:

He received an incidence, where was discovered an error in a Function Module (FM): The Function Group (FG) is inconsistent in QA (missing include for "new" FM), but when he checked out the FG and FMs in DEV, everything is OK, the FG is consistent in DEV.

Is not possible to take a look at the source code of the regarding FM in QA because inmediatly appears an error (apparently somebody created this one before, he don't have enough information). When reading the procedure described by error message, is suggested to "Repair" the FG from the menu in SE37.

But, how can one "repair" the FG in DEV, where is consistent, if everything is OK ??(the FG is inconsistent in QA, repair is not allowed there).

He tried to include the FG in a new change request (CR), activating the whole FG from SE80, but nothing happens. After transporting this CR, the error still happens.

Any other way to solve this?

Regards,

José Gabriel.

[Former Member]

Hi, in se80 give the FG name and click on main program, then click on PROGRAM - GENERATE, then move it to QA. i think it vl solve the problem.

[ThomasZloch]

I was about to suggest what you mentionend in your last sentence. Can you doublecheck that the repair transport actually contained the object key R3TR FUGR <name of FG> ?

In case it contained a number of LIMU keys, than you should try again using that R3TR key.

Greetings

Thomas

Edit: it would also be helpful if you could post the actual FG name and the exact number and text of the error message that occurs.

[josgabriel_martnez]

OK, my friend told me that the issue was solved.

Apparently, the previous CR took effect much later and the FG was updated later too. The FM and the whole FG is consistent in QA now.

He did not perform anything else, so it was not necessary try to "generate" nor create a new CR, it's very strange.

I was thinking about tell him that could create a new CR, including two entries: the FG ( FUGR ) and the partial object (LIMU - FUNC), but is not necessary.

Thanks anyway for your advices.

By the way, the error message number was: FL023.

Regards,

JG.

[josgabriel_martnez]

The solution, apparently, was only wait a time until the previous CR really updated the FG.

[Former Member]

Your FM' include may not be present in the Function Group L[YOUR_FUNCTION_GROUP]UXX include in QA.

In that case, you'll have to create a transport request and add the LIMU REPS L[YOUR_FUNCTION_GROUP]UXX object.