Activation Error in ODS - Record mode 0 unknown (data record REQU_4DPGJKCKN
I created a generic extractor in R3 with a generic delta. In BW, my delta init loads with no errors but when I activate the data in the ODS, I get the activation error.
"Record mode 0 unknown (data record REQU_4DPQ31IK7WM9OTK26S5JMJ6LM/000001/"
I searched SDN but didn't found anything, and I searched help but only found general information about 0recordmode.
Can someone provide a solution and/or some more detailed information about the error message?
Thanks
Hello,
When you have created the InfoSource for the generic datasource, have you added field 0RECORDMODE to the InfoSource? When loading data to a ODS, 0RECORDMODE is essential.
The InfoObject is usually mapped to ROCANCEL (Indicator: Cancel Data Record) field of the extractor. This field is usually present in Standard extractors. But even if the field is not present in your extractor, add it to InfoSource Communication structure and leave it unmapped in transfer rules.
I think this might solve the problem.
Regards,
Pankaj
Similar Messages
-
Searching attibutes in the record mode in Data Manager
Hi,
If i create a new attribute in taxonomy mode,i cannot view it in the corresponding search in the record mode in Data Manager.The particular attribute which i have added is not getting displayed in the attributes in the search pane.If i have to search for that attribute in the record mode what should i do.
Thanks and Regards,
Preethihi Preethi,
there are a few differencies between fields and attributres
have a look at table:
Tab. 1 Comparison Fields vs. Attributes
from this document
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5d4211fa-0301-0010-9fb1-ef1fd91719b6
for search options based on attributes have a look at the bottom
of the table I mention
hope this will clarify a little bit
Regards,
michal -
Hi
when i am loading the data i got the error " Record 3 :0OPERATION : Data record 3 ('0001004854220010 ') : Language key is initial " .
lot of records are there like this.
Can you put a light on this.
Reward points .
Thx
sivaEven I am facing the same problem. Can any one help us out. I have Master data load, but as Info provider loading. I have added 0LANGU in attributes info source and in my flat file, i have 'E' as the value for 0LANGU. When I load attributes data, it gets succesfull along with 'EN' for 0LANGU (Conversion). In my text info source I have Key Number and Medium description fields. When I load Text file, it gives me the error ' ' Record 1 :0OPERATION : Data record 3 ('0001004854220010 ') : Language key is initial' and its for all records in the text file.
Edited by: venu Avula on Jun 16, 2008 9:52 PM -
HI Gurus,
I have a typical scenario.
I am loading data into ODS.The data loads get completed but activation is failing.Giving no error.
At the same time data is getting reportable, but when I check into the active data table, the number of records is 0.
I tried to force it green so that I can carry out manual activation,but the status(both QM & Technical) is not changing.
I tried deleting & loading the data again.NO success.Is it some BASIS issue?If yes, then plz let me now the probable solution.
Plz help.Hi,
when you go for manual activation
Go to ODS Manage screen
Click on activate button
you will get the POPUP
where you have the Button Job Overview
Select that and look for the Job log
try to find at which step it is getting failed
if you can solve it
Please past the Log here
we will try to provide the solution
Regards
Hari -
Error message "EDI: Field SEGNAM in data record is default"
Hi all,
I am facing issue in Idoc creation. I am getting error message saying 'EDI: Field SEGNAM in data record is default' and so Idoc is not getting created.
Can anybody tell me how to resolve this. I checked in debugging mode and found that this error message is coming from a standard program.
Waiting for some good replies.
Thanks,
ArchanaHi,
Yes, it is getting displayed from FM 'EDI_SEGMENTS_ADD_BLOCK'.
But not getting any clue how to resolve this as it is getting displayed from standard program.
Any clue on this?
Thanks,
Archana -
Activation error in ODS 0FIGL_O02
Hi,
I am facing one problem in my BIW that daily the activation of the ODS 0FIGL_O02 is failing. Daily I am activating the data using the program RSODSACT1.
It is included in the process chain.
Please help me to remove my manual work for activation tha data of the ODS.
Thanks,
Nitesh.Hi,
You can give this a try:
uncheck the "Activate ODS object data automatically" setting in DSO, and include the DSO data activation step in the process chain. this will the serailize the process and hope fully solve your issue.
Hope this helps...
Regards,
Umesh -
0pp_c15 activation error - Field /BI0/ACOPC_O0100 is unknown
hi,
There is an error occured while activating the cube 0PP_C15 - Backlogged production orders.Transformation 0PP_C15 80PP_DS01 is not active .
The following error shown in its transfer routine while trying to activate the transformation.
E:Field "/BI0/ACOPC_O0100" is unknown. It is neither in one of the
specified tables nor defined by a "DATA" statement. "DATA" statement.
Thanks & Regards
Shyne Sasimohanan
<removed by moderator>
Edited by: Siegfried Szameitat on Sep 29, 2010 3:53 PMHi,
Try to activate the DSO 0COPC_O01 and re-activate the transformation.
Hope this helps...
Rgs,
Ravikanth. -
Activation error in ODS:URGENT
Hi All !
The data was loaded successfully to ODS but there was activation failure due to <b>Communication error ( RFC call ) occured .</b>
Moreover , it is saying ..<b>Request REQU_1W740A2GOY7338IOPKOF2VC4F , data package 000001 incorrect with status 9</b> .
Could tell me the reason ? And some more details about status . Sometimes it is giving Status1 , 2 , 9 . What does this mean ?Hi Rajib Goon
Just rerun the Activation Job Since its succesfull up to loading . If not just make
the Qm status in to manuall red though its in red and then just reschedule the
INfopak .Be fore rescheduling make just have a check reg RFC connectivity from u
r Basis Team.
Thanks & Regards
R M K
**Winners dont do different things,they do things differently**
> Hi All !
>
> The data was loaded successfully to ODS but there was
> activation failure due to <b>Communication error (
> RFC call ) occured .</b>
>
> Moreover , it is saying ..<b>Request
> REQU_1W740A2GOY7338IOPKOF2VC4F , data package 000001
> incorrect with status 9</b> .
>
> Could tell me the reason ? And some more details
> about status . Sometimes it is giving Status1 , 2 , 9
> . What does this mean ? -
Hi Experts,
I am loding to the data to ODS,When i am loding data to ODS It's Showing below given error
Record mode 1 unknown data record , activation failed,Please give him to suggestion so that i am go throw that your suggetion please help me.
Regards,
Suresh.Hi,
RECORDMODE object can only have values N,R,X,D, and blank ...
It cannot have 1 as the value in the recordmode field.
check your mappings for the RECORMODE object in the DSO and see which field you have mapped in the transformation for this DSO.
if not appearing in the main transformation then look for it in the other rule groups.
Its should be mapped to either ROCANCEL or any indicator like deletion indicator..which brings only X and blank.
If nothing like that is coming from the datasource then you can leave it blank and should not map to anything.
Right now I think you have done wrong mappings and have recordmode to something which is bringing values 1.
correct the mappings and reload the data.
Thanks
Ajeet -
Loading ODS - Data record exists in duplicate within loaded data
BI Experts,
I am attemping to load an ODS with the Unique Data Records flag turned ON. The flat file I am loading is a crosswalk with four fields, the first 3 fields are being used as Key Fields in order to make the records unique. I have had this issue before, but gave up in frustration and added an ascending number count field so simply create a unique key. This time I would like to solve the problem if possible.
The errors come back referring to two data rows that are duplicate:
Data record 1 - Request / Data package / Data record: REQU_4CNUD93Q3RCC80XFBG2CZXJ0T/000003/ 339
Data record 2 - Request / data package / data record: REQU_4CNUD93Q3RCC80XFBG2CZXJ0T/000003/ 338
And below here are the two records that the error message refers to:
3 338 3902301480 19C* * J1JD
3 339 3902301510 19C* * J1Q5
As you can see, the combination of my three Key Fields should not be creating a duplicate. (3902301480, 19C(asterisk) , (asterisk)) and (3902301510, 19C(asterisk) , (asterisk)) I replaced the *'s because they turn bold!
Is there something off with the numbering of the data records? Am I looking in the wrong place? I have examined my flat file and can not find duplicates and the records that BW say are duplicates are not, I am really having a hard time with this - any and all help greatly appreciated!!!Thank you for the response Sabuj....
I was about to answer your questions but I wanted to try one more thing, and it actually worked. I simply moved the MOST unique Key Field to the TOP of my Key Field list. It was at the bottom before.
FYI for other people with this issue -
Apparantly the ORDER of your Key Fields is important when trying to avoid creating duplicate records.
I am using four data fields, and was using three data fields as the Key Fields. Any combination of all three would NOT have a duplicate, however when BW finds that the first two key fields match, sometimes it apparantly doesn't care about the third one which would make the row unique. By simply changing the order of my Key Fields I was able to stop getting the duplicate row errors...
Lesson - If you KNOW that your records are unique, and you are STILL getting errors for duplicates, try changing the ORDER of your key fields. -
Hi friends,
In ods we are adding 0Recordmode .am i right?can u tell me is it compulsory to add 0recordmode for ods?what does it do?
thanks
manoHi Mano,
Most of the time the system by itself would the 0recordmode. The 0recordmode is most useful in the delta loads from the ODS to another ODS/Cube.
You would find lots of posts on the 0recordmode in this forum.
<u><b>From SAPhelp:</b></u>
RECORDMODE
Definition
This attribute describes how a record in the delta process is updated. The various delta processes differ in that they each only support a subset of the seven possible characteristic values. If a Data Source implements a delta process that uses several characteristic values, the record mode must be a part of the extract structure and the name of the corresponding filed must be entered in the Data Source as a cancellation field (ROOSOURCE-INVFIELD).
The seven characteristic values are as follows:
<b>' ':</b> The record delivers an after image.
The status is transferred after something is changed or added. You can only update the record straight to an Info Cube if the corresponding before image exists in the request.
<b>'X':</b> The record delivers a before image
The status is transferred before data is changed or deleted.
All record attributes that can be aggregated have to be transferred with a reverse +/- sign. The reversal of the sign is carried out either by the extractor (default) or the Service API. In this case, the indicator 'Field is inverted in the cancellation field' must be set for the relevant extraction structure field in the Data Source.
These records are ignored if the update is a non-additive update of an ODS object.
The before image is complementary to the after image.
<b>'A':</b> The record delivers an additive image.
For attributes that can be aggregated, only the change is transferred. For attributes that cannot be aggregated, the status after a record has been changed or created is transferred. This record can replace an after image and a before image if there are no non-aggregation attributes or if these cannot be changed. You can update the record into an Info Cube without restriction, but this requires an additive update into an ODS Object.
<b>'D':</b> The record has to be deleted.
Only the key is transferred. This record (and its Data Source) can only be updated into an ODS Object.
<b>'R':</b> The record delivers a reverse image.
The content of this record is the same as the content of a before image. The only difference is with an ODS object update: Existing records with the same key are deleted.
<b>'N':</b> The record delivers a new image.
The content of this record is the same as for an after image without a before image. When a record is created, a new image is transferred instead of an after image.
The new image is complementary to the reverse image.
<b>'Y':</b> The record is an update image.
This kind of record is used in the change log of an ODS object in order to save the value from the update. This is for a possible rollback and roll- forward for key figures with minimum or maximum aggregation. This record also has the update value for characteristics (in this case, it is the same as the after image). Null values are stored for key figures with totals aggregation. An update image is only required when the value from the update is smaller or larger than the before image for at least one key figure with minimum or maximum aggregation.
The table RODELTAM determines which characteristic values a delta process uses (columns UPDM_NIM, UPDM_BIM UPDM_AIM, PDM_ADD UPDM_DEL and UPDM_RIM). The table ensures that only useful combinations of the above values are used within a delta process.
When extracting in the 'delta' update mode in the extracted records for the record mode, a Data Source that uses a delta process can deliver only those characteristic values that are specified in the delta process.
Hope this helps.
Bye
Dinesh
Message was edited by: Dinesh Lalchand -
Is there any setting in ODS to accelerate the data loads to ODS?
Someone mentions that there is somewhere in ODS setting that make the data load to this ODS much faster. Don't know if there is kind of settings there.
Any idea?
Thankshi Kevin,
think you are looking for transaction RSCUSTA2,
Note 565725 - Optimizing the performance of ODS objects in BW 3.0B
also check Note 670208 - Package size with delta extraction of ODS data, Note 567747 - Composite note BW 3.x performance: Extraction & loading
hope this helps.
565725 - Optimizing the performance of ODS objects in BW 3.0B
Solution
To obtain a good load performance for ODS objects, we recommend that you note the following:
1. Activating data in the ODS object
In the Implementation Guide in the BW Customizing, you can implement different settings under Business Information Warehouse -> General BW settings -> Settings for the ODS object that will improve performance when you activate data in the ODS object.
2. Creating SIDs
The creation of SIDs is time-consuming and may be avoided in the following cases:
a) You should not set the indicator for BEx Reporting if you are only using the ODS object as a data store.Otherwise, SIDs are created for all new characteristic values by setting this indicator.
b) If you are using line items (for example, document number, time stamp and so on) as characteristics in the ODS object, you should mark these as 'Attribute only' in the characteristics maintenance.
SIDs are created at the same time if parallel activation is activated (see above).They are then created using the same number of parallel processes as those set for the activation. However:if you specify a server group or a special server in the Customizing, these specifications only apply to activation and not the creation of SIDs.The creation of SIDs runs on the application server on which the batch job is also running.
3. DB partitioning on the table for active data (technical name:
The process of deleting data from the ODS object may be accelerated by partitioning on the database level.Select the characteristic after which you want deletion to occur as a partitioning criterion.For more details on partitioning database tables, see the database documentation (DBMS CD).Partitioning is supported with the following databases:Oracle, DB2/390, Informix.
4. Indexing
Selection criteria should be used for queries on ODS objects.The existing primary index is used if the key fields are specified.As a result, the characteristic that is accessed more frequently should be left justified.If the key fields are only partially specified in the selection criteria (recognizable in the SQL trace), the query runtime may be optimized by creating additional indexes.You can create these secondary indexes in the ODS object maintenance.
5. Loading unique data records
If you only load unique data records (that is, data records with a one-time key combination) into the ODS object, the load performance will improve if you set the 'Unique data record' indicator in the ODS object maintenance. -
Unique Data Record Settings in DSO
Hello Experts,
I have checked Unique Data Record Settings in DSO.
Error Message while Activation of DSO through Process Chains.
Records already available in Activation Table
Duplicate Records
Activation error occurs & it specifies the Req No/Record No.
But in reality there are no duplicate records available in the specified Record No.
I faced this issue several times, why does this happen.
I guess this Unique Data Records Setting doesnt work.
Regards,
KVHi,
I am not sure why unique data setting is set, This is generally used when data with the same key will not come again or you are flushing the DSO and loading everyday. In normal cases it may happen for e.g there can be two records with the same sales document number as user might change the sales document twice.
So i think in u r case u dont need the check mark. Let me know if u have doubt.
Regards,
Viren -
SapErrorMessage=Inconsistent IDocs passed: Data records or control records
Dear Friends
I am not a basis guy but am doing that work, since we don't have any basis admin in our company. One of our clients using our server in the lab is doing some testing of sending IDOCs from one server to another and are getting the following error message
SapErrorMessage=Inconsistent IDocs passed: Data records or control records missing..
AdapterErrorMessage=Error occurred while calling function module "INBOUND_IDOC_PROCESS" in R/3
Is there any log files or some thing that I can see to get more info on this problem. I don't know where the log files related to this kind of problems get stored. Any feedback will be highly appreciated.
Thanks
RamHi,
thanks all for your help, great progress has been made!
There was no idoc record in sap as the document had not made it that far
A large part of the problem was my lack of understanding of sap versioning. My previous understanding was that you had a major version of the document: ORDERS01, ..., ORDERS05 and each of these have a version that relates to the software version, e.g. 47, 62, 64 etc.. which appears in the control record.
So I apparently have:
ORDERS05 64 V2
ORDERS05 64 V3
Can anyone explain this versioning model?
I would assume that V3 is the newer version but ...
thanks and regards
m -
Cannot display archived idoc data records in SARA
Hello,
In our ERP system, we regularly archive idocs older than 6 months. To view these archived idocs I use transaction SARA (with archive object IDOC and infostructure SAP_IDOC_001) to search for the relevant idoc that has been archived. Once the idoc is displayed, I drill down further by clicking the magnify glass button which then displays the idoc levels:
EDIDC Control record (IDoc)
EDIDD Data record (IDoc)
EDIDS Status Record (IDoc)
SRL_ARLNK SREL: Archive Structure for Links
When I try to view the Data Records, I get a message saying "You are not authorized to display table EDIDD". According to our Authorizations department, this is not an Auth issue but rather config setup or program issue.
Why can't I view the archived idoc data records? Is there another way to view archived idoc data?
Regards,
FawaazHi Jurgen,
Thanks for moving my post to the correct space.
Our Auth team is very confident that this is not a user auth issue. This could possibly be true because the idoc data resides on the following tables when in the database (before archive) - EDIDC, EDID4 & EDIDS. The idoc could then be viewed via transaction WE02 or the Data Browser (SE16). There is no EDIDD table in our ERP system so obviously no authorization object to assign to.
Once the idoc is archived, the data is removed from the ERP tables and moved to our archive database/server for storage. So when trying to view the archived record, the system does not access the ERP tables but rather the archive directory (that it's mapped to in settings). I assume the SARA transaction merely displays the data in the same segments/grouping with these table names (mentioned above in my first post) but instead of EDID4 it displays EDIDD.
According to the error longtext, "The check performed when data is read from the archive is the same as that of the Data Browser (transaction SE16)". So I was not involved with setting up our archiving procedure but could it be that table EDID4 was incorrectly mapped to table EDIDD in archives?
Regards,
Fawaaz
Maybe you are looking for
-
How to design a browser-like swing app ?
I'm about to write a browser-like application. There is a login screen and there are multiple windows much like these old web browser before they got tabs. - Should I extend JFrame and implement Runnable or shall I extend Thread and handle the JFrame
-
Issue on Creating RFx in webdynpro ABAP application - SRM Business Package
Hi We are in to SRM 7.0 with the same version of Business Package in SAP Portal also. I am trying to create a RFx from Portal which in turn calls the webdynpro ABAP application (Strategic Purchasing->Strategic Sourcing->Create Documents->RFx) sap/bc/
-
Iphoto troubles, moving, editing, sorting, everything..
Hi everyone, I just spent 4 hrs reading through most of the articles in here to find a solution. I am pretty convinced that I am the first one in here with this problem, unless I missed out a few post. I apologize if you have answered this problem be
-
AccessControlException while running XSLT started from JavaScript in jre1.5
All, My applet does XSLT using javax.xml.transform.Transformer. The transformation is initiated with a JavaScript call to Java and it is implemneted using AccessController.doPrivileged(...). It worked fine under JRE 1.4.2 but it throws exception unde
-
Guten Tag Ich habe ein Katalog (29,000 Fotos) von Photoshop Elements 11 in die aktuelle Testversion von Lightroom (englisch) importiert aber sie sind einfach von 1 - 29'000 durchnummeriert. Keine Ordner und keine Metadaten vorhanden. Ich habe mehrere