997

[Former Member]

Hi ALL,

Could you please explain 997 Functional acknowledgment.How the Functional acknowlegdment message is created and how it works?.

thanks

walter

Edited by: WALTER STEPHEN on Jun 22, 2009 11:12 AM

[Former Member]

Hi walter,

<Read Rules of Engagement>

thanks,

Edited by: Prateek Raj Srivastava on Feb 3, 2010 12:36 PM

[Satyagadadas]

997 Functional ack will be generated for the documents you are sending for ex: 850/860.

Ex:

If you are sending 850 to 3rd party vendor, they will send you 997 in a separate coomunication once they are able to upload that EDI file.

Once you process 997 to your R/3 system. The idoc which is holding that 850 documnet data status will be changed to "16" from "03".

[Former Member]

<Read Rules of Engagement>

please send the scenario with fuctional acknowledgement and PDF.

THANKS AND REGARDS

WALTER

Edited by: Prateek Raj Srivastava on Feb 3, 2010 12:37 PM

[Former Member]

Hi,

Can you send these documents to me ?

my id is <Read Rules of Engagement>

Thanks in advance.

Regards,

Vinay

Edited by: Prateek Raj Srivastava on Feb 3, 2010 12:35 PM

[Former Member]

Hello,

997 is functional ack generated for ANSI X12 EDI messages in general

In PI there are EDI adapters which takes care of generating the same

for. e.g Seeburger is an adapter which needs to have a separate licencse for using the same with PI takes care of generating Functional ack for the EDI message sent to PI

HTH

Rajesh

[former_member185881]

This message was moderated.

[Former Member]

Hi Walter,

The Functional Acknowledgement solution enables users to create ANSI X.12 997, EDIFACT CONTRL and other acknowledgement messages for received documents.

These messages are used to let the business partner, (who originally sent the documents), know whether the processing of the documents has been successful, or whether the documents contained any errors.

2. The solution not only creates the EDI acknowledgements, but also performs interchange splitting by document type.

The input message (interchange) normally contains more than one document of different types. The solution creates a new XI message for each correctly acknowledged document.

Flow of Functional Acknowledgment:

1. Firstly a new EDI Interchange has been

sent to SAP XI using one of the adapters.

An EDI Interchange is, e.g., a file, which can contain one or more EDI

Documents of one or several types. E.g., an interchange can contain 3

orders and 2 invoice.

2. The message is processed by the module

processor in the communication channel. The modules will create a

SEEBURGER proprietary Functional Acknowledgement.

This is an XML document containing information about accepted and

rejected EDI documents in the original EDI Interchange.

3.

The functional acknowledgement must be sent back to the business partner. Before this can be done, the acknowledgement must be converted from SEEBURGERu2019s proprietary format to one of the EDI formats (for example 997 in ANSI X.12 or CONTRL documents in Edifact).

This is performed by the XI Mapping tool inside the Integration Server . However the XI Mapping tool can only create XML documents (not EDI documents), as a result it creates an XML representation of the EDI acknowledgement.

4. The Acknowledgement is routed using the XI configuration objects (receiver determination, receiver agreement ...) and passed on to an outbound communication channel, which should send the acknowledgement back to the business partner.

This channel contains a module chain, which must perform the final conversion from the EDI documentu2019s XML representation to the final EDI format. This is performed by means of a 1:1 mapping.

5. In the final step the receiver adapter sends the acknowledgement to the business partner using one of the communication protocols.

Thanks & Regards

Kunaal

[Former Member]

Hi

thanks for your response.

The flow of scenario is EDIXIR3

Message is shipping schedule (862)

Here the doubt is 862 messages are sending from EDI system to R3 system through XI.

One functional acknowledgement should send back to EDI system.

1. How the functional acknowledgement should generate the message?.

2. Is it ALE AUDIT FUNCTION the 997 is generated?.

3.for functional acknowledgement message is accepted and partly accepted message is required?.

thanks

walter

[Former Member]

Hi KUNAAL MASIH ,

please correct me if I am wrong.

Here the functional acknowledgement is getting generated with help of

SEEBURGERu2019s proprietary format to one of the EDI formats.

is it required any accepted and partly accepted for functional acknowledgement.

please if you have any documents kindly send to me

thanks

walter

[Former Member]

>

> Hi 
> thanks for your response.
> The flow of scenario is EDIXIR3
> Message is shipping schedule (862)
> Here the doubt is 862 messages are sending from EDI system to R3 system through XI.
> One functional acknowledgement should send back to EDI system.
> 1. How the functional acknowledgement should generate the message?.
> 2. Is it ALE AUDIT FUNCTION the 997 is generated?.
> 3.for functional acknowledgement message is accepted and partly accepted message is required?.
> thanks
> walter

Hey,

For your EDI message 862 FunctionalAck will get generated automatically by EDI(in our Seeburger ) adapter.

No ALE AUDIT is for idoc which is different from EDI

If your message contains bulk of EDI messages and one of them is not proper then PartlyAccepted will work ,if you dont want to process those improper EDI messages then Accepted is needed which will process if EDI format is valid

HTH

Rajesh

[Former Member]

Hi,

Functional Ack will be generated automatically by Seeburger...all you need to do is follow the module chain Classifier, BIC and Split...you also need to create a project(whatever name) in BICMD and import ANSIX12_See, AnsiX12_ERROR, AnsiX12_ERROR_CHILD and all the other mappings like 850,810 whatever EDI transaction you are receiving...

Thanks,

Srini

Edited by: Srinivas Davuluri on Jun 22, 2009 5:10 PM

Edited by: Srinivas Davuluri on Jun 22, 2009 5:11 PM

[Former Member]

Hi Walter,

What type of acknowledgement are you looking for. Are you dealing with EDI formats

This is a technical confirmation. This is not exchanged via an individual message but the status report for IDoc processing. The status values used are:

"22" Shipping OK, acknowledgment has yet to come

"16" Functional Acknowledgment positive

"17" Functional Acknowledgment negative

The status values "14" and "15" are available for the Interchange Acknowledgment accordingly.

Regards,

Nithiyanandam

[Former Member]

you are talking EDI , am i right?

997 is a message type which is used for giving acknowledge, you can use it as seprate message or configure BPM to send it every time when 850 or any other message is arrived.