SAP OGW1_SD_BUMP_PROCESSING Function Module for Golden Gate SD Document processing for bump and/or version changes









OGW1_SD_BUMP_PROCESSING is a standard ogw1 sd bump processing SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Golden Gate SD Document processing for bump and/or version changes 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 ogw1 sd bump processing FM, simply by entering the name OGW1_SD_BUMP_PROCESSING into the relevant SAP transaction such as SE37 or SE38.

Function Group: OGW1
Program Name: SAPLOGW1
Main Program: SAPLOGW1
Appliation area: V
Release date: 05-Aug-1996
Mode(Normal, Remote etc): Normal Function Module
Update:



Function OGW1_SD_BUMP_PROCESSING 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 'OGW1_SD_BUMP_PROCESSING'"Golden Gate SD Document processing for bump and/or version changes
  EXPORTING
   IEQUI_NO =  "Internal equipment number
*  QUOTE_FLAG = '1' "Flag for open (bump) quote selection
*  ORDER_FLAG = '1' "Flag for recurrent billing order selection
*  CONTRACT_FLAG = '1' "Flag for contract (Service or BP) selection

 IMPORTING
   FOUND =  "Flag for item found

TABLES
   DOC_LIST =  "SD document list

EXCEPTIONS
   EQUI_NOT_FOUND = 1
.



IMPORTING Parameters details for OGW1_SD_BUMP_PROCESSING

IEQUI_NO - Internal equipment number

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

QUOTE_FLAG - Flag for open (bump) quote selection

Data type: C
Default: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)

ORDER_FLAG - Flag for recurrent billing order selection

Data type: C
Default: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)

CONTRACT_FLAG - Flag for contract (Service or BP) selection

Data type: C
Default: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for OGW1_SD_BUMP_PROCESSING

FOUND - Flag for item found

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

TABLES Parameters details for OGW1_SD_BUMP_PROCESSING

DOC_LIST - SD document list

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

EXCEPTIONS details

EQUI_NOT_FOUND - Equipment number incorrect

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

Copy and paste ABAP code example for OGW1_SD_BUMP_PROCESSING 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_found  TYPE C, "   
lt_doc_list  TYPE STANDARD TABLE OF OGW1VBAKP, "   
lv_iequi_no  TYPE EQUI-EQUNR, "   
lv_equi_not_found  TYPE EQUI, "   
lv_quote_flag  TYPE C, "   '1'
lv_order_flag  TYPE C, "   '1'
lv_contract_flag  TYPE C. "   '1'

  CALL FUNCTION 'OGW1_SD_BUMP_PROCESSING'  "Golden Gate SD Document processing for bump and/or version changes
    EXPORTING
         IEQUI_NO = lv_iequi_no
         QUOTE_FLAG = lv_quote_flag
         ORDER_FLAG = lv_order_flag
         CONTRACT_FLAG = lv_contract_flag
    IMPORTING
         FOUND = lv_found
    TABLES
         DOC_LIST = lt_doc_list
    EXCEPTIONS
        EQUI_NOT_FOUND = 1
. " OGW1_SD_BUMP_PROCESSING




ABAP code using 7.40 inline data declarations to call FM OGW1_SD_BUMP_PROCESSING

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.

 
 
"SELECT single EQUNR FROM EQUI INTO @DATA(ld_iequi_no).
 
 
DATA(ld_quote_flag) = '1'.
 
DATA(ld_order_flag) = '1'.
 
DATA(ld_contract_flag) = '1'.
 


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!