Error while activating DSO

Hi,
I am getting an error while activating the DSO. I am able to load the data but this occurs when I try to activate the data. I get the follwing error message
"Value "09020751987.44 " from characteristic 0REF_DOC_NO contains an error at position 15
Message no. BRAIN290
Diagnosis
Characters that have a hexadecimal display between HEX00 and HEX1F are not permitted in characteristic values. The character at position 15 is one of these characters. The value is therefore not permitted.
Note that these characters cannot be displayed and are therefore displayed as '#'. The actual character '#' has the hexadecimal display HEX23.
Procedure
Check the origin of the characteristic value. If possible, change the characteristic value in the source.
Incorrect source text in update routines and transfer routines can also cause this problem."
Any thoughts how I should correct/

Hi Tanu,
this is an error in the data loaded. If you have used PSA, then try searching for the packet containing this record using the change log table, by request id. (This step is to precisely find the position of the record in PSA).
Now delete the request from the DSO and correct the data in PSA. The issue could be a tab or a space in the reference document feild and then save the data. Reconstruct this packet from PSA and then try activating.
Subsequently let the data team/ user know about the correction in the source system as well, in order to avoid any future failures.
This should correct the issue.
regards,
Naveen.A

Similar Messages

Error while Activating DSO Data

Hello
I am having a problem, I am getting an Error while activating DSO Data, Data is loaded in DSO succefully but can not be activated with this error
"Activation of M records from DataStore object 0FIAR_O03 terminated"
Thanks

Hi,
The activation would have failed due to varies reasons..
It would be a short dump,check in ST22.
check the job log in SM37 for better understanding of the issue.
Have you loaded the respective master data?
if it is a transaction data load,then the SID is checked at the time of activation and not during loading.
So if the master data is not loaded then the activation would fail.
It can also be due to the system performance at that moment.
Even if the data volume is huge ,there are chances of the activation failing..
Try repeating the activation once again.it might succeed..
Else check the logs to understand the actual issue.

Hexadecimal Error while activating DSO

Hello Experts,
I'm getting following error while activating DSO. I tried ALL_CAPITAL, ALL_CAPITAL_HEXADECIMAL in RSKC. still i'm facing this problem anyone can suggest anything. Iam using BW3.x flow
Value "CC-5012 TRYPSIN/EDTA SOLUTION 100ML" (HEX 430043002D0035003000310032000A00540052005900500053) of characteristic 0CRM_ITDESC contains an error at position 8
Message no. BRAIN290
Diagnosis
Characters that have a hexadecimal display between HEX00 and HEX1F are not permitted in characteristic values. The character at position 8 is one of these characters. The value is therefore not permitted.
Note that these characters cannot be displayed and are therefore displayed as '#'. The actual character '#' has the hexadecimal display HEX23.
Procedure
Check the origin of the characteristic value. If possible, change the characteristic value in the source.
Incorrect source text in update routines and transfer routines can also cause this problem.
Thanks
Ajay.D

Hi Ajay,
There are invalid characters at the specified position. Now you ahve 2 options:
1. Either edit the PSA manually and replace this invalid character
2. Use the Funvtion Module 'RSKC_CHAVL_CHECK' . Pass the data to it & get the invalid char replace it with space. This can be called in the filed level routine if the effected info object is identified .
Check out these threads:
Re: Problem with Characters that have a hexadecimal display between HEX00
Re: Invalid Characters issue
Regards
Raj

Error while activating DSO after loading from another DSO..Production issue

Hello Gurus,
I got an error while activating DSO2 after loading from another DSO1.
DSO1 load and activation was sucessful but while loading from DSO1 to DSO2 load was fine but got error while activating...
>Error when assigning SID: Action VAL_SID_CONVERT table ZWEEK_NUM
>Value u201809u2019 of characteristic ZWEEK_NUM is not a number with 000004 spaces
this theard was posted after searching for related post in SDN.
and i tried Function Module RSODS_CHECK_RSODSACTUPDTYPE but it is not available .. but I used this in BW 3.10u2026..
is their any similar Function Module in BI 7.0 please advice.
We are using SAP NetWeaver BI 7.0
Release- 700 Service level- 017
Thanks in advance
Sandy

sloved the issue......
it was due to wrong data for the related field...
it must be "0009 "
Thanks for ur support. closing the ticket
Regards
Sandy

SQL error while activating DSO and loading Mater Data

Hello Experts,
we are having process chains which include process activating DSO and loading to Master data,
while executing achai, we are getting error:
An error occurred during confirmation of process 000008. See long text
Message no. RSODSO_PROCESSING024
Diagnosis
Note the detailed system message:
An SQL error occurred when executing Native SQL.
when i go to T-Code: ST22
the diagnosis is below:
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Date and Time          20.05.2010 22:18:02
What happened?
     The database system detected a deadlock and avoided it by rolling back
     your transaction.
What can you do?
     If possible (and necessary), repeat the last database transaction in the
      hope that locking the object will not result in another deadlock.
     Note which actions and input led to the error.
     For further help in handling the problem, contact your SAP administrator
     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.
     Note which actions and input led to the error.
     For further help in handling the problem, contact your SAP administrator
     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.
Could you please help me out how can i deal with this issue, .
Regards
Sinu Reddy

it seems that the target you're loading to is already locked by another load...if it concerns a master data is also possible that the master data is locked by a change run. check your scheduling and make sure you don't load the same target at the same moment...
M.

Error while activating DSO ....date is not possible....

Hi all,
While activating the DSO ,I am getting the following error: Value '20022009' of characteristic 0DATE is not possible
In FEB 20/02/2009 is possible ...but why system giveing this message...?
Any suggessions...on this..
Thanks....Bk
Edited by: BK BI on Feb 24, 2009 9:39 AM

Hi BK,
Looks like in your case 20 is being considered as month which is obviously invalid hence no SID could be generated for 0calday and hence the DSO fails when activation.
Now as Daya and anil mention you could change the date to format yyyymmdd and try reloading the file.
The general principle would be go to menu settings ---> status and check the logged on date ...the format being shown to you is the format you can try loading in.
Or go to System --- > User profile -
> Own data --->defaults tab .... check the data format there and enter the value in that format in your file..
Hope it helps,
Regards,
Sunmit.

Invalid character error while activating DSO - Please help

Hi experts,
I'm getting invalid hex character error when loading a text infoobject in my DSO. Repairing data records in the PSA is not an option. Changing the data in the source system is also not an option. I've tried many of the methods suggested in other threads, but am unable to get it working (ABAP code, "ALL_CAPITAL" etc). We are on an unicode system.
Can someone provide some clean code to eliminate the illegal hex characters (00-1f) in my transfer rule routine. Basically, replace the illegal hex characters with space or an acceptable character.
Many thanks,
Anita S.

Hi,
I have used the below code for removing all unwanted chars from 0MATERIAL, that worked fine. You can modify it for ur need.
CONSTANTS:
       G_ALLOWED_CHAR(58) TYPE C VALUE
         ' !"%&''()*+,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ'.
    data : E_ALLOWED_CHAR(58).
RESULT = SOURCE_FIELDS-MATNR.
    SHIFT RESULT RIGHT DELETING TRAILING SPACE.
    SHIFT RESULT LEFT DELETING LEADING SPACE.
    TRANSLATE RESULT TO upper case.
*RESULT = comm_structure-/BIC/ZCONTRTD.
    while RESULT ca '#'.
      RESULT+sy-fdpos(1) = ' '.
    endwhile.
    if RESULT(1) = '!'.
      RESULT(1) = ' '.
    endif.
    do.
      if not RESULT co g_allowed_char.
        shift RESULT+sy-fdpos left.
      else.
        exit.
      endif.
    enddo.
Thanks
dipika

Error while activating DSO req-reg

Hi Experts,
I was trying to load data from a flat file. I got my data till PSA level. I have executed the DTP from datasource to DSO and when i am trying to activate the request i got request status red and error message says "Request is already (partially) activated; no further QM action possible". all records are transfered and my request is available for reporting. When i go to monitor there is no red symbol in any step but the overall status is red.
I searched in the forum for the same error message and i got that the data is transfered already. But i am not able to see the data in DSO through 'display data'. Plese let me know what is the reason for the red status and guide me how to proceed further.
Your help would be highly appreciated.
Thanks in advance.
Nikhil Joy

Hi Nikhil,
When you activate the data in DSO manually, job will create with your username. Job name will be ODSA_****
Please check the job log, you will get the details.
This might be due to non-availability of SID's or some duplicate records.
Please check the job log and post here
Regards,
Venkatesh

Process Chain Error while activating DSO

Hello.
1st, let me say that I'm pretty new to BI so I apologize for the stupid question :-S
I have a process chain (Warehouse Mangement) that failed this morning at the DSO data activation step. It's simply because some entries have lowercase value in a field that should not. I know how easy this is to fix in the transformation but my problem is more on how to fix the actual fail of the process chain. Can I edit the "non-activated" data in the DSO (only 2-3 records that I need to put in uppercase) and "repair" my process chain or should I proceed another way?
Thanks for your help.

Hi John.
If guess your Process Chain process ended in "Red color". Once you fix the error you can try to make "right-click" on the process with error and select "Repair". If this operation is "supported" by the activation process you won't have error.
But I really believe that you'll have to erase the request and launch the complete process (o set of related processes) once again. It's possible that the data you want its already in the NEW-DATA table of your ODS.
This tables is the following. /BIC/A<your ods tech-name>40
Hope it helps
gdmon.-

Getting a sid's generation error while activating DSO

Dear All,
We are created a standard dso on top of generic data source. This data source is created on top CDHDR and CDPOS tables through function module.
While acting the DSO , We are getting a sid generation error.
Please let me know the process to resolve the issue or tell me any other alternative solution is available to overcome this situation.
Thanks
Regards,
Sai.K

Dear All,
Thanks for your prompt response and please find the below attachment.Here , the info object fetches some hexa decimal values due to that it got failed.
Please let me know solution to overcome the this error.
Thanks
Regards,
Sai.k

Authorization error while activating DSO

Hi Gurus,
When I am trying to Activate DSO, it is throwing the following error.. Can anyone let me know what type of Authorizzation object should I give to resolve this issue..
You do not have authorization for the DWB object
Message no. RSM831
CAUSE&
You do not have authorization for object 'SOURCESYS' in the Data Warehousing Workbench.
System Response
The current activity was terminated.
Procedure
You require authorization for authorization object Data Warehousing Workbench - Object with Data Warehousing Workbench object 'SOURCESYS' and activity '03'.
Thanks in advance

Hi,
Try activating again and if you get the error again then without going back to any other screen directly go to /NSU53 tcode.
Expand all the nodes and see if you get any object name uder red color background. If you get some object name then you basically need that object assigned value '03'.
Let me know if you are able to solve it.
Regards,
Anup

Error in PC While Activating DSO

Hi All,
we are getting error while activating the DSO in PC and getting below error message:
Error when assigning SID: Action VAL_SID_CONVERT, InfoObject 0PART_CCTR.
Value '1000rsc us' (hex. '3100300030003000720073006300200075007300') of characteristic 0COSTCENTER
We took reference character 0COSTCENTER for 0PART_CCTR.
Have checked in PSA level there is rsc us value loaded today, changed it to UPPERCASE to RSC US and ran the load again but again failed and showing same error.
Thanks in advance,
Teena

Hi
Value '1000rsc us' (hex. '3100300030003000720073006300200075007300') of characteristic 0COSTCENTER
contains invalid characters
Looks like there is a special character in the info object 0PART_CCTR.
Please follow the below steps:
1.First check what you have given in t-code RSKC or check
the table RSALLOWEDCHAR.
Try giving CAPITAL_ALL_PLUS_HEX.
Then delete the data and try reloading and activating.
Regards
Raj Rai
Edited by: Raj Rai on Apr 26, 2011 2:01 PM

Error While Activating the CO-PA DSO

Hi Friends
As i am new to CO-PA . I am facing problems while activating DSO.
Error : Short dump has not been completely stored (too big)
What happened?
Error in the ABAP Application Program
The current ABAP program "GPDI1O4GBC7CYZNYW1LK35LKP6J" had to be terminated
because it has
come across a statement that unfortunately cannot be executed.
Error analysis :
    You attempted to assign a field to a typed field symbol,
    but the field does not have the required type.
Please Suggest me
Thanks
Gowtham

Hi Fathima
Here is the screen description
Short text
    Type conflict with ASSIGN in program "GPDI1O4GBC7CYZNYW1LK35LKP6J".
What happened?
    Error in the ABAP Application Program
    The current ABAP program "GPDI1O4GBC7CYZNYW1LK35LKP6J" had to be terminated
     because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    You attempted to assign a field to a typed field symbol,
    but the field does not have the required type.
Trigger Location of Runtime Error
    Program                                 GPDI1O4GBC7CYZNYW1LK35LKP6J
    Include                                 GPDI1O4GBC7CYZNYW1LK35LKP6J
    Row                                     886
    Module type                             (METHOD)
    Module Name                             EXECUTE
Thanks
Gowtham

Error while Activating the Standard DSO

Hi,
I am getting the below error while Activating the Standard DSO.
Characteristic 0DPM_DCAS__0CSM_SPRO: DS object 0DPM_DCAS__0CSM_STAT (master data check) does not exist
I tried searching the forum , but didnt find any answer.
Any suggestions are welcome.
Thank you,
Adhvi.

Hi,
Are you getting the error while trying to activate the DSO data after loading or just while trying to activate the DSO itself.
If it is during the activation of a request,then please check if you have loaded some data in the DSO which doesnt have the corresponding Master Data loaded.For preventing this, you can check in Infopackage/DTP -"No Update without Master Data".
You can also go into RSRV and perform elementary tests for the DSO and check the SID table consistency.
Thanks,
Divya.

Invalid character error while activating data in DSO.

Hi Experts,
We are facing an issue with presence of invalid characters in data from source. This throws SID generation error while activating data in DSO. Long text of error shows like this:
"Value " ĠĠĠĠĠĠĠĠĠĠĠĠĠĠĠ" (HEX 000D0120012001200120012001200120012001200120012001) of characteristic contains an error at position 1"
Also we've tried adding the character " Ġ " in TCode RSKC, but it then shows as a rectangle box which I'm not able to copy manually(looks like a blank space or something of that sort).
We've tried implementing routine to remove special characters while loading data, but still it fails. Due to huge amounts of data, its practically unfeasible to check each record manually.
Any useful suggestions will be acknowledged.
regards,
anoop

Hi,
We are using following code for the same purpose. U can use it at infoobject level mapping. This code will check value of each character in the data coming, whether it is in RSKC, if it is a allowed one then it will be passed as it is. Otherwise it will replace that character by space.
    data: l_d_length like sy-index,
             l_d_char type c,
             l_d_index type sy-index,
          l oopx like sy-tabix.
    data : xinfobj(30) type c value 'RABC'.    -> this is ur infoobject name
    clear : result.
    call function 'CONVERSION_EXIT_ALPHA_INPUT'
      exporting
        input = tran_strucutre-XYZ     -> object name in ur structure
      importing
        output = result.
    l_d_length = strlen( result ).
    do l_d_length times.
      l_d_index = sy-index - 1.
      l_d_char = result+l_d_index(1).
      call function 'RSKC_CHAVL_OF_IOBJ_CHECK'
        exporting
          i_chavl                 = l_d_char
          i_iobjnm                = xinfobj
    I_S_COB_PRO             =
    I_T_COB_PRO_CMP         =
       exceptions
         chavl_not_allowed       = 1
         others                  = 2
      if sy-subrc <> 0.
        result+l_d_index(1) = ' '.
      endif.
    enddo.
Regards;
Jitendra

Error while activating DSO

Similar Messages

Maybe you are looking for