CCreate Release Strategy using department name in "Release Code", not User ID SAP.

hi experts...
i wanna create new release strategy, but in part "choose activities => Workflow => assignment of role to release code"
in field Agent ID usually we fill SAP user ID, but i wanna using department name.
is there anyone can help me
thanks,

Hi Raju,
Are you setting release for purchase requisition or purchase order ? If you are setting the release strategy for purchase requisition you need to enter table name as CEBAN and for purchase order give table name as CEKKO.
Enter tcode SE11 and give database table name as CEKKO and choose the appropriate field name for the desired component from here. Do the same with table name CEBAN for pur req.
Hope this was helpful.
Cheers,
XsNitin

Similar Messages

How to approve or release a Custom workflow release strategy using a prog.

Hi There,
I am working with a custom transaction with release strategy using custom workflow. I am done with the module pool and workflow templates. And also I can able to start workflow using the FM SAP_WAPI_CREATE_EVENT.
My actual Issue is I have set of buttons in the module pool screen with names Approve (1 to 5) and Reject (1 to 5). When I press the "Approve 1" release strategy of the first person need to approved. Is there any Function Module or Classes for approving the workflow release strategy using buttons in screen.
Thanks in advance,
Viruman

Hi
Make use of the function module SAP_WAPI_DECISION_COMPLETE. To this function moduel pass the workitem ID and pass decision parameter value as 0001 for approve and 0002 for rejection action. You can check in this forum with this function module you will find lot of threads.
If its not a decision step then you can make use of SAP_WAPI_EXECUTE_WORKITEM or SAP_WAPI_WORKITEM_COMPLETE.
Regards
Pavan
Edited by: Pavan Bhamidipati on May 26, 2011 11:43 AM

How to control PO Release strategy using WorkFlow

please tell me how to control PO Release strategy using WorkFlow.
Moderator message: please search for available information/documentation.
Edited by: Thomas Zloch on May 31, 2011 9:35 AM

Hi,
Yes they are same unless you differentiate by using
1> Purchasing Document Category i.e CEKKO -BSTYP
A..... Request for Quotation
F......Purchase Order
K......Contract
L......Scheduling Agreement
So if you just create a characteristics for CEKKO-BSTYP then maintain its values only for F so it will not be applied to RFQ

Release strategy: Tx CL20N Error: Entry 01 does not exist in table T16FS

Dear MM Gurus,
I was designing new release strategy for PR and PO, so I deleted all the previous entries(SPRO) available in SAP. I created my new entries but in the transaction CL20N I got the above mentioned error: "Entry 01 does not exist in table T16FS-Check your entry" . I checked the table T16FS, where the entries were available. It also showed the previous entries I deleted from SPRO.
Refering the SAP note 365604 (version 29, valid from 08.10.2008), I created the deleted entries again so that I could delete them in the required sequence
1. release strategies
2. release indicators
3. release codes
4. release groups
5. class
After deleting the entries in the above mentioned sequence also I am getting the same error in CL20N.
I ran report RCCLZUOB, it shows the entries does not exist.
Please help.
Edited by: Akshay Kurhe on Mar 2, 2009 6:02 AM

hi
check this setting
Distribution Using Object Classes -->Maintain Class Types & Maintain Classes

Using scan name in tns file not working at client side...

Hi All,
I have installed 2 node RAC -11gR2 on ORACLE VM Server 2.2.1.
now, I want to give tnsentry to dev team to use this RACDB.
I am using scan name in tnsnames.ora file. Also I have make scan name entry in /etc/hosts not in the DNS.
I have below entry in RACDB server...
RACDB =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = RWCORA-cluster-scan)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = racdb)
== now in dev user side, If I give the same above tns entry and make entry of this scan name and two VIPs in /etc/hosts file of dev user then SQL*Plus is successfully connected but not JDBC like SQL*Developer.
I have make below entry in dev user's /etc/hosts file:
10.40.0.51 RWCORARAC1-vip
10.40.0.52 RWCORARAC2-vip
10.40.0.50 RWCORA-cluster-scan
Is this correct way or suggest me perfect link through which I canconnect all OCI, JDBC connection from client side.
Thanks...

you can use JDBC thin URL in SQL developer.
Choose NEW/DATABASE CONNECTION, then put the connection type "Advanced" and then place the jdbc url as :
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=RWCORA-cluster-scan)(PORT=1521))(LOAD_BALANCE=yes)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=racdb)(FAILOVER_MODE=(TYPE=SELECT)(METHOD=BASIC)(RETRIES=180)(DELAY=5))))

PO release strategy- order of names

Hi! I have 3 releasers and either of the 3 may release the PO first that's why I did not ticked any prerequisites. However, I would still want the names to appear in a certain order in the PO release tab. How do I control this? Example: the order that I entered in the releasers are: Releaser 21, Releaser 35, Releaser 25. But in the actual PO, the order became Releaser 21, Releaser 25, Releaser 35. I want to change the order, how do I do this? Thanks!

looks like it is alphabetical order, so you would need to add a character for the sequence in the description like
A Releaser 21
B Releaser 35
C Releaser 25
or Relaser 1_21 , Releaser 2_35, Releaser 3_25

Release Strategy Processor Names under Release Strategy tab for a PReq

Hello Experts,
We have situation in Release Strategy for Purchase Requsitions in which we need to display all approvers names under the Release strategy tab for a Purchase Requisition.
Senerio work as follows.
Based on the Release strategy customization settings,Purchase Requisition subjected to release strategy selects the approver names from a custom table.
In the Custom table we have names of the approvers with release codes.
Purchase Requisition displaying the names of the approvers according to alphabetical order.Hence it displays First one user or approver name under the release strategy according to the approver alphabetical order from the custom table.
Can we display name of all approvers in one line according to initial investigation there is room for 40 characters under the release strategy tab.
Let me know if any Standarad OSS notes available for this.
Amogh

Hi amogh if you configure with workflow the strategy and the name of the persons are in transaction SU01, you don´t need to put nothing. The release strategy shows the names of the persons that release the document, but if you change one person in the release strategy, the system don´t save history for this, all old documents that have been released for this person, release strategy is blank. You have to do a non standard report that shows what person releases what document.
I hope that this information help you
Rose

Release strategy transport using BD91/ BD92 and BD93

I would like to move Characteristics/ Class and Release strategy using ALE transactions BD91/ BD92 and BD93.
The question I have is that do I run the ALE transaction from the Source enviornment( Development box) to export it toTarget box( QA)?
Or do I run it in Target box (QA) to import it from DEV box?
Thanks
Raj

Hello,
You need to setup Customer Distribution Model (BD64) and Partner Profiles in DEV (Outbound) and QA (Inbound) systems with ALE Port. Then run the transactions BD91, BD92 and BD93 in DEV. If the partner profile in DEV is setup to transfer immediately, IDOCs will be transferred to QA.
Thanks,
Venu

Class and release group and code in release strategy??

hi experts ,
Can some body explain me..
I have created Characteristics and Class for for release strategy.
But while creating release group , i should assign my class with release group , after doing this when i save , its giving error as check the release classes????
I m using the same class what i have created for my company..
So how to over come this issue
Thanks

Release Prerequisites
Definition
The release prerequisites indicate the sequence in which a purchase requisition or an external purchasing document must be approved via the release codes. The release prerequisites are defined in the Purchasing Customizing facility (in the release strategy).
The approval procedure for purchase requisitions in an enterprise may be set up in such a way that a department manager must approve a requisition item before the next level of authority (e.g. the cost center manager). In this case, approval by the department manager is a prerequisite for approval by the cost center manager.
Release Indicator
Definition
When a requisition or an external purchasing document has been processed via a release code, a release indicator is assigned to it.
When the system sets which release indicator is defined in the Customizing facility for Purchasing (in the release strategy via the release statuses).
What does the release indicator determine?
Requisitions...
External purchasing documents....
Whether the item may be changed by Purchasing or Materials Planning and Control after the start of the release procedure
Whether a new strategy is determined and whether existing releases must be cancelled in the event of changes
Whether an RFQ or a PO may be created with reference to the item
Whether the document may be changed by Purchasing after the start of the release procedure
Whether a new strategy is determined and whether existing releases must be cancelled in the event of changes
Whether the purchasing document is released for transmission
Alternative Release
Definition
Within the release sequence, you can define alternatives. This means that several employees can effect release (signify approval) at a certain point in the sequence. If just one of these employees has effected release, the next release status is reached. The other employees thus need take no action.
Five release codes are defined for purchase requisitions in an ascending hierarchy. The requisition item can be converted into either an RFQ or a PO if release has been effected either with the release codes 01, 02, 03 and 04 or - alternatively - with release code 05.
The box with the information on the release strategy also offers you the possible alternatives for selection (see Displaying Release Information).
An alternative release cannot be a prerequisite for the next release code. In the above example, the releases with codes 01, 02, 03 and 04 could not be prerequisites for release with 05.
Release w. Classification (PReqs./Ext. Pur. Docs.)
Use
The aim of this 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 requisition or other purchasing document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
This release procedure can be used to approve requisitions and the external purchasing documents RFQ, PO, contract, scheduling agreement, and service entry sheet.
Purchase requisitions are released either at item level or in total. There is no provision for item-wise release (i.e. partial approval) in the case of the external purchasing documents. The latter can only be released in their entirety.
If you set up the release procedure with classification for purchase requisitions, the procedure without classification is deactivated.
Prerequisites
The release procedure with classification must have been set up in Customizing for Purchasing. In addition, a class with characteristics must have been created for each document (requisition, purchase order, etc.).
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.
How to do this is outlined in the Implementation Guide (IMG) for Purchasing in Define Release Procedure for the relevant documents and in Set Up Release Procedure with Classification for purchase requisitions. You will find detailed information on classification in the R/3 Library in the documentation CA Characteristics and CA The Classification System.
This procedure offers a wide range of possible combinations of release criteria. Should you nevertheless have other requirements, use the enhancement provided by SAP.
Operation of Release Procedure w. Classification
The characteristic values from a requisition or external purchasing document are passed on to the classification system.
The system checks whether the values correspond with release conditions. If so, it assigns a release strategy.
The persons responsible for the release codes process the document in the sequence defined in the release strategy.

Item wise release strategy

Hi Experts,
I made item wise release strategy and used material group in class ,however when add this CEBAN-MATKL it doesn't find release strategy when remove this release strategy is working is it need to add something into material master data ?Need your advice
Thanks in advance

create release class, FRG_EBAN is available in system
create release characterisitics .. here what ever name you give, you have to make it 'reference to table CEBAN' and corresponding CEBAN field , in additional data
create a release group and attach the release class created
create release codes, and while doing it you have to specify for which release group it is valid
create release indicator , here specify the changeability
create release strategy with release codes, release prerequisites, release statuses etc
if you are transporting this, in the operational client, using CL24N assign char values for each characterisitcs of release strategy. ( you need not assign char value when that characterisitic is not present int he document e.g.if account assignment is a char, then for release strategy for document without account assignment should not have any value for that char)
if you ensure this much your release strategy should work ok

PR Overall Release Strategy Problem

Hi Expert,
I have set the following
Characterisrtic Name:
1) ZPR_Release_Plant, Char : CEBAN-WERKS (Char format : 4)
2) ZPR_Release_DOC_Type , char : CEBAN-BSART (Char format : 4)
3) ZPR_Release_Pur_Grp, Char: CEBAN_EKGRP (Char format : 3)
4) ZPR_Release_Total_Value, Char: CEBAN-GFWRT (Curr format : 15 and EUR)
I assign the above to Class : ZPR_Overall_Rel
I created Release Grp R1 and assign the class and tick "Overall Release" checkbox. There is only one class, no others in the list
I created two Release codes, F1 - Senior Finance Manager, C2, CEO
I created two purchasing group, LLL and LYL
I used the standard indicators for S - block 2 - RFQ/PO and I created two release strategies A1 and A2 for Rel grp R1.
A1 - release Code: F1, Classfication: Plant 0001, Doc Type : NB, Value : > 0.00 EUR, and Pur Grp : LLL
A2 - release Code: C2, Classfication: Plant 0001, Doc Type : NB, Value : > 0.00 EUR, and Pur Grp : LYL
The problem is when I tried to created the PR, it doesn't work at all. No trigger whether I click the "check" button at the toolbar of the PR (i.e., the release strategy tab not appearing at the header). I also tried saved and display the PR and see if the Release strategy appears at the header but still not triggering.
Can you folks advise?
Thanks
Lo

Forgot to check the box "Overall Release" forthe Nb doc Type. The problem is now solved.

PR Release Strategy-Characteristic Z_GSWRT must be linked with CEBAN-GFWRT

Dear Experts,
I did a simple config for PR Release strategy. using Plant(Z_WERKS) and Item values(Z_GSWRT )
chose overall PR Release. During simulate release
the second level release its not able to simulate and it says check Prerequistie for second level
Can somebody expain why the system is giving me this below message.
Characteristic Z_GSWRT must be linked with CEBAN-GFWRT
Message no. ME_RELCHK056
Thank you
Imraan

Thanks for the solution that helped me to understand PR Release much better.
Values: Plant (WERKS)& Itemvalue (GSWRT) & Now I created (GFWRT) For another class for Overall PR release.
In my PR Release strategy with 2 levels I have these below things:
Rel Groups : 1 Group with name AA
Rel Codes: For AA is A1, For another AA is A2.
Rel Indicator: nothing is selected, am not sure what to do in this step.
Rel Strategy : For AA is S1, For another AA is S2.
I created class Z_GFWRT but am not sure which group I should assign it AA or I have to create another new group for Overall release.
After I checked the release strategy the system is giving me this below message.
No release group exists
Message no. ME_RELCHK014
Please can you walkme through in this process. This is first time I am creating a PR Release.
Thank you Very Much
Imraan

PO release strategy for changes in price ($ and %)

Hello,
I have searched this forum and others to find an answer to my question, but as I was unsuccessful, I decided to post my question here.
I have a requirement for a PO release strategy that involves triggering the release strategy only if the total value of the PO has increased over a certain dollar amount or %. I will need to calculate the difference in the total value between the original PO and the changed PO.
Example:
Original PO total net value is $1000
PO after a price change - total net value is $1500
Total net value has increased by $500 or 50%.
Tolerance for price change is $200 or $20, so tolerance has been exceeded.
I know I will be using the total net order value (CEKKO-GNETW). I will have my tolerances in a custom table, and I will need to take the difference in the total net value from the changed PO and the original PO and check against my custom tolerance table. I also know that I will use a user defined field (CEKKO-USRC1) to indicate if the tolerance has been exceeded or not. I know that I will put this tolerance check code in the M06E0004 enhancement for changes to communication structure for release of PO.
What I don't know is where will I find the previous total net order value once the PO has been changed? Is the only place that information is stored in the change logs? If so, what is the change log table name? Or is there a different table that would contain this information?
Thanks in advance for any help you can provide.
Sincerely,
Angela

Update:
I utilized function module EXIT_SAPLEBND_002 as a solution to this. I got the old PO value from the database table EKPO, and I got the new/changed value from the I_CEKKO structure which is accessible from this FM.
I check to see if my tolerance has been exceeded. If it has, I pass a 'Y' as a tolerance flag via CEKKO-USRC1.
I originally thought about using the change document tables, but I discounted this when I discovered that those tables weren't updated at the time that the function module EXIT_SAPLEBND_002 was being hit.

Issue with retriggering Release Strategy

Hi all,
We have a one off situation here. We had already 10 release staragies in our system. We added 2 more release strategies with a new characteristic. We updated the characteristic value only for the new 2 release strategues and did not update the rest 10. Although now we had updated the characteristic value for remaiining strategies, the purchase documents created in the mean tme is not subjected to release strategy. To ensure business control we need to retrigger back the release strategy for almost 1000's of documents.
As any change to purcahsing document will retrigger it when done manually, but given the number of documents and as per Note 493900 we cannot trigger it by any backgoriund job to modify as below:
16. Question :
Why is there no release strategy determination when a program changes in
background a purchasing document which corresponds to the classification of
a release strategy ?
Answer :
This is the system design that a release strategy determination can only be
triggered through a user action and not by changes made in background
process.
If you create a document (e.g. PO, Contract, etc), the determination of the
release strategy takes place only in case of a user event like checking or
saving the document.
Kindly suggest any best practise to retrigger release strategy for the missing documents to ensure business control. Any easy and time savig measure to get it resolved will be appreciated.
Regards,
Anand Sampath

Hi Arnand,
After investigation by searching customer messages database ,I found
other customer has similar problem as the release strategy has changed
after creation of the SES please review the explanation from developer
:(whose release code is 03 )
When you try to revoke the acceptance of the service entry sheets
in ML81N or ML81, the 'Enter release code' pop up window appears, but
entering the code that is determined via the menu path Goto -> Entry
Sheet -> Release Strategy (which is the 03), the SES remains the same.
Nothing changes. The status does not vary and no error or warning
message is issued.
Checking the customizing for the release strategy, the release code
03 should have never been assigned to the SES 800024272 as the values
for the relevant characteristics were not included under that code.
I do not know how it was managed to accept the SES.
Now, when you try to revoke it, it seems that no release
strategy can be determined, not even including the values RCARESANO
and 012 between the valid values for the characteristics of the release
code 03 (RCARESANO as valid value for SUPERVISOR_SERVICIOS
(CESSR-ERNAM)and 012 as valid value for GRUPO_COMPRAS (CESSR-EKGRP)).
The only Possibility is to change now the SES so that the release
strategy can be re-determined by the system.This is the Only possible
way that the system can redetermine the Release Strategy , but it will
not be possible to do so as the SES is already accepted with the Old
strategy and it does not admit any further changes.
To be able to change it you would need to revoke the SES first,
but this Will also not be possible as the Release Strategy was changed
and the system still applies the old rules for determining the Release.
Solution to our Problem
The Only way to revoke the SES is to Restore back the Old Strategy that
was prior to 03 in the customizing.So now what will happen is that by
applying the Old Rules the System will be able to revoke the SES that#s
using the Old one. Once the necessary SES are revoked then go back to
customizing and apply the new strategy as it was did now, and
Change the SES and save , the new value of the Release Strategy will get
updated in the table ESSR and the field frgsx will now have 03.
Problems associated if the Release strategy is changed
Actually the release strategy is not supposed to be changed when there
are some documents in the System that uses it and even if you change the
Strategy the Old records will not get AUTOMATICALLY UPDATED by the
system.The Release Strategy routine has to run again to update the
values. This is Possible by changing the document SES ,
This change will happen only if the SES is not accepted and if its
accepted then you need to revoke and to revoke you need to restore the
old strategy , revoke and then change the SES , and have to go back to
customizing and Start using the New strategy from now on by doing so the
Routine will update the old record with the new strategy.
b) You may want to use CEKKO-BADAT(Requisition Date) or any other
structure in CEBAN or CEKKO and create a new release strategy
to differentiate the old release strategy.
Hope this helps,
Kind Regards,
Matthew

Precautions to be taken before going for new PR Release strategy

Dear all,
We are going to implement release strategy with classification at item level release. Current process in our company release strategy without classification at item level release was implemented and its Production for past 3 years.
Need your advice on
1)If we go for new release strategy as off with existing release strategy -what are the precautions to be taken before implementing new strategy - any problem will happen to existing data with old releases, which already release, yet to release?
2)Once after implementing the new releases, the PR with old release strategy (which is not release yet)u2026does this will trigger new release?
3)Any other which I missed out, please suggest me
Thanks
RS

Hi,
It is better to release all existing PRs using your current procedure without classificaton and clean up.
If you impliment procedure with classification, It depends on the parameters like Plant, value, purchasing group you are going to use in the strategy. Also you may decide whether to have overall req release or item level release of PR by having diffrent release groups.
REgards
Ram
Edited by: ramachandran subramanian on Feb 18, 2009 7:00 AM

CCreate Release Strategy using department name in "Release Code", not User ID SAP.

Similar Messages

Maybe you are looking for