Release strategy for MRP generated PR.

Dear friends,
Can we have release strategy for MRP generated purchase requisitions.....
What are the steps required if yes.....
Plz. suggest....
Thanks in advance
Navin

HI,
IF you want to characteris MRP genrated PR then you have to define different document type other than the standrad one.
For this MRP define the release stratergy has usual procedure.
In case if ou dont have a different document type also the standard release procedure which you have conffigured will hold good.
Thanks & Regards,
KIran

Similar Messages

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

How to setup a release strategy for store generated purchase order

Hi there,
Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
Greatly thank for your help.
Kind Regards,
2tea

Please go thru the below Release Procedure and check whether you have maintained all the settings properly.
PO RELEASE STRATEGY
The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic e.g. NETVALUE
Click Additional data Table name CEKKO Field name GNETW and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for PO
Release codes - New entries
Grp Code
02 01
Release indicators
Release indicators Release Description
0 Blocked
1 X Release
Release Strategy
Release group 02
Rel.strategy 01
Release codes 01
Release status 01
Classification Choose your check values
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
Regards,
Ashok

PR Release Strategy for MRP & Manually created PR

There is a scenario in which it's required when,
PR is generated automaticaly through MRP then Release strategt should be applicable and when
PR is created manually then release strategy won't be applicale.
Please suggest about this..........
Thanks in advance.

Hi,
You should have two document types ( as required by you here), MRP PR document type & Manual PR document type.Link plant, MRP group and the default order types as MRP PR document type in OMDT t.code.
You should create release characteristics (CT04) with the table & field and add all release characteristics in release class. For document type release characteristics with CEBAN & BSART and do not keep value ZNB which you do not want, just keep value ZMNB. During design of release strategy keep value only for document type ZMNB with other character values.
Regards,
Biju K

Release strategy for PR generated through network activity (Project)

*Hi,
I am facing the problem that PR generated through network activity (Project) does not have release strategy attached. For same combination of characteristics value of PR document type , account assignment, release strategy strategy is attached for PR created manuelly.
Please suggest
Regards.*

What is the account assignment used in Network generated PR, Have included that in your characteristics? Is PR in Your defined document type?

Release Strategy not working for MRP generated PR

I have one qurey. Currently we are release strategy for normal PR.Now client want to activate release strategy for MRP generated PR.
current Release Strategy for normal PR configured as following.
Purchase requisition document     RV
Purchase requisition document     ZADV
Purchase requisition document     ZIMP
Purchase requisition document     ZSER
Purchase requisition document     ZSTD
Purchase requisition document     ZSTR
Purchasing group     A01
Total value of requisition for     > 1.00 INR
Creation indicator (purchase r     Realtime (manual)
Overall release of purchase re     Yes
For MRP generated PR I add creation indicator B - Material requirements Planning.Even after add creation indicator release strategy is not triggering for PR.
To trigger PR any setting need to do other than add creation indicator.
Regards
Sathish

Hi
You don't have to include creation indicator as parameter. Check in what documnet type MRP PR is generated. You can see it in t.code OMDT. At document type level also you can manage it. You need to include creation indicator only if a seperate person approves MRP generated PR.
To know how to configure release procedure see the below link
http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE
Regards
Antony

Release Strategy for reservation created from PM and PS

Dear All,
How to configure the release strategy for reservation generated from PM and PS.
Regards,
Atanu

do you talk about release strategie for requisitions, or really reservations?

Release procedure for MRP PRs

Hi,
Is it possible to configure release procedure for MRP generated PRs?
Regards,
Supriya.

Hi Supriya,
1. Create a Characteristic Value with the Table name CEBAN and Field ESTKZ (Creation indicator)
2. Assign the above to a Class
In the Char Value, select 'B' as the option as it refers to MRP created PR.
Hope this will be useful for you

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...??

Rel. proce. for MRP generated PRs

Dear all
Can we effect release procedure (approval) for the PRs which created thru MRP? Pls explain.
Thanks in advance

Creation for Release strategy of automatically generated PR is same as the normal one.
can u let us know for nomal standard PR what are the characteristics r u using?
regards,
indranil

External mail for workflow of release strategy for PO

Dear All,
I have configured the workflow of two step release strategy for purchase order and the internal mail is getting generated in the sap business workplace with the error message SWF_RUN 594 this i have taken care with SWE2 with changing the settings of "Behaviour upon error feedback" from "default" to "do not change linkage"
Now the requiremnt is that the message has to be send to first level releaser through external mail and once first level release the PO external mail should be send to second level releaser.
Please help me with the configuration step that is to be done
Thanks in advance
Naveen Singh

Schedule the report Rswuwfml2. this will send workitem from sap inbox to respective user external mail id maintain in user master.

Release strategy for auto created PO's

Hi Guys,
I have a requirement to implement release strategy for automatically created PO's.
PR's are created automatically and we have a program which create PO's automatically.
we would want to release them before generating output to vendor.
could anyone please have any inputs here.
regards
mittu

Hi!
You may use your existing release strategy or create a new one (depending on your requirement). You just have to add/ use the document type you used for your auto-generated POs.
Hope this helps! =)

How to configure wokflow for MRP generated & manually created PR

Dear Gurus,
I have to customize SAP workflow for releasing Purchase requisitions. I will be using enhancement M06B0001 for my own role resolution.
I have some questions regarding workflow
1) How to configure workflow for MRP generated & manually created PR?What are the steps? what are the limitations in doing so?
2) Since we are facing the problem of insufficient user license ,How to send notifications to NON SAP users?(We have thought of creating a Z table for the same)
Looking forward to your reply,
Thanks in advance,
Best regards
Tushar
SAP MM Consultant

Dear Mike,
Thanks for your reply, & sorry for not responding on time.
Here are my constraints:
1) Not a single component of HR module will be implemented.(Project management decision:-()
2) Number of user licenses are less, considering the workflow users.(Hence we have thought of creating Z table for employee nos. & EMAIL IDs ,& this table will be accessed by using M06B0001 user exit.(It is still in development phase. Truely speaking, dont know whether it will work or not).If this works out ,then I believe, record from SU01 will not be used (Please correct me here).
3)We have 2 instances on development server.(in short,2 separate installations on same server by creating additional instance). What are the implications of this particular system landscape on workflow? Whether workflow will work or not??:-(, :-(.
The reason I asked you 3rd question is , As soon as 2 nd instance was created on development server, Short Dumps are coming while running transactions of Workflow builder.(SWDD & PFTC).It is giving error" Table is unknown or does not exist". Description of error says"The current program"SAPLSWF3 had to be terminated because one of the statements could not be executed."
"An SAP Open SQL Statement contains a table that does not exist in the database or is not listed in the ABAP Data dictionary.The Table is "SWF_WFPDSC" or another table is accessed in the statement.
Program=SAPLSWF3
Include=LSWF3U05
Row=22
Module name=SWF_WFP_REPOSITORY_CONTENT_GET
The same dump is coming while accessing SWF_WFPVW table from SE16.
Request to Mike & all of you, help me in this regard.
Thanks in Advance,
Regards,
Tushar

Release strategy for PR with materials having different prices

Hai Gurus
Can we make a release strategy for a variant configured material ?
I mean create a strategy in such a way that price is critical factor and the materials what ever we choose for the PR has different characteristics dependencies like for example ( A chair having different characteristics like color, material ( like steel, leather etc) and other features like wheels etc and whatever characteristics we choose has a different price.......... so when v come to the release strategy it has to be approved by the next level if it reaches $ 1000 and so on.
please help me out in this issue

Hello Arif Mansuri
thanks for your reply, yes I have taken it as total value only. The scenario is I am asked to use three different characteristics ( total value, materials, MRP Controller) and assign them to a class and if the customer picks any number of different materials and if the price is more than 1000 then it has to reach to the next level for approval. i thought i am suppose to use object dependencies here......... can we do this in a normal release order if so how would be the strategy played here?
thanks for your time

Release strategy for PO and Contract

Hi,
I maintain characteritic for PO
Plant
Doc Type
Net Order Value
Purchasing Group
I maintain characteristic for contract
Company code
Target Value
Doc Type
Purchasing group
My class consist of
Plant
Doc Type
Net Order Value
Purchasing Group
Company code
Target value
Q1: Do i need to maintain ALL characteristic value when i define my release strategy for PO or Contract as some characteristic only apply to PO only or contract only?
Q2: What option do i have if i need to maintain all characteristic value ? leave it blank ? empty
Currently my PO release is working fine but when i try to maintain the contract release inside the class . my PO release is not triggering . I maintained diffrent release group for both PO and Contract .
Thank for your advice

First of all
For purchasing like PO,pr,contract you can able to get in ekko table.No need to maintain separate release unless if it your business requirement.Take Document type as one of the characteristics it will distinguish whether it is PO or contract.
You have to maintain all the characteristic value then only it will trigered release.
Check the release indicator as well.
Hope it will help.

Release strategy for MRP generated PR.

Similar Messages

Maybe you are looking for