Skip to Content
author's profile photo
Former Member

Enhacement in PO header Text

Hi Friends,

I want to make certain fields of Header Text in transaction ME21N as mandatory so that whenever a user creates a PO & if he leaves those header text blank(doesn't fill) the while saving/checking the PO system should display some error message.

Solutions will be rewarded with good reward points,

Thanks for your time,


Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • author's profile photo
    Former Member
    Posted on Sep 27, 2007 at 01:03 PM


    You can do it by using a User exit or BAPI for a PO at header level

    But there will be no direct field for header.

    Texts are stored with 4 parameters like OBJECT,ID,OBJECTNAME and LANGUAGE in STXH table

    so you have to check this table with OBJECT =EKKO and OBJECTNAME = PO number , whether a text exists or not.

    Use the BAPI ME_PROCES_PO_CUST with the method PROCESS_HEADER

    or some user exit like

    MM06E001/002/003/004/005 etc and write the code



    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Former Member
    Posted on Sep 28, 2007 at 03:22 AM

    USER EXIT,295199,sid63_gci982756,00.html

    Transaction Code - ME21N Create Purchase Order

    Exit Name Description

    LMEDR001 Enhancements to print program

    LMELA002 Adopt batch no. from shipping notification when posting a GR

    LMELA010 Inbound shipping notification: Transfer item data from IDOC

    LMEQR001 User exit for source determination

    LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt

    LWSUS001 Customer-Specific Source Determination in Retail

    M06B0001 Role determination for purchase requisition release

    M06B0002 Changes to comm. structure for purchase requisition release

    M06B0003 Number range and document number

    M06B0004 Number range and document number

    M06B0005 Changes to comm. structure for overall release of requisn.

    M06E0004 Changes to communication structure for release purch. doc.

    M06E0005 Role determination for release of purchasing documents

    ME590001 Grouping of requsitions for PO split in ME59

    MEETA001 Define schedule line type (backlog, immed. req., preview)

    MEFLD004 Determine earliest delivery date f. check w. GR (only PO)

    MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.

    MEQUERY1 Enhancement to Document Overview ME21N/ME51N

    MEVME001 WE default quantity calc. and over/ underdelivery tolerance

    MM06E001 User exits for EDI inbound and outbound purchasing documents

    MM06E003 Number range and document number

    MM06E004 Control import data screens in purchase order

    MM06E005 Customer fields in purchasing document

    MM06E007 Change document for requisitions upon conversion into PO

    MM06E008 Monitoring of contr. target value in case of release orders

    MM06E009 Relevant texts for "Texts exist" indicator

    MM06E010 Field selection for vendor address

    MMAL0001 ALE source list distribution: Outbound processing

    MMAL0002 ALE source list distribution: Inbound processing

    MMAL0003 ALE purcasing info record distribution: Outbound processing

    MMAL0004 ALE purchasing info record distribution: Inbound processing

    MMDA0001 Default delivery addresses

    MMFAB001 User exit for generation of release order

    MRFLB001 Control Items for Contract Release Order

    AMPL0001 User subscreen for additional data on AMPL

    No of Exits: 35

    Rewards if useful.........


    Add comment
    10|10000 characters needed characters exceeded