SAP FMCA_DPSOBBPACC_BP_ACC_SELECT Function Module for
FMCA_DPSOBBPACC_BP_ACC_SELECT is a standard fmca dpsobbpacc bp acc select 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 dpsobbpacc bp acc select FM, simply by entering the name FMCA_DPSOBBPACC_BP_ACC_SELECT 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_DPSOBBPACC_BP_ACC_SELECT 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_DPSOBBPACC_BP_ACC_SELECT'".
EXPORTING
I_PARTNER = "Business Partner
I_PARTNERACC = "Contract Account Number
* I_VALDT = SY-DATLO "Validity Date
* I_BYPASS_BUFFER = ' ' "Read Directly from the Database?
* I_READ_OBSOLETE = ' ' "Read Obsolete Entries Also?
TABLES
T_DPSOB_BP_ACC = "Data on Contract Object, Partner and Contract Account
EXCEPTIONS
NOT_FOUND = 1 INVALID_INPUT = 2
IMPORTING Parameters details for FMCA_DPSOBBPACC_BP_ACC_SELECT
I_PARTNER - Business Partner
Data type: DPSOB_BP_ACC-PARTNEROptional: No
Call by Reference: No ( called with pass by value option)
I_PARTNERACC - Contract Account Number
Data type: DPSOB_BP_ACC-PARTNERACCOptional: No
Call by Reference: No ( called with pass by value option)
I_VALDT - Validity Date
Data type: SY-DATLODefault: SY-DATLO
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_BYPASS_BUFFER - Read Directly from the Database?
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_READ_OBSOLETE - Read Obsolete Entries Also?
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FMCA_DPSOBBPACC_BP_ACC_SELECT
T_DPSOB_BP_ACC - Data on Contract Object, Partner and Contract Account
Data type: DPSOB_BP_ACCOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND - 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
Copy and paste ABAP code example for FMCA_DPSOBBPACC_BP_ACC_SELECT 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_partner | TYPE DPSOB_BP_ACC-PARTNER, " | |||
| lv_not_found | TYPE DPSOB_BP_ACC, " | |||
| lt_t_dpsob_bp_acc | TYPE STANDARD TABLE OF DPSOB_BP_ACC, " | |||
| lv_i_partneracc | TYPE DPSOB_BP_ACC-PARTNERACC, " | |||
| lv_invalid_input | TYPE DPSOB_BP_ACC, " | |||
| lv_i_valdt | TYPE SY-DATLO, " SY-DATLO | |||
| lv_i_bypass_buffer | TYPE XFELD, " SPACE | |||
| lv_i_read_obsolete | TYPE XFELD. " SPACE |
|   CALL FUNCTION 'FMCA_DPSOBBPACC_BP_ACC_SELECT' " |
| EXPORTING | ||
| I_PARTNER | = lv_i_partner | |
| I_PARTNERACC | = lv_i_partneracc | |
| I_VALDT | = lv_i_valdt | |
| I_BYPASS_BUFFER | = lv_i_bypass_buffer | |
| I_READ_OBSOLETE | = lv_i_read_obsolete | |
| TABLES | ||
| T_DPSOB_BP_ACC | = lt_t_dpsob_bp_acc | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| INVALID_INPUT = 2 | ||
| . " FMCA_DPSOBBPACC_BP_ACC_SELECT | ||
ABAP code using 7.40 inline data declarations to call FM FMCA_DPSOBBPACC_BP_ACC_SELECT
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.| "SELECT single PARTNER FROM DPSOB_BP_ACC INTO @DATA(ld_i_partner). | ||||
| "SELECT single PARTNERACC FROM DPSOB_BP_ACC INTO @DATA(ld_i_partneracc). | ||||
| "SELECT single DATLO FROM SY INTO @DATA(ld_i_valdt). | ||||
| DATA(ld_i_valdt) | = SY-DATLO. | |||
| DATA(ld_i_bypass_buffer) | = ' '. | |||
| DATA(ld_i_read_obsolete) | = ' '. | |||
Search for further information about these or an SAP related objects