Factors governing start time in purchase requisitions

Hi,
What are the factors which decides 'Time' in start date of purchase requisition?
I executed heuristics for 1 location-product, there is different time in start date of PRs
Means 1 PR is showing start time as 11.45 and other is showing as 8.45
We are working on SCM 5.0
Thanks for your help!
regards
Yogesh

The start time is governed by
1. requirement time
2. Transport duration in transportation lane.
It is not really governed by planned delivery time.
If my requirement is say 15th June 10.00 am and transport duration in t-lane is 18 hrs, the PR will have end time as 15 June 10.00 am and start time will be 14th June 16.00hrs. (this is if planned delivery time is 4 days or so).
But with same data if requirement is say 5th June 12.00 and planned del time is 4 days. PR will have end time as 7th June 12.00 (because today is 3rd June and you can get the material only after 4 days and you have taken heuristic run at 12.00 hrs today) while the start time will be 18 hrs before that is 6th June 18.00.
In your case two PRs are showing different start time because of different transport durations.
Hope this is clear.
Nitin
Edited by: Nitin Thatte on Jun 3, 2009 7:25 AM

Similar Messages

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.

FM or BAPI for date and time for the creation of a Purchase Requisition

Hi people:
Does anybody knows about a FM, BAPI or table in which i have de detail for the date and hour of the creation of a Purchase requisition?
Points for helpfull answers.
Thanks in advanced

Hi,
If you want to get the time along with the creation date then use the tables CDHDR and CDPOS, but be careful while passing the data need to pass the entire primary fields data else it will fail in the performance test.
Reward points if useful.
Regards,
Suman

Purchase Requisition creation time?

Hi,
Does anybody know how to see at what time was a Purchase requisition created?
There is the creation date in EBAN table (EBAN-BADAT), but i need to know the creation time as well.
Many thanks,
Marc

Hi,
I'm sure creations are stored in CDHDR and CDPOS tables (CDHDR-CHANGE_IND=I) but I can not find out how to enter the table for the purchase requisitions. For Purchase Orders I can enter both tables with CDHDR-OBJECTID=PO number but this doesn't work for Purchase requisitions.
On the other hand, in me53n in environment-item changes, the creation data is not stored.
Any further suggestions?
Thanks,
Marc

Purchase requisition - no GR processing time

Hi,
when you create a purchase requisition in transaction ME21n the goods receiving processing time is considered (from the material master MM02).
In some cases (e.g. Third-Party) we want that this GR processing time is ignored.
Is there a possibility in the standard to set up this functionality?
Or must we implement coding in an userexit or BAdi?
Thanks for your help.

SB,
Purchase requisitions are not normally created in ME21. For manual creation, you would normally use ME51, or ME51N for the Enjoy version.
As far as I know, goods receipt processing time is specific to the Material/plant. It is irrelevant to the source of the supply proposals.
Keep in mind that purchase requisitions are often created by MRP. Your ME51 mod will most probably have no effect on these PRs. During MRP, at the time when the PR is being created, the completion date has already been determined, but the source has not yet been determined. In addition, not all purchase reqs are sourced. Your programmers will have an interesting task ahead of them if you want to make MRP, during PR creation, to consider GRPT on selected PRs, based on source of the PR. Good luck!
Normally, if you wish to have sourced PRs act differently, depending on the source, you enter planned delivery time in the Purchase Info Record, and then configure your PRs to use Purchase Info record data rather than Material Master data. This will not alter the finish date as GRPT will, but in some cases it gives you enough functionality to meet your business requirements.
Rgds,
DB49

Required start date in a services purchase requisition. How?

When hiring equipment (eg. a tower wagon), it is required to specify in the purchase requisition on what date the equipment needs to be available and on what date the equipment needs to be picked up again. So basically, the required start and end date of a service need to be captured in the purchase requisition (and copied to the PO and subsequently sent to the vendor).
The end date of the service is already recorded in the delivery date field. The start date can be entered in the item text. But since it is required to report on the start date of services, it is desirable to record the start date in a separate field in the purchase requisition. This way a list could be created with all the equipment that should have been made available by the vendor on a certain date.
Does anybody have any good suggestions on how to make such a 'required start date' field available? N.B. To make things more complex, the requisitions are raised in Plant Maintenance, so ideally the start date would be filled from the PM-order too.

The validity dates in the PO are maintained at header level. The required start and end date for an equipment should be maintained on item level, as there can be multiple items in one PO each with different start and end dates.
Also, the validity end date in the PO has the functionality that "No further service entry sheets can be created after this date." It is very common that a Service entry sheet is raised after the hire period is ended.
So using the validity dates in the PO is not a good option.

Purchase requisition created only for the vendor lead time

Hello MRP experts,
I have a requirement that the purchase requisitions should be created by MRP only in the vendor lead time and rest of them should be in planned orders. Can this done and if so how. Thanks in Advance and due points will be awarded.

Hi,
As per my understanding there is no standard settings to achieve this requirement.
Regards,
Manish

Purchase Requisition Processing Time

I am currently facing an issue with the purchase requisitoin processing time functionality. It does not appear to work for items without a material master. So if I create a purchase requisition with material master line items and non-material master line items only the material master line items will have the delivery date increased by the purchase requisitoin processing time. Is this standard SAP or a bug?

Dear MM Project.
PR processing time/ GR processing time etc are fields which are mentioned in the material master for each material.
while you process the document with a master record, these details make an impact in those documents. however we may or may not have master records for consumables. the consumables which have a master record will show this impact. these are material types UMBW and NLAG.
for consumables which doesnt have any master record, you can not expect system to impact these values.
hence if you need to have the impact of PR processing time, please create a master record for all those materials and process documents further.
Raghavan

HT201272 when i start downloading a CD purchase it downloads approx 3 to 4 songs then just stops says downloading waited a hour still downloading had to force quit iTunes then reopen to complete download keeps doing this every time i purchase a cd any ide

when i start downloading a CD purchase it downloads approx 3 to 4 songs then just stops says downloading waited a hour still downloading had to force quit iTunes then reopen to complete download keeps doing this every time i purchase a cd any ideas ?

I too am facing this problem, however a little differently. I am in the process of uploading my vinyl collection to digital format in Audacity and am having this problem with multiple tracks when played in iTunes. The first few albums I ripped play just fine in iTunes, but the last few skip over about the last minute of every song and go to the next song. As you said, if you drag the time marker past the skipping point though, the rest of the song will play to the end just fine. I then synced these songs onto my iPod and they play perfectly straight through. I was leaning toward a bad mp3 encoding process that was maybe creating a glitch but I'm not sure at this point if they play correctly on my iPod. In quicktime the song will just stop playing at that specfic point, but if you hit play again, it will continue to the end. I can say though, I haven't seen this problem with any iTunes download, or ripped CD that I have ever put into iTunes (which makes my situation a tad different than yours), it's been purely the songs that I have imported via Audacity from LP's.

Clubbing of purchase requisition at the time of PO Creation

Dear All;
We need a requirement to to club all the PR requirements of same item in PO ,but same PR item is from different project .
Joydeep

Hi ;
In this scensrio we have tested with different Network as acount assignment but system is not clubbing the items .
Scenario in detail is as below Different Purchase requisition comes from different different projects and IT department to raise RFQ after clubbing the same Items but in SAP we are not able to club PReq based on same items as there is no option is available .
Exmple : PR No 123
     Line 10 Desktop       qty 15
    Net work   X
PR No 456      Line 10
Desk top                   qty 10 .
Network Y .
How to club in one PO line item ?
Best Regards;
Joydeep mukherjee
and thanks in advance for your help.

Worflow 20000077 Release Purchase Requisition will not start.

I have the configuration completed on the release codes and when I create a purchase requisition it is blocked but I can't get the system to release the workflow. Does anyone have detailed directions on how to get this done? Thanks!
Chris Lintner
Aflac

I watched the online tutorial on SDN and it answered ALL of my questions! Go SAP!

Plan only releases one purchase requisition at the time

has anyone seen this scenario? When the planner checks multiple purchase requisitions for release and then, when he attempts to release them, the dialog box shows that only one req got released?

That is unusual.
Has the planner saved the earlier records after checking the for release box? Was there any error/warning message?
Have you checked on the Source side if 1 or more reqs. got created?
Is it possible that the other records were Internal reqs or wip jobs?
Sandeep Gandhi

Workflow error in release Purchase requisition

Hi All,
I configured the settings for workflow in Purchase Requisition.(both purchsing & task specific )
Now, my workflow is started but its status is Error.
actually it is not able to find the recepient in role 20000026.As i already mark relevent release code as 1 & also assign US user id in the PR release settings & also put the User ID in task specific customization.
Still i am facing this error.One thing i want to mention is i am not aware of the settings required in the Edit Qrganizational Plan tab in SPRO.
If some more clarification is required ,i will prode the same..
Plz suggest some solution in this regard with T codes & bit detail.
Thanks & Regards,
Sandeep Sharma

Sandeep,
Okay here's some details which will help you out. I presume that you have done customizing for PR release strategy.
If not then follow this procedure:
http://help.sap.com/saphelp_47x200/helpdata/en/04/92761846f311d189470000e829fbbd/frameset.htm
Once you establish release strategy , event releasestepcreated will automatically created by system based on release codes.
so say for a standard pr type you have defined two release codes I1 and I2 (based on certain amount- you can see this in class characterisitic using tcode CL02) and class type -032 and class PR_RELEASE most probably, check Char. tab).
Once you define char. in CL02, you gotta run tcode CT04, give the name of char. and fill all tab.
inside tab Addl data, you have to define CEKKO table and field too
this is where we have referenced the event releasestepcreated implicitly.
FOR all customizing of release strategy check this link , this is really great blog
http://www.sap123.com/forumdisplay.php?s=cced678eca43fe7a7e3bb9b83dc94022&f=2
then search for "setting up simple release procedure" thread in it.
It is for PR.
So if I1 release take place event will triggered, say A has approved I1 level and for whole PO release I2 is also required then one more time event releasestepcreated event would be triggered.
You can create workflow for PO release. Approver are determined based on rule AC20000026 (check in PFAC) based on FM which has user exit EXIT_SAPLEBNF_001 where you can write down your own code for approver determination.
I think that you gotta put 9 (in release code settting in SPRO). If you are inserting 1 then you have to define US and user name (which I think you have done).
Hope it will clear your doubts
Cheers
Jai

Workflow for MM purchase Requisition steps required

Dear all,
        I am trying to configure purchase requisition Workflow.
        I am working with Work flow, WS 00000038
        I have assigned agents to TS 20000162
        Now how to proceed further, do i need to maintain some more settings
        or i should try to test system.
        Regards,
        Gaurav sood

Under the assumption that things have not changed much since 4.70, here's quick introduction:
The workflow is started only when a relevant release strategy is found, so customizing of release strategies is a very important (first) step here.
In the Implementation Guide you find the customizing in the following path:
Materials Management
-- Purchasing
-- -- Purchase Requisition
-- -- -- Release Procedure
-- -- -- -- Procedure with Classification
Only the procedures with classification are relevant if you want to use workflow to notify about requisitions waiting for release.
First you must set up a classification class if that has not already been done. Derive your characteristics from the structure CEBAN. The online help is not too bad, I had never set up classifications before and managed to get it working.
If you need data that are not available in CEBAN, or you want to modify them for the purpose of determining the release strategy there is an enhancement you can implement, and there are customer fields you can use. The enhancement definition's name is M06B0002.
As an example of what you can do, I have used it to set the company code in one of the customer fields, and to change the account assignment type. However, whether you need this enhancement or not depends strongly on what data you use to determine your release procedures (a step in customizing you will get to later).
When that is done you define release groups and release codes. Release codes are defined within each release group. Whether you should use one group or several groups is often a matter of choice.
I myself prefer using several groups even if I don't have to, so long as it doesn't lead to having to define duplicate release strategies (which you will soon get to). So, if there is some characteristic that clearly separates your release strategies, e.g. the highest amount that does NOT require release etc, you can define one group for each value (group) of this characteristic.
For instance, if some company codes require release for everything worth more than 100EUR while the default is to require release from 10.000EUR you could create to release groups. None of your release strategies will be duplicates since the value from which release is required will be different and you thus need to have that as a characteristic.
You then check that the set-up of release indicators is OK, and then you are ready to start defining the strategies. Release stragies are defined within each release group, and use one or more release codes (two or more release indicators).
It is fairly self-explanatory once you get into the screens. The thing to be observant about is to not define overlapping strategies, as this will prevent the solution from working.
When you are done, and have tested the solution in DEV it is time to transport it to the QA system. That's when I got a rather unpleasant surprise. The classification data are not transported, so both the characteristics and class, as well as the classification data in each release strategy had to be redefined. And in roughly two hours I have to do it again in production.
It is possible to transport classification information, it is described in SAP OSS Notes (different solutions for different versions).

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>

Factors governing start time in purchase requisitions

Similar Messages

Maybe you are looking for