Group of messages in file adapter

Hi friends
File adapter picks a message at a time , but can a file adapter picks group of messages at a time or is there any setings in sender or receiver file adapter. Can any one provide me the solution?

> File adapter picks a message at a time , but can a file adapter picks group of messages at a time or is there any setings in sender or receiver file adapter. Can any one provide me the solution?
Hi,
Just give the file name as *.xml and it will pic all the xml files from the source dircetory.
If you could provide the file name or it's format then I can let u know the exact formatting.
Regards,
Sarvesh

Similar Messages

Multiple message through FIle Adapter using XI 2.0

I have scenario to create multiple message using File adapter .My file structure will be like
EMPID     NAME     SKILLS
001     A      ABAP
001     A      XI
002     B      JAVA
Now I want to post first 2 records in one message and last record in other message.
Can we do it in XI 2.0.Any help appreciated

Hi Suraj.
Thank you very mutch for your reply.
Excuse me...my mapping is done for message type and idoc.
My problem is that when the interface start, on the sxmb_moni I see an error like this:
Creating Java mapping com.sap.xi.tf._MM_XmlOrderToIdocMapping_ --- Using MappingResolver with context URL //srvsapdev/sapmnt/CX1/SYS/global/xi/mapping/gestione_magazzini/7fa9c9e15a7811dab710f3e3ac10826e/ --- Load of com/sap/xi/tf/_MM_XmlOrderToIdocMapping_.class from //srvsapdev/sapmnt/CX1/SYS/global/xi/mapping/gestione_magazzini/7fa9c9e15a7811dab710f3e3ac10826e failed. --- Class not found: com.sap.xi.tf._MM_XmlOrderToIdocMapping_ --- java.lang.ClassNotFoundException at RUMappingJava.load(): Could not load class: com.sap.xi.tf._MM_XmlOrderToIdocMapping_ Class not found: com.sap.xi.tf._MM_XmlOrderToIdocMapping_ --- com.sap.aii.ibrun.server.map.MappingRuntimeException: at com.sap.aii.ibrun.server.map.MappingRuntimeException.code_STYLESHEET_OR_CLASS_NOT_FOUND
..where 'gestione_magazzini' is my namespace and 'MM_XmlOrderToIdocMapping' is my message mapping.
Can you help me to undestand the problem?
Thanks,
Gianluca

Mapping Error - Dump source message to file adapter comm channel

Hi
Does anyone know of a way to dump the source message to a file adapter comm channel if - and only if - the message fails during mapping. For example, we receive a message from a trading partner that lacks an element that is mandatory during the mapping. When the mapping fails, the source message is sent - as is - to a file adapter comm channel.
I don't need anything more than the source message i.e. no need for any errors etc... to be included.
The kicker.. I would like to do this without using BPM if at all possible.
Any ideas greatly appreciated. Thx, Duncan

Hey Ram,
Go to Integration Directory and open the Receiver Determination for your scenario.
Check the configured receiver services. They are in a table-like area in the middle of the screen.
In this table of configured receiver services for that particular Sender Service/Interface, you should have the system that normally receives that message (your ERP or any other application system) and the service that contains the receiver file comm channel that will receive the message in case of error.
Check help.sap.com for help on condition editor on receiver determinations.
Now, the issue. You can only check whether a field exists, you can't check whether it doesn't exist (There's only a "EXIST" operator, and no negative operator). Thus, you can only do the following: always send messages to File, but you can avoid messages that dont have field from being sent to App System. Yeah, that sucks...
But don't fear, young padawan! There is a possible workaround. =D
In your message mapping, do the following for that particular field:
If field exists (check with Exist and IF standard functions) just bypass the field. Else, map the field with an impossible value (like string "$CREATED$"). Then, in your receiver determination, you will do the following conditions:
for App System: If field =/= $CREATED$
for File Receiver: If field = $CREATED$
Now, if the field doesnt exist, it will have value $CREATED$, thus the message will be sent to File and not to App System. If the field exists, the message will be sent to App and not to File.
Try that out.
Regards,
Henrique.

Recordsets per Message in File adapter

Hello All,
I am using Recordsets per Message option in Sender file adapter. And my source file contains more than the specified in Recordsets per Message.
Can you please tell me why it is not working
Regards,
Moorthy

Hi,
Please try to make small addition in your Sender FCC.
Recordset Structure: Row,5000
Recordset per Message: 1
It will divide your file into 5000 records and generate separate messages.
Hope this helps to you.
Regards,
P.Rajesh

How to handle rejected messages in file adapter

Hi....! every one.........
in file adapter read operation it will pick the files even the file contains unstructure message but that file wont be processed.
where the rejected message goes.
i have requirement like that rejected message i have to store in another file
please provide me answer..........

Hi,
You can add the parameter 'PhysicalErrorArchiveDirectory' in the JCA file (of the File Adapter).
Put there the required directory where you want the rejected file to be sent.
You can add this property in 2 ways:
1. In your JDeveloper open the JCA file and add: <property name="PhysicalErrorArchiveDirectory" value="/../.."/>
2. In EM, right click the composite->Service/Reference Properties->Choose your file->On the Properties tab press Add-> Choose 'PhysicalErrorArchiveDirectory' and put the directory-> press Apply.
Arik

Regarding hierarchy of message using file adapter

Hi all.
I have following source-structure
<name of MT>
<Header>
<h1></h1>
<Subheader>
<sh1></sh1>
<LineItem>
<l1></l1>
<LineItem>
</Subheader>
</Header>
</name of MT>
Input is coming like a flat file.
can file adapter can read the above structure? may be it doesn't because, <l1> item is in 4th level of message. so adapter can't read more than 3rd levels.. is it right? Please give u r inputs.
Thanks

Hi,
To my Knowledge
>>so adapter can't read more than 3rd levels.. is it right? Please give u r inputs
It is not like that.
Regards
Agasthuri Doss

Dicarding messages in file adapter

Hi,
I wish to process a file that has invoice data. The structure of the file is thus:
$H$<<Supplier Name>>,<<Supplier Site>>,<<Invoice Number>>
$D$<<Line Number>>     ,<<Business Unit>>,<<Location>>,<<Store Name>>
$D$<<Line Number>>     ,<<Business Unit>>,<<Location>>,<<Store Name>>
$H$<<Supplier Name>>,<<Supplier Site>>,<<Invoice Number>>
$D$<<Line Number>>     ,<<Business Unit>>,<<Location>>,<<Store Name>>
$D$<<Line Number>>     ,<<Business Unit>>,<<Location>>,<<Store Name>>
The intent is to configure the file adapter in such a fashion that it rejects the entire invoice if there are any errors in any of the lines that belong to that invoice. The invoices that follow the erred inovice should be processed normally. How do I configure the adapter to achieve this. Any help is greatly appreciated.

Have a look at the startWith example in this link Jason provides.
Also you can see this post as it provides examples
Re: ESB- Flat file records to different DB tables based on first field
cheers
James

How To split large message using File Adapter

Hello everyone,
Here is my scenario FTP > XI > BI.
I got 2 questions:
(1) I am getting large message around 70 MB file.
    How we can split the message into multiple files 10 MB each before processing the file into XI?
(2) Is there is any way we can find out size of file which is on FTP without contacting FTP admin?
    through XI before processing the file?
Thanks
Vick

hi vick,
check the blog
Zip or Unzip your Payload with the new PayloadZipBean module of the XI Adapter Framework
Working with the PayloadZipBean module of the XI Adapter Framework
SAP XI acting as a (huge) file mover
The specified item was not found.
Managing bulky flat messages with SAP XI (tunneling once again) - UPDATED
The specified item was not found.
regards
kummari

How to post multiple message using file adapter in XI2.0

We have to post multiple IDOCS.We have scenario as below.
We will have file structure like as shown below.
VKORG,VTWEG,SPART,BSART,PARVW,PARTNER,BSTDK,MATNR,MENGE,VSART,BSTZD,POLINE,BSARK
BE10;10;10;OR;SP;1000033;;M184-ISS01;2;G;131;0002;
BE10;10;10;OR;SP;1000033;;M184-ISS01;2;G;131;0002;
BE30;10;10;OR;SP;1000033;;M184-ISS01;2;G;131;0002;
For this we want that 2
messages should be created.In first message there will be first 2 records
with VKORG BE10 and in second message there will be last record with VKORG BE30.
We can do it through FILE2XMBWITHSTRUCTURECONVERSION and using some options.
I am sending the configuration that I have done for my adapter.
classname=com.sap.aii.messaging.adapter.ModuleFile2XMB
mode=FILE2XMBWITHSTRUCTURECONVERSION
#mode=FILE2XMB
XMB.TargetURL=http://20.60.53.36:8000/sap/xi/engine?type=entry
XMB.ReceiverBusinessSystem=sapdev210
#XMB.ContentKind=B
XMB.ContentKind=T
#XMB.ContentType=application/xml
XMB.ContentType=text/xml
#XMB.ContentType=text/plain
XMB.QualityOfService=EO
##xml conversion properties if mode FILE2XMBWITHROWCONVERSION specified (example, see docu)
xml.recordsetStructure=IDOC,*
xml.recordsetName=SALESDATA
xml.recordsetsPerMessage=1
xml.documentName=SALESDATA
#xml.fieldFixedLengths=
xml.IDOC.processFieldNames=fromConfiguration
xml.IDOC.fieldNames=VKORG,VTWEG,SPART,BSART,PARVW,PARTNER,BSTDK,MATNR,MENGE,VSART,BSTZD,POLINE,BSARK
xml.keyFieldName=VKORG
xml.keyFieldType=CaseSensitiveString
xml.IDOC.keyFieldValue=BE10.
xml.IDOC.fieldSeparator= ;
What I have tried is hardcoding 2 in xml.recordsetStructure=IDOC,2.It works fine
Since I already knew this.
Butin real scenario we wont be knowing this that is why I have given * in configuration , and
given
xml.keyFieldName=VKORG
xml.keyFieldType=CaseSensitiveString
xml.IDOC.keyFieldValue=BE10.
With this it should identify on key field and its value and put first 2 records in one message
and last record in second message.
It is not giving any error when we start adapter but no XML message is created.Can u plz help me
for the above problem.
My datatype in repository is like
SALESDATA
    IDOC
         VKORG
         VTWEG
and allother remaining fields.
Is this scenario possible in XI 2.0.If yes then will it be done through above approach or something else.
Thanx.
Rekha.

Hi,
I think you can not handle this problem with keyFieldName/keyFieldValue.
In my opinion with keyFieldName/keyFieldValue you can create different substructures of the same XML, but you can not seperate messages with the same substructure.
But I don't know how to handle your problem ;-(
Another point is that I see a dot after xml.IDOC.keyFieldValue=BE10.
My be this is a problem too.
Christoph

File Adapter Source Directory

I have set up a File Adapter comms channel that should be picking up a file from the XI SAP system directory path F:\usr\sap\temp.
I place a file in that directory and can see it via SAP transx AL11.
However my comms channel is not picking up the file so my process does not start. I had previously been using a FTP File Adapter and that was working fine. So I know my other configuration is correct. I now needed to testing something use just the plain File Adapter.
The RunTime Cache has been refreshed and I can see my CC via SXI_CACHE.
Here is what I have entered into the File Sender Adapter
Transport Protocol : File
Message Protocol : File
Adapter Engine : Integration Server
Source directory : F:\usr\sap\temp
File Name : MYFILE.XML
Processing Options :
QAS : EO
Poll Interval 60s
Processing Mode : Delete
Processing Seq : By Name
File Type : Binary
Adapter Status : ACTIVE

Hi
check the following things
first select ur message protocol as "NFS". save the changes and activate the channel.
if still not work go to the communication channel monitoring using the path
runtime work bench->compnent monitoring->dispaly->adapter ebngine->communication channel monitoring--->enter ur channel name and click on use filer button.
and check whether the channel is started or stopped.
if stopped start the channel and the try.
if u still face the problem please reply me back.
Thanks
Rinku

Error in Receiver File adapter - FCC

Got error message as "File Adapter Receiver Channel CC_OB_REQ: Not initialized - cannot proceed: null"
My requirement is to send IDOC to file which consists of 4 fields, My target message interface is
MT_REQ
FILE_STRUC
    FILE_OP
       AAA (Field1)
        BBB(Field2)
       CCC(Field3)
       DDD(Field4)
Output file should contain the above 4 fields with fixed lengths 20,1,1,2
So I declared FCC in File Adapter as
I tried many options
RecordSet Structure: MT_REQ,FILE_STRUC,FILE_OP
FILE_STRUC.fieldSeparator - 'nl'
FILE_OP.fixedFieldLengths - 20,1,1,2
FILE_OP.fieldSeparator - 'nl'
FILE_OP.endSeparator - 'nl'.
Please let me know where is the problem?
Thanks in advance,
Krishna

Hi Ramakrishana,
In FCC fixed length file format when your XML payload is goes to Adaptor engine, it should contain all fields in XML. Otherwise its throw error in FCC channel. Please check receiver payload at SXMB_MONI or message monitoring of Run time work bench. In that payload you will find that some of the fields is not generated in target payload.
Field in receiver payload is not generated means from sender payload corresponding field is not coming. As per my past experience this generally happens in IDOC sender.
solution:- In message mapping in every field from IDOC to file use mapWithDefault node function with null value. Due to this though if any field do not generates in IDOC, corresponding field will generate in File Payload and it will not throw error in FCC.
Regards,
Prashant

Inbound File Adapter problem

Can someone tell me why my message is not processed by XI. I use a File Adapter. The File Adapter is "active" with the following configuration.
Adapter type = File
transport protocal = Filesystem
message protocol = File
adapter engine = integration server
Source directory = "e:/XIprocessFiles"
File name = *.xml
File type = text

Edward,
What do you exactly meant with not processed? Is the file adapter not processing/sending your xml file to the XI system? Or
is your interface defined in XI not doing anything with the input message?
Assuming your situation is the first one; Then you should start by checking the source file name, source directory name, contentType (you have text, this should be text/xml), ContentKind (this should be T) and PollingInterval...
In the second situation you should then look at adapter config settings like: namespace, sender interface name, sender business name etc...
Cheers,
Rob

Receive File Adapter - Error in CallSAPAdapter Name not known

Using xml to File Adapter. Just want to store the xml file somewhere ie on XI Server in folder E:\usr\sap\interface\XMLfiles
Getting error in Adapter Engine - Exception caught by adapter framework: Object not found in lookup of CallSAPAdapter.
Delivery of the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Object not found in lookup of CallSAPAdapter.: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of CallSAPAdapter..
Receiver Adapter configured to receive file write a .tmp version no conversion so set type to Binary.
I can see the Communication Channel in the monitor green.
Any ideas to find the problem
thanks,

I tried changing the communication channel as suggested with no further success. I have viewed the LogViewer on the server in cluster->server->logs defaultTrace.trc and com.sap.xi -> xi.log with no more information available.
So is it that I cannot do a simple XML send to file receiver and leave its content unchanged?
My test message payload was of the order
<?xml version="1.0"?><LIST><S_STX><C_STDS><D_STDS1>... with all the data in.
Adapter type = file
Receiver
Transport Protocol = File System (NFS)
Message Protocol = File
Adapter Engine = Integration Server
Target Directory = E:/usr/sap/Interfaces/XMLFiles (and tried it with /usr/sap/interface/XMLFiles)
Create filedirectory = ticked
Filename filename.xml
File Construction Mode = add timestamp
Write Mode = use temporary file
Temporary filename scheme = filename.tmp
Filetype = Binary
Module Tab
1 localejbs/CallSAPAdapter Local Enterprise Bean 0
and thats it.
On testing from the Integration Engine it reaches the Adapter Engine and reports the error as stated in my first post.
The message data is of the construct
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SOAP:Header>
- <sap:Main xmlns:sap="http://sap.com/xi/XI/Message/30" versionMajor="3" versionMinor="0" SOAP:mustUnderstand="1" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<sap:MessageClass>ApplicationMessage</sap:MessageClass>
<sap:ProcessingMode>asynchronous</sap:ProcessingMode>
<sap:MessageId>09c99665-f3cf-d247-993b-8cb46c37d820</sap:MessageId>
<sap:TimeSent>2007-09-19T16:42:31Z</sap:TimeSent>
- <sap:Sender>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty">AS2</sap:Party>
<sap:Service>XMLFILE</sap:Service>
</sap:Sender>
- <sap:Receiver>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty">MyCompany</sap:Party>
<sap:Service>XMLFILE</sap:Service>
</sap:Receiver>
<sap:Interface namespace="http://warburtons.com/genhdr">MI_XMLFILE_V3</sap:Interface>
</sap:Main>
- <sap:ReliableMessaging xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<sap:QualityOfService>ExactlyOnce</sap:QualityOfService>
</sap:ReliableMessaging>
- <sap:Diagnostic xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<sap:TraceLevel>Information</sap:TraceLevel>
<sap:Logging>Off</sap:Logging>
</sap:Diagnostic>
- <sap:HopList xmlns:sap="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
- <sap:Hop timeStamp="2007-09-19T16:42:31Z" wasRead="false">
<sap:Engine type="IS">is.00.srvsapxidev</sap:Engine>
<sap:Adapter namespace="http://sap.com/xi/XI/System">XI</sap:Adapter>
<sap:MessageId>09c99665-f3cf-d247-993b-8cb46c37d820</sap:MessageId>
- <sap:Branch>
<sap:MessageId>707ecbbd-a474-514d-b731-f4003c38c4df</sap:MessageId>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty">ASD</sap:Party>
<sap:Service>IP_I_XMLFILE_Collect</sap:Service>
</sap:Branch>
- <sap:Branch>
<sap:MessageId>09c99665-f3cf-d247-993b-8cb46c37d820</sap:MessageId>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty">MyCompany</sap:Party>
<sap:Service>XMLFILE</sap:Service>
</sap:Branch>
<sap:Info>3.0</sap:Info>
</sap:Hop>
- <sap:Hop timeStamp="2007-09-19T16:44:56Z" wasRead="false">
<sap:Engine type="AE">af.xid.srvsapxidev</sap:Engine>
<sap:Adapter namespace="http://sap.com/xi/XI/System">XIRA</sap:Adapter>
<sap:MessageId>09c99665-f3cf-d247-993b-8cb46c37d820</sap:MessageId>
</sap:Hop>
</sap:HopList>
</SOAP:Header>
- <SOAP:Body>
- <sap:Manifest xmlns:sap="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <sap:Payload xlink:type="simple" xlink:href="cid:[email protected]">
<sap:Name>PayloadName</sap:Name>
<sap:Description>PayloadDescription</sap:Description>
<sap:Type>Application</sap:Type>
</sap:Payload>
</sap:Manifest>
</SOAP:Body>
</SOAP:Envelope>
The Payload is
<?xml version="1.0" ?>
- <LIST>
etc
Message status
2007-09-19 17:44:56 Success Message successfully received by messaging system. Profile: XI URL: http://srvsapxidev:50000/MessagingSystem/receive/AFW/XI Credential (User): XIISUSER
2007-09-19 17:44:56 Success Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2007-09-19 17:44:56 Success Message successfully put into the queue.
2007-09-19 17:44:56 Success The message was successfully retrieved from the receive queue.
2007-09-19 17:44:56 Success The message status set to DLNG.
2007-09-19 17:44:56 Success Delivering to channel: CC_toMyCompany_XMLFILE
2007-09-19 17:44:56 Error Exception caught by adapter framework: Object not found in lookup of CallSAPAdapter.
2007-09-19 17:44:56 Error Delivery of the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Object not found in lookup of CallSAPAdapter.: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of CallSAPAdapter..
2007-09-19 17:44:56 Success The asynchronous message was successfully scheduled to be delivered at Wed Sep 19 17:49:56 BST 2007.
2007-09-19 17:44:56 Success The message status set to WAIT.
Now I have been reading all the documentation available and forum questions in this area but there is a lot of information but not quite for what I am currently trying to do. I need to preserve the xml file as xml for further processing. This is just a resting place for the file as I am trying to cut down a long running (over a day) collect BPM scenario by collecting the files in the directory then triggering the collect scenario to read in the files from this directory and perform all the processing and mapping in one chunk of short time. (But that is another story)
Any more suggestions appreciated could the SAPCallAdapter not be where I think it is? Does my directory and filename case have to be exact lower and upper case. (I will test this tomorrow)...and let you know if any difference and continue to read the links put on by the other person who answered.
thanks,

File Adapter: SYSTEM_FAILURE_INTERNAL

Hi,
in the adapter monitor I got the following error message for my file adapter (ftp):
Error: Module Exception 'com.sap.aii.af.mp.module.ModuleException: senderChannel
'8b22e3718bad3bf2882e300031a0722f': Catching exception
calling messaging system' found, cause:
com.sap.aii.af.ra.ms.api.DeliveryException:
XIAdapter:SYSTEM_FAILURE_INTERNAL
I think this has somthing to do with my BPM. In the XI Runtime Cache (TCode: SXI_CACHE) the integration process has the return code 99 and when I try to activate the process again I fot the following messages:
S: --- Translating step type 'RECEIVE' with ID '3' ---
S: --- Translating step type 'TRANSFORM' with ID '26' ---
S: --- Translating step type 'SEND' with ID '13' ---
W: Send step: Property exception for '383A2D10157311DAA315DAFC0A872198' is missing
E: Send step: Fault message '579e5eb4157311dac7dcdafc0a872198' is not defined
I: Language not set. Using system default E
Looking for this two numbers I found the following XML lines:
<property id="13" guid="83cf6e10157411daa0e7000bcd69ce64" name="383a2d10157311daa315dafc0a872198" counter="0" type="XIFAULT" valueType="" parentguid="e7665bd013be11daabe3000bcd69ce64">579e5eb4157311dac7dcdafc0a872198</property>
</properties>
Can anybody help me?
Thanks,
Fabian

Hi Fabian,
take a look at the "Send step":
go to your integration process inside IR
and click F7 to check it
then you can also check if your message doesn't need fault message type
one more thing:
<b>are you sure your message interface is asynchronous ?</b>
you can only send async messages to file adapter
also your send step is asyn right?
if you notice anything to be changed
remember you have to go to the SXI_CACHE
and reactivate your BPM just to make sure it has code 0 and not 99
Regards,
michal
Message was edited by: Michal Krawczyk

File Adapter Write Compilation problem JDev 11.1.1.6 and BPEL 2.0

Hi,
Im creating a simple BPEL Project with a One-way Process template project.
I have added just one Partnerlink with a File Adapter to do a write operation.
I have assigned the main process input to the file Write Invoke operation.
But I am getting a compilation error.
Error(81): inputVariable "inputVariable" of type "client:BPELProcessWriteToFileRequestMessage" is not compatible with WSDL message "ns1:Write_msg".
Can you pl help ?
Here is the BPEL syntax :
<?xml version = "1.0" encoding = "UTF-8" ?>
<process name="BPELProcessWriteToFile"
targetNamespace="http://xmlns.oracle.com/FirstApplication/FileWriter/BPELProcessWriteToFile"
xmlns="http://docs.oasis-open.org/wsbpel/2.0/process/executable"
xmlns:client="http://xmlns.oracle.com/FirstApplication/FileWriter/BPELProcessWriteToFile"
xmlns:ora="http://schemas.oracle.com/xpath/extension"
xmlns:bpel="http://docs.oasis-open.org/wsbpel/2.0/process/executable"
xmlns:ns1="http://xmlns.oracle.com/pcbpel/adapter/file/FirstApplication/FileWriter/WriteTextToFile"
xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20"
xmlns:oraext="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc"
xmlns:dvm="http://www.oracle.com/XSL/Transform/java/oracle.tip.dvm.LookupValue"
xmlns:hwf="http://xmlns.oracle.com/bpel/workflow/xpath"
xmlns:ids="http://xmlns.oracle.com/bpel/services/IdentityService/xpath"
xmlns:bpm="http://xmlns.oracle.com/bpmn20/extensions"
xmlns:xdk="http://schemas.oracle.com/bpel/extension/xpath/function/xdk"
xmlns:xref="http://www.oracle.com/XSL/Transform/java/oracle.tip.xref.xpath.XRefXPathFunctions"
xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap">
<import namespace="http://xmlns.oracle.com/FirstApplication/FileWriter/BPELProcessWriteToFile" location="BPELProcessWriteToFile.wsdl" importType="http://schemas.xmlsoap.org/wsdl/"/>
<partnerLinks>
<partnerLink name="bpelprocesswritetofile_client" partnerLinkType="client:BPELProcessWriteToFile" myRole="BPELProcessWriteToFileProvider"/>
<partnerLink name="WriteTextToFile" partnerLinkType="ns1:Write_plt"
partnerRole="Write_role"/>
</partnerLinks>
<variables>
<variable name="inputVariable" messageType="client:BPELProcessWriteToFileRequestMessage"/>
</variables>
<sequence name="main">

<receive name="receiveInput" partnerLink="bpelprocesswritetofile_client" portType="client:BPELProcessWriteToFile" operation="process" variable="inputVariable" createInstance="yes"/>
<assign name="Assign">
<copy>
<from>string('$inputVariable.payload/client:input')</from>
<to>$inputVariable.payload/client:input</to>
</copy>
</assign>
<invoke name="InvokeWriteTextToFile"
partnerLink="WriteTextToFile" portType="ns1:Write_ptt"
operation="Write"
inputVariable="inputVariable" bpelx:invokeAsDetail="no"/>
</sequence>
</process>

The error seen in your case typically occurs when the schemas of BPEL valriable and the schema of message in file adapter WSDL are different. You may use a transform activity in BPEL to map the fields of the two schemas.
You may also like to have a look at various file adapter examples at
http://java.net/projects/oraclesoasuite11g/pages/FileAdapters
These samples provide working examples of how to handle various kinds of data when using file adapter.
Regards.

Group of messages in file adapter

Similar Messages

Maybe you are looking for