One of the main benefits of using the Oracle ERP Adapter is the capability to easily receive the Callbacks of a previously triggered FBDI job. Triggering the FBDI job is great, but without knowing the result, the whole process lacks consistency.
This post will focus on the Callback. Have a look at this one, that covers the mechanism to Import files into ERP.
Enable Callback
We need to modify the Import Integration from the previous post, and that is selecting the option Enable Callback. This is quite simplified now. In the past we would need to refer to the Integration Name and Id for this to work. Now, the CallBack is an Event published by ERP.
Then we create a new Integration to handle the Callback.
The option is :”Receive Callback Message upon completion of FBDI bulk Import Job….”
And the Process is Import Journals – This was the process invoked in the previous post.
The Idea is to decide what to do when the Callback arrives. In this case I use a Switch Action to decide between:
- Do Nothing
- Notify Users
For this I check on the SUMMARYSTATUS Attribute.
Execute the process
When this is put to test, we see in the Monitoring page that the callback has an Error Status. This means the notification branch of the Switch activity will kick in and send an outbound email.
Worthwhile mentioning that the message structure coming from ERP contains several steps of the FBDI process, each one with an individual status, which gives a better insight on where the issue occurred.
The NotifyUSers action sends an email with a simple subject/body and uses as attachment the file reference coming with the Callback.
I did not look at the contents of the attachment, as it comes encoded – I guess I would need an extra step in the Integration, but that was out of scope for this post 🙂
Handling the callback is the final piece of the puzzle for the full automation of the FBDI process for Oracle ERP.