SAP CHECK_OBJECT_REFERENCES Function Module for NOTRANSL: SFA: Checks fo rreferences from CUSTOMERCRM to CUSTOMER (OLTP)

Search SAP Function Modules

CHECK_OBJECT_REFERENCES is a standard check object references SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: SFA: Checks fo rreferences from CUSTOMERCRM to CUSTOMER (OLTP) processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for check object references FM, simply by entering the name CHECK_OBJECT_REFERENCES into the relevant SAP transaction such as SE37 or SE38.

Function Group: CRM3
Program Name: SAPLCRM3
Main Program: SAPLCRM3
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CHECK_OBJECT_REFERENCES pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'CHECK_OBJECT_REFERENCES'"NOTRANSL: SFA: Checks fo rreferences from CUSTOMERCRM to CUSTOMER (OLTP)
  EXPORTING
   I_SFA_KEY_CUST =  "
*  I_KUNNR =  "
*  I_SFA_KEY_CONT =  "
   I_CONTEXT =  "

 IMPORTING
   E_KUNNR =  "
   E_PARNR =  "
   E_MESSAGE =  "

CHANGING
   E_KEY_INFO =  "

EXCEPTIONS
   NO_CUSTOMER_EXISTING = 1    R3KEY_NOT_FOUND = 2    DOUBLE_ENTRY = 3 

.

IMPORTING Parameters details for CHECK_OBJECT_REFERENCES

I_SFA_KEY_CUST -

Data type: BAPICRMSFK-SFA_KEY
Optional: No
Call by Reference: No ( called with pass by value option)

I_KUNNR -

Data type: KNA1-KUNNR
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_SFA_KEY_CONT -

Data type: BAPICRMSFK-SFA_KEY
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_CONTEXT -

Data type: BAPICRMKEY-CHANGE_ID
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CHECK_OBJECT_REFERENCES

E_KUNNR -

Data type: KNA1-KUNNR
Optional: No
Call by Reference: No ( called with pass by value option)

E_PARNR -

Data type: KNVK-PARNR
Optional: No
Call by Reference: No ( called with pass by value option)

E_MESSAGE -

Data type: BAPICRMMSG
Optional: No
Call by Reference: No ( called with pass by value option)

CHANGING Parameters details for CHECK_OBJECT_REFERENCES

E_KEY_INFO -

Data type: BAPICRMKEY
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NO_CUSTOMER_EXISTING -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

R3KEY_NOT_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

DOUBLE_ENTRY -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for CHECK_OBJECT_REFERENCES Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM CHECK_OBJECT_REFERENCES

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects