PR delivery date vs PR release date

Hi, did anyone know why changing PR delivery date will affect the PR release date? Can PR release date remain unchange if changes made to PR delivery date?
Pls advise.
Thanks.

Hi,
I guess you're referring to the Release Date which is shown in Quantities/Dates tab in the PR.
If yes, then what you notice is a standard system behaviour. This release date is calculated as Delivery Date - PLDT.
Hope the above answers your question.
If helpful award points
Regards,
Vivek

Similar Messages

I pre-ordered an iPhone 6 Plus and the delivery date now says October 14th. The point of the pre-order is to get it on release day (or shortly thereafter). Can I go to a Verizon store to pick up my new phone on release day?

I pre-ordered an iPhone 6 Plus and the delivery date now says October 14th. The point of the pre-order is to get it on release day (or shortly thereafter). Can I go to a Verizon store to pick up my new phone on release day?

I'm not sure that answers the question Candice.
I'm in the same situation. I was up trying to get on the Verizon page at 11:55, kept getting the ECPD error. When finally got through, the Silver Iphone Plus 64 showed arrival of 9-19. At every step of the process, it seemed that I was ordering a phone that would arrive on day1. At no point did it say this was an estimate. At no point did it say it might change. In a big yellow box, it said "9-19". Ordered it, then got confirmation email stating it should arrive at 9-19. Seems like all should be good, right? Order site said 9-19, I've got a confirmation email saying 9-19, done and done.
Then I check the website, and suddenly it changed to 10-14?!?!?!? I feel like this was a bait and switch. I was able to pickup an iphone5 in a local store on launch day, and would not have locked myself into a preorder through Verizon if I had known this would happen!
So, that leads back to the original questions. Lets assume I walk into a Verizon store on 9-19, and there is an available iphone6 plus just sitting there, can I either get that phone as fulfillment of my pre-order. Or, cancel my pre-order and buy that phone right then and there?
JJK
PS: It seems there are many people you misled this way. For every person who takes the time to post on this site, there are going to be many many more who are silently ****** off.

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

Redetermine PO Delivery Date on Release

Hi
When a PO is created, the buyer ensures that the correct delivery date is put in place. However it sometimes very long for the PO to be released and by the time the PO is released and the PO is sent to the Vendor, the delivery date is already in the past.
Is there anything that can be done in order to redetermine the PO delivery date at the time of release/ at the time the PO is sent to the Vendor.
Thanks
Vinesh

Hi Vinesh,
You can change the delivery date manually in ME22N(Change PO) if there are more line items then u can use fast change to change the delivery date.Once delivery date is changed u have to release the PO again..As per i know automatica redetermination is not possible for already cretaed PO.
Regards,
AM

Change in Expected Delivery date (EDD) field in the PO after final release

Hello Experts,
There is a business requirement, whereby after PO final release is completed & when the PO is released for further processing, no further changes should be possible, except for the expected delivery date (EDD) field in the Delivery schedule tab of the PO Item details. Other than this, no changes should be possible in the PO, neither qty, nor price, not even the simple PO text should be allowed to get changed. In other words no field should be allowed to change.
Ideally, except the EDD field, other all fields should be in grey mode, or atleast changes in any of the PO fields (except EDD) should not be allowed to get saved after the PO is final released.
Please let me know if SAP provides any such facility, whereby you can selectively choose certain fields (like EDD field) on which Release Strategy should not be applied & changes should be allowed in these fields even after PO final release.
Thanks in advance,
Zafar.

If you go to OMET transciton and here you can assign the field selection key in the field FieldSe
and assing the User parameter EFB in user id of the user using SU3 transction
for more help see below
Create a Functional Authorization in the Following path:
Material Mangement - Purchasing - Authorization Management - Define Functional Authorization for Buyers
Now, in SU3 trxn ,Give the User Parameter EFB in the user master Parameters Tab and give the parameter value.
create the fields selction which you want use here in PO field seleciton config.

PO Release ME28, Delivery date display

This is regarding collective release of PO's via ME28
Approve like to see delivery date of PO in the list, tried changing layout but this field seems to be unavailable
Any suggestions?

Dear Sasi,
Gd Day.
Goto ME28, tick List with items & Scope of List select ALLES. You could see all info including delivery date. Hope this could help you. TQ
rgds,
nanthakumar

How to derive Budget Period from Delivery date in PR/PO

Hello Gurus,
I have activated the Budget Period functionality in FM (BCS). I am deriving the budget period from Posting date but in case of PR/PO I want to derive it from Delivery date instead of Document/Posting Date.I know it is not possible while standard derivation. Could any one help me with some suggestion like if I can use some exit/BaDI in MM. Also I am creating a PM order and at the time of release of PM order system creates the PR in background hence I need to know some kind of exit/BADI which can be called to update the Budget Period field in PR.
Thanks in Advance!
Regards
Rohit Goel

Hello Eli,
I have one more query to ask on the above scenario.
The scenario is my delivery date in PO is say July but I did good issue in May hence the Budget Period should be May and not july in my GR and IV.
Now when I am doing GR in May then system is showing the Budget Period as July in GR document but in FM Document it is populating as May. I have defined a derivation strategy to derive budget period from posting date so may be because of that.
But when I am doing IV then it is again moving the amount from May to July. It may be right behaviour that system is deriving all the account assignment from Source document but is there any way to overwrite.
I have defined the derivation strategy with the condition that overwrite with new value if already written (Deriving from Posting Date to Budget Period).
Please guide me on this if possible.
Thanks in Advance
Regards
Rohit

Delivery date in the PR is wrongly calculated

Hi,
This is a severe issue we are facing, delivery date in PR is wrongly calculating. consider this example:
sales order was created on 31.08.2007 and the planned delivery time assigned in MMR is 9 days, GR processing time is 1 day. Due to some reasons we have created PR on 17.09.2007 but the system is showing the delivery time as 17.10.2007 the release date is on 05.10.2007
Can any body tell me how system calculates delivery date in PR and wat are the factors influence this calculation and also the reason for this unusaual behavior of the system?
Many thanks for your quick reply.
Sri

Please request one Abaper to solve this problem.
You cannot due nothing as the problem is in Code.
Regards
William

MRP for STO Delivery Date Issue

Dear Gurus,
We are using MRP to generate STO purchase requisition for a specific material.
We have entered planned delivery time in the receiving plant. The supplying plant is 1000 and receiving plant is 2000.
We have entered planned delivery time in plant 2000 for 10 days . MRP is run at mid night. System is generating PR . But the delivery date is same as current date.
E.G: Material A planned delivery time 10 days in plant 2000
Planning date is 20/07/2014
in PR : Delivery date is 29/7/2014
and PR release date is 19/7/2014.
The release date is appearing in the past. Kindly help me to resolve this issue.
Thanks in Advance.
Sreedhar

Hi Dev,
When i create STO PR manually all the dates are appearing as per standard calculation considering the planned delivery cost.
The issue is in MRP run.
Thanks & Regards,
Sreedhar

Committed Delivery Date in a Purchase Order?

Commmited Delivery Date in Purchase Order?
Can any one tell me , how is the commited delivery date in Purchase Order Determined!
I get a date which is sunday as committed delivery date but according to Route Calendar and shipping
point calendar sunday is not a working day?
Any suggestions?
Thanks!

Hi,
find this notes might be use full for you .
Commitment dates switch for calculation rule
Key that controls how the commitment quantities should be calculated per sales document type.
Use
The commitment date is calculated using the delivery time for releases to contracts with delivery times, or sales orders that refer to quotations containing delivery times. The committed quantity results from the agreed delivery time or the confirmed quantity, according to the calculation rule set here.
Dependencies
You can set the following calculation rules:
A: Consider agreed delivery time
Here, all required schedule lines are committed for the date that lies at the agreed distance from the delivery time, according to the date on which the order was placed. If the customer requests a later date, this can be confirmed. The confirmation does not affect the calculation. If you do not enter a delivery time, the system does not calculate a committed quantity.
B: First confirmation date
The committed quantity is calculated according to the first confirmed quantities. If a delivery time exists for the item, the system takes it into account, as in calculation rule A, and confirms the earlier date. The commitment date is recalculated if the material, quantity, first date, or delivery time change. The quantities confirmed then are valid once the document has been saved.
C: First confirmation date
Rule C is the same as calculation rule B but for new items. If you save a document again but the system can confirm more for the customer, the more favorable situation will be saved as the commitment. As in rule B, the commitment date will be recalculated if changes are made to the material, quantity, requested delivery date, or delivery time.
No entry
Commitment dates are not calculated or displayed.
With best Regards,
venkataswamy.y

Problem in BAPI_PO_CREATE1 with delivery date option

Hi Experts,
I'm using BAPI_PO_CREATE1 for uploading user excel file to create purchase orders.
The issue is PO is created successfully but the delivery date is not picking properly. System is picking some other delivery date.
Can any one help me out from this?????????
Any USEFUL INPUTS for solving this issue will be rewarded.
Code :
REPORT zmm_bapi_po_create.
*                             ''~``
*                            ( o o )
*    +------------------.oooO--(_)--Oooo.------------------+
*    | ZMM_BAPI_PO_CREATE -To create Purchase orders       |
*    |                                                     |
*    |                    .oooO                            |
*    |                    (   )   Oooo.                    |
*    +---------------------\ (----(   )--------------------+
*&    Program Name     : ZMM_BAPI_PO_CREATE
*&    Transaction Code :
*&    Module Name      : MM
*&    Developer        : Lakshmiraj.A
*&    Functional       : Xavier
*&    Transport Request:
*&    Program Type     : Report
*&    SAP Release      : 46C
*&****************************REVISION LOG*****************************
*& Log     Date         Author              Description
*&------------------------ TABLE USED --------------------------------*
*&---------------------- VARIABLE DECLARATION ------------------------*
* For Storing file name.
DATA : filename1 TYPE string.
* Flag to identify the matching entries
DATA : flag(1).
* For Display Message
DATA : g_msg(80) TYPE c.
* Declaring that as a character with length 4096.
TYPES truxs_t_text_data(4096) TYPE c OCCURS 0. " Type Group : TRUXS
* Containing RAW Data
DATA : it_raw TYPE truxs_t_text_data.
*&------------------------- INTERNAL TABLE ---------------------------*
DATA: gstest LIKE bapimepoheader.
DATA: g_ebeln LIKE bapimepoheader-po_number.
DATA: BEGIN OF g_bapimepoheader OCCURS 0.
        INCLUDE STRUCTURE bapimepoheader.
DATA: END OF g_bapimepoheader.
DATA: BEGIN OF g_bapimepoheaderx OCCURS 0.
        INCLUDE STRUCTURE bapimepoheaderx.
DATA: END OF g_bapimepoheaderx.
DATA: BEGIN OF g_bapimeposchedule OCCURS 0.
        INCLUDE STRUCTURE bapimeposchedule.
DATA: END OF g_bapimeposchedule.
DATA: BEGIN OF g_poschedulex OCCURS 0.
        INCLUDE STRUCTURE bapimeposchedulx.
DATA: END OF g_poschedulex.
*DATA: BEGIN OF g_bapieikp OCCURS 0.
*        INCLUDE STRUCTURE bapieikp.
*DATA: END OF g_bapieikp.
DATA: BEGIN OF g_bapimepoitem OCCURS 0.
        INCLUDE STRUCTURE bapimepoitem.
DATA: END OF g_bapimepoitem.
DATA: BEGIN OF g_poitemx OCCURS 0.
        INCLUDE STRUCTURE bapimepoitemx.
DATA: END OF g_poitemx.
DATA: BEGIN OF g_bapiret2 OCCURS 0.
        INCLUDE STRUCTURE bapiret2.
DATA: END OF g_bapiret2.
DATA: BEGIN OF itab OCCURS 0,
doc_type       LIKE    bapimepoheader-doc_type,
vendor         LIKE    bapimepoheader-vendor,
purch_org      LIKE    bapimepoheader-purch_org,
pur_group      LIKE    bapimepoheader-pur_group,
comp_code      LIKE    bapimepoheader-comp_code,
incoterms1 LIKE bapimepoheader-incoterms1,
incoterms2 LIKE bapimepoheader-incoterms2,
po_item        LIKE    bapimepoitem-po_item,
material       LIKE    bapimepoitem-material,
short_text     LIKE    bapimepoitem-short_text,
quantity       LIKE    bapimepoitem-quantity,
plant          LIKE    bapimepoitem-plant,
delivery_date LIKE    bapimeposchedule-delivery_date,
END OF itab.
DATA: it_itab LIKE itab OCCURS 0 WITH HEADER LINE.
*&------------------------ SELECTION SCREEN --------------------------*
SELECTION-SCREEN BEGIN OF BLOCK blk WITH FRAME TITLE text-100.
PARAMETERS : p_file LIKE rlgrap-filename.
SELECTION-SCREEN END OF BLOCK blk.
*&-----------------------AT SELECTION SCREEN -------------------------*
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
* For getting input filename
PERFORM get_filename.
*&-----------------------START OF SELECTION---------------------------*
START-OF-SELECTION.
* Open the Excel file and Update with the internal table
PERFORM update_inttable.
PERFORM bapi_upload.
*       FORM bapi_upload                                              *
FORM bapi_upload.
it_itab[] = itab[].
SORT itab BY vendor material.
DELETE ADJACENT DUPLICATES FROM itab COMPARING vendor.
LOOP AT itab.
    g_bapimepoheader-comp_code = itab-comp_code.
    g_bapimepoheader-doc_type = itab-doc_type.
    g_bapimepoheader-creat_date = sy-datum.
    g_bapimepoheader-created_by = sy-uname.
    g_bapimepoheader-vendor = itab-vendor.
    g_bapimepoheader-purch_org = itab-purch_org.
    g_bapimepoheader-pur_group = itab-pur_group.
    g_bapimepoheader-incoterms1 = itab-incoterms1.
    g_bapimepoheader-incoterms2 = itab-incoterms2.
    APPEND g_bapimepoheader.
    g_bapimepoheaderx-comp_code = 'X'.
    g_bapimepoheaderx-vendor = 'X'.
    g_bapimepoheaderx-doc_type = 'X'.
    g_bapimepoheaderx-purch_org = 'X'.
    g_bapimepoheaderx-pur_group = 'X'.
    g_bapimepoheaderx-incoterms1 = 'X'.
    g_bapimepoheaderx-incoterms2 = 'X'.
    APPEND g_bapimepoheaderx.
    LOOP AT it_itab WHERE vendor = itab-vendor.
      MOVE-CORRESPONDING it_itab TO g_bapimepoitem.
      CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
           EXPORTING
                input = it_itab-material
           IMPORTING
                output = it_itab-material.
      g_bapimepoitem-material = it_itab-material.
      APPEND g_bapimepoitem.
      g_poitemx-po_item = it_itab-po_item.
      g_poitemx-po_itemx = 'X'.
      g_poitemx-item_cat = 'X'.
      g_poitemx-plant = 'X'.
      g_poitemx-stge_loc = 'X'.
      g_poitemx-net_price = 'X'.
      g_poitemx-acctasscat = 'X'.
      g_poitemx-material = 'X'.
      g_poitemx-short_text = 'X'.
      g_poitemx-matl_group = 'X'.
      g_poitemx-quantity = 'X'.
      g_poitemx-po_unit = 'X'.
      g_poitemx-orderpr_un = 'X'.
      g_poitemx-trackingno = 'X'.
      g_poitemx-delete_ind = 'X'.
      APPEND g_poitemx.
      g_bapimeposchedule-po_item = it_itab-po_item.
      g_bapimeposchedule-sched_line = '001'.
      g_bapimeposchedule-del_datcat_ext = 'X'.
      g_bapimeposchedule-delivery_date = it_itab-delivery_date.
      g_bapimeposchedule-quantity = it_itab-quantity.
      APPEND g_bapimeposchedule.
      g_poschedulex-po_item = it_itab-po_item.
      g_poschedulex-sched_line = '001'.
      g_poschedulex-po_itemx = 'X'.
      g_poschedulex-sched_linex = 'X'.
      g_poschedulex-del_datcat_ext = 'X'.
      g_poschedulex-delivery_date = 'X'.
      g_poschedulex-quantity = 'X'.
      g_poschedulex-deliv_time = 'X'.
      g_poschedulex-stat_date = 'X'.
      APPEND g_poschedulex.
    ENDLOOP.
    CALL FUNCTION 'BAPI_PO_CREATE1'
         EXPORTING
              poheader         = g_bapimepoheader
              poheaderx        = g_bapimepoheaderx
         IMPORTING
              exppurchaseorder = g_ebeln
              expheader        = gstest
         TABLES
              return           = g_bapiret2
              poitem           = g_bapimepoitem
              poitemx          = g_poitemx
              poschedule       = g_bapimeposchedule
              poschedulex      = g_poschedulex.
    IF NOT g_ebeln IS INITIAL.
      COMMIT WORK.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
           EXPORTING
                wait = ''.
      REFRESH : g_bapimepoitem,
                g_bapimepoheader,
                g_bapimepoheaderx,
                g_bapiret2,
                g_poitemx,
                g_bapimeposchedule,
                g_poschedulex.
    ENDIF.
ENDLOOP.
ENDFORM.
*       FORM GET_FILENAME                                             *
FORM get_filename.
CALL FUNCTION 'F4_FILENAME'
       EXPORTING
            program_name = sy-cprog
            dynpro_number = sy-dynnr
            field_name    = ''
       IMPORTING
            file_name     = p_file.
ENDFORM.
*       FORM UPDATE_INTTABLE                                          *
FORM update_inttable.
REFRESH : itab[] , itab.
CLEAR : itab.
IF NOT p_file IS INITIAL.
    CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
     EXPORTING
*     I_FIELD_SEPERATOR         =
       i_line_header            = 'X'
       i_tab_raw_data          = it_raw         " WORK TABLE
       i_filename               = p_file
     TABLES
       i_tab_converted_data     = itab[]    " ACTUAL DATA
     EXCEPTIONS
       conversion_failed        = 1
       OTHERS                   = 2.
    IF sy-subrc NE '0'.
      PERFORM callerr USING 'File Error!'.
      STOP.
    ENDIF.
ELSE.
    PERFORM callerr USING 'Choose the file'.
    STOP.
ENDIF.
ENDFORM.
*       FORM CALLERR                                                  *
* --> TEXT                                                          *
FORM callerr USING text TYPE string.
CALL FUNCTION 'FC_POPUP_ERR_WARN_MESSAGE'
       EXPORTING
            popup_title = 'ZMM_BAPI_PO_CREATE'
            is_error     = 'X'
            message_text = text
            start_column = 30
            start_row    = 8.
ENDFORM.
Regards
~Lakshmiraj~

Hi,
1. In Which system you are trying to run this ???? Are you running in IDES or currently running system?
   The reason may be if you are running in IDES , the factory calender may not be correctly positioned.
2. Also this error will occur at situations like....if your factory calendar will be of 2007 year....but the delievery date which you are giving is of 2008 . So error "delivery date exceeds factory calendar" occurs.
Some useful info for you,
Factory calander is must to run SAP. All the scheduling are calculated based on this only. You can define halidays for factory and assign to the calander. You can have 365 days calander / Sat& SU holiday calander or the holiday can be your wish.
The T code is SCAL. create holidays first. create holiday calendar and assign the holidays in holiday calendar. create factory calender and assign the holiday calendar in factory calendar.The Factory calendar is client specific
Rgds,
Lakshmiraj

Delivery date in Third party sales order

Hi,
If a sales order is created on 15th of October with TAS item category, system is proposing the delivery date as 22nd October. PR was released on 20th of Oct after backward scheduling and the plnd delivey time is 1 and GR time is 1 and the 18 & 19 are holidays.
Could any body clarify me why system is not considering 16 & 17 for PR release?
How the system proposes the delivery date as 22?
I kindly request you to clarify.
Warm Regards,
Sridhar Burugula

Dear Venkateswarlu,
Many thanks for your reply.
I have checked the document type (order) and the lead time mentioned is zero.
Could you please help me in this regard??
Warm Regards,
Sridhar

Purchase Requistion - delivery date

hi
there is a sub DC where replenishment takes place from a bigger DC only when safety stock goes down.
now when the safety stock goes down say today, MRP generates PR which has delivery date as today and with a release date in past based on planned delivery time, GR time etc.
but in real sense, it would be apt if system tells the delivery date in future considering the lead times and release date as today..
can it be attained by fwd scheduling ? if so how do i do for selective plants.
Pls suggest.
regards
joe

Is this sub DC defined as a plant in SAP ?
Which is the MRP type for the items (consumption: i.e. PD or somethig or reorder point as V1 ).
There is some kind of demand on sub DC so you can foresee this problem ?
without demand on the items, the system will react "later" when the SS is reached.
Whenever a demand exist, the MRP will prepare the supply element in advance....
Perhaps, if the consumption in unplanned, you should shift to a V1 MRP type , with a reorder point.

Delivery Date in Purchase Requisition

Hello all,
This could be a kind of familiar post but i need a clear cut advice on this particular aspect.
Delivery date in a purchase requisition is calculated based on PDT in material or purchasing info record. Date proposed would exclude the non working days as setup in the factory calendar. This is what my understanding with regards to the subject.
let's take this case.
#1. PR was created on 20th June so as per the Planned delivery time, delivery date should have calculated to 8th of august. But it's 30.07.2014
#2. Planning calendar:
Note: I do see an exception of 30 and rescheduling date is set to current date in the MD04 screen.
Procurement proposal was triggered for a customer requirement (created on 19.06.2014) with requirement date : 24.06.2014.
Please do help out.
Regards,
Rahul

Hi Rahul
Take a look on the following link, where the scheduling for external procurement is described:
http://help.sap.com/erp2005_ehp_06/helpdata/en/f4/7d29f344af11d182b40000e829fbfe/content.htm?frameset=/en/f4/7d29e644af1…
As explained here, the delivery date is firstly calculated to match the requirement date minus the goods receipt processing time. After that, the release date is calculated using the planned delivery time and the purchase processing time (defined on customizing). If you don't allow the start in the past on customizing, system switches to forward scheduling and the following procedure is used to schedule the order:
http://help.sap.com/erp2005_ehp_06/helpdata/en/f4/7d2a0d44af11d182b40000e829fbfe/content.htm?frameset=/en/f4/7d29f344af1…
BR
Caetano

Delivery date of PR in past

Hello,
We are having one PR which is created by MRP run. PR is created with the delivery date in the past.
PR requested date   :20.02.2014.
PR release date       :19.02.2014
PR delivery date       :19.02.2014.
Planned delivery time : 1.
GR processing time    : 1.
We are using APO for planning.when i tried to create a PR manually for the same material, below dates are got picked.
PR requested date : 26.2.2014
PR release date     :26.02.2014
PR delivery date     : 27.02.2014
Can anyone explain this?
Thanks,
Sankar.

Hello Sankar,
PReq delivery date of the purchase requisition consider the WEBAZ. Fisrt check you have same GR posiing time in ECC and APO.During this process, the factory calendar is taken into account.Variances occur if WEBAZ and the calendar do not match in the both systems.
Also check when this PR was created by MRP. In your both the case PR requested date is different 20.02.2014 and 26.2.2014.
What is result when you create manaul PR in ECC?
Go to SPRO > Materials Management > Purchasing > Environment Data > Define Attributes of System Messages > System Messages - Here make message no. ME039 i.e. Delivery date is in the past as E= Error.
Best Regards,
R.Brahmankar

PR delivery date vs PR release date

Similar Messages

Maybe you are looking for