Record in DSO Active Table different from result of Update Rule Simulation

Hi,
I have a problem with the update of a particular Data Field for certain records via an Update Routine in 3.x Update Rules, from a Source DSO to one Target DSO.
The DSO Key is the same in the Source DSO and the Target DSO. The Update Routine for the particular (target) Key Figure performs a calculation based on a number of COMM_STRUCTURE Data Fields and gives the Result. For this specific record, the Result being written to the target DSO is 0.00 (It is an 'Amount' Key Figure).
Based on the Update Routine (which I have run through functionally), this is the incorrect result.
However, I have run Simulation for this record and the correct result is simulated into the Data Target. I have also run the simulation with Debugging on the Update Rules. Each component/step of the Update Routine is processed correctly, eventually giving the correct result.
I have tried to re-perform the load and I continually get the same result. This is occurring for a number of records being updated, but not all. Some records where the result of this Data Field is being calculated correctly are 'identical' in all important areas to the problem records.
The problem records all appear to be in the same Data Package, however that Data Package also contains records being processed correctly.
Based on the Simulation/Debugging it appears that the Update Routine is correct, however if anyone is willing to have a stab at this I am happy to send you the code.
Also, a short time ago, we took a copy back from our Production system to our QA system. As a result, this record exists in the QA system as well. I have performed the load there and the record is processed correctly. The Production and QA systems are in line.
Thanks and Regards,
Tom

Hi Ramesh,
Thanks for posting a response. This is an Update Routine rather than a Start Routine.
Also, in answer to the Sudhi's reply/post, Yes, the Update Type has been set to Overwrite.
The problem is actually only present in Production. Changes was made through our landscape some time ago (this is not my development).
These changes have been tested through QA and were working. It is only when a reload has taken place in production that this issue has been occurred. A reload has then taken place in QA and has worked successfully.

Similar Messages

How to check if a DSO Active Table is being used in any look-up's?

Hi Gurus,
We have a DSO that is being loaded on a weekly basis. Now this DSO is being loaded right from the time our project went live. There are no reports built on top of this DSO and the DSO is not being used as a Data Mart i.e. it doesn't feed any other DSO's or InfoCube's. Also this DSO is not being used in any MultiProviders.
So the only sensible reason for using this DSO that we can think of is that the data from this DSO is being 'looked up' by some other DSO's or InfoCube at run-time. So Is it possible to check if the active data table of an DSO is being ;looked up' at run time by some other data loads? I already tried using an 'Where Used List' on the active data table of the DSO, but it didn't show any results.
Thanks
Arvind

Try the following:
Check the table RSAABAP in SE16, you can search the technical name of DSOs active table in field EDIC.
You get all Code-IDs, where this table is used in ABAP coding.
In RSAROUT you can check, which code-type it is.
Now you know, if the DSO is used in any routines.
Hope this helps.
Regards
Tobias

No records in main.active table?

I just updated my Muse, made a few changes to my site and saved. While saving, Muse crashed. Now when I try opening the site I receive the message "This Adobe Muse site file cannot be opened. no records in main.active table"? I freaking out here a little.... please help. Thank-you!

Please contact me directly at [email protected] I'd like to thoroughly understand your network and exactly how/where the file was being saved.
During Save As muse creates a file named similarly to the file you're attempting to Save As over with the ending "renamed". If a major error occurs during Save As (as appears to have occurred in this case), this file should still be present next to the file you were attempting to Save As to. This "xxx renamed" file will be your original file. Make a copy of it and rename it to have a .muse file extension.
Please contact me directly so I can better understand what may be unique to your environment to have resulted in this error. Thanks.

(Calculate Result via update rule) vs. (Calculate Result in a query)

Hi,
I got requirements to count number of people who sold the same product category in the same region.
I'm not sure if query could fullfill the following requirements or not.
<b>Example data in the ODS:</b>
for Period: 06/2005
People-A (region-M1) sold product category-C1.
People-A (region-M1) sold product category-C2.
People-B (region-M1) sold product category-C1.
People-B (region-M1) sold product category-C3.
People-C (region-M1) sold product category-C3.
People-D (region-M2) sold product category-C3.
In a report,
- user filter: Month/Year
- user filter: only one People at a time
- it should display all product categories.
I'm thinking to count number of people through an update rule and store the result directly in the ODS. I'm not quite sure whether this is a good idea or not.
Any suggestion would be sincerely appreciated.
Thanks much.
-WJ-

Hi Wachira,
We usually fulfill the "counting" reqts by adding a Counter KF to the InfoProvider (supply a constant of 1 in the transfer rules). Then in the query you can use exception aggregation for calculating different Count By...this is a more flexible approach.
Hope this helps...

Activating SIS structure error while maintaining update rules

Hi Experts
please reply <removed by moderator>
i am trying to activate self defined SIS structure but at the time of creating maintain update rule in transaction MC24 i am getting error
please guide what i am missing
DDIC structure S990 for info structure S990 not active in Data Dictionary
Message no. M2464
Diagnosis
It is not possible to maintain the updating procedure since DDIC structure S990, which belongs to info structure S990, is not active.
The info structure has probably been saved but not generated.
Procedure
The info structure must be generated.
Regards
Abhi
Message was edited by: Manish Kumar

Hi ,
Just check whether update rules has any routines or fomula, or constant.
If so collect that in a request and transport it.
Assign points if it is helpful.
Thanks
Shanba

BW Datasource on an Infoset Query based on 2 DSO Active tables

Hello,
We have created a Datasource in the BW system over an Infoset query (through SQ02) built on 2 DSO tables.
In RSA3, this datasource is working fine - it shows us some data (close to 1000 records).
The issue is when i try and run a infopackage for the datasource.
The request times out and no records are fetched.
I have added all the users to the Infoset user group - so, no issue with the authorization.
IDoc Statuses changes from 53 --> 62 --> 64 --> 50.
The extraction process does not complete - does not get the no. of records sent.
Can anybody point to a probable cause here?
Thank you.

IDoc logs do not say much.
Status Record 53: IDoc was successfully transferred
Status Record 62: IDoc passed to application; Direct call started
Status Record 64: IDoc ready to be transferred to application; No filter, no conversion
Status Record 50: IDoc added
Then, it does not go any further.
We're using the Datasource on the Infoset query because we could not use the traditional BW infoset.
Datsource is used to feed a DSO as we directly could not use anything else (we're trying with an expert routine also).
The issue is that the base DSO tables are huge and querying on them (using SELECT) is taking a very long time.
So, we thought of using an Infoset to create a view and then populatet he data.
In an traditional infoset, we could not specify a condition with a range. So, the infoset query through SQ02.
I have not tried using an APD, but that might be a good option.
Only thing, we'll have to use a Direct DSO - which i am not sure will satisfy our requirement.
Thank you.

Error Message "This adobe Muse site file cannont be opened. no records in main.active table"

Is anyone else getting this message? It crashed just as I tried to save my website in the updated Muse

coolxkid,
You should have a file named MuseLog.txt in your user documents folder.
Please send that file to [email protected] so we can follow up on this problem.

Aperture 3.3 after recent upgrade doesn't show icons in colour and I noticed the adjustments panel seems a bit different from the previous update.

I updated about a week ago an now all the icons are no longer in colour (ie, project, smart album etc) Really liked to see them in colour because it helped me sort more easily. Also, I seem to be missed my quick adjustments panel like auto adjust. I checked the aperture preferences but could not find anyway to correct.
Any suggestions?
Melissa T.

Thanks Frank. Once I posted, I was able to find all the other discussions regarding this. I don't have time to manually change what Apple should have put into preferences. Will manage with it the way it is and send a request to Apple for future updates.
Best regards,
M

Difference between Delta "Change Log" and "Active Table (Without Archive)"?

In BI7.0 environment, we perform our Delta loads (the DTP settings under the Extraction tab, there is a field called Extraction Mode and it's value is selected as "Delta") every day among all our DSOs.
There is a section called "Delta Init. Extraction From..." under the same tab in DTP, there are four radio buttons:
Active Table (With Archive)
Active Table (Without Archive)
Archive (Full Extraction Only)
Change Log
Then what is the difference between "Change Log" and "Active Table (Without Archive)" if both Extraction Mode is "Delta" for two Delta loads?
Thanks!

Hi ,
The new options SP16 has are:(Chk Note 1096771)
Active Table (with Archive)
The data is read from the active table and from the archive or from a near-line storage if one exists. You can choose this option even if there is no active data archiving process yet for the DataStore object.
Active Table (Without Archive)
The data is only read from the active table. If there is data in the archive or in a near-line storage at the time of extraction, this data is not extracted.
Archive (Only Full Extraction)
The data is only read from the archive or from a near-line storage. Data is not extracted from the active table.
Change Log
The data is read from the change log of the DataStore object.
Delta will always be picked from change log table.Only during intialization you can choose between getting data from change log or active table.If you are doing the load first time and are initializzing delta in subsequent data targets, then pulling data from active table will get lesse volume of data then it would have got from change log table....All subsequent deltas will be picked up from the change log. And when we need to reload data into the data target (which would be a full load) - we use active table.
From change log : you can take below ones as targets
1) Cube 2) DSO with Addition as the update for the Keyfigures
From Active table: you can take below ones as targets
1) Cube ,if and only if, the records are never changes in the source once after creation
2) DSO with Addition as the update for the Keyfigures ,if and only if, the records are never changes in the source once after creation
3) DSO with Overwrite as the update for the Keyfigures ( incase deletions is not happening in the source system)
Pls check this link
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/47/e8c56ecd313c86e10000000a42189c/frameset.htm
Regards,
CSM Reddy

Activation is changed from single lookups to to package fetch of active tab

I was going through some of the Performance enhancements in BW 7.3. Could someone please explain what do the following mean?
1. DSO Activation is changed from single lookups to package fetch of active table
2. Optimized delta load for master data due to package fetch instead of single look-ups
Thanks & Regards
Dharmendra

Just thought I'd post the resolution:
1) Simply changing the Disc Media Type in the ProjectData folder does nothing. The dual-layer setting causes it to change from a value of 4 to 8 (guess that's no surprise), but iDVD still treats the drive as a single-layer drive and so you can't create a disc image based on a dual-layer disc.
2) Turns out the folks from MCE sent along, after requesting it, a patch to enable dual-layer support in iDVD. From what I can tell from the .command file, it looks like it's probably just the HardMac.com hack repackaged for convenience. The don't offer it for download, but if you call or email them, they'll send it.
Thanks again for your advice.

Update rule from one Cube to another

Hello Gurus!
Here is the situation :-
We have a IC ZCube1. This cube contains order data at schedule line level. It contians an IO for each Hold Status (in all 10 ) . IO has value 'X' if it is active else blank. 1 order line item can have multiple holds.
We need a aging report that should show how long particular line is on a Hold .
Date of change of hold status is not in the cube ZCube1, it is in another ODS. We have created new cube(ZCube2) that will have Orderitem, Line#, DOC#...etc(as key field) and an IO for Hold status (here we have only one IO to hold all status code) and data of change of hold status (we will populate it from ODS ) .
We have create start routine in ZCube2 that filter out order lines with no active Hold status. Also in this start routine we have logic to create 1 row for each hold status and store it in internal table(ITAB1).
Problem :
Not able to understand how to proceed in update rule to insert multiple rows from ITAB1 into ZCube2.
We can copy ITAB1 to ITAB2 and read it with Key fields. After this we have ITAB2 with multiple Hold status codes with same order item.
Problem here is how do I assing multiple rows from ITAB2 in update rule to get multiple line item in ZCube2.
Any thought or input to above said will be very helpful.
Thanks,
Murtuza.

Hi Srinivas,
I did some change , till earlier post I was trying to figure out how to Move source DP values to internal table.
Eventually what I need is to Break each order line from source pacakge which contians multiple holds on same line into 1 orderline with only 1 hold status .
e.g for a orderline if there are 3 hold Source DP will return 1 row . After I execute below code is start routine Source DP will have 3 order line everything same but hold status . I have done changes to the code in previous post and I am able to achieve what I need , but not sure this is efficient way to do ...
Please advice .
LOOP AT SOURCE_PACKAGE ASSIGNING <SOURCE_FIELDS>.
MOVE-CORRESPONDING <SOURCE_FIELDS> TO wa_ITAB_DP.
      IF <SOURCE_FIELDS>-/BIC/ZCSTATDM EQ 'X'.
        wa_ITAB_DP-/BIC/ZCSTATDM = 'X'.
        wa_ITAB_DP-/BIC/ZCSTATFH = ''.
        wa_ITAB_DP-/BIC/ZCSTATCC = ''.
        wa_ITAB_DP-/BIC/ZCSTATSC = ''.
        wa_ITAB_DP-/BIC/ZCSTATSP = ''.
        wa_ITAB_DP-/BIC/ZCSTATFA = ''.
        wa_ITAB_DP-/BIC/ZCSTATFV = ''.
        wa_ITAB_DP-/BIC/ZCSTATNF = ''.
        wa_ITAB_DP-/BIC/ZCSTATPV = ''.
        wa_ITAB_DP-/BIC/ZCSTATIP = ''.
        APPEND wa_ITAB_DP to ITAB_DP.
      ENDIF.
      IF <SOURCE_FIELDS>-/BIC/ZCSTATFH EQ 'X'.
        wa_ITAB_DP-/BIC/ZCSTATDM = ''.
        wa_ITAB_DP-/BIC/ZCSTATFH = 'X'.
        wa_ITAB_DP-/BIC/ZCSTATCC = ''.
        wa_ITAB_DP-/BIC/ZCSTATSC = ''.
        wa_ITAB_DP-/BIC/ZCSTATSP = ''.
        wa_ITAB_DP-/BIC/ZCSTATFA = ''.
        wa_ITAB_DP-/BIC/ZCSTATFV = ''.
        wa_ITAB_DP-/BIC/ZCSTATNF = ''.
        wa_ITAB_DP-/BIC/ZCSTATPV = ''.
        wa_ITAB_DP-/BIC/ZCSTATIP = ''.
        APPEND wa_ITAB_DP to ITAB_DP.
      ENDIF.
      IF <SOURCE_FIELDS>-/BIC/ZCSTATCC EQ 'X'.
        wa_ITAB_DP-/BIC/ZCSTATDM = ''.
        wa_ITAB_DP-/BIC/ZCSTATFH = ''.
        wa_ITAB_DP-/BIC/ZCSTATCC = 'X'.
        wa_ITAB_DP-/BIC/ZCSTATSC = ''.
        wa_ITAB_DP-/BIC/ZCSTATSP = ''.
        wa_ITAB_DP-/BIC/ZCSTATFA = ''.
        wa_ITAB_DP-/BIC/ZCSTATFV = ''.
        wa_ITAB_DP-/BIC/ZCSTATNF = ''.
        wa_ITAB_DP-/BIC/ZCSTATPV = ''.
        wa_ITAB_DP-/BIC/ZCSTATIP = ''.
        APPEND wa_ITAB_DP to ITAB_DP.
      ENDIF.
      IF <SOURCE_FIELDS>-/BIC/ZCSTATSC EQ 'X'.
        wa_ITAB_DP-/BIC/ZCSTATDM = ''.
        wa_ITAB_DP-/BIC/ZCSTATFH = ''.
        wa_ITAB_DP-/BIC/ZCSTATCC = ''.
        wa_ITAB_DP-/BIC/ZCSTATSC = 'X'.
        wa_ITAB_DP-/BIC/ZCSTATSP = ''.
        wa_ITAB_DP-/BIC/ZCSTATFA = ''.
        wa_ITAB_DP-/BIC/ZCSTATFV = ''.
        wa_ITAB_DP-/BIC/ZCSTATNF = ''.
        wa_ITAB_DP-/BIC/ZCSTATPV = ''.
        wa_ITAB_DP-/BIC/ZCSTATIP = ''.
        APPEND wa_ITAB_DP to ITAB_DP.
      ENDIF.
      IF <SOURCE_FIELDS>-/BIC/ZCSTATSP EQ 'X'.
        wa_ITAB_DP-/BIC/ZCSTATDM = ''.
        wa_ITAB_DP-/BIC/ZCSTATFH = ''.
        wa_ITAB_DP-/BIC/ZCSTATCC = ''.
        wa_ITAB_DP-/BIC/ZCSTATSC = ''.
        wa_ITAB_DP-/BIC/ZCSTATSP = 'X'.
        wa_ITAB_DP-/BIC/ZCSTATFA = ''.
        wa_ITAB_DP-/BIC/ZCSTATFV = ''.
        wa_ITAB_DP-/BIC/ZCSTATNF = ''.
        wa_ITAB_DP-/BIC/ZCSTATPV = ''.
        wa_ITAB_DP-/BIC/ZCSTATIP = ''.
        APPEND wa_ITAB_DP to ITAB_DP.
      ENDIF.
      IF <SOURCE_FIELDS>-/BIC/ZCSTATFA EQ 'X'.
        wa_ITAB_DP-/BIC/ZCSTATDM = ''.
        wa_ITAB_DP-/BIC/ZCSTATFH = ''.
        wa_ITAB_DP-/BIC/ZCSTATCC = ''.
        wa_ITAB_DP-/BIC/ZCSTATSC = ''.
        wa_ITAB_DP-/BIC/ZCSTATSP = ''.
        wa_ITAB_DP-/BIC/ZCSTATFA = 'X'.
        wa_ITAB_DP-/BIC/ZCSTATFV = ''.
        wa_ITAB_DP-/BIC/ZCSTATNF = ''.
        wa_ITAB_DP-/BIC/ZCSTATPV = ''.
        wa_ITAB_DP-/BIC/ZCSTATIP = ''.
        APPEND wa_ITAB_DP to ITAB_DP.
      ENDIF.
      IF <SOURCE_FIELDS>-/BIC/ZCSTATFV EQ 'X'.
        wa_ITAB_DP-/BIC/ZCSTATDM = ''.
        wa_ITAB_DP-/BIC/ZCSTATFH = ''.
        wa_ITAB_DP-/BIC/ZCSTATCC = ''.
        wa_ITAB_DP-/BIC/ZCSTATSC = ''.
        wa_ITAB_DP-/BIC/ZCSTATSP = ''.
        wa_ITAB_DP-/BIC/ZCSTATFA = ''.
        wa_ITAB_DP-/BIC/ZCSTATFV = 'X'.
        wa_ITAB_DP-/BIC/ZCSTATNF = ''.
        wa_ITAB_DP-/BIC/ZCSTATPV = ''.
        wa_ITAB_DP-/BIC/ZCSTATIP = ''.
        APPEND wa_ITAB_DP to ITAB_DP.
      ENDIF.
      IF <SOURCE_FIELDS>-/BIC/ZCSTATNF EQ 'X'.
        wa_ITAB_DP-/BIC/ZCSTATDM = ''.
        wa_ITAB_DP-/BIC/ZCSTATFH = ''.
        wa_ITAB_DP-/BIC/ZCSTATCC = ''.
        wa_ITAB_DP-/BIC/ZCSTATSC = ''.
        wa_ITAB_DP-/BIC/ZCSTATSP = ''.
        wa_ITAB_DP-/BIC/ZCSTATFA = ''.
        wa_ITAB_DP-/BIC/ZCSTATFV = ''.
        wa_ITAB_DP-/BIC/ZCSTATNF = 'X'.
        wa_ITAB_DP-/BIC/ZCSTATPV = ''.
        wa_ITAB_DP-/BIC/ZCSTATIP = ''.
        APPEND wa_ITAB_DP to ITAB_DP.
     ENDIF.
     IF <SOURCE_FIELDS>-/BIC/ZCSTATPV EQ 'X'.
        wa_ITAB_DP-/BIC/ZCSTATDM = ''.
        wa_ITAB_DP-/BIC/ZCSTATFH = ''.
        wa_ITAB_DP-/BIC/ZCSTATCC = ''.
        wa_ITAB_DP-/BIC/ZCSTATSC = ''.
        wa_ITAB_DP-/BIC/ZCSTATSP = ''.
        wa_ITAB_DP-/BIC/ZCSTATFA = ''.
        wa_ITAB_DP-/BIC/ZCSTATFV = ''.
        wa_ITAB_DP-/BIC/ZCSTATNF = ''.
        wa_ITAB_DP-/BIC/ZCSTATPV = 'X'.
        wa_ITAB_DP-/BIC/ZCSTATIP = ''.
        APPEND wa_ITAB_DP to ITAB_DP.
      ENDIF.
    IF <SOURCE_FIELDS>-/BIC/ZCSTATIP EQ 'X'.
        wa_ITAB_DP-/BIC/ZCSTATDM = ''.
        wa_ITAB_DP-/BIC/ZCSTATFH = ''.
        wa_ITAB_DP-/BIC/ZCSTATCC = ''.
        wa_ITAB_DP-/BIC/ZCSTATSC = ''.
        wa_ITAB_DP-/BIC/ZCSTATSP = ''.
        wa_ITAB_DP-/BIC/ZCSTATFA = ''.
        wa_ITAB_DP-/BIC/ZCSTATFV = ''.
        wa_ITAB_DP-/BIC/ZCSTATNF = ''.
        wa_ITAB_DP-/BIC/ZCSTATPV = ''.
        wa_ITAB_DP-/BIC/ZCSTATIP = 'X'.
        APPEND wa_ITAB_DP to ITAB_DP.
      ENDIF.
     CLEAR wa_ITAB_DP.
ENDLOOP.
SOURCE_PACKAGE[] = ITAB_DP[] .

Error when activating update rule after transporting to QA

Hi,
When we transport Info cubes and update rules along with Process chains. There are the following errors in Transport request(XXXXXXXX).
1. Error when activating update rule 22HSFD3ZMALU46LS0R8PRF2MW
IC=ZSDPCXY2 IS=2LIS_11_VAITM error when checking the update rules
2. Error when activating update rule 7NT4WIDPDCN2ERFDRXIGH95PM
IC=ZSDPCXY2 IS=2LIS_12_VCHDR error when checking the update rules
and etc.
Then we activated and saved all the erroneous update rules in another tranport request(YYYYYYYY) and again we transported alongwith the previous transport request(XXXXXXXX).
The last request(YYYYYYYY)was successfully tranported and still there are same errors in TR(XXXXXXXX).
Quick answers will be highly appreciated.
Regards,
Vijay

Hi Vijay,
Next time you would have transport only (YYYYYYYY). Transport Request (XXXXXXX) was not required to be moved.
Normally Update Rule gets deactivated in QA when any changes to the CUbe/ODS are moved.
Thus either you can transport transport request for only active update rule to QA or activate your UR directly in QA system in case you have authorization to do that.
Regards,
Rohini

ODS update rule activation

Hi,
Can some help me out for ODS (0SD_O03) update rules activation,I am not finding any thread related to this issue.
Please donot suggest for RSAU_UPDR_REACTIVATE_ALL prg.It is for only Infocube update rules activation
Thanks,
Praveen

Hi Praveen,
RSAU_UPDR_REACTIVATE_ALL program is not only for InfoCubes update rules activation. You can activate any update rule through this program.
In program
S_UPDID give updaterule technical name such as(CONA85AOASV0HQ3B8I6E2EBJM)
S_TARGET give 0SD_O03
S_SOURCE give infosource name

Error while activating data from new table of DSO to active table

HI,
while activating data from new table of DSO to active table i am getting
error message as "Error occurred while deciding partition number".
Plz any idea hoe to resolve this one.
thanks & regards
KPS MOORTHY

Hi
You are trying to update/upload the Records which are already been there in the DSO Active Data Table which has the partition.
Try to see the Record Nos already been activated and update/upload with selective, if possible.
You can trace the changes at Change log table for the same.
Hope it helps
Edited by: Aduri on Jan 21, 2009 10:38 AM

Error during activation of DSO - Activation of M records from DataStore obj

Hi All,
Below is the error i am getting while activating the DSO, Even though similar post on this topic, solution not mentioned, any solution greatly appreciable.
When -
During Activation of DSO
State of DSO -
Request become "RED", It is available for reporting, some records in Active table, some in new table and some in new table.
Job Log -
Error when inserting the data record for data package
Process 000105 returned with errors
Error when inserting the data record for data package
Process 000106 returned with errors
Process 000107 returned with errors
Data pkgs 000001; Added records 1-; Changed records 0; Deleted records 0
Log for activation request ODSR_4GXKRYHMY97R9U62M6U52XXXY data package 000001...000001
Errors occured when carrying out activation
Analyze errors and activate again, if necessary
Activation of M records from DataStore object Z_DSPO terminated
Report RSODSACT1 ended with errors
Job cancelled after system exception ERROR_MESSAGE
Detail log -
Error when inserting the data record for data package 106
Message no. RSODSO_PROCESSING002
Diagnosis
Failed to store data records persistently. Possible causes are:
You tried to save a record that is already stored in the database.
This error only occurs with DataStore objects with option "Unique Data Records".
A unique index was created for the table of active data.
You can check this in the Data Warehousing Workbench by choosing "Display" for the DataStore object and opening the "Indexes" folder.
There is a technical problem on the database.
Thanks,

HI PT,
I am also getting the same error like i have loaded the data into DSO and tried to activate the init request but it has become red and checked in log found that there are some SID Generation errors so please give me the step by step solution.
SID Generation
Data Package 000056
Data Package 000064.
Thanks in advance,
Jay

Record in DSO Active Table different from result of Update Rule Simulation

Similar Messages

Maybe you are looking for