COPA Extraction Error

HI friends ,
My COPA extractor 1_co_pa_200_2000_1 , is showing me records in rsa3 ( R/3 ) & but when transferring in BW , it is giving "Error in source System ".
What could be the possible reason & how to correct that.
Regards
Ankit

Hi
Check the assignment to the source system is proper. You can seek the help of basis for this
Second, ensure that this datasource is never extracted to BW anywhere other than the infoarea your trying
Regards
N Ganesh

Similar Messages

COPA extraction issues - Incorrect field name for selection

Dear gurus,
I've issues with my COPA extraction, hope you guys could give me some clue here, point will be rewarded if I could fine the solution.
Requirement:-
To add additional field.
Step:-
As usual 1) Delete
2) Create back with select the new field. (KEB0)
3) Do not have issues when check RSA3 from DEV, but when transport to QAS I hit this issues.
Issues:
At RSA3 , when do check hit the error, "Errors occurred during the extraction"
When check from RSA3 log here I get..
** Did try to find any solution in SCN forum, with no luck. Hope get some help here.
thank you
rgds
Edi.

Yes I did get this feedback ..
Hi Edi,
As per the standard SAP, once you have assigned characteristics and values fields to your operating concern (KEA0), you can't de-assign them. When characteristics or values fields are in assigned status, you can't delete them.
But I hope there won't be much problem of having that characteristic also. If you look at performance wise, then instead of deleting, make "not used" under profitability segment characteristics, remove from the characteristic groups etc. While doing so, please check any derivation rules written based on these, or any assessment cycles defined with these also..
Regards...
Jose
forward to my FICO ..

CC 2014 update extraction error on Mac

When attempting to update to CC 2014 on Mac OS 10.9.3, I'm repeatedly met with "Update Failed: Unable to extract the downloaded files. Press Retry to download again. (U44M1I210)."
Strange enough, Adobe Media Encoder and Adobe After Effects updated to their 2014 versions no problem, but this broke the dynamic link to Premiere. (Another hassle to deal with throughout the work day until Premiere is updated)
Adobe Illustrator stalled at 42% for 3 hours, so I quit the Creative Cloud manager and tried again. Continuously met with the same extraction error message.
Any resolutions out there? Restarting the computer and repairing permissions has not yielded any change.

Hi Rave,
Thank you for taking the time to reply. I found that simply deleting the ~/Library/Application Support/Adobe/AAMUpdater/ directory was a faster solution than taking the time out of my day to uninstall and reinstall all of my Adobe apps. I will be submitting a bug report to address the issue with the Creative Cloud updater.
Thanks,
dtderong

COPA Extraction

Hi Friends,
Im new2 BI7.
1)Plz provide detailed info on hw 2 go abt for COPA extraction.
2)I need 2 make Customer specific Datasources.So plz guide on this
3)Since my existing Copa reps r frm Report painter/Abap,they just drill down 2 multiple screen,,Is multiple drill down functionality possible in BI?If so plz provide details on hw to make sample drill report.
4)Wat are the crucial steps to take in Copa extraction.
Plz provide any links/ppts/pdf's.
It vll be highly appreciated.
Thanks & Regards.

CO-PA:
CO-PA collects all the OLTP data for calculating contribution margins (Sales, cost of sales, overhead costs)
CO-PA also has power reporting tools and planning functions however co-pa reporting facility is limited to
          Integrated cross-application reporting concept is not as differentiated as it is in BW.
     OLTP system is optimized for transaction processing and high reporting work load has negative impact on the overall performance of the system.
Flow of Actual Values:
During Billing in SD Revenues and Payments are transferred to profitability segments in Profitability Analysis at the same time sales quantities are valuated using standard cost of goods manufactured.
In Overhead cost controlling primary postings is made to objects in overhead cost controlling and assigned to relevant cost object. Actual cost of goods manufactured also assigned to cost objects and at the same time performing cost centers are credited
The Production Variances calculated for the cost objects i.e. the difference between the actual cost of the goods manufactured and the standard costs are divided into variance categories and settled to profitability segments (example production orders).
What are the top products and customers in our different divisions. This is one of the typical questions that can be answered with CO-PA Module.
Characteristics are the fields in an operating Concern according to which data can be differentiated in Profitability Analysis.
Each characteristic in an operating concern has a series of valid characteristic values.
Profitability is a fixed combination of valid characteristic values.
Characteristics:
Some Characteristics are predefined in Operating concern like Material, Customer, and Company Code. In addition to these fixed characteristics we can define up to 50 characteristics of our own. In most cases we will be able to satisfy our profitability analysis requirements with between 10 to 20 Characteristics.
Value Fields:
Key Figures like revenue, cost of goods sold, overhead costs are stored in value fields.
Organizational Structure:
The Value fields and Characteristics that are required to conduct detailed analysis vary from industry to Industry and between Individual Customers.
In CO-PA we can configure structure of one or more operating concerns in each individual installation.
An operating concern is an Organizational Structure that groups controlling areas together in the same way controlling areas Groups Companys together
Data Base Structures in CO-PA:
Actual Line Item table:      CE1xxxx
Plan Line Items: CE2xxxx
Line Item Contain some information at document level that most cases is too detailed for analysis example CO-PA Document Number, Sales document Number, Posting date.
CO-PA Maintains summarization of data used by all CO-PA functions like reporting, planning, assessments, settlements and so on.
Actual Line Item table:      CE1xxxx
Plan Line Items: CE2xxxx
Line Item Contain some information at document level that most cases is too detailed for analysis example CO-PA Document Number, Sales document Number, Posting date.
CO-PA Maintains summarization of data used by all CO-PA functions like reporting, planning, assessments, settlements and so on.
Segment Table: CE4xxxx
The Characteristics that describes the market are first separated from the rest of the line Items.
Each combination of characteristic vales is stored in profitability segment number. The Link between the profitability segment number and characteristic values is maintained in Segment Table.
Segment Level: CE3xxxx
The Value fields are summarized at profitability segment and period levels and stored together with these fields in Table CE3xxxx.
This table contains total values of the period for each Profitability segment number.
Storage Procedure:
We can compare an operating Concern associated by segment table and segment level to an Info cube. Info cube comprises Dimension Table Segment Table) and the fact table (Segment Level).
Unlike Fact table the segment level key contains other keys like processing type in addition to the key field from the segment table.
Characteristics in Info Cube correspond to characteristics (Or Attributes) in Info Cube.
Value fields can be regarded as a Key Figures.
Summarization level in Operating Concern have the same function as aggregates for an Info Cube, the difference is that aggregates for Info Cube are managed together with the Info Cube Itself while summarization levels are updated at regular intervals usually daily.
Line Items in CO-PA is comparable with Operational Data Store
Data Staging Overview:
To Provide Data Source for BW all CO-PA Data Sources must be generated in the Source System.
Data Sources can be defined at Operating Concern and client level.
Data Source contains the following Information
Name of the Operating Concern
Client
Subset of the Characteristics
Subset of the Value fields
Time Stamp which data has already been loaded in to BW.
Creating Data Source:
Since Data Source is always defined at operating concern and Client levels a standard name is always generated which starts with 1_CO_PA_<%CL>_<%ERK . We can change this name if necessary however the prefix 1_CO_PA is Mandatory.
Data Source-Segment Table:
Characteristics from the segment table are the characteristics that are maintained in transaction KEQ3.
By Default all characteristics are selected.
Data Source-Accounting Base:
When we generate CO-PA Data Source select accounting based option.
Fields KOKRS, BUKRS, KSTAR are compulsory.
There are no Characteristics available for line Items because accounting based data sources do not contain characteristics.
There are no value fields or calculated key figures available
KOKRS and PERIO must be selected as selection fields.
Hope it will helps you........

COPA EXTRACTION---BASICS TO ADVANCE

HI GURUS,
I AM NEW AND PRACTISING COPA EXTRACTION.
SORRY I AM EDITING IT FOR MORE CLARITY.
I KNOW THAT THEIR R
CHARCTERSTICS
CHARCTERSTICS VALUES
VALUE FIELDS
SEGMENT LEVEL
SEGMENT TABLE
HOW THEY R LINKED TO EACH OTHER-- BECOZ WHEN I COMPLETE THE SELECTION -
THEY ALL APPEAR IN ONE GROUP --AND HOW TO MODEL A INFOCUBE (DO WE NEED TO GO BACK TO R/3 TO CHECK.)
ON R/3 SIDE-- WHEN WE DEFINE COPA DATASOURCE WE DO AT OPERATING CONCERN LEVEL...RIGHT??
I WANT TO KNOW WHEN DEFINING WE DO SOME SELECTION OF
CHARCTERSTICS FROM THE DATA SOURCE...WHAT IS THAT BASED
ON WE HAVE TO DO OUR OWN ANALYSIS R ELSE ....THE CLIENT
WILL BE GIVING THE REQUIRED SELECTION .CRITERIA.
SORRY ONCE AGAIN FOR POSTING CONFUSED MSSG I AM DESPARATE TO UNDERSTAND THIS....PLZ TRY TO UNDERSTAND AND HELP ME.
Message was edited by: neelkamal moganti
Message was edited by: neelkamal moganti

If i've understood now you have to link your datasource to the infosource and then create the infopakage; there you can find selection criteria.
Regards

Cost Center hierarchy extraction errors

Hi,
I'm trying to extract R3 Cost center hierarchies into BW and in doing so, I get following errors. Could some one shed some light on these errors.
Extraction (messages):Errors occured
Error occured in the data selection
But, I successfully extracted Cost center master data from R3 just before hierarchy extraction.
I also checked RSA3 for the hierachy that I'm trying and it pulled around 2000 records in R/3 datasource extractor.
Appreciate any help
Hari Immadi
http://immadi.com
SEM BW Analyst

Hi,
Thanks for your reply.
I replicated the datasource before starting the extraction & also I double cheked the hierarchy name between BW & R3.
I don't get any other useful messages in the log & here is the entire log.
Requests : Everything OK
Extraction : Errors occured     --> Errors occured in the data selection
Trasnfer IDOCS & TRFC :     Everything OK
Processing (data packet)     :     No data
Subseq processing          :     Missing messages
Soon after execution of extraction, I get ALE Inbox error as follows & I double cheked that hierarchy in R/3 is not being edited.
Express document "Check Load from InfoSource 0COSTCENTER" received from author " Warehouse background user"
Check Load from InfoSource 0COSTCENTER , Packet Cost Center hier test
for demo
Please execute the mail for additional information.
Error message from the source system
Diagnosis
An error occurred in the source system.
System response
An error occurred in Service API .
Check the error message.
Procedure
The procedure for removing errors takes place depending on
the error message:
Note
If the source system is a Client Workstation, then it is possible that
the file that was to be loaded was being edited at the time of the data
request. Make sure that the file is in the specified directory and is
not being edited, and restart the request.
Note: If you not wish to receive any mails, maintain transaction
RSMONMAIL.
Hari Immadi
http://immadi.com
SEM BW Analyst

Photoshop CS3 Eng Widows WebInstaller Extract Error

I downloaded Photoshop CS3 and run the installer. After it extracted some part of installator files it displays extraction error, so the installator placed on the ADOBE.COM web site is corrupted. Where to find correct one?

Lets say. I tryed on 2 mashines: 1 in corporate network and second in home lan. Everyone of them have NOD32 antivirus installed and do not reported anything suspicios.
Problem still here.

COPA derivation error: no segment found

Hi
We are executing transaction code FAGL_IT_01 for the year ending closings we get the error message COPA derivation error: no segment found
Regards
Medha

Hi Medha
It seems you have written a derivation step in KEDR to derive segment.... Check your Der steps in KEDR and see if its written correctly
Also, in the attributes tab, you might have selected "issue error msg"... Is it so??
Br, Ajay M

Copa extraction and tables read

We want to perform currency translation for a copa extraction. The requirement to determine if translation takes place is currency type, company code and plan/act indicator.
I understand copa dynamically picks which table to read during extraction (I've read the notes).
The problem we face is that CE3 has the plan/act indicator, but no company code. CE4 has company code, but no plan/act indicator.
The only table that has all this information is CE1. How can we be sure all the correct records are translated if it reads from CE3 and CE4?
Our COPA datasource has line item information coming over. So I know it will be reading CE1, but what if it reads CE3 and CE4, this will create inconsistencies??
Thanks,
Mark.

Totalling can be done in reporting.
This is what I think - Since you are extracting line item level data, summarized data can't be extracted at that level as it will be incorrect( a total getting repeated for each line). If you have chosen even a single line item characteristic, summary level values can't be included in the datasource.
When you run a query, you have all the option to see the totals in various ways based on the line item level values.

Position Activity Sequence Resulting in data extracting error

hi gurus
can any body tell me what is this position activity sequence error resulting in data extracting error, plz help. this is very high priority for me.
regards
dev

I rebuild the report using a tabular form and populated the primary key with a PL/SQL expression and now it appears to be working. P1_ISSUE_NO is the primary key on the issue table and I could not figure how to get it in the issue_no field of the tabular report when a new line was entered I ended up putting the following code in for the default for
issue_no on the report:
Begin
return :P1_ISSUE_NO;
end
It works great.

Difference between LO and COPA Extraction and Steps

Hello All,
Can you please share the COPA extraction steps and also advise why COPA is differnt from other extraction (e.g.LIS/LO etc.) mechanisms?
And also advise what should be my aproach for any COPA extraction related reporting projects.
Thanks,
Mainak

Hi Mainak,
COPA Extraction -steps
R/3 System
1. KEB0
2. Select Datasource 1_CO_PA_CCA
3. Select Field Name for Partitioning (Eg, Ccode)
4. Initialise
5. Select characteristics & Value Fields & Key Figures
6. Select Development Class/Local Object
7. Workbench Request
8. Edit your Data Source to Select/Hide Fields
9. Extract Checker at RSA3 & Extract
BW
1. Replicate Data Source
2. Assign Info Source
3. Transfer all Data Source elements to Info Source
4. Activate Info Source
5. Create Cube on Infoprovider (Copy str from Infosource)
6. Go to Dimensions and create dimensions, Define & Assign
7. Check & Activate
8. Create Update Rules
9. Insert/Modify KF and write routines (const, formula, abap)
10. Activate
11. Create InfoPackage for Initialization
12. Maintain Infopackage
13. Under Update Tab Select Initialize delta on Infopackage
14. Schedule/Monitor
15. Create Another InfoPackage for Delta
16. Check on DELTA OptionPls r
17. Ready for Delta Load
LIS, CO/PA, and FI/SL are Customer Generated Generic Extractors, and LO is BW Content Extractors.
LIS is a cross application component LIS of SAP R/3 , which includes, Sales Information System, Purchasing Information System, Inventory Controlling....
Similarly CO/PA and FI/SL are used for specific Application Component of SAP R/3.
CO/PA collects all the OLTP data for calculating contribution margins (sales, cost of sales, overhead costs).
FI/SL collects all the OLTP data for financial accounting, special ledger
Difference: CO-PA / LIS / LO / FI-SL
1)Method for Delta: Time Stamp / LIS InfoStructure / Change Log / PseudoDelta
2) Application Specific: All are
3) Extractors: Customer Generated (CG) / SAP BW Content / CG / CG
4) Tables Used: Line item tables / 1 structure (s5nn). 2 tables (BWl1 and 2) and control change log (TMCBIW) / V3 update(asynchronous) and two tables: VBDATA and ARCFC (change log from SAP R-3 / Three types of tables - Line Item Tables- ZZP(plan) & ZZA(actual), - Total Table ZZT, - Objects Tables ZZO & ZZC
Pls refer:
http://help.sap.com/saphelp_nw04/helpdata/en/ee/cd143c5db89b00e10000000a114084/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sapportals.km.docs/documents/a1-8-4/how%20to%20set%20up%20connection%20co-pa%20-%20extraction
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sapportals.km.docs/documents/a1-8-4/how%20to%20set%20up%20connection%20co-pa%20-%20retraction
Differences between LIS,LO,CO/PA and FI-SL extractors
*Pls Assign points if info is useful*
Regards
CSM Reddy

Step by step procedure for copa extraction

hi experts,
            what are the steps involved in copa extraction, please give me step by step procedure for copa extraction.
Thanks,
Rk

Hi Rama Krishna
     COPA STEPS
     SERVER R/3 SERVER  CONTOLLING & PROBALITY ANALYSIS  ENTER COPA WITH T-CODE 9TRANSACTION CODE KEBO)  CREATE (OPERATING CONCERN ; IDEAS (CLICK ON EXCUTE)  ENTER (SHORT TEXT,MEDIUM TEXT,LONG TEXT)  FIELD NAME FROM PERITION ; BURKS  DESLECT SOME VALUE FIELDS  LICK ON CHECK BUTTON  CLICK ON SUMMATIATION LEVEL CLICK ON INFO CATALOG  IT GOES TO ATA SOURE [CUSTOMER VERSION EDIT.  SELECT IN SELECTION , HIDE FIELD  CLICK ON SVE BUTTON  NEXT CLICK ON GENERATE  GO BACK  TO CHECK THE DATA IN COPA DATA SOURCE  T- CODE RSA3 IMP  DATA SOURCE  1-CO PA800 STISH  CLICK ON EXTRACTION.
     SERVER BW SYSTEM  GO TO INFO SOURCE YSTEM  SELECT YOUR SOURCE SYSTEM  DOUBLE CLICK ON SOURCE SYSTEM  SELECT BW DATA SOURCE  SAP APPLICATION COMPONENTS  CONTROLLING  PROFITABILITY ANALYSIS  RIGHT CLICK  REPLICATE DATA SOURCES  ELECT COPA DATA SOURCE (R.C)  SELECT REPLICATE DATA SOURCE  DOUBLE CLICK ON DATA SOURES  APPLICATION PROPOSAL  1-CO-PA800 SATISH  CLICK ON TRANSFER BUTTON  YES  PROPOSE TRANSFER RULES  IF WARNING OCCURS SAY CONTINUE  ACTIVATE  GO BACK  CREATE INFO AREA  INFO PROVIDER  CREATE INFO CUBE  INFO SOURCE  1-CO PA8000SATISH  CREATE UPDATE RULES  GO BACK TO INFO SOURCES  REFERESH  FIND THE 1-CO-PA800  PC ON SOURCE SYSTEM AND CREATE INFO PACKAGE  SCHEDULER  MONITOR.
Regards
Ashwin

COPA datasource error - Errors occurred during the extraction

Hi,
I have an issue with the COPA datasource,
1. I have created a COPA datasource in DEV and its working fine in DEV. the entire extraction is working fine.
2. Then I transported this copa datasource to QA where I am getting belor error.
In Extract checker, when checking for the data, i am getting the error
"Errors occurred during the extraction"
Application Log:
@5C\QError@ Syntax error in generated program @35\QLong text exists@
Syntax error in generated program
Message no. RD117
Diagnosis
A syntax error has occurred in the generated program for the CO-PA extractor:
MSGV1: "RSFHGEN2"
MSGV2: "No component exists with the name "HILFS". ."
MSGV3: " 18"
MSGV4: ""
Regards,
Vijay

Hi,
Thanks for your answer, I have gone through this note and i know that there are inconsistencies b/w the extract structure and operating concern.
But I would like to know is,
1. why its working in DEV?
2. How to fix this error in QA?
3. Do I need to recreate the datasource and Operating concern with/without the fields which are giving the problem.
Regards,
Vijay

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 ?

COPA extraction is taking too much time

Hi,
We are extracting data from R/3 by using COPA data Source with Delta update. It is taking 3 -4 hrs time to extract around 3000 records.
In the Job log:
1 LUWs confirmed and 1 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DATA
Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 2,535 records
Between these two statements 3hrs is taking.
Can anyone help to solve this .
Thanks in Advance
Chetan.

Try a smaller set of data .. like one day if you can. Also look at what else is happening in the system (SM50/SM51/SM66). If you are running in the middle of the day while someone else is running a big job, that could severely slow down a small system.
Also, the COPA datasets are usually very wide and contain a lot of data. You could potentially be going out and gathering a few gig of data ... which will take awhile.
Also, look at transaction KEB2 and make sure there are no errors (you may have to scroll down very far to find an error). Also, simulate it with KEB5 and see how fast it goes through that transaction.
The key is to let it do it's work. If you see nothing happening and cancel the job or start a new one, you have corrupted the queue and need to let everything finish running .... then reinitialize. I did this once .... restarted, waited 10 minutes ... nothing .. cancelled job, restarted again .... etc...
It wasn't until I walked away for a day and came back on a Saturday to reinitialize that everything went smoothly and quick.
Brian

COPA Extraction Error

Similar Messages

Maybe you are looking for