06-02-2008 12:24 PM
Hi all,
I am having trouble implementing a user-check for POD in our IS-U CCS installation release 46C / 4.64:
We want the fields for the point of delivery in transaction ES31 to be obligatory. I am using enhancement EEDMUI02, but unfortunately user-exit EXIT_SAPLEEDM_UI_EXT_TYP2_001 for customer specific checks is not triggered unless input has been made in the fields for POD. I do not want to modify the screen and make the fields input mandatory, because the field values usually can not be filled in manually but are determined by function EXIT_SAPLEEDM_UI_EXT_TYP2_002 (proposal for POD)
Has anybody done something like this before?
Thank you for your help & kind regards, Kathrin!
06-09-2008 3:46 PM
Hi,
I would use the logic showed and described in viewcluster VC_EUISTRUTYPE. When using this you will ALWAYS have the same logic. If you use something else - it will NEVER work within the master data generator (e.g. CRM replication) or any other transaction to assign an installation to a PoD (e.g. EEDM10).
So either use the user exits provided or the already included functionality where you have to do nothing except some customizing ...
Hope that helps
Uwe
06-03-2008 10:14 AM
Hi,
Try to user Exit EXIT_SAPLES30_001, of the Enhancement EMDI0001.
KR,
AAL!
06-04-2008 10:17 AM
Hi,
As said above, you can gow with the user exit but the validation will trigger only on save...
But if you want the validation to trigger immediately on the screen, then use the concept of field exit...You can use it since the release is 4.6C and SAP supports in the release...
You can access field exit from prg: RSMODPRF
Assign the validation for the field exit in the data element of the corresponding screen field...
Reward if useful
Regards
Shiva
06-04-2008 11:05 AM
Hi,
If you want to make the field mandatory then you can use Transaction variant (T code SHD0).
thanks and regards
Deepak
06-09-2008 3:46 PM
Hi,
I would use the logic showed and described in viewcluster VC_EUISTRUTYPE. When using this you will ALWAYS have the same logic. If you use something else - it will NEVER work within the master data generator (e.g. CRM replication) or any other transaction to assign an installation to a PoD (e.g. EEDM10).
So either use the user exits provided or the already included functionality where you have to do nothing except some customizing ...
Hope that helps
Uwe