Scheduling agreement in SD, release number

Dear All,
I trying to implement an automatic process for one customer, getting in an EDI 862; transferring this in an IDOC message type DELINS of Basictype DELFOR02 and updating the scheduling agreement accordingly.
This is working fine, for simple cases, but this customer is sending different release numbers for the same product at one time, and also sending the release numbers multiple times.
e.g. today I am getting for product A a release number 111 with multiple schedule lines, and also a release numberr 112 for the same product with multiple schedule lines.
tomorrow I might get again an EDI 862 for this same product, containing revised information for release number 111 and 112.
This is in my understanding not matching the SAP logic, where it's clearly stated, that a new release number is replacing completely the old release number.
Does anybody has any idea how to implement such a process?
I already have studied all documentation, tried to implement it in different ways, but I am reaching every time only a 80 % solution.
Do we have in this community any experts on scheduling agreements on the SD side, which might be able to help me?
Thanks for any possible help.

check these
BAPI_CUSTSCHEDULAGREE_CONFDELV Customer Sched. Agreement: Confirmation of Delivery; Document Flow Upd
BAPI_SALES_DEL_SCHEDULE_CREATE BAPI for creation of releases in scheduling agreements

Similar Messages

Scheduling Agreement - Automatic Release Individual Schedule Lines

Dear all.
I've create a "LPA" scheduling Agreement and its release type is "JIT". So, I use to ME38 to maintain the individual JIT delivery schedule lines.
The problem I have is this method requires the person to manually release each individual delivery schedule line document on the due date before GR is allowed. Hence, is there a SAP system function that can automatically release any due delivery schedule line document without having to manually track and release using ME38 each day/week/month?
Thanks.
Steven

Hello
use t.code ME84 then system release the sch.lines automatically those maintained with me38.
Laxman

Scheduling Agreement Release

Hi All
Scheduling agreement is created & released. Release indicator is 6, after the release again some line items are blocked & some line items are deleted without affecting any characteristic of release strategy
( No Change in value , Document type , Purchase group on which release strategy is based)
Wheteher release strategy will be reset in this condition form release to unrelease
Please suggest
Thanks in advance
Regards
Rajesh

Hi,
If no user exit is activated in support for your release strategy, then any change which results in no revision of your original value will not cause any release strategy reset.
Cheers,
HT

SCHEDULING AGREEMENT AND SCHEDULING LINE CREATION

Hello Guys,
I trying creating a scheduling agreement(SA) for vendor & material combination.
I have created a Scheduling agreement in ME31L then maintained in ME38.
In ME38 i have also mentioned the delivery date. when i am checking EKKO for Purchasing document , its created with the delivery date specified.
My question is how to create a schedule line ? Do we need to maintain a source list of that material, plant and vendor.
If we have the source list maintained, then what is the next step after SA is created and maintained.
Do we need to do MIGO? because i tested by creating one SA in ME31L and maintained in ME38. I mentioned the delivery date as today and when i checked EKKO table the Purchasing document is created.
Do i need to create a Purchase Order?
If no then do i need to do MIGO? If i need to do MIGO, for what reference do i need to do MIGO???
My client never maintained a Scheduling agreement, they want the scheduled lines to be created and sent to vendor and we need to receive the goods on specified delivery date.
Help will be appreciated.
Thanks.

Hi,
You need to make a distinction between the scheduling agreement (ME31L/ME32L) and the delivery schedule creation (ME38/ME84)
With ME31L you create the scheduling agreement. In the scheduling agreement which is created for a vendor you maintain the parts that you will order at this vendor, the target quantity that you will order over a certain period and the price.
In ME38 you use the scheduling agreement number that is created with ME31L to create schedule lines (manually). These schedule lines consist of a date and an quantity. This is the data that needs to be transmitted to the vendor and against which the vendor is shipping the ordered materials.
Once the vendor ships the materials you post the goods receipt in Migo against the scheduling agreement number.
That is the basic working of the scheduling agreement and the delivery schedule.
Now some remarks.
You need to set-up the required output conditions for transmitting the data to the vendor either via print, fax, email or EDI.
You can do this manually in each scheduling agreement and each release but typically you maintain the output condition records.
For scheduling agreement contract (ME31L) you use transaction MN07.
For the delivery schedule (ME38/ME84) you use transaction MN10.
In order for you to be able to post the goods receipt the delivery schedule needs to have been transmitted otherwise you will get a message that not requirement are found when trying to post goods receipt.
Also the goods receipt can only be posted if the requirements are valid on the day that you are performing MIGO. This means if you would post GR today then the open requirements in the scheduling agreement need to be for today or already from previous dates. The system will not allow you to post GR for quantities that are only due tomorrow (if this is required a user exit needs to be set-up).
If you want schedule lines created via MRP then you need to set-up a source list using ME01. You have to make sure that the MRP key is set to 2 in orer for the system to generate schedule lines and you also have to make sure that you have the correct MRP parameters set-up.
You can use ME84 to transmit the delivery schedule lines generated by MRP if no changes are required. With the ME84 you can transmit multiple releases at once, however this transaction can not be used to make manual changes to the MRP proposal.
The scheduling agreement offers lot's more possibilities but the above should get you going with the basics.
Hope this will help you on your way.

Scheduling agreement GR

I tried to carry out procurement using Scheduling agreement , I made the same using ME31l. I gave the schedule lines using ME38. I ensure that this scheduling agreement is not subjected to any release stratergy. When I tried to go for MIGO using this Scheduling Agreement and type its number against PO . System displays error message there are no selectable items in the scheduling agreement. I want to know what can be the reason for the same.
Also Would like to have stepwise procedure and subsequent checks to carry out complete procurement cycle using Scheduling Agreement.

HI
Please maintain schedule lines for todays date and do <b>MIGO on the same day</b> by giving the scheduling agreement number in the purchase order coloumn.I think it may work.
Reward if useful
Thanx and Regards
SHYAM.R

Question regarding SAP note 765494 and Scheduling agreements

In a SAP ECC 6.0 environment has anybody dealt with note 765494? It appears that the changes allow the user to change shipping data on stock transfer scheduling purchase orders using the ME22N screen (Enjoy) but not the ME32L scheduling agreement change screen. Does anybody know of a work around to change shipping data on a stock transfer scheduling agreement?

Hi Mahesh,
A contract is a type of outline purchase agreement against which release orders (releases) can be issued for agreed materials or services as and when required during a certain overall time-frame.
Contracts are of two types:
1. Quantity contracts - Use this type of contract if the total quantity to be ordered during the validity period of the contract is
known in advance.
2. Value contracts - Use this type of contract if the total value of all release orders issued against the contract is not to exceed a certain predefined value.
But a scheduling agreement is a form of outline purchase agreement under which materials are procured on predetermined dates within a certain time period. A scheduling agreement consists of a number of items, for each of which a procurement type is defined. The
The following are the procurement types:
- Standard
- Subcontracting
- Consignment
- Stock transfer
Delivery of the total quantity of material specified in a scheduling agreement item is spread over a certain period in a delivery schedule, consisting of lines indicating the individual quantities with their corresponding planned delivery dates.
Contracts and Scheduling Agreement transaction codes:
Transaction codes:
Contracts: ME31K to ME35K
Scheduling agreements: ME31L to ME35L.
Please award if helps!
Thanks!
preethi.

Regarding : Contracts and Scheduling Agreements

Hi All SAP Proffessionals,
Can anybody tell me what do we mean by Contracts/Scheduling Agreements?

Hi Mahesh,
A contract is a type of outline purchase agreement against which release orders (releases) can be issued for agreed materials or services as and when required during a certain overall time-frame.
Contracts are of two types:
1. Quantity contracts - Use this type of contract if the total quantity to be ordered during the validity period of the contract is
known in advance.
2. Value contracts - Use this type of contract if the total value of all release orders issued against the contract is not to exceed a certain predefined value.
But a scheduling agreement is a form of outline purchase agreement under which materials are procured on predetermined dates within a certain time period. A scheduling agreement consists of a number of items, for each of which a procurement type is defined. The
The following are the procurement types:
- Standard
- Subcontracting
- Consignment
- Stock transfer
Delivery of the total quantity of material specified in a scheduling agreement item is spread over a certain period in a delivery schedule, consisting of lines indicating the individual quantities with their corresponding planned delivery dates.
Contracts and Scheduling Agreement transaction codes:
Transaction codes:
Contracts: ME31K to ME35K
Scheduling agreements: ME31L to ME35L.
Please award if helps!
Thanks!
preethi.

How to close the Scheduling Agreement

how to close the scheduling agreement
means i don't want to procure the material any more against the Scheduling agreement.

Abhishek
Please follow the below procedure.
You block items in Schedule agreements to prevent release orders or delivery schedules (in the latter case, including SA releases) being created against the agreement. For example, you may want to block an item if a vendor has delivered goods of poor quality.
Procedure
1.     Choose Schedule agreement Change.
2.     Specify the number of the outline agreement. Then press ENTER .
3.     Select the item(s) you wish to block. Then choose Edit Block.
The system inserts an S in the column D, indicating that the item is blocked.
To unblock the item, select it and then choose Edit Reset deletion indicator.
4.     Save the agreement.
or
You can delete the item in schedule agreement
Thanks & Regards,
Sridhar

Scheduling Agreement Delivery Schedule Maintenance

I have recently been given the task to maintain the delivery schedules
for schedule agreements in the EKET table using data from external
sources. I have been unsuccessful at finding standard interface
techniques (Call Transaction, BAPI, ) to do this. A similar program
already exists at my client site that uses the SAP function
ME_UPDATE_SCHEDULES_DISPO to do this, but I am uncomfortable issuing a call to this function out of context to accomplish these updates.
Can anyone confirm for me that use of this function would essentially be
the same as calling a BAPI (if one existed) and that there should be
little or no risk to our application as a result of using this approach?
Please note that my question concerns scheduling agreements and not
purchase orders. I have found references to BAPIs for scheduling agreement maintenance in release 6.0, but my client is running release 4.7.

hi,
plz go thru following threads
How to pass table as input parameter of a BAPI ?
Pass Parameters from InputField to BAPI
Pls let me know how to pass the parameters for the bapi BAPI_OBJCL_CHANGE
<b>plz reward if useful</b>
Swati

Fully Close Off Under Delivered Schedule Agreement Line Items

Hi There,
I am supporting a customer who is having an issue with line items on a scheduled agreement, which she has closed off, appearing in MIGO.
Example: I have a scheduled line item of 100 EA. I GR 90 EA but I am happy with this so I want to close off the line.
I go into ME38, select the line item, click the delivery schedule icon, set the scheduled quantity to 90 and click the fixed check flag. I refresh the Schedule Agreement and re-release it.
However when I go into MIGO and do a Goods Receipt for my scheduled agreement, MIGO is still proposing the 10 EA to me.
I have two questions
1) Are the steps I am doing the correct way to close off an under-delivered scheduled line item
2) If 1 is correct, how come the 10 EA is still being proposed and how do I stop this happening?
Many Thanks for any help provided,
Colm

No Answer

Process for Scheduling Agreement

Please tell me the process for Scheduling Agreement?
I have created Scheduling Agreement thru ME31L and delivery schedule thru ME38. what is the further process?

Scheduling agreements provide for the creation of delivery schedules specifying purchase quantities, delivery dates, and possibly also precise times of delivery over a predefined period.
Create scheduling agreement
ME31L
Create stock transport scheduling agreement
ME37
Change scheduling agreement
ME32L
Maintain scheduling agreement supplement
ME34L
Recalculate scheduling agreement prices
ME3R
Re-number schedule lines
ME85
Aggregate schedule lines
ME86
Aggregate PO history
ME87
Reset agreed cumulative quantity and reconciliation date
ME88

Scheduling Agreement --- IDOC Setup

Hi,
Please let me know the Configuration for SA for Inbound & Outbound IDOC
Regards
Amey Kulkarni

HI,
I don't know if you're talking about SD Schedulling Agreements or MM Purchasing Schedulling Agreements.
For the second type there is also an important IDOC output:
- message type: DELFOR / DELJIT
- basic type: DELFOR02
that carries Delivery Schedule Forecast and/or JiT lines that you release and send to supplier.
to receive despatch advice from Supplier there is:
- message type: DESADV
This messages are predefined in SAP so you only need to set them in WE20 t-code for each Supplier as partner.
To outbound Delivery Schedule with IDOC (EDI) it is also needed to maintain Output type LPH1 in MN10 t-code and sometimes in SPRO in Message settings for Schedulling Agreement Delvr Schd release output,
Best Regards,
Tomek

MEKL - Update prices in Schedule Agreements

Hello,
Do you know a link to check the steps I need to folllow to excute that transaction?
I ran it, but does not do nothing....

Hi,
Try the following steps:
First of all, you have to create a Schedule Agreement with a material number, just for test.
Use Net value for this item = 1000
1 - Tcode MEKL
2 - Enter Purchase Organization
3 - Enter Vendor and, if you want, enter Schedule Agreement number you have just created
4 - Sched. Agreements w/o Materials and Test Run does not need to be selected for this test
5 - Enter Absolute Amount
6 - Sign = + That means system will get Actual Schedule Agreement Value (PB00) + Absolute Amount you have entered.
So, if you created a Schedule Agreement with one line 10 - Material xxxxx - Net Value 1000, and you entered Absolute Amount = 1000 and sign = + that means, system will change your Sechedule Agreement to 2000.
Sign = - if you want decrease value
7 - Gross Price should be selected
8 - Scale lines does not need be selected
9 - Supplementary conditions does not need be selected
10 - Condition valid on = today (the day you have created your Schedule Agreement)
11- Press F8 or run
System should give you a table result with your Schedule Agreement
If everything is ok, press Save Button
Now, go to ME33L and check new values.
I hope it helps you.
If you have any doubts, please, let me know.
Best Regards,
Natan
Edited by: Firenarrow on Jun 9, 2010 10:04 PM
Edited by: Firenarrow on Jun 9, 2010 10:06 PM

About scheduling agreement

Hi,
Can anoybody tell me that what is the difference between scheduling agreement with release document and scheduling agreement w/o release document?
what are the benefits of the scheduling agreement with release document?
Thanks
Ashish

Hi Ashish,
Release nothing but creating output messages which we will send to vendor ( just like purchase order output message like printouts), by automatically ( without release, document type LP) or depending upon certain criteria i.e with release, document type LPA.
If you ar using scheduling agreements without release documentation ( document type LP), the message is generated directly. i.e the movement you save the schedule lines the system creates the delivery schedule and sends to the vendor
If you are using scheduling agreements with release documentation ( document type LPA), you must explicitly generate SA releases ( FRC or JIT)
The schedule lines of a scheduling agreement release contain finalized information for the vendor regarding quantities and delivery dates. The schedule lines are recorded with the aid of the release documentation and can thus be displayed and verified at any time. The release documentation enables you to see which schedules you transmitted to the vendor during the last two weeks, for example, and check the correctness of goods receipts against the relevant schedule lines.
In the case of with release (delivery schedules) the output messages are controlled by creation profile.
Creation profile
1.     it aggregates the release (i.e. scheduled) dates and quantities
2.     It generates an SA release in accordance with the creation strategy and the entries on the initial screen for SA release creation.
3.     The releases (delivery schedules) are transmitted as messages to the vendor
The advantage of with release is you can create forecast delivery schedule (FRC) and Just in time delivery schedule ( JIT)
Forecast (FRC) delivery schedule
Provides the vendor with longer-term data regarding the quantities needed of a material and when delivery is required. In such schedules, the timing of delivery is usually expressed in terms of calendar months or weeks. Note: approximately equivalent EDI terms for the forecast delivery schedule are: planning schedule with release capability (ANSI 830) delivery schedule (message) (EDIFACT DELFOR), and delivery instruction (ODETTE DELINS).
       Just-in-Time (JIT) delivery schedule
Provides the vendor with data on required quantities and desired delivery dates/times covering the near future.In such schedules, the timing of delivery is usually expressed in terms of specific days or even times of the day. Note: equivalent EDI terms for the JIT delivery schedule are: Shipping schedule: (ANSI 862) and Delivery just in time message (EDIFACT DELJIT).
Thanks
Janardhana

Scheduling Agreement - Delivery schedule line number

Hi,
I am developing a report to show the Goods receipt postings for each delivery schedules of Schedule agreements.
I am not able to find Delivery Schedules line(EKET-ETENR) in Material document table(MSEG).
How do we exactly link the GR quantity to Scheduling agreement Delivery schedules.
We have line item number but not delivery schedules.
GR quantity may be posted to different delivery scheules and for some SAs when the MRP Runs it is positng randomly.
Is there function to find the link,
Searched EKBE, EKET, MSEG and other tables also.
Appreciate your help <offer removed by moderator>.
Satya
Edited by: Thomas Zloch on Jan 18, 2011 2:44 PM

Hi Shravan,
Thanks for answering, I checked those two tables EKEH, EKEK are release tables. We have some SAs without release documentation. I have to find the delivery schedules using the GR document to which delivery schedules the qty it is delivering.
It is not posting the qty from top of schedules, for some SAs it posted randomly.
Any other ideas or any function modules,
In BW it is possible using extractor but we need in R/3
Thanks,
Satya

Scheduling agreement in SD, release number

Similar Messages

Maybe you are looking for