VA01 - Error determination for condition MWST

Hi experts,
I have a problem in the transaction VA01 since the system is determining the value of the condition MWST wrongly.
Material - Tax data:
Client - Tax data:
VK12 - MWST tax condition:
However, when I create the sales order the system determine the value of the MWST condition according to the values 0/0:
Why is it happening? How can I resolve this problem?
Thanks in advanced!!!!

Hi Lydia,
I think this is a problem due to the tax classification table field you have used in your access table.
There are " tax classification", "tax classification 2", tax classification 3" etc available for table fields.
these are to represent different tax categories you have in the master record. so for your case, in customer master the first tax category MWST will be represented by " tax classification" field, and second tax category "ZSDF" represented by tax classification 1" field.
Same goes for material master too.
Please check this and correct the access tables, if they are wrong
Regards
Jobi

Similar Messages

Account determination for condition type

Hi Guru,
I have requirement where I need to assign G/l account in VKOA for condition type used for discount and markup same time. I know I can aasign trade discount to this condition type but how about markup. can we assign two diffeent account to same condition type based on uses.
Thanks

This is pricing conditions not condition type like KOFI. The pricing condition are like base price, discount , markup, special custmer discount, ect. You can see these contions in sales order under condtion tab. My issue is there one condtion that user use some time for discount and some for mark up and requirement is when this condition is used for discount, it post to one account and if used for mark ,should go to different accoount. In VKOA sequence 501, we can only assign one account to one condition. if some one know how to assign two G/Ls to one condition .

Mandotory condition MWST is missing.

Dear friends,
I assigned pricing procedure to sales org., division etc. in test server. In test server I can create an order and everything goes fine. After I sent request to main server, I can not create order. SAP gives an error as : Mandotory condition MWST is missing.
In the VA01 screen, conditions tab; In main server there is no MWST condition type. But in the test server MWST is there.
But the pricing procedure is the same...
What can fix this issue??

Dear friends,
I maintained VK11 for MWST, sales doc, type. The problem has been solved.
Thanks,

Error in VF02 (Posting keys for account determination for transaction JTS)

Hi,
I have created new account key JTS and also assigned G/L account in VKOA, But at the time of releasing the billing document to accounting, I am getting the below error;
Posting keys for account determination for transaction JTS do not exist
Message no. F5598

Hi Amanulla,
once we create the Account key in revenue determination we have to assign that account key to respective procedure and condition types.
check that.
please award points.
ravikanth

Not possible to determine a condition type for the price in ME49

Hi,
While saving the price in ME49 i.e. comparision of Quotation i am getting below error:
Not possible to determine a condition type for the price
Message no. 06657
Diagnosis
When it attempted to generate the time-dependent conditions for the price you entered, the system was unable to determine a condition type. Price determination is therefore not possible.
Procedure
Contact your system administrator.
The latter can maintain the calculation schema assigned to the purchasing document using the Implementation Guide (IMG).
Utsav

Hi Utsav,
You can refer to the following link. it might be useful to you
RFQ price
Thanks
Nisha

Pricing error: Mandatory condition MWST is missing

Hi Every Body
While creating a sale Order i have enter two items when i double click on Meterial the following error appears.
Pricing error: Mandatory condition MWST is missing.I am using RVAA01 standard pricing procedure. what i have to do.
Thanks

Thanks for your respond. Actually i want to mantain the tax. when i enter the sale order and i and i click check item availbility Pricing error: Mandatory condition MWST is missing .
Then Logistics > sales and distribution>master data
>conditions>Change. there i select Taxes-->VAT/ATX1 click execute button. when i try to enter data in this the following error accor. i think upper error related with it. Tax code in procedure PKJTAX is invalid
please guide for mainting tax in sale order what should be the exact process.
Regards.
Rai Zeeshan

Pricing error: mandatory condition MWST missing

hai SAP experts,
while trying to create a sales order OR i am getting the error pricing error: mandatory condition MWST missing
please help to create the sales order.
thanks in advance
reddy

Hi Narayana
pricing error mandatory condition MWST is missing
there are two possible reasons
1) In your pricing procedure you have maintained MWST has ticked mandatory .
2) you have not maintained VK11 for this MWST condition type after ticking mandatory in your pricing procedure.
maintain VK11 for your MWST condition type and then create sales order with sales doc type OR.
another option is in MWST condition type details go to manual enteries can be changed there you can see manual entries feild as D change it C. .so that the time creation of sales order also if you get the same error you can enter manually. in emergency case
Reward points if useful
Regards
Srinath

Error: No vendor could be determined for article 124

Hi Friends,
I am getting an error" No vendor could be determined for article 124" while maintaing Sales view for article. I have given supply source as Standard in basic view and also maintained purchasing view. I entered this vendor in sales view, but error comes. Pl help to solve this.
Also, How price calculation is done in article master? I have give net price in PIR and add mark up 10% and how the system arrives at sales price. Pl help.
Regards,
Ram

Hi Ram,
Function in Pricing that enables you to calculate sales prices for the materials that are carried by a retail company in different steps of the value chain, and to store them as condition records in the system.
Calculating sales prices for materials is arranged according to the usual order of goods flow in retailing. Thus, the two main elements of sales price calculation are:
Determining purchase prices (purchase price determination)
Determining sales prices (sales price determination)
The margin is also calculated as a characteristic key figure for the relationship between sales and purchase price. Various different procedures are used for determining sales and purchase prices. The sales price can, for example, be calculated from the purchase price using a planned markup; it can, however, also be derived from competitor prices.
The sales price calculation function also allows mass maintenance of conditions. Sales price calculations can be performed for a range of materials and organizational levels. The different organizational levels here, for example stores and distribution centers, represent the various steps in the value chain
Source:help.sap.com
Also pl look into the following link:
http://help.sap.com/saphelp_45b/helpdata/en/12/085091470311d1894a0000e8323352/frameset.htm
Hope this helps you.
Regards,
S.V.ManiKumaar

Error "codepage could not be determined for the receiver-system"

Hi,
we use the idoc-adapter to send message from mySAP ERP to PI.
All worked fine.
So, this morning I have changed the datatype of the messageId from "char" to "int" in mySAP ERP in the customizing menue (install param). So, no message received in SAP PI.
When I start transction "we05" in mySAPERP" I get the following error:
"codepage could not be determined for the receiver-system" status 02.
I have changed the datatyp to "char" but the same probleme
Can anybody help me please?
Regards
Stefan

This error shouldn't occur unless there is some modification at the OS level codepages.
Please check the entried in the RFC destination for connecting to the XI system. Unicode settings.
Regards,
Prateek

Error :Maintain pricing conditions for the material for the excise invoice

Hi
i have maintained excise data for material, after that i have created scheduled agreement with lp and with 0 value private and dummy tax code and delivery schedule is released. Now when i do the goods receipt i am getting error " Maintain pricing conditions for the material for the excise invoice date
Message no. 8I629" can some body can help me.
with regards
Narendra kumar

Hi,
goto tcode fv11 u have to maintained the condition.
first enter the condition type like jmop -
then enter, next screen u have the select the below comination.
select the plant/vendor/material base u have to maintain the conditions.
Thank's
MVS

"Error determining planning periods for calendar " when running a program

Hi,
When i am running a program with date range say "01/05/2011" to "30/06/2011",the program is executing successfully without any error. When i am executing the same program with date range as a) "01/05/2009" to "30/06/2011" and b)"01/05/2008" to "30/06/2011" the program is failing with error as "Error determining planning periods for calendar". Can anyone suggest me what i should do to avoid the failure of the program with above date ranges also.
Thanks in advance,

Dear,
Error message 61123:"Error determining planning periods for calendar &".The PPC planning calendar specified in the material master MRP 2 view for the material is incorrectly.
The planning calendar periods are insufficiently maintained for the planning calendar used.
Check the period of planning calendar in MD26 and generate the correct period.You can avoid the problem in several ways:
Maintain the planning calendar far enough in the future (at least until beyond the end of the planning horizon).
Also check any demand is lies beyond the validity period of planning calendar.
Reduction of the planning horizon of MRP also can control such issue, as MRP planning horizon lies in an area in which the planning calendar is no longer maintained
Regards,
R.Brahmankar

Error message "No business area can be determined for item 000010"

Hi all,
I had maintained business area assignements.
However, while creating a sales order, the following error message appears : "No business area can be determined for item 000010"
What does it mean ? And how can I fix this problem ?
Regards,
Bahia.
Edited by: Bahia M. on Nov 13, 2008 11:58 AM

Dear Bahia,
Please go to IMG path assign the business area
IMG>Enterprise structure>Assignment>Sales and Distribution>Business Area Account Assignment-->Define Rules By Sales Area(Roule 1)
-->Assign Business Area To Plant And Division
I hope this will help you,
Regards,
Murali.

Error showing - No price could be determined for subcontracting in CK11N

Hi,
We are facing a problem in CK11N that while we are creating Material Cost Estimate with Quantity Structure, getting an error message..
No price could be determined for subcontracting
Message no. CK468
Diagnosis
The system could not calculate a price for the subcontracting because none of the valuation strategies in valuation variant 001 was successful.
System Response
If the system issues a warning message or an information message, the costing item is used in the cost estimate with a zero value.
If the system issues an error message, it sets the status "KF" (costed with errors).
If the system issues a termination message, the cost estimate cannot be processed.
Procedure
If you have authorization for Customizing, check the valuation strategy for subcontracting in valuation variant 001.
I read many thread already, but no solution is suit my requirement..
please help..

We run the transaction OPN2 and select 001- Planned valuation - mat. Valuation Variant. Db Click on it and select Subcontracting tab.
There Strategy Sequence is defined as under:
Priority......Strategy Sequence
1...............Effective price from Purchase Order
2...............Net Purchase Order price
3...............Effective price from Quotation
and in Quotation in Purchasing option, there is selected - Auto quota arrangement.
please guide.

Error Message : " No value could be determined for Customer Exit Variable "

Hello BI Experts ,
I have created a "ZYTD_PERIOD" Customer Exit Variable Interval Mandatory and ready for input check mark removed.
The reference character is '0FISCPER' .
I want to have YTD figures when the user enter single Fiscal Year Period for variable 0P_FPER.
So I have written below code in SE37 : EXIT_SAPLRRS0_001 and include program : ZXRSRU01
==================================================================
case i_vnam.
              WHEN 'ZYTD_PERIOD'.
              IF I_STEP = 2.
              LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGE WHERE VNAM = '0P_FPER'.
              CLEAR L_S_RANGE.
              L_S_RANGE-LOW0(4) = LOC_VAR_RANGE-LOW0(4).
              L_S_RANGE-LOW+4(3) = '001'.
              L_S_RANGE-HIGH = LOC_VAR_RANGE-LOW.
              L_S_RANGE-SIGN = 'I'.
              L_S_RANGE-OPT = 'BT'.
              APPEND L_S_RANGE TO E_T_RANGE.
              EXIT.
              ENDLOOP.
              ENDIF.
===================================================================
After that I use this 'ZYTD_PERIOD' variable in the query .
Also I have used the variable 0P_FPER in another structure.
When I execute the query by entering the value of 0P_FPER as 010.2009 or any other value ,
I am getting below error message ,
*No value could be determined for variable ZYTDPERIOD*_
Below is details of this Error message ,
Note that I have proper Master and Text data for 0CO_AREA and 0COMP_CODE loaded into BI.
=======================================================================
Diagnosis
This error diagnosis is specific only to the variables 0P_FVAEX or 0P_CTPCA !
Termination message BRAIN 632 appears:
Could not determine value for variable 0P_FVAEX (or 0P_CTPCA).
System Response
1. Operation method of SAP-Exit-Variables 0P_FVAEX or 0P_CTPCA
With queries from the CO application, both SAP-Exit-Variables look for an entry for 'controlling area'. With this controlling area from the selection screen, the SAP-Exit-Variables program reads the attributes for InfoObject 0CO_AREA (controlling area).
With queries from the FI application, the SAP Exit Variable 0P_FVAEX looks for an entry for 'company code'. With this company code from the selection screen, the SAP Exit Variables program reads the attributes for InfoObject 0COMP_CODE (Company Code).
0P_FVAEX determines the fiscal year variant (attribute 0FISCVARNT) from the attributes for 0CO_AREA (CO queries) or 0COMP_CODE (FI queries). 0P_CTPCA determines the currency type of the profit center local currency (attribute 0CURTP_PCA) from the attributes for 0CO_AREA.
2. Cause of Error
The attributes for the controlling area (InfoObject 0CO_AREA) or company code (InfoObject 0COMP_CODE) were not loaded into the BW system, or the attributes for the controlling area are not active in the BW system.
Check whether this is the cause of the error in your BW system. Display the contents of table /bi0/mco_area or /bi0/mcomp_code using transaction se16.
Application CO:
Check whether the attributes 'fiscal year variant' (field FISCVARNT) and 'profit center local currency currency type' (field CURTP_PCA) are filled in the 'A' version (field OBJVERS) for the selected controlling area. If the fiscal year variant in the OBJVERS = 'A' is empty, then the error is with variable 0P_FVAEX. If the currency type of the profit center's local currency in OBJVERS = 'A' is empty, then the error is with variable 0P_CTPCA.
Application FI:
Check whether or not the attribute 'fiscal year variant' (field FISCVARNT) is filled in the 'A' version (field OBJVERS) for the selected controlling area. If the fiscal year variant is empty in OBJVERS= 'A', then the error is with variable 0P_FVAEX.
Procedure
Using InfoSource 0CO_AREA, load the attributes for the controlling area or company code into your BW system.
Afterwards, activate the attribute changes in your BW system. To do this, use transaction rsa1, path 'Tools > Hierarchy/Attribute changes', functions button 'InfoObject list'. Choose InfoObject 0CO_AREA or 0COMP_CODE from this list, and activate the attribute changes.
=====================================================================================
Is there any special settings needed before writing BEx Customer Exit ?
I have already created a project in CMOD and assinged a proper RSR00001
and EXIT_SAPLRRS0_001 and project is active.
Any help please ....
Regards ,
Amol

My Code is as below ,
          case i_vnam.
              WHEN 'ZYTD_PERIOD'.
              IF I_STEP = 2.
              LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGE WHERE VNAM = '0P_FPER'.
              CLEAR L_S_RANGE.
              L_S_RANGE-LOW0(4) = LOC_VAR_RANGE-LOW0(4).
              L_S_RANGE-LOW+4(3) = '001'.
              L_S_RANGE-HIGH = LOC_VAR_RANGE-LOW.
              L_S_RANGE-SIGN = 'I'.
              L_S_RANGE-OPT = 'BT'.
              APPEND L_S_RANGE TO E_T_RANGE.
              EXIT.
              ENDLOOP.
              ENDIF.
              ENDCASE.

PY error message - EE's salary group could not be determined for Plan Life

We are running through Payroll errors when there is a Separation action being carried :
u201DEmployeeu2019s salary group could not be determined for plan LIFEu201D.
On IT0168 the costs are u20180u2019
This has to be resolved ASAP. Any inputs/ advise is greatly appreciated.

During the "Separation" action, does the employee change WT on IT0008?
If so, it could be that the Life Plan's Calculation Base does not include that WT (and check the IMG under Payroll > Benefits Integration > Define WageTypes for Benefit Plans)

VA01 - Error determination for condition MWST

Similar Messages

Maybe you are looking for