Significance of Document Name in JDBC Sender

hi folks,
tell me what exactly mean by the Document Name parameter in the JDBC Sender adapter? where does that plays?
thanks
nikhil bos

> tell me what exactly mean by the Document Name
> parameter in the JDBC Sender adapter? where does
>  that plays?
If you created MT_JDBC_Sender (for Example)
Go to IR and Test your mapping..then take the input message from there and paste it to the Notepad...you will find the Root Element will be
<<b>MT_Sender_JDBC</b> >
  <row>
<>
</MT_Sender_JDBC >
now when you configured the JDBC adapter then by defalut the Document Name is <b>resultset</b>
so XML from From JDBC sender adapter will come in this format.:
<<b>resultset</b> >
  <row>
<>
</<b>resultset</b> >
So coming XML does not match with the structure that u define..so finally need to overide the name of the defult document namespace so that it will not fail at runtime:-)
Thanks
Farooq.

Similar Messages

  • Stuck with logical system name for JDBC Sender system!!!!!!!!!!!!!

    Hi All,
    I'm doing a scenario as JDBC2FILE.
    I tried to add my jdbc sender system to SLD. So i created the technical system
    now i'm creating business system...what should i give at logical system name tab? I've created tech system and business system as third party.
    do we need logical system name in this scenario where we are not interacting with any R/3???
    can anyone suggest the way to achieve this scenario?
    Thanks in advance.....
    Santhosh.

    Hi Santhosh,
    I just want to add ons..few more information which it might help you.
      You no need to give logical system when you are using Thirdpaty.
    Please check the below blog you will get more idea how to proceed to achieve the JDBC Scenario.
    /people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
    If you have any doubts while proceeding with your scenario plesae let me know..I will try my level best.
    Thanks and Regards,
    Chandu

  • Problem with XML document created by JDBC Sender adapter

    We are using a sender JDBC adapter to publish data out of a DB2 table.  The message generated by the XI sender adapter seems to have 2 extra characters that break our mapper.  You can see the characters (the dashes on lines 2 and 4) in the XML document that I copied from message monitoring.  Once I remove these dashes and test the mapper in test mode, it works.  If I test with the dashes, the mapper fails. Has anybody else seen this issue?
    Regards,
    Ivailo
      <?xml version="1.0" encoding="utf-8" ?>
    - <ns:CUSTOMER_SCOPE xmlns:ns="http://com.gatx/xi/RCRepairEstimate">
    - <row>
      <CM_CUST_GROUP_CODE>2915</CM_CUST_GROUP_CODE>
      <CM_CUST_SUB_CODE>2</CM_CUST_SUB_CODE>
      <CM_CUST_ID />
      <CM_TERMS>30</CM_TERMS>
      <CM_CUST_SHIPTO_GRP>2915</CM_CUST_SHIPTO_GRP>
      <CM_CUST_SHIPTO_SUB>2</CM_CUST_SHIPTO_SUB>
      <CM_BILL_NAME>GATX RAIL/CANADA</CM_BILL_NAME>
      <CM_BILL_ADDR1>540 5TH AVENUE SW SUITE 1225</CM_BILL_ADDR1>
      <CM_BILL_ADDR2 />
      <CM_BILL_ADDR3 />
      <CM_BILL_CITY>CALGARY ALBERTA</CM_BILL_CITY>
      <CM_BILL_STATE />
      <CM_BILL_ZIP5>0</CM_BILL_ZIP5>
      <CM_BILL_ZIP4>0</CM_BILL_ZIP4>
      <CM_FOREIGN_ZIP>T2P 0M2</CM_FOREIGN_ZIP>
      <CM_ATTENTION>AL FREDERIKSEN</CM_ATTENTION>
      <CM_SALESMAN_INI />
      <CM_DB_RATING />
      <CM_CRED_LIMIT>0</CM_CRED_LIMIT>
      <CM_CRED_FLAG />
      <CM_LAST_CHG_DATE>1282005</CM_LAST_CHG_DATE>
      <CM_CHANGED_BY_USER>XSKISSEL</CM_CHANGED_BY_USER>
      <CM_REORG_CODE>N</CM_REORG_CODE>
      <CM_CORP_GROUP_CODE>0</CM_CORP_GROUP_CODE>
      <CM_CORP_SUB_CODE>0</CM_CORP_SUB_CODE>
      <CM_RECORD_CODE />
      </row>
      </ns:CUSTOMER_SCOPE>

    Hi Ivailo,
    I think the problem lies in the way you copy the data from monitor.
    whenever you want to copy data from XI monitor to test in your IB,make sure you select "view source" and then copy the source message otherwise you will get the browser view of the XML document which contain those "-" for expanding and collapsing the document.
    Regards,
    Sridhar

  • Document name, servlets, jdbc

    Yes ;)
    Everything works just fine, my servlet now reads binary documents from my database and pushes them over to the client web-browser.
    But... ducument names are all set to the servletname... what an annoyance.
    Ideas, anyone?

    And for parsing: (I haven't tested it but I remember using something like this long time ago)
    Hashtable params = new Hashtable();  //this will contain param/value pairs
    String queryString = request.getQueryString();
    if (queryString == null) {
       //no query String .. do whatever you need to do in that case
    StringTokenizer st = new StringTokenizer(queryString, "/");
    while (st.hasMoreTokens()) {
         String key = st.nextToken();
         String value = null;
         if (st.hasMoreTokens()) {
             value = st.nextToken();
         params.put(key, value);
    String idString = (String)params.get("id"); //id in the sample URL you provided

  • JDBC Adapter-XML Document Name

    I am working on XI 2.0 and need to change the XML document name I am receiving from an inbound JDBC adapter.  The document I am receiving is:
    <resultset>
      <row>
        <col1>ABC</col1>
        <col2>123</col2>
      </row>
    </resultset>
    I want to receive:
    <MyDocumentName>
      <row>
        <col1>ABC</col1>
        <col2>123</col2>
      </row>
    </MyDocumentName>
    Does anyone know how to override the default "resultset" name from the JDBC adapter???  The reason I need to do this is because my message mapping does not work properly unless I have the Message type of the message from my JDBC adapter as "resultset". 
    Thanks for your help!
    Dan Pettingill

    (Note: I work with Dan Pettingill, the starter of this thread)
    I decompiled the class Renato suggested, but I don't
    think that's going to be the solution.  The DB2XMBProcesser is dependent on XI properly setting the properties values for the jdbc adapter.  DB2XMBProcesser will use a property named "db.documentname" to set the name of the root node of the DB2 results. If no such property is defined, the default value of resultSet is used.
    [documentName = getParaWithDefault("db.documentName", "resultset");]
    Our problem seems to be that XI is not passing along the parameters we define in the adapter configuration.  We've tried numerous combinations and names, but they never take. 
    The only way we can get XI to recognize that we are sending in a documentName parm is to call it "docName".  Any other name is essentially ignored (including db.documentname, documentname, XMB.docName, and a lot of other permutations as well).
    But here is the log from that adapter when we do so.  Not that it sees the value we're setting, but it won't set the documentname parm going to the jdbc.
    2004-08-31 17:33:45 : jdbcListener
    Raw configuration data ***
    Transport protocol: JDBC, version
    Message protocol: JDBC, version
    pollInterval|301
    additionalParameters|true
    jdbcDriver|com.ibm.db2.jcc.DB2Driver
    retryInterval|null
    dbpassword|***
    queryStatement|SELECT * FROM RBPRDB.T1256;
    queueName|null
    autoCommit|false
    updateStatement|Delete from RBPRDB.T1256 Where GUID Is Not Null;
    dbdisconnect|false
    dbuser|r50445
    adapterStatus|active
    isolationLevel|2
    addParameterParams|*** TABLE , 2 ROWS DEFINED ***
    addParameterParams|addParameterParams$0$addParameterParamName$docNamespace
    addParameterParams|addParameterParams$0$addParameterParamValue$urn:freescale.com
    /xi/db2-ims/wms
    addParameterParams|addParameterParams$1$addParameterParamName$docName
    addParameterParams|addParameterParams$1$addParameterParamValue$SelectAckQueue
    pollIntervalMsecs|null
    execute|null
    connectionURL|jdbc:db2://WACCTSO.sps.mot.com:9003/WACCDB2T
    qualityOfService|EO
    Used configuration data ***
    'MessageProtocol': 'JDBC'
    'adapterStatus': 'active'
    'addParameterParams.dbEncoding': ''
    'addParameterParams.docName': 'SelectAckQueue'
    'addParameterParams.docNamespace': 'urn:freescale.com/xi/db2-ims/wms'
    'addParameterParams.docNamespaceScope': 'root'
    'additionalParameters': 'true'
    'autoCommit': 'false'
    'connectionURL': 'jdbc:db2://WACCTSO.sps.mot.com:9003/WACCDB2T'
    'dbdisconnect': 'false'
    'dbencoding': ''
    'dbpassword': '***'
    'dbuser': 'r50445'
    'documentname': 'resultset'
    'documentnamespace': ''
    'execute': ''
    'isolationLevel': '2'
    'jdbcDriver': 'com.ibm.db2.jcc.DB2Driver'
    'pollInterval': '301'
    'pollIntervalMsecs': '0'
    'qualityOfService': 'EO'
    'queryStatement': 'SELECT * FROM RBPRDB.T1256;'
    'retryInterval': '301'
    'updateStatement': 'Delete from RBPRDB.T1256 Where GUID Is Not Null;'
    OK - initialized

  • JDBC send data to oracle, oracle only accept column name in Upper case

    Hi experts,
    I am doing a scenario File --> XI --> JDBC,  JDBC send data to a Oracle 10g database, I have configured JDBC receiver to use XML-SQL format. in oracle database ,  table "EMPLOYEE" has a column "NAME", but when I send data to oracle using JDBC receiver, the column is "name", then XI complains
    " 'EMPLOYEE' (structure 'insert'): java.sql.SQLException: FATAL ERROR: Column 'name' does not exist in table 'EMPLOYEE'.
    can anyone help me to let oracle accpet column "name". I can't change colum in JDBC receiver from "name" to "NAME".
    Thanks a lot.

    <i>can anyone help me to let oracle accpet column "name"</i>
    Making Oracle case insensitive is not possible (in my opinion). By default all object names are stored in UPPER case in the rdbms dictionary.
    When XI searches for column name in Oracle, this search is case sensitive. So u have to configure accordingly.
    Regards,
    Prateek

  • How to add document name and document namespace to xml mail sender msg

    Hi,
    I have set up a sender mail CC that accepts messages already in XML format. However, the messages are missing the document name and document namespace. I am trying to use MessageTransformBean to add these to the message payload. However the examples I've found so far all talk about converting plain text coming in. When I used convertionTpe -> SimplePlain2XML it messed up the original content with unnecessary xml tags.
    Can someone please tell me how to insert the document name and namespace into the payload without converting the original xml content? Thanks in advance.

    Dont think there is a way.
    As the source is a XML, why dont you create the MessageType with the same name and namespace as the XML file in the email.
    Regards,
    Bhavesh

  • JDBC Sender Adapter - No Namespace found

    Hello
    I am currently using PI 7.1. The scenario is JDBC to ECC ABAP Client Proxy. When the JDBC Sender Adapter sends the data to the Integration Server, the root element does not contain the xmlns attribute. This root element is constructed from the Document Name of the JDBC Sender Adapter attribute.
    I am getting the following error:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
      <SAP:P1>com/sap/xi/tf/_MM_HIS_Material_Consumption_</SAP:P1>
      <SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
      <SAP:P3>on: Cannot create target element /ns0:MT_Material_</SAP:P3>
      <SAP:P4>Consumption_ECC/Material. Values missing in queue~</SAP:P4>
      <SAP:AdditionalText />
      <SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_HIS_Material_Consumption_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:MT_Material_Consumption_ECC/Material. Values missing in queue~</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    When I perform a test at RWB, the message gets posted successfully. Once posted, the payload of this message contains the xmlns attribute.
    Here is the root element from both the instances:
    From RWB:  <ns0:MT_Material_Consumption_JDBC xmlns:ns0="http://xxx.com/xxx/finance">
    From JDBC Adapter:  <ns0:MT_Material_Consumption_JDBC>
    Could you please let me know, what has to be done to obtain the xmlns in the sender payload?
    Thank you in advance.
    John Jeyaraj
    Edited by: John jeyaraj on Apr 7, 2011 8:22 AM

    Hi Hiren
    When I test the MM without the xmlns attribute, I get the following error:
    The prefix "ns0" for element "ns0:MT_Material_Consumption_JDBC" is not bound.
    When I add the xmlns attribute, the mapping is successful.
    Thanks
    John

  • JDBC sender -Login Failed

    Hi
    I am trying to connect to SQl server 2005 database ..Getting with login failed for user...
    JDBC connection paramteres in lieu with the SQL version
    com.microsoft.sqlserver.jdbc.SQLServerDriver
    jdbc:sqlserver://<ip>:1433;DatabaseName=XXXX
    1.I can see my driver 'sqljdbc.jar' in the com.sap.aii.af.jmsproviderlib in /ext folder .
    2.I can access the database contents using studio express with the same credentials ..
    3. Telnet is successful eliminating firewall/network issues .
    4.SQl and windows authentication set in database
    5.Document name and namespace given in sender JDBC
    6 tried to establish connection picking up top 1* record from the view
    Any more options to check for resolving this error ..
    Please advise
    Anusha

    Hi Anusha
    It looks like the drivers have not been installed. Ask your basis team to check and deploy the correct driver.
    Also, according to this wiki, it seems that the connection string is not correct.
    http://wiki.sdn.sap.com/wiki/display/VC/JDBCConnectionSetup
    It should be jdbc:sqlserver://<host_name>:<port>;database=<db_name> (database instead of DatabaseName)
    Regards,
    Giuseppe

  • JDBC Sender Adapter

    Hi everybody
    I have the following error in my JDBC to JDBC scenario; I  configured the JDBC sender adapter and receive the following message back. In the Configuration I set “Document Name” to MT_ScanningStatus:
      <?xml version="1.0" encoding="utf-8" ?>
    <MT_ScanningStatus>
    <row>
      <ScannerNb>1</ScannerNb>
      <Status>0</Status>
      </row>
    <row>
      <ScannerNb>2</ScannerNb>
      <Status>2</Status>
      </row>
    <row>
    <ScannerNb>3</ScannerNb>
      <Status>0</Status>
      </row>
    <row>
      <ScannerNb>4</ScannerNb>
      <Status>2</Status>
      </row>
      </MT_ScanningStatus>
    I defined the  corresponding datatype as follow:
    DT_ScanningStatus Complex Type
            row              Element 1...unbounded
              ScannerNb      Element 1
              STatus         Element 1
    In the following Mapping I tried to Map this structure to the Structure used to send an Update SQL Statement to the JDBC Receiver to update the same table.  A normal Test in the Mapping Tool runs fine but when I enter under source the above incoming Message from the JDBC Adapter I got the following error. I think the incoming message cannot be interpreted. Can someone support me? I read the documentation for the JDBC adapter and also a lot of weblogs and discussion threads. Maybe someone knows a weblog describing more detailed the sender adapter and how to handle the incoming Message!!
    Thanks in advance Oliver
    14:58:03 Start of test
    Compilation of MM_JDBC_to_JDBC_test successful
    Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
    com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
    at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:130)
    at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68)
    Root Cause:
    com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)(:main:, row=1, col=8) -> com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
    at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2009)
    at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2657)
    at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2713)
    at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:162)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:132)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:142)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245)
    at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:276)
    at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:338)
    at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
    at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
    at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:128)
    at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68)
    at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144)
    at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
    at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:128)
    at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68)
    Caused by: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
    at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2009)
    at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2657)
    at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2713)
    at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:162)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:132)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:142)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245)
    at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:276)
    at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:338)
    at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
    ... 3 more
    Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)

    Hi Oliver,
    >>>>source the above incoming Message from the JDBC Adapter I got the following error. I think the incoming message cannot be interpreted.
    do this:
    in the test tab try your mapping once more
    (the correct one)
    then save the source xml as file
    next compare this saved file with the one
    you get from the jdbc sender
    >>>>>Declaration not allowed here.(:main:, row:1, col:8)
    and compare the first lines in those two XML files
    are they the same?
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • JDBC Sender Adapter - Transaction & Parameterized Query?

    Dear Experts,
    I'm curious about the JDBC sender adapter in SAP PI.
    As I see from the document and have been searching in the Internet, The default procedure of the sender JDBC adapter is to first run a SELECT/Store Procedure query then update the records that have been read before.
    Configuring the Sender JDBC Adapter - Advanced Adapter Engine - SAP Library
    What I want to ask is:
    - What is the database transaction used for the SELECT and the UPDATE? I mean what if the SELECT is successful and the records have been sent to the IE, but the UPDATE failed. This way, the next polling run, the same records could be read again. Is it possible? Are the SELECT and UPDATE query atomic (if one fails the other fails too)?
    - Is it possible to have a parameterized query / stored procedure in sender JDBC adapter? Because seeing at the default procedure, there should be at least a field that will be used as a flag (for example the processed field needs to be updated to '1'). Something like:
              - SELECT * FROM table_a WHERE docno > $last_doc_no
                             $last_doc_no is a paramter or variable from PI
              - EXEC sp_do_something ( $param_a, $param_b )
                             $param_a, $param_b are parameters or variable in PI
    Thank you,
    Suwandi C.

    Hi Suwandi,
    all action to database are in one transaction and thats mean if one failed all failed.
    And it is possible to have parameterized storied procedure. You sould send something like
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:mt_proc xmlns:ns0="http://aaaa">
       <statementname>
          <stProc action="EXECUTE"/>
          <TABLE>PROCEDURE NAME</TABLE>
          <access>
             <param_in isInput="1" type="some_type">input param</param_in>
             <param_out isOutput="1" type="some_type"></param_out>
          </access>
       </statementname>
    </ns0:mt_proc>

  • JDBC Sender -Not selecting records

    Hi all
    I have set up a JDBC sender. The communication channel monitor shows that "Polling interval started" but It is not retrieving data from the JDBC table using a select statement.
    This is a sql select statement.
    SELECT * FROM table
    there is also a corresponding update statement.
    clearly ,XI is unable to pick up data from the table.
    if i change the name of the table , it does throw an SQL exception that the object doesnt exist. I have also checked with other tables and it is fetching data correctly. The table under problem does contain a row of data in ORacle side.
    Why doesnt XI select the records of the table?
    Any help will be highly appreciated
    thanks
    krishna

    Hi
    yes, the table does contain data
    and the sql stmnt is actually
    select * from table where flag= 'true' ( i also tried it without the where condition)
    here are the other parameters
    QOS : Exactly Once
    Poll interval: 6
    Document name: Resultset
    Update sql stmnt : UPDATE TBL SET FLAG = 'FALSE' WHERE FLAG = 'TRUE'
    hope this helps
    regards
    krishna

  • Query Print Layout - Generated PDF Document Name?

    Hi All,
    Query Print Layouts associated to my user queries work great for printing...but does anyone know if there is a way to set a more appropriate document file name when attaching an edited PDF report to an email? It seems to always automatically create a document name starting with 'Query Manager_-1_12' or something similar when attaching the report document directly to email.
    I do realize that I can save the file locally, choose any name I like, then attach to email... but this defeats the purpose of being able to send the query report directly to the email icon.
    If anyone knows how I can do this it would be much appreciated. There seems no option in the QPLD document properties.
    Best regards,
    John

    Hello,
    Yes, I have the same question. It could be great being able to choose the name of the document when creating a pdf. Even better if you could chose fields of the document for the name of the pdf, such as, name of customer, number of document, date, etc.
    Is there any way for doing this?
    Thanks in advance,
    Javier.
    Hi All,
    Query Print Layouts associated to my user queries work great for printing...but does anyone know if there is a way to set a more appropriate document file name when attaching an edited PDF report to an email? It seems to always automatically create a document name starting with 'Query Manager_-1_12' or something similar when attaching the report document directly to email.
    I do realize that I can save the file locally, choose any name I like, then attach to email... but this defeats the purpose of being able to send the query report directly to the email icon.
    If anyone knows how I can do this it would be much appreciated. There seems no option in the QPLD document properties.
    Best regards,
    John

  • "Empty document Found" error while sending a text file

    Below is the error I'm getting while I'm trying to send a txt file using a fiel adapter.
    Channel FILE_TLE_Sender_SalesOrder_CC: Converted complete file content to XML format.
    Channel FILE_TLE_Sender_SalesOrder_CC: Empty document found - proceed without sending message.
    File "/data/TLE/XS1/inbound/850/Test_SalesOrder_3064_12-15-10.txt" deleted after processing.
    On the Communication Channel this is what I have:
    Recordset Name: DOCUMENT_ROOT
    Recordset Structure: DOC_HEADER,1,PO_HEADER,1,TAX,,FREIGHT,,SPECIAL_SHIP,,DOCUMENT_NOTE,,SHIP_TO_ADDRESS,,PRODUCT,,LINE_SHIP,,LINE_ITEM_NOTE,,ASSOC_LINE,,ORDER_MEMO,,DOC_TRAILER,1
    Key Field Name: keyfield
    DOC_HEADER.fieldNames    Value: keyfield,Source_System,Source_SUB_System,Source_Doc_Type,Source_Doc_Gen_Date,Source_Doc_Gen_Time,Source_Company,Source_Division,Source_Party_ID,Source_Ship_Location,Source_Sell_Location,Event_Name,Application_Program_File,Application_Program_Name,Destination_System,Destination_SUB_System,Destination_DOC_Type,Destination_Company,Destination_Division,Destination_Party_ID,Destination_Ship_Location,Destination_Sell_Location,Interchange_Control_Number,Group_Control_Number,Document_Control_Number,Date_Translated,Time_Translated,Primary_Key
    DOC_HEADER.fieldFixedLengths  Value: 30,30,30,30,10,4,30,15,30,20,20,8,30,30,30,30,30,30,15,30,20,20,10,10,10,10,4,30
    DOC_HEADER.keyFieldValue        Value: DOC_HEADER
    DOC_HEADER.lastFieldsOptional       Value: YES
    DOC_HEADER.endSeparator           Value: 'nl'
    Then I have same pattern for PO_HEADER, TAX and so on....
    Can someone tell me why this error is happening?  I'm using the same exact parameters in another XI environment and there's no error there.

    > Channel FILE_TLE_Sender_SalesOrder_CC: Empty document found - proceed without sending message.
    > Can someone tell me why this error is happening? 
    Maybe your source file is empty?
    This is exact what the error message says.

  • Document name wot it is?

    Hi
    Create PO > confirmation.Here we able to see document name
    Description:
    Here we able to document name as blank ,wot the document name is??
    In R/3 we have document types ( mat and a/c), in my knowledge dont have document name.
    Please guide me
    Thanks
    Hareesha

    Hi Hareesha,
    In SRM confirmation is nothing but Goods Receipt. If you are talking about confirmation name its the name you can give at the time of making confirmation (GR) for a Purchase order. This is one of the search field in the find confirmations.
    That is the only significance for this confirmation name.
    Hope this makes you clear.Clarifications are welcome.
    Rgds,
    Teja

Maybe you are looking for