Condition types MWSI and MWVO for TAXES

Hi,
I am trying to create the new condition types MWSI, MWVO and accounting keys SIV, SIO for new tax keys (TAXES) for the report RFIDESM340. I didnu2019t find any instruction about the parameters behind MWS and MWVO.
Can someone advise me on this?
Thanks and Regards,
Detlef
Edited by: Detlef Weiss on Mar 15, 2010 1:06 PM

Dear,
The difference between pricing conditions PB00 and PBXX is :
PB00- automatic pricing - can be used for automatic pricing determination
PBXX- manual pricing - used for manual pricing.
When you maintain the pricing condition for the PO, the system will look at the available condition records (for PB00) and make the automatic pricing determination. In case, such condition records were not defined, then it is mandatory that you have to maintain manually the pricing condition where PBXX will be automatically defaulted in replacement for PB00.
Regards,
Syed Hussain.

Similar Messages

Condition type SKTO and SKTV

Hi all,
I wanna ask how the system determine whether use condition type SKTV or SKTO. I know the value is based on term of payment, the case is i do the same think with term of payment in 2 different client, but the result is different, one using condition type SKTV and SKTO for the other one. how is it work? can anybody help me
Thanks
Regard,
Hendry

Hi,
SKTV calculates cash discount before tax
SKTO calculates cash discount after tax
the formulae and configuration are the same.
difference is the requirement in pricing procedure. SKTV is picked before tax, while SKTO is after tax.
you can pay attention to the requirement in both pricing procedures in different clients...
Thanks!

Condition type EDI1 and EDI2

Dear all,
we have to a requisition that we will receive confirmations of order (ORDRSP) from our suppliers in the future.
In OSS note 456127 (FAQ EDI MM) question 14 it says that prices will only overtaken in the purchase order,
if the condition types EDI1 and EDI2 are part of the calculation schema.
In our calculation schema we do not use EDI1 and EDI2 so far.
I can not find a manual that says what to do.
RM0000 does not contain these two condition types either.
In which way do we have to add EDI1 and EDI2 to our calculation schema?
Thank you for your help in advance!

Check these Schemas
RM2000 - STO scenarios
RMMP00 - Market Price Scenarios
Define Calculation Schema
In this step, you define the calculation schemas.
In the MM area, a calculation schema - a framework of steps used to calculate or determine something - is used among other things to calculate costs, prices, period-end rebates, and taxes.
Note
This concept is referred to in the Sales and Distribution (SD) area as a pricing procedure.
In the calculation schema (pricing procedure), you specify which condition types are to be taken into account in which sequence.
In the price (or cost) determination process, the SAP System automatically determines which calculation schema is valid for a business transaction and takes into account, one after another, the condition types it contains.
Standard settings
The following calculation schemas are predefined in the standard system. You should not change these schemas.
RM0000 and RM1000
Control the price determination process in POs, quotations, and scheduling agreements.
Both calculation schemas require 2 condition types for the gross price: one for automatic price determination (standard: PB00) and one for manual maintenance (standard: PBXX).
RM0001 and RM1001
Determine which condition types you can enter in purchasing document headers with time-dependent conditions (e.g. contracts).
RM0002, RM1002
Determine which additional condition types you can enter in purchasing document items with time-dependent conditions or in the purchasing info record.
RMMP00
Defines the condition type for determining the market price which can be entered for each material.
RM2000
Controls the delivery cost determination process in stock transport orders and stock transport scheduling agreements.
Note
In the calculation schemas RM0000, RM1000, RM0001, and RM1001, the field "Subtotal" must contain the following values in the following lines:
Gross value: 9
Effective value: S
If the interim total 'S' is not set, the PO values cannot be updated in the Purchasing Information System (PURCHIS).
Actions
1. Check to what extent you can use the calculation schemas provided in the standard SAP System.
2. Create new calculation schemas by copying similar existing ones and changing them.
Enter a key (length max. six characters) for the schema you wish to create, and a descriptive text.
For each schema, specify the condition types in the order of their usage, and maintain the relevant data.

Condition type PB00 and PBXX, coming in the same PO Item

Hi,
In the PO (created with reference to Outline Agreement), condition types PB00 and PBXX are coming in the same line item.
In the PO output, the PB00 value is also showing up and PBXX value is also showing up. User entered PBXX value as 350000 dollars which is right, however system is picking 1.2 million dollar of PB00 from outline agreement which is not intended here. As a result of that the output going to Vendor is exceeding more than 1.2 million dollar instead of 350,000 dollars. I cannot change or delete any othe condition types.THis is a production problem.
Has anyone faced this problem. I appreciate your reply in advance.
Thanks,

Well, thanks Saurav and Prabhakaran, however the problem still stays.
The contract is created for services (1 lot), so the dollar amount can vary depending upon the service rendered by the consultant.
That mean user will only enter the service amount.
Saurav, system should not copy down PB00, it should come by itself when user enters the specific amount. And it comes from contract. PBXX should only appear if there is no PB00 maintained in the contract. This is not the case. The service amount is maintained in the contract. Also, I don't think that PBXX and PB00 should come in one line item together as normal system behaviour & as a normal business process too. Moreover, it is not happeniing in the other two line items - line item 20 and line item 30 are fine. The pricing analysis shows both the conditions as found - PB00 and PBXX, so I could not take any clue from analysis too.
Prabhakaran, system is only behaving incorrectly for line item 10. It is behaving as expected (good ) for other line items and other PO's. So, we cannot touch the pricing procedure as that will affect other line items.
Regards

CIN condition type J1CV and JCDB not appearing in PO history

The 2 above mentioned condition types are appearing in PO conditions tab.
however, after GR was posted, the amount from J1CV and JCDB condition types was not showing up in the PO history tab.
and these 2 condition types did not have their statistic box ticked so by right it should be appearing.
however there's no problem with other condition types like JCV1, JECV, JEDB...etc
anyone can advice?

Hi,
Condition types J1CV and JCDB are stand for what pricing conditions?
There may be any causes for above.
Option-1----- >JCDB (IN Basic customs) is used for Basic Custom duty and this may be added to inventory account of material, so no separate entry in GR document.
Option-2----- >May be J1CV and JCDB (IN Basic customs) condition types have no value and during PO creation, this condition types may be deleted.
Option-3----- > Check J1CV and JCDB (IN Basic customs) condition types are there in MM Calculation Schema.
Regards,
Biju K

Condition types PB00 and PBXX

Dear Experts,
1) Can anybody please explain that can we use Condition type PB00 in number of Pricing procedures. like i have three pricing procedures, local purchase, Import Purchase,
External Service Pricing procedure.
what is recommend, eiether to use same one (PB00) or maintain seperate condition type for each Pricing procedure ?
2) What is the difference between Condition type PB00 and PBXX ?
Waiting for your valuable reply
Thanks in Advance

Dear,
The difference between pricing conditions PB00 and PBXX is :
PB00- automatic pricing - can be used for automatic pricing determination
PBXX- manual pricing - used for manual pricing.
When you maintain the pricing condition for the PO, the system will look at the available condition records (for PB00) and make the automatic pricing determination. In case, such condition records were not defined, then it is mandatory that you have to maintain manually the pricing condition where PBXX will be automatically defaulted in replacement for PB00.
Regards,
Syed Hussain.

What is the difference between Condition Type PB00 and PBXX

Hallow all,
Can anybody please explain, What is the Difference between Condition type PB00 and PBXX in Materials Management Pricing?
And also please explain control or Application of both on Price determination ??
Thanks in Advance !!!!!

Hi,
PB00 condition type is used for automatic pricing in PO
PBXX condition type is used for manual pricing in PO
In Pricing access sequence play a vital role . If you need pricing automatic in the PO, you have use of Access Sequences and Schema Group of Vendor.You can see the difference in both standard condition type PB00 and PBXX, where as PB00 is assigned to Access sequence(0002)but in case of PBXX no access sequense assigned.
Regards,
Biju K

Condition type EK02 and VPRS.

Hi Everyone,
In our pricing procedure there are two condition types EK02 and VPRS at header level. The profit margin we are getting is in negative. Can any one through some light about the use of EK02 and VPRS condition types and how system picks the values for the condition type EK02 ?
Thanks
Raksha.

Hi,
VPRS condition type is a Statistical Condition Type that returns the cost price of material from material master. It is basically used for comparison purpose. If you want to add it in the pricing procedure, make sure you add it at the last i.e. after adding of all the condition types.
EK02 is also a Statistical Condition Type and used for comparison purpose.
regards,
Sagar

Condition type PB00 and PBXX

Dear Gurus,
When system pick condition type PB00 and when it picks PBXX ?
I have made one scheduling agreement having 20 line items. For some line items it has picked condition type PB00 and for rest it has picked PBXX. Why system is picking PB00 for some line items and PBXX for rest ?

Hi,
If you create an Info Record manually or automatically the gross price is entered or adopted is assigned to condition type PB00.
When PO is created with reference to a contract or a quotation a vendor`s gross price for a material is adopted from the Info Record condition. (or where appropriate from PO price history) as default value for condition type PB00.
If no valid info. record condition exists and no order price history can be found, the R/3 system is not able to suggest a price and requires the manual entry of price and a manual entry of net price. The manually entered price is assigned to the condition type PBXX.
These two condition type for the gross price must be available in the calculation schema assigned to the standard PO. In the standard system these are the condition type PO00 and PBXX. An access sequence is assigned to PB00 so that the price determination process can be carried out for this condition type. No access sequence is assigned to PBXX . PB00 must come before PBXX in the calculation schema. You can also use your own comparable condition type in place of PB00 and PBXX.
At the time a PO is created, is the system finds a condition record belonging to PB00 with valid condition, PBXX is irrelevant. PBXX is taken into account only if requirement 6 is fulfilled. Requirement 6 checks the condition exclusion indicator (KOMP-KZNEP).
Hope this lengthy answer clears your doubt(s)!!
Reetesh

Allow mov type 261 and 262 for a material type only

Requirement is to allow movt type 261 and 262 for a particular material type.( Assume Only 261 - 262 issue transactions happen against that material type.)
User to be restricted, while material issue (migo), for the material type XXXX to 261 - 262 movt type only.
No any other movt type allowed for this material type while issuing material.
All suggestions welcomed.
Regards,
Rakesh

Thanx amit.
But same user uses all other movt types for other material type also.

VA00 condition type not getting determined for the returns order

Hi All,
I have a case where VA00 condition type not getting determined for the returns order that has been created with respect to the billing document.
When the pricing conditions are being copied from invoice it is getting copied but later it is getting deleted in the include LV61AA42.
Note:VA00 condition type is getting deleted from the internal table tkomv[].
If any one came across this scenario can you please help me.
Request your valuable inputs

Hi,
Please check the copy control setting in VTAA.
Maintain the pricing type as "D" at item category level for the respective document type .
Hope this will resolve your issue.
Regards,
Krishna O

In material master two countries are comming Hu and De for tax classificati

Hi All,
In material master two countries are comming Hungary and germany for tax classification ,can anybody tell why .
Thanks

Hello,
Please check the Tax Determination Rules & Tax Relevancy of Master Records in the link below:
IMG - Sales and Distribution - Basic Functions - Taxes
1. Define Tax Determination Rules
2. Define Tax Relevancy Of Master Records - Materiall Master.
It is from the above links the Countries & Tax Categories are proposed in Material Master / Customer Master.
Hope this helps,
Thanks,
Jignesh Mehta

SCD type 2 and 3 for Relational Dimension?

SCD type 2 and 3 for Relational Dimension?
==========================
Thanks for your replies.
I searched this forum and web on SCD 2 and 3 implementation using Relational Dimension (Table) using OWB.
I find some thread talks about implementing Oracle Dimensional structures, which has levels/hierarchy etc.
If we design our dimension in pure relational fashion, how do we go about using OWB for SCD 2 and 3?
Are there any new SQL features of 11g to help us here?
Thanks in helping.
RI

Hi,
several years ago Oracle published whitepaper which described steps for designing OWB mappings for loading SCD (types 1,2,3) tables.
But recently (after website reorganization) this whitepaper was removed, although you can stil find it by googling with "scdwhitepaper",
or you can directly download it from http://sourceforge.net/projects/owbland/files/Stuffs_from_Oracle_site/SCDWhitePaper.zip/download
Also it is available for download OWB experts which implement generation of SCD2 mappings according this whitepaper:
http://odi-ee.blogspot.com/2009/02/scd-type2-expert-table-operator.html
http://owbexpert.blogspot.com/2008/12/hallo-hallo.html
Also look at this thread {message:id=4336731} with discussion of bug which force to update all rows in target table, even they not changed between mapping executions.
Regards,
Oleg

Condition Type in an Invoice for Output tax

Hi,
In our Invoice we have different condition types for Output tax. These are the condition types :- MWST, IDM2, ZVLT and IDM3. All thse condition tpye refer to Output tax, although only MWST holds the actual value. But there is certain setting (i guess structure ikomv) which is sending all the condtion types in the IDOC. As the remaining conditon types are not required it is further giving an Error in XI. Please tell us which is the transaction that configures these condtions and also the required changed in our configuration.
regards,
Milan Thaker

I think this can be handled by adding a filter by condition type in the distribution model. See transaction BD64.

Er Job Devmt Assessmt tax (wage types /415, /615 and /715) for Tax Auth DC

When I am running payroll for an emp belonging to Tax Authority DC, wagetype /615 is being calculated correctly. However wagetype /715 is not adding up a particular wagetype amt and is thus less in amt than /615.
Wagetype /715 should be equal to /615. How do I approach this problem ? If at all there is an issue at BSI 's end, how can I zero-in on the exact problem?
N.B: I have already checked the Tax Model settings, alls fine.
Thanks And Regards,
Somdeb Banerjee.

Hi Manny,
               Thnx for the input. However I checked table T5UTX to see the ceiling there. The ceiling is 9000.00. However amt in RT Table for /715 wage type is much below the ceiling value i.e 1,210.51.
Amt in /615 = 1,213.47 . This diff of $ 2.96 is due to the presence of Gross-up wagetype 12SC. I have checked the Tax Model settings for DC thoroughly to see that this wagetype 12SC gets included in the taxable for Er Job Devmt Assessmt tax. And /615 is being calculated as expected in the RT Table. The problem lies with /715 !!
I am a bit confused by the presence of 2 entries for Tax Type 15 in the payroll log in Func USTAX:
Tax authority DC District Of Columbia DA01
Tax Category                                                  Tax.inc    Tax-free Inc.Declare Tax.earning         Tax
01 Withholding Tax                          (REG)     1213.47        0.00     1213.47     1213.47            57.00
10 Employer Unemployment Tax      (REG)     1213.47        0.00     1213.47     1213.47           15.78
15 Er Job Devmt Assessmt Tx      (REG)        2.96            0.00        2.96        2.96                    0.01
15 Er Job Devmt Assessmt Tx      (REG)     1210.51        0.00     1210.51     1210.51             2.42
41 Employee Disability Tax             (REG)        2.96             0.00        2.96        0.00                  0.00
Why are there 2 entries separately for Tax Type 15 ? The answer might be the solution to this issue.
Please help.
Thanks And Regards,
Somdeb Banerjee.

Condition types MWSI and MWVO for TAXES

Similar Messages

Maybe you are looking for