Error in SLA in solman after pricing procedure is determined.

Hi
I have configured SLA in solman system.
I have created a service contract and for which i have give product and quantity. For this service contract pricing procedure and Item Category is determined successfully
But i am getting one error in header area::
Found no handler for remote function module SPC_GET_PRICING_PROCEDURE_INFO
Could any one provide me information on this.
Thanks in advance

Hi Guys,
I managed to resolve the probelm.
I am not sure if you were doing the same actions that I was to cause the error, ut here is what I did to reoslve it.
The issue is with the Item catergory. Go to "Define Item categories" in IMG. Open the Item category that you error transaction is using. In this item category you need to remove the "Pricing indicatior" you will find this on the thrid level of the item category.
This resovled the error for me. Try it out and let me know how it went.
Good Luck.
Regards,
Farhad.

Similar Messages

BAPI Error - Condition FS00 is missing in pricing procedure A V

ORDER_CONDITIONS_IN-ITM_NUMBER = '000010'.
ORDER_CONDITIONS_IN-COND_ST_NO = '10'.
ORDER_CONDITIONS_IN-COND_COUNT = '10'.
ORDER_CONDITIONS_IN-COND_TYPE = 'FS00'.
ORDER_CONDITIONS_IN-COND_VALUE = '20000'.
ORDER_CONDITIONS_IN-CURRENCY = 'KRW'.
ORDER_CONDITIONS_IN-COND_UNIT = 'EA'.
ORDER_CONDITIONS_IN-TAX_CODE = 'VA'.
ORDER_CONDITIONS_IN-ACCOUNTKEY = ''.
ORDER_CONDITIONS_INX-ITM_NUMBER = '000010'.
ORDER_CONDITIONS_IN-COND_ST_NO = '10'.
ORDER_CONDITIONS_IN-COND_COUNT = '10'.
ORDER_CONDITIONS_INX-COND_TYPE = 'FS00'.
ORDER_CONDITIONS_INX-UPDATEFLAG = 'U'.
ORDER_CONDITIONS_INx-COND_VALUE = 'X'.
ORDER_CONDITIONS_INx-CURRENCY = 'X'.
ORDER_CONDITIONS_INx-COND_UNIT = 'X'.
I'm trying to using the BAPI 'BAPI_SALESORDER_CREATEFROMDAT2'.
But, I cannot use it because of this message ' Condition FS00 is missing in pricing procedure A V'.
How can I solve this problem.
thank you for reading,
Best regards,
Jonghwan.

hi,
maintain the condition type in your pricing procedure
goto v/08
select your pricing procedure
maintain FS00 condition type in your pricing procedure
regards
senya

Pricing procedure not determined

HI
When i tried to create sales order with sales area lg11/lg/lg.I am getting the error that pricing procedure is not determined,because no entry with keys lg11/lg/lg 'a' 'v' exists in table 683v.
I am not able to move further. Can u pls help me.
Thanks&Regards
Prasad.G

Hi,
This is nothing but the problem in pricing determination.
Go to OVKK.
And maintain the required entries for your sales organisation, distribution channel, division, customer pricing procedure , document pricing procedure and the required pricing procedure that you want to get triggered when once enter this sales area with the other combinations.
Customer pricing procedure comes from customer master data .(sales area data sales tab) and document pricing procedure comes fromthe controls of order document(VOV8)
Mohan
Award points if it adds information.

Pricing Procedure - Account Determination

PO:
During price determination,
How does Condition type (example ZSPI), should post to GL# 123XXX.
-We want to create PO condition type for VAT which will post to perticular GL!
-where does Condition Type <> Account Key <> GL A/c# can be configured.!!
Suggestion pls..
Thanks
-SAM

Hai,
1.what is the Condition type ZSPI?.
2.Generally the Tax ( input purchases / output sales ) will flow from the Tax procedure. Net taxes on the PO is shown in the Pricing procedure.
3. Check the IMG -FInancial accting new - Financial Global settings - Tax on sales and purchases - Basic settings - Check calculation procedure - Define condition types - Define procedures. If the tax procedure is <b>TAXINJ,</b> then you have to maintain the % of taxes in the tax codes thro' - IMG - Financial Global settings - Tax on sales and purchases - Calculation - Define taxcodes for sales and purchases.
The condition type for VAT is JIP5 - A/P VAT RM ded, JIP6 - A/P VAT RM non-ded, JIP7 - A/P VAT CG ded, JIP8 - A/P VAT CG non-ded & the respective JP5,JP6,JP7 & JP8. This accural keys are assigned to GL accounts in the path - IMG -Logistics general - Tax on goods movements - India - Acct determination - Define GL accts for taxes. In this for the corresponding accurals / transactions - for your chart of accounts - you can assign GL accts to the condition types thro this accurals.in this JIP6 & JIP8 is described as a Non Deductible tax for RM & CG i.e., this tax values are loaded into the material acct.For your clarification check the IMG - FInancial accting new - Financial Global settings - Tax on sales and purchases - Basic settings - Check and change settings for tax processing - for the accural keys JP6 & JP8, it is flagged as a non deductible tax ( Details ).
4.If the Tax procedure is TAXINN, all the procedure are same as above said, only changes are you have to maintain the condition records to maintain the % rate of taxes VAT using the TCode FV11.
Hope the above said will help.

Error in Pricing Procedure Determination in Sales Order

Hi All,
I have created a Pricing Procedure and asiigned it with the SALES ORG, DIV, DISTR CHANL, CUSTOMER PRCDR and DOCUMENT PRCDR in SPRO.
i have assigned the Cust Doc Prcd with the BP and the Docuemnt Prcdr with the respective transaction. And also created the Basic Price for product and Discount Price for Sold To Party via CONDITION MAINTENANCE.
Still getting this error.
Looking for the solution.
Thanks,
VS

If you have check what RK suggested and is ok, then check also the customization of your transaction in spro>crm>transactions>basic settings>define transaction types.
go to your transaction type and then in left panel select customazing header. there check if you have defined under pricing data the doc.pric.proc. (document pricing procedure)
and also if you are not always using customer pricing procedure it is good to define in spro for determination of pricing procedure 1 determination rule which has filled only the folowing data:
- sales organization
- distribution channel
- document pricing procedure (the one you defined on transaction - which I described above)
- procedure
and division (if you use the dummy one) and customer pricing procedure leave empty. this way the procedure will be determined even if it's not found from customer sales data
And also be aware that once the error message for determination of pricing procedure appears it can't be removed so don't try the determination with already corrupted transaction.

Customer Pricing Procedure error

Hello Gurus,
While creating inquiry document in SAP SD I am getting error " Customer Pricing procedure not determined".
What to do?
Please Help

Hi,
Please follow the path as below:
Firstly you need to configure pricing procedure,
1) please go to spro>Sales and distribution>Basic functions>pricing>Prcing control>define and assign pricing procedures> maintain pricing procedure and assign your conditions there regarding of your procedure.
2) customer pricing procedure, and document pricing procedure have standard options. ı think you do not need to maintain new one for them. but you should assign your document procedure to order type and billing type from spro>Sales and distribution>Basic functions>pricing>Prcing control>define and assign pricing procedures> Assign document pricing procedures to order types and Assign document pricing procedures to billing types.
3) Moreover, you need to maintain determination for sales doc. as combination of your pricing procedure+ sales orgdistChdvdoc. pricing procedurecustomer pricing proc.+condition type from spro>Sales and distribution>Basic functions>pricing>Prcing control>define and assign pricing procedures>Define Pricing Procedure Determination.
Finally, maintain your condition records from VK11 regarding of your access sequence. and maintain customer pricing procedure to your customer master from sales area sales tab in customer master data from XD02.
Please check these configurations and I hope these will solve your problem.
Regards,

Pricing procedure determination error

Hi all!
We are facing with pricing error CRM_PRIDOC_COM 401
We use BT complaints without pricing determination procedure (we don't need them). We use common products without any problem or errors. But when we add complaint item with any product variant (from configuration products) we facing this error.
This is sap code error or error in customizing (but where?)?

Hi,
Did you checked pricing procedure determination?
Which is assigned SA+DPP+CPP=Pricing Procedure.
Then you can check in the GUI Create complaint and check required pricing procedure was determined or not. In the TABS.
Regards
Sudha Yadav

Customer pricing procedure is changed after creating order

Hi Gurus,
the issue is   we have created an order and pricing procedure is determined in the order. Now the user wants to get a new pricing procedure determined for this order. So he have changed the Customer pricing procedure in Customer master data. He assumed that new pricing procedure will be determined for the order which is already created. But it didnt happen. As per my knowledge pricing procedure canot be redetermined for already created orders. My question is
how to redetermine the pricing procedure for the order ? is there any way to get a new pricing procedure for the order in change mode?
what should we do. we need to delete the order and create a new one or is there any way to get the new pricing procudure for the order?

Hi ,
   basically pricing prodeure is determined by a combination of three things
       Doc pricing procedureCustomer Pricing proceduresales area .
   You can see this using transaction OVKK. So you have to consider all the three things.
In sales doc we have the option of updating the pricing. If you do that i think it will redetermine the procedure and your issue will be solved.
Thanks,
Shyam

Explain the Pricing Procedure

Hi Friends
Explain how the pricing is determined for an item, starting from the sales order
Discuss the full cycle also make a mention on the Condition type controls, and Maintain pricing procedure controls.
Kindly explain it with an example.
Thanks

Pricing Procedure is indeed an heart of SD module, reason being if everything else is working fine, but price is not being calculated correctly, the purpose of billing fails.
An Overview of Determination & Configuration of Pricing Procedure is as follows:
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Pricing Procedure --> Determine Pricing Procedure.
Step 5: Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.

Pricing procedure execution...

Hi Folks,
How SAP reads the pricing procedure..
Example
Con.Type      Requirement        Routine
ZSAA            601                     901
ZSAB            602                     902
Doubt 1: -Is system reads this pricing procedure line by line or coulmn by column?, In the debug we noticed it goes column by colmun? why?
Doubt 2: - I want to know the value found for ZSAA during the execution of 602 requirement. Example scenario is if ZSAA is more than 100$ don't execute ZSAB.

Pricing Procedure:
Determination of Pricing Procedure:
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure through T.Code: OVKK. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
Configuration of Pricing Procedure:
Step 1:
Condition table (T.Code: V/04): If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence (T.Code: V/07): If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type (T.Code: V/06): If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure (T.Code: V/08): It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure (T.Code: VOK0): After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record (T.Code: VK11 / VK12): Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc. Condition Record is maintained in T.Code: VK11 / VK12, which are captured in Sales Order & Billing.
Also check document pricing procedure in Sales Document Type (T.Code: VOV8 - Sales order Type, VOFA: Billing Type (If Required)), customer pricing procedure in Customer Master Data (T.Code: XD02), ... are in place.
Regards,
Rajesh Banka
Reward suitable points.

How to design a Pricing Procedure with both MWST and MWSI in it ?

Hi there.
My business requirement dictates that I can have both Tax inclusive(PR01/MWSI) and Tax Exclusive(PR00/MWST) items within a Single Sales Order.
I know that One pricing procedure can only be assigned to 1 Document Type. So,
Has anyone successfully created a Pricing Procedure that incorporates both the MWST and MWSI tax components ? If so, could you post a sample of the pricing procedure in order for me to understand how I should group the discounts/surcharges and reflect the Subtotals, as well as incorporate the MWST and MWSI all within a single Pricing Procedure ? I will also need to include the PR01 and PR00 conditions into the procedure too, right ?
Really really hope someone with the experience, can aid me on this. I cannot find any relevant materials on this matter, both in OSS Sapnotes and within this forum.
regards
Poo

In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
It is assumed that document pricing procedure, customer pricing procedure , ... are in place.
Similarly in MM Module we have Pricing Schema.
Regards,
Rajesh Banka
Reward points if helpful.

External Service Mangement Service Pricing Procedure not picking up in PO

Hi ,
We have an issue with External Services pricing procedure:
In SPRO->MM->External services Management->Maintain Conditions for Service
Have defined and assigned Schema for Services , but when I make a PO entry the pricing procedure is not picked.
I have maintined condition types , and defined schema procedure for services and there after have assigned service pricing procedure to document type for PO.
I get a message 'Conditions for service price determination incomplete'. And the conditions which are populated are from a different pricing procedure.
Please help me sort the issue.
Thanks

Hi,
This error triggers in case of own pricing procedure or changes to standard pricing procedure. Other reasons could be the price calculation schema is not set up for External Services Management or calculation schema not adopted from client 0 when system configured. Please refer following notes. Thanking you.
SAP Note No. 25357 MM-SRV: Error in the case of service conditions
SAP Note No. 27024 MM-SRV: Setting up components (services)

Pricing procedure in sap

hi
could any body tel me
pricing procedure in sap............

In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
It is assumed that document pricing procedure, customer pricing procedure , ... are in place.
Similarly in MM Module we have Pricing Schema.
Regards,
Rajesh Banka

Pricing procedure not determind

Hi Gurus,
I was creating a Sales order but i cannont save the sales order and getting a error message as
Pricing procedure not determined.
Please help.
Thanks,
Dardo

Hi Dardo
Check in OVAZ wheather the sales document type is assigned to the sales area or not . But , after creation of sales order if you are getting this error Pricing procedure not determined. then go to OVKK and maintain the data sales area + Cupp + Dupp =Pricing procedure and then check, if you are still getting error then maintain sales area + Cupp + - = Pricing procedure
Regards
Srinath

New pricing procedure for invoice correction

Hi ALL,
We want a new pricing procedure during invoice correction request.
Scenario:When we execute a sales order ,create a delivery & create a billing docuemnt with z@1111 a pricicng procedure.
Now we want to create an invoice coreection with different pricicng procedure Z@0002.
can any one help!!!
Regards,Rajneesh

Maintain a new Document Pricing Procedure in Invoice correction request. This will help in determining new pricing procedure based on assignment in T.Code: OVKK.
Pricing Procedure:
Determination of Pricing Procedure:
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure through T.Code: OVKK. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
Configuration of Pricing Procedure:
Step 1:
Condition table (T.Code: V/04): If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence (T.Code: V/07): If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type (T.Code: V/06): If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure (T.Code: V/08): It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure (T.Code: VOK0): After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record (T.Code: VK11 / VK12): Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc. Condition Record is maintained in T.Code: VK11 / VK12, which are captured in Sales Order & Billing.
Also check document pricing procedure in Sales Document Type (T.Code: VOV8 - Sales order Type, VOFA: Billing Type (If Required)), customer pricing procedure in Customer Master Data (T.Code: XD02), ... are in place.
Regards,
Rajesh Banka
Reward suitable points.

Error in SLA in solman after pricing procedure is determined.

Similar Messages

Maybe you are looking for