Thanks for persisting with this issue for sometime :) . We set the LC as Internal and used "%FROM_PARTY%_%TO_PARTY%_%DOCTYPE_NAME%_%DOCTYPE_REVISION%_%TIMESTAMP%.xml" as the filename format and Agreements are being Picked appropriately .
1. Does Oracle 11G support “CONVERSATION_ID” in the filename format for FTP/SFTP/File Protocols ?
We require this property to correlate responses with requests .
As of now we are extracting the conversation id of outbound requests using the format "%INREPLYTO_MSG_ID%" and stubbing the responses using JMS Stubs and are using this value in header property “CONVERSATION_ID” . So it would have been useful if “CONVERSATION_ID” was supported in filename formats so that we could have used file/ftp/sftp protocol .
As an alternative we can try correlating the requests and responses during configurations using Correlation tab while creating Document Definitions . But we would like to do minimal configurations and let file/ftp/sftp pick up extract the conversation id .
2.In Oracle 10G for Email/FTP Outbound for Agreement Pick Up , below JMS properties would have been enough :
In Oracle 11G it requires Doctype Name and Doctype Revision as well . Doctype Name we can atleast extract from the Action sent by backend components . But DocType Revision is something that is confined only to Oracle and we cant expect Backend components to send Doctype Revision but its a mandatory property for the agreement to be picked without which we are getting the below error :
Description: Agreement not found for trading partners: FromTP BTGS, ToTP EmailTP with document type CreateSimpleSREmailResponse-null-OUTBOUND.