SAP CO_BT_AFVG_READ_WITH_LOGKEY Function Module for NOTRANSL: Lesen Vorgangssatz mit Auftragsnummer, Folgennumer und Vorgangsn









CO_BT_AFVG_READ_WITH_LOGKEY is a standard co bt afvg read with logkey SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Lesen Vorgangssatz mit Auftragsnummer, Folgennumer und Vorgangsn 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 co bt afvg read with logkey FM, simply by entering the name CO_BT_AFVG_READ_WITH_LOGKEY into the relevant SAP transaction such as SE37 or SE38.

Function Group: COBO
Program Name: SAPLCOBO
Main Program: SAPLCOBO
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CO_BT_AFVG_READ_WITH_LOGKEY 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 'CO_BT_AFVG_READ_WITH_LOGKEY'"NOTRANSL: Lesen Vorgangssatz mit Auftragsnummer, Folgennumer und Vorgangsn
EXPORTING
APLFL = "Sequence
AUFNR_ACT = "Order Number
* FLG_STAT = ' ' "
* FLG_WORK = ' ' "Indicator: read job data
* STTAG = '000000' "
* ALSO_SOP = ' ' "Selection for Entry in a Dynpro Field
VORNR = "Operation Number

IMPORTING
AFVGD_EXP = "Order: Dialog Table for Table AFVG (Order Operation)
INDEX = "
RCR01_EXP = "Job data
VBKZ_EXP = "Update indicator

EXCEPTIONS
NOT_FOUND = 1
.



IMPORTING Parameters details for CO_BT_AFVG_READ_WITH_LOGKEY

APLFL - Sequence

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

AUFNR_ACT - Order Number

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

FLG_STAT -

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

FLG_WORK - Indicator: read job data

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

STTAG -

Data type: RC271-STTAG
Default: '000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

ALSO_SOP - Selection for Entry in a Dynpro Field

Data type: SY-DATAR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

VORNR - Operation Number

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

EXPORTING Parameters details for CO_BT_AFVG_READ_WITH_LOGKEY

AFVGD_EXP - Order: Dialog Table for Table AFVG (Order Operation)

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

INDEX -

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

RCR01_EXP - Job data

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

VBKZ_EXP - Update indicator

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

EXCEPTIONS details

NOT_FOUND - no record found for the key

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

Copy and paste ABAP code example for CO_BT_AFVG_READ_WITH_LOGKEY 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_aplfl  TYPE AFVC-APLFL, "   
lv_afvgd_exp  TYPE AFVGD, "   
lv_not_found  TYPE AFVGD, "   
lv_index  TYPE SY-TABIX, "   
lv_aufnr_act  TYPE AUFK-AUFNR, "   
lv_flg_stat  TYPE AUFK, "   SPACE
lv_rcr01_exp  TYPE RCR01, "   
lv_flg_work  TYPE RCR01, "   SPACE
lv_vbkz_exp  TYPE AFVGB-VBKZ, "   
lv_sttag  TYPE RC271-STTAG, "   '000000'
lv_also_sop  TYPE SY-DATAR, "   SPACE
lv_vornr  TYPE AFVC-VORNR. "   

  CALL FUNCTION 'CO_BT_AFVG_READ_WITH_LOGKEY'  "NOTRANSL: Lesen Vorgangssatz mit Auftragsnummer, Folgennumer und Vorgangsn
    EXPORTING
         APLFL = lv_aplfl
         AUFNR_ACT = lv_aufnr_act
         FLG_STAT = lv_flg_stat
         FLG_WORK = lv_flg_work
         STTAG = lv_sttag
         ALSO_SOP = lv_also_sop
         VORNR = lv_vornr
    IMPORTING
         AFVGD_EXP = lv_afvgd_exp
         INDEX = lv_index
         RCR01_EXP = lv_rcr01_exp
         VBKZ_EXP = lv_vbkz_exp
    EXCEPTIONS
        NOT_FOUND = 1
. " CO_BT_AFVG_READ_WITH_LOGKEY




ABAP code using 7.40 inline data declarations to call FM CO_BT_AFVG_READ_WITH_LOGKEY

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 APLFL FROM AFVC INTO @DATA(ld_aplfl).
 
 
 
"SELECT single TABIX FROM SY INTO @DATA(ld_index).
 
"SELECT single AUFNR FROM AUFK INTO @DATA(ld_aufnr_act).
 
DATA(ld_flg_stat) = ' '.
 
 
DATA(ld_flg_work) = ' '.
 
"SELECT single VBKZ FROM AFVGB INTO @DATA(ld_vbkz_exp).
 
"SELECT single STTAG FROM RC271 INTO @DATA(ld_sttag).
DATA(ld_sttag) = '000000'.
 
"SELECT single DATAR FROM SY INTO @DATA(ld_also_sop).
DATA(ld_also_sop) = ' '.
 
"SELECT single VORNR FROM AFVC INTO @DATA(ld_vornr).
 


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!