Process Inbound EDI 997(ACK)

Hi
Is there any way to process inbound EDI997 files. I tried to process the 997 files with a orchestration but got the below error.
The output message of the receive pipeline "Microsoft.BizTalk.Edi.DefaultPipelines.EdiReceive, Microsoft.BizTalk.Edi.EdiPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" failed routing because there is no subscribing
orchestration or send port.
The sequence number of the suspended message is 1.
I'm sure the orchestration has no issues since i have processed other files like 214,204, 210 etc.
I want to extract the acknowledgement details from 997 files and log it into a custom table. Please let me know is there any way to do this.
Thanks in advance.

As described in the other post, the 997 Schema is included in Microsoft.BizTalk.Edi.BaseArtifacts.dll.
Since it's generated internally, you cannot change the namespace of the generated message.
You can use the ESB Toolkits Remove and Add Namespace components to customize the 997 for you app:
http://msdn.microsoft.com/en-us/library/ff699608.aspx

Similar Messages

Unable to process inbound EDI docs from TP-multiple Host ID's,1 transaction

Issue:
Unable to process inbound EDI documents from trading partners
(Same doctype and revision, but diff receiver ID’s for host)
Host: ISA ID’s are HOSTA, HOSTB
Transaction: X12, 210, 5010
Trading Partner A: sends EDI document with these values
Interchange Sender ID: TPA
Application Sender's Code: TPA
Interchange Receiver ID: HOSTA
Application Receiver's Code: HOSTA
B2B setups are as below
Business action: Process_210
Operational Capability for Trading Partner A : Process_210_Initiator It has
Interchange Sender ID as TPA
Interchange Receiver ID as TPA
Application Sender's Code: TPA
Application Receiver's Code: TPA
This creates a Process_210_Responder for HOST
It has
Interchange Sender ID as HOSTA
Interchange Receiver ID as HOSTA
Application Sender's Code: HOSTA
Application Receiver's Code: HOSTA
Validated Agreement and deployed, Result is success and everything works fine until here
Note: B2B validates taking everything from Process_210_Initiator except the Interchange Receiver ID that it gets from the Process_210_Responder
New Trading Partner B also sends us an X12, 210, 5010 but he uses Receiver ID as HOSTB
Trading Partner B: sends EDI document with these values
Interchange Sender ID: TPB
Application Sender's Code: TPB
Interchange Receiver ID : HOSTB
Application Receiver's Code: HOSTB
B2B setups are as below
Business action: Process_210
Operational Capability for Trading Partner B : Process_210_Initiator It has
Interchange Sender ID as TPB
Interchange Receiver ID as TPB
Application Sender's Code: TPB
Application Receiver's Code: TPB
This doesn’t create a new Process_210_Responder for HOST It has
Interchange Sender ID as HOSTA
Interchange Receiver ID as HOSTA
Application Sender's Code : HOSTA
Application Receiver's Code : HOSTA
Validated Agreement and deployed, Result the document fails with error
Validation of Interchange parameters failed. Please verify all the Interchange parameters in the B2B configuration match the Group parameters in the message. Make sure that the ecs file for this Interchange is valid
Upon looking at the log file it fails, as the Interchange Receiver ID in data is HOSTB where as in Process_210_Responder it is setup as HOSTA
Work Around that we tried, but could not succeed
Create a new business action called Process_210_HOSTB, created a new Document Protocol Revision X12_5010_HOSTB,Created a doc type 210 version 5010 under that
Used this new Business action for Trading Partner B so the new setups look like this
Business action : Process_210_HOSTB
Operational Capability for Trading Partner B : Process_210_HOSTB_Initiator It has
Interchange Sender ID as TPB
Interchange Receiver ID as TPB
Application Sender's Code : TPB
Application Receiver's Code : TPB
This creates a new Process_210_HOSTB_Responder for HOST It has
Interchange Sender ID as HOSTB
Interchange Receiver ID as HOSTB
Application Sender's Code : HOSTB
Application Receiver's Code : HOSTB
Validated Agreement, but could not deploy as I was getting AIP-11016 SQL error , may be integrity constraint issue
Note: I was able to deploy this agreement if I change the Document Type from 210 to something else like 210_new, but since the document is EDI I can’t have the Document Type as anything except 210

Ramesh,
Sorry for the delay , but this was the first thing I tried and it didn't work, I tried again just to be sure, it didn't work I am getting this error
When group Receiver ID didn't match
"Validation of Group parameters failed. Please verify all the Group parameters in the B2B configuration match the Group parameters in the message. The following parameters do not match the configured parameters in B2B"
In addition, when Interchange Receiver ID did not match
"Validation of Interchange parameters failed. Please verify all the Interchange parameters in the B2B configuration match the Group parameters in the message. Make sure that the ecs file for this Interchange is valid"
Here is the log file extract
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Enter
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl validateEnvelope = true
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Leave
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@12d8ecd
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = SeverityConfig
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = null
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@1fa5e5e
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:reset Enter
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:reset Leave
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@497062
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Enter
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeReceiverQual, val = [02]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [02]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeSenderID, val = [REMOTETP]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [REMOTETP]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeReceiverID, val = [SLCY]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [SLCY]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = Standard, val = [X12]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [X12]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeControlVersion, val = [00200]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [00200]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = ec_DataNodeName, val = [Interchange]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeSenderQual, val = [02]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [02]
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = ecsFileKey
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 60DD87849FFE4147BFCEB66842A33298-26-1-4
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValueBlob Param Name = ecsOptFileBlob
2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValueBlob Param Name = ecsFileBlob
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getStream Enter
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getStream Leave
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = SeverityConfig
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = null
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:setControlNumber sName = Interchange, controlNumber = 210011217
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:setControlNumber return = true
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = TPName
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = RemoteTP
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Enter
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit NodeGUID = {156BEDFC-931E-4923-840D-3AC0BAB670F2} position = 0
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Leave
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@1b5c22f
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Enter
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = GroupReceiverID, val = [STMSLCY]
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [SLCY]
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Value and doc parameter don't match2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = GroupVersionNumber, val = [005010]
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [005010]
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = ec_DataNodeName, val = [Group]
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = GroupSenderID, val = [REMOTETP]
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [REMOTETP]
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = false
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = false
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = TPName
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = RemoteTP
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Enter
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit getLookUpError Key = key = [GroupReceiverID] value = [STMSLCY] param = [SLCY] Value = null
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit NodeGUID = {6EE88EFC-B084-4FA8-8EE8-8C7BD397E9F1} position = 0
2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Leave
2008.07.28 at 14:31:25:073: Thread-10: B2B - (DEBUG) iAudit report :
Error Brief :
5082: XEngine error - Guideline look-up failed.

EDI 997 Schema

Hi
Can anyone please let me know do we have a inbuilt schema for EDI 997 with this target namespace
http://schemas.microsoft.com/EDI/X12#X12_997_Root .
I'm trying to process inbound EDI 997 file and store the data in a custom table. I couldn't find the schema matching exactly the same target namespace mentioned above. Please let me know how could i extract values from EDI 997 files in my orchestration?

John,
I've added the reference to the Edi.BaseArtifacts.dll. Could we create a schema with this dll? Please tell me detailed steps to create a schema in VS2012 with http://schemas.microsoft.com/EDI/X12#X12_997_Root
target namespace.
Thanks
Sivakumar

Inbound EDI multiple customers using 1 partner profile

I would think that it's possible to set up a single partner profile in WE20 through which you can process multiple idocs against multiple customers for order processing. Can anyone guide me on how to achieve this.
Thanks, Mart

Absolutely. You could have an EDI Partner called 'GENERIC' for example, and could use that to process inbound EDI Sales Orders. Obviously you would need an identifier to represent the correct Customer account, ideally this would be the Sold-to number. If it's not your Internal Sold-to, but another unique number, then you should be able to add mapping via transaction VOE4 to table EDPAR. I.e the Customers sends an external number 123 representing their Store Id, you map that back to your internal Customer Number. Only trouble with this is if two different Customers had the same external Id, as you would have no control over that. For our generic EDI Partners, the Customer Number is mandatory.
Cheers, Paul.

EDI 997 flow

Hi,
I am working on EDI transaction. We recieve EDI 101 transaction and send EDI 997 functional Ack.
I configured B2B to handle EDI 997 ack. I set Document Protocol Parameters in host side (ProcessBA_997 - 1.0) - Initiator and client partner side (ProcessBA_997 - 1.0) - Responder. B2B is able to send 997 transaction to configured transport protocol.
The issue is that B2B is taking the Document Protocol Parameters values (to generate ack) from Host side and not a client partner side parameters. This parameters will vary for client parnters.
Kindy advise me how to override the host side document protocol parameters. Thanks in advance.

If you want a custom FA as per the trading partner then better approach will be inserting the FA from backend.
Receive the message B2B to backend then change as per your requirement and insert FA again to B2B.
Rgds,
Nitesh Jain

Process Inbound 997 using Orchestration in BizTalk 2010

MS,
After reviewing and trying all the topics related to Inbound 997, I am creating this new topic that appears to have worked for some of the forum users. So here is what I did:
First Attempt:
Created a simple Orchestration that has a receive port listening to the folder (on a FTP server) where our trading partner (THEM) drops a 997 when we (US) send them an 850.
The Orchestration basically writes the XML schema to another folder C:\Rcvd997 using a Send Port.
We have a receive port listening to this C:\997Drop folder.
The first receive shape in the orchestration has a Filter expression BTS.MessageType == "http://schemas.microsoft.com/Edi/X12#X12_997_Root".
We confirmed that the BTS.MessageType is a promoted property when the message is received. This clearly indicates that the receive port/location is reading in the file (and of course the file gets deleted from C:\997Drop when it is read).
We get an error
The output message of the receive pipeline "Microsoft.BizTalk.Edi.DefaultPipelines.EdiReceive, Microsoft.BizTalk.Edi.EdiPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" failed routing because there is no subscribing orchestration or send port. The sequence number of the suspended message is 1.
There is no XML file written to C:\Rcvd997. We also added writing to the Event logs in an expression shape within the Orchestration with no luck.
Second Attempt:
In addition to that, we added a new SendPort called "EDI-997BadPort" with Filters BTS.MessageType == http://schemas.microsoft.com/Edi/X12#X12_997_Root and EDI.IsSystemGeneratedAck == false. Both these values are promoted in the message received.
This processes the file dropped in C:\997Drop folder and also completes the process successfully with no errors in the Administration console.
However, the message was never picked up by the orchestration.
In addition, the new file created on port "EDI-997BadPort" uses the EDI fallback settings in the ISA segment for Receiver and Sender for some reason. But the rest of the EDI seems to be correct.
Third Attempt:
Tweaking the Party agreements did not make any difference. We unchecked the trading partner "Local BizTalk processes messages received by the party or supports sending message from this party
The Transaction Set list is blank in trading party both (US --> THEM and THEM --> US) agreement tabs.
Fourth Attempt:
We also created a custom EDI pipeline hoping that will disable the default behavior of EDI-997.
We have tried several things since then with absolutely no luck. So why do we need to do this - because we are exchanging EDI files over FTP and we need to do some custom processing once we receive 997 from THEM when we send them a 850.
Why is there no way to intercept or disable what EDI does when it receives a 997?
Any ideas, suggestions, recommendations?
Thanks!

Hi
Can you please let me know if there is any solution for this. I tried to process the inbound 997 files but receive the same error.
The output message of the receive pipeline "Microsoft.BizTalk.Edi.DefaultPipelines.EdiReceive, Microsoft.BizTalk.Edi.EdiPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" failed routing because there is no subscribing orchestration or send port. The sequence number of the suspended message is 1.

Process Inbound 997: X12_00502_997.xsd

Hello,
I am developing an orchestration in BizTalk R2. This orchestration will process inbound 997 messages.
In my project I have added the existing file: X12_00502_997.xsd. Then I have created a Message Variable with the message type to that schema.
After I have added a "Receive" Shape. This shape is targeting to the Message Variable. I have also added a "construct" message to cast the inbound message to an xml variable. And finally I send out that Xml to a Windows Folder.
I am using the EdiReceive Pipeline; and I have created the corresponding parties; however when I put the following Edi in the Inbound Folder; my orchestration is never activated.
ISA*04*FA426     *00*          *02*RRDC           *02*KCS            *081024*0901*U*00502*001797871*0*P*;…
GS*FA*ISSP*KCS*20081024*0901*241273*X*005030RAIL…
ST*997*412730001…
AK1*RW*73295…
AK2*426*64974…
AK5*A…
AK9*A*1*1*1…
SE*6*412730001…
GE*1*241273…
IEA*1*001797871
I realized that the xml built by BizTalk has this structure:
<?xml version="1.0" encoding="utf-8" ?>
<ns0:X12_997_Root xmlns:ns0="http://schemas.microsoft.com/Edi/X12">
  <ns0T>
<ST01>997</ST01>
<ST02>412730001</ST02>
</ns0T>
<AK1>
<AK101>RW</AK101>
<AK102>73295</AK102>
</AK1>
I have created another EDI projects and those projects are building the xml files with these headers:
<ns0:X12_00502_998 xmlns:ns0="http://schemas.microsoft.com/BizTalk/EDI/X12/2006">
<ns0:X12_00502_864 xmlns:ns0="http://schemas.microsoft.com/BizTalk/EDI/X12/2006">
<ns0:X12_00502_426 xmlns:ns0="http://schemas.microsoft.com/BizTalk/EDI/X12/2006">
So; I really do not know why the orchestration is never activated. But I set in Filter Expresion in "Receive" Shape the following filter: BTS.MessageType = "http://schemas.microsoft.com/Edi/X12#X12_997_Root"
But the orchestration is still never activated.
The parties have unselected option: "Generate 997".
Any advice why it is happening this?
Thanks in advance,
Pablo

Thank you for your help!
You are right!!
I have been making several tests and finally I discovered when an EDI-997 interchange is received using EdiReceive Pipeline, BizTalk detects that its a functional acknowledge and it disassembles the message into XML, and drops the message XML into the MessageBox. However that Xml is dropped with the MessageType as
     "http://schemas.microsoft.com/Edi/X12#X12_997_Root". I have developed others EDI projects using: X12_00502_426, X12_00502_998, X12_00502_864 and all the Xml files created by BizTalk have different MessageType.
So, my orchestration had a wrong subscription to all the messages that match to this message type =
"http://schemas.microsoft.com/BizTalk/EDI/X12/2006#X12_00502_997"
That is the reason why my orchestration is never activated.
I have already modified my orchestration to subscribe it to functional acknowledge message type and now is activated.
However I need to read the values: GS02, GS03 from Inbound Message 997. Unfortunatelly when I try to read a GS value in a shape expression like this:
      System.Diagnostics.Trace.WriteLine(InboundMsg(EDI.GS02));
I am getting this exception:
Inner exception: There is no value associated with the property 'EDI.GS02' in the message.
I presume because when the orchestration is activated, the message is in xml format and those data elements are not included in the message; right?.
Do you know how can I read those data elements?
Thank you
Pablo

EDI 997 generation feature of B2B

Hi all,
Customer wants to the EDI 997 enabling for B2B They had set up Inbound 810 Transaction for a Remote Trading Partner and have used "EDIX12 over Generic Exchange" as the Exchange Proto. In the Operational Capability they have set the Is Functional Acknowledgement Required Property as True with the assumption that a EDI 997 will be generated for the corresponding EDI 810 received.But when they tested that with a sample file, they get error in B2B saying "Unable to identify the document protocol of the message" and it is showing the Business Action as Acknowledgement. They then set the property Is Functional Acknowledgement Required Property as False and tested but they are getting the same error.
Any pointers will be helpful.
Thanks in advance,
Senthil

Hi Ramesh,
I would briefly explain our set ups.
1. We have set up Remote Trading Partsnow which will send us an Inbound 810 Invoice file which has to be processed by B2B. The set up is working fine and the EDI file is getting translated to EDIFECS XML and there are no errors being
thrown.
2. As per the Business Requirement,a corresponding FA should be generated for the inbound 810 file. We set up the FA by referring to the B2B Technical note mentioned in the link below:
http://www.oracle.com/technology/products/integration/b2b/pdf/B2B_TN_006_Acknowledgements.pdf
We created a new Business Action for FA and attached the Business Action to the Partsnow Trading Partner(remote trading partner) Agreement.
The FA is getting generated but it is not in the expected format. Many additional segments are also coming up in the output FA file.
We already have a TAR# 6174945.992 open for this issue but we are yet to get any resolution on this.
It would be great if you could provide some inputs on whether we are missing any set ups.
Please let me know your contact info so that i can have a conf call with you and get the issue resolved. I am currently working in EST time zone and we are nine and half hours behind you. So please let me know when it is suitable for you to have the conf call.
My contact number is 484-318-1969.
Thanks In Advance.
Regards,
Dibya

Receiving EDI 997 into SAP

Hello,
I am having trouble understanding how a 997 inbound into SAP would be reflected in the system (we are receiving a 997 from the vendor based on a PO we send out)
1. Where would the 997 be reflected in the PO? Would this be a new confirmation category under the 'Confirmation' tab?
2. What basic idoc type/message type would be used?
Thanks for the help!!

Hello Tiffanie
The EDI 997 message is a functional acknowledgment which corresponds to an acknowledgement IDoc in SAP. This acknowledgment is reflected in the EDI/ALE status of the outbound IDoc.
Example:
I created a purchase order and sent it as outbound ORDERS.ORDERS05 IDoc (no = 414840).
For this outbound IDoc I created an inbound ALEAUD IDoc. Processing the acknowledgement IDoc (WE19, inbound fm IDOC_INPUT_ALEAUD) Idoc 414840 received an additional status 41 = Application document created in target system.
To be honest I do not know whether this IDoc acknowlegement is somehow reflected in the original purchase order but I doubt this is the case.
The ALEAUD01 IDoc looked like this:
Header E1ADHDR:
MESTYP     ORDERS
MESTYP_LNG     ORDERS05
Status E1STATE:
DOCNUM     0000000000414840
STATUS     53
STATXT     DOCUMENT PROCESSED SUCCESSFULLY IN APPLICATION
STAMQU     SAP
STAMID     IDOC_ADPAPTER
STAMNO     000
Regards
Uwe

Outbound EDI 860/Inbound EDI 865 Integrated to JDE 9

Has anyone successfully integrated an outbound EDI 860 and an inbound EDI 865 into JDE 9?

Hi,
I think Order05 should work for you. Let me try to answer your questions
1) which IDOC message type should i use for this transaction, to send an 865 ?
A: ORDERS. Basic type should be ORDERS05
2) What program and Form routine should i use to send an 865 , while configuring the output type in V/30 ?
A: RSNASTED. Form routine: EDI_PROCESSING which is pretty standard. You can use BA00 output type which is standard again.
3) Please advice me the SAP setting we need to do for an 865 (order change Ack) .
A: i. You should have the EDI settings done by your Basis team. (Else Idocs will not generate)
ii. You should create a partner profile in WE20 for KU customer, outbound.
iii. In the Outbound options mention the port and other stuff. Maintain the message control. Note that you put in BA00 there in the message type and put the right process code (Should be SD01).
I think these are the only things. Try and this should work for you.
Regards,
Mukund S

Inbound EDI 852

Can anyone of you please tell me about the inbound edi 852?
What would the IDoc file look like? What are the mandatory fields and what values should go in there etc...
Also , what transaction or tables are being accessed in SAP to post this data.
Your help is much appreciated.

Hi Sara,
In the E1ADRM1 segment, what values should we get?
The values should be 'WE' for customer and 'LF' for supplier.
Also where r the checks performed ? VOE2 , VOE4 ?
The data check is performed in FM IDOC_INPUT_PROACT.
Do you have any sample Idoc file for inbound 852?
Sorry, I don't have any IDoc sample. But you can use WE19 (Test tool) to simulate the IDoc and try to process using standard FM IDOC_INPUT_PROACT.
Again, hope this will help to start with.
Regards,
Ferry Lianto

Create EDI 997 with conversion agent

Hello,
I work with conversion agent by ItemField to convert EDI messages to xi and from XI to EDI.
I succeeded to receive EDI 850, to parse this message and to transfer it to the IDOC and create purchase order.
Now I try to send back to the customer EDI acknowledgment (997).
I'll be happy to hear if someone use with conversion agent to create EDI 997.
Elad

Hi Elad,
What are 997s?
997 Functional Acknowledgments are EDI transactions that a receiver of EDI transaction sets sends back to the party that sent the EDI transaction sets. All EDI transactions require an EDI 997 to be sent back.
Here is an example
Wal-Mart sends an EDI Purchase Order to a supplier. With EDI Standard X12, Wal-Mart expects a 997 to be sent back to them. The 997 lets Wal-Mart know that the supplier received the Purchase Order. It does not say that the supplier accepts the terms or conditions of the purchase order. It simply lets them know that the supplier successfully received the Purchase Order.
Here is another example. A supplier sends Wal-Mart an EDI Invoice. Wal-Mart will send a 997 back to the supplier. The 997 informs the supplier that Wal-Mart has successfully received the invoice.
CovalentWorks handles all of your EDI transactions for you, including 997s, as an outsourced EDI service. If you choose us as your EDI provider, our system will automatically send and receive all your 997 Functional Acknowledgements. And every one of them is processed for you at no charge.
Thanks,
Satya Kumar..

Issue with inbound EDI idocs

Hi
we are receiving inbound EDI idocs throgh third party. Third party received EDI file having 5000 transactions .
It was transalated same number of idocs text document and posted in SAP. But after 4 hours same file processed in SAP.
Third party saying they sent only once .
Is there any way in SAP file placed two times or one time .
Any table stores this information . we are using TRFC port . I know EDIF12 table but it was not used here.
Any clue on this.
Thanks

HI
ANY Clue on this issue

Inbound edi problem

hi ,
i have problem with inbound EDI for po acknowledgment(855) ,message type used ordrsp process code ORDR and basic type is orders05. i am testing the idoc in we19.for the segment E1EDP19 i specified qualifier 001 (means Material number used by customer) and IDTNR (marterial no) matnr in PO it runs successfully and idoc is posted to application.but if i specify qualifier- 002 (means Material number used by vendor ) it is not working and idoc is not posting to application with message Material number differs from that of ordered material. I have even assign value IDTNR (material no) from material info record i.e. vendor material no from table EINA but still idoc is not posting to application. Can anyone spot why this error occurs and give the solution.Is there any other table which maintains vendor material no. is there any OSS note available for this error?
Relevant points will be awarded for the solution.

This might be due to the material inventory being locked if these idocs contain the same material. The ideal would be to process these sequentially. if its process immediately in WE20, then multipe idocs can get processed simultaneously and ending in error if all are using the same material.

Inbound edi

hi,
can any one say me step by step process for inbound edi.

Following link is helpful
http://www.erpgenie.com/sap/sapedi/index.htm
Also in SAP help, read the following section
http://help.sap.com/saphelp_nw2004s/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm

Process Inbound EDI 997(ACK)

Similar Messages

Maybe you are looking for