SAP FDM_AR_DOC_DISPUTE_BUILD Function Module for

Search SAP Function Modules

FDM_AR_DOC_DISPUTE_BUILD is a standard fdm ar doc dispute build 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 dispute build FM, simply by entering the name FDM_AR_DOC_DISPUTE_BUILD 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_DISPUTE_BUILD 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_DISPUTE_BUILD'"
  EXPORTING
*  I_SINGLE = 'X' "
*  IT_NOTES =  "Notes
*  IT_FILECONTENT =  "FSCM-DM: File Content for Attachment to Dispute
*  IT_FILECLASS =  "FSCM-DM: Classifications for Attachments to Dispute
*  IT_OBJECTS =  "
*  I_CALLER = 0 "FSCM-DM: Calling Application
*  I_DIALOG = 'X' "
*  I_CHECK = 'X' "
*  I_SAVE = 'X' "
*  I_MESSAGE = 'X' "
*  I_ACTION = FDMCO_CREATE "
*  I_SUBJECT = '000' "Subject of Dispute Case
*  IT_ATTRIBUTES =  "Attributes
*  IS_NOTE_PROPERTIES =  "FSCM-DM: Properties for Notes for Dispute Case

TABLES
   T_BSEG_FDM =  "FSCM-DM: Structure for BSEG (with Fields from BKPF)

EXCEPTIONS
   CANCELLED = 1    ITEM_LOCKED = 2    ITEM_CLEARED = 3    ITEM_DISPUTED = 4    VENDOR_NOT_ACTIVE = 5    NO_INVOICE = 6    NO_ITEMS = 7    NO_PARTNER = 8    CDIS_NOT_ACTIVE = 9 

.

IMPORTING Parameters details for FDM_AR_DOC_DISPUTE_BUILD

I_SINGLE -

Data type: BOOLE_D
Default: 'X'
Optional: Yes
Call by Reference: Yes

IT_NOTES - Notes

Data type: TLINETAB
Optional: Yes
Call by Reference: Yes

IT_FILECONTENT - FSCM-DM: File Content for Attachment to Dispute

Data type: FDM_T_AR_FILECONTENT
Optional: Yes
Call by Reference: Yes

IT_FILECLASS - FSCM-DM: Classifications for Attachments to Dispute

Data type: BDM_T_FILECLASS
Optional: Yes
Call by Reference: Yes

IT_OBJECTS -

Data type: FDM_T_AR_OBJECTS
Optional: Yes
Call by Reference: Yes

I_CALLER - FSCM-DM: Calling Application

Data type: FDM_CALLER
Optional: Yes
Call by Reference: Yes

I_DIALOG -

Data type: BOOLE_D
Default: 'X'
Optional: Yes
Call by Reference: Yes

I_CHECK -

Data type: BOOLE_D
Default: 'X'
Optional: Yes
Call by Reference: Yes

I_SAVE -

Data type: BOOLE_D
Default: 'X'
Optional: Yes
Call by Reference: Yes

I_MESSAGE -

Data type: BOOLE_D
Default: 'X'
Optional: Yes
Call by Reference: Yes

I_ACTION -

Data type: FDM_ACTION
Default: FDMCO_CREATE
Optional: Yes
Call by Reference: Yes

I_SUBJECT - Subject of Dispute Case

Data type: FDM_CASE_SUBJECT
Default: '000'
Optional: Yes
Call by Reference: Yes

IT_ATTRIBUTES - Attributes

Data type: FDM_T_ATTRIBUTE
Optional: Yes
Call by Reference: Yes

IS_NOTE_PROPERTIES - FSCM-DM: Properties for Notes for Dispute Case

Data type: BDM_S_NOTE_PROPERTIES
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for FDM_AR_DOC_DISPUTE_BUILD

T_BSEG_FDM - FSCM-DM: Structure for BSEG (with Fields from BKPF)

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

EXCEPTIONS details

CANCELLED - Action was canceled by the user

Data type:
Optional: No
Call by Reference: Yes

ITEM_LOCKED -

Data type:
Optional: No
Call by Reference: Yes

ITEM_CLEARED -

Data type:
Optional: No
Call by Reference: Yes

ITEM_DISPUTED -

Data type:
Optional: No
Call by Reference: Yes

VENDOR_NOT_ACTIVE -

Data type:
Optional: No
Call by Reference: Yes

NO_INVOICE -

Data type:
Optional: No
Call by Reference: Yes

NO_ITEMS -

Data type:
Optional: No
Call by Reference: Yes

NO_PARTNER -

Data type:
Optional: No
Call by Reference: Yes

CDIS_NOT_ACTIVE - CDIS Function Not Active

Data type:
Optional: No
Call by Reference: Yes

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

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