Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Field exits

Former Member
0 Likes
733

Hi All,

We have a requirement in our project to create field exits for data elements.Presently we are working on SAP R/3 4.6c system and client is trying to upgrade to ECC 6.0,We want to know the effect of upgrade on field exits and will these userdefined field exits be available in ECC6.0 and if so do they require any modifications to be done to make them work in ECC 6.0.?

1 ACCEPTED SOLUTION
Read only

Clemenss
Active Contributor
0 Likes
698

Hi shiva,

Field exits are no longer supported by SAP though they still work.

I'm convinced they will work with ECC6.0 as long as you have pure screens processed via SAPGUI or BDC.

As soon as anything changes (WEB interface, GUI control,...) they will not work any longer.

If there is any possibility, try to choose anything different from Field exits. I don't know your business scenario. Possibly you can use conversion exits (on domain level).

The conversion exit will be triggered whenever a screen field (for the dataelement with the linked domain) is processed.

The conversion exit could possibly do what the screen exit should have done. Conversion exits are deeply intergrated into SAP system so they will be supported forever(?).

Regards,

Clemens

Hi All,

We have a requirement in our project to create field exits for data elements.Presently we are working on SAP R/3 4.6c system and client is trying to upgrade to ECC 6.0,We want to know the effect of upgrade on field exits and will these userdefined field exits be available in ECC6.0 and if so do they require any modifications to be done to make them work in ECC 6.0.?

4 REPLIES 4
Read only

Clemenss
Active Contributor
0 Likes
699

Hi shiva,

Field exits are no longer supported by SAP though they still work.

I'm convinced they will work with ECC6.0 as long as you have pure screens processed via SAPGUI or BDC.

As soon as anything changes (WEB interface, GUI control,...) they will not work any longer.

If there is any possibility, try to choose anything different from Field exits. I don't know your business scenario. Possibly you can use conversion exits (on domain level).

The conversion exit will be triggered whenever a screen field (for the dataelement with the linked domain) is processed.

The conversion exit could possibly do what the screen exit should have done. Conversion exits are deeply intergrated into SAP system so they will be supported forever(?).

Regards,

Clemens

Read only

Former Member
0 Likes
698

Hi clemens,

Acc to my requirement, i need to stop the user from using suppose a particular order type(AUART)= 'NUPM' across various transactions(IW31/IW31...etc). so i use a field exit and validate if user enters order type = NUPM, then raise an error message....across any transaction.

Hence i am required to validate the data element using field exits

Regards

Shiva

Read only

Former Member
0 Likes
698

Perhaps you will find some information in OSS note 29377

Read only

Clemenss
Active Contributor
0 Likes
698

Hi,

I think this should be done in Customizing. There is a flag to mark an order type for manually processing not allowed.

Don't know exactly where, but I know that an order type can be excluded from manually processing.

And there is a whole lot of authority restrictions possible.

Check with your functional guys!

Regards,

Clemens