Problem in rel.strategy

I created two doc. Type for P.R. i.e- zno1, zno2. I have one user i.d- MMCONS. For releasing P.R Document (ZNO1) we have rel code-01 & for releasing P.R Document (ZNO2) WE HAVE REL. CODE -02.WE HAVE CREATED CHARACTERSTICS FOR DOCUMENT TYPE, PLANT & USER I.D. Is it possible to give authorization in one user i.d. to release the different doc. type P.R in a single user I.D.waiting for your early response.
nrk

Hi
Try with assigning release code 01 and 02 to same user in authorization
Vishal...

Similar Messages

Problem in release strategy in a plant PO. Strategy does not appear

Hi:
I have a problem with release strategy in plant PO. When we create a PO in this plant, we have no tab for release strategy, if I change the plant in PO for a different one I get this tab with all data.
I have checked OMGS, CL20N and everything seems to be in order. I think this is a problem in plant definition, but I really donu2019t know where I can look for. This plant is a copy of an existing one, and in this plant there is no problem.
Please, any idea?
Thank you very much in advance.

you can test if one or more strategies can be found. (you should one find one, otherwise SAP is not able to determine which one should be used)
go to CL30N.
Enter your class and class type 032, hit enter
Enter values for the characteristics. and click button for a search in initial class.
I dont think it has something todo with plant customizing. Classification just takes the values that are in your PO and searches for a strategy which has to be in table T16FS.

Po rel. strategy

Hi,
In p.o rel. strategy we have the three stage release status. First A( say) will rel. then B then C. we have released lot of p.o in the same manner. Now we want to change the rel.status to two step. That means A will release then B will rel.the document as the final rel. authority. But in the previous P.O created which was subject to three stage rel. status has been already reduced to two stage. Where is the setting so that it will not effect the old p.o rel. strategy procedure.

Hi,
For this you have to create two release strategies as given below:
1. For old PO's
Add a new characterstic (Say DOCUMENT_DATE) to the old 3 level release strategy having value as before today's date (i.e. <13.06.2011 ).
2. For new PO's
Add a new characterstic (Say DOCUMENT_DATE) to the new 2 level release strategy having value as on & after today's date (i.e. >= 13.06.2011). Rest all the characteristics will be same as the old 3 level release rstrategy.
The characterstic DOCUMENT_DATE will have Table name as CEKKO & Field name as BEDAT (i.e. PO creation date).
So, For Example if you will go for making any changes to PO created before today's date will pick the same old 3 level strategy however for creation or changes to PO's having creation date today onwards will pick the new 2 level release strategy.

Rel.strategy

Dear cons
We have created one user I.D (procurement) for creation of purchase requisition. One person is only able to approve the document. We have created another I.D for finance deptt. For thr Pur. Doc.we want both person can approve the document. i.e- first fi ance deptt. Will approve then procurement deptt. Will approve. Because at the time of creation P.R the purchase deptt. Enters a wrong G/L account. To avoid this first it will come to finance deptt. So how can you make settings in the release strategy. If I create two release code & enter in the rel. strategy of procurement I.d Then How it will come to finance i.d. pl.look into the matter. Without workflow it is possible or not.. Basis people has restricted the user i.d.pl. give some hints.

Hi Nirupama,
Create the 2 release codes for that Release strategy.First release code should be for Finance dept 2nd should be pur dept user.
Give the authorization to 2 user ids with release codes one for Finance dept and another for Pur dept with the help of Basis Consultant.
Once the Pur dept user creates the Pur requisition.In the PR release tab the 2 release codes will appear . Then the first release code should be Finance dept user. Then final release can be Pur dept user.
So that before releasing the PR the finance dept user will correct the G/L account and then release the PR. Then the Pur dept user will finally release the PR for procurement.
Hope you understand
rgds
Chidanand

PR Rel Strategy scenario

Hello
I have 2 requirements in PR Rel Strategy scenario.
1.No changes should be allowed in the PR once the PO is created.Can we fulfill this requirement by assigning changeability Indicator 1.
2.Once the PR is released and PO created it should not allow to revoke the release.
Any ideas on this?
Regards
Vaibhav Mahajan

Hello Afshad and Swaminathan
Users are revoking the release after the PO is created.With changeability indicator no changes are possible via ME52N but revoke is possible in ME54N.
Bases on the links given by Afshad I am checking if we can use the User Exit but not sure which user exit will work.
Regards
Thanks for the suggestions.

New release strategy should not trgger for PO released with old Rel Strategy

Hi All,
Please suggest. Po has been fully released with Release Strtgy V1 XX. Now I m replacing release strategy XX with ZZ. If I change any po which has old rel str XX , system will reset new release strategy as in config changeability indicator 4 maintained.
But requirement is if there is any change or value decreasing in fully released Pos with old strategy it should not retrigger new release strategy. If value Increases then New strategy should retrigger.
Please help me on this.
regards,
Rohit

HI Rohit
A reset of the release strategy only takes place if
       - the changeability of the release indicator is set to '4' in
          case of a purchase requisition and '4' or '6' in case of
          another purchasing document (purchase order, request for
          quotation, contract, scheduling agreement),
       - the document is still subject to the previous release
          strategy,
       - the new TOTAL NET ORDER VALUE is higher than the old one.
The most important thing to consider in to avoid changes to release strategy customizing once the release strategy is used.
The commom steps are:
1- make sure all of the old POs should have been released.
2- don't delete/change the original release strategy. create a new release strategy with copy function, then the old release strategy will not be replaced.
3- if you delete the original release strategy and add a new release strategy which the characteristics in classification is same as old release strategy then the PO (have been approved) will be replaced with the new release strategy.
Kind regards,
Lorraine

Problems in planning strategy 20

Hi Experts,
My scenario is I am using Planning strategy 20 (Make To Order).
In Planning strategy 20, Purchase requisition & Planned Order is generated after MRP for RM, SFG & FG respectively.
But the problem is that RM is already in stock & I dont want Purchase requisition for Raw material after MRP run & system should consider this stock against the Sales order.
If I will get this solution, my query will resolve.
Please help me as my client is demanding.
Waiting for your reply
Thanks & Regards,
Uttam Pal

If you want plant stock to be considered for RM, then maintain Indiv/Coll indicator as 2. Then the demand & supply will be plant segment.
But if you want the demand for the RM to be in sales order segment & yet net off against plant stock, it will not happen. You will have to transfer the plant stock to sales order stock, then system will net supply & demand.
Hope the above clarifies.

Contract rel strategy

Gurus,
I have congfig Con rel stg.I rel it.Then i go & change the qty & value.The sys prompts a msg,rel liable to be rest.But when i go try to rel again,the sytem says no suitable documents found.

hi,
check for the release strategy set up options ie, under release indicator settings...
here set the changability option and for fine tuning changebility % value for your release ID....
You can use option 4 or 6 depending whether you want to see relevent changes with regards to output or not...
Regards
Priyanka.P

Problem withn Release strategy having Multiple release codes

Hi
I am working on a Release Strategy which has 2 Release codes say 01 and 02.
The PR document can be released only when 01 and 02 both releases.
But suprisingly, the first code 01 is able to release the 02 code also.
How to remove this problem.
Kindly relpy ASAP !!
Cheers
MaruthiRam

Hi,
This can be controlled through authorisation.Ask your Basis team to assign the Release code and release group in authorisation object "M_EINK_FRG" .Here give only the release code applicable to the concerned user only and remove the other release code .
Also please check if you have mantained the release prerequisite in img.That is for release code 02 the release pre requisite must be 01.Check the required boxaccordingly.
Dhruba

Rel. strategy is not triggered while creation of PR with cost centr

Hi Gurus,
While creation of PR release strategy is not getting triggered with cost centre BCWSV870. But release strategy of PR triggered for cost centre BCWSV852 (In PR changed only cost centre as BCWSV852 instead of BCWSV870). Both cost centres are similar and the both cost centres are exist in characteristics value in CL20N for the same release strategy.
My question is why for one cost centre triggers release strategy triggers and for other cost centre release strategy is not triggered. Can you please tell how come this and rewarded for answer this.
With regards,
C. Sundar Rajan

Hi,
In regard to problematic PR with cost center BCWSV870, was your PR maintained with only one line item? or multiple line items?. In additions, when defining cost center as part of the release strategy structure, did you enter all cost centers with leading zeros? Tak a further look into OSS Note 365604 for your further investigation.
Cheers,
HT

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.

Performance problem with relatively simple query

Hi, I've a statement that takes over 20s. It should take 3s or less. The statistics are up te date so I created an explain plan and tkprof. However, I don't see the problem. Maybe somebody can help me with this?
explain plan
SQL Statement which produced this data:
select * from table(dbms_xplan.display)
PLAN_TABLE_OUTPUT
| Id | Operation               | Name              | Rows | Bytes |TempSpc| Cost |
|   0 | SELECT STATEMENT        |                    | 16718 |   669K|       | 22254 |
|   1 | SORT UNIQUE            |                    | 16718 |   669K|    26M| 22254 |
|   2 |   FILTER                |                    |       |       |       |       |
|* 3 |    HASH JOIN            |                    |   507K|    19M|       | 9139 |
|   4 |     TABLE ACCESS FULL   | PLATE              | 16718 |   212K|       |    19 |
|* 5 |     HASH JOIN           |                    |   507K|    13M| 6760K| 8683 |
|* 6 |      HASH JOIN          |                    |   216K| 4223K|       | 1873 |
|* 7 |       TABLE ACCESS FULL | SDG_USER           | 1007 | 6042 |       |     5 |
|* 8 |       HASH JOIN         |                    |   844K|    11M|       | 1840 |
|* 9 |        TABLE ACCESS FULL| SDG                | 3931 | 23586 |       |     8 |
| 10 |        TABLE ACCESS FULL| SAMPLE             |   864K| 6757K|       | 1767 |
|* 11 |      TABLE ACCESS FULL | ALIQUOT            | 2031K|    15M|       | 5645 |
| 12 |    INDEX UNIQUE SCAN    | PK_OPERATOR_GROUP |     1 |     5 |       |       |
| 13 |    INDEX UNIQUE SCAN    | PK_OPERATOR_GROUP |     1 |     5 |       |       |
| 14 |    INDEX UNIQUE SCAN    | PK_OPERATOR_GROUP |     1 |     5 |       |       |
| 15 |    INDEX UNIQUE SCAN    | PK_OPERATOR_GROUP |     1 |     5 |       |       |
Predicate Information (identified by operation id):
   3 - access("SYS_ALIAS_2"."PLATE_ID"="SYS_ALIAS_1"."PLATE_ID")
   5 - access("SYS_ALIAS_3"."SAMPLE_ID"="SYS_ALIAS_2"."SAMPLE_ID")
   6 - access("SYS_ALIAS_4"."SDG_ID"="SDG_USER"."SDG_ID")
   7 - filter("SDG_USER"."U_CLIENT_TYPE"='QC')
   8 - access("SYS_ALIAS_4"."SDG_ID"="SYS_ALIAS_3"."SDG_ID")
   9 - filter("SYS_ALIAS_4"."STATUS"='C' OR "SYS_ALIAS_4"."STATUS"='P' OR "SYS_ALIA
              S_4"."STATUS"='V')
11 - filter("SYS_ALIAS_2"."PLATE_ID" IS NOT NULL)
Note: cpu costing is off
tkprof
TKPROF: Release 9.2.0.1.0 - Production on Mon Sep 22 11:09:37 2008
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Trace file: d:\oracle\admin\nautp\udump\nautp_ora_5708.trc
Sort options: default
count    = number of times OCI procedure was executed
cpu      = cpu time in seconds executing
elapsed = elapsed time in seconds executing
disk     = number of physical reads of buffers from disk
query    = number of buffers gotten for consistent read
current = number of buffers gotten in current mode (usually for update)
rows     = number of rows processed by the fetch or execute call
alter session set sql_trace true
call     count       cpu    elapsed       disk      query    current        rows
Parse        0      0.00       0.00          0          0          0           0
Execute      1      0.00       0.00          0          0          0           0
Fetch        0      0.00       0.00          0          0          0           0
total        1      0.00       0.00          0          0          0           0
Misses in library cache during parse: 0
Misses in library cache during execute: 1
Optimizer goal: CHOOSE
Parsing user id: 61
SELECT distinct p.name
FROM lims_sys.sdg sd, lims_sys.sdg_user sdu, lims_sys.sample sa, lims_sys.aliquot a, lims_sys.plate p
WHERE sd.sdg_id = sdu.sdg_id
AND sd.sdg_id = sa.sdg_id
AND sa.sample_id = a.sample_id
AND a.plate_id = p.plate_id
AND sd.status IN ('V','P','C')
AND sdu.u_client_type = 'QC'
call     count       cpu    elapsed       disk      query    current        rows
Parse        1      0.09       0.09          0          3          0           0
Execute      1      0.00       0.00          0          0          0           0
Fetch        1      7.67      24.63      66191      78732          0         500
total        3      7.76      24.72      66191      78735          0         500
Misses in library cache during parse: 1
Optimizer goal: CHOOSE
Parsing user id: 61
Rows     Row Source Operation
    500 SORT UNIQUE
520358   FILTER
520358    HASH JOIN
16757     TABLE ACCESS FULL PLATE
520358     HASH JOIN
196632      HASH JOIN
   2402       TABLE ACCESS FULL SDG_USER
834055       HASH JOIN
   3931        TABLE ACCESS FULL SDG
864985        TABLE ACCESS FULL SAMPLE
2037373      TABLE ACCESS FULL ALIQUOT
      0    INDEX UNIQUE SCAN PK_OPERATOR_GROUP (object id 33865)
      0    INDEX UNIQUE SCAN PK_OPERATOR_GROUP (object id 33865)
      0    INDEX UNIQUE SCAN PK_OPERATOR_GROUP (object id 33865)
      0    INDEX UNIQUE SCAN PK_OPERATOR_GROUP (object id 33865)
select 'x'
from
dual
call     count       cpu    elapsed       disk      query    current        rows
Parse        1      0.00       0.00          0          0          0           0
Execute      1      0.00       0.00          0          0          0           0
Fetch        1      0.00       0.00          0          3          0           1
total        3      0.00       0.00          0          3          0           1
Misses in library cache during parse: 1
Optimizer goal: CHOOSE
Parsing user id: 61
Rows     Row Source Operation
      1 TABLE ACCESS FULL DUAL
begin :id := sys.dbms_transaction.local_transaction_id; end;
call     count       cpu    elapsed       disk      query    current        rows
Parse        1      0.00       0.00          0          0          0           0
Execute      1      0.00       0.00          0         12          0           1
Fetch        0      0.00       0.00          0          0          0           0
total        2      0.00       0.00          0         12          0           1
Misses in library cache during parse: 1
Optimizer goal: CHOOSE
Parsing user id: 61
OVERALL TOTALS FOR ALL NON-RECURSIVE STATEMENTS
call     count       cpu    elapsed       disk      query    current        rows
Parse        3      0.09       0.09          0          3          0           0
Execute      4      0.00       0.00          0         12          0           1
Fetch        2      7.67      24.63      66191      78735          0         501
total        9      7.76      24.72      66191      78750          0         502
Misses in library cache during parse: 3
Misses in library cache during execute: 1
OVERALL TOTALS FOR ALL RECURSIVE STATEMENTS
call     count       cpu    elapsed       disk      query    current        rows
Parse       48      0.00       0.00          0          0          0           0
Execute     54      0.00       0.01          0          0          0           0
Fetch       65      0.00       0.00          0        157          0          58
total      167      0.00       0.01          0        157          0          58
Misses in library cache during parse: 16
    4 user SQL statements in session.
   48 internal SQL statements in session.
   52 SQL statements in session.
Trace file: d:\oracle\admin\nautp\udump\nautp_ora_5708.trc
Trace file compatibility: 9.00.01
Sort options: default
       1 session in tracefile.
       4 user SQL statements in trace file.
      48 internal SQL statements in trace file.
      52 SQL statements in trace file.
      20 unique SQL statements in trace file.
     500 lines in trace file.Edited by: RZ on Sep 22, 2008 2:27 AM

A few notes:
1. You seem to have either a VPD policy active or you're using views that add some more predicates to the query, according to the plan posted (the access on the PK_OPERATOR_GROUP index). Could this make any difference?
2. The estimates of the optimizer are really very accurate - actually astonishing - compared to the tkprof output, so the optimizer seems to have a very good picture of the cardinalities and therefore the plan should be reasonable.
3. Did you gather index statistics as well (using COMPUTE STATISTICS when creating the index or "cascade=>true" option) when gathering the statistics? I assume you're on 9i, not 10g according to the plan and tkprof output.
4. Looking at the amount of data that needs to be processed it is unlikely that this query takes only 3 seconds, the 20 seconds seems to be OK.
If you are sure that for a similar amount of underlying data the query took only 3 seconds in the past it would be very useful if you - by any chance - have an execution plan at hand of that "3 seconds" execution.
One thing that I could imagine is that due to the monthly data growth that you've mentioned one or more of the tables have exceeded the "2% of the buffer cache" threshold and therefore are no longer treated as "small tables" in the buffer cache. This could explain that you now have more physical reads than in the past and therefore the query takes longer to execute than before.
I think that this query could only be executed in 3 seconds if it is somewhere using a predicate that is more selective and could benefit from an indexed access path.
Regards,
Randolf
Oracle related stuff blog:
http://oracle-randolf.blogspot.com/
SQLTools++ for Oracle (Open source Oracle GUI for Windows):
http://www.sqltools-plusplus.org:7676/
http://sourceforge.net/projects/sqlt-pp/

Release strategy:ME53N : Older PR documents shows, modified PR rel.strategy

Hi Friends
We have updated the sequence of release codes for certain PR release strategies. But when we moved the changes production, i observe that all the older PR documents (Which were released last year and completed) also shows the updated release strategy in transaction ME52N/ME53N.
Can someone pls some explain? Is this normal?
SAP doesnt store the release strategy and its sequence of release codes, which were determined at the time of document creation?
Thanks for your help...Raj

Hi,
There is no change in the older documents.
The documents are older by few years.
I have checked few documents randomly, the tcode ME53N shows only the updated release strategy.
I did some investigation today on this.
i think system will not keep the release strategy pertaining to document creation.
It will just store Release Group and Release strategy in the Purchase Requisition tables (like EBAN).
And when ever we try to display the document it will go and read the release strategy sequence from relevant tables.
Hope someone helps to validate if my investigation is correct.
Good day..

Rel strategy for PR

I want to create Release Strategy for PR as follows:
For Standard PR (NB) one level of release is always required.
(eg HOD will have to release all the PRs of a department)
How shall I proceed pleae guide in detail.
regards
VS

Hi,
Release Process for PR is as below
1 Create the Characteristics for your release strategy based on fields of table CEBAN.
2 Create a class of class type 032. You have a free choice of names for the new class
3. Assign your characteristics to the class on the tab page Characteristics.
4. Create Release Groups
5. Create Release Code -HOD in your case
6. Create Release indicator -all type of PR or selective
7. Define Release prerequisites
Hope you will explore after this overview on RS.
Regards,
Ashish

PR rel strategy

I want to create Release Strategy for PR as follows:
For Standard PR (NB) one level of release is always required.
(eg HOD will have to release all the PRs of a department)
How shall I proceed pleae guide in detail.
regards
VS

Hi
I have created a release procedure for PR by maintaining 4 levels. Have made all the necessary conf. in SPRO & then trying to release the PR in ME54N. But iam unable to release it as iam getting an error
Pr No1 can't be released & Msg # MEPO822.
pls. i neeed a solution for this.
shouldn't i select 4 levels to approve a standard PR
Vineeth

Problem in rel.strategy

Similar Messages

Maybe you are looking for