Validation to check a field in Purchase Order.

Dear friends ,
Could we create an Validation to check a field in tcode ME21N, and this validation must check if field (header) is empty if yes when SAVE send error message"You could not create PO without release strategy , please contact IT area! "
Rule to check it.
Tcode ME21N
if field EKKO-FRGSX or EKKO-FRGKE without value when Saving document so send an error message as discribed above not allowing user to save and create PO.
Best regards
Ale

hi Amams
check this link
Adding Fields to Sales order
i think it may give u some idea
Regards,
Naveen

Similar Messages

Make short text field in Purchase order creation only display..

Sir,
Yeah my requirement is quite unusual, but such is the situation.
I want to make the short text field in purchase order creation "only disply". what is happening is that user while creating PO is able to change the text of material in short text column. I want to make it only for display.
Can it done on document type level, since for service type, and Text type of account assignment cat, only text field is filled up. so how to do it.
Please assist...
Rahul

Dear Rahul,
If you want to have the short text display only for standard item but not service item, you may check below customizing.
Transaction SPRO:
MM-PUR-PO
-> Define screen layout at document level
Field Selection group: Basic Data, Item
Field Selection Key: PT0F Standard item purchase order
Field: Short text -> set as display
Hope this help.
Ian Wong Loke Foong

PR to be made mandatory field in Purchase Order

Hello,
PR to be made mandatory field in Purchase Order.
How i can do this in SAP ?
Regards
Rahul

Hi,
First check your PO document type which you want to make PR number field as mandatory in ME21N.
Then Goto -> SPRO- Material Management - Purchase order- define document type for Purchase order - E.g NB- check the field selection assignment ( NBF)
Next,
Goto - Define screen layout at document level ( t.code OMF4) SELECTION GROUP Reference data, item and under Field selection key as NBF.
Field name - Purchase Requisition as Required entry with flagged check box.
Now in purchase order for the choose document type NB=PO the PR field as required entries.
System will allow to create PO only with reference to PR.
Thanks
Thiru

Drill down of purchase request number field in Purchase order

Hi, We need Drill down of purchase request number field in Purchase order. Please help.

Hi
In VOV8 as far as i understood by your query you are asking about the following :
Enter Purchase Order number - This indicator checks for the purchase order number and if you dont enter the purchase order number then system will consider the sales document number as purchase order number
Check Purchase order number - If you check then system will check wheather the purchase order number existed or not for this sales document type
Regards
Srinath

Authority check on Creation of Purchase order usin badi BBP_ITEM_CHECK_BADI

hi all,
i have to apply authority checks on creation of Purchase order and shopping cart in SRM using badi BBP_ITEM_CHECK_BADI.
i have applied checks on creation of shopping cart using this badi which have some filters but how to apply on purchasing order using BBP_ITEM_CHECK_BADI.

hi,
You can use the BBP_DOC_CHECK_BADI.
BR,
Disha.
Pls rewar points for useful answers.

ERS field in Purchase Order Line detail (Invoice Tab)

Hi ... I was trying to figure out the priorities for ERS field in Purchase order ...
What i could simulate is ...
Case 1
In case Vendor master has ERS = YES but in info record ( for vendor and material) NO ERS is defined.
Then ERS field will get appeared in PO LINE detail with value NO (not set)
Case 2
In case Vendor master has ERS = No but in info record (for vendor and material) ERS is set.( NO ERS = not set)
Then ERS field will not get appeared in PO LINE detail
Case 3
In case Vendor master has ERS = YES and in info record (for vendor and material) ERS is set.( NO ERS = not set)
Then ERS field will get appeared in PO LINE detail with ERS = YES
Here I am doubtful about case 2 .... I believe info record should always have priority over vendor , but system is not behaving as per expectation.
Could u pls tell me the exact conditions when ERS field will not appeared and if appeared from where it will pick the default values in PO LINE details
Regards
SANDEEP

the info record has precedence.
The bad thing is, that this field is , contrary to other field that appear in vendor and info record, has a negative meaning.
ERS field name in vendor is auto eval GR settlement,
while in info record it is : No ERS.
lets do an example:
V=vendor
I = Info record
P = purchase order
X = box selected
N = box not selected
so we can have this 4 cases:
VIP
XNX
XXN
NXN
NNN
The 3rd case NXN does not really make any sense.

Implementation Of Badi ME_GUI_PO_CUST for adding fields in Purchase Order

Hi All
I am implementing BADI ME_GUI_PO_CUST / ME_PROCESS_PO_CUST to add additional fields in Purchase Order.
The implementation of the BADI ie the Subscreen of the fields to be added appears in transaction ME23N but it does not appear in the transaction ME22N and ME21N.
Can anyone help me on this.
Thanx.
Moderator message - Duplicate post locked
Edited by: Rob Burbank on Jul 10, 2009 12:10 PM

check the answer
[New tabs added by Badi ME_GUI_PO_CUST not seen in ME21N and ME22N;
bye

Prevent unauthorised changing of 'Ship to' field of Purchase order

Hi experts
I am trying to prevent users from changing 'Ship to' field of Purchase Order without authorisation. OPOR.Address2
I am thinking to do this I should use a Stored Procedure which cause error if a condition is not met?
First I am trying to prevent any change of this field:
SP attempt:
--No changing of ship to address on PO
IF @object_type = '22' AND @transaction_type IN ('U','A')
BEGIN
IF EXISTS (SELECT T0.Address2 FROM dbo.OPOR T0 WHERE T0.Address2 <> (SELECT T1.CompnyAddr FROM dbo.OADM T1) AND T0.Address2 = @list_of_cols_val_tab_del)
SELECT @error = 1, @error_message = N'Direct shipment requires authorisation'
END
The above does not work - please can someone assist?
If there is better way to achieve my required outcome please advise me.
Thanks
Karen

Hi,
Try this:
IF @object_type = '22' AND @transaction_type IN ('U','A')
BEGIN
IF EXISTS (SELECT T0.[Docentry] FROM OPOR T0 WHERE T0.[Address2] <> ( select T0.[CompnyAddr] from OADM T0) AND T0.docentry = @list_of_cols_val_tab_del)
SELECT @error = 1, @error_message = N'Direct shipment requires authorisation'
END
Thanks & Regards,
Nagarajan

Purchase Req as mandatory field at Purchase Order

Hi Gurus,
I have the next problem:
I'm trying to put purchase requisition as mandatory field at purchase order.
At img i made the following steps:
Materials Management > Purchasing > Purchase Order > Define screen layout at document level
I sellected the screen layout that I want to change
At 'reference data, item' I sellected 'purchase requisition' as 'reqd. entry'.
Next I try to do a PO and it doesn't work...
Anyone knows why?
Regards
LR

Force buyers to create Purchase Order with ref. to a Pur. Req., Quotation or Pur. Ord.
Transaction OMET
Create a new entry, give it a name and tick :-
Ref. to PReq
Ref. to P.O.
Ref. to quotation
Next, you've got to associate via SU01
Click Parameters, insert a new parameter id EFB to the authorization code.
Type in Parameters value you want e.g. XX
You have to assign the control for ALL the SAP buyers via thier SAP users id.
Logoff and login again. Then try to create a Purchase Order without a reference.
Source link: http://www.academictutorials.com/sap-mm/sap-mm-configuration-tips.asp

Adding a new check box in change purchase order screen

Hi
I have to add one custom field a check in the screen for change purchase order in EBP.
We are using ITS.
Kindly advice.
Thanks and Regards
Manoj

Hello Manoj,
you can define Customer Fields (CUF) at header, item, accounting level on any document type (including PO).
Adding seach fields acts as old ABAP method of table append, i.e. those fields are stored in standard SRM tables. So you can process your own logic and checks against those fields.
There is a BADI to control the display or not, the input or not, the default or input values.
There is a BADI to control the ergonomy of CUF (by default they are added one after the other after standard fields).
There have been many posts about CUF and linked OSS notes explaining own it works and which includes to use.
Rgds
Christophe

Linking field between purchase order and inbound delivery

Hi
I have to enter some data in the purchase order and it has to automatically updated in the inbound delivery.
For eg: if we enter bill of ladding number in purchase order, it has to get automatically populated in inbound delivery.
Regards
shaker

Hi,
Is the example provided by you, just for example purpose or is that the field you want to copy? If that is the field you want to copy from PO to Inbound document, then how would you know the BoL no. / details at the time of PO creation?
However if it is just an example & you want to copy some other field, then you might want to evaluate the below exits:
MM06E001 User exits for EDI inbound and outbound purchasing documents
LMELA010 Inbound shipping notification: Transfer item data from IDOC
Check with your abaper.
Regards,
Vivek

Defining condition according to the new field of purchase order?(urgent!!!)

hi all,
i added new field to the table ekko (screen me21n). and now i want to define pricing conditions of purchase order according to this field. i create table and access sequence for condition type and define a condition record. but when i am creating a purchase order, the condition is not found. i must define a relationship between new field of ekko and condition type. do i have to write a routine for this. if yes how? or what can i do?

if you want to determine your price based on the field on the PO then
1) field should be availble at PO level
2) add that field in your condition table (if not available at acondition table selection then usse the oss note 39462
3) define the access seq. based on this table
4) create condition type and add this access seq in the condition
5) add this condition in your pricing procedure (make sure that for this condition Man, Mdt or Stat check box is not checked in Pricing procedure)
6) maintian this condition for price in the tcode MEK1
if oyu done all this then when you create the PO and it match all the criteria of your condition table then system will pull this condition

7 character field to purchase order ,customer number

please help
1)
data : kunnr1(7) type c.
data : kunnr like kna1-kunnr.
kunnr1 has only field length 7 and it is of type character.
kunnr is a sap field.
everytime i need to fill the data from the field kunnr1 to sap kunnr and pass to bdc .
suppose kunnr1 = 1930903 ie 7 characters .
and in sap shall i simply copy like this
kunnr = kunnr1. " will this work
or
concatnate '000' kunnr1 to kunnr.
or
any other one .
2)same with the purchase order number.
data : po(7) type c.
dat : bstdk type vbak-bstdk.
po = asdefgr
bsdtk = po
or
concatenate '' po to bsdtk.
if i assign value from po to bsdtk will at end command will work on bstdk?
example
loop at itab into workarea.
at last bsdtk." i need this to work so tell me how to assign the value from po to bsdtk
endloop.

i checked the customer number in sap system,
in the sales order it is stored as 1277494
i checked in vbak table and it is stored as 1277494and rest blank spaces.
i checked in kna1 table , the same kunnr is stored as 0001277494.
why is this difference?
so i need to use the 'CONVERSION_EXIT_ALPHA_INPUT' for kunnr?
I checked for po but that is stored as a charater format and no need to add the leading zeros, is that right?
I used CONVERSION_EXIT_MATN1_INPUT for material do i need to use CONVERSION_EXIT_ALPHA_INPUT for material also?
thank you for the solutions given.

Regarding fields for Purchase order

can any body help what are the fields reqiured to develop a p.o report to display the change date,user name,time,p.o name and vendor code.

Hi
see the sample report for the fieldnames and other logic
all the PO info is there here.
*& Report ZMM_PO_REPORT
REPORT ZMM_PO_REPORT message-Id yb
       NO STANDARD PAGE HEADING
       LINE-COUNT 60(1)
       LINE-SIZE 230.
       D A T A B A S E T A B L E S   D E C L A R A T I O N
TABLES: lfa1,           " Vendor Master
        t161,           " PO Doc Types
        t024,           " Purchase Groups
        ekko.           " PO Header
               T Y P E S D E C L A R A T I O N S
Purchase Orders Main Structure
TYPES: BEGIN OF s_po,
        ebeln TYPE ebeln,           " PO No.
        ebelp TYPE ebelp,           " PO Item
        bstyp TYPE bstyp,           " PO Category
        bukrs TYPE bukrs,           " Company Code
        bsart TYPE bbsrt,           " PO Type
        lifnr TYPE lifnr,           " Vendor No
        ekgrp TYPE bkgrp,           " Purchase Group
        waers TYPE waers,           " Currency
        bedat TYPE etbdt,           " PO Date
        txz01 TYPE txz01,           " Material Text
        werks TYPE ewerk,           " Plant
        lgort TYPE lgort_d,         " Storage Location
        matkl TYPE matkl,           " Material Group
        menge TYPE bamng,           " PR Quantity
        meins TYPE bamei,           " UOM
        bprme TYPE bbprm,           " Price Unit
        netpr TYPE netpr,           " Net price
        peinh TYPE peinh,           " Price Unit UOM
        pstyp TYPE pstyp,           " Item Category
        knttp TYPE knttp,           " Account Assignment Category
       END OF s_po.
Purchase Orders History Structure
TYPES: BEGIN OF s_account,
        ebeln TYPE ebeln,           " PO No.
        ebelp TYPE ebelp,           " PO Item
        gjahr TYPE mjahr,           " Fiscal Year
        belnr TYPE mblnr,           " PO Invoice No
        menge TYPE menge_d,         " PR Quantity
        wrbtr TYPE wrbtr,           " Price in Local Currency
        dmbtr TYPE dmbtr,           " Price in Foreign Currency
        waers TYPE waers,           " Currency
        shkzg TYPE shkzg,           " Dr/Cr Indicator
       END OF s_account.
Purchase Orders History Structure(Item Sum)
TYPES: BEGIN OF s_inv_sum,
        ebeln TYPE ebeln,           " PO No.
        ebelp TYPE ebelp,           " PO Item
        menge TYPE menge_d,         " PR Quantity
        wrbtr TYPE wrbtr,           " Price in Foreign Currency
        waers TYPE waers,           " Currency
       END OF s_inv_sum.
Purchase Orders Main Structure
TYPES: BEGIN OF s_rep,
        lifnr TYPE lifnr,           " Vendor No
        ebeln TYPE ebeln,           " PO No.
        ebelp TYPE ebelp,           " PO Item
        bstyp TYPE bstyp,           " PO Category
        bsart TYPE bbsrt,           " PO Type
        ekgrp TYPE bkgrp,           " Purchase Group
        waers TYPE waers,           " Currency
        bedat TYPE etbdt,           " PO Date
        txz01 TYPE txz01,           " Material Text
        werks TYPE ewerk,           " Plant
        lgort TYPE lgort_d,         " Storage Location
        matkl TYPE matkl,           " Material Group
        menge TYPE bamng,           " PR Quantity
        meins TYPE bamei,           " UOM
        bprme TYPE bbprm,           " Price Unit
        netpr TYPE netpr,           " Net price
        peinh TYPE peinh,           " Price Unit UOM
        pstyp TYPE pstyp,           " Item Category
        knttp TYPE knttp,           " Account Assignment Category
        name1 TYPE name1,           " Plant
        orewr TYPE netpr,           " To be Invoiced Price
        curr TYPE waers,           " Inv Doc Currency
       END OF s_rep.
           D A T A D E C L A R A T I O N S
DATA: gv_title1 TYPE sylisel,            " Report title
      gv_dial.                           " Color flag
            C O N S T A N T S D E C L A R A T I O N S
CONSTANTS: c_x                VALUE 'X',   " Flag X
           c_h                VALUE 'H',   " Debit
           c_vgabe TYPE vgabe VALUE '2'.   " Transaction Type
     I N T E R N A L T A B L E S D E C L A R A T I O N S
DATA: i_po    TYPE STANDARD TABLE OF s_po WITH HEADER LINE,
                             " Purchase Order
      i_inv   TYPE STANDARD TABLE OF s_inv_sum WITH HEADER LINE,
                                     " PO Invoice Values
      i_rep   TYPE STANDARD TABLE OF s_rep WITH HEADER LINE,
                                 " PO Invoice Values
      i_ekbe TYPE STANDARD TABLE OF s_account WITH HEADER LINE.
                           " PO Invoice Values
                 S E L E C T I O N S C R E E N                      *
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECT-OPTIONS: s_lifnr FOR lfa1-lifnr MATCHCODE OBJECT kred,
                s_ebeln FOR ekko-ebeln MATCHCODE OBJECT mekk,
                s_bsart FOR t161-bsart,
                s_ekgrp FOR t024-ekgrp,
                s_bedat FOR ekko-bedat.
SELECTION-SCREEN END OF BLOCK b1.
                  I N I T I A L I Z A T I O N                        *
INITIALIZATION.
              A T S E L E C T I O N - S C R E E N                   *
AT SELECTION-SCREEN.
Validate the screen fields
PERFORM validate_screen.
               S T A R T - O F - S E L E C T I O N                   *
START-OF-SELECTION.
Fetch main data
PERFORM fetch_data.
               T O P - O F - P A G E                                 *
TOP-OF-PAGE.
Header of the List
PERFORM header.
               E N D - O F - P A G E                                 *
Footer
END-OF-PAGE.
ULINE.
               E N D - O F - S E L E C T I O N                       *
END-OF-SELECTION.
Display the Report Output data
PERFORM display_data.
At Line-Selection
AT LINE-SELECTION.
When double clicked on EBELN display the details of Purchase Doc
PERFORM line_sel.
*&      Form validate_screen
Validation of Selection Screen fields
FORM validate_screen .
Validation of Vendor Number
CLEAR lfa1-lifnr.
IF NOT s_lifnr[] IS INITIAL.
    SELECT lifnr UP TO 1 ROWS
        INTO lfa1-lifnr
        FROM lfa1
        WHERE lifnr IN s_lifnr.
    ENDSELECT.
    IF sy-subrc <> 0.
      MESSAGE e000 WITH 'Invalid Vendor'(002).
    ENDIF.
ENDIF.
Validation of PO Number
CLEAR ekko-ebeln.
IF NOT s_ebeln[] IS INITIAL.
    SELECT ebeln UP TO 1 ROWS
        INTO ekko-ebeln
        FROM ekko
        WHERE ebeln IN s_ebeln.
    ENDSELECT.
    IF sy-subrc <> 0.
      MESSAGE e000 WITH 'Invalid Document Number'(003).
    ENDIF.
ENDIF.
Validation of PO Document Type
CLEAR t161-bsart.
IF NOT s_bsart[] IS INITIAL.
    SELECT bsart UP TO 1 ROWS
        INTO t161-bsart
        FROM t161
        WHERE bsart IN s_bsart.
    ENDSELECT.
    IF sy-subrc <> 0.
      MESSAGE e000 WITH 'Invalid Purchase Document Type'(004).
    ENDIF.
ENDIF.
Validation of Purchasing Group
CLEAR t024-ekgrp.
IF NOT s_ekgrp[] IS INITIAL.
    SELECT ekgrp UP TO 1 ROWS
        INTO t024-ekgrp
        FROM t024
        WHERE ekgrp IN s_ekgrp.
    ENDSELECT.
    IF sy-subrc <> 0.
      MESSAGE e000 WITH 'Invalid Purchasing Group'(005).
    ENDIF.
ENDIF.
ENDFORM.                    " validate_screen
*&      Form fetch_data
Fetching the PO related data from Database Tables
FORM fetch_data .
CLEAR i_po.
REFRESH i_po.
SELECT a~ebeln            " PO No.
         b~ebelp            " PO Item
         a~bstyp            " PO Category
         a~bukrs            " Company Code
         a~bsart            " PO Type
         a~lifnr            " Vendor No
         a~ekgrp            " Purchase Group
         a~waers            " Currency
         a~bedat            " PO Date
         b~txz01            " Material Text
         b~werks            " Plant
         b~lgort            " Storage Location
         b~matkl            " Material Group
         b~menge            " PR Quantity
         b~meins            " UOM
         b~bprme            " Price Unit
         b~netpr            " Net price
         b~peinh            " Price Unit UOM
         b~pstyp            " Item Category
         b~knttp            " Account Assignment Category
    INTO TABLE i_po
    FROM ekko AS a JOIN ekpo AS b
    ON a~ebeln = b~ebeln
    WHERE a~ebeln IN s_ebeln AND
          a~lifnr IN s_lifnr AND
          a~ekgrp IN s_ekgrp AND
          a~bsart IN s_bsart AND
          a~bedat IN s_bedat.
SORT i_po BY ebeln ebelp.
break-point.
IF NOT i_po[] IS INITIAL.
Fetch the PO History/Invoice Details from EKBE Table
    CLEAR i_ekbe.
    REFRESH i_ekbe.
    SELECT ebeln           " PO No.
           ebelp           " PO Item
           gjahr           " Fiscal Year
           belnr           " PO Invoice No
           menge           " PR Quantity
           wrbtr           " Price in Local Currency
           dmbtr           " Price in Foreign Currency
           waers           " Currency
           shkzg           " Dr/Cr Indicator
     INTO TABLE i_ekbe
     FROM ekbe
     FOR ALL ENTRIES IN i_po
     WHERE ebeln = i_po-ebeln AND
           ebelp = i_po-ebelp AND
           vgabe = c_vgabe.
    IF sy-subrc = 0.
      SORT i_ekbe BY ebeln ebelp.
      LOOP AT i_ekbe.
        IF i_ekbe-shkzg = c_h.
          i_ekbe-wrbtr = i_ekbe-wrbtr * -1.
        ENDIF.
        MODIFY i_ekbe.
      ENDLOOP.
break-point.
Sum up the Item wise Invoice totals
      LOOP AT i_ekbe.
        AT END OF ebelp.
          READ TABLE i_ekbe INDEX sy-tabix.
          SUM.
          MOVE-CORRESPONDING i_ekbe TO i_inv.
          APPEND i_inv.
        ENDAT.
        CLEAR i_inv.
      ENDLOOP.
      SORT i_inv BY ebeln ebelp.
        break-point.
    ENDIF.
ENDIF.
Move the Vendor Name and Invoice Values to I_rep Internal Table
LOOP AT i_po.
    MOVE-CORRESPONDING i_po TO i_rep.
    CLEAR i_inv.
    READ TABLE i_inv WITH KEY ebeln = i_po-ebeln
                              ebelp = i_po-ebelp.
    IF sy-subrc = 0.
      i_rep-orewr = ( i_po-menge - i_inv-menge ) * i_po-netpr.
      i_rep-curr = i_inv-waers.
    ELSE.
      i_rep-orewr = i_po-menge * i_po-netpr.
      i_rep-curr = i_po-waers.
    ENDIF.
break-point.
Get the Vendor Name
    CLEAR lfa1-name1.
    SELECT SINGLE name1 FROM lfa1 INTO lfa1-name1
      WHERE lifnr = i_po-lifnr.
    IF sy-subrc = 0.
      i_rep-name1 = lfa1-name1.
    ENDIF.
    APPEND i_rep.
    CLEAR i_rep.
      break-point.
ENDLOOP.
SORT i_rep BY lifnr ebeln ebelp.
DELETE i_rep WHERE orewr LE 0.
break-point.
ENDFORM.                    " fetch_data
*&      Form display_data
Display the Report Output data
FORM display_data .
DATA: lv_flag,               " New Flag
        lv_rec TYPE i.         " No of Records
CLEAR lv_rec.
IF i_rep[] IS INITIAL.
    MESSAGE e000 WITH 'No Data found'(022).
ELSE.
    LOOP AT i_rep.
Toggle Color
      PERFORM toggle_color.
      IF lv_flag <> space.
        NEW-LINE.
      ENDIF.
At New Purchase Document
      AT NEW ebeln.
        WRITE:/1 sy-vline, 2(10) i_rep-ebeln INTENSIFIED OFF.
        lv_flag = c_x.
        lv_rec = lv_rec + 1.
      ENDAT.
      WRITE: 1 sy-vline,
            12 sy-vline,13(4)   i_rep-bsart,
            17 sy-vline,18(10) i_rep-lifnr,
            28 sy-vline,29(35) i_rep-name1,
            64 sy-vline,65(4)   i_rep-ekgrp,
            69 sy-vline,70(10) i_rep-bedat,
            80 sy-vline,81(5)   i_rep-ebelp,
            86 sy-vline,87(40) i_rep-txz01,
           127 sy-vline,128(9) i_rep-matkl,
           137 sy-vline,138(1) i_rep-pstyp,
           139 sy-vline,140(1) i_rep-knttp,
           141 sy-vline,142(4) i_rep-werks,
           146 sy-vline,147(4) i_rep-lgort,
           151 sy-vline,152(13) i_rep-menge UNIT i_rep-meins,
           165 sy-vline,166(3) i_rep-meins,
           169 sy-vline,170(15) i_rep-netpr CURRENCY i_rep-waers,
           185 sy-vline,186(4) i_rep-waers,
           190 sy-vline,191(5) i_rep-peinh,
           196 sy-vline,197(4) i_rep-bprme,
           201 sy-vline,202(15) i_rep-orewr CURRENCY i_rep-curr,
           217 sy-vline,218(4) i_rep-curr,
           222 sy-vline,223(7) i_rep-bstyp centered,
           230 sy-vline.
      NEW-LINE.
      hide: i_rep-ebeln.
    ENDLOOP.
    ULINE.
    FORMAT COLOR OFF.
    WRITE : /2 'Total Number of Purchasing Documents:'(025) COLOR 3,
                lv_rec COLOR 3.
ENDIF.
ENDFORM.                    " display_data
*&      Form header
Write the Report Header
FORM header .
FORMAT RESET.
header
WRITE:/1(230) 'LIST OF PURCHASE DOCUMENTS PER VENDOR'(006) CENTERED.
SKIP.
FORMAT COLOR COL_HEADING.
ULINE.
WRITE:/1 sy-vline,2(10)   'Pur.Doc.No'(006) CENTERED,
        12 sy-vline,13(4)   'Type'(007),
        17 sy-vline,18(10) 'Vendor'(008) CENTERED,
        28 sy-vline,29(35) 'Name'(009) CENTERED,
        64 sy-vline,65(4)   'PGrp'(010) CENTERED,
        69 sy-vline,70(10) 'Doc.Date'(012) CENTERED,
        80 sy-vline,81(5)   'Item'(011),
        86 sy-vline,87(40) 'Material Short Text'(024) CENTERED,
       127 sy-vline,128(9) 'Mat.Group'(013),
       137 sy-vline,138(1) 'I',
       139 sy-vline,140(1) 'A',
       141 sy-vline,142(4) 'Plnt'(014),
       146 sy-vline,147(4) 'SLoc'(015),
       151 sy-vline,152(13) 'Quantity'(016) CENTERED,
       165 sy-vline,166(3) 'UoM'(017),
       169 sy-vline,170(15) 'Net Value'(018) CENTERED,
       185 sy-vline,186(4) 'Curr'(019),
       190 sy-vline,191(5) 'Per'(020),
       196 sy-vline,197(4) 'Unit'(021),
       201 sy-vline,202(15) 'To be Invoiced'(023) CENTERED,
       217 sy-vline,218(4) 'Curr'(019),
       222 sy-vline,223(7) 'Doc.Cat'(026),
       230 sy-vline.
ULINE.
ENDFORM.                    " header
*&      Form toggle_color
This routine alters the color of the records in the list
FORM toggle_color.
IF gv_dial = space.
    FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
    gv_dial = c_x.
ELSE.
    FORMAT COLOR 1 INTENSIFIED OFF.
    CLEAR gv_dial.
ENDIF.
ENDFORM.                    " toggle_color
*&      Form LINE_SEL
*When double clicked on EBELN field display the details of Purchase Doc
FORM line_sel.
CASE sy-lsind.
    WHEN '1'.
      DATA: lv_field(20),
            lv_value(10),
            lv_bstyp like i_rep-bstyp.
      clear: lv_bstyp,lv_value, lv_field.
      GET CURSOR FIELD lv_field VALUE lv_value.
      IF lv_field = 'I_REP-EBELN'.
        IF NOT lv_value IS INITIAL.
          READ LINE sy-index FIELD VALUE i_rep-bstyp
                                   INTO lv_bstyp.
         READ CURRENT LINE FIELD VALUE i_rep-bstyp INTO lv_bstyp.
          if lv_bstyp = 'F'.
            SET PARAMETER ID 'BES' FIELD lv_value.
            CALL TRANSACTION 'ME23N' AND SKIP FIRST SCREEN.
          elseif ( lv_bstyp = 'K' or lv_bstyp = 'L' ).
            SET PARAMETER ID 'VRT' FIELD lv_value.
            CALL TRANSACTION 'ME33' AND SKIP FIRST SCREEN.
          elseif lv_bstyp = 'A'.
            SET PARAMETER ID 'ANF' FIELD lv_value.
            CALL TRANSACTION 'ME43' AND SKIP FIRST SCREEN.
          endif.
        ENDIF.
      ENDIF.
ENDCASE.
ENDFORM.                    " line_sel
Regards
Anji

Manufacturer field in Purchase Order - display only

Does anyone know of a way (config or user exit) to make the field MFRNR on the purchase order item detail (Material Data tab) as an optional entry rather than dispaly only?
I checked in the screen layout configuration for the screen sequence NBF (which is what we use) and I didn't see it as a changeable/updateable field.
We are on ECC 6.0
Thanks,
Gina Feldner

Gina Feldner,
May be you can check for ME21N level also,
Regards,
Bhima

Validation to check a field in Purchase Order.

Similar Messages

Maybe you are looking for