Scheduling agreement JIT

Hello Experts
If Scheduling agreement is released JIT does still able to release before after the delivery date ? any restriction.
JIT is only for customer to notify the delivery date or on time ? or else back our own system also get restricted ?
thanks
MM

JIT is short term requirement and should be released well before delivery date as agreed with supplier.
[JIT|http://help.sap.com/SAPHELP_470/helpdata/EN/75/ee0fb555c811d189900000e8322d00/content.htm]
Edited by: Karthik on Aug 15, 2011 11:10 AM

Similar Messages

Schedule agreement-JIT and creation profile (are necessary to maintain)

Hi Friends ,
I am doing schedule line agreement in this way.
1) Create SA agrement -ME31L
2) Maintain schedule lines -ME38
3) MIGO-
4)MIRO
That is working.
A ) But then why it is necessary to maintain in material master under purchasing tab- JIT
and
B) in vendor master -Creation profile
Please can u explain me A and B
Regards,
Mahesh.

Hi Mahesh,
Maintaining JIT in material master is necessary only if you wish to Use JIT scheduling agreement schedule lines, if you are fine with only FRC schedule line, then you don't need to update this field. This is a control on the material level, like you know if a certain material can't be managed on a JIT level then you will not use it, so JIT agreements can't be created for it.
I don't feel Creation Profile is mandatory for vendor master, because you can opt to enter the creation profile in the Scheduling agreement additional data. Creation profile basically has a lot of control function, here isthe abstract from SAP Help
The creation profile determines:
    Which event triggers the creation of a scheduling agreement release (changes involving the lines of the overall schedule and/or the reaching of the next transmission date)
    How the delivery dates are shown (aggregation and release horizon)
    Whether Backlogs and Immediate Requirements are determined and shown in the scheduling agreement (SA) release
    Whether a tolerance check is carried out for SA releases that are created due to changes to the overall delivery schedule in the system
Regards
Chandra Shekhar

Scheduling Agreement JIT / Forecast calculating wrong

Hello experts,
I´m with a problem with JIT / Forecast.
The forecast are calculating wrong values. For example:
Cumulative quantity calculated: 584
JIT schedule:
DATE             TIME         Order Quantity       Cml. released quantity        Open Quantity
06.01.2012     00:00     32          32
10.01.2012     00:00     352          384
13.01.2012     00:00     128          512
17.01.2012     00:00     88          600              16
Forecast schedule
DATE             TIME         Order Quantity       Cml. released quantity        Open Quantity
20.01.2012     00:00     112          112
24.01.2012     00:00     224          336
27.01.2012     00:00     128          464
31.01.2012     00:00     200          664
The values of forecast are calculating by Cumulative quantity calculated that is 584 and I dont have any Open Quantity and in this case I need to have Open Quantity in Forecast.
The forecast must not be calculated by the amount in transit
Help me.
Tks
LFC

Hi ashish
Check the planning delivery schedule tab and go to item data -> delivery schedule header and check wheather any proper information has been filled or not
Regards
Srinath

Next JIT schedule date in Schedule Agreement

H, This is reg JIT - in Schedule Agreements
JIT schedules are created to day 10.02.2010 ..
In Creation profile for JIT, 'Changed or next date' is given & 'Weekly trans' option is chosen
I could see system calculated 'Next JIT sched' date as 15.02.2010 [Next week monday] , it is as expected
I created JIT today and i am not able to release today itself as part of testing solution. Even in production environment cant i release on same day of JIT schedules creation? why so ?
Help Says only those scheduling agreement items with respect to which the creation date is earlier than the current date are chosen for release generation."

I found the issue ...
output message for JIT was an issue
when i see JIT out message type properties for this message, Print parameters field was set to blanck
When i chenged to Purchase Group, it worked ..
Can some one help me what effect it had in generating message, before that message was green but i was not able to genertae JIT schedules

Scheduling agreement Fcst del schedules and JIT question

We have a requirement of not sending forecast delivery schedules TOR to MRP from SA.
Instead, we take this forecast delivery schedules and massage the data (add or delete) and then send it to MRP as regular forecast (PIR).
so when the JIT schedules come, does the forecast get consumed with the JIT's in MD04?
lets say, I got 100 pc for 2nd week of July 2011 as forecast delivery schedule from customer and I loaded them into MRP as PIR
and I got JIT for only 90 PC for the 2nd week of july 2011.in MD04 will the 90 get consumed from the PIR??

925,
so in system it will show on 3/21 monday
I guess this means that you are entering using a Day format rather than Week format.
You have answered you own question already. If the online SAP help, which you have read and reasonably paraphrased, is not clear enough to make you understand this, I cannot help you.
JIT horizon is 3/23, Forecast is for 3/21.
As I stated before, even though it may in your mind represent a week's demand, it is still for one day. There is no bucketing, nor time-based disaggregation, nor consumption. It is just a scheduling agreement.
You wrote
am using MRP indicator D. that means within jit horizon, consider my jit quanity for requirements. and after jit horizon consider my forecast delivery schedules as requirements.
. This is a reasonable paraphrase of the SAP online help. Do you believe this?
Forecast schedule is for 3/21. NOT for W 12/2011. This is before the JIT horizon, isn't it? What do you think will happen to the forecast schedule, looking at the last 'rules' you just wrote? and as stated in the SAP help that you read?
Now you want to enter JIT schedules. 21/22/23/24/25/26. JIT horizon is 23. 24/25/26 are after JIT horizon. What do you think will happen, based on the 'rules' you just wrote?
I feel my time is being wasted when you keep asking me these questions, already having the answers explicitly stated in SAP oinline help. Since you do not have access to a system, this cannot be a support issue, it is a evidently a matter of idle curiosity for you. I therefore believe I will will move onto other forum questions, where there is a possibility that the questioners will get some business benefit from my answers.
Best Regards,
DB49

Using a JIT call with stock transport scheduling agreement

Hi,
I have a requirement to send forecast schedules for a stock transport scheduling agreement from procuring plant to producing plant. Production would be done in producing plant against these forecast schedules. Producing plant would only ship against a JIT call (pull trigger) from procuring plant and not against a forecast schedule line. Is there a way in standard SAP to achieve this?
Thanks,
Krishna

I don't think so.
You need to transfer the production forecast as demand plan in the production plant. Have a MTS planning strategy (like 10), then manufacturing is triggered by this demand plan, and goods are stocked in the production plant, waiting for the pull call from the sales plant.
Don't forget to take care of the consumption of demand with STO (I think there's a note on this).

Scheduling agreement with relase - doc type LPA with JIT

Hi
can any one give the steps for Scheduling agreement with relase - doc type LPA with JIT process.. and explain how the JIT will work in SA.
Pls advise what are config required and what the user tcode needed to perform the SA with JIT concept.

Dear Friend,
Without release documentation(Document type LP)
The delivery schedule lines have official character-that is to say,they are transmitted to the vendor as they are saved in the system.The system does not document in detail releases aganist the scheduling agreement that have been sent to the vendor.Therefore,in the case of the document type without release documentation,the message control facility should be set up in such a way that a message is immediately sent to vendor if any changes are made to the delivey schedule stored in the system.
With release documnetation(Document type LPA)
If you use scheduling agreement with release documentation,the delivery schedule lines are not transmitted directly to the vendor.Intially ,the lines of the delivery schedule stored in the system for an LPA scheduling agreement for an internal information only.A message informing the vendor of your material requirements cannot be transmitted to the vendor until you explicitly create an SA release,that is forecast (FRC) or Just in Time(JIT) delivey schedule.Through this process,you can change the way schedule lines are represented.With release documentation,you can disply the SA releases(delivery schedules) transmitted to a vendor over a certain period of any time.This enables you to trace precisely when you sent which information to vendor.
Regards
Pramod

Procedure of scheduling agreement with jit

Can any one explain the step by step by procedure of creation of scheduling agreement with jit(just in time)
Vasu,K

Dear vasu,
The steps are
Step 1: Create Creation Profile in IMG under Scheduling agreement node
Step 2: Assign that creation profile to Material in the material master and the JIT indicator
Step 3: Ensure that creation profile copied to the SA, if not then assign it in the item detail
Step 4: Then run the Transaction for the delivery shedule creation
Ste 5: Check the shedule created
Thanks,
With regards,
Krishna Reddy

JIT Scheduling Agreement Not getting saved

Hi Gurus,
while saving a JIT scheduling agreement LZJ type in VA31 t-code, i am getting the following error;
"Call usages for LP 30075000 and JIT customer SAJ4 do not match. Message no JIT00 801"
can anyone of you let me know what setting is missing.
its urgent to proceed with testing...
thanks in advance
Sunil

Sunil,
If i am right you may have to check the following for "Controlled delivery profile" to function properly;
1. Ship to party in JIT agreement
2. Ship to partner description against JITV partner description
3. Usage field at header and item level in agreement
4. Shipping point
5. Route.
If all these are ok, then the error should go and document should get saved.
Regards,
Syed Nasir

Unable to generate a JIT schedule on a Vendor Schedule agreement using ME38

Hi,
I am having a problem generating a JIT schedule on a Vendor Schedule agreement using ME38
The message I get is 'Error generating release against scheduling agreement (cause 2)'
Yet when I use ME33L I can see the output under Header>Messages.
Any help gratefully appreciated...
Robin

Robin,
ME38 is to Maintain schedule lines. In ME38 Select line item and press 'Delivery Schedule' or 'F2' to see the schedule lines. Maintain the schedule line here.
ME84 is the transaction to generate JIT.
Please ensure to have JIT Indicator set in Material Master Purchasing View.
Regards,
Hari.

Schedule Agreements with JIT/FRC

We are using schedule agreements with JIT and FRC. When MRP runs it generates the delivery schedule lines with the delivery dates which appear on the JIT/FRC schedule. However, when MRP pulls in the date and suggests a new (earlier date) in MD04 under rescheduling date, the date on the delivery schedule and the JIT schedule do not reflect this rescheduled date. Is there a setting or some configuration I have missed. I need to have the delivery schedule and JIT schedule reflect the rescheduled MRP dates.

Thank you Ramakrishna,
I tried entering the data as you specified (below), but it still did not bring the rescheduled dates into the delivery schedule. I tried increasing the days and %, still no change. My rescheduled dates go back to March 07, but the delivery date still says 8/07.
A few questions:
In the Tol. profile under Legnth in workdays, what does this mean if I enter 10. Does it only check the previous 10 days? and what does each period do? Do I need to specify days and %'s in each period?
<b>Tolerance Profile</b>
You specify 10 days as the checking period for JIT schedules, since this corresponds to the release horizon. You enter 5% as upper and lower tolerance limits and choose Overall check.
Regards,
Elizabeth

Jit Scheduling Agreement and JIT customer

Hi All,
while I am creating new Scheduling agreement system asking to assign first JIT customer assignment before saving.
Where we set this condition.
Chidambaram

As you have probably already discovered, the Partner Description stored on the Ship to line of the Sold to customer master links to the Partner Description in the JIT Customer on JITV and links to the Partner Description in OVAI (This last, so that you get the Forecast Idocs and the JIT Calls posting to the same SA)
And in my experience, once you set up a LZJ type SA for a particular Ship to, you cannot change the Ship to, like you can do on LZ type SA's.
If you need to abandon a SA that already has JIT calls posted, 1) create the new SA, 2) flag the old with "reason for rejection" and 3) use JITR to move the JIT Calls from the old one to the new one.

How to measure performance of supplier when using scheduling agreement ?

Hello all,
My client has an absolute need to be able to measure the performance of its suppliers based on delivery dates and delivered quantities. That is to say he needs to be able to compare what dates and quantities were asked to what has been really delivered.
Most of the procurement processes used are based on scheduling agreements : schedule lines are generated by MRP and forecast is sent to supplier while firm requirements are sent through JIT calls.
It seems that when doing GR in MIGO, it is done against the outline agreement number, and not against the call. Therefore, we have no way to compare dates and quantity with what was expected (in the JIT call).
Do you know if SAP proposes a standard solution to this, and what could be a solution to this issue ?
Thanks for your help
E. Vallez

Hi,
My client faced the same problem and we ended up developing an own analysis in LIS. Since the GR is not linked to specific schedule line (SAP does some kind of apportioning, but it doesn't have to correlate to the correct match), one needs to do assumptions. Our assumption was the closest schedule line, i.e. each GR is related to the schedule line with the closest date. Then all GR the same day are totaled together before the quantity reliability is calculated, since the very same shipment can be reported through several GR transactions in SAP (one per pallet).
If anybody has info about what SAP has to offer in this question (or is developing), please tell us!
BR
Raf

Error In scheduling agreement proccessing

Hi Friends
1. If I enter new schedule line in JIT Delivery tab of scheduling agreement and try to save it , it is throwing error that u201CDelivery go ahead was reducedu201D. Message no. V4042.
I went ahead and saved the scheduling agreement .
2. When I try to create delivery with reference to this scheduling agreement it is throwing error that u201Corder canu2019t be deliveredu201D Message no. VL461 and no schedule lines are due upto selection date .
Could you help me to correct it .
Jaya

Hi Jaya,
what i meant is that, if you have changed the existing JIt delivery schedules i.e changing the existing schedule line qty.
If the Jit delivery schedules are not saved with open quantity in the Scheduling Agreement, cannot creat delivery for that schedules.
Regards
vk

Expired Scheduling Agreements still in Credit Check / Rescheduling

Hello everyone,
I am running into an issue with expired Scheduling Agreements on the SD side (VA31,VA32, etc.). There are many Scheduling Agreements that expired on a range of dates from 2005 to 2009, SA's that customers will not send JIT delivery schedules for anymore and are basically just out in the open and unused. The issue is that these Scheduling Agreements are still being taken into account when a credit check is run. Additionally, when our rescheduling jobs run at off-hour times, the system is still attempting to allocate materials to these orders. The main problem with this is that it causes additional processing time for the rescheduling job.
The current business process for these old Scheduling Agreements is to reject all the line items within the applicable SA, and as a result our rescheduling jobs avoid these orders, and they do not show up in VKM4. However, the Valid To date in the SA is clearly in the past and I'm wondering if there is a way to have these closed without having to reject every line item.
Any help would be greatly appreciated.

Andy
For credit check I would recommend:
1) Using your own routine to exclude expired sch agreements in OVA8- Document controlling- 'No credit check' field.
2) rejecting at header level/ using "mass'.
For Rescheduling
1) Using button "Unconfirmed documents required" checked.
2) Creating your own copy of the program SDV03V02 including document number, document type in the selection fields and creating a variant excluding specific, expired Sch Agreements. To reduce processing time, you may also try the 'divide and rule' policy and execute several parallel/serial runs by using ranges of materials, plants, document types. I am sure you might have already tried this.
Hope this helps.

Scheduling agreement JIT

Similar Messages

Maybe you are looking for