XI EDI 834 format

Hi all I am new at SDN.
my client is interesting in integrating XI for all their interfaces. EDI 834 format is what the client want to globalize(for future vendors). my approach is to generate a proxy that have 834 format and then make a copy for different third parties. I would appreciate the view of some of the advance developer out there . please share your opinion on what is the best approach to implement and EDI834 format through XI.
my client is not interested in buying any XI adapter such as Seeburger adapter due to cost.

Hi,
Try to read the following links
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
http://www.stylusstudio.com/edi/XML_to_X12.html
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
Check this for Conversions-
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
Regards
Chilla

Similar Messages

How to work on EDI 834 Benefit Enrollment and Maintenance

Hi All.
I am new to B2B.
Please can anyone help me out in providing the information regarding how to work on EDI 834 format.
Also how to start the process to work on B2B.
Thanks In Advance.

Rajesh,
These are just another method of representing the business documents.
Its called as ANSI X12 format.
810 - Customer invoice
850 - PO create sales order
855 - PO acknowledgement
856 - Advance shipment notice
Check the below links,
http://help.sap.com/saphelp_erp2005vp/helpdata/en/dc/6b7c9f43d711d1893e0000e8323c4f/frameset.htm
i hope this will help you.
Reward points if its help full.
-Prsna

Using PI to map IDoc BENEFIT3 to EDI 834

Has any used PI/XI to map IDoc BENEFIT3 to EDI 834? We are looking to use this approach but have had problems finding a standard map. You would think SAP would have one since they stand by their BENEFIT3 IDoc being sufficient to map to the 834. This will take forever to do it from scratch or even without an example. Help please.

Hi
You can do 1:n multimapping
in message mapping in messages tab ..add both the structures in target tab and do the mapping
and in operation mapping add both the message interface on the target side
PLease go through this blog
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible

Does oracle B2B(11.1.1.6) supports to generate EDI VICS format based 856/810 messages?

Hi All,
I've checked the form that answers to receive a 850 EDI VICS formats, by removing GS08 codelist and that works good. This setup is to receive a PO from trading partner(Inbound).
But how the outbound(like sending 856/810/846 documents to partner) EDI VICS documents are generated in B2B?
Appreciate your help.
Thanks,
Levey

In your dmesg appears the following:
[ 110.659286] NVRM: Your system is not currently configured to drive a VGA console
[ 110.659294] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
[ 110.659298] NVRM: requires the use of a text-mode VGA console. Use of other console
[ 110.659301] NVRM: drivers including, but not limited to, vesafb, may result in
[ 110.659305] NVRM: corruption and stability problems, and is not supported.
Do you have any other video drivers installed that may be conflicting with the nvidia driver?
# pacman -Qs xf86-video
If not, try removing your nvidia xorg config and rebooting to a default set-up. It could be one of the settings in the xorg config.
# mv /etc/X11/xorg.conf.d/20-nvidia.conf /path_to_back_up_your_config
Cheers.

Conversion of EDI File format to IDOC format

We have a file in u201C.ediu201D format. We could not process this file with RSEINB00 ( IDoc inbound processing using file ) program.
1-) Could we directly do our process with this u201C.ediu201D file ? Or do we have to convert this u201C.ediu201D file to IDOC format?

If it's EDI format file (Ex: EDIFACT, X12 ...etc), we should convert the file to IDOc file by using mapping in subsystems like Gentran or TLe..etc. Conversion from edi format to idoc format will not be done in SAP.
Reddy

EDI File formats EANCOM2002 and UN 96A are same??

Hello Evyone,
The partner system wants the DESADV EDI file in EANCOM2002 format.
Iam having the XSD's for for the following formats.
DESADV_UN_D96A
DESADV_UN_D97A
DESADV_UN_D97B
DESADV_UN_D99B.
Does any of the above formats is equal to EANCOM2002??
PS: If i use any of the above XSD and the seeburger mapping name as "See_X2E_DESADV_UN_D96A".
Will it reach to partner system in EANCOM2002 format.
Let me know if it works??
Thanks & Regards
Seema.

Hi chirag,
I too observe the same.
Now im doing the development by using File adapter.
So i can finish off the development by using UN96A..
But when it goes live..we are going to replace it with AS2 adpter. Iam worrying of it may fail at the partner system because of wrong format??
Any idea any impact will happen??
Regards
Seema.

How to define the Structure and FCC parameters for EDI file format.

Hi All,
I have a EDI file(FTP)-->XI-->IDOC
the source file content is as follows
PR H01PHUPS
FH   SHP 0.0.5
H1   S0022323
W6   7752508853                     D
PT   1Z58R7070341111111
PT   1Z58R7070342222222
PT   1Z58R7070353333333
N1ST ZZ 142222
N3ST 8827 D OLD
N4ST MARCY
N1WH ZZ 2070
N3WH 401 QUALITY
N4WH HARRIS
DTENT20111206
DTSHP201112061754
N9LL BN20700033333333
N9NT
CD   CP      UPS
IT026
P1GD    VN A1111
PD   Product ID 1
QTORD000000000000010CA
QTSHP000000000000010CA
AM U 000000000000000000M
AM X 000000000000000000
LTLT 1112811111
AM G 000000000000000000
AM N 000000000000000000
AM TAX000000000000000000
AM SVC000000000000000000
AM COD000000000000000000
ST   00000000100000000010000000000000000000000000008500LB
Can any body share me how to declare the structure in DataType.
The first two characters in each record is constant , so this would be the keyfields right?
ex:- PR,FH,H1,W6,PT,AM,N1,N3,N4......
In Comm channel the FCC parameters
i need to go for fieldFixedLengths?
Thanks&Regards
Sai_SHA

Hi.
if you need to convert an EDI to XML you need to use an Adapter specific (e.g Seeburger) because PI doesn't support EDI files.
Also if you use a FCC , this configuration is for two level Header and Detail.
Check this.
http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/frameset.htm
Regards
Luis Ortiz

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

EDI 861 format

Has anyone worked or developed solution of processing 861 inbound Receiving Advice in INV?
Oracle e-Commerce/Gateway does list this transaction as one of the supported one so was wondering if anyone has any ideas they can share.
Thx

Hi John,
IDOC type PEXR2002 would be appropriate for receiving the payment advice notes.
I hope this answer helps you out.
Thank you.
Regards,
Karun.M

IDOC to EDI file in PI 7.0. ( exchange infrastructure)

i have to do one application
SAP ECC 6.0 -> SAP XI -> Non SAP File Server
Non SAP file server accepts only .edi format files.
m trying IDOC to File scenario. IDOC generated is not giving exact EDI format which needs to send. How to transfer EDI format file from this scenario.
if its done by file content conversion, pls describe more.
eg . file output(.edi file) should be in below form
EDI_DC40 100000000000027837646C 3012 O
E2EDK01005 100000000000027837600000100000001 XSEK 5.23120

Hi,
There are two ways:
1. You can find out if an EDI provider (3rd party) which supports XML EDI Messages so you can just send XML EDI messages You can use Seeburger Adapter to conver into EDI Format.
In general , If sender side is File the that file must be generated by EDI mappers tool like BIC.
If file is in receiver side you have to use some Adapter to conver into EDI format.
-you can use FILE/FTP Adapter with Seeburger modules.
-you can use Seeburger OFTP Adapter.
See the following documents to help you ..
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/alexander.bundschuh/blog/2006/03/14/integrate-sap-conversion-agent-by-itemfield-with-sap-xi
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
http://www.stylusstudio.com/edi/XML_to_X12.html
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
Check this for Conversions-
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
2. You can use EDI 834 Enrollment messages with XI you don't need an adapter - you can use adapter module:
a) you can develop the adapter module for file adapter yourself
for one message it will ont be that difficult
b) you can use SAP conversion agent to create the EDI adapter module
(it has many EDI messages included)
Thanks
Swarup

Handling Multiple 834 documents through B2B

Hi,
We are trying to send a daily reconciliation transactions HIPAA file using 834 format. We would like to know how to concat each individual transactions into one 834 EDI file for daily reconciliation.
We tried the batching option however we found that the header information of each transaction was also getting appended.We would want to concat only the body information.
Any help is appreciated.
Rudraksh

One option is query oracle b2b tables/view to get all the transactions and rerun them through b2b again to concat them,
Thanks,
Kathar

About EDI outbound file name

Hi Anuj,
When I test EDI X12 834 outbound, the file generated is in the format %From_party%_%unique_id%.dat. I am not sure the unique_id is message ID or transaction control number, anyway it is a timestamp unique.
My question is can I specify outbound file name format? File name convention is recently proposed. It is not compliant with the default outbound file name.
Thank you,
Alena
CGI

Hello Sir,
Thank you for reading my thread.
Yes, we have worked on edi 834 and completed a few different transactions with people's support in this forum. Now I am glad to help other people on this.
1. Is HCA Adapter required for EDI 834?
HCA is not required for EDI 834. There are a couple threads discussed this in the forum. You can search Anuj's comments regarding this. See the the link. Oracle B2B is the right solution.
https://forums.oracle.com/thread/2551859
2. Any Healthcare Libraries?
If you are encountering B2B validation problem, you need to install Healthcare Library. But your problem has nothing to do with that. If you don't install the healthcare library, you still can do everything except B2B validation.
3. Any patches
If you are running SOA Suite 11.1.1.6.0, you need to install Health Care Patch to fix B2B validation problem. That is a bug.
If you are running SOA Suite 11.1.1.7.9, you need to install HealthCare Library to fix B2B validation problem. It is the same bug.
4. Any other??
If you are using Oracle B2B, you need to active B2B ui project. It has already deployed on Weblogic server, but you need to activate it. You should be able to access B2B via:
http://localhost:7001/b2bconsole or: http://localhost:7101/b2bconsole
5. Any special care while generating .ecs,xsd,.dazt from doc editor???
I don't need .dazt. You need ecs and xsd for B2B configuration. I disabled a couple validation rules to meet our business requirements. You may not need to.
For your particular problem, as the error message says "it can't find the agreement for the trading partners. B2B needs three information to identify the agreement. The document type (here it is 820 or 834), From TP, and To TP. If these three things meet, then B2B should be able to find it.
Let me know how are you doing after you check these things.
Alena Li

B2B Error while generating 850 EDI Document

Hi All,
We are facing the following error in B2B while generating an EDI 850 outbound document.
To give a brief background of our process:
We are using a BPEL process to pick a fixed length file from FTP adapter and then transform it and provide it to B2B for converting it into an EDI 850 Purchase Order. The BPEL part of the Process is working fine and it is successfully transforming the fixed length file into intermediate XML that it gives to B2B engine.
In B2B, the ECS file that we use has been generated from an XSD and we upload the corresponding ECS and XSD in B2B during configuration.
But we get the following error when B2B converts it into EDI 850 format.
Error Brief :
5084: XEngine error - Invalid data.
I am also giving around 100 lines from the b2b log before this error occurred.
2006.10.30 at 01:50:14:416: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter AcknowledgementType = 997
2006.10.30 at 01:50:14:416: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter GroupSenderID = 19508030411I
2006.10.30 at 01:50:14:416: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter InterchangeECSFileBlob
2006.10.30 at 01:50:14:416: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter InterchangeAuthorizationInfoQual = 00
2006.10.30 at 01:50:14:416: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter GroupID = PO
2006.10.30 at 01:50:14:416: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter TagDelimiter = null
2006.10.30 at 01:50:14:417: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter TransactionECSFileKey = 1BA24E3F6DB690CAE0430A0B3E7290CA-274-1-42
2006.10.30 at 01:50:14:417: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter InterchangeSecurityInfoQual = 00
2006.10.30 at 01:50:14:417: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter GroupECSFileBlob
2006.10.30 at 01:50:14:417: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter TPName = CANON
2006.10.30 at 01:50:14:417: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter TransactionImplementationReference = null
2006.10.30 at 01:50:14:417: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter ReplacementChar = null
2006.10.30 at 01:50:14:417: Thread-11: Repository - (DEBUG) CatalogDriver manager == oracle.tip.model.metadata.CatalogMetaManager@9f90cf3
2006.10.30 at 01:50:14:417: Thread-11: Repository - (DEBUG) CatalogMetaManager getDriverjava.lang.InheritableThreadLocal@72418cf0 oracle.tip.repos.core.driver.CatalogDriver@121ccf4
2006.10.30 at 01:50:14:418: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Enter
2006.10.30 at 01:50:14:419: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl fullOutboundBatching = false
2006.10.30 at 01:50:14:419: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl validateEnvelope = true
2006.10.30 at 01:50:14:419: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Leave
2006.10.30 at 01:50:14:419: Thread-11: Repository - (DEBUG) LargeStringImpl.getString() - object OID - 20D326898FA9D054E0430A0B3E72D054-11-1-1
2006.10.30 at 01:50:14:421: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Enter
2006.10.30 at 01:50:14:421: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = ec_DataNodeName, val = [Interchange]
2006.10.30 at 01:50:14:421: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@34c90cf5
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = InterchangeSenderQual
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 01
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = InterchangeSenderID
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 195080304
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = InterchangeReceiverQual
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 01
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = InterchangeReceiverID
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 0415306925
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = InterchangeControlVersion
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 00401
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Enter
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = ec_DataNodeName, val = [Group]
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@2c760cf5
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = GroupID
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = PO
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = GroupSenderID
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 19508030411I
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = GroupReceiverID
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 0415306925
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = GroupVersionNumber
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 004010
2006.10.30 at 01:50:14:425: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Enter
2006.10.30 at 01:50:14:425: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = ec_DataNodeName, val = [Transaction]
2006.10.30 at 01:50:14:425: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
2006.10.30 at 01:50:14:425: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
2006.10.30 at 01:50:14:425: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
2006.10.30 at 01:50:14:425: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@25070cf5
2006.10.30 at 01:50:14:425: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = TransactionID
2006.10.30 at 01:50:14:425: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 850
2006.10.30 at 01:50:14:427: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = SegmentDelimiter
2006.10.30 at 01:50:14:427: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 0x0A
2006.10.30 at 01:50:14:427: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = ElementDelimiter
2006.10.30 at 01:50:14:427: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 0x7D
2006.10.30 at 01:50:14:427: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = SubelementDelimiter
2006.10.30 at 01:50:14:427: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 0x3E
2006.10.30 at 01:50:14:427: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = RepeatingSeparator
2006.10.30 at 01:50:14:427: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = null
2006.10.30 at 01:50:14:428: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = ReplacementChar
2006.10.30 at 01:50:14:428: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = null
2006.10.30 at 01:50:14:428: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:reset Enter
2006.10.30 at 01:50:14:428: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:reset Leave
2006.10.30 at 01:50:14:428: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = TPName
2006.10.30 at 01:50:14:428: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = CANON
2006.10.30 at 01:50:14:429: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Enter
2006.10.30 at 01:50:14:429: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Leave
2006.10.30 at 01:50:14:429: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument XML = 1
2006.10.30 at 01:50:14:429: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument no result from XDataToNative
2006.10.30 at 01:50:14:442: Thread-11: B2B - (DEBUG) iAudit report :
Error Brief :
5084: XEngine error - Invalid data.
iAudit Report :
<?xml version="1.0" encoding="UTF-16"?><AnalyzerResults Guid="{06B942E5-E267-DB11-9E73-006163130000}" InterchangeReceived="1" InterchangeProcessed="1" InterchangeAccepted="0"> <ExecutionDate>Monday, October 30, 2006</ExecutionDate> <ExecutionTime>01:50:14 AM (EST)</ExecutionTime> <AnalyzerReturn>Failed</AnalyzerReturn> <NumberOfErrors>1</NumberOfErrors> <ErrorByCategory> <Category Name="Rejecting"> <Severity Name="Normal">1</Severity> </Category> </ErrorByCategory> <Status>Finished</Status> <DataFile> <FilePath/> <FileName/> <LastModified/> <FileSize/> <DataURL>file://</DataURL> </DataFile> <Interchange Guid="{424043E5-E267-DB11-9E73-006163130000}" InterchangeAckCode="R" FunctionalGroupReceived="1" FunctionalGroupProcessed="1" FunctionalGroupAccepted="0" RError="0" NError="0" OtherWI="0"> <DataXPointer> <StartPos>0</StartPos> <Size>1337</Size> </DataXPointer> <NodeInfo> <Links> <Link Name="InterchangeSenderQual">01</Link> <Link Name="InterchangeSenderID">195080304</Link> <Link Name="InterchangeReceiverQual">01</Link> <Link Name="InterchangeReceiverID">0415306925</Link> <Link Name="InterchangeControlVersion">00401</Link> </Links> <Properties> <Property Name="Standard">X12</Property> <Property Name="SegmentDelimiter">0xa</Property> <Property Name="ElementDelimiter">0x7d</Property> <Property Name="SubelementDelimiter">0x3e</Property> <Property Name="RepeatingSeparator"/> <Property Name="ReplacementChar">0x20</Property> </Properties> </NodeInfo> <FunctionalGroup Guid="{F28543E5-E267-DB11-9E73-006163130000}" FunctionalGroupAckCode="R" TransactionSetsIncluded="0" TransactionSetsReceived="1" TransactionSetsProcessed="1" TransactionSetsAccepted="0" RError="0" NError="0" OtherWI="0"> <DataXPointer> <StartPos>0</StartPos> <Size>1337</Size> </DataXPointer> <NodeInfo> <Links> <Link Name="GroupSenderID">19508030411I</Link> <Link Name="GroupReceiverID">0415306925</Link> <Link Name="GroupVersionNumber">004010</Link> </Links> <Properties> <Property Name="GroupID">PO</Property> </Properties> </NodeInfo> <Transaction Guid="{33303938-3738-3533-3630-353932353933}" TransactionAckCode="R" RError="1" NError="0" OtherWI="0"> <DataXPointer> <StartPos>0</StartPos> <Size>1337</Size> </DataXPointer> <NodeInfo> <Links> <Link Name="TransactionID">850</Link> </Links> <Properties/> </NodeInfo> <TransactionErrors> <Error ErrorCode="{F35AFE03-C479-4F96-B4F1-2EF36DABC5FE}" Severity="Normal" Category="Rejecting" Index="1" ID="50840000"> <ErrorBrief>5084: XEngine error - Invalid data.</ErrorBrief> <ErrorMsg>Invalid data.</ErrorMsg> <ErrorObjectInfo> <Parameter Name="ErrorLevel">0</Parameter> <Parameter Name="Name">XData2Native</Parameter> <Parameter Name="_ec_dn_guid_">{33303938-3738-3533-3630-353932353933}</Parameter> <Parameter Name="_ec_index">0</Parameter> <Parameter Name="ec_error_scope">Transaction</Parameter> </ErrorObjectInfo> <ErrorDataInfo> <Part1/> <ErrData/> <Part3/> <DataXPointer> <StartPos>0</StartPos> <Size>0</Size> </DataXPointer> </ErrorDataInfo> </Error> </TransactionErrors> </Transaction> </FunctionalGroup> </Interchange></AnalyzerResults>
2006.10.30 at 01:50:14:443: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sErrorGuid = {F35AFE03-C479-4F96-B4F1-2EF36DABC5FE}
2006.10.30 at 01:50:14:443: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sDescription = Invalid data.
2006.10.30 at 01:50:14:443: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sBrDescription = 5084: XEngine error - Invalid data.
2006.10.30 at 01:50:14:443: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = ErrorLevel sParameterValue = 0
2006.10.30 at 01:50:14:443: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = Name sParameterValue = XData2Native
2006.10.30 at 01:50:14:443: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = ecdn_guid_ sParameterValue = {33303938-3738-3533-3630-353932353933}
2006.10.30 at 01:50:14:443: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = ecindex sParameterValue = 0
2006.10.30 at 01:50:14:444: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = ec_error_scope sParameterValue = Transaction
2006.10.30 at 01:50:14:444: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument added Hash Key = {33303938-3738-3533-3630-353932353933}
2006.10.30 at 01:50:14:444: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument batch Position = 0
2006.10.30 at 01:50:14:444: Thread-11: B2B - (ERROR) Error -: AIP-51505: General Validation Error
     at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:1668)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1132)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:710)
     at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:821)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:532)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java(Compiled Code))
     at java.lang.Thread.run(Thread.java:568)
If anybody has faced a similar issue, then please post on how to overcome this error.
Thanks In Advance,
Dibya

Hi,
I am facing a similar problem.
I am trying to transfer a xml in 850 format with internal properties of Interchange,Group and Transaction from BPEL to B2B.My BPEL setup consist of :
A partnerlink which read xml in 850 format using file adapter.
A receive Activity which receive the data.
I have created a partnerlink which use AQ Adapter to enqueue data in IP_OUT_QUEUE.
A invoke Activity invokes this partnerlink.
Then I have assigned the read data in Receive to input variable of Invoke activity.
I have used another Assign Activity to populate the Header; and passed this header in Invoke Activity.
In B2B I have created two trading partner one remote and one host, defined a business action and defined the Communication capability for them. I am using FTP1.0 . I defined a agreement and deployed the configuration in b2b server.
The ecs and xsd I am using is the one provided with Purchase order tutorial, it contains only ST-SE,I have also tried with envelope segments for 4010-namely
ISA-->GS-GE-->IEA.When I am turning off validation and translation its throwing the input XML as output in the .dat file. If I turn on Translation I am getting unrecognized data last known segment is GSA.In this case the input XML had internal properties of Interchange and Group.If I remove the transaction part from ST-SE the dat file is generated in native dat format but with ISA -GS-GE -IEA but no transaction portion.
As a work around I tried seperate group ecs,interchange ecs and transaction ecs and tried to pass a 850 xml with only transaction fields.
I have tried with no ecs file at all and in that case the dat file is also generated.So does this mean that B2B have seeded ecs file which it use as default if I dont use any ecs file?
It seems from the post you have successfully completed this part can u send me :
1>The 850 ecs and xsd file you used.
2>If you have used any group ecs and interchange ecs.
3>The input you are sending in BPEL.
4>The BPEL process and B2B export xml you are using in zipped format.
My mail ID: [email protected]
phone:09831964607
I tried out different ways suggested in the post but nothing seem to be working for me,I am still getting the invalid data error and if it is creating the dat file only envelope segments are created.
If you send me the working example I can work on it as baseline, this will be of great help in my work.

Creation of EDI 820 for outgoing payments in SAP

Hi Experts,
We have a requirement where in we need to create an outgoing payment file in EDI820 with in SAP.
We basically need to create specifications in EDI820 format for the bank to print checks and make wires and EFT payments.
That EDI820 file will be created at the time of Automatic Payment Run(F110).
Right now our client is sending a flat file to external service provider and they are creating EDI820 files and sending to the banks. Going forward the services of this service provider will be decommissioned and an EDI820 file is to be generated in SAP and sent to the bank via SWIFT Net.
Bank has provided us a sample file and file format for EDI820. This file format contains ST, BPR, RMR, REF etc records. There records have different codes and qualifiers.
As far as we have analyzed, there are no standard SAP programs that can generate flat file in the EDI 820 format. Therefore we are heading towards developing a Z program for creating an EDI820 format.
We are facing problem in mapping this file with SAP fields. We need to know how exactly we can map this file in SAP so as to create a program to generate EDI820. If anybody has had a similar requirement (for creating outbound EDI820 in SAP) and can provide us some lead, it will be greatly helpful for us.
Thanks in advance for the help!

Have you worked on this requirement?
Could you please provide step by step instructions to configure and the high level process?

Creation of EDI 820 fromat for outgoing payments in SAP

Hi Experts,
We have a requirement where in we need to create an outgoing payment file in EDI820 with in SAP.
We basically need to create specifications in EDI820 format for the bank to print checks and make wires and EFT payments.
That EDI820 file will be created at the time of Automatic Payment Run(F110).
Right now our client is sending a flat file to external service provider and they are creating EDI820 files and sending to the banks. Going forward the services of this service provider will be decommissioned and an EDI820 file is to be generated in SAP and sent to the bank via SWIFT Net.
Bank has provided us a sample file and file format for EDI820. This file format contains ST, BPR, RMR, REF etc records. There records have different codes and qualifiers.
As far as we have analyzed, there are no standard SAP programs that can generate flat file in the EDI 820 format. Therefore we are heading towards developing a Z program for creating an EDI820 format.
We are facing problem in mapping this file with SAP fields. We need to know how exactly we can map this file in SAP so as to create a program to generate EDI820. If anybody has had a similar requirement (for creating outbound EDI820 in SAP) and can provide us some lead, it will be greatly helpful for us.
Thanks in advance for the help!

The program that sends the flat file should give you all the necessary fields, selection criteria, etc. If the third-party constructs EDI820 from it, then there is enough data in that file for you to add steps to create an 820.
So, I'd start with the existing program, a particular outbound file and a copy of the 820 file created from it (if that can be obtained) and figure out how the intermediary converted the data to the correct format. Piece of cake, right?

XI EDI 834 format

Similar Messages

Maybe you are looking for