MM - Purchase requisition initial data

Hi,
I would like my Purchase Requisitions to be created as "blocked". Does anyone knows how to do that ?
Best Regards,
Remi

Hi,
Set the release strategy for PR .check the link
http://www.sap123.com/showthread.php?t=59
reward if helpful,
Regards,
Chetan.

Similar Messages

Purchase Requisitions opening date in past

Hi Experts,
We are using SNP Optimizer (SCM 7.0).
We are facing issue with Purchase Requisition Opening Date is showing in past.
Lets say Planned Delivery time for externally procured material (Componenent) is 30 days and there is NO stock of this component.
This componenent is input to Finished goods which has forecast on 15th March and there is NO stock.
As planned delivery time is 30 days, earliest componenet can be procured will be 8th April (today is 9th march).
Opening period should be shown as 8th April but I am seeing opening date of this compoenent in February which is past.
Why it is creating Pur Req in past openign date with receive date as today's date?
Regards,
Vipul

Hi Santosh,
No, we are not using opening period or stock transfer horizon.
Regards,
Vipul

Purchase Requisition Start Date

Hi,
I have a Purchase requisition in R/3 and APO for a product and location. I see in Md04 that the planned date, delivery date and release date are all 28.07.2008 but when it gets to APO, in pproduct view, I see the PR start date as 29.07.2008 and the end date as 08/03/2008.
Can somebody give me an idea why this is happening?
If the order is stuck in CIF que and gets pushed the next day, does the order date change???

Hi Harish,
Here are the settings:
R/3 - Local time - EST
Product View - ( Settings>time zone) UTC
We are using time stream id as a transportation calendar in Transportation lane means of transport - EST
does this effect the dates? Do you mean that I have to change the product view setting to EST? Is that enough?
Is the note you are talking about is 443500?
This material is a external procurement (F). So, i guess there won't be any PPMs.

Purchase requisition release date

Purchase requisition is created through MRP run and release date of the pur req is 2 days before delivery date.I have not maintain sheduling margin key,planned delivery time,GR processing time,etc.How this is happening?

Hi
Please check in config Materials management--> Purchasing-> Purchase requisition ---> Processing time . You might have given 2 days for purchase requisitin processing time for your plant. That may be the reason you have 2 days difference.
Remove this and save and re run MRP. It will work for you
Regards
Antony

Purchase Requisition No data satisfying selection criteria

We have created a Maintenance Notification and converted it into Maintenance Order, after approval of maintenance Order it will generate a MM purchase requisition automatically.
But upon checking on Me53N or any other report for MM PR the PR does not exist. on Me53n it gives the error: No data satisfying selection criteria
but the PR exist on table EBAN.
thanks God bless

If you give proper inputs in ME5K or ME5A, you can get the PR list without any problem.
Also, while selecting PR in ME53N, have you given proper PR number directly or are you searching through some Search help option??
Please post your screen shots PM Order document flow, Operation tab, Components tab, ME53N search steps as well as MM PR reporting selection screen with that error message.

Purchase requisition approved date field name by differnt release codes

can any body give me field name of the date of purchase requisition released by the release code.
regards
reddy
Edited by: Ian Wong on Sep 18, 2008 6:37 PM

Hi,
Table name is EBAN
Field name is BADAT.
Pass Pur Req no..you can get the Date.
Rgs,
Dhanush.

Purchase requisition creation date ...

Our auditor want to know the creation date of purchase requisition ,
i have check table CDHDR ... using Object value <PR NUMBER> and using BANF, it only display change history only ... where can i find creation date of PR ?

Hi,
It is incorrect that CDHDR is only used for PO. It is used for all purchasing document changes.
Hi,
The creation date of PR is seen in EBAN-BADAT field.
Cheers,
HT

Purchase requisition delivery date before the requested/created date

Dear Experts,
We are getting an issue that Purchase requisitions created by APO are having Delivery Date one day before of requesed Date.
Eg Purchase requistion created on 20.02.2015 and having delievery date on 19.02.2015.
I have checked contract, Purchase info record Tlane all master data settings are ok.
Planned Delievery Time maintained in the info record is 0 and GRPT time is 1 day.
Same vendor, contract, PIR exists for 2 material, But we are facing issue only for one material.
It is an urgent issue , if anyone is having any idea , suggestions please reply to me if any information required will update here.

Hi Mariano,
Thanks for your Reply !!
GRPT and PDT in ECC maintained as 1 day In material master.
In Purchase Info record PDT is maintained as 0 days and GRPT is 1.
I also checked tlane it is coming as 1 day and GRPT is 0 days.
So which i analysed from some other eg of materials pur req is considering the settings of which is maintained in Tlane, so giving 1 day back date in Pur Req.
But it solved my previous question but arises one more question that tlane we have not mannually maintained, it always created on the basis of contract in our scenario, so how the PDT=1 day come inside tlane?
Regards
Deepika Kukreja

Purchase Requisition Date is not updated with Scheduleline Delivery Date

Hi,
This is a third part Sales Scenario. The Delivery date on the schedule line is passed on to purchase requisition as the delivery date of that item. Due to some business requirement, the delivery date of the schedule line is changed just before saving the sales order in the BADI called through the userexit userexit_save_document_prepare. Now on saving the sales order, the purchase requsition is also created.The delivery date of the schedule line is changed but has not reflected on the Purchase Requision.
If the Sales Order is opened in VA02 and the schedule line delivery date is modified, the Purchase Requisition delivery date is also getting modified.
Why did it not happen at the time of saving the Sales Order.
What is the structure into which the purchase requsition information is stored, so that on processing the sales order, this information is utilized to create the purchase requsition.
Please help.

Hi,
Check the following table for the mentioned fields EBAN-BADAT and EBAT-FRGDT
Thanksk and Regards,
Hari Challa.

User Exit/BADI to change the Purchase Requisition date,creating threw MD02

Hi,
I've a requirement to change the Purchase Requisition creation date.
I'm using MD02 to create Purchase Requisition.
Based on the requirement if the available qty is less than the required quantity,we can change Purchase requisition date.
Please let me know if any BADI's/User Exits we can use for this purpose.
I've checked EXIT_SAPLMEREQ_010. I've kept debugging point nad i run MD02, but it is not stopping in the exit.
we are using SAP 4.6c.
Thanks,
Adi.

Hi Experts,
Could you please give me a suggestion for the above problem???
Thanks,
Adi.

Delivery Date getting Copied to Release Date in Purchase Requisition

Hello,
When i am releasing the Purchase Requsition, what ever the Delivery Date the system is proposing based on the Planned Delivery Days given in Material Master is copied to the Purchase Requisition Release Date.
Is there any error in Customization ??
Regards,
Kumar

Hello Shakthi,
System is considering Delivery date as Release Date when you create the purchase requisition.
Thanx & Regards,
Kumar

Due date in purchase requisition

Hi experts,
I want to know in which table "Due Date" will be stored during the purchase requisition generation???

Dear Nandakumar,
Please check in table EBAN for the following fields
BEDAT = Purchase Order Date
BADAT = Requisition (Request) Date
LFDAT = Item Delivery Date
FRGDT =Purchase Requisition Release Date
Check and revert back.
Thanks & Regards,
Hegal K Charles

Purchase Requisition fields & table

hi experts,
                I have a requirement to make Purchase Requisition report. Is there any standard report so i can copy and modify it. Or u guys have made some report of the same. its urgent.
Or plz tell the table & field names of the following requirement. also help me on what fields I can join that tables.
Purchase Requisition (PR) date
Delivery date
PR No.
PR Material No.
PR Quantity
STO date
STO No.
STO material
STO Qty.
Supplying Plant
Delivery Plant
Delivery No.
Delivery Date ( when delivery created)
Delivery material
Delivery Qty.
PGI
thanks. alot.
Khan

REPORT ZPurchase_alvsample                 .
TABLES:     ekko.
type-pools: slis.                                 "ALV Declarations
*Data Declaration
TYPES: BEGIN OF t_ekko,
ebeln TYPE ekpo-ebeln,
ebelp TYPE ekpo-ebelp,
statu TYPE ekpo-statu,
aedat TYPE ekpo-aedat,
matnr TYPE ekpo-matnr,
menge TYPE ekpo-menge,
meins TYPE ekpo-meins,
netpr TYPE ekpo-netpr,
peinh TYPE ekpo-peinh,
END OF t_ekko.
DATA: it_ekko TYPE STANDARD TABLE OF t_ekko INITIAL SIZE 0,
      wa_ekko TYPE t_ekko.
*ALV data declarations
data: fieldcatalog type slis_t_fieldcat_alv with header line,
      gd_tab_group type slis_t_sp_group_alv,
      gd_layout    type slis_layout_alv,
      gd_repid     like sy-repid,
      gt_events     type slis_t_event,
      gd_prntparams type slis_print_alv.
*Start-of-selection.
START-OF-SELECTION.
perform data_retrieval.
perform build_fieldcatalog.
perform build_layout.
perform build_events.
perform build_print_params.
perform display_alv_report.
*&      Form BUILD_FIELDCATALOG
      Build Fieldcatalog for ALV Report
form build_fieldcatalog.
There are a number of ways to create a fieldcat.
For the purpose of this example i will build the fieldcatalog manualy
by populating the internal table fields individually and then
appending the rows. This method can be the most time consuming but can
also allow you more control of the final product.
Beware though, you need to ensure that all fields required are
populated. When using some of functionality available via ALV, such as
total. You may need to provide more information than if you were
simply displaying the result
              I.e. Field type may be required in-order for
                   the 'TOTAL' function to work.
fieldcatalog-fieldname   = 'EBELN'.
fieldcatalog-seltext_m   = 'Purchase Order'.
fieldcatalog-col_pos     = 0.
fieldcatalog-outputlen   = 10.
fieldcatalog-emphasize   = 'X'.
fieldcatalog-key         = 'X'.
fieldcatalog-do_sum      = 'X'.
fieldcatalog-no_zero     = 'X'.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'EBELP'.
fieldcatalog-seltext_m   = 'PO Item'.
fieldcatalog-col_pos     = 1.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'STATU'.
fieldcatalog-seltext_m   = 'Status'.
fieldcatalog-col_pos     = 2.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'AEDAT'.
fieldcatalog-seltext_m   = 'Item change date'.
fieldcatalog-col_pos     = 3.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'MATNR'.
fieldcatalog-seltext_m   = 'Material Number'.
fieldcatalog-col_pos     = 4.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'MENGE'.
fieldcatalog-seltext_m   = 'PO quantity'.
fieldcatalog-col_pos     = 5.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'MEINS'.
fieldcatalog-seltext_m   = 'Order Unit'.
fieldcatalog-col_pos     = 6.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'NETPR'.
fieldcatalog-seltext_m   = 'Net Price'.
fieldcatalog-col_pos     = 7.
fieldcatalog-outputlen   = 15.
fieldcatalog-do_sum      = 'X'.
fieldcatalog-datatype     = 'CURR'.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'PEINH'.
fieldcatalog-seltext_m   = 'Price Unit'.
fieldcatalog-col_pos     = 8.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
endform.                    " BUILD_FIELDCATALOG
*&      Form BUILD_LAYOUT
      Build layout for ALV grid report
form build_layout.
gd_layout-no_input          = 'X'.
gd_layout-colwidth_optimize = 'X'.
gd_layout-totals_text       = 'Totals'(201).
gd_layout-totals_only        = 'X'.
gd_layout-f2code            = 'DISP'. "Sets fcode for when double
                                        "click(press f2)
gd_layout-zebra             = 'X'.
gd_layout-group_change_edit = 'X'.
gd_layout-header_text       = 'helllllo'.
endform.                    " BUILD_LAYOUT
*&      Form DISPLAY_ALV_REPORT
      Display report using ALV grid
form display_alv_report.
gd_repid = sy-repid.
call function 'REUSE_ALV_GRID_DISPLAY'
       exporting
            i_callback_program      = gd_repid
            i_callback_top_of_page   = 'TOP-OF-PAGE' "see FORM
            i_callback_user_command = 'USER_COMMAND'
           i_grid_title           = outtext
            is_layout               = gd_layout
            it_fieldcat             = fieldcatalog[]
           it_special_groups       = gd_tabgroup
            it_events               = gt_events
            is_print                = gd_prntparams
            i_save                  = 'X'
           is_variant              = z_template
       tables
            t_outtab                = it_ekko
       exceptions
            program_error           = 1
            others                  = 2.
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
endform.                    " DISPLAY_ALV_REPORT
*&      Form DATA_RETRIEVAL
      Retrieve data form EKPO table and populate itab it_ekko
form data_retrieval.
select ebeln ebelp statu aedat matnr menge meins netpr peinh
up to 10 rows
from ekpo
into table it_ekko.
endform.                    " DATA_RETRIEVAL
Form TOP-OF-PAGE                                                 *
ALV Report Header                                                 *
Form top-of-page.
*ALV Header declarations
data: t_header type slis_t_listheader,
      wa_header type slis_listheader,
      t_line like wa_header-info,
      ld_lines type i,
      ld_linesc(10) type c.
Title
wa_header-typ = 'H'.
wa_header-info = 'EKKO Table Report'.
append wa_header to t_header.
clear wa_header.
Date
wa_header-typ = 'S'.
wa_header-key = 'Date: '.
CONCATENATE sy-datum+6(2) '.'
               sy-datum+4(2) '.'
               sy-datum(4) INTO wa_header-info.   "todays date
append wa_header to t_header.
clear: wa_header.
Total No. of Records Selected
describe table it_ekko lines ld_lines.
ld_linesc = ld_lines.
concatenate 'Total No. of Records Selected: ' ld_linesc
                    into t_line separated by space.
wa_header-typ = 'A'.
wa_header-info = t_line.
append wa_header to t_header.
clear: wa_header, t_line.
call function 'REUSE_ALV_COMMENTARY_WRITE'
       exporting
            it_list_commentary = t_header.
           i_logo             = 'Z_LOGO'.
endform.
      FORM USER_COMMAND                                          *
      --> R_UCOMM                                                *
      --> RS_SELFIELD                                            *
FORM user_command USING r_ucomm LIKE sy-ucomm
                  rs_selfield TYPE slis_selfield.
Check function code
CASE r_ucomm.
    WHEN '&IC1'.
Check field clicked on within ALVgrid report
    IF rs_selfield-fieldname = 'EBELN'.
    Read data table, using index of row user clicked on
      READ TABLE it_ekko INTO wa_ekko INDEX rs_selfield-tabindex.
    Set parameter ID for transaction screen field
      SET PARAMETER ID 'BES' FIELD wa_ekko-ebeln.
    Sxecute transaction ME23N, and skip initial data entry screen
      CALL TRANSACTION 'ME23N' AND SKIP FIRST SCREEN.
    ENDIF.
ENDCASE.
ENDFORM.
*&      Form BUILD_EVENTS
      Build events table
form build_events.
data: ls_event type slis_alv_event.
call function 'REUSE_ALV_EVENTS_GET'
       exporting
            i_list_type = 0
       importing
            et_events   = gt_events[].
read table gt_events with key name = slis_ev_end_of_page
                           into ls_event.
if sy-subrc = 0.
    move 'END_OF_PAGE' to ls_event-form.
    append ls_event to gt_events.
endif.
    read table gt_events with key name = slis_ev_end_of_list
                           into ls_event.
if sy-subrc = 0.
    move 'END_OF_LIST' to ls_event-form.
    append ls_event to gt_events.
endif.
endform.                    " BUILD_EVENTS
*&      Form BUILD_PRINT_PARAMS
      Setup print parameters
form build_print_params.
gd_prntparams-reserve_lines = '3'.   "Lines reserved for footer
gd_prntparams-no_coverpage = 'X'.
endform.                    " BUILD_PRINT_PARAMS
*&      Form END_OF_PAGE
form END_OF_PAGE.
data: listwidth type i,
        ld_pagepos(10) type c,
        ld_page(10)    type c.
write: sy-uline(50).
skip.
write:/40 'Page:', sy-pagno .
endform.
*&      Form END_OF_LIST
form END_OF_LIST.
data: listwidth type i,
        ld_pagepos(10) type c,
        ld_page(10)    type c.
skip.
write:/40 'Page:', sy-pagno .
endform.
regards,
srinivas
<b>*reward for useful answers*</b>

Purchase Requisition and RFQ

Friends,
I want to check the time lag between Purchase requisition release date and RFQ date. Please tell me if any standard Function is available. If not tell me the way
Thanks

Rakesh,
I don't think there is any straight forward function module that gives you this.
The logic should be that you find out the release date of the purchase requistion and find out the date on which the RFQ was created. Once you have both the dates you can calculate the difference.
Purchase Req. release details can be fetched using BAPI_REQUISITION_GETRELINFO. And the RFQ created date can be directly fetched from EKKO table.
Regards,
Ravi
note : Please reward the posts that help you.

Purchase Requistion release date as system date

Dear Experts,
Our Requirement is the top management want to know time taken to release a purchase requisition,means the duration
between purchase requisition creation date to release date.
here user are manually changing the release date to system date to know duration exact time duration between the creation date and release date,so user requirement is the release date should be system date so he can easily understand when the requisition is released.
we are thinking that,if we make the release date as system date,please suggest me.
Thanks in Advance.
Varun

Dear Madhu,
1.)     Whenever you are creating a new PR system will automatically take that PR creation date as system date.
2.)     All the releases in SAP System will be recorded as Item/Header change and system will maintain their history in Item/Header change details
3.)     If your requirement is to track the duration between creation, release of levels it can be very much possible by creating a quary it self.
Regardsu2026
Srini Rao

MM - Purchase requisition initial data

Similar Messages

Maybe you are looking for