AOI datatype member as input to itself

Anyone ever used an AOI datatype member tag as an input to an AOI of the same datatype?

To clarify what I mean...
When you create an AOI, RSLogix automatically creates an Add-On-Defined UDT and in order to use the AOI in the code, you have to define a tag with that datatype. Let's say I have an Input parameter in the AOI called "Enable" that's defined as a required parameter. Any issue with using the Enable tag that's a member of the datatype as the tag that is entered into the field for the "Enable" input outside the AOI? It doesn't cause any errors and I've done this before and everything seems fine but I'm curious if anyone else has seen issues when doing this.

I do this all the time, especially when there are more conditions to turn "AOI_EX1.Enable" true.

In your example I would just tie an "Always One" bit to the block call directly, but this example is oversimplified I guess .

Going back to basics, when you used to supply Input Parameters to JSR instructions, they simply stacked the data of the input parameters, to be "un-stacked" in the SBR of the subroutine.

Simply put if both "stacked" parameter tag or address and "un-stacked" parameter tag or address were valid, it worked.

Same thing happens with AOIs, if the Input parameter is valid (and a member of the AOI tag is a valid location), then you can effectively pass data into an AOI that already exists within the AOI tag !!