SAP FDM_AR_SYNC_LDDB_SET_INVALID Function Module for

Search SAP Function Modules

FDM_AR_SYNC_LDDB_SET_INVALID is a standard fdm ar sync lddb set invalid 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 sync lddb set invalid FM, simply by entering the name FDM_AR_SYNC_LDDB_SET_INVALID into the relevant SAP transaction such as SE37 or SE38.

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

Function FDM_AR_SYNC_LDDB_SET_INVALID 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_SYNC_LDDB_SET_INVALID'"
  EXPORTING
   I_CASE_GUID =  "FSCM-DM: GUID (Internal Key of Dispute Case)
*  I_BUKRS =  "Company Code
*  I_BELNR =  "Accounting Document Number
*  I_GJAHR =  "Fiscal Year
*  I_BUZEI =  "Number of Line Item within Accounting Document

.

IMPORTING Parameters details for FDM_AR_SYNC_LDDB_SET_INVALID

I_CASE_GUID - FSCM-DM: GUID (Internal Key of Dispute Case)

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

I_BUKRS - Company Code

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

I_BELNR - Accounting Document Number

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

I_GJAHR - Fiscal Year

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

I_BUZEI - Number of Line Item within Accounting Document

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

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

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