SAP FDM_AR_DOC_CHECK_DISPUTED Function Module for

Search SAP Function Modules

FDM_AR_DOC_CHECK_DISPUTED is a standard fdm ar doc check disputed 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 fdm ar doc check disputed FM, simply by entering the name FDM_AR_DOC_CHECK_DISPUTED into the relevant SAP transaction such as SE37 or SE38.

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

Function FDM_AR_DOC_CHECK_DISPUTED 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 'FDM_AR_DOC_CHECK_DISPUTED'"
  EXPORTING
   I_BUKRS =  "Company Code
   I_BELNR =  "Assignment of Item Numbers: Material Doc. - Purchasing Doc.
   I_GJAHR =  "Fiscal Year
   I_BUZEI =  "Number of Line Item within Accounting Document

 IMPORTING
   E_IS_DISPUTED =  "
   E_IS_CUST_DISPUTED =  "
   E_IS_SOLVED =  "
   E_IS_CONFIRMED =  "
   E_IS_ORIGINAL =  "
   E_IN_DISPUTE =  "
   ET_CASE_GUID_LOC =  "FSCM-DM Integration: List of Local Case GUIDs

.

IMPORTING Parameters details for FDM_AR_DOC_CHECK_DISPUTED

I_BUKRS - Company Code

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

I_BELNR - Assignment of Item Numbers: Material Doc. - Purchasing Doc.

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

I_GJAHR - Fiscal Year

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

I_BUZEI - Number of Line Item within Accounting Document

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

EXPORTING Parameters details for FDM_AR_DOC_CHECK_DISPUTED

E_IS_DISPUTED -

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

E_IS_CUST_DISPUTED -

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

E_IS_SOLVED -

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

E_IS_CONFIRMED -

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

E_IS_ORIGINAL -

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

E_IN_DISPUTE -

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

ET_CASE_GUID_LOC - FSCM-DM Integration: List of Local Case GUIDs

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

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

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