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

Similar Messages

Invalid data status error during the data extraction

Hi,
while extracting capacity data from the SNP Capacity view to BW. i get the "invalid data status error" and the data extraction fails.
when debugged the bad requests of the ODS object, i found that for a certain product(which has both positive and negative input and out qtys) co-product manufacturing orders were created. but this product was not marked as the co-product and functionally its fine.
how can i rectify the data extraction problem..can you advice.
Thanks,
Dhanush

Sir,
In my company for some production order status some are having "errors in cost calculation" ie "cser" .how to deal these kind of errors.

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???

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

Problem of Missing parts during the Process Order release

Hi
For a Make to Order strategy, I have run MRP for a sales order which resulted in planned order for the material. But when I try to convert the Planned Order to Process Order, I am getting error Parts are missing during the availabilty check even though the components are available in the stock.
But when I create a Process Order manually, I am not facing the problem of missing parts as stock for components are available in stock.
Please advice why I am facing the problem with Planned Orders which are created via MRP.
Regards
Brijesh

Dear all,
If we set the Individual requirement (1) in MRP4 view of the material master for the component, the system will not consider the plant stock and it will give the message like Parts are missing during the Process Order process even though the plant stock is exists for the component.
So I would like to where in customization you define this?
--> To not consider the plant stock if individual req is set (1)
--> To consider the plant stock if collective req is set (2)
Kindly advice,
Regards,
Brijesh

Delta extraction is not possible at the moment

Hello,
I am trying to run a delta load and am getting the message "Delta extraction is not possible at the moment". This is actually a repeat because i have tried this load multiple times with no success.
The Diagnosis in the error message is:
The delta extraction is not possible at the moment because the status list of the request is locked in the Cube. This can be for a number of reasons:
1. Another extraction is taking place in the target BI.
2. The control parameters of the request in the InfoCube are locked by deletion or compressing processes.
I dont see that any other extraction or a deletion or compression job. I've tried going through each failed job in the monitor and red lighting them but that hasnt helped. Any ideas what to check or how to fix the problem?
Regards,
TMS

Hi,
From what you are describing, there is already some process going on on the infoprovider you are trying to load the data to. Check if a data load is still active/activation is happening, if its a cube then are there aggregates and are they rolling up. You can check the process in SM66 or SM50 and the jobs in SM37.
The process has locked the infoprovider and no delta or for that matter any process can be done until the earlier one finishes. You can take help from the BASIS team to find out what is locking your infoprovider.
Cheers,
Kedar

* Delta Extraction for 0ASSET_ATTR_TEXT

Hi All,
Can someone help me for the delta extraction for 0ASSET_ATTR_TEXT datasource.
Steps performed as per SAP Help
1. Activated the BADI
2. Ran the initialization without datatransfer infopackage.
3. Created new records in R/3 side
4. I can see the newly created records in the Table : BWFIAA_AEDAT_AS
5. Ran the delta infopackage ( no records are getting updated)
When i check in RSA3 with the delta update, its giving an error.
Please guide me if i am missing any steps
Regards
Ram

Hi Ram,
Check this note,
Note 816560 - DeltaInit w/o data transfer does not createe time stamp
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=816560
Hope this helps....

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.

Delta extraction for FI (AR & AP) data sources

I tried extracting the data from 2 standard SAP data sources under FI module for Accounts Receivable.
0FI_AR_10(Customer payment history via delta extraction)
0FI_AR_5 (customer payment history)
The data to be extracted into 0FIAR_C05(payment history) info cube.I assigned the 2 data sources to an info source and pumped the data into the cube via an ODS.Now the problem is with delta extraction.No records are picked in the delta extraction.So I checked in extractor checker RSA3 with delta update mode.I got the following error.
"Could not determine BW release of logical system"
Could some one resolve the issue?Thanks in advance.
Thanks & Regards
Vinay

Hi ,
Please go through 493422 note once . see if suits to your requirement follow it accordingly .
Thanks ,
Anil

Regarding R/3 down time during the INIT Run

Hi All,
Please let me know the methods to reduce to R/3 Down time during the INIT Run.
What happends if the tables( Setup / Update) are not locked in R/3 during the INIT Run.
Your help would be appreciated.
Thanks,
Vijay

Hi,
To conclude..
In Direct delta:
note that no documents can be posted during delta initialization procedure from the start of the recompilation run in R/3 (setup tables filling job) until all records have been successfully updated in BW: every document posted in the meantime is irrecoverably lost.
In Queued delta:
The document postings (relevant for the involved application) can be opened again as soon as the execution of the recompilation run (or runs, if several and running in parallel) ends, that is when setup tables are filled, and a delta init request is posted in BW, because the system is able to collect new document data during the delta init uploading too (with a deeply felt recommendation: remember to avoid update collective run before all delta init requests have been successfully updated in your BW!).
dont forget that, regardless of the update method selected, its ALWAYS necessary to stop any document postings (for the relevant application) during setup tables recompilation run !
Hope its clear.
reward if helpful.
shylaja.

How to see deleted records in delta extraction from view

Hi folks,
i am currently reflecting about delta extraction from a view:
The view contains a date field (change date) which is used to identify new or changed records.
So the delta extraction of new and changed records works without problems.
But what is happening with records that are deleted in the source system?
My current understanding is that deleted records will not be shown in the view. Therefore the deletion is not visible in the extraction.
- Is there a workaround for this problem?
- How is deletion of records normaly handled in generic extractors?
- Is it impossible to extract a deletion when using views?
any suggestions and help will be appretiated...
bye

Hello Florian,
Generally records will not be deleted (until if you physically delete it from table) but will have a status deleted.
So it doesn't matter whether you use view or tables the deleted records will be extracted through the view to update the BW data targets.
Thanks
Chandran

Delta extraction understanding

Hi All, Can anyone tell me whatz the difference between the generic delta in a Generic datasource and the delta in the Lo Cockpit.
Thanks,
Simmi

Hi simmi,
Well, you can also load the generic delta to Cube also provided you only need new records created and is not intrested in records that have changed during the delta period.
If you need real delta, or the set of new as well as changed records during the delta period then you will have to use the ODS using (AIE) (New status for changed records) method.
The architechture of ODS is so helpful that when you activate the data in ODS, it will automatically create the before/after images for us and fill it in the ChangeLog table. From there it can be transfered to the required datatargets using update rules.
But as everybody will warn you, when you delete records generic delta is rather helpless and you may have to write your own logic using Function modules to accomodate that.
Hope this clears your doubt.
regs
Anoop C M

Error in Delta extraction of Material using MDM_CLNT_EXTR

Hi All ,
I am facing the following error while doing the delta extraction for material by using MDM_CLNT_EXTR.
ABAP/4 processor: MESSAGE_TYPE_UNKNOWN
I used MATERIAL_EXTRACT stucture, and successfully run the intial load.
Any help will be appriciated
BR
Syam

Hi Syam,
Just check whether the target system defined in XI and the extraction object that you are selecting are in sync.
Such error is possible when there is a conflict in the same.
You can also refer to the below link.
Delta Extraction Using MDM_CLNT_EXTR (Urgent)
Hope it helps.
Thanks,
Minaz
Edited by: Minaz Kathawala on Sep 30, 2008 4:14 PM

Delta Extraction Hung

Hello All ,
Please help in coming to a conclusion .
The Delta Extraction JOb ( SM37 ) for a load is hung for a long time ( pulls 0 by 0 ) . The job log in R/3 doesnt progress ahead of the step --
"Asynchronous sending of InfoIDOCs 2 in task 0001 (0 parallel tasks) ".
When I looked in SM66 for the Process ID - Its is just hung at " UPDATE roosprmsc " step .
Has any one ever come across the scenario . The datasource used for extraction is a generic datasource which has been running fine for a long time now.
Thnx

Hi,
There is some problem with the R/3 source system.
Contact yr R/3 counterpart and check if they also have the same issue with other jobs in R/3.
Try to pull delta for some other ODS from the source system ad check if it works fine.
If not contact your Basis guy.
Also check if Full load is working..
Regards,
Balaji V

Delta Extraction - Generic Datasource

Hello Guys,
I have an issue related with the delta extraction for a generic DS. I have a DS setup with
a generic delta for a calendar day and safety interval upper limit 1. So i think that for some reason no all values are loaded in the
delta load. Please help me to find the best approuch for this.
Regards,
Iván.

Hi,
Hope below links are helpful for you to find the best approuch
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33?quicklink=index&overridelayout=true
Generic delta safty intervals
Regards,
Vinay

PCA doment missing during the delta extraction

Similar Messages

Maybe you are looking for