cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Request failed with SID value not found

Former Member
0 Likes
1,105

Hi all ,

In RSMO I am getting 1 request failed since last 3 days . when i analysis this I found this error

"No SID found for value 'LOT 'of char 0UNIT BRAIN"

in 2 -3 data packets . this request is on productive server with direct update to data targets.I checked that data packet manually ( by creating another new request from PSA to data targets ) . still same error it was getting me .

I tried to do this with its solution of OSS notes 69987 .

OSS nots 69987

-


If you do not find the value in the T006 or TCURC table, you must insert it. Note that the initial value is always allowed.

If you nevertheless receive this error message for the initial value, this means that there is an inconsistency in the SID table for the 0UNIT or 0CURRENCY characteristic. You can eliminate this inconsistency by calling the RSDMD_INITIAL_LINE_INSERT function module with I_CHABASNM = 0UNIT or 0CURRENCY.

If units are loaded in the external format, you must either convert these into the internal format in the transfer or update rules or change the extractor/file.The CONVERSION_EXIT_CUNIT_INPUT function module converts the external value of a unit into the internal value.

-


I am doing the same even in next request i am getting the same error ,if you faced the same or know the solution please share with me .

With regards,

Vikas

Message was edited by: vikas sharma

View Entire Topic
Former Member
0 Likes

Hi Vikas,

Did you apply the conversion routine in your transfer routine for the 0UNIT as described in your message. Try that also.

Bye

Dinesh.

Former Member
0 Likes

yes Dinesh I followd the same as per OSS notes . but not luck yet

thanks for your support

Former Member
0 Likes

Hi Vikas,

Units are not loaded via Master data but at the source system. Go to Source Systems and right click on your R/3 system. Choose Transfer of Global Settings and select Units of Measurement and Update Tables on the next screen. Run the report and try it again.

Best regards

Dirk