EDI Correlation in B2B

Brethren,
Is their anyway that B2B checks for duplicate records? For ex. if the same inbound 850 is send by the trading partner twice with the same control number etc... Can B2B identify it as duplicate and trigger an error message. I highly doubt it.. but just thought of shooting it.. maybe there is a new tip.properties that dev has come-up with !!!
Any help here would be appreciated !!
thanks - Shailesh

Hi Shailesh and Ramesh,
I working Outbound 855 transaction.
I have created Business Action 855 and used the same 997(created for 850).
I have also created the TPA for 855-997 and deployed the configuration.
I am able to receive the Business event generated in oracle Apps in the BPEL process.
I have set the AQ-header parameter like following in BPEL process
FROM_PARTY=GlobalChips
TO_PARTY=ACME
DOCTYPE_NAME=855
DOCTYPE_REVISION=4010
MSG_TYPE =1
After this I have enqued it using the AQ adpater with the following details
QueueName="IP_OUT_QUEUE"
DatabaseSchema="B2B"
ObjectFieldName="PAYLOAD"
PayloadHeaderRequired="true"
RecipientList="B2BUSER"
OpaqueSchema="false" .
Now there is no 855 EDI file getting generated .
I have also seen the table AQ$IP_QTAB; and I can some entries for the consumer B2BUSER.
Can you suggest how crack this issue and if I am missing something.
Thanks in advance.
Regards
Lalit

Similar Messages

Filtering EDI Files in B2B 11g

Hi Gurus,
We have a requirement that we should not process the EDI files which will have Usage Indicator(ISA15) has 'T' value. Rather we should send the file to some test directory on SOA file system.
Could you please let me know whether we can achieve this in B2B 11g.
Regards,
Raghav

Hi Raghav,
Oracle B2B is not a service bus and hence does not has a functionality of content based routing. Better change your design and have a service bus before B2B to do content based routing.
Regards,
Anuj

Error in getting content of edi 834 file - B2B inbound

Hello B2B Guru,
I am frustrated about this error. It seems so straightforward but just not working.
B2B 834 inbound file is processed successfully. After that, SOA BEPL need to post-process the 834 xml file generated by B2B. I need to check the 834 xml content to determine what to do next. The 834 xml is populate in Receive1_Consume_Message_InputVariable payload correctly. But I just can't get the following "assign" work. It is empty. I got selection exception.
<assign name="Assign1">
<copy>
<from>$Receive1_Consume_Message_InputVariable.body/ns4:Loop-1000A/ns4:Segment-N1/ns4:Element-67</from>
<to>$g_test</to>
</copy>
</assign>
I guess may namespace matters, but I can't figure out. Is there anyone have similar experience?
Thank you very much in advance,
Alena

Hi Anuj,
Thank you very much for your help. Yes, it is the name space issue. I have changed xsd name space due to name convention but didn't update B2B configuration. So what I need to do is to update B2B document definition with the same xsd in SOA, right?
Your ongoing support has been dramatically affected our development phase. Appreciated.
Alena
CGI
Edited by: Alena on Jun 1, 2013 12:59 PM

Send EDI request to B2B from BPEL

I am working on an integration effort.
Our plan would be have a BPEL pick up a X12 message from IBM MQ and send it to B2B to transform it into a XML format. Because of the asynchronous manner. The B2B will pass the result to a TP, which is another BPEL process.
We believe we need to create a listening channel for the B2B host TP to pick up the request. If we use a B2B Adpater in our composite, what should the listening channel be? An alternative would be the BPEL process drop the message in a JMS queue through JMS adapter and the listening channel is pointing to the JMS queue.
Can anybody confirm our solution or help us find a better solution?
Thanks
John

If we use a B2B Adpater in our composite, what should the listening channel be?It depends on mode of integration (Integration Type in adapter) and default internal delivery channel (queue) being used in B2B.
If you select "Default" mode in B2B adapter then no listening channel needs to be configured. A B2B WSDL is generated for the SOA composite to communicate with Oracle B2B directly.
If you select "AQ" mode in B2B adapter and using default internal delivery channel (IP_IN_QUEUE or IP_OUT_QUEUE depending upon direction) in B2B, then also no listening channel needs to be configured. However if you have created a custom AQ queue and using same in B2B adapter then an internal listening channel of Generic AQ type needs to be created.
Similarly, if you select "JMS" mode in B2B adapter and using default internal delivery channel (B2B_IN_QUEUE or B2B_OUT_QUEUE depending upon direction) in B2B, then also no listening channel needs to be configured. However if you have created a custom JMS queue and using same in B2B adapter then an internal listening channel of Generic JMS type needs to be created.
Remember, B2B can only use AQ of the type IP_MESSAGE_TYPE.
Please refer -
http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10229/intro_ui.htm#CHDEGEEB
Regards,
Anuj

B2B-51507- Payload validation error - 11.1.1.7 Latest Version

Anuj/Nitesh (B2B Gurus)
I am facing a problem when Posting the message from SOA to B2b (XML->EDI) using the B2b Adapter.
Flow is : Ebusiness->PLSQL->AQ->BPEL->B2B. Once the message is posted to B2b It is throwing the following Error.
But I am passing all the mandatory and Optional Parameters.
Tried the Following Threads, But No luck. I am passing all the Mandatory Parameters.
How to map Internal-Properties in XSLT.
Oracle B2B Payload Validation exception
Scenario - 1 (Success No Errors , Output Does not Contain PO Details)
Disabled the Validate flag in the Partner Agreement for the B2B Document.
Verified the B2b Wired Message, Output got generated but without the PO information I am passing from BPEL.
Scenario - 2 (Error )
Enabled the Validate flag in the Partner Agreement for the B2B Document. The system is generating an error and throwing list of errors.
Error
Id
C064016C14103689486000005559CD14
Message Id
C064016C14103688C7F000005559CD0F
Refer To Message
Refer To Message
Sender Type
Name
Sender Value
ABC
Receiver Type
Name
Receiver Value
TEST123
Sender
ABC
Receiver
TEST123
Agreement Id
EDI_850_tpa_Lt7763342564515893374
Agreement
XXX_EDI_X12_4010_850_Outbound
Document Type
850
Document Protocol
EDI_X12
Document Version
4010
Message Type
REQ
Direction
OUTBOUND
State
MSG_ERROR
Acknowledgement Mode
NONE
Response Mode
NONE
Send Time Stamp
9/9/2013 10:48
Receive Time Stamp
9/9/2013 10:48
Document Retry Interval(Channel)
0
Document Remaining Retry(Channel)
0
Document Retry Interval(Agreement)
0
Document Remaining Retry(Agreement)
0
Native Message Size
Translated Message Size
5471
Business Action Name
Business Transaction Name
Xpath Name1
XPathName1
Xpath Value1
Xpath Expression1
Xpath Name2
XPathName2
Xpath Value2
Xpath Expression2
Xpath Name3
XPathName3
Xpath Value3
Xpath Expression3
Correlation From XPath Name
CorrelationFromXPathName
Correlation From XPath Value
Correlation From XPath Expression
Correlation To XPath Name
CorrelationToXPathName
Correlation To XPath Value
Correlation To XPath Expression
Wire Message
Wire Message
Application Message
Application Message
Payload Storage
Payload Storage
Attachment
Attachment
Label
soa_b2b_ - Thu Sep 05 11:51:44 CDT 2013 - 4
Collaboration Id
C064016C14103688E1A000005559CD13
Collaboration Name
Collaboration Version
Business Action Name
Exchange Protocol Name
Generic File
Exchange Protocol Version
1
Interchange Control Number
Group Control Number
Transaction Set Control Number
Error Code
B2B-51507
Error Description
Description: Payload validation error.
Error Level
ERROR_LEVEL_COLLABORATION
Error Severity
ERROR
Error Text
Error Brief : Error reporting limit exceeded. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. A functional group code mismatch was encountered. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. A transaction ID mismatch was encountered. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. An X12 syntax error occurred. An X12 syntax error occurred. An X12 syntax error occurred. An X12 syntax error occurred. An X12 syntax error occurred. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. An X12 syntax error occurred. An X12 syntax error occurred. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. An X12 syntax error occurred. An X12 syntax error occurred. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered.
Error Brief :^M
Error reporting limit exceeded.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Description: Payload validation error., null, null, null, null, C064016C140EF31BFCA000005559CC
A4, null, null, 1258, B2B-51507, null, null, null, null, null, 2013-09-05 12:35:49.092, null, ^M
Error :^M
Analysis halted after 101 error(s) (Limit for Transaction is 100). Large numbers of errors usually indicate that the same error is repeatedly encountered in multiple segments or transactions. Fix the repeating error and resubmit the test to obtain further results.^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 1{br}{tab}Characters: 210 through 212^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 2{br}{tab}Characters: 247 through 257^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 3{br}{tab}Characters: 292 through 294^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 4{br}{tab}Characters: 329 through 339^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 5{br}{tab}Characters: 374 through 376^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 6{br}{tab}Characters: 411 through 426^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 7{br}{tab}Characters: 463 through 465^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 8{br}{tab}Characters: 502 through 517^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 9{br}{tab}Characters: 552 through 558^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 10{br}{tab}Characters: 593 through 597^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 11{br}{tab}Characters: 632 through 633^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 12{br}{tab}Characters: 668 through 673^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 13{br}{tab}Characters: 708 through 717^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 14{br}{tab}Characters: 752 through 753^M
Thanks
Rao.

Issue is resolved by doing the Following Steps.
1. Open the ECS file in the Document Editor, Exclude the ISA, GS segments in the ECS file. Save the File and Upload the Document and Redeploy the Agreement.
2. Export the XSD and refer it in the BPEL process and do the transformation.
Thanks
Nethi.

Setting Message-ID email header from Oracle B2B backend in 11g

Hi,
Is it possible to set the Message-ID from the backend application via JMS header? Is there a JMS header exposed to set this message id in case of email transport? Will the email server able to honor this value that we set and send to Oracle B2B in 11g and send it as the email header (Message-ID)? Is this possible?
The idea here is if my backend application can set this Message-ID value of the request message, then the response message which would be a reply to the initial message will have the value of the Message-ID in the property in-reply-to. Now if this in-reply-to is also exposed an a JMS header to the backend application, then i will be able to co-relate the request and the response messages.
Please let me know at the earliest if this would be possible.
Regards
Kavitha

Kavitha,
Is it possible to set the Message-ID from the backend application via JMS header? Yes, please set the MSG_ID header (jca.jms.JMSProperty.MSG_ID). It will be used as Message-ID in Wire Message.
, then i will be able to co-relate the request and the response messages.Generic Mail does not support correlation as of now. You may consider logging an enhancement request with support. If you are exchanging XML messages then you may consider using content based correlation at B2B.
Regards,
Anuj

Comparison between split Adapter in Seeburger and EDI Separator

Hello All,
Currently we are designing EDI interfaces using B2B Add-On.
I am trying to compare the split Adapter of Seeburger and EDI Separator of B2B Add-on.
In Seeburger Splitter configuration:
The additional split configuration helps to map the Sender ID, (EDIType,Transaction,Version) combination to split channel and sender agreement.
I believe a List of Sender Id, Mappings (Standard, Transaction, Version) combinations can be added to the same Split channel and Sender Agreements.
In B2B Add-On:
The sender ids , EDI details are directly mentioned in the channel and it is bound to sender agreement.
Does it reduce the flexibility in EDI Scenarios.Is that a correct point of view?
Your inputs highly appreciated.
Thanks.
Regards,
Sudharshan N A

Dear Sudharshan,
yes, I would say that this is a correct point/observation. When the Seeburger Adapters were introduced many years ago, one focus was put on the flexibility by keeping all functionality related to the "format conversion" (Classifier/Bic/Splitter) completely separated from the "data transmission" functionality directly in the channel.
This way, the format conversion modules could be included in any adapter that was running on the AdapterEngine and not just to the See-Adapters.
In a typical setup on client side, almost all inbound channels were using the "AUTO" functionality to detect all required parameters to select the right Split-Channel...so all channels had the same module-chains included (no matter if it was an AS2-Channel or a simple FILE/FTP-channel.
This also allowed for easy reprocessing of any received file (via AS2, X400 , OFTP or else....) by just putting the file again to a file-channel with the same module-chain parameters.
Kind Regards
Stefan
Btw... I am not very familiar with the B2B AddOn, but if you have additional questions regarding the Seeburger-EDI-Adapters, feel free to ask...

Outbound EDI missing envelope segment

Outbound EDI file is missing envelope segment (ISA,GS,GE AND IEA). Input xml is getting processed successfully. However, the outbound EDI is missing the envelope segment. My vendor says he needs envelope segement. What am I doing wrong? Thanks for your help.
Satya

Satya,
Does it still still use transaction set ecs to validate the input file? or, does B2B use .xsd for validating the input edi xml file?In case of EDI, it is ecs always which is used for translation and validation (if translation and validation is enabled in agreement). XSD is only used for proving integration with back-end middleware. You may validate it by providing ecs only as part of document definition and enabling validation & translation in the agreement.
Could this be the reason for not generating the envelope segment? The only reason why there is no envelope segments could be an invalid ecs.
You mentioned that our ecs file is not valid. However, all seems to work without any issue except for envelope segment.When I say invalid then it means improper structure of ecs and that's why I pointed you to refer the sample ecs which comes as part of installation itself. You may match your ecs with that sample ecs and easily figure out the differences. Oracle B2B is already pre-seeded with interchange and group ecs and hence transaction set ecs must not contain these two parts. It should have only transaction set (ST to SE) defined in it. In case you have any specific requirement then ONLY you should override interchange and group ecs at respective settings in document definition otherwise you should go ahead with pre-seeded (actually standard) Group and Interchange ecs files.
This document may be useful for you, if you have not gone through it yet -
http://www.oracle.com/technetwork/testcontent/edi-cookbook-oracle-b2b-133194.pdf
Regards,
Anuj

Mapping handling in third party vs SAP PI for EDI 850

Hi Experts,
Can I know Pros and Cons for hanling mapping translations in third party vs handling mapping translations in SAP PI for EDI 850 interface.
We are already paying money to third party. I just need pros and cons.. we will choose best approch based on your valuable points
Appreciate your help.
Regards,
Krishna.

Hi Mohan,
Pros:
SAP PI is a middleware and all Middlewares work pretty much on the same principles.
I am assuming that EDI 850 would have some sort of structure, [ to be honest I have not worked on EDI but just read about it] and SAP PI would require you to convert this structure into XML -> the only language SAP PI understands.
Now, I am sure there are lots of third party adapters available in the market for EDI. PI will give you flexibility to convert this interface into any kind of requirement be it JDBC/FILE/IDOC or anything and vice versa is also true. PI give you this enormous ability to convert to and from any format as long as it is viable.
Last but not the least, it will provide a robust system with Alerting and Monitoring.
Cons: You may have to invest on a third party adapter to read the EDI
You can read the following links for more abt EDI and SAP PI:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10b17369-9522-2c10-84a6-d75d8a8ace22?overridelayout=t…
Step by step interface for IDOC ORDERS05 to EDI 850 using B2B add-on and getting Functional acknowledgement 997 back
EDI 850 to R/3 scenario
Thanks & Regards,
Tejas Bisen

Reset the control numbers in Oracle B2B

Is there a provision for reseting the ISA / GS control numbers for outbound documents in B2B ?
We are presently moving from an older EDI translator to B2B, and the requirement is to ensure that we start from the next number that the older translator has generated for the ISA and GS control numbers. This would ensure that the trading partners don't receive a duplicate control numbers (control number already generated by the previous translator) and may reject the file, marking it as duplicate. Most trading partners check for duplicates based on control numbers of the incoming file.
Any help would be appreciated ?

Hello Shailesh,
Please reset the control numbers in B2B_CTLNUM_OUT table.
Rgds,Ramesh

About oracle b2b installation.

Hi Gurus,
Can you send me some blog to guide me step by step to build Oracle b2b SOA application.
Please clarify:Do i need to install B2B document editor soft(CD 1of 1,CD 1 of 2,CD 1 of 3) or Installation of CD 1 of 1 is sufficient for b2b document editor.
Is B2B server is different from SOA server?If at all i need to deploy some doc in server,Can i deploy in SOA server using document editor?
Can i have some clarity on 1.How to install b2b doc in server?
Can i have a step by step sample to run a simple b2b application?
Regards
Ramesh

Hi Ramesh,
Have you tried the samples from Oracle?
http://java.net/projects/oraclesoasuite11g/pages/B2B
Also try this, http://www.oracle.com/technetwork/middleware/soasuite/b2b-tu001-edi-133051.pdf
B2B document editor is currently works in only on windows platforms. If you want to define custom protocols, you need to go for CD2.
Is B2B server is different from SOA server?If at all i need to deploy some doc in server,Can i deploy in SOA server using document editor?Document editor is used only to create document protocols/analyse the data/data generation etc. not for deploying the applications.
Regards
KPR

What are the pre requisites for Oracle B2B

Hi -
Could some one share me the sample tutorial for EDI transactions using B2B.
The documents and the threads which i checked does not have complete and basic knowledge for B2B developer.
My requirement is like ,i have an EDI transaction 214 ecs/flat file which needs to be converted to XML file through b2b and the corresponding artifacts can be used by SOA component(BPEL or mediator) to process the output xml further to complete the integration.
Kindly help me with .
Thanks in advance,
Rohini

Hello Peter,
When it comes to DB refresh you need to know what all the client dependent data which needs to be retained.
For example you need RFC connections, Variants, User master etc.
As a pre task of Database refresh you may need to export the tables which are related to this so that once the database is refreshed you need to import them.
Ensure the proper backup of production database is available. Also check all the STMS configurations which need to be retained again.
Make sure that you need to have enough disk space which can accommodate your production data in to the pre production system.
These are some of the general consideration one needs to have but again it depends on the environment on which one runs SAP systems.
Regards
Vivek

The data starting at position 219 is not a valid EDI interchange. The remai

Hi B2Bgurus,
While our tp sending 997 to us , ther are getting an 500 error. The same file if I am trying to send using generic(in-house) its showing the problem
Unable to identify the document protocol of the message.
So ,I validated their 997 file using ECS, we got the below error, Could you please tell wats the exact error.
The data starting at position 219 is not a valid EDI interchange. The remainder of the data file was ignored.
Please find the attached file
ISA*00* *00* ZZPenske ZZEMR *090917*0622*U*00401*000000003*0*P*>~GS*FA*Penske*EMR*20090917*0622*3*X*004010~ST*997*30001~AK1*PO*1030~AK9*A*1*0*0~SE*4*30001~GE*1*3~IEA*1*000000003~
Regards
Srinivas .
Edited by: user11342588 on Sep 17, 2009 11:45 PM

Hi,
I tested your EDI data using B2B document editor. I am getting the following Error:
The Interchange Trailer is missing. The segment itself may be missing or the Segment Delimiter may be missing.
As Dheeraj mentioned in previous post, ISA segment is not constructed properly. I have modified your EDI data and validated in B2B document editor.
Correct EDI data:
ISA*00*Authrizati*00*Penske ZZEMR *01*EMR *090917*0622*U*00401*000000003*0*P*>~GS*FA*Penske*EMR*20090917*0622*3*X*004010~ST*997*30001~AK1*PO*1030~AK9*A*1*0*0~SE*4*30001~GE*1*3~IEA*1*000000003~
I used EDI version 4010.

EDI INterchange ID

Hi,
My company is trying to newly setup EDI transactions through B2B.
We dont have a EDI Interchange ID for our company.
Please let me know if we can use any random ID or do we have to register with someone.
Thanks,

Hello Deepti,
EDI Interchange ID is generally an ID that you and your trading partner agree on to identify each other. It can be of many types. It may be a Duns (Dun & Bradstreet) number, SCAC (Standard Carrier Alpha Code), FMC (Federal Maritime Commission), Phone (Telephone Companies), Duns Plus Suffix, Mutually Defined etc.
In short, EDI interchange ID is neither issued nor registered with an authority but there are several ID's (which you may have got by a third party ID provider like DUNS) which can be used as an Interchange ID. While passing data, in segment ISA05 and ISA07 you define the qualifier code (type of ID) and in segments ISA06 and ISA08 you provide the corresponding ID values for sender and receiver respectively.
Regards,
Anuj
Edited by: Anuj Dwivedi on Nov 17, 2010 1:04 PM

What is native EDI and a EDI file

What is a Native EDI file and what difference it contains standard EDI file
can i have some samples -- will the TP accepts which format
Edited by: user7395064 on Oct 7, 2009 5:22 AM

Hi,
but the question a raises how the data will be converted in Native EDI before the b2b talk to TPB2B uses XEngine to translate the XMLs coming from back-end into native EDI file. It uses the ecs file for the mapping of values and on the basis of that only envelope is created.
You may use B2B to transfer native EDIs as well and in that case translation won't be required but in this case you won't get support for Batching and back-end has to send the complete envelope. Please refer -
http://www.b2bgurus.com/2007/08/oracle-as-b2b-edi-faq.html
Regards,
Anuj

EDI Correlation in B2B

Similar Messages

Maybe you are looking for