SAP /ACCGO/DFW_OE_TRIGGER Function Module for DFW : Function module to create a reversal ticket









/ACCGO/DFW_OE_TRIGGER is a standard /accgo/dfw oe trigger SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for DFW : Function module to create a reversal ticket 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 /accgo/dfw oe trigger FM, simply by entering the name /ACCGO/DFW_OE_TRIGGER into the relevant SAP transaction such as SE37 or SE38.

Function Group: /ACCGO/DFW_OE
Program Name: /ACCGO/SAPLDFW_OE
Main Program: /ACCGO/SAPLDFW_OE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function /ACCGO/DFW_OE_TRIGGER 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 '/ACCGO/DFW_OE_TRIGGER'"DFW : Function module to create a reversal ticket
  EXPORTING
   IS_DOCUMENT =  "Document Flow ALV Display Structure
   IV_LOG_HANDLE =  "Application Log: Log Handle
*  IV_UNIT_ID =  "ID of Unit in Background RFC
*  IV_EXT_ID =  "Application Log: External ID
   IV_REV_PROV_STL =  "Single-Character Indicator
*  IV_REV_GUID =  "Unique Identifier

 IMPORTING
   EV_TICKET_KEY =  "OIL-TSW: Ticket key

EXCEPTIONS
   RFC_EXCEPTION = 1    INVALID_DOCUMENT = 2
.



IMPORTING Parameters details for /ACCGO/DFW_OE_TRIGGER

IS_DOCUMENT - Document Flow ALV Display Structure

Data type: /ACCGO/CMN_S_DOC_FLOW_ALV
Optional: No
Call by Reference: No ( called with pass by value option)

IV_LOG_HANDLE - Application Log: Log Handle

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

IV_UNIT_ID - ID of Unit in Background RFC

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

IV_EXT_ID - Application Log: External ID

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

IV_REV_PROV_STL - Single-Character Indicator

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

IV_REV_GUID - Unique Identifier

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

EXPORTING Parameters details for /ACCGO/DFW_OE_TRIGGER

EV_TICKET_KEY - OIL-TSW: Ticket key

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

EXCEPTIONS details

RFC_EXCEPTION - DFW: Exception Class for Milestone workcenter

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

INVALID_DOCUMENT -

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

Copy and paste ABAP code example for /ACCGO/DFW_OE_TRIGGER 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_is_document  TYPE /ACCGO/CMN_S_DOC_FLOW_ALV, "   
lv_ev_ticket_key  TYPE OIJ_EL_TKT_KEY, "   
lv_rfc_exception  TYPE OIJ_EL_TKT_KEY, "   
lv_iv_log_handle  TYPE BALLOGHNDL, "   
lv_invalid_document  TYPE BALLOGHNDL, "   
lv_iv_unit_id  TYPE BGRFC_UNIT_ID, "   
lv_iv_ext_id  TYPE BALNREXT, "   
lv_iv_rev_prov_stl  TYPE XFELD, "   
lv_iv_rev_guid  TYPE /ACCGO/E_GUID. "   

  CALL FUNCTION '/ACCGO/DFW_OE_TRIGGER'  "DFW : Function module to create a reversal ticket
    EXPORTING
         IS_DOCUMENT = lv_is_document
         IV_LOG_HANDLE = lv_iv_log_handle
         IV_UNIT_ID = lv_iv_unit_id
         IV_EXT_ID = lv_iv_ext_id
         IV_REV_PROV_STL = lv_iv_rev_prov_stl
         IV_REV_GUID = lv_iv_rev_guid
    IMPORTING
         EV_TICKET_KEY = lv_ev_ticket_key
    EXCEPTIONS
        RFC_EXCEPTION = 1
        INVALID_DOCUMENT = 2
. " /ACCGO/DFW_OE_TRIGGER




ABAP code using 7.40 inline data declarations to call FM /ACCGO/DFW_OE_TRIGGER

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!