SAP MM_ARRANG_READ_NEW_COND_UA Function Module for NOTRANSL: Liest neuen Konditionssatz nach









MM_ARRANG_READ_NEW_COND_UA is a standard mm arrang read new cond ua 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: Liest neuen Konditionssatz nach 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 mm arrang read new cond ua FM, simply by entering the name MM_ARRANG_READ_NEW_COND_UA into the relevant SAP transaction such as SE37 or SE38.

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



Function MM_ARRANG_READ_NEW_COND_UA 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 'MM_ARRANG_READ_NEW_COND_UA'"NOTRANSL: Liest neuen Konditionssatz nach
  EXPORTING
   I_VAKE =  "
   I_KONA =  "
   I_T6B1 =  "

 IMPORTING
   E_VAKE_PER =  "
   E_KONP_PER =  "
   E_KONH_PER =  "
   E_VAKE_MAIN =  "
   E_KONP_MAIN =  "
   E_KONH_MAIN =  "
   E_T685A =  "Conditions: Types: Additional Price Element Data

TABLES
   T_XKONP =  "
*  T_XKONH =  "
   T_XVAKE =  "

EXCEPTIONS
   CONDITION_NOT_FOUND = 1
.



IMPORTING Parameters details for MM_ARRANG_READ_NEW_COND_UA

I_VAKE -

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

I_KONA -

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

I_T6B1 -

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

EXPORTING Parameters details for MM_ARRANG_READ_NEW_COND_UA

E_VAKE_PER -

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

E_KONP_PER -

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

E_KONH_PER -

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

E_VAKE_MAIN -

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

E_KONP_MAIN -

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

E_KONH_MAIN -

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

E_T685A - Conditions: Types: Additional Price Element Data

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

TABLES Parameters details for MM_ARRANG_READ_NEW_COND_UA

T_XKONP -

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

T_XKONH -

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

T_XVAKE -

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

EXCEPTIONS details

CONDITION_NOT_FOUND -

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

Copy and paste ABAP code example for MM_ARRANG_READ_NEW_COND_UA 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_i_vake  TYPE VAKE, "   
lt_t_xkonp  TYPE STANDARD TABLE OF KONPDB, "   
lv_e_vake_per  TYPE VAKE, "   
lv_condition_not_found  TYPE VAKE, "   
lv_i_kona  TYPE KONA, "   
lt_t_xkonh  TYPE STANDARD TABLE OF KONHDB, "   
lv_e_konp_per  TYPE KONP, "   
lv_i_t6b1  TYPE T6B1, "   
lt_t_xvake  TYPE STANDARD TABLE OF VAKEVB, "   
lv_e_konh_per  TYPE KONH, "   
lv_e_vake_main  TYPE VAKE, "   
lv_e_konp_main  TYPE KONP, "   
lv_e_konh_main  TYPE KONH, "   
lv_e_t685a  TYPE T685A. "   

  CALL FUNCTION 'MM_ARRANG_READ_NEW_COND_UA'  "NOTRANSL: Liest neuen Konditionssatz nach
    EXPORTING
         I_VAKE = lv_i_vake
         I_KONA = lv_i_kona
         I_T6B1 = lv_i_t6b1
    IMPORTING
         E_VAKE_PER = lv_e_vake_per
         E_KONP_PER = lv_e_konp_per
         E_KONH_PER = lv_e_konh_per
         E_VAKE_MAIN = lv_e_vake_main
         E_KONP_MAIN = lv_e_konp_main
         E_KONH_MAIN = lv_e_konh_main
         E_T685A = lv_e_t685a
    TABLES
         T_XKONP = lt_t_xkonp
         T_XKONH = lt_t_xkonh
         T_XVAKE = lt_t_xvake
    EXCEPTIONS
        CONDITION_NOT_FOUND = 1
. " MM_ARRANG_READ_NEW_COND_UA




ABAP code using 7.40 inline data declarations to call FM MM_ARRANG_READ_NEW_COND_UA

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!