Materials available only for Purchase requisition creation

Hi Experts,
My client wants some materials available only for Purchase requisition creation and some materials donu2019t want available only for Purchase requisition creation.
How we can control
Thanks in advance,
Chandhu

1) Solve your issue first you have to bifurcate between the materials where requisition is possible & where not...u can do this by selecting some field which is not in use presently in material master-basic data view & maintain some unique value for those materials for which PR will be not possible....otherwise check whether you can bifurcate it through material groups or not...
After this take help of your ABAP person and implement BAdI::ME_PROCESS_REQ_CUST...here use the logic that after user enters the material code in PR system will check in the background what has been maintained in the said field in the basic data view of the material...if found blank then it will allow the user process further or if found any data in that field then system will stop the user from processing the same by throwing some customized error message.
2) Use the Plant-sp.matl status in purchasing view as Blocked for procment/whse for those material against which you don't want to create any PR.But this will be plant specific and both PR & PO will get blocked.
Regards,
Indranil

Similar Messages

USer Exit/BADI for Purchase requisition creation in MDBT or WC27 /MRP Run

I am looking for an enhancement where a purchase req is created during MRP Run in the background ( MDBT or WC27 or program - RMMRP000 .
Any suggestions would be welcome.

Hi,
try the exits:
LMDR2001 User exits restr. profiles of opt. pur.ord.
LMDZU001 User exits in additional planning
Regards,
Renjith Michael.

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

Error code 083 on LSMW - Purchase Requisition creation

Hii all,
I have generated a bapi program for purchase Requisition creation.
the followings are the programe details:
Business Object
BUS2105
Method
CREATEFROMDATA1
Message Type
PREQCR1
Basic Type
PREQCR101
I have divided the structures into 3 sections:HEADER,ITEM DETAIL,ACCOUNT ASSIGNMENT.In the account assignment group at the "Maintain Field Mapping and Conversion Rules" (E1BPMEREQACCOUNT), wbs element field marked as "move".
At the "E1BPMEREQACCOUNTX" the wbs field was mared as "X".
the programm can read the feild & displays the WBS element that it can read from the datafile.
the problem is that during the stage of " Create IDoc Overview"
it provides the following error:
Enter WBS Element
Message no. ME083.
I have checked the WBS element& nothing is wrong with it.
any one can help me out on this?
thanks
M S

Hi Jurgen,
Thanks for replying.
1. For BAPI, at step 14. when i execute, it is a warning message
No Data could be selected
2. yes, I have activated the IDOC Settings.
Please suggest.
Thanks,
Sahil

Purchase Requisition Creation From Release

Dear PM Gurus,
For Manual material availability Check to work before release, the Purchase Requisition check is to be set to Immediately in SPRO-> Define Change Docs and Collective PR or Activating Pr from Now On from Maintenance Order. The issue is that I want to restrict the creation of Purchase Requisition to Release of Maintenance Order but what is happening is upon saving the Maintenance Order, the PRs for all non stock materials are created and I also want the manual availability check to work before release.
Simplifying above details:
I want Manual material availability check to work and PR generation from release both in my Maintenance Order to work..
Regards..

Hi DP Singh,
I had seen the configuration settings that you are telling me but you see the Problem is:
If in Define Change Docs, Collective Purc. Req. Indicator, Operation No. Interval, you define the Res/PReq Indicator as Immediately, then the Manual Material Availability Check would work accurately but upon saving the Order, System would generate the Purchase Requisition.
and If in Define Change Docs, Collective Purc. Req. Indicator, Operation No. Interval, you define the Res/Preq Indicator as From Release, then the Manual Material Availability Check would not work as no material is as such MRP relevant till the time of releasing the Order but the Purchase Requisition would be created only when the Order is released.
Now What I want is both the Manual Availability Check to work and Purchase Requisition Creation From Release, but this is not possible according to the Standard SAP System. A workaround could be that I configure the automatic material availability upon release and configure the Res/Preq indicator as From Release, that way the material availability would be checked when the order is released and Purchase Requisitions would also be created from Release but still the Manual Availability Check would not work.
The Ideal Solution should have been configuring the Res/Purchase Requisition Indicator for all Non Stock Materials to be From Release and the Res/ Purchase Requisition Indicator for all Stock Materials to be Immediately. This way your manual availability Check would work for all Stock Materials and Purchase Requisition for all Non Stock materials would only be created upon Release. But this But still this is an ideal solution not the actual solution for standard SAP does not give you the flexibility to do such a setting in customizing or using Enhancement.
The Work Around Solution given by SAP is as follows: The system provides the following workaround:
After you change the indicator for materials planning-relevance to
"immediately" you can execute the availability check as required. You must
not save the order or network.
Regards,
Muhammad Usman Kahoot
Edited by: Usman Kahoot on May 27, 2010 1:32 PM

User exit/BADI for Purchase requisition through release of Process order

Hi ,
i need to add some text to the Pur Req.
The Pur Req will be created THROUGH the release of PROCESS order. Please let me know any exits are available for the same.
regards

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

Do not want Budget check & Commitment value for purchase Requisition

Hi Experts,
I hope you all are doing well.
My client's requirement is that at the time of Creation of Purchase Requisition there should be no budget check against WBS element and also Commitment value should not be for Purchase Requisition.
Please suggest.
Thanks & Regards

Hi Gokul,
Thanks for ur quick reply.
I have done changes in tolerence limit (activated it for PO only).
Now i created 1 Project PR of more than value of budget (system didnt check the Budget against WBS) but when i am trying to create PO with reference to same PR, system is giving error of budget. That is OK for me.
Now my requirement is to not take PR value as commitment in my reports, i want only PO value in Commitment column of repport.
I have read all 3 notes suggested by you. Can u tell me whcih one should i implement to stop PR value as commitment in reports.
Thanks & Regards

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

Customer Subscreen for Purchase Requisition

Hello All,
I need a custom subscreen on requisition at <b>HEADER</b> level. 'MEREQ001' adds a screen at item level. Is there any Screen Exit / BADI to add a custom screen at header level? Any kind of help is really appreciated.
Thank you all,
Chandni

Hi Chandi Reddy,
The t.code is ME51 For this available exits are :
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
For t.code we51n the available exits and badi are :
Enhancement/ Business Add-in            Description
Enhancement
MEREQ001                                Customers' Own Data in Purchase Requisition
Business Add-in
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
o.of Exits:          1
o.of BADis:          3
Rewards some points.
Rgds,
P.Naganjana Reddy

Validate Materials according type of Purchase Requisition

Good morning.
At present the system we have several types of Purchase Requsitions (document created by the ME51N) that users can use (PR for Material, PR for contracts, PR for services, etc)
When creating the PR, the user chooses the PR type and write materials codes. The system is not Restrict the user to do things like, for a PR with type pshicical Materials, request a service material, which is obviously wrong and generate rework.
What we require is to know how to parameterize the system to validate that type of PR, only to order the materials associated with each type and do not let things like the example above.
We have the material well classified by Material Group and Purchase Group. I just need to know how to assign materials to each type of PR.
Research on this topic, I found the SPRO something I think I could serve.
SPRO -> Materials Management -> Purchasing -> PR -> Documents types
See here for example for PR ZS01 - PR Materials (used to order everything that is NOT services, ie physical materials), if I go to see the types of position allowed me see the following:
Code:
Tp.Pos | Text Pos Type
Normal
C Appropriation
L Outsourcing
I Wanted to third
Transfer V
F Service
I also see that all other types of PR of which there are established, have enabled the same kind of position.
Anyone know if this is why users can request a service for a material type PR Materials. o A physical material in a service PR?
Could Restrict through this that for example if the user creates a type PR SERVICE, only to enter service type material (a material through the group I guess)?
At last if i cant by parameterization, which I think is to create a Ztable with the association "MATERIAL - TYPE Purchase Requisition" and a field-exit to the fields where the materials are entered in PR to validate that the user typed material associated with this type of PR chosen and if that does not leave PR record. What I like about this solution is that the material planner will add a function over having to keep this updated Z table.
I would appreciate opinions.

Hi,
By using following BADI you can put a check while saving PR
You can put a check with reference to item category and document type , and material group of the entered material and PR document type , if required you can maintain Z table with allowed relationship or you can update the same in BADI
(BAdI) ME_REQ_POSTED, you can trigger a variety of follow-on processing operations for purchase requisitions at the time of posting
Thanks
Diwakar

Release strategy for purchase requisition does not kick in

Hi Gurus!
I've been struggling with this issue for some weeks now.
I have set up the release strategy configuration for purchase requisitions with classifications.
However, if I create a purchase requisition the release functionality is not taken into account by the system.
See below some more information regarding my configuration:
1. I've created a new characteristic "REL_PR_GROUP". Status: released, Multiple values, Number of Chars 3, 7 values (TR1, TR2, TR3....TR7), Table name: CEBAN, Field name: EKGRP, Procedure for value assignment set to not ready for input.
2. I've created a new class: "REL_PR_ANPC". Class type 032, Status: released, Same classification: do not check, Char: "REL_PR_GROUP"
3. I have one release group "T1", Rel. object 1, OverReqRel is marked, Class: "REL_PR_ANPC"
4. I have 5 release codes. Grp: T1, Code: 01....05
5. I have 2 release indicators:
"R = Released", Rel. for ordering is marked, Changeabil: 4, Value chgs. 100,0
"X = Blocked", Changeabil: 4, Value chgs. 100,0
6. I have 1 release strategy:
"T1 with Grp T1"
- one release group, 01 Manager
- release prerequisites not applicable because of only one release group
- release status, nothing marked = blocked, 01 marked = released
- classification, purchasing group is TR1 or TR2 or TR3 or TR4 or TR5 or TR6 or TR7
I intentionally kept the configuration as simple as possible so I can try to get it working first.
Now if I create a purchase requisition for an item with release group T1, I would expect the release strategy to be activated. However, this is not the case. I don't see the "release status" tab in the PR, and if I try to relase via ME54 the system says the PR is not relevant for release.
Could you please assist in getting this working?

Hi,
Have you checked in CL30/CL30N if your release strategy is derived successfully?
See section 3 of Note 365604. A small section of it:
You can use transaction CL30 search for an object using the data
of the purchase requisition/purchase order. Here, it is important
that the object search determines exactly one strategy. If this
is not the case, this indicates that there are overlapping
strategies in the system or that the release strategies in
Customizing do not correspond with those from transaction CL24.
See the previous point. If the object search returns more than
one result, the system subsequently determines an incorrect
release strategy or no release strategy at all.
If it is derived successfully, next, check the user exit EXIT_SAPLEBND_001 as per Note 371667:
The following assignment statement has to exist within activated SAP
enhancements M06B0002 (include zxm06u13) and M06B0005 (include zxm06u31)
for purchase requisitions:
E_CEBAN = I_CEBAN.
Regards,
Purnima.

Getting errors when iam using BAPI_PO_CREATE1 for Purchase Order creation

Hi sap Gurus,
I am getting Errors when iam using BAPI_PO_CREATE1 for Purchase Order creation that Material (144) does not exist but it is alreardy maintained in MM01.
I dont get how it is coming.and what are the mandatory fields in bapi BAPI_PO_CREATE1 in item level .that is too material only.
pls let me know .
thanks in advance.

Hi,
Check the sample code..
report zpo_test             .
*DATA DECLARATION
constants : c_x value 'X'.
*Structures to hold PO header data
data : header like bapimepoheader ,
headerx like bapimepoheaderx .
*Structures to hold PO account data
data : account like bapimepoaccount occurs 0 with header line ,
accountx like bapimepoaccountx occurs 0 with header line .
*Internal Tables to hold PO ITEM DATA
data : item like bapimepoitem occurs 0 with header line,
itemx like bapimepoitemx occurs 0 with header line,
*Internal table to hold messages from BAPI call
return like bapiret2 occurs 0 with header line,
*Internal table to hold messages from BAPI call
pocontractlimits like bapiesucc occurs 0 with header line.
data : w_header(40) value 'PO Header',
purchaseorder like bapimepoheader-po_number,
delivery_date like bapimeposchedule-delivery_date.
data : ws_langu like sy-langu.
*text-001 = 'PO Header' - define as text element
selection-screen begin of block b1 with frame title text-001.
parameters : company like header-comp_code default '122' ,
doctyp like header-doc_type default 'NB' ,
cdate like header-creat_date default sy-datum ,
vendor like header-vendor default '2000000012' ,
pur_org like header-purch_org default 'PU01' ,
pur_grp like header-pur_group default '005' .
*sociedad like HEADER-COMP_CODE default '122' ,
*vendedor like HEADER-SALES_PERS default 'sale person'.
selection-screen end of block b1.
selection-screen begin of block b2 with frame title text-002.
parameters : item_num like item-po_item default '00010',
material like item-material default '12000000' ,
tipo_imp like item-acctasscat default 'K' ,
*pos_doc like ITEM-ITEM_CAT default 'F' ,
shorttxt like item-short_text default 'PRUEBA BAPI' ,
grup_art like item-matl_group default '817230000' ,
plant like item-plant default '3001' ,
mpe like item-trackingno default '9999' ,
*contrato like ITEM-AGREEMENT default '4904000003' ,
*quantity like ITEM-QUANTITY default 1 .
po_unit like item-po_unit default 'EA'.
selection-screen end of block b2.
Par?mnetros de imputaci?n
selection-screen begin of block b3 with frame title text-004.
parameters : centro like account-costcenter default '1220813150',
cuenta like account-gl_account default '6631400' ,
num_pos like account-po_item default '10' ,
serial like account-serial_no default '01' ,
ind_imp like account-tax_code default 'I2' .
selection-screen end of block b3.
start-of-selection.
*DATA POPULATION
ws_langu = sy-langu. "Language variable
*POPULATE HEADER DATA FOR PO
*HEADER-COMP_CODE = sociedad .
header-doc_type = doctyp .
header-vendor = vendor .
header-creat_date = cdate .
header-created_by = 'TD17191' .
header-purch_org = pur_org .
header-pur_group = pur_grp .
header-comp_code = company .
header-langu = ws_langu .
*HEADER-SALES_PERS = vendedor .
*HEADER-CURRENCY = 'DOP' .
*HEADER-ITEM_INTVL = 10 .
*HEADER-PMNTTRMS = 'N30' .
*HEADER-EXCH_RATE = 1 .
*POPULATE HEADER FLAG.
headerx-comp_code = c_x.
headerx-doc_type = c_x.
headerx-vendor = c_x.
headerx-creat_date = c_x.
headerx-created_by = c_x.
headerx-purch_org = c_x.
headerx-pur_group = c_x.
headerx-langu = c_x.
*HEADERX-sales_pers = c_x.
*HEADERX-CURRENCY = c_x.
*HEADER-ITEM_INTVL = c_x.
*HEADER-PMNTTRMS = c_x.
*HEADER-EXCH_RATE = c_x.
*HEADER-EXCH_RATE = c_x.
*POPULATE ITEM DATA.
item-po_item = item_num.
item-quantity = '1'.
*ITEM-MATERIAL = material .
item-short_text = 'prueba bapi_po_create1'.
*ITEM-TAX_CODE = ''.
item-acctasscat = 'K' .
*ITEM-ITEM_CAT = 'D' .
item-matl_group = '817230000' .
item-plant = '3001' .
item-trackingno = '99999'.
item-preq_name = 'test'.
*ITEM-AGREEMENT = '' .
*ITEM-AGMT_ITEM = ''.
item-quantity = '1' .
item-po_unit = 'EA'.
*ITEM-ORDERPR_UN = 'EA'.
item-conv_num1 = '1'.
item-conv_den1 = '1'.
item-net_price = '1000000' .
item-price_unit = '1'.
item-gr_pr_time = '0'.
item-prnt_price = 'X'.
item-unlimited_dlv = 'X'.
item-gr_ind = 'X' .
item-ir_ind = 'X' .
item-gr_basediv = 'X'.
*ITEM-PCKG_NO = '' .
append item. clear item.
*POPULATE ITEM FLAG TABLE
itemx-po_item = item_num.
itemx-po_itemx = c_x.
*ITEMX-MATERIAL = C_X.
itemx-short_text = c_x.
itemx-quantity = c_x.
*ITEMX-TAX_CODE = C_X.
itemx-acctasscat = c_x.
*ITEMX-ITEM_CAT = c_x.
itemx-matl_group = c_x.
itemx-plant = c_x.
itemx-trackingno = c_x.
itemx-preq_name = c_x.
*ITEMX-AGREEMENT = C_X.
*ITEMX-AGMT_ITEM = c_x.
itemx-stge_loc = c_x.
itemx-quantity = c_x.
itemx-po_unit = c_x.
*ITEMX-ORDERPR_UN = C_X.
itemx-conv_num1 = c_x.
itemx-conv_den1 = c_x.
itemx-net_price = c_x.
itemx-price_unit = c_x.
itemx-gr_pr_time = c_x.
itemx-prnt_price = c_x.
itemx-unlimited_dlv = c_x.
itemx-gr_ind = c_x .
itemx-ir_ind = c_x .
itemx-gr_basediv = c_x .
append itemx. clear itemx.
*POPULATE ACCOUNT DATA.
account-po_item = item_num.
account-serial_no = serial .
account-creat_date = sy-datum .
account-costcenter = centro .
account-gl_account = cuenta .
account-gr_rcpt = 'tester'.
append account. clear account.
*POPULATE ACCOUNT FLAG TABLE.
accountx-po_item = item_num .
accountx-po_itemx = c_x .
accountx-serial_no = serial .
accountx-serial_nox = c_x .
accountx-creat_date = c_x .
accountx-costcenter = c_x .
accountx-gl_account = c_x .
account-gr_rcpt = c_x.
append accountx. clear accountx.
*BAPI CALL
call function 'DIALOG_SET_NO_DIALOG'.
call function 'BAPI_PO_CREATE1'
    exporting
      poheader         = header
      poheaderx        = headerx
    importing
      exppurchaseorder = purchaseorder
    tables
      return           = return
      poitem           = item
      poitemx          = itemx
      poaccount        = account
      poaccountx       = accountx.
*Confirm the document creation by calling database COMMIT
call function 'BAPI_TRANSACTION_COMMIT'
exporting
wait = 'X'
IMPORTING
RETURN =
end-of-selection.
*Output the messages returned from BAPI call
loop at return.
    write / return-message.
endloop.
Regards
Sudheer

Problem in Purchase Requisition Creation

Dear Experts:
We are facing a problem while purchase requisition creation. We have created an Internal order No. 600406 and an Asset in Company Code AB01 but while creation of Purchase Requisition level when we are selection that Order and Asset in Purchase Requisition system automatically changing my Order no. 600020 instead of 600406. I've checked OKB9 where Order no. maintained as 600020 against Company code AB01 which I deleted and save but after that Purchase requisition asking for Order Number that means we have to maintain Order number in OKB9. Now can you please advise how can we get my current order number in requisition instead of any default number.
Thanks in advance and your kind suggestion is highly appreciated.
Best Regards.
Ripon Kumar Paul

Please find attached screen shots of OME9

Automatic Purchase Requisition Creation in MRP run

Hi,
1. I create a Sales Order for quantity 20 of main material MAT which has two sub-components - COMP1 and COMP2. The plant in which this sales order is being created does not have any stock quantitiy of the material or its sub-components. For quantity 20 of the main material, quantities required of the sub-components are 40 and 60 respectively.
2. I run MRP using transaction MD03 for the sub-components. This created purchase requisitions for the sub-components automatically. But, I see that the system creates only one purchase requisition of quantity 40 for COMP1 but two purchase requisitions for COMP2 each having quantity 60.
Can you please tell me why is the system creating two purchase requisitions for COMP2?
Thank you,
Helpful answers will be immediately rewarded!

Hi Janakiraman,
I compared the parameters - Safety stock, Lotsize, Maximum Lot Size, Reorder point - between the two components but found all the values to be same.
The only difference I found in the parameter values was...
For COMP2 (the one for which 2 PRs were generated) 'Special Procurement' field was blank
For COMP1 this field had the value 4A which means "STO from X101 plant"
Do you have any idea what could be the reason?
Thank you.

Automatical Purchase Requisition Creation in MRP run

Hi,
1. I create a Sales Order for quantity 20 of main material MAT which has two sub-components - COMP1 and COMP2. The plant in which this sales order is being created does not have any stock quantitiy of the material or its sub-components. For quantity 20 of the main material, quantities required of the sub-components are 40 and 60 respectively.
2. I run MRP using transaction MD03 for the sub-components. This created purchase requisitions for the sub-components automatically. But, I see that the system creates only one purchase requisition of quantity 40 for COMP1 but two purchase requisitions for COMP2 each having quantity 60.
Can you please tell me why is the system creating two purchase requisitions for COMP2?
Thank you,
Helpful answers will be immediately rewarded!

Hi Janakiraman,
I compared the parameters - Safety stock, Lotsize, Maximum Lot Size, Reorder point - between the two components but found all the values to be same.
The only difference I found in the parameter values was...
For COMP2 (the one for which 2 PRs were generated) 'Special Procurement' field was blank
For COMP1 this field had the value 4A which means "STO from X101 plant"
Do you have any idea what could be the reason?
Thank you.

Materials available only for Purchase requisition creation

Similar Messages

Maybe you are looking for