RCCLBI01 and Purchase Requisition Release Strategies

I'm trying to use RCCLBI01 to load Release Strategies. I've found a few threads on it but they don't tell you what you can and can't do with it. I know I can load the characteristic values for an already existing Release Strategy, but I have hundreds of Release Strategies that I need to create.
Will this load the strategies as well, or do I really have to go create them by hand in SPRO first then run it? Or is there another program that will load strategies and the codes and the characteristics?

Kris,
RCCLDI01 is now used. However Here's my view:
1. You will have to create chracteristics to begin with. I hope the number is not huge as it will narrow down the functionality otherwise.
2. The class-- How many would you create?? I don't believe you would need a Batch input program to create a class as I believe there could not be more than a handful, unless necessary
3.Now the classification.. the buggest task of all, where you could run in to hundreds.. Maintaining them is a nightmare and you'd have to have your strategies first.. I do not know of any input program to create Release strategies. So my answer is "a manual task"
4. RCCLBI02 is of no help here for release strategies.
5. I would rather use TCODE: CLMM to do the mass changes.. it makes life a lot easier.
6. The last option is for some one technical to help you create a script to load the data.

Similar Messages

Release approval procedure and purchase requisition

Hello gurus,
just now I discovered a strange behaviour (in my view) in one of our client's system:
There is a release strategy for certain purchase requisitions. When I create one of those, the release strategy is applied and the Requisition Processing State is set to "In release" automatically.
But now comes the strange part: I can create a PO and copy that same purchase requisition item into it and save the PO! I.e. I can order the item, even though there was no prior release of the purchase requisition.
Unfortunately I cannot try myself right now, but this is not standard behaviour, or is it? Where is the sense in having a release strategy when the item can be ordered anyway, even without release?
Thanks in advance
Alicia

Hi Alicia,
Go to transaction OLME -> Purchase Requisition -> Release Procedure
-> Procedure with Classification -> Set Up Procedure with
Classification -> press button 'RELEASE INDICATOR', make
'double click' in your last release indicator and check if the flag
'REL.FOR ORDENING' is set or not.
Go to transaction OLME -> Environment Data -> Define Attributes of
System Messages, and see if you have defined the message
06 055 as warning or error?
Please check additionally if you have in EBAN (for the requisition) the fields FRGKZ, FRGZU, FRGST filled with entries.
Also deactivate your user exits and check the behaviour again (see note 365604).
Regards,
Edit

Are these requisition release strategies common?

All,
I’m designing new requisition release strategies for indirect requisitions at a chemical industry client. I’d like to know how often you have seen the following sorts of design before:
Existing design: Item-based release with workflow, with three dollar levels. At the lowest levels, two strategies for each cost center approver (the one used is based on whether the desired vendor is foreign or domestic). Characteristics assign several cost centers to each approver. Strategies and codes are named for users, so we change configuration whenever someone changes jobs. The codes are linked to positions, which are attached to user IDs. Result: about 80 release codes and 140 strategies, taking a lot of time to maintain.
Current redesign: Overall release, using 6 strategies and 6 codes based on dollar level and foreign vs. domestic. A user exit selects the approver for each code from a custom table that stores the user IDs for each cost center, with a custom maintenance transaction for the table.
Now the client wants both individual approval by cost center owner and items with different cost centers on a single requisition combined with approval of the overall purchase. I’m considering item-based approval of requisitions, with the user exit and custom table, and adding overall approval of indirect POs with the overall approvers.
Thanks for your help!

Hi,
No-Requisition release strategies are not common, one need to design release strategies based on business requirement. Release strategies looks simple after designing but its design needs creating thought to it.
In your case, you can go for designing redesigning release strategies for Overall release with using 6 strategies and 6 release codes. Considering you have configured release strategies with all release values for PO document type ,PO value and Purchasing group. Now design a custom table and go for followings:
Client---Pur Group--Rel Code1-- Rel Code2-- Rel Code3-- Rel Code4-- Rel Code5-- Rel Code6
The search help is required to pull in purchasing group details from T024 table and SAP user ID from Table USR01
Concept: Create Purchasing Group (OME4) as Department & assign the Department name to Cost center (KS01).
For more refer a discussion:
PR release: place holder for Cost center and Material grp
NOTE: User training required crate requisition for one department only where only one cost center involved- No requisition creation allowed for multiple cost center.
You can also go for other concept designing of your Requisition release strategies
Regards,
Biju K

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

Questions on Rules-Based ATP and Purchase Requisitions for STOs

Hello experts,
We are working on rules-based ATP configuration and have several questions about the functionality. Iu2019m hoping that some of you are using this functionality and can help give us direction.
In our environment we have multiple distribution centers and multiple manufacturing plants. We want to confirm sales orders against stock and production orders in any of those plants, depending on the locations that have stock or planned production. For example, we will place a sales order against plant A. If there is not enough stock in plant A then rules-based ATP will use location determination to check in plant B, then C. The scope of check on the ATP check will include stock and released production orders. We will configure plant A as the u201Cconsolidation locationu201D so if stock is found in plants B or C then stock transport orders will automatically be created to move the stock to plant A before shipping to the customer.
We have configured rules-based ATP and this functionality is working well in our Development system. The ATP check is executed and uses the rules-based ATP to find eligible stock in other plants. The system is also creating purchase requisitions to move the stock to the consolidation plant.
Our first concern is that there doesnu2019t appear to be any firm linkage between the sales order and the resulting purchase requisition. For example, if we create sales order 123 for plant A and the rules-based ATP finds stock in plant B it automatically creates a purchase requisition 987 to move the stock from plant B to plant A. However, there doesnu2019t appear to be a linkage between sales order 123 and purchase requisition 987. For instance, if we delete sales order 123 the purchase requisition doesnu2019t get deleted.
Our second concern is that the quantity on the purchase requisition can still be confirmed against later sales orders. For example, say the above scenario resulted in a purchase requisition 987 that consumed all the stock available in plant B. We then create a second sales order 456 for the same product. Plant A is out of stock so the rules-based ATP looks in plant B. We would expect that plant B would also not have any stock because itu2019s all been consumed by the purchase requisition. Instead, the system creates a second purchase requisition to move quantity from plant B to plant A. Itu2019s as if the system doesnu2019t realize that the purchase requisition 987 is already planning to move stock out of plant B.
Does anyone have any thoughts or suggestions on these two scenarios? Is there a way to configure the system so there is a hard linkage between the sales order and the purchase requisition so that if the sales order is deleted then the purchase requisition is also deleted? Should ATP realize that purchase orders are consuming inventory and not allow later sales orders to confirm against that same inventory? Any advice or experience would be greatly appreciated.
Thanks,
David Eady
Application Delivery Team Lead
Propex, Inc.

Hi,
The scheduling is done in SCM, and from there, whenever the RBA is triggered, the calculation is done always with the old route in SCM. Until you get back to R/3 this is when your route is determined. But the ATP check is always with the original route. So the idea would be that you change the values of the route while still in APO, this is possible via the user exit. Should be done in scheduling in APO.
Hope this information is helpful.
Regards,
Tibor

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 release strategy tab missing

Hi all
I configured purchase requisition release strategy and ME51N is working issuing no error but it is not displaying Release Strategy Tab , please help me where i am wrong.

hi,
check few reasons:
1. There might be more than 1 release strategy using the same class, due to which it is not possible for sap system to determine the unique rel. strategy..this normally happens when you copy the exsisting class and assign it to own new one...
2. check the release strategy OMGSCK, is there any problem with your release strategy...
3. Check whether you have maintained all the classified field in the document or not..
4. check whether the release is assigned to any workflow...if so, then check the inbox pls...
regards
Priyanka.P

Purchase Requisition Release Procedure Modification

Hi
In Purchase Requisition Release, we have two deviations in business requirement from standard SAP behaviour:
1. In multistep release, system allows PR release to be revoked by a lower level release authorized person even though higher level release has been done. Example, PR Release has release codes A1, A2 and A3, A2 can revoke release even after A3 has released the same. How do I prevent this from happening?
2. If business requirement is to have release procedure based on item cost per unit and not on total value of the line item, how can this be achieved?
Appreciate any guidance on these issues
Thanks
Sriram

Hi,
There is BADI ME_REQ_POSTED
in method POSTED you can write your code to trigger the workflow and get the information related to release strategy and
Purchase requisation .
for more than one PR use below logic .
LOOP at im_eban into gwa_im_eban .
    concatenate gwa_im_eban-banfn gwa_im_eban-bnfpo into gwa_objkey .
add data into container -----------------
      gwa_event_container-element = 'PurchaseRequisition'.
    gwa_event_container-value = gwa_im_eban-banfn.
    append gwa_event_container to gi_event_container.
    clear: gwa_event_container.
    gwa_event_container-element = 'ItemOfRequisition'.
    gwa_event_container-value = gwa_im_eban-bnfpo.
    append gwa_event_container to gi_event_container.
get the other details and create event to start workflow .
select single * from eban into lwa_eban where banfn = gwa_im_eban-banfn
                                              and bnfpo = gwa_im_eban-bnfpo .
        if sy-subrc <> 0 .
      call function 'SWE_EVENT_CREATE'
        exporting
          objtype           = 'BUS2009'
          objkey            = gwa_objkey
          event             = 'zcreated'
        tables
          event_container   = gi_event_container
        exceptions
          objtype_not_found = 1
          others            = 2.
ENDLOOP .
Hope this will resolve your issue.
Thanks and Regards,
Deepanker Dwivedi

WS2000077 (Purchase Requisition Release) problem

Dear all
workflow task WS2000077 (Purchase Requisition Release) causes the following problem:
While executing an approval release (ME54N) through workflow, the result is always 'requisition release refused'.
Does anyone know why?
I appreciate your help in advance

Hi,
Go through the below links it may help you...
Workflow Definition WS20000077 and sequence of the events, significantly...
po release workflow issue/problem
PR Workflow problem
std workflow ; user to role agent assignment ?
Regards,
Udaya.

Release code - Purchase requisition - Release Procedure

Hello,
In the purchase requisition release procedure with classification, we are defining release codes say K, P etc.
My doubt is , Is this being defined else where based upon the designatin of the person in the organisation, or else, we are defining here straight away?
Best regards,
K.Kumaran.

HI
You are correct, you need to define the release code there only. There is no other place where it is defined. What you have to ensure is make sure that it is of Two character and not single. Assign the codes against the designation of the person as per your requirement.
Regards

User Exit for me54n on purchase Requisition Release i.e EXIT_SAPLMEREQ_05

HI   All Experts ,
                      I have one Requirement that , i want to insert data in Ztable using all details from header data in me54n on purchase release i.e When i will Click on Purchase release Requisition i want to insert records using few fields such as , matnr ,menge , item, quantity ,requisioner,plant storage locaton , date etc . i am using user exit on this i.e smod EXIT_SAPLMEREQ_005 in mereq001 which is called when clicked on purchase requisition release , now how to collect that details in this user exit .
need some help regarding this .
Thanks And Regards
Deepak Dhamat

Dear Peter ,
               yes you are correct that ebeln is part of structure MEREQ_ITEM but it is always empty .i want Purchase Requisition no i.e     PR. Manual           2000009940 which is present in me54n first line of screen i.e above the header note .
after looking at the property of that field it show as given
below
Struct.          MEREQ_TOPLINE
Field name       BANFN_EXT
Data element     BANFN
DE supplement    0
Parameter ID     BAN
Screen field     MEREQ_TOPLINE-BANFN_EXT
Program name     SAPLMEGUI
Screen no.       0014

Purchase Requisition Release at Header Level

Hi MM experts,
We are on ERP6. Can we activate purchase requisition release at header level (ie overall requisition dollar level - sum total of all requisition line items) just for one business (company code) without affecting rest of client which uses release strategy at requisition line item level?
Is it possible to share the same document type, e.g. NB that is used by other business?
Many thanks.
Thomas

With the release procedure with out classification , it is possible to release the PR at header level based on the value of the PR . In determination of release strategy , you can maintain the value , currency and release stratergy .
But to restrict this to a particular comany code , you may use the exit M06B0002 where in you can write the logic .
-Hari.

Workflow for purchase requisition release strategy

Hi all,
I need an urgent help on Workflow for Purchase Requisition Release. The requirement is that when a purchase requisition with a given combination (Purchasing Group, Material Group and Account Assignment Category) is created and saved, it should trigger a workflow for approval of release or rejection to one specific business manager. If he dont responds in 2 days, it should be sent to other business manager. If any one of them releases the requisition, it should send a mail to the requestor that the requisition is released. And if it is rejected, then also a mail to be sent to the requester informing that his requisition is rejected...
Can anyone take some pain and guide me step by step procedure to implement this or to use any existing one.... I know its BUS2009 thats used in this but really dont know how to implement it properly.
Its urgent...
Edited by: Hima on Apr 11, 2008 12:45 PM

Check this link
http://help.sap.com/saphelp_47x200/helpdata/en/04/92762546f311d189470000e829fbbd/frameset.htm
Thanks
Arghadip

Badi for Purchase Requisition Release Strategy

Can any help me to know about the BADI for Purchase Requisition Release Strategy .Is their any BADI to control the PO Price for a PR release strategy
Thanks for your help

This badi is for schedule agreement ?
BAdI: Release Creation for Scheduling Agreements with Release Documentation
Use
You can use this Business Add-In (BAdI) to influence release creation.
This BAdI is used in the application component Scheduling Agreements (MM-PUR-OA-SCH).
This BAdI includes the following methods:
Change Data Before Release Creation (BEFORE_CREATION)
Change Data After Release Creation (AFTER_CREATION)
This BAdI is called during manual and automatic release creation.

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 !

RCCLBI01 and Purchase Requisition Release Strategies

Similar Messages

Maybe you are looking for