Problems in GR for forecast delivery schedule

Hi all,
Whenever i try to post GR for forecast delivery schedule the systeme proposes a quantity equals to 0 evev though i sent the form to the vendor(using trans me9e &me9l).
Anubody knows why?

Hi Moshe,
If you are using your scheduling agreement type LPA(with document).Check wheather you have released the FC schedule in ME38.In the delivery schedule>edit>generate forecast schedule.
Then only you will get your message output in ME9E and MIGO.
regards
venkadesh

Similar Messages

About selecting Scheduling Agreement and Forecast delivery schedule

Hi Experts,
i want to write a Report, with 2 parameters for the selection : Sold-to-party and Period
For this Sold-to-party/Period, I want to list all scheduling agreement + Forecast delivery schedule.
I already found the Function SD_VBEP_READ_WITH_VBELN to read all Forecast delivery schedule lines using Sales Doc.No. , but how can I select all Scheduling Agreement for the Period ?
Regards,
David

Solution:
by selecting data from table VEPVG (Delivery Due Index) and using function SD_VBEP_READ_WITH_VBELN for each SD Document.
Regards,
David

Forecast delivery schedule lines consumption

Hi,
I cannot fully understand what is the logic behind the consumption of the forecast delivery schedule lines. This is how the problem can be exactly defined:
- scheduling agreement with delivery orders (LZM)
- JIT delivery schedules are not used and no delivery schedule is maintained... just a forecast delivery schedule
- the whole process is manual, there is no EDI implied
- the cumulative received quantity is updated by an ABAP development that is triggered at delivery goods issue
The rest, happens normal - forecast schedule lines are updated weekly, the customer send pick-up sheets, a TAM delivery order is created, then delivery, GI...
The problem: not always the MRP requirements generated by the forecast delivery schedule lines are consumed by the delivery order/GI. If the delivery orders / deliveries are made on the exact quantity of the schedule lines everything works fine. It is also ok when there are two successive delivery orders with a cumulative quantity that matches exactly the forecast line. As soon as a over-delivery is made, everything turns upside-down: older delivered schedule lines appear again in planning as if nothing was delivered until now...
I suspect that the problem is related to the fact that the whole process is manual and updating the cumulative received quantity is not the only parameter that is counting... is it so? Or the forecast delivery schedule has to be respected 100% in terms of quantities and timing?
I would really appreciate your help.
Regards,
H.

Also please clarify whether delivery schedule lines in ME38 (even it is created automatically), in Planning time fence, will get affected by MRP run.

Forecast delivery schedules incorrect cumulative release quantity.

Hi Gurus,
We implemented the standard LZM - Scheduling agreement with delivery orders solution for component suppliers.
The entire SAP standard configuration activated and the functionality is working correct.
u2022     Scheduling agreement type LZM / Item category LZMA / Schedule line category L2
u2022     Order Type TAM / / Item category TAMA / Schedule line category CP
Example:
Scheduling agreement forecast delivery schedule for 1000 units./ Md04 show SchAgr of 1000 units
Delivery order for 250 units (MD04 Shows Order for 250 units and SchAgr for 750 Units)
Created delivery for the order (MD04 shows Deliv. For 250 units SchAgr for 750 Units)
Goods issue the delivery / MD04 shows the SchAgr for 750 units.
*Issue:*
When we update the Cumulative quantity received by the customer it is summing up with the forecast quantity (double counting the shipped quantity).
When the Cumulative quantity received by the customer updated to remove the in-transit quantity, the forecast is adding by 250 units and   MD04 shows SchAgr for 1000 units.
Thanks & Regards
Suresh

Hi Suresh
The *** issued qty gets updated when the PGI for the delivery happens. There is a field called *** received by customer and it gets updated when customer sends the *** back in the 830 or 862 as the case may be.
The difference between the *** issued and the *** recieved is always shown in transit.
If you do not want the schedule line to be opened up, then in *** recd change it to the *** issued or ideal option is populate the last delivery PGI'd on the delivery number field next to *** recd field. Hope this helps and let me know if you need any more informataion
Regards

Forecast delivery schedules and JIT deliveries

Hi Gurus,
Got a question on sales scheduling agreements schedule lines. Our customer sends 10 weeks of forecast delivery schedules and 2 weeks of JIT deliveries. which one of these two are passed to MD04?
Assuming only forecast delivery schedules are seen in MD04:
Assuming customer sends forecast delivery schedule for week2 as 50. but in JIT deliveries he only sent 40 for that week. if only forecast deliveries are see in md04, then my forecast and planning quantity is 50 , but actually my JIT delivery is only 40. AM I producing 10 extra? that means my planning is wrong?

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

Importance of Forecast Delivery Schedules in SD scheduling agreements

Hi ALL,
I would just like to consult you a scenario that I'm facing.
When I create a JIT scheduling agreement, even though that schedule lines are maintained for the JIT delivery schedule tab, if the Forecast delivery schedule tab has no schedule lines, the NET value of the document will be zero.
Can you explain the Logic behind this?
Also, why am I not allowed to create an outbound delivery and invoice if the Forecast Delivery schedule tab has no schedule lines?
I know that the document will be incomplete without the net value, but why is it even though schedule lines are created in the JIT tab?
Please help me with this.
Thanks in advance guys!

This is what I found out in an SAP “Knowledge Base Article" (1472965), indicating that there has to be requirements in the forecast delivery schedule in order for the schedujle agreement line item to not be considered incomplete for price.
https://websmp230.sap-ag.de/sap/support/notes/convert2pdf/002007204200000153012010?sap-language=EN
Resolution
l You have to enter schedule lines for the forecast delivery schedule
l The VBAP-NETWR is calculated based on forecast delivery schedule and not according to the JIT delivery schedule
Regards,
Jeff

Planning delivery schedule , forecast delivery schedule , JIT delivery sche

Hi
could any one tell me the difference between Planning delivery schedule , forecast delivery schedule , JIT delivery schedule & their respective ways of processing delivery???????????????????????????????????????????????/

Hello Friend,
Planning Delivery Schedule:
You want to plan requirements for a certain customer for the next 16 weeks. You create a planning delivery schedule on the basis of information that you have gathered in an internal planning system. A few days later, the customer sends you a forecast delivery schedule that covers only 12 weeks. You decide to generate a planning delivery schedule by copying the schedule lines from the forecast delivery schedule for those 12 weeks, splitting them into units and days that fit your production schedule. For the remaining four weeks that you require, you simply adopt schedule lines from the previous planning delivery schedule in the scheduling agreement.
For another customer, you create a six-week planning delivery schedule on the basis of internal data. When the customer sends in a forecast delivery schedule for the same six weeks, you notice that the first four weeks of schedule lines in the customer delivery schedule are detailed enough for production, but the last two are inaccurate. You decide to copy the first four weeks of schedule lines unchanged into the new planning delivery schedule. You adopt the remaining two weeks of schedule lines from the previous planning delivery schedule, which already exists in the scheduling agreement.
Forecast Delivery Schedule:
For an SD scheduling agreement, a customer sends a forecast delivery schedule containing requests for individual schedule lines. On the SD side, a delivery can be created automatically from this.
JIT Delivery Schedule:
A release carried out at an exact point in time of quantities in a schedule line (of a delivery schedule).
The JIT delivery schedule is way of fine tuning production for the customer and shipping for the vendor.
The term is used predominantly in the automobile component supplier industry.
Delivery in Forecast in done through VL10 & VL01N and Delivery through JIT is done from JITK.

Problem with pgi for returns delivery

Hi,
I'm trying to do PGI for returns delivery through BAPI_GOODSMVT_CREATE.
The when the delivery is opened through VL02N, the Post Goods Issue button has Post Goods Receipt text written on it. When the GI is done, the material document has movement type 651.
However I'm not able to create the same through the BAPI. I have tried various combinations of GM_CODE and all other variables. Have anybody of you tried doing movement type 651 for a returns delivery using the same BAPI?
Please reply if you've come across some similar situation. I know how to use the BAPI, I've been using it successfully for other movement codes etc. It's only in this case that I'm stuck up.
Regards,
Vijay

Hi Vijay,
can u pls tell me how did u do it....i am also having the same requirement....
Developed a custom program for creating and updating Goods Movement Document by using BAPI_GOODSMVT_CREATE & WS_DELIVERY_UPDATE_2.
thanks, Ankita.

Delivery schedules in SA(LPA)

Gurus,
I have created a LPA scheduling agreement and generated JIT schedule lines with Firm and Tradeoff zones through MRP.
Now, I want to release them manually.
could anyone let me know how these have to be released and sent to vendor with all the information about the zones.
I would really appreciate your help in this regard.
Cheers
Mittu G

Hi
You can create the SA release using transaction ME84.
Use transaction ME35L for approving/releasing the scheduling agreement.
For SA releases to be transmitted as messages to the vendor, the following settings must be made in Customizing for Purchasing:
Releases (Message Determination) at Item Level
In order for a separate message to be generated for each SA release (i.e. per scheduling agreement item and release type), you must set the Release message indicator in Customizing for Purchasing under
Define Message Schemas for SA Release/Expediter - > Assign Schema: SA Release/Expediter.
If you do not select the Release message indicator, the messages will be generated at header level. You can then view the messages under
Header-> Messages.
If you select the Release message indicator, the messages will be generated at item level. The messages generated are listed in the release documentation.
If you have initially not selected the indicator, messages will be generated at header level. If you select the Release message indicator at a later point in time, you will find the newly generated messages in the release documentation. You will still find the already generated messages under Header ->Messages.
Define "Main Message Type"
You must designate just one message type as the "main message type" for each SA release type (FRC or JIT delivery schedule) in Customizing for Purchasing, and set the indicator A (update print-dependent data) for this message type.
This means that when an SA release with the "main message type" is outputted, the print-dependent data is updated in the SA item, the SA releases, and the delivery schedule lines. Only if an SA release is outputted with the main message type is it taken into account in the current stock/requirements list, for example.
You set this indicator using the fine-tuned control facility for the message type.
In the case of scheduling agreements with release documentation (document type LPA), the message types LPH1 and LPJ1 are used for forecast delivery schedules and JIT delivery schedules respectively in the standard system.
In the case of scheduling agreements without release documentation (document type LP), the message type LPET is used in the standard system. In this case, no release is created. Instead, the message is generated as soon as the scheduling agreement delivery schedule (specifying the scheduled quantity) is created or changed.
Outputting Releases in the Main Message Type
All releases must always be created with the main message type because the system will otherwise not update the print-dependent data. This is particularly important if you are working with different message types.
You send SA releases to the vendor with the main message type LPH1. You provide the forwarder or carrier with a copy (message type LPH2) and create a printout for your own files (message type LPH3).
If you send SA releases to the majority of your vendors as printouts (i.e. in hardcopy form) and have an EDI arrangement with just a few of them, you can create message records for the main message type:
At document type level with the transmission medium "Print", and
At vendor/purchasing organization/EDI level with the transmission medium "EDI" for the EDI vendors.
Do not set the change indicator in the message overview. A set indicator has no effect in the case of scheduling agreement releases. As a general rule, the system outputs all releases that have not yet been transmitted.
For full details you can follow the link
http://help.sap.com/saphelp_47x200/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
Thanks & regards
Kishore

SA delivery schedule release problem

Hi all,
I am created a schedule agreement (Type LPA) and created delivery schedule for it.
When I am trying to release the delilvery schedule using ME84, I am getting the follwing error.
Msg No 06/857 -> No message record found.
I created condition record through NACE for Allication area EL, output type LPET. Still the problem persists.
Require your suggestions.

How to release directly from ME38 ?
I tried in the path delivery sche > Edit > generate Forc Sche
but the msg below:
Error generating release against scheduling agreement (cause 2)
Message no. 06857
Diagnosis
The function module for generating a scheduling agreement release (forecast delivery schedule or JIT delivery schedule) has run up against an error, causing processing to be terminated.
In this case the cause of the error is 2.
*System Response*
The error may involve one of the following situations:
1: The nature of the error cannot be specified precisely.
2: The forecast delivery schedule or the JIT delivery schedule was generated but no message record could be generated.
3: A document type for which the functions "Generate forecast delivery schedule" or "Generate JIT delivery schedule" are not defined may be involved.
4: A material for which the function "Generate JIT delivery schedule" is not defined may be involved.
5: A scheduling agreement that has not yet been released by all persons responsible may be involved.
6: The factory calendar has not been maintained correctly.

Forecast delivery schdule and JIT delivery schedule difference

Hi All,
What isthe difference between Forecast delivery schdule and JIT delivery schedule in JIT scheduling agreement (LZJ)??
I am doing JIT Inbound process now. Is it necesary to update both the schedule lines(Forecast delivery schedule&JIT delivery schedule)??
Thanks,
Anbazhagan E

Hello,
Forecast Schedule updates your planning , i.e. in MD04 you could see system is planning for quantities updated in forecast schedule.
regards,
amol

Zreports for vendor wise Delivery schedule release

hi ,
Can some one help me with codes for the reports for the Delivery Schedule Release vendor wise. which shows vendor details , on titles, Schedule agreement Nos and then the material listed with the qty and targetted date.
Kindly help
regards
Kim

How to release directly from ME38 ?
I tried in the path delivery sche > Edit > generate Forc Sche
but the msg below:
Error generating release against scheduling agreement (cause 2)
Message no. 06857
Diagnosis
The function module for generating a scheduling agreement release (forecast delivery schedule or JIT delivery schedule) has run up against an error, causing processing to be terminated.
In this case the cause of the error is 2.
*System Response*
The error may involve one of the following situations:
1: The nature of the error cannot be specified precisely.
2: The forecast delivery schedule or the JIT delivery schedule was generated but no message record could be generated.
3: A document type for which the functions "Generate forecast delivery schedule" or "Generate JIT delivery schedule" are not defined may be involved.
4: A material for which the function "Generate JIT delivery schedule" is not defined may be involved.
5: A scheduling agreement that has not yet been released by all persons responsible may be involved.
6: The factory calendar has not been maintained correctly.

Automatic assignment of output message for delivery schedules changes

Hi,
we have defined an output type ZDSS for scheduling agreement release. For perticular Delivery schedule documents we are getting the below error.
Diagnosis
An unprocessed output exists (output type ZDSS) has been deactivated.
System Response
Output type ZDSS will no longer be determined.
It seems some user has set the unprocessed outpout type ZDSS of this document to deactive (permanent) status. I need to reactivate the auto assignment of output type for these documents.
Can someone let me know as to how can i reactivate this unprocessed output type OR delete this output type entry from the document?
Please suggest.
Regards,
Prashant

Hi,
Problem is solved on my own... Closing the message.
Regards,

Material po text repeating in a table loop for delivery schedules

Hello,
i am displaying a purchase order in a smart form. In the main area of the table(where i am displayin the material and the delivery schedules) after displayin the material i have created a loop node in which i am displayin the delivery schedules(against each material). Inside the loop i have a text node in which i am displaying a 'material po text'. What is happening is, the 'material PO text' is repeating for every delivery schedule (cuz its inside the loop, so every time the loop iterates the text is repeated).
I want to have a condition or an event by which i can display the 'material PO text' once for every material.
NOTE: the 'material PO text' to be displayed is inside the loop(for delivery schedules)
i know its a mess , but i hope u have understood ...
thanks..

Hii,
please reward points if the post helps you..
Ok just forget whatever is written above:
Just follow the steps below:
1. declare a global variable called Last_material.
2. Inside the loop in the text node where you are printing the material PO text -> goto the conditions tab -> give a condition -> itab-matnr ne last_material.
3. create a code node(program lines) just after the loop node. Assign the material number you are printing(itab-matnr) to Last_Material.
This should solve your problem..
Lokesh

GR Date for Delivery Schedule line

Vendor On-Time Delivery Report
We have vendor On-Time Delivery report requirement, where we rate the
goods-delivery of a vendor as "On-Time" or "Early" or "Late". The
rating is given based on the difference between "Statistical Delivery
date" and "GR date" (in the PO/Scheduling Agreement).
In case of Scheduling Agreement (SA) we have to give delivery rating
for each Delivery Schedule Line - Based on the difference
between "Statistical Delivery date" and "GR date"
The Goods Receipt is done at Schedule line item level and not at
Delivery Schedule Item level, the GR date is not populated at Delivery
Schedule Line level and we are not able to find the GR date for each
Delivery Schedule Line.
Once we get the "GR date" at SA Delivery Schedule line level, then from
the difference between this date and "Statistical Delivery" date, we
can rate the delivery of vendor as "On-Time" or "Early" or "Late".
Is there any way that we can populate/get the GR date (GR creation date) for each delivery
schedule line?
Thanks in advance.

Hi Rahul,
I am working on the same requirement. Appreciate ur help on the same. The notes helps in understanding how quantities are distributed while GR. did u implemented any logic for this distribution or something else to compare the dates. I believe by checking the open quantity (EKET) (scheduled - GR quantity) we can see if there is open quantity for any schedule for the previous day then tht falls under the delayed quantity and if there is zero open quantity, it is on time delivery.
thnx,
Upender

Problems in GR for forecast delivery schedule

Similar Messages

Maybe you are looking for