Manual Pricing in SRM 4.0

[Former Member]

Since we upgraded our system from SRM 2.0 to SRM 4.0 and a price is manually entered, when the requisition gets created on the backend (R/3), the ‘Valuation’ tab will contain a “PO Price” field with <b>‘as gross price’</b> field populated to ‘1’. We are populating the price field so it is considered ‘manual’ pricing and therefore the requisistion gets created with a ‘PO Price’ indicator or ‘1’ and the info record/contract is ignored. Therefore, some of the PO`s are sent out with incorrect prices. Also, if the buyer does catch it, they cannot change it. What is the criteria for the AS GROSS price field to be triggered in R/3 and how do we shut it off????

[Former Member]

HI DON

I had faced the same problem where the PO used to take the SC price and ignore the contract price or Info record price.

WE then set the user parameters EVO abd EFB as 01 in R3 SU01 parameters where by the field where Gross price is default changes to "Do not adopt" as default.

by doing this the SC/ PR price is not picked in the PO and prefernce is given to Contract price first and if contract does not exits then Infor receod price is picked up.

try first with EVO and check in the PR field Gross price changes to DO not Adopt.

If EVO does not work then Add EFB .

Right now i dont have the system with me but either one of this paramenters change the price field and set indicator as "do not Adopt" after that probel is solved.

regards,

Nimish Sheth

Do reward points for helpful answers.

[Former Member]

Nimish, thanks!

From a role standpoint, who needs to have the EVO/EFB parameters set to 01? EBP shopping cart creators? Our purchasing buyers currently have the parameters set to 02. Please advise, thanks!!!

[Former Member]

HI DOn

All buyers should have 01 for parameters EFB.

See when ever you want that PR price should not be refered in PO. keep 01 for parameter EFB in user profiles.

Now what is 01 then go to SPRO --> Purchasing > Authorization Management> Define Function Authorizations for Buyers--> Function Authorizations --> select 01 and click on detail tab ->

there in General parameters put tick on option Order price adoption.

Secondly if you have a policy that PR price should never be taken into consideration and in absence of the Contract or info record buyer will enter the price manually. then in that case remove this tick above, then the field PO price will not appear at all and in absence of any price buyer will have to enter the price manually in PO. and PR price will never be copied to PO.

hope this closes the topic.

regards.

Nimish Sheth

Do reqards points for helpful answers,

[Former Member]

Nimish,

This "as gross price" is still an issue for us, any other ideas? How is this indicator invoked in the first place? Changing the parameters did not seem to "turn it off". Any help would be appreciated!

[Former Member]

Hello Don,

There are three prices you can set.

1. Gross Price

2. Net Price

3. Effective Price

for the items.If you have already set '1', try setting 0 or 2 and check whether it satisfies your goal.

please give points if i have answered your question.