Characteristics of Purchase requisition

Hi Gurus,
I am looking for a FM which can update the characteristics values of paritcular purchase requisition.
I found a BAPI 'BAPI_OBJCL_CHANGE' which can update the characteristic values of material, but I am not sure how this can be used for updating the characteristic values of PR.
Any help, will be greatly appreciated...
Thanks.

Vijay,
Can you give more details, what do you mean updating char values on a PR.
The Characteristics are attached to a material and not PR and for that BAPI_OBJCL_CHANGE should work.
You can skip OBJECTKEY, OBJECNUM will be the material number, OBJECTTABLE will be MARA, CLASSNUM and CLASSTYPE you should know which class this material it belongs to which you should be able to get from CT04 transaction, however you will have to get the Class key, which can be read from KALH table, if I remember it right.
What exactly are you trying to do.
Regards,
Ravi
Note - Please mark all the helpful answers

Similar Messages

Problem in purchase requisition release strategy code

Hi
We are facing a problem in purchase requisition, a new release strategy was created and change request transported but when PR is displayed in release strategy chart a same user is showed in different release strategy code.
Note: new strategy was copied from other.
Thanks in advance.

hi,
As you said tht you have copied the release stategy n created the new one...
If you do so, you would have copied the class also...to which the release group is attached...
If this is the case, then system doesn't recognise the new one, and inorder to solve it you have to define the new characteristic and class...then assign this class to the release group and make your release strategy again...
Once you do this check the release strategy at OMGSCK...and then try at PR...
You do all settings at :
SPRO >> IMG>> MM >> Purchasing >> PR >> define release strategy >> W/o classification >> here edit characteristics/class and all other link are provided...
Regards
Priyanka.P

Workflow for MM purchase Requisition steps required

Dear all,
        I am trying to configure purchase requisition Workflow.
        I am working with Work flow, WS 00000038
        I have assigned agents to TS 20000162
        Now how to proceed further, do i need to maintain some more settings
        or i should try to test system.
        Regards,
        Gaurav sood

Under the assumption that things have not changed much since 4.70, here's quick introduction:
The workflow is started only when a relevant release strategy is found, so customizing of release strategies is a very important (first) step here.
In the Implementation Guide you find the customizing in the following path:
Materials Management
-- Purchasing
-- -- Purchase Requisition
-- -- -- Release Procedure
-- -- -- -- Procedure with Classification
Only the procedures with classification are relevant if you want to use workflow to notify about requisitions waiting for release.
First you must set up a classification class if that has not already been done. Derive your characteristics from the structure CEBAN. The online help is not too bad, I had never set up classifications before and managed to get it working.
If you need data that are not available in CEBAN, or you want to modify them for the purpose of determining the release strategy there is an enhancement you can implement, and there are customer fields you can use. The enhancement definition's name is M06B0002.
As an example of what you can do, I have used it to set the company code in one of the customer fields, and to change the account assignment type. However, whether you need this enhancement or not depends strongly on what data you use to determine your release procedures (a step in customizing you will get to later).
When that is done you define release groups and release codes. Release codes are defined within each release group. Whether you should use one group or several groups is often a matter of choice.
I myself prefer using several groups even if I don't have to, so long as it doesn't lead to having to define duplicate release strategies (which you will soon get to). So, if there is some characteristic that clearly separates your release strategies, e.g. the highest amount that does NOT require release etc, you can define one group for each value (group) of this characteristic.
For instance, if some company codes require release for everything worth more than 100EUR while the default is to require release from 10.000EUR you could create to release groups. None of your release strategies will be duplicates since the value from which release is required will be different and you thus need to have that as a characteristic.
You then check that the set-up of release indicators is OK, and then you are ready to start defining the strategies. Release stragies are defined within each release group, and use one or more release codes (two or more release indicators).
It is fairly self-explanatory once you get into the screens. The thing to be observant about is to not define overlapping strategies, as this will prevent the solution from working.
When you are done, and have tested the solution in DEV it is time to transport it to the QA system. That's when I got a rather unpleasant surprise. The classification data are not transported, so both the characteristics and class, as well as the classification data in each release strategy had to be redefined. And in roughly two hours I have to do it again in production.
It is possible to transport classification information, it is described in SAP OSS Notes (different solutions for different versions).

User Exit/BADI for Purchase Order and Purchase Requisitions

HI,
I have a requireent where i have to check the the user does not enter both Subitems and Over a Limit for a Service Purchase Requisition.
Is there a User Exit or Badi that i can use where this information is availaible.
also i have to check that release strategy is assigned to every purchase order where the version has been completed.
Is there a User Exit or Badi where Information of EREV table is availaible.
Regards,
Tarun Bahal

For Purchachase requisition , the BADIs and USER EXITS are
ME_COMMITMNT_PARKING BAdI for Redefining Commitment Interface When Parking
ME_MEREQ_PARKING BAdI Purchase Requisition: "Hold"
ME_REQ_HEADER_TEXT Copy Header Text: Enjoy Purchase Requisition
try with the above BADI's
MEREQ001 Customers' Own Data in Purchase Requisition
for Purchase order , the BADIs and USER EXITS are
ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
ME_BAPI_PO_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PR_CREATE_02
ME_BSART_DET Change document type for automatically generated POs
ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
ME_CHECK_OA Check BAdI for Contracts
ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
ME_CIN_MM06EFKO Copy PO data for use by Country version India
ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
ME_COMMITMENT_RETURN Commitment for return item
ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
ME_PO_PRICING Enhancements to Price Determination: Internal
ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Customer
ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
ME_PURCHDOC_POSTED Purchasing Document Posted
ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
ME_REQ_POSTED Purchase Requisition Posted
ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
MM_DELIVERY_ADDR_SAP Determination of Delivery Address
MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
SMOD_MRFLB001 Control Items for Contract Release Order
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
LMELA002 Adopt batch no. from shipping notification when posting
LMELA010 Inbound shipping notification: Transfer item data from
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Rece
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition rel
M06B0003 Number range and document number
M06B0004 Number range and document number
M06B0005 Changes to comm. structure for overall release of requi
M06E0004 Changes to communication structure for release purch. d
M06E0005 Role determination for release of purchasing documents
ME590001 Grouping of requsitions for PO split in ME59
MEETA001 Define schedule line type (backlog, immed. req., previe
MEFLD004 Determine earliest delivery date f. check w. GR (only P
MELAB001 Gen. forecast delivery schedules: Transfer schedule imp
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MEVME001 WE default quantity calc. and over/ underdelivery toler
MM06E001 User exits for EDI inbound and outbound purchasing docu
MM06E003 Number range and document number
MM06E004 Control import data screens in purchase order
MM06E005 Customer fields in purchasing document
MM06E007 Change document for requisitions upon conversion into P
MM06E008 Monitoring of contr. target value in case of release or
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound proces
MMAL0004 ALE purchasing info record distribution: Inbound proces
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001
Regards,
Anirban

Purchase requisition create/release

Hi
I am creating purchase requisition. And i want to release this requisition.
But in my created purchase requisition there is no tab such as release strategy
And i want to keep my purchase requisition as blocked initially and later i want to release it. Can u please tell me what are the configuration or release procedure i've to do to make this happen.
I know purchase requisition can be released be me54n. But my created purchase requisition is not release relevant.
I hope u understood.
with regards
mandeep

Hi Mandeep,
For release strategy cstomising u need to go spro
Matl mgmt>Purchasing>Purchase requisition>Release procedure with classification
there u maintain, characteristics, class, create release strategy and maintain, release group, release code and indicator etc. Once u do all this then u will get the tab in PR
hope this helps
regards
Anand.c

Purchase requisition release strategy

I want each purchase requisition should be created with valid release strategy. The problem presently is that if somebody puts wrong parametes (such as purchasing group, currency) the purchase requisition will not be applicable to release and the purchase order can be easily created. So in such cases there is no need to release purchase requisition which is not correct for business point.
Pls advise.

Hi Balaji
Ur need is appreciated but inorder for that to work we have to make sure that all the possible combinations exist in ur characteristics list which may not be possible all times.
So better way would be to check whether the characteristics combinations of ur class and the corresponding data of ur requisitions matches and trigger error msg if differs.
Ex: Plant and doc type be the characteristics used in ur class.
Check whether the PR has only the plants and doc types that is specified in ur release strategy and if no trigger error msg.
Try this using BAPI also. Get help from ur ABAPer.
Thx
Raja

Release Procedure of Purchase Requisition

We are trying to configure the release strategy of purchase requisition with classification system. Following field are included in the release strategy: document type, creation indicator, requisitioner, item category, purchasing organization and total value of item; but the strategy is not effecting due to the item category field. We have verified all the remaining fields and they are working properly.
Following are the characteristics detail of the item category.
1.Multiple values checked in the Basic Data tab
2.Following values set in the Value tab
         a. blank for standard
         b. K for consignment
         c. D for services
3.Following values set in the Additional data tab
         a.CEBAN in the table name
         b.EPSTP in the field name
However, we have also verified the following table and field values in Additional data tab
1.     CEBAN table with PSTYP field
2.     MEREQ3211GRID table with EPSTP field
3.     MEREQ3211GRID_DATA table with EPSTP field
4.     MEREQ3211GRID_DATA table with PSTYP field
But none of the above is working.
It will be highly appreciated if you provide help to configure the Release Strategy of Purchase Requistion with item category.
Thanks & Best Regards
M. Rehan Qureshi

Hi Muhammad
The item category applied in PR is external one (Field: EPSTP)
In IMG ("Define external representation of Item categories"), a corresponding internal item cat are defined (Field: PSTYP).
In the comm structure CEBAN, the available field is internal item cat. is PSTYP.
Hence u need to maintain the values of internal item cat for the characterisic.
By this, you will get the desired.
warm regards
sairam akundi

Purchase Requisition release

Hi,
Could anybody help me out with the configuration settings of purchase requisition Release.
Client want to set release status for Purchase Requisition , where two persons will be responsible to release the requisition . when the first person releases the requisition , it will come to the second or final person for release ,when he releases then the requisition is released for purchase orders.
Could anybody help me out with the configuration settings.
Thanks N Regards,
Siddhartha

Use this steps. below is for PO same do it with PR. that is in place of PO take it as PR.
Releasing Procedure for Purchase Documents
Use
This setting is incorporated to just give demonstration of how SAP Release procedure works. The aim of this procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual Ctrl principle. The person responsible processes the purchasing document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
3.4.24.1     Creation of Characteristics
Procedure
1.     Access the activity using one of the following navigation options:
IMG Menu     Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Edit Characteristic
Transaction Code     CT04
2.     On the Characteristic screen, make the following entries.
3.     In put POVAL in filed Characteristic and choose Create (White paper) icon or Ctrl + F3 to begin creation of characteristic.
Field name     Description     User action and values     Note
Select Addnl Data tab
Table Name     Table Name     CEKKO
Field Name     Field Name     GNETW
Choose Enter to continue, system will give an information message saying Format Data taken from ABAP dictionary, Choose Enter again to continue.
Select Basic Data tab
Description     Description     Total net order value
Status     Status     Released
Data Type     Data type     Currency format     Selected by system
Number of characters     Number of characters     15
Decimal places     Decimal places     2
Currency     Currency     INR
Interval vals allowed     Interval values allowed     Check this tick box
Multiple Values     Multiple values allowed     Select this radio button
4.     Choose Enter to complete the entries
5.     Choose Save icon or Ctrl + S to save the characteristic.
3.4.24.2     Creation of Class
Procedure
1.     Access the activity using one of the following navigation options:
IMG Menu     Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Edit Class
Transaction Code     CL02
2.     On the Class screen, make the following entries:
Field name     Description     User action and values     Note
Class     Class     PORELPROC
Class Type     Class Type     032
Choose Create icon or white paper icon to create new class.
Description     Description     Purchase Order Release Procedure
Status     Status     Released
Choose Char. Tab to input characteristic name.
Characteristic     Characteristic     POVAL     Created in above step
3.     Choose Enter to complete the entries
4.     Choose Save icon or Ctrl + S to save the characteristic.
Result
Class type 032: Class PORELPROC created.
3.4.24.3     Configuration of Release Procedure
Procedure
1.     Access the activity using one of the following navigation options:
IMG Menu     Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Define Release Procedure for Purchase Orders
Transaction Code     SPRO
2.     On executing the transaction system will give a popup screen choose Release Groups, system will display Change View u201CRelease Groups: External Purchasing Documentu201D: Overview.
3.     Choose New Entries icon and make the following entries:
Field name     Description     User action and values     Note
Rel. Group     Release Group     02
Class     Class Name      PORELPROC     Created in above step
Description     Description     PO Release Procedure
4.     Choose Enter to complete the entries
5.     Choose Save icon or Ctrl + S to save the entries.
6.     Choose yellow arrow to go back to popup screen.
7.     Choose Release Codes to select.
8.     Choose New Entries icon and make the following entries:
Field name     Description     User action and values     Note
Grp     Release group     02     Created in above step
Code     Release Code     01
Workflow     Workflow     Leave it blank
Description     Description     Purchase Officer
Grp     Release group     02     Created in above step
Code     Release Code     02
Workflow     Workflow     Leave it blank
Description     Description     Materials Manager
9.     Choose Enter to complete the entries
10.     Choose Save icon or Ctrl + S to save the entries.
11.     Choose yellow arrow to go back to popup screen.
12.     Choose Release indicator to select.
13.     Choose New Entries icon and make the following entries:
Field name     Description     User action and values     Note
Release ind.     Release Indicator     1
Released     Released     Leave it blank
Chgable     Changeability     4
Value change %     Change of value     10%
Description     Description     Purchase Order Blocked
Go to 2nd line and input the following values:
Release ind.     Release Indicator     2
Released     Released     Select Check box
Changeable     Changeability     6
Description     Description     Purchase Order Released
14.     Choose Enter to complete the entries
15.     Choose Save icon or Ctrl + S to save the entries.
16.     Choose yellow arrow to go back to popup screen.
17.     Choose Release Strategies to select.
18.     Choose New Entries icon and make the following entries:
19.     System will give new screen New Entries: Details of Added Entries
Field name     Description     User action and values     Note
Release Group     Release group     02
Rel. Stategy     Release Strategy     S1
          Capital Items Release
Release Code     Release Code 1     01
Release Code     Release Code 2     02
20.     Choose Enter to complete the entries.
21.     Choose Release prerequisites icon and select check box 02 at the bottom and choose Enter.
22.     Choose Release statuses icon, system will give a popup screen system will default 1, 1 and 2 entries one by one as a default. Choose Continue.
23.     Choose Classification icon, here you can see Total net order value is displayed, please input >= 1.00 INR value in the white placed and choose Enter.
24.     Choose Next Screen icon or choose F8 to continue.
25.     If you want to simulate the release procedure you can choose Release Simulation icon.
26.     Choose Enter to complete the entries.
27.     To save the settings choose Save icon or Ctrl + S.
Result
Release procedure is saved.
3.4.24.4     Assignment of Values to Release Procedure
As a default all the purchase documents >= Rs. 1000000.00 is suggested in the following step of release procedure, if you want to have different one you need to change the value in the following step. If you do not want release procedure you may change the value to Zero.
Procedure
1.     Access the activity using one of the following navigation options:
IMG Menu     Cross-Application Components  Classification System  Assignments  Assign Object to Classes
Transaction Code     CL20N
2.     On the Class screen, make the following entries:
Field name     Description          User action and values     Note
Class Type     Class Type          032
Choose Enter to Assign values.
Release group     Release Group          02
Rel. Strategy     Release strategy          S1
Choose Enter.
System will give Class name in Assignments, Double choose Class Name.
System will display Characteristic name Total net order value. Assign the value >= 1000000.00 INR against filed Value.
3.     Choose Enter to complete the entries
4.     Choose Save icon or Ctrl + S to save the characteristic.
Regards
S

Can't use Overall Release for Purchase Requisitions

I have two groups, AA and ZZ. Each group has it's own Class.
Group AA uses Cost Center Class (CN) (uses Characteristics Cost Center and Line Amount)
Group ZZ uses Order Class (OC) (uses Characteristic Order)
I have built one and only one Release Strategy for each of these Groups. These Strategies both work successfully when I select the other group to be the group for Overall Release. That is, if I set ZZ to be for Overall Release, then create a requisition, the release strategy for Group AA is applied successfully. However, if I modify the req the strategy for ZZ, does not get applied.
The opposite is true. When AA is set to be for Overall release, then ZZ works. However, if I modify the req, then AA's release strategy does not get applied.
Again, both strategies work correctly when the other Group is set to be the one to use for Overall Release. However, neither strategy works if its group is set to be the one for Overall Release.
What am I missing? I only have two classes, two groups, and two release strategies.

SAP Standard system allows only 8 levels of release codes.If client requirement is more than 8 then for excess release codes customisation is done by the technical team (Abapers).Lets take an example of 15 release levels required for a client according to his Business needs then in this case initial 7 codes are customised and remaining 8 release codes are configured in the system.
Release procedure is of two types
Release Procedure without classification
             This procedure is applicable only for Purchase Requisitions.
             Here PR is released Item by Item only.
Release Procedure with classification
            This procedure is applicable to PR,RFQ,Service Entry sheet,RFQ,PO,Contract and scheduling agreements.
            Item by Item and Header level releases can be configured
            For PR - both item by item and Header level release can be configured
            For external purchasing documents - Release is possible only at Header level.
Step 1:
Create Characteristics
In this step we need to create characteristics - conditions to be satisfied for triggering Release startegy.For example client has asked to set release strategy based on 3 inputs.Combination of value, Plant and Purchasing group
            1) Total value of PR more than Rs 50,000
               create characteristic as "Release_PR_total_value" in transaction code CT04.
              Tab - Basic data " Data type --- CURR currency format", "Decimal places - eg. 2 " and "currency eg. INR or USD"
              Tab -values key in > 50000 INR
              Tab - Additional Data- Table Name "CEBAN" and Field Name "GSWRT"
              Tab - Restrictions - class type - 032 - Release strategy
            2) Plant
                 Create characteristic "Release_PR_plant" in transaction code CT04.
                 Tab - Basic data - Data type - CHAR; Number of chars - 4
                 Tab - Values - Key in all the plants for which you are required to configure release proc. eg. 1000,2000,3000
                 Tab - Additional data - Table name CEBAN and Field Name is WERKS.
            3) Purchaisng Group
                 Create characteristic "Release_PR_PurchasingGroup" in TCode CT04
                Tab - Basic data - Data Type - char, Number of chars eg. 3
                Tab - values - Key in all the purchasing Groups for which Release proc. is to be configured as required by Client.
                Tab - Addnl Data - Table Name CEKKO and field name - EKGRP
Step 2:
Define class in transaction code CL02
Menu path SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Edit classes
Here we assign all the above created Characteristics to a CLASS so that a release strategy to be triggered when all the conditions are met.
Create a new class with free choice of names as "PR_Release_proc" in transaction code CL02.*Key in the class name and select class type as 032 - RELEASE STRATEGY then click on symbol create to enter all the details as mentioned below.
Tab - Basic data - Enter description as "PR_Release-Proc",
status- Released, Same classification - check the push button - Warning Message
Tab- CHAR Enter above created 3 characteristics
1.Release_PR_total_value
2.Release_PR_plant
3.Release_PR_PurchasingGroup
step3:
Menu path is
SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>set up procedure with classification>
here define
1.Release Groups
Release group 01 is used for Purchase requisitions and 02 for Purchase orders.
Here assign class "PR_Release_proc" against release code "01"
check "OvRelPReq" indicator for over all release (All line items )of document in one shot else it will be released line item wise.
2.Release codes
Release codes are assigned to Release groups, in Workflow these release codes are tagged to users' SAP IDs through which they will be able to approve or reject a PR in SBWP(Inbox in SAP Business workplace.
PRs are released by users in transaction code ME54N.
Eg
Type of user            - Level -             Release code
PR creator - clerk or Business user -
Approver    - Supervisor                 -   R1
Approver -   Project Lead              -   R2
Approver   - Asst. Manager             - R3
Approver   - HOD/General Manager - R4
Release codes R1 to R5 are assigned to corresponding users.Manager R4 can only approve the PR if prior approvals till R3 are completed else not in ideal situation.
For detailed info please refer
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
3. Release Indicator:
Release indicators show the release status of a Purchase Requisition.
For detailed info please refer SAP Help official site
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
4.Release Pre requisites:
These define the order in which individuals or departments release the PR in sequence.
3.Release strategies
Create a new release startegy eg ."A1" or "U1" , write its description PR release for value >1 lakh
Now select release codes according to the Chart of Authority set by your client.
Eg.
Release startegy " A1 - PR release for value >1 lakh"
R1 - Supervisor
R2- Project Lead
R3- Asst. Manager
R4- General Manager
Now click on" Release Prerequisites "push button and check all the boxes in ascending order.Save the document
click on "Release statuses" push button, check release statuses then click on "Continue" push button.
In third push button you can maintain CLASSIFICATION data or later you can directly mainatain in transaction code CL20N for this strategy.
Classification data for example
1. Value - > 100000
2. Plant - 1000,2000,3000 etc
3. Purchasing groups - 101,102,103 etc
By clicking on "Release Simulation" push button you can check whether release is getting affected for configured release codes or not.
In this way you can configure all the required Release startegies.
Now create a PR in T code ME51N with the above conditions then a new tab will appear in PR creation screen at the time of check.Save the document and this can be released by respective users in TCode ME54N.
Tcode - ME54N - For Individual Release
Tcode - ME55 - For Collective Release
For detailed info please visit SAP HELP website
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
Regards,
Indranil

Creating structured texts for purchase requisitions

Hello,
I would like to know if it's possible to define structured texts for purchase requisitions. By example, the item text would be like this :
Building :
Room :
and the user should only complete the missing information.
Does anybody have an idea on how to realize this ?
Thanks in advance.

Hi,
It is not a simple thing to do.
The item text comes from the material master (if you are using one) and so you could easily have the text for that as "Building Room" and the material text can be changed (if you configure the system correctly) so they could just add the information.
But you are limited to the size of the material text and so many people just use a non-material approach and manually key in the information in the text options rather than the Item text on the requisition line on the main screen. But in this case it is not a standard option to preformat the text as you require.
It is almost as if configurable materials may help, these use the classification function and so they have characteristics, it would be easy enough to have a characteristic for room and one for building. The user would then be prompted to enter just the values for each and so it would do exactly what you need.
But I don't have enough detailed experience of configurable materials to know for sure that you could use them like this, perhaps someone who knows them well could confirm if this would work?
Whatever happens it is not a simple standard option, but SAP is very flexible and so there may be a reasonable work-around option.
Steve B

ME52N: Purchase Requisition Change GL Account Number

Requirement: ABAP auto-change the GL Account field number in a Purchase Requisition after the Material Group is changed.
Background: This custom logic has been successfully applied to all types of Purchase Requisitions using BADI ME_PROC_REQ_CUST, with the exception of a Purchase Requisition type that is called a 'Service Limits'. There are differences that are important to note between a 'Service Limits' Purchase Requisition and the other Purchase Requisitions that had custom code added without any problems.
1)This type of Purchase Requisition uses a item category of 'B', and the logic has a tendency to flow through SAP differently.
2)This type of Purchase Requisition's GL Account number is under-intensified on the 'item' subscreen, and cannot be changed manually on that screen like the others..
3)In order for the GL Account to be changed manually, or for the GL Account to be changed once my code has changed the GL Account Number, the user must select the 'Limits' tab and select the Account Assignment arrow, then a popup appears where the GL Account can be changed manually, or, my coded GL Account number change then occurs.
Problem: I want the custom code to be able to change the GL Account NUmber without having to go into thge 'Limits' tab, where the icon has to be selected. I believe the problem is that the field is protected, because it displays as under-intensified, thus, preventing my new GL Account NUmber from displaying. I also have the subsequent SAP code below that appears to reject set_exkn because protect is set to 'X'.
CODE1: Is my custom code.
CODE2: Is the SAP code that my will flow into where this field appears to be unchangeable.
My question:
I am thinking that this GL Account field is protected and cannot be changed because it is under-intensified on the subscreen on the Purchase Requisition. Can it be changed with custom code, a way to 'unprotect it'? Or, are there settings that should be changed in SPRO for the Purchase Requisition to allow this functionality to change the GL Account number.
   Thank-You
(CODE1)
METHOD IF_EX_ME_PROCESS_REQ_CUST~PROCESS_HEADER.
*Purchase Requisition Item Declarations
DATA: LT_ITEMS        TYPE MMPUR_REQUISITION_ITEMS.
DATA: LS_ITEM         TYPE MEREQ_ITEM.
FIELD-SYMBOLS: <FS_ITEM> TYPE LINE OF MMPUR_REQUISITION_ITEMS.
*Purchase Requisition Accounting Declarations.
DATA: LT_ACCT         TYPE MMPUR_ACCOUNTING_LIST.
DATA: LS_ACCT         TYPE EXKN.
DATA: LS_SETX          TYPE MEPOACCOUNTING_DATAX.
FIELD-SYMBOLS: <FS_ACCT> TYPE LINE OF MMPUR_ACCOUNTING_LIST.
CALL METHOD IM_HEADER->GET_ITEMS
    RECEIVING
      RE_ITEMS = LT_ITEMS.
LOOP AT LT_ITEMS ASSIGNING <FS_ITEM>.
    LS_ITEM = <FS_ITEM>-ITEM->GET_DATA( ).
    LT_ACCT = <FS_ITEM>-ITEM->IF_ACCT_CONTAINER_MM~GET_ITEMS( ).
    LOOP AT LT_ACCT ASSIGNING <FS_ACCT>.
      LS_ACCT = <FS_ACCT>-MODEL->GET_EXKN( ).
      LS_ACCT-SAKTO = 'N500300   '.
      LS_SETX-SAKTO = 'X'.
      <FS_ACCT>-MODEL->SET_EXKN( LS_ACCT ).
      <FS_ACCT>-MODEL->SET_EXKNX( LS_SETX ).
    ENDLOOP.
ENDLOOP.
ENDMETHOD.
(CODE2)
METHOD if_accounting_model_mm~set_exkn.
DATA: ls_buffer     LIKE LINE OF my_data_input_buffer,
        ls_bufferx    LIKE LINE OF my_data_input_bufferx,
        l_buffered    TYPE sy-subrc,
        l_data_old    TYPE exkn,
        l_data_oldx   TYPE mepoaccounting_datax,
        l_data_newx   TYPE mepoaccounting_datax,
        l_indx        TYPE sy-tabix.      "1478013
*PROTECT EQ 'X'
CHECK my_state->protect EQ mmpur_no.
Edited by: Tom Matys on Dec 12, 2011 10:55 AM

Your PO release strategy must have been based on Cost Center as one of characteristics.
Pl check & confirm.
Regards
Bhavesh Mistry

Issue with Purchase Requisition Release strategy

Hi Gurus,
We are using ECC 6.0.For the approvals of purchase requisitions, we are using standard SAP functionality of release procedure. There were some 52 release strategies configured for the PR .The release strategy was based on value of the following fields that is below were characteristics grouped together for class for PR:
1.     Creation Indicator of PR-R (Configured only for manually created PRs)
2.     Purchasing Group
3.     Value of the PR
As a result of PM module implementation, there is requirement of additional 30 release strategies.
We configured them but one more field of doc type was added in the characteristics fields.
Now the release strategy was based upon following fields:
1.     Creation Indicator of PR-R (Configured only for manually created PRs)
2.     Purchasing Group-(Configured against new purchasing groups )
3.     Value of the PR
4.     Document type of purchase requisitions.
Classification data was accordingly maintained that is for older release strategies,
Old PR doc. Type: NB was maintained where as other values were same. For new release strategies, new PR document types:NB1-NB6 for Doc type have been maintained .
The above set up worked fine for some time. But suddenly, none of the PR release strategies are working. I checked all the related configuration settings and all look fine. I also checked my release strategies in tcode: OMGQCK. But no error was there.
Could any body help in finding the reason why PR release strategy stopped working all of a sudden? What could be the probable reasons? What should be the approach to resolve it?
We are in testing phase. Many of the test scripts failed due to this issue.
Quick response will be appreciated!!!
Thanks & Regards,
Niti

Dear Niti,
Please check if your "overall release" indicator is consistent for document type and release group:
a)SPRO:MM-PUR-PR-Define Document Type
"overall release" indicator
b)SPRO: MM-PUR-PR-Release Procedure-Set Up Procedure with Classification
->Release group
"overall release" indicator
Regards,
ian,Wong Loke Foong

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 !

Purchase Requisition Release Strategy help

SAP Gurus,
I have set up PR release strategies for item level and it is not working. Our setup is as follows:
Document type NB with "Overall release of purchase requisitions" unchecked
3 characteristics defined: one for Line item total, cost center, and an account assignment category.
1 class with all three characteristics assigned
1 Release group with "Overall release of purchase requisitions" unchecked
104 different release codes
127 different release strategies with varying combinations of cost centers and dollar amounts.
Executed cl24n with all release strategies.
Now when i enter a PR with amounts and cost centers that should trigger the release strategy, it is not triggering.
I executed CL30N with different parameters and none of them register.
The only clue i have as to what could be wrong is when running OMGQCK, it lists that the release group does not exist, but it does. Message 620401/2006 references note 365604 lists the problem i am experiencing, but none of the suggested steps have corrected the problem.
I would appreciate any suggestions anyone has on what i can try to get this release strategy working
Thanks,
Rachel

hi,
Check your release codes and its assignments in the release strategy..
Also do check whether the PR is liable to trigger for the given characteristics as compared to your PR which you are making...
Regards
Priyanka.P

Purchase Requisition Release strategy for MRP based Requisition

Hello Gurus
We want to set up the urchase Requisition Release strategy for MRP based Requisition ..Any can one Please share your experience about the impact down the road?
Thanks
Nick

Hi,
If you want include the MRP related PR in Release strategy.
You need to include the field CEBANESTKZ-Creation Indicator (Purchase Requisition/Schedule Lines) in one of the characteristics which you create and include the characteristics value as per the field values like AReal time, BMRP, CConverted Planned order etc.. and include the charactristic in the Release Strategy will release group & release codes.
So when ever the PR is created through MRP run then this creation indicator will update in the PR as per that release Strategy will trigger in the PR.
there is one more option you need to create the separate document type as MRP PR then create document type as characteristics and include the values of all these document types and include in Release strategy.
But it will not pop up for direct PR from MRP run only trigger when planned order is converted to PR manually there you need to select this MRP document type then release strategy will trigger.
I think first one is best suited.
rgds
Chidanand

Characteristics of Purchase requisition

Similar Messages

Maybe you are looking for