@ruben.maas Sir any suggestions on this

Hi, 

There is no access_group column on the shipment \ receiving screens. 

you can assign the access group to a user def field but that does not have any effect on data access logic. 

You can define a relation in custom meta data for shipment with relation type "Access”. this way you can validate the access group against the related parent object (request or part need for example). 

baseline uses same approach for TIME_COMMIT, for which the access group is validated against either the request, task, request_unit etc…

so you can also check how this is defined for TIME_COMMIT in the baseline meta data.

Cheers, 

Ruben

Thanks a lot @ruben.maas Sir for your help as always.

For example if I want to apply data access logic on shipment screen based on the place id  from's access group ,do I need to set up another relation in custom metadata of shipment table and add a access type relationship with place table and link shipments place id from with place table place id even if there is another default/join relationship between shipment table and place table in baseline fsm/custom metadata.