cancel
Showing results for 
Search instead for 
Did you mean: 

Activation failing in DSO

Former Member
0 Kudos

Hi Experts,

From R/3 one of the field ZTEST is coming with value MV37906   000409677, #ABC XYZ. This is failing during activation in dso in Prod system. But, this is successful in Development and Sandbox system. Issue is giving due to #. My question is that when it is successful in Dvelopment and Sandbox then why failing in Prod system.

Please suggest.

Regards,

Prakash

Accepted Solutions (0)

Answers (5)

Answers (5)

former_member182343
Active Contributor
0 Kudos

Hi,

Do the following changes in EV and transport again to Prod by adding following code at Transformation level field routine. Because Error stack DTP functionality will not support for DSO, better to go for this option.

DATA A TYPE /BIC/OIA_ADDLINE.

DATA: L_LEN TYPE I,

      L_TIME TYPE I.

MOVE SOURCE_FIELDS-LOCAT TO A.

TRANSLATE A TO UPPER CASE.

L_LEN = STRLEN( A ).

DO L_LEN TIMES.

  IF  A+L_TIME(1) CN

    ',<>?/\:;"''ABCDEFGHI JKLMNOPQRSTUVWXYZ!%^&*()__+=1234567890'.

    A+L_TIME(1) = '~'.

    ENDIF.

     L_TIME =  L_TIME + 1.

     ENDDO.

     REPLACE ALL OCCURRENCES OF '~' IN A WITH SPACE.

     CONDENSE A.

     RESULT = A.

Regards,

rvc

mohd_abdullah
Contributor
0 Kudos

Hi

Use the following code in the routine(field level) for the field ZTEST

replace ALL OCCURRENCES OF '#' in RESULT with ' '. (This will replace the occurence of # with Space ..Instead of space you can use any desired value )


Hope this helps

Regards .

former_member188080
Active Contributor
0 Kudos

Hi,

I think u need to remove # and space both..

Thanks and regards

Kiran

Former Member
0 Kudos

Hi Prakash,

I suppose that # is maintained in RSKC in Develpoment & Sandbox but not in production..can you check the same.

BR,

Arpit

Former Member
0 Kudos

# is a forbidden character.  Adding it in RSKC won't help you.

You should avoid loading it.  Replace it with another character or remove it.

Former Member
0 Kudos

How to replace the same if there are 10000 records with such an issue? Please let me knw how we can correct the same

a_nagelhout
Explorer
0 Kudos

Hi Prakash,

I don't think it's the issue, but just for sure, did you maintain this character in TC RSKC?

regards, André