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

Similar Messages

Error in delta extraction with SAP DataSource 2LIS_11_VAHDR ...

Hi all
I used the old data load process(3.5) in 2004s system.
There are errors in detla extraction with SAP data source
2LIS_11_VAHDR
2LIS_11_VAITM
2LIS_12_VCHDR
2LIS_12_VCITM
The delta data(before/after image) aren't right.
Has anyone experices with this problem?
thanks in advance

No Problems yet,explain the error message with error number in details here for some one to help you.
Hope it Helps
Chetan
@CP..

[urgent ]runtime error occured while creating the material using mm01

hai
am configure the ale program now . the problem is occured during the creating the material using mm01.
am using client 000 (sending system). and i want to send the material to the client 400(receiving system)
while am save the created material using t-code mm01 in client 000 . it depicts the error as
syntax error in program SAPLC140.
plz resolve this problem.
regards
surender

Hi,
In MM01 transaction code u have a problem..normally u will go to mm01 screen to create the material..i thought the same error will occur...so call basis to rectify this problem..
Thank u,
Manjula Devi.D

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

Error In Delta Extraction on 0HR_PT_1

Hi,
The status for delta load for 0HR_PT_1 stays yellow, and the application log in R/3 shows warning messages as
Personnel number 00001503 could not be locked.
It would be great if anyone could help.
Thanks

Sai,
I don't 0HR_PT_1 but I think there is a lock in sm12 for the personnel number because there is an user that modify the personnel number.
alessandro

Error while creating a material using Bapi_material_savedata

Hi,
there is an error encountered while creating a material using BAPI_MATERIAL_SAVEDATA..
The Error description is " Material description is not transfered " even after supplying the Material description and other mandatory field information like industrial sector, material type ,basic view indicator,Base UOM,Base UOM ISO code.
Please let me know the solution, if you know.

Hi,
Please search the SCN for the answers
https://www.sdn.sap.com/irj/scn/advancedsearch?query=errorinBAPI_MATERIAL_SAVEDATA+&cat=sdn_all

Delta extraction for dunning history is not active

Hi all,
I am loading data to the FI Cube (Financial A/c -> Contract a/c receivables ) Dunning header .
This is a Standard infocube. This cube contains two DSOu2019S 0FC_DS08 , 0FC_DS11. When I starting the data loading from the DSO ( 0FC_DS08 ), I create the INIT package . When creating itself it throwing the error u201C Delta extraction for dunning history is not active u201D
When I check on SDN SAP , ( Use Tcode sbiw. Select 'Settings for apllication-specific datasources (PI) ->Contract Aacounts Receivable -> Make Central Settings'. Then tick 'Delta Extraction for Dunning Items Active'.) I got this link. But I could not proceed this link. Can you explain detailed step by step how to proceed to solve this issue.
Regards,
Baskaran.

Hello Baskaran,
Did you ever solve this issue?
We do not have the link in SBIW (ERP 6.0 EHP6).
Thanks,
Andreas

Only Delta load from R3 to MDM using MDM_CLNT_EXTR

Hi ,
I need to set up *only delta load * extraction from R3 to MDM using MDM_CLNT_EXTR. I dont want to put Intial load.
Can anyone help me in sorting out this.
BR
Syam

Hi Syam,
The extraction of delta data can be very well done by selecting the distribution mode as D in the transaction MDM_CLNT_EXTR.
But prior to that u need to take initial loads so as to differentiate the changes.
For more information you can refer to the below links.
https://websmp103.sap-ag.de/installmdm
Re: MDM-XI-ERP (customer master data)
https://websmp201.sap-ag.de/~sapidb/011000358700001119492007E
Hope it helps.
Thanks,
Minaz

Change pointers in CRM for Product Data Extraction using MDM_CLNT_EXTR

Hi All,
We want to extract Product data in Delta mode using MDM_CLNT_EXTR.
I think change pointers are activated in CRM system in a different way. Please let me know steps to activate change pointers in CRM system for Product Data.
Thanks in advance for your help.
Regards,
Shiv

Hi,
   Please follow the below steps fro change pointers.
1.      In the Implementation Guide (IMG, transaction SALE), choose Modeling and Implementing ® Master Data Distribution ®Replication of Modified Data ® Activate Change Pointers ‑ Generally.
2.      Set the activation status Activate Change Pointers ‑ Generally, and save your entry (i.e BD61 Activate Change Pointers ).
3.      Choose the activity Activate Change Pointers for Message Types like ORDERS.
4.      Set the active indicator for the message type .
5.      Save your entries.
warm regards
Mahesh.

Error while doing DELTA Extraction

Hi BW Experts,
In my R/3, I have a generic data source ZBUT_VW.
It receives data from a View which is created based on couple tables.
When I do full load to the corresponding ODS, it is successful.
But after that I delete the ODS and created CUBE with DELTA
I have Initialized delta.
When I do DELTA extraction, it fails.
The error
The ALE inbox of the SAP BW is identical to the ALE outbox of the source system
and/or
the maximum wait time for this request has not yet run out
and/or
the batch job in the source system has not yet ended.
I delete the initialization load and trying to do DELTA extraction again and it Fails With the same error
Please let me know how can I resolve this problem.
URGENT
gaurav

I dont think it is possible to have to additive delta with creation date.
Try a full load to cube to check if the extractor is working.

Error while doing DELTA Extraction (generic data source)

Hi BW Experts,
In my R/3, I have a generic data source ZBUT_VW.
It receives data from a View which is created based on couple tables.
When I do full load to the corresponding ODS, it is successful.
But after that I delete the ODS and created CUBE with DELTA
I have Initialized delta.
When I do DELTA extraction, it fails.
The error The ALE inbox of the SAP BW is identical to the ALE outbox of the source system
and/or
the maximum wait time for this request has not yet run out
and/or
the batch job in the source system has not yet ended.
I delete the initialization load and trying to do DELTA extraction again and it Fails.
With the same error
Please let me know how can I resolve this problem.
URGENT
gaurav

I dont think it is possible to have to additive delta with creation date.
Try a full load to cube to check if the extractor is working.

Code For Delta Extraction Using Function Module

Dear Experts,
I want a sample code for Delta Extraction using Function Module ( If it is customized already working code very helpful ), I have already created Function Module but Full update is happening. If I give delta update again it is retrieving all records. It is very urgent, if you have please send me to the following mail ID.
[email protected]
Best Regards,
SGK.

Dear KJ,
Thank for your response. I saw the code that you sent, you have used some ztables like ZSC_DELTA_IP, ZSC_SAFETY_DELTA, ZSC_SET_EXT_TIME
What are the fields that you have created in these tables , what is use of these tables, can you send the fields that you have used in these tables.
Thanks & Regards,
SGK

What are the delta mechanisms and tables used for Lo Extraction & COPA

Hi all
what are the delta mechanisms and tables used for Lo Extraction & COPA.
please explain clealry.
Thanks & Regards,
James

James,
Please go through Roberto's weblog :
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
Anyways,
As you know LO cockpit consists of different modules(MM, PP, SD, etc)
They are called appl components. Each of them have a number (eg.MM=02) and for each appl comp they might be different Data sources and for each DS they might be different tables. So, unless you be specific we cant tell a specific table for a DS.
coming to the delta mechanisms, there are " direct delta, queqed delta and serialized delta".
Copa is based on the oepration concern. it can be created on " accouting based" or "costing based".
Assign points if helpful
Kalyan

When am creating the material using the transaction MM01 getting the error

Hi all,
Could you please help me to solve this issue, When I am creating the material using the transaction MM01, am receiving the error message "Express document "Update was terminated" received from author "XXXXXXXX", I checked the in SM13 found error message showing in Z_LGPLA_BIN_POSTING.
Regards,
Muralikrsihna.

ST22 Error is : SAPSQL_ARRAY_INSERT_DUPREC, below is full error message
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"Z_LGPLA_BIN_POSTING" "(FUNCTION)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
If you use an ABAP/4 Open SQL array insert to insert a record in
the database and that record already exists with the same key,
this results in a termination.
(With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
Regards,
Muralikrishna

Use of Update Table in Delta Extraction ....

Hi all ,
I have a small doubt regarding why there is an update table introduced between statistical table and delta queue in delta extraction process ... why not directly extract data from the statastical table and put it in to the delta queue .....
Kindly help me regarding this ...
Regards ,
Santosh ....

Hi Santosh,
I think it is related to resource, batch and memory, problem. Infact you can use only delta queue if you select direct update, but you use this kind of update only for huge amount of data produced in a short period of time.
The two queue let you divide transaction moment to batch collection moment.
Hope this help.
Ciao.
Riccardo.

Error in Delta extraction of Material using MDM_CLNT_EXTR

Similar Messages

Maybe you are looking for