PR Release Stgy - With Classification & Without Classification -Difference?
Hi
Pls tell me the concept behind this and the difference
Vijay
Hi ,
In without classification only four characterstics are allowed and they are
account assignment category
material group
plant
purchase requisition value
Where as without classification you have more flexibilty and almost all the fields in table EBAN can be used for setting up Release strategy ( Also we can have release strategy at item as well as at header level in with classification )
Regards
Ankur
Similar Messages
-
Creating Roles for Purchase Req. release strategy with classification
Hi friends,
Since I have created Purchase req rel strategy where I have four release strategy
1. For Plant 1 When value <= 5000 (Officer) will release , release code 01 release release strategy r1 and rel code L1
2 For Plant 1 When value >= 5000 (Manager) will release , release code 01 release release strategy r2and rel code L2
Now the manager will have 2 release code,if officer is absent he could release the requisition.
Same has to be done for plant 2
The release Group and code needs to be assigned to the Roles , could anybody tell me where i could know about roles and will be able to create roles and assign authorisation objects to the Roles , and release group and code to the enduser.
though its a basis job , since I have no idea , I mean I have never worked with Roles ,as now I have created the Release strategy with classification I need to assign authorisation objects to the Roles as I have four release strategy
1. For Plant 1 lower value of requisition 1 codeL1(Officer)
2 For higher value of requisition 2 code say Li and L2(Manager)
Manager should have 2 codes if officer is absent he could release
Same has to be done for Plant 2
Thanks N Regards
SiddharthaHii,
Steps:
1) Create a Role
2) Add the authorization Object M_EINK_FRG by taking the manual option
3) Assign Release Code and Release Grp
4) Assign the Role to the User ID which has the authorization of the Release Code and Grp.
Regards,
Kumar -
Tranposrt - Purchase Requisition Release Strategy with Classification
Gurus!
Tell me if I want to Transport the Purchase Requisition release strategy with classification. The Data in each charisteristics in each PR Strategy that I have set in Dev is not getting transported to Quality.
Do I have to enter the data in characteristics again in Quality and the same procedure I have to apply for Production.
If yes, in this scenario, Can I make Production modifiable.
Regards
SajidHello,
Create a special ID in PRD with access to change characteristics. This ID should be released for specific purposes and with approval (project manager/SAP support manager). You can also turn on auditing so that all activites performed are logged which can be used to satify auditors.
Cheers ! -
PR release strategy with classification
As part of a rollout, we are migrating an instance of SAP to the template SAP. Both the SAP instances are following u2018PR release strategy with classificationu2019.
The limitation is that I can configure only two release group in PR release strategy with classification. One for overall release and one at item level release. Also, I cannot assign two different release class for the same release group. If I add additional characteristics in the existing class and keep other irrelevant characteristics as blank the release strategy doesnu2019t works. the release strategy does not triggers.
Any pointers to solve this will be highly appreciated.Hi Ashish,
If your requirement is to have release strategy with more or different characteristics than in the existing system,you may create a new release group and assign the same to release class.There no restriction for having multiple release groups for same release class.Then create new release strategies for the newly created release group and so on.
Regards,
Edited by: Dayanandan Kamath on Oct 20, 2010 7:52 AM -
Release Strategy With Classification
Hey All,
I would like to get some information about release strategy with classification for purchase requisation and purchase order.
Please send me some information regarding this.
Thanks
Kawalhi,
To see the all the linkages firstly see the classifcation and class defined in the sap system at:
SAP easy access --> Cross application components --> classification system --> master data --> characteristics and classes(CT04 and CL02)...
TO see the customisation, check:
Spro --> MM --> Purchasing --> PO/PR etc --> Release procedure --> Rel procedure with classification --> Here check for all the different transactions...like Relase codes, release stategy, access sequence, schema etc...
Also one important point abt it is:
PR is possible to release at header as well as at item level...
But PO and other external docs are only possible to release at header level only...
In the customisation check all the linkages you will get best out of it....
Regards
Priyanka.P -
Release procedure with classification not getting triggered
Hi,
I have configured the new release procedure for the PR release of type with classification, but its not getting triggered. Earlier my SAP system had without classification in place, but I wanted to have with classification. Can any one suggest how do I switch between two.
Ideally once I create the release group in with classification procedure that procedure gets activated and gets triggered. Unfortunately its not happening in my case. I tried deleting the entries from the without classification side too, but still it doesnt respond. Is there in patch or note missing.
Your suggestion would be highly appreciated.
sachinHi Jurgen,
I am configuring it for PR and with classification method. Well for simplification I am using just purchase group as characteristics, but still its not working. Earlier system had without classification in place, as its there in a default system and used to get triggered. When I created new procedure its not getting triggered. To be assured I deleted the data from witout classification, but still its not working.
Where as I did the same setting for PO, its working and giving me correct releaes strategy.
My characteristic is PRGRP using the communication structure CEBAN and field as EKGRP
Please suggest me on this.
sahcin
Edited by: sachin sagane on May 18, 2010 6:32 PM -
Trouble shooting Purchase requstion Release stratergy with classification
Hi,
I am trying tos Set up a release startergy for Purchase requistion items with classification
I am trying to capture Requestions with the following characteristics.
Purchasing document type (ref to CEBAN -BSART)
Total Item Value (ref to CEBAN-GSWRT)
Purchasing group (ref to CEBAN-EKGRP)
I have set up the release stratergy. However when I create a requisition with the criteria matching the release stratergy the PO does not get activated.
I want to see what Charactersitics my PR has at runtime so that I can try to reslove the issue.Does anyone know of a transaction or report I can check to see what charatersitics my PR picks at runtime?
Thanks,
Ishan.Hi,
Go into trx CL30N and enter the values of the document :
1.If you don't get a result> check in customizing definition of release strategy and check
In trx OLME > PR > define document type
"Overall release of purchase requisitions" flag ( fiield V_T161-GSFRG ) should not be SET
In TRX OLME > OR > release staregy > Release Groups
also FRGFG should not be set
2. If you get one result> check
If you have activated the userexit 'EXIT_SAPLEBND_001'
(Include ZXM06U13) This exit is relevant for the individual release.
If you activating the userexit, please ensure that you implement
the coding line E_CEBAN = I_CEBAN. in the include or deactivate the
exit. Please refer to point 3) of the note 365604.
BR
Nadia Olrandi -
Regarding Release Procedure with classification
Hi All,
Please anybody tell me,is't possible to release at item level in external document like PO,RFQ.
Thanks & Regards
Suresh.In principle you wouldn't send (/release) part of an external document.
The information at Header level applies to the whole of the document, in other words it can also be considered as applying to each item. For example the payment terms apply to the whole of a PO, not the individual items. The individual items can not be considered complete without the Header information. Consequently the release strategy is set at Header level.
In theory all POs may be created with reference to preceding documents and these may be released at item level e.g. Purchase Reqs. Therefore at the time of creating the PO the individual PR items have been approved from a business point of view, the PO typically represents the overall commercial approval for the items. -
Purchase Requisition Release Strategy with classification
Hi there,
Please help,
I have the release strategy and workflow working. (Overall Release)
Problem is that Org Structure is not updated so workflow has been configure going to (US) user. As i am using workflow option 1 which is resolved via Group, Code & Plant, I have to have a code for every region and manager to resolve the workflow. I am not using plant as business requirement is overall release.
Scenario is that there are 8 regions with 1 senior region manager and 1 executive.
The region managers can each release up to 20k. Senior region manager must release from 20k - 50k. Executive must release from 50k -250k.
Release Codes:
Regions = L1 - L8
Senior Region Manager = SR
Executive = X1
Characteristics are:
DocType = NB
AccAsingment = K (Cost Centre requisitions)
Purchasing Group = (Each region has own group)
TotValue = 0k -20k, 20k - 50k, 50k - 250k.
Now the release strategies.
Even though it is the same senior manager and executive why do i have to create a new strategy for every region's escalation above 20k taking into account that the business requirement is that the correct region manager has to release before the senior manager can release? It just seems so pedantic when i would rather just add the correct Purchasing Group everytime.
This is only one leg of the Org Structure there are over 40 depts, and managers that will create and release. Do i really need a strategy for every single scenario?
Thanks for taking the time to read.Hello,
Create a special ID in PRD with access to change characteristics. This ID should be released for specific purposes and with approval (project manager/SAP support manager). You can also turn on auditing so that all activites performed are logged which can be used to satify auditors.
Cheers ! -
Release Procedure with classification
hai all,
I read a statement which say "Realese procedure with calssification PR can be relesed at header level"
I want to know what does this sentence mean actually. if possible please expalin me with a practical example
thanks in advance
with regards
Sreenivasa Chary
9848993644Release procedure defined at the client level and it use only one class
now suppose you have assigned the 6 char to the class then your release strategy should contain the value in each characteristcs other wise your release will not work.
the bottom line is you have to define the value for each char. -
Migration form W/O Classification to With Classification Release Strategy
Hi MM Experts,
Our client is currently having purchasing requisition release strategy based on without classification. There are almost hunderds of release codes for multiple sites.
Now he wishes to migrate to release strategy with classification. So, Can anyone guide me on what all the cut-over tasks that has to be considered before going live ???
Thanks in advance.
Best Regards,
Devendra Gawarehi,
first for doing the settings
follow this link
http://www.sap123.com/showthread.php?t=59
all these settings should be done in development server and test it
if it working good
migrate the data to production server
if useful Reward me
Thanks & Regards
Swathi -
Shifting the PR without classification to with classification
Hi All,
I have deleted the PR release strategy without classification randomly and configured PR release with classification in dev server.
Now I want to delete the PR without classification from Live server and incorporate the new PR release strategy with classification in live server.
Let me know the sequence I should follow to delete the PR without classification from Quality server and apply in live server so that new PR release strategy with classification should take place.
Thnx,
AChello Amit,
yes, delte the strategies first.. check Table T16FS, T16FV and make sure there are no entries
Then delete the codes and check T16FC, followed by the groups.. T16FG.. these should dbe empty
You don't have to delete the characteristics and class information, if you know you'd be using them again -
PR-Rease strategy with classification
Hi,
What are the steps Involved from shifting PR without classification to with classification?
Can we include the parameter # 1) Total value of requisition for overall release procedure 2) Plant 3) purchasing group 4) cost centre 5) Account assignment category in with classification startegy ?
Thanks.Hi,
If you set up the release procedure with classification for purchase requisitions, the procedure without classification is deactivated. The two procedures are mutually exclusive (that is to say, you must decide in favor of one of them only - you cannot use both).
If you wish to set up both the overall release procedure and the item-wise procedure for requisitions, you must create one class for each procedure.
To set up a release procedure with classification, you must make a series of settings in Customizing. You must perform the following steps:
1. Create characteristics and classes
Note
If you wish to link your release procedure to workflow, you must perform steps 2 and 3. You make these settings in Customizing for Business Workflow (Basis -> Business Management).
Otherwise, continue with step 4.
2. Define organizational plan
3. Assign standard tasks and activate event-receiver linkage.
4. Set up release procedure with classification
a) Create release group
b) Create release code
c) Create release indicator
d) Create release strategy
Note
You need only carry out the following step if you wish to link your release procedure to workflow.
e) Assign release code to a release point
5. Check release strategies
And, regarding your 2nd query:
In communication structure CEBAN, you will find all the fields that can be used as characteristics for a release condition (e.g. MATKL for the material group and GSWRT for the value of the item).
Check which fields you wish to use as characteristics for your release strategy. To do so, choose Tools -> ABAP Workbench -> Development -> Dictionary, enter CEBAN in the Database table field, and choose Display.
Regards,
Narayana. -
Release strategy with classfication & w/o classfication problem
Hello guys
I am facing problem in setting up the release strategy . ECC 6,0 came up default without classification. we need with classification. i set up w/o classification, then delete it and then did with classification.. it works fine for me in the Sand Box , but in dev server it didn't work for me. It is working only w/o classification , When i am trying to set up with classification , it didn't work for me , i am getting the error message in the check release strategy as follows . How i can find which release group need to create ?
Any help will be highly appreciated
Thanks
N
Release code for release group is inconsistent
Message no. ME_RELCHK057
Diagnosis
The release code is not allowed because the associated release group no longer exists.
Procedure
1. Recreate release group .
Note
The release codes and release strategies for a release group are only displayed if the release group still exists. Therefore you must create release group in order to delete the release codes and release strategies.
2. If necessary, delete the release strategies and the release codes for release group .
3. Then delete release group .Hi,
If you set up the release procedure with classification for purchase requisitions, the procedure without classification is deactivated. The two procedures are mutually exclusive (that is to say, you must decide in favor of one of them only - you cannot use both).
To set up a release procedure with classification, you please delete all entries in the Release codes and Release Groups for Purchasing Requisitions and start a fresh creation of new Release Codes and Release Groups.
Hope you have followed the following procedure:
1. Create characteristics and classes
Note
If you wish to link your release procedure to workflow, you must perform steps 2 and 3. You make these settings in Customizing for Business Workflow (Basis -> Business Management).
Otherwise, continue with step 4.
2. Define organizational plan
3. Assign standard tasks and activate event-receiver linkage.
4. Set up release procedure with classification
a) Create release group
b) Create release code
c) Create release indicator
d) Create release strategy
Note
You need only carry out the following step if you wish to link your release procedure to workflow.
e) Assign release code to a release point
5. Check release strategies
Hope, this time you will be able to perform the PR Release with Clasiification.
Regards,
Narayana. -
PR overall release strategy with acc. assignment category characteristics
Hi,
Here is my issue : i created an Overall release strategy but the characteristic is on item level. In some precise cases, no release is generated.
see below more details :
I have created the following PR release strategy with classification.
PR type concerned " NB": overall release
Rlease group concerned : overall release
In this release group i have 1 class
in this class i have 2 characteristics : PR type and Account assignement category.
Release strategy 1 :
PR type = NB
Acc. assignment cat = P, W
Release strategy 2:
PR type = NB
Acc. assignment cat = K, V
TEST 1 : PR type NB, 1 item with P category
OK the release strategy 1 is generated
TEST 2 : PR type NB, 1 item with W category
OK the release strategy 1 is generated
TEST 3 : PR type NB, 2 items with P category
OK the release strategy 1 is generated
TEST 4 : PR type NB, 2 items with P and W category
TEST KO, no release strategy is generated
=> what should i do to solve this issue ?
Thank you in advance for your quick answers,
IsabelleWhat is the specific requirement for Overall release strategy?
Besides, once you go for Overall release strategy, you cannot have another release strategy at item level.
Every line item generates a PO, so logically should be set to a release strategy.
Bottomline is use release strategy at line item level Unless a specific reason exists.
Regards,
Sameer
Maybe you are looking for
-
HT1379 How do I stop a program from opening at start up(iPhoto)?
How do I stop a program from opening at start up? (iPhoto) Also, my mac recently shuts down completely while in sleep mode. Any reason why this happens?
-
After install ios 7 wifi won turn on please help....
after install ios 7 wifi won turn on please help....
-
Enforcing additional checks in sequence of activities of e-recruitment
Hi Experts, Is there any way to make the steps of an activity mandatory? Something like the "Check Suitability" activity needs to be in "Complete" state before I can go ahead with the next activity like "Acknowledge Registered Application" ? As per t
-
I continue to receive an App upgrade notice for an App that is not on my computer. After spending several hours with a variety of divisions (Lion,iTunes,iPad,iMac) of Apple Tech Support, none can give me any definitive explanation or solution. Prior
-
Captivate 7 project fails to publish to Adobe Connect
ERROR MESSAGE: "Failed to publish your project to the Adobe Connect Server. Verify your network conection and try again" First of all, my network connection is fine. And I have run through a number of solutions to try to make this work but im running