COPA issue : Error in Value field data

Hi Experts,
I have created a new value field an assign it to the SD condition type in KE4I. But when I am creating a new billing document with this condition type, values are not flowing to this newly created value field.
Please help to solve this.
Regards,
Ankit Agarwal

Hi Ankit,
please go to transaction code VA03 and provide Sales order number and choose line item and click on item conditions. If you required more detailed click on analysis.
Please check whether the new condition type is getting updated with price (value) or not.
If the amount is zero, values will not be updated while posting the billing document against new value filed.
Ravi Polampalli

Similar Messages

SD- conditions to be mapped to COPA value field data in BI

Hi Experts,
I have a req where in I have to map condition level Sales order data to some COPA value fields. Currently for one Sale order item there are multiple conditions that means multiple line items. But when I try to find the COPA value field for the same same (Sales order, Sales order item ) key I get only one line item.
This has to be done for BI integration, but needs to be done at the source system level.
So my questions are,
1) How can we get the condition level data from COPA? Is it possible to fetch the data at that granularity?
2) Is it possible to integrate SD & COPA data on condition level i.e. at Sales order, sales order item & condition level.

Hi,
In KEA0, Data structure tab click on pencil button (change view).
Then click on -> change
Now you will be able to select new value fields
Rememeber, after changing click on save, activate and then back button. system will ask for regeneration, click ok.
Regards
Raghu

Settle Production Variances to COPA- Cost elements and Value fields

Dear All,
I know this question has been discussed in the past, but I have one specific doubt regarding this topic.:
When assigning cost elements to variance categories in t-code KEI1, how do we figure out what combination of cost elements (in the top half of the screen) constitute Input Price Variance, Scrap variance etc (in the bottom half of the screen)? I know the net of the postings on those cost elements tells us what variances we are looking it, but how do we get the cost elements (group) for let's say, 'Input/Output Quanity Varinace or 'Lot size Variance' ?
Or is this a futile exercise? May be I should just create three types of variances: Labor, Machine and Overhead. And I know what cost elements (net of the postings) would, in total, make up the $ variance in each of those categories. I can then use them in my report painter reports.
Please help clear the fog for me.
Ajay?
Thanks a lot,
Deepak

Hi Deepak,
Welcome to SDN!!
There are 2 ways of updating variances in COPA... I Prefer the 2nd option always...
1. Category wise variances (Input Prc, Usage var, etc) - Here, create a Cost ele group, where in you include all the Cost elements that can be posted to the Prod orders
For the sake of simplicity, you can include Cost elements 1 to 99999999 in the Cost element group...
2. Cost Comp Structure wise variances -
a. Create as many assignment lines in PA Trf Structure as in your Cost Comp Str...
Eg: If your Cost Comp Str in OKTZ has Raw Mat, Labor, Overhead - Create 3 Assignments in PA Trf Structure..
b. Assign the same cost elements in the SOURCE as in the Cost Comp Str
c. Choose the radio button "Costs/Revenues" in your assignment line, instead of " Variance on Production orders"
d. Assign each Assignment line to a separate Value Field
br, Ajay M

ORA-01841 Error when value for date col is NULL in .dat (using SQL Loader)

Hello Gurus,
I have some data in .dat file which needs to be loaded into oracle table. I am using SQL * Loader to do the job. Although "NULLIF col_name =BLANKS" works for character datatype, but when value for date col is NULL then I get ORA-01841 error. I have to make NULL for all rows withour value for date column
Early reply will be highly appreciated
Farooq

Hi,
May be this problem is not with the NULLIF. The value for the date column is not in proper date format.
create table:
create table kk (empno number, ename varchar2(20), deptno number, hiredate date)
Control file:
LOAD DATA
INFILE 'd:\kk\empdata.dat'
insert into TABLE kk ( empno position (1:2) integer external,
ename position(4:5) char NULLIF ename=BLANKS,
deptno position (7:8) integer external NULLIF deptno=BLANKS,
hiredate position (10:20) date NULLIF hiredate=BLANKS)
data file:
10 KK 01-jan-2005
20 10
SELECT * FROM KK;
EMPNO ENAME DEPTNO HIREDATE
10 KK 01-JAN-05
20 10
Verify the data file.
Hope it will help

COPA document generated , but value field 'Revenue' was missing.

Hi COPA-Experts:
I got a problem when tranferring 'Billing document to COPA'.
COPA document was generated but some value fields missing, like 'Revenue'
i checked it by T-code 'KE4ST'(simulate), everything is OK in that session.
then I checked the pricing procedure, the price condition type was assigned by 'KE4I'
Cost element was also checked , revenue account have a CE category '11',
ULINE
when i changed 'account assignment group' in Material Master,
(by VKOA, another G/L account assigned to account assignment group )
everything was OK both in COPA and simulating.
so i guess, account assignment group(material) is revelant to COPA value fields?
how did it do that?

Resolved.
Other one had written some code in user exit (SMOD "COPA0002"),
update some value fields by account assignment group for material.
then the user exit was assigned in KE4U.
so , that's the answer

RE: In COPA define value fields

Hi All,
My requirement is to create Value field for COPA
- how to create value fields and where to create and where to assign them
- i have to assign one (sale conditon type) for this what i have to do
i am trying to create in t code kea6 assigning in ke4i it is giving error message.
please let me know.
points will be assigned.

Hi,
First of all you have to create Operating Concern
2. Create Characterastics in KEA5
3.Create Value fields in KEA6
4. set your operating concern
5.assign SD condition type to Value field in KE4I.
6.check whether sd condition type created in V/08 for Pricing procedure.
Regards,
Sany.

Value Field in COPA doesn't updated in Pricing Procedure

Dear SAP Experts,
I have a problem about Value Field in COPA.
Why the Value Field in COPA that have been assigned to Transfer of Billing Document for Statistical Condition Type doesn't updated in Pricing Procedure (SD) when Billing Posting?
Any suggestion will be appreciated.
Thank You
Regards,
Kursteilnehmer

HI
in pricing procedure SD consultant are creating the pricing condition rules wher these keys are purley belongs to revenue keys .the conditions wich are taken consideration these are all belongs to finding profit margin.
coming to CO-PA the main objective of copa is analysig the profitability of particular segment .wher as in CO-PA the most happend flow from sd saide . so wat ever conditions are taking in pricing procedure its compulsary add co-pa valu fields .to take the reports.
even though in FI-SD interface levele this pricing is taking greater place to flow the values with the help accounting keys.
coming to stastical condistion co-pa is real cost object

Copa flow of actual values

Hi all,
In our COPA, we have some value field that are linked to SD documents and assessments from cost center. The issue is that the SD documents and the assessed documents have different prefixes. Is it possible to match the prefix, so that the same prefix is used for both, the SD documents and the assessed documents?
Thanks
Anne

HI,
SAPNET note 33178 describes the +/- sign logic in CO-PA. In line with that note, I suggest to do not assign SD-values and CO-values to the same CO-PA value field.
If you REALLY want to change +/- signs you can do that in COPA005 enhancement project by multiplying values with -1 but I guess this reates more problems than it solves.
best regards, Christian

Pring VALUE field as blank, if it's worth is 0.00

Hello,
I have value field (DATA: V_Net_Value TYPE KONV-NETWR) in my ALV grid display report. When i dont have any value, am getting 0.00 as output in my ALV report, but, user would like to see it as blank/nothing. Because of some reasons, i can not use a CHARACTER type field for outputting in order to get blank in ALV. Pls. let me know is there any other option/flag to get my requirement.
Thank you

There was a similar question which was discussed long back. You can check the idea suggested by Sourav Bhaduri here Replace amount in OOPS ALV
It sounds promising. I had not got a chance to try it till now. Other than this i donot see any other way( without converting it to type C ).
Just try like if input = '0.00' then output = space.

Purchase Rebate is adding to Material cost value field

HI,
When i execute purchase rebate scenario, that amount is adding to Material cost value field in COPA report. Kindly tell me what isthe problem and where is the link between this.
Thanks
KB

In customizing the integration of other modules with COPA you have keep in mind the sign logic because it may be different for values coming from different modules.
Example: In our system revenue-reducing sales conditions come to COPA with a negative sign. In postings that come directly from FI to COPA, a negative sign means earnings. So we cannot assign any Fi account for direct posting to COPA to the same value field as SD conditions, because the sign logic doesn't match. We have to use different value fields and then get the formulas right in creating COPA reports to get the correct result in COPA.
I think your problem here is of the same kind: Rebates from purchase seem to come with the same sign as cost of goods sold AND go to the same value field, although one consitutes cost and the other a reduction in costs.
I think you have to get your rebates to post to another value field. Are those rebates an MM-condition or do they go to COPA through an assignment of FI-account to a value field?
Regards
Nikolas

COPA Value Field +/- Error while releasing Billing Document for Return orde

Hi,
We have done Sale Order - PGI - Delivery and Billing for Quantity 10 and the customer returned 10 Qty due to some problem.
When i am doing the return process billing, I am getting the below error...
9000000892 000000 Check value field assignment for condition SGL1*
When condition "OR01" (application "V") was transferred to the value field "ERLOS" in operating concern "OR01" in
Profitability Analysis, the following became apparent:
o   The condition can take both positive and negative
    values
o   The flag "Transfer values with +/- signs" has not be
    set in Customizing for value field assignment.
Inconsistencies in the data could occur as a consequence.
Can any body help me on this issue
Is there any consequences if i activate +/- sign in KE4I for the above value field Please suggest me
Thanks
KC

Hi Kischow
You shud tick the +/- indicator only if
1. any One condition type repeats in the pricing procedure and can have +ve and -ve values
2. Two cond types in pricing procedures are assigned to same Value Field and the cond types can have +ve and -ve values
In COPA, all values are transferred as absolute values without + or - sign, with some exceptions ofcourse....
So, if you dont check + / - indicator in the cases mentioned above, say, +100 and -80 will be transferred as 100and 80 and the result will be 180 instead of 20
Regards
Ajay M

Assign direct material cost to value field in copa while issue to Prod orde

Dear All,
My requirement is like this:
There are some 16 material groups from A to P each containing some materials(finished goods).
I want to allocate overhead to different material groups(Charecteristic in copa) in COPA using the periodic assesment cycles. I am able to allocate overhead(admin & sales cost) to different value fields in copa from different cost centers.
I want to analyse the product cost and also the profitability of each material group in COPA using Report painter. Iam able to pull all the costs which i assign to value fields using assessment. But, i am NOT able to get the direct material cost which is issued to production orders using BOM.
My question is whether we can assign the direct material cost to any user defined value field(material cost value field) while the material is being issued to production orders. Is there any automated way where we can directly assign the direct material cost to value field in copa while issuing the material to Production orders.
Pls explain me whether we can do it. if yes how?
Thank you very much in advance.
Regards,
Vishnu
VST-IT.

PA is a Profitability analysis tool. That means it gets updated when a sale is made, not before. (Except for settlements and assessment of overheads.)
Goods issues for production gets updated in CO-PC, and needs to be analysed there. If you don't, you loose all the inbuilt tools for variance analysis, cost estimate comparisons, Wip Calculation etc. To the best of my knowledge, a Profitability Segment cannot be used as a cost object in Production Planning, because amongst others, you need to be able to capitalise the produced materials to stock at the end of the production run, or to WIP at the end of the Financial period,which is not possible with PS.
Similarly, overheads are recorded in CCA and needs to be analysed there.
If one goes against these big groupings in SAP, you always run into problems.

Excel 2007 accessing PivotItem.Visible gives error if the field item value is a DATE

I have VBA code to manipulate the content of a pivot table - essentially it hides all but the first N items in a pivotfield. Under Excel 2003 the code works fine, as expected irrespective of the data content of the pivot field item. Under Excel
2007, if the data content is a date, the VBA code generates one of several error conditions.
pivotItems(i).Visible = True
Generates error 1004 - Unable to set the visible property of the pivot class
If pivotItems(i).Visible = True then...
Trying to test the visibility generates error 13 - type mismatch
?pivotItems(i).Visible
Trying to determine the visibility of the pivot item in the VBA immediate window, this generates error 2042
I have an illustrative spreadsheet which permits the code to process two different pivot tables, one using a field containg dates; the other a field containing text. Under Excel 2003, the code works on both pivot tables. Under Excel 2007 it works
on the text field table, but fails on the date field table.
I have looked for answers on numerous support forums including answers.microsoft but found not found any answers... only the same or similar unanswered question.

Hi Herbert,
Thank you for your continued interest; please find a revised illustration of the problem here -
http://www.mediafire.com/download.php?zc6ty9ctl1n7yd9
I have made the following changes / additions to the problem illustrator:-
Adopted the use of lists for the data source of the pivot table
Removed reference to '(blank)' as a reserved item not hidden by the VBA code to avoid the possibility of hiding all items
In respect of my original code (MK1), utilised a 'real' item name to be the
reserved item
Added a new (MK2) macro to alter the number of visible items which
hides all but one of the VisibleItems collection
makes the first N items in the collection visible
checks that there are only N items visible (the position of the reserved item
might be greater than N)
The code still executes as expected under 2003, but fails (the same as before) under 2007 when the data type of the PivotItem is date.
The MK1 code fails when testing the current visibility of the Item before trying to set the visibility with:- RTE 1004 Unable to
get the PivotItems property of the PivotField Class
The MK2 code fails when trying to set the visibility with:- RTE 1004 Unable to
set the Visible property of the PivotItem Class as reported above. Note - given that MK2 avoids trying hide invisible items or unhide visible items, I no longer believe that this error is due to the attempt
to set visibility to current state as seen under Excel 2003. I am deeply confused by this now!
I observe with care the different CLASSES on which these failures are reported even though in each case the operations are on the PivotItem.Visible property - MK1 queries it / MK2 attempts to alter it.
Just in case you have been wondering where this is going, this spreadsheet has no prupose beyond illustrating the Excel 2003 / 2007 problem being encountered elsewhere when manipulating pivot table items whose value are dates. The requirement
is to provide a simple user interface to a complex managing reporting spreadsheet consisting of a significant number of pivot tables and charts - altering one cell causes the VBA code to modify the collection of pivot tables to deliver a revised view of the
data. All works fine for 2003 users of the model, but not 2007 users. I need one spreadsheet which will work correctly on both 2003 & 2007.
Regards.

Delete COPA value fields in a productive system

Does anyone have practical experience with deleting COPA value fields in a productive system?
The issue is that old, no longer used value fields should be deleted from a productive system to allow creating new ones, as the maximun number of value fields is reached.
An alternative would be to delete the prior transaction data captured on these no longer to be used value fields and rename them for their new use (to avoid that different kind of old and new data is reported on the same value field).
I am refering to the documentation on transaction KEA0 (or OSS note 160892 up to release 4.5), where it is mentioned that deleting value fields should only be done for operating concerns that have not yet been used productively. Did anyone do this already in a productive system?
Cheers, Peter

To delete characteristics or value fields, you should perform the following
activities:
1. Delete the corresponding characteristics and value fields from
Customizing in all clients (this includes forms, reports, planning
layouts, and so forth). To locate characteristics and value fields, use
the appropriate where-used list in the Customizing Monitor. You can
access it by choosing Tools -> Analysis -> Check Customizing Settings
(TA KECM).
You can jump directly from the where-used list to the relevant
Customizing transaction and then delete the appropriate field there.
2. Switch to the screen for maintaining the data structure of an
operating concern (Maintain operating concern).
3. If you need to effect other changes to the datastucture for the
operating concern before making any deletions, effect those changes and
save the data structure.
4. In order to be able to select the fields of the data structure,
choose Extras -> Characteristics (or Value fields) -> Unlock.
5. Select the characteristics and value fields to be deleted and remove
them from the data structure with the "Reset fields" function.
6. Reactivate the operating concern. The system starts by checking
whether the operating concern contains any data and whether the fields
to be deleted are still being used in any Customizing settings.
7. If none of the fields are still in use, the system then starts the
re-activation. If the operating concern does not contain any data or
does not require the database system to be converted, the tables are
activated. You are then able to activate the environment for the
operating concern. In this case, the following activities no longer
apply.
If the operating concern already contains data, a system message tells
you that the database needs to be converted. If you proceed, an
activation log appears (at the top of the list).
8. Analyze the activation log. If it only contains error messages
telling you to convert the tables, proceed with the next activity.
You must otherwise remove the cause of the errors before the tables can
be converted. In this case, you should answer "No" to the next prompt,
which asks whether the conversion transaction should start.
9. If you still only receive error messages telling you to convert the
tables, choose "Back" and start the conversion.
10. Plan a job for the conversion. A list of the tables to be converted
is shown for this. If the tables only contain a small amount of data
(less than 10 000 records), then all the tables can be converted in one
job. In that case, you can select all the tables.
For larger tables, conversion should take place in several jobs.
However, you should ensure that table CE4xxxx (where xxxx = operating
concern) is the last table to be converted.
Warning. No other changes can be made to the operating concern during
the conversion.
A copy of the table is generated during the conversion. The database
system should have sufficient memory available for this copy.
To schedule conversion as a job, use the "Schedule selections" function.
You can display the current status of the conversion by selecting the
"Refresh" icon. Tables disappear from the list once they have been
converted sucessfully. If a conversion is taking a while, it is also
possible to leave the transaction. You can then continue the conversion
using DB requests -> Mass processing in one of the following ways:
With the job overview. You access this by choosing System -> Services ->
Jobs.
Using the database utility transaction. You access this by choosing
Utilities -> Database Utility in the ABAP Dictionary menu.
You can use the status function to call up the status of the operating
concern during operating concern maintenance. You need to activate all
tables after conversion.
11. To analyze errors that have occurred during the conversion, you can
use the database utility transaction by choosing Extras -> Logs. The log
has the same name as the conversion job: TBATG-date. You can also
restart the conversion with this transaction.
For more information on the database utility, choose Help -> Application
help while still in the above transaction.
12. Once you have activated all the tables in the operating concern,
generate the operating concern environment from within operating concern
maintenance.
You can then use the operating concern again.
Please, refer to the IMG documentation under Controlling ->
Profitability Analysis -> Structures -> Define operating concern
-> Maintain operating concern, for further details.
Hope it helps

FI to COPA Value fields Currency translation

Hello All,
We are having the following situation.
1) The company code currency is RUB
2) Operating concern currency is EUR.
3) Second local currency as EUR.
we are using a customised program to run the settlement. This program calls the KE21 transaction and creates the settlement line items.
The program passes the amount in the document currency to Ke21 transaction and the transaction inturn does the currency conversion to operating concern currency EUR.
The issue is that because of this there are some differences in the Amount in FI and Amount in CO-PA in EUR currency because the RUB exchange rate is volatile.
The userexit COPA0004 will give control only to the exchange rate type that can be defined.
Please let us know whether there is any user exit or any other way to have a control on the date of the currency conversion.
We tried sending the Second local currency,in this case the amount in EUR(Operating concern) is correct but the amount in the company code currency-RUB in COPA (Ke23)is not matching with the FI amount.
Hence our assumption is that if we can have a control on the date of the conversion then the FI and COPA amounts will match.
Please let us know incase the above requirement can be achived in any other way.
Thanks in Advance.
Regards
Pavan M

You should be able to achieve this by implementing the COPA valuation enhancement. Enhancement COPA0002, EXIT_SAPLKEAB_001 can be used to populate value fields. To use the exit you first must assign an exit number to your valuation strategy (t-code KE4U), which you then use in the exit. You can find documentation for the enhancement there as well.
thanks,

COPA issue : Error in Value field data

Similar Messages

Maybe you are looking for