Forward Error Handling - File interfaces?

Hello Experts,
Can we use Forward Error Handling (FEH) for implementing error handling in File Interfaces ?
Like for simple Application Server file interfaces, if something goes wrong during the process of writing/reading a file on App Server, can we use FEH for showing the log?
I know it is a concept used for PI...so we want to know if it can be used for file interfaces as well? Just want to keep similar approach for error handling and logging (for both PI and File Interfaces).
Thanks.

Edit 1 May 2015: Added inbound
Just a slight correction.
FEH is used in the ABAP backend systems and are only for asynchronous inbound proxy interfaces. It is not available for sync proxies, IDocs, BAPIs. Neither is it available for any error handling on the PI system itself.
PI/XI: Forward Error Handling (FEH) for asynchronous proxy calls with the use of Error and Conflict Handler (ECH)
Message was edited by: Eng Swee Yeoh

Similar Messages

How to activate Forward Error Handling in SRM

Hello Gurus,
I got an requirement to activate Forward Error Handling in SRM. I have searched on SDN but didn't find appropriate answer on it.
Even I found some link: PI/XI: Forward Error Handling (FEH) for asynchronous proxy calls with the use of Error and Conflict Handler (ECH)
It explains me some points like activating FEH from SRM in SPRO. I have activated the same, plz check the screen shot:
It also follows some development for the same.
Here my concern is, should I follow this document? Does it applicable to all to all the scenarios?
Step 8: it assign object id and type what does it mean...
Does any one can explain me in detail..... Please provide me any document to configure the FEH in SRM.
I am trying to implement FEH in my SRM system. So that when even XML fails due to error, I should be able to reprocess/restart it with some editing to the XML.
My receiver interface for XML is PurchaseRequestERPSourcingRequest_In
I think this is standard one and no need to make any custom code for it. SAP has all ready given solution for it with some Configuration.
I have made some configurations like:
The view FEHV_ACTIVE must have the status active.
In transaction /SAPPO/LOGSYS , the logical system must be defined for the software component SRM-EBP-ESA .
As stated in in the link :
http://esworkplace.sap.com/socoview%28bD1lbiZjPTAwMSZkPW1pbg==%29/render.asp?id=2BAABCB0D30111DC2B8D000F20FCB6A9&fragID=…
Also I have made some configuration according to the Note: 1973768 - No reprocess option is available in FEH for failed in XML in SRM
Resulted, the “Process” button get activated in the XML Post Processing screen.
But can I reprocess my XML with edited value from there..?
All the configuration part of PI is already done .
I wanted to know about the FEH Part. what are the steps i am missing or where i am going wrong ?
Please let me help.
Thanks
Regards
Karan

Dear Raz,
I have gone with above mentioned note, it explains about creating Custom Proxy and configuration with PI scenario. Even the link in my previous post, explains about the custom proxies and configuration..
I think I should must be descriptive about my issue.
I am trying to implement FEH in my SRM system. So that when even XML fails due to error, I should be able to reprocess/restart it with some editing to the XML.
My receiver interface for XML is PurchaseRequestERPSourcingRequest_In
I think this is standard one and no need to make any custom code for it. SAP has all ready given solution for it with some Configuration.
I have made some configurations like:
The view FEHV_ACTIVE must have the status active.
In transaction /SAPPO/LOGSYS , the logical system must be defined for the software component SRM-EBP-ESA .
As stated in in the link :
http://esworkplace.sap.com/socoview%28bD1lbiZjPTAwMSZkPW1pbg==%29/render.asp?id=2BAABCB0D30111DC2B8D000F20FCB6A9&fragID=…
Also I have made some configuration according to the Note: 1973768 - No reprocess option is available in FEH for failed in XML in SRM
Resulted, the “Process” button get activated in the XML Post Processing screen.
But can I reprocess my XML with edited value from there..?
Can any one tell me, what are the steps I am missing here. As this is my first time to implement FEH, I am confused.
Please let me help.
Regards,
Chandan

How to Setup Forward Error Handling in PI Scenarios. Can you help me with the same with screen shots if possible?

Dear all
How to Setup Forward Error Handling in PI Scenarios. Can you help me with the same with screen shots if possible?
Thanks
Regards
karan

Hello
These are the following errors
1. Trace level="1" type="T">no interface action for sender or receiver found</Trace>
2. <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!
3.
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</
Trace level="3" type="T">No persisting of message after plsrv call, because of config</Trace>Trace level="3" type="T">Error of the prevous version:</TraceTrace level="3" type="T">Error ID APPLICATION_ERROR</Trace>
tThere are repeating errors also.
TThanks
Regards
kkaran

Forward Error Handling

Hi,
Does anyone know where I can find more information on SAP Forward Error Handling? The only info I have found so far is here [<clicky>|http://esoadocu.sap.com/socoview%28bD1lbiZjPTAwMSZkPW1pbg==%29/render.asp?sap-unique=125551&sap-params=cGFja2FnZWlkPURDQkQzMTVCNkQ3MjU1RjE5QUYyMDAxNDM4QzNCQzA4JmlkPTYyMTEwMEJBRkQ4NDQzQjBCNjkyN0FERjNGNkQ3MkZBJnBhY2thZ2VpZD1ERTA0Mjg0Njg3QkVCREYxOTUxNTAwMUE2NEQzRjQ2Mg%3d%3d]
I have found the correct place in the IMG but there is not much additional documentation there either.
Thanks
Manish

Goto SAP service marketplace and search for
SAP Reference Implementation Guide -> Cross-Application Components -> Processes and Tools for Enterprise Applications -> Enterprise Services -> Error and Conflict Handling .
Your link is not correct, I found one: http://esoadocu.sap.com/socoview(bD1lbiZjPTAwMSZkPW1pbg==)/render.asp?sap-unique=122005&sap-params=cGFja2FnZWlkPURDQkQzMTVCNkQ3MjU1RjE5QUYyMDAxNDM4QzNCQzA4JmlkPTYyMTEwMEJBRkQ4NDQzQjBCNjkyN0FERjNGNkQ3MkZBJnBhY2thZ2VpZD1ERTA0Mjg0Njg3QkVCREYxOTUxNTAwMUE2NEQzRjQ2Mg%3d%3d
Reards,
Gourav

Forward Error Handling (FEH) framework?

Hi all
Forward Error Handling (FEH) framework - can any one expalin this?
Muthu

Hi,
Forward Error Handling (FEH) is a framework in SOA for performing error processing in
asynchronous communication on the receiver side. Please check the troubleshooting document.
https://service.sap.com/sap/support/notes/1270081
Regards,
Masa

Error handling : File( sender and receiver)

Hi Experts,
This is regarding some information i require in the Error Handling mechanisms we can use while picking up the file through File Sender Adapter and while placing the same on the receiver adapter :
Scenarios like :
a) Validations we can put , on the file , should that be done in SAP XI or after placing in SAP ERP.
b) If the file is of a different format and isnt picked up how can that be handled ? ]
c) if the File contains wrong data , should the alert be generated in SAP or SAP XI ?
d) If the file does not arrive in the folder itself what is the error handling meachanism ?
e) diff
thanks
Dev

a) Validations we can put , on the file , should that be done in SAP XI or after placing in SAP ERP
Do validations on File mean perform a check on the file for its contents, format, structure? If yes, then these are performed in XI/ PI
b) If the file is of a different format and isnt picked up how can that be handled ?
The file channel will throw an error if it is not able to find the file (specified in sender channel) during its poll interval.
c) if the File contains wrong data , should the alert be generated in SAP or SAP XI ?
If SAP is the target system, then better the check and alert be done in SAP XI/ PI, as far as possible we should avoid sending wrong data to the target.
d) If the file does not arrive in the folder itself what is the error handling meachanism ?
Which folder are you talking about? If it is source folder then the error will be thrown as mentioned in point b.
If it is target folder, then the error (if any) will be captured either in IE or AE of SAP XI/ PI and can be intimated using alerts.
Regards,
Abhishek.

Error Handler (File not Found) missing .cfm

Hi,
I have multiple applications on my server. For each
application I would like an error handler that will catch missing
.cfm files. If a user types in www.abc.com/test.cfm, and test.cfm
does not exist, each site will use its own "errorHandler.cfm" file
for example.
I already can handle .htm and .html files in IIS, basically
when the 404 error happens, it calls my html error handler. I also
tried checking the option in IIS where you see a list of file
extensions, you go to .cfm (this is all in IIS), and there is a
checkbox that says "check if file exists", so I have checked and
unchecked this, but not luck.
In CFAdmin there is an area where you can specify a missing
template handler. This seems to apply to the whole server. Each of
our application are very different, I would like to have an
individual error handler in each application.
I am getting a CF error, (File not Found) not an IIS error
when you type a file in the url string as mentioned above. I tried
using <cferror> in my Application.cfm file, but to no avail.
I tried using try/catch to no avail. I have heard of others having
this frustration as well.
Help is greatly appreciated
-Westside

I've not tried this, but consider having the server-wide
error handler look at the CGI.HTTP_REFERER variable to see what
application threw the error. Then do a <CFLOCATION> to the
application-specific error handler.

Forward Error Handler - Add component to table '

Hello,
I've been configuring SOA. Note '1270081 - Trouble shooting SOA Services' explains monitoring of SOA including FEH. It says that you need to maintain an entry for every system in table: '/n/SAPPO/LOGSYS'. In our case SRM <> R/3 we would need to configure 2 entries, one entry per system.
The above table does not excist in any of both systems. However i did find the following tableview: /SAPPO/VLGSYS. Should we use and configure it here? What does this configuration do / why is it required?
Kind regards,
Tim

Tim,
Rather than table, did you try it as Transaction ..
/n/SAPPO/LOGSYS
It's works.. also try transaction /n/SAPPO/PPO2.
Regards,
Sandeep Parab

FEH for File Interfaces?

Hello Experts,
Can we use Forward Error Handling (FEH) for implementing error handling in File Interfaces ?
Like for simple Application Server file interfaces, if something goes wrong during the process of writing/reading a file on App Server, can we use FEH for showing the log?
I know it is a concept used for PI...so we want to know if it can be used for file interfaces as well? Just want to keep similar approach for error handling and logging (for both PI and File Interfaces).
Thanks.

Edit 1 May 2015: Added inbound
Just a slight correction.
FEH is used in the ABAP backend systems and are only for asynchronous inbound proxy interfaces. It is not available for sync proxies, IDocs, BAPIs. Neither is it available for any error handling on the PI system itself.
PI/XI: Forward Error Handling (FEH) for asynchronous proxy calls with the use of Error and Conflict Handler (ECH)
Message was edited by: Eng Swee Yeoh

General Error Handling - use of FEH (PPO/ECH)

We are investigating the usage of Forward Error Handling, known with SAP as PPO (Post Processing) and ECH (Error Capture Handler) to be able to re-process errors (automatically or manually) from incoming messages.
I am interested in talking with anyone who has implemented this. General questions are:
- how have you found it to work in real life?
- configuration/set-up straight-forward?
- what scenarios have used it in?
- incorporated into your custom services?
But am interested in any comments.
I am posting this within the PI forum as it ties into the fact we async scenarios inbound to SAP, typically from our PI system, and when those scenarios encounter an error we are looking for a way to have a business/end user - friendly interface for reprocessing the error. Implementing a proxy scenario, and thus having the errors show within sxmb_moni/sxi_monitor, is probably not going to work for us - too technical. I am also aware of an add-on, AIF I believe, but our company is not interested in installing that.
There are 4 blogs out there that I am aware of - 2 from Tobias and 2 from Michal. Very informative. I am finding some config not as ours though. Am really interested in anyone has really implemented and used this in a prod environment.
Regards,
Keith

I think I am exactly at the same position as you in figuring out the usage of FEH in an environment. I just completed a small document (for internal purpose) that I prepared gathering all the information from those blogs, SCN and TechEd. Here are my 2 cents:
>>- how have you found it to work in real life?
We haven't implemented it yet. But we believe it will be quite useful in handling business specific errors. We are trying to find out if it can be merged with the existing BPEM infrastructure to generate BPEM cases.
>>- configuration/set-up straight-forward?
Yes, the blogs should be quite useful to provide this information.
>>- what scenarios have used it in?
Most importantly it will be used for standard service implementation where we consume enterprise services from ES workplace. These services have FEH capability built in (they have FEH method implemented within). The scenarios are of course inbound abap proxy.
>>- incorporated into your custom services?
We are still in design phase. But if you ask me about it, i would say yes you can and I think you should use it for custom ones as well.
Kind regards,
Prateek Raj Srivastava

Error handling in File - XI - SOAP scenario without BPM

Hello!
We have a File -> XI -> SOAP scenario without BPM. The problem is that if the Web Service sends back an error XI tries to reprocess the same message again and again instead of taking the next one.
We do not want set the retry interval to NULL because most error cases are temporary connection problems and then also those messages would not automatically be reprocessed any more.
We also have to use BE instead of EO, otherwise the Web Service will not return a response. But we need the response to be sure that the processing was successful. The message volume in this scenario is quite high and we do not want to use BPM only for the error handling.
I know that from SP19 some additional adapter modules are available for async - sync scenarios without BPM. I tried to configure it like described in File - RFC - File without a BPM - Possible from SP 19. but it did not solve the problem. Does anybody have any other ideas? Thanks.
Regards, Tanja

Hi Tanja,
>>>The volume is 3000 messages/day on business days and 700 messages/day during weekends but the traffic will increase in the future
I think, you should check that out. It is assumedly only 2 days work to build a scenario:
IDoc -> BP
BP <-> SOAP/HTTP
BP -> IDoc (Acknowledgement)
In the process you need a condition branch, where you decide success or not. You need 2 Interface Mappings for filling the ALEAUD.
Just send 1000 IDocs to the Test-XI and look to performance monitoring at Runtime Workbench, to find out, how many message will be processed in one hour. Assumedly 3000 and more per day should be possible. The advantage would be to reduce number of systems (no file system) and messages (better monitoring) and using the standard (better maintenance).
>>>So you are suggesting I should use HTTP adapter and then add the SOAP header manually in a mapping?
Yes, build the SOAP envelop during the mapping. Most easy is to use XSL or, if your mapping is ready, an additionsal XSL. You can put the error into the Acknowledgement to see it in ERP transaction WE02.
Filling of ALEAUD fields:
E1ADHDR/MESTYP: original message type
E1ADHDR/E1STATE/DOCNUM: original IDoc number
E1ADHDR/E1STATE/STATUS: 68 in case of error, 53 in case of success
E1ADHDR/E1STATE/STATXT: Short description for R/3 user what has happend
I ve done such a scenario several times. That works without any problems.
Regards,
Udo

File receive adapter command line error handling

Hi,
This is our requirement - After the file receive adapter, we need to run a script. Based on the return code of the script, we need to handle the error handling of the interface (i.e. send an email about the error).
I have looked at the operating system command line in the file adapter. How does XI handle return codes for the command line? If the command line has a error return code, how to send an email from XI?
If anyone has ideas on this topic, please respond!!
thanks,
lasya

Hi,
I don't think so, it is possible directly. You can not get the Response back to XI pipeline from the shell script.
But you can think, if you are able to call this from Mapping.
And one more option is using Transport Acknowledgement ( with BPM) if the file is not able to write into the target directory you can raise an alert-
Blog on this-
/people/michal.krawczyk2/blog/2006/06/22/xi-playing-with-the-file-adapters-acknowledgments
Regards,
moorthy

Using code interface node with dll crashes LV 2011 but not LV 8.6... using max error handling does nothing

Hi all,
I'm having a peculiar problem.
I inherited a project saved in LabVIEW 8.6. The project must use of particular dll that was built a few years ago. The original developer and source code for this .dll are long gone. The very core logic exists, in the form of embedded C code, and that's it. The .dll is called through a Code Interface Node in LV 8.6 and this setup manages to "work". Howver, running the VI that calls this .dll in LV 2011 causes an "insta crash", as in, no "program has stopped responding". Error message pops up, then all LV windows close.
It's very similar to that described in here:
http://digital.ni.com/public.nsf/allkb/D84C9775ABD921CF8625772A005CA50C
but this KB says to try putting the amount of error handling to maximum. I tried that, but it didn't help.
Using the "Debug" option allows me to run the just-in-time debugger with CVI 2010, which then proceeds to say this:
Finally, I manage to get this out of it:
FATAL RUN-TIME ERROR: Unknown source position, thread id 0x000012D4: A non-debuggable thread caused a 'General Protection' fault at address 0x00000000.
I don't think that really helps at all, but it's there.
Here is the function prototype of the .dll:
void _inputPM@224(uint8_t arg1, uint16_t arg2, uint8_t arg3, float arg4, float arg5, float arg6, float arg7, float arg8, float arg9, float arg10, float arg11, float arg12, float arg13, float arg14, float arg15, float arg16, float arg17, uint16_t arg18, uint16_t arg19, uint16_t arg20, uint16_t arg21, uint16_t arg22, uint16_t arg23, uint16_t arg24, uint16_t arg25, uint16_t arg26, float arg27, float arg28, float arg29, float arg30, float arg31, float arg32, float arg33, float arg34, float arg35, float arg36, float arg37, float arg38, float arg39, float arg40, float arg41, float arg42, float arg43, float arg44, float arg45, float arg46, float arg47, uint16_t arg48, uint16_t arg49, uint16_t arg50, uint16_t arg51, uint16_t arg52, float arg53, float arg54, float arg55, float arg56);
(never seen a function take 50 input params like that (wouldn't you use a struct? array? something? But I digress, and I don't know anything about .dlls...))
I do have a ".lib" and a ".cdb" file with the same name as the .dll, but those also looks like some kind of compiled file.
I'm sure the answer I'm going to get is that there is no way of telling what's really going on without .dll source code. I'm hoping against hope that there may be another way or hack.
Any ideas? Thank you for you help.
Regards,
Mark G
Solved!
Go to Solution.

MarkCG wrote:
Changing the call library node to stdcall (WINAPI) did the trick! No more crash. Thank you very much!
I haven't run LV2011 on windows XP, only on windows 7, so I don't know if that makes a dfference. But The call type makes no difference when using LV 8.6 on the same machine, however.
Now I've got to make the .DLL run corretly on a compact fieldpoint.... and avoid crashing IT.
Thank you for the help all!
Well, the DLL did work fine in LabVIEW 8.6 because earlier versions of LabVIEW automatically proceeded to change the calling convention to stdcall, if they noticed a function name decoration of @# (# = number of bytes passed on the stack) appended to the name. This is the default naming decoration for stdcall functions used by VisualC. However this decoration can be overwritten with linker switches, other compilers don't use them always in the same way, and most likely there are in the mean time compilers out there that can produce such decorations also for non stdcall calling convention. So this automagic trickery was removed from newer LabVIEW versions.
I do think it could be considered a bug in the code that upgrades LabVIEW VIs, that it uses the calling convention that is configuerd in the dialog, instead of the calling convention earlier LabVIEW versions used automagically, but it is an esoteric corner case.
What Compact Fieldpoint controller do you have? If it's anything newer than 20xx or 21xx forget it. The 22xx controllers use a PPC CPU and VxWorks operating system and can never get a Windows DLL to operate properly. If it is a 20xx controller it's still highly likely that DLL can not even get loaded into LabVIEW as it likely relies on other runtime libraries and possibly Win32 APIs not present in the Pharlap ETS runtime kernel used on those controllers.
There is a tool to check a DLL for incompatible imports that are not present on specific ETS RT systems. And this list summarizes the RT system used on the various NI controllers.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Getting error when testing Proxy to File interface

Hi Guru's,
While I am testing a Proxy to File Interface, using SPROXY transaction i am sending a message from R/3 to PI.
the message showing successful in R/3 Moni,but in PI moni I am getting the following Error..
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In this inreface, I am suppose to send the mesasage to only one Target system(ftp server) . i have checked in ID part also,
every thing is clear in ID. Can any body please tell where the mistake might exists...
Thanks in advance..
Regards
Raj

Hi,
No receiver could be found means Check your Receiver Determination. Activate and update cache. Asysnchronous messages can be manually restarted.
have you seen this threads,
NO_RECEIVER_CASE_ASYNC
No receiver could be determined
regards,
ganesh.

Error Handling in File Adapter

I have been working on a requirement where the file adapter picks up the file and gives to the BPEL for processing the data.
So, in order to do Error Handling for file adapter, i have been reading the Oracle documentation for technology adapters. In that, some of the
points which i felt valuable for my error handling when using file adapter are the uniqueMessageSeparator property, fault-policies for rejected messages,
and one of the action for rejected messages could be writing the payload to a file or invoking any other webservice.
In my composite, i have configured the file adapter as a service for reading files, and i defined the xsd using the native format builder....If i put some data like 'aaaa' in the attribute of type integer , the .csv file is being picked up and its being passed to the BPEL without any error ? I believe there should be a translation error...right...
But i am not getting the error, please tell me if anything is wrong in my xsd....
Here is my xsd...
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd"
xmlns:tns="http://TargetNamespace.com/InboundService"
targetNamespace="http://TargetNamespace.com/InboundService"
elementFormDefault="qualified"
attributeFormDefault="unqualified"
nxsd:version="NXSD"
nxsd:stream="chars"
nxsd:encoding="US-ASCII"
nxsd:hasHeader="true"
nxsd:headerLines="1"
nxsd:headerLinesTerminatedBy="${eol}"
>
<xsd:element name="names">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="name" minOccurs="1" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="FirstName" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="LastName" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," />
<xsd:element name="Number" type="xsd:integer" nxsd:style="terminated" nxsd:terminatedBy="${eol}" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
And for DB Adapter, there is a property called SchemaValidation, i think that is not there for File adapter, by default it will take care of validation i guess....In another composite, my file adapter is picking up the .xml file and if i put any wrong data over there, that is working fine, i am getting the translation error, but only here in the case of csv file, i am not getting the error. Experts, please help me in this regard...I am using SOA 11G
Thanks,
Naresh

Hi Yatan,
Thanks for the reply. I did the same way, where my composite is picking up an XML file and translation error is coming. Even the fault policies are working fine, like writing to a file and even invoking other web service. Its really good that you have achieved the same thing in csv files. But the same thing i am unable to achieve when my file adapter is picking up the csv file. I really cant understand where i am doing wrong.
here is my XSD which i defined through my native builder format...
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd"
xmlns:tns="http://TargetNamespace.com/FileRecv"
targetNamespace="http://TargetNamespace.com/FileRecv"
elementFormDefault="qualified"
attributeFormDefault="unqualified"
nxsd:version="NXSD"
nxsd:stream="chars"
nxsd:encoding="US-ASCII"
nxsd:hasHeader="true"
nxsd:headerLines="1"
nxsd:headerLinesTerminatedBy="${eol}"
>
<xsd:element name="Roots">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="FirstName" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
<xsd:element name="LastName" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="," nxsd:quotedBy=""" />
<xsd:element name="Number" type="xsd:integer" nxsd:style="terminated" nxsd:terminatedBy="${eol}" nxsd:quotedBy=""" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
the jca file ..
<adapter-config name="FileRecv" adapter="File Adapter" wsdlLocation="FileRecv.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
<connection-factory location="eis/FileAdapter" UIincludeWildcard="n*.csv"/>
<endpoint-activation portType="Read_ptt" operation="Read">
<activation-spec className="oracle.tip.adapter.file.inbound.FileActivationSpec">
<property name="DeleteFile" value="true"/>
<property name="MinimumAge" value="0"/>
<property name="PhysicalDirectory" value="C:\files"/>
<property name="Recursive" value="false"/>
<property name="PollingFrequency" value="5"/>
<property name="IncludeFiles" value="n.*\.csv"/>
<property name="UseHeaders" value="false"/>
</activation-spec>
</endpoint-activation>
</adapter-config>
I told that the file will contain only 1 record while defining xsd and i kept a record whose values are John , Peter and akjdkjdskj.
Now if the data is like above, the file is still getting picked up without any translation error and the BPEL is getting completed successfully...
Is it possible for you to send your sample project and the csv file from which you have defined the xsd to me if you dont mind ?
Thanks,
Naresh

Forward Error Handling - File interfaces?

Similar Messages

Maybe you are looking for