Total PO value per vendor

Hi,
We want to option that for certian vendors in a financial year we don't want issue PO if the total issued PO's order value crosses 1,00,000GBP.
Is it possible to control and how?
Thank you

Hi,
Chk PO/GR/Invoice amount in MC$4 for a vendor
BR,
Krishna

Similar Messages

Total Purchasing dollars per Vendor

I would like to get a query where only for the Vendors which have "ERS" -Evaluated Receipt Settlement type slected , I want to get the total dollars purchased from that vendor.
Which table gives the total Purchasing dollars per Vendor?

Here is a quick approach using Excel:
First extract vendors marked for ERS by using SE16 - table lookup for table LFM1. Add field XERSY (flagged for ERS) to the selection fields and use the AVL list as output option. Once you have the list, download it into Excel.
Now run transaction MC$4, which will access information structure S012 (Purchasing Information System) and run the report by selecting a range of periods. There are a bunch of key figures available, from the original PO $ to invoiced $. Once you have selected the key figure/key figures you need, download the report into Excel.
Now use the vblookup function in Excel, using the downloaded ERS vendors as reference to find the desired key figures from the second downloaded table.

How can I check stock value per valuation class at a certain period

Hi,
I have done this several times but with material ledger, but if I don't have material ledger available, how can I check the total stock value per valuation class for example at a certain period, lets say december 2012?
I have check menu reports, and also the historical tables, but is there any standard to use?
Thank you,

HI,
Please check transaction
S_P00_07000140
S_P00_07000139

Total order value (net) per PO with ME2N (Purchase order List display)

Hello,
with ME2N I can see the order value (net) of a PO per item line. Is it also possible to see the the total order value for all item lines in a PO?
Thanks for coming back to me!
Sofia

hi in standard reports that is not possible
But you can opt for filter in PO no. feild and go for an specific PO and press enter it will show all the line item of that PO then you can apply the Total of all Po line items in net price feild
Or even while running the report you can go for specific PO no and then execute the report.
Hope this helps
Else need to devlop an Z report with help of ABAPER
Try with the table EKPO and feild RLWRT
He can solve your purpose
Regards
Sujoy
Edited by: SUJOY on Sep 22, 2008 2:39 PM

Vendor Down Payment should not exceed Total PO Value

Dear All,
We want to restric the Vendor Down payment to total PO value and system must not allow to post the Down payment more that Total PO value.
Eg.
Material value - 1000
Tax 100
Other charges 150
Total PO Value - 1250/-
Now when we make down payment to the above vendor against the PO,the system must not allow us to make down payment more then 1250/-.
Do suggest.
Regards,

Hi,
You need to write validation rule & user exit for checking PO amount with down payment.
Whenever you post a down payment with reference to PO, in PO header, there is a status tab where you can check the status of PO i.e down pymt made, GR done etc., so write a user exit on that basis.
Regards
Anuj

Values in "vendor batch" in the Goods-in-order and Goods-in-plan lists are

Vendor batch No. : Transaction ZJPMPU322
(Background)
There are "vendor batch" and "batch" fields in Goods-in-order and Goods-in-plan lists (transaction ZJPMPU322). Values for these fields are retrieved from inbound delivery document (transaction VL33N). After core 7.0 upgrade, "vendor batch" is not copied from "batch" in inbound delivery document any more so that nothing appears in the vendor batch field in the lists.
(Change request)
Values in "vendor batch" in the Goods-in-order and Goods-in-plan lists are retrieved from "batch" in inbound delivery document ONLY IF "vendor batch" is blank in the inbound delivery document.
(Current design)
Batch is retrieved from LIPS-CHARG
Vendor batch is retrieved from LIPS-LICHN
(If there is no record in LIPS, blank will be printed out for both fields)
(After change)
Batch is retrieved from LIPS-CHARG
Vendor batch is retrieved from LIPS-LICHN only if LIPS-LICHN is not blank.
If LIPS-LICHN is blank, vendor batch is retrieved from LIPS-CHARG.
(If there is no record in LIPS, blank will be printed out for both fields. If both LIPS-CHARG and LIPS-LICHN are blank, blank will be printed out for both fields),
Following is the program:
REPORT zjpmrpu322 MESSAGE-ID zjpm001
              NO STANDARD PAGE HEADING
                        LINE-COUNT 50
                        LINE-SIZE 255.
*&   Development ID: PU_DD_322_LJP                                     *
*&   Report        : ZJPMRPU322                                        *
*&   The Purpose of this program is to print the Goods-in-order list *
*&   and the Goods in plan list for raw materials, materials purchase *
*&   etc at the Sasayama plant, Japan.                                 *
*&   Change Log:                                                       *
*&   Init    Who              Date        Text                         *
*&   PV      P V R S Varma    07-May-2003 Initial Version             *
*&   DU      D.Usui           2004/02/26   CR No. 1432                 *
*&   DU      D.Usui           2004/03/08   CR No. 1447                 *
*&   DU      D.Usui           2004/05/06   CR No. 1591                 *
                        Constants
CONSTANTS:
c_werks   LIKE ekpo-werks VALUE 'JP01',    "Plant code - Sasayama plant
c_id      LIKE thead-tdid VALUE 'F02',     "Text ID for Info record
c_object LIKE thead-tdobject VALUE 'EKPO',"Object of text for info rec
*c_zzjp_r1 LIKE marc-zzjp_re1 VALUE 'GMP', "Goods in plan- Domestic
*c_zzjp_r2 LIKE marc-zzjp_re1 VALUE 'GMPI', "Import sales order document
c_plus    TYPE c VALUE '',                "Holding '' sign
c_spras   LIKE makt-spras VALUE 'J',       "Language key Japan
*c_device(7)    type c value 'PRINTER',    "Device type
c_form(16)     TYPE c VALUE 'ZJPMPU305', "Form name
c_ele_gmp(4)   TYPE c VALUE 'GMP',        "GMP Text element
c_ele_gmpi(4) TYPE c VALUE 'GMPI',       "GMPI Text element
add begin CR1432
c_ele_bgmp(4) TYPE c VALUE 'BGMP',       "BGMP
c_ele_bgmpi(5) TYPE c VALUE 'BGMPI',      "BGMPI
add end CR1432
c_function(3) TYPE c VALUE 'SET',        "Function
c_type(4)      TYPE c VALUE 'BODY',       "Window area in main window
c_win_head(7) TYPE c VALUE 'HEADING',    "Heading window
c_win_shead(7) TYPE c VALUE 'SUBHEAD',    "sub heading window
c_win_fot1(7) TYPE c VALUE 'FOOTER1',    "Footer 1 window
c_win_main(4) TYPE c VALUE 'MAIN',       "Main window
c_comd(8)      TYPE c VALUE 'NEW-PAGE',   "New-page command
c_zar TYPE ekko-bsart VALUE 'ZAR',
c_x            TYPE c VALUE 'X',          "Indicator for print options
c_f            TYPE c VALUE 'F',          "Indicator for Purchase Order
add begin CR1591
Deletion indicator in purchasing document
c_loekz(1)     TYPE c VALUE 'L',
For ranges tables
c_sign_i(1)    TYPE c VALUE 'I',          "Sign(include)
c_op_eq(2)     TYPE c VALUE 'EQ',         "Option(=)
Confirmation category
c_ebtyp_ab(2) TYPE c VALUE 'AB',         "Order acknowledgment
add end CR1591
c_la(2)        TYPE c VALUE 'LA'.         "Indicator for Inbound deliver
                      Database Tables
                    Vaiables / Internal tables                       *
Internal table to store PO information
Not used after CR1591
DATA: BEGIN OF t_purc OCCURS 0,
         ebeln LIKE eket-ebeln, "Purchasing Document Number
         ebelp LIKE eket-ebelp, "Item Number of Purchasing Document
         eindt LIKE eket-eindt, "Item delivery date
         menge LIKE eket-menge, "Scheduled quantity
         charg LIKE eket-charg, "Batch number
         matnr LIKE ekpo-matnr, "Material code
         werks LIKE ekpo-werks, "Plant
         meins LIKE ekpo-meins, "Unit of measure
         lifnr LIKE ekko-lifnr, "Vendor number
      END OF t_purc.
Internal table to store material description.
DATA: BEGIN OF t_makt OCCURS 0,
        matnr LIKE makt-matnr, "Material code
        maktx LIKE makt-maktx, "Material description
      END OF t_makt.
Internal table for storage of final EKET data
DATA: BEGIN OF t_eket OCCURS 0,
         ebeln LIKE eket-ebeln, "Purchasing Document Number
         ebelp LIKE eket-ebelp, "Item Number of Purchasing Document
         ebelp_ex(6) TYPE n,    "Extended ebelp with length 6
         eindt LIKE eket-eindt, "Item delivery date
         menge LIKE eket-menge, "Scheduled quantity
         dabmg LIKE ekes-dabmg, " Delivered Quantity
         charg LIKE eket-charg, "Batch number
         matnr LIKE ekpo-matnr, "Material code
         werks LIKE ekpo-werks, "Plant
         maktx LIKE makt-maktx, "Material Description-- jp check
         etens LIKE ekes-etens, "Sequence Number
         meins LIKE ekpo-meins, "Unit of measure
         lifnr LIKE ekko-lifnr, "Vendor number
         vbeln LIKE ekes-vbeln,
         vbelp LIKE ekes-vbelp,
         vpnam(40) TYPE c,      "Vendor product name
      END OF t_eket.
Internal table for extraction of data from EKES
Not used after CR1591
DATA: BEGIN OF t_ekes OCCURS 0,
         ebeln LIKE ekes-ebeln, "Purchasing Document Number
         ebelp LIKE ekes-ebelp, "Item Number of Purchasing Document
         etens LIKE ekes-etens, "Sequence No
         eindt LIKE ekes-eindt, "Item delivery date
         menge LIKE ekes-menge, "Scheduled Quantity
         dabmg LIKE ekes-dabmg, " delivered quantity
         vbeln LIKE ekes-vbeln,
         vbelp LIKE ekes-vbelp,
         mark TYPE c,
      END OF t_ekes.
Internal table for extraction of data from EKES
Not used after CR1591
DATA: BEGIN OF t_ekes_temp OCCURS 0,
         ebeln LIKE ekes-ebeln, "Purchasing Document Number
         ebelp LIKE ekes-ebelp, "Item Number of Purchasing Document
         etens LIKE ekes-etens, "Sequence No
         eindt LIKE ekes-eindt, "Item delivery date
         menge LIKE ekes-menge, "Scheduled Quantity
      END OF t_ekes_temp.
Internal table for storing data from MLGN table.
DATA: BEGIN OF t_mlgn OCCURS 0,
         matnr LIKE mlgn-matnr, "material code
         lhmg1 LIKE mlgn-lhmg1, "Standard pallet size
         lhme1 LIKE mlgn-lhme1, "Unit of measure
         lety1 LIKE mlgn-lety1, "tower
         ltkze LIKE mlgn-ltkze, "Storage location
      END OF t_mlgn.
Internal table for storing data from MARM table.
DATA: BEGIN OF t_marm OCCURS 0,
         matnr LIKE marm-matnr, "material code
         umrez LIKE marc-zzjp_cas_size, "Std package unit
         meins LIKE ekpo-meins, "alternate unit
      END OF t_marm.
Internal table for storing data from MARC table.
DATA: BEGIN OF t_marc OCCURS 0,
         matnr LIKE marc-matnr,               "Material code
         zzjp_nyu_sop LIKE marc-zzjp_nyu_sop, "Product Std number
         zzjp_dos_frm LIKE marc-zzjp_dos_frm, "Dosage form
         zzjp_aprn     LIKE marc-zzjp_aprn,   "Apperance
         zzjp_re1     LIKE marc-zzjp_re1,     "Heading
      END OF t_marc.
Internal table for storing data from lfa1 table.
DATA: BEGIN OF t_lfa1 OCCURS 0,
         lifnr LIKE lfa1-lifnr, "Vendor code
         name1 LIKE lfa1-name1, "Vendor name
      END OF t_lfa1.
Internal table for Storing data from LIPS table.
DATA: BEGIN OF t_lips OCCURS 0,
         vbeln LIKE lips-vbeln, "Delivery document no
         posnr LIKE lips-posnr, "Item number for Delivery document
         charg LIKE lips-charg, "Batch number
         lichn LIKE lips-lichn, "Vendor Batch number
      END OF t_lips.
Internal table for storing the final display data.
DATA: BEGIN OF t_display OCCURS 0,
        g_checkbox type c,      "check box for selection of records
         ebeln LIKE ekes-ebeln,      "Purchasing Document Number
         ebelp LIKE ekes-ebelp,      "Item Number of Purchasing Document
         etens LIKE ekes-etens,      "Sequence No
         eindt LIKE eket-eindt,      "Item delivery date
         menge LIKE eket-menge,      "Scheduled Quantity
         vpnam(40) TYPE c,          "Vendor product name
         lifnr LIKE ekko-lifnr,      "Vendor code
         name1 LIKE lfa1-name1,      "Vendor name
         meins LIKE ekpo-meins,      "Unit of measure
         matnr LIKE ekpo-matnr,      "Material Number
         maktx LIKE makt-maktx,     "Material Description-- jp check
         charg LIKE lips-charg,      "Batch number
         lichn LIKE lips-lichn,      "Vendor Batch number
         lhmg1 LIKE mlgn-lhmg1,     "standard pallet size
         lhme1 LIKE mlgn-lhme1,      "Unit of standard pallet
         lety1 LIKE mlgn-lety1,     "tower
         ltkze LIKE mlgn-ltkze,      "Storage location
         umrez LIKE marc-zzjp_cas_size,      "Std package unit
         meinh LIKE ekpo-meins,      "alternate unit
         zzjp_nyu_sop LIKE marc-zzjp_nyu_sop,      "Product Std number
         zzjp_dos_frm LIKE marc-zzjp_dos_frm,      "Dosage form
         zzjp_aprn     LIKE marc-zzjp_aprn,          "Apperance
         zzjp_re1     LIKE marc-zzjp_re1,           "Heading
         std_pac_no(13) TYPE n,            "Std receipt package no
         tot_std_pt(13) TYPE n,             "Total no of std pallets
add begin CR1447
Add new field 'Goods-in-order','Item' for goods in plan list
         vbeln like ekes-vbeln,     "Goods-in-order
         vbelp like ekes-vbelp,     "Item
add end CR1447
      END OF t_display.
Internal table for storing the final display data -Goods in order list
DATA: BEGIN OF t_display1 OCCURS 0,
         ebeln LIKE ekes-ebeln,      "Purchasing Document Number
         ebelp LIKE ekes-ebelp,      "Item Number of Purchasing Document
         etens LIKE ekes-etens,      "Sequence No
         eindt LIKE eket-eindt,      "Item delivery date
         menge LIKE eket-menge,      "Scheduled Quantity
         vpnam(40) TYPE c,          "Vendor product name
         lifnr LIKE ekko-lifnr,      "Vendor code
         name1 LIKE lfa1-name1,      "Vendor name
         meins LIKE ekpo-meins,      "Unit of measure
         matnr LIKE ekpo-matnr,      "Material Number
         maktx LIKE makt-maktx,     "Material Description-- jp check
         charg LIKE lips-charg,      "Batch number
         lichn LIKE lips-lichn,      "Vendor Batch number
         lhmg1 LIKE mlgn-lhmg1,     "standard pallet size
         lhme1 LIKE mlgn-lhme1,      "Unit of standard pallet
         lety1 LIKE mlgn-lety1,     "tower
         ltkze LIKE mlgn-ltkze,      "Storage location
         umrez LIKE marc-zzjp_cas_size,      "Std package unit
         meinh LIKE ekpo-meins,      "alternate unit
         zzjp_nyu_sop LIKE marc-zzjp_nyu_sop,      "Product Std number
         zzjp_dos_frm LIKE marc-zzjp_dos_frm,      "Dosage form
         zzjp_aprn     LIKE marc-zzjp_aprn,          "Apperance
         zzjp_re1     LIKE marc-zzjp_re1,           "Heading
         std_pac_no(13) TYPE n,            "Std receipt package no
         tot_std_pt(13) TYPE n,             "Total no of std pallets
      END OF t_display1.
Internal table for storing the final display data - Goods in plan list
DATA: BEGIN OF t_display2 OCCURS 0,
         ebeln LIKE ekes-ebeln,      "Purchasing Document Number
         ebelp LIKE ekes-ebelp,      "Item Number of Purchasing Document
         etens LIKE ekes-etens,      "Sequence No
         eindt LIKE eket-eindt,      "Item delivery date
         menge LIKE eket-menge,      "Scheduled Quantity
         name1 LIKE lfa1-name1,      "Vendor name
         meins LIKE ekpo-meins,      "Unit of measure
         matnr LIKE ekpo-matnr,      "Material Number
         maktx LIKE makt-maktx,     "Material Description-- jp check
         charg LIKE lips-charg,      "Batch number
         lichn LIKE lips-lichn,      "Vendor Batch number
         lhmg1 LIKE mlgn-lhmg1,     "standard pallet size
         lety1 LIKE mlgn-lety1,     "tower
         ltkze LIKE mlgn-ltkze,      "Storage location
         tot_std_pt(13) TYPE n,             "Total no of std pallets
add begin CR1447
Add new field 'Goods-in-order','Item' for goods in plan list
         vbeln like ekes-vbeln,     "Goods-in-order
         vbelp like ekes-vbelp,     "Item
add end CR1447
      END OF t_display2.
add begin CR1591
RANGES: r_matnr FOR mara-matnr,   "for p_matnr
        r_ebeln FOR ekpo-ebeln.   "for p_ebeln
add end CR1591
DATA: line TYPE i.            " line number
DATA: g_checkbox TYPE c.      "check box for selection of records
DATA: g_tab LIKE sy-index.    "variable to hold index
DATA g_tabix LIKE sy-tabix. "holder for table index
Printing Options.
DATA: lw_pr_options LIKE itcpo.
*lw_pr_options-tddest = 'SA03'.      " Print Device Name
lw_pr_options-tdpreview = 'X'.      " Print Preview
lw_pr_options-tdnewid = 'X'.        " New Request
lw_pr_options-tdlifetime = 2.       " Retention in Spool
                        Selection Screen                             *
SELECTION-SCREEN BEGIN OF BLOCK blk1 WITH FRAME.
SELECT-OPTIONS:
s_date FOR sy-datum DEFAULT sy-datum. " Search period.
PARAMETERS:
p_matnr LIKE mara-matnr,               " Material code
p_ebeln LIKE ekpo-ebeln.               " Purchase Document No
SELECTION-SCREEN END OF BLOCK blk1.
                   Selection Screen Checks                           *
AT SELECTION-SCREEN.
IF ( s_date-low IS INITIAL ) AND
     ( p_matnr IS INITIAL ) AND
     ( p_ebeln IS INITIAL ).
    MESSAGE e000 WITH 'Entry Must in atleast one of the Fields'(t00).
ENDIF.
IF ( NOT p_matnr IS INITIAL ) AND
     ( s_date IS INITIAL )      AND
     ( p_ebeln IS INITIAL ).
    MESSAGE e000 WITH 'Date should also be Entered'(t01).
ENDIF.
del begin CR1591
This check is not found in original FS
IF ( NOT p_matnr IS INITIAL ) AND
    ( s_date IS INITIAL ) AND
    ( NOT p_ebeln IS INITIAL ).
   MESSAGE e000 WITH 'Date should also be Entered'(t01).
ENDIF.
del end CR1591
               Validations for Data selection                        *
del begin CR1591
Waste check
IF ( NOT s_date IS INITIAL ) AND
    ( p_matnr IS INITIAL ) AND
    ( p_ebeln IS INITIAL ).
   PERFORM f_check_date_in_eket.
ENDIF.
IF ( NOT s_date IS INITIAL ) AND
    ( NOT p_matnr IS INITIAL ) AND
    ( p_ebeln IS INITIAL ).
   PERFORM f_check_matnr_in_plant.
   PERFORM f_check_matnr_in_ekpo.
   PERFORM f_check_date_in_eket.
   PERFORM f_check_matnr_in_plant.
   PERFORM f_check_matnr_in_ekpo.
ENDIF.
IF ( NOT s_date IS INITIAL ) AND
    ( NOT p_matnr IS INITIAL ) AND
    ( NOT p_ebeln IS INITIAL ).
   PERFORM f_check_matnr_in_plant.
   PERFORM f_check_matnr_in_ekpo.
   PERFORM f_check_date_in_eket.
   PERFORM f_check_ebeln_in_ekpo.
   PERFORM f_check_werks_in_ekpo.
ENDIF.
IF ( NOT p_ebeln IS INITIAL ) AND
    ( NOT s_date IS INITIAL ) AND
    ( p_matnr IS INITIAL ).
   PERFORM f_check_date_in_eket.
   PERFORM f_check_ebeln_in_ekpo.
   PERFORM f_check_werks_in_ekpo.
ENDIF.
IF ( NOT p_ebeln IS INITIAL ) AND
    ( s_date IS INITIAL ) AND
    ( p_matnr IS INITIAL ).
   PERFORM f_check_ebeln_in_ekpo.
   PERFORM f_check_werks_in_ekpo.
ENDIF.
del end CR1591
                     Data selection from Tables                      *
START-OF-SELECTION.
SET PF-STATUS 'SELECT'.
add begin CR1591
Set ranges tables
PERFORM set_ranges.
add end CR1591
mod begin CR1591
**Selection of PO data from EKET into internal table t_purc.
PERFORM f_select_eket.
**Selection of corresponding PO data for EKET from EKES into t_ekes.
PERFORM f_select_ekes.
**Selection of material desc from MAKT table into T_makt.
PERFORM f_select_makt.
**Copy the contents of t_purc and t_makt into t_eket table.
PERFORM f_move_eket.
**Replace the corresponding entries of t_eket with t_ekes.
PERFORM f_update_eket.
Selection of PO data from EKET into internal table T_EKET.
PERFORM f_select_eket2.
Selection of corresponding PO data from EKES appending to T_EKET.
PERFORM f_select_ekes2.
Selection of material desc from MAKT table into T_MAKT.
PERFORM f_select_makt2.
mod end CR1591
*Selection of vendor product name.
PERFORM f_select_vpnam.
del begin CR1591
No need
**copy t_eket-ebelp into temporary variable.
PERFORM f_copy_ebelp.
del end CR1591
*selection of data from MLGN table into t_mlgn internal table
PERFORM f_select_mlgn.
*selection of data from marm table into t_marm internal table
PERFORM f_select_marm.
*selection of data from marc table into t_marc internal table
PERFORM f_select_marc.
*selection of data from lfa1 table into t_lfa1 internal table
PERFORM f_select_lfa1.
*Selection of data from LIPS table into t_lips internal table
PERFORM f_select_lips.
del begin CR1591
Don't display list screen when no data exists
*END-OF-SELECTION.
del end CR1591
*lines = sy-linno - 1.
*Collection of data into the final display internal table t_Display
PERFORM f_collect_final.
*Display the contents of t_display as a simple List
PERFORM f_list_display.
AT USER-COMMAND.
PERFORM f_select_layout.
INCLUDE zjpmipu315.
INCLUDE zjpmipu316.
*&      Form f_check_MATNR_in_plant
     This Routine is to check if the the selected material code is
     available in the plant 'JP01'.
FORM f_check_matnr_in_plant.
DATA: l_matnr LIKE mara-matnr.
SELECT matnr UP TO 1 ROWS FROM marc
                   INTO l_matnr
                   WHERE
                   matnr = p_matnr AND
                   werks = c_werks.
ENDSELECT.
IF l_matnr IS INITIAL.
    MESSAGE e000 WITH
    'The material is not available in '(t02) c_werks 'plant'(t20).
ENDIF.
ENDFORM.                    " f_check_MATNR_in_plant
*&      Form f_check_EBELN_in_EKPO
      This Routine is to check if the Purchase order number selected
      is existing or not and if it exists, check if it is related to
      the plant 'JP01'.
FORM f_check_ebeln_in_ekpo.
DATA: l_ebeln LIKE ekpo-ebeln.
SELECT ebeln UP TO 1 ROWS FROM ekpo
                INTO l_ebeln
                WHERE
                ebeln = p_ebeln AND
                werks = c_werks.
ENDSELECT.
IF l_ebeln IS INITIAL.
    MESSAGE e000 WITH
    'PO not available or not related to '(t03) c_werks 'plant'(t21).
ENDIF.
ENDFORM.                    " f_check_EBELN_in_EKPO
*&      Form f_check_matnr_in_ekko
      This routine is to check if any PO exist for the selected
      Material code.
FORM f_check_matnr_in_ekpo.
DATA: l_matnr LIKE ekpo-matnr.
SELECT matnr UP TO 1 ROWS FROM ekpo
                   INTO l_matnr
                   WHERE
                   matnr = p_matnr.
ENDSELECT.
IF l_matnr IS INITIAL.
    MESSAGE e000 WITH
    'PO does not exist for the material no'(t04) p_matnr.
ENDIF.
ENDFORM.                    " f_check_matnr_in_ekpo
*&      Form f_check_date_in_eket
      This routine is to check if any purchase order exists
      with the selected
FORM f_check_date_in_eket.
DATA: l_eindt LIKE eket-eindt.
SELECT eindt UP TO 1 ROWS FROM eket
                   INTO l_eindt
                   WHERE
                   eindt IN s_date.
ENDSELECT.
IF l_eindt IS INITIAL.
    MESSAGE e000 WITH
   'No PO exist with the selected delivery date '(t05).
ENDIF.
ENDFORM.                    " f_check_date_in_eket
*&      Form f_check_werks_in_ekpo
      This Routine is to check if the selected purchase order
      is associated with the plant JP01
FORM f_check_werks_in_ekpo.
DATA: l_ebeln LIKE ekpo-ebeln.
SELECT ebeln UP TO 1 ROWS FROM ekpo
                   INTO l_ebeln
                   WHERE
                   werks = c_werks.
ENDSELECT.
IF l_ebeln IS INITIAL.
    MESSAGE e000 WITH
    'The selected P0 is not relevant to '(t06) c_werks 'plant'(t22).
ENDIF.
ENDFORM.                    " f_check_werks_in_ekpo
*&      Form f_select_eket
      Routine to collect data from EKET, EKPO, MAKT, EKKO tables
      using inner join and store the data into internal table
      t_PURC. The data selection is based on the selection screen's
      input.
FORM f_select_eket.
IF ( NOT s_date-low IS INITIAL ) AND
     ( p_matnr IS INITIAL ) AND
     ( p_ebeln IS INITIAL ).
    SELECT
            eket~ebeln
            eket~ebelp
            eket~eindt
            eket~menge
            eket~charg
            ekpo~matnr
            ekpo~werks
            ekpo~meins
            ekko~lifnr
     INTO TABLE t_purc
    FROM
             ( ( eket INNER JOIN ekko ON
              eketebeln = ekkoebeln )   INNER JOIN ekpo ON
              eketebelp = ekpoebelp AND
              ekpoebeln = ekkoebeln )
WHERE
            eket~eindt IN s_date AND
            ekpo~werks = c_werks AND
            ekpo~elikz NE c_x AND
            ekko~bstyp EQ c_f AND
            ekko~bsart NE c_zar.
ELSEIF ( NOT s_date-low IS INITIAL ) AND
     ( NOT p_matnr IS INITIAL ) AND
     ( p_ebeln IS INITIAL ).
    SELECT
            eket~ebeln
            eket~ebelp
            eket~eindt
            eket~menge
            eket~charg
            ekpo~matnr
            ekpo~werks
            ekpo~meins
            ekko~lifnr
     INTO TABLE t_purc
    FROM
             ( ( eket INNER JOIN ekko ON
              eketebeln = ekkoebeln )   INNER JOIN ekpo ON
              eketebelp = ekpoebelp AND
              ekpoebeln = ekkoebeln )
WHERE
            eket~eindt IN s_date AND
            ekpo~matnr = p_matnr AND
            ekpo~werks = c_werks AND
            ekpo~elikz NE c_x AND
            ekko~bstyp EQ c_f AND
            ekko~bsart NE c_zar.
ELSEIF ( NOT s_date-low IS INITIAL ) AND
     ( NOT p_matnr IS INITIAL ) AND
     ( NOT p_ebeln IS INITIAL ).
    SELECT
            eket~ebeln
            eket~ebelp
            eket~eindt
            eket~menge
            eket~charg
            ekpo~matnr
            ekpo~werks
            ekpo~meins
            ekko~lifnr
     INTO TABLE t_purc
    FROM
             ( ( eket INNER JOIN ekko ON
              eketebeln = ekkoebeln )   INNER JOIN ekpo ON
              eketebelp = ekpoebelp AND
              ekpoebeln = ekkoebeln )
WHERE
            eket~eindt IN s_date AND
            ekpo~matnr = p_matnr AND
            ekpo~ebeln = p_ebeln AND
            ekpo~werks = c_werks AND
            ekpo~elikz NE c_x AND
            ekko~bstyp EQ c_f AND
            ekko~bsart NE c_zar.
ELSEIF ( s_date-low IS INITIAL ) AND
     ( p_matnr IS INITIAL ) AND
     ( NOT p_ebeln IS INITIAL ).
    SELECT
            eket~ebeln
            eket~ebelp
            eket~eindt
            eket~menge
            eket~charg
            ekpo~matnr
            ekpo~werks
            ekpo~meins
            ekko~lifnr
     INTO TABLE t_purc
    FROM
             ( ( eket INNER JOIN ekko ON
              eketebeln = ekkoebeln )   INNER JOIN ekpo ON
              eketebelp = ekpoebelp AND
              ekpoebeln = ekkoebeln )
WHERE
            ekpo~ebeln = p_ebeln AND
            ekpo~werks = c_werks AND
            ekpo~elikz NE c_x AND
            ekko~bstyp EQ c_f AND
            ekko~bsart NE c_zar.
ELSEIF ( NOT s_date-low IS INITIAL ) AND
     ( p_matnr IS INITIAL ) AND
     ( NOT p_ebeln IS INITIAL ).
    SELECT
            eket~ebeln
            eket~ebelp
            eket~eindt
            eket~menge
            eket~charg
            ekpo~matnr
            ekpo~werks
            ekpo~meins
            ekko~lifnr
     INTO TABLE t_purc
    FROM
             ( ( eket INNER JOIN ekko ON
              eketebeln = ekkoebeln )   INNER JOIN ekpo ON
              eketebelp = ekpoebelp AND
              ekpoebeln = ekkoebeln )
WHERE
            eket~eindt IN s_date AND
            ekpo~ebeln = p_ebeln AND
            ekpo~werks = c_werks AND
            ekpo~elikz NE c_x AND
            ekko~bstyp EQ c_f AND
            ekko~bsart NE c_zar.
ENDIF.
IF sy-subrc <> 0.
   MESSAGE s000 WITH 'Data not found'(t07).
   LEAVE LIST-PROCESSING.
ELSE.
SORT t_purc.
ENDIF.
ENDFORM.                    " f_select_eket
*&      Form f_select_makt
      Routine to select the material description for all the
      materials present in T_purc table
FORM f_select_makt.
DATA: l_t_makt(4) TYPE c VALUE 'MAKT'.
SELECT
      matnr
      maktx
FROM
      makt
INTO TABLE t_makt
      FOR ALL ENTRIES IN t_purc
WHERE
     matnr = t_purc-matnr AND
     spras = c_spras.
IF sy-subrc <> 0.
    MESSAGE s000 WITH
      'Relevant data not found in'(t09) l_t_makt 'table'(t23).
ELSE.
    SORT t_makt.
ENDIF.
ENDFORM.                    " f_select_makt
*&      Form f_move_eket
      Routine to join data in T_PURC and T_MAKT tables into
      internal table T_MAKT.
FORM f_move_eket.
LOOP AT t_purc.
    t_eket-ebeln = t_purc-ebeln.
    t_eket-ebelp = t_purc-ebelp.
    t_eket-eindt = t_purc-eindt.
    t_eket-menge = t_purc-menge.
    t_eket-charg = t_purc-charg.
    t_eket-matnr = t_purc-matnr.
    t_eket-werks = t_purc-werks.
    t_eket-meins = t_purc-meins.
    t_eket-lifnr = t_purc-lifnr.
    READ TABLE t_makt WITH KEY matnr = t_purc-matnr
                                     BINARY SEARCH.
    IF sy-subrc = 0.
      t_eket-maktx = t_makt-maktx.
    ENDIF.
    APPEND t_eket.
    CLEAR t_eket.
ENDLOOP.
ENDFORM.                    " f_move_eket
*&      Form f_select_ekes
      Routine to select EKES data for all corresponding entries
      of T_EKET.
FORM f_select_ekes.
DATA: l_tabix TYPE i.
IF NOT s_date IS INITIAL.
   SELECT
           ebeln
           ebelp
           etens
           eindt
           menge
    INTO   TABLE t_ekes
     FROM
           ekes
    WHERE
           eindt IN s_date.
ELSE.
DESCRIBE TABLE t_purc LINES l_tabix.
IF l_tabix GT 0.
    SELECT
            ebeln
            ebelp
            etens
            eindt
            menge
            dabmg
            vbeln
            vbelp
     FROM
            ekes
     INTO   TABLE t_ekes
           FOR ALL ENTRIES IN t_eket
            FOR ALL ENTRIES IN t_purc
     WHERE
            ebeln = t_purc-ebeln AND
            ebelp = t_purc-ebelp AND
            eindt IN s_date.
          AND ebeln eq p_ebeln.
       and matnr in p_matnr.
ENDIF.
CLEAR l_tabix.
IF NOT s_date IS INITIAL AND NOT p_ebeln IS INITIAL.
    SELECT
            ekes~ebeln
            ekes~ebelp
            ekes~etens
            ekes~eindt
            ekes~menge
            ekes~dabmg
   APPENDING TABLE t_ekes
      FROM ekes
     WHERE
            eindt IN s_date AND
            ebeln EQ p_ebeln AND
            ebtyp EQ c_la.
ELSEIF NOT s_date IS INITIAL AND p_ebeln IS INITIAL.
    SELECT
                ekes~ebeln
                ekes~ebelp
                ekes~etens
                ekes~eindt
                ekes~menge
                ekes~dabmg
       APPENDING TABLE t_ekes
          FROM ekes
         WHERE
                eindt IN s_date AND
           ebeln EQ p_ebeln AND
                ebtyp EQ c_la.
ELSEIF s_date IS INITIAL AND NOT p_ebeln IS INITIAL.
    SELECT
                ekes~ebeln
                ekes~ebelp
                ekes~etens
                ekes~eindt
                ekes~menge
                ekes~dabmg
       APPENDING TABLE t_ekes
          FROM ekes
         WHERE
           eindt IN s_date AND
                ebeln EQ p_ebeln AND
                ebtyp EQ c_la.
ENDIF.
IF sy-subrc = 0.
    SORT t_ekes.
ENDIF.
IF NOT t_ekes[] IS INITIAL.
    t_ekes_temp[] = t_ekes[].
    SORT t_ekes_temp BY ebeln ebelp.
    DELETE ADJACENT DUPLICATES FROM t_ekes_temp COMPARING ebeln ebelp.
    LOOP AT t_ekes_temp.
      READ TABLE t_purc WITH KEY ebeln = t_ekes_temp-ebeln
                                 ebelp = t_ekes_temp-ebelp.
      IF sy-subrc NE 0.
        CLEAR t_purc.
        SELECT SINGLE
              eket~ebeln
              eket~ebelp
              eket~eindt
              eket~menge
              eket~charg
              ekpo~matnr
              ekpo~werks
              ekpo~meins
              ekko~lifnr
       INTO CORRESPONDING FIELDS OF t_purc
      FROM
               ( ( eket INNER JOIN ekko ON
                eketebeln = ekkoebeln )   INNER JOIN ekpo ON
                eketebelp = ekpoebelp AND
                ekpoebeln = ekkoebeln )
    WHERE
             eket~ebeln = t_ekes_temp-ebeln
      AND    eket~ebelp = t_ekes_temp-ebelp
      AND    ekpo~elikz NE c_x
      AND    ekko~bstyp EQ c_f
      AND    ekko~bsart NE c_zar.
        IF sy-subrc EQ 0.
          APPEND t_purc.
          CLEAR t_purc.
        ENDIF.
      ENDIF.
    ENDLOOP.
ENDIF.
REFRESH: t_ekes_temp, t_ekes.
CLEAR: t_ekes_temp, t_ekes.
Once the header is filled up get the details from EKES
SELECT ebeln ebelp etens eindt menge dabmg vbeln vbelp
                     INTO TABLE t_ekes
                     FROM ekes
                     FOR ALL ENTRIES IN t_purc
               WHERE ebeln EQ t_purc-ebeln.
Mark the entries as 'X' which falls in the date range
LOOP AT t_ekes.
    IF t_ekes-eindt IN s_date.
      t_ekes-mark = 'X'.
      MODIFY t_ekes INDEX sy-tabix TRANSPORTING mark.
    ENDIF.
ENDLOOP.
SORT t_ekes BY ebeln ebelp ASCENDING mark DESCENDING.
Delete the entries from eket if no entries in EKES falls in the period
LOOP AT t_purc.
    l_tabix = sy-tabix.
    READ TABLE t_ekes WITH KEY ebeln = t_purc-ebeln
                               ebelp = t_purc-ebelp.
    IF sy-subrc EQ 0.
      IF t_ekes-mark NE 'X'.
        DELETE t_purc INDEX l_tabix.
      ENDIF.
    ENDIF.
ENDLOOP.
delete the entries from EKES which do not fall in the specified period
DELETE t_ekes WHERE mark NE 'X'.
ENDFORM.                    " f_select_ekes
*&      Form f_update_eket
      Routine to substitute relevant t_eket entries with that of
      t_ekes entries.It does not modify the remaining entries for
      for which the corresponding values in t_ekes doesnot exist.
FORM f_update_eket.
DATA: BEGIN OF lt_temp_eket OCCURS 0,
           ebeln LIKE eket-ebeln, "Purchasing Document Number
           ebelp LIKE eket-ebelp, "Item Number of Purchasing Document
           eindt LIKE eket-eindt, "Item delivery date
           menge LIKE eket-menge, "Scheduled quantity
           dabmg LIKE ekes-dabmg, " Delivered quantity
           matnr LIKE ekpo-matnr, "Material code
           maktx LIKE makt-maktx, "Material Description-- jp check
           etens LIKE ekes-etens, "Sequence Number
           meins LIKE ekpo-meins, "Unit of measure
           lifnr LIKE ekko-lifnr, "Vendor number
           charg LIKE eket-charg, " Batch number   Added by PD 08/08/03
           vbeln LIKE ekes-vbeln,
           vbelp LIKE ekes-vbelp,
        END OF lt_temp_eket,
        l_menge LIKE ekes-menge.
LOOP AT t_eket.
    LOOP AT t_ekes WHERE ebeln = t_eket-ebeln
                    AND ebelp = t_eket-ebelp.
Added by PD 08/08/03
      MOVE t_eket-charg TO lt_temp_eket-charg.
addition ends
      MOVE t_eket-ebeln TO lt_temp_eket-ebeln.
      MOVE t_eket-ebelp TO lt_temp_eket-ebelp.
      MOVE t_eket-meins TO lt_temp_eket-meins.
      CLEAR l_menge.
      l_menge = t_ekes-menge - t_ekes-dabmg.
      IF l_menge LE 0.
        CONTINUE.
      ELSE.
        MOVE l_menge TO lt_temp_eket-menge.
      ENDIF.
      MOVE t_ekes-eindt TO lt_temp_eket-eindt.
      MOVE t_ekes-etens TO lt_temp_eket-etens.
      MOVE t_eket-lifnr TO lt_temp_eket-lifnr.
      MOVE t_eket-maktx TO lt_temp_eket-maktx.
      MOVE t_eket-matnr TO lt_temp_eket-matnr.
      MOVE t_ekes-vbeln TO lt_temp_eket-vbeln.
      MOVE t_ekes-vbelp TO lt_temp_eket-vbelp.
      APPEND lt_temp_eket.
      CLEAR lt_temp_eket.
      CLEAR t_ekes.
    ENDLOOP.
    IF sy-subrc NE 0.
Added by PD 08/08/03
      MOVE t_eket-charg TO lt_temp_eket-charg.
addition ends
      MOVE t_eket-ebeln

Dear
Problem No 1 : we are working in a process industries with three plants each of them have three order type. we have define MRP group in "OPPR" then assign each MRP group to Orde types in "OPPE". Now the problem is whn i convert plan order in process order for any material systme automaticaly pick the order type PIi01.
Answer :
1.Please check the OPPR -Plant and MRP group -Select Order Type Button -Check what Order Type you have assinged here ( PI01( May be the default Process Order Type )
2.If you are maintaing MRP group ( 0001 or 0002) , did you asisng the same in MRP1 view ?? because
3.Did you maintain the similar Order type in OPKP -Define Production Scheduling Profile ? -This has highest priority .
4.Did you maintain correct order type in OPJH-Maintain Order Type ??
Refer the expert comments on the same issue : Strategy group to define production order type
Problem No 2: 2nd Problem is system system is not creating plan order for prrevios dates. say i enter PIR for month of november from first november to 30th november and run MRP on 29th the sytem create plan order on 30th of november with exception message 30.
Answer : You can plan the order in back dated , if you maitain Satrt date in the Past optiuon in OPU3/OPU5-Define Scheduling parameters .Goto OPU3 -Select the Order Type -Double click -Maintain 90-60 days in the Start Date in the past in Scheduling Control and Details scheduling tab .
Hope it helps
regards
JH

Back Order per Vendor

Hi All,
I want create Value of Back Order per Vendor report, Any body help me,
What are the tables I have to use.
My selection options are :
Vendor and Delivery Date.
Thanks,

Hi,
If you are on release 4.7 or newer then you don't need to use the tables.
You can use ME2N with a scope of list that has the ALV flag set on (if there isn't one then create one). With the ALV format this (and simialr) transactions can be used to obtain a lot of different reports.
For example if you run ME2N with a selection parameter of WE101 (open deliveries exist) and a delivery date range in the past, you will get a list of POs that are overdue for delivery. You can click on the delivery schedule icon to see the individual delivery dates.
the ALV format means that you can get these lists in the layout you need and they can even be transferred to excel very easily (try doing that with the non-ALV layout !!)
Steve B

Total ordered value for PO

HI All,
Is there any standard report to check total ordered value for PO.
I checked in ME80AN but its not giving excise value. I need Base + Excise + VAT / CST. (Total Net order value per PO)
Please suggest.
Regards
Mahesh M J

Dear Mahesh,
ME81N - Anlysis of order values - By Material / By buyer / By supplier
Totals analysis - ABC analysis -Analysis using comparison period - Frequency analysis
Regards
Anand

Purchases per Vendor

Hi,
We need to generate a report listing out the purchases per vendor and giving the details of articles purchased, quantaties, and values. Could you please advise as to how can this be generated ? We tried to ran the report ME80FN, and after checking for the "Invoice Receipt" under the Dynamic Selections, we observed that the values picked up are same as those mentioned in the PO. However, while doing the Invoice Verification the values were changed and it is desired to generate a report for purchases with the final vlues and not purely the PO values.
Thanks in advance.

Dear Raj,
Run tcode SAP1, this will give you all SAP standard reports available. You can find here various reports according to your choice. Menu Path is: SAP1 - MM- Purchasing/Inventory/LIV....
Rewards me if it helps you.
Thanks.
Vineet Dhawan

Discount on Total Order Value

Hi everybody ,
We need the Discount to be calculated automatically on the Total Order Value.
Its a promotion.
Useful suggestions will be rewarded.
Thanks
Kartik

Hi pls follow the procedure below, Hope it will help u out
VOFM: ON PRICING
This note is an explanation of function "Maintain: Requirements and Formulas", which is also known as "VOFM".
By using descriptions and examples, this note explains how the VOFM function works in the R/3 Standard System, which objects are related to it and which restrictions exist.
Chapter 2.7 explains possible causes of errors and solutions for problems with the VOFM function.
To provide a good overview, this note is subdivided into the following sub areas:
1. General information
1.1 Definition of terms
1.2 Application areas
1.3 A frank word on the "source code responsibility"
2. Technology
2.1 Introduction
2.2 Namespaces
2.2.1 SSCR object registration
2.3 Structure of a VOFM object
2.3.1 Include file with ABAP form routine
2.3.2 Table entries in TFRM and TFRMT
2.4 Calling VOFM objects
2.4.1 VOFM object carrier
2.5 Activation, generation and RV80HGEN
2.6 Transport
2.7 FAQs: Possible causes of errors and problems
Technical field names are displayed in angle brackets [].
Note that this note only explains the mode of operation of the VOFM in an R/3 Standard Core System.
For R/3 industry solutions or Add-Ons the VOFM function displays a different behavior in subareas, however, this is not dealt with in this note.
Additional key words
VOFM, SAPMV80H, TFRM, TFRMT, RV80HGEN, XPRA, formulas, requirements, data transport routine, copy routine, data transfer.
Cause and prerequisites
1. General information
1.1 Definition of terms
Depending on the business processes used it may be necessary to influence the standard behavior of R/3 applications. For that purpose the VOFM function provides a corresponding environment in order to be able to develop and manage customer-specific logic simply.
The system stores the objects generated via the VOFM in the Customizing of the respective application area
(Pricing, message determination and so on) and its programs call the objects correspondingly.
Also SAP delivers certain functions in the form of VOFM objects.
Consequently, the VOFM is an exit technology as explained in more detail in Note 381348.
1.2 Application areas
Typical VOFM objects are requirements, formulas and data transfer routines.
These are used in processes of the purchase order, the delivery, billing, price determination, material determination, message determination, the free goods, the pricing and of others.
In the entries of the R/3 core menu of Transaction VOFM you can find a precise overview of the supported application areas.
1.3 A frank word on the "source code responsibility"
As in user exits, in VOFM objects are many fields and tables available. Thus, the use of VOFM objects is very versatile and consequently also very critical under certain circumstances. For the use of "customer-specific" VOFM objects the statements in Note 381348 regarding the responsibility for customer enhancements (Maintenance responsibility, problems during the upgrade and so on) apply. Read this note carefully before you decide on the use of customer-specific VOFM objects.
Errors and data inconsistencies that are caused by improper application or implementation of VOFM objects are not processed by the SAP Support but exclusively within the framework of the Consulting that has to be purchased separately.
2. Technology
2.1 Introduction
A VOFM object is uniquely defined via characteristics "group indicator" [GRPZE] and "group number" [GRPNO].
Here the group indicator, technically represented by a character field of length 4, is the logical connection to the calling environment.
Examples:
ABED copying requirement in the order
ADAT data transfer in the order
PBED requirements pricing
CASC Data transfer for sales activities
PBEK requirements account determination
CHRG requirements batches
REAK archiving for orders
VFCL Multi-dimensional scales
You can find all defined group indicators in the allowed values of the "GRPZE" domain in the ABAP Dictionary (Transaction SE11).
The group number can have a value from 1 to 999.
Exceptions are group indicators "PSTK" (= group key routine pricing) and "TDAT" (= data transfer for texts). For these the system can only assign group numbers from 1 to 99.
2.2 Namespaces
The VOFM has separate number ranges in order to distinguish VOFM objects delivered by SAP from customer-specific VOFM objects. These number ranges are often also called "VOFM namespaces".
However, note that this is not a "real namespace" that is protected by corresponding entries in system table "TRESC" (= reserved names for Customizing tables and Customizing objects).
Instead, only the VOFM logic itself does the definition and check of the number ranges.
The following list displays the customer number ranges sorted according to group indicators:
Indicator     Name     Number range customer
FOFU     Subsequent functions     900 - 999
PSTK     Group key routines     50 - 99
TDAT     Data transfer routines f. texts     50 - 99
all other group indicators           600 - 999
In Note 356737 you can find more information on the available VOFM number ranges.
2.2.1 SSCR object registration
VOFM objects are subject to SSCR registration (= SAP Software Change Registration).
The reason for that is the necessity that every VOFM object is physically assigned to that SAP development class, from whose programs a corresponding jump into the VOFM object later occurs.
If you use the VOFM interface the system makes the assignment automatically. An assignment of customer-specific development classes is not possible.
2.3 Structure of a VOFM object
A VOFM object consists of the following parts:
Include file with ABAP form routine
TFRM table entry
TFRMT table entry
2.3.1 Include file with ABAP form routine
In the ABAP form routine the desired function is programmed.
Example pricing value formula number 001:
Include name : FV64A001
Form routine : FRM_KONDI_WERT_001
Implementation: * * Profit margin considering rebate agreements
form frm_kondi_wert_001.
xkwert = komp-kzwi3 - komp-wavwr.
endform.
Dependending on the selected group indicator, the group number and the system type (SAP or customer system), the system assigns and generates the include name and form routine name automatically.
For this reason, standard routines delivered by SAP generally have a different structure of the include name than customer-specific routines.
Example:
SAP standard value formula for the pricing
=> prefix FV64A + object number with 3 places from 'SAP namespace'
=> for example FV64A001
Customer-specific value formula for the pricing
=> prefix RV64A + object number with 3 places from 'customer namespace'
=> for example RV64A905
2.3.2 Table entries in TFRM and TFRMT
The entries in tables TFRM and TFRMT belonging to a VOFM object are used for the status management and assignment. The system always analyzes them if the user calls Transaction VOFM or if a generation operation occurs (for details refer to section 2.5).
The system generates exactly one TFRM table entry per VOFM OBjekt. In this TFRM entry the following information is stored:
Group indicator     GRPZE
Group number     GRPNO
Routine 'active' indicator     AKTIV_TFRM
Application     KAPPL
Date of the last generation     GNDAT
Time of the last generation     GNZEI
Examples:
GRPZE     GRPNE     AKTIV_TFRM     KAPPL     GNDAT     GNZEI
PBED     001     X     V     06 13 2001     09 06 39
TDAT     001     X           06 13 2001     09 06 39
CHRG     003     X           06 13 2001     09 06 39
The meaning of group indicators and group numbers has already been dealt with.
The 'active indicator' controls whether a VOFM object is 'active' or 'inactive'. Active VOFM objects have characteristic value AKTIV_TFRM = 'X', inactive objects have characteristic value AKTIV_TFRM = initial.
VOFM objects flagged as 'active' are 'known' to the calling program logic, that means they were included in the main program of the 'calling program' and can thus be addressed and
processed during the runtime.
You cannot delete VOFM objects that are still 'active'. In this case you have to reset the active indicator manually before.
The content of the 'Application' field serves to filter the relevant VOFM objects in various display functions and Customizing functions.
Example: Condition value formula 010 'Relevant Price'. This formula has characteristic value 'MS' for the 'Application' field (= External Services Management purchasing). Therefore the object is not open for selection in the input help during the maintenance of pricing procedure SD (Transaction V/08), because this is a Customizing transaction assigned to application 'V' (= Sales and Distribution).
Storing an application key is optional.
The generation date and the generation time record the time of the last registration of the VOFM object (the object carrier, refer to section 2.4.1).
In addition to the respective TFRM entry a VOFM object can have 'n' entries in table TFRMT. The entries are used for the storage of language-dependent object descriptions, which are structured as follows:
- Language key [SPRAS]
- Group indicator [GRPZE]
- Group number [GRPNO]
- Description [BEZEI]
Examples:
SPRAS     GRPZE     GRPNO     BEZEI
D     PBED     001     Regulierer abweich
E     PBED     001     Different payer
The system supplies the language key automatically with the logon language of the user during the creation of a new VOFM object.
The length of the object description is limited to 20 characters.
Important! A VOFM object is only consistent if both the Include file with ABAP form routine and a corresponding TFRM table entry exist. Entries in table TFRMT are optional.
2.4 Calling VOFM objects
As mentioned above, VOFM objects are called directly by the application logic of R/3 standard programs. Technically this is implemented by ABAP statement 'PERFORM ... IN PROGRAM'. With the aid of this statement you can specify both the name of the subroutine and the main program dynamically (during the runtime).
Example: Call of a condition value formula from the pricing
if xkomv-kofrm ne 0. <<< formula reference existing?
xkwert = xkomv-kwert. <<< act. value in work variable
frm_kondi_wert-nr = xkomv-kofrm. <<< set up object names
perform (frm_kondi_wert) in program saplv61a if found. <<<CALL
xkomv-kwert = xkwert. <<
endif.
In the example above the subroutine is determined by the contents of variable 'FRM_KONDI_WERT'; the main program, which is to be searched for the form routine, is SAPLV61A.
If the called routine is not known in the main program, a program termination with the title 'PERFORM_NOT_FOUND' occurs.
Therefore some users of the VOFM technology call ABAP statement 'PERFORM ... IN PROGRAM' together with the addition 'IF FOUND', which has the effect that a jump into the form routine is only executed if this in fact exists in the main program. This does indeed prevent a program termination, however, the result of the overall process may deviate from the
result expected by the user, because in this case the system does not execute the source code implemented in the VOFM object.
2.4.1 VOFM 'object carrier'
Object carriers are required to make a VOFM object 'known' in the main program of the calling program (refer to section 2.4). The object carrier is integrated in the main program of the calling program as an independent include (for example SAPLV61A, SAPMV45A and so on).
Example: Inclusion of object carriers for word processing in SD
documents; Program 'SAPLV45T'
System-defined Include-files. *
INCLUDE LV45TTOP. "Global Data
INCLUDE LV45TDEF.
INCLUDE LV45TUXX. "Function Modules
INCLUDE LV45TNNN. <<< 'carrier' copy requirements for texts
INCLUDE LV45TENN. <<< 'carrier' copy routines for texts
Every active VOFM object (for an explanation on the active indicator refer to section 2.3.2) must be registered in the 'carrier'.
The system writes standard VOFM objects delivered by SAP directly into the 'carrier', VOFM objects from the number range reserved for customers (refer to section 2.2 'Namespaces') are sorted into a 'sub-include' included in the carrier.
Exactly one carrier exists per group indicator. The names of all defined object carriers are hard-coded in program MV80HF0A, form routine 'AKTIVIEREN_TRAEGER_SETZEN'.
Here the names of the sub-include for customer-specific VOFM objects belonging to the main carrier are also defined.
Example: Carrier object 'FV63ANNN' for the registration of condition basis formulas in the pricing (Program SAPLV61A)
FV63ANNN
<<< main
carrier-include
|-INCLUDE RV63ANNN. "User-Routinen <<< sub-include customer objects
| |- INCLUDE RV63A910. "Customer specific
| |- INCLUDE RV63A911. "Customer specific
| |- INCLUDE RV63A912. "Customer specific
| |- ...
|- INCLUDE FV63A001. "Volume
|- INCLUDE FV63A002. "Net value
|- INCLUDE FV63A003. "Net Price
|- INCLUDE FV63A004. "Net Value Plus Tax
|- INCLUDE FV63A005. "KZWI1
|- ...
Because the content of the VOFM object carriers is automatically created source code, you should avoid manual changes to them.
SAP notes, which suggest manual changes to the object carriers, are therefore also incorrect. However, if you nevertheless receive such a note to solve a problem, contact the SAP
Support with a reference to this note.
2.5 Activation, generation and RV80HGEN
The 'activation' is the inclusion of an VOFM object in an object carrier. A 'deactivation' results in the removal of the VOFM object from the object carrier.
The overall process for the creation of a current object carrier is often called 'generation'.
Generally the activation or generation fall into three types.
- Individual activation
- Collective activation
- Generation of object carriers via report RV80HGEN
The 'individual activation' causes the registration of an individual VOFM object in the corresponding object carrier. Which object carrier is relevant is determined with the aid of the group indicator and the group number. In addition to the entry of the VOFM object in the object carrier the system writes the date and time of the generation into table TFRM (refer also to section 2.3.2).
You can start the individual activation only manually. It is always always executed when a user selects a line within the VOFM editing interfaces and afterwards selects activity
'Activate' from the 'Edit' menu.
The 'collective activation' causes the registration of all VOFM objects that belong to a certain group indicator. Analog to the individual activation the system determines the relevant object carrier automatically and writes date and time into table TFRM. The 'collective activation' is a process which you can start also only manually. For this purpose, choose activity
'Activate all' from the 'Edit' menu.
During the generation via report RV80HGEN the system sets up the object carriers of all defined group indicators again. However, the system includes only those VOFM objects that have set the 'active' indicator in the corresponding TFRM table entry. Nonactive VOFM objects are not included in object carriers during the generation via report RV80HGEN.
Due to the quantity of the data to be processed,
the generation via RV80HGEN can take between 0,5 and >5 minutes (depending on the system and the constellation).
Because the RV80HGEN is defined as 'XPRA', it is executed automatically during a system upgrade.
You can also use this XPRA feature for the transport of VOFM objects in order to implement an automatic update of the object carriers after the import of VOFM objects into the target system (section 2.6 provides more details on the transport).
Both the collective activation and the activation via report RV80HGEN technically revert to the program components of the individual activation. For the separate control of the individual activation types form routine AKTIVIEREN_EINZELN (Include MV80HF0A) has a 'USING' parameter, which can have the following characteristic values:
'E' Activate individually
'A' Activate all (= collective activation)
' ' Deactivate individually
During the generation via RV80HGEN the system executes a collective activation for every group indicator sequentially, that means a call of form routine
AKTIVIEREN_EINZELN with characteristic value 'A'.
2.6 Transport
If you want to transfer VOFM objects from one system (= source) into another system (= target), this is generally made with an object transport.
As of Release 4.0, the VOFM function has a connection to the SAP 'Change and Transport System' (CTS) in order to simplify the transfer process for the user.
By the transport connection the system automatically adds newly created or changed VOFM objects to the object list of a transport request which was selected by the user before.
All steps necessary for the execution of a VOFM transport are described in detail in Note 22808 'Transferring formulas'. Note that steps 1-4 are only needed
if the VOFM maintenance environment providesno automatic connection to the transport system or if you want to combine a transport request manually. In any case you must execute step 5, regardless of how the transport request was created.
In addition to Note 22808, Note 385067 contains an overview for releases >= 4.6C regarding which sorts of tasks and object entries are required in a
transport request (depending on the activity carried out (create/change/activate/deactivate/delete)) in order to transport a VOFM object successfully.

Sum of values exceeds the allowed maximum value per service line

Hi Guys,
While creating PO wrt to contract : I get error msg : Sum of values exceeds the allowed maximum value per service line Message no. SE402. Can I change it to warning or should I bifurcate one line into two , as the value is very big. Totalling to 11 characters excluding decimal. Its like xxx,xxx,xxx.xx inr.
Regards,
SK

Hi,
For service line items, the maximum allowed limit is 999999999.99 (total 11 digits including 2 decimals) as per design. If you want more than that, you may split the service in to two line items.
The note: 1810281 - System does not issue error message SE 402 explains the logic.
Regards,
AKPT

Mvt Types used to calculate Total Consumption Values

Hi All,
I have a report that has the Total Consumptions Output from the MVER table for every period. Now My requirement is to eliminate certain Movement types from the Total Consumption Quantity. These Movement types are input as select-options by user.
Now my main problem is that , The values got from MVER table are total values per period. And if i need to exclude certain movement types that are in the total, i need to know which movement types were used to calculate the total. What movement types contribute to the values in MVER-GSV01, MVER-GSV02.....etc. How is that value found. How is that table populated by SAP directly. What is that criteria. Can i find any other table which can let me do the same, i mean manually add values to get that total.
I tried MSEG-MKPF and got some values for Material-Movement type-Period combination. But which of those values should i consider for the total value? I guess only certain movement types are considered as sum of all movement types results in a value higher than the value in MVEr. Does T156 tell us anything about which to add?
Thanks in advance..!

Hi,
Field KZVBU of T156 will give you clue which of the movement types will update consumption data. But you have to check for field XLAUT to check whether the movement is a reversal of some other movements and accordingly do the calculations.
Give me some more time to find out whether the movement types we get from above observations are the once to be considered.

Total Workflow Associations per Site

Greetz!
We are planning our SharePoint 2013 Enterprise On-Premise Farm. We are relying heavily on a Nintex Workflow 2013 product which has a dependency on the 2010 Workflow Platform.
Looking over SP2013's Boundaries and Limitations I see that the total workflow associations per site is limited to 1799 and being a boundary it is a static limit (actually a limit within the Service Bus that WF uses).
Does this apply only to workflows that are running in the 2013 Platform?
Is the document using "site" as in SPSite or is this a limitation on the number of SPWebs with a workflow association?
Is the limitation 1799 instances of the same workflow or of all workflows running on the container?
What happened to the SP2010 Boundaries and limits? If these limitations are for the 2013 Workflow Platform only then are the limitations for the 2010 Workflow Platform the same as they were in 2010? EDIT: I discovered that these settings were not published
in the 2010 edition.
Thank you!
Love them all...regardless. - Buddha

Hi,
Workflow for SharePoint 2013 is on different platform with SharePoint 2010.
In SharePoint 2013, the Service Bus supports a maximum of 1,799 subscriptions per scope. This maximum value includes the sum of both published and unpublished associations. This is in boundary limit type which cannot be exceeded by design.
Please refer to the link below for workflow limit in SharePoint 2013:
http://technet.microsoft.com/en-us/library/cc262787(v=office.15).aspx#Workflow
Here is an article for SharePoint 2013 workflow fundamentals which might be help to understanding:
http://msdn.microsoft.com/en-us/library/office/jj163181(v=office.15).aspx
Please download document for Capacity planning for Microsoft SharePoint Server 2010 via:
http://www.microsoft.com/en-us/download/details.aspx?id=21307
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected] .
Rebecca Tu
TechNet Community Support

Report for Number of invoice per vendor with amount

Hi All,
is there any standard SAP report we have which provide us number of invoices and amounts invoiced per vendor for a given time period.
Amit.

Hi amit
I have the same requirement
"The requirement is to view POs related to invoices per vendor""
Can you suggest me a solution
Please help
Regards
Shanker

Total Settlement Value field not getting populated in IW38 Transaction

Dear all PMCS group Members,
I have a list of Maintenance Orders on which Actual Costs are posted and also periodic settlements done before TECO. When i list these Maintenance Orders in IW38 transaction the system is bringing in the values in Total Actual Costs column but not the Settlement values in Total settlement column which i need to cross check before i do mass TECO.
Your help will be greatly appreciated.
regards,
rajaraman.

Dear Rajaraman,
You can see the Total Settlement values by using tcode IW38.
---> Goto IW38
---> Execute the Report for selected Orders
---> Click on the Current Tab or Press CTRL+F8
---> Select the Column of Total Settlements and Actual Settlements
---> Click on the Save Button... it will ask you to enter the Layout... Enter it and hit Enter
Your Required Fields will be Displayed.
Regards
BK

Total PO value per vendor

Similar Messages

Maybe you are looking for