SAP MR_STRING_DETERMINE Function Module for NOTRANSL: Ermittlung des Buchungsstrings und der BUZID

Search SAP Function Modules

MR_STRING_DETERMINE is a standard mr string determine 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: Ermittlung des Buchungsstrings und der BUZID 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 mr string determine FM, simply by entering the name MR_STRING_DETERMINE into the relevant SAP transaction such as SE37 or SE38.

Function Group: KONT
Program Name: SAPLKONT
Main Program: SAPLKONT
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MR_STRING_DETERMINE 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 'MR_STRING_DETERMINE'"NOTRANSL: Ermittlung des Buchungsstrings und der BUZID
  EXPORTING
   I_KNTTP =  "
   I_KOART =  "Account Type
   I_PSTYP =  "
   I_VGART =  "Transaction/Event Type
*  I_XEKBZ = ' ' "
*  I_KZBWS = ' ' "
*  I_ANLN1 =  "
*  I_TBTKZ =  "

 IMPORTING
   E_BUSTW =  "Posting String
   E_BUZID =  "

EXCEPTIONS
   NOT_FOUND_T163K = 1    NOT_FOUND_T169W = 2 

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLKONT_001 User Exit Before MR_CHECK_TOLERANCE
EXIT_SAPLKONT_002 Customer Exit: Change Tolerance Check - Conventional Invoice Verification
EXIT_SAPLKONT_011 Account Grouping for GR/IR Account Determination
EXIT_SAPLKONT_412 Brazil: User Exit to determination Acct Modif.for 3rd NF for F. Del.

IMPORTING Parameters details for MR_STRING_DETERMINE

I_KNTTP -

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

I_KOART - Account Type

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

I_PSTYP -

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

I_VGART - Transaction/Event Type

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

I_XEKBZ -

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

I_KZBWS -

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

I_ANLN1 -

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

I_TBTKZ -

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

EXPORTING Parameters details for MR_STRING_DETERMINE

E_BUSTW - Posting String

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

E_BUZID -

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

EXCEPTIONS details

NOT_FOUND_T163K -

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

NOT_FOUND_T169W -

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

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

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