OBJECT_UNKNOWN exception occurs due to lack of permission. When the SAP system account is not assigned with appropriate role in SAP, OBJECT_UNKNOWN exception will be thrown.
Below are some of the possible causes for ABAP errors
- Authorization problems
- Incorrect or incomplete entries in the RFC destination (SM59)
- Network problems
- Error in the RFC program
Error:
EventName=RfcServerCompletedCallHasErrorResponse Level=Warning ProcessID=3648 ThreadID=4380 functionName=IDOC_INBOUND_ASYNCHRONOUS systemAttributes=[DEST=a_rfc OWN_HOST=xxx PARTNER_HOST=xxxx SYSTNR=01 SYSID=SBP CLIENT=128 USER=xxxxx LANGUAGE=E ISO_LANGUAGE=EN OWN_CODEPAGE=1100 PARTNER_CODEPAGE=1100 OWN_REL=722 PARTNER_REL=700 PARTNER_TYPE=3 KERNEL_REL=722 RFC_ROLE=C] sessionId=83917117 transactionId=AC10C86F04906297321A006B unitId= unitAttributes= serverDetails=0O+xxxxxx==server~11 Running [REPOSITORY_DESTINATION=xxxxxx==client SNC_MODE=0 NAME=0O+xxxxxxxx==server~11 GWHOST=abc.xyz.com GWSERV=3301 PROGRAM_ID=AZUREPRD] stateful=False inTransaction=True exception=SAP.Middleware.Connector.RfcAbapException: OBJECT_UNKNOWN
IDOC_INBOUND_ASYNCHRONOUS is a function module in SAP Basis application which corresponds to IDoc inbound processing via tRFC. The following RFCs are used to send and receive IDOCs; when sending IDOCs, the adapter/connector uses these RFCs, whereas when receiving IDOCS, the SAP system uses them.
- INBOUND_IDOC_PROCESS. This function module is used for SAP releases before 4.0.
- IDOC_INBOUND_ASYNCHRONOUS. This function module is used for SAP release 4.0 and later.
When receiving IDOCs, the SAP adapter supports different message formats, which can be specified as a value for the binding property, ReceiveIDocFormat exposed by the SAP adapter.
- If set to "Typed", the XML schema is strongly typed to the specific IDOC being received. (The schema for this message can be seen from the Receive operations. Note that the schema is different for different IDOCs). This yields an XML IDOC.
- If set to "String", the incoming IDOC data is returned as a String value. (The schema for this message can be seen from the ReceiveIdoc operation). This yields an XML message with the <idocData> tag.
- If set to "Rfc", the message schema matches the RFC (or tRFC) schema for the RFC operations IDOC_INBOUND_ASYNCHRONOUS or INBOUND_IDOC_PROCESS, depending on the incoming IDOC version. If you specify this binding property you should use the IDOC_INBOUND_ASYNCHRONOUS or INBOUND_IDOC_PROCESS RFC to receive the IDOC. In the first two options, the adapter internally uses this RFC. In this option, you explicitly use this RFC to receive an IDOC.
To be able to successfully perform a Receive operation, you must have relevant authorization in the SAP system.
Make sure that you set up your SAP server and user account to allow using RFC. For more information, which includes the supported user account types and the minimum required authorization for each action type (RFC, BAPI, IDOC), review the following SAP note: 460089 - Minimum authorization profiles for external RFC programs.
- For RFC actions, the user account additionally needs access to function modules RFC_GROUP_SEARCH and DD_LANGU_TO_ISOLA.
- For BAPI actions, the user account also needs access to the following function modules: BAPI_TRANSACTION_COMMIT, BAPI_TRANSACTION_ROLLBACK, RPY_BOR_TREE_INIT, SWO_QUERY_METHODS and SWO_QUERY_API_METHODS.
- For IDOC actions, the user account also needs access to the following function modules: IDOCTYPES_LIST_WITH_MESSAGES, IDOCTYPES_FOR_MESTYPE_READ, INBOUND_IDOCS_FOR_TID, OUTBOUND_IDOCS_FOR_TID, GET_STATUS_FROM_IDOCNR, and IDOC_RECORD_READ.
- For the Read Table action, the user account also needs access to either following function module: RFC BBP_RFC_READ_TABLE or RFC_READ_TABLE.
