HolderAndrew
Well Known Member
Hi All,
Since the old days (B7321-->Xe) we have always had the ability to insert records directly into F986113 from outside of OneWorld in order to trigger UBE subsystem processes effectively. This was done by concatenating the required RI DSTR values into a pipe separated string and assigning it to the SRVBLOBA column along with all the other necessary columns (PID, VERS, ENHV, etc...).
In 811 this is no longer possible as the SRVBLOBA column is set to *POINTER when a record is inserted via the standard api ubeReport_AddSubsystemRecord. I have a few questions which I would be very grateful if anybody out there knows.
Q) Where is the RI DSTR information now stored?
Q) Does anybody know of a method to insert records into F986113 successfully from outside EnterpriseOne 8.11 (or maybe 8.10)?
I suspect that we need to use interoperability method (using COM wrappers) but then this takes time for the connection to take place before the BSFN api can be called successfully.
I was hoping that we could maybe have a table trigger to call the api upon an insert action on a temp file but this can only work inside of E1?
Any ideas would be appreciated.
Regards
Andrew Holder
Since the old days (B7321-->Xe) we have always had the ability to insert records directly into F986113 from outside of OneWorld in order to trigger UBE subsystem processes effectively. This was done by concatenating the required RI DSTR values into a pipe separated string and assigning it to the SRVBLOBA column along with all the other necessary columns (PID, VERS, ENHV, etc...).
In 811 this is no longer possible as the SRVBLOBA column is set to *POINTER when a record is inserted via the standard api ubeReport_AddSubsystemRecord. I have a few questions which I would be very grateful if anybody out there knows.
Q) Where is the RI DSTR information now stored?
Q) Does anybody know of a method to insert records into F986113 successfully from outside EnterpriseOne 8.11 (or maybe 8.10)?
I suspect that we need to use interoperability method (using COM wrappers) but then this takes time for the connection to take place before the BSFN api can be called successfully.
I was hoping that we could maybe have a table trigger to call the api upon an insert action on a temp file but this can only work inside of E1?
Any ideas would be appreciated.
Regards
Andrew Holder