B2B Document Editor

Similar Questions

• documents Editor

  Hi all
  
  
  What I need to install the editor of documents to work on B2B. I have installed soa suite 11 g which includes B2B.
  
  Thank you

  Hello

  If you are working on commercial documents such as EDI X 12, EDIFACT, HL7, RosetteNet... etc, you must install the b2b document editor to create and validate business documents. If you do not work on such a document of company, so no need to install the document editor.

  Published by: Ramesh Tosun on December 4, 2009 02:11

• Download Document Editor B2B

  Hello

  I'm trying to understand from where I can download B2B Document compatible with version 11g SOA Editor. Can someone share the link?

  Kind regards

  Hello

  You need to download using Oracle delivery: https://edelivery.oracle.com/

  Choose a package of product: Oracle Fusion Middleware

  Platform: select your desired platform

  Then choose:

  Oracle Fusion Middleware 11g Media Pack

  And finally:

  Publisher of B2B v11.1.1.6.0 documents

  See you soon

  Tiago

• New Apps tab in the Console B2B document definition page

  Hi all
  I am trying to find a way to convert all EDI formats in a single XSD canonical format before sending it to the SOA layer. This avoids the various SOA services for each EDI format.
  
  Could you please let me know something on the applications tab in the Console B2B document definition page. I see a field of XSLT file. What can we use here?
  
  Kind regards
  Ralu

  If I download the standard 850 ecs in B2B file, can B2B read all 850 custom files, shorten, based on standard ecs and send it to the SOA layer in a single XSD format (850)?

  He will be supported in future releases. From now on, you have two options-

  1 handle it to SOA by using XSLT transformations. Recommended.
  2. you can create a CBE 850 credits that can handle transactions of 850 custom on your side if it will be limits, and I do not recommend it personally.

  And on the applications tab, I can create an XSLT file to convert the EDI format to the canonical format for B2B itself?

  N ° B2B does not all XSLT to transform messages.

  Kind regards
  Anuj

• Publisher of B2B documents

  Where is publisher of Document B2B?
  I can't find.

  Editor of documents is available at:
  http://www.Oracle.com/technology/software/products/middleware/htdocs/fmw_11_download.html

• Cannot find the Arial italic fonts that won't integrate into my document editor

  I'm emptying a project of Publisher policies. He published in PDF format, but when I download the book on LULU.com, which will be published in an electronic book, they so because Arial Italic will not stir. I can't find anything in the file of the editor that USES even this font and there seems to be NO way to track it down. I went on every block of text in the thing, and this font is not really used anywhere! It is not in the document Styles, either... Help!

  Hi daniel_1028,

  Here is a link that has the same request for support of lulu. Link:https://support.lulu.com/Discussion.jsp?title=Having-problems-trying-to-upload-PDF&id=20730

  If the link above does not help, I suggest you post in the forum of publisher to improve assistance: link, please refer to: http://social.answers.microsoft.com/Forums/en-US/addpubs/threads

  With regard to:

  Samhrutha G S - Microsoft technical support.

  Visit our Microsoft answers feedback Forum and let us know what you think.

• Why can I not use my document editor out of school?

  I have a laptop for school and I want to access my Microsoft Publisher document, but sometimes eith an x next to it. Why is this? What can I do about it?

  The first thing that comes to mind is that the file is saved on the network of the school and outside the school you are not connected to the network and therefore cannot access the file.  Copy the file on a USB key or drive of the laptop.

• EDI - Publisher of B2B documents data validation

  I have the file specific ecs customer for EDI 272 V4020 where they send ^ element I65 - repetition separator. The translator EDI in B2B Survey character unreadable error when validating the edi data. I tried to change the Type of item to YEAR in the file of the ecs by changing it in the data dictionary, but it did not work. There are many types (YEAR, N, TM, N0,...) for the element Properties.Can anyone please let me know what type must be selected and the ecs in file so this translator would not lift error for ^ character.
  
  Thank you
  Mani

  Hi Mathieu,

  Threads below may be useful to you-

  manipulation of repetition for X 12 version 5010 separator

  Re: AIP-51505 5081: XEngine error - invalid direction for the 5010 EDI

  Error code: AIP: 50080: misidentification of Protocol Exchange

  Kind regards
  Anuj

• missing b2b Oracle option missing in export for the last editor of documents

  Recently, I installed the last editor b2b
  http://www.Oracle.com/technetwork/middleware/soasuite/downloads/index.html
  
  B2B Document editor part 1 of 3 size: 3.5 GB, checksum: 904191719
  B2B Publisher documents part 2 of 3 size: 3.88 GB, checksum: 898880311
  B2B Document editor part 3 of 3 size: 2.17 GB, checksum: 1504650504
  I am trying to export the file (X 12 - > 4010-> 850) ecs to xsd, in this State, I see this export format IE "b2b Oracle 1.0" & "Oracle B2B 2.0" is missing. "
  
  I am bit confused
  -It's because of any installation problems, or
  -These two options has been removed from the editor for this version (latest version).
  
  Here are the export format that I am able to see
  SEEBURGER BIC Message format
  Exports BizTalk XDR format.
  BizTalk XML schema.
  Comma Separated Values (CSV)
  Definition of the subject Business CrossWorlds
  EDI gXML v0.8
  Gentran DDF format.
  Gentran Unix IG format.
  gXML v1.0
  HTML with wiring diagram
  Mendelson Transformation engine
  Oracle 1.0
  Oracle 2.0
  Pervasive XML
  Standard Exchange format (SEF)
  ATTACH the Managerformat (EMM) mapping
  
  
  Please help me on this.
  
  Thank you.
  --
  SyAM
  
  Published by: user12196358 on April 25, 2013 16:03

  Use «Oracle 2.0»

  I don't see "Oracle B2B 2.0" or another option. I have always used 'Oracle 2.0' to generate xsd.

  Thank you
  Ismail.

• Processing outgoing EDI 810 EBS for B2B Transaction

  I'm working on creating a 810 EBS outgoing transaction to B2B. I created a SOA process that reads the data from the EBS and it corresponds to the schema generated by the Oracle B2B document editor. I did not the custom changes to the ECS file and the generated xsd. I can get the SOA process to invoke the B2B adapter but I get an error in the reports of B2B. I validated the load generated against the schema document and it's validate properly without giving me any errors. I also looked in the newspapers, and it does not give much information about why the guideline is slightest mistake out.
  
  The error I see is:
  
  {completionPersistPolicy = null, b2b.documentProtocolVersion = 4010, b2b.documentProtocolName = EDI_X12, masterConversationId = null, b2b.documentDefinitionName = New, replyToPortType = null, MESH_METRICS = null, tracking.parentReferenceId = 1763452-BpInv1 - BpSeq0.3-5, tracking.compositeInstanceId = 2733459, b2b.toTradingPartnerId = USA, tracking.ecid = c46525970c6ee401:73274bea:134aa93bd59:-8000-0000000000160855, priority = 0, b2b.fromTradingPartnerId = MyCompany, tracking.conversationId = urn:B735C8E0408C11E1BFCDBD484724BE1C, tracking.compositeInstanceCreatedTime = Mon Jan 16 15:54:50 CST 2012, tracking.parentComponentInstanceId = bpel:1763452, b2b.documentTypeName = 810}
  OUTGOING direction
  MSG_ERROR State
  B2B-51507 error code
  Brief text in error: error loading guideline.
  Error description: cannot load the Guide:
  
  Looks like my payload:
  
  <? XML version = "1.0" encoding = 'UTF - 8'.? > < xmlns:ns1 Transaction-810 = "urn: oracle: integration: b2b:X 12/4010/810 ' XDataVersion = '2.0' Standard = 'X 12' Version ="V4010"GUID ="{32393037-3231-3438-3239-353132353131}"CreatedBy ="XEngine_2819"xmlns =" urn: oracle: integration: b2b:X 12/4010/810 "> < ns1:Segment - ST > < ns1:Element - 143 > 810 < / ns1:Element - 143 > < ns1:Element - 329 > 438300001 < / ns1:Element - 329 > < / ns1: Segment-ST > < ns1 : Segment-GRAND > < ns1:Element - 373 > 20111204 < / ns1:Element - 373 > < ns1:Element - 76 > 2460087834 < / ns1:Element - 76 > < ns1:Element - 324 > 11665 < / ns1:Element - 324 > < ns1:Element - 328 > 1019080025 < / ns1:Element - 328 > < / ns1:Segment - GRAND > < ns1:Segment - REF > < ns1:Element - 128 > BM < / ns1:Element - 128 > < ns1: Element-127 > 41176425 < / ns1 : Element-127 > < / ns1:Segment - REF > < ns1:Segment - REF > < ns1:Element - 128 > IV < / ns1:Element - 128 > < ns1:Element - 127 > 2460087834 < / ns1:Element - 127 > < / ns1:Segment - REF > < ns1:Loop - N1 > < ns1:Segment - N1 > < ns1:Element - 98 > ST < / ns1:Element - 98 > < ns1:Element - 93 > USA for Heartland Co - op (West Des Moines, Iowa) < / ns1 : Element-93 > < ns1:Element - 66 > 9 < / ns1:Element - 66 > < ns1:Element - 67 > 9999999990000 < / ns1:Element - 67 > < / ns1:Segment - N1 > < ns1:Segment - N4 > < ns1:Element - 19 > Indianola, IA < / ns1:Element - 19 > < ns1:Element - 116 > 50125 < / ns1:Element - 116 > < ns1:Element - 26 > U.S. < / ns1:Element - 26 > < / ns1:Segment - N4 > < / ns1 : Loop-N1 > < ns1:Loop - N1 > < ns1:Segment - N1 > < ns1:Element - 98 > BT < / ns1:Element - 98 > < ns1:Element - 93 > United Services Association < / ns1:Element - 93 > < ns1:Element - 66 > 9 < / ns1:Element - 66 > < ns1:Element - 67 > 9999999990000 < / ns1:Element - 67 > < / ns1:Segment - N1 > < ns1:Segment - N3 > < ns1:Element - 166 > 2328 Rocklyn drive < / ns1 : Element-166 > < / ns1:Segment - N3 > < ns1:Segment - N4 > < ns1:Element - 19 > Urbandale, IA < / ns1:Element - 19 > < ns1:Element - 116 > 50322 < / ns1:Element - 116 > < ns1:Element - 26 > U.S. < / ns1:Element - 26 > < / ns1:Segment - N4 > < / ns1:Loop - N1 > < ns1:Loop - N1 > < ns1:Segment - N1 > < ns1:Element - 98 > RE < / ns1 : Element-98 > < ns1:Element - 93 > Koch nitrogen Company LLC (son/ACH) < / ns1:Element - 93 > < ns1:Element - 66 > 9 < / ns1:Element - 66 > < ns1:Element - 67 > 9999999990000 < / ns1:Element - 67 > < / ns1:Segment - N1 > < ns1:Segment - N3 > < ns1:Element - 166 > JP Morgan Chase Bank < / ns1:Element - 166 > < ns1:Element - 166_1 > ABA # 021000021 account # 709373963 < / ns1 : Element-166_1 > < / ns1:Segment - N3 > < ns1:Segment - N4 > < ns1:Element - 19 > New York, NY < / ns1:Element - 19 > < ns1:Element - 116 > 10005 < / ns1:Element - 116 > < ns1:Element - 26 > U.S.. < / ns1:Element - 26 > < / ns1:Segment - N4 > < / ns1:Loop - N1 > < ns1:Segment - DII > < ns1:Element - 446 > 20111219 < / ns1:Element - 446 > < / ns1: Segment-ITD > < ns1:Segment - DTM > < ns1:Element - 374 > 011 < / ns1:Element - 374 > < ns1:Element - 373 > 20111201 < / ns1:Element - 373 > < / ns1:Segment - DTM > < ns1:Loop - IT1 > < ns1 : Segment-IT1 > < ns1:Element - 358 > 19.830 < / ns1:Element - 358 > < ns1:Element - 355 > ST < / ns1:Element - 355 > < ns1:Element - 212 > 645.000 < / ns1: Element-212 > < ns1:Element - 235_1 > VC < / ns1:Element - 235_1 > < ns1:Element - 234_1 > NH3 < / ns1:Element - 234_1 > < / ns1:Segment - IT1 > < ns1:Loop - PID > < ns1 : Segment-PID > < ns1:Element - 349 > F < / ns1:Element - 349 > < ns1:Element - 352 > anhydrous ammonia < / ns1:Element - 352 > < / ns1:Segment - PID > < / ns1: loop-PID > < / ns1:Loop - IT1 > < ns1:Segment - TDS > < ns1:Element - 610 > 12790350 < / ns1:Element - 610 > < ns1:Element - 610_1 > 0 < / ns1:Element - 610_1 > < ns1:Element - 610_2 > 12790350 < / ns1 : Element-610_2 > < / ns1:Segment - TDS > < ns1:Segment - CAD > < ns1:Element - 91 > M < / ns1:Element - 91 > < ns1:Element - 140 > SCAC < / ns1: Element-140 > < / ns1:Segment - CAD > < ns1:Loop - BAG > < ns1:Segment - BAG > < ns1:Element - 248 > C < / ns1:Element - 248 > < ns1:Element - 1300 > ZZZZ < / ns1:Element - 1300 > < ns1 : Element-610 > 1279035 < / ns1:Element - 610 > < / ns1:Segment - BAG > < / ns1:Loop - BAG > < ns1:Segment - SE > < ns1:Element - 96 > 20 < / ns1:Element - 96 > < ns1: Element-329 > 438300001 < / ns1:Element - 329 > < / ns1:Segment - SE > < / Transaction-810 >
  
  Can someone guide me in the right direction please?
  
  Thank you
  POOJA

  POOJA,

  Your repository has been damaged. Please purge your B2B repository and the agreement I sent through importation. Test and let me know the result.

  Kind regards
  Anuj

• How to build custom EDI .ecs and .xsd to a file

  B2B gurus,
  
  I have a question. I have with me the file with an extension of steffen42. This isn't a standard EDI file. So, I need to create this file steffen42-based .ecs and .xsd files. How to do this in the Document B2B Oracle Editor. I tried going on the card manufacturer, but it gives an error. can you help me please on this.
  
  Thank you
  NGO

  Hello, NGO,

  Use the SpecGenerator tool in B2B Document Editor to generate ecs from a data file. With the help of ecs you can generate XSD later.

  Don't forget, it's the same risks as the generation XSD from an XML where it will be very specific to the structure of the data file used to generate the spec. Ideally, you should follow the opposite approach that is firstly set the ecs according to your requirement and then to generate data to test out of it.

  Kind regards
  Anuj

• Validation of EDI error: Segment GS (functional group header) to orientation

  Hello
  
  I'm working on the 272 EDI transaction (inbound).
  
  I created the ECS for the 272 EDI file and posted 272 EDI data with file ECS in the B2B document editor. Validation has been successful in B2B document editor
  
  When I download the same file of ECS and even tested in B2B. I use EDI version 4020.
  
  I get the following error,
  
  The position of guideline 0200 GS (functional group header) segment is missing. Standard option of this segment is mandatory. {br} {br} This segment was expected after: {br} {tab} Segment count: 1 {br} {tab} character: 105

  Hey riri,.

  You must change the data type of the particular element in the SCE itself.

  Kind regards
  Anuj

• XEngine error - error from the XML parser

  Hello
  
  I configured EDI X 12 generic exchange for outgoing FTP. I generated data EDI841 of the B2B document editor. When I try to send xml 841, I get the following log in the b2b.log file
  
  
  Error in brief:
  5083: XEngine error - error in the XML parser.
  
  iAudit report:
  <? XML version = "1.0" encoding = "UTF-16"? > < AnalyzerResults Guid = "{29FD00C2-DE93-4B22-AD75-9462FDB54F3F}" > < ExecutionDate > Thursday, November 20, 2008 < / ExecutionDate > < ExecutionTime > 19:55:18 (normal time of the India) < / ExecutionTime > < AnalyzerReturn > Failed < / AnalyzerReturn > < NumberOfErrors > 1 < / NumberOfErrors > < ErrorByCategory > < Category Name = "Reject" > < name of gravity = 'Normal' > 1 < / gravity > < / category > < / ErrorByCategory > < status > completed < / status > < DataFile > < FilePath > D:\OraHome_ 2\ip < / FilePath > < FileName / > < LastModified / > < FileSize / > < DataURL > file:\\D:\OraHome_2\ip < / DataURL > < / DataFile > < AnalyzerErrors > < error ErrorCode gravity = "{C0046014-9F8C-4C50-8AD0-22176044D2D6}" = "Normal" category = "Reject" index = '1' ID = '50830000' > < ErrorBrief > 5083: XEngine error - XML parser error. < / ErrorBrief > < ErrorMsg > XML parser error. < / ErrorMsg > < ErrorObjectInfo > < 'ErrorLevel' > 0 = parameter name < / parameter > < parameter Name = "Name" > XData2Native < / parameter > < name of the parameter '_ec_dn_guid_' = > {BD729023-F5CD-497E-95CD-501129074879} < / parameter > < parameter = "_ec_index" > 0 name < / parameter > < name of the parameter = "ec_error_scope" > Document < / parameter > < / ErrorObjectInfo > < ErrorDataInfo > < Part1 / > < ErrData / > < Part3 / > < DataXPointer > < StartPos > 0 < / StartPos > < size > 0 < / size > < / DataXPointer > < / ErrorDataInfo > < / error > < / AnalyzerErrors > < / AnalyzerResults >
  2008.11.20 to 19:55:19:084: Thread-11: B2B - (DEBUGGING) = {C0046014-9F8C-4C50-8AD0-22176044D2D6} oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sErrorGuid
  2008.11.20 to 19:55:19:084: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sDescription = XML parsing error.
  2008.11.20 to 19:55:19:084: Thread-11: B2B - sBrDescription oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument (DEBUG) = 5083: XEngine error - error in the XML parser.
  2008.11.20 to 19:55:19:084: Thread-11: B2B - (DEBUGGING) ErrorLevel = 0 sParameterValue = oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName
  2008.11.20 to 19:55:19:084: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = sParameterValue Name = XData2Native
  2008.11.20 to 19:55:19:084: Thread-11: B2B - sParameterName oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument (DEBUG) = ecdn_guid_ sParameterValue = {BD729023-F5CD-497E-95CD-501129074879}
  2008.11.20 to 19:55:19:084: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = sParameterValue index ec= 0
  2008.11.20 to 19:55:19:084: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = ec_error_scope sParameterValue = Document
  2008.11.20 to 19:55:19:084: Thread-11: B2B - oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument (DEBUG) added pound key = {BD729023-F5CD-497E-95CD-501129074879}
  2008.11.20 to 19:55:19:552: Thread-11: B2B - lot of oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument (DEBUG) Position = 0
  2008.11.20 to 19:55:19:568: Thread-11: B2B - Error (ERROR) -: AIP-51505: General Validation error
  at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2231)
  at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1610)
  at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:968)
  at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1131)
  at oracle.tip.adapter.b2b.data.MsgListener.onMessage (MsgListener.java:833)
  at oracle.tip.adapter.b2b.data.MsgListener.run (MsgListener.java:400)
  at java.lang.Thread.run(Thread.java:534)
  
  2008.11.20 to 19:55:19:568: Thread-11: B2B - Error (ERROR) -: AIP-51505: General Validation error
  at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2231)
  at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1610)
  at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:968)
  at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1131)
  at oracle.tip.adapter.b2b.data.MsgListener.onMessage (MsgListener.java:833)
  at oracle.tip.adapter.b2b.data.MsgListener.run (MsgListener.java:400)
  at java.lang.Thread.run(Thread.java:534)
  
  2008.11.20 to 19:55:19:568: Thread-11: B2B - Error (ERROR) -: AIP-51505: General Validation error
  at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2285)
  at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1610)
  at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:968)
  at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1131)
  at oracle.tip.adapter.b2b.data.MsgListener.onMessage (MsgListener.java:833)
  at oracle.tip.adapter.b2b.data.MsgListener.run (MsgListener.java:400)
  at java.lang.Thread.run(Thread.java:534)
  
  2008.11.20 to 19:55:19:568: Thread-11: B2B - Error (ERROR) -: AIP-51505: General Validation error: error -: AIP-51505: General Validation error
  at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2285)
  at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1610)
  at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:968)
  at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1131)
  at oracle.tip.adapter.b2b.data.MsgListener.onMessage (MsgListener.java:833)
  at oracle.tip.adapter.b2b.data.MsgListener.run (MsgListener.java:400)
  at java.lang.Thread.run(Thread.java:534)
  Caused by: error -: AIP-51505: General Validation error
  at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2231)
  ... 6 more
  
  2008.11.20 to 19:55:19:568: Thread-11: B2B - (DEBUGGING) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage, B2BDomainException
  2008.11.20 to 19:55:19:568: Thread-11: B2B - oracle.tip.adapter.b2b.engine.Engine:handleOutboundException (DEBUG) Update Error Message: error -: AIP-51505: General Validation error
  2008.11.20 to 19:55:19:568: Thread-11: B2B - (DEBUGGING) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState entry
  2008.11.20 to 19:55:19:584: Thread-11: B2B - message (DEBUG) AccessRepo:findBusinessMessageByB2BMessageId found successful with B2bMessageId: 96768985 and ProtocolMessageId 96768985
  2008.11.20 to 19:55:19:584: Thread-11: B2B - oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState (DEBUG) thread not found message.
  2008.11.20 to 19:55:19:584: Thread-11: B2B - oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState (DEBUG) update computer error message
  2008.11.20 to 19:55:19:662: Thread-11: B2B - (DEBUGGING) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState output
  2008.11.20 to 19:55:19:662: Thread-11: B2B - (DEBUGGING) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException line Update Native event Tbl
  2008.11.20 to 19:55:19:662: Thread-11: B2B - (DEBUGGING) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow entry
  2008.11.20 to 19:55:19:662: Thread-11: B2B - message (DEBUG) AccessRepo:findBusinessMessageByB2BMessageId found successful with B2bMessageId: 96768985 and ProtocolMessageId 96768985
  2008.11.20 to 19:55:19:662: Thread-11: B2B - oracle.tip.adapter.b2b.msgproc.DbAccess (DEBUG):
  
  * DbAccess:updateNativeEvtTblRow:tip_wireMsg not found wiremsg
  2008.11.20 to 19:55:19:662: Thread-11: B2B - (DEBUGGING) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException notification App
  2008.11.20 to 19:55:19:662: Thread-11: B2B - enter engine: notifyApp (DEBUG)
  2008.11.20 to 19:55:19:662: Thread-11: B2B - engine queue (DEBUG) AQJMSCorrelationID = 3AB8B0051B5E4C17A7D3DEF093027FF8
  2008.11.20 to 19:55:19:662: Thread-11: B2B - notifyApp:notifyApp (DEBUG) the exception ip message queue:
  < exception xmlns = "http://integration.oracle.com/B2B/Exception" xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance" >
  < correlationId > 96768985 < / correlationId >
  < b2bMessageId > 96768985 < / b2bMessageId >
  < errorCode > AIP-51505 < / errorCode >
  < > 5083 errorText: XEngine error - XML parser error. < / errorText >
  < errorDescription >
  <! [CDATA [info from the Machine: (PC022350)]]
  XML parsing error.  []] >
  < / errorDescription >
  < errorSeverity > 2 < / errorSeverity >
  < / exception >
  2008.11.20 to 19:55:19:662: Thread-11: B2B - (DEBUGGING) AQJMSCorrelationID = 3AB8B0051B5E4C17A7D3DEF093027FF8
  2008.11.20 to 19:55:19:755: Thread-11: B2B - output engine: notifyApp (DEBUG)
  2008.11.20 to 19:55:19:755: Thread-11: B2B - oracle.tip.adapter.b2b.engine.Engine:handleOutboundException (DEBUG) update successfully Error Message: error -: AIP-51505: General Validation error
  2008.11.20 to 19:55:19:755: Thread-11: B2B - validation DBContext (DEBUG): enter
  2008.11.20 to 19:55:19:755: Thread-11: B2B - validation DBContext (DEBUG): Transaction.commit)
  2008.11.20 to 19:55:19:755: Thread-11: B2B - (DEBUGGING) DBContext commit: leave
  2008.11.20 to 19:55:19:755: Thread-11: B2B - (DEBUGGING) oracle.tip.adapter.b2b.data.MsgListener:onMessage output
  
  Please help me solve this problem.

  a special character at the beginning of the file (before even the tag ) Please make sure that the XML is valid, no need to turn off validation w.

• What is the latest version of the editor Document B2B?

  What is the latest version of the Document Editor? Can someone give some advice?

  Please check:
  http://www.Oracle.com/technetwork/middleware/downloads/FMW-11-download-092893.html

  Check also under Blog to know more details such as samples, userguide of developers, etc.
  http://blogs.Oracle.com/oracleb2bgurus/2010/04/oracle_b2b_started_kit.html

  Kind regards
  Dheeraj

• B2B 11 GR 1 matter unable to identify the EDI document via the channel look file

  Hello
  
  I was wondering if someone might have encountered this problem, I see a bit of noise on this forum about recognition of documents, and this may sound familiar to some of you...
  
  It is necessary to configure B2B 11 g (11.1.1.2) to query a file from a certain location. In 10g, there is an option to create the directory name of the poll with a certain convention %FROM_PARTY%_TO_PARTY%_%DOCTYPE_NAME%_%DOCTYPE_REVISION%.edi etc., but this option is totally removed from 11 GR 1 material, so the only option is to go for changed file name (with the same format as above).
  
  Now I have to deal with incoming EDI files, so creaed the file with the above names naming convention and configured a channel listen to extract the file. The EDI file is simple with normal elements of ISA, GS and functional group, also passing thro validation documents Editor. B2B pulls, Archive it, but during the identification phase, he simply out craps with the following messages in the journal:
  
  [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] EDIDocumentPlugin: processIntNode: []
  intNode name: Interchange
  ]]
  [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] EDIDocumentPlugin: processIntNode: ISA Key = InterchangeControlVersion Val = 00401
  [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] EDIDocumentPlugin: processIntNode: ISA Key = InterchangeReceiverID Val = XXXXXXXX
  [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] EDIDocumentPlugin: processIntNode: ISA Key = InterchangeReceiverQual Val = 12
  [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] EDIDocumentPlugin: processIntNode: ISA Key = InterchangeSenderID Val = YYYYY
  [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] EDIDocumentPlugin: processIntNode: ISA Key = InterchangeSenderQual Val = 08
  [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] EDIDocumentPlugin: processIntNode: ISA Key = InterchangeUsageIndicator Val = T
  [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] EDIDocumentPlugin: processIntNode: standard = X 12
  [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] EDIDocumentPlugin: processIntNode: number of nodes group = 0
  [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] EDIDocumentPlugin: processNode: number of nodes to Exchange > 1
  [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] [EDIDocumentPlugin: processNode: counterProperties >]
  [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] EDIDocumentPlugin: identifyIncomingDocument: no IDE or HL7
  [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] EDIDocumentPlugin: identifyIncomingDocument: no IDE or HL7. Return
  [2011-03-16 T 13: 19:11.476 - 04:00] [soa_server1] [ERROR] [] [oracle.soa.b2b.engine] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@2fa8a24d] [username: < anonymous >] [ecid: 0000Iuz2yY3CwklqwsJb6G1DW8Ew000031, 0] [APP: soa-infra] error -: B2B-50083: Protocol for the identification of the Document error. [[
  at oracle.tip.b2b.engine.Engine.identifyDocument(Engine.java:4203)
  at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:1850)
  at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1395)
  at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:3216)
  at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:2960)
  at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:2706)
  at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:540)
  at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:200)
  to oracle.integration.platform.blocks.executor.WorkManagerExecutor$ 1.run(WorkManagerExecutor.java:77)
  to weblogic.work.j2ee.J2EEWorkManager$ WorkWithListener.run (J2EEWorkManager.java:183)
  at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
  
  ]]
  
  I am unable to understand what makes the engine EDI to throw the paper away when everything is in order? Just to clarify, there are also a commercial partnership with ECS, configuration files and agreements XSD.
  
  I see a similar discussion at 11g - inbound configuration for any group or no header Exchange with no resolution.
  
  Pointers?
  
  Concerning

  B2B understood the agreement to be executed in spite of not providing the name file name or dir (% TO_PARTY % etc...) convention. Remains to be seen if they made any changes specific to the PS2.

  Essentially arrivals, file name or directory name is used to identify the TP which sends the document, but there is in the case of EDI and other parameters that can be used for the identification of TP as ISA and GS headers. So, even if the identification of TP with the help of file name or directory name fails, always TP can be identified on the basis of present envelope parameters in the EDI message. You can view-

  http://www.b2bgurus.com/2007/08/trading-partner-identification-in-EDI.html

  Above blog is for B2B 10 g and where he mentions some properties to set, but these properties are part of the product of g 11 B2B itself and therefore, no additional configuration is necessary.

  Finally I discovered that the problem of managing EDI is the line breaks. When I provide the entire load in one line, the B2B is able to implement the agreement, but when I the segment using line breaks separate the same error is thrown.

  IDE itself is a delimited file that uses it's own delimiters (known as o delimiters EDI separators) to separate the segments, elements etc. Even from every part of the IDE has fixed length designed in ecs file. If you insert a line break between the two, then this file will become invalid because you're characters additional ading inside (line break is a character) and engine EDI will not be able to analyze this document. This is according to the standard guidelines and nothing specific to Oracle B2B. So do not add in additional characters (including line breaks)

  Kind regards
  Anuj