My Oracle Support Banner

Document Type customization fail to receive messages. (Doc ID 371055.1)

Last updated on APRIL 23, 2019

Applies to:

Oracle B2B 10g (Business to Business) - Version and later
Information in this document applies to any platform.


The environment is set as follows:

Create 3A4 collaboration with V02.00 using standard naming convention for document type. 
Create another 3A4 collaboration. with Version V02.03 within same doc protocol revision tab (V02.00)
B2B will not allow to create the same even with different version of document type.
Collaboration will be possible only with different names for document type.

For eg:
RequestPurchaseOrder instead of Pip3A4PurchaseOrderRequest & PurchaseOrderConfirmation instead of Pip3A4PurchaseOrderConfirmation.

Send a 3A4 request payload
Encountering document type mismatch error while receiving PO confirmation from trading partner.

3A4 collaboration was created with customized names for PO request(RequestPurchaseOrder instead of Pip3A4PurchaseOrderRequest) & PO confirmation (PurchaseOrderConfirmation instead of Pip3A4PurchaseOrderConfirmation)event.
The outgoing PO request is happening successfully, but the PO confirmation is failing giving document type mismatch error.
The incoming message is referring root element of the payload for recognizing the document type which is always Pip3A4PurchaseOrderConfirmation while internal definition have PurchaseOrderConfirmation as document type name.
Renaming of document type in B2B is failing at deployment due to already existing definition for V2.00

3A4 acknowledgement will result in the following error :

AIP-51905: Document type name Pip3A4PurchaseOrderConfirmation and revision V02.03 does not exists.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.