Extraction program error
Hi,
While loading data from ECC, the BIREQU* jobs can not be released in some cases and remains as "scheduled". This reflection to BW is an error like: "Error 8 when starting the extraction program".
When we check the logs in SM21, we see the following details about these extraction jobs:
Job BIREQU_4DIIPJ8DQ8ILBDJRBUKBOH180/00155600 is locked by user <unknown>
Job /00 is locked by user <unknown>
After repeating the data load, everything works fine and it finishes successfully.
Has anyone experienced a similar case? Any ideas about the cause of this error?
Regards,
Erdem
Hi Erdem,
This is like;
Traveling on the 2 boats at once.
Let me explain you in detail:
If you have started a load from a Datasource 1 and then in parallel another person is trying to load data from the same datasource1. then it throws this type of error.
If you are running throw a process chain, check before whether any other process chain is running from the same data source.
the solution is nothing but change the process chain start variant schedule timings.
Hope this helps.
With Regards,
Ravi Kanth
Similar Messages
-
Incorrect call-up of the extraction program---error while extraction
Hi All,
We are loading the data first time(Full update) in BW Production we are getting the below error.
Error message is as follows:
Incorrect call-up of the extraction program R3 8
Errors in source system RSM 340
Details of error are as follows:
Requests (messages): Everything OK
Extraction (messages): Errors occurred
Error occurred in the data selection
We request you help for correcting this error.
Regards
DevaHi ,
Here is little more info about error details we see in Status tab of monitor.
Error message from the source system
Diagnosis
An error occurred in the source system.
System Response
Caller 09 contains an error message.
Further analysis:
The error occurred in Service API .
Refer to the error message.
Procedure
How you remove the error depends on the error message.
Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the
regards
Dev -
Error 8 when starting the extraction program
HI all
I have the following problem when i start an extraction. "Error 8 when starting the extraction program" I test the Extraction program on the R/3 system(source system) and it works, It displays records. On the target system in the infpk under step-by-step it gives you the error and It does not give a oss number, it only suggest that you need to look for a OSS. We have BW 3.5 installed with ECC 5.0.
Also on the source system Tcode WE02, for the load period id displays the IDOC with a red light with the same error. It displays the partnet, basic type and the port, the Error is marked next to inbound(inbox).
Regards
alexAlex,
Check the following OSS notes
947690
511475
23538
Even though the note 947690 is for process chain the steps mentioned in this note could cause Error 8 when scheduling a package for extraction. I think in your case the server name or the host name is incorrect. Check the host and the server name in TCODE SM51 and ask basis to look for the same in RFC entries using SM59 as well.
Abdul -
'Error 8 occurred when starting the data extraction program'
Hello Experts,
I am trying to pull master data (Full upload) for a attribute. I am getting an error on BW side i.e. 'The error occurred in Service API .'
So I checked in Source system and found that the an IDOC processing failure has occurred. The failure shows 'Error 8 occurred when starting the data extraction program'.
But when I check the extractor through RSA3, it looks fine.
Can someone inform what might be the reason of the failure for IDOC processing and how can this be avoided in future. Because the same problem kept occurring later as well.
Thanks
Regards,
KPHi,
Chk the idocs from SM58 of source system are processing fine into ur target system(BI system)...?
Chk thru Sm58 and give all * and target destination as ur BI system and execute and chk any entries pending there?
rgds,
Edited by: Krishna Rao on May 6, 2009 3:22 PM -
Error 8 when starting the extraction program (BI7.x)
I am receiving the following message when loading from the ODS to the data targets:
Error 8 when starting the extraction program
Message no. R3019
Diagnosis
Error 8 occurred when starting the data extraction program.
System response
The data extraction is terminated.
Procedure
Check for relevant OSS Notes, or create a problem message of your own.
I have searched the forums and OSS, and can't find anything that matches my situation exactly. I was originally getting an error message that the infosource (80FIA_DS11) didn't exist in the source system. I restored the BIP client and all transfer structures were reactivated. Now when I try to load, I get this error 8. Has anyone experienced this issue?
Thanks,
PamJosko,
I am also using BI 7.x and had the problem loading from DSO to Infocube. What are the entries in table ROIDCPRMS? What is the host name displayed when you run transaction SM51 in the BI system?
Pam -
Error 4 when starting the extraction program
Hello Gurus,
Yesteday I got one error "Error occured in the source system"that "Error 4 when starting the extraction program" and "error in the source system" has given, it has affected all the loads,please any one give me solution for thia it is urjent.
Please find the error message bello.
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
Thanks,
Muddu Reddy.Hi sekhar,
You can try this. you right click on the datasource and click on display in source system it takes you to the R/3 system enter the user id and password so u can now see the datasource in the R/3 so now click on back f3 so now u vl be in BI now replicate the datasource and try to load the data. I think now it should work fine.
Tell me if you still face some problem.
Thanks
Ram -
Message no. R3009 - error in extraction program for the DSO
Dear All,
I get the following error, when I execute the data source object, when I select monitor button in the window the process is in Red. So I couldn't get the report at the ODS. Please help me to clear the following error :
The extraction program does not support object ZSHIPTRACKND
Message no. R3009
Diagnosis
The application program for the extraction of data was called up using the invalid InfoSource/invalid InfoObject ZSHIPTRACKND.
System Response
The data extraction is terminated.
Procedure
Check the SAP Support Portal for the appropriate Notes and create a customer message if necessary.
with Regards,
JeraldWhat release are you at?
Have you searched SAP Notes and the SDN forums for this. A quick search indicates 9 SAP Notes and 15 SDN posts regarding this error message. Unless we know what release level you are at we are unable to offer viable solutions. -
Datasource problem - error 8 when starting extraction program
Hello,
we are using a datasource (data mart) to write data from one cube to another.
When running the infopackage we get the 2 errors below. When testing with the extractor checker, everything was fine. Datasource was replicated, transfer rules are active.
1. Message no. R3019 - Error 8 when starting extraction program
2. Message no. RSM340 - Errors in source system
more error info...
" Error message from the source system
Diagnosis
An error occurred in the source system.
System response
Caller 09 contains an error message.
Further analysis:
The error occurred in Service API ."
Has anybody any ideas?
Thank you,
RuairiHi Friend,
Check the following OSS notes
947690
511475
23538
Even though the note 947690 is for process chain the steps mentioned in this note could cause Error 8 when scheduling a package for extraction. I think in your case the server name or the host name is incorrect. Check the host and the server name in TCODE SM51 and ask basis to look for the same in RFC entries using SM59 as well.
Regards,
varun. -
Message "Error 4 when starting extraction program" with any extraction.
Hi to everyone.
We have a problem in a pre-existing BW system of development.
When we start any extraction (for example 0MATERIAL_ATTR), the monitor give us the following error:
ERROR 4 WHEN STARTING THE EXTRACTION PROGRAM (R3-19).
I've checked the link between the two system, and it may be right. When I check the soursystem from BW I havn't any error.
Then, when I test the extractor on R/3 with RSA3, any error as result and the tester extracts a lot of records.
Anyone have any idea ?
MaxThanks for your fast help.
Claudio, the messages are only two ...
- Error 4 when starting the extraction program
R3 19
- Errors in source system RSM 340
No dump on the R/3 and BW.
Roberto, I've followed the note 325470 too, but the problem remain. Only one ... the note 147104 say ...
"This server must be capable of starting a background process for data extraction".
Is there a way to check this point ?
Thanks in advance guys.
Max -
Error 8 when startingthe extraction program
Error 8 when startingthe extraction program
Hi Friends,can anyone tell what the error is:
Message no. R3019
Diagnosis
Error 8 occurred whenstarting the data extraction program.
System response
The data extraction is terminated.
Procedure
Check for relevant OSS Notes, or create a problem message of your own.It may be due to non background user trying to run the job in background.
You might want to change the user type for the user id used to run th eextraction.
you may use su01, and change the user type in tab 'logon data', set the type to 'system' or 'background'. ask basis help if you have no authorization to do so. -
PS CS3: "could not complete your request because of a program error"
Hi,
I am using Photoshop CS3 on Windows XP Pro (Upgraded from PS v7.0 a few months ago) on about 10% of my images I'm getting an the error:
"could not complete your request because of a program error"
when trying to save the file after doing changes to it. Oddly enough I do NOT get the error when doing "Save As" even after the recieving the error on a save. Nor do I get the error if I open one of the affected files in PS v7.
I believe from searching on line that the problem is "something to do" with the format of the metadata in the images. I am not sure exactly what, nor am I sure why it only affects about 10% of my images - all of which have been processed, captioned and keyworded the same way. However it is noticable that I cannot open "File info" dialog box in PS CS3 for any image that won't save. The error given is: "Could not complete the File Info command because of a problem with the File Info module"
Oddly, I CAN open the same File Info dialog box in Bridge CS3, I can change metadata via Bridge but then even after doing that the problems still exist when the image is opened in Photoshop.
At the moment, the ONLY work round I have is for each effected image, open it, do a "save as" - to save it under a different name delete the original image and then rename the image back to it's original name to ensure that my DAM can still locate the image.
I am a professional photographer with over 25,000 PSD files. As you can imagine it is impractical to manually open every image to see is affected. Can anyone think on any automated method to locate which images have the problem?
Does anyone have a fix to this problem? The workround above has one MAJOR drawback. Like most/all DAM users I locate and open my images from within my DAM (IMatch in my case). If I use the save-as/delete/rename method while the DAM is open I lose the data records associated with the image in the DAM. (The data is lost when the original image is deleted).
Any help would be appreciated. This is becoming a MAJOR problem for me.
Thanks,
Ian M Butterfield
www.imb.bizHi Rob,
I've uploaded one of the images to my server....
http://www.iphotos.co.uk/downloads/tmp/FA0309A-E02305.zip (30Mb download).
I wouldn't say that the "image" is corrupt - the "image" is fine and in fact "Save As" to a new filename corrects the problem altogether. What I would say is that PS CS3 isn't handling the metadata in some of my images correctly. I use a lot of different programs to view/edit/update both image and metadata. PS CS3 is ONLY program I have found that has any problem with the files.
I only have two makes of camera Canon 5D and 10D. I can't say for certain whether it affects 10D files as the vast majoity of images I'm working on are from my 5D. What I can say however that not all images from a given shoot with the 5D will be affected - only a small proportion of them.
Anyhow, please download the zip file and extract the PSD to a suitable location. Then open the image in PS CS3 from that location. Make a minor edit to the image and you will see that PS CS3 can't save the file. Quit. Open the image again and select "File | File Info" and you will see the other error message. If you open the file and do "save as" to a new filename and repeat the above step everything works as it should.
If this was just a single file that I was having problems with I'd put up with the work round of "Save as" to correct the problem. But with 25,000+ PSD files and at a guess a random 10% of my files being affected you can imagine how frustraiting this is.
Thanks,
Ian. -
The extraction program does not support object 0JOB_ATTR
HI all,
I'm getting the following error when execting 0JOB_ATTR extractor in R/3 system (via RSA3):
The extraction program does not support object 0JOB_ATTR
Message no. R3009
Diagnosis
The application program for the extraction of data was called up using the invalid InfoSource/invalid InfoObject 0JOB_ATTR.
System Response
The data extraction is terminated.
Procedure
Check the SAP Support Portal for the appropriate Notes and create a customer message if necessary.
I've found various threads with this error (or similar ones), but none of them are solved (or not published solution). Haven't found any SAP notes yet either, so any input would be very helpfull.
Thank you.
G.0JOB_ATTR not in use and SAP replaced this with 0EC_CJOB_ATTR... U have to use 0EC_CJOB_ATTR to load master data for 0JOB.
Even i faced the same problem and found the following info in one of the SDN thread, and we are using 0EC_CJOB_ATTR (make sure u have data in table HRP5050).
I have sent a message to SAP asking for the solution . Below is the reply what they gave.
"This error appears because of naming conventions we have to switch the name of the Data Source from 0JOB_ATTR to 0EC_CJOB_ATTR. Please use this data source to extract the compensation job attributes to BW.
Note also that data source 0EC_CJOB_ATTR extracts data from table HRP5050.
If no data is being extracted please do the following:
If you have data in HRP5050 and still do not get any data please try the following :
1) Take over the Data Source from the business content (RSA5)again and check in RSA3 .
2) Replicate the Data Source to BW
3) Activate the Info Source again.
4) Delete any previous delta initializations for the datasource.
5) Initialize the delta again
6) Try to load data". -
Extraction program for EH&S (EH&S to XI scenario)
Dear Experts,
I am from the XI background and am new to EH&S. I would like to know whether there exists an extraction program to extract substance data from EH&S(ECC) and send it to XI. If yes then what is it? The EH&S team here doesn't know of any kind. They have only used Change pointers to extract data from one client to the another.
Please help.
Thanks,
MerrillyHello,
How to set up ALE for substances is described in the IMG / Customizing for EH&S.
For EH&S 2.7B on R/3 4.6C this is located under:
Environment, Health & Safety -> Product Safety -> Interfaces -> EH&S Application Link Enabling (ALE) -> ALE for Specification Management.
All necessary information should be found in 'Set up Distribution of Specification Data':
Set Up Distribution of Specification Data
In this IMG activity you set up the distribution of data on
specifications (see also Information About the Concept in EH&S
Application Link Enabling (ALE)).
Requirements
1. Setting the Active Code Page
To transfer the data using ALE, you must ensure that the active code
pages are the same in the receiving system and sending system as
follows:
- You must select a code page for transfer (for example, SAP(ISO)
code page 1100) that you set up on all SAP Systems that belong
to your ALE distribution model.
- In Customizing for Product Safety in the IMG activity Specify
Environment Parameters using the environment parameter
ALE_TRANSFER_LANGUAGE, you must specify a language of the
previously selected code page as the transfer language in the
sending system. This language controls which code page is active
in the sending system during data transfer.
- The RFC destinations of the target systems must be defined with
the logon language that corresponds to the specified code page.
- If data is to be transferred to different SAP(ISO) code pages,
the operating systems of the sending and receiving systems must
use the same character sets (ASCII or EBCDIC):
Sending system Receiving system Transfer possible
AS400 AS400 Yes
UNIX UNIX Yes
NT NT Yes
NT UNIX Yes
UNIX NT Yes
AS400 NT No
AS400 UNIX No
NT AS400 No
UNIX AS400 No
For more information, see:
- The IMG activity Specify Environment Parameters
- The IMG activity Set Up EH&S Native Language Support
- The Product Safety documentation in the section EH&S Native
Language Support
2. Settings in Customizing for Distribution (ALE)
You have made the necessary settings in Customizing for Distribution
(ALE).
Also maintain, for example, the sections
- Basic Settings
- Communication
3. Settings in the Product Safety Component
Make sure that you have fulfilled the following prerequisites:
a) Maintain the environment variables for serialization
Serialization collects the IDocs and makes sure that they are
processed in the correct order. For more information, see
section Serialized Distribution in Customizing for Distribution
(ALE).
You specify the serialization number for the sending logical
system in the IMG activity Specify Environment Parameters using
the environment parameter ALE_SERIAL_ID. You specify one unique
channel per logical system.
b) Specify specifications to be distributed
If you want to distribute specification data manually, choose
the specification directly from the hit list in specification
management.
For automatic distribution, the specifications must appear in a
set of hits that is assigned to the distribution method. If a
set of hits has not been assigned, all of the specifications are
distributed, providing that you have not defined filters.
Apart from standard filters (see below), you can use the
following customer exits to define further restrictions and
filters:
- Specify Additional Table and Parameter Filter (1)
- Specify Additional Table and Parameter Filter (2)
c) Ensure unique identification of specifications
The specification object must have a unique specification key.
In the standard system, identification is supported by the
specification key.
You can use the customer exit Develop Enhancement for
Identification to enhance the identification, for example, to
link with one or more identifiers.
d) Check authorizations
For manual distribution and automatic scheduling, you must have
the read authorization for all the specification data to be
distributed.
You also need the appropriate authorizations for inbound
processing in the target system.
Activities
1. Maintain the Distribution Model in Distribution (ALE) Customizing
In Customizing for Distribution, call the IMG activity Maintain
Distribution Model.
For more information, see the documentation for the IMG activity.
To guarantee communication between systems during distribution, you
must make the following entries in the IMG activity Maintain
Distribution Model by choosing Add method:
Field Entry
Sender/client: <Key for EH&S system>
Receiver/server: <Key for target system>, for example,
Sales and Distribution system (SD), on which EH&S
is installed.
Object name/interface: Substance (substance(specification),
BUS1077)
Method: SavRepMul (save replicated specifications)
Note:
Message type SUBMAS is supported.
You can set the following filters:
- Reducing specifications by determining recipients:
You can reduce the specifications to be distributed by defining
the following filters:
- Specification type
- Authorization group
- Substance nature
- Set of hits (external key of group object)
You can enter several values for a filter field. Individual
values are linked with OR, whereas the filter groups are linked
with AND.
If no filters are entered, all specifications are distributed.
- Reducing specifications using 'IDENTHEADER' filtering
You define the identification category and identification type
whose specifications are to be distributed.
- Reducing data using 'PROPHEADER' filtering
You specify the value assignment types for which specification
data is to be distributed.
- In Distribution (ALE) Customizing, you can use the IMG activity
Set Up Segment Filtering to exclude further tables from
distribution, for example:
- Material assignment
- Regulatory list assignment
- Reference specification assignment
- Usage
- Assessment
Then in Distribution (ALE) Customizing, you maintain the IMG
activity Generate Partner Profiles.
2. Maintain Settings in the Sending and Recipient Systems
The following tables must be maintained in the same way in the
sending and recipient systems:
- Value assignment type TCG01 and description TCG02 (system
tables)
- Table of names for the DDIC objects TCG03 (system table)
- Table of names for the child DDIC objects TCG04 (system table)
- Specify Value Assignment Types
Value assignment type TCG11 and description TCG12
Value assignment type - specification type assignment TCG13
- Identification category TCG21 and description TCG22 (system
tables)
- Check Identification Types
Identification type TCG23 and description TCG24
- Check Identification Listing
Identification listings TCG26 and description TCG27
Definition of identification listings TCG28
- Assign Characteristic-Specific Identification
Overriding identification list definitions TCG29
- Specify Specification Types
Specification type TCG31 and description TCG32
- Specify Authorization Groups
Authorization object TCG36 and description TCG37
- Specify Types for User-Defined Texts
Value assignment text type TCG41 and description TCG42
- Create Sources
Source TCG46
- Specify Source Types
Source type TCG47 and description TCG48
- Set Up Property Trees
Property tree TCG51 and description TCG52
Property tree - value assignment type assignment TCG53
- Specify Data Origin
Data origin TCG56
- Specify Phrase Libraries and Phrase Groups
Phrase library TCG61 and description TCG62
Phrase group TCG63 and description TCG64
- Specify Language Selection
Phrase language (languages supported in phrase library) TCG65
- Value assignment type class characteristic TCG66
System table, filled using master data matchup
- Check Value Assignments
Value assignment assessment TCG71 and description TCG72
- Specify Component Types for Compositions
Component type TCG76 and description
- Specify Regulatory Lists
Regulatory list TCG81 and description TCG82
- Specify Ratings
Value assignment rating TCG86 and description TCG87
- Specify Validity Areas
Validity area TCG91 and description TCG92
- Specify Usage Profiles
Usage profile TCG96 and description TCG97
Usage profile - rating - validity area assignment TCG98
- Specify Exchange Profiles
Exchange profile TCGC3 and description TCGC4
- Specify Environment Parameters
General environment parameters TCGENV
- Protect Characteristics Within Namespace
Namespaces for characteristics TCGK1
- Manage User Exits
User exit parameters from user exit management TCGUEEN
User exits from user exit management with function module
assignment TCGUEFU
Language-dependent user exit names from user exit management
TCGUENA
User exit categories from user exit management TCGUETY
3. Check Master Data to Be Distributed
For the ALE process, the following master data must be distributed
to all the relevant systems:
- Phrases
- Phrase sets (for systems, in which data is created)
- Classes and characteristics
- Materials (all material data that is required for
material-specification assignment)
- Change numbers
Note:
Classes and characteristics are distributed via export and
import. The help texts and phrase sets are also transferred to
other systems along with the classes and characteristics.
Classes and characteristics can also be distributed using ALE.
Note:
The required data providers must have been created manually in the
Product Safety component under Tools -> Edit addresses -> Data
provider before data is distributed in the recipient system. The
data providers must be unique with regard to the following three
fields:
- Name (NAME1)
- City (CITY1)
- Country (COUNTRY)
During distribution, the data providers of the specification to be
sent are read and also distributed. When writing to the recipient
system, the SAP System determines the corresponding address number
for the data provider in the recipient system by comparing the three
fields Name, City and Country for the address numbers that were
sent, and then transfers this address number that was determined to
the Data provider field (OWNID).
You can determine the address number of the data provider in
Customizing for Product Safety in the IMG activity Specify
Authorization Groups.
To do this, call the input help for the Data prov. field in the IMG
activity. You will find the value you require in the Addr. no.
field.
The address number is not displayed in address management in the
Product Safety component.
4. Check Control Data to Be Distributed
See above: "Maintain Settings in the Sending and Recipient Systems"
5. Check Consistency
A consistency check can be performed for the settings in the
distribution model and the partner profiles.
To do this, in Distribution (ALE) Customizing, call the IMG activity
Check Partner Profiles and Model Settings.
The distribution model must have been distributed and the partner
profiles must have been maintained in all relevant systems.
6. Error Handling
As soon as an error occurs when an IDoc is processed, the whole IDoc
is not updated. You can use a workflow to correct errors. IDocs can
be modified manually (you can change the identifier, for example)
and updated retrospectively.
General Procedure
1. In a customer reference model you define which data is to be
distributed to which system. You use sets of hits to define the
specifications that are to be distributed and specify filters with
regard to specifications or specification data as required.
2. The first time you distribute specifications to the target systems,
you do it manually, using the method REPLICATE according to the
distribution model. Serialization must be switched off.
3. You activate serialization and switch on delta distribution as
follows:
Activating Serialization
a) In Customizing for Product Safety, in the IMG activity Specify
Environment Parameters specify the channel for the parameter
ALE_SERIAL_ID through which the ALE data is to be distributed.
b) In Customizing for Distribution (ALE) choose Set Up Data
Distribution -> Serialized Distribution -> Serialized
Distribution Using Object Types -> Activate Inbound Object Types
and specify the inbound object types for which serialization is
to be performed.
c) Schedule a job (RBDAPP01) that posts the IDocs that arrive in
series in the recipient system.
Switching On Delta Distribution
a) Activating change pointers for a message type
Changes to master data objects are logged in the form of change
pointers during master data distribution. To activate the
writing of change pointers, in Customizing for Distribution
(ALE) choose Set Up Data Distribution -> Master Data
Distribution -> Activating Change Pointers -> Activate Change
Pointers for Message Types and set the Active indicator for the
message type for which you want to realize delta distribution.
b) Activating change pointers for each field
From the SAP R/3 screen, choose Tools -> Business Framework ->
ALE -> Development -> Master data -> Activate change pointer for
each field and enter the message type for which you want to
determine fields, for which the SAP System writes change
pointers. All relevant data fields are delivered. If necessary,
adjust the table to your requirements.
c) Activating change pointers generally
To generally activate master data distribution using change
pointers, in Customizing for Distribution (ALE), choose Set Up
Data Distribution -> Master Data Distribution -> Activating
Change Pointers -> Activate Change Pointers (generally) and set
the active indicator.
d) Scheduling delta distribution as a job
You can perform delta distribution manually or schedule it as a
job.
To perform delta distribution manually, from the SAP R/3 screen
choose Tools -> Business Framework -> ALE -> Administration ->
Periodic processing -> Process change pointers and enter the
message type you require and choose Execute.
To schedule delta distribution as a job, in Customizing for
Distribution (ALE) choose Scheduling Periodic Processing ->
Scheduling Generation of IDocs from Change Pointers -> Define
Variants and create a variant. Then in the IMG activity Schedule
Jobs create a job (RBDMIDOC) for the variant. You can set the
time at which distribution is performed, for example,
immediately after a change or periodically.
The following applies when transferring data:
o If a specification is not found in the target system, it is created
with the specification key that is transferred.
o If a specification is available in the target system, its data is
updated.
o When complete specification data is being sent, the specification is
locked and no changes can be made to it. If this lock cannot be set,
the specification cannot be processed. The IDoc is given the status
with error and a work item is created.
Note:
In manual distribution, change pointers are not taken into account.
In other words, the entire data record is distributed and delta
distribution is not performed.
Note on Executing the Report Program RC1PHDEL:
You must NOT schedule the report program RC1PHDEL (physical deletion
of data) to run in the source system or manually run it between
initial distribution and delta distribution, because the keys of
logically deleted data records can no longer be read and distributed
by delta distribution after the report program has been executed.
Before initial distribution you can execute the report in the source
system.
In the target system you can execute the report program independent
of distribution, as long as the target system does not serve as the
source system for further distribution.
If you want to execute the report program after the first delta
distribution, you must first make sure that all change pointers
created have been fully processed by the delta distribution and, if
possible, that all IDocs (intermediate documents) created were also
successfully posted in the target system. Otherwise, there is no
guarantee that the source and target systems will be consistent.
Example
The report program RC1PHDEL was executed in the source system so
that the deletions of an identifier of the identification category
NUM and the identification type CAS and a phrase item were not
distributed.
Then an identifier of the identification category NUM and
identification type CAS with the identical value that was previously
deleted and a phrase item for the same phrase in the previously
deleted language are created. The following errors occur in the
subsequent delta distribution:
- The identifier cannot be created because the NUM-CAS value
already exists. The IDoc cannot therefore be posted.
Notes:
If you attempt to create duplicate identifiers in the dialog,
the same error messages will be displayed as when posting using
ALE.
If the NUM-CAS identifier was not identical to the previously
deleted identifier, the IDoc would be posted successfully and
the identifier would be created in addition.
- The phrase item cannot be created, because only one phrase item
is permitted for a phrase in each language. The old phrase item
must be deleted first before the IDoc can be posted.
The next section describes the solution for similar error cases. You
should, however, try to avoid the need for this procedure by not
executing the report program.
e) In the target system in the dialog, delete the EH&S objects
(specifications, phrases, reports), for which you have already
run delta distribution. These objects are internally marked with
a deletion indicator.
Caution:
When you distribute reports, the report bodies are distributed.
To delete these, you simply need to delete all report reference
specifications. Deleting report bodies is not necessary and also
not possible. If you cannot delete objects (such as
specifications or phrases) owing to their where-used-list, it is
sufficient to delete the 'deleted' detail data in the target
system that has not been distributed. This may require more
processing effort than if you delete all the objects using the
hit list and distribute all the data again in full.
f) In the target system, set the Set missing deletion indicators
and Delete physically indicators in the RC1PHDEL report program
and execute the report program in the target system.
This triggers the following actions:
- The deletion indicator is set in the tables that depend on the
header data to be deleted.
- All data with deletion indicators is deleted physically.
- The corresponding entries in the table ESTALE (conversion
table for ALE) are deleted physically.
g) Deactivate the active serialization and the writing of change
pointers and start initial distribution of all objects again.
h) You can now activate the writing of change pointers and
serialization again and use delta distribution as usual.
Note:
If you still have IDocs in the source system or target system that
were created before the deletion in your target system, but were not
distributed or posted, ignore these IDocs and do not post them. You
can do this by changing the channel before repeating the initial
distribution by using the environment parameter ALE_SERIAL_ID (for
more information on the environment parameter, see the IMG activity
Set Up Distribution of Specification Data).
Return ->
Application
Hope this helps
Mark -
Category ABAP Programming Error
Runtime Errors MESSAGE_TYPE_X
ABAP Program CL_RSBM_LOG_DTP_DP============CP
Application Component BW-WHM-DST
Date and Time 28.04.2014 15:08:07
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).Error analysis
Short text of error message:
*** Data request to the OLTP ***
Long text of error message:
Technical information about the message:
Message class....... "RSM"
Number.............. 000
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
please use the following search criteria:
"MESSAGE_TYPE_X" " "
"CL_RSBM_LOG_DTP_DP============CP" bzw.
"CL_RSBM_LOG_DTP_DP============CM001"
"ADD_MSG"
If you cannot solve the problem yourself, please send the
following documents to SAP:
Information on where terminated
Termination occurred in the ABAP program "CL_RSBM_LOG_DTP_DP============CP" -
in "ADD_MSG".
The main program was "RSBATCH_EXECUTE_PROZESS ".
In the source code you have the termination point in line 111
of the (Include) program "CL_RSBM_LOG_DTP_DP============CM001".
The program "CL_RSBM_LOG_DTP_DP============CP" was started as a background job.
Job Name....... "BIDTPR_1276822_1"
Job Initiator.. "BWREMOTE"
Job Number..... 15080600
Source Code Extract
Line SourceCde
81
82 l_posit = l_posit + 1.
83
84 l_s_mess-requid = p_requid.
85 l_s_mess-datapakid = p_datapakid.
86 l_s_mess-step = l_step.
87 l_s_mess-substep = l_substep.
88 l_s_mess-runid = p_runid.
89 l_s_mess-posit = l_posit.
90 MOVE-CORRESPONDING i_s_msg TO l_s_mess.
91 if not ( l_s_mess-msgty = 'I' or
92 l_s_mess-msgty = 'S' or
93 l_s_mess-msgty = 'W' or
94 l_s_mess-msgty = 'A' or
95 l_s_mess-msgty = 'E' or
96 l_s_mess-msgty = 'X' ).
97 l_s_mess-msgty = 'I'.
98 endif.
99 CALL FUNCTION 'RSSM_GET_TIME'
100 IMPORTING
101 e_timestampl = l_s_mess-timestamp.
102 APPEND l_s_mess TO p_t_mess.
103
104 READ TABLE p_t_header INTO l_s_header WITH KEY
105 requid = p_requid
106 datapakid = p_datapakid
107 step = l_step
108 substep = l_substep
109 runid = p_runid.
110 IF sy-subrc <> 0.
>>>>> MESSAGE x000(rsm).
112 ENDIF.
113 IF l_s_header-max_state IS INITIAL OR
114 l_s_header-max_state < cl_rsbm_log_dtp_req=>convert_msgty_to_state( l_s_mess-msgty ).
115 l_s_upd-requid = p_requid.
116 l_s_upd-datapakid = p_datapakid.
117 l_s_upd-step = l_step.
118 l_s_upd-substep = l_substep.
119 l_s_upd-runid = p_runid.
120 l_s_upd-max_state = cl_rsbm_log_dtp_req=>convert_msgty_to_state( l_s_mess-msgty ).
121 APPEND l_s_upd TO l_t_upd.
122 l_header_changed = 'X'.
123 ENDIF.
124 IF l_header_changed = 'X'.
125 IF l_s_header-substep <> '0' AND
126 l_s_header-step <> '0'.
127 READ TABLE p_t_header INTO l_s_header WITH KEY
128 requid = p_requid
129 datapakid = p_datapakid
130 step = l_step -
Incorrect call-up of the extraction program
Hi,
I am trying to extract the data from R/3 into BW through a function module( function module based extraction).
I get the error message while trying to extract in RSA6 as
"Incorrect call-up of the extraction program".
Could you please let me know if its the problem in any settings or any other issue.
Thanks
Regds
GautamHi Gautam,
If possible send the Code for your fm....and i think the error shld be name of the data source.
You need to mentioned the name of the data source in your code i_datasource.....
If this help please assign points.
Regards,
Pawan.
Maybe you are looking for
-
Hello, The following command runs without problem or any output. It wouldn't create any entry. Also my refind.conf is not being followed. rEFInd is able to detect kernels and boot fine from /boot efibootmgr -c -g -d /dev/sda -p 1 -w -L "rEFInd" -l '\
-
I have done something really stupid. Whilst attempting to extend the partition for my boot camp with winclone, I inadvertently wiped my external hard drive by creating a partition the whole size of the external hard drive instead of 40g which would h
-
Line item problem in FBL3n and FS10n
Dear ALL FI expert In my one G/L account(WIP) I do not see any line item data using FBL3n, FS10n. But the transaction is made in period jan ~ march/2009. Can anybody tell me why the problem happend? Note: Actually I can see last year data and it is o
-
Hi, I get this error when I try to supply a String object as the query parameter to the where clause. The annoying thing is when I convert the value that I pass to a date object, the error message would change to expected NUM got DATE!!! how can I so
-
Display Arabic numbers in dashboard
Hi, I want to display year in Arabic format in drop down box component of Xcelsius 2008 SP2. For example: ٢٠١٠, ٢٠١١ ... Is it possible? Thanks, Rakesh Edited by: Rakesh Khandelwal on Feb 16, 2012 6:15 PM