O/p Type EDI

Hi all!
   I know O/p type w.r.t Scripts (where we assign the print program & layout for printing)
   can i know the same in case of EDI what the o/p types plays the role.
   Looking for your reply guys.
   Thanks
    Rahul.

Hi,
if we want to send the information related to purchase order or salesorder to other sap or legacy system then we use ALE/EDI as the medium.instead of using print output,FAX as medium.we use ALE/EDI medium.
Regards,
NAGARAJ

Similar Messages

Message type EDI is not triggering for outbound deliveries

Hello,
When ever the shipment status is completed message type EDI is triggered for the outbound delivery.
However, in spite of the shipment completion the DESADV EDI message is not created in the outbound delivery.
So, i request you to help me in this issue.
Regards,
Anil

Hi,
1st please check the partner porfile for whom it is sent ( Eg -- Ship to party) using T.code WE20 in partner type ku, look for the customer for whom it is sent.
Check for the message type wheter it is add in outbound parameteres.
Finally check the varaint of shipment whether the required output is maintained in the shipment varaint and also make sure that condition record is maintained for the output.
You find some solution with this.
Regards
vk

Need help with output type EDI for ERS

All,
I want to be able to run and ERS settlement and have the invoices created sent via EDI/XML to the supplier.   I have several questions on the set up.
1) I have output type ERS6 which is defined as ERS EDI. I assume because it does not start with Z* this is SAP standard, so I shouldn't have to modify any of this.
2) I've added my supplier to this output type.
3) I assume I need to create a partner profile for this supplier? If so can someone tell me the message type to use?
Is there any set up I'm missing in this process?   I've executed ERS but do not get an idoc and I'm fairly certain it's because I haven't done the partner profile set-up.
Thanks for your help.
Sandra

Hi,
You don't have to modify thise setup unless you have any customized requirement.
You are missing partner profile setup.Carry out the setup and run MRRL tcode to create the idocs
Enter the following values using tcode WE20.
Field                                       Value
Message type                         GSVERF
Partner type                             LI (vendor)
Partner function                        LF (vendor)
Port                                         SUBSYSTEM ( Port to your middleware)
Output mode                            such as Collect IDocs
Basic type                                GSVERF01
Application                                 MR
Output type                                ERS6 or the type you have defined
Regards,
Karuna

Sales Order - Output Type EDI

Hi All,
I am working on an SD requirement in which I get Perchage Order from third party through IDoc (Basic Type ORDERS05).
After receiving this IDoc I have to create a Sales Order (that I am doing using FM IDOC_INPUT_ORDERS). Here as soon as Sales Order gets created, an Outbound IDoc gets triggered (Message Type - ORDRSP) for confirmation. This outbound idoc gets created every time I do any change in sales order items. Every thing is visible in trasaction.
My problem is, I want to get all the outbound IDocs triggred in a particular sales order in my Z program.
Please let me know if there is any 'Table' or 'Function Module' or any other way to get them.
Thanks !!

Hi Immanuel,
Thanks a lot for your ans !!!
It solved my prob.
Many Thanks ....
Rewarding you points for this
Regard,
Neha

EDI Message type issue

Dear Friends,
In my current project my issue is related to EDI Message type the problem is as below
If I use output type (message type) NEU which is SAP standard and if I select this out put type (NEU) with medium EDI after saving this I can see all the data segments in Outbound Idoc.
Now the actual issue is if I use the ZNET customize output type which is the extension of NEU with medium type EDI after saving this if I check the Idoc (We02) I am not able to see few purchase orders data segments like E1EDKT1(Header Text ) and E1EDPt1(Item Text)
What could be the reasons? Is there any setting where output types and data segments are linked
Your help will be highly appreciated
With Best Regards,
Ashish Vats

Hi,
Thanks for your reply.
I have maintained all the parameters in partner profile.... I think Could not explained the issue in detail.
the issue is as below
When I select the output type ZNET in purchase order and medium EDI(Partner profile for Vendor maintained for outbound PO) after saving the same when I check the outbound IDOC generated by system in that some segments are not coming while in NEU output type all the segments are coming properly.
ZNET is the Extension of NEU .. now my question is to forum where output types are linked with segments ?so that I can compare the ZNET with NEU and findout the missing segments or could link the missing segments with ZNET
Hope I could explained you...........
Regards,
Ashish

B2B Add on (Edi separator) IDOC AAE Receiver Error

Hi
We are getting an error, Transmitting the message to endpoint <local> using connection EDISeparator_http://sap.com/xi/XI/EDISeparator failed, due to: com.sap.engine.interfaces.messaging.api.exception.ConfigException: No sender agreement configured that matches the message's header fields (sender party: "xxxx", sender service: "", interface: "xxxx", receiver party: "", receiver service: "xxxx") when using IDOC_AAE Receiver adapter with ICO, scenarion works fine with standard IDOC adapter on integration engine
We have 7.31 dual stack with B2B addon sp03
We are using control records from mapping (reciver idoc adapter >advanced>control record in IDOC XML> all options selected)

Hi,
Yes, I filled the information on EDI separator channel, however this works fine with standard idco reciever adapter on integration engine, the issue is when I use ICO with Idoc_aae reciever adapter
you mean to say I have to use (.*) filling all sender edispeartor channel information mandatorily
what if I have to use the information to filter the message type from a multiple message type EDI file
Again this works absolutely fine with idco adapter on IE

Condition types EDI1 & EDI2

How are Condition types EDI1 & EDI2 used?

dear venkat
EDI1 AND EDI2 (Customer expected price):
In normal business process, business charges certain price for particular material but customer expects certain price. Customer expected price can be entered manually or through EDI (Electronic Data Interchange). Someone in the business may accept or reject customer expected price. So that system has to block the billing document by considering sales document as a incomplete one so that the document can be released by using transaction code V.25 by accepting or rejecting customer expecting price.
Condition type EDI 1 is used to compare the net price for each item whereas condition type EDI2 is used to compare the overall item value (net price * quantity)
For EDI1, calculation is = 8; for EDI2, calculation is = 8 make it as a manual/statistical.
In V/08, include EDI1 and EDI2 as last steps.
Go to VA01, raise the sales order
Go to item condition screen, now include EDI1 as 40/- and EDI2 as 40/-
Raise delivery and invoice. System block invoice
Now go to V.25 and click on release and now raise the invoice
The customer expected price is differ from the automatically determined price or value by more than the maximum difference allowed then the system will look this order as incomplete when it is saved .
The blocked sales order should be released by concern person through work list traction code: V.25
     logistics
     S d
     sales
     Information. System
     Work listV.25 release customer expected price.
Select the sales order click on release, save and exit.
rewards pls
siva

Output type for XML in ECC - XI conversion?

Hi,
I ahve few queries regarding the PO o/p sent from ECC for XML output type...
I header XML is supported in ECC from EHP4..is this true?
If PO from ECC need to be sent out via XML,the output configuration for ECC PO's need to be changed also?
Also if PO o/p needs to be sent EDI or XML,my understanding is XI will be mandatory for PO to be sent to supplier system.Can you pls confirm.
Also when we say PO is sent via EDI(idoc) or XML,is there any difference in the data format/way in which data is sent to XI?If there any conversion happening on XI based on output type EDI or XML?
On ECC side,is XML one of the output type or we just ALE and EDI?

Hi,
Check this help.
http://help.sap.com/saphelp_srm30/helpdata/en/91/41faf2c220e84c9002a4ae4cc1906a/content.htm
Best Regards,
Ravi

Re : Inter company stock transfer through EDI

Hi
      How to do the intercompany stock transfer through EDI. In this if Purchase order is created from one comapny a sales order should created automaticall in another Company. Fot this what is the SPRO settings.
How to do this.
Thanks
Anto

Hi,
continues from here,
Inbound file:     edi_in
Function module:     See text below.
Status file parameters
Directory:     /home/edi/<portname>/
Outbound file:     status.idoc
Function module:     Leave blank if using above
u2022     Both the portname and the exchange directory should be created according to the same naming convention. However, the portname should be in upper case whereas the corresponding directory name should be in lower case (see examples below).
     Portname (upper case):
                         <portname>
     Exchange directory name (lower case):
                         /home/edi/<portname>
     where <portname> consists of:
     EDI<system name><client number><id char>
     <system name> is the name of system on which port exists eg.      F01, PG1 etc.;
     <client number> is name of client on system which will use this      port; and
     <id char> is a single alphabetical character such as u2018au2019,u2019bu2019 etc.      typically,      u2018au2019 will denote dynamic outbound file naming (used      for testing) whereas      u2018bu2019 will denote static outbound file naming.      All ports will use static      inbound filenames.
For example, the name of a port using dynamic file naming on system F01, client 610 would be named EDIF01610A. The exchange directory would be named edif01610a. Similarly, the name of port using static file naming on system PG1, client 600 would be EDIPG1600B. The exchange directory name would be edipg1600b.
Note that the function u201CEDI_PATH_CREATE_USERNAME_DT_TMu201D can be used in the u201CFunction moduleu201D field of the Outbound file parameters if IDocs are to be written to multiple files. In this case, the corresponding outbound filename field should be left blank. The standard IDoc exchange interface between the SAP EDI component and the EDI subsystem uses a single file for each transfer direction. However, should the exchange interface change, or for testing purposes, the function modules for dynamic naming can be used.
2.4.2.     Control of EDI processes in R/3
2.4.2.1.      Maintain: Outbound Process Code (WE41)
IMGCross-Application ComponentsALE Extensions  Outbound
Check that the outbound EDI processes in the R/3 system are defined. Indicates which ABAP/4 function module to execute in order to create an outbound IDoc.
The following assignments are available for R/3:
2.4.2.2.      Maintain: Inbound Process Code (WE42)
IMGCross-Application Components  ALE  Extensions  Inbound
Check that the inbound EDI processes in the R/3 system are defined. Indicates what kind of inbound processing to execute.
     A long list of options is available under Processing by function module, relevant ones are:
INVF     INVOIC FI     Invoice receipt (Financial Accounting)
INVM     INVOIC MM     Invoice verification (Mat Management)
ORDC     ORDCHG     Change customer order
ORDE     ORDERS     Create customer order
ORDR     ORDRSP     Purchase order confirmation
2.4.2.3.      Control: System Process Codes (WE40)
     Choose Processing by task. Check that the codes indicating the type of EDI processing error are defined. The only valid entries are the entries shown on the screen, as they are directly called via the EDI basis module.
2.4.2.4.      Control: Status maintenance (WE47)
     Check that the codes indicating status of IDoc processing are defined. The status values for outbound IDocs are between 01 and 39, while the status values for inbound IDocs begin with 50. These values are delivered by SAP and cannot be customised.
2.4.2.5.      Control: Partner Types (WE44)
     Check that the codes that identify the commercial relationships between the receiver and sender are defined. Values are delivered by SAP. Names of the programs and routines that validates the entry of the EDI trading partner ID:
Partner type     Report name     Form routine
B - Bank     RFETESTP     READ_T012
KU - customer     RSETESTP     READ_KNA1
LI - vendors     RSETESTP     READ_LFA1
LS - logical system ( ALE)     RSETESTP     LOGSYS
2.4.2.6.      Control: Forward Inbound (WE45)
Allows for the forwarding of IDocs to a specific application. Contains the exactly defined destination of an inbound IDoc within the SAP system. Usually no changes are required.
2.4.2.7.      Control: Status Process code (WE56)
Choose Processing by task: The following set-up has been provided as default:
Process code:     EDIS
Identification:     TS30000078
Description:     EDI-IDoc status record processing
The process code is for inbound status, The ID type is an identification code for inbound processing method (workflow or standard task) of the status record.
3.     MM IMG CONFIGURATION
3.1.     Global settings (IMG):
3.1.1.     Units of measure (IMG  Global settings):
The ISO code is important for EDI. It is used to convert the internal SAP units of measure into standard units.
The MM configurer must link the Unit Of Measure, EACH, with the ISO code PCE (Piece).
3.2.     Link Schema to Purchase order
Check the following:
IMG  MM  Purchasing  Message determination  Message determination  Message Schemas
Execute transaction u201CDefine Message Schemas for Purchase Orderu201D
Select transaction: Assign Schema to purchase order
Add:      Usage =B for output
     Application = EF for purchase order
     Procedure = RMBEF1 for purchase order
3.3.     Link application to EDI interface via message control:
IMG  MM  Purchasing  Messages  Output Control
Check following under Output Control:
     Condition table
     Access sequence
     Message types
     Message schema
     Output control
3.4.     Enabling Multiple Output for Purchase Orders (Optional)
For example: EDI & Printing
IMG  MM  Purchasing  Message determination  Message determination Access sequence
u2022     Create new access sequence (e.g. ZPUR), copy the access sequence 0001 but leaving the ''E'' flag blank (Exclusive is off). (Transaction M/50)
u2022     Goto Define message types  maintain message types:
     Create a new message type (e.g. NEU1), setting the output type to 1 for printed output and using ZPUR as access sequence. (Transaction M/34)
u2022     Goto Message Schema  define message schema  maintain output determination procedure:
     Update procedure RMBEF1 by adding a step for the new condition type (e.g. NEU1) prior to the standard delivered step for NEU. (Transaction M/36)
u2022     Goto Processing program  Define Processing program  Output program: Purchase Order.
     - Add a NEU1 record to table TNAPR. The program FORM Routine and layout must be specified. (Copy an existing NEU record). (Transaction OMTB)
u2022     Goto Processing program  Define Processing program  Output by partner type.
     - Add NEU1 record for VN (vendor). (Transaction OMTG)
3.5.     Link Output type (fax=2, E-mail=7) to NEU (Purchasing)
IMG  MM  Purchasing  Message determination  Message determination Access sequence
u2022     Goto Processing program  Define Processing program  Output program: Purchase Order.
     - Add another NEU record to table TNAPR with the appropriate output medium. Copy an existing NEU record. (Transaction OMTB)
u2022     Goto Processing program  Define Processing program  Output by partner type.
     - Add NEU record for VN (vendor). (Transaction OMTG)
4.     SD APPLICATION REQUIREMENTS
Assumption: SD is only used for testing purposes and configuration is based on a need basis - only configure the minimum.
Reference SAP Course manual Chapter 11.
4.1.     EDI Configurations
4.1.1.     Conversion of SAP item categories to IDOC item categories (VOE1)
IMG  S&D  EDI  EDI Messages  Conversion of SAP item categories to IDOC item categories
Add the following entry:
For Standard Item description :     0     OR     LDN
Typically error message: ''Transaction LDN is not defined".
4.1.2.     Partner functions
IMG  S&D  EDI  EDI Messages  Configure EDI Partners Partner  Application  Partner function
Check that the following partner functions exist: (at least)
SP     Sold-to party
VN     Vendor
BP     Bill-to party
SH     Ship-to party
Note - the German abbreviation is passed to the IDoc.
4.2.     S&D Sales Configurations
4.2.1.     Maintain Item categories
IMG  S&D  Sales  Sales document  Sales doc item  Define item categories
Add LDN for standard item:
          Item type = B
          Relev for billing = B
          Tick following:     Bus data item
                              Sched line allowed
                              Credit active
                              Pricing
          Screen seq. grp = N
4.2.2.     Assign Item categories
IMG  S&D  Sales  Sales document  Sales doc item  Assign item categories
Add/Update the following entries:
     1     2     3
Sales doc type     OR     OR     OR
Item category group     NORM     DIEN     LEIS
Item category     LDN     TAD
LDN     LDN
4.2.3.     Assign Schedule line categories
IMG  S&D  Sales  Sales document  Schedule lines  Assign Schedule line categories
Add Item category LDN to table (with no other parameters).
4.3.     S&D Pricing Configurations
4.3.1.     EDI pricing condition types
IMG  S&D  Basic functions  Pricing  Pricing control  Define condition types  Maintain condition types
Maintain the following condition types:
     EDI 1 - Calculate type =C for Quantity
     EDI 2 - Calculate type = B for Fixed amount
4.3.2.     SD Pricing procedures (V/08)
IMG  S&D  Basic functions  Pricing  Pricing control  Define & Assign pricing procedures
Maintain pricing procedure for ZVAA01 (Standard).
Select control and add EDI1 and EDI2 as steps 1 and 5 respectively with no other parameters.
5.     INVOICE IMG CONFIGURATION
No additional IMG configuration (not partner specific) was needed for Inbound Invoice processing.
Thanks,
Swamy H P

EDI and ALE

hi,
can anyone tell what are the table get affected while using EDI and ALE , and also with their explanation.
thanks
Ganesh

ALE tables.
EDMSG - logical message type
TBD05 - distribution model for message type
TBDLS - logical system
TBD00 - view of customer model
TBD10 - idoc field in ALE objects
BDCP - change pointer
CDHDR - chnage document header
CDPOS - change document item
TBD21 - ale idoc reduction
TBD30 - ale conversion rule
TBD11 - ale object type
EDI Tables
EDI_DC40 - Idoc control record structure
EDI_DC - Control record structur
EDIDC - Idoc control record
EDI_DD40 - Idoc data record structure
EDI_DD - data record structure
EDID4 - Idoc data record from v4
EDID2 - Idoc data record from v3
EDIDS - status record idoc
EDIDD - data record idoc
EDID3 - Idoc data record from v3

File type support by SAP XI

Hello,
I looking for table with details about file formats that support by SAP XI.
file format that support by SAP XI with adding's (like Itemfield) and formats that not support by SAP XI.
For example:
File type .CSV support by SAP XI
File type .EDI support by sap xi with Itemfield add in
Thank you in advance for your help
Elad

XI talks with files using its File Adapter. This file adapter can pick up any file with any structure.
After picking up the file, the task of adapter is to convert it into XI readable XML format. For this,
- XI could directly understand input xml file or
- XI could read text file using file content conversion or
- u could write ur own code to read structures of any other file
So no limitations as such.
Regards,
Prateek

Query regarding NACE output types

Hello Gurus,
I have two Output types ZABC & ZXYZ. I have placed ZABC and ZDEF in this order in Procedures. ZABC is of the type 'Special Function' while ZXYZ is of the type 'EDI'. Please help me understand if these output types will be triggered parallely or in the sequence described above.
Thanks
Rohit

Hi,
If you are triggerring both the output types, it will process in the order which you triggered.
Thanks
Arul

Configuration of condition type..Urgent..

Hi All,
Can anyone let me know the process of copying a new ZED1 from std Condtion type EDI(customer Expected Price) in sales order creation. Am an ABAPER. Like i got the req to modify the routine which is associated wid EDI and to build a new routine so that i can attach that to ZED1 without making changes to Std SAP Settings..
Regards,
Parvez.

Have got an obj on SD. Its an enhancement. I need to change standard routine. I know the routine. But the thing is that where sud i write that routine after modifying the standard routine.
The std routine is associated wid a std condition type EDI1(Customer Expected Price) and this EDI1 has to b copied to new condition type i.e., ZEDI1. As i told u earlier that EDI is associated with routine # 9 (frm_kondi_wert_009). I think, after configuring this new ZED1, the new routine has to attached to it... but i dont know how it sud be?? and Where this new routine has to be written..
You can find the routine in VOFM tc Formulas --> Condition Value and the routine no# 9.
Configuration of New condition is done becoz we dont want to change the std settings of SAP.. Plz provide me steps for configuration too.. if u guys know..
My Question is Wher exactly we need to write a new routine and how?
I have made one approach in creating a new routine thru VOFM tc. Formulas -->Condition value and I entered new routine no. 909 and its description and pressed source code icon on the appl tool bar, hoping that i cud enter directly into the coding screen but system was askin the Access key, so i cudnt proceed further. I tried this in IDES.
Can u tell me whether i was right in doing so..?? If so, can u take me further into the processing....
And moreover in the configuration part, i think we have to do two steps as per my knowledge... like.. We first copy the std EDI to ZED1 and then we assign this condition type to ZED1.. Can u thru some more points on it...
Am bit confused.. can u guys help me out...
Thanks and Regards,
Parvez...

Sap edi

what is sap mm with EDI what does EDI stand for? An for what it is been used??

hi,
It is an output type EDI(Electronic data interchange)
An inter-company, application-to-application communication of data in standard format for business transactions. Electronic Data Interchange (EDI) is a set of standards for structuring information that is to be electronically exchanged between and within businesses, organizations, government entities and other groups. The standards describe structures that emulate documents, for example purchase orders to automate purchasing. The term EDI is also used to refer to the implementation and operation of systems and processes for creating, transmitting, and receiving EDI documents.
thanks
Suresh.

Java.lang.UnsatisfiedLinkError: com/edifecs/xengine/xeobjects/XEHelper.cre

Protocol Name : EDI_X12
Document Verison : V4010
Document Type : 850
Document Definition as : EDI_X12-V4010-850-850def
Listening Channel :
Protocol : Generic File 1.0
Tansport Protocol Parameter :
Folder Name :/u01/ftp_root/Inbound (A folder on Server)
File Format : %FROM_PARTY%_%DOCTYPE_NAME%_%DOCTYPE_REVISION%.dat
Preserve File Name : Enabled(Checked)
Host Trading Partner :
Profile :Vallues Given for following Identifier Types
Identifier Type : EDI Group ID , EDI Interchange ID , EDI Group ID Qualifier,EDI Interchange ID Qualifier
Document : EDI_X12-V4010-850-850def (Receiver = Checked)
It's Receiver of the Document.
Host Channel :
Protocol : Generic File 1.0
Tansport Protocol Parameter :
Folder Name :/u01/ftp_root/Outbound (A folder on Server)
Remote Trading Partner:
Profile :Vallues Given for following Identifier Types
Identifier Type : EDI Group ID , EDI Interchange ID , EDI Group ID Qualifier,EDI Interchange ID Qualifier
Document : EDI_X12-V4010-850-850def (Sender= Checked)
It's Sender of the Document.
Agreement Direction :
From Remote Trading partner --> To Host Trading Partner
Agreement Parameters : Only Translate = Checked.
Identifier are selected and channels specifies in the Agreement as required.
Note :
1. .ecs , .xsd and .dat files were generated by B2B Doc Builder
2. File saved in format as :
%FROM_PARTY%_%DOCTYPE_NAME%_%DOCTYPE_REVISION%.dat
Following are the installation specifications :-
1. OS Linux 64 bit with JRocket 64 bit. (Yes Verified)
2. Environment :Single (Not-Clustered) (Yes Verified)
3. XEngine Installed and Installation Tested. (Yes Verified)
4. LD_LIBRARY_PATH set (Yes Verified)
5. Other Xengine Environment Variables are set. (Yes Verified)
Problem I am facing are:
1. While creating agreement following parameter need to be "checked" if we wish to get a translation of document from EDI-->XML
"Agreement Parameters : Only Translate = Checked.
If I don't check Translation,means if I don't enable translation.It works fine.
File is picked from Source location and Dropped into Destination Via B2B
However if I check(Enable) Translation it's giving Processing Error java.lang.UnsatisfiedLinkError"
Server.log says :
[d03-c02-s01] [ERROR] [] [oracle.soa.b2b.engine] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@23e23fcf] [userId: <anonymous>] [ecid: 11d1def534ea1be0:507ef52a:12f581580da:-8000-0000000000059a10,0] [APP: soa-infra] java.lang.UnsatisfiedLinkError: com/edifecs/xengine/xeobjects/XEHelper.createN2XNative()Lcom/edifecs/xengine/xeobjects/XEDataProc;[[
     at com.edifecs.xengine.xeobjects.XEHelper.createN2X(Unknown Source)
     at oracle.tip.b2b.document.edi.EDIDocumentPlugin.processIncomingDocument(EDIDocumentPlugin.java:1113)
     at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:2488)
     at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1638)
     at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:3978)
     at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3654)
     at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3127)
     at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:619)
     at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:220)
     at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
     at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
     at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
java.lang.UnsatisfiedLinkError: com/edifecs/xengine/xeobjects/XEHelper.createN2XNative()Lcom/edifecs/xengine/xeobjects/XEDataProc;
     at com.edifecs.xengine.xeobjects.XEHelper.createN2X(Unknown Source)
     at oracle.tip.b2b.document.edi.EDIDocumentPlugin.processIncomingDocument(EDIDocumentPlugin.java:1113)
     at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:2488)
     at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1638)
     at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:3978)
     at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3654)
     at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3127)
     at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:619)
     at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:220)
     at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
     at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
     at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
[2011-04-18T09:46:36.241+02:00] [d03-c02-s01] [ERROR] [] [oracle.soa.b2b.engine] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@23e23fcf] [userId: <anonymous>] [ecid: 11d1def534ea1be0:507ef52a:12f581580da:-8000-0000000000059a10,0] [APP: soa-infra] java.lang.IndexOutOfBoundsException: Index: 0, Size: 0[[
     at java.util.ArrayList.RangeCheck(ArrayList.java:547)
     at java.util.ArrayList.get(ArrayList.java:322)
     at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:2894)
     at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1638)
     at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:3978)
     at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3654)
     at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3127)
     at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:619)
     at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:220)
     at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
     at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
     at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Suggestions/Help/Guidence are welcome.
Am struck on this ..
Thanks in advance to B2B community for the help..

Hi Anuj,
I spoke to Oracle and they found that we have JRocket 64 bit installed.
However they recommend JDK 64 bit for the Development Environment.
And we are gonna do a Fresh SOA installation in a day.
SOA Verison is : 11.1.1.4
I hope this may help us.
Thanks Anuj for continous help.
Thanks
Vivek

O/p Type EDI

Similar Messages

Maybe you are looking for