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

Similar Messages

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

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

Purchase order release strategy report

Dear Gurus,
We are using purchase order release strategy with classification.
We have 3-4 level of release. We want to develop a report where we will come to know at which level purchase order is pending for release .
How to get it ?
Please provide ur help for the same
Rgds,
Saurabh

Hi,
Basically in EKKO table there is a field name FRGZU -
Release status based on that we can write a logic take the report.
for example A1,B2,C3 ARE THREE release codes in that if A1 released means with check thable whether A1 released once it is release it will go to next release code it iwll check the status again inthe loop....
Just tell him the logic to ABAP person they will develop
Rehgards
Murugan J

Issue: Purchase order release strategy with storage loaction.

Hi Friends,
I have created release strategy for purchase order considering following characteristics.
1. Plant
2. Purchase organization
3. Purchase group
4. Document type
Hence the release strategy is working fine.
Now the requirement is changed, PO approves should be picked depending on the storage location wise. So i tried to create characteristic for storage location with table name CEKKO and with field LGORT. However system not allowing to create, telling that field LGORT not found in table CEKKO.
Can any one tell me how to maintain this LGORT filed in structure CEKKO.
Thanks in advance
Shashidhar

HI Shashi ,
Thanks for your quick response,
I have Appended a structure to Standard Structure CEKKO with Field LGOBE.
Also we written the code :move: i_cekko = e_cekko, in user User-Exit M06E0004 function exit
FUNCTION EXIT_SAPLEBND_002.
However, the release strategy is not triggering when PO is saved,
also the user-exit is not getting triggered , even though i have included the statement ' Break-Point'
in it.
Kindly reply.
Thanks ,
Shashidhar

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

Purchase Order not subject to release strategy

Good day everyone!
I've created one release strategy for all my purchasing documents. The characteristic is net value, and the value of this characteristic is >=0.00. Meaning, ALL purchase orders are subject to release strategy.
After I did the release strategy in SPRO, I created a few PO and when I tried to release them, I got this message: "Purchasing document 45xxxxxxxx not subject to release strategy".
My question is: How to assign purchasing document to release strategy?
Please help. Thank you in advance.
Anisah

hi
yes you have to use table CEKKO for PO release strategy , now , in PO you can't create without clasification so it will be applicabe for whole PO not for line items ,
now below i am giving u one by one steps , follow and let me know .
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   0
                        1
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
ravikant dewangan

Purchase Order not subject to release strategy for contract rel. strategy

Hello, I am trying to set release strategy for contracts (TCODE: ME31K). I have created characteristic, which use table CEKKO and field name BSTYP in Addnl data tab. I have checked values, and they are correct. Then I have assigned in release strategies in classification view value contract. But when I try to check release strategy in ME31K with green flag, it display error: Purchase Order not subject to release strategy. (I have tried to do the same strategy in purchase order, of course with value Purchase order, and it works nice).
So I have checked this release strategy with this codes:
CL24N ok,
CT04 ok,
CL30N ok,
CL20N ok,
Release simulation in release strategy works,
Then I found out that I should check SE38, SE37 but I do not understand how to use them (according: Purchasing Document Not Subject to Release Strategy).
Thank you for your help in advance.

I haven't said to use EKPO table in characteristics. You have to use CEKKO - BSTYP in characteristics.
I've just said the compare the value which you have given in Release strategy - Classification and EKPO table for the particular contract.
Also compare your release strategy settings with many existing documents in SCN.
Check your Classification should be like that.
You may see the error message in ME31K. Just save the contract then go to ME32K/ME33K or ME35K you can see the release strategy will effect for the contract.

Purchase Order Release Strategy with Dependency Condition

Hi
We have a scenario where we have to set up Purchase Order Release based on a combination of the following
Vendor + Purch Org + Dollar Value.
We have successfully set up the release strategy for which we have done the following
1) Create Characterstics for Vendor, Purch Org and Net Order Value
2) Assign the above characterstics to a Class
3) Assign Class to the Release Strategy in SPRO.
So far everything is good.
Now we try to define a Condition. With a Fourth Characterstic (TRIG_RELEASE ) attached to the same class.
And attached a Dependency condition to it.
$SELF.TRIG_RELEASE = 'Y' IF VENDOR = '1000' and PURC_ORG ='8500' and NET_VALUE > 1000.
When this dependency is set, the release doesnt trigger.
but modifying the condition to
$SELF.TRIG_RELEASE = 'Y' IF VENDOR = '1000' and PURC_ORG ='8500' .
Trigger the Release for that condition.
How can we base the dependency on Net Value also ? What are we doing wrong or missing ?
Regards
Aju Paul

Hi Paul,
I'm not sure why you really need that fourth characteristics. In my opinion, the three characteristics are good enough to achieve the desired release strategy. Why don't you just create a strategy that has those specifc characteristics value in your classification.
You can do that from SPRO or CL24N.
Define a new strategy in SPRO e.g "Vendor 1000 Porg 8500 > 1000"
In CL24N, enter the class name; e.g Z_PO_RELEASE.
class type 032
Hit the enter key for existing release strategies to be displayed. Select the one you one just created above. Then click on detail and your characteristics/Value is displayed below.
Then maintain the different values for the charateristics and then test with PO creation
Xtic                  Value
Vendor                1000
P.Org                  8500
Value                  > 1000

Purchase order release strategy with a characteristic value as a variable

Hi all,
We have Purchase order release strategy based on the following characteristics:
Total Net Order Value
Purchasing Organization
a few other custom fields
We would like to add a characteristic based on the creator of the PO. In the purchasing department there are two person which have the authorization to create an release POs. The goal is now to check if the actual user, who release the PO, is different from the PO creator. The value of this characteristic may not be a fix value, it must be contain the name of the actual user name.
Is there are a possibility to insert the characteristic value as a variable such as SY-UNAME instead a fix value?
Thanks,
Charles

this is verymuch possible. You can use unsed fields user1, user2 etc in CEKKO or (ii) insert a new field in CEKKOZZ and use the new field. You need to build up logic in user-exit such that this field will take the value of person who had logged in. This can be done by ABAPer.
Hope this resolves ur problem

Table name for release strategy

Hi
In which place i need to take table name for purchase requisition and purchase order release strategy configurartion,plz suggest
Regards
Sam

HI
While defining characteristics you required table name in po & pr

Subcontract purchase order release strategy

Iu2019m trying to customize a release strategy for subcontract purchase order (SC) but PO document is not taking any release strategy.
Now Iu2019m not sure about SAP standard allows to have a release strategy for subcontract purchase orders (SC)?
Thanks for your help.

Hi,
1. Please check this link (it is for PR but I think might be useful):
http://www.sap123.com/showthread.php?t=59
2. Remark: You can use user exit EXIT_SAPLEBND_002, M06E0004 if you want to make your release startegy sensitive for item category - however this was not question.
3. On additonal data tab of the characteristics (assigned to the class), can you see table CEKKO and its field name in the suitable fileds? (CT04)
4. Does your strategy work for other purchase orders (with other document types)?
5. Please check classification settings under your release startegy, whether the values defiend there are in harmony with the values defined in the subcon-PO (I mean purch doc. category, purchasing group, order type, plant). SPRO > MM > Purchasing > PO > Release procedure for POs > Define Release Procedure for POs - here choose release strategies...
Regards,
Csaba

Release strategy for Purchase order

Hi Friends,
My client was using Release strategy for purchase order. Now we want to know the T-code for showing list of Rejected Purchase orders, T-code for for showing list of approved purchase orders, T-code for showing list of blocked purchase order.
Thanks and regards
Krishna

HI,
You can go to SE16N view table name EKKO
FRGKE   Release ind. = B
FRGZU   Release status = <blank>
mean, this PO yet to approve/ rejected.
FRGKE   Release ind. = R
FRGZU   Release status = X
means, this PO has been approved.
Hope this helps

What is the name of the table where Release Strategy changes are maintained

Dear Friends,
Every time I make the changes in the Release Strategy Codes the Signature of the Approver changes in the Output. The problem is that it even changes for the Older PO's which are already approved by some other approver. Is there any way this problem can be sorted out? or can any one give the name of the table which records the changes made in the Release Strategy along with time and date? I will be really thankful if you guys can help me out!

Hi Chintan,
I hope you are talking about the release codes, which we attach later on to user Ids and signature means its description. I hope followed correctly.
In standard system, as and when you change the description of release code at back end, it gets reflected on front end. No matter whether its old or new PO. There is no way out to stop this. Every time you display the purchase order, the release codes checks for description at back end and displayes the same. Still, it should not bother you, as the already released PO dosent get affected for any changes you do at back end in the entire release strategy.
Beside the tables mentioned by other friends AUSP is the table where all release related entries gets stored.
I hope it clarifies.
Regards
sachin

PO Release Strategy not triggerred for particular Total Net Order Value

Dear,
I am currently facing the issue where release strategy for purchase orders is not getting triggered for a particular value or lower.
For order value 1 INR or less, no release strategy is triggered for new created PO. And for value > 1 INR release strategy is getting triggered.
All otehr PO characterstics are the same, I mean to say the values for other characterstics such as plant material group are identical.
But the characterstics for release for Total net order value are <= 30000 INR. There are two system copies, where in one system the same release strategy is working as expected. But in other system the above mentioned issue occurs. There is no differnce which I can see in the release strategy setup.
Please suggest for solution.
Thank you.
Warm Regards.

Dear All,
While looking further into the issue by going into debugging mode, we have found that in include LCLSCF2I, Internal table p_selection_criteria_tab , the value for ATFLV (Internal Floating point from) gets different values in the two systems. For example, in the affected system, for PO with 1INR tottal value, for one of the Total value chaaracterstics before INR characterstic, ATFLV value is 0,0000000000000000E+00, hence it gets out of loop and doesn't trigger release strategy.
But in another system for same PO values and release setup, ATFLV value is 1,0000000000000000E+00 for that characterstic.
May I know how the value for this field gets calculated.
Thank you.
Warm Regards.

PO release strategy- order of names

Similar Messages

Maybe you are looking for