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
9848993644

Release 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.

Similar Messages

  • 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.
    sachin

    Hi 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

  • 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.

  • Release procedure with out classification

    HI, AJIT SINGH HERE,
    after making proper settings in the 'release procedure with out classification', when i try to create a puchase requisation by ME51N to test the working of release procedure ,i'm not getting check boxes of approval levels.
    please guide

    hi
    did u took the pur grp as the chrecteristic for release
    if yes then put the value of pur grp in release strategy
    plz check ur release strategy as per follows
    http://www.sap123.com/showthread.php?t=59
    http://www.sapstudymaterials.com/search/label/0270-MM%20Configuration%3A%20PR%20Release%20Strategy%E2%80%93Basic%20Concept
    regards
    kunal

  • 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
    Sajid

    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 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
    Kawal

    hi,
    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 without Classification

    Hi Experts,
    i have create a release strategy for the release procedure without classification, which PR document type i use for this? NB?
    Do i need to assign a PR document to this release procedure?
    Thanks

    Hi Chun,
    You can not use one release strategy with classification and one more without classification at a time in the system. Only one will work.
    For your case, already you have Overall release, and I suggest you go for second class with Itemwise release. With classification, it's possible to use two release strategies at a time based on the document type. ("Overall Release " check box for document type)
    Umakanth

  • 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
    Siddhartha

    Hii,
    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

  • 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

  • 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

  • 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

  • Release Procedure with materia No. as characterstic.

    hi SAPERS,
    I am trying to put Release procedure for P.R. by keeping Material No, Plant, Purchase Group as characterstics.
    When I assign the Plant, Purchase Group charactersic to Class the Release Procedure is working fine.
    By instanct I assign the Material No. charactersic to same class the Release Proocedure is not working.
    Please explain me where i did mitake? Can we add the Materia No as characterstic in Release Procedure, If no what are all the reasons.
    Thanks in Advance.
    Venkat.

    Hi
    It advisable not to add material number as a release characteristics for PO wheras for PR you can add it ..the job of the release characteristics is  to to find the data in the purchasing document and apply the appropriate release stategy to it .this is done through communication structures .CEBAN is the communication structure for PR and CEKKO for PO.
    note: if u add material no as a release characteristics u need to add each and every material number created into the class for your release strategy and release group through t code cl20n.
    Regards
    Sandeep

  • 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 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.

  • Release Procedure in PR .....

    Hi SAP Gurus,
    We do release procedure in PR with Account assignment category K.Here ,for collective release in pr (ME55),check box is disabled... Kindly help me how we enable the check box.We use scope of list as "F".All customization for release procedure is correct.
    Thnks & Regards
    SAP MM User

    You use this component if you wish to set up approval procedures for purchase requisitions or other purchasing documents. Under such a procedure, if a purchase requisition or external purchasing document fulfills certain conditions (e.g. the total order value exceeds $10,000), it has to be approved (by the cost center manager, for instance) before it can be processed further. This process of approving (clearing, or giving the "green light" to) a proposed item of expenditure is replicated in the SAP System by the "release procedure".
    It is sensible to define separate release procedures for different groups of materials for which different departments are responsible, and to define separate procedures for investment goods and consumption goods.
    Features
    Each person involved in the release procedure effects release (signifies approval) via a release transaction, using his or her release code. Once effected, a release can also be cancelled with the same code (that is to say, the original status is reinstated).
    If linkage to  SAP Business Workflow has been defined for a release code, rejection is also possible. This is only possible for purchase requisitions.
    Which Documents Can be Released (Approved)?
    Release procedures can be defined for the following documents:
    Purchase Requisition
    The external purchasing documents purchase order (PO), contract, scheduling agreement, request for quotation (RFQ), and service entry sheet
    Release Procedure for Purchase Requisitions
    Two different procedures are available for requisitions:
    With classification
    With this procedure, requisitions can be released both at item level (i.e. item-by-item) and in total. The latter approach is also termed "overall release".
    Without classification
    With this procedure, requisitions can only be released at item level.
    The two procedures are mutually exclusive (that is to say, you must decide in favor of one of them only - you cannot use both).
    Release Procedure for External Purchasing Documents
    External purchasing documents (i.e. purchasing documents other than requisitions) are released at header level. Item-by-item release is not possible. These documents can only be released using the release procedure with classification.
    sri

Maybe you are looking for