Retriggering Release strategy for PR with Document Type, Company Code and Price Range as Characaterstics

Hi Friends,
I have a issue to fix. The issue is releated to PR.
There are some PR's in the system which has wrong release strategy picked up or wrong approvers picked up due to some congif change. now that the config changes are rectified correctly, we need to find a solution to correct the PR's which got affected due this.
I have to retrigger the release strategy for all the affected PR's.
The characterstics which we have consider for release strategy is Document Type, Company Code and Price Range.
Can anyone suggest how can we retrigger the PR in bulk or individual to all the affected PR's, so that it picks up correct release strategy as per new config changes.
Regards,
Manjunath K

Hi,
Refer the discussion to triggers release again on release code addition/change in release strategy.
release code is changed on PR release strategy - old PR can´t be approved
Regards,
Biju K

Similar Messages

Add release strategy in the PO document type

Dear all,
I create one PO Return but there is no release strategy in ME28, what should I do to add the release strategy for that PO doc type.
Thanks
Pauline

Pauline,
I would suggest you to please post this query in ERP MM forum to get it answered asap.
Regards,
Faisal

Release Strategy for a new material type in PR

Dear Friends,
One of our client require new Release Strategy for a particulat material type PR. Can u pl provide me the steps to configure a new release strategy for PR for a particular Material type.
Regards,
Ask

Hi,
Create a Char for your material types in CT04(MARA-Table,Field-MTART) and assign the same to your Class in CT02.
Then follow all the cusmozation path for your PR release startegy .
For Config part refer the below wiki link it may help you.
http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE
http://wiki.sdn.sap.com/wiki/display/ERPLO/ReleaseprocedureforPurchaseRequisitioninMM?focusedCommentId=195723808#comment-195723808

Release strategy for PR with multiple item category

Hello,
I'm trying to create a global release strategy for a PR based on the item category. I have defined a caracteristic with different item categories (A and K).
If I create a PR with item category A, the correct strategy is triggered as well as for an PR with item category K. The problem is when I create a PR with 2 positions, one A and one K, there is no strategy triggered.
How can I change my settings that there is also a strategy triggered in this case ?
Thank you in advance for you help.
Kind regards

Hi,
Solution is very small. Please maintain a blank entry too in the characteristics value. It will start working.
Sanjeev

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 in purchase order document type

Hi Gurus..
I'm tring to tweak the single RS in the system.
I've set the charcteristic using table CEKKO field BSART, restriction 032, I've set two document types as the Characteristic Value (ZLOG - ZADM). Then I´ve set the class with this characteristic, Created Release Groups & linked to class , Created Release Codes, Release Indicator, and Set up strategies
.. but It doesn´t pick any release strategy.
The funny thing is if I delete the document types values entered in CL20N it works for all doc typs, but if I set the docs types that it should take to pick the RS it doesn't work at all...
Please advice..

I´m not such a abapper but I guess there is not values taken to ekko, does it ring a bell?
                                        BUKRS
                                        BSTYP
                                        BSART
                                        BSAKZ
                                        LIFNR
                                        SPRAS
                                        EKORG
                                        EKGRP
                                        WAERS
                                        BEDAT                                             00000000
                                        LLIEF
                                        KUNNR
                                        RESWK
                                        LBLIF
                                        INCO1
                                        KTWRT                                             0.00
                                        LIFRE
                                        WERKS
                                        MATKL
                                        LTSNR
                                        USRC1
                                        USRC2
                                        USRN1                                             0000000000
                                        USRN2                                             0000000000
                                        GNETW                                             0.00
                                        SUBMI
                                        MEMORY
                                        KONNR
                                        REVNO
                                        PDUMMY
                                        KDATB                                             00000000
                                        KDATE                                             00000000
                                        EBELN

Issue in Release strategy for PO while adding intermediate rel code/Strateg

Hi Experts,
we have Existing release code 10,20,30,40,50 & 60. Now, we tried to add an intermediate Release Code(say 25) & release strategy(say R3) in existing release set up for PO.
And NO pre-requisite is defined ; final release by the last rel code.
However, the system shows release possible by 30 & 40 for last release strategy also. It`s showing the alternate release as release possible.
Pls throw some light on resolving the issue....
Regards,
Ganesh S....

Thanks Ajit.
I mean the release should get afftected only after release 60. (i.e. final approver) That`s the way it`s been working.
Now, while I tried adding 1 more rel code in between ; it`s afftecting the release with (20+40) instead of the intended 60.
BR,
Ganesh

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

Release Strategy for Contract is not getting picked whereas it is ok for PO

Dear Experts,
I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
Kindly resolve the issue.
Satish

S0004830404 wrote:
Dear Experts,
>
> I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
> I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
>
> Kindly resolve the issue.
>
> Satish
hi,
use create other characteristic for value CEKKO-GNETW in this use the mk , wk values in value field and assign this characteristic to your class and save.
Thanking you

PR Release Strategy for DOCUMENT TYPE

Hi Gurus,
I have created a Document Type in PR & I want to set a Release Startegy for ONLY that Document Type.
Can anybody explain me step by setp procedure for this ?, I have gone thru one link :
http://www.sap123.com/showthread.php?t=59
but I could not set the relase startegy. May be I am missing something ??
Thanks & Regards,
Vikas

If you want to define the release strategy only for doc type
then
create the class using CL02
create the chra for Doc type using CT04 - the table is CEBAN and the field is BSART
then assign the doc type value in char (after you create the char then go back and assign the value)
now assign your char to your class
now go to SPRO and goto PR release strategy config - procedure with classification
go to Set Up Procedure with Classification
create your release group by assigning the calss you have created (make sure this config should have only one class)
create release code
release indicator is already exist in sap so you don;t need to create
create your release strategy and assign the value in classification tab of release strategy
this will work
but make sure that - if you are creating only for doc type means all the reqs created for this doc type will be blocked by the system. so if you have reqs like if this doc type and the amount >5000 then only block then you have to have amount is also you char in your class
hope this will give you a cleat idea

Release Strategy for Condition Records

Hi,
This is a requirement from my client. The client needs to give 4 levels of release strategy for the condition records created. The selling price for the products will be entered by person 1. This has to be approved by the sales execute (person 2); then by the sales manager (person 3); finally by the General Manager (Person 4). The selling price of the products ranges from 10 lakhs to 40 lakhs. so, the release strategy is needed. This type of release strategy is available in MM for PR and PO. Please let me know whether similar facility is available in SD. Any alternative is also solicited.
Regards,
K Bharathi

Hi,
Thanks for your valuable reply.
I defined 3 Processing status (Menu path: SPRO >> SD >> Basic Fn >> Pricing >> Define Processing status). They are EU-End user, KU-Key user, MD-Final authority. These processing statuses are assigned to Release status. First two processing status EU, KU were assigned to A (Blocked). The third processing status MD was assigned to Blank (Released). The purpose is: at processing status EU one person will upload the price master. Second person will check the price and will change the processing status to KU if he satisfies with the accuracy of the price master. The third person (final authority) will check the price and set the Processing status MD. Once the condition record gets the status MD, the prices can be used for creating sales order because it is released.
In the condition record for PR00, when I enterthe processing status EU or KU the release status shows 'Blocked' release statuses. When I enter MD in the processing status, the release status show 'released'.
My question is how can assign the responsibilities of changing the processing statuses EU to KU, KU to MD to two different persons.
Regards,
K Bharathi

Release strategy for RFQ

Hi,
Please let me know,how to set release strategy for rfq.. i'VE ACTIVATED MY RELEASE STRATEGY FOR po USING TABLE cekko... iF I WANT TO ACTIVATE RELEASE STRATEGY FOR rfq... WHICH TABLE AND FIELD NAME I WANT TO USE... PLS EXPLAIN..

For RFQ also we can use the same communication structure CEKKO, but for differentiation between release startegy of Contrcats Purchase orders & RFQ's better to use the Charcteristic Document category i.e CEKKO - BSTYP - Purchasing Document Category

How to calculate no.of records for a specific company Code and Transaction

Hi All,
Could you please help me how to calculate or count no.of records, in a table which are having a specific Company Code and Transaction Code and populate in an output table displaying that these many records are present for this company code and Transaction code.
The table is having the data like this:
LOB   TRAN CODE    COUNT
X1                             1
X1                              2
X1                              3
X1                              4
F1   NB                      5
F1   NB                     6
F1   NB                     7
F1   NB                    8
F1   NB                    9
F1   NB                    10
F1   NB                    11
F1   NB                    12
F1   NB                     13
F1   NB                     14
F1   NB                     15
F1   NB                     16
F1   NB                     17
F1   NB                     18
F1   NB                    19
F1   NB                    20
F1   NB                   21
F1   NB                   22
F1   NB                   23
F1                          24
F1                         25
F1                         26
F1                         27
    In the above table there are totally 27 records,where as the no.of records with F1 as company code and NB as transaction code are 18..so i have to display like F1 NB and 18 as one record as output.
Thanks and Regards,
Johny

You can go for Control Breaks for your requirement.
First sort the internal table by company code and transaction. Declare a counter variable.
Now loop the internal table and increment the counter variable. within the loop use AT END OF tcode.......ENDAT. Within the control break append the counter variable as well as the company code and tcode to some other ITAB and clear the counter.
This will give you the total number of records for a combination of co code and tcodes.
This will be a good reference for your requirement. What I am doing here is, for each Vendor i am calculating total number of deliveries and amounts for that vendor. For every new vendor i am writing the ouput on to a list and clearing the counter variables.
LOOP AT t_vend_prod_grp INTO fs_vend_prod_grp.
    w_total_delv = w_total_delv + 1.
    w_total_amt = w_total_amt + fs_vend_prod_grp-dmbtr.
    AT NEW matkl.
      w_mat_grp = fs_vend_prod_grp-matkl.
* To display the material group and the header texts for the data
* grouped by material group and vendor.
      SKIP 1.
      WRITE: text-mtk COLOR COL_HEADING
                              INTENSIFIED,
            / w_mat_grp COLOR COL_NORMAL
                              INTENSIFIED OFF.
      SKIP 1.
      FORMAT COLOR COL_HEADING ON INTENSIFIED.
      ULINE 1(54).
      WRITE:/ sy-vline,
            2 text-ven,
           12 sy-vline,
              text-dlv,
           26 sy-vline,
           38 text-amt,
              sy-vline,
           46 text-cur,
           54 sy-vline.
      ULINE /1(54).
      FORMAT COLOR COL_HEADING OFF INTENSIFIED.
    ENDAT.                             " AT NEW MATKL
    AT END OF lifnr.
* To display the actual data for the grouping based on Material group
* and Vendor.
      FORMAT COLOR COL_NORMAL ON INTENSIFIED OFF.
      WRITE: / sy-vline,
             2 fs_vend_prod_grp-lifnr COLOR COL_KEY,
            12 sy-vline,
               w_total_delv,
            26 sy-vline,
               w_total_amt CURRENCY text-usd,
               sy-vline,
            46 text-usd,
            54 sy-vline.
      FORMAT COLOR COL_NORMAL OFF INTENSIFIED OFF.
      CLEAR: w_total_amt,
             w_total_delv.
    ENDAT.                             " AT END OF LIFNR
ENDLOOP.                             " LOOP AT T_VEND_PROD_GRP

Release strategy for purchase requization on basis of document type

Hi All
can somebody can explain me the procedure for creating releasing strategy on basis of doc type
Nabil

Hi,
The below link will help you to understand the process.
Please open the below link and u will get the complete process to have the Release stretegy on the basis of Doc. Type.
http://www.sap-img.com/materials/release-procedure-for-purchase-requisitions.htm

Problem with document type on WF for parking document

Hello
Iu2019m actually working on the SAP workflow dealing with the FIPP object and the event u201Ccreatedu201D (FI park document transaction (FV60)).
The problem is that the WF is launched for all document types wich is not the need of the customer. Iu2019m looking for a solution to launch the WF for some specific document types.
Iu2019ve already tried to use the workflow variant, approval groups, paths and procedure with no success. (SPRO -> financial accouting-> accounts receivable and accounts payable -> business transaction -> incoming credit invoice memo -> make and check setting for document parking)
Thank you for help.
SL

Here is the solution I have eventually found :
1- Application of the OSS note 559276 which enables the customizing of the workflow variant (the transaction OBWD becomes here effective)
2- Assignment of the documents types, workflow variants and release approval groups with the transaction OBWD.
Therefore, the document types that are not defined in the transaction OBWD will not require validation (no workflow will be launched).
SL

Retriggering Release strategy for PR with Document Type, Company Code and Price Range as Characaterstics

Similar Messages

Maybe you are looking for