SAP FLT01_ORDER_COUNTER_GET_DB Function Module for NOTRANSL: Fahrzeuge: Auftragszählerstand lesen

Search SAP Function Modules

FLT01_ORDER_COUNTER_GET_DB is a standard flt01 order counter get db 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: Fahrzeuge: Auftragszählerstand lesen 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 flt01 order counter get db FM, simply by entering the name FLT01_ORDER_COUNTER_GET_DB into the relevant SAP transaction such as SE37 or SE38.

Function Group: FLT01
Program Name: SAPLFLT01
Main Program: SAPLFLT01
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FLT01_ORDER_COUNTER_GET_DB 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 'FLT01_ORDER_COUNTER_GET_DB'"NOTRANSL: Fahrzeuge: Auftragszählerstand lesen
  EXPORTING
*  I_CAUFVD =  "Dialog Structure for Order Headers and Item
*  I_OBJNR =  "Object Number
*  I_POINT =  "Measuring Point
*  I_LANGU = SY-LANGU "ABAP System Field: Language Key of Text Environment

 IMPORTING
   E_IMRG =  "Measurement Document
   E_RECNT =  "Counter Reading in Entry Unit
   E_MSEHI =  "Unit of Measure
   E_MSEH6 =  "External Unit of Measurement in Technical Format (6-Char.)

EXCEPTIONS
   NO_PRI_POINT = 1 

.

IMPORTING Parameters details for FLT01_ORDER_COUNTER_GET_DB

I_CAUFVD - Dialog Structure for Order Headers and Item

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

I_OBJNR - Object Number

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

I_POINT - Measuring Point

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

I_LANGU - ABAP System Field: Language Key of Text Environment

Data type: SY-LANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FLT01_ORDER_COUNTER_GET_DB

E_IMRG - Measurement Document

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

E_RECNT - Counter Reading in Entry Unit

Data type: RIFLTCOUN-RECNT
Optional: No
Call by Reference: Yes

E_MSEHI - Unit of Measure

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

E_MSEH6 - External Unit of Measurement in Technical Format (6-Char.)

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

EXCEPTIONS details

NO_PRI_POINT - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

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

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