SAP FDM_AR_SYNC_DET_ORIGIN_STATUS Function Module for









FDM_AR_SYNC_DET_ORIGIN_STATUS is a standard fdm ar sync det origin status 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 det origin status FM, simply by entering the name FDM_AR_SYNC_DET_ORIGIN_STATUS 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:



Function FDM_AR_SYNC_DET_ORIGIN_STATUS 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_DET_ORIGIN_STATUS'"
  EXPORTING
   I_CASE_GUID =  "FSCM-DM: GUID (Internal Key of Dispute Case)
*  I_BUZEI =  "Number of Line Item within Accounting Document
   I_CASE_TYPE =  "FSCM-DM: Case Type
   I_PROC_SEQNR =  "FSCM-DM: Sequential Number of Process
   I_CHANGETIME_CASE =  "Creation Event for Dispute Case
*  I_OBJECT_TYPE =  "FSCM-DM: GUID (Internal Key of Dispute Case)
*  I_OBJECT_KEY =  "Object Key
*  I_BUKRS =  "Company Code
*  I_BELNR =  "Assignment of Item Numbers: Material Doc. - Purchasing Doc.
*  I_GJAHR =  "Fiscal Year

 IMPORTING
   ET_ITEM_CHANGES =  "FSCM-DM: Table Type for Attribute Changes Synchronization
.



IMPORTING Parameters details for FDM_AR_SYNC_DET_ORIGIN_STATUS

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

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

I_BUZEI - Number of Line Item within Accounting Document

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

I_CASE_TYPE - FSCM-DM: Case Type

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

I_PROC_SEQNR - FSCM-DM: Sequential Number of Process

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

I_CHANGETIME_CASE - Creation Event for Dispute Case

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

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

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

I_OBJECT_KEY - Object Key

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

I_BUKRS - Company Code

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

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

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

I_GJAHR - Fiscal Year

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

EXPORTING Parameters details for FDM_AR_SYNC_DET_ORIGIN_STATUS

ET_ITEM_CHANGES - FSCM-DM: Table Type for Attribute Changes Synchronization

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

Copy and paste ABAP code example for FDM_AR_SYNC_DET_ORIGIN_STATUS 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_case_guid  TYPE BDM_CASE_GUID, "   
lv_et_item_changes  TYPE FDM_T_FIELDCHANGES, "   
lv_i_buzei  TYPE BUZEI, "   
lv_i_case_type  TYPE BDM_CASE_TYPE, "   
lv_i_proc_seqnr  TYPE BDM_PROC_SEQNR, "   
lv_i_changetime_case  TYPE FDM_TIMESTAMP, "   
lv_i_object_type  TYPE SWO_OBJTYP, "   
lv_i_object_key  TYPE SWO_TYPEID, "   
lv_i_bukrs  TYPE BUKRS, "   
lv_i_belnr  TYPE BELNR_D, "   
lv_i_gjahr  TYPE GJAHR. "   

  CALL FUNCTION 'FDM_AR_SYNC_DET_ORIGIN_STATUS'  "
    EXPORTING
         I_CASE_GUID = lv_i_case_guid
         I_BUZEI = lv_i_buzei
         I_CASE_TYPE = lv_i_case_type
         I_PROC_SEQNR = lv_i_proc_seqnr
         I_CHANGETIME_CASE = lv_i_changetime_case
         I_OBJECT_TYPE = lv_i_object_type
         I_OBJECT_KEY = lv_i_object_key
         I_BUKRS = lv_i_bukrs
         I_BELNR = lv_i_belnr
         I_GJAHR = lv_i_gjahr
    IMPORTING
         ET_ITEM_CHANGES = lv_et_item_changes
. " FDM_AR_SYNC_DET_ORIGIN_STATUS




ABAP code using 7.40 inline data declarations to call FM FDM_AR_SYNC_DET_ORIGIN_STATUS

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!