Thanks for the response.
Are you on the AIF development team by any chance?
The reason I ask is that I'd like to make a suggestion for a future development. It may be in version 3.0 but I haven't had a chance to play around with 3.0 yet.
For PI proxy interfaces, I see AIF has the ability to generate structures automatically based on the PI development. This greatly simplifies the creation of those structures in the ABAP stack.
For inbound interfaces specifically, I really like to keep control of the interface in the ABAP stack. So what I typically do is initiate the PI data transfer from a Z-program. That way the user has the ability to trigger the job on an ad-hoc basis as well as having it scheduled to run periodically.
Since I do this, AIF Sees this as an OUTBOUND interface, not an inbound interface, and generates the structures as a destination structure instead of a source structure.
What would be great is the ability to designate the structure as a source or destination structure. Does that make sense?