Missing PCA document  in BW during delta extraction of 0EC_PCA_3

Hi experts,
We are using Oracle 10g Data base for our ECC6.0 R/3 system.During BW extraction some of the PCA line item records got missed which gets update in data base table GLPCA in R/3 after successful document creation.
We are in the process of analysis to find out the root cause of the issue as we are approaching year end close.
Please let me know how to get the following logs(Information) in R/3
1.Total time taken in Application server for a particular document which was Entered.
2.Total time taken for a document from posting(Document entry) to successful data base server update.
(OR Application server to Data base server update log details OR Document posting to DB write for a document)
Please treat this as a matter of urgency
Regards
Kumar

I thought payment run is only for AP and AR documents.Is Payment run applicable for PCA journal also?
true the AP and AR postings will come in the PRC4 load in 0EC_PC_1.
But the other side of the AP and the AR is bank which is posted directly to 0EC_PCA_3.
Go to the AP posting for the payment - then document overview and you will see the balance sheetposting for the bank
In th emenu accoutning documents somewhere is the link to the PCA document - you can check there
The sm13 errors naturalyl wont excist as they have been processed
This is goign to be a nightmare to try and prove - I gave up trying to do this when I lost some data once
Yes GLPCA is the line item table that 0EC_PCA_3 reads
0EC_PCA_1 in full mode reads GLPCT but 0EC_PCA_1 in delta mode - actually creates a proper RSA7 delta queue for GLPCA but summarises into a GLPCT structure(!!! yeah I know!)
My only requirement is GLPCT data - I currently run this every hour based on the delta queue and also I have a real time read for up to the second reads for importatn queries

Similar Messages

  • How to debug mapping function module during delta extraction?

    Hi experts,
    Somehow our delta is not working properly, and i would like to debug our mapping function module. How can i debug it during a delta extraction?
    Some info:
    Our source system is CRM and our extractor is extracting one order document (contracts in this case). I know that when we modify a contract, a bdoc is generated and then passed throught the mapping function then the extracted data to the delta queue. I just need to debug when the bdoc is being mapped to see what's wrong with the extracted data.
    Thanks in advance,
    Van

    Hi,
    Since you are using a Function Module for the Extraction. Edit the Function Module and give "BREAK-POINT" before the loop command. Check and activate the Function Module.
    Now Extract the datasource using RSA3. Now you can debug it. After checking remove the "BREAK-POINT" from the function module. Also Check and activate the same.
    Regards
    Jayaram M

  • Processing overdue error during delta extraction from datasource 0CO_OM_CCA

    Hi,
    I'm getting "Processing overdue error" in BW while extracting delta from datasource 0CO_OM_CCA_9. all other extraction jobs from R3 -> BW are successful. Even Delta init on this datasource is successful & problem is only with delta package.
    I appreciate if someone could provide information based on the following error details on this issue.
    here are the extraction steps we followed.
    Full load of fiscal years 2006 & 2007 Into transactional cube.
    load budget data into transactional cube.
    compression of the cube with "0 elimination"
    Delta Initialization with fiscal period selections 1/2008 to 12/9999
    all the above steps were successful.
    and when delta package is scheduled, we are getting following errors.
    BW system log
    BW Monitoring job is turning red with following message.
    Technical : Processing is overdue
    Processing Step : Call to BW
    Sending packages from OLTP to BW lead to errors
    Diagnosis
    No IDocs could be sent to the SAP BW using RFC.
    System response
    There are IDocs in the source system ALE outbox that did not arrive in
    the ALE inbox of the SAP BW.
    Further analysis:
    Check the TRFC log.
    You can get to this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
    Removing errors:
    If the TRFC is incorrect, check whether the source system is completely
    connected to the SAP BW. Check especially the authorizations of the
    background user in the source system.
    R3 Job Log
    Even after BW job turns to red, R3 job continues to run for 2 hours and
    eventually gets cancelled with an ABAP dump & here is the log.
    Job
    started
    Step 001 started (program SBIE0001, variant &0000000110473, user ID
    BWREMOTE) DATASOURCE = 0CO_OM_CCA_9
    Current Values for Selected Profile Parameters
    abap/heap_area_nondia.........2000000000 *
    abap/heap_area_total..........2000000000 *
    abap/heaplimit................20000000 *
    zcsa/installed_languages......EDJIM13 *
    zcsa/system_language..........E *
    ztta/max_memreq_MB...........2047 *
    ztta/roll_area................6500000 *
    ztta/roll_extension...........2000000000 *
    ABAP/4 processor: SYSTEM_CANCELED
    Job cancelled
    Thanks,
    Hari Immadi
    http://immadi.com
    SEM BW Analyst

    Hi Hari,
    We were recently having similar problems with the delta for CCA_9.  And activating index 4 on COEP resolved our issues.
    Yes, by default there is a 2 hour safety interval for the CCA_9 DataSource.  You could run this extractor hourly but at the time of extraction you will only be pulling postings through 2 hours prior to extraction time.  This can be changed for testing purposes but SAP strongly discourages changing this interval in a production environment.  SAP does provide an alternative described in OSS note 553561.  You may check out this note to see if it would work for your scenario.
    Regards,
    Todd

  • PCA doment missing during the delta extraction

    Hi R/3 DBA experts,
    We are using Oracle 10g Data base for our ECC6.0 R/3 system.During BW extraction some of the PCA line item records got missed which gets update in data base table GLPCA in R/3 after successful document creation.
    We are in the process of analysis to find out the root cause of the issue as we are approaching year end close.
    Please let me know how to get the following logs(Information) in R/3
    1.Total time taken in Application server for a particular document which was Entered.
    2.Total time taken for a document from posting(Document entry) to successful data base server update.
    (OR Application server to Data base server update log details OR Document posting to DB write for a document)
    Please treat this as a matter of urgency
    Regards
    Kumar

    Hi,
    To move the data from Update Tables to Delta Queue, u need to run the V3 Job Control in LBWE. Once if the job is successfully completed then all the data from Update tables are moved to Delta Queue. Check once in the job overview of V3 job control is there any errors.
    Hope this helps in solving u r problem
    Regards
    Ramakrishna Kamurthy

  • Load Missing documents w/o disturbing delta

    Hi Experts,
    We miss several documents for particular reason. This cube is being loaded with delta package. Now they want the missing documents into the Infocube.We are updating data from R/3 DS(Controlling)----->Cube.
    If I load missing documents with a new data package giving required selection in document number, will it disturb daily delta loading process for this cube. What is your advice.
    Thanks,
    Philaphi.

    Hi,
    If your data is missing, you may go for Repair full delta option available in infopackage. This would not disturb your deltas and bring in any missing data from R/3.
    As you have mentioned that your dataload is delta load, therefore, you would not be able to change the selection conditions for your extraction as the selection condition for your delta load will have to be same as that of your Init delta load.

  • 0FI_GL_10 can't delta :Errors occurred during the extraction.

    hi,sdn!
    i have 3 DataSources,
    0FI_AA_11(FI-AA: Transactions),
    0FI_AA_12(FI-AA: Posted Depreciations) and 0FI_GL_10(General Ledger: Leading Ledger Balances).
    The initialize and full extraction is ok.
    when i delta it in rsa3,the system tell me:Errors occurred during the extraction.
    Is Append Structure result in this error?
    i want to know the reason,thanks!

    For summarization of line items by master record characteristics (such as cost center) during posting of ODS objects to InfoCubes, master data must already exist prior to extraction of transaction data. The following sequence must therefore be kept to during extraction:
    0FI_GL_4               
    General Ledger: line items (if required)
    0ASSET_ATTR_TEXT          
    Asset subnumber (flexible updating)
    0ASSET_AFAB                        
    Depreciation area real or derived
    then the transaction data
    0FI_AA_11             
    FIAA : transactions and / or
    0FI_AA_12             
    Posted depreciations (period values)

  • "Errors occurred during the extraction" for delta Extraction

    Hi All,
    I have one data source which is getting extracted by using the FM.Initially this is only full load.But now I have enabled delta on this data source.
    While extracting the data from RSA3, with delta option, I am getting the error "Errors occurred during the extraction".
    But I have given Target System, replicated the data source in target system and reactivated it again.
    But again I am getting the error "Errors occurred during the extraction".
    Could you please help me on this.

    Hi
    I have done the Data Source Initialization.

  • Missing V2 records using Unserialized V3 deltas in Logistics

    We have been experiencing missing Deltas in our Material Movement transactions feeding BW. This always occurs between 5:30AM and 6:00AM. When we examine the intermediate queues we notice the Deltas are not present in the V2 queue. I have read several articles describing the process by which SAP moves Deltas through its arthitecture in order to get Deltas from ECC all the way to the Delta Queue in BW using the Unserialized V3 update method of extraction. All the articles state very clearly that if the V2 update fails, then the transactions are not going to make it through to the Delta queue - that makes sense.
    What none of the articles explain, and what doesn't make sense, is why the V2 updates would fail in the 1st place. So...that is my question - Under what circumstances would the system not complete a V2 update? As a result of messing around with this problem for a couple of weeks and not getting anywhere, we have abandoned the Unserialized V3 Delta process in favor of using the Direct Delta technique. The up side is we will be getting all the Deltas into BW. The down side is that we have not solved our problem - we've only circumvented it, and the next time we attempt to implement the Unserialized V3 update technique, we most likely will go through a similar period of frustration.
    I'm NOT looking for info on "where to look". I'm looking for "concepts" - whiy would a V2 udpate fail? If I know the answer to that question, then the answer to "where to look" should be obvious.
    Thanks in advance for someone's help.

    Hello,
    Here are some useful tips (in my opinion) to this problem:
    - Refer to transaction SM13 to view the 'V2' requests which aren't made into 'V3' Queue. Choose the status option 'V2 Executed', user as '*"  and select the appropriate time. This transaction would provide all the V2 requests which wern't updated. It's also possible to re-post the failed updates using the "Repeat update" option
    - Normally there will be a dump recorded to respective failed update and this can be check using the transaction ST22. If you analyze the problem then you might be able to find the root cause of this failure.
    We are using the 'Queued' delta method for application '03' and this method is working fine and never missed any documents. May be it's worth checking this update method.
    Hope the above tips will help you.
    Cheers
    Bala Koppuravuri

  • Problem while delta extraction

    Dear Experts,
    I am facing a poblem while delta extraction for AR ODS. When I check the status of delta extraction it shows green and records transferred as well but when i check into BW side I find some records missing. When I faced this problem for first time I did the init load again after which all records came into BW side but subsequently again when some changes were made in R/3 side and delta was uploaded, again the same records were found missing.
    If anyone has any idea why this is happening please guide me as to how to go about it. Also I have given no filter conditions in data selection.
    Thanks in advance. Will assign points happily for any kind of assistance.
    regards
    akshat

    Hi,
    the standard delta extraction is not sensitive to program in the R/3 side that write directly into tables. For my experience, this is the only reason when the delta does not work.
    So, check with the R/3 people, if they are input account document by write directly into BSIS or BSAS.
    Rgs
    Antonino

  • Problems with Delta Extraction for 0CRM_OPPT_H (no data found)

    Hi,
    I've some problems with the Delta Extraction of the Infosource 0crm_oppt_h (CRM Opportunities Header). After initialization I get no delta data from the CRM system.
    What I already did:
    Activated 0crm_oppt_h Data Source (checked functionality with rsa3)
    Started Info Package (Init) on BW side (worked fine)
    Checked the status of the Data Source on the CRM system using BWA7 ("initial upload" is unmarked; "delta active" is marked and what makes me worry is that the column "Queue exists" in <i>unmarked</i>...)
    If I change anything (like Phase, Expected Sales Vol.) in the opportunity, the Delta Extraction get no changes.
    Could You help me out, please?
    Best regards,
    Markus Svec

    hi Markus,
    try to check oss note 788172
    Release Status Released for Customer
    Released on 23.03.2005
    Priority Correction with high priority
    Category Program error
    Symptom
    No data exists in delta extraction from the CRM server to the BW system for business transactions, if parallel processing is applied as per note 639072. But Data is extracted if parallel processing is switched off.ie. when BWA_NUMBER_OFF_PROCESSES is set to 1,there is data during delta. This applies to the following DataSources:
    0BBP_TD_CONTR_1
    0CRM_COMPLAINTS_I
    0CRM_LEAD_ATTR
    0CRM_LEAD_H
    0CRM_LEAD_I
    0CRM_OPPT_ATTR
    0CRM_OPPT_H
    0CRM_OPP T_I
    0CRM_QUOTATION_I
    0CRM_QUOTA_ORDER_I
    0CRM_SALES_ACT_1
    0CRM_SALES_CONTR_I
    0CRM_SALES_ORDER_I
    0CRM_SRV_CODES
    0 CRM_SRV_CONFIRM_H
    0CRM_SRV_CONFIRM_I
    0CRM_SRV_CONTRACT_H
    0CRM_SRV_PROCESS_H
    0CRM_SRV_PROCESS_I
    Other terms
    DataSources, BWA, initial extraction, delta init, parallel processing, no data in delta.
    Reason and Prerequisites
    There is an update on the generated delta table which causes data corruption in running delta initializations as the changed delta sets will be deleted with every further update on documents. An open cursor statement is there without fetch data in SMOX3_GET_DATA.
    Solution
    The problem is solved with the attached corrections.After applying the corrections a new initialization of the affected datasources is necessary.

  • Errors occurred during the extraction, Message nos. RJ012

    Hi Gurus,
    I have created one generic data source using FM for CO-PA and it's in activate staus in rsa6. When I checked the data in RSA3, it's saying below message
    Errors occurred during the extraction
    Message no. RJ012
    Please help me to resolve this issue.
    Thanks & Regards,
    Saketh

    Hi Saketh,
    The cause of the error can be  some missing code that you didn't add to the function modul.
    You can check the document at the below link.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c062a3a8-f44c-2c10-ccb8-9b88fbdcb008?overridelayout=t…
    Thanks&Regards,
    Oya.

  • Errors occurred during the extraction - in Confirmations

    Hi All,
    When I do the extracton for delta in RSA3 for extractor 0BBP_TD_CONF_1, an error occured saying "Errors occurred during the extraction". when I go into details it didnot give much info except Message no. RJ012.
    I couldn't find any note on this specific to SRM source system.
    Anyone please let me know if you have faced the same issue or any solution. Thanks all.
    S

    Hello Raja,
    I can understand that's not related to your question.Your question has just given the message number and therefore its not possible to make out for anyone by just looking at the message number.
    I just wanted to let you know that if you follow the steps as mentioned in the document then chances of error are less and you can compare your code with the document.
    All the function modules are based on the same logic and use the same syntax and I am sure yours will be no different other then the tables which you have used.
    Did you tried to debug your data source in RSA3 in debug mode??
    You will get the exact issue where it is failing.Check the option debug and execute in RSA3
    Give the desired inputs and see the values of all the parameters which is getting filled and see after which code you are getting the error.
    Thanks
    Ajeet

  • Delta Extraction: Cross Application Table

    Hello Gurus,
    While enhancing an LO extractor, I understand that we need to create a structure with the fields needed for extraction and then append this to the main extract structure and populate this through the user exit. Now what I am worried about is if the fields happend to be a from a cross application table, how the delta would be taken care of?
    As an Example, if I need to add in couple of fields of the delivery tables (LIPS and LIKP) in the Purchasing extractor (2LIS_02_SCL), am I going to get changed fields during the delta extraction?
    Thanks...

    Is that always true? Please look through the following scenario that Sunmit mentioned in response to Roberto's one of the blogs:
    If a scenario demands a cross application enhancement
    eg: Enhancing shipment relevant field in a delivery data source/extractor or delivery relevant field in an invoice relevant data source.
    Is the delta relevance of these enhanced fields retained by enhancing the datasource at communication structure level? I guess, the delta of these enhanced fields would still be lost, since they are not included in the events that are used to create the delta.
    (ie a shipment document (our field) may change without change in delivery document).
    Any ideas???

  • Safety intervels in genric delta extraction.?

    can anyone expliain me with an example how to set safety intervel limit?how to set upper limit and lower  limit?

    Hello Shilpa !
    Guess this doc will clear ur issues:-
    Safety Interval Upper Limit of Delta Selection
    This field is used by DataSources that determine their delta generically using a repetitively-increasing field in the extract structure.
    The field contains the discrepancy between the current maximum when the delta or delta init extraction took place and the data that has actually been read.
    Leaving the value blank increases the risk that the system could not extract records arising during extraction.
    Example: A time stamp is used to determine the delta. The time stamp that was last read is 12:00:00. The next delta extraction begins at 12:40:00. In this case, the selection interval is 12:00:00 to 12:40:00. At the end of extraction, the pointer is set to 12:40:00.
    A record - for example, a document- is created at 12:40 but not saved until 12:40. It is not contained in the extracted data but, because of its time stamp, is not extracted the next time either.
    For this reason, the safety margin between read and transferred data must always be larger than the maximum length of time that it takes to create a record for this DataSource (with a time stamp delta), or it must display an interval that is sufficiently large (for determining delta using a serial number).
    Safety Interval Lower Limit
    This field contains the value taken from the highest value of the previous delta extraction to determine the lowest value of the time stamp for the next delta extraction.
    For example: A time stamp is used to determine a delta. The extracted data is master data: The system only transfers after-images that overwrite the status in the BW. Therefore, a record can be extracted into the BW for such data without any problems.
    Taking this into account, the current time stamp can always be used as the upper limit when extracting: The lower limit of the next extraction is not seamlessly joined to the upper limit of the last extraction. Instead, its value is the same as this upper limit minus a safety margin. This safety margin needs to be big enough to contain all values in the extraction which already had a time stamp when the last extraction was carried out but which were not read. Not surprisingly, records can be transferred twice. However, for the reasons above, this is unavoidable.
    these are used to determining the delta in a datasource:
    1. Time stamp - The field is a DEC15 field which always contains the time stamp of the last change to a record in the local time format.
    2. Calendar day - The field is a DATS8 field which always contains the day of the last change.
    3. Numerical pointer - The field contains another numerical pointer that appears with each new record .
    also download Generic Delta doc
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
    Regards
    Tom.

  • Business Partner Items (0FC_BP_ITEMS) delta extraction help

    Has anybody used 0FC_BP_ITEMS extractor? The documentation says that it supports delta, but it needs to be enabled.
    I did enable delta extraction in IMG as SAP help site suggested. However, the documentation also says that before running delta, I need to update/initialize it in tcode FPOP. I go to that tcode, but I can hardly understand what to do in that tcode and there is no help or documentation I can find on how to initialize that delta extraction for 0FC_BP_ITEMS in OLTP system.
    anybody came across any help document on FPOP tcode?
    Thanks

    Have you found a solution to the problems you were facing? is there any documentation you have regarding the BP Items extractor.

Maybe you are looking for