topic Re: reg. Screen Element attribute - FctCode in Application Development and Automation Discussions

reg. Screen Element attribute - FctCode

Former Member — Fri, 19 Aug 2016 08:18:57 GMT

hi Friends,

Issue was on selection screen field checkbox - ideally if User press checkbox field at report selection screen, next screen has to trigger - analyzed and found out that the FctCode been missing at screen element level attributes and maintained the same and moved the Transport to Quality along with other changes.

But

Rest of all code changes replicated fine in Quality except the FctCode - it's blank when i try to find it at element attributes screen at Quality system !! Even i can see the specific screen number been saved at task level of that TR !

here is the snapshot of screen element attribute:

'HIS' been missing in Quality system after TR movement.

Any inputs on this, please

Regards,

Suren.

Re: reg. Screen Element attribute - FctCode

RaymondGiuseppi — Fri, 19 Aug 2016 08:23:52 GMT

Did you check sequence and log of import in quality?

Re: reg. Screen Element attribute - FctCode

Former Member — Fri, 19 Aug 2016 08:56:13 GMT

hi Raymond,

Checked the sequence and Transport log at Quality and i could see the status 'screen and program successfully generated'.

And reg. sequence - in object list, first came with screen no. and then report name.

Pl let me know for any inputs on correct sequence expected, thanks.

And i thought of adding Object directly at TR level i.e., Screen/LIMU/DYNP - any ideas pl

Regards,

Suren.

Re: reg. Screen Element attribute - FctCode

RaymondGiuseppi — Fri, 19 Aug 2016 09:50:07 GMT

I was directing at sequence of requests not objects in the same request...

Could you execute a remote comparison of version for the dynpro, does the last version of development match the current version in target system?

You could also transport either the dynpro LIMU/DYNP or the whole program R3TR/PROG or FUGR.

Regards,

Raymond

Re: reg. Screen Element attribute - FctCode

Former Member — Fri, 19 Aug 2016 10:38:49 GMT

hi Raymond,

I just included the Object R3TR/PROG/progname in new Transport and released to Quality intending the generation of screen occurs and FctCode replicates...but again failed !!

FctCode value is blank at screen level at Quality...please suggest.

Regards,

Suren

Re: reg. Screen Element attribute - FctCode

RaymondGiuseppi — Fri, 19 Aug 2016 12:21:46 GMT

I just notice the

at report selection screen,

Did you modify a generated selection-screen , in this case the post-import activation will regenerate the dynpro and erase your changes, try to activate the report in development system?

Re: reg. Screen Element attribute - FctCode

Former Member — Mon, 22 Aug 2016 06:50:55 GMT

hi Raymond,

I already did the report activation before and included the Object in TR as R3TR/PROG/prgname and moved to Quality, but still the issue persists - function code is still blank !!

the above highlighted 'HIS' is missing in Quality system - hence no response at report selection screen when user clicks on this checkbox.

Please suggest.

Regards,

Suren.

Re: reg. Screen Element attribute - FctCode

RaymondGiuseppi — Mon, 22 Aug 2016 06:59:14 GMT

If this is a selection-screen you MUST define the function code in the source, else further activation implicit (SE37) or implicit (Import, Impact of another modification) will regenerate the dynpro.


PARAMETERS: p_his AS CHECKBOX USER-COMMAND his.

Regards,

Raymond

Re: reg. Screen Element attribute - FctCode

Former Member — Mon, 22 Aug 2016 11:54:07 GMT

Able to resolve the issue.

While saving the TR at change mode of Screen attributes screen, it needs to use 'Transfer' button - you can find this option only in change mode of screen level attributes. so, only the TR with screen will serve the purpose.

Regards,

Suren.

Re: reg. Screen Element attribute - FctCode

Sandra_Rossi — Mon, 22 Aug 2016 14:10:30 GMT

BUT you should never do that ! Next time you activate the program, your modifications (of the selection screens) will be lost ! In one year, nobody will remember that the selection screen has been changed.

Re: reg. Screen Element attribute - FctCode

Former Member — Fri, 26 Aug 2016 08:11:09 GMT

This issue raised as part of Upgradation (version upgrade), post-upgradation this issue been raised and can handle this way considering this as exceptional - hope you understand that this is not part of any development.

Regards,

Suren.

Re: reg. Screen Element attribute - FctCode

RaymondGiuseppi — Fri, 26 Aug 2016 08:25:28 GMT

Til next upgrade/SP/SAINT which can activate the program again...

Re: reg. Screen Element attribute - FctCode

Former Member — Fri, 26 Aug 2016 09:04:56 GMT

As part of upgradation process, it needs to maintain Redbook entries to handle these exceptions - hence for this custom program screen changes, i made an entry stating the function code issue with detailed documentation also at modifcation history of the program and this serves the purpose.