SAP FMCA_DPSOB_READ Function Module for Read Contract Object in DPSOB

Search SAP Function Modules

FMCA_DPSOB_READ is a standard fmca dpsob read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Contract Object in DPSOB 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 fmca dpsob read FM, simply by entering the name FMCA_DPSOB_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: 20-Jan-2004
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMCA_DPSOB_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_READ'"Read Contract Object in DPSOB
  EXPORTING
   I_PSOBKEY =  "ID Key for Contract Object
*  I_VALDT = SY-DATLO "Validity Date
*  I_BYPASS_BUFFER = ' ' "Read Directly from the Database?
*  I_READ_BDT_MEMORY = ' ' "If Necessary, Also Include BDT Current Memory in Search?

 IMPORTING
   E_DPSOB =  "Contract Object in IS-PS-CA

EXCEPTIONS
   NOT_FOUND = 1    INVALID_INPUT = 2 

.

IMPORTING Parameters details for FMCA_DPSOB_READ

I_PSOBKEY - ID Key for Contract Object

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

I_VALDT - Validity Date

Data type: SY-DATLO
Default: SY-DATLO
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_BYPASS_BUFFER - Read Directly from the Database?

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

I_READ_BDT_MEMORY - If Necessary, Also Include BDT Current Memory in Search?

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

EXPORTING Parameters details for FMCA_DPSOB_READ

E_DPSOB - Contract Object in IS-PS-CA

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

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_DPSOB_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.

ABAP code using 7.40 inline data declarations to call FM FMCA_DPSOB_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