Delivery date blank in PR (Purchase requisition)

[Former Member]

Dear All,

I have got a requirement that Delivery Date should be blank instead of sy-datum in Purchase Requisition (ME51N), so that user can enter his date .

I tried BAPI and user exits for PR, but the structures used there do not contain the Screen field EEIND. So I m unable to handle it.

Please suggest me what else i can do.

Thanks

-Harshita Saxena

[former_member201275]

Have you tried the enhancements:

LMEKO001

LMEKO002

[Former Member]

Resolved:

Enhancement spot created in :

Prg: SAPLMEREQ

include: LMEREQF15

Line : 265

Method : METHOD calculate_delivery_date.

ENHANCEMENT 1  ZSET_DEL_DATE.    "active version
" Code Segment Added by Sharitija Saxena on 10.3.2014
IF RE_LFDAT IS NOT INITIAL and sy-tcode = 'ME51N'.
   RE_LFDAT = ' '.
ENDIF.
" End of Code Segment
ENDENHANCEMENT.
*$*$-End:   (1)---------------------------------------------------------------------------------$*$*
   ENDMETHOD.                    "calculate_delivery_date

[Former Member]

Done same for PO:

Implemented badi : ME_PROCESS_PO_CUST

method : OPEN

METHOD if_ex_me_process_po_cust~open.
  
   DATA: lv_del TYPE char1 VALUE 'X'.
   lv_del = 'X'.
   EXPORT lv_del = lv_del TO MEMORY ID 'POD'.
   EXPORT lv_itm = '00010' TO MEMORY ID 'ITM'.
  
ENDMETHOD.

Method : Process_item

METHOD if_ex_me_process_po_cust~process_item.

DATA: lv_del TYPE char1,
         lv TYPE char1,
         lv_itm TYPE char5,
         lv_ebelp TYPE char5.

   IMPORT lv_del = lv_del FROM MEMORY ID 'POD'.

ls_mepoitem = im_item->get_data( ).

   ls_mepoitem-eeind = ' '.
   ls_mepoitem-eindt = ' '.

   IMPORT lv_itm = lv_itm FROM MEMORY ID 'ITM'.

   lv_ebelp = ls_mepoitem-ebelp.
   IF lv_del = 'X'
     OR lv_itm NE lv_ebelp.

     CALL METHOD im_item->set_data
       EXPORTING
         im_data = ls_mepoitem.

     lv_del = ' '.
     EXPORT lv_del = lv_del TO MEMORY ID 'POD'.
     EXPORT lv_itm = lv_ebelp TO MEMORY ID 'ITM'.
   ENDIF.

[JL23]

Can you share how a PR without delivery date  appears in MD04?

Is it immediatley overdue, or where in the timeline does it appear?

How is it considered from MRP run in case it is a material which is planned as well by MRP?

I mean it is possible to make everything happen with a program language, even inconsitencies. The question for me if such doing does not harm other transactions, does not srew up the planning logic in general.

[Former Member]

HI Jurgen,

We did this development just to get the delivery date field blank for input. This field is mandatory and PR/PO will be saved only after user enters the value in this field.

Hence this field is blank only at initial level and not at time of saving, so it does not effect any other transaction

_Harshita