SAP MM_ARRANG_BUSINESS_VOLUME_COMP Function Module for Maintenance of business volume comparison via call dialog









MM_ARRANG_BUSINESS_VOLUME_COMP is a standard mm arrang business volume comp SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Maintenance of business volume comparison via call dialog 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 business volume comp FM, simply by entering the name MM_ARRANG_BUSINESS_VOLUME_COMP into the relevant SAP transaction such as SE37 or SE38.

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



Function MM_ARRANG_BUSINESS_VOLUME_COMP 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_BUSINESS_VOLUME_COMP'"Maintenance of business volume comparison via call dialog
  EXPORTING
*  I_ARRANG_NUMBER =  "Arrangement number
*  I_NEW_TRANSACTION = 'X' "
*  I_DATALOSS = 'X' "
   I_AKTYP =  "Activity category
*  I_KONA =  "Arrangement header
*  I_T6B1T =  "Text on arrangement type
*  I_T6B1 =  "Arrangement type table
*  I_CALL_SOURCE =  "Source of calling program
*  I_COMMIT_MODUS =  "Type of update
*  I_WITH_POSTING =  "Call with updating
*  I_ABTYP_GENERAL =  "Arrangement category

 IMPORTING
   E_KONA =  "Arrangement after processing
   E_T6B1 =  "Arrangement type
   E_T6B1T =  "Arrangement type text
   E_SAVE_REQUESTED =  "Saving requested
   E_BUSI_VOL_CHANGE =  "Business volume data changed
   E_CREDIT_NOTE_CREATE =  "Settlement created

TABLES
*  ARRANG =  "Categor with all data on arrangement
*  ERROR_MESSAGES =  "Error message table

EXCEPTIONS
   NO_ARRANG_NUMBER = 1    INVALID_ABTYP_BOART = 10    INVALID_KOBOG = 11    BUSINESS_VOLUME_ERROR = 2    NO_AUTHORITY = 3    NO_AUTHORITY_EKORG = 4    INVALID_TCODE = 5    INVALID_KONA_NUMBER = 6    ENQUEUE_ON_RECORD = 7    BUSI_VOLUME_COMP_ERROR = 8    BUSI_VOLUME_NOT_POSIBLE = 9
.



IMPORTING Parameters details for MM_ARRANG_BUSINESS_VOLUME_COMP

I_ARRANG_NUMBER - Arrangement number

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

I_NEW_TRANSACTION -

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

I_DATALOSS -

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

I_AKTYP - Activity category

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

I_KONA - Arrangement header

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

I_T6B1T - Text on arrangement type

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

I_T6B1 - Arrangement type table

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

I_CALL_SOURCE - Source of calling program

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

I_COMMIT_MODUS - Type of update

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

I_WITH_POSTING - Call with updating

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

I_ABTYP_GENERAL - Arrangement category

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

EXPORTING Parameters details for MM_ARRANG_BUSINESS_VOLUME_COMP

E_KONA - Arrangement after processing

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

E_T6B1 - Arrangement type

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

E_T6B1T - Arrangement type text

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

E_SAVE_REQUESTED - Saving requested

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

E_BUSI_VOL_CHANGE - Business volume data changed

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

E_CREDIT_NOTE_CREATE - Settlement created

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

TABLES Parameters details for MM_ARRANG_BUSINESS_VOLUME_COMP

ARRANG - Categor with all data on arrangement

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

ERROR_MESSAGES - Error message table

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

EXCEPTIONS details

NO_ARRANG_NUMBER - No arrangement number passed on

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

INVALID_ABTYP_BOART - Wrong arrangement category for arrangement type

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

INVALID_KOBOG - Invalid condition type group

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

BUSINESS_VOLUME_ERROR - Error in business volume comparison

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

NO_AUTHORITY - No authorization

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

NO_AUTHORITY_EKORG - No authorization for purchasing organization processing

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

INVALID_TCODE - Invalid SAP transaction code

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

INVALID_KONA_NUMBER - Invalid arrangement number

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

ENQUEUE_ON_RECORD - Error during blocking

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

BUSI_VOLUME_COMP_ERROR - Error performing business volume comparison

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

BUSI_VOLUME_NOT_POSIBLE - Business volume comparison not possible

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

Copy and paste ABAP code example for MM_ARRANG_BUSINESS_VOLUME_COMP 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:
lt_arrang  TYPE STANDARD TABLE OF WBON_ARRANG_TAB, "   
lv_e_kona  TYPE KONA, "   
lv_i_arrang_number  TYPE KONA-KNUMA, "   
lv_no_arrang_number  TYPE KONA, "   
lv_i_new_transaction  TYPE C, "   'X'
lv_invalid_abtyp_boart  TYPE C, "   
lv_i_dataloss  TYPE C, "   'X'
lv_invalid_kobog  TYPE C, "   
lv_e_t6b1  TYPE T6B1, "   
lv_i_aktyp  TYPE T180-AKTYP, "   
lt_error_messages  TYPE STANDARD TABLE OF ARRANG_ERR, "   
lv_business_volume_error  TYPE ARRANG_ERR, "   
lv_i_kona  TYPE KONA, "   
lv_e_t6b1t  TYPE T6B1T, "   
lv_no_authority  TYPE T6B1T, "   
lv_i_t6b1t  TYPE T6B1T, "   
lv_e_save_requested  TYPE C, "   
lv_no_authority_ekorg  TYPE C, "   
lv_i_t6b1  TYPE T6B1, "   
lv_invalid_tcode  TYPE T6B1, "   
lv_e_busi_vol_change  TYPE C, "   
lv_i_call_source  TYPE C, "   
lv_invalid_kona_number  TYPE C, "   
lv_e_credit_note_create  TYPE C, "   
lv_i_commit_modus  TYPE C, "   
lv_enqueue_on_record  TYPE C, "   
lv_i_with_posting  TYPE C, "   
lv_busi_volume_comp_error  TYPE C, "   
lv_i_abtyp_general  TYPE C, "   
lv_busi_volume_not_posible  TYPE C. "   

  CALL FUNCTION 'MM_ARRANG_BUSINESS_VOLUME_COMP'  "Maintenance of business volume comparison via call dialog
    EXPORTING
         I_ARRANG_NUMBER = lv_i_arrang_number
         I_NEW_TRANSACTION = lv_i_new_transaction
         I_DATALOSS = lv_i_dataloss
         I_AKTYP = lv_i_aktyp
         I_KONA = lv_i_kona
         I_T6B1T = lv_i_t6b1t
         I_T6B1 = lv_i_t6b1
         I_CALL_SOURCE = lv_i_call_source
         I_COMMIT_MODUS = lv_i_commit_modus
         I_WITH_POSTING = lv_i_with_posting
         I_ABTYP_GENERAL = lv_i_abtyp_general
    IMPORTING
         E_KONA = lv_e_kona
         E_T6B1 = lv_e_t6b1
         E_T6B1T = lv_e_t6b1t
         E_SAVE_REQUESTED = lv_e_save_requested
         E_BUSI_VOL_CHANGE = lv_e_busi_vol_change
         E_CREDIT_NOTE_CREATE = lv_e_credit_note_create
    TABLES
         ARRANG = lt_arrang
         ERROR_MESSAGES = lt_error_messages
    EXCEPTIONS
        NO_ARRANG_NUMBER = 1
        INVALID_ABTYP_BOART = 10
        INVALID_KOBOG = 11
        BUSINESS_VOLUME_ERROR = 2
        NO_AUTHORITY = 3
        NO_AUTHORITY_EKORG = 4
        INVALID_TCODE = 5
        INVALID_KONA_NUMBER = 6
        ENQUEUE_ON_RECORD = 7
        BUSI_VOLUME_COMP_ERROR = 8
        BUSI_VOLUME_NOT_POSIBLE = 9
. " MM_ARRANG_BUSINESS_VOLUME_COMP




ABAP code using 7.40 inline data declarations to call FM MM_ARRANG_BUSINESS_VOLUME_COMP

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 KNUMA FROM KONA INTO @DATA(ld_i_arrang_number).
 
 
DATA(ld_i_new_transaction) = 'X'.
 
 
DATA(ld_i_dataloss) = 'X'.
 
 
 
"SELECT single AKTYP FROM T180 INTO @DATA(ld_i_aktyp).
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!