I am familar with the practice of attaching custom data in an eConnect transaction as documented here:
And illustrated well here:
But outside of transactional consistency, what is the advantages of this method over simply calling a stored procedure directly in GP? In my case, when inserting a budget master record, I need to insert a row of data into a standalone table inside of GP . I'm having a hard time justifying the extra work of attaching the extra xml over just inserting the row directly.