This discussion is archived
6 Replies Latest reply: Apr 22, 2013 10:26 AM by Rakesh JS RSS

B2B Gateway fails to generate xml for 997

Rakesh JS Newbie
Currently Being Moderated
Hi All,

i am facing a peculiar issue with one of my test B2B instance, where xml for 997 EDI X12 file is not getting generated. The EDI 997 file is getting picked up however it fails to generate the application message. there are no errors in the report as well. When i click on the details link on the reports page for the 997 message the application message link is not active and doesnt redirect to the application message details pop-up on clicking it.

Could any of you please suggest why this issue is occuring.. it ran in my dev instance perfectly...

Also please suggest if more details could be found in any log files of B2B.


regards
Rakesh
  • 1. Re: B2B Gateway fails to generate xml for 997
    Rakesh JS Newbie
    Currently Being Moderated
    Any suggestions please..
  • 2. Re: B2B Gateway fails to generate xml for 997
    Rakesh JS Newbie
    Currently Being Moderated
    all,

    Need help desperately out here!!!
  • 3. Re: B2B Gateway fails to generate xml for 997
    Anuj Dwivedi Guru
    Currently Being Moderated
    Rakesh,

    In the corresponding request agreement (for e.g. - 850), select "No" in "FA Handled Automatically" drop-down. SAVE+VALIDATE+DEPLOY the request agreement and test again.

    Regards,
    Anuj
  • 4. Re: B2B Gateway fails to generate xml for 997
    987937 Newbie
    Currently Being Moderated
    Your real problem is the configuration...

    You need to go to the Configuration tab under Adminstration, and under the Acknowledgment section of the page, set the "Notify Inbound Functional Acks" and the "Functional Ack handled automatically" to "true". Otherwise the Application message does not get generated for your inbound 997s.
  • 5. Re: B2B Gateway fails to generate xml for 997
    Anuj Dwivedi Guru
    Currently Being Moderated
    Your real problem is the configuration...
    You need to go to the Configuration tab under Adminstration, and under the Acknowledgment section of the page, set the "Notify Inbound Functional Acks" and the "Functional Ack handled automatically" to "true". Otherwise the Application message does not get generated for your inbound 997s.
    And how did you reach to this conclusion? Those are global settings and are used for different purpose -

    -----

    Notify Inbound Functional Acks - If set to true, B2B sends an acknowledgment notification to the application when a functional acknowledgment is received.
    When Functional Ack Handled by B2B is set to false, then Notify Inbound Functional Acks must be set to false also for the inbound FA to be sent to the back-end application. If Notify Inbound Functional Acks is set to true (while Functional Ack Handled by B2B is set to false), then the incoming 997 (FA doc) generates only a notification and the 997 document itself is not sent back to the back-end application.

    Functional Ack Handled by B2B - To specify how a functional acknowledgment is handled, set this property to true or false.
    If set to true, then B2B autogenerates the functional acknowledgment (FA) message for inbound EDI and HL7 messages. Inbound FA messages are consumed when this option is true.
    When this option is set to false, B2B does not autogenerate the FA document. The back-end application (middleware) must generate the FA and provide it to B2B as an outbound message. When option is set to false, inbound FA documents are passed back to the back-end application.
    If the document does not require an FA (as indicated by the agreement-level setting), then this option is ignored. The default value for this property is true.
    If the FA is marked as expected in an agreement, then the message is placed into the MSG_WAIT_FA state and the back-end application is expected to generate the FA and push it to B2B as an outbound message back to the partner.
    See Section C.1, "Properties To Set in Fusion Middleware Control," for more information.
    When Functional Ack Handled by B2B is set to false, then Notify Inbound Functional Acks must be set to false also for the inbound FA to be sent to the back-end application. If Notify Inbound Functional Acks is set to true (while Functional Ack Handled by B2B is set to false), then the incoming 997 (FA doc) generates only a notification and the 997 document itself is not sent back to the back-end application.
    The following limitations apply when generating the FA from the back-end application:
    The FA is correlated with the original message based on the ReferToMsgID value set in the enqueue properties. The FA is correlated based on control numbers also.
    If the FA indicates that there was an error in the received message, the status of the correlated message is not updated to indicate an error. The correlated message is updated to MSG_COMPLETE.
    These limitations are not present when the FA is generated by B2B (that is, when this property is set to true).

    http://docs.oracle.com/cd/E28280_01/user.1111/e10229/bb_config.htm#CEGEADFJ
    -----

    Regards,
    Anuj
  • 6. Re: B2B Gateway fails to generate xml for 997
    Rakesh JS Newbie
    Currently Being Moderated
    thanks All... in my current scenario i set the FA handled automatically to false in the config section under administration. I have a 997 response only for an 824 msg.. however thanks for all the comments as it gives varied perspective to the problem...

    regards
    Rakesh

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points