Are idoc fields case sensitive?

Hello, there has been an error during idoc processing. The trading partner field was filled in lowercase and this is bringing me error Message no. FB279 ' Company dp0017 is not defined'. The other idocs had DP0017 filled in and were processed fine.
Any input on this? thx.
Edited by: Antish Awootar on Jun 7, 2011 8:02 AM

Hi Antish,
It actually depends on the value that is stored in the IDOC, if the IDOC has company code in lower case then that is exactly how it will be used in the program for all purpose and no automatic conversion is applied. The below message is thrown in the FM - FI_COMPANY_CHECK This FM will look up the table T880 - If you check the entry in this table will be DP0017 and not dp0017. Hence it is throwing the error message.
If your question is it works fine when i try in SE37 with the FM "FI_COMPANY_CHECK" or if i input "dp0017" in WE19 or in SE11 against T880, then the reason for that is a conversion is applied automatically and it is changed to DP0017.
To answer your question "Are idoc fields case sensitive?", it depends on the context, does it retain the case when it is filled in, yes it does.
Regards,
Chen
Edited by: Chen K V on Jun 7, 2011 4:10 PM

Similar Messages

SOAPAction Header field case sensitive

Hi gurus,
I am trying to consume a webmethods java webservice via XI/PI NW2004 and when I send a request, PI send the soapaction field in uppercase.
POST http://webservices.kuehne-nagel.com/HelloWorld_test HTTP/1.0
Accept: /
Host: https://webservices.kuehne-nagel.com/HelloWorld_test
User-Agent: SAP-Messaging-com.sap.aii.messaging/1.0505
content-id: <soap-4C4DF1260912013BE10080009E344EB9sap.com>
Content-Type: text/xml; charset=utf-8
Content-Length: 316
SOAPACTION: "http://webservices.kuehne-nagel.com/helloWorld/hello"
It should be like SOAPAction : "http://webservices.kuehne-nagel.com/helloWorld/hello"
How can I set/change it on XI/PI ?
Regards,
Rodolfo Miã

Gourav,
This is W3 Standard:
HTTP verbs are case sensitive. (http://www.w3.org/TR/wsdl)
In my case, the webservice provider was implemented in JAVA code and in Linux server. Java and Linux are case sensitive.
I agree with you if we are working with .NET implementation.
I already have tried to consume a .Net asmx webservice and works fine.

LIS enhancement via CMOD: are new fields "delta sensitive".....

...or not? If not, how to do for it??
Thanks in advance!
Bye!
Ferdinando

Ferdinando:
The new added fields are not "delta sensitive"...
Deltas are based normally in unique and changin fields, like a "Record Change Date" or a Serial or Numeric Indicator, etc...
If you want to "watch" the changes on those fields, you'll have to do it by yourself, via a program or function in R/3... It's a lot of work, I can tell you that...
Table CDHDR (and I don't remember if there's another) register all changes to all tables in R/3... Take a look at it and maybe it can help you...
Regards,
Luis

CSS cookieurl: case sensitive?

Hello,
As far as I understand, the HTTP header cookie field, and the embedded cookie (in a URL) are case-sensitive. Is this correct?
The settings look like this:
content stickyCookie
advanced-balance cookieurl
string prefix "SESSION_ID="
On the HTTP header the cookie field looks like this:
Set Cookie: SESSION_ID=ABCDEF
But if instead of this, the request comes from a client with the cookie embedded in the url, it looks like this:
http://localhost/Info/index;session_id=ABCDEF?page=home.
Is this field case-sensitive for the CSS? I know it is for the ACE, as I have done this and there is the "cookie secondary" command where you can specify how the url-embedded cookie looks like.
So I am afraid there is no way of making this work on a CSS?
Any help will be much appreciated!

Hi Javier,
The Cisco CSS is case-sensitive when searching for this string.
When configuring the CSS 11000 and 11500, determine first if you need a server cookie string. If the string operation under the content rule is match-service-cookie, which is the default setting, this parameter must be configured. In this case the service cookie string is matched against the cookie contained in the HTTP header for load balancing decision.
If the string operation under the content rule is set to the hash method, this parameter is not needed. In order to select one of the available servers, the cookie contained in the HTTP header is mathematically processed using a hashing algorithm. If available, the hash algorithm assigna the connection carrying a certain cookie to the same server. This example focuses on the match-service-cookie case.
Note: Cookies are case sensitive.
Configuring the Service
training4(config># service server_g
training4(config-service[server_g])# string LV2KJK (the server cookie text)
training4(config># service server_h
training4(config-service[server_h])# string AARIKA
Configuring the Content Rule
Note: Cookies require a Layer 5 rule.
You can create a Layer 5 rule by adding a URL.
For example, .
A Layer 4 rule can be promoted to a Layer 5 rule by issuing the advanced-balance cookies command.
Choose the advanced-balance method.
training4(config-owner-content[cookie-layer5])# advanced-balance cookies
Configure the string operation.
training4(config-owner-content[cookie-layer5])# string operation ?
match-service-cookie (DEFAULT)
hash-crc32
hash-xor
hash-a
Define the starting/ending bytes.
training4(config-owner-content[cookie-layer5])# string range 1 to 200
Start byte position of cookie/url after header (Range:1-600)
Specify the prefix located in the string range.
training4(config-owner-content[cookie-layer5])# string prefix "ASPSESSION"
"Quoted textual information"(Len: 0-32)
Indicate how many bytes to skip after the starting prefix.
training4(config-owner-content[cookie-layer5])# string skip-length 9
"Quoted textual information"(Len: 0-32)
Indicate how many bytes after the prefix/skip-length make-up the string.
training4(config-owner-content[cookie-layer5])# string process-length 6
Integer value(Range: 0-64)
If no string process length is configured, search after end of string character.
training4(config-owner-content[cookie-layer5])# string eos-char "&"
"Quoted textual information"(Len: 0-5)
Specify the failover in the event that a server goes down or is suspended.
training4(config-owner-content[cookie-layer5])# sticky-serverdown-failoversticky-srcip
sticky-srcip-dstport
sticky-srcip
balance (Default)
redirect
reject
Below is an example of a cookie string, and how some of the parameters work.
ASPSESSIONJJKKJJKK=LV2KJK44444444
!--- The string prefix = ASPSESSION.
!--- The string skip-length = 9. Skip
!--- nine characters after the prefix.
!--- The string process-length = 6, which would make
!--- the string LV2KJK matching service server_g.
ASPSESSIONSQPMMJHK=AARIKAMDESLD
!--- Matches service server_h.
Below is a sample configuration for the cookie strings.
!************************** SERVICE **************************
service server_g
ip address 172.17.63.240
string LV2KJK
active
service server_h
ip address 172.17.63.241
string AARIKA
active
!*************************** OWNER ***************************
owner braden
content server-cookie
protocol tcp
vip address 172.17.63.199
port 80
advanced-balance cookies
string range 1 to 200
string prefix "ASPSESSION"
string skip-length 9
string process-length 6
add service server_g
add service server_h
active
Kindly tell if this information is of any use to you.
Sachin garg

Table and Primary Key Case Sensitive in Automated Row Fetch

Why are the table and primary key fields case sensitive in the Automated Row Fetch process? I'm debugging an error in this process and I'm not sure what the case should be.

Russ - It's a defect of sorts. Use upper case in the process definition. I don't think these processes will work with tables or columns whose names are not known to the database as upper-case values, i.e., defined using double-quoted non-upper case.
Scott

Web Dynpro & case sensitive selection of Adobe Forms

Hi Community
how can I solve this issue:
I have a Web Dynpro View with a button. Clicking this button generates a Adobe form and displays it.
So long everything's fine.
Here's my problem:
There are 4 different case sensitive forms in dependence of the user's selection. How can I solve this?
The form is assigned to the view via layout, so do I have to create 4 views,related to the amount of forms? And additionally the pdf's are displayed in dialog windows, so do I have to create 4 windows additionally where I have to embed a view for each of them?
Is there any other way to solve it? It looks for me like a not very nice solution.
Thanks in advance,
Tan

Hi Tan,
Solutions that i am proposing may not be the best solution but you need to take a call on the best one:
Solution 1 :
1. Try Creating only one view and one window for pop up ( in addition to your existing view with button )
2. in the view add an interactive form and bind it to one of the form.
3. in WDDOMODIFYVIEW method , depending on the situation try to change the mapping to this interactive form
4. This embedded view in the pop up window is always called, only based on the conditions the adobe forms changes.
Solution 2:
1. in your view add 4 Interactive forms , bind them to different nodes as per its mapping requirement
2. create 4 Visibility context attributes , bind them with each of the forms
3. depending on the condition , hide or make visible the adobe forms.
4. show this view in the pop up window.
My suggestion would be to go with Solution 2 , since it does not involve dynamic modifications at runtime.
Regards,
Ashish Shah

Why is default URL created by iWeb Case Sensitive

I have posted a new website using iweb and it will only load if I use "Site" in the URL. If I type "site" Apple reports that no Website is available. Try it.
http://web.mac.com/alan.fozzard/Site/Welcome.html
http://web.mac.com/alan.fozzard/site/Welcome.html

it will only load if I use "Site" in the URL
No problem for me with just the short version, and that is how it should work for you too:
http://web.mac.com/alan.fozzard
Urls that include a file path are almost always case sensitive. Best get used to it.

Make material number in MM01 case sensitive

Hi Experts,
I got an requirement like to make MM01 transaction while creating material number it has to accept both Lower and Upper Case..
Say for example : "a12" as one material
"A12" as another one material
any suggestions please send.....
Thanks.
Preethi jose

First check conversion-exit of domain MATNR (something like MATN1) with Customizing behind, you will have to analyze your Customizing (and the list of extensions, solutions installed on your system) to find the actual field(s) which contains the external format of the material master id (e.g. MARA-MFRPN for a sample) AND look at table MATERIALID (domain MATNR_EXT is also not case sensitive), then you may, with a SSCR key for the object as it will be a change of the standard, change the domain(s) definition to allow lowercase. But consider before some problems like search help becoming case sensitive, it is usually (at least) not a good idea to have key fields case-sensitive...
If possible, my advice is to not make this change by a developement, but to look for Customizing, check
Regards,
Raymond

WE19 (iDoc Test Tool) and case sensitive content

Hi experts,
I am not able to send case sensitive content via WE19. When I change a value of an existing iDoc (via WE19) all values of the segment are converted to uppercase (independent of the domain).
To reproduce:
1) Open transaction WE19
2) Use any existing iDoc as template
3) Open any segment
4) Fill any field with a lowercase text
5) Press ENTER
6) Re-open the segment and check changed field. -> The value is converted to upper case
This (translate to upper case) happens only on the segment that has been edited in WE19.
In my opinion, the transaction WE19 is not usable because it is not possible to edit/change case-sensitive values. In our customer setting we need to send case-sensitive data in iDocs to the receiver.
Question: Is there any other transaction to read an existing iDoc, change the data case sensitive and send it to the receiver.
Thanks in advance.
Björn

Hi,
yes - this is a "strange" behaviour ;o)
Only other solution I know you need an IDoc in status 51 for:
- go to bd87
- select the IDoc in status 51
- navigate to the needed data record
- double click it
- menu => display => change
- insert your data
After saving the status will be reset and you can process the IDoc in BD87.
I am not sure this will work for each IDoc and element - but you may give it a try.
For converting an existing to status 51 you can use this report: RC1_IDOC_SET_STATUS
Regards,
Kai

Is IDOC case sensitive?

Hi all,
I am trying to edit IDOC in bd87.
for eg. for
field A = x, i am editing this to '123k54'
after editing the value is change to.
field A = 123K54,
please observe that the 'K' is changed to caps.
is there any way that i get the same 'k' in the value.
please suggest.
Thanks in Advance
satheesh

Satheesh,
I think it depends on the field that you are editing. Look at the data element and then the domain to which its being referred. If its marked as CASE SENSITIVE then it will not change the data into uppercase. Otherwise it might.
Regards,
Ravi
Note : Please reward points if this helps.

Case sensitive field in to_date function

update "Ab_Order" set "OrderDate" = to_date("Order Date String", 'yyyy/mm/dd)
Here the OrderDate column is of type Date
"Order Date String" is varchar2. Iam trying to copy the data from "Order Date String" which contains data in this format '2011/04/24' to OrderDate column to perform some date functions
when I try to run this query it gives a error: ORA-01830: date format picture ends before converting entire input string
So I tried to run this query by creating a test table wit 2 columns : update testtable set column1 = to_date(field1, 'yyyy/mm/dd')
where column1 is date field and field1 is varchar2 and this worked.
So Iam assuming this is the problem with case sensitive fieldnames . As far as i know we should include case sensitive fields in double quotes. Is there anything else to do wit the to_Date function. Can anyone please let me know how to do that.

Hi,
Welcome the the forum!
882431 wrote:
update "Ab_Order" set "OrderDate" = to_date("Order Date String", 'yyyy/mm/dd)It looks like you're missing a single-quote right before the last ')'.
Here the OrderDate column is of type Date
"Order Date String" is varchar2. Iam trying to copy the data from "Order Date String" which contains data in this format '2011/04/24' to OrderDate column to perform some date functions
when I try to run this query it gives a error: ORA-01830: date format picture ends before converting entire input stringThat error occurs when when you have characters in the 1st argument that do not correspond to anything in the 2nd argument. For example:
TO_DATE ( '30-Aug-2011 12:00'
, 'dd-Mon-yyyy'
)In this example, TO_DATE doesn;t know what to do with the ' 12:00' at the end of the 1st argument. According to the 2nd arguemnt, there's only supposed to be 11 characters in the string. So it raises the ORA-01830 error.
So I tried to run this query by creating a test table wit 2 columns : update testtable set column1 = to_date(field1, 'yyyy/mm/dd')
where column1 is date field and field1 is varchar2 and this worked.
So Iam assuming this is the problem with case sensitive fieldnames . As far as i know we should include case sensitive fields in double quotes. Is there anything else to do wit the to_Date function. Can anyone please let me know how to do that.Case sensitive column names are a bad idea because they cause so amny problems, but I don't think this is one of those problems. It's more likely that you need to use SUBSTR (or some other string manipulation function) on "Order Date String" before using it in TO_DATE.
Whenever you have a problem, please post a little sample data (CREATE TABLE and INSERT statements, relevant columns only) from all tables, so people can re-create the problem and test their ideas.
Also post the results you want from that data, and an explanation of how you get those results from that data, with specific examples.
Always say which version of Oracle you're using.

The query screens are case sensitive I want to remove the case sensitivity

The current query screens are case sensitive ,I want to remove the case sensitivity is there a setting somewhere to remove this or how else can this be done.
Example:In the restrict value range of the query screen.If we give for a particular field anything in capital letters/small it should take.
Please let me know ASAP
Thanks

Hi pavan,
generally case sensivity is related to InfoObject Master Data.
Take a look via Tcode RSD1 to the master data of your InfoObject and check in first screen if flag for capitol letters has been marked.
If this is the situation it is a problem, because MAster Data in cube have been saved as different if are written like "Letter" or "LETTER".
Ciao.
Riccardo.
Message was edited by:
Riccardo Venturini

Hello. I keep my IPhoto library (about 90GB) on an external HD and am trying to back it up to another external drive. Both are formatted Mac OS Extended (Case-sensitive, Journaled). Recently, backup has failed from the start due to error 36. Howtoresolve?

Hello. I keep my iPhoto library (about 90GB) on an external HD and am trying to back it up to another external drive. Both are formatted Mac OS Extended (Case-sensitive, Journaled) and both check out when scanned with Disk Utility. Recently, backup has failed from the start due to error 36. Any ideas how to resolve? Also, what's the maximum recommended size for an iPhoto library file? Thx!

Since you can't drag the library to the other EHD for the backup see if you can duplicate it (if you have enough room on the drive) by selecting it and typing Command+d (duplicate).
If you do rebuild the library without a backup and it goes awry you won't lose your photos but you may lose your orgnaizational efforts. So try the following:
Fix #1
Launch iPhoto with the Command+Option keys held down and rebuild the library.
Select the options identified in the screenshot.
Fix #2
Using iPhoto Library Manager to Rebuild Your iPhoto Library
Download iPhoto Library Manager and launch.
Click on the Add Library button, navigate to your Home/Pictures folder and select your iPhoto Library folder.
Now that the library is listed in the left hand pane of iPLM, click on your library and go to the File ➙ Rebuild Library menu option
In the next window name the new library and select the location you want it to be placed.
Click on the Create button.
Note: This creates a new library in the location of your choosing based on the LIbraryData.xml file in the library and will recover Events, Albums, keywords, titles and comments but not books, calendars or slideshows. The original library will be left untouched for further attempts at fixing the problem or in case the rebuilt library is not satisfactory.
NOTE: Fix 2 above might be the method you might want to try first with iPLM creating the new library on your second EHD. If it works that would get your backup copy on the second EHD at the same time as repairing it. If it does'nt work then go back to Fix 1.
OT

Change Case-sensitivity of field ASKTX in Search Help ASMD

Hi experts,
In Collective Search help ASMD, there is a elementory search help /SAPBOQ/ASMD_MITEM where field ASKTX is Case sensitive.
How can I remove the case-sensitivity of this field ?
Thnks in advance,
Goutam

owngoal wrote:
You say your "backups still turn up corrupted now and then" - how do you know? Is it only when you try to access them that you will know this?
Sometimes a backup will fail, sometimes you can't access them, sometimes you'll get this message:
See #C13 in Time Machine - Troubleshooting for details.
And by this stage is it too late to recover anything?
Sometimes. Sometimes they can be repaired by Disk Utility. Sometimes only a heavy-duty 3rd-party disk repair app like DiskWarrior ($100) can fix them. Sometimes nothing can. Sometimes you can restore some individual items, sometimes not. Sometimes you can do a full system restore from some backups, other times not.
does it help that I am using a Gigabit WIRED connection between iMac - 10/100/1000 switch - Airport Extreme Base Station?
Probably -- you won't have WIFI interference.
But if you have an iMac, why not just connect the external HD directly to your Mac? That's much faster and more reliable (and supported).
You'd need to erase the disk in that case, since Time Machine won't bother with a sparse bundle at all on a direct backup. Just format the disk as GUID, with Mac OS Extended (Journaled) and let 'er rip!

ALV grid case-sensitive edit field

Hello,
i've a editable field on a alv grid.
The field is case-sensitive in the domain.
But when i enter a field an click rturn, the letters get uppercase.
What's the problem?
Best regards,
TomSd

Hi,
Add the attribute lowercase = 'X' while preapring field catalog for this field.
Regards,
Gopi.
Reward points if helpfull.

Are idoc fields case sensitive?

Similar Messages

Maybe you are looking for