Question:
Invalid character,#, was found in Allocation Number and Reference Doc No. This character is already maintained in BW in permissible character because some of the texts are conatining it.So we cannot filter it earlier.
The transaction data load failed bcz Allocation Number and Reference Doc no contains #,where as both are defined as char-string.
Could anyone give reason for this?
Answer:
Hi,
the problem is probably that there is another sign hiding behing the # but the "#" is what is displayed for you. Use the HEX translation to find out what it really is.
Depending on what it is you can either remove/change the sign in the source or if it's because of another language (eg japanese) install this language if needed to e able to interpret the sign.
Kind regards
/martin
Answer:
Martin,
Thanks for ur reply.Pls suggest me how to do HEX translation?
Thanks
Answer:
Hi again,
if you debug your load and set a break point to stop where the error occurs you can get the value "#" and then diplay HEX code in the debugger. This should give you thw HEX code for the sign and then you can translate this using a HEX-translation. Ask basis people or check on the web, I only have a list on paper, so I can't send you the translation.
Some database resource should have a manual somewhere where you can check this.
Kind regards
/martin
Answer:
Martin,
Thanks for ur response.I havn't created any routine in transfer rules.
Answer:
Martin,
Thanks for ur response.I havn't created any routine in transfer rules.
Answer:
martin,
when there is a blank in masterdata attrribute , it is being represented by a HASH(pound) # symbol (key) and in description of the same a junk is appearing.
what could be the problem? I am not able to get why it is so?
regards
rao