on 06-14-2005 1:21 PM
Hi all,
I am loading data for 0material(texts) from R/3 and we do a delta update everyday. I got this error message today, was wondering if anyone knows why I got this?
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.
Please let me know.
thanks
Sabrina.
Hi Sabrina,
as usual, you have to look to R/3 to check if there is some dump !
(anyway, perform a full update if you need urgently these texts!)
Bye,
ROberto
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hallo Sabrina
If you do a full load, you have everything but if you want to get tomorrow the change or new record you need to do again a full load. if you reinitialize then you can go forward with the delta.
http://help.sap.com/saphelp_nw04/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
Mike
Just some little consideration...
if you don't have an huge master data (but I cannot give you an exact number from which you can consider a master data as huge because it depends from many factors, all performance-relevant), it's better to use FULL method, in order to avoid any error related to delta management (that is 'more problematic')...in other words, use delta management (init+subsequent deltas) only if necessary because a full extract too many records each time !
Hope it helps!
Bye,
Roberto
Hi all,
The problem is -- we have daily master data loads and few of them have wild cards in extraction (thats what I was told) and when they have upgraded the system to plugin 2002_2_46c patch level 5 they have started facing problems. They have tried OSS Note 721538 and still they have the same problem. I am actually trying to investigate into this and fix this.
Please let me know if anyone has encounted this? Any ideas on how to proceed on this?
Let me know if i have to post this as a new question?
sabrina.
Hi Roberto,
I don't know exactly what they did and where they have use those wild cards and why? How they extracted the master data (I know they extracted from R/3), can you please guide me how I can start exploring all this. Any material in this respect?
I greatly appreciate your help.
thanks,
Sabrina.
Hi Roberto,
The symptom sections contains this
You had entered selections with wildcards ('+' or '*') in the extractor check tool. However, the selections were not passed correctly to the extractor. Instead of 'CP', the OPTION field of the I_T_SELECT selection
table contained the value 'EQ'.
Can you tell me where can this wildcard be entered in the selection of data. Is it in infopackage? Extractor check tool is only to test the extraction of data?
Please let me know.
Sabrina.
Hi Sabrina,
What is happening is that the selection that you are making using the wild cards is not being accepted by the extractor as it is looking for a selection equal to a particular value...as the message mentions the field has EQ (equal) and we want CP (Contains Pattern) in order to use the wildcard. The same problem will occur if you put a * selection in the InfoPackage.
I think you would need to make a change against the field for which you putting in this selection, in the ROOSFIELD table, field SELOPTS.
Hope this helps...
Sabrina,
let's try to start from the beginning (and, if you prefer, open a new thread) and explain to us where exactly you are facing the problem !
Bye,
Roberto
Ah, now I'm reading your new post...
Try to reproduce the same selection by entering several rows or some range (give us a list of these selections)
Instead of 90800*
PUT 908000000 - 908009999
Message was edited by: Roberto Negro
Hi Roberto and Bhanu,
OK, now I have enough information to discuss this with you.
The wildcard selections are not working after we upgraded the plugin to 2003_1_620. I entered the same selection criteria in extract checker and it is not working there too. The from value in the infopackage for field x has *_tel. We applied note 721538 but still facing the same problem.
This datasource is created on top of a infoset, so can we filter at the infoset level itself intead of doing it at the infopackage level.
thanks,
Sabrina.
Hi Sabrina,
Hope you have solved the wildcard Problem.I too face the same problem while selecting material using the string TR*.If you have solved the problem, Please help me and explain me , how you have solved it
I gone through sap help and could make out that certain datasources dont support wildcard.If so How can I create a datasource which support wildcard.
I created two datasources from an infoset and Table view.The infoset datasource supports wildcard, but the table view datasource is not supporting wildcard. Can anyone found a solution on this?
regards
Happy Tony
Hallo
I suppose there was no cmmunication between R/3 and BW at the time when you start your loading. Unfortunately you cannot do the delta repetition with the Masterdta as it is not supported. You have to reinitialize.
Please also chec in R/3 if you see nay error a the time of loading.
Mike
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.