Exclude Purchase Requisition as a source of requirement

Hi All,
Please help me to configure the scenario.
Sales order is created - Plant A, Sales Org u2013 A. (Item category u2013 BANC, Plant B is created as a vendor for Stock Transfer Purchase Order)
Production Happens in - Plant B
Present scenario u2013 we create sales order in SO u2013A, against plant A----automatic purchase requisition is created in Plant A against vendor Plant B. whenever we run MRP against plant B it create planned order against stock transfer requisition. From that planned order we get prod order and produce the material and deliver STO and finally customer.
***but our requirement is whenever we run mrp in Plant B it should not consider purchase requisition as source of requirement and will not create Planned order until or unless PR in plant A is converted to PO.
I will be waiting for your valuable reply.
Regards
Nirmal

hi,
I am sorry as I was away for 2 weeks.
I think the OPPQ settings may not do the trick for you as that is just stock in transfer ( not stock transfer request from other plants).
For the user exit details which I was talking before, you can see the link below
How is the requirement type for STO materials determined
hope this helps.
regards
Rav

Similar Messages

Frame work purchase requisition service number gross price required entry

Hi
In me51n t.code i am selecting document type FO then enter service numbers qty without entering gross price system taking zero price how to restrict this for particular document type FO,my configurations Spro >> Materials Management >> Purchasing >> Purchase Requisition >> Define Document Types field selection for my doc type FO is FOB,Spro >> Materials Management >> Purchasing >> Purchase Requisition >> Define Screen Layout at Document Level MY field selection key FOB & under Quantity and price i give required entry,still not working,
Regards
Sam

Hi,
Please give the Business requirement to be able to give you solution.
Best regards
Amit Bakshi

Purchase requisition not generate for dependent requirement after MRP run

Hello PP expert,
In our MTO scenario after MRP run planned order generate for header material but no PR generate for BOM components, (BOM not explode) when we run MRP component level in MD02 PR generate, system showing message "40- No coverage not provided by master plan" in MD04 order tree. this problem coming after when we DIMP applied. I checked some OSS note also.
Can any one provide right solution.
thanks in advance.....its urgent as client requirement.
regards,
Amit Awasthi.

Hi Amit
You must select the green star for the correct answer, in order to close the thread.
You may also select the yellow start for the helpful answers, in order to award points for those who helped you. See the blog below for more details:
How to close a discussion and why
I can see that most of your old threads are still open, therefore, I'd like to ask you to review and close them, by selecting the correct answer.
BR
Caetano

BAPI for assing source of supply for purchase requisitions

Hi,
can any one let me know if there is any bapi or function module to assing source of supply for purchase requisitions.
Points will be given
regards,
siva prasad.

Define fixed indicator in the source of supply , and set the source list usage of MRP to "1 "
Below is help from sap:
==================================================================
Determining the Source of Supply via the Source List
The system first checks whether a quota arrangement has been maintained for the material, which has a validity period that covers the requirements date of the purchase requisition.
It then checks whether only one entry exists in the source list that is relevant to MRP. The indicator for source list usage must therefore be set for a particular vendor so that purchase requisitions and delivery schedules, which are created during the planning run, are automatically assigned to this vendor. In the case of a delivery schedule, you must also have maintained a scheduling agreement for this entry.
If you have maintained all the entries correctly, the system creates a purchase requisition with the source of supply that is recorded in the source list.

How to attach Source of Supply to Purchase requisition(by MRP)

Hi Friends,
Source list - we are maintaining Source list for source of supply.
Please tell me how to attach Source of supply by means of source determination to the Purchase requisition(generated by MRP) ?. What are the configuration and transaction steps?.
Thanks

Define fixed indicator in the source of supply , and set the source list usage of MRP to "1 "
Below is help from sap:
==================================================================
Determining the Source of Supply via the Source List
The system first checks whether a quota arrangement has been maintained for the material, which has a validity period that covers the requirements date of the purchase requisition.
It then checks whether only one entry exists in the source list that is relevant to MRP. The indicator for source list usage must therefore be set for a particular vendor so that purchase requisitions and delivery schedules, which are created during the planning run, are automatically assigned to this vendor. In the case of a delivery schedule, you must also have maintained a scheduling agreement for this entry.
If you have maintained all the entries correctly, the system creates a purchase requisition with the source of supply that is recorded in the source list.

Viewing purchase requisitions/purchase orders

Hi Every body,
Can anybody guide me any transactions to view purchase requisitions/purchase orders/planned orders at a glance for the selected materials
Regards,
Manish

Hi check with this
ME52N     Change Purchase Requisition
MEMASSRQ     Mass-Changing of Purch. Requisitions
ME53N     Display Purchase Requisition
ME51N     Create Purchase Requisition
ME56     Assign Source to Purch. Requisition
ME57     Assign and Process Requisitions
ZPRPRINT
ME54N     Release Purchase Requisition
ME55     Collective Release of Purchase Reqs.
ME5F     Release Reminder: Purch. Requisition
ME5A     Purchase Requisitions: List Display
ME5K     Requisitions by Account Assignment
ME26     Display PO Supplement (IR)
ME24     Maintain Purchase Order Supplement
MEPO     Purchase Order
ME23N     Display Purchase Order
ME22N     Change Purchase Order
ME21N     Create Purchase Order
ME28     Release Purchase Order
ME29N     Release purchase order
Z
ME9F     Message Output: Purchase Orders
ME2W     Purchase Orders for Supplying Plant
ME2M     Purchase Orders by Material
ME2K     Purch. Orders by Account Assignment
ME2B     POs by Requirement Tracking Number
MELB     Purch. Transactions by Tracking No.
ME2C     Purchase Orders by Material Group
ME2N     Purchase Orders by PO Number
ME2A     Monitor Confirmations
ME80FN     General Analyses (F)
ME81N     Analysis of Order Values
ME2L     Purchase Orders by Vendor
ME1P     Purchase Order Price History
ME22N     Change Purchase Order
MEPO     Purchase Order
ME23N     Display Purchase Order
ME24     Maintain Purchase Order Supplement
ME22N     Change Purchase Order
ME26     Display PO Supplement (IR)
ME21N     Create Purchase Order
ME28     Release Purchase Order
ME29N     Release purchase order
Z
ME9F     Message Output: Purchase Orders
MELB     Purch. Transactions by Tracking No.
ME2N     Purchase Orders by PO Number
ME2M     Purchase Orders by Material
ME2K     Purch. Orders by Account Assignment
ME2C     Purchase Orders by Material Group
ME2B     POs by Requirement Tracking Number
ME2W     Purchase Orders for Supplying Plant
ME2A     Monitor Confirmations
ME80FN     General Analyses (F)
ME81N     Analysis of Order Values
ME2L     Purchase Orders by Vendor
ME1P     Purchase Order Price History
ME22N     Change Purchase Order
ME26     Display PO Supplement (IR)
MEPO     Purchase Order
ME22N     Change Purchase Order
ME23N     Display Purchase Order
ME24     Maintain Purchase Order Supplement
ME21N     Create Purchase Order
ME28     Release Purchase Order
ME29N     Release purchase order
Thanks & Regards
Mangal

How to Restrict one more line item in Purchase Requisition

Dear SAP MM Guru's
My business Requirement is to Restrict one more line item to create in Purchase Requisition,
Using T code : ME51N i have created a PR with 10 (TEN) Line item's on 20 June '14 ,
Using T Code : ME52N on 23 June '14 my business demands to add one more line item 11th with different material code in Purchase Requisition .
Now Sourcing Team is demanding is once Purchase Requisition is created Don't allow to create one more Extra line item in same PR .
Through an Error : " One More Line Item is not possible to ADD "
Can i use below BAPI :
1) BAPI_PR_CHANGE
2) BAPI_REQUISITION_CHANGE
Please do the Needful
Thanks & Best Regards
Kumar

Hi,
Change Screen layout for PR.
For ME52N make Material number and Material description/short text fields to 'Only display'. By this user cannot enter new material code or direct material description to add new item.
In this scenario check :
1. Create new with reference to another PR by adopting details.
2. Check with Change push button behavior within ME52N and ME53N transactions available.
3. Consider remove ME52N authorizations from users (& Change Push button also from ME53N).

Creation Of A Single Purchase Requisition From Different Planned Orders

Hi,
After MRP run i get different Planned Orders for different raw materials . My requirement is that can i combine all the Planned Orders for diiferent materials into a single Purchase Requisition.This is a urgent requirement.
If useful i will award points.
Regards
Jimmy

Hi,
it is not possible to combine with planned orders for different materials into single PR but differet PR can combine into a single Purchase Order.
pls let me know any clarification.
thanks
mohan
Message was edited by:
Mohan Ramalingam

User Exit/BADI to change the Purchase Requisition date,creating threw MD02

Hi,
I've a requirement to change the Purchase Requisition creation date.
I'm using MD02 to create Purchase Requisition.
Based on the requirement if the available qty is less than the required quantity,we can change Purchase requisition date.
Please let me know if any BADI's/User Exits we can use for this purpose.
I've checked EXIT_SAPLMEREQ_010. I've kept debugging point nad i run MD02, but it is not stopping in the exit.
we are using SAP 4.6c.
Thanks,
Adi.

Hi Experts,
Could you please give me a suggestion for the above problem???
Thanks,
Adi.

Purchase Requisition field in TCode:- MD09

Dear Experts,
I have a requirement, currently in MD09 we can enter the only one 'Purchase Requisition' number to get Pegged Requirement Details. My requirement is to make the 'Purchase Requisition' field available for multiple input entries... is there any user exits with which i can do this modification the SAP Standard MD09 Tcode....????
Plz suggest...
Thanks in advance...

It may be easier to create an enhancement or implementation. Did you try looking at a BADI like ME_PROCESS_REQ_CUST? Inside here you can create an implementation .
Or, to find a BADI to put your code into, put a breakpoint inside this method. After executing your transaction you will see every BADI that this transaction will hit inside of this method:
CALL METHOD cl_exithandler=>get_class_name_by_interface
EXPORTING
instance = instance
IMPORTING
class_name = class_name
CHANGING
exit_name = exit_name
EXCEPTIONS
no_reference = 1
no_interface_reference = 2
no_exit_interface = 3
data_incons_in_exit_managem = 4
class_not_implement_interface = 5
OTHERS = 6.
CASE sy-subrc.

Assign document date to purchase requisition date

Hi All,
I have a question regarding purchase requisition. I have a requirement where i have to change the purchase requisition date based on certain condition. I tried to change it in the user exit "MV45AFZZ" when the sales order is released, but at this point the purchase requisition number is not yet created in the database though it is available in this internal table "XVBEP-BANFN" in the include "FV45EFMA_BESCHAFFUNG_SICHERN" of "SAPFV45E". Can anyone tell me when will EBAN table get updated and when should i change the requisition date? I hope the doubt is clear, otherwise let me know.
Thanks and have a nice day.
Cheers,
Ashley

Hi Ashley
I have tried on my system and itz working, Can you
place a break-point in MV45AFZB and see if the flow is
reaching the place at the point where you need.
Coming to the Customer Function in
FV45EFMA_BESCHAFFUNG_SICHERN, have you checked as per
the documentation of it:
FU EXIT_SAPFV45E_001
Text
Update Purchase Order from Sales Order
With this customer exit the standard system behavior
regarding updating order data from the sales order can
be expanded or restricted.
The module is called up when the sales order is changed,
as long as the conditions for changing the order have
been filled. It transfers the document number, the
purchase requisition number and a table for the fields
to be changed in the order (T_PURCHASE_DATA). <b>This
can be expanded or restricted in the existing
Customizing.</b>
<b>The rule is: To change a field with the name
FIELDNAME, a subprogram (form routine) with the name
POSITION_CHANGE_FIELDNAME must exist in the program SAPMM06E.</b>
Try to find if POSITION_CHANGE_BADAT exists in
SAPMM06E. If not found ask you functional consultant to
expand it for purchase requistion date and see if it
works.
Hope your problem resolves.
Kind Regards
Eswar

SNP Heuristic recreation and adding of Purchase requisition

Dear All
Thanking In advance,
Critical Issue
We have scheduled a heuristic run for 7 FERT materials,
Run was successful in simulation version, When we take a re-run
(heuristic) on the same data,It is adding the quantities of the
forecast to the same purchase requisition for only two FERTS, for
others it is deleting and recreating purchase requisition same as the
forecast requirement. This in turn is leading to doubling of
requirement for these two FERTS at the lower BOM materials.
e.g.If demand is 10 and we run heuristic in first run it will create 10
purchase requisitions, if we Re-run heuristic on the same data it is
adding 10 more quantity for same purchase requisition.
Before generating the requisitios it will show the message Invalid order and help of which shows "Order does not exist in Live-Cache"
What could be the reason for this?
Amol

Dear all,
problem solved by upgarding Support Pack to 15.0
Amol
Edited by: Amol Chavan on Jan 21, 2008 4:08 PM

Search Receipt by Purchase Requisition (PR) Number

Hi,
I need to Search Receipt by Purchase Requisition (PR) Number.
eg. for PR 10001203 i need to know items in this PR have been received to the inventory or not.
Please help me find a solution.
Thanks
JB

The requisition field in the Receiving forms are there for the Internal Requisition and not for the Purchase Requisitions.
To fulfil your requirement, I suggest you to navigate to the Purchase Order Summary form -> Related documents section.
Enter your requisition number in the respective field and select the Shipment radio button. Click on Find.
You will be able to see all the related purchase order and received, accepted, billed qty etc. in the subsequent form.
Thanks,
PS.

Heuristic run @ destination location is creating the purchase requisition without source plant

Hello All,
Trust you are doing well.
Believe this is the good time to connect with you all get some advice on the below mentioned scenario:
Material (XXXXXX) is discontinued at source location (Plant specific material status: 90) but the same material
(XXXXXX) is still used in destination location (plant specific material status: 60). Here heuristic run @ destination location is creating the purchase requisition without source plant.
Here the customer expectation is that “SNP should not create the order, since the material is discontinued in source plant”
Could you please advise?
Regards,
Prabin

Hi Prabin,
You can change the SNP profile to NO PLANNING automatically and exclude the target location from the SNP run. Maybe you can try using Badi: SMOD_APOCF005.
This is what I would do:
1- Do not exclude the status 90 in the iModel.
2- Then when you change the status in order to discontinue a material at the source location you will be changing the status from 60 to 90 and you will CIF this modification to APO. At this time, I would use the BAdI: SMOD_APOCF005 to identify this situation. You will need to add a code in order to identify what are the possible target plants of your source plant and you will need to change the SNP Profile at the target location.. look for a BAPI for this...
Take a look of this document to see an example code of SMOD_APOCF005:
APO SNP - Master Data Automation
Kind Regards,
Mariano

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

Exclude Purchase Requisition as a source of requirement

Similar Messages

Maybe you are looking for