Receiver File Adapter - File Content Conversion

My XML is like this in XI:
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:Target xmlns:ns0="http://test.com">
- <Target>
- <Directory>
  <Comment_1>#</Comment_1>
  <Directory_Rec>testfile.csv</Directory_Rec>
  </Directory>
- <File>
  <Comment_2>#</Comment_2>
  <File_Rec>testfile.csv</File_Rec>
  </File>
  <Target_Rec>Record 1</Target_Rec>
  <Target_Rec>Record 2</Target_Rec>
  <Target_Rec>Record 3</Target_Rec>
  </Target>
  </ns0:Target>
and my CSV file should looklike
#testfile.csv
#testfile.csv
Record 1
Record 2
Record 3
How can I do that. Would someone help he. If I put fieldseparator as 'nl' its writing as follows
Record 1
Record 2
Record 3

Hi Ram,
with the structure you have given we can not achieve your target csv structure. at the max you can achieve the output as the following
#testfile.csv
#testfile.csv
Record 1Record 2Record 3
using the below specified config
Recordset Structure: Target,Directory,File
Target.fieldSeparator as 'nl'
Directory.fieldSeparator as '0'
Directory.endSeparator as 'nl'
File.fieldSeparator as '0'
File.endSeparator as 'nl'
in teh output the last line Record 1... comes like that because the File.fieldSeparator's value overrides the parents fieldSeparator i.e of Targets. '0' stands for no separator.
if you want to achieve your target output Target_Rec should be inside one more node say TargetRecords
and XML should be like this in XI:
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:Target xmlns:ns0="http://test.com">
- <Target>
- <Directory>
<Comment_1>#</Comment_1>
<Directory_Rec>testfile.csv</Directory_Rec>
</Directory>
- <File>
<Comment_2>#</Comment_2>
<File_Rec>testfile.csv</File_Rec>
</File>
<TargetRecords>
<Target_Rec>Record 1</Target_Rec>
<Target_Rec>Record 2</Target_Rec>
<Target_Rec>Record 3</Target_Rec>
</TargetRecords>
</Target>
</ns0:Target>
and the content conversion configuration should be
Recordset Structure: Target,Directory,File,TargetRecords
Target.fieldSeparator as 'nl'
Directory.fieldSeparator as '0'
Directory.endSeparator as 'nl'
File.fieldSeparator as '0'
File.endSeparator as 'nl'
TargetRecords.fieldSeparator as 'nl'
Regards,
Sundar

Similar Messages

  • File Adapter with Content Conversion

    Hi -
    I am trying to convert a Flat file which has data as
    firstnamelastnamecompanyName
    Now i have created a message type which has a root name as Contact and its children are FirstName,LastName,Company.
    And in the configurator i have created a file adapter with the content conversion, but being very new to XI i have never used a file adapter with content conversion.  This is what i have in my Content Conversion Parameters.Please correct my code.
    Document Name      ::   MT_Contact
    Document Namespace ::   http://venkat
    Document Offset    :: <i>i did not enter anything here</i>
    Recordset Name     ::   RootNode(i gave this name just like that,,, Should it be something from the IR??
    Recordset NameSpace:: <i>i did not enter anything here</i>
    Recordset Structure::   Contact (this is the name in my IR
    Recordset Sequence ::  Ascending
    Recordsets per Message :: Contact,* (Can someone explain what should be given here)
    Then in the bottom in the name value pairs i have given
    Contact.fieldNames   =   FirstName,LastName,Company
    Contact.fieldSeparator = #
    When i am using the above configuration the error i am getting in RWB is Error: Conversion initialization failed: Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
    Format error in 'xml.recordset' argument: incomplete structure (name,number) pairInvalid 'xml.recordsetsPerMessage' value 'Contact,*' found
    I am very new to XI and i am unable to understand what exactly each field means in the file adapter when the content coversion is used. Can someone take the pain of explaining them.
    Thank you
    Venkat

    Hi,
    Use the following to create an XML strucutre like this,
    <MT_CONTACT>
    <CONTACT>
    <FirstName> </FirstName>
    <LastName> </LastName>
    <CompanyName> </CompanyName>
    </CONTACT>
    <MT_CONTACT>
    DocumentName : MT_TEST
    DocumentNamespace : Yournamespace
    RecordserName : record
    RecordsetStructure : CONTACT,1
    In the table,
    ignoreRecordsetName  : true
    CONTACT.fieldNames : FirstName,LastName,CompanyName
    CONTACT.fieldSeparator : #
    Go through the links suggested by moorthy and also these blogs to understand content conversion better,
    /people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
    /people/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns
    /people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
    /people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem
    /people/sap.user72/blog/2005/01/06/how-to-process-csv-data-with-xi-file-adapter
    Regards,
    Bhavesh

  • Sender file adapter with content conversion  Simple XML

    Hi experts,
    I'm trying to parametrize my sender file adapter content conversion.
    I'm receiving a text file with one single line like:
    AA1;AA2; AA3;
    and I want to convert it to an XML like
    <MT_A1>
    <field1>AA1</field1>
    <field2>AA2</field2>
    <field3>AA3</field3>
    </MT_A1>
    Actually I know how to do somenthing like
    <MT_A1>
        <LINE>
              <field1>AA1</field1>
              <field2>AA2</field2>
              <field3>AA3</field3>
         <LINE>
    </MT_A1>
    What I want is remove the <LINE> tag from my XML.
    Regards
    Gonzalo
    Edited by: Gonzalo del Castillo on Nov 28, 2008 2:18 PM

    Hi
    Use this help document for receiver FCC
    http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
    Content Conversion (Pattern/Random content in input file)
    File conversion text to xml (Few Last Post)

  • Sender File Adapter and content conversion

    Hi,
    How can we remove the last line from the file using content conversion?
    The last line should not be read from the input file.
    Like for the first line we can use Document Offset .......similarly do we have any option for the last line?

    >
    neelansha singh wrote:
    > date                       Empno         Empname
    > 19.03.2009            12345            Neel
    > 20.03.2009             34566           Neelkanth
    > EmpDes                 Japan        100
    >
    >
    > The file is like this first row i have removed using document offset.......from 2nd row till nth row the structure is as shown above and the last row has no. of fields 1 less than all other rows and also its root node is different like shown above its rootnode is EmpDes..........How to use File content conversion for this?
    do you want to avoid the last line i.e
    EmpDes                 Japan        100
    in that case the 3 options are
    1. use a adapter module and remove the last line - this is the ideal option
    2. use a OS script - will work but only if you are using the NFS option in the file adapter instead of FTP
    3. read that also using content conversion (treat it as a trailer) and ignore it during the mapping

  • File sender adapter and content conversion with polish character

    We are loading a csv file with PI 7.0 file sender adapter using "content conversion" - all fields go through EXCEPT a special character hex '208C' (space in front) looks like "Æ" is converted to hex 'C28C'.
    We are using code page UTF8
    We are using:
    enclosuresign "
    enclosuresignescape ""
    fieldcontentformatting nothing
    enclosureconversion NO
    Hope some one can help

    Hi Bohamo,
    Hope you have set the following for your file sender adapter :
    1. Transfer Mode is set to Binary,
    2. File Type Text,
    3. Encoding ISO-8859-1( for Western European Latin ).
    Inorder to recognize Polish Character, try as follows :
    Your sender file after coming into Pi has XML encoding declaration 'UTF-8'.
    Write a simple XSLT mapping to change the value of the attribute "encoding" to "ISO-8859-1" in the output XML of message mapping . Include this XSLT map as the second mapping step in your interface mapping.
    First step in your interface mapping will be your already existing message mapping.
    An example of the XSL code :
    <?xml version='1.0'?>
    <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
    <xsl:output method='xml' encoding='ISO-8859-1' />
    <xsl:template match="/">
    <xsl:copy-of select="*" />
    </xsl:template>
    </xsl:stylesheet>
    or you can also do java mapping if you are comfortable with java code !
    Cheers,
    Ram.

  • File sender with content conversion and ignoreRecordsetName

    Him,
    I have an scenario with a compressed file sender with content conversion.
    In my sender cc i have:
    1     AF_Modules/PayloadZipBean     Local Enterprise Bean     unzip
    2     AF_Modules/MessageTransformBean     Local Enterprise Bean     transform
    3     CallSapAdapter     Local Enterprise Bean     2
    In module configuration, I have also added:
    xml.ignoreRecordsetName  --> true
    But RecordsetName is not removed from XML
    Why?
    thanks, in advance
    Carme

    Hi,
    No need to enter anything in module configuration. Just specify following Name-Value pair in the table provided on the Content Conversion tab of your file adapter.
    Add a row with Name = ignoreRecordsetName and Value = true (Both case-sensitive)
    For details, see [this link|http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm].
    [some more here|http://www.riyaz.net/blog/index.php/2008/02/20/xipi-file-content-conversion-for-complex-structures/]
    Regards,
    Riyaz

  • Sender File Adapter : File Name Determination

    Hi All,
    My Scenario :
    1) Im my scenario i need only the "FileName" of the File when picked up by the Sender File Adapter.
    2) Rest Content of the File need not be in the XML file format.
    Now what i did was developed "File Adapter Module " to get the "FileName" when picked up by the Sender File Adapter.
    Outcome : When i put the developed module at first and put the file in specified folder allowint the Sender file Adapter to pick up. Now Everything is fine working when one kind of File is placed as per my Content Coversion paramaters.
    Actual : My Client would place file of any kind (.jpeg -> Mostly , gif ) i need to get only the file name in the Outbound interface , which i would split it further to my Target Interface.
    How could i achieve this , when i took away this content conversion , in sxmb_moni it shows error.I need only the filename in the Outbound not the Content , moreover the hit is i donot know what could be content of my file as it could be different and varing , so i could not set particular content conversion paramters:
    Second Question:
    Now my outbound XML interface looks as below when i test with a file , with proper content conversion paramerters:
      <?xml version="1.0" encoding="UTF-8" ?>
    - <MT_DMS_FINAL>
    - <Record>
    - <Row>
      <FirstName>2323_eer_rtr</FirstName>
      </Row>
      </Record>
      <FileName>d:\mdmtest\srinivaS\padusrini.txt</FileName>
      </MT_DMS_FINAL>
    Well i have designed in my MI only FirstName , how to capture this element "FileName" which i can use it in mapping , if i have to write any UDF to capture it ,please guide me.
    thx in advance for u r help
    with regards
    Srini

    Hi Guys ,
    Can i use File Content Conversion for .pdf document , my pdf doc content is not known, means it"s a complete info doc.I may get .jpeg any picture or drawing.
    I thought i can use below file content conversion paramters:
    Document Name : MT_DMS_FINAL
    RecordSet Name : Record
    RecordSet Structure : Row,*
    Row.fieldNames - FirstName
    Row.fieldSeparator - ;
    Row.processFieldNames - fromConfiguration
    Row.additionalLastFields - ignore
    Row.missingLastfields  -  ignore
    Now i put a pdf doc of unknown content , and my assumption was some set of charater would be dumped in  XML and rest would be ingonered which is least bothered part in my scenario , unless i get the filename from runtime ot Adapter module developed
    But in RWB CC monitoring i see below error :Error: org.xml.sax.SAXParseException: Illegal XML character:  &#xb;.
    Any views on this , can any one help me out with the above requirment. Hope u guys got wat am trying to put out here
    thx in advance for u r help
    with regards
    Srini

  • Receiver File Adapter - File Content Converstion

    Hi,
    I have an xml-output (as a string) but I need to use the content converstion tool in the receiver file adapter to make this into one string without the nodes etc. Example of the format that i want the file to be in:
    1AXXX10363501       00000013PC..........etc.
    And I need each instance of SBR in a new row. How can I do this? Please tell me if things are unclear.
    Example of the structure the file has now without content converstion.
    <?xml version="1.0" encoding="UTF-8"?>
    <StockBalanceFlatfile><Rows><SBR>
    <Type>1</Type>
    <Mode>A</Mode>
    <Owner>XXX</Owner>
    <SKU>10363501</SKU>
    <Quantity>00000013</Quantity>
    <UOM>PC</UOM>
    <Attr1>2476</Attr1>
    <Status>0000</Status>
    <Filller>----
    </Filller>
    <ELM>*</ELM>
    <CRLF>CRLF</CRLF>
    </SBR></Rows></StockBalanceFlatfile>
    Best Regards
    Claes

    Claes,
      Use the below content conversion parameters.
    <u>Content Coversion Parameters</u>
    <b>Recordsetstructure</b>    StockBalanceFlatfile,Rows,SBR
    <b>Name</b>     <b>Value</b>
    SBR.endSeparator           'nl'
    If it doesn't help, reply back.
    Best Regards,
    raj.

  • Doubt regarding Recever file adapter file content conversion (FCC)

    Hi Expetrts, below is the my target structure.
    <?xml version="1.0" encoding="TF-8"?>
    <ns1:MT_StatusChange xmlns:ns1="urn:passhe.com/ChangeOfStatusISA26">
         <IV_ST_OBJID>65390091</IV_ST_OBJID>
         <IV_BEGDA>25082008</IV_BEGDA>
         <LT_STUDENT_STATUS>
               <item>
              <HS_CAMPUS>65</HS_CAMPUS>
              <STOBJID>65390091</STOBJID>
              <STUDENT12>michal</STUDENT12>
              <HS_STATUS>MISC</HS_STATUS>
               <item>
            <LT_STUDENT_STATUS>
    </ns1:MT_StatusChange>
    How to configure in File Content Conversion Recever File Adapter for above target structure. i have done as below, but i am getting error.  please correct me where i did mistake.
    Recordset Structure : IV_ST_OBJID,IV_BEGDA,LT_STUDENT_STATUS,item
    IV_ST_OBJID.fieldNames : IV_ST_OBJID  -> for this field there is no subfield
    IV_ST_OBJID.fieldSeparator: , (comma)
    IV_BEGDA.fieldNames : IV_BEGDA -> for this field there is no subfield
    IV_BEGDA.fieldSeparator: , (comma)
    LT_STUDENT_STATUS.fieldNames  : HS_CAMPUS,STOBJID,STUDENT12,HS_STATUS
    LT_STUDENT_STATUS.fieldSeparator: 'nl'
    item.fieldNames  : HS_CAMPUS,STOBJID,STUDENT12,HS_STATUS
    item.fieldSeparator: , (comma)
    I am getting below error:
    'Conversion configuration error: Unknown structure 'ns1:MT_StatusChange' found in document', probably configuration error in file adapter (XML parser error)'
    Thanks
    Dhanush.

    Hi Dhanush,
                        It is better always if u have a structure with Header and trailers if u have a subsrtuctures in it & always try make it in this format:
    <?xml version="1.0" encoding="UTF-8"?>
    <MT_ContentConversion_Test>
       <Header>
          <F1>HF1</F1>
          <F2>HF2</F2>
       </Header>
       <Item>
          <F1>IF1</F1>
          <F2>IF2</F2>
       <Item>
       <Trailer>
          <F1>TF1</F1>
          <F2>TF2</F2>
       </Trailer>
    </ns0:MT_ContentConversion_Test>
    Try to go through this blog it will be very helpful to u :
    /people/shabarish.vijayakumar/blog/2007/08/03/file-adapter-receiver--are-we-really-sure-about-the-concepts
    Regards,
    Vinod.

  • File Adapter - File Content Conversion to XML last element missing

    I'm using the SAP File Adapter with File Content Conversion to convert | (pipe) delimited records into XML.
    When the last field is blank, I would expect that an empty node gets created, however, the node doesn't get created at all.
    For example given these settings...
    Record.fieldSeparator = |
    Record.endSeparator = 'nl'
    Record.fieldNames = FIELD1,FIELD2,FIELD3
    Using this three record file as my data...
    |123|XYZ
    ABC||XYZ
    ABC|123|
    When converted to XML, this is what the recordset XML structure looks like...
    <Recordset>
    <Record>
    <FIELD1 />
    <FIELD2>123</FIELD2>
    <FIELD3>XYZ</FIELD3>
    </Record>
    <Record>
    <FIELD1>ABC</FIELD1>
    <FIELD2 />
    <FIELD3>XYZ</FIELD3>
    </Record>
    <Record>
    <FIELD1>ABC</FIELD1>
    <FIELD2>123</FIELD2>
    </Record>
    </Recordset>
    Notice that the last record is missing the "FIELD3" element.
    Edited by: William Krick on Jun 17, 2011 4:49 PM

    Giuseppe Agnello wrote:
    > Sorry, there was a typo in the parameter name.
    > Word fields should start with capital F.
    > Try with Record.missingLastFields, with value "add"
    >
    > http://help.sap.com/saphelp_nw70/helpdata/en/ae/d03341771b4c0de10000000a1550b0/frameset.htm
    >
    > Similar issue was resolved with same parameter in this thread:
    > Sender file adapter with FCC not creating last field
    That did the trick.  It was a typo.  Thanks Giuseppe.
    I'm willing to bet that this parameter was added to fix the parsing bug without breaking existing users that had already worked around the original bug.   You shouldn't really have to special case the last field.

  • Sender File Adapter - File Content Conversion

    Hello,
    i do have a problem with the file content conversion at the sender file adapter.
    I have configured the file content conversion with key field defined
    keyfield: key
    recordsetstructure is set as head,1,item,*
    head.fieldSeparator  | 
    head.beginSeparator  |
    head.endSeparator  |
    head.keyFieldValue  H
    head.fieldNames  key,....
    item.fieldSeparator  | 
    item.beginSeparator  |
    item.endSeparator  |
    item.keyFieldValue I
    item.fieldNames  key,....
    When i run it like this it will not read since it has a problem to identify the key fields.
    When ever i change the whole logic to be not based on fieldseparator but on fixed length, everything is working perfectly fine.
    but this unfortuantly doesn't help as i have no fixed structure for the rest of the fields.
    also when i change the recordsetstructure to head,1,item,1 my file is also processed correctly, of corse only for the first line, it at least tells me that the file structure is correctly defined.
    Can anyone help why the identification for the keyfields doesn't work with field names and separator but in the same set up with fixed lengths ?
    thanks a lot

    Hello All,
    thanks for the helpful answers.
    So i tried Jayan tip and removed the begin Separter.
    Unfortuantly my file is really looking like this |H|...|...| for the header record
    and for the item record |I|...|...| ( this was an" I" like in Item ...
    In my opinion this means i really do have a begin seperator which is the same like the field separator.
    When i removed it from both the file and the config it started to work.
    So i wrote an java function which will trow away the first digit in this case and integrated it in my szenario.
    So that when this file is read there is no | as a begin flag anymore.
    And the whole thing starts to work, this sounds more like a bug then a feature but anyway i am happy.
    so thanks a lot
    Tina

  • File adapter modules : Access to file data before content conversion

    I have a file sender channel for which content conversion in applied. The incoming file has data in comma separated values format.
    e.g.
    102366,Amol Joshi,DEPT1
    107752,XYZ PQR,DEPT2
    I want to access the the actual data in the file before content conversion takes place. Is it possible to access this data inside the adaper module? I tried creating an adapter module and put it before CallSAPAdapter,it still gets the XML after content conversion as the input data to the module.
    Any pointers?

    Hi Amol,
    I dont know if it is the right approach.
    But if u r not able to meet ur requirement u can do one work around.
    Use Message Transformation Bean to convert it once again in to CSV (flat file structure) and then proceed with ur module.
    There should be a better way than this.
    Hope we could find a better solution in the forum.
    Regards,
    Sudharshan

  • Remove of quotes"' in the sender file adapter -- file content conversion

    HI Guys,
    MY source file is comma seprated file (,) in the file i had quotes" " for the data like
    "5000543","0.00","03/04/2009",
    is there any way i can remove the quotes in file content conversion
    Please help me on this
    Regards
    Srinivas

    Srinivas,
    This should not be a big deal, because your fields are separated by a comma. So you need to keep in mind like you are doing the content conversion for a csv file.
    See this blogs for some information:
    /people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
    /people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
    In the second blog 1345 there are parameters for content conversion. So similarly mention your conversion parameters in your sender communication channel. So after converting to xml your input fields have values like:
    field1:  "5000543"
    field2:  "0.00"
    field3: "03/04/2009"
    So all your field values has with "". Now you can use either standard replace funciton or a udf as given above and then it will remove the quotes and then you can map according to your requirements. If you think sometimes you can get quotes and sometime not in the file then you can use function like startswith or endswith along with exists and can map accordingly.
    Regards,
    ---Satish

  • Create substructures via file adapter - file content conversion

    I have a need to create a structure as follows using file content conversion from a flat file
    source:
    H1~00
    S1~1A
    L1~1B
    S1~2A
    L1~2B
    S1~3A
    L1~3B
    <?xml version="1.0" encoding="UTF-8"?>
    <ns:x_MT xmlns:ns68="urn:abt.com/IAM">
      <DocHeader>
          <Label />
          <type />
      </DocHeader>
      <DocItem>
          <Ship>
            <Label />
            <type />
          </Ship>
          <Lines>
            <Label />
            <type />
          </Lines>
       </DocItem>
    </ns:x_MT>
    I can successfully create a x_MT but I do not get the  heirarchy (DocItem node) and therefore I'm having trouble on the mapping side.
    My file content conversion is as follows:
    Document Name: x_MT
    Document Namespace: urn:abt.com/IAM
    Recordset Name: x_DT
    Recordset structure: DocHeader,1,Ship,,Lines,
    Recordsets per message: *
    Key Field Name: label
    DocHeader.fieldSeparator     '0x7E'
    DocHeader.endSeparator             'nl'
    DocHeader.fieldNames             label,type
    DocHeader.keyFieldValue         H1
    Ship.fieldSeparator     '0x7E'
    Ship.endSeparator     'nl'
    Ship.fieldNames             label,type
    Ship.keyFieldValue      S1
    Lines.fieldSeparator     '0x7E'
    Lines.endSeparator     'nl'
    Lines.fieldNames     label,type
    Lines.keyFieldValue     L1
    What I get is a structure without the node DocItem and therefore appears like a flat structure and mapping fails since I have multiple 'Lines' and only the last one gets mapped.
    I've read all the weblogs around this topic and none seemed to address more than one node. Please help.
    Thank you,
    Parimala

    Hi Parimala,
    As per SAP help document the structure created by content conversion would look like this..
    http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
    <documentName>...
       <recordset>
    <NameA>
    <field-nameA1>field-value</field-nameA1>
    <field-nameA2>field-value</field-nameA2>
    <field-nameA3>field-value</field-nameA3>
    </NameA>
    <NameB>
    <field-nameB1>column-value</field-nameB1>
    <field-nameB2>column-value</field-nameB2>
    <field-nameB3>column-value</field-nameB3>
    </NameB>
       </recordset>
       <recordset>
       </recordset>
    </documentName>...
    If you require a <DocItem> node then you have to handle this in mapping.
    Regards
    Anand

  • File Adapter: Initialization error: Conversion initialization failed

    Hi all,
    I'm trying to establish a file adapter (FTP, File Content Conversion).
    In the adapter monitor I' ve got the following error:
    Sender Adapter v1325 for Party '', Service 'BS_ACN_PCS_A':
    Configured at 14:49:34 2005-08-29
    Initialization error: Conversion initialization failed with java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
    Format error in 'xml.recordset' argument: incomplete structure (name,number) pair
    My content conversion parameters are:
    BP_BusinessPartnerMasterData_IncomingData.fieldFixedLengths:
    20,50,50,1,10,50,10,50,5,20,20,15,15
    BP_BusinessPartnerMasterData_IncomingData.fieldNames: Number,Name2,Name1,Gender,Birthdate,City,Postcode,Street,
    HouseNo,PhoneNumber,Fax,BankId,BankAccount
    BP_BusinessPartnerMasterData_IncomingData.fieldContentFormating:
    trim
    BP_BusinessPartnerMasterData_IncomingData.keyFieldInStructure:
    ignore
    What could be the error or where I have to look for it?
    Thanks,
    Fabian

    Yes,
    Recordset name: BP_BusinessPartnerMasterData_IncomingData
    Recordset structure: BP_BusinessPartnerMasterData_IncomingData
    The corresponding Message Type:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://pcs.acn.com/basicdata" targetNamespace="http://pcs.acn.com/basicdata">
         <xsd:element name="BP_MasterDataIncomingFil" type="BP_BusinessPartnerMasterData_IncomingData" />
         <xsd:complexType name="BP_BusinessPartnerMasterData_IncomingData">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   f323a4b018a911da9fd9000bcd69ce64
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="Number">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8500fe111da89f2d1210a87220d
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Id from Sender for BP
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="20" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Name2">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8510fe111dacfd7d1210a87220d
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Last name or Company name
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Name1">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8520fe111da94bad1210a87220d
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             First name or Company name 2
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Gender">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8530fe111da99add1210a87220d
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             m or f or blank
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Birthdate">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8540fe111dab156d1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="City">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8550fe111daa58cd1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Postcode">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8560fe111dac0c2d1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Street">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8570fe111dabbd3d1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="HouseNo">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8580fe111dab63fd1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="5" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="PhoneNumber">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8590fe111dac782d1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="20" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Fax">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e85a0fe111daa9ebd1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="20" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="BankId">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e85b0fe111dace1ed1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="15" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="BankAccount">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e85c0fe111da8801d1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="15" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
              </xsd:sequence>
         </xsd:complexType>
    </xsd:schema>

Maybe you are looking for

  • I can't get my software to recognize my second nano.  How?

    no more message than that!

  • Sleep wake failure experienced a problem

    I am experiencing random (and quite frequent) restarts with my 5k iMac. This is the error message I get: This problem seems to have started after I recently connected two LaCie thunderbolt 2 external backup drives. Prior to that I was using a LaCie B

  • FSG:EXPAND PARENT VALUE PROFILE OPTION 에 대한 설명

    제품 : FIN_GL 작성날짜 : 2004-10-14 FSG:EXPAND PARENT VALUE PROFILE OPTION 에 대한 설명 ============================================== PURPOSE FSG 작성 시 'FSG: Expand Parent Value' profile 의 역할에 대해 설명한다. Explanation FSG:Expand Parent Value profile 은 FSG report 작성

  • Add lens blur

    This question was posted in response to the following article: http://help.adobe.com/en_US/photoshop/cs/using/WSA75837E3-FE05-4f86-A9DF-3C0DD602CA63a.htm l

  • Elements 12 - Software setup screen??

    Where is Software Setup Screen in Photoshop Elements 12 in the trial version; purchased and now need to enter serial number.