Committed Date Calculation in an STO

Hello,
Can anyone detail how exactly the committed date is calculated during an availability check for an STO?.
Thanks.

STO Delivery Date is receipt date at destination location. This minus Transportation Lead time is STO requirement date at source.
When you conduct ATP check for this PO/STO, your committed date is updated at source and delivery date will be updated as committed date plus TL lead time. Also check SAP help at http://help.sap.com/saphelp_45b/helpdata/en/41/191fce45fd11d188ff0000e8322f96/frameset.htm

Similar Messages

How does committed date in STO- different company codes gets calculated

Dear All,
Please let us know How does committed date (ATP date) in the STO across different company codes gets calculated
Regards
Ahmad Idais

Hello,
RA is always a Company Code specific process due to the possibility of financial postings. I think that your WBS structure better be reconsidered not to mix up different Company codes at different levels, but maybe having a parallel nodes for different Company codes.
I also believe there is a consulting OSS note to explain the standard system behavior, just search the OSS.
Since you already have a master data in place it must be quite easy for you to test how the system behaves.
Regards,

Why the committed Date of STO becomes 12/31/9999

Hi Please help me, just new in STO.
We have the problem in STO where if checking md04, available stocks still is on 500K++
though there are entries such as Open SO qty and some delivered items already.
But what happen is the STO was created sept 28 but we put delivery date of it as dept 17 earlier
than those dates in delivery.
still if checking the stocks, deliver items doesnt short the stocks buy why
sto committed date becomes infinity date.
does the open so quantity consumes the stocks already?
is there a way we can see where the priority of stocks allocation is set in the configuration?
thank you

Hello,
If not all quantity can be confirmed for the delivery date,
and the ATP-chek runs without Replenishment lead time, the system set
the committed date to 12/31/9999. This is the normal system behavior
and not an bug.
During an STO-process the system check the availability in the supplying
plant(APO) for the date when the delivery has to be created (ekpv-ledat)
This date can be determined with shipping data determination or
without, accordingly your settings in customizing OMGN. Without the
system takes only the planed delivery time into account. This time
can be different in PREQ and Material master so it can be different
in the time when the system checks the availability if you create the PO
with reference to an Preq or without.
In addition, the committed date in the PO is only for informational
purposes, it is not interpreted by the ATP check since the ATP situation
might have changed immediately after the committed
date was calculated.
Regards,

Committed quantity and committed date in STO

Hello friends,
How and on what basis the committed quantity, committed dates updates in STO delivery schedule tab while doing the STO.
Regards,
Cherryk

Cherry,
During configuration of STO's, an availability check is assigned (IMG > MM > Purchasing > Purchase order > Set up Stock transport order > Assign delivery type and checking rule).
Because of this, during the creation of a STO, the system will perform an availability check for the material in the source plant. The results of this ATP are the two fields that you have mentioned. Zero in committed quantity means that the ATP check found no material available, according to the ATP check you have assigned, on the date you have proposed. A quantity less the entire quantity of the STO indicates that only a portion of the STO requirements was found to be available on the proposed date in the supplying plant.
Any time the committed quantity is less than the entire quantity of the STO, it means there is no assurance that there will be product available when the day comes to actually create the delivery note and PGI the STO.
Any time a requirement is not committed during an ATP check, the possibility also then exists that other requirements in the supplying plant (such as new sales orders, or new production order dependent requirements) may take stock that you intended for use in your STO. It is always wise (but not mandatory) to manipulate your STOs so that committed qty = delivery qty.
Rgds,
DB49

Doubts in statistic Delivery Date and Commited Date in STO PO

Hi,
I would like to know statistic delivery date and Commited Delivery date in STO PO.
2 different type of date is displaying STO PO like;
1. We are getting statistic delivery as "09.02.9999" and Commited Date as "09.02.2011"
2. 1. We are getting statistic delivery as "09.02.9999" and Commited Date as "09.02.9999"
Could you explain, where we are maintiang those date and how it is displaying in PO Delivery schedule line?
Thanks.
Dhanush.

When you create a PO, then the statistical delivery date is set equally to the delivery date.
the statistical delivery date is automatically changed if you change the delivery date before you have outputted the PO.
After you outputted the PO, the statistical delivery date has to be changed manually by the user if he changes the delivery date.
the idea behind this is because of the vendor evaluation, the vendor evaluation is done with the statistical delivery date.
as long you have not printed/faxed/mailed the PO to your vendor, then the statistical delivery date is changed automatically with a delivery date change.
But after a transmission you always have to ask yourself, who is responsible for the change in the delivery date.
If it is you, then you have to change the statistical delivery date to the new delivery date manually, to avoid that the vendor gets valuated against the wrong delivery date. But if it is because the vendor cannot meet the delivery date, then you change the delivery date to have an accuracy for planning, but you keep the old date in the statistical delivery date to valuate the vendor against it.

Committed date in delivery schdule ?

hii
Some body can explai nme
From where the committed date is fetched in delivery schedule tab in item detail level in PO??
Thanks

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.

Shipping data of plants in sto

Dear Guru's,
I want to know in detail about the configuring shipping data of plants in STO.
Suppose if I am having One manfacturing plant and 3 depots.
In the shipping data of the supplying plant, what should i fill in the fields of internal customer and sales area.
And in the shipping data of the receiving plants, what should i fill in the fields of internal customer and sales area.
regards

hi
STOCK TRANSFER ORDER
Follow STO Process for this;
1.Create a vendor for the company code of receiving plant, using account group :0007 using T-Code XK01.
2. Assign this vendor to Delivering plant
Go to XK02 >Purchasing view>Extras>Add. Purchasing data>Plant
3. Create internal customer with the sales area of the vendor. Go To XD01
4. In Pricing procedure determination relevant to STO, assign document Pricing Procedure and customer pricing procedure appropriate for STO to get the pricing in the invoice.
5. Maintain condition records for the relevant pricing condition.
6. Some more setting for STO: Go to MM> Purchasing > Purchase Order > Set up STO > define shipping data for plants > Go to Receiving plant >assign customer here & Supplying SA (for billing) to Receiving plant here
7. Go to MM > Purchasing > Purchase Order > Set up STO > define shipping data for plants > Go to Supplying plant and assign the sales area of receiving plant.
8. Go to MM > Purchasing > Purchase Order > Set up STO > assign delivery Type & Checking rule
Assign the delivery type to document type. In this case, Delivery type NLCC is assigned to Document type NB
9. Go to MM> Purchasing > Purchase Order > Set up STO > Assign document Type, One step Procedure, Under delivery tolerance
Assign the document type NB to supplying plant and receiving plant
10. After all settings , Create the STO using T-Code:ME21N and maintain pricing conditions of freight and Save.
11. Create Delivery :VL10G
Click on the Background Button after selecting line item
A message is flashed : See log for information> next Click on Log for delivery creation Button >click on line item>click on document button to get Delivery document No
12. Picking, PGI:VL02N
13. Billing:VF01
Save the document and its done
14. J1IIN - Outgoing Excise Invoice
15. MIGO - Goods Receipt against outbound Delivery
16. J1IEX - Capture & Post Excise Invoice
Pricing configuration for STO: -
In SPRO > MM > Purchasing > Conditions > Define Price Determination Process > Define Schema Determination > Determine Schema for Stock Transport Orders > Here assign Calculation Schema "RM2000" i.e. Stock Transfer Document to Schema Grp Pur. Org, STO Type (For e.g. UB) and Supplying Plant.
Calculation Schema "RM2000" has condition type P101 which will pick up the MAP of supplying plant automatically during creation of STO in ME21N ("Conditions" Tab).
You can create new freight / delivery cost conditions in M/06 and assign in pricing procedure "RM2000" in M/08 and also assign the Accrual Key to this and do the Account Determination for this Accrual Key in OBYC
At the time of PGI, following accounting entry will get generated;
Stock A/c - Dr - 110 INR (Receiving Plant)
Stock A/c - Cr - 100 INR (Supplying Plant)
Freight Clearing A/c - Cr - 10 INR (Supplying Plant)
regards
KI

Schedule Line Delivery Date Calculation with Transportation Scheduling

Hi All,
We are currently running into a problem where our Sales Order Schedule Line delivery dates are being pushed out too far into the future - because of the Calendar being used to determine the transit time.
We have 'Delivery Scheduling' and 'Transportation Scheduling' activated for our Sales Document type
We have Routes that are configured with a 'Transit Time' and a 'Factory Calendar'
Order Scenario:
'Factory Calendar' assigned to our 'Route' is setup with only one 'Workday' in a given week e.g. Wednesday
Our 'Route' has a Transit Time of 2 days
We create a Sales Order on Monday for a Material that is available in our Plant
The 'Goods Issue' date is being determined correctly for the next Workday - being Wednesday
The 'Delivery Date' is extending out over 15 days (2 Wednesdays into the future) - since it is working on 'Calendar Days' and not 'Actual Days'
Does anyone know of a way (config or other) to only influence the 'Goods Issue' date with the 'Factory Calendar' assigned to the Route, and have the 'Delivery Date' calculated using the Transit Time on the Route and 'Actual Days' rather than Calendar days?
All help greatly appreciated.
Thanks,
Ravelle<i></i>

Hi Pathik,
Thanks for your reply. I have already maintained the Calendars I'm using for this business process in <SCAL> - same as <OY05>.
The problem I'm having though is that by assigning a Calendar directly to my route (which I doing to influence the goods issue date - using a 1 Working Day Calendar) it is also taking precedence in determining the Transit time - which in this case I don't want, as I want my Transit time to be determined using a 5 Working Day Calendar.
I don't think this problem has a config option as a work around...I think the only possibility in this case is a development to achieve the results we need.
Thanks,
Ravelle

SAP Inter company PO Checking rule and commitment date

Hello there,
I am trying to understand the commitment Qty and commitment Date on the NB type PO between two different plants.
I have a setup where my Plant1 buys from Plant2 and Plant1 takes 100 days to get it from Plant2.
Plant2 will source it from Vendor1 and takes 200 days for the Vendor1 to supply to Plant2.
Plant 2 does not have any stock today, the stock from Vendor 1 will arrive only on 6/10/2015, there is an Open PO for Vendor2 for GR will be done on 6/10/2015. So on 6/10/2015, there will be a stock of 2500 units.
No other requirement exists in MD04 for this material in Plant 2.
Plant1 is raising a PO for Vendor Plant2 on 3/27/2015 for 1000 units. The planned delivery date is 100 days on Plant1 Material Master. So the delivery day is shown on PO is 100 days from now which is 7/5/2015.
Considering the fact that Plant2 is receiving 2500 on 6/10/2015, why wont SAP commit to the Qty. When I do the availability check, it does not consider the 2500 units coming in from PO and from CO09. The checking rule does not consider the Purchase Order Qty.
Now, here is where I need clarification.
The checking rule says not to consider Purchase Order in the in/out movement, So when I play around with this check I was able to commit the Qty on the PO. When I take out the check it will not commit the Qty and puts the commitment date based on the Plant 2 planned delivery time ( the time Plant 2 takes to buy it from the supplier).
It makes sense so far, however when excluding Purchase order to be considered for my purchase order availability check and when I remove the 200 days from Plant2 material masters planned delivery date and then create a purchase order, my PO is committing the QTY, how is this explained? or am i having some bad setup somewhere.
Same exact checking rule i.e excluding purchase order, everything else constant.
Scenario 1: Qty committed on PO when Planned Delivery time on Plant2 is zero days
Scenario 2: Qty not committed on PO when Planned Delivery time on Plant2 is 200 days
Can someone assist me to understand this. thank you

Anyone thoughts? thanks

Message "iTunes could not sync contacts to iPhone because an error occurred while committing data"

Hello all. I recently replaced the HD in my MacBook Pro. Just after, I retrieved my old files from the Time Machine backup, which I made just before the replacement. During the first sync of my iPhone via iTunes and while I was trying to sync my contacts I saw the message "iTunes could not sync contacts to iPhone because an error occurred while committing data". After that, I lost my iPhone contacts (I have them only from iCloud). The only problem is contacts, all the others (Calendars, Apps) are normally syncing. Does anybody has a solution? Thanks in advance!

hello,
There was a similiar posting that I have seen from others and they found out that the back up was bad. https://discussions.apple.com/message/6139533#6139533
I would use a previous backup (earlier one) to the one you have tried to just do.

Date Calculation in BEx

Hello All,
In my report, User wants to see a day counter which is the dfference of a date (date coming from cube) and Current date. For current date we are using 0f_aday sap exit. How we can we acheive this, does it involve any User exits at the back end or can I use a calculated keyfigure to find the difference between these two dates.
Please reply to this as it is very Urgent Issue
thank you

HI AL,
Thanks for the udpate. But I believe we can update any thread if its related with the same subject if its less than 3 years. Is it not right ? I have a mail in my inbox, from some moderator confirming the same. That is the reason I have updated this thread...as its related to the same question and this thread is created n 2011.
Anyway, thanks for the answer. I will change the dimension to date and calculate the difference from the 2 variables.
Reg another doubt, from the below link...
https://docs.google.com/viewer?a=v&q=cache:YQS2jPhWysAJ:www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/705734f2-4e85-2e10-2ebf-891d0110de74%3FQuickLink%3Dindex%26overridelayout%3Dtrue+&hl=en&gl=au&pid=bl&srcid=ADGEESjL8dx81tAAJNL0Ln4c2MW4k3yZRDNFsop1pptOc3bQf1xU0Le9e3loFsZXJi5rWuYt3j7yoStGMktsL5XEdV9T3ONzdKay0x5yrIbaUBB3Dpz1Fr6xuggf_IZX-S0Q4WONpBhN&sig=AHIEtbTZfXXLN4gZCsw7qpZXgrkjeCYLcA
what is the field used for Interval ( from, to , range) . You have missed my other question, why am I getting X below the result while doing the date calculation . I mean I am getting the result, but below every row, there is a X . Any ideas ?
Thanks,
DR

Due Date Calculation on A/R Invoice

The Due date calculation on an Invoice for a customer with a payment condition of 30 days is wrong on the system:
Invoice DocDate: 11.05.17
Invoice DueDate: 11.07.01
On the BP Master Data is set a payment condition of 30 days. So it should be a due date of June, not July. This is a invoice that comes from a Sales Order with Approval Procedure.
Our version is 2007 A SP:00 PL:49.
Thanks in Advance...

Hello,
Perfect Notification
For Payment Terms for Business Partner----
IF (@transaction_type = 'A' Or @transaction_type = 'U') AND @object_type = '17'
BEGIN
Declare @GroupNum as Nvarchar(20)
Declare @OCRDGroupNum as Nvarchar(20)
Declare @PaymentTermCode as Nvarchar(20)
Declare @PaymentTermName as Nvarchar(20)
Set @PaymentTermCode = (Select GroupNum from OCRD where CardCode = (Select CardCode from ORDR where DocEntry =@list_of_cols_val_tab_del))
Set @PaymentTermName = (Select PymntGroup from OCTG where GroupNum = @PaymentTermCode )
Set @GroupNum = (select GroupNum from ORDR where DocEntry =@list_of_cols_val_tab_del)
Set @OCRDGroupNum =(Select GroupNum from OCRD where CardCode = (Select CardCode from ORDR where DocEntry =@list_of_cols_val_tab_del))
If @GroupNum != @OCRDGroupNum
     begin
          SET @error = 10
          SET @error_message = N'Payment Terms Should be ' + '   ' + @PaymentTermName + ' ' +' For this Business Partner'
     end
END
End----
It will Definatillly Help You.
Thanks
Manvendra Singh Niranjan

Baseline date calculation

Hi,
We have a requirement to exclude non-Business days while calculating Baseline date(for the Accounting Document created on saving the Billing document)
Currently the Baseline Date being populated in the Accounting Document is Document date + 5days(including Holidays).
For eg
Current Scenario
Document Date: 12th Feb 2008
Baseline date: 17th feb 2008.
Requirement:
Document Date: 12th Feb 2008
Baseline date: 19th feb 2008(Excluding Sat & Sun).
Request you to share useful info in this regard.
Thanks
Binu

Hi,
Use user exit RV60FUS5 for these base line date calculations.
Thanks
Krishna.

Baseline date calculation excluding non-Business days

Hi,
We have a requirement to exclude non-Business days while calculating Baseline date.
Currently the Baseline Date being populated in the Accounting Document is Document date + 5days(including Holidays).
For eg
Current Scenario
Document Date: 12th Feb 2008
Baseline date: 17th feb 2008.
Requirement:
Document Date: 12th Feb 2008
Baseline date: 19th feb 2008(Excluding Sat & Sun).
Request you to share useful info in this regard.
Thanks
Binu

Hi,
Use user exit RV60FUS5 for these base line date calculations.
Thanks
Krishna.

Baseline date calculation in Invoice verification (MIRO)

Dear experts,
I need to set baseline date after 40 days from document date in MIRO.
Baseline date calculation of "Terms of Payment" in IMG has two parameters:
・Fixed day
・Additional months
We cannot set 40 days in these parameters.
Can anybody tell me how to set baseline date not month but date(not fixed day) ?
Please advise me on the settings SPRO>MM>Purchasing>Vendor Master>Define terms of Payment.
Thanks & Regards
Ken

Hi,
You can't do this.
The baseline date is the date on which the calculations are made.
So if you have 40 days to pay, this will be 40 days from the baseline date.
This will either be the document date or another date, but you can't (in standard SAP) have the baseline date as "X" days after "Y".
So the baseline date is the date of an event (e.g. the date that the Invoice was posted) not a calculation.
Is it possible that you have misunderstood the use of this date?
If you just want to ensure that the payment date is 40 days after invoice recipt, then set you just have to enter the number of days in the payment terms and the baseline date stays as the invoice date (etc.)
Steve B

Committed Date Calculation in an STO

Similar Messages

Maybe you are looking for