Skip to Content
Author's profile photo Former Member

Effect of ‘Field Only Known in Customer Exit’

The document describes the issue occurred in datasource because of Check of flag on Field Only Known in Customer Exit and its solution.

Fields with Field Only.. check  are not processed during standard extraction, but can be processed in customer exits, BADIs (Business Add-ins), or Business Transaction Events.

Issue that we can face on check of Field Only..

If developer has checked the flag “Field Only..” in RSA6 and the field is also used for selection purpose then selection values will not work in extraction process. By default these values are not passed to the extractor from field list and selection table.

Following example that explains in detail:


Check “Selection” flag of any two fields.

Check “Field only…” flag at one of the selection field and not on other field.


Save and activate datasource.

Extract data in RSA3 with no selection on any field.


Full data is selected in RSA3 extractor.

Now give value in BUKRS which was made unchecked in “Field Only..“ flag and extract data.


In RSA3 we can see, field whose “Field Only..” flag was unchecked is fetching corresponding data on giving selection.

Now try with FKTYP selection values.


FKTYP selection is not working; extractor is fetching full record from tables. Reason is, checking “Field Only..” flag in FKTYP in RSA6.

To resolve data fetching issue on selection parameter simply  do not check the “Field only…” flag in RSA6 of datasource. With this setting system will allow passing the selection table to extractor and fetch corresponding records.

Points To Keep in Mind:

1. While checking Selection flag do not check the “Field only known in Customer Exit” flag.

2. Do not use unnecessary ‘Selection’ fields in datasource as Extractor checks the selection table entries while fetching record.


Ankit Gupta

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.