Each predefined transaction service is based on an Oracle Applications business object. Each service provides a business document structure that is based on the service’s associated business object. The sections in this guide that describe the individual predefined transaction services include descriptions of the services’ business document structures, and mappings to webMethods documents (if applicable).

For receive services, the business document structure includes a mapping from a webMethods document to the structure of the service’s business object as it is defined in the Oracle Applications open interface tables. If you want to change the mapping for a receive service, you can modify the structure of webMethods document by updating the receive service’s supporting bizDocMapping service; however, you cannot modify the structure of the side of the mapping that represents the Oracle Applications open interface tables. If you do modify the open interface table document structure, the service will no longer correctly map to Oracle Applications.

For send and query services, the business document structure represents the form of the document as it is retrieved from Oracle Applications. If you want to modify the business document structure for a send or query service, you must change the transaction definition for the service’s supporting getDocTxn or queryDocTxn service, refresh that service for the modified transaction definition, and then update the send or query service to reflect the change in the business document’s structure.