ConnectivityProcessingHandler:LoadInboxMessage as projection in IFS Cloud

I’m answering my own question - there is no Projection for ConnectivityProcessingHandler:LoadInboxMessage . I had to develop PLSQL package and user PlSQL connector to get IN:MESSAGE data into Connectivity.

Hi NZCNESOSE,

Can you please explain a bit how you use PLSQL  connector to get into the connectivity table?

/Jeewan

In short, you create a Oracle package function with following parameter signature:
FUNCTION Load_Inbox(in_xml_ CLOB) RETURN CLOB

then, create IFS Connect address with type = PLSQL and enter name of the function and PLSQL parameter. Route your XML message to this address and you will get XML filen in  in_xml_ CLOB variable.

Thereafter use Oracle XMLTABLE functionality to “convert” XML into usable cursor that can be used to insert data into In_Message nd In_Message_Line.

Thank you.

/Jeewan

Hi All,

Could you please verify whether we need to develop the same approach (procedure to create lines) for 23r2 and later versions, or if IFS has introduced a new process to create connectivity inbox data?

Thank you,
Lochana

Hi ​@Lochana95 and ​@NZCNESOSE 
did you guys found anything related to ConnectivityProcessingHandler:LoadInboxMessage in IFS cloud. I need it to create instant invoices 

As far as I know, ConnectivityProcessingHandler:LoadInboxMessage is not available in IFS Cloud.
You will have to create own Oracle package to handle incoming data.
Se my previous comment.

Yes, I agree with ​@NZCNESOSE . We had to create our own Oracle package to handle the incoming data.

We developed similar method & used a routing rule/address to route the XML message to this method. 

 CURSOR cur_msg_header IS
      SELECT * 
      INTO   c_receiver_, c_sender_, c_class_id_ 
      FROM   (SELECT receiver, 
                     sender, 
                     class_id
              FROM   XMLTABLE('/IN_MESSAGE' 
                              PASSING XMLTYPE(in_xml_) 
                              COLUMNS receiver  VARCHAR2(255) PATH 'RECEIVER',
                                      sender    VARCHAR2(255) PATH 'SENDER',
                                      class_id  VARCHAR2(30)  PATH 'CLASS_ID'
                             )
             );