The best way of figuring out ucm side tables for making back end db entries is to set systemtdatabase* tracing section along with Full verbose option . Then make a single entry from EBS Side and capture the data from ucm server logs .
Based on that you can write a batch script or PL/SQL procedure to achieve the requirement .
Note that this is not the best way to load data and attach / link them to EBS attachments .
We understand this is not the best way to link attachments to EBS. But we have bulk of contents migrated from another system to be attached to EBS transactions. So manually attaching them from screens is not an option.
We have one thing to confirm. Will updating UCM tables be sufficient to link the attachments? Or do we need to update any EBS or AXF tables also?
Yes Arijit, and thanks for the reply.
I feel, this would not be that easy... because if you see, the Managed Attachments and OAF configurations are bit complex and we not sure what tables get updated when attaching documents from EBS transactions...
I guess, we need to go in other way... like providing a link in EBS transactions for these documents and use the Managed Attachments for going further documents.
Customer also agrees this for the migrated documents. Whats your opinion on this!
When documents are attached using the "From Repository" option in Managed Attachments screen, the AFObjects table is populated with the application, businessobjecttype and businessobject along with ddocname. This is working for us when we are using a dummy transaction. Yet to explore a proper EBS transaction. But populating AFObjects with the right values should solve the re-attachment functionality.
AFKeys and AFGrants tables are also populated but these two tables don't need to be populated manually.
I understand from the discussion that you need to attach and image/document to EBS entity like Invoice, PO, etc which is stored in UCM.
you need should know the UCM - URL (a web location) of the document to be attached.
In EBS you have 3 tables which you should fill the data
fnd_documents: this table will have the details of the URL + some PK ID + security information about document
fnd_attached_documents: this table will have a relation between EBS entity and document PK ID
fnd_documents_tl: this table is having he details like language based name, etc + document PK ID.
If you fill in this then the EBS will show this as a WEB URL type attachment to respective entity.
I have tried a similar setup successfully, the integration is very loose, and it allows you to bulk load documents in UCM by simply modifying the AFObjects table,
You will first need to configure the forms you want with the MA solution using the mappings table for either Core Forms or OAF, once the form is configured and you have defined the primary keys and entity names to be used, you can attach documents to the EBS object from UCM, there are 2 ways to go about this:
1) You can manually add the link to the table, if the documents are already in UCM, you can enter the lines in the OFObject table giving the DDocName, the application name (EBS Instance name) , the Business Object Type (EBS entity, i.e. AP_INVOICES) and the BusinessObject (primary key, i.e. invoice number).
2) another alternative is that you can use idccommand to add the metadata to the documents you can update existing documents or check new ones by entring the values to the metadatafields dAFApplication, dAFBusinessObjectType, and dAFBusinessObject.