Standard Pricing Procedures not found

Hi Experts,
We have been migrating from ECC4.5 to ECC6.0, Now when i check the Standard Pricing Procedures in SPRO settings in Define Calculation Schema, I am not finding Lot of the default Standard Pricing Procedures which Usually appear in ECC6 of Fresh Installation. Could any one help me is there any Patches or Notes to be applied on that.
Advice your valuable inputs.
Best Regards
Javeed

i think you have to import from the client 000 or 001.
ask your basic consultant to create a user in this client and go to this client ,m/08 ,select the procedures and control data ,create Transport request via menu bar table view -- Transport and save . after that select all the condition types in that procedure and at the top you can see * include in the transport * ,include all selected entries and save .repeat for all the procedures.
goto your actual development client import it via SCC1 transaction
Same way you have to import all the condition types also in M/06

Similar Messages

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)

Whta is the standard pricing procedure in CIN INDIA

i want to take a standard pricing procedure ,so what is the standard pricing procedure in CIN INDIA
i want to include the condition like
<b>base price
maximum retailing price
customer discount
material discount
excise duty
VAT
educational cess
additional cess duty</b>
i want to know what should be the customer pricing procedure
and document pricing procedure

hi,
pl use TAXINN. Remaining as usual.
TAXINJ & TAXINN are Tax Procedures in India. TAXINJ is old version & TAX INN is new version. Both has its own advantage & disadvantage.
Upto 4.6C & partially 4.7 version of SAP, TAXINJ was used. TAXINJ is formula based calculation, in which we maintain the tax rate in Tax Code itself. The implication is that if say we are having product range such that say Excise rate differes for separate chapter ID, VAT, CST & permutation & combination of these, we require that many Tax Codes. For example:
Tax Code: A1
Taxes: 16% Excise Duty + 2% Education Cess + 12% VAT
Tax Code: A2
Taxes: 16% Excise Duty + 2% Education Cess + 8% VAT
Tax Code: A3
Taxes: 12% Excise Duty + 2% Education Cess + 12% VAT
Tax Code: A3
Taxes: 12% Excise Duty + 2% Education Cess + 8% VAT
From 4.7 version onwards of SAP, TAXINN is being recommended & used. TAXINN is more user friendly & condition record based. In TAXINN, Tax Codes are statistical & of not much relevance, but are required to be maintained in condition record for taxes condition type. This makes Tax Codes simpler. The implication is that if say we are having product range such that say Excise rate differes for separate chapter ID, VAT, CST, we need not have the tax codes to that combination. For example:
Tax Code: A1
Can be used for any rate of excise duty, as tax code is only required to be maintained statistically in condition record.
Tax Code: A2
Can be used for any rate of VAT, as tax code is only required to be maintained statistically in condition record.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
Select Tax Calculation Procedure
Use
In this IMG activity, you specify which tax procedure you want to use for determining excise duties and sales taxes on input materials in India.
If you use condition-based excise determination, use a copy of the tax procedure TAXINN.
If you use formula-based excise determination, use a copy of the tax procedure TAXINJ.
This tax procedure also supports condition-based excise determination, so that you can work with both concurrently.
We strongly recommend that new customers use condition-based excise determination. Note that once you have started using a tax procedure, you cannot switch to another one, otherwise you will not be able to display old documents.
Maintain Excise Defaults
Use
In this IMG activity, you define which tax procedure and pricing condition types are used in calculating excise taxes using formula-based excise determination.
Activities
If you use condition-based excise determination, fill out the CVD cond. field and leave all the others blank.
If you use formula-based excise determination, fill out all of the fields as follows:
Enter the tax procedure and the pricing conditions that are relevant for excise tax processing.
Specify the purchasing and sales conditions types used for basic excise duty, additional excise duty, special excise duty, and cess.
Specify the conditions in the sales order that are used for excise rates.
Specify the countervailing duty condition type used for import purchase orders.
Regards,
Rajesh Banka
Reward points if helpful.
Rajesh Banka
Posts: 1,308
Questions: 7
Registered: 11/21/06
Forum points: 1,800
   Re: Taxinn tax procedure settings in SD pricing
Posted: May 6, 2007 11:34 AM    in response to: Sunil Kumar Garg       Reply      E-mail this post
Impact on Pricing Procedure & Condition Record:
Another Important difference between TAXINJ & TAXINN is that in TAXINJ along with formula in Tax Code, you also have to maintain condition record & there are 2 condition types for Basic Excise duty & similarly other excise duties. in one condition you maintain the actual excise duty % & in other you main as 100%, which will be a copy of actual excise duty. But in TAXINN, instead of 2, you require to maintain only one condition type for each excise dity like JEXP for Basic Excise duty & similarly for other excise duties. You require to design pricing procedure accordingly.
source forum thread :
<a href="https://forums.sdn.sap.com/click.jspa?searchID=2814520&messageID=3397693">source thread</a>
thanks.
Sadhu Kishore

How to include taxes in the standard pricing procedure

Dear All,
I have configured the Ecc 6.0 version.i have used standard pricing procedure
Rvaa001 as my pricing procedure. i am able to invoice and post the same to the accounts document when i use PR00 condition type.Now i want to include taxes
to sales order.How should i include the taxes.Country is india and the standard
conditions that are given JTX1,JTX2,JTX3,JTX4 are for taxes for india.how i should
include these for my pricing procedure.I also need to include Vat, service tax apart from 50%of gross value tax etc.kindly guide me to include these in my pricing procedures.
Plaese guide me to accopmplish these tasks.
Award points are assured for timely support.
Thanking you
Best Regards,
R.Srinivasan

Instead of RVAA01, try the pricing procedures as under, which will have most tax conditions, as per Indian Environmemt.
JDEPOT     IN:Depot sale with formula
JEXPOR     IN:Export sales with formula
JFACT     IN:Factory sale with formula
JINDEP     IN:Depot sale
JINEXP     IN:Exports
JINFAC     IN:Factory sale
JINSTO     IN:stock transfer
JSTKTR     IN:Stock transfer with formula
Hope this helps you.
Regards,
Rajesh Banka
Reward suitable points.

Stored procedure not found when creating a new recordset binding in Dreamweaver CS6 with ColdFusion Server 11

Stored procedure not found when creating a new recordset binding in Dreamweaver CS6 with ColdFusion Server 11. I can see the tables and views in the database tab, but no stored procedures. If I connect to a data source created in ColdFusion Server 6 I am able to see the stored procedures.

Ben thanks for the reply!
Yes that is the process I am following:
In Dreamweaver, open the page that will run the stored procedure.
In the Bindings panel (Window > Bindings), click the Plus button, and then select Stored Procedure.
In the Data Source pop‑up menu, select a connection to the database containing the stored procedure
Enter the ColdFusion Data Source user name and password.
At this point in the procedure drop down I would get a message that said No Stored Procedure Found.
Right now it appears to be working, I had to create a new site that pointed to the older CF 6 server's data source and create a page following the process above, then when I went back to the CF 11 site the stored procedures were now populated. I need to make sure it is pulling from the correct server but right now it appears to be working.
Thanks
Dwight

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

Standard Pricing Procedure Control Options

Hi,
Need to know the use of columns in control tab of the pricing procedure like: counter, From & To with an example.
Say i have 10 - 100 steps ....
In the 50th step i have From as 10 and To as 40......what will happen for the 50 th step condition value....Also, in the 50 th step you have condition type and condition records are maintained.......
Regards

Hi,
Hope the below reply helps you.
Step:
Number that determines the sequence of the conditions with in a procedure.
It indicates the position of the condition type in pricing procedure.
Ex.: 10, 15 etc.
Counter:
System uses the counter to count the steps and also it can be used to count mini steps of same condition types. So that number of steps can be reduced in the pricing procedure and hence enhancing the system performance.
Access number of the conditions with in a step in the pricing procedure.
During automatic pricing, the system takes into account the sequence specified by the counter.
Condition Type:
It represents pricing element in pricing procedure as a base price, discount, freight and tax.
The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.
Ex.: PR00 - Price
K004 - Material Discount
K005 - Customer/Material Discount
K007 - Customer Discount.
Description:
System copies description of condition type from its description (V/06).
From and To:
1. From: This can be used as a base to the condition type for calculating further value.
2. From and To: The range between the steps from and to can be used to specify the range between same condition types. So that depending upon the condition type, the system deducts or adds the total value of those condition types from specific common source.
Manual:
This indicator specifies whether the specific condition type can be determined manually during sales order processing.
If we check the box then the entry is going to be manual, if we uncheck it, it is going to be automatic.
For Base Price and Taxes, the entry should be automatic.
For Discounts and Freights, The entry should be manual.
If we check the box, in VA01 when we go to conditions at the header/item level, the condition type will not be listed. If we require we will have to manually enter it.
If we uncheck the box, in VA01 when we go to conditions at the header/item level, the condition type will be listed.
Mandatory:
This indicator specifies that particular condition type is mandatory in the pricing procedure.
If we check the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will not allow us to do it and throws an error.
If we uncheck the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will allow us to save it, without giving any error.
Mandatory check box should be checked in condition types which are compulsorily required in pricing procedure. Ex.: PR00, MWST.
If the condition type is checked with mandatory option, then value should be maintained for that condition type, otherwise the system will not allow the user to process the document.
Statistical:
This indicator if it is activated will not allow the value of the condition type to be taken into net value calculation.
It is used only for information purposes only.
This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value).
This is commonly used for condition types
SKTO - Cash Discount
VPRS - Cost (Moving average price/Standard Price).
Print:
The value of this field specifies whether line item can be printed or not in the sales document and at what level it is to be printed.
Subtotal:
The value of this field determines where the values of subtotals to be captured i.e. in which table and which field.
Controls whether and in which fields condition amounts or subtotals (for example, a customer discount or the cost of a material) are stored.
If the same fields are used to store different condition amounts, the system totals the individual amounts.
These condition amounts or subtotals are used as a starting point for further calculations. You may, for example, want a subtotal of all the discounts included in the pricing of a sales order.
Requirement:
It is a routine that is written by an ABAP consultant according to the business requirement.
By defining Requirement in condition technique we can restrict the access of condition type.
To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).
For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".
This Requirement will ensure that these condition types will appear only during the billing document processing.
If new Requirements are to be defined we follow the procedure given below.
Go to T.Code: VOFM. - Maintain Requirements & Formulas
Click on the "Requirements" in the top menu and then click on "pricing".
We have a list of requirements, we can ask ABAP consultant to create new requirement based on the client requests.
And we assign the application type like V - Sales/Distribution etc.
AltCty - Condition formula for alternative calculation type:
It is again a Routine that is written by ABAP Consultant.
It is an alternative formula for the condition type that can be used instead of standard formulas.
For example, let us take the Profit Margin which can be both + / - , so here this routine will help us in generating the value which can be either + or -. Profit margin is not a condition type so it cannot be classified as +ve or -ve in the V/06.
Ex.: 950 0 Profit Margin 11.
So we assign 11 - Profit Margin.
If new routines are to be defined we follow the procedure given below.
Go to T.Code: VOFM. - Maintain Requirements & Formulas
Click on the "Formulas" and then on the "Condition Values".
We have a list of routines, we can ask ABAP consultant to create new routines based on the client requests.
And we assign the application type.
AltCBV - Alternative formula for condition base value:
Formula for determining the condition basis as an alternative to the standard.
It is again a Routine that is written by ABAP Consultant.
It is used as a basis to calculate value of the condition type instead of using it from the "FROM" column.
Ex.: Freight - KF00.
Freight is calculated based on weight, volume etc. and not on the base price. In pricing there is no entry of weight from which the value can be referred like we do for discounts using base price. We have to get the value from the Material master.
In this column we can mention the value as 12 - Gross Weight or 13 - Net Weight.
During pricing, the system will consider the value that is mentioned in this column and determine the freight based on this value.
Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. And if we mention 13 in this column then the Freight condition KF00 will be calculated using the weight as 100 kgs.
AcyKy - Account Key/ Accrls - Accruals:
The values of the Sales Revenues, Sales Deductions, Freight Revenues, Tax Revenues, and Rebate Accruals etc. are going to be posted in the respective G/L accounts in Fi Module.
In order to do this we assign account keys/ accruals to the different condition types based on their classification. The classification shown below.
ERB Rebate sales deduct.
ERF Freight revenue
ERL Revenue
ERS Sales deductions
ERU Rebate accruals
For Ex.,
For all Price condition types like PR00 etc. we assign ERL - Revenue.
For all Discount condition types like K004, K005 etc. we assign ERS - Sales Deductions.
For all Freight condition types KF00 etc. we assign ERF - Freight Revenues.
For all Rebates condition types BO01 to BO05 we assign in Account key ERB - Rebates Sales deductions and for Accruals ERU - Rebate Accruals.
This account keys and accruals are in turn assigned to respective G/L accounts. So the system posts respective values in respective G/L accounts in Fi-Co Module.
This also one of the areas of SD - Fi Integration. SD consultants assign the account keys and Fi Consultants assign the respective G/L accounts in T.Code:VKOA.

I would like to convert a matlab file into a .dll and use it in LabVIEW. However, when I run the .dll in LabVIEW I get an error stating "... Procedure not found". What could this be? Can anyone help me...

I wish to convert my Matlab files into .dll's so that I can use them in LabVIEW. I am using 'mcc' and 'mbuild' of Matlab to convert my .m files into .c and .dll.
When I try to run the .dll's in LabVIEW, I get an error message in a modal window stating some required .dll or procedure is not found.
How should I resolve this issue. Should I add any other Matlab .dll's in course of making my .dll?
Please help in solving this issue... Thankyou very much.

KJV wrote in message news:<[email protected]>...
> When I run the matlab generated dll, it is stating 'matllb.dll not
> found'. Is it that I should set the path for matlab\bin to include
> all the dll's before I compile? When I make dll from C, it works fine
> in LabVIEW. The problem is from .m to .dll. The problem also arises
> when I convert my .m to .exe. The same error of 'matllb.dll not
> found' comes over. Should I change my matlab compiler options or
> something else? Please help me?
I have the same question,I don't know how to use the matlab DLL file in labview,
I hope someone can descripe the procedure in detail.

Pricing procedure not getting determined in sales order

Hi All
I have did all the configuration settings for determining the pricing procedure in the sales order,but it is not getting in the order.
The assignment sales area + customer pricing procedure + document pricing procedure are fine
And in the customer master the customer pricing procedure is maintained properly
And in document type TA,the document pricing procedure is maintained properly.
Without IPC is it not possible to get the prcing procedure of CRM in to the sales transaction.
I dont have IPC installed on my system.
Appreciate ur help
Regards
Sreekar M

Thanks Shalini for the information
Then i think i cant create a billing document in CRM with reference to sales order...as the sales order is incomplete
Is creation of delivery possible in CRM?
Regards
Sreekar M

Pricing procedure not showing up in Inquiry

Hi All,
I have developed a very simple pricing procedure for inquiry. It has only one condition type i.e. PR00. I just want to enter price to update the value of inquiry on saving. It works fine if i mention material ode in inquiry, but if i do not mention material code and enter qunatity with some description, then the condtion type PR00 does not show up in the conditions TAB. How can i record my inquiry with quantity and amount for text items.
SAPXPT

I suggest you ask this question in an SD forum, this here is about technical questions running a SAP system on SQL Server.
Markus

Pricing procedure not to bill customer but revenue recognition

I'm looking for guidance on how to setup a pricing procedure conditions. First let me explain the situation. What happens is the customer buys say 2000 software licenses on a sales order. The customer is billed and the customer account is debited and a deferred account is credited. Now the customer activates one of the licenses. The pricing from the sales order is copied to a contract. This contract has a start and end date for the license. Now that license can start to be recognized based on the period of the line item contract dates.. The issue we have is that normally for deferred revenue billing takes places. Problem is customer was already billing on the sales order. Somehow the pricing procure has to credit the deferred account that was posted on the sales order and then credit the revenue recognition account that can be used by transaction VF44.
So on the invoice associated with the sales order Invoice from sales order
Dr Customer $1000
Cr 2370 $1000
The account 2370 is the deferred account. This part is fine.
Now we activate 1 of the licenses.
So the pricing procedure has to do the following with no billing to the custo0mer account Invoice from contract
Dr 2370 $120
Cr 2371 $120
This is the problem part. crediting the deferred account 2370 and then posting into the revenue recognition account 2371
Rev Rec – VF44 for Period1
Dr 2371 $10 Cr 4340 $10 Any ideas would be appreciated

Hi
In SD billing documents customer is always debited or credited based on nature of transaction. For posting in two different G/Ls instead of customer account there is only one possible way which I know. In free goods pricing system can post debit and credit entries to different G/Ls and these G/Ls are controlled through account keys which you assign to condition types in pricing procedure.
Do you have any Idea of free goods pricing and its posting? Explore this and give it a try. I am not sure about this because I didn't test this. You can test and see if it helps.
In this for contract item category you have to use free goods pricing which you set in item category settings in VOV7.
Thank$

Generated Forms does not compile - NEXT ITEM and PREVIOUS ITEM procedure not found

I tried to generate forms using Designer 6i.
FMB was created, but there are compilation errors.
The Compiler can not found procedures called CGNEXTITEM and CGPREVIOUSITEM.
Judging by the names, those procedures are supposed to be generated by designer as well,
but there are no codes with the names.
Any idea?
Yusan

Is your temporary table created with the clause "on commit preserve rows" or "on commit delete rows"?
If it's the latter then try changing to the former as you have a commit in the middle of your code, doing this will keep the data in the table for the duration of the session.
If you need to clear the table of data within your session, you'll have to do an explicit delete.
Ady

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.

Procedure not found error

Hi.
I'm trying to run a test program(C program) on Timesten and getting an error like below.
SQLERR [SQLExecute: st_no_sp] : 7005 [TimesTen][TimesTen 11.2.1.2.0 ODBC Driver][TimesTen]TT7005: Procedure `SP_CREATE_ORDER' not found -- file "saCanon.c", lineno 5763, procedure "ppCall"
and here is a some part of the code
SQLLEN len;
SQLCHAR q_no_sp[256];
SQLHSTMT st_no_sp=SQL_NULL_HSTMT;
sprintf((char*)q_no_sp,"CALL sp_create_order(?,?,?,?,?,?,?,?,?,?,?)");
len = SQL_NTS;
rc = SQLBindParameter(st_no_sp, 1, SQL_PARAM_INPUT, SQL_C_SSHORT, SQL_SMALLINT, 0, 0, &w_id, 0, &len);
if (rc != SQL_SUCCESS) Error(st_no_sp, "SQLBindParameter");
rc = SQLBindParameter(st_no_sp, 11, SQL_PARAM_INPUT_OUTPUT, SQL_C_SLONG, SQL_INTEGER, 0, 0, &o_id, 0, &len);
if (rc != SQL_SUCCESS) Error(st_no_sp, "SQLBindParameter ");
//rc = SQLExecute(st_no_sp);
rc = SQLExecDirect(st_no_sp, (SQLCHAR *)q_no_sp, SQL_NTS);
if(rc!=SQL_SUCCESS){Error(st_no_sp,"SQLExecute: st_no_sp");}
anybody knows why I'm gettint the error?

Thank you for your reply.
but I'm getting the another error like below :
SQLERR [SQLExecute:st_pay_sp_name ] : 8508 [TimesTen][TimesTen 11.2.1.2.0 ODBC Driver][TimesTen]TT8508: Question mark parameter markers are not allowed in PL/SQL blocks -- file "ptSqlL.l", lineno 2458, procedure "lex question mark parameter"
sprintf((char*)q_no_sp,"begin sp_create_order(?,?,?,?,?,?,?,?,?,?,?); end;");
rc = SQLPrepare(st_no_sp, q_no_sp ,SQL_NTS);
if(rc!=SQL_SUCCESS){Error(st_no_sp,"SQLPrepare: st_no_sp");}
len = SQL_NTS;
rc = SQLBindParameter(st_no_sp, 1, SQL_PARAM_INPUT, SQL_C_SSHORT, SQL_SMALLINT, 0, 0, &w_id, 0, &len);
if (rc != SQL_SUCCESS) Error(st_no_sp, "SQLBindParameter");
rc = SQLBindParameter(st_no_sp, 11, SQL_PARAM_INPUT_OUTPUT, SQL_C_SLONG, SQL_INTEGER, 0, 0, &o_id, 0, &len);
if (rc != SQL_SUCCESS) Error(st_no_sp, "SQLBindParameter ");
//rc = SQLExecute(st_no_sp);
rc = SQLExecDirect(st_no_sp, (SQLCHAR *)q_no_sp, SQL_NTS);
if(rc!=SQL_SUCCESS){Error(st_no_sp,"SQLExecute: st_no_sp");}
I guess that begin procedure statement executes with ? marks before prepare, bind and execute..
any suggestions?

Invoice pricing procedure not using alt calc type from the pricing procedur

The sales order has the same pricing procedure as the invoice but when the invoice is created it is not using the alt calc type that is on the pricing procured like it is on the sales order. This is causing one of the condition types to have different values on the sales order vs. invoice.
I am not sure what other areas to check to see why this is happening. Any thoughts?

I have checked and in the copy controls for Delv type = LF and target Bill type = F2 the Pricing Type = G (copy pricing elements unchanged and redetermine taxes). Condition types such as ZPR2 where there is condition record copy in correctly to the invoice. It is condition type ZZIF where it is determined from a routine, not a condition record, where I am having this issue.
Is there another place in config that I should be making a setting so that condition types determined by routines are copied to the invoice without being redetermined at invoice create?

Standard Pricing Procedures not found

Similar Messages

Maybe you are looking for