topic Re: Screen/dynpro text fields with active foreign key flag in Application Development and Automation Discussions

Screen/dynpro text fields with active foreign key flag

DanielB — Wed, 27 May 2020 08:28:16 GMT

Hello,

what sense does it make to set the foreign key flag for screen/dynpro fields of type "Text"?

I've just checked some SAP standard dynpros and found it for example in:
SAPMV45A Screen 4303: "Text"-Fields VBAK-BUKRS_VF, VBAK-LANDTX, VBAK-STCEG_L, VBKD-LCNUM
SAPLMEGUI Screen 1221: "Text"-Fields MEPO1222-EKORG, MEPO1222-EKGRP or MEPO1222-BUKRS

Regards
Daniel

Re: Screen/dynpro text fields with active foreign key flag

Sandra_Rossi — Wed, 27 May 2020 11:46:44 GMT

Press F1:

Foreign key check of Dictionary is active

If a foreign key check is defined for the ABAP/4 Dictionary field, it is always active in the screen. When the screen is generated, a chain of FIELD statements and a SELECT statement are generated at the same time. Depending on whether the field with the foreign key check is a loop field or not, the chain is generated in the flow logic either after the LOOP statement or after the PROCESS AFTER INPUT. This processing sequence cannot be altered.

If you do not want the foreign key check defined for an ABAP/4 Dictionary field, you can deactivate this. In this case, you can still display the possible values with F4.

Re: Screen/dynpro text fields with active foreign key flag

DanielB — Thu, 28 May 2020 06:47:42 GMT

Hello Sandra,

I know the meaning of a foreign key check and I already had a look into the F1 help, but I wonder why setting a foreign key check on a label/text field, which can't be changed (it's just a output field and not an input field). You also have no value help on a text/label field.

I found a note, which also describes that a foreign key indicator on a text field isn't correct: 545761 ("Symptom: On the qantity subscreens of Transaction CO11N indicator 'Foreign key check' is set for text field AFRUD-GRUND. This does not make any sense as you cannot make any entries can be made in a text field.").

But I found this in several SAP standard screens as I mentioned and you can see in my screenshot, so why!?

Thanks & regards Daniel