We’ve recently configured EDI integration for our order management process using Oracle B2B Gateway in Fusion Cloud 22D. Inbound 850 purchase orders from trading partners are being received and processed correctly into sales orders. However, the outbound 997 functional acknowledgements are not being sent back to trading partners, causing compliance issues.
Our trading partners are complaining they never receive confirmation that we’ve successfully received their orders. When I check the B2B message logs, I can see the inbound 850 messages with ‘Success’ status, but there are no corresponding outbound 997 messages in the queue or history. The trading partner profile mapping appears correct, and we’ve configured the agreement to require 997 acknowledgements for all inbound transactions.
I’ve verified that the EDI 997 configuration in the document type settings is enabled and the template is active. The B2B gateway logs don’t show any errors related to 997 generation. It’s as if the system is simply not triggering the acknowledgement process after successfully processing the 850. Has anyone experienced issues with automatic 997 generation in Oracle Fusion Cloud’s B2B integration?
I had a similar issue last year. Beyond the delivery channel, make sure your 997 document type is properly associated with the trading partner profile. In the B2B console, go to Trading Partners > Document Types and verify that the 997 document is enabled and linked to your EDI standard version (4010, 5010, etc.). Sometimes the 997 generation fails silently if the document type configuration doesn’t match the inbound 850 version.
Let me provide a comprehensive solution for your EDI 997 acknowledgement issues in Oracle Fusion Cloud.
Root Cause Analysis:
Based on your description, the problem stems from three configuration gaps: EDI version mismatch, incomplete outbound delivery channel setup, and trading partner profile mapping.
EDI 997 Configuration Requirements:
First, verify your 997 document type matches your inbound EDI version:
- Navigate to B2B Gateway Console > Administration > Document Types
- Locate the 997 Functional Acknowledgment document
- Ensure the EDI version is set to 4010 (matching your inbound 850)
- Verify the document definition references the correct 997 schema
- Confirm the document is in ‘Active’ status
Outbound Delivery Channel Setup:
The 997 requires a properly configured outbound delivery channel:
- B2B Console > Administration > Delivery Channels
- Create an outbound AS2 channel if it doesn’t exist
- Configure the channel with:
- Trading partner’s AS2 receiving URL
- Your AS2 identifier (AS2-From header)
- Partner’s AS2 identifier (AS2-To header)
- Signing and encryption certificates if required
- Test the channel connectivity using the ‘Test Connection’ feature
Trading Partner Profile Mapping:
Ensure complete bidirectional configuration:
- B2B Console > Trading Partners > [Partner Name]
- Under ‘Agreements’, verify both inbound and outbound agreements exist
- Inbound Agreement (850):
- ‘Generate Functional Acknowledgment’ = Enabled
- Document Type = 850 version 4010
- Delivery Channel = Inbound AS2 channel
- Outbound Agreement (997):
- Document Type = 997 version 4010
- Delivery Channel = Outbound AS2 channel
- Routing = Direct to partner endpoint
B2B Message Logs Verification:
To diagnose the exact failure point:
- B2B Console > Reports > Message Tracking
- Filter: Direction=Outbound, Document Type=997, Date Range=Last 7 days
- Check message status:
- If no messages appear: 997 generation is not being triggered (agreement issue)
- If messages show ‘MSG_ERROR’: Document type configuration problem
- If messages show ‘DELIVERY_FAILED’: Outbound channel issue
- Click message ID to view detailed error logs and payload
Validation Steps:
After making configuration changes:
- Request a test 850 from a trading partner
- Monitor B2B message logs for both inbound 850 and outbound 997
- Verify 997 appears in outbound queue within 2-3 minutes of 850 receipt
- Confirm partner receives 997 at their AS2 endpoint
- Review 997 payload to ensure correct acknowledgement codes
The key issue is that automatic 997 generation requires complete bidirectional configuration. The system must know not just to generate the acknowledgement, but also how to deliver it back to the trading partner using the correct EDI version and transport protocol.
Yes, the EDI version mismatch is likely your root cause. The 997 must match the version of the inbound document it’s acknowledging. If you receive a 4010 850, you must send back a 4010 997. To check message flow, go to B2B Console > Reports > Message Tracking and filter by direction=‘Outbound’ and document type=‘997’. This will show you if 997 messages are being created in the system but failing during delivery.
That’s a good point about the EDI version matching. We’re using 4010 for the 850 inbound, and I just noticed our 997 document type is configured for 5010. Could this version mismatch prevent the 997 from being generated? Also, where exactly in the B2B console can I check the message flow to see if 997 messages are being created but failing at the delivery stage?
The 997 acknowledgement generation is typically triggered automatically after successful validation of the inbound EDI document. If you’re seeing successful 850 processing but no 997 output, check your trading partner agreement configuration. Specifically, verify that the ‘Generate Functional Acknowledgment’ checkbox is enabled in the inbound agreement settings for each trading partner.
The 997 should use the reverse delivery channel configuration. If your inbound 850 comes via AS2, the outbound 997 needs an AS2 delivery channel configured in the opposite direction. Check your delivery channel settings in the B2B Gateway console. You need both inbound and outbound channels defined for bidirectional EDI communication. Also verify that the trading partner’s AS2 receiving endpoint URL is correctly configured in the outbound channel.