Sure.
If you read the documentation for Internal Communication, you will get to know that Source and Target BO structures should be same or atleast at the same level of heirarchy for the message to be sent.
Development Points:
- Create a Proxy BO (Custom BO) which is of same structure as of Supplier Invoice BO.
- Action points from your side is to maintain that 2nd point which I said earlier i.e, you need to create an A2A between your Proxy BO and SupplierInvoice BO. Check the studio documentation if you are not sure of Internal Communication.
- If you don't want Proxy BO instance soon after the SI is saved, then you will have to create SI XBO and its BeforeSave event. Send the UUID of Proxy BO's in the A2A mapping so that you can retrieve that instance in the Before Save of SupplierInvoice XBO and delete it as we will not have any use of it anymore.
- Next step is that you should write code to create instances of your Proxy BO from Origin BO's actions/events. You know where to write as you already wrote code to create SI instances. Delete / Take a backup of that code which you wrote for creating SI instances and replace it with code that creates your Proxy BO's instances.
Screenflow:
- Once user does something that invokes your Origin BO's code of creating Proxy BO's instances, a Proxy BO instance would've been created.
- The A2A which was setup by you triggers a call to Supplier Invoice BO automatically.
- Once the Supplier Invoice instance is saved successfully, Proxy BO's instance will get deleted if you followed 3rd bullet in above Development Points.
Clear ???