COPA account based extractor (Bill type field FKART) missing

Hello Experts,
I am new to COPA and currently working on account based COPA DataSource on ECC 6.0 & BI 7.0.
I have created the DataSource in KEB0 for account based by selecting the appropriate operating concern. One of the field requirements for me is to have billing doc type but it is not available in KEB0 or in RSA6.
When checked in KEA0 billing type (FKART) is available as display fixed fields.
Main menu -> extras -> display fixed fields.
Could you please let me know how to get this part of my DataSource?
Does enhancing the DataSource is only the solution?
Highly appreciate your help.
Best Regards
VJ

Hi Vijay!
If your current scenario does not present you with the standard extractor from the source system, perhaps you should try to create a generic datasource for your business requirements.

Similar Messages

COPA account-based only!

Hi
I intend to implement COPA for my customer, but only COPA account-based.
As my knowledge about COPA, costing based uses value fields instead of account as in account based.
But when i demo in client 800 (IDES), I realized that many diffirences between costing based and account based. It seem to be not only relevant to the value fields and account based.
For example:
when i post an invoice (fb50) in FI, then click profit segment field. I can not find characteristics that i want to post to such as material group. And there is nowhere for choosing all characteristics in client.
How can i find the way to post to characteristics that i want to post to directly from FI to PA?
Another example:
when I create report in PA account-based, there are limited characteristics in compare with PA costing based, so I can not choose profit segments i want?
What's the problem here?
Is it possible? Which problems can I meet if i do not use costing-based?
I am apreciated any help of you!
Thanks

Couple of things:
In Account based CO-PA:
1. You can't get Cost component break down.
2. No break down of variance categories.
3. Create a Characteristic in KEA5 and add to operating conern in KEA0. KEQ3 is to define segment level characteristics. To improve system performance, you can also restrict the characteristics that make up the profitability segment.
4. When you add a characteristic to operating concern, then by default that characteristic is available at the time of document entry. We use characteristic groups to determine what characteristics appear in which order on the screens for assigning profitability segments in different business transactions. If no characteristic groups are defined, the user can enter values for any characteristic in the operating concern.
5. Account based CO-PA uses the same tables (COEP, COEJ, COSP, COSS etc.,) as used by overhead cost management, whereas costing based COPA has it's own tables. The definitions of profitability segments for both CO-PA sub-modules are stored in the same table, the CE4XXXX table (where XXXX = operating concern).
6. Period account approach, unlike costing based which is cost of sales accounting approach.
7. Account-based CO-PA stores all transaction in three currencies: the transaction currency, the local currency, and the controlling area currency.
Also, check SAP note 69384 on account based COPA.
What kind of business is your client in? What reporting is he expecting out of CO-PA?
Edited by: Pradeep kumar Athmakur on Dec 31, 2009 6:32 PM

COPA Account Based Problem

Dear All,
I had created two DataSource for COPA one is Cost Based and another is Account Based using T-code KEB0 in R/3 Dev. I can able to see the data in RSA3 for Cost Based but when come the Account Based it is giving "Error Occured during the extraction" (When i get into the Help -During the extraction phase an error occurred for the extractor. An exception, 'error_passed_to_mess_handler' was triggered.-).
Could any one please help me in creating of COPA Account Based, and please do help me in some notes.
Thanks in advance,
Prashanth

Hi all,
the solution is:
the extractor needs a summarization level in CO-PA --> see OSS 392635 (TC KEDV).
After Creation of this level you have to build new level (TC KEDU) --> fill with data.
After this you have to create the datasource CO-PA.
Notice: lucky time entry: e.g. 2005.001 in RSA3, RSA6
Questions remains: why does this information/hint (sum. level missing?) is not included in the error message.
Dieter

How can I create ACCT_BUDAT into COPA account based data source?

hi Friends,
I create a COPA data source use standard BI function: KEB0 and find that the posting data(ACCT_BUDAT ) can not include into it.
I checked the table CE4xxxx_acct and find that it has already in it, however when I check tcode KEQ3 I found that this field is not in the list.
So can anybody tell me the reason and advice? the posting data is important for the report. Also if possible, may I include the COPA document number into the COPA account based datasource?
thanks very much!

Hi,
   The posting date BUDAT is not a characteristic ; its just a technical field.
   There is a logical reason for this
The CE4XXXX table basically holds a unique PA segment no for a unique combination of characteristics. For example let us say you have only 2 characteristics customer and product. Then let us say for customer 1 and product 1 you have PA no 1; for customer 2 and product 2 PA no 2 and so on. Every time you post a document with customer 1 and product 1 the same PA no 1 will be reused i.e. no new entry will be made to CE4XXXX.
   Now if you were to introduce a new characteristic called date in this table then every time the date changes a new PA no will have to be generated and the entries in CE4 table will grow. This will make reporting more difficult and will also cause performance problems.
regards
Waman

CO -PA Account based extractor

Hello
We want to create a CO -PA Account based extractor delta. We have created the summarization levels (KEDV) and tried fill it with Data (KEDU). The problem is that this process takes too much. It spends too time and reach the time out for the machine. How may I optimized this time? Is it true that we must run this transaction before each load in BW not only for BW Full load but BW Delta load by CO -PA Account extractor?
Thanks.

Hello
We want to create a CO -PA Account based extractor delta. We have created the summarization levels (KEDV) and tried fill it with Data (KEDU). The problem is that this process takes too much. It spends too time and reach the time out for the machine. How may I optimized this time? Is it true that we must run this transaction before each load in BW not only for BW Full load but BW Delta load by CO -PA Account extractor?
Thanks.

Customizing CO-PA Account-Based Extractor

A requirement exists to customize our Account-Based CO-PA extractor. The Costing-Based extractor has been customized/appended but some team members have suggested that AB-PA extractor should not be. These would all be characteristics. Is there a problem with adding fields to this extractor - and if so, why? Any differences from adding to the Costing-Based? Thanks.

Don,
CE1 and CE2 tables are the ones to store actual line items and plan line items. I am pasting the relevant para from SAP help at the bottom of my msg.
Reg your other question, what level of summarization your users are talking about?
Ravi Thothadri
Physical Structure of the Data in CO-PA
The following sections describe the detailed physical structure of the data (physical insertion sequence) and the typical accesses of the dataset.
In the section Physical Distribution of the Data in CO-PA, we will propose a way to distribute the data effectively over larger areas (table spaces, hard drives, striping, and so on).
Documents
Actual line items are stored in table CE1xxxx (where xxxx = operating concern). The system inserts into this table on an ongoing basis (sorted according to time stamp of the insertion point).
In drilldown reporting, cost center assessment, etc., the system accesses the data by this time stamp. Thus the physical insertion sequence corresponds to the typical read access method.
Plan line items are stored similarly in table CE2xxxx and are accessed in the same way. Consequently, this table will not be referred to separately in the following.
Segment Level
The segment level -- CE3xxxx -- contains the data in its first summarized form. The profitability segment number and the period are key fields (along with additional technical fields: plan version, record type, plan/actual indicator, etc.). The data part consists of the value fields.
The data in the segment level is typically sorted by period when it is created (INSERT) and updated during the period. That is, the insertion sequence depends on the random order in which the business transactions occurred and is only sorted roughly according to period (or period block PERBL).
The typical queries search in the segment level with a few (approximately 100) fixed segment numbers (WHERE PAOBJNR IN <List> ...) and a condition of time (... AND PERBL IN ...). Thus the physical insertion sequence does not correspond to the typical read access sequence! The segment level is always accessed via the primary index CE3xxxx__0.
Segment Table
The segment table CE4xxxx contains a unique profitability segment number (the primary key) for each combination of characteristic values (data part) to which data has been posted.
The records are inserted in the order of the profitability segment numbers (albeit only approximately, due to buffering of the segment number assignment on the application servers) and are practically never changed.
Selections from the segment table can generally be divided into two groups:
Selections of large data volumes for drilldown reporting, planning or cost center assessment
Here the system finds all the profitability segment numbers whose combination of characteristic values meets a specified condition (e.g. in a drilldown report). If a suitable index exists, the system uses it to access table CE4xxxx. In that case the access does not correspond to the physical insertion sequence. If no suitable index exists, the system selects using the primary index. To read about how you can improve performance for this type of access, see Physical Distribution of the Data in CO-PA.
Determination of a profitability segment number based on the known combination of characteristics
In this case the system finds the profitability segment number when the values of all characteristics are known. To read about how you can improve performance for this type of access, see Index Support for Determination of Segment Numbers.

Account Based PA Billing Qty

Hello Guruu2019s:
If I have multiple condition types in a pricing procedure, when I release billing to accounting in account based PA, I see Sales Qty associated with the account mapped to first condition type in my procedure. Is there anyway to replicate billing qty to all Accounts mapped in account based PA?
Regards
Raghu

Hi,
Please read the note 160011. It explains how you can change the standard behavior in this regard.
I quote from the note:
"customer can influence the quantity update in CO in the SD user exit for the G/L account item (EXIT_SAPLV60B_004): Set indicator XACCIT-XMFRW (quantities in accounting) to 'X' for all rows of the accounting document (structure ACCIT), for which the quantity should be updated in CO. "
Please test this throughly in test system and see if it meets your requirements.
regards
Waman

COPA : Accounting Based and Costing Based

Hello Guru's,
We are on ECC 6.0 and BI 7.3. Our customer is going to implement Accounting based COPA and Costing based COPA in ECC. We have a requirement to have both the Accounting based and Costing based COPA analysis available in BI.
My questions and concerns:
If we configure both type of COPA in ECC then Can we create both type of data sources also in ECC ? one for Accounting based COPA and one for Costing based copa ? If yes then do we need to have 2 infocubes in BI or one infocube with mapping of both the data source will work ? ... do please correct me or suggest me.
Regards,
Komik Shah

Hi Sridhar,
Thanks for your reply, can you explain if we want to stop one of the method, what is the steps that need to be done?
thanks again!

COPA Account based Report

Hi,
Can any one explain the procedure to prepare account based COPA report.
Thanks in advance.
Thanks
D.K.Lakshmi Narayana

Hi,
You can try KE31-KE34 for managing reports in COPA. KE30 has the list of reports.
Rgds.

COPA Account based extraction error

We have an account based COPA Datasource modified to add another characteristic.
All the pre-reqs involving this re-generation( new characteristic in same operating concern) have been done by R/3 consultant. During Transport, it works fine in all instances but production. All the R/3 checks(KEDV,KEB0 ...) have been performed and summarization levels have been generated. In BW everything is in order, but when trying to load data(full load) it fails with zero records. The error message is
"No source could be found to answer the search query"
Any thoughts?
Thanks!

Thanks Sam for your answer.
The R/3 functional consultant confirms that the summarization levels are generated properly and nothing seems to be amiss there.
Is there a SAP note on this?
Thanks for your answers . Any more thoughts ?

Deactivate COPA postings for particular billing type

Hi
We have a requirement that for particular billing type, values of billing documents should not flow to COPA & no posting should be made in COPA for such documents.
Can someone please guide how to go about for such requirement.
Regards,
Santosh

Hi
Any pointers on this would be helpful.
Regards,
Santosh

Select query based on Simple Type field in JDT

Hello Experts,
We have a JDT table consisting of a field "CONSUMPTION_ID" which refers to a Simpletype.So at oracle level the datatype of the field shows as CLOB instead of String. I am unable to use this simple type field in the WHERE clause in my bean .
Following are the queries i have tried and the errors i have got executing them :
Query1 - SELECT * FROM TEST_TABLE WHERE CONSUMPTION_ID <> 'RT'
Error - com.sap.sql.log.OpenSQLException: The SQL statement "SELECT * FROM "TEST_TABLE " WHERE "REF_MAT_DOC_NO" = ? AND "REF_MAT_DOC_YEAR" = ? AND "CONSUMPTION_ID" <> 'RT'" contains the semantics error[s]: - 1:84 - type check error: the expression >>"CONSUMPTION_ID"<< (CLOB) is not comparable and must not be used with "<>"
- 1:84 - type check error: the left hand side >>"CONSUMPTION_ID"<< (CLOB) and the right hand side >>'RT'<< (CHAR) of a comparison operator are not comparable
Query 2 - SELECT * FROM TEST_TABLE WHERE to_char(CONSUMPTION_ID) <> 'RT'
Error - com.sap.sql.log.OpenSQLException: The SQL statement "SELECT * FROM TEST_TABLE WHERE REF_MAT_DOC_NO = ? AND REF_MAT_DOC_YEAR = ? AND to_char(CONSUMPTION_ID) <> 'RT'" contains the syntax error[s]: - 1:91 - SQL syntax error: the token "(" was not expected here
Please let me know if any one has used WHERE clause on fields which refer to a simpletype in JDT, or any other solution to the above problem
Regards,
Virag

Hello Experts,
We have a JDT table consisting of a field "CONSUMPTION_ID" which refers to a Simpletype.So at oracle level the datatype of the field shows as CLOB instead of String. I am unable to use this simple type field in the WHERE clause in my bean .
Following are the queries i have tried and the errors i have got executing them :
Query1 - SELECT * FROM TEST_TABLE WHERE CONSUMPTION_ID <> 'RT'
Error - com.sap.sql.log.OpenSQLException: The SQL statement "SELECT * FROM "TEST_TABLE " WHERE "REF_MAT_DOC_NO" = ? AND "REF_MAT_DOC_YEAR" = ? AND "CONSUMPTION_ID" <> 'RT'" contains the semantics error[s]: - 1:84 - type check error: the expression >>"CONSUMPTION_ID"<< (CLOB) is not comparable and must not be used with "<>"
- 1:84 - type check error: the left hand side >>"CONSUMPTION_ID"<< (CLOB) and the right hand side >>'RT'<< (CHAR) of a comparison operator are not comparable
Query 2 - SELECT * FROM TEST_TABLE WHERE to_char(CONSUMPTION_ID) <> 'RT'
Error - com.sap.sql.log.OpenSQLException: The SQL statement "SELECT * FROM TEST_TABLE WHERE REF_MAT_DOC_NO = ? AND REF_MAT_DOC_YEAR = ? AND to_char(CONSUMPTION_ID) <> 'RT'" contains the syntax error[s]: - 1:91 - SQL syntax error: the token "(" was not expected here
Please let me know if any one has used WHERE clause on fields which refer to a simpletype in JDT, or any other solution to the above problem
Regards,
Virag

COPA : account based vs cost based?

Hello
Can somebody clearly explain me the difference between AB and CB COPA types
I dont need copy paste from help as it doesnt clarify anything

Plz follow forum rules.
this query is answered multiple times

COPA Costed and Account based

Hi Experts,
I have running In BW, PA Costed based, and now I need activate PA accounted based extractor.
a) does somebody have any doc or how-to papers, specific about COPA Accounted?
b) can will appear any issue or problem about my current PA costed based loads?
c) how can I see with pa model (costed or account based) is running in the R/3 instalation?
Thank you in adavance!

Hi,
Costing-based Profitability Analysis is the form of profitability analysis that groups costs and revenues according to value fields and costing-based valuation approaches, both of which you can define yourself. It guarantees you access at all times to a complete, short-term profitability report.
Account-based Profitability Analysis is a form of profitability analysis organized in accounts and using an account-based valuation approach. The distinguishing characteristic of this form is its use of cost and revenue elements. It provides you with a profitability report that is permanently reconciled with financial accounting
Hope this helps
Regards,
Aparna

Billing type based on plant

Dear experts,
The client requires the billing type to be default based on plant.
I tried searching for it but could not find. Kindly let me know the possibility of achieving this.
Thank you.

Dear SCM.Sd,
There are 2 options.
One is standard where you will have to maintain copy control between your delivery type and all the different billing types which represent billing from each plant.(assuming that in the scenario, you have a single sales order type and delivery type).
Now during VF01, user can manually select the billing type and do the billing .
Else identify an exit during vf01 (creation) , and write a code to check the plant from the delivery.
For that put the delivery number in LIKP as VBELN and fetch LIKP-WERKS.
In the code , you will have to either hardcode the plant-billing type combination or
it is better to maintain an Z-table where we can maintain PLANT- BILLING TYPE, so that in future when more plants are created, we can easliy maintain it here in Z-table than re-work on the code.
So in the exit, write the code to find the Plant as per the above logic (from LIKP-WERKS) and put that WERKS in Ztable to find the corresponding billing type and input it automatically in the billing type field in VF01.
Thanks & Regards,
Hegal K Charles

COPA account based extractor (Bill type field FKART) missing

Similar Messages

Maybe you are looking for