cancel
Showing results for 
Search instead for 
Did you mean: 

condition type only one time

Former Member
0 Kudos

Hi ,

In pricing procedure there is a manual condition type.Now the user can do entry for this condition type more than one time for the line item.If i want to stop that by the user ,what should i do . Only requirement in the pricing procedure, is the option or there is anything else in the standard SAP ..Please suggest .

Thanks ,

Abhijit.

Accepted Solutions (0)

Answers (2)

Answers (2)

Lakshmipathi
Active Contributor
0 Kudos

Dear Abhijit

I think by two methods you can control this.

1) With the help of your basis team, prevent authorization for VA02

2) By applying User Exit mv45afzv, you can prevent the respective users not to change the condition value in VA02.

thanks

G. Lakshmipathi

Former Member
0 Kudos

but then dear G. Lakshmipathi, user can give same condition while creating PO only

and if you prevent authorization for VA02 then how can end user will be able to change other data in PO, if required?

Lakshmipathi
Active Contributor
0 Kudos

Dear Vishal

I believe Abhijit's requirement is from SD point of view whereas you are talking about MM point of view.

Abhijit's question is

"Now the user can do entry for this condition type more than one time for the line item.If i want to stop that by the user ,what should i do".

So I feel that I had answered to the question as explained above.

Moreover, I feel that the maximum number of changes in any document happens only in change mode rather in creation mode and in that case, both my suggestion will work. Of course only Abhijit has to decide whether these suggestions can be considered or not as he is the best judge after studying the client's process.

To answer your question

"how can end user will be able to change other data",

as suggested above, through user exit, you can very well control making changes of any particular field which ABABers can do that.

Hope to have explained fairly to your question.

thanks

G. Lakshmipathi

Former Member
0 Kudos

thanks for correcting me. but then also i ahve seen end users giving price many times while creating PO only so better to maintain PURCHASE INFO RECORD b'coz then though user will give price again n again but net amount will be calculated based on price mentained in purchase info record n more over is there are any changes user can change the price

Former Member
0 Kudos

dear abhijit,

I have faced same problem and for this a solution is to maintain purchase infor record.

like you must be purchasing article from different vendors then you can maintain the different purchasing price for different vendor

Purchasing info records determine the prices suggested in purchasing documents in two ways:

The system,

• 1st searches under POrg. Data 1 - Conditions:

Conditions are included if they have been maintained for an info record manually or from a quotation (but can be changed manually afterwards)

• 2nd searches under POrg. Data 2 – Last Purch Doc.:

If an info record does not contain any conditions (under POrg. Data 1), the system reads the number of the last purchasing document in the info record and then suggests the price from this document.

‘Info Update’ indicator for Conditions (in PO, RFQ/Quotation, Contract) :

• for PO – the update occurs in POrg Data 2 (last purch doc)

• for RFQ/Quotation - the update occurs at POrg Data 1 – Conditions (can be changed manually afterwards) and POrg Data 2.

• for Contract – the update occurs at POrg Data 1 - Conditions, IF at the time of the contract creation there is No info rec. Otherwise the info rec is updated with the last release order under POrg. Data 2.

but please note that the final price will get calculated on one condiition only and not on others.

regards,

Vishal

Edited by: Vishal Jajoo on Feb 19, 2008 2:16 PM