Hi @Abdelmajid 

What are you trying to achieve?

You can add the table to the custom metadata and preform <hierarchy_select>

<hierarchy_select>
  <primary_table>i_xml_to_m5</primary_table>
  <attrs>
    <attr>i_xml_to_m5.*</attr>
  </attrs>
  <from>
    <table>i_xml_to_m5</table>
  </from>
  <where />
</hierarchy_select>

Cheers!

Hi Shneor,

Thanks for your reply.

I am training on FSM Integration,

and in the FSM pdf training,it is told in an exercise 

and as i understand in step 1.a , we don’t insert mi_sequence..

The delivery process is a 2 step process.

1. insert the message into the middle table. The table, i_xml_to_m5, is provide with the integration framework.

     a. Insert into i_xml_to_m5 (mi_xml,status, mi_reference) values (‘XML message’,‘04’,’my_reference’)

here i’ve got the error..

     b. Retain or get the mi_sequence of the record just inserted.

For person testing, use sql Select mi_sequence, status, mi_xml, mi_reference from i_xml_to_m5 order by mi_sequence desc. Find mi_sequence for ‘my_reference’

2. Post a message that tells the integration framework to get and process the message. i_xml_to_m5 

<perform_process_itable>
<parameters>
<table_name>i_xml_to_m5</table_name>
<mi_sequence>123</mi_sequence>
</parameters>
</perform_process_itable>

if i force a mi_sequence in step 1a, i also have got error in step 2 telling i_xml is unknown..

Could you help please ?

Thanks,

Best Regards,

Abdelmajid

Hi @Abdelmajid 

I am getting the same results.

I am not sure if this should work differently. I cannot see that the column is defined as Identity in the DB, I can see it is defined as NOT NULL.

I suggest waiting for more comments.

Cheers!

Hi @Abdelmajid ,

In the above process, are you trying to achieve an inbound xml integration ? If that’s the scenario you can use the following xml to create a request using inbound integration.

<perform_inbound_integration>
  <parameters>
    <xml_import>
      <inbound>
        <request>
          <request_id> 1158</request_id>
          <place_id>197</place_id>
          <cust_prob_descr>TEST_5</cust_prob_descr>
        </request>
      </inbound>
    </xml_import>
  </parameters>
</perform_inbound_integration>

In the above xml, if we don’t have the request_id tag then the newly created request will be taking an auto incremented value for the request_id. If we use an already existing request_id then it will be updating the parameters mentioned in the xml. Make sure to include the required fields, if not the creation of request will throw an exception in the integration run log. 

Hope this answer helps.

Best Regards,
Atheeq

Hi Atheek, Shneor,

Thanks for your replies.

Shneor : In DB structure, the mi_sequence column doesn’t accept null values ..as it is the key of the table..

perhaps a problem in the training documentation or the documentation based on an older version of FSM...

Atheek : yes I know this command, i was trying to do an exercice from integration training documentation following the steps…insert record in i_xml_to_m5 table then this command was indicating to catch the xml from the middle table to create the transaction in FSM (details in previous reply).

Best Regards,

Abdelmajid

So we agree. Hence the insert fails.