SAP FMCA_DPSOB_BP_ACC_RL_READ Function Module for









FMCA_DPSOB_BP_ACC_RL_READ is a standard fmca dpsob bp acc rl read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fmca dpsob bp acc rl read FM, simply by entering the name FMCA_DPSOB_BP_ACC_RL_READ into the relevant SAP transaction such as SE37 or SE38.

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



Function FMCA_DPSOB_BP_ACC_RL_READ 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 'FMCA_DPSOB_BP_ACC_RL_READ'"
  EXPORTING
   I_PSOBKEY =  "Identification Key for Contract Object
   I_PARTNER =  "Business Partner Number
*  I_PARTNERACC =  "Contract Account Number
   I_PARTNERACCTYP =  "Contract Account Category
*  I_INCOTYP =  "Inbound Correspondence Category
   I_INDIVIDUAL =  "Overwrite Customizing Settings

TABLES
   T_DPSOB_BP_ACC_RL =  "Rules for Generating Categorized Inbound Correspondence

EXCEPTIONS
   NOT_FOUND = 1    INVALID_INPUT = 2    PERIOD_CUSTOMIZING = 3
.



IMPORTING Parameters details for FMCA_DPSOB_BP_ACC_RL_READ

I_PSOBKEY - Identification Key for Contract Object

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

I_PARTNER - Business Partner Number

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

I_PARTNERACC - Contract Account Number

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

I_PARTNERACCTYP - Contract Account Category

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

I_INCOTYP - Inbound Correspondence Category

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

I_INDIVIDUAL - Overwrite Customizing Settings

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

TABLES Parameters details for FMCA_DPSOB_BP_ACC_RL_READ

T_DPSOB_BP_ACC_RL - Rules for Generating Categorized Inbound Correspondence

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

EXCEPTIONS details

NOT_FOUND - Table entry not found

Data type:
Optional: No
Call by Reference: Yes

INVALID_INPUT - Insufficient Entry Parameters for Database Access

Data type:
Optional: No
Call by Reference: Yes

PERIOD_CUSTOMIZING -

Data type:
Optional: No
Call by Reference: Yes

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

DATA:
lv_i_psobkey  TYPE PSOBKEY_PS, "   
lv_not_found  TYPE PSOBKEY_PS, "   
lt_t_dpsob_bp_acc_rl  TYPE STANDARD TABLE OF DPSOB_BP_ACC_RL, "   
lv_i_partner  TYPE BU_PARTNER, "   
lv_invalid_input  TYPE BU_PARTNER, "   
lv_i_partneracc  TYPE VKONT_KK, "   
lv_period_customizing  TYPE VKONT_KK, "   
lv_i_partneracctyp  TYPE VKTYP_KK, "   
lv_i_incotyp  TYPE INCO_TYP_PS, "   
lv_i_individual  TYPE INCORR_CUST_PS. "   

  CALL FUNCTION 'FMCA_DPSOB_BP_ACC_RL_READ'  "
    EXPORTING
         I_PSOBKEY = lv_i_psobkey
         I_PARTNER = lv_i_partner
         I_PARTNERACC = lv_i_partneracc
         I_PARTNERACCTYP = lv_i_partneracctyp
         I_INCOTYP = lv_i_incotyp
         I_INDIVIDUAL = lv_i_individual
    TABLES
         T_DPSOB_BP_ACC_RL = lt_t_dpsob_bp_acc_rl
    EXCEPTIONS
        NOT_FOUND = 1
        INVALID_INPUT = 2
        PERIOD_CUSTOMIZING = 3
. " FMCA_DPSOB_BP_ACC_RL_READ




ABAP code using 7.40 inline data declarations to call FM FMCA_DPSOB_BP_ACC_RL_READ

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!