Scheduling Agreements-Error processing Shipments

When i try to make any changes to the delivery document (change/delete) created by the combination of two scheduling agreements the system shoots an error ME803 dump.txt. I looked at Note 100690 which says inconsistency and executed the correction report to fix the same. But whenever new delivery is created from these scheduling agreements encounters the same problem. Need to run the correction program to reprocess the delivery document. This is affecting the shipments from other plants.
Delivery Quantity is getting updated wrongly
Can any one tell me the root cause of this problem.
Thanks in advance
Regards
Balu

Answered.

Similar Messages

Stock Transport Scheduling Agreement - error message: 'Stock in transit...

Stock Transport Scheduling Agreement - error message: 'Stock in transit exceeded'
Hi, I do have a question about transport scheduling agreements.
I have created a stock transport scheduling agreement via ME37, doc. type LU for a stock material from issuing plant TT01 to receiving plant TH01. The material is maintained in both plants.
After that,I maintain the delivery schedule via ME38 for a quantity for today. The quantity is available at issuing plant TT01, checked via MMBE.
Then, I try to post the goods via MIGO. When I try to post the document, I get the following error message: "PL Stock in transit exceeded by 1,000 T% : 794 TH01 S1". Why do I get that? My target is to decreate the stock quantity in TT01 and to increase the stock quantity in TH01.
Thanks, Peter

Hi,
This happens when you are issuing more on the schudle qty, Check you have anything on the transit receive it the try agin to process the issue.
Hope it helps.
Suresh

Scheduling agreement error

Hi experts,
I am updating a scheduling agreement using IDOC with basic type DELFOR02 and message type DELINS. After posting an IDOC, I get an error message of "No batch input data for screen SAPMSSY3 0121" or "No batch input data for screen SAPMSSY3 0131". I don't know where it is coming. Any idea? Please help.
Thanks,
Lalyn

Hi,
Please go to transaction code WE19 - Test tool for IDoc processing, and clieck "Inbound Functional Module" at the top and first give Functional Module Name ( most probelly it will be "IDOC_INPUT_DELINS_START" or you can check functional Module name by cliecking "Standerd Indound" button from front screen) and after giving functional module name sellect option "In Forground" and then process it. By trying this way you may exactelly reach to the problem area and even if it dosent helps you then on the same screen sellect debug mode option and ask your ABAP Consultant to help you in this case.
May be it will serve your purpose.
Thanks...
Imzo

Scheduling agreements Error??

Hello Friends,
I have an issue creating invoice for a scheduling agreement,delivery and PGI has been done. I get the following costing error when I try to create the invoice "Create billing document" not allowed (Sys. status Cost, object VB3200000705000010" but when I try to cost it along with FI person I get the following error " Costing cannot be done because order quantity is missing".
Within the first screen of scheduling agreement we don't enter any quatity, it is always at the "forecasted delivery schedule" tab.
Please advice what do I need to do in order to cost this agreement which eventually leads to an invoice creation.
Appreciate your help and advice,
Thanks in advance.

Hi Mike
Can you share how you have solved this issue with the forum?
Also when you have solved it by yourself or with the help of forum members please update the thread and also mark your thread as answered
regards

SAP BW Purchasing - Scheduling Agreement delta processing

Hi,
I have a question about Scheduling Agreements coming from ECC to BW with delta processing.
When a goods receipt happens for a Scheduling Agreement item, it registers process key 2.
However, it seems that when a second goods receipt happens for that same scheduling agreement item, the old goods receipts updates with a process key 4, and the new receipt takes the process key 2 when we aggregate at an InfoCube level. In the first level write optimized DSO, the process keys are in tact for every line item & schedule line (all goods receipts process key 2 are there).
Can somebody confirm this logic?
We are having issues because we need all of that goods receipt history stored in our InfoCubes, and we do not know how to resolve. Please help! Points will be assigned...
Thanks very much,
Courtney

are you saying that Process Key is 2 for both the good reciepts in write optimized DSO but in cube, first good reciept is having a process key 4 when second good reciept is also there?
If yes, it seems that problem is with the info object for process key - is it a Key Figure or characteristic?
It should be a characteristic so that the value is not added but overwritten.
you are doing a full or delta from Data Source to DSO and DSO to Cbue?
Regards,
Gaurav

Schedule Lines generated for expired Scheduling agreements

Hi All,
We are facing problems in Scheduling agreements.
Schedule lines are getting generated for those agreements whose validity has expired(i.e Validity in Past).
Is there any check to restrict those Scheduling Agreements??
Please Help.
Regards,
Ritesh.

from OSS note 914607 - FAQ: Validity and status of scheduling agreements
1. Question: When I process scheduling agreements without delivery schedules, I have the option to specify the validity of the scheduling agreement: "Valid" and "Valid to". What role does the validity play when the scheduling agreement is processed?
Response: In the case of scheduling agreements without delivery schedules, the system checks the validity of the scheduling agreement if you create a new schedule line or change an existing schedule line. If the schedule line date is outside the validity interval, a warning message is issued. You can then decide whether or not to create the schedule line or whether to adjust the validity of the scheduling agreement. No error message is issued.
2. Question: What role does the validity play in the case of scheduling agreements with delivery schedules?
Response: The function is similar to scheduling agreements without delivery schedules. The only difference is that the entry of the validity is optional (unlike scheduling agreements without releases) and this is not checked by the system. If the validity is missing, the system does note issue a warning message. If you specify the validity, the system behaves in the same way as for scheduling agreements without releases.

Open (procurement) scheduling agreement

Hi,
We will use subcontracting scheduling agreement to process subcontracting. Does anyone have any data conversion experience of open scheduling agreement?
I didn't find any standard SAP batch input program at LSMW. I am working on recording the creation steps at LSMW. Any input?
Regards,
Nancy

Hi Nancy
Please check if BAPI: BAPI_AGREEMENT_MAINTAIN helps you.
Documenation of BAPI can help you using the same.
Kind Regards
Eswar

Problem While Uploading Customer Requirements To Scheduling Agreement

Hi
I have received a ticket from client which is as below .
As itu2019s new issue for me , I am not able to fix the issue . It goes like this u2026u2026.
Customer scheduling agreement. 30000000
Part 300.F
The customer 862u2019s have been coming in during the mid morning hours (8or 8:30AM)
The customer 830u2019s and 862u2019s arrive once a week, on Fridays. 862 adds 5 addition firm order onto the end of the remaining firm orders.
This is what happened this morning.
7AM, VL10A due to ship today correctly shows 425pc.
7AM we created todays delivery for 425pc. Delivery 80005515. this removed the 425 from the open quantity on the scheduling agreement.
After the delivery was created for todayu2019s shipment, the new 862u2019s arrived, from customer , and populated the scheduling agreement.
Todayu2019s shipment was PGIed.
The scheduling agreement below shows 425pc due to ship today after we made todayu2019s shipment.
The problem seems to happen when todayu2019s delivery is already set up and THEN the new 862u2019s arrive and populates the scheduling agreement.
Is there any way of resolving this issue?
We know that the customer scheduling agreement is set up differently to receive 862u2019s.
This customer adds new firm orders each Friday.
So , could I request you to help me out in this case where I have to check up and how can I fix the issue .
Thanks in advance .

Hi Friends
Could I request you to help me out on this aspect
Thanks

Schedule Agreement filed- lphis

Hi
In the customizing for the document type for the scheduling agreement there is check box for Release documentation, which says that if it is activated then forecast schedule will be saved in a seperate file and displayed anytime.
This tick was activated in our client which prevented the goods receipt and system says 'no selectable item found'. When i removed the tick, the system allowed the goods receipt.We are using only standard schedule agreement with out forecast and jit schedules.
Could anybody inform me the significance of the field LPHIS. Does the activation of release documentation requires schedule agreement schedule lines to be printed before goods can be receipted.
Regards
Arvind

Hello,
there are two kind of SA, SA with and without release documentation. if the field LPHIS is set so you have SA with release documentation.
Now, if you are managing SA using SA with release documentation you have to perform the Scheduling agreement release process, otherwise all schedule lines remain non official.
hereafter a descritpion of the Release process "source : the standard SAP document page 221
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MMPUR/MMPUR.pdf"
Scheduling Agreement Releases: Process
Purpose
A scheduling agreement release
enables you to record the current status of the lines of a delivery schedule stored in the system
for a scheduling agreement item and then transmit this status to the vendor.
Process Flow
1. Materials Planning generates delivery schedule lines for scheduling agreement items. You
can also create schedule lines manually.
2. You create scheduling agreement (SA) releases (delivery schedules) comprising the
schedule lines for a certain scheduling agreement item. These are snapshots of the overall
delivery schedule stored in the system at given points in time.
In creating such releases, the system proceeds as follows:
a. If a creation profile exists, it aggregates the release (i.e. scheduled) dates and quantities.
b. It generates an SA release in accordance with the creation strategy and the entries on
the initial screen for SA release creation.
c. If a creation profile exists, it determines any backlogs and immediate requirements.
d. If a creation profile exists, it checks any applicable tolerances in the case of SA releases
created due to changes to the overall schedule in the system.
3. The releases (delivery schedules) are transmitted as messages to the vendor.
regards

Scheduling agreement receipt

Please explain me Scheduling agreement receipt process under HU managed warehouse.
This warehouse update WM first and then IM.
Please explain me the process till invoice verification. Document type user for scheduling agreement is LP.
I have created Scheduling agreement and schedule line.
What next. please explain me check point in each tcode.
Thanks,
Kiran

Whether it is scheduling agreement or a PO, the process remains the same. Once SA & Delivery schedule is created, on or after the scheduled receipt date as per the schedule line, you post a GR and then you can invoice it, using the same MIGO & MIRO transaciton. Since your inventory is HU managed and warehouse managed, you will create a HU while posting the receipt and then create a transfer order to move it to the relevant bin.

Scheduling Agreements-Not able processes shipments

When i try to make any changes to the delivery document (change/delete) created by the combination of two scheduling agreements the system shoots an error ME803 dump.txt. I looked at Note 100690 which says inconsistency and executed the correction report to fix the same. But whenever new delivery is created from these scheduling agreements encounters the same problem. Need to run the correction program to reprocess the delivery document. This is affecting the shipments from other plants.
Delivery Quantity is getting updated wrongly
Can any one tell me the root cause of this problem.
Thanks in advance
Regards
Balu

Hi Will,
It's an outline agreement that is created for one or more materials and outlines the overall expected quantity of the material(s) to be delivered to the customer over a specific period of time.
Use
The scheduling agreement is used as a basis for delivering a material. The customer sends in scheduling agreement releases, referred to as delivery schedules, at regular intervals to release a quantity of the material.
Structure
The structure of scheduling agreements with delivery schedules resemble that of other sales documents in the R/3 System, in particular the standard scheduling agreement.
Data that applies to the entire document appears in the header; data about materials appears at item level; and delivery dates and quantities appear in the schedule lines within the delivery schedule. Additionally, the system maintains a history that permits you to compare and contrast various generations of delivery schedules.
Integration
Data in scheduling agreements comes from three sources:
The customer sends in requested quantities and dates, normally by Electronic Data Interchange (EDI)
The component supplier enters data manually
The system automatically copies data into the scheduling agreement from master records
Hope it helps. Please reward if useful.
Thanks & Regards
Sadhu Kishore

Scheduling agreement process doc

Hi,
can anybody share the Process Document/config doc for Procuing Materials from Supplier through ALE
1. Scheduling agreement created and IDoc tranfered to Supplier.At supplier end Sales Scheduling agreemenet created.
2. Maitain Delivery schedules and trigger Idoc and transfer to Supplier. At supplier end Delivery order to be created with delivery schedule.
i hav tried with Schedule release documentation with ME84 also with message DELORD,But Idoc getting errors .
if any body knows the process pl share.
Regds

Hi,
i found this document...
http://help.sap.com/bp_imc603/BBLibrary/Documentation/667_Scen_Overview_EN_CN.ppt.
maybe you can find the same building block (667) that applies for you.
regards, Paul.

BAPI_SCHEDULE_MAINTAIN throws error for time- independent scheduling agreement

Hi All,
I get the below error while modifying a stock transport Scheduling agreement in UI5 using BAPI “BAPI_SCHEDULE_MAINTAIN”
“Scheduling agreements with time-independent conditions are not supported”
Found a note 1046794-
"BAPI_SAG_CHANGE (and BAPI_SAG_CREATE) can only treat scheduling agreements with time-dependent conditions. Document conditions are not supported. Therefore, this kind of scheduling agreements cannot be processed. This is a missing functionality”
To meet some finance requirements, we need to use time-independent conditions in the scheduling sgreement, in order for a custom condition type to be picked up.
I'd appreciate any advice I can get about how to fix this functionality in the BAPI or alternatively how to link the pricing condition type to the Scheduling agreement document type?
Thanks so much.

Link between Time dependent / independent condition and Scheduling agreement document type is in configuration under SPRO>MM>PURCHASING>SCHEDULING AGREEMENT>DEFINE DOCUMENT TYPES>SCROLL TO THE RIGHT here you find a check box Time-D.C.
Thanks
DD

Error generating release against scheduling agreement

Need help in resolving the below error msg for Scheduling Agreement.
ERROR message:
"Error generating release against scheduling agreement (cause 2)"
"2: The forecast delivery schedule or the JIT delivery schedule was generated but no message record could be generated."

Yes.. its solved now...
problem areas:
1: delivery date not matching GR date.
solution: chng delvry date to GR date in ME38 and thn do GR.
2: Release not hapnd properly incase if u hav used doc typ LPA for JIT/Forcasting.
solution: in ME84, chk if the indicator for 'create release' is 'green' for ur SA#. In ME38, select the line and click on 'Release" icon. Select ur relevant delivery schudle line and click on JIT release or Forcast Release icon. See if the indicator is 'Green". If not, the issue is wit message output for the perticular delivry date. (use msg typ LPET process for output) MAKE SURE U SAVE THIS CHNG. Chk againg for the Release indicator for delivry line. If green thn.. its done..
Let me know if it was hlpful... or need clarity

Error generating release against scheduling agreement (cause 6) in ME38

Hello Experts,
Need your inputs on the the below error getting generated in ME38
Error generating release against scheduling agreement (cause 6)
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 6.
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.
Procedure
Error source 1:
Check whether the vendor and plant shown in the PO actually exist in the system.
Error source 2:
Check the Customizing facility for message determination with respect to delivery schedules created under scheduling agreements (print operation '9').
Error source 3:
In Customizing, maintain the document types accordingly ( Define document types for scheduling agreement). Then create a new scheduling agreement with a document type for which release documentation is defined.
Error source 4:
Maintain the JIT delivery schedule indicator in the material master record.
Error source 5:
Have the scheduling agreement released by the person(s) responsible.
Error source 6:
If you are using a release creation profile without aggregation, you must maintain the factory calendar for the next 999 days
Regards,
Santosh

Hello Mallinath,
I referred the note and following are the observarion in the system.
Step1:Run T-code SE16 (table T001W) to check the calendar ID of the plant.
-----Referred the Calendor ID
Step2: Check the JIT/Forecast delivery schedule of release creation profile in customizing. (T-code OLME -> Scheduling Agreement -> Maint. Rel. Creation Profile for Sched. Agmt. w. Rel. Docu.)
Run T-code SCAL to adjust the period of the calendar ID which checked in STEP 1 according to the JIT/Forecast delivery schedule of the release creation profile which checked in STEP 2.
(For example, if the JIT/Forecast delivery schedule of the release creation profile is "999" days, then the calendar should be extended for the next 999 days at least)
---------In this case factory calendor is valid till 2015 and according to note needs to change the factory calendor till 2018( or for 999 days) ?
Waiting for your inputs.
Thanking you,
Santosh

Scheduling Agreements-Error processing Shipments

Similar Messages

Maybe you are looking for