Create new mode for each receiver RFC call

[Former Member]

Hi,

               We are using PI 7.3 and have a JDBC to RFC interface. RFC is the standard RFC CLOI_CHANGES_UPL_31 which we are using for create\change\delete work orders.

The interface is successful in PI, but the RFC is giving a failure response with code 010 - 'Restart interface after commit'. Upon investigation, we found the following link which states :

http://www.saptechies.com/faq-cloichangesupl31-commit-control-commitflg-545860/

CLOI_CHANGES_UPL_31 can only be called up once within a mode with COMMITFLG = 'C'. Therefore it is necessary to create a new external mode for another call with COMMITFLG = 'C'

If CLOI_CHANGES_UPL_31 is called up via RFC by an external system, a new mode can be created by exiting the current mode (closing RFC connection) and creating the RFC connection afterwards again (set up connection).

The issue is that in the PI RFC receiver comm channel, I do not have any option of closing the RFC connection and recreating a new one for each call. Also, since this is not a BAPI, option 'Commit Handling for single BAPI call' is not working as the return type RETURN is not present.

My query is, can we somehow do this in PI, create a new connection mode for each RFC call?

Regards

[MichalKrawczyk]

Hi,

using RFC is a bad thing anyway due to lack of monitoring in SAP backend system

so maybe you can combine two things at one:

- create an ABAP proxy which will call this RFC inside itself - and it will work on connect forget basis (so the connection will be closed each time)

- you will have a nice logging for any errors in SXI_MONITOR in backend system

Regards,

Michal Krawczyk

[former_member184681]

Hi,

You can use "BAPI Advanced Mode" to enter another table (CLOI_MESSAGE_LOG_EXP or CLOI_MSG_OBJ_LOG_EXP?) to be used instead of RETURN. See more here: http://help.sap.com/saphelp_nwpi71/helpdata/en/c8/e80440a832e369e10000000a155106/content.htm

Hope this helps,
Greg