There are already some amazing blogs around Functional acknowledgement for EDI interfaces

The specified item was not found.

Functional Acknowledgement Status Reporting in sap PI 7.31 B2B add-on


For beginners in B2B integration,it’s still a challenge to distinguish between the approaches for sending 997 in inbound and outbound scenarios(personal experience 🙂 )


Thought of sharing these two different methods in a simple blog:

(Will take example of ANSI X12 EDI message)



Outbound Scenario:

-> Order change IDoc from SAP is transmitted to EDI VAN in form of EDI 860

->EDI 997 (to concede the receipt of EDI 860)  is sent back by vendors, this should update the status of Outbound ORDCHG IDoc from 03 to 16 (FA received)  

   one possible way is to translate incoming 997 to STATUS IDoc

Fa997_1.png


Outbound IDoc to EDI Mapping -> Send IDoc number(trailing 9 characters) in any of the control numbers ( this case we have per IDoc one EDI document)

  here, ISA13/GS06 can be mapped as per requirement

Fa997_3.png

Fa997_16.png


EDI 997 to STATUS IDoc Mapping ->


EDI 997 structure, has different AK levels, in this case we consider GS level

AK102 is mapped to ESTATS-> DOCNUM

Fa997_4.png

AK901 is mapped to STATUS field ( A (accepted) -> 16, R (rejected)-> 17))

Fa997_5.png

First Flow:

ORDCHG IDoc to EDI 860

Fa997_10.png

Module X12ConverterModule is used at the receiver side

Fa997_11.png

Second Flow:

EDI 997 to EDI separator receiver; EDI separator sender to STATUS IDoc (refer Inbound Scenario in the latter part)

Once the STATUS IDoc is delivered successfully, the status of original Outbound IDoc is changed to 16

Fa997_6.png

Inbound Scenario:


Reference-
B2B- EDI Inbound -Step by Step Configuration

Fa997_7.png


First Flow-> EDI 855 is sent from EDI VAN (any B2B sender adapter) to EDI separator receiver (no mapping is required)

Fa997_8.png

EDI separator receiver splits the received bulk messages and has a configuration to send back FA 997(options- required/ not required/ read from envelope (ISA segment)

Fa997_9.png

Second Flow -> EDI separator sender (855) to SAP (here, IDoc)->( mapping is required)


Fa997_12.png

Module X12ConverterModule is used at the sender side

Fa997_13.png


Third Flow-> EDI separator sender (997) to EDI VAN -> (no mapping required) 

Fa997_14.png

Reverse the sender /receiver ID of the first flow in the 997 configuration

Fa997_15.png


Note- No converter module is required here, as 997 is generated by adapter in raw EDI format.

Monitoring of acknowledgements is already covered in blogs related to B2B monitoring

Improved monitoring of B2B scenarios running on SAP NetWeaver Process Orchestration – part 2: local message monitoring capabilities

Note– FA 997 can also be configured based on partner profiles using TPM

Hope this helps 🙂

To report this post you need to login first.

8 Comments

You must be Logged on to comment or reply to a post.

  1. Haripriya Vrvb

    Hi Pooja,

    Thanks for this post. We are working on outbound B2B scenario and the 997 being sent from partner is not getting properly in PI monitoring.

    I understand that this blog talks about updating the status of the transaction at SAP ECC.

    But can also get similar status in PI.

    We are working with SAP PI B2B Add-on SP04

    regards,

    Haripriya.

    (0) 
  2. Ajay Garg

    Hi,
    In case we have some proxy to EDI scenario, can we still use STATUS Idoc for inbound 997 ?

    Else what is the good approach for handling 997 back.

    Kindly Advise.

    BR
    Ajay Garg

    (0) 

Leave a Reply