Release /Approval of PO

Dear All SAP GURU's
Regarding release of PO:
In normal senario, po release goes to DGM->GM level. But when material net price is more than the tolerance limit then it should go for approval to director level.
say example : Suppose purchase department is procuring raw material .For that top managment will decide the price of item is 50/- per kg. and tolerance limit +10% acceptable. And when for that we create po @ 53/- kg then po should go release to DGM /GM .But if rate of the material exceeds tolerance say 60/- kg then approval should go to managment level that means to director.Then top management will ask reason for increased rate of item. This is not considering PO value.Only item rate is considered here.
Can anybode suggest how to resolve this issue.
Thanks in advance
Mahesh

Hi
In standard SAP it is not possible as it will retrigger same release strategy if given percentage value exceeds the limit given in release strategy.
What you need to do here is you have to create two releases one with value< X and other with value>X.
Even then it will not serve your purpose as it will go to different people, when you change price by 10%.

Similar Messages

Error while assigning user for release approval path for payment release

Hi everyone,
     I am trying to assign user for payment release in SPRO. I have defined upto 'Define relevant document types for release for payment', after that while assigning user in terms of position for release and save it, i am getting error 'Program error: ASSIGN with length 0 in program "MP120800" '.Because of it i can t proceed further.
The data in details below;
1. Create Workflow Variant for Release for Payment
   1000     SAP
2. Assign Company Code Workflow Variant for Release for Payment
1000     1000     SAP
3. Define Release Approval Groups for Release for Payment
0001     Vendor A
0002     vendor B
0003     Vendor C
0004     G/L accounts
4. Define Release Approval Paths for Release for Payment
0001     Vendor high
0002     Vendor middle
0003     Vendor low
0004     G/L accounts
0005     Other
5. Assign Release Approval Paths for Release for Payment
1000     KZ     0001     0001
1000     KZ     0002     0002
1000     KZ     0003     0003
6. Assign Release Approval Procedure for Release for Payment
1000     0001     20,000.00     KES     1     WS10000052     WS00400011
1000     0002     50,000.00     KES     2     WS10000052     WS00400021
1000     0003     1,000,000.00     KES     3     WS10000052     WS00400022
7. Define Relevant Document Types for Release for Payment
     1000     KR
1000     KZ
8. Define Users with Authorization to Payment Release
1000     0001     1     20,000.00     KES
1000     0001     2     50,000.00     KES
1000     0001     3     100,000.00     KES
here i have selected the option and tried to create Orgobject, i am getting following error
Program error: ASSIGN with length 0 in program "MP120800"
If any corrections in the definitions, Please let me know.
Thanks in advance!!

Hello,
Please start the report RSWOGIND, set also the checkbox "generate all
ObjTypes from new". This should solve the problem.
Best regards, Hana

Workflow Flow Release Approval

Dear All,
I have Workflow Issue and i am sending my Requirement Go Through it .
Issue:
I am using F-67 forcustomer credit memo parking my requirement is if I post below 500/- SAR thedocument should not lock and the accountant can release the document throughFBV0 t-code and if the accountant post above 500/-SAR than the document should lock and accountant cant able to release above 500/-SAR document Through FBV0 T-code only it must be released by the Finance Director.This I want to configure in Workflow, Release Approval Level in T-code SWDD.
Get me out of this as i am very new to workflow as i am FICO Consultant.Your earliest reply on above is requested.
Regards,

Hello,
after checking linkage and Workflow .
i'm getting this error.
Following error occurred:
00 341
RFC_NO_AUTHORITY
Message text:
Runtime error RFC_NO_AUTHORITY has occurred
SAP System: EDV
Client: 100
Event container appended as attachment.
Event linkage not changed.
Event stored temporarily.
Events can be redelivered via event queue
administration (transaction SWEQADM).
so what should i do to solve this problem.

Work Order Release Approval workflow

Hi All,
I am trying to setup Work Order Release Approval workflow. I have set its AME using supervisory level as the action type. When I tried set work order status, I had to set the department as I set department attribute as its AME condition, and work order status changed into Release - Pending and form become disable.
Where can the supervisor make his/her approval to relese the pending status?
I tried the Maintenance Super User page, but it can only review.
Any help is greatly apprecaited.
Thank you,
Iqbal

HI
Please post EBS release version da and platform details
1001759 wrote:
Hi All,
I am trying to setup Work Order Release Approval workflow. I have set its AME using supervisory level as the action type. When I tried set work order status, I had to set the department as I set department attribute as its AME condition, and work order status changed into Release - Pending and form become disable.
Where can the supervisor make his/her approval to relese the pending status?
I tried the Maintenance Super User page, but it can only review.please see if this helps you
follow this navigation
1. eAM
2. Work Orders > Query for existing unreleased work order.
3. Release it & submit for approval.
4. Approve the WO.
;) AppsMAsti ;)
Sharing IS Caring

PO Release/Approve

Hello i need some info regarding PO's.
1) Where can i get the information as to who has released/approved the PO. The person who creates the PO can be found in ekko table, likewise where can i find info regarding the person who approved/released the PO.
2)Is there any Tcode which displayes all the invoices for a given PO.
Regards,
Rahul

1. Check if BAPI_PO_GETRELINFO gets the info you are looking for.
2. If that doesn't work, then you can look at the change documents of the release indicator in EKKO table. From the change documents you can find who has approved the PO.
Second Question
1. ME23n, if you look at the history tab in bottom part of the screen, it will display all the invoices as well the GR documents issued against that PO.
Regards,
Ravi
Note - Please mark all the helpful answers

Report for POs pending Release (approval) and POs overdue (past deliv date)

Hi All,
In ME2N - std report for POs. How do I set the selection critieria in order to get the following information
1. POs pending Approval (subject to Release Strategy)
2. POs pending delivery from Vendor where the delivery date requested in the POs is past. (How does Selection parameter WE101 help in this report.? How to show how many days past requested delivery date in the PO?)
Thanks in advance

Dear,
1. POs pending Approval (subject to Release Strategy) : -
Enter ME2N, select Dynamic Selection.
Here click on Purchasing Document Header,
Double click on Release Indicator field and assign "X" ,
Then souble click on Subject to release and also give "Yes" indicator then click on execute you get list of purchase order which is unrelease.
2) POs pending delivery from Vendor: -
Enter ME2N, Select selection parameter WE101,
Here you can find list of pending purchase order, You can see document date or delivery date from change layout to find out how it is past.
Regards,
Mahesh Wagh

Order release approval

Dear
Just have the idea about below one. We need the maintenance order approval based on plan cost.
For this we created Class type 032. The created class is assigned there. In class we referred the PMCO table and value is above one dollar.
Now the thing is how to make this effect in order level. Even i cant assign to the equipments,functional location. Also there is no standard t Code is available for order release like PR.
Thenna

hi all,
find the solution for planned cost,maintenance acitivity types,etc
1.create ct04characteristicand maintain values 10k,20kof some range if your going to call permits on planning cost here in additional tab mention the structure CSEVPERMIT & any field names
ILART-Maintenance activity type
PKOSTEN for planning cost
USER4 for estimated cost
IKOSTEN for actual cost.
2.Create permit class and put the charc in permit class and for class type 049 maintain classification status in IMG.[Cross application components--> classification system->classes---->maintain object types and object keys(here plz read the note and maintain status for class type 049).
3.Create permits using IPMD and put category , order status and goto classification and maintain permit class and select particular charc value for that permit.
By the above process respective permits assume that you have given based on planned cost of the orderget automatically assigned to the order,now you can maintain authorisation for the permit for issuing
Hope this might have met you requirement.
Plz try the same and let me know if you have any querries or no .If working give up points'''
regards
pushpa

Disabling selected Purchase Order field(s) after released/approved

Hi Experts,
I have a requirement to disable specific Purchase Order fields after released via ME29N.
For example, in Purchase Requisition - I can "Release Indicator - Field Selection Key" to control Purchase Requisition screen layout. However, for Purchase Order - the configuration for "Release Indicator" consist only standard default "Chgable" options.
Question:
Is there a way to customize the Purchase Order "Release Indicator" for screen layout based on customer requirements other that using the default as mentioned above?
Thank you.
Steven

Hi Padmasri,
I understand your explanation on the standard SAP behavior.
Nevertheless, I'm looking for some flexibility to meet customer requirement. Like in Purchase Requisition, there is option to further customize the screen layout by linking it to the "Release Indicator".
Therefore, apart from the standard 6 options given by standard SAP, can we add/customize the options? For example, my customer may one to change a field in the Purchase Order even after released.
Thank you.
Steven

PO Release Approval Error

First i did Release strategy in one client and i have transported it to other client
that time i didnt know that it cant be transported
After doing 3 PO when i tried to release it then i come to know that i have to configure again the Release Strategy in this client
When i tried to reconfigure it after doing some changes i want to check the class
when i clicked on Edit class it is showing the error
Class type 032: Class PO_RELEASE_CLASS being processed by MMUSER

Hi
Check out the same Screen is opened by MMUSER . We can able to open it in display mode only.
If you dont know check via SM12.
Regards
Anand

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

Credit Approval/Releasing

Credit Approval/Releasing
Approval Path Credit Analyst > Credit Team Leader> Credit Manager > Sales Director>Credit Committee
There should be an Approval Workflow for a blocked SO to be released and then invoiced. The approval hierarchy should be based on the Excess over Credit Limit % or amount and Past Due % or Amount (computation by Credit).
Is this possible?
Thanks!
Cindy

Hi Cindy Sy,
This is possible and you will have to use Work flow Program for this. You take the help of a Technical person who has knowledge about work flow programming and he will be able to help you.
To maintain the Approval Hierarchy and the Credit Limit % or amount based on which OR upto which a Approver can release and the details of next approver in authorised to release etc can be maintained in a Z Table which can be maintained in SM 30 Transaction.
Work in coordniation with Technical person with work flow knowledge and this can be done easily.
Reward points if it helps
Regards
Srini

What is the table field for PO releaser in R/3 (4.7 Enterprise)?

Hi Gurus out there:
Do you know if there is a table field for PO releaser in R/3 (4.7 Enterprise)?
We use for e.g. the transaction ME29N to release a PO and I haven't been able to find a DB table where the PO releaser is stored.
In DB table EKKO I can find the fields FRGGR (Release group), FRGSX (Release strategy), FRGKE (Release Indicator), FRGZU (Release status) and FRGRL (Release Not Yet Completely Effected) but no information of the user who released the PO.
Many thanks in advance.
/hw

Hi
<b>Have you tried reading the details of the PO Releaser using the BAPIs ?</b>
BAPI_PO_GETRELINFO
BAPI_PO_GETITEMSREL
BAPI_PO_GETITEMSREL            List Purchase Orders for Release (Approval): New as of 4.0A
BAPI_PO_GETRELINFO             Display Detailed Release (Approval) Information on Purchase Order
BAPI_PO_RELEASE                Release Purchase Orders
BAPI_PO_RESET_RELEASE          Cancel Release of Purchase Orders
<u>Related link -></u>
Re: How to fetch data from back end for PO?
Hope this will help.
Do let me know.
Regards
- Atul

Vendor payments release workflow!!!

Hi all
Can somebody explain to me how we setup standard workflow so that all vendor invoices greater than 100.000 can be blocked for payment automatically & released by some other user?
I tried to give the document type "KR" to the workflow variant & tried to do invoicing for the vendor. But I do not how I could release that blocked invoice...Is there any specific tcode or I have to go to the proposal & change the blocked reason from P to 'space'.
Thanks for all your time....

Hello Morgan,
Payment Release Process
Purpose
For each workflow variant, you can specify the amount from which a payment release should be triggered.
You can differentiate between one, two, and three-level release. This enables between one and three people to be involved in the release procedure, thus supporting both dual and triple control.
Prerequisites
You have made the following settings in Customizing:
Release approval procedure
(document type and amount for each workflow variant)
Assign persons with release authorization
In order to do this, you must first create release approval groups that can be entered in the customer and vendor master records.
Depending on these criteria and the release level, you can assign release authorizations in the form of organizational objects (job, position, organizational unit) in Customizing. If you do not define any criteria (such as release approval groups), the system takes the initial value of these criteria when the payment program is run. For example, if the system was unable to determine the release approval group, the release approval procedure and the employees with release authorization are determined on the basis of release approval group zero.
Process Flow
Minimum requirements:
The payment release function must be activated.
The relevant document type must be defined.
An item containing the following specifications must be created for employees with release authorization:
Workflow variant
Initial release approval path
Initial level
Maximum amount
Employees with release authorization can also be determined and assigned by user exits at each stage of the release approval procedure.
Result
If, when the payment run is made, the system could not determine an employee with release authorization, then it sends a message to the inbox of every person who has been assigned the task "payment release". Only after all these people have released the payment will the payment block be removed.
If a line item is refused for release, it is forwarded to the clerk who entered it for correction. After the document has been changed, the payment release procedure begins again. If changing the line items necessitates further actions, these must be defined within the Workflow component. The event CHANGED has been preconfigured for this purpose in the standard workflow model. If you run this event, the system assumes that the line item was rejected for payment. However, the item is NOT forwarded for correction to the clerk who entered it.
If an item is cleared before it is released, the payment release procedure is terminated (event CLEARED).
===========================================================
Workflow settings: The standard system contains several workflow models for payment release: One workflow framework (WS00400012) and three sub-workflows. In Customizing for Financial Accounting, you can specify which sub-workflow should be used when the workflow framework is run. You can also enter your own sub-workflows. They must however send and receive the same data from the workflow framework as the workflow models do.
You can use the standard sub-workflows (WS00400011, WS00400021, and WS00400022) to carry out a one, two, or three-level payment release procedure. If you require more than three release levels, you can copy the workflow models, enhance them and then enter the enhanced workflow definition in Customizing for Financial Accounting.
Event Linkage for the Event CREATED
If an amount requires a payment release, the event CREATED is triggered when a document is posted.
In this case, you must go into the workflow framework in the Workflow Workbench and enter the event linkage for this event, as described below:
Data for Event Linkage
Object type
BSEG
Event
CREATED
Receiver type
WS00400012
Receiver module
SWW_WI_CREATE_VIA_EVENT
Check Function
Receiver type
FM (function module)
Global
X
Enabled
X
Standard Tasks for the Event CREATED
The standard system contains two standard tasks that are triggered from the workflow mailbox and used in the workflow models.
Payment release (line item)
Change (line item)
Creating and Assigning Organizational Objects for Payment Release
You must assign organizational objects (organizational units, jobs, positions) to the standard tasks. These organizational objects can be created either in Personnel Planning and Development, via the Workflow Workbench, or in Customizing for Financial Accounting (assignment of release authorization to employees).
When you create organizational units, you must assign them to jobs or positions. You can then assign users to the positions.
Examples for assignments:
Organizational unit X < Position Y < User
Organizational unit X < Job Y < Position Z < User
In Customizing for Financial Accounting, you can assign organizational objects to the workflow variant, the release approval path, the release approval level, and the amount. These objects then release the amount depending on these criteria.
The organizational objects for payment release defined in Customizing for Financial Accounting are automatically assigned in the background to the standard payment release task (TS00407862).
The organizational objects for changing line items after they have been rejected for payment must be assigned to the standard task "Change line item" (TS00407864), either in Personnel Planning and Development, or via the Workflow Workbench. Alternatively, you can define the task as a general task (Additional data -> Classification).
Changing Line Items
The workflow models described above all contain a pre-configured event (CHANGED), which triggers other events in the same fashion as a rejection does. This event can be triggered by change documents. You must define it via the Workflow Workbench.
Hope I had been able to help you. Please assign points.
Rgds
Manish

Purchase Order Release Strategy didn't trigger

Hi Gurus and SAP People!
Good Day!
I currently have a problem regarding one purchase order which didn't trigger a release strategy. I checked the classification/conditions/classes and it's all satisfied. I tried replicating the scenario in our Development server and I always end up triggering a release strategy.
Moreover, as far as i know, the release procedure is not locked as it is one of the most commonly used release group and code. Can anyone have any ideas why that certain PO didn't trigger any release procedure upon saving?
More details that might help.
1. PO was initially on hold status then saved. (tried to replicate this as well and yet a release strategy was triggered)
2. Upon saving, PO triggered an IDoc successfully. (my replication results always stayed "yellow" as it is still waiting to be released/approved before the actual Idoc generation (green)).
3. Line item details had been changed between the PO being on hold and the actual saving. (but yet it still satisfies the release classifications)
4. Line items came from PRs, Contracts, RFQs.
Will greatly appreciate your help.
Thank you very much!
Regards,
JV

Hi Suzy!
Thanks for the answer.
I already checked the classification and searched our documentation repository if there were changes made and did not find any. Development and Production environment customization are the same.
I forgot to include that after a few days the PO was created, they deleted one line item. That deletion made the PO trigger a release strategy.
Nevertheless, the question still remains - why the PO didn't trigger any release procedure upon the initial saving.
Regards,
JV

Purchase Order Approval email confirmation

hello
i am trying to do a workflow that look like already exist in the SRM module WS14000089 ,
This workflow requires approval of the PO / PO-CV by the manager of the relevant purchasing organization. If the manager approves, the PO/ PO-CV is released; if he rejects, the PO/ PO-CV gets the status rejected, the workflow is terminated and the creator can reprocess the PO/ PO-CV and submit it for approval again.
how the description say , i need the release/approval of Purchase Manager and VP for total release a PO and i want send a email with 2 button : approval , reject and description and PO number .
now i am total lost in the workflow world , i try copy and customize the standard workflow template WS20000075
Workflow for release of purchase order but not sure what change i need to do for get what i want , if anybody can give me some tips or hints will help me a lot.
Thanks

This is a very involved question - far more than how to send email. There are numerous posts, wikis, and blogs on topics such as mobile approvals. I recommend that you search SCN more thoroughly.
Some helpful threads may be:
Offline approval on blackberry device in SRM
Approval Process on Blackberry
http://mailman.mit.edu/pipermail/sap-wug/2008-December/029818.html
Regards,
Sue

Release /Approval of PO

Similar Messages

Maybe you are looking for