DSO activation error due to 0WBS_ELEMT

[paddyw]

Hi   We are on 7.3 BW now.We got following error while running process chain.Error happened while activating DSO.   "Error when assigning SID:Action VAL_SID_CONVERT infoobject 0WBS_ELEMT Characteristic value  xxxxx of charcateristic 0WBS_ELEMT is not WBSEL converted Activation of records from DSO terminated"

I have done a lot of search online but no solution found yet. Note 1654346 is not relevant for this case.

Any idea how to proceed with this problem?   Thanks a lot.

[former_member182516 · Accepted solution]

Hi Paddy,

We had faced the same issue after BW7.3 upgrade. We had contacted SAP ... here is the reply from SAP for the above issue.

--> Write a field level routine ...

CALL FUNCTION 'CONVERSION_EXIT_WBSEL_INPUT'

     EXPORTING INPUT = SOURCE_FIELDS-POSID

     IMPORTING OUTPUT = RESULT.

Let me know if you need more help on this...

We had faced one more issue after implementing the above field level routine... DTP was consuming more time when compared to earlier.

Just keep in mind.. you need to create index on table /BI0/PWBS_ELEMT consisting of the fields OBJVERS, WBS_ELM_EX & WBS_ELEMT.

Create index only if you face the same issue while loading.

Regards,

KP

[former_member638921 · Accepted solution]

This message was moderated.

[Former Member]

Hi Jin,

This error is due to conversion happening in the WBS Element field. check the format in below link.

http://help.sap.com/erp2005_ehp_04/helpdata/en/d7/22417391807646910d01ee241628e1/content.htm

There should be some characters which does not match this format.

May be checking more regarding the error message will help you to find extract record causing issue.

Regards,

Ganesh

[colm_boyle]

Hi Paddy,

The note 1786451 might fit this problem, it is a similar issue for
0WBS_ELEMT.
See Symptom:

Characteristic value '****' of characteristic **** is not ****-converted
Message no. BRAIN068

Solution: You need to make sure that the source and target both have the
same conversion routine maintained. This is required to make sure that
the correct data is getting loaded in the Master Data tables.

It is possible that the datasource loading the value for 0WBS_ELEMT is
in external format and is not converted during the loading process. You
could include WBSEL as a conversion routine in the datasource.

Another solution is to use conversion routine
CONVERSION_EXIT_WBSEL_INPUT in the transformation
to convert the values to the correct internal format for infoobject
0WBS_ELEMT.

7.x systems allow the incorrect internal format.
This leads to inconsistent master data.

So in 730 a plausibility check has been defined which is more strict
towards the incorrect internal format values. That is the reason why the
activation process cancels only after upgared to 730.

I hope this helps,

Colm

[Former Member]

BW 7.3 seems to have a more stringent check on conversion exits than pervious version. To fix this issue, use CONVERSION_EXIT_ABPSP_OUTPUT. In my particular case, the conversion exit on the source field in the datasource was ABPSN while the conversion exit on 0WBS_ELEMT was WBSEL. Add this code to your transformation and reload data, it will resolve the issue:

* Call conversion function to fix error after 7.3 upgrade on

* ABPSN to WBSEL; "Error when assigning SID:

* Action VAL_SID_CONVERT InfoObject 0WBS_ELEMT"

* Message no. RSDRO302

  call function 'CONVERSION_EXIT_ABPSP_OUTPUT'

      exporting

        input = SOURCE_FIELDS-<your_source_field>

      importing

        output = RESULT.

[former_member182470]

Look at the last suggestion. This may help you. Hope you have loaded the master data for your infoobject.

http://scn.sap.com/thread/3196382

[Former Member]

I have faced a similar issue .

In my case there were invalid records of WBS element in PSA .

In the manage tab of DSO -> request tab , next the load monitor , there is a column named 'logs for DSO-request processing . Click on that column , it will show in which data package error has occured and reason for the error .

Find the erroneous record in PSA and correct it and reload the data .

[Former Member]

Hi Jin

It would be great if can share once you find the solution. We are also facing similar issue everyday for our production load. The failure is only for one WBS and not all the records. Not sure what creating the issue. Apart from WBS we are facing same issue for 0MATERIAL info object.

Thanks

Anjali

[paddyw]

I still haven't find the way to solve this issue. It makes me crazy..

[former_member182516]

Hi Paddy,

We had faced the same issue after BW7.3 upgrade. We had contacted SAP ... here is the reply from SAP for the above issue.

--> Write a field level routine ...

CALL FUNCTION 'CONVERSION_EXIT_WBSEL_INPUT'

     EXPORTING INPUT = SOURCE_FIELDS-POSID

     IMPORTING OUTPUT = RESULT.

Let me know if you need more help on this...

We had faced one more issue after implementing the above field level routine... DTP was consuming more time when compared to earlier.

Just keep in mind.. you need to create index on table /BI0/PWBS_ELEMT consisting of the fields OBJVERS, WBS_ELM_EX & WBS_ELEMT.

Create index only if you face the same issue while loading.

Regards,

KP