Extending the IDoc to cXML scenario

Hi Experts,
I have a scenario IDoc to cXML for sending ORDERS05 .
We got a requirement to develope a scenario by extending the Order header and line extention segements to include extra fields)of the IDoc used in the above scenario , hence I am doing the following
-Imported the extended IDoc into the Integration repository.
-Mapped the extra fields included to the target message.
-reloaded the IDoc Metada using IDX2.
As i am doing this as part of the other project please suggest on the following
--Explain the sections to be included in the Technical design document for XI configuration.
--configurations that I need to work on.
please do suggest any other things i need to work on to take the right approach.
Thanks in advance.
MK

Hi,
Nothing more u require in XI development when ever u are dealing with the Extended IDOC's.
Normal procedure as Standard IDOC's only.
If u are not able to view the extended IDOC's in the Repository means then u have to think the solution.
This problem is not there for u. so go a head with the normal procedure by importing those IDOC's in IR and do mapping as usual
Regards
Seshagiri

Similar Messages

Idoc to cXML scenario

Hi,
I have a requirement (IDOC to cXML file), where i have to map PO IDOC to cXML file format. I understand from the cXML.org url that there are some DTD's freely available.
I guess the cXML file format is same as normal xml file with special format. please correct me if i am wrong.
can we use FILE adapter to convert the file to cXML file format. for example to abc.cxml.
can some one help me .
thanks.
azim

Hi Azias,
> Do we have to use third part adapter for this?
3rd party expression is usually used for Business Systems. Yes, you should create a 3rd party BS.
> can i use FTP adapter to create a file?
Yes
> what will be the extension of the file (i.e. abc.cxml)?
*.cxml
> Do we require secure connection in FTP adapter?
if you want to secure the connection / if you have sensible data
>
> If i want to post the cxml message to URL, then which adapter should is use? (HTTP/SOAP)?
http
Regards,
Udo

How to extend the Idoc

Hi,
We need to pass revision level field from MM PO to SRM SUS PO . We checked the message type for this is ORDERS. Now, in this message type there is no revision level field.
Our scenario is from MM the idoc goes to XI and from XI XML goes to SRM SUS.
So, now how do we proceed to acheive this.
Thanks in Advance,
Manu

Hi,
Kindly take ABAP help and insert this field for that message type and ensure both Receiver and sender are configured to this include XI team also.
Thanks
Suresh

Hi gurus how to extend the idoc

hi gurus how to extend the idoc

HI vasu,
in order to extend an IDOC goto WE30 tcode.
1) Give you basic IDOC type at the object name
2) select the Extension radio button
3) click on create button
4) it asks for 3 types of extension . so give the basic IDOC type over there
5) give description and click on continue button.
6) so at which segment level you want to add your segment, select that particular segment and click on create segment button and place your already created segment.
7) save and go back.
this the procedure of extending an IDOC.
Reward points if useful....
thanks,
satheesh.

How to extend the IDoc ORDERS05 and populate values?

Hi,
My requirement is to add few fields to the standard IDoc ORDERS05 and populate values to the newly added fields.
Please let me know how to extend the standard IDoc ORDERS05.
Regards,
Balaji. R

Hi balaji,
you can try to google for SAP R/3 IDoc Cookbook for EDI and Interfaces by Axel Angeli et.al.
Although Axel refers primarily to MATMAS Idoc the technique of extending IDOCs is explained very well.
Also very good is the search function here on SCN, I just found
[Some Experience on IDoc Enhancement|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=%28J2EE3414900%29ID0711317150DB10743789739220747754End?blog=/pub/wlg/8285]
Blogs and Wikis here are the best source for general questions like yours, usually of much more value than forum answers
Regards,
Clemens

Getting ROUTING_BACK_ERROR in the IDOC to JDBC Scenario

Hello,
I am working on the scenario IDOC to JDBC .Here from IDOC i have successfully inserted the entries in the table usig JDBC adapter.But it is giving the error in the acknowledgement as below
SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">ROUTING_BACK_ERROR</SAP:Code>
<SAP:P1>,XD1_WEB</SAP:P1>
<SAP:P2>,EDI,,</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error in back routing Error in communication channel</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Regards,

Hi Muthu,
Sorry for the late reply, i missed the auto mail.
Anyways is the problem solved?
Actually the acknowledgement is asked by sender SAP system which pots idoc so it donot matter if your target is JDBC,
You can see this weblog where the author sends an idoc to xi and xi posts a file and sends back an acknowledgement to SAP server.The technical reason which i think is that SAP system posts and sees the target as a Business system or business service or an intregation process so it donot matter if target is JDBC or file.
The weblog is:
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
I mean get a try to this, if this donot work we can troubleshoot or think of alternative solution.
Have a great day!!
Anirban.

How to suppress the Acknowledgement Error in IDOC to File scenario?

Hi -
I got the status in SXMB_MONI as 'Processed Successfully' for the IDOC to File scenario but the Acknoledgement status throws an error saying 'Acknowledgement not possible'.
I read one of the documents in the forums on how to suppress the acknowledgement using a table on R/3 side using IDXNOALE,
i tried that option but i still get the 'Acknowledgement not possible' error.
Is there any other way to suppress this error?
Thanks,
Tirumal

Hi Tirumal,
Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender. Acknowledgements are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments. The RNIF and CIDX adapters are exceptions to this rule, since they also support scenario-dependent application acknowledgments. Sender adapters of the Adapter Engine do not request any acknowledgments.
This means, JDBC adapter does only send system acks, however IDoc adapter is requesting application acks. Therefore as mentioned by the previous poster, you have to disable acks for this scenario using report IDX_NOALE.
Also go through these documents for any further help:
http://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how to handle acknowledgments for idoc.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
Regards,
abhy

ORDERS05 IDoc to cXML SOAP - SOAP failing (Ariba call)

I am performing the following scenario:
I am sending an ORDERS05 IDoc from R/3 4.6 to XI. XI then maps the IDoc into cXML. I am then attempting to send the cXML via the SOAP adapter to Ariba via HTTP.
Everything works except the adapter fails when trying to send to Ariba. Here is the audit log:
2005-07-06 17:05:39 Success The message was successfully received by the messaging system. Profile: XI URL: http://myserver:50000/MessagingSystem/receive/AFW/XI
2005-07-06 17:05:39 Success Using connection AFW. Trying to put the message into the receive queue.
2005-07-06 17:05:39 Success Message successfully put into the queue.
2005-07-06 17:05:39 Success The message was successfully retrieved from the receive queue.
2005-07-06 17:05:39 Success The message status set to DLNG.
2005-07-06 17:05:39 Success Delivering to channel: cXML2Ariba
2005-07-06 17:05:40 Success SOAP: request message entering the adapter
2005-07-06 17:06:01 Error SOAP: error occured: java.io.IOException: failed to get the input stream from socket: java.lang.NullPointerException
2005-07-06 17:06:01 Error Exception caught by adapter framework: failed to get the input stream from socket: java.lang.NullPointerException
2005-07-06 17:06:01 Error Delivery of the message to the application using connection AFW failed, due to: failed to get the input stream from socket: java.lang.NullPointerException.
2005-07-06 17:06:01 Success The asynchronous message was successfully scheduled to be delivered at Wed Jul 06 17:11:01 UTC 2005.
2005-07-06 17:06:01 Success The message status set to WAIT.
Does anyone know what the error message means?
Could it possibly be that I am taking an Async IDoc, and posting a synchronous SOAP to Ariba?
Thanks!

Mary -
Hi I was wondering how you were able to determine that your XI server did not have internet connectivity and what you were able to do? We have a similar scenario only we are trying to use SSL for the connection with certificate AND getting the following error :
2005-09-08 15:46:31 Success The message was successfully received by the messaging system. Profile: XI URL: http://XIServer024:50700/MessagingSystem/receive/AFW/XI
2005-09-08 15:46:31 Success Using connection AFW. Trying to put the message into the receive queue.
2005-09-08 15:46:31 Success Message successfully put into the queue.
2005-09-08 15:46:31 Success The message was successfully retrieved from the receive queue.
2005-09-08 15:46:32 Success The message status set to DLNG.
2005-09-08 15:46:32 Success Delivering to channel: PCARD_Activate_File_Receiver
2005-09-08 15:46:32 Success SOAP: request message entering the adapter
2005-09-08 15:46:32 Error SOAP: error occured: java.lang.NullPointerException
2005-09-08 15:46:32 Error Exception caught by adapter framework: null
2005-09-08 15:46:32 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.

Problem in idoc to file scenario

hi
while creating the idoc to file scenario i am facing few problems.
1) My design time objects are working fine. i have checked my message mapping, message interface etc.. (all design time objects are in active mode).
2) In ID, i have tested my configuration in test configuration, its working fine there as well (in ID i am using 2 business service one for sender, one for receiver)
3) i am using my ecc6 training server as my sender and using my XI server as receiver.
4) i am sending idoc from ecc6 and converting it to file in XI server and saving it in XI server itself(my receiver in this case).
my error:
i send my idoc from we19 transaction, and i see a error message stating
that 'RCVR_DETERMINATION.NO_RECEIVER_CASE_ASYNC'
my doubts.
1) while sending the idoc from ecc6, is it mandatory to give process code in partner profile ( that is, assign an outbound function module to push the created idoc to the mentioned destination).
2) also is it mandatory to have a partner profile on the receiver side( XI in this case) along with inbound process code.
3) in my receiver adapter ( file adatper in this case ) i have used NFS protocal. is it rite?
kindly help me with this issue.
regards
manoharan

>
manoj murugesan wrote:
> 1) while sending the idoc from ecc6, is it mandatory to give process code in partner profile ( that is, assign an outbound function module to push the created idoc to the mentioned destination).
>
> 2) also is it mandatory to have a partner profile on the receiver side( XI in this case) along with inbound process code.
>
> 3) in my receiver adapter ( file adatper in this case ) i have used NFS protocal. is it rite?
>
>
> kindly help me with this issue.
>
>
> regards
> manoharan
and to 1 & 2 ref. below,
Configuration steps required for posting idoc's(XI) -
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
ALE configuration for pushing idocs from SAP to XI -
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
3. NFS protocol is used to read/write files to the XI server itself. If you have to write to a local machine then use FTP

Issues in IDOC to File scenario using bussiness service

Hi Team
I found a blog which explains about the IDOC to FILE scenario by using bussinss services. I followed the steps and finally i am getting a error message while posting an idoc in we19 (ie IDOC 09878 was saved but cannot or should not be sent). The setting which have done on SAP side are as below
SAP SIDE CONFIGURATIONS
1. Created RFC destination : RFC_XI_SYSTEM
2. Created port : PORT_TEST
3. created logical system: IDOC2FILE
4. created partner profiles: IDOC2FILE
XI side configurations
1. Created RFC destination: RFC_SAP_SYSTEM
2. Created port : by using IDX1 t-code
DOUBT: here it is asking for PORT, CLIENT,Description and RFC destination, please let me know what values i need to put here, please find the SAP and XI system details below and suggest accordingly.
3. metadata: by using idx2.
DOUBT: here it is asking for IDOC type and source port, i can give the idoc name but i am not getting what i need to give to source prort field, please check and let me know, please find the SAP and XI system details below and suggest accordingly.
SAP system details
Client: 800
User name: sapuser
system id: DEV
system number:10
XI system details
Client:100
username:xisuper
system id: SXI
system numebr: 00
I request you to please check and help to successfullly completion of this scenario. I request you to please provide me the screen shots of the pre-requiste settings and suggest me the steps to debug the scenario.
Thanks in advance.
Raju

To complete your scenario successfully with better understanding of Idoc adapter
read http://help.sap.com/saphelp_nw70/helpdata/en/ab/bdb13b00ae793be10000000a11402f/content.htm.
for troubleshooting refer http://help.sap.com/saphelp_nw70/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm

Idoc to file scenario general query

Hi All,
I know about the basic settings needed for the Idoc to file scenario.
My query is related the idoc /ALE settings.
I have a scenatio wrking in my system where we have configured the port for B type partner and also the port as XML-HTTP
I can not see any DM(BD64) created for it basically.I want to know that in what scenarios the BD64 configuration is required.
Or it is the case that if we define the BD64 then we do not need to configure we20 and we21, it will be auto configured?
Please let me know the use cases for these different configurations if any.
Thanks in advance.
Regards,
Rahul Kulkarni

Hi Rahul,
BD64 uses mostly IDoc to IDoc scenarios because the IDoc consults the distribution model and determines whether any filter objects are specified for a receiver.
WE20 and WE21 (Partner Profile,Port Definition) we have to define in any scenarios where ECC included.
Thanks,
Seshu.

Seeburger IDOC-to-File scenario: Error using Classifier module

Hello,
I am running the following scenario: ORDERS.ORDERS05 IDOC -> XI -> X12 850 4010 File.
In the file receiver channel, I am using Seeburger's Classifier and BIC modules as follows:
localejbs/SeeClassifier        classifier
localejbs/CallBicXIRaBean      bic
CallSapAdapter                 0
classifier   attID             classifierAtt
classifier   destSourceMsg     MainDocument
classifier   showInAuditLog    true
bic          classifierAttID   classifierAtt
bic          destEncoding      UTF8
bic          destSourceMsg     MainDocument
bic          destTargetMsg     MainDocument
bic          mappingName       AUTO
bic          newLine           true
bic          srcEncoding       UTF8
After conversion in XI, the file fails to write to the folder because of this error:
Message processing failed. Cause: javax.resource.ResourceException: ---
Conversion of synchronous request from module chain ended with errors
---Error: [Error:ID=1010;LEVEL=1] BICMapping runMapping() The mapping:
See_XML_AnsiX12 you are trying to load cannot be found in the classpath!
Maybe you forgot to compile or to activate the mapping! DESCRIPTION:
BICMapping Error: The mapping [not specified] you are trying to load cannot
be found in the right path! Maybe you forgot to compile or to activate the
mapping!
When I set the mapping directly to See_X2E_AnsiX12_850_V4010 instead of using the Classifier module, the configuration works fine. But I want to design the receiver channel to be able to receive all types of EDI messages coming from XI.
I am only facing this problem for the IDOC-to-File scenario. Somehow the same configuration works for a File-to-IDOC scenario.
I talked to our Basis team and they said that the map See_XML_AnsiX12 does not exist in Seeburger's delivered content, although I believe that it should be. Has anyone encountered this problem before?
Any suggestions would be appreciated.
Thanks,
Arianne

Hi Yomesh,
Here is the payload.
<?xml version="1.0" encoding="UTF-8"?>
<LIST>
<S_ISA>
    <D_I01>00</D_I01>
    <D_I02/>
    <D_I03>00</D_I03>
    <D_I04/>
    <D_I05>ZZ</D_I05>
    <D_I06>CELORGS01</D_I06>
    <D_I05_2>ZZ</D_I05_2>
    <D_I07>AVX</D_I07>
    <D_I08>032008</D_I08>
    <D_I09>1718</D_I09>
    <D_I10>X</D_I10>
    <D_I11>00401</D_I11>
    <D_I12>000000008</D_I12>
    <D_I13>0</D_I13>
    <D_I14>T</D_I14>
    <D_I15>^</D_I15>
    <S_GS>
      <D_479>PO</D_479>
      <D_142>CLS01</D_142>
      <D_124>058895921</D_124>
      <D_373>20080320</D_373>
      <D_337>1718</D_337>
      <D_28>8</D_28>
      <D_455>X</D_455>
      <D_480>004010</D_480>
      <S_ST>
        <D_143>850</D_143>
        <D_329>800001</D_329>
        <S_BEG>
          <D_353>00</D_353>
          <D_92>SA</D_92>
          <D_324>4500005037</D_324>
          <D_373>20051110</D_373>
        </S_BEG>
        <S_CUR>
          <D_98>BY</D_98>
          <D_100>USD</D_100>
        </S_CUR>
        <S_FOB>
          <D_146>CC</D_146>
          <D_309>OR</D_309>
          <D_352>FREE CARRIER</D_352>
          <D_334>02</D_334>
          <D_335>FOB</D_335>
          <D_309_2>DE</D_309_2>
        </S_FOB>
        <S_ITD>
          <D_336>01</D_336>
          <D_333>3</D_333>
          <D_351>45</D_351>
        </S_ITD>
        <G_SN9>
          <S_N9>
            <D_128>L1</D_128>
            <D_369>GEN</D_369>
            <S_MSG>
              <D_933>TEST</D_933>
            </S_MSG>
            <S_MSG>
              <D_933>MESSAGE</D_933>
            </S_MSG>
          </S_N9>
        </G_SN9>
        <G_SN1>
          <S_N1>
            <D_98>BY</D_98>
            <D_66>92</D_66>
            <D_67>6310</D_67>
            <S_PER>
              <D_366>BD</D_366>
              <D_93>Graham Crawford</D_93>
            </S_PER>
          </S_N1>
        </G_SN1>
        <G_SN1>
          <S_N1>
            <D_98>BT</D_98>
            <D_66>92</D_66>
            <D_67>6310</D_67>
          </S_N1>
        </G_SN1>
        <G_SN1>
          <S_N1>
            <D_98>SE</D_98>
            <D_93>3M COMPANY</D_93>
            <D_66>92</D_66>
            <D_67>0000019591</D_67>
          </S_N1>
        </G_SN1>
        <G_SN1>
          <S_N1>
            <D_98>ST</D_98>
            <D_93>SAMPLE</D_93>
            <D_66>92</D_66>
            <D_67>6310</D_67>
          </S_N1>
        </G_SN1>
        <G_SPO1>
          <S_PO1>
            <D_350>00010</D_350>
            <D_330>10.000</D_330>
            <D_355>EA</D_355>
            <D_212>10</D_212>
            <D_639>PE</D_639>
            <D_235>BP</D_235>
            <D_234>230-1812-01JDS</D_234>
            <D_235_2>EC</D_235_2>
            <D_234_2>A00000000000002</D_234_2>
            <G_SPID>
              <S_PID>
                <D_349>F</D_349>
                <D_352>TIE WRAP,LOCKING,PANDUIT-PLASTIC PART C</D_352>
              </S_PID>
            </G_SPID>
            <S_REF>
              <D_128>CO</D_128>
              <D_127>4500005037-00010</D_127>
            </S_REF>
            <G_SSCH>
              <S_SCH>
                <D_380>10.000</D_380>
                <D_355>EA</D_355>
                <D_374>002</D_374>
                <D_373>20051208</D_373>
              </S_SCH>
            </G_SSCH>
          </S_PO1>
        </G_SPO1>
        <G_SCTT>
          <S_CTT>
            <D_354>1</D_354>
          </S_CTT>
        </G_SCTT>
        <S_SE>
          <D_96/>
          <D_329>800001</D_329>
        </S_SE>
      </S_ST>
      <S_GE>
        <D_97>1</D_97>
        <D_28>8</D_28>
      </S_GE>
    </S_GS>
    <S_IEA>
      <D_I16>1</D_I16>
      <D_I12>000000008</D_I12>
    </S_IEA>
</S_ISA>
</LIST>
Thanks,
Arianne

Sending Purchase Order to XI(IDOC to File Scenario)

Hi,
I have imported IDoc type ORDERS05 for Message Type ORDERS in XI 7.0 & i have created the IDOC to File Scenario for Purchase Order & activated all the objects.
Now in SAP ECC 6.0, i have created a purchase order using ME21N. No idocs created. Let me know the steps to send that PO. Which T.Code & what entries to follow...
Regards,
Balaji

Hi,
You would need to configure the data distribution model, activate change pointers, create your partner profiles and rfc connections.
Then do your XI Config.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
http://help.sap.com/bp_bpmv130/html/K16_EN_US.htm
http://help.sap.com/bp_bpmv130/Documentation/K16_Config_PurchaseOrderRequest_SellerPCK_EN_US.doc
Check these replies too...
Create PO in R/3 using XI
Regarding PO in XI
A basic guide..
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/73527b2c-0501-0010-5398-c4ac372c9692
Thanks,
Vijaya.

Want to create IDoc to Webservice Scenario

Hi All,
I wan to do Idoc to Web Service Scenario, I have already done Idoc to File Scenario and I have mapped the file of both end in ESR and I am done with Configuration in Integration Directory.
Now If I want to convert it to IDoc to Web Service Scenario, what all steps need to be done. and also want to know that How we can access and Send the files from Web Service to PI 7.1. As such web service is not available need to create the same also.
Can anyone provide How to guide on this scenario.
Regards,
Nitin Patil
Edited by: Nitin Patil on Dec 19, 2008 2:44 PM

Hey,
     as you have familiar with idoc to file, the idoc to webservice scenario is not different.
     You need to do the ALE settings on the R\3 side. import the Idoc in XI.
     Now for mapping purpose you need the source and the target structure.
     In case of webservice you need to import the WSLD (unlike the file in which you wold have created the data type and message type)
In order to import the WSLD, you need to do following things.
Ou require NWDS and the following settings needs to be done
Deployement of Web Services:-
Step 1)
     Goto Windows->Open Perspective->J2EE development.
Step 2)
     Goto File->new->Ejb module(give project name).
Step 3)
     Right Click on the <project name> eg. work_ejb select new->Ejb.
Step 4)
     Give an appropriate EJB name and default package (eg. com.xxx.yyy).
     Also select stateless Ejb.
     Click next then next and then next.
Step 5)
     Add method with an appropriate name.
     Mention the return type and also assign the required parameters.
     Logic is written in the EJB module bean.
Step 6)
     Right click on the <project name> and build.
     Creates .jar
Step 7)
     Goto File->new->Enterprise Application project(to create EAR)
Step 8)
     Give project name, assign EJB and build.
     Creates EAR.
Step 9)
     Right Click on the EJB.
     Goto new->Web services.
     Specify name of the web service.
     Specify EAR in the WEB service.
Step 10)
     Build EAR.
     Build Ejb.
Step 11)
     Goto Windows->Prefrences->SAP j2EE engine.
     Give the message server host name.
Step 12)
     Right Click on EAR and deploy.
Step 13)
     Goto-> http://<host name>:<port no.>/index.
Step 14)
     Choose the web service name,test it and download it(default WSDL).
Step 15)
     Import port(WSDL) in External definition of SAP PI.
After you import the wsld, you need to follow the same procedure as idoc to file.
regards,
Milan

Very strange error : IDOC to jdbc scenario

Hi
I am getting a very strange error when I see the log for the idoc to jdbc scenario that I am building.
The mapping test shows the header record and line item record properly in the mapping result.
insert, access nodes, fields with access nodes are all formed correctly.
However the communication channel log shows below error.
Could not execute statement for table/stored proc. "tblTestItem" (structure "Item") due to com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near ')'.
JDBC Message processing failed, due to Error processing request in sax parser: Error when executing statement for table/stored proc. 'tblTestItem' (structure 'Item'): com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near ')'.
The message status was set to WAIT.
The query that I see in the log is :INSERT INTO tblTestItem () VALUES ()
However mapping tool shows that all nodes are correctly formed.
Please assist.

Hi
I am still getting this issue even after the below steps so kind of stuck - actually very much stuck.
1. Restart of the dev environment
2. Tried with a new extension of the idoc
In the communication channel log for the JDBC receiver channel I still see
INSERT INTO tblItem () VALUES ()
The payload that I see in the message content tab is as follows
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_XXX_XXXX xmlns:ns0="http://capita.com/pi/XXXX">
- <Statement>
- <dbTableName action="INSERT">
<table>tblItem</table>
</dbTableName>
- <access>
<InvoiceNo>0000000009293467</InvoiceNo>
</access>
</Statement>
</ns0:MT_XXX_XXXX>
How do I debug the jdbc adapter to see how it converts the above xml output from the mapping step (note that this output is from an actual run and not test tool) to a sql query.
Very strange that the column names are present in the target payload but it is not reflecting in the query.
I have other tables being populated with the same jdbc receiver communication channel which makes this more and more confusing.
PLEASE ADVICE.

Extending the IDoc to cXML scenario

Similar Messages

Maybe you are looking for