NO Approved found for Purchase Requisition

HI,
we have a case, employee belongs to company B and raising the PR for company A. when he / she was initiating the PR. it says "NO Approved found for Purchase Requisition". we are following the Position Hierarchy. we have only one hierarhy for the two companies Can only please let me know how to sort the issue.
regards

Hi,
Are you using positional Hierarchy for approval for your Purchasing? Please check what is the final approver's approval limit/Position
and how much he can approve ?
You will get "No approver found" when system failed to find a approver based on the amount/position in your PR/PO.
Moreover, Please review the following MOS doc.
How To Diagnose Deferred Purchase Order And Requisition Workflows? [ID 884391.1]
How to Diagnose No Approver Found (Document Status Remains Incomplete with No Action Taken) and Build Default Approval List Failures in the Purchasing Approval Workflow [ID 295153.1]
HTH
sd

Similar Messages

Facing 'No Approver Found for Purchase Requisition' error when using AME

Hello All,
I am trying to test one simple rule in AME. Below are the the details of the rule.
Rule name - VO Category = SUPPLIES.FACILITIES
Item Class - Header
Rule Type - List Creation
Conditions
1. ITEM_CATEGORY in (SUPPLIES.FACILITIES)
Condition Type - Ordinary
Attribute - ITEM_CATEGORY
Data Type - String
Item Class - Line Item
String Value - SUPPLIES.FACILITIES
2. TRANSACTION_SET_OF_BOOKS_ID is equal to 1
Condition Type - Ordinary
Attribute - TRANSACTION_SET_OF_BOOKS_ID
Data Type - Number
Item Class - Header
Details
TRANSACTION_SET_OF_BOOKS_ID is equal to 1
Actions
Action Type - approval-group chain of authority
Rule Type - Chain of Authority
Order No - 1
Ordering Mode - Serial
Voting Method - Serial
Action - Require approval from Facilities Approver Group
Approver Group Details
Name - Facilities Approver Group
Type - Static
Voting Method - Order Number
There are two member in this approver group
Approver Type Approver Order Number
HR People HR People: akshay7 1
HR People HR People: akshay8 2
Now when i create a requisition with akshay7 as preparer then following notification is displayed
To akshay7
Sent 21-May-2013 16:55:08
ID 4681179
Approval workflow database error occurs while approving Purchase Requisition 14315
Contact your system administrator to identify the problem and to use SQL*Plus or Workflow Monitor to reactivate the approval workflow where it left off.
Give your system administrator the following information:
PL/SQL procedure: POR_AME_REQ_WF_PVT.GET_NEXT_APPROVERS
Error: ORA-20001: The procedure getNextPosition could not find parent position for : HR Positions: 01.Jrbuyer
Both the employees have one supervisor.
How to reslove this error?
Thanks in advance.

Hi Everyone,
The problem is solved now. The cause was that the test requisition that I was making was satisfying more than one rules and hence I end dated the remaining rules which solved the problem.
Thanks!

Building Odata service for Purchase Requisition

Hi Experts,
I have a requirement where I need to build a workflow approval service for Purchase requisition.
I want to build this service using the BOR/RFC option for itemwise approval of PR.
There are 2 BAPI's BAPI_REQUISITION_GETDETAIL and BAPI_PR_GETDETAIL but I am not getting the approach to get itemwise detailed information of a PR.
Could you please help me the steps taken to build this service.
Thanks in advance.

Hi Kavi;
I have configured Workflow Mailer Service for PO Approval and REQ Approval. For PO Approval Mail is coming correctly. But For Requisition Approval , Mail not coming. I have given 'REQAPPRV' in Correlation ID. What is error, did you check log file for details?
Please also check below:
11i/R12 - A guide for troubleshoting Workflow Notification Emails - Inbound and Outbound Doc ID:831982.1
Notifications Not Being Sent In Workflow Doc ID: 1012344.7
Workflow Mailers Not Sending Notifications Doc ID: 560472.1
Regard
Helios

Report - who is the current approver for purchase requisition

Hi Experts
Is there a report that can give information the status / who is the current approver for purchase requisition?
currently if we open the PR directly, we can only know the release strategy, release code, status of approver, but we cannot have the information who is the person that should approve this PR.
Thanks in advance
Prashanth.v

Hi All.
Unfortunately we want to have this information for our end user, and they will not have the access to SE16.
Another thinks is from CDHDR we will have the information if changes are made in PR. So it will give information user that already approve the PR
What we want to have is a report of outstanding PR (not yet released) that have information who is the user (the user complete name / user id) that should approve the PR.
Thanks In Advance
Prashanth.Venkategowda

Budget Approver for Purchase Requisition

Hi,
In MM setup for purchase requisition, 4 levels has been setup for approving based on amount. The person who will approve is configured to be determined based on user exit (value - 9) in TCode OMGQ.
My question here is where is this user exit and how can we know to whom this PR will actually reach for approval.
Please help me out.
Regards,
Binay Agarwal

That you have to check in the Workflow settings based on the organization defined in PPOME
User exit M06B0001
you ca check the logic of user exit in SMOD
enter the above user eixt and display the component logic

Is it possible Line level approval in AME for purchasing requisition?

hi
is it possible Line level approval in AME for purchasing requisition ?
so that send each line to separate approver ?

If using AME, it should be possible. Check AME Guide for POs for details. Let me know if you run into issues.
Thanks
Shree

Is it possible Line level approval for purchasing requisition in AME?

hi
is it possible Line level approval for purchasing requisition in AME?
so that send each line to separate approver ?

If using AME, it should be possible. Check AME Guide for POs for details. Let me know if you run into issues.
Thanks
Shree

AME for Purchase Requisitions

Hello All
I am in the process of setting up AME in R12.1.2 for purchase requisitions and got struck with an issue
My requirement is to route the requisition to a particular job based on the item category and the requisition total. I setup conditions, action types and approval groups and then the rule.
When I used static in my Approval Group setup it works fine with out issues however we do not want to use static as employees keep changing and want my approval driven out of the job hence updated the approval group to use Dynamic usage type and used the below query to pick the name of the employee based on the job.
select papf.full_name from per_all_assignments_f paaf, per_all_people_f papf, per_jobs pej where
paaf.person_id = papf.person_id
and sysdate between paaf.effective_start_date and paaf.effective_end_date
and paaf.job_id = pej.job_id
and pej.name like 'IT.Group IT Operations Manager.Staff'
Now when trying to create a requisition it shows up a message that "Approval List could not be generated. Please contact your System Administrator to review AME rules setup."
When validated the above query it says query is valid but still not working. I even tried with person_id but still no luck
Thanks a ton in advance
Regards
Dilip

Hi Dilip,
Pl. visit following links.
AME for iProcurement requisitions
Re: AME-Hierarchy Deciding Feature ?
HTH
Sanjay

ALV report for Purchase Requisitions(PR)

Hai All!
i am developing an ALV report for Purchase Requisitions(PR) tht are not approved ( ie IN RELEASE status), so i want to get who has approved PR and who has not approved it... from which table & which field i can get this data...
plz help me

Hi Following fields are used to set / reset release of PR
EBAN-FRGKZ
EBAN-FRGZU
EBAN-FRGST.
You will have to understand combination of these field from MM Fuctional Consultant.
rgds
rajesh
Edited by: RAJESH KUMAR on Aug 6, 2008 12:18 PM

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

Can AME used in combination with position heirarchy for purchase requisitions ?

Hello,
We are using position heirarchy for purchase requisitions.
Can we use Approval Management engine in combination with the existing position heirarchy for purchase requisitions for more flexible workflow routing ?
regards,
Natalia

Hi Natalia,
Have your inquiry been addressed? Please let me know if you need any further assistance in this, otherwise, Please mark the answer as Correct/Helpful in order to leverage the discussion and facilitate correct answer to other members who may confront the same concern of yours.
Note: Liking the answer will not mark it as Correct/Helpful, you have to open the discussion first to be able to mark it (This is not possible by opening the discussion from your inbox)
Thanks,

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

Release strategies for purchase requisitions

Hello,
I'm having trouble with profiles and roles for release strategies, this is the scenario:
-for purchase requisitions we have two approval levels, release code S1 and S2. When release code S1 is cleared, then S2 must be approved. The head of a certain purchasing group will use S1 to approve the requisitions from his own department, and then the financial director will approve with S2. However, finance is also a purchasing group, so in some instances the finance director will have to approve with S1 and then S2.
My question is: how can we use profiles and roles so that the finance director has access with S2 to all (*) purchasing groups, but with S1 for only a certain purchasing group (in this case "500")? we can't seem to be able to define certain purchasing groups to different release codes, purchasing groups must be defined at purchsing requisitiom level.
Many thanks
Daniel

HI,
Not necessarily, you just need a different strategy for each different combination of release codes involved.
So if certain P groups need to be put through a different sequence of approvals, then have one new strategy for this group of P groups and one for the other combination of P groups.
Or however many different variations you have.
Steve B

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

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.

NO Approved found for Purchase Requisition

Similar Messages

Maybe you are looking for