Skip to Content

PI To Teradata JDBC adapter error

Hi Experts,

I am using PI 7.4. I am creating one MDM- PI- Teradata Scenario. The Teradata JDBC driver has already been deployed in the PI system. I have created the sender side message structure as below:

<MT_Sender_Out>

<Record>

<Object>

<MFG_CD/>

<MFG_NM/>

<CREAT_BY/>

<CREAT_DT/>

<UPDT_BY/>

<UPDT_DT/>

<ACTV_FLG/>

</Object>

</Record>

</ns0:MT_Sender_Out>

The Receiver side message structure is like:

<MT_Receiver_IN>

<MFG_Table>

<action>

<access>

<MFG_CD/>

<MFG_NM/>

<CREAT_BY/>

<CREAT_DT/>

<UPDT_BY/>

<UPDT_DT/>

<ACTV_FLG/>

</MFG_Tabe>

</MT_Receiver_IN>

The mapping is as below:

action --> mapped to constant value "INSERT"

MFG_CD--> one to one

MFG_NM --> one to one

CREAT_BY --> One to One

CREAT_DT --> one to one

UPDT_BY --> One to one

UPDT_DT --> One to onr

ACTV_FLG --> One to One

Note:- I have declared "access" as "attribute" in the receiver data type and it's occurrences is "optional".

I have configured the scenario as mentioned above. Now I am getting the below error:

No action attribute found in XML document (attribute action missing or wrong XML structure)

JDBC message processing failed; reason Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)

MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)

Exception caught by adapter framework: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure) using connection MDM_http://sap.com/xi/MDMAdapter failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)" tabIndex=0 ti="0" lsdata="{0:'Transmitting the message to endpoint using connection MDM_http://sap.com/xi/MDMAdapter failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing request in sax parser: No \'action\' attribute found in XML document (attribute "action" missing or wrong XML structure)',8:true}" ct="TV" aria-label="Transmitting the message to endpoint using connection MDM_http://sap.com/xi/MDMAdapter failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)" bMarkedAsFocussed="true" bResetTabIndex="true"Transmitting the message to endpoint <local> using connection MDM_http://sap.com/xi/MDMAdapter failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)

Please advise.

Thanks in advance.

Regards,

Moumita

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    Posted on Jul 10, 2015 at 08:27 AM

    Hi Moumita,

    You are not using a right structure. Please check the documentation: Defining XML Documents for Message Protocol XML SQL Format - Configuring the JDBC Adapter in the Integration Directory/P…

    Action must be an attribute of MFG_Table, not one field.

    Regards.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.