In what scenarios does Reference condition type is being used?

In what scenarios does Reference condition type is being used?
Please provide inputs.

<b>Reference condition type</b>
A condition type which can be used as a reference so that you only have to create condition records once for condition types that are very similar.You may need to use different condition types for the same condition. These can differ in the access sequence, the description, the reference stage of the pricing procedure or the calculation type, for example, you can enter the condition type under which the condition records are created.
<b>Refer below example</b>
Condition type MWSI only differs with condition type MWST in the calculation type. For this reason an entry is made in field ReferenceCondTypeMWST for condition type MWSI . Now, condition records only need be created for condition type MWST and not additionally for MWSI.
Thanks and regards

Similar Messages

What exactly does "your IP address is being used by another device"

everything is in the question, I recently had to deal with hacking attempts by e-mail, that's why I pay attention
thank you

Most likely, you're getting a network address from your router. The address assignment ("lease") expires, and has to be renewed, after a certain amount of time, which might be one hour or one day. The lease expired without being renewed because the device was offline at the time. Meanwhile, the address was leased to another device on the network. When the first device comes back online, it still has the address that's now also leased to the second device. Depending on what kind of router you have, the conflict may resolve itself automatically. If not, then from the menu bar, select
 ▹ System Preferences ▹ Network
If the preference pane is locked, click the lock icon in the lower left corner and enter your password to unlock it. Then click the Advanced button and select the TCP/IP tab. Now look at the menu labeled Configure IPv4. If the selection in that menu is Using DHCP, click the button labeled Renew DHCP Lease. Test.
Less likely, you have a network address that you assigned yourself, and another device is assigning itself the same address. In that case, the selection in the Configure IPv4 menu will be either Manually or Using DHCP with manual address. This kind of conflict won't be resolved automatically. You have the following options to resolve it:
Change the menu selection to Using DHCP.
Change the manually-assigned address to one that isn't being used by another device.
Change the address of the other device.
Which of these options you should choose depends on the details of why you're using a static IP address. Any change you make to the network settings must be applied before it takes effect. To do that, click OK and then Apply.

Reference condition type wrt IV01 and PI01..

Hi PPL,
Can u plz explain Referrence Pricing condition wrt to the condition types :
IV01 and PI01,
Both are condition tyres pertaining Inter company ,IV01 has a Reference condition Type PI01 assigned to it.
What does it mean in the inter company scenario.Points for sure..:-)
Best Regards,
Subbz..

Hi,
PI01 condition type represents costs to Ordering company code (in other words revenue to supplying company code).
It is statistical condition type & meant for information purpose only.
Condition records for PI01 are created with the following key combination:
Ordering sales Org + Supplying Plant + Material
PI01 represented under pricing procedure RVAA01 is reference condition type for IV01 and the same is defined in the condition type IV01. Due to this these two condition types represent same value.
The condition type IV01 in intercompany billing document represents revenue to the Supplying Company. But its corresponding condition type PI01 in the billing document to the end customer is shown as a statistical item meant for information purposes.
The use of two different condition types in Intercompany billing is necessary to ensure that data is transmitted correctly to the financial statement (Component CO-PA).
Hope this provides you with your answer,
Regds,
Rupali

Reference Condition type

Hi,
Can someone share with me on the usage of the reference conditon type field in the condition type field? If i put in the PR00 as the reference condition type in PB00?
How this will affect the price determination?
Still quite new to price determination in MM. Hope someoneone can give me some guidance on it.
Thanks.

hi
A condition type which can be used as a reference so that you only have to create condition records once for condition types that are very similar.
Ex: AMIW and AMIZ, these both condi types are used for minimum order value.
If u maintain AMIW- (min ord value) condition type We have to assign this condition type to AMIZ (surcharge value) cond type as reference condition type. then only it will work it.
Edited by: Roddick Redy on Apr 21, 2008 7:29 AM
Edited by: Roddick Redy on Apr 21, 2008 7:32 AM

What is replacement of file type IBM while using GUI_UPLOAD?

Hi All,
what is replacement of file type IBM while using GUI_UPLOAD?

Iam using the class CL_GUI_FRONTEND_SERVICES and method GUI_UPLOAD
instead of directly calling the GUI_UPLOAD FM
Please note the difference marked star against it
Let me know what i have to pass
DATA: INP TYPE STRING.
clear : inp.
MOVE in TO INP.
CALL METHOD CL_GUI_FRONTEND_SERVICES=>GUI_UPLOAD
EXPORTING
FILENAME = INP
FILETYPE = 'ASC'
HAS_FIELD_SEPARATOR = SPACE
HEADER_LENGTH = 0
READ_BY_LINE = 'X'
DAT_MODE = SPACE
CODEPAGE = SPACE
IGNORE_CERR = ABAP_TRUE
REPLACEMENT = '#'
VIRUS_SCAN_PROFILE =
IMPORTING
FILELENGTH =
HEADER =
CHANGING
DATA_TAB = cr *******************************
EXCEPTIONS
FILE_OPEN_ERROR = 1
FILE_READ_ERROR = 2
NO_BATCH = 3
GUI_REFUSE_FILETRANSFER = 4
INVALID_TYPE = 5
NO_AUTHORITY = 6
UNKNOWN_ERROR = 7
BAD_DATA_FORMAT = 8
HEADER_NOT_ALLOWED = 9
SEPARATOR_NOT_ALLOWED = 10
HEADER_TOO_LONG = 11
UNKNOWN_DP_ERROR = 12
ACCESS_DENIED = 13
DP_OUT_OF_MEMORY = 14
DISK_FULL = 15
DP_TIMEOUT = 16
NOT_SUPPORTED_BY_GUI = 17
ERROR_NO_GUI = 18
others = 19
The above code gives me an error
"CR" is not type-compatible with formal parameter "DATA_TAB".
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
FILENAME = INP
FILETYPE = 'ASC'
HAS_FIELD_SEPARATOR = ' '
HEADER_LENGTH = 0
READ_BY_LINE = 'X'
DAT_MODE = ' '
CODEPAGE = ' '
IGNORE_CERR = ABAP_TRUE
REPLACEMENT = '#'
CHECK_BOM = ' '
VIRUS_SCAN_PROFILE =
NO_AUTH_CHECK = ' '
IMPORTING
FILELENGTH =
HEADER =
TABLES
DATA_TAB = cr *****************************
EXCEPTIONS
FILE_OPEN_ERROR = 1
FILE_READ_ERROR = 2
NO_BATCH = 3
GUI_REFUSE_FILETRANSFER = 4
INVALID_TYPE = 5
NO_AUTHORITY = 6
UNKNOWN_ERROR = 7
BAD_DATA_FORMAT = 8
HEADER_NOT_ALLOWED = 9
SEPARATOR_NOT_ALLOWED = 10
HEADER_TOO_LONG = 11
UNKNOWN_DP_ERROR = 12
ACCESS_DENIED = 13
DP_OUT_OF_MEMORY = 14
DISK_FULL = 15
DP_TIMEOUT = 16
OTHERS = 17
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
I assume that CR is a table with header line, in OO context, header lines are not allowed so you specifically have to state that you are passing the body of the table.
*HEADER =
TABLES
DATA_TAB = cr[]      "<- Like This
EXCEPTIONS
call method cl_gui_frontend_services=>gui_download
exporting
    filename                = str_file
changing
    data_tab                = istr.
Message was edited by:
        Karthikeyan Pandurangan

How to implement the Reference Condition Type

Dear Friends,
My Client is using the Refernce Condition type ZMWS which is referencing MWST condition type. He has implemented the same for one company code already. When I am creating a Sales Order, I am able to get the condition type MWST for the newly created condition type ZMWS through the condition record maintained for MWST.
But when I am doing the same for other company code I am getting a pricing error as it is saying mandatory condition ZMWS is missing.
I am not getting any clue what to do. Do I need to maintain any settings?
Thank you,
Prakash K M

Dear Prakash,
In V/06, detail screen of condition type, under under master data you have to give the reference condition.
Regards,
Abhee.

How to create Reference Condition Types

Hi ,
Please tell me how to create Ref.Condition Types?
I have a requirement.."I should create a Zdiscount(13%) which should be copied to the sales order automatically based on PR00"
How to do that?
Points for sure
RamChandra

Hi,
You can use condition supplement functionality.
Check the link [Condition Supplements|http://help.sap.com/saphelp_47x200/helpdata/en/93/7432de546011d1a7020000e829fd11/frameset.htm]
You can also check the field RefConType for the discount condition type in SPRO -> Sales and distribution -> Basic functions ->Pricing -> Pricing control ->Define condition type.
Regards,

How to block particular condition type not being posted

Hi,
We don't want a particular condition type ( customized & accruel ) to be posted into accounting when creating a billing. That condition type is deleted and after that this is how it works now.
1. When a billing is cretaed from a new sale order ( which does not have that condition type ) it works fine.
2. When a billing is created from a sale order which refers to the old sale order which in turn has this condition type, then this conditon type is posted into accounting.
Can some one help in this issue so that I want to block this condition type being get posted in accounting. Is there any Userexit or can it be done with other options. I am an ABAPer, please give specific answer.

Hi Jagadish,
The reason why we do account determination is that we would want the system to post the respective amounts to respective G/L accounts automatically. What amounts to be posted to what G/L accounts is decided by the Account keys .
Now if for a particular condition type in the pricing procedure if you remove Account key the system will not post to the G/L accounts. But generally in this case I believe while creating the Bill system will throw an error in account determination.
For that what you can do is create completely new accont key and assign a provisional G/L account which is not to be included in your Balance Sheet accounts or P & L accounts (can be restriscted by FI Guys).
But remember to use a completely new oricing proicedure for this case.
Hope this helps.....
J Nagesh

Condition type value updation using characteristic value in sales order

Hi Experts,
We are implementing SAP for one of our Spain client. In that one of the Legal requirements is, whenever they are selling the finished products to domestic customers who contain OIL as one of the component then, some additional cost needs to be calculated and collected from customer and which needs to be paid back to Spain Government every month on Region basis.
If OIL is not a component to produce the finished product then, not required to charge the customer additionally.
The OIL content used to produce every finished product will vary based on product characteristic value. Meaning, for some finished product the OIL used will be 2.2 KG and for some products it will be 3.5, 4.3 KG and etc.
Since various combinations of products are available for the client, during sales order creation we are planning to update some special characteristic which the data flow from u201CVariant Tableu201D. In the variant table we are going to maintain the OIL Quantity required making finished product.
But we are not sure how to activate a new condition type with the value fetched in the special characteristic. This new condition type needs to be activated based on this characteristic value and multiplied with total order quantity and price to charge from customer.
Example, the special characteristic fetched the value of 2.2 KG based on variant table. Total Order quantity is 10 PC and charge is 0.06 EURO per KG. in this case, (2.2 x 10 ) x 0.06 EURO = 1.32 EURO
I need the expert opinion how to activate the new condition type based on characteristic value and achieve the above requirement.
Thanks in advance.
Warm Regards,
VEL

Hello,
I have replicated the whole requirememt in IDES and getting the price calculation as needed but the only issue with the Conversion factor for the condition type. Either you need to maintian the conv factor in material master or need to enter manually for the condition type in SO. Some how you have to maintain the conversion factor to calculate the price for the condition type in different unit.
For easy of understanding Lets make the whole requirement in 2 parts
Part - 1
Oil qty calculation. For convenience sake I have taken oil qty also in TO
1) Created a num char OIL_QTY1 with length 9 and decimal places 5 and UOM as TO
2) Created Variant table to infer the OIL qty in TO per piece of finished prod ( This oil qty data may be depends on various factors). For certain Finished products the oil qty may be 0 or blank
3) Created a REF char SO_QTY to pull the SO qty to configuration and add this char in class 300(Table:VBAP,Field :KWMENG)
4) Created another char SO_OIL_QTY (Num with length 9 and decimal places 5 and UOM as TO)
5) Created a PROCEDURE say PROC_SO_OIL_QTY with code
*$self.SO_OIL_QTY = $self.OIL_QTY1 * $self.SO_QTY*
6) Create another PROCEDURE as mentioned earlier with modified code
$SELF.A_VARCOND = 'TEST_001' if OIL_QTY1 specified,
$SET_PRICING_FACTOR ($SELF,A_VARCOND,'TEST_001', SO_OIL_QTY)
Note: Maintain proper seq of the procedures in profile. The Qty cal proc should be before the price related procedures.
PART-2
1) For the condition type maintained 60 EUR per TO (0.06 EUR per KG)
Now if you create SO for the Finished product of 10 PC
the Char values will be
OIL_QTY1 = 0.00022 TO (inferred from Variant table th proc)
SO_QTY = 10
SO_OIL_QTY = 0.0022 TO
Get into conditions tab
Here Condition type ZSIG will be displayed as error with Amount 60 EUR per TO and condition value will be blank. Just enter value 1 in the col NumC and CCon fields.
Now the Condition value will appear as 1.32 EUR.
Hope this gives some more clarity
Regards
Brahmaji D

How does time machine work when being used with a mac pro?

How does time machine work when backing up a mac pro?
Considering the fact that the mac pro can hold 8TB and a external (non NAS) hard drive can hold only 2TB does time machine only backup the OS disk.

macnewcomer22 wrote:
Considering the fact that the mac pro can hold 8TB and a external (non NAS) hard drive can hold only 2TB does time machine only backup the OS disk.
Time Machine will backup everything by default, on every disk in your Mac.
Choose System Preferences > Options to exclude items. You could exclude everything except your OS...but I'd think it is your data that's more important to you, if you have to make choices.
See...
http://discussions.apple.com/thread.jspa?threadID=1964018
While it's true you can store almost 8TB, how much do you think you'll actually store? If you have 1TB of data you want to store then a 2TB drive can do it. Also when your TM drive begins to get full it will begin deleting the oldest backups to make room.
You could also get a Drobo with 8 bays...
http://www.drobo.com/products/index.php
-mj

Condition Types in Price Determination Process

Hi
Can any one explain me about in Detail about the VARIOUS TABS that work in the CONDITION TYPE of PRICE DETERMINATION PROCESS
Thanks & Regards,
Senmani.

hi
hi
control data 1 :
Condition Class is a grouping that lets you control each condition type differently.
For example, the condition type "taxes" defines that the taxes in a document must be recalculated if the country of the ship-to party changes.
Condition category (examples: tax, freight, price, cost)
A classification of conditions according to pre-defined categories (for example, all conditions that relate to freight costs).
Condition category basically identifies the type pf cost the Condition type is being used for & can be used for .
Calculation type
Determines how the system calculates prices, discounts, or surcharges in a condition. For example, the system can calculate a price as a fixed amount or as a percentage based on quantity, volume, or weight.
The calculation type can be set when generating new condition records. If this does not happen, the calculation type maintained here is valid for the condition record
Rounding rule
The rule that determines how the system rounds off condition values during pricing. The last digit will be rounded.
Example
In the standard rounding rule '_', values are rounded off according to business standards:
10.454 -> 10.45 DEM
10.455 -> 10.46 DEM
In rounding rule 'A', values are always rounded up:
10.459 -> 10.46 DEM
10.451 -> 10.46 DEM
In rounding rule 'B', values are always rounded down:
1045.9 -> 1045 LIT
1045.1 -> 1045 LIT
In this example, the currency of the condition rate is Italian Lira. The Italian Lira does not have any places after the point.
Structure condition
controls whether the condition type should be a duplicated condition or a cumulated condition.
This control is only helpful when you use bill of materials or configurable materials.
Aduplicated condition is duplicated into all assigned items.
A cumulated condition contains the net value of all assigned items.
control data 2 :
promotions
Specifies that the condition type in question is only valid for Promotions.
Use
Conditions for which this indicator has been set can only be maintained via the 'Promotion' menu - not via the Purchasing menu.
Accrual (e.g. Freight)
Indicates that the system posts the amounts resulting from this condition to financial accounting as accruals.
Use
If you mark this indicator, the condition appears in the document as a statistical condition.
Before Release 4.0 variant conditions (VA00) had to be created with the condition category 'O'
Problem: It was not possible to indicate a 'Variant condition' at the same time as 'Internal costing condition' and 'Freight'.
Solution: For this reason more indicators are being set up in 4.0 for the condition type:
'Variant condition' (KVARC)
'Internal costing condition' (KFKIV)
The characteristic values O and I for the condition category must no longer be used.
For more information, see the note 93426.
inv.list condi
Condition for invoice list
Marks the condition type as relevant for internal costing.
Quantity conversion
This field controls the quantity conversion during determination of the condition basis.
The field is only relevant for calculation rule 'C' (quantity- dependent.
It is relevant if the sales quantity unit and the condition quantity unit are identical (and is different to the basis quantity unit).
Deactivated: The condition basis quantity is converted via the quantity to the stockkeeping unit. This means that the condition quantity is determined for planned factors. This means that a change to the conversion factors in the delivery or the order are not taken into account.
Rounding errors can occur during quantity conversion.
Activated: If the sales quantity unit and the condition quantity unit are identical, the quantity of the document item is used, i.e. the actual quantity.
Condition for inter-company billing
Conditions for Internal Costing, for example PI01 and PI01 were defined before Release 4.0 by KNTYP = I (Price for internal costing).
Problem: It was not possible to indicate 'Freight condition' at the same time as 'Internal costing condition' and 'Variant condition'.
Solution: Therefore a new indicator 'Internal costing condition' (KFKIV) has been set up. You can use this to indicate a freight condition as an internal costing condition. For more information, see note 93426.
Scale :
Scale basis indicator
Determines how the system interprets a pricing scale in a condition. For example, the scale can be based on quantity, weight, or volume
Checking rule for scale rates
Indicates whether the scale rates must be entered in ascending or descending order.
Scale Type
Indicator that controls the validity of the scale value or percentage:
From a certain quantity or value (base scale)
Up to a certain quantity or value (to-scale)
Alternatively, it is possible to work with interval scales. Interval scales must be stored in the condition type, that is, the scale type "interval scale" cannot be changed in the condition record. The reason for this is technical restrictions resulting from the programming within pricing.
Formula for scale base value
Formula for determining the scale base value.
Use
You can use this formula to specify calculation methods that are not provided in the standard system.
reward points if helpful
thanks and regards
ravikant dewangan

Pricing condition types in SRM 7.0

Hi,
We are using SRM 7.0, we have decided to go ahead with the pricing proceedure and the condition types which are there in ECC the same should be replicated to SRM.
We have created the same pricing proceedure and the calculation scheema in SRM.
Now my requirement is when i create a PO with the conditions and when i am transfering to ECC the PO should also be with the condition types. It should be a similar PO in ECC.
Is this can be addressed.

Hello All,
As I have already mentioned the condition types in SRM are identically matched to ERP condition type hence the data is flowing correctly and even the idoc has the z-condition type Z123.The IDOC in backend ERP has status 53.
On trial and error method we did unchecked the manual indicator check in the pricing schema for the relevant condition type and because of that now the Z-condiiton type can be seen in the backend ERP contract.
If the indicator was checked, this means that this condition can be maintained only manually (directly in the transaction
ME32K in ECC) and nothing can be transfer from other source.
Note: If the same condition type is being used in more than one pricing procedure then ensure that the check bok is unchecked for agianst the relevant condition type.
Thanks,
Yatin

Determination of Base price condition type depending on Item Category

Dear All,
The requirement I have is as stated below:
There are two materials A and B that are individually sellable materials. But during a specific time period the company decides to give a scheme where in Material B is given as free when a particular quantity of material A is purchased. Irrespective of the scheme, material B can also be individually purchased during the scheme period.
Now in the former scenario where material B goes free with material A in the same order, the base price of material B should not go to revenue G/L but to a different G/L called Scheme G/L. To counter this scheme G/l there is another counter G/L into which 100% discount on base price to material B goes.
In the latter case, if material B is sold individually, then the base price should go to Revenue G/L and not scheme G/L and the 100% discount is not applicable.
Can you please guide me on how to configure this.
The approach I have taken is as follows:
The condition types for base price are ZBPR and ZBP1(reference condition type of ZBPR)
Item Categories to be considered: ZTAN and ZTNN (for material B going as free during the scheme)
The requirement is such that, whenever the item category for a particular material is ZTAN, the condition type to be picked must be ZBPR while the condition type ZBP1 must be deactivated.
Similarly, if the item category for the line item is ZTNN, then the condition type to be picked must be ZBP1 and the condition type ZBPR must be deactivated

Dear All,
I have fulfilled this by doing rev acct determination in vkoa using item category and moving it up the order. Also I used a requirement in v/08 for 100% discount on free material.
This has resolved my issue and i am now closing this thread.
Thanks and Regards,
Rohan
Edited by: Lakshmipathi on Apr 2, 2011 10:53 AM
Since you have arrived at a solution, please change the status of the thread to "Answered"

Change the condition type based on sales document type

Dear ALL,
I have created a condition Zxxx which is a fixed calculation type for the documents created by the upload from external tool to SAP. I created this condition because external tool is using a 15 place decimal which SAP doesn't allow and if the normal condition type Zyyy is used SAP calculates once in SAP and there are rounding issues. What the Zxxx condition type does is accept whatever value is sent up from external tool to SAP, regardless of the quantity. The problem is that whenever they create a credit with reference, in SAP and they want to do a partial credit, the Zxxx doesn't take the partial quantity into consideration and doesn't change the value.
Is there a way to force SAP to change the condition type from Zxxx to Zyyy based on sales document type without recalculating the whole document because that would again, cause rounding issues. We would need to have the calculation done only on quantities changed in the credit memo request .
please advice me. your inputs are highly appreciated.
TIA
KOGI

Dear ALL,
someone please help me with this issue. your inputs are higly helpful.
TIA
KOGI

Pricing Procedure and Condition Types

Hi Guys,
What do we mean by a pricing procedure in SD? Where do we assign this Pricing Procedure and what is the purpose of this?
Also what do we mean by the condition types? What does a condition type signify...
Please let me know the tcodes and also how can i understand these topics from a Sales order perspective? How do these coincide?
Thanks,
Srikanth.

It has been observed that you are posting so many basic questions and I am sure, you would not have searched the forum before posting such questions.
Please go through this link for Forum Rules
[Read this before posting |Read this before posting;
If you have searched the forum and could not find any solution, please let me know what you had searched and still what are you expecting from forum.
For other members, please dont encourage giving suggestions for such repeated / basic threads. In fact, as per the guidelines, a Moderator can even deduct the points given but I dont want to do this
thanks
G. Lakshmipathi

In what scenarios does Reference condition type is being used?

Similar Messages

Maybe you are looking for