Update for Oracle B2B Documents
Manually update document in the Oracle Argus Safety database table B2B_ARGUSSAFETY_DOC under ESM Schema as mentioned in Oracle B2B UI > Configuration > Document.
The following table list the sample factory data:
Doc_ID | Doc_Type | Doc_Revision | Comments (Not a column) |
---|---|---|---|
1 |
AS_XmlDoc |
ArgusSafety_1.0 |
Xml for E2B Message and Acknowledgments |
2 |
AS_BinaryDoc |
ArgusSafety_1.0 |
Zip for PMDA E2B Message files |
3 |
AS_BinaryDoc |
ArgusSafety_1.0 |
PDF for E2B Attachments |
4 |
AS_EDIDoc |
ArgusSafety_1.0 |
EDI files |
- The Admin should update only Doc_Type and Doc_Revision columns from Oracle B2B UI.
- The Doc ID column must not be updated as new Doc ID is not supported.
- the mapping between Doc ID and other columns is assumed to be exactly as provided in
the sample above. For example:
- Doc_ID = 1 should not point to Binary Docs.
- Doc ID = 2 and Doc ID = 3 can point to the same or different doc type and doc version but neither of these should be left blank.
- Doc_ID=4 may be left blank, if there is no Reporting Destination with EDI Header and Footer configuration.
This information is picked up by outbound SOA Composite at run time to dynamically attach Document Type and Document Version properties to outgoing file via JMS.
Parent topic: Configurations for Oracle Argus Safety