I'm fairly new at this but what I've seen is under the Logic dropdown > MAP PLC/SLC Messages. If there is data there attached to a file number, then in DeltaV the messaging class was Class 3 with PCCC.
One of our other PLC programs one of the routines in the tree handles DCS Comms. A MOV block takes information from a transmitter and moves the value to a tag in an array in controller tags. in the DCS the dataset is configured as UCMM with Logix Tags and the Logix tag name is used matching the tag name in the PLC array. With other parameters in the dataset the PLC is able to send the value to the DCS. (Rack#, slot#, data type.) For example the tag name in the PLC could be _TX_DCS_FI-1234 and this tag name would be used in the DCS.
Another one similar to the first has controller based tags for DCS comms and MAP PLC/SLC with a file#. ST is used in the PLC to write to the controller tag array. Class 3 with PCCC is used in DCS. For example the PLC could have an INT array tag called _TX_DCS with 50 elements in the array. each element corresponds to a sensor or signal. the file number in the MAP PLC/SLC could be 11. but if you have 50 elements in the PLC array then you would want to grab 50 values in the DCS, and these would be made into signals under the data set.
I had to set up a dataset on a new Logix 500 controller. This was trial and error with data types, file type, and file number. I managed to get data from file number 7 which comes from integers and made it a 8bit unsigned integer. I couldn't spend more time on it to figure out how I got it to work, but it does. Maybe I will revisit it to learn.
If you saying that its explicit messaging, I know there is Class 3 explicit, where my examples are Class 3 with PCCC. But, hopefully I have given you something useful to work from.