Scheduling aggreement release procedure

hello gurus,
can anybody tell me how release procedure for of scheduling aggrement differ from purchase order releases?
my client want release of scheduling aggrement,pls tell me full customization steps that for same.
regards
simran

Hi,
Please check below path.
Transaction SPRO
Path: MM-PurchasingScheduling agreement
-> Release Procedure for Scheduling Agreements
You may read the documentation for details at by clicking the texpad icon.
Release procedure is same as PO/PR release process.
You must assign the authorizationM_EINK_FRG to the persons who are to be involved in the
release procedure (Authorization Management -> Create Authorization Profiles and Assign to
Users)
Regards
Sayan

Similar Messages

Scheduling agreement Release strategy release indicator

Hi all
For the Scheduling aggreement Release strategy is present & release indicator is 6 , Now the requirement is whenever user is changing the any value Scheduling agrrement it should go for rerelease. for any minor change in value even the value lies between the same Release strategy
Release strategy is configured on Purchase group & Value character
Also what is the difference between release indicator 4 & 6. for any changes in the SLA release strategy will be reset in this two release indicator.
Thanks & Regards,
Rajesh

Hi,
This is a standard phenomena any change in value (increase)will reset the release stategy
and indicator 4 & 6 are same only in case od indicator 6 if you have taken the oout also it will get affected

How to configure release procedure for rate contracts release

Dear all,
How to configure release procedure for rate contract following are the requirements
they are two release codes c1 & c2 <=100000,>=100000
                if c1 is not there c2 has to be approved
     Change in the value of the rate contract contract
     Change in the validity of the rate contract
     Addition of deletion of line items
While using a non u2013 released rate contract in the PO an error message should shoot out.
Also the logic should be changed while using the rate contract in the PO.
The usage of the rate contract should be till the validity of the rate contract. i.e. the measurement should be end date of the rate contract and the PO creation date and not the delivery date of the PO. &
It should be possible to refer existing valid rate contracts in purchase orders.
Regards,
bhaskar

Hi,
In SAP rate contract is known as value contract denoted with wk. The release procedure for rate contract is same as that of other contracts and scheduling agreements. The tables for contracts will vary with SA (Scheduling agreement) .You may try and maintain condition records based on the customer combination and maintian the validity date of condition records as per your requirement.For contract and PO will have the same header/item table as EKKO/EKPO, and the release
class in standard is the same FRG_EKKO, you can use the same for contract.
To distinguish if it's a contract or PO, EKKO-BSART can be used.
For contract EKKO-BSART will be MK or WK, while PO will have NB/UB etc..
You can restrict the document type to set up the release strategy for only contract.
Of cause, you can also create your own release class Z* for contract copying standard
one FRG_EKKO via CL01/Class type 032, and then assign the class Z* to customizing:
OLME:
-> contract
->Release Procedure for Contracts
->Define Release Procedure for Contracts
->Release Groups
If you have already created the PO release class.
Assign a new chracteristic of Document Category -BSTYP
Please check below link for detailed release procedure. I hope this wil help you out .Thanking you.
http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE#RELEASEPROCEDURE-TABLESUSEDFORRELEASEPROCEDURES

Release Procedure in PR .....

Hi SAP Gurus,
We do release procedure in PR with Account assignment category K.Here ,for collective release in pr (ME55),check box is disabled... Kindly help me how we enable the check box.We use scope of list as "F".All customization for release procedure is correct.
Thnks & Regards
SAP MM User

You use this component if you wish to set up approval procedures for purchase requisitions or other purchasing documents. Under such a procedure, if a purchase requisition or external purchasing document fulfills certain conditions (e.g. the total order value exceeds $10,000), it has to be approved (by the cost center manager, for instance) before it can be processed further. This process of approving (clearing, or giving the "green light" to) a proposed item of expenditure is replicated in the SAP System by the "release procedure".
It is sensible to define separate release procedures for different groups of materials for which different departments are responsible, and to define separate procedures for investment goods and consumption goods.
Features
Each person involved in the release procedure effects release (signifies approval) via a release transaction, using his or her release code. Once effected, a release can also be cancelled with the same code (that is to say, the original status is reinstated).
If linkage to SAP Business Workflow has been defined for a release code, rejection is also possible. This is only possible for purchase requisitions.
Which Documents Can be Released (Approved)?
Release procedures can be defined for the following documents:
Purchase Requisition
The external purchasing documents purchase order (PO), contract, scheduling agreement, request for quotation (RFQ), and service entry sheet
Release Procedure for Purchase Requisitions
Two different procedures are available for requisitions:
With classification
With this procedure, requisitions can be released both at item level (i.e. item-by-item) and in total. The latter approach is also termed "overall release".
Without classification
With this procedure, requisitions can only be released at item level.
The two procedures are mutually exclusive (that is to say, you must decide in favor of one of them only - you cannot use both).
Release Procedure for External Purchasing Documents
External purchasing documents (i.e. purchasing documents other than requisitions) are released at header level. Item-by-item release is not possible. These documents can only be released using the release procedure with classification.
sri

SCHEDULING AGGREMENT RELEASE

Dear All,
can any one of you please explain .. what are the steps for release procedure for scheduling aggrement.
Is the release procedure for scheduling aggrement is same as for purchase order?
and also, why we maintain release creation profile for scheduling aggrement with release documents.
please help me..
Thanks .
piyush singh

SA release creation profile with doc type LPA is used to initiamate vendor abt ur requirements with the approval of schedulling coordinator. During the generation of schedule line and releaseing the Sch line ...controller has the freedom to alter the requirements...and this freedom is depends on 3 factors:
1)Aggregation of requirements(what is the time period which you maintain to aggregate the requirement before releseing them to vendor)
2)Communication with vendor(How often you will commmunicate with vendor, different for JIT and forecast)
3)Tolerance with which you can allow the schedule lines.(suppose after releasing the lines, you found the requirements again in span of a hours, then u should check the tolerance limits whetther to release the new schedule lines if it exceeds the tolerance or not)
Hope you get the clear idea about the SA release creation profile.
BR,
Krishna

Customisation of release procedure

hi,
how to do the customisation of release procedure.
thanks
katrina

The aim of this release procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual control principle. The person responsible processes the relevant document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
This procedure provides for the release (approval) not only of requisitions (i.e. internal purchasing documents), but also of the external purchasing documents RFQ, purchase order, contract, scheduling agreement and service entry sheet.
1. Create Characteristics
2.Create class
3.Set up release strategy with classification
4.Create release group
5.Create release code
6.Create release indicator
7.Create release strategy
Important Transaction codes
ME51N Create Purchase Requisition
ME21N Create Purchase Order
ME54N Individual Release (PR)
ME55    Collective Release (PR)
ME29N Individual Release (PO)
ME28    Collective Release (PO)
Communication Structure for characteristics
CEBAN - Purchase Requisition
Commonly used fields u2013
BSART     Purchase requisition document type
ESTKZ     Creation indicator (purchase requisition/schedule lines)
EKGRP     Purchasing group
AFNAM     Name of requisitioner/requester
MATNR     Material Number
WERKS     Plant
LGORT     Storage location
BEDNR     Requirement Tracking Number
MATKL     Material group
GSWRT     Total Item Value
CEKKO - Purchase order
BUKRS     Company Code
BSART     Order type (Purchasing)
LIFNR     Vendor's account number
EKORG     Purchasing Organization
EKGRP     Purchasing group
BEDAT     Purchase Order Date
INCO1     Incoterms (part 1)
WERKS     Plant
MATKL     Material group
GNETW     Total net order value
The fields from EKKO that are related to PO release strategy
FRGGR
FRGSX
FRGKE
FRGZU
Check the tables for the release codes
T16FG
T16FS
T16FB
SAP Help : http://help.sap.com/saphelp_47x200/helpdata/en/75/ee14a355c811d189900000e8322d00/frameset.htm

Use of Release Procedure / status in Condition Table

What is the purpose of Release Procedure / Release status when creating condition tables ?

Hi
Release procedures are used in condition tables to control whether the condition types for these condition tables have to be read during pricing condition determination or not.
If the condition table status is released then only the condition types will be read during pricing determination. If the status is not released, then they can be used for information purposes or for simulation of pricing.
The release status is controlled by processing status too, which can be seen in condition record creation screen.
So in crux, the processing status with Release status help in simulation of pricing, blockign the condition records from being read during pricing etc.
For more information an F1 help on the following path will give you some more information.
SPROSD-BF-PRICING-DEFINE PROCESSING STATUS----Here read the documentation meant for this link. You will get some more clarity on this.
Rwd point if it helps.
Reward points if it helps.

Scheduling Agreement Release Comparison

Hi Experts
does Scheduling agreement release comparison works for JIT delivery schedule (Doc Type LP) in SNC?
if yes then how it works and how it is different than forecast delivery schedule release comparison (Doc Type LPA)
Thanks

Hi Indira,
The are two ways to address your business case :
1. The simple way is to forward the work item to the concerned person (by selecting the user from user list) for releasing the work item.
2. In the second option, we need to modify the workflow. A conditional work item (Accept/Reject) needs to be inserted immdtly after the SA workitem to accept or reject the user decision. Based on the decision, the workitem will either show him the SAP user list to redirect the same for releasing or it should go to the concerned user automatically (in static agent assignment). In case of acceptance, it will go to next step bypassing the rejection loop.
In case of any further queries, please revert.
Regards,
Ashish J. K.

How to delete the old schedule line release?

Hello,
How to delete the old schedule line release in apo?
Generally GR has to be carry out schedule line release in r/3 which reduces the Schdule line release.
But i do want do GR against old schdule line release instead i want to delete the old schdule line release.
Please suggest.
Regards,
Sunil Patil

Sunil ,
/sapapo/cmds_del is the tcode to deleted sales scheduling agreement confirmations and releases
/sapapo/display_conf is the tcode for displaying sls. sch.agr confirmations and releases
The above two are in the supply chain collaboration menu
/sappao/cmds_sc02 is the tcode to delete sales scheduling agreements . This tcode is in the application specific master data menu
Thanks
Saradha

How to delete the old schedule line release in apo

How to delete the old schedule line release (from current date) in apo which is having schedule firmed?
Please suugest.
Sunil

How is it possible to delete old purchasing schedule lines in APO (that do not exist in R/3)?
Though used successfully before, /SAPAPO/CCR will not reconcile our discrepancy in this case.
Thanks in advance,
Jim

PR release procedure no longer working-error MEPO 822

I've raised a message previously regarding PR release problem. Now i've found something that need expert helps to clarify on this.
Situation :
One of my client(ABC) implemented release procedure for PR which is not assign to value limit. It is by document type. They had 2 document types; NB and RNB.
NB = NOT subject to release
RNB = SUBJECT to release.
So when they :
create a PR with document type RNB - it will goes for approval.
create a PR with document type NB - it will not go to approval.
It was working fine until after they created a new document type which copied from NB, called ZTP.
ZTP = NOT subject to release.
They did not touch anything on PR release configuration. However, the release has no longer working. Means, when they create PR with document type RNB, it will NOT go for approval as it suppose to. I've check in configuration, all are fine.
Findings:
I've created a PR, and go to ME45N to release it but system prompt me an error message
"Purchase requisition 10000066 cannot be released". I check on the message data, the error coming from MEPO, message number 822.
So i check in OSS and found a note which is similar to this case.
Note 939371 - Overall release PR using ME54N gives error MEPO 822
Link : https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=939371#Text
But my question is,is it also applied to ME51N and without external application as per my client's case?
Please anyone help.
Thanks.

Hi guys!
Wants to share something. I had a problem to release my PR. When i want to release PR via ME54N, system give me error message "Purchase requisition 10000066 cannot be released". When i checked message data, it is coming from MEPO Messafe 822. So i asked SAP, they said this one is caused by different issue. Here's the reply from SAP.
Here's the reply from SAP :
Purchase requisition 10000066 cannot be released
Message no. MEPO822
Now click the other requisition button and let say
choose Purchase requisition 10000068,
Execute ME54N again:
Purchase requisition 10000068 cannot be released
Message no. MEPO822
Comment/explanation:
The log incidence seems not having problem with release
strategy as it was ok but it was the last PR was called
everytime ME54N was called. This same as it works in enjoy
transaction ME21N/ME22N or ME51N/ME52N.
For example, When using ME21n or ME22n to create or change PO,
after saving the PO. There are 2 ways to exit the transaction,
1, enter another T-code or use /n to exit directly.
2, use 'F3' or the 'green tick' to exit ME21n (or ME22n)
Then you can access ME23n to see the difference.
For the 1st way, ME23n won't display the last PO created in ME21n
For the 2nd way, ME23n will display the last PO just created!!!
Please see attached consulting note 595627 that explains a new
functionality as of release 470:
Due to performance problem, a decision had to be taken about the way to
use transactions. If you leave transaction ME21N/ME22N via the
exit button (F3), the expected PO will be displayed next time you use
these transactions. But if you quit abruptly (/nXXX) the PO number
won't be saved for the next transaction ME2?N.
As SAP note is the official document to explain system behavior,
this document is provided by SAP developement to explain this system
behavior to customers.
In your case, you had used ME54N and this was same as you use ME53N.
The last PO always display. You may try to view Purchase requisition
with release strategy, for example Release group R1, Rel. strategy
R1, then after this execute transaction ME54N again, the message
MEPO822 will not be there anymore.
Hope this will help you guys if you're having the same problem in future.
Thanks,
Crystal.

Bapi for scheduling agr release

hi could someone help me to findout bapi for scheduling aggrement releases
transaction me84.

Hi Alok,
I am not sure about BAPI for this function.I suggest you try this kind of function with user exit like COOPA002 using appropriate program logic.
Regards,
Ashok

Creating a new "Class type" in release procedure.

Hi guys,
how can I create a new <b>"Class type"</b> in release procedure?

Hi,
But I do not know why anyone would create a new batch type for release strategies, it is totally unnecessary and provides no additional options. The class type indicates which objects can be classified and there is already one for release strategies.
You can create a new class or add characteristics to the existing class used in the release strategy anyway.
Ther is also NO WAY that two classes can be used in the release strategy and this new class type would not change this either???
Steve B

How restrict the release procedure tab in ME21N

Hi,
We have the Condition tab for free goods Iin PO.
Now, we want to implement release procedure in PO, and also restrict the release procedure for free goods in the same based on the combination of document type (EKKO-BSART) and free goods (USMON)field. Please provide the solution.
Regards,
Mars.

Hi
Try using the exit M06E0004.
Regards
Shiva

Scheduling Agreement Release Strategy Issue

Hi,
We have a typical problem in Scheduling Agreement Release Strategy.
Once the SA is released for the first time it should restart the release strategy again if there is a change in Quantity or Value or Purchasing group. The release strategy is getting restart for some of the release strategies and not for others. I compared the characteristics, class for both the release strategies and I am not seeing any difference.
Can anyone please help me in this regard.
Thanks in advance.
Regards
Ram

release strategy can be rerigger in case where qty or price change and the changes is over the percentage you defined for Release indicator
goto release indicator config and in SPRO for release strategy and check the Value change %
maintian 0.1 here
so any change above 0.1 will retrigger
and maintian value 4 in chgable field.

Scheduling aggreement release procedure

Similar Messages

Maybe you are looking for