Inactive SD Conditions to COPA

We are having an issues with an SD condition value (specifically VPRS) not being sent to COPA. It is statistical , which should be not a problem, but it's also inactive. Do inactive condition values get sent to COPA? Thanks.

What is the meaning of inactive/ Where is it inactive.
Normally, if it has been assigned in SD pricing procedure. And addigned to COPA vlaue field, it gets updated in COPA.

Similar Messages

Posting manual SD conditions to COPA

Hi,
I have customized KE4I transaction with all the SD condition types, but when the billing document has the conditions filled manually it doesn't appear in the PA document.
Is it possible to post this conditions to COPA?
Thank you very much!!!

You could try KE26 for reposting, if it were subsequently added. May be the condition type has to do something with statistical or non statistical? Refer also to the note 20254 .

Extracting Inactive Pricing conditions from 2lis_11_vaikon

Hi,
Currently we are able to extract all the pricing conditions except Inactive conditions.
Can any one advice how to extract inactive pricing conditions from 2lis_11_vaikon.
Regards,
Rahul.

see note 1062462
(you can find that via a simple Google search btw)

Trading goods MM Conditions into COPA ( Condition wise)

Dear Experts,
Any possibility is there to get the MM Pricing conditions into COPA like SD Conditions with out activating IS Retail Module.
Any alternative method or MM condition Types into COPA.
Regards,
Goda

Hi,
Yes, it is possible to post values into Value fields of PA by assigning the MM Conditions in KE4IM like what we do for SD conditions in KE4I.
Trust this helps much!
Cheers!

Set up of MM conditions in COPA

Dumb question.... but in Customizing (next to KE4I) there is an option to map MM conditions to Value Fields just like we can map SD conditions to Value Fields...
How is this used?
What document in logistics triggers this posting? (Just like Billing will in SD condition etc.)
Thank you in advance!

Hi Arif,
This is what SAP feels the requirement for MM to COPA
Direct Posting from FI/MM
You can transfer direct primary postings from Financial Accounting (FI) and Materials Management (MM) to profitability segments.
The following are some typical cases of when you would want to do this:
You post special direct costs from sales, such as transport insurance for a certain delivery, and would like to assign these primary costs directly to a profitability segment.
You post an invoice for promotional events and you want this invoice to appear statistically in the responsible marketing cost center, and at the same time assign it to a profitability segment in Profitability Analysis. In this case, you would assign the invoice to both a cost center and a profitability segment.
You create automatic postings in Materials Management and you want these revenues and expenses from the revaluation of material stocks to be posted automatically to Profitability Analysis. This instance also requires that you define "Automatic assignment to a profitability segment".
Requirement
1. The operating concern must be fully defined.
2. The desired form of Profitability Analysis must be active for the relevant controlling areas.
3. You have maintained number ranges for record type "B".
4. You have created a group of characteristics (under "Master Data") to define the screen for assigning postings to profitability segments, and assigned this characteristic group to business transaction "RFBU".
You need to customize in TCode KEI2 and/or OKB9.
Regards,
Suraj

SD planned revenues from inactive price condition

Hello,
please assist.
Revenue elements from the SD pricing procedure (coditions) that are not statistical are updated as planned revenue on the sales order item (within table COSP with the business transaction SDOR).
The relevant revenue accounts are determined within the revenue account determination.
Is the revenue account determination processed also for SD conditions, which are inactive (KOMV-KINAK)?
We have got an issue, that also some conditions, which are inactive because of subsequent price (KOMV-KINAK=Y) are updated into the COSP-SDOR as planned revenue. Therefore the position has more planned revenue within the result analysis and as we use the revenue based result analysis method, it influences the WIP calculation.
Thanks in advance
P

Issue solved.
The reason was the SAP Note 1062462.
This note is used to extract also inactive conditions into BW. Unfortunatelly, due to this modification, the inactive conditions are not deleted from xmckomv, which is used also for updating the planned revenues (and other SIS statistics, which are based on the conditions), so they were added to the planned revenues.
We have to deimplement the note.

Statistical Conditions in COPA

I find that there are few conditions types in SD which are "statistical". I am not clear about how this statistical conditions will flow to COPA. Will they flow to COPA ? Since these have no FI postings, the COPA figures will not be in tally with FI, right ?

Hi NIki
SAP HELP outlines this concept.. However, my collection of points on this subject reads the following
Costing based vs. Account based copa (ABC)
a.     Account based copa uses transaction tables and hence affects performance of CO transactions
b.     Estimated values not possible in ABC (Stat Values)
c.     Reports based on line items not possible in ABC
d.     Actual Top Down distribution not available in ABC
e.     Revaluation of actual data to plan data is not available in ABC
f.     No key figure schemes are available in ABC
g.     COGS breakup cant be achieved in ABC
Explanation on (b) - Using stat values, you can take tax values also to COPA.. i.e. you create a Stat cond type with 100% condition record on Sale Tax Cond Type... Hence, you can take tax values to COPA
If you use ABC, you cant use Stat Values.. And tax account being a balance sheet account cant be taken to COPA
Regards
Ajay M

STO Conditions to COPA

Hi,
we have a scenarion where the sales order is placed in the trading company and a STO would raised to another manufacturing company to do the production. my question is Some of the SD conditions are drwn to the STO. can i map the conditions in STO so that it would populate into COPA during the time of billing, since some of those conditions are not in the intercompany billing document.
Thanks in advance
Roville

Hi Roville
The biling of an STO in an inter company scenario will behave exactly the same way as normal billing
If you add those conditions to pricing procedure, and map them to value field in KE4I - It will flow to COPA (Provided the GL is created as 11 or 12 category cost ele)
Regards
Ajay M

Disable or Hide or INACTIVE the CONDITIONS tab in ME22N(Change Pur.Order)

Hello,
We want to hide or Inactivate or greyed out all fields of CONDITIONS tab at 'Item Detail Level' while editing or changing Purchase Order(ME22N) for particular PO type.
I am not able to find the particular BADI or Enhancement or SCRREN EXITS, so that I can make greyed out all the fields of CONDITIONS tab at 'Item Detail' level while editing or changing Pur.Order(ME22N)
Regards,
Mahesh

Hi Mahesh,
[http://wiki.sdn.sap.com/wiki/display/Snippets/TransactionVariant-AStepbyStepGuidefor+Creation]
[Hide Conditions|Hide conditions in PO;
Create a transaction variant and try.
Regards,
Madhu.
Edited by: madhurao123 on Aug 9, 2011 9:30 AM
Edited by: madhurao123 on Aug 9, 2011 9:34 AM

Error while releasing Billing: Assign HD00 (Frieght) Condition type in COPA

Hi,
I am getting the below error while releasing billing document.
Assign condition HD00 type in COPA
HD00 condition type is frieght condition type
Is it good thing if we assign this condition type to COPA value field in KE4I? or we should not assign Frieght condition to COPA?
Please advise
Thanks
Kishore

HI Kishore,
To which GL account are you posting this freight condition value? Is that GL created as a revenue element (of category '11'/'12')?
If yes (has to be 'yes', since you are getting the error message), then you don't have a choice but assigning a CO-PA value field in KE4I. The idea here is, if you have created the GL as revenue element, then you intend to take it to Controlling module for further analysis. Thus, making your FI/CO reconciliation easy.
If you do want to carry this value to CO-PA for analytical reporting then don't create that particular GL (assuming you are posting freight to a separate GL) as a revenue element. That said, it does make sense to carry this value to CO-PA and in your present case, you don't have a choice as the message which you got is an error message, which you can't circumvent.
Hope this helps.

Inactive conditions when AZWR is used

Hi,
All condition types in pricing procedure are set to inactive, when condition type AZWR is determined.
My doubt is will system calculate taxes and discounts for this downpayment.
Please help
Thanks

Hello,
please have a look at the conditions which are excluded by the condition AZWR.
In the condition detail there is the inactive indicator. This indicator gets an information why the condtions are excluded.
maybe you use eclusion procedure with exclusion groups.
Please check the systembehaviour.
Regards
Claudia

What does 'condition inactive' mean? Thanks in advance!

Hi, This question has puzzled me many days, but still no answer. Any one can help me ? Many many thanks!!
In SAP GUI, under item conditions tab, there is a column 'Exception' with traffic lights.
Three kinds of tracffic lights are avaible in this column, red, green, and Amber Light.
The explantion of F1 help is not so clearly. My questiones are:
1. If a condition type is with 'amber light', what does that mean?
2. If a condition type is with 'green light', what does that mean?
3. If a condition type is with 'red light', what does that mean?
4. If a condition type is inactive, How can I know why this condition type is 'inactive'?
Thanks soooooo much!!
Regards,
Hedy
Edited by: hedyee on Jul 25, 2009 12:06 PM

Hi,
Condition inactive means, condition is not active in that particular transaction.
The meaning for traffic lights is
Red: Condition Contains errors, which has to be rectified before saving.
Green: Condition is active in the transaction and the prices are taken into consideration.
Amber: Condition is inactive on various reasons (for e.g., due to subsequent price)
If a condition is inactive, the tool tip in Web UI shows the reason. But in SAP GUI, We need to go through the pricing procedure.
Regards,
Krishna

Inactive conditions in Pricing

Hi all,
In our company product after pricing engine execution, if a condition has KINAK not initial we are considering it as INACTIVE condition and not considering it in Price Calculation.
But one of our clients says we have to consider a condition if KINAK = Y which is also considered by SAP standard Pricing.
I want to know what are the other cases of considering conditions if KINAK is not initial and why do we do that ?
Thanks in Advance.

Hi Kishore,
There are various options at which condition type is considered as Inactive
INACTIVE : A
if Condition is inactive with message as A , then there would be another condition added in the condition Exclusion ( best condition within two condition types)
INACTIVE : K:
This value is set only in shipment cost document. if there are two condition types for freight in sales order in which both shared same combination, system will set one of the condition as Inactive with K
INACTIVE : L
condition is set to inactive as L , if the Header condition is not active or set as Header condition exclusion
INACTIVE :M:
one condition type determined in sales order using Condition record and you also tried to enter manual price for the same condition type which will inactive condition value triggered with condition record, in that case , condition type will set as inactive with M
INACTIVE : X
this will result, if any of the routines such as Requirements, alternative calculation type and conditon base formulas are set correctly or not
INACTIVE: Y
if two or more condition types is determined in the sales order which is valid which have same properties, then automatically one valid record will be active and all other lower conditions will set as inactive with Y
for example, if you have one Price with 100$ and other has been enteed manually with 110$, then system will set price with 100$ to inactive with status Y
hope you understood
revert if you need some more information

Zero not allowed for price condition type

Hi experts,
   I have a scenario related to return. Based on the received return goods quality, we give different % of reimbursemnet to our customer.
Currently, in my pricing procedure, I have
PRICE COND 1 (which is the original selling price) (not allow manually change)
HA00 (depends on the % of reimbursement, we apply a %. Let's say we give 70% reimbursement to our customer, then we input -30%)
PRICE COND 2 (which is the net value of PRICE COND1 and HA00, calculate type is 2 - Net value)
For PRICE COND 1, and HA00, we haven't assigned any account key to them, since they are for reference only and shouldn't have any account posting.
The problem now is that, we received return goods with damage, and need to give 0% inbursement. For inventory point of view, we do receive the damaged goods and then directly go to scrap. However, when we try to input -100% in HA00 (so net price for that item is 0), error occurs when we issue credit for return, account cannot determined for PRICE COND 1 and HA00. It is because when PRICE COND 2 is not zero, PRICE COND 1 and HA00 are both become inactive in conditions. But now, since PRICE COND 2 is zero, both PRICE COND 1 and HA00 are become active and due to missing account key, it creates the error during account determination.
   Please kindly help. Thanks.

hi gundam,
   why do u need to create a credit memo for 100% loss?
just need the material movement document that will update the stock accounts then add a billing block.
thank you and best regards.

How to Avoid Duplicate Pricing Condition Types In Sales Order and Billing

Hi SAP Gurus
I have a requirement in Pricing (Sales and Distribution). We have issue duplicated condition types in Sales order and it causes wrong posting in to accounts.
I want make them inactive duplicated Condition type in Sales order and Billing Documents.
Please advice me how to make inactive status to duplicated Condition types
Thanks in Advance.
Ravikanth

Hi
You can use Exclusion Group
You can define 2 Groups and include 1 condition type in each
and define exlusion procedure
A   Best condition between condition types
B   Best condition within the condition type
C   Best condition between the two exclusion groups
D   Exclusive
E   Least favorable within the condition type
F   Least favorable betweent the two exclusion groups
you can use Exclusive to set your condition type or as per your requirement
Regards
Jitesh

Inactive SD Conditions to COPA

Similar Messages

Maybe you are looking for