Vendor data (field name LIFNR) is not filled in extractor. Currently my CCA Actual and Plan cube are stored in the same cube, and the Actual data is for multiple years, and the amount of data has gotten very large. 0co_om_cca_4 cosr. Because of this, i am not able to extract records in to BW in systems limited time. However, I could not find a datasource for Plan (Budget) Data with Material Number. From the OBJNR of the totals record (places 7-16 of the object number) LSTAR. Technical name: 0CO_OM_CCA_1. Cost center costs in object currency are identified by the system in records with 0CURTYPE = 10 (company code currency). Application Component. About the 0CO_OM_ABC_2 Datasource . For example Finance data extractor 0FI_GL_10 is Whitelisted with S/4 HANA, this means the data source is fully supported and will work with out any restriction. RemoteCube Compatibility. ZZSEGMENT Segment. Datasource Type: Transaction Data Extractor. By default, all corporate memory DSOs provided by the SAP HANA-optimized BI Content have been created according to the DataStore object (advanced) template Corporate memory without compression. But i can able to see those 2 fields in Exstract Structure: ICCTRCSTA1. Configuration of the New General Ledger . 0co_om_cca_3 cosl, cokl. ELEHK is read from table TKA07 based on the KOKRS, VERSN and fiscal year from the extractor. Sicne EKPO is not a part of base tables & extract structure for 0CO_OM_CCA_9, you need to follow the above procedure. Click on the below-highlighted icon to change the perspective which in this case will be BW modeling. 2002. 0 I am trying to replicate the KSB1 report from R3 to BW. - 0CO_OM_CCA_9 - Cost Centers: Actual Costs Using Delta Extraction. RemoteCube-Capable Yes. SAP BI ExtractorsJanuary 21, 2022 9 minute read. 0 and the blue square button is gone now. * For more information about source system IDs, see SAP HANA-Optimized BI. The InfoCube is provided with information from InfoSources 0CO_OM_ABC_1 and 0CO_OM_ABC_7. Hello All, I am trying to extract Cost Center Actual data using 0CO_OM_CCA_9 datasource. V_COVP (Generated Table for View) Table in SAP. We added some fields of the COEP and COBK tables without writing code in the cmod to populate them. Create an InfoPackage for InfoSources 0CO_OM_CCA_9, 0CO_OM_OPA_6, 0CO_OM_WBS_6, 0CO_OM_NTW_2,0CO_OM_NWA_2 and 0CO_OM_NAE_2 to load the actual data. Type of DataSource. Source System for R/3 Entry*. ZZPRCTR Profit Center. Description: Cost centers: Statistical key figures. Edited by: Christian Korb on Mar 24, 2009 5:04 PM. This enables additional fields (not contained in the COSP and COSS totals tables) to be transferred to the BW. 0CO_OM_CCA_9: Cost Centers: Actual Costs Using Delta Extraction: CO - Cost Center Accounting: 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 0FI_GL_4: General Ledger: Line Items with Delta Extraction: FI - General Ledger Accounting: 0CO_OM_WBS_6: WBS Elements: Actual Costs Using Delta Extraction: CO. at our situation here we are facing a situation where we use the 0CO_OM_CCA_9 datasource. 0CO_OM_CCA_40 (Cost Centers: Actual Line Items (can produce delta figs)) Now my question is. Hi All, I've activated sap standard DSO 0CCA_O09 in dev, the datasource 0CO_OM_CCA_9 has also been activated in rsa5 and when i check the extractor in RSA3 it is working fine. We loaded again 2013 in full (Data consistency reason) but I found differences in data, this time was less data than the first upload. Cost Centers: Actual Costs Using Delta Extraction. Date and Time 23. CO-OM-CCA: Costs and Allocations - Fund Accounting - SAP. In respect to SAP Help the data have to be loaded in Full Mode every time. next delivered datasources: - 0CO_OM_OPA_6 - Orders: Actual Costs Using Delta Extraction. from the ERP we get from the 0CO_OM_CCA_2_D datasource. I have 3 questions. Secondary Cost Elements Datasources. 2010 13:05:44 Job started 00 516 S. The DataSource is used to extract the actual data for sales orders and sales order items that are linked to financial plans. use an Additive Delta Delta type Extractor : Delta records are directly selected from the R/3 tables using a timestamp mechanism (Timestamp table BWOM2_TIMEST). 0. This InfoSource contains the structure to provide actual line items for internal orders to the EDW Core Layer. · 0CO_OM_CCA_9 Cost Centers: Actual Costs with Delta Extraction. I want to extract only expense GL accounts related expense into BW. Following is the logic for populating the appended fields. 0GN_R3_SSY. 40 BI Content Add-On 7. On a good day, it takes 2+ hours to pull from ECC, much longer that any other extractor that we have. 0CO_OM_CCA_1: Cost Centers: Costs and AllocationsGoto table ROOSOURCE -> 0CO_OM_CCA_9 -> and find the extractor type. Hi Experts, I am trying to load data from R3 source system into BW for standard datasource Cost center Actuals (0CO_OM_CCA_9). 0co_pa_3 zcopa_c02. Add a Comment. Type of DataSource. Create an SAP RemoteCube for InfoSource 0CO_OM_CCA_9 in the customer system by using the proposed characteristics and key figures from InfoSource 0CO_OM_CCA_9. CO-OM OPA: Actual Line Items (0CO_OM_OPA_40) - /IMO/OPA_IS10. Configuration of the New General Ledger . In the OLTP system, DataSources are created so that delta datasets can be recorded. The logic used is like below. 1 Answer. The content was built around the Layered Scalable Architecture (LSA) approach. Have you use Datasource 0CO_OM_CCA_9 before? I have created an InfoPackage for this Datasource and perform the Initialization with Data Transfer for the first. A New Home in New Year for SAP Community: Exciting times ahead for the SAP Community!Sathiendiran Balu. No. 0co_om_cca_4 cosr. Dear All, In standard datasource 0CO_OM_CCA_9, extract structure ICCTRCSTA1. V_COVP is a standard Overhead Cost Controlling General View Structure in SAP CO application. This requires a special procedure when loading the data from the source systems into the Cube. g. By default, the key fields in the standard SAP delivered CCA DSO are: controlling area, CO Document Number, Line Item of CO Document, Currency Type, Key Figure Type, Value Type for Reporting and Fiscal. This requires a special procedure when loading the data from the source systems into the Cube. None. No. Now should i be creating a new include or can add the fileds I want form COBK in BWOM2_COBK_COEP include or CI_COBL. Use. Thanks. About the 0CO_OM_ABC_2 Datasource . 0B. I have to enhance the datasource 0C0_OM_CCA_9 with teh following fields . use an Additive Delta Delta type Extractor : Delta records are directly selected from the R/3 tables using a timestamp mechanism (Timestamp table BWOM2_TIMEST). unable to create view on COSP table for enpense related GL accounts. Unlike the InfoSource 0CO_OM_OPA_1, you can use 0CO_OM_OPA_6 to select delta datasets. For DS,0CO_OM_CCA_9, A delta load is already up and running in our BW 7. Available from OLTP Release. 0CO_OM_CCA_10 . for this I have used 0CO_OM_CCA_9 data source, from this i am getting 70% of fields which are there in KSB1. x to BI NW4s 7. 0CO_OM_CCA_9 not populating Quantity fields. Can someone please advice why and when it suppose to happproceed as follows when you create an InfoPackage: When you create the package, choose the tab page Data target. thanks, keith 0co_om_cca_9 0co_om_opa_6 0co_om_opa_7 0co_om_opa_8 0co_om_wbs_1 0co_om_wbs_6 0fi_gl_4 0fi_gl_6 special_ledger 2lis_02_scl 2lis_02_itm 2lis_13_vdhdr 2lis_13_vditm 2lis_13_vdkon 2lis_12_vchdr 2lis_12_vcitm 2lis_12_vcscl 2lis_11_vahdr 2lis_11_vaitm 2lis_11_vascl 2lis_03_bf 2lis_03_um 0co_pc_01 0co_pc_02 RSM, 340, 0CO_OM_CCA_9, 0EC_PCA_3, 0FI_AR_4, 0FI_GL_4, 0FI_GL_10, 0FI_GL_14, 3FI_GL_xx_TT, 3FI_GL_xx_TT, 1_CO_PA, RSC2_QOUT_CONFIRM_DATA, RSDBTIME , KBA , BC-BW , BW Service API , BC-BW-ODP , Operational Data Provisioning (ODP) and Delta Queue (ODQ) , Problem Delta loads for 0CO_OM_CCA_9 datasource. · 0CO_OM_OPA_6 Internal Orders: Actual Costs Using Delta Extraction. Below is the job log from ECC. I have replicated and done 'init without data transfer' for datasource 0co_om_cca_9, 3. We added some fields of the COEP and COBK tables without writing code in the cmod to populate them. BCT-CO delta DataSources: Technical background information. Unlike the 0CO_OM_WBS_1 InfoSource, you can use the 0CO_OM_WBS_6 InfoSource to select. Technical name: 0CO_OM_CCA_1. Unlike the InfoSource 0CO_OM_CCA_1, you can use 0CO_OM_CCA_9 to select delta datasets as well. Visit SAP Support Portal's SAP Notes and KBA Search. Datasource : 0CO_OM_CCA_1. next delivered datasources: - 0CO_OM_OPA_6 - Orders:. ZZPRCTR Profit Center. Description: Cost Centers: Commitment Line Items. Can we find the fields WOG001 to WOG016 from COSP table in any extractor. Check whether this isapplicable to your concrete business case. I migrated one flow from 3. - 0CO_OM_WBS_6 - WBS Elements: Actual Costs Using Delta Extraction. privacy statement, for purposes that may include site operation, analytics, enhanced user experience, or advertising. · 0CO_OM_CCA_9 Cost Centers: Actual Costs with Delta Extraction. 53 Views. Application Component. RemoteCube-fähig. 0co_om_opa_1 0co_om_opa_6 0co_om_opa_5 0co_om_opa_2 0co_om_opa_3 zcopa_c05. CO Extractor + FI Document Number. Environment Source System of BW system SAP R/3 SAP R/3 Enterprise. Unlike the InfoSource 0CO_OM_CCA_1, you can use 0CO_OM_CCA_9 to select delta datasets as well. On a good day, it takes 2+ hours to pull from ECC, much longer that any other extractor that we have. About the 0CO_OM_CCA_4 Datasource . In the OLTP system, DataSources are created so that delta datasets can be recorded. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Skip to Content. But when i checked the timestamp in BWOM2. 0CO_OM_CCA_9 is delta enabled and we would like to use that functionality. Technical Data. Available for all Plug-In releases. I have checked all the available notes, nothing helped me to improve the extraction performance on delta loads, I have checked R3 Table indexes all are exists as per the available notes. Keys for the 0CO_OM_CCA_9 is specified by SAP on the note 553561: 0CO_DOC_NO CO document number. In the screen shots below, we are trying to load the data in a standard CCA DSO – 0CCA_O09 which is loaded from the data source – 0CO_OM_CCA_9. 0CO_OM_CCA_9: Cost Centers: Actual Costs Using Delta Extraction CO - Cost Center Accounting: 6 : 0CO_OM_CCA_1: Cost centers: Costs and allocations CO - Cost Center Accounting: 7 : 2LIS_04_P_COMP: Component View from PP/PP-PI PP - Production Planning and Control: 8 : 2LIS_40_S278: Transfer BW: Non CumulativeStandard datasources like 0CO_OM_CCA_9,this datasource is delta capable. This DataSource contains information on the commitments that were posted to cost centers. kunnr , gkoar , Offsetting Account Type , 0CO_OM_CCA_9 , customer , vendor , KBA , BW-BCT-CO-OM , BW only - Overhead Cost Controlling , How To . I have implemented 0CO_OM_CCA_9 data flow with Delta, using ODS= 0CCA_O09. And it have a single transfer rule also. 0co_om_cca_4 cosr 0co_om_cca_5 cosb 0co_om_cca_6 coomco 0co_om_cca_7 bpja, bppe. Technical name: 0CO_OM_CCA_9. 0B. 0CO_OM_CCA_1. COSP is a standard Overhead Cost Controlling Transparent Table in SAP CO application, which stores CO Object: Cost Totals for External Postings data. I see in help it appears this extractor only selects currency type 10. BW SD MM FI 常用 数据源. Available from Plug-In Release. Available from OLTP Release. InfoSources. Can I please know the difference between the two data sources as even the Tables / Description used are the same under both the cases and even there is no delta among the two. Datasource for COOI Table. I have checked all the available notes, nothing helped me to improve the extraction performance on delta loads. Iam loading one of the standard ODS 0cca_o09 which is getting data from 0CO_OM_CCA_9 data source. I am enhancing around 9 fields in the data source: 0CO_OM_CCA_9. This one is a Timestamp Interval Datasource storing these timestamps in table BWOM2_TIMEST in the TS_LOW and TS_HIGH. How 0CO_OM_CCA_40 extracts data from COVP - SAP Q&A Relevancy Factor: 1. I need to enhance 0CO_OM_CCA_9. Nein. That is, it supplies the new state of the selected internal order line items from the OLTP. if my understanding is correct then how we can design the data. Is there a way to fill the new fields with no need to write a user exit, because they exist in the base table of the structure?Relevancy Factor: 260. X flow . when I use tcode rsa7 in r/3 to check the delta queue,there is always no records in '0co_om_cca_9',but the new data has. These DataSources select data from the line item table COEP. BW CO-OM: Timestamp Table for Delta Extraction. 21. DataSource 0CO_OM_CCA_9 is able to extract revenue postings. I have checked the Request Monitoring and can see that it says: "11:28:32 ( 2934447 From 2934447. ***** Field REFBTI have a requirement in which I need to model the CCA dataflow in BI. These DataSources select data from the. CO-OM-CCA: Costs and Allocations 0CCA_C11. The DataSource works in what is called the after-image process. ABAP Program name : SBIE0001. what is the Table name and Value type to look for budget data in ECC. BUKRS) and to fill this new field in the CMOD enhancement. You are able to identify such postings as follows: BELTP (debit type) '2' (revenues). 0COSTELMNT_ATTR is Not whitelisted, will work but with some restrictions. That is, it supplies the new state of the selected internal order line items from the OLTP. The function module ZZ0CO_OM_CCA_9 finally contains the actual logic that fills the LIFNR field when it is empty and the other fields in the extracted structure enable the search of LIFNR in table MSEG: data: begin of mov_cdc. My example requirement is the derivation of the partner objects in the transformation between DataSource 0CO_OM_CCA_9 and InfoSource 0CO_OM_CCA_9 where the partner is derived using function module CO001_BIW_PARTNER_DECODE in the old legacy BW 7. Function Module: EXIT_SAPLRSAP_001. About the 0CO_OM_CCA_4 Datasource . Click more to access the full version on SAP for Me (Login required). hi experts: I have a scenario where the next list of extractors are being used: 0FI_GL_6. These costs could have. For the 0CO_OM_CCA_1 no key can be defined. Today it took over 8 hours to pull from ECC. Value type: 20- plan. The InfoSource contains the actual costs and quantities of the WBS element. x DTP. I need to enhance the extractstructure of 0CO_OM_CCA_9 to add new fields from table COVP which it is the base table of this extractor. Case A (with delta process): If you use the delta process, you can load your actual data at any time. The extract structure ICCTRCSTA1 contain an appended structure BWOM2_REFBLG. Configuration of Activity Based Costing . Cost centers for elimination of internal business volume (BW) COST, COEJ, COEP. Rest 30% includes : EBELN(Purchase document number). During the extraction of data from the R/3 System into the BW System by using DataSources 0CO_OM_CCA_9, 0CO_OM_OPA_6, 0CO_OM_ABC_7, 0CO_OM_WBS_6, 0CO_OM_NAE_2 and 0CO_OM_NWA_2 performance problems occur in the Delta Init mode. Even Delta init on this datasource is successful & problem is only with delta package. 0CO_AREA Controlling area. 0CO_OM_CCA_40 (Cost Centers: Actual Line Items (can produce delta figs)) Now my question is. Can anyone please give me a pseudo code for the below logic . The system identifies the costs in object currency of a WBS element in records with 0CURTYPE = 00 (transaction currency), 10 (company code currency), or 20 (controlling area currency). The system identifies costs of a WBS element in object currency in records with 0CURTYPE = 00 (transaction currency), 10 (company code currency), or 20 (controlling area currency). 0CO_OM_ABC_1 is Not Whitelisted and DS not working – no alternative exists. 4) This also started a background job say BC_INST_JOB2 which finished in around 60secs and DS 0CO_OM_CCA_9 was assigned to infosource 0CO_OM_CCA_9 with new source system RAT2. Therefore, every FI document which creates also CO document (accounts used in this document are defined as cost elements) will be resulted in COEP update. Available from OLTP Release. Also get data for document type but not the document date and posting date. Technical Name of Target InfoObject. #. thanks, keith 0co_om_cca_9 0co_om_opa_6 0co_om_opa_7 0co_om_opa_8 0co_om_wbs_1 0co_om_wbs_6 0fi_gl_4 0fi_gl_6 special_ledger 2lis_02_scl 2lis_02_itm 2lis_13_vdhdr 2lis_13_vditm 2lis_13_vdkon 2lis_12_vchdr 2lis_12_vcitm 2lis_12_vcscl 2lis_11_vahdr 2lis_11_vaitm 2lis_11_vascl 2lis_03_bf. Technical name: 0CO_OM_CCA_9. Application Component. The 0CO_OM_CCA_8 (cost centers: prices) InfoCube provides the entries for the following characteristics, using data from the OLTP system: Valuation view (0VALUATION), Price indicator (0ACTPRIND) and Currency type (0CURTYPE). cx_sy_dynamic_osql_semantics. 2LIS_02_SCL EKKO, EKBE,T001, T001W, EKET, EKPA. Manojkumar0CO_OM_CCA_9: Cost Centers: Actual Costs Using Delta Extraction CO - Cost Center Accounting: 15. Typ der DataSource. You can also use this ODS object to extract current data to BW without the safety margin of 2 hours using the DataSource Cost Centers: Actual Costs - Line Items (Delta) (0CO_OM_CCA_9), as described in. Also check out the comments section to view/add related contributions, questions or screen shots, based on real life experience. Field *COEP-TIMESTMP is used as a reliable timestamp for selecting new CO-OM line-items. I have a requirement to change Quantity keyfigure mapping to new fileds for delta extractor 0CO_OM_CCA_9, this change is required to get all quantity data ( Note 438207), I have to change following mapping, SMBG = COEP-MBGBTR. 0CO_OM_OPA_7. August 21, 2023 at 10:50 am. 0GN_R3_SSY. COOMCO is used to read the data. datasources using FULL UPDATE method. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. 0CO_OM_CCA_9. The fiscal. Timestamp Interval Datasource 0CO_OM_CCA_9 - two BW target systems from ECC - SAP Q&A Relevancy Factor: 1. Thanks for your valuable. I have data sources for 0CO_OM_OPA_6. Dear All, I have create Datasource in R3 "ZBI_IS01" Tcode RSO2 using function module. 0CO_OM_CCA_9: Cost Centers: Actual Costs Using Delta Extraction: CO - Cost Center Accounting: 0CO_OM_WBS_7: WBS Elements: Commitment Line Items: CO - Overhead Projects: 0CO_OM_WBS_3: WBS elements: Overall plan: CO - Overhead Projects: Table Fields related to ICWBSCSTA1 TABLE FIELD Description;The 0CO_OM_CCA_8 (cost centers: prices) InfoCube provides the entries for the following characteristics, using data from the OLTP system: Valuation view (0VALUATION), Price indicator (0ACTPRIND) and Currency type (0CURTYPE). It would be useful to us if u can share the procedure since it is now critical for the business here. 12. Use. Technical name: 0CO_OM_CCA_10. 10. 7805 Views. txt) or read online for free. It says the VBELN is ambiguous. 2. 2002. In contrast to the DataSource WBS Elements: Costs, you can also select delta. And transported everything to PRD environment. To discuss above points I have used example of CCA load which failed, While rest of the running loads were failed lets say BPC data load and Planning loads, Z_0CO_OM_CCA_9_XXX process chain was running and adding the records. However when i am trying to extract the data some fields are missing from my PSA such as field REFBN 'Ref Document No'. V_COVP. Use. 0co_om_cca_4 zcca_c04. RSM, 340, 0CO_OM_CCA_9, 0EC_PCA_3, 0FI_AR_4, 0FI_GL_4, 0FI_GL_10, 0FI_GL_14, 3FI_GL_xx_TT, 3FI_GL_xx_TT, 1_CO_PA, RSC2_QOUT_CONFIRM_DATA, RSDBTIME , KBA , BC-BW , BW Service API , BC-BW-ODP , Operational Data Provisioning (ODP) and Delta Queue (ODQ) , Problem . 0CCA_C11 and 0COOM_C02 are the infocubes which gets directly loaded from both of the datasources mentioned. Best. Since ECC upgarde happened, We have to again initialize data. Transaction Data. The above standard extractor doesn't bring this field directly, but it is using this field doing some lookup in. I was wondering why the data source 0CO_OM_CCA_40 doesn't extracts all document number from COVP. Für alle PlugIn-Release verfügbar. I want to create an OLAP variable for 0CO_OM_CCA_9 infopackage to select all cost centers for one 0comp_code. Xiaofang Liu August 4, 2020 2 minute read FI-CO Delta Safety Interval Summary 0 4 4,319 Introduction Safety interval is mandatory to FI-CO extractors, the underlying reason is FI. 0co_om_cca_9 covp (coep& cobk), cosp, cost, coej, coep, t001. Cost Center Accounting CO-OM-CCA. · 0CO_OM_OPA_6 Internal Orders: Actual. Configuration of the New General Ledger . Application Component Cost Center Accounting (CO-OM-CCA) Available as of Release SAP enhancement package 3 for SAP ERP 6. either). No. Can i upload full upload 2011 ( to 2011001 2012016 ) & then initialize delta 2012001 to unwards. Recenly we introduced new company code. Run transaction SE11 in the R/3 system to create a view which is based on the table of COEP and COBK. 方便各位开发顾问查询. Transparent Table. 3) Later system asked me to manually select Activation of BC and I just said "Install>Install in background". Available from Plug-In Release. . . 0CO_OM_CCA9 is used for actual line items with delta capability. (CORRTYPE = X, if WRTTP = 8 or 9) CCTR_IBV. Most important BW Extractors for 0co Om Cca 9 Source Table. This enables additional fields (not contained in the COSP and COSS totals tables) to be transferred to the BW. 0co_om_cca_3 cosl, cokl. the other four data source show 0 record and running move than 20 hours ( still not finished). In a defined context, they are considered as a whole and serve a common purpose. "Dear All, The client wants FI document type in the 0CO_OM_CCA_9 extract structure. 2LIS_02_ITM EKKO, EKBE,T001, T001W, EKPO, TMCLVBW, T027C, ESSR, T147K, T147. Configuration of Activity Based Costing . Technical name: 0CO_OM_CCA_9. CO-OM-CCA Cost Center Accounting: 0CO_OM_CCA_9 Cost Centers: Actual Costs Line Items (Delta) CO-OM-OPA Overhead Orders: 0CO_OM_OPA_6 Orders: Actual Costs Line Items (Delta) Note Please note that other DataSources for attributes, texts, and hierarchies may be relevant for your implementation. I tried standard extractor to know base table i could find the logic. This info source contains information regarding costs (primary and secondary) and quantities posted to cost centers (actual, plan and commitments). 7 (R/3 Enterprise). Timestamp Interval Datasource 0CO_OM_CCA_9 - two BW target systems from ECC - SAP Q&A Relevancy Factor: 1. 0. Search for additional results. 0CO_OM_CCA_9, 0CO_OM_WBS_6, 0CO_OM_OPA_6, 0CO_OM_NWA_2, 0CO_OM_NAE_2, 0CO_OM_NTW_2, 0CO_OM_CCA_40, 0CO_OM_OPA_40. The updated data models include reporting on plan and budget data. i have a qucik question. Cost Center Accounting CO-OM-CCA. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. g: 0CO_OM_CCA_1, 0CO_OM_CCA_2, 0CO_OM_CCA_5, 0CO_OM_CCA_9 and so on. This will create customized enhancement structure so it is not standard modification. Source System for R/3 Entry*. anyone met same problem as I. 2. This requires a special procedure when loading the data from the source systems into the Cube. 0CO_OM_CCA_9 is a datasource which i am using in my sap bi implementation project. Mapping the Debit/Credit Indicator (0DB_CR_IND) Mapping the Version and Transfer Price Valuation . CO delta DataSources a) Actual line item - possibly already partly archived 0CO_OM_CCA_9, 0CO_OM_WBS_6, 0CO_OM_OPA_6, 0CO_OM_ABC_7, 0CO_OM_NWA_2, 0CO_OM_NAE_2, 0CO_OM_NTW_2. CALL FUNCTION 'ZZ0CO_OM_CCA_9' TABLES. About the 0CO_OM_ABC_2 Datasource . This requires a special procedure when loading the data from the source systems into the Cube. 0CO_OM_CCA_9 is giving data to both of these cubes. Description: Cost Centers: Actual Costs Using Delta Extraction. 0CO_OM_CCA_1 Cost Centers: Costs. 0CO_OM_CCA_9 Cost Centers: Actual Costs Using Delta Extraction CO - Cost Center Accounting: 14 : 2LIS_12_VCITM Delivery Item Data SD - Sales and Distribution: 15 : 0COMP_CODE_TEXT Company code: FI - Financial Accounting: 16 : 0CUSTOMER_ATTR Customer Number Logistics - Logistics - General: 17 :0CO_OM_CCA_9: Cost Centers: Actual Costs Using Delta Extraction: CO - Cost Center Accounting: 2LIS_04_P_COMP: Component View from PP/PP-PI: PP - Production Planning and Control: 2LIS_04_P_MATNR: Material View from PP/PP-PI: PP - Production Planning and Control: 0CO_OM_NWA_2: Delta extraction: Netw. Technical Data. Hope this helps. Configuration of Accounts Payable and Accounts Receivable . This is a preview of a SAP Knowledge Base Article. Hello, I have activated the datasource 0CO_OM_CCA_9 which extract Actual Data. Datasource Type: Transaction Data Extractor. RemoteCube Compatibility. 2LIS_01_S001 is deprecated. 4. In your case it is a function module extractor using BWOMD_GET_CTRCSTA1. 4. Select only the InfoCube that you want to be filled by the InfoSource. Click to access the full version on SAP for Me (Login required). BWOM2_TIMEST. Description: Cost centers: Costs and allocations. Technical Name of Target InfoObject. 0CO_OM_CCA_9 Delta load issue. for this I have used 0CO_OM_CCA_9 data source, from this i am getting 70% of fields which are there in KSB1. Application Component. Rest 30% includes : EBELN(Purchase document number). The initial screen will look like below. if the. Create an InfoPackage for InfoSource 0CO_OM_CCA_9 to load the actual data. The system identifies the costs of a cost center in object currency with 0CURTYPE = 10 (company code currency). Then you can assign value in your extractor and read it somewhere else. And I would like to know on which fields, it triggers delta. Available from Plug-In Release. pdf), Text File (. The first step is to add a BW project which is nothing but connecting to your BW/4HANA system. without data transfer and then repair full load , but every time we run the delta , it is keep on runing and always showing 0 from 0 records . At 00:21:57 it showed 3 LUWs confirmed and then didn't do anything again until 08:46:12. 3) Create a User Exit for your Datasource. Line Items (Delta) (0CO_OM_CCA_9). · 0CO_OM_WBS_1 WBS Elements: Costs.