on 02-04-2008 5:02 AM
Hi,
I have configured an inbound interface to receive a file and as such configured a file adapter communication channel. Does the file need to be in an XML structure or can it be in a tab delimited or CSV format? If it needs to be in XML format is there any built in functionality to convert from tab delimited or CSV into XML format before XI picks it up?
Thanks, Warren
Hi Raj,
I just got to that blog but having troubles understanding what needs to go into the Content Conversion section. I've entered the following in the Content Conversion Parameters:
Document Name: FILEINPUT
Recordset Name: Record
Recordset Structure: ?
What I'm unsure of is what exactly needs to be entered into record set. Is it just:
Row.fieldNames - field name1, field name 2
Row.fieldSeparater - '0x09'.
Regarsds, Warren
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Warren,
Let's consider ur structure looks like
<MT_Input>
<Rows>
<Field1/>
<Field2/>
<Field3/>
<Field4/>
<Field5/>
</Rows>
</MT_Input>
Follow the below parameters.
Document Name : MT_Input (Give ur message type name)
Document namespace : (Give ur Message type namespace)
Recordset Name : Records (Give any arbitrary name, we are going to ignore it in the below parameters)
Recordset Structue Rows,*
Recordser per message *
Parameters
Name Value
ignoreRecordsetName true
Rows.fieldNames Field1,Field2,Field3,Field4,Field5
Rows.fieldSeparator '0x09'
Rows.endSeparator 'nl'
Also , please refer http://help.sap.com/saphelp_nw70/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/frameset.htm
raj.
Raj,
I'm using this file to populate BAPI_EXCHANGERATE_CREATE. When I view the processed XML messages it shows "Processed" but when I verify it on the R/3 end it hasn't created the exchange rate. Now is there a way I debug this because it's obvious the BAPI is not posting? I am sure all the mandatory data is being passed to the BAPI as I tested this inside R/3 before creating the interface in PI. I went into the communication channel for the RFC receiver adapter and checked on the "Commit Handling for Single BAPI Calls" but doesn't seem to make a difference.
Regards, Warren
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Raj,
Thanks for your explanation - it worked fine but I didn't quite understand all the various pieces of information that I had to enter. Do you have any documentation explaining this? The SAP Help is more of a reference than a working example.
Thanks, Warren
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Raj,
I just saw the option in the Communication Channel to specify Content Coversion. The file will look like the following:
M<tab>01012007<tab>USD<tab>AUD<tab>1.40
M<tab>01012007<tab>USD<tab>GBP<tab>1.40
and so on....
Pretty simple structure.
Regards Warren
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Warren,
The solution is pretty simple. According to ur structure create Datatype with five fields something like below
Records -- 0..Unbounded
--Field1
--Field2
--Field3
--Field4
--Field5
Then in the sender adapter apply the conversion parameters. Please refer the links provided above. Since u've tab space u can follow the below blog on how to specify TAB parameters
/people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter
If u've any doubts, plz reply back.
raj.
Hi Raj,
The scenario is File->BAPI. So XI will pick up the file (flat) and map the source to the target fields in the BAPI structure. So I'm wondering if XI will allow me to use a flat file?
Regards, Warren
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
As suggested you need to go for file content conversion if ur file is CSV format.
Can you please go through the below web log and do the configuration in File adapter.
FCC
Ref:
Sender -
/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
Key value:
/people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
/people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter -/people/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns
/people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem
/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
Thnx
Chirag
Warren,
Are u getting the same csv file from the source and wish to move to other location? Or you are getting XML as source and wish to convert csv file?
If the source and target are csv then there is no problem no need for any conversion, u can send it directly.
If the source is xml and the receiver is csv then u need to do content conversion in receiver adapter.
For second case, plz wait lot of links will be provided by our forum mates...
raj.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.