PO Release process item level control

Hi,
Please guys any way to control Release process at item level based on account assignment any configuration or user exit or bapi.
JACK

Hello Jack,
Addition to my previous response, here is the step by step process to define release procedure.
http://www.sap123.com/showthread.php?t=59
When you maintain characteristic, consider the OSS note which I mentioned in my previous thread.
Hope this helps.
Regards
Arif Mansuri

Similar Messages

ITEM LEVEL CONTROL IN SALES ORDER

Dear All,
In a sales order if I have 5 line items,usualy if the stock is not there for first two line items, in delivery it will start with 3rd line item...Is there any control in item level where I can keep first line item as mandatory ,then only it should process to second line and 3rd line item with out using any userexit.
Please help
Regards
CNRNAIR

with out using any userexit.
No unless you apply a suitable user exit, this requirement cannot be met.
thanks
G. Lakshmipathi

PO release at item level

Hi all
Is it possible to release PO at item level.
Our requirement is as follows:
We have a field in material master of each material to be checked before PO can be released.
The PO price should not be greater than the value in the material master field for each material.
Is there any way to do this.??
Thanks in advance
JOE

Hello all
Thanks for your responses.
The industry is contract manufacturing where we quote raw material cost also to customer.
Actually this price is stored in the material master accounting 2 field.
While creating the PO , buying price should not exceed this price.
So we have a user exit to check the prices and give an error message.
In some situations like short lead time for FG from customer, they agree for higher price of raw material because of short lead time.In this case higher authority need to approve the higher PO price.
any suggestions.
Thanks
jo
Edited by: Jo George on Jan 5, 2009 9:08 AM
Edited by: Jo George on Jan 5, 2009 9:10 AM

Release strategy - item level

hii all
can some body tel me , how and where we have to configuration for PR release strategy at item overview level.
And the same item level release strategy is posssible to configure for PO also??
If not y what is reason???
Thanks in advance
SAP-MM

hi
> how and where we have to configuration for PR release strategy at item overview level.
http://www.sapstudymaterials.com/2008/08/purchase-requisition-pr-release.html
>And the same item level release strategy is posssible to configure for PO also??
hi we cant have itemised release for PO
logically thinking PR can have multiple item and no fixed vendors and even not sure for placing order
so the realing person will decide for the item to be purchase so it has itemised relase
now in PO ,u will raise PO only when u have confirmed the purchase and the order will be for one vendor
so for ordering u have to relese the whole po,
or u can say u will create PO for all the items which have to procure so release will be for whole PO
go to spro>MM>Purchase Requisition>Release Procedure read the left side help for WITH and WITHOUT CLASSIFICATION
Edited by: Kunal Ingale on Mar 9, 2010 6:32 AM

Item level release

Hi experts,
what is mean item level release and header level release in PR. How to configure it.
pls explain in detail
regards
arun

Hi,
Release Procedure
Use
You use this component if you wish to set up approval procedures for purchase requisitions or other purchasing documents. Under such a procedure, if a purchase requisition or external purchasing document fulfills certain conditions (e.g. the total order value exceeds $10,000), it has to be approved (by the cost center manager, for instance) before it can be processed further. This process of approving (clearing, or giving the "green light" to) a proposed item of expenditure is replicated in the SAP System by the "release procedure".
It is sensible to define separate release procedures for different groups of materials for which different departments are responsible, and to define separate procedures for investment goods and consumption goods.
Which Documents Can be Released (Approved)?
Release procedures can be defined for the following documents:
·     Purchase Requisition
·     The external purchasing documents purchase order (PO), contract, scheduling agreement, request for quotation (RFQ), and service entry sheet
Release Procedure for Purchase Requisitions
Two different procedures are available for requisitions:
·     With classification
With this procedure, requisitions can be released both at item level (i.e. item-by-item) and in total. The latter approach is also termed "overall release".
·     Without classification
With this procedure, requisitions can only be released at item level.
Release Procedure for External Purchasing Documents
External purchasing documents (i.e. purchasing documents other than requisitions) are released at header level. Item-by-item release is not possible. These documents can only be released using the release procedure with classification.
Regards,
sasi

Item Level PR Release

Dear all,
I am using PR release at Item level, I have 2line items in my PR i have refused 1 line item & approved the other, now when i m creatin the PO from that PR it still shows both the line items...
system should show only the released line items..
please guide
cheers

Dear,
As per my view, When you create purchase order with reference of purchase requisition system take both line item which you given.
But if you want to restrict the creation of purchase order for not released line item of purchase requisition.
Make Message no. 06055 as error message number via sap config.
For do this follow bellow path.
SPRO -> Material Management -> Purchasing -> Environment Data -> Define Attributes of System Messages
and make it as error message.
Regards,
Mahesh Wagh

Pr release process

hi expert
I want to configure pr release stratgy can u tell me what are the setting to be done step by step and our campany have got one plant
Thanks & regards
vijay

HI
Release Procedure - Procedure in which one or more authorized persons (e.g. a cost center manager) give(s) the go-ahead or "green light" to procure a material or external service.
(Release Procedure for PR, RFQ, PO, Contracts & Scheduling Agreements)
The following purchasing objects can be released:
Purchase requisitions
A requisition (regarded as an internal purchasing document) cannot be converted into a follow-on document until it has been released.
External purchasing docu. (RFQs, purchase orders, contracts, scheduling agreements and service entry sheets)
An external purchasing document cannot be issued to a vendor until it has been released.
Note:
Requisitions can be released either item-wise or in total. External purchasing documents can only be released in total.
Release Procedure for Purchase Requisitions:
Two different procedures are available for requisitions:
With classification
With this procedure, requisitions can be released both at item level (i.e. item-by-item) and in total. The latter approach is also termed "overall release".
Without classification
With this procedure, requisitions can only be released at item level.
Characteristics (CT04): In the classification system, characteristics describe the properties of objects. The values of a characteristic specify these properties.
Characteristic COLOR has the values 'red', 'green', and 'blue'. When you classify an object, you use this characteristic to specify the color of the object.
Steps:
1. Enter Character Name using Create button.
2. In Basic Data Screen - Enter Description, Status, No. of Characters & multiple Values.
3. Go to Additional Data Screen - Enter Table Name, Field Name then choose tick Not ready for I/P.
4. Go to Values Screen - Enter Char. Value & Description.
5. Go to Restriction Screen - Enter Class Type.
6. Then go to Additional Data Screen remove the Tick of Not ready for input & save.
Class (CL02): Group of characteristics that can be attributed to a product. A class is a grouping of similar objects according to common characteristics.
Class Type: A class type is a top-level unit of control for classes. Each class must be allocated to exactly one class type. There is no connection between the individual class types.
Steps:
1. Enter Class Name & Choose Class type then Create using button.
2. In Basic Data Screen - Enter Description & Status.
3. Then nothing will be entered in keywords & Texts screens.
4. In Characteristic Screen u2013 Enter created characteristic then save.
Set Up Procedure with Classification (OMGQ):
1. Then go to Set Up Procedure with Classification
a. Release Group - Enter two char. (or) no. for Release Group, Class & Description then save.
b. Release Code u2013 Enter release group, Code Workflow & Description.
c. Release Indicator u2013 Nothing to enter.
d. Release Strategy u2013 Enter Release Group, Release Strategy, and Release Codes.
Release Prerequisite u2013 Choose order of release.
(ii) Release Status u2013 give continue.
(iii) Classification u2013 Enter the Value of Characteristics Description.
(iv) Release Simulation u2013 Double click and activate.
e. Workflow
Release with Link to Workflow:
Use
When you set up the release procedure with classification for purchase requisitions or purchase orders, you can define a link to the SAP Business Workflow. This is particularly advisable if employees whose daily duties include tasks other than the approval of requisitions or purchase orders are involved in the release procedure.
Features
The employee is automatically advised when a release is to be effected. A work item appears in his or her inbox, which he or she can process directly. When the item is processed, the SAP release transaction is automatically invoked with the relevant release code.
Then do PR in that Release Strategy will appear in both Item Level & Header Level. After that go to Release approval for Purchasing Document (ME28).
Release Group - The multiple usage of the same release strategy key.
Release Code
Two-character identifier with which a person responsible for processing a document can release (approve) an item of a purchase requisition, a complete purchase requisition, or a complete external purchasing document, or cancel such release (that is, revoke a previously granted approval). If a link to SAP Business Workflow has been defined for the release code, the person involved can also refuse to effect release (withhold approval), thus rejecting the relevant item or document.
Release Indicator
Shows the release (approval) status of a purchasing document.
When you have released (approved) an internal or external purchasing document with your release code, a release indicator is assigned to this document. The release indicator determines how the document may be processed further. For example, it may show that a requisition can be converted into a purchase order, or that a subsequent release point (individual or department) must first signify approval.
Release Strategy
The release strategy defines the approval process for purchase requisitions or external purchasing documents. The strategy specifies the release codes necessary and the sequence in which releases have to be effected. You can define a maximum of eight release codes.
The assignment of the release strategy to a requisition or a purchasing document is based on the release conditions.
Release Prerequisite
Specifies the sequence in which the processors (members of staff responsible for processing a certain document) must approve an internal or external purchasing document with their respective release codes.
Example:
The release (approval) procedure for purchase requisitions within an enterprise may provide that a department manager must release (approve) a requisition item before the next-higher level of authority (for example, the cost center manager). In this case, approval by the department manager is the prerequisite for approval by the cost center manager.
Release Status
Displaying the Release Status
You can display the release status of all items of a purchase requisition or the Complete Purchase Requisition in an overview. The overview shows whether each item or requisition has been released or is blocked, etc.
1. Display the item overview for the relevant purchase requisition.
2. Choose Goto Release info Release status.
A dialog box providing information on release statuses appears.
Displaying the Release Strategy
To display details pertaining to the release of an item or a complete requisition, proceed as follows:
1. Display the item overview for the relevant purchase requisition.
2. Select an item.
3. Choose Goto Release info Release strategy.
A box appears, giving you the following information:
1. Description of the release strategy
2. Previously effected releases involving the purchase requisition
3. All release codes with which the requisition must be released before it can be converted into an RFQ or a PO (final release)
If alternative release codes have been defined, the different ways in which this requisition item can achieve final release are shown.
Regards,
Kiran

PR Release by Item Not Triggering

Hi SAP Experts,
Went thru the forums on this release issue but could not seem to find the solution for my problem.
I've configured the release strategy for PR (to be released at item level). This PR is basically auto generated after the user entered a Sales Order when they changed the item category.
The following characteristic are being used for this specific class (which have been pre-created as this is being used for other release strategies).
Acct Assignment cat (CEBAN-KNTTP)
Item Cat in Purchasing Doc (CEBAN-PSTYP)
Document Type (CEBAN-BSART)
Plant (CEBAN-WERKS)
Creation Indicator (CEBAN-ESTKZ)
Total Value of item (CEBAN-GSWRT)
Material Group (CEBAN-MATKL)
Purchasing Group (CEBAN-EKGRP)
I have 2 different release strategies set up due to different levels of approval.
Strategy 1 - Department Manager (for value less than 100K)
Strategy 2 - Department Manager and General Manager (for value 100K and above)
As for the value of the classification, I did not specify all the characteristics.
Acct Assignment cat - Cost Center (K)
Item Cat in Purchasing Doc - blank
Document Type - ZRR (customized)
Plant - P101 to P110
Creation Indicator - blank
Total Value of item - based on the above criteria
Material Group - ZG1
Purchasing Group - ZGL
All values above are already ensured that they are allowed values, and I have assigned this release strategy in CL24N.
When I ran the simulation - the release strategy works fine as well.
However, when I wanted to do a test run by creating SO which leads to PR auto creation - the release strategy does not work.
It prompted a message of ME297 in the PR document. Tried to go to ME54N and it shows message MEPO822.
Thanks in advance.

hi,
Once check your relarse values in cl20n, cl30n,
in spro->Materials Management->Purchasing->Purchase Requisition->Release Procedure->Procedure with Classification->Set Up Procedure with Classification in that exigute and remove the over all release check mark.
and in
spro->Materials Management->Purchasing->Purchase Requisition->Define Document Types
in that do execute for your document type please remove the over all release tick and save.
Thanking you.

PR Release Strategies - Item Value & PR Value

I have this requirement from user. For marketing department, they want to release PR base on total PR value whereas Supply Chain want to release by item level.
I have created 2 classes and the only different is the characteristic whether to use PR value or PR item value. The other characteristic is CREATOR_USER_ID.
In release group for class with PR value, I have ticked the 'OverReqRel'.
Now the problem is that the one with PR item value work fine, but the PR Value is not working.
What could go wrong?

hi
you should have two release strategy.
combining the Creator Item Value one and
The creator and PR value one.

How to disable the link for Credit -check at item level

Hi Experts,
I have an issue tht we want to make a block to the link available for
credit-release at item level. In the view of the item, when we select the item
in edit view we have a button saying MORE and in tht we have CHEC CREDIT RELEASE.
We want to disable this.
I found tht if we made some changes in do_prepare method, we can solve this issue.,but i was
check fi anyother way we can do it.
Awaiting for the replies.
Thanks,
SA

Hey Saurabh,
If you dont want the functionality occurred due to that button, just simply comment the event handler code for that particular button. That will definitely help.
Let me know if that work.
Regards,
Shobhit

Process Controlled Workflow- Shopping Cart Item level approval

Hi experts,
In SRM 7.0 I have activated BC Set '/SAPSRM/C_SC_600_001_SP04' & I have implemented BADI '/SAPSRM/BD_WF_RESP_RESOLVER'.
My requirement is to send work item to WBS owner at item level.So the possible cases are 10 items will go for 10 approvers if they have 10 different WBS..
I have written logic to fetch WBS owner in method'GET_APPROVERS_BY_AREA_GUID' & assigning approvers to 'rt_approver'.
But the problem is all the approvers are assigned to all items.Rather it should be one item & corresponding WBS owner should be the approver.
Please suggest how I can achieve the required functionality.
Thank you.

Hi Masa,
I have used 'GET_AREA_TO_ITEM_MAP' only to export 'is_document-document_guid' from method '~GET_AREA_TO_ITEM_MAP' to 'GET_APPROVERS_BY_AREA_GUID'.
Can I use this method for mappping Items & approvers?
Please suggest.
Thank you.

Sales order status "Being processed" due to "Not referenced" in Item level.

Hi All,
I am facing with document status issue.
I have the following process,
1) Main contract (without line items )--> Yearly Contract-->Billing--> Renewal contract w.r.to First Year contract and this renewals will continue until the customer cancel the order.
Status will be as below,
Main Contract                   – No status ( Since, no item category referred in Copy control)
1 Year contract                 – Being processed.
1Year Billing                        - completed.
2nd year contract               – Being processed.
2nd Year Billing                    - completed.
Config settings:
In item category – Completion rule = C Item is completed after the target qty is fully referenced
In VTFA :In item level :
Billing qty = A     Order quantity less invoiced quantity
Pos./neg. quantity = +
Please advice to overcome this.
FYI:In contract line item --> status tab.

Hi Moazzam,
Thanks for the reply..
A is : Item is completed with the first reference. i will try with this but needs to check with the business if they have any partial qty might refer for Invoice.
But, as per existing config.
C - Item is completed after the target qty is fully referenced.
Which i am doing / referring for Invoice full qty. but i am getting " Not referenced" . Request to please make me understand the C functionality.- thanks.

PR Item Level Release WF not working after Release Strategy change

Hi Experts,
           I did PR item Level Release Standard Work flow and it was working fine now due to client requirement we changed the release strategy and now when the PR workflow triggers it gives the Below mentioned error.
I really don't understand y after changing the release strategy workflow is not working and giving the following error.
Even if i restart the workflow in SWPR the same error is occuring.
Exception occurred    - Error when starting work item 000000390118
PROCESS_NODE     - Error when processing node '0000000003' (ParForEach index 000000)
CREATE                   - Error when creating a component of type 'Step'
CREATE_VIA_WFM - Agent determination for step '0000000003' failed
EVALUATE_AGENT_VIA_RULE - Error in resolution of rule 'AC00000148' for step '0000000003'
AC00000148             - Object type 'TS' not valid
Executing flow work item   - Work item 000000390118: Object FLOWITEM method EXECUTE cannot        be executed
Executing flow work item   - Error when processing node '0000000003' (ParForEach index 000000)
Regards,
Hari

Hello Hari,
please set a breakpoint at function module
ME_REL_GET_RESPONSIBLE
and see what happends in section
    CASE t16fc-frgwf.
* keine Ermittlung
      WHEN space.
        RAISE nobody_found.
* Ermittlung über T16fW
      WHEN '1'.
If using the T16FW-table, it should go to '1', otherwise it may that a user exit under '9' is used. So please check this.
Best wishes,
Florin

PO and SchdAgreem Release Strategy at Item Level

Hello!!
I have the request to setup a the release strategy for the PO and Schedule agreements at line item level....
as far I know for PurReqs is possible to do that... but for PO and SAs it is only at header level...
Do you know if is possible to do that in configuration??

Hi,
Release strategy for PO & SA is only at Header level, since these documents are external purchase documents.
But, PR is internal purchase document and release strategy is possible at both item and header level.
i think, it is not possible to do release strategy at item level for PO & SA as you said,
Regards,
Srinu.K

Item level PO Release in ECC 6.0

Hi All,
It is possible to configure item level release strategy for PO ?
I am sure it is not possible till version 4.7 and you please advise whether it is possible with ECC 6.0 .
If so, can you please explain how can this be configured.
Gobinathan G

Hi
As per SAP release procedure are of two types.
With classification ( Item level and Header Level)
Without Classification ( Header Level only)
For PR which is internal document both release types are applicable but in case of PO which is external document release type without classification is allowed

PO Release process item level control

Similar Messages

Maybe you are looking for