SAP /ACCGO/BR_CALL_CMGL_PUR_SCREEN Function Module for Call Commingled Purchase Screen









/ACCGO/BR_CALL_CMGL_PUR_SCREEN is a standard /accgo/br call cmgl pur screen SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Call Commingled Purchase Screen 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 /accgo/br call cmgl pur screen FM, simply by entering the name /ACCGO/BR_CALL_CMGL_PUR_SCREEN into the relevant SAP transaction such as SE37 or SE38.

Function Group: /ACCGO/BR_CMGL_APPL_PUR
Program Name: /ACCGO/SAPLBR_CMGL_APPL_PUR
Main Program: /ACCGO/SAPLBR_CMGL_APPL_PUR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function /ACCGO/BR_CALL_CMGL_PUR_SCREEN 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 '/ACCGO/BR_CALL_CMGL_PUR_SCREEN'"Call Commingled Purchase Screen
  EXPORTING
   IV_REF_TC =  "Reference Trading Contract Number
   IV_REF_IT =  "Reference Trading Contract: Item Number
   IV_PUR_QTY =  "Quantity
   IV_PUR_UOM =  "Purchase Unit of Measure
   IV_NF_CURR =  "Currency Key
   IV_VENDOR =  "Account Number of Vendor or Creditor
*  IV_VENDOR_DESC =  "Vendor Name
   IV_NATURAL_PERSON =  "Is Natural Person?

 IMPORTING
   EV_PUR_QTY =  "Quantity
   EV_PUR_UOM =  "Purchase Unit of Measure
   EV_UCOMM =  "Function code that PAI triggered
   ES_NFDATA =  "Brazil: Application Nota Fiscal Data
   EV_ONE_STEP =  "True = One step purchase; False = Two step purchase
.



IMPORTING Parameters details for /ACCGO/BR_CALL_CMGL_PUR_SCREEN

IV_REF_TC - Reference Trading Contract Number

Data type: /ACCGO/E_BR_REF_TC
Optional: No
Call by Reference: Yes

IV_REF_IT - Reference Trading Contract: Item Number

Data type: /ACCGO/E_BR_REF_TC_IT
Optional: No
Call by Reference: Yes

IV_PUR_QTY - Quantity

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

IV_PUR_UOM - Purchase Unit of Measure

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

IV_NF_CURR - Currency Key

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

IV_VENDOR - Account Number of Vendor or Creditor

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

IV_VENDOR_DESC - Vendor Name

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

IV_NATURAL_PERSON - Is Natural Person?

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

EXPORTING Parameters details for /ACCGO/BR_CALL_CMGL_PUR_SCREEN

EV_PUR_QTY - Quantity

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

EV_PUR_UOM - Purchase Unit of Measure

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

EV_UCOMM - Function code that PAI triggered

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

ES_NFDATA - Brazil: Application Nota Fiscal Data

Data type: /ACCGO/CMGL_S_BR_NF_DATA
Optional: No
Call by Reference: Yes

EV_ONE_STEP - True = One step purchase; False = Two step purchase

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

Copy and paste ABAP code example for /ACCGO/BR_CALL_CMGL_PUR_SCREEN 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_iv_ref_tc  TYPE /ACCGO/E_BR_REF_TC, "   
lv_ev_pur_qty  TYPE MENGE_D, "   
lv_iv_ref_it  TYPE /ACCGO/E_BR_REF_TC_IT, "   
lv_ev_pur_uom  TYPE MEINS, "   
lv_ev_ucomm  TYPE SYUCOMM, "   
lv_iv_pur_qty  TYPE MENGE_D, "   
lv_es_nfdata  TYPE /ACCGO/CMGL_S_BR_NF_DATA, "   
lv_iv_pur_uom  TYPE MEINS, "   
lv_iv_nf_curr  TYPE WAERS, "   
lv_ev_one_step  TYPE ABAP_BOOL, "   
lv_iv_vendor  TYPE LIFNR, "   
lv_iv_vendor_desc  TYPE NAME1_GP, "   
lv_iv_natural_person  TYPE ABAP_BOOL. "   

  CALL FUNCTION '/ACCGO/BR_CALL_CMGL_PUR_SCREEN'  "Call Commingled Purchase Screen
    EXPORTING
         IV_REF_TC = lv_iv_ref_tc
         IV_REF_IT = lv_iv_ref_it
         IV_PUR_QTY = lv_iv_pur_qty
         IV_PUR_UOM = lv_iv_pur_uom
         IV_NF_CURR = lv_iv_nf_curr
         IV_VENDOR = lv_iv_vendor
         IV_VENDOR_DESC = lv_iv_vendor_desc
         IV_NATURAL_PERSON = lv_iv_natural_person
    IMPORTING
         EV_PUR_QTY = lv_ev_pur_qty
         EV_PUR_UOM = lv_ev_pur_uom
         EV_UCOMM = lv_ev_ucomm
         ES_NFDATA = lv_es_nfdata
         EV_ONE_STEP = lv_ev_one_step
. " /ACCGO/BR_CALL_CMGL_PUR_SCREEN




ABAP code using 7.40 inline data declarations to call FM /ACCGO/BR_CALL_CMGL_PUR_SCREEN

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!