Reg:condition origin

Hi Gurus,
What is condition origin in condition records ? If we want to chage the condition origin ,what is the path to change it ? It is in table KOMV:KHERK.
Pls give me ur inputs
sash.

Condition origin in condition records indicates from where the condition originated (for example, whether you entered the condition manually or whether the system determined it automatically).
Condition - Agreement defining prices, surcharges/discounts, tax, and other costs according to the influencing factors selected (such as vendor, customer, customer group, vendor sub-range, material, and service). It remains valid for a specified period
When you define your Pricing procedure, then there are indicators for manual and statistical. If you mark a condition type as manual, then system allows for manual entries at the document level.
Similarly, when you configure the Condition type , you can maintain indicator against "Manual entries" field.
"blank" = No limitation
"A" = Free
"B" = Automatic entry has priority
"C" = Manual entry has priority
"D" = Not possible to process manually.
Based on this configuration, when you create the document, the system first searches for the condition values from the condition records or from any exits defined .If it gets the condition records, then the value is copied into the document condition as "Automatic entry" (here condition origin becomes = automatic)
If it does not get values from condition records, then it asks for manual entries ( for mandatory condition types). If you enter a manual value, then this value gets recorded as an "manual entry. ( Condition origin is = Manual)
I hope this clarifies your doubt.
Regards

Similar Messages

Condition origin

Hi,
We have condition ZHDL handling charges in m/06, which is maintained for " manual entry has priority" & maintained for header aswell as for line item. When ZHDL entered in two line items for different vendor, one line item show "Inactive due to manual entry " & condition origin shows as Automatic pricing, I am unable to do MIRO for this line item.

Hi,
Good Day,
Condtion Origin is one of Control Data which will be useful to analyse the Condtion Type.
Example : Condition value arrived through Access Sequnce then it will be Automatic Pricing.
Subtotal Condtion type also will be Automatic Pricing.
If Condtion value are Manually maded in Header then Condtion orgin will be Header condition.
Best Regards,
KSK

Condition origin in Header condition type

Dear Experts,
I am on ECC 6.0 and have defined a pricing procedure for PO. I have defined a condition type at the header level ZRB1 for freight.
When i create a PO, it does not allow me enter a freight value at the header. The requirement is , e.g, i enter 100$ as freight at header level which gets distributed as per the grouping condition for the items.
The problem is that header condition type is pointing to the condition origin at the item level. Is there an option to modify the condition origin by selecting the condition type details in the header?
Thanks in advance
Learner

Hi,
In M/06, tick the condition as header and also as group and routine 0.
if you want to distribute this cost to line item apportinoately tick item condition also.
what i see from your you are looking for that, so tick both header and item condition and group condition.
Regards
Rajesh

Condition origin settings

Hello friends,
How to maintain condition origin at "A" i.e. Automatic pricing instead of "C" i.e. manually entered, which is default setting on item condition detail screen.
I want the conditions to be displayed automatically at the time of creating sales order.
I tried with V/06 but i could not find those specific settings in contol data 1 tab.
Please share your inputs.
Thank you
Sadanand

Hi Sadanand,
In the sale order If you go to conditions screen at the item level and double click on the condition it will show you the condition origin box. Here the system shows whethe the condition has been determined automatically or manually entered in the sales order. If its showing automatically determined means that the condition has come from the condition record(VK11). To get this you have to assign the Access sequence to the condition definition in V/06 and maintain a record for the same. If you dont want the condition to be dtermined manually at all then go to V/06 AND in the tab "changes which can be made" and in the check box manual entries , put the option "D". Kindly please let me know If you need any more information on this.
Regards
Ram Pedarla

Change condition origin for PR00

hai,
I want to change the condition origin for the condition type PR00
where will u change the condition origin for a particular sales condition type.
condition origin option:
A- Automatic pricing
B-
C-Manually
Its there like that.
I want to change that condition origin there.
Thanks in advance
by
babs

hi,
i am not asking for manual entries in condition type PR00
i asked condition origin which can be seen while creating sales order.
select item condition
select PR00
select overview icon
there u can see condition origin
below condition control
i want to change that condition origin
condition origin option:
A - Automatic pricing
B - Duplicated from main item
C - Manually entered
D - Header condition
E - Item total
F - Condition supplement
etc
here i want to enter A instead of C
Thanks in advance
by
babs

Pricing: Condition Origin

Hello All,
I would like to ask the difference among the following condition origin being set in Item-Conditions-detail. Kindly enlighten me how each condition origin is use.
A     Automatic pricing
B     Duplicated from main item
C     Manually entered
D     Header condition
E     Item total
F     Condition supplement
G     Original header condition
H     Correction Rebate
I     Cost Correction
I would really want to know especially the difference of D, E and G. Thanks in Advance!

There are Condition Analysis Messages to Fields in Pricing Analysis.
Kindly refer following SAP help like for Pricing Analysis.
http://help.sap.com/erp2005_ehp_04/helpdata/EN/93/743517546011d1a7020000e829fd11/frameset.htm
D - Header conditions are those which appear in the header level of any sales order. these conditions are to be entered manually and get distributed automatically and the basis for distribution are taken from the NET VALUE of items mentioned at item level.
E - Item total is total of Item conditions.
G - Original header condition is in reference doc pricing and is copied from reference doc.
Thanks & Regards
JP

Reg. condition based receiver Determination

Hi,
 I need to send the records to two systems based upon the value
For Ex. All the material group record letz say (1,2,3,4,5,6) Shuld go to Receiver1 and only the records which belongs to material grp shud go to Receiver2.
I am trying using Condition based Receiver Determination
 For Receiver 1 :-
 I didnot give any condition.Coz all the records have to go to Reciver1.
 For Receiver 2 :-
 I have written the condn in the Interface determination
 i.e) Material Group = 2.
But All the records are going to these two receivers.I have tried everything.
Thanks in advance
Regards
Anandan

Anandan,
Similar situation has worked for me. Please check the condition you have mention in Interface Determination.
In the Interface determination you need to have 2 inbound interfaces. Specify the respective condition for each inbound interface.
Example: if the Response field has the value as "Success" or "Failure" the message has to go to first interface. The message has to go to second interface only if the response is "Failure". so you can provided following condition in the interface determination:
Condition 1:For first inbound interface (/p1:MessageType/RecordSet/Response = F) OR (/p1:MT_RESPONSE_FROM_PS_BI/RS/Response = S)
Condition 2:For second inbound interface (/p1:MessageType/RecordSet/Response = F)
The above condition has worked for me. Hope this would be helpful to you.
Regards,
Sridhar

Reg.condition types should come automatically during CR and Billing creatio

Dear Friends
I create new condition types for MRP price and other taxes which is working fine but I have to be entered each time when I create CR and Billing, I want those conditions which is mentioned in the procedure-.control data should come automatically during the the CR and Billing. Please advice me. Previously I got a reply that should create condition record for each condition in VK11,HOW it is possible ?
I didnot assign any access sequence to my conditions which is newly created, so that the above problem could be arrived?
Thanks in advance
Rajakumar.K

Hi,
If there is access sequence then it is possible to bring condition in sales document automatically.
for this Just create on dummy access sequence and assign to condition type
Generate table with combination of only sales organization by V/03
Create access sequence by V/07 and assign this table
Assign this access sequence to condition type
in V/06 under change can be made tab for Manual entries put blank (No limitations)
Maintain condition record for condition type (with price or without price)
Then condition will come automatically
kapil

Reg:Condition types in Tax code

Dear all,
I'm Creating a new tax code for which I've to include my own condition type where can i do this juz give me the path

Hi
Where are you planning to create Tax code? For PO you can create with the help of Txn code FTXP and assign your own percetange etc inside the condition types already existing.
If it is outside then you have to create a new conditon type, then use Txn M/06 .
Best Regards

Reg: condition value computing.

Hi,
i am using bapi to create an order. I have to migrate the legacy data to the sap system, it has 2 condition record in the header and 4 in the item,
how to calculate the amount for each conditions. the conditions which we would be receiving is not fixed. based on which the value (KBETR) has to be computed..
for example
if the Condition type is ZHP1(discount) - the input value is 2 but the expected value is 0.2-
if the condition type is ZMV1(Netprice) - the input value is 4 the expected value is 4.0
how to update this.. is there any function module.. which determines it based on the structure
Konv structure.
Adv Thanks & Regards
Dinesh

I dont think this is possible.
The reasoning is that if SAP allows it, then there is no control over what values exist in the file. This means anyone can change values in the file which defeats the purpose of one of SAP's important plus points - strict control over master data.

Reg condition record number (knumh)

Hello All,
I want to knw from which tcode the entries of field knumh are getting entered in the table konp.
Where we define this condition record number?
Thnks,
Sunita

Hi
From Pricing related transactions in Both SD and MM modules the data is entered in the pricing related tables KONV,KONP etc
KONP stores the item level condition based amounts.
Not from a single tcode, all pricing related tcodes data will enter into it.
Reward points for useful Answers
Regards
Anji

Reg.Condition types required

Dear All
The below condition types are not in our Development system.
Where to get it. JMOP,JEC1,JVCS and JVRD
JMOP - Excise Duty
JEC1 - Cess
JVCS - CST
JVRD - VAT
Please help.
Thanks
Rajakumar

Yes,Every condition type doing different different calculations.
Therefore which condition type should be selected for CESS and ECESS. when I look for JEC1 and JSEP for CESS and ECESS. There is not available in condition type.
Please advise
Thanks
Rajakumar

Reg:Condition based upon source in mapping

Hi All,
My Scenario is R/3-PI-JDBC(SYN Scenario).
My Source has two fields
 *<Record>*
 *<FromDate>19870909</FromDate>*
 *<ToDate/>*
 *</Record>*
My target is
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_Sel xmlns:ns0="http://hnwl.com/abc.com/">
<StatementName1>
<dbTableName ...<dbtable>
<StatementName2>
<dbTableName ...<dbtable>
<StatementName3>
<dbTableName ...<dbtable>
Condition : 1.If fromdate has value then statment1 should be executed
 2.If Fromdate and todate has value then statement 2 should be executed
 3.If fromdate and todate doesnt have value then statement3 should be executed
Please let me know how to handle this in mapping.Thanks in advance
Regards,
Dinesh

One possible option is use enhanced interface determination. In the mapping decide what receiver structure to be used. see this link..
[Link |http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90dcc6f4-0829-2d10-b0b2-c892473f1571?QuickLink=index&overridelayout=true]for enhanced interface determination
Regarding mapping
Source field followed by node function exists followed by if withoutelse function and map to target root node of the each structure.
similarly do three times for the three conditions.

Reg: Condition type

Dear Experts.
In Std SAP the condition type we can maintain max 4 digit.
We can maintain 2digit 3 digit or max 4 dight based on our naming convention.
My clients requirement is make the condition type to 6 digit.
Please explain in details.
Regards
Nayak

This is not possible. Try to convince the client.

Reg Condition type JASS in JINFAC

Hi,
What is the use of condition type JASS in JINFAC
Regards
Guna

hi
it is for Excise Conditions (tax normally used for at the customs ..between countries)
thanks
madhan
correct me if im wrong

Reg:condition origin

Similar Messages

Maybe you are looking for