Quantcast
Channel: Jive Syndication Feed
Viewing all articles
Browse latest Browse all 10881

Field set as required is not validated

$
0
0

There are some concerns about "required" flag, available at metadata field configuration.

 

When going to SPRO -> SRM Server -> Cross-Application Basic Settings -> Extensions and Field Control (Personalization) -> Configure Field Control -> Configure Control for Fields on Item Level, a non mandatory field can be set as required.
For example, we can set BE_STGE_LOC as required for BUS2121.


However, when creating a shopping cart using a valid requestor who doesn't have any storage location stored in PPOMA_BBP, system does not perform field validation, informing end user that field hasn't been filled.

 

Actually this is the expected behavior from system.

 

When a non mandatory field is set as "required" at metadata level, this only means that wildcard (*) will be visible in this field. System will not perform any validation.
If validation is needed, custom BAdI or enhancement should be develop.


For additional information, read KBA 2024094.


Viewing all articles
Browse latest Browse all 10881

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>