Document Category Contains Invalid "#" Value (0DOC_CATEG_TEXT)

We recently applied support packs to our ECC6 system. Somewhere in there, additional data records were added to the VBTYP domain (SD document categories). This domain is used for the 0DOC_CATEG_TEXT BW datasource. When I am loading document category master data into BW, it returns an error because SAP decided to make the symbol "#" the key value for one of the new doc categories. OSS Note 173241 states "The value that only consists of the single character '#' is not allowed because the initial input is masked with '#'."
What were they thinking? Has anyone found an OSS note to resolve this or have encountered this problem?
What we applied:
Netweaver is EHP1 support package stack 3
ECC6 EHP4 Support Pack Stack 3
Thanks,
Lisa.

Has this issue been resolved from anyone who experienced the same problem? We just upgraded our R3 server to Enhancement Pack 5. Since then, our load process for the 0DOC_CATEG_TEXT datasource has been erring because of newly added values from the EhP5 upgrade. Several new categories were added using symbols, but the load is failing specifically against 2 of them: a § symbol, and the other one I'm unsure of because as some already pointed out, SAP masks the value with a pound (#) symbol, rather than showing the actual value.
Granted, I could easily add the § symbol into allowable characters (would rather not; allowing characters like that can easily create confusion and other errors down the road in reporting), but not knowing what the second one it's failing on is because it's masked with the # character, would not do my any good.
As someone suggested, I could also add in some logic to our user exit to delete anything outside of the ABC123 values, but was hoping maybe there was a note or something in regards to fixing this issue before going down this route.

Similar Messages

Error for EC-CS : The dependent char. partner unit contains invalid value?

Hi,
We are using PC consolidation and while doing rollup for p1/2011 facing following error:
The dependent char. partner unit contains invalid partner unit. We are facing this error only for one newly created GL/Fs item and that to for some company codes/consol groups.
The intercompany transaction created in FI is not rolling to EC-CS thru CXCD rollup.

Hi,
We need to maintain the default values in transaction - CXOAA.
The issue is solved.
Njoy
Siva

!!!how to control invalid value in PSA

Hi, all
Maybe you are in an international corporation, and the database are complicated as well as master data value such as material description in English, Chinese, Indian or others like ? & #@. Some of them are not notified by SAP BW system especailly when we extract master data from R/3.
And there maybe thousands of error records not only several. I have tried to use T-code:RSKC, but no result.
How do you solve this problem?
Thanks for your friendly answer!
Carina

Hi Carina,
Pls go thru the below link
Characteristic contain invalid values.
Regards,
Bhargava Bommidi.

Update routine to populate value for field ZDOCCATG(Document category)

Hi Experts,
   I need to populate data for field ZDOCCATG(Document Category) based on the value of the below two fields,
1. 0deb_cre_lc(Debit / credit Amount)
2. 0ac_doc_typ(Belegart)
The logic is as follows:
if 0deb_cre_lc > '0'.
     if 0ac_doc_typ == 'dz'.
      ZDOCCATG = Disputes.
     else
ZDOCCATG = Invoices.
   end If.
else
if 0ac_doc_typ < '0'.
ZDOCCATG = Credits.
end if.
I need to write the update routine to get the values assigned for Document category based on these two fields. When i open the routine for the field ZDOCCATG, i can see the below screen:
PROGRAM UPDATE_ROUTINE.
$$ begin of global - insert your declaration only below this line -
TABLES: ...
DATA:   ...
$$ end of global - insert your declaration only before this line   -
FORM compute_data_field
TABLES   MONITOR STRUCTURE RSMONITOR "user defined monitoring
USING    COMM_STRUCTURE LIKE /BIC/CS80FIAR_O03 - (Communication structure)
           RECORD_NO LIKE SY-TABIX
           RECORD_ALL LIKE SY-TABIX
           SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
CHANGING RESULT LIKE /BIC/AZOARFSCM00-/BIC/ZDOCCATG
           RETURNCODE LIKE SY-SUBRC "Do not use!
           ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update
$$ begin of routine - insert your code only below this line        -
fill the internal table "MONITOR", to make monitor entries
result value of the routine
RESULT = .
if abort is not equal zero, the update process will be canceled
ABORT = 0.
$$ end of routine - insert your code only before this line         -
ENDFORM.
Please let me know the code to be inserted (based on the logic mentioned above) in the above screen . Thanks
Regards,
Kavitha Jagannath

Hi Kavitha,
      Supposing the technical name of fields is /bic/0deb_cre_lc and /bic/0ac_doc_typ use the code below at the marked position.
PROGRAM UPDATE_ROUTINE.
$$ begin of global - insert your declaration only below this line -
TABLES: ...
DATA: ...
$$ end of global - insert your declaration only before this line -
FORM compute_data_field
TABLES MONITOR STRUCTURE RSMONITOR "user defined monitoring
USING COMM_STRUCTURE LIKE /BIC/CS80FIAR_O03 - (Communication structure)
RECORD_NO LIKE SY-TABIX
RECORD_ALL LIKE SY-TABIX
SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
CHANGING RESULT LIKE /BIC/AZOARFSCM00-/BIC/ZDOCCATG
RETURNCODE LIKE SY-SUBRC "Do not use!
ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update
$$ begin of routine - insert your code only below this line -
fill the internal table "MONITOR", to make monitor entries
result value of the routine
<----- Paste the code below as shown here --->
if comm_structure-/bic/0deb_cre_lc > 0.
if comm_structure-/bic/0ac_doc_typ == 'DZ'.
   result = 'DISPUTES'.
else
   result = 'INVOICES'.
endIf.
elseif comm_structure-/bic/0deb_cre_lc < 0.
result = 'CREDITS'.
end if.
<----
>
if abort is not equal zero, the update process will be canceled
ABORT = 0.
$$ end of routine - insert your code only before this line -
ENDFORM.
Regards:
Jitendra
Edited by: Jitendra Gupta on Oct 15, 2009 3:05 PM

Value 'KIRBYu00A0' of characteristic 0SORTL contains invalid characters

hello experts!
i am facing this error while activating 0vendor. data not available either in info object master neither in psa.
Error Message: Value 'KIRBY ' (hex. '004B004900520042005900A0') of characteristic 0SORTL contains invalid characters
Message no. BRAIN060
Diagnosis
Only the following standard characters are valid in characteristic values by default:
!"%&''()*+,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ.
Furthermore, characteristic values that only consist of the character # or that begin with ! are not valid.
You are trying to load the invalid characteristic value 1. (hexidecimal representation 004B004900520042005900A0).
Procedure for System Administration
Try to change the invalid characters to valid characters.
If you want values that contain invalid characters to be admitted into the system, make the appropriate setting in BW Customizing. Refer to the documentation describing the requirements for special characters and the possible consequences.
For more information on the problems involved with valid and invalid characters, click here.
regards
vijay

Hi Vijay,
after KIRBY is a characteristic value which cannot be interpreted by BW properply / is not in the valid char list.
KRIBY is hex value 004B0049005200420059
the invalid char is hex value 00A0 -> online hex converter didn't found a ASCI match.
To solve the problem you will need to fix the record in the source. Or you go to PSA -> delete all in teh field and re-enter KRIBY.
Best regards,
Axel

Error Parameter WI_ID contains an invalid value in webdynpro abap

Hi Experts,
i am working with webdynpro abap and using work flow in my component , here i am getting error and the error is
Parameter WI_ID contains an invalid value .
its showing the error in windows parameter : wi_id and the wi_id is type sww_wiid
and the same parameter i am using in application parameter .
can u suggest me how to use this parameter wi_id in window parameter and application parameter and what the type should be for wi_id parameter.and what the value should be for application parameter wi_id.
her i am giving the complete error details.
please give me the requried information if u porvided screen that will be very useful
The following error text was processed in the system RD1 : Parameter WI_ID contains an invalid value .
The error occurred on the application server S0164SAPDEV2_RD1_00 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: HANDLESTART of program /1BCWDY/BP6P95H8W6B71I7VVRPR==CP
Method: IF_WDR_VIEW_DELEGATE~WD_INVOKE_EVENT_HANDLER of program /1BCWDY/BP6P95H8W6B71I7VVRPR==CP
Method: INVOKE_EVENTHANDLER of program CL_WDR_DELEGATING_IF_VIEW=====CP
Method: DISPLAY_TOPLEVEL_COMPONENT of program CL_WDR_CLIENT_COMPONENT=======CP
Method: INIT of program CL_WDR_CLIENT_APPLICATION=====CP
Method: IF_WDR_RUNTIME~CREATE of program CL_WDR_MAIN_TASK==============CP
Method: HANDLE_REQUEST of program CL_WDR_CLIENT_ABSTRACT_HTTP===CP
Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_WDR_MAIN_TASK==============CP
Method: EXECUTE_REQUEST_FROM_MEMORY of program CL_HTTP_SERVER================CP
Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
Thanks & Regards.
khanna

Hi Nawal Kishor Mittal,
thanks for the reply,
i have given the application parameter wi_id with type string also but in 120 client (development) is working fine. when i test in 130 client( testing) its going to dump.
what should be given to application value i given parameter wi_id and what the value should be there.
waiting for reply.
Thanks & Regards.
Khanna.

Infopath cannot submit the form because it contains errors. Errors are marked with either a red asterik(required fields) or a red, dashed border (invalid values)

Infopath cannot submit the form because it contains errors. Errors are marked with either a red asterik(required fields) or a red, dashed border (invalid values).
Press Ctrl+Shift+O for next error or Press Ctrl+Shift+I for error details
Please help me, Thank in advance.
Sravan.

Hi Sravan, this means that one or more of the fields are required to be filled in or have validation set up on them so that the information entered matches a certain criteria. Make sure what's entered matches what's required. If the form still can't be
submitted, check the rules set in InfoPath and the list/library to see what's causing the error(s).
cameron rautmann

Modify Values Document Category List

Hi All,
Can you please explain how to modify values or add new ones to the Document Category list, that belongs to the manage contract documents Actions?
I am working on OM > Blanket Sales Agreement >
Thanks for your help
Deneb

What exactly do you need, just a list of categories applied on a document or something more? Here is a basic AttributeRequest for getting category info from document:
        AttributeRequest[] catAR = new AttributeRequest[]
          new AttributeRequest(Attributes.CATEGORIES, new AttributeRequest[]{
            new AttributeRequest(Attributes.CATEGORY_CLASS_OBJECT, new AttributeRequest[]{
              new AttributeRequest(Attributes.DISPLAY_NAME, null)
            new AttributeRequest(Attributes.CUSTOM_ALL, null)
    Item file = fm.resolvePath(filePath, catAR);
    NamedValue[] categories = file.getRequestedAttributes();
    Item[] categoryInstances = (Item[])categories[0].getValue(); //index [0] is for Attributes.CATEGORIESthen you cycle through categoryInstances to get each category's display name.... Hope this helps, if you have any other questions - ask and I will try to give you the answer!
Pedja

Error: 'InfoObject ZDATE contains invalid characters in record 1 in value'

Dear friends,
When I am uploading data from oracle datasource (in BW 3.5) I am getting an error 'InfoObject ZDATE contains invalid characters in record 1 in value'. There are no illegal characters in the date instead the date field is blank in datasource. There are other date fields technically the same as ZDATE with blank values but they dont throw an error when scheduler runs.
Though when I manually upload the data, it's loaded successfully.
Please suggest where can the error be?
Regards,
Amit Srivastava

You have 2 options:
1. Corect your data for the characteristics that give errors.
Or
2. go to SPRO in BW - Netweaver - BW - general settings - maintain permitted characters.
In this screen, you maain tain any special characteristic that you the system to recognise and accept. In your case, take your characteristics that give error and add to this.
Ravi Thothadri

Invalid text value. A text field contains invalid data. Check the value and try again

Hello,
I am having a problem with the error mentioned in the title. I see alot of others have experienced the same problem, but I have quite a twist to it.
I see the problem when I try to edit a list item, and then try to save the changes.
Here what I see in the ULS log:
System.Runtime.InteropServices.COMException: Invalid text value. A text field contains invalid data. Check the value and try again
at Microsoft.SharePoint.Library.SPRequestInternalClass.AddOrUpdateItem(String bstrUrl, String bstrListName, Boolean bAdd, Boolean bSystemUpdate, Boolean bPreserveItemVersion, Boolean bUpdateNoVersion, Int32& plID, String& pbstrGuid, Guid pbstrNewDocId,
Boolean bHasNewDocId, String bstrVersion, Object& pvarAttachmentNames, Object& pvarAttachmentContents, Object& pvarProperties, Boolean bCheckOut, Boolean bCheckin, Boolean bMigration, Boolean bPublish, String bstrFileName, ISP2DSafeArrayWriter
pListDataValidationCallback, ISP2DSafeArrayWriter pRestrictInsertCallback, ISP2DSafeArrayWriter pUniqueFieldCallback)
at Microsoft.SharePoint.Library.SPRequest.AddOrUpdateItem(String bstrUrl, String bstrListName, Boolean bAdd, Boolean bSystemUpdate, Boolean bPreserveItemVersion, Boolean bUpdateNoVersion, Int32& plID, String& pbstrGuid, Guid pbstrNewDocId, Boolean
bHasNewDocId, String bstrVersion, Object& pvarAttachmentNames, Object& pvarAttachmentContents, Object& pvarProperties, Boolean bCheckOut, Boolean bCheckin, Boolean bMigration, Boolean bPublish, String bstrFileName, ISP2DSafeArrayWriter pListDataValidationCallback,
ISP2DSafeArrayWriter pRestrictInsertCallback, ISP2DSafeArrayWriter pUniqueFieldCallback)
I have 3 front end servers(fx wfe1, wfe2, wfe3). And here is the twist.
If I access the library directly through wfe1 and wfe2, I get the error. If I access the library via wfe3 if works just fine.
So because of this, I think it is safe to assume that is has nothing to do with the character limit of 255. Nor does it have anything to do with the field type, since it is already set to mulitible lines of text.
So. Any ideas?
Regards,
Michael
mic

Check if there is any change in web.config of these servers
http://support.microsoft.com/kb/2880758
To work around this issue, limit the length of the personal message in the invitation to 256 characters or less.
This is a known issue. Microsoft is working to resolve this issue.
http://social.msdn.microsoft.com/Forums/en-US/7bb16e51-e7cc-439e-a8b3-755683ccac1a/max-length-on-custom-field-types
To solve the problem you may have to change the field's parent type to "note". To do that you have to open your fldtypes... file under Templates/xml and change the line to:
"<Field Name="ParentType">Note</Field>" from "<Field Name="ParentType">Text</Field>"
You might also have to add a sql type if your text needs to be longer than 255 characters
<Field Name=”SQLType”>ntext</Field>
and inherit from SPFieldMultiLineText instead of SPFieldText
If this helped you resolve your issue, please mark it Answered

Value '! u2018Hex. '0021characteristic ZORG_INPT contains invalid characters

Dear ALL Expert,
In BI 7 Environment while loading data from psa to Cube I getting error in DTP( Value '! u2018(Hex. '0021 ') of characteristic ZORG_INPT contains invalid characters ). Please guide me regarding is error
regards,
ravi

Hello Ravichendra,
I had a same problem and i have resolved by writing a abap routine in update rules below.
$$ begin of routine - insert your code only below this line        -
CALL FUNCTION 'SCP_REPLACE_STRANGE_CHARS'
EXPORTING
    INTEXT                  = COMM_STRUCTURE-EQUIPMENT
INTEXT_LG               = 0
INTER_CP                = '0000'
INTER_BASE_CP           = '0000'
IN_CP                   = '0000'
   REPLACEMENT             = 32
IMPORTING
   OUTTEXT                 = RESULT
OUTUSED                 =
OUTOVERFLOW             =
EXCEPTIONS
   INVALID_CODEPAGE        = 1
   CODEPAGE_MISMATCH       = 2
   INTERNAL_ERROR          = 3
   CANNOT_CONVERT          = 4
   FIELDS_NOT_TYPE_C       = 5
   OTHERS                  = 6
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
*fill the internal table "MONITOR", to make monitor entries
result value of the routine
RESULT = v_eqp.
if the returncode is not equal zero, the result will not be updated
RETURNCODE = 0.
if abort is not equal zero, the update process will be canceled
ABORT = 0.
$$ end of routine - insert your code only before this line         -
Regards
Sankar

Value '05uFF71uFF7BuFF8B ' for characteristic ZJLEG_PPL contains invalid characters

Hi,
One of our Master data attribute load is failing with the following error message.
Value '05ｱｻﾋ ' for characteristic Z_PPL contains invalid characters
As you see there are some Japanese characters when it is trying to load into Char string?
Can we load such characteristics?
Where can we check which all Languages are installed in the system?
If we want to maintain these to the Special characteristics in RSKC transaction?
Can we enter these characteristics using English keyboard?
Regards
Ajay

Hi Ajay
Some time in the run time environ ment field values are moved to junk chars .
In this case even if u r traying to place the same char in RSKC also it wont
accept..
So in this can just edit that particular error record like in the ordinary process in
the PSA.other wise if its a master data u need to select the option error handling
in the info pak and rerun the info pak..
Hope itz clear a little atleast...!
Thanks & Regards
R M K
***Assigning pointz is the only way of saying thanx in SDN ***
**Winners dont do different things,they do things differently**
> Hi Although,
>
> We do have same Characteristics maintained to QA and
> Production.
>
> But when I load the Same data in QA it is successful
> but it is failing in Production.
>
> Regards
> Ajay

Word cannot open this document. The document might be in use, the document might not be a valid Word document, or the file name might contain invalid characters (for example,\ /).

I recently upgraded to a new Macbook Air running Lion, from my 2007 white Macbook running Snow Leopard. I had Office for Mac 2004 on the 2007, but had to upgrade to Office for Mac 2011 to be compatible with Lion on the Air. Now when I try to open my documents on the Air that were saved under Office 2004 on the old computer, I get the following message: Word cannot open this document. The document might be in use, the document might not be a valid Word document, or the file name might contain invalid characters (for example,\ /).
Any suggestions? Thank you.

Ha,ha,ha.....I figured it out. But for anyone else who's having this problem, it seems that while Office 2004 allowed dates in this format: 00/00/00, Office 2011 doesn't like it at all. I just changed the format in the document names to 00-00-00 and all is well. Documents are opening beautifully!

Need help with Value '# ' of 0REF_DOC_NO contains invalid characters

Hi Experts
We are having load failure due to this Value '# ' of characteristic 0REF_DOC_NO contains invalid characters error. I have managed to find out at PSA level there are few records with contains # value. I have also informed the user about it and user had rectified the record from ECC level.
Our load goes evey night through process chains from PSA to DSO and then to Cube.
We have requests in DSO till today and the problem happened two weeks ago e.g. 7 DEC. In cube the last record came on 6 DEC as after that it was failing everyday.
Now I am just wondering with few questions :-
Should I wait for next delta load to happen so that it can bring all the records from DSO to Cube or Do i need to change the record of that certain date in DSO too.
Please give me your valuable suggestion and steps.
Regards
Sunny

Sorry for posting it in wrong section, i have moved it to right thread now.
Cube is failing with invalid characters error Value # of 0REF_DOC_NO

Value '#' (hex. '') of characteristic 0customer contains invalid characters

Value '#' (hex. '') of characteristic 0customer contains invalid characters
I didn't get the error message when I am loading into ODs.The error occurs only the ODS to Cube load.
RSKC transaction -I have values
ALL_CAPITAL+/=1234567890~`@#$%^&*()_-{}[]\|'";:?.>,<
Other than ABAP routine is their anyway can I handle the invalid characters.
Because I am loading millions of records in the transaction.I can't Manually update in the PSA.
Advance Thanks

Hi
I am surprised why you have not faced this problem while loading to ODS. I guess your ODS is not ON for BEx Reporting. Anyways, You need to write a transfer routine for 0CUSTOMER.
Just replace ZZZ with you transfer structure field.
DATA: L_USER_ALLOWED_CHAR TYPE RSALLOWEDCHAR,
L_ALL_ALLOWED_CHAR(140) TYPE C,
L_RESULT_STR_LEN TYPE I,
L_STR_INCREMENT TYPE I.
CONSTANTS C_SAP_ALLOWED_CHAR(58) TYPE C VALUE
' !"%&''()*+,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ'.
IF L_ALL_ALLOWED_CHAR IS INITIAL.
SELECT SINGLE * FROM RSALLOWEDCHAR
INTO L_USER_ALLOWED_CHAR
WHERE ALLOWKEY = 'S'.
CONCATENATE C_SAP_ALLOWED_CHAR
L_USER_ALLOWED_CHAR-ALLOWCHAR
INTO L_ALL_ALLOWED_CHAR.
ENDIF.
RESULT = TRAN_STRUCTURE-ZZZ.
TRANSLATE RESULT TO UPPER CASE.
L_RESULT_STR_LEN = STRLEN( RESULT ).
L_STR_INCREMENT = 0.
WHILE L_STR_INCREMENT <> L_RESULT_STR_LEN.
IF NOT RESULT+L_STR_INCREMENT(1) CO L_ALL_ALLOWED_CHAR.
RESULT+L_STR_INCREMENT(1) = ' '.
ENDIF.
ADD 1 TO L_STR_INCREMENT.
ENDWHILE.
Hope this helps
Regards
Pradip

Document Category Contains Invalid "#" Value (0DOC_CATEG_TEXT)

Similar Messages

Maybe you are looking for