Release strategy for Scheduling Agreement(SA)

Dear Forum,
This issue is with regards to the release strategy for Scheduling Agreement(SA)
Until now release has only been applicable to contracts at our client site. But we now plan to introduce it for SA as well. Such a feature is available in SAP but the problem is that with the given release strategy GR is not allowed until the release is affected. The system allows you to post the delivery schedule.
Now what I want is that after making the SA the system should not allow to make delivery schedule if release is not affected.
We also have MRP run at client site..Kindly suggest the procedure as, how to configure it.Are der any User Exit for the same,if so please discuss..
Warm Regards
Nainesh
SAP ECC 6.0

Hi,
What's the SA Type that was created via MRP.
If it's LP (without release document), release will not do anything BUT
If it's LPA (release document), then you will not be able to Post the GR until release is affected.
Thanks.
Scheduling Agreement can be categories as
1) LP (without release document) and
2) LPA (with release document)
If use LP, you can do GR without release but with LPA, you need to release the schedule line via ME38.
Thanks.
NanoSAP
Posts: 58
Registered: 1/5/09
Forum Points: 6
   Re: release strategy for Scheduling Agreement(SA)
Posted: Jun 26, 2009 8:32 AM    in response to: sathish.kumar           Reply
Dear Mr.Satish,
Thanks a lot for your earliest reply...But my point is i want the system should not allow to make delivery schedule if release is not affected...Though schedule lines are generating through MRP run...Is is possible,by any chance...??

Similar Messages

Appluing release strategy for scheduling agreement

Dear Sapguru,
Can anybody explain.How to apply release strategy to scheduling agreement.I'm working on MRP implementation project.
Here already release strategy using for PO.
Pls explain steps of release strategy to scheduling agreement.

Hi,
Welcome you post on the forum.
Have you searched the forum already? Such as:
http://forums.sdn.sap.com/search.jspa?threadID=&q=%22applyreleasestrategy%22&objID=f245&dateRange=all&numResults=15&rankBy=10001
Thanks,
Gordon

Release strategy for Schedule lines in SD

Hello All
Can we create a release strategy for Schedule Lines in Scheduling Agreement? If Yes How?
I have already maintained a release strategy for Item Level... which I want to put it for Schedule line as well....
Thanks in advance.

Hello,
I think you are in the wrong forum. Please choose the right forum category and post it there.
Matthias

Release strategy for sheduling agreement

Hi,
pl suggest me about release strategy of sheduling agreement.
Is there any different release class required for SA other than PO?

Hi,
Release Procedure method is same for all the External Purchasing Documents (RFQ, PO, Contract and Scheduling Agreements)
You have to use class with class type 032 and characteristics with Communication Structure CEKKO

Approval process (Release strategy of scheduling agreement)

Hi,
Recently we are trying to implement the approval process of scheduling agreements.
Client requirement is when ever there is a change in price irrespective of the following
1. Retrospective price change in any line item
2. Current price change in any line item
3. Future price updation in SA in any line item
4. New addition of line item
the system should trigger the release process (i.e. Approval process).
Our idea is to design the approval process based on document type and net value of SA. Based on which trigger should happened. But when we test it we find the following issues.
1. Trigger is not happening for future date price change or price for new period as the net value of SA is based on validity time.
Becuase the net value change will happen only on that onwards..
Also we are not using any cumulative pallned values in agreements.
Any can suggest the best solution to over come this..or Any user exit is avaliable to handle this issue.
regards,
K.Sundaresan.

Below are the (changed) item fields :
Purchasing Document Item Change Date AEDAT
Item Delivery Date EINDT
Schedule Line is "Fixed "FIXKZ
Below are the (changed) header fields :
Release Indicator: Purchasing Document FRGKE
Release status FRGZU
Purchasing document processing state PROCSTAT
Item and header changes have same "Change document number " and transaction code "ME38" , this happened only in some cases,Rel Strategy is on document type level ,I am also confused on this .
Please assist on this

ME38 resets Release strategy of Scheduling agreement

Hello,
It seems when the users change the delivery date in the delivery schedule (transaction ME38), the system in some cases resets the release strategy of the scheduling agreement from "Release" to "Not Release".It happened only in some case,release indicator set to "4" in our case.
I cannot understand why this happens.
Has anyone encountered such a problem before.
Thanks
Sunil

Below are the (changed) item fields :
Purchasing Document Item Change Date AEDAT
Item Delivery Date EINDT
Schedule Line is "Fixed "FIXKZ
Below are the (changed) header fields :
Release Indicator: Purchasing Document FRGKE
Release status FRGZU
Purchasing document processing state PROCSTAT
Item and header changes have same "Change document number " and transaction code "ME38" , this happened only in some cases,Rel Strategy is on document type level ,I am also confused on this .
Please assist on this

Release strategy for Schedule Lines

Hi,
The requirement is MRP should not run for Line item unless it is released by an authorized user. Logically availability check has to happen at the time release of the requirement line for the consideration of realistic manufacturing time. Also, user should not be able to cancel the release, or edit the schedule line once Planned or Production Order is generated for the requirement line.
What we want is a Release Strategy in sales order for each schedule line individually similar to PO Release.
I have currently set up a status profile, which has 2 levels Processing and approved, which effectively block creation of DELIVERY doc, but I am unable to control the schedule line.
Any ideas?
Cheers.
Edited by: Sowmya Mohan on Sep 12, 2008 1:14 PM
Edited by: Sowmya Mohan on Sep 17, 2008 10:17 AM
Edited by: Sowmya Mohan on Sep 17, 2008 1:03 PM

Hello,
I think you are in the wrong forum. Please choose the right forum category and post it there.
Matthias

Release strategy for Future validity period- (Outline agreements)

Dear All,
I want to create release strategy for Scheduling agreement.But I am creating the SA for furure validity period.In this case how the release strategy will triger.
E.g Today 09.03.09 I create a Sceduling agreement and the validity period I maintain is from 01.06.09 to 31.12.09 and Amount say 100 Rs.
I am using Characteristics Doct type and Amount.. The system checks the rate as on date (i.e on 09.03.09) and since it doesnt find any value the Release strategy is not trigeering.
How to set up release strategy in the above case.
Thanks in Advance.
Regards
Amar

Hi Amar,
1) if you maintain a target value (EKKO-KTWRT) in the header of the
contract this value is the basis for the determination of the release
strategy. If the target value is 0, the system will cumulate the
values of the items and will use this value for the determination.
2) So if the target value is 0 and you change the price of a condition
with a validity period in the future the system will react in the
following way:
Example:
   the contract contains one item with quantity = 100 and a net price
of EUR 5,-.
   all contracts with a target value from EUR 0 - 1.000,- should be
subject of a release strategy
   the contract is created and released on October the 1st
   ME32K -> October the 2nd you define a new price of EUR 7,- with a
validity period from 03.10.09 - 30-10.09 -> you save the contract
-> the release strategy is not reset, as the start date is not
reached yet (system date < startdate of validity period)
   ME32K October the 3rd you change a field in the contract -> the
release strategy is reset
This is system design that a release strategy can only be reset through
an action by the user. The determination of the release strategy can't
be triggered automatically in the background.
If you create a document which is subject of an overall release strategy
(e.g. p.o., contract) the determination of the release strategy takes
place when the user hits the 'save' button or chooses the 'check'
function.
So there must be a kind of event that tells the system that something
has changed.
Regards,
Edit

Exit for role determination via exit for scheduling agreement and contract?

Hi..
I have a requirement to fetch the agents in run-time for PO,PR,SCHEDULE AGREEMENT, CONTRACT..
For PO i am using EXIT : - M06E0005
For PR release i am using EXIT :- M06B0001
By using above 2 exits i am getting the agents at run-time...
Same way i need the EXIT for SCHEDULE AGREEMENT and CONTRACT..
if there is any EXIT for this please share with me..
Regards,
Imtiaz Khan

Hi Imtiaz,
Ideally you should have your agent determination logic in workflow itself instead of determinining them in EXIT.
Can you tell me why you are determining agents in exit and how you are making use of it ?
Also let us know how your workflows are getting trigger for all these documents.
Regards,
Ibrahim

Automatic delivery schedule for Scheduling Agreement

Hi all...........
I like to create automatic delivery schedule both JIT & FRC schedules for Schedule agreement, means system has to suggest the schedule lines.
I created SA and creation profile, when Im trying to generate JIT schedule system showing "Error generating release against scheduling agreement (cause 2)".
Pls let me know wht configuration I hve to do and pls let me know all the steps.
I like to know output determination setting for SA releases also.
regards
Durga Ram

Hi
'Propose all Items" is ticked so that MIGO proposes all the items irrespective of the delivery date and quantity. This means that even if the delivery date has not yet been reached or the complete qty has been received, the system will still allow you to do the GR.
Hope this clarifies.
Thanks

Data migration approach for Scheduling Agreements

Gurus,
Can anyone provide guidance on the data migration approach for Scheduling Agreements? How can we migrate the open delivery schedules and the respective cumulative quantities? The document type being used is "LZ".
Can correction deliveries (Doc type - LFKO) be used update the initial cumulative quantities?
Any help in this regard is higly appreciated.
Regards,
Gajendra

Hi Zenith
You might find useful information here: IS-U data export (extraction) for EMIGALL.
I've done numerous IS-U migrations in the last 10+ years, but never one from IS-U to IS-U.
One main questions to start with: Are the two systems on the same release level?
If they are not and it would be too much effort to get them onto the same release level I would think creating your own extract programs and using the Migration workbench (EMIGALL) is the way to go.
If they are on the same level, there might possible other ways to do it, dependent on the differences between the two systems (mainly around customising). Assuming there are significant differences - otherwise why would you bother migrating? - there's the high probability that using EMIGALL is the way to go as well.
Yep
Jürgen

Purchase Requisition Release strategy for MRP based Requisition

Hello Gurus
We want to set up the urchase Requisition Release strategy for MRP based Requisition ..Any can one Please share your experience about the impact down the road?
Thanks
Nick

Hi,
If you want include the MRP related PR in Release strategy.
You need to include the field CEBANESTKZ-Creation Indicator (Purchase Requisition/Schedule Lines) in one of the characteristics which you create and include the characteristics value as per the field values like AReal time, BMRP, CConverted Planned order etc.. and include the charactristic in the Release Strategy will release group & release codes.
So when ever the PR is created through MRP run then this creation indicator will update in the PR as per that release Strategy will trigger in the PR.
there is one more option you need to create the separate document type as MRP PR then create document type as characteristics and include the values of all these document types and include in Release strategy.
But it will not pop up for direct PR from MRP run only trigger when planned order is converted to PR manually there you need to select this MRP document type then release strategy will trigger.
I think first one is best suited.
rgds
Chidanand

Release strategy for GR?

Hi,
My company has requirement that GR should be subject to approval process before it can be posted. As far as I know there is no standard functionality in SAP for this (at least in ECC, as in SRM there is one).
Has anyone encounter this before? And how you deal with this? I have tried to persuade the user to drop this, but the problem is they already have this functionality in their legacy (which is custom made web based application), so it is pretty hard to argue with them in this area.
Any help will be appreciated.
Best regard

Hi Yosea,
Yes you said is right that there is no Release strategy. And can't imagine the situation in the legacy as well for this approval process thru Release strategy while doing the GR. But there is another way of accepting the goods either partial or full using movement types, you can do so.
My question is why do you (i.e., your client or company) want to control (through the approval process) at Goods receipt level. That makes complex and un logical as well, thats why there is an approval process comes into picture at PO (Purchase order is an external purchase document and is going out to an external party /vendor /supplier) against that they can supply the material /provide the services to the Organization/company and is required to control before issuing this perticular document called PO (i.e., work order and is required to be controlled thru Electronic release strategy in SAP) instead of manual before in legacy since there is money matter involved and needs to control over investment on Inventory /services purchases.
But where as GR, this is an incoming document, what the meaning in controlling it through approval process. That is the way you have to conveincene the client or company.
Ok fine. If still they want this functionality to be implemented (that is to controlling at the GR level for the goods coming in. Then there is another way to control it through receiving the stocks into different stock types using the respective movement types, but not through Release strategy such as Blocking (GR blocking), Quality stock (for checking the quanlity standards thru Quality Inspection) and then later you can move these stocks to Unrestricted use stock, so that this can be allowed to use further.
I dont think there is a functionality in the SRM as well. As I know that you can receive the Goods in SRM through Online Desktop confirmation that too partial or full quantity, that is nothing accepting/approval for the Partial or full quantity that is received against the PO which is created wrto to respective Shopping cart. And that is how you can control the goods that are coming inside / received at Stores/WH inorder to maintain the good quality of Inventory.
Note: Controll always suggested at the time of making agreement (i.e., Release strategy for the PO) but not at the time of receiving the goods. Here while receiving the goods only thing that a Stores person can see tmainly is needs to check for the Quantity, Quality of the goods that are ordered, Delivery time, Mode of transport, Shipping instructions, etc. This will help them further in evaluating the vendor.
Hence there is no logic is going for that option
Hope it clarifies,
Regards,
Sapsrin

What is the procedure for scheduling agreements, for manual entry

dear sirs,
pls explain the procedure for scheduling agreements(manual) creating and invoicing.

From the Purchasing menu, choose Outline agreement ® Scheduling agreement ® Create.
The initial screen appears.
Enter the necessary data. Any data you enter under Default Data: Item will appear as default data in each item.
In the Agreement type field you specify whether you are creating a scheduling agreement with or without release documentation, for example. The agreement types LPA (with release documentation) and LP (without release documentation) are defined in the standard system.
Press ENTER.
The header data screen appears.
Enter the duration of the scheduling agreement. Check the other fields on this screen. Make any necessary changes (e.g. the terms of payment) and define the header conditions (see Maintaining Conditions).
Press ENTER.
The item overview screen appears.
Enter the necessary data for each item (material number, target quantity, price, receiving plant, account assignment etc.).
Material without material master record: leave the field for the material number empty and enter the following:
A short description of the relevant material or service in the Short text field
The material group to which the material belongs
The account assignment category (column A)
The target quantity and the order unit
If you specify an account assignment category, you must enter the relevant account assignment data for each item of the scheduling agreement. To do so, choose Item ® Account assignments.
(See also Account Assignment.)
If necessary, review the details for each item. Select the item(s) to review. Then choose Item ® Details to call up the item detail screen.
Enter the desired conditions for the item (discounts, surcharges etc.). To do so, select the item and choose Item ® Conditions.
Enter further text for the item if any additional instructions to the vendor or to Goods Receiving are necessary. Choose Item ® Texts ® Text overview.
Save the scheduling agreement.
Fi you want to use firm zone then
On the scheduling agreement item overview screen, select the item for which you wish to define delivery schedule time zones.
Choose Item ® More functions ® Additional data.
In the Firm zone field, enter a number of days (calculated from the current date) defining the period after whose expiration the firm zone ends and the trade-off zone begins.
In the Trade-off zone field, enter the number of days (calculated from the current date) defining the period after whose expiration the trade-off zone ends and the planning zone begins.
If the firm zone is to cover one month, enter the value 30 (days) in the Firm zone field. If the trade-off zone ends one month after the firm zone, enter the value 60 in the Trade-off zone field.
In the Binding for Materials Planning field, specify whether Materials Planning may change schedule lines that fall within the firm or trade-off zones.
Save your data.
Delivery schadule
Choose Outline agreement ® Scheduling agreement ® Delivery schedule ® Maintain.
The initial screen for the creation of delivery schedules under scheduling agreements appears.
Enter the document number of the scheduling agreement and press ENTER.
The item overview screen for the scheduling agreement appears.
Select the item you wish to schedule. Then choose Item ® Delivery schedule.
Enter the following for each schedule line:
- Date category (Month, Week, or Day) and the corresponding date
- Delivery time-spot (if applicable)
- Quantity to be delivered (the unit of measure is the same as in the scheduling agreement)
Referencing a purchase requisition: Choose Sch. agmt. schedule ® Create w. reference ® To purchase req. to adopt the delivery data from an existing requisition.
Save the delivery schedule.
Invoice is same like PO

MRP To Generate SCHEDULE LINES for Scheduling Agreement

Hi
I have followed the below steps but still the Schedule lines is not generated for scheduling agreement.
1Maintain MRP views 1,2,3,4 for the material in material mste.(MM01)
2. Maintain Purchase Info Record for the vendor plant & material combination.(ME11)
3. Create Scheduling agreement using ME31L
4. Maintain source list for the material & the scheduling agreement # and Line item set the MRP relevant indicator 2 (Necessary ?) ME01
During Run MRP for the material.the below details entered///
Processing key NETCH Net Change in Total Horizon
Create purchase req. 1 Purchase requisitions in opening period
Schedule lines 3 Schedule lines
Create MRP list 1 MRP list
Planning mode 1 Determination of Basic Dates for Planned
Run MDBT or MD02 but still doesn't create the schedule lines......Anything else missing.
MRP1:
MRP Procedure: PD
MRP Group: 0000 (External Procurement only)
Lot Size: EX (Lot For Lot)
MRP2:
Procurement Type: F
Sched Margin Key: 000
MRP3:
Avilablity chec: 02 (Individual requirement)
MRP: 4
Nil

Raj,
Source List a Mandatory for Scheduling Agreement, if you want to create automatic Scheduling line.
Plz use (2) in MRP RELEVENT tab in ME01 (Source List).
rest of the thing is ok, make sure a material master(MRP 2 VIEW) in that view you have to give a planed delivery days. it is must.
HOPE IT WILL WORK
Regards:
Poision

Release strategy for Scheduling Agreement(SA)

Similar Messages

Maybe you are looking for