SAP CRD_GET_AS_FOR_BP_WD_RFC Function Module for CRD: Reads Credential Assignments for BP (RFC)

Search SAP Function Modules

CRD_GET_AS_FOR_BP_WD_RFC is a standard crd get as for bp wd rfc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for CRD: Reads Credential Assignments for BP (RFC) 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 crd get as for bp wd rfc FM, simply by entering the name CRD_GET_AS_FOR_BP_WD_RFC into the relevant SAP transaction such as SE37 or SE38.

Function Group: CRD_WD_RFC_INTERFACE
Program Name: SAPLCRD_WD_RFC_INTERFACE
Main Program: SAPLCRD_WD_RFC_INTERFACE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function CRD_GET_AS_FOR_BP_WD_RFC 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 'CRD_GET_AS_FOR_BP_WD_RFC'"CRD: Reads Credential Assignments for BP (RFC)
  EXPORTING
   IV_PARTNER =  "
*  IV_CRD_TYPE =  "
*  IV_CRD_DESC =  "
*  IFLG_SAVE_LOG_TO_DB = '' "
*  IV_NO_MSG = '' "
*  IV_BUSI_BEGIN_DATE =  "Effective Start Date
*  IV_BUSI_END_DATE =  "Effective End Date

 IMPORTING
   ET_AS_UI =  "
   ET_MSG =  "

.

IMPORTING Parameters details for CRD_GET_AS_FOR_BP_WD_RFC

IV_PARTNER -

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

IV_CRD_TYPE -

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

IV_CRD_DESC -

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

IFLG_SAVE_LOG_TO_DB -

Data type: BOOLEAN_FLG
Default: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_NO_MSG -

Data type: BOOLEAN_FLG
Default: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_BUSI_BEGIN_DATE - Effective Start Date

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

IV_BUSI_END_DATE - Effective End Date

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

EXPORTING Parameters details for CRD_GET_AS_FOR_BP_WD_RFC

ET_AS_UI -

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

ET_MSG -

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

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

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