PR Header TEXT Mandatory

Hi All
Whether  is it possible to make Header Text mandatory in a PR during PR creation.
If Yes , How? any exit or any BADI
Thanks in advance ,
Rajesh

Please check this answered link. Header text mandatory is possible as its maintained in my current system.
To make PR header text as Mandatory

Similar Messages

  • Header text mandatory in Purchase requisition

    Hello,
    Ho do i make the header text mandatory in my Purchase Requisition ?
    Regards
    Kasi

    Not Possible in Standard SAP. You Cannot Set the Header text field Mandatory for PR.
    Use Enhancement on Purchase Requisition MEREQ001
    You Can check Enhancements in SMOD by Packages

  • Make Document header text mandatory

    Hi,
    I want make Document header text mandatory at document parking level. Please suggest me which user exit I can use for that. Please help me.
    Rgds,
    Hemant Maurya

    Hello,
    There is nothing like make header text mandatory at the time of parking.
    However, you can make header text mandatory at the time of posting.
    In OBA7 - document type, make the document header text field as mandatory - last two check boxes.
    Regards,
    Ravi

  • Text mandatory in vf01

    Dear All,
    I want to make header text mandatory in VF01.
    Pls suggest.
    Nikhil

    Dear Nikhil,
    You don't have incompletion procedure process for the billing, so you can try with this option,
    You do the text determination for the deliveries you define and maintain the Text ID in the delivery text procedure maintain access sequence and other settings in the delivery level.
    You put that Text id in the incompletion procedure of the deliveries,now system will not allow to do the PGI with out entering the text for that text id.
    You can copy that text to the billing header text through check the Delivert text check box in the billing document detail screen.Go to VOFA transaction then select your billing document type then go in to the details here you can find the field Delivert text check box in the top most bottom of the screen.
    Do the text determination for billing also with define and maintain same text ID which you maintain in the delivery.
    Now when you create billing with reference to that delivery text will be copied to the billing document automatically.
    I hope this will help you,
    Regards,
    Murali.

  • Header Text in Billing Document MANDATORY

    HI Gurus,
       Can you please let me know if we can make the Header text field in the Billing Document---> Header Level as mandatory. Is there any possibility to do that or not?
      Thankyou,
      Rakesh Tummala.

    Hi,
    Goto the Transaction code VOTXN and select the SALES DOCUMENT  HEADER radio button
    and goto the change mode inthe application tool bar
    Choose your text determination procedure as defined for Header
    and in the TEXT IDs in the text procedure in the control tab choose your TEXT ID and maintain the TEXT AS OBLIGATORY
    save it and now create the sales order and check the text .
    hope it clarifies your requirement
    thanks
    santosh

  • How we will maintian Header Text in Purchase Order Mandatory?

    Dear All,
    How we will maintian Header Text in Purchase Order Mandatory?Please suggest a Solution..
    Thanks,
    Raju

    hi
    in standard  it is not posible  u need to use User exit: EXIT_SAPMM06E_012 of enhancement MM06E005. check details with ABAPer
    Vishal...

  • Mandatory field - Header text and Reference field  for company code

    Hi
    In transaction code FB60, I want to make header text and reference field mandatory at the company code level.
    For one company code , the header text and the reference field should be made mandatory but for the other 8 company codes , those fields should not be mandatory.
    if I make the fields mandatory via the document type , then it will be applicable for all the company codes using the document type.
    thanks in advance
    Kind regards
    sap student

    Hi Chintan
    I have written the validation rule and it is working fine.
    Thanks
    kind regards
    sap student

  • Purchase order Header text as mandatory text

    Hi,
    We would like to set some of the PO header text as mandatory text while creating the PO.
    Is there a way to configure this?
    thanx
    Miri

    Hi
    Not possible through configuration.
    Last time when I faced with this requirement, I used User exit: EXIT_SAPMM06E_012 of enhancement MM06E005.
    You can use BADI ME_PROCESS_PO_CUST to trigger an error message. Need abap developer for this.
    Best regards
    Ramki

  • Header text field mandatory

    Hi all,
    how can we make document header text manditory while doing GR
    regards
    Rakesh

    At text determination, shipment header-->text procedure, you can make your text type as mandatory.
    Or if you want to take previous document's text then create access sequence.

  • To make PR header text as Mandatory

    hi Gurus
              In ME52N (ie.Purchase requestition) I want to make the Header text as mandotary field.Any User exit or BADI available?

    Please go thorugh below mentioned Badi's and user exits :
    ME_REQ_HEADER_TEXT   Copy Header Text: Enjoy Purchase Requisition(BADI)
    MEREQ001  Customers' Own Data in Purchase Requisition(User Exit)
    Hope some what helpful to you

  • How to Make Purchase Order TEXTS Mandatory

    Hi.........
                 I want to make some Purchase Order texts mandatory(for ex Header text) so that i should appear in PO Print and user should not be able to proceed unless he make an entry.
                                            Please help me out......
    Thanks

    Hi,
    In spro>mm>pur>po>define screen layout select filed selection AKTH Create for ref.data item make it
    required entry
    BR
    Diwakar

  • Header text in me21n

    Hi,
        i found one badi 'ME_PURCHDOC_POSTED'. my requirement is to make the header taxt, warranty text mandatory. For that can i write code here. what code i have to write over here. please help me.

    go through this ....
    DATA: wa_ltext     TYPE tline,
          current_line TYPE i,
          prev_line    TYPE i.
    LOOP AT ta_ltext WHERE tdline NE space.
      CASE ta_ltext-tdformat.
        WHEN '='.
          prev_line = sy-tabix - 1.
          READ TABLE ta_ltext INTO wa_ltext INDEX prev_line.
          IF sy-subrc = 0.
            CONCATENATE wa_ltext-tdline ta_ltext-tdline
                   INTO ta_ltext2-tdline.
            MODIFY ta_ltext2 INDEX current_line.
          ENDIF.
        WHEN OTHERS.
          ta_ltext2-tdline = ta_ltext-tdline.
          APPEND ta_ltext2.
          current_line = sy-tabix.
      ENDCASE.
    ENDLOOP.
    DATA:   BEGIN OF ttab OCCURS 0.
            INCLUDE STRUCTURE tline.
    DATA:   END OF ttab.
    DATA:   BEGIN OF tinlinetab OCCURS 0.
            INCLUDE STRUCTURE tline.
    DATA:   END OF tinlinetab.
    DATA: BEGIN OF thead.
            INCLUDE STRUCTURE thead.
    DATA: END OF thead.
    lv_objname = it_lips-posnr.
      CONCATENATE it_lips-vbeln lv_objname INTO lv_objname.
      PERFORM read_item_text1 USING lv_objname it_lips-vbeln.
    *&      Form  read_item_text1
          text
         -->P_LV_OBJNAME  text
         -->P_IT_LIPS_VBELN  text
    FORM read_item_text1  USING    P_OBJNAME
                                   P_IT_LIPS_VBELN.
      CLEAR : v_regcarr , v_intcarr ,
                v_reqdate , v_commdate.
      CLEAR: thead,it_likp-traty.
      REFRESH : ttab, tinlinetab.
      thead-tdid     = '0001'.
      thead-tdspras  = sy-langu.
      thead-tdname   =  p_objname.
      thead-tdobject = 'VBBP'.
      CALL FUNCTION 'READ_TEXT_INLINE'
        EXPORTING
          id              = thead-tdid
          inline_count    = 1
          language        = thead-tdspras
          name            = thead-tdname
          object          = thead-tdobject
        IMPORTING
          header          = thead
        TABLES
          inlines         = tinlinetab
          lines           = ttab
        EXCEPTIONS
          id              = 1
          language        = 2
          name            = 3
          not_found       = 4
          object          = 5
          reference_check = 6
          OTHERS          = 7.
      IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    Edited by: Ankur Sharma on Apr 30, 2008 12:31 PM

  • Fbcj "document header text"

    hi experts.
    i am using "fbcj" transaction code but i need an information about "document header text" area .
    when i save a document with fbcj transaction , this document's "document header text" is always empty. i have to enter some numbers in this area before the save document. how can i fix it?

    Hi,
    Please refer this link :
    is it possible to configure the reference-document date as mandatory -FBCJ
    Regards,
    Pramitha.

  • Doc. Header Text (BKTXT) in MB1C

    Hello Experts,
    Requirement is to copy 501 mvt type into a new mvt type & for the new one, the field Doc. Header Text (BKTXT) should be made mandatory in MB1C t-code.
    1)Whether any configuration available to achieve the same?
    2)If it can be done through some enhancements, then whats the BADI/BAPI/Field Exit/User Exit available?
    Please suggest.
    Regards
    Mahesh

    Hi Mahesh,
    There is an enhancement point in form OK-CODE_PRUEFEN in MM07MF00 which could be used.
    ENHANCEMENT-POINT OK-CODE_PRUEFEN_01 SPOTS ES_SAPMM07M.
    If you put your check in here you should be able to get the desired result.
    For future use, if you debug from the point where you want the check to occur you can normally find the enhancement points, or, identify where you can create an enhancement using an implicit enhancement point.
    Regards,
    John

  • LSMW - Direct Input - Sales order - Header Text

    Hello,
    I upload scheduling agreement with header text.  Upload is successful and I have seen the text from both front end and table STXH.  However, this field is set mandatory, and even it is uploaded, it is still shown on incompletion log.  Only when I manually make some change it passes the incompletion check.
    Here is what i have done In LSMW::
    BTEXHKOM                       Communication fields for maintaining text header
        Fields
            OLDNR                        Document and item number of the data in the external system
                                Source:  ZHEADER-OLDNR (QAD SO no.)
                                Rule :   Transfer (MOVE)
                                Code:    BTEXHKOM-OLDNR = ZHEADER-OLDNR.
    Caution: Source field is longer than target field
            LAISO                        Language according to ISO 639
                                Code:    BTEXHKOM-LAISO = 'EN'.
            TDID                         Text ID
                                Rule :   Constant
                                Code:    BTEXHKOM-TDID = 'ZTTR'.
           BTEXLKOM                       Communication fields for maintaining text lines
               Fields
                   OLDNR                        Document and item number of the data in the external system
                                       Source:  ZHEADER-OLDNR (QAD SO no.)
                                       Rule :   Transfer (MOVE)
                                       Code:    BTEXLKOM-OLDNR = ZHEADER-OLDNR.
    Caution: Source field is longer than target field
                   TXPARGRAPH                   Tag column
                                       Code:    BTEXLKOM-TXPARGRAPH = '/'.
                   TXLINE                       Text editor text line
                                       Source:  ZHEADER-ZTEXT1 (Title of transfer)
                                       Rule :   Transfer (MOVE)
                                       Code:    BTEXLKOM-TXLINE = ZHEADER-ZTEXT1.
    I put them under same structure ZHEADER together with other header fields in SA. Is there anything missing?
    Thanks in advance.
    Susan

    Hi all,
    Many thanks for the suggestions.  One of our expert developers got involved and provided the solution.
    In order to have item level text populate, the VBAP-PSTYV  (the sales document item category) field also needs to be populated.  The VBAP-PSTYV field value is dependent on the sales document type.  (Or, at least it is for the configuartion set up in my example)  The sales document type is VBAK-AUART.
    Stuart

Maybe you are looking for