SAP COD_CONTRAC_REPL_RECIPIENT_GET Function Module for Find receiving logical system for the given partner

Search SAP Function Modules

COD_CONTRAC_REPL_RECIPIENT_GET is a standard cod contrac repl recipient get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Find receiving logical system for the given partner 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 cod contrac repl recipient get FM, simply by entering the name COD_CONTRAC_REPL_RECIPIENT_GET into the relevant SAP transaction such as SE37 or SE38.

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

Function COD_CONTRAC_REPL_RECIPIENT_GET 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 'COD_CONTRAC_REPL_RECIPIENT_GET'"Find receiving logical system for the given partner
  EXPORTING
   NAST =  "Message Status

 IMPORTING
   PARTNER_FUNCTION =  "Partner Function of Receiver
   PARTNER_NUMBER =  "Partner Number of Receiver

CHANGING
   PARTNER_TYPE =  "Partner Type of Receiver

EXCEPTIONS
   NO_RECIPIENT_FOUND = 1    OWN_SYSTEM_NOT_DEFINED = 2    OTHER_ERROR = 3    NO_MESSAGE_TYPE_FOUND = 4    MULTIPLE_MESSAGE_TYPES_FOUND = 5    MULTIPLE_RECIPIENTS_FOUND = 6 

.

IMPORTING Parameters details for COD_CONTRAC_REPL_RECIPIENT_GET

NAST - Message Status

Data type: NAST
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for COD_CONTRAC_REPL_RECIPIENT_GET

PARTNER_FUNCTION - Partner Function of Receiver

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

PARTNER_NUMBER - Partner Number of Receiver

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

CHANGING Parameters details for COD_CONTRAC_REPL_RECIPIENT_GET

PARTNER_TYPE - Partner Type of Receiver

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

EXCEPTIONS details

NO_RECIPIENT_FOUND - Bo recipient found

Data type:
Optional: No
Call by Reference: Yes

OWN_SYSTEM_NOT_DEFINED - Own logical system not defined

Data type:
Optional: No
Call by Reference: Yes

OTHER_ERROR - Other error

Data type:
Optional: No
Call by Reference: Yes

NO_MESSAGE_TYPE_FOUND - No message type found

Data type:
Optional: No
Call by Reference: Yes

MULTIPLE_MESSAGE_TYPES_FOUND - Multiple message types found

Data type:
Optional: No
Call by Reference: Yes

MULTIPLE_RECIPIENTS_FOUND - Multiple recipients found

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for COD_CONTRAC_REPL_RECIPIENT_GET 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 COD_CONTRAC_REPL_RECIPIENT_GET

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