Using Direct Input mode: UTF-8 character encoding assumed

When I validate a web page in dreamweaver CS5 (using Jeffrey Zeldman's Web Standards Advisor ) I receive the following warning; Using Direct Input mode: UTF-8 character encoding assumed.
However if I validate using W3C either as a file upload or via the live site the page validates correctly.
Can anybody please help, as it is driving me insane.

Hi John
Thank you for your swift response,
As I said before this only happens locally within Dreamweaver CS5.
However The web address is www.countryimage.co.uk/index.htm
As you will see from the code I have included <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> within the head

Similar Messages

Tax issue with Direct Input mode of RFBIBL00

Hi, I have a problem using RFBIBL00 (direct input mode) to create A/R invoices. There is no tax associated with the invoice, however, when I use direct input mode, instead of posting immediately, a batch input session is created. In the log, an information message: 'Specify a tax jurisdiction key'. The BDC session is processed with no error.
When using Call transaction mode for RFBIBL00, the document is posted immediately but the requirement is to use Direct input mode.
There is no converted data in the BBTAX structure since the doc. does not need to post to tax account. Do I need to populate the Tax amount, Tax code and jurisdiction code in this structure and BBSEG in order to by pass the information message?
Any advice is appreciated.
- Minami

Problem solved. Just need to untie the relationship between the ITEM import structure and the BBTAX so the Direct Input program will not require a tax jurisdiction code.

LSMW to create Sales Order using direct input RVINVB10

Hi,
I need advise on 2 parts of Sales Order creation using direct input program RVINVB10.
1) How do I enter the WBS Element PS_POSID in the item line of Account Assignment tab? There does not seem to be a field in the direct input program structure to fill this in.
2) How can I fill in item tab 'Billing Plan' that appears only when Item Category = 'Milestone Billing'?
Thanks

Nandan,
Please go through the documentation of the BAPI. It gives you details of what needs to be filled in in which structure/parmater. Also, read the documentation associated with each structure, that will tell what to fill.
It is really hard to explain it in simple terms as to what are required. But, you need the header, items and partners at the minimum. Also, with some of these structures there are also 'X' structures(like ORDER_ITEMS_INX for ORDER_ITEMS_IN) which should also be filled based on what fields you filled in the original structure. For example, if you filled 'MATERIAL' field on the ORDER_ITEMS_IN structure, you should also fill in the same field on the ORDER_ITEMS_INX structure with an 'X' in it.
All this is well documented in the BAPI.
Srinivas

LSMW using Direct Input

Hi,
can anyone tell me in details how to create lsmw using direct input and using BAPI?
please let me know.

Hi,
Refer this link..
LSMW using Direct Input
http://learningabap.wordpress.com/2007/03/28/step-by-step-guide-for-using-lsmw-to-update-customer-master-records/
Using BAPI..
http://www.****************/Tutorials/LSMW/BAPIinLSMW/BL1.htm
Regards
Sowmya

How to set the router and play the Command & Conquer using direct IP mode?

My router is WRT54GFirmware Version: v3.03.1
How to set the router and play the Command & Conquer using direct IP mode with other computer?

Hi, when you say direct IP mode, what do you mean ? do you wanna play the game online or on the LAN ??
can you give a few more details.

Using Direct input method(LSMW)Can I upload only 3 fields for MM01

Using Direct input method(LSMW)Can I upload only Matnr,mbrsh,mtart fields for MM01.Otherwise I have to give all the mandatory fields.?

Hello TJK,
LSMW will work in the same way as you create normal material master with the transactions, here you are giving the value through flat file and creating material master with program.
You can create only one view with LSMW but you need to give all mandatory field on that particular view, so if you have only these three field as mandatory then yes it is possible, if you have any more field mandatory addition to these fields then it will not work out, during the last step it will throw error saying "maintain the value for field XXX"
Hope this helps.
Regards
Arif Mansuri

Quotation marks display as &quot in web pages, I'm using Unicode UTF-8 character encoding.

On many web pages, where a quotation mark character should appear, instead the page displays the text &quot. I believe this happens with other punctuation characters as well such as apostrophes although the text displayed in these other cases is different, of course. I'm guessing this is a problem with character encoding. I'm currently set to Unicode (UTF-8) encoding. Have tried several others without success.

Here's a link where the problem occurs. Note the second line of the main body of text.
http://www.sierratradingpost.com/lp2/snowshoes.html
BTW, I never use IE, but I checked this site in IE and it shows the same problem, so maybe it is the page encoding after all rather than what I thought.
In any case, my thanks for your help and would appreciate any solution you can suggest.

Help me for material master upload by using Direct Input method

Hi All,
Can any one help me out for developing Material Master Upload program by using Direct Input Method where we are also submitting the report to upload the data in SAP Database.

Thanks in Advance!
Ramkumar.K

Hi Kumar,
Thanks! I am using submit statement in my program as well but its populating all the views like Sales Organization Data, Sales - General / Plant Data, Accounting, and all the other views except the Basic Data View.. Eventhough i have populated the corresponding fields of the same.
I am also using structure BGR00, BMM00, BMMH1 to upload the data
Can you please help me on this..

Regards,
Ramkumar.K

XI 3.0 - XML - IDOC inbound scenario via ftp UTF-8 character encoding

Hi Everyone,
I'm having difficulties with a particular scenario. I receive via the ftp adapter xml files which have a header indicating UTF-8 coding. In SXMB_MONI, i see the cyrillic characters and after mapping the target message payload as well have readable cyrillic characters. The problem comes when i have the SAP-side check the idoc that posted in their system. They see gibberish (i.e ##### #### ### #').
I have already tried changing the XSD definition of the xml to UTF-8 however upon import it automatically changes it to ISO-8859-1. I've tested sending the xml file to XI with an ISO-8859-1 coding header and in SXMB_MONI it's gibberish as well. So i've elminated that from possible problems.
i have checked SM59 on the receiving system and unicode is checked as well.
where could the problem possibly be?
Thank you,
Kent

Hi,
Thank you for the quick reply. however that did not solve it. I believe the Cyrillic character set lies in the UTF-8 set. i mentioned about the ISO to elmiinated its possibility and the problem i face when importing an XSD definition as it automatically changes the encoding to that set. I have confirmed that it should be UTF-8.
I have isolated the problem to between the XI box and the SAP receiving box. in SXMB_MONI, up to the call adapter part, the payload shows the correct characters. upon checking it in the receiving system at tcode "we02", the value is all gibberish.

UTF-8 character encoding not working in Firefox

I have a jPlayer playlist that works fine in all browsers except Firefox.
The issue is with non-standard characters, i.e. characters with accents or asian characters. I have set up a demo playlist so that you can see [http://monthlymixup.com/mixups/july_2012/index.php here].
When I enter the characters in UTF-8 form (track 1 in the playlist) they work on all browsers except for Firefox, and when I enter them in ISO Latin 1 (track 2 in the playlist) they work in Firefox but no other browsers.
So, for instance in Firefox å¤§å°æ¸æ¿.mp3 works, whereas 大地書房.mp3 doesn't.
There is a meta tag for UTF-8 on the demo page, i.e.
My understanding is that Firefox overwrites this with the response header if a default encoding isn't set in FF. I have however set UTF-8 to be the default encoder and I have checked that the page is using UTF-8 by going to Tools/Page Info (I am on a Mac and I believe this is the way to check the encoding on the page).
So, I'm at a loss as to what is going on, and would be glad of some help.

No time to register at the moment...
Are you specifying the titles and file names in your JavaScript code as on this jPlayer demo page? http://jplayer.org/latest/demo-02/

Soem help on lsmw using direct input for mm01

hi,
this is to srinivas.i have done all the steps u have given.but at the step...convert data it is showing soem error msg.the error is
sytax error in prgm in include in line 68.for type "C",max length specification of 65535 is allowed.thanx in advance....

Hi Praveen,
the steps i was given you is working fine.
i just check the entire process
where did you got error.
I think in 6th step you just create fixes values,Translations & User-defined routines
ans delete all you have done at 6th step then the cursor goes to 7th step.
please let me know any error.
thanks & regards
Sreenivasulu P

Special character "/" replacing with blank with Direct Input Method posting

Hi All,
I am posting FI historical data using Direct Input Method. Payment term contains special character "/"( I/E). SAP standard program replacing Special character "/" with blank (I E) so document posting is failing. Could you please advise.
Thanks
Chandra.

Can You please specify the Transaction code and SAP program name for direct input.

Which character encoding do Adobe ExportPDF use when converting to word document?

Which character encoding do Adobe ExportPDF use when converting to word document?

Hi Ram,
Sorry for the long delay. I've been trying to track down this answer for you.
We're using UTF-8 character encoding for our files.
-David

LSMW for equipment creation-Standard Batch/Direct Input

Hi,
We developed an LSMW with standard batch / direct input method for creating equipment masters.
We used Object =0400 ( equipment ) and method = 0001 ( batch input)
We maintained source structures and source fileds. In the source field , we maintained only those fields that we need from table IBIPEQUI but in the order given in this structure.
Also we maintained filed mapping and field convertion rules for the above source fields.
When we run LSMW step - Display converted data , we see that
Transactions Read:                   1
Records Read:                          1
Transactions Written:                0
Records Written:                       0
Not sure what could have gone wrong?
Please provide some clues to the following questions.
1) Should the source structure be same as fields from stuc. IBIPEQUI and should it include all the fields in the source structure?
2) Is field mapping required or not ?
3) We are getting an error - transaction is not supported in direct input mode.
Thanks in advance
Rgds,
Rajesh

1. Source fields are( same as IBIPEQUI structure ; the tab delimited file matches with these fields)
TCODE                          C(020)    Transaction Code
RECORDNAME                     C(008)    Record name
EQUNR                          C(018)    Equipment
DATSL                          C(008)    Valid On
EQTYP                          C(001)    Equipment category
EQKTX                          C(040)    EQKTX
BEGRU                          C(004)    Authorization Group
EQART                          C(010)    Technical obj. type
GROES                          C(018)    Size/dimensions
INVNR                          C(025)    Inventory number
BRGEW                          C(017)    Gross Weight
GEWEI                          C(003)    Weight unit
ELIEF                          C(010)    Vendor
ANSDT                          C(008)
ANSWT                          C(017)    Acquisition Value
WAERS                          C(005)    Currency
HERST                          C(030)    Manufacturer
HERLD                          C(003)    Country of manufact.
BAUJJ                          C(004)    Construction year
BAUMM                          C(002)    Construction month
TYPBZ                          C(020)    Model number
SERGE                          C(030)    ManufSerialNumber
MAPAR                          C(030)    ManufactPartNo.
GERNR                          C(018)    Serial number
GWLEN                          C(008)    Warranty end date
KUND1                          C(010)    Customer
KUND2                          C(010)    End customer
KUND3                          C(010)    Operator
SWERK                          C(004)    Maintenance plant
STORT                          C(010)    Location
MSGRP                          C(008)    MSGRP
BEBER                          C(003)    Plant section
ARBPL                          C(008)    Work center
ABCKZ                          C(001)    ABC indicator
EQFNR                          C(030)    Sort field
BUKRS                          C(004)    Company Code
ANLNR                          C(012)    Asset Number
ANLUN                          C(004)    ANLUN
GSBER                          C(004)    Business Area
KOSTL                          C(010)    Cost Center
PROID                          C(024)    PROID
DAUFN                          C(012)    Standing order
AUFNR                          C(012)    Order
TIDNR                          C(025)    Technical IdentNo.
SUBMT                          C(018)    Construction type
HEQUI                          C(018)    Superord. Equipment
HEQNR                          C(004)    Position
EINZL                          C(001)    Single installation
IWERK                          C(004)    Planning plant
INGRP                          C(003)    Planner group
GEWRK                          C(008)    Main work center
WERGW                          C(004)    Plant for WorkCenter
RBNR                           C(009)    Catalog profile
TPLNR                          C(030)    Functional Location
DISMANTLE                      C(001)    DismIndic.
VKORG                          C(004)    Sales Organization
VTWEG                          C(002)    Distribution Channel
SPART                          C(002)    Division
MATNR                          C(018)    Material
SERNR                          C(018)    BOM explosion number
WERK                           C(004)    WERK
LAGER                          C(004)    LAGER
CHARGE                         C(010)    CHARGE
KUNDE                          C(010)
KZKBL                          C(001)    Load records
PLANV                          C(003)    PLANV
FGRU1                          C(004)    FGRU1
FGRU2                          C(004)    FGRU2
STEUF                          C(004)    Control key
STEUF_REF                      C(001)    STEUF_REF
KTSCH                          C(007)    Standard text key
KTSCH_REF                      C(001)    Std text referenced
EWFORM                         C(006)    EWFORM
EWFORM_REF                     C(001)    EWFORM_REF
BZOFFB                         C(002)    Ref. date for start
BZOFFB_REF                     C(001)    BZOFFB_REF
OFFSTB                         C(007)    Offset to start
EHOFFB                         C(003)    Unit
OFFSTB_REF                     C(001)    OFFSTB_REF
BZOFFE                         C(002)    Ref. date for finish
BZOFFE_REF                     C(001)    BZOFFE_REF
OFFSTE                         C(007)    Offset to finish
EHOFFE                         C(003)    Unit
OFFSTE_REF                     C(001)    OFFSTE_REF
WARPL                          C(012)    Maintenance Plan
IMRC_POINT                     C(012)    Measuring point
INDAT                          C(008)    Inverse date
INTIM                          C(006)    Processing time OC Workbe
INBDT                          C(008)    Start-up date
GWLDT                          C(008)    Guarantee
AULDT                          C(008)    Delivery date
LIZNR                          C(020)    License number
MGANR                          C(020)    Master warranty
REFMA                          C(018)    REFMA
VKBUR                          C(004)    Sales Office
VKGRP                          C(003)    Sales Group
WARR_INBD                      C(001)    Inbound warranty
WAGET                          C(001)    Warranty inheritance poss
GAERB                          C(001)    Indicator: Pass on warran
ACT_CHANGE_AA                  C(001)    ACT_CHANGE_AA
STRNO                          C(040)    STRNO
DATLWB                         C(008)    Date Last Goods Movmnt
UII                            C(072)    UII
IUID_TYPE                      C(010)    IUID Type
UII_PLANT                      C(004)    Plant Responsible for UII
2, source structure is assigned to target structure IBIPEQUI
3. In the assign files step - all settings given above are correctly maintained.
4. Field mapping
TCODE                        Transaction Code
                    Rule :   Default Settings
                    Code:    IBIPEQUI-TCODE = 'IE01'.
RECORDNAME                   IBIP: Name of the Data Transfer Record
                    Rule :   Default Settings
                    Code:    IBIPEQUI-RECORDNAME = 'IBIPEQUI'.
EQUNR                        Equipment Number
                    Source: ZIE01_002_SOURCE-EQUNR (Equipment)
                    Rule :   Transfer (MOVE)
                    Code:    if not ZIE01_002_SOURCE-EQUNR is initial.
                               IBIPEQUI-EQUNR = ZIE01_002_SOURCE-EQUNR.
                             endif.
DATSL                        Date valid from
                    Source: ZIE01_002_SOURCE-DATSL (Valid On)
                    Rule :   Transfer (MOVE)
                    Code:    if not ZIE01_002_SOURCE-DATSL is initial.
                               IBIPEQUI-DATSL = ZIE01_002_SOURCE-DATSL.
                             endif.
EQTYP                        Equipment category
                    Source: ZIE01_002_SOURCE-EQTYP (Equipment category)
                    Rule :   Transfer (MOVE)
                    Code:    if not ZIE01_002_SOURCE-EQTYP is initial.
                               IBIPEQUI-EQTYP = ZIE01_002_SOURCE-EQTYP.
                             endif
When I read data with 1 record uploaded ( in the assign fields step , I did not choose "fields names at start of file" and also saved the file with tab delimited text format without field names), it shows as
Transactions Read:                    2
Records Read:                         2
Transactions Written:                 2
Records Written:                      2
I uploaded only one record but it reads as 2 records and can not figure out why 2 records?
Also when I checked display converted data , it shows 2 records .
First record shows
TCODE         Transaction Code                                             IE01
RECORDNAME    IBIP: Name of the Data Transfer Record                       IBIPEQUI
EQUNR         Equipment Number
DATSL         Date valid from                                              05072010
EQTYP         Equipment category                                           H
EQKTX         Description of technical object                              PNEUMATIC PIPE BENDER
BEGRU         Technical object authorization group
EQART         Type of Technical Object                                     MECH-PRESS
GROES         Size/dimension                                               1000X500X1500MM
INVNR         Inventory number
BRGEW         Gross Weight     : IBIP Character Structure                  50
GEWEI         Weight Unit                                                  KG
ELIEF         Vendor number
ANSDT         Acquisition date
ANSWT         Acquisition Value: IBIP Character Structure
All the fields following this , are blank.
2nd record shows
TCODE         Transaction Code                                             IE01
RECORDNAME    IBIP: Name of the Data Transfer Record                       IBIPEQUI
EQUNR         Equipment Number                                             2009
DATSL         Date valid from
EQTYP         Equipment category                                           S
EQKTX         Description of technical object                              1006324
BEGRU         Technical object authorization group
EQART         Type of Technical Object
GROES         Size/dimension                                               20100406
uploaded values are jumbled in 1st and 2nd record.
Hope to receive your valuable ideas for finding out the reason and corrective action required.
Rgds,
Rajesh
I
Edited by: Rajesh63 on Jul 6, 2010 10:37 PM

Character Encoding for IDOC to JMS scenario with foreign characters

Dear Experts,
The scenario is desribed as follows:
Issue Description:
There is an IDOC which is created after extracting data from different countries (but only one country at a time). So, for instance first time the data is picked in Greek and Latin and corresponding IDOC is created and sent to PI, the next time plain English and sent to PI and next Chinese and so on. As of now every time this IDOC reaches PI ,it comes with UTF-8 character encoding as seen in the IDOC XML.
I am converting this IDOC XML into single string flat file (currently taking the default encoding UTF-8) and sending it to receiver JMS Queue (MQ Series). Now when this data is picked up from the end recepient from the corresponding queue in MQ Series, they see ? wherever there is a Greek/latin characters (may be because that should be having a different encoding like ISO-8859_7). This is causing issues at their end.
My Understanding
SAP system should trigger the IDOC with the right code page i.e if the IDOC is sent with Greek/Latin code page should be ISO-8859_7, if this same IDOC is sent with Chinese characters the corresponding code page else UTF-8 or default code page.
Once this is sent correctly from SAP, Java Mapping should have to use the correct code page when righting the bytes to outputstream and then we would also need to set the right code page as JMS Header before putting the message in the JMS queue so that receiver can interpret it.
Queries:
1. Is my approach for the scenario correct, if not please guide me to the right approach.
2. Does SAP support different code page being picked for the same IDOC based on different data set. If so how is it achieved.
3. What is the JMS Header property to set the right code page. I think there should be some JMS Header defined by MQ Series for Character Encoding which I should be setting correctly) I find that there is a property to set the CCSID in JMS Receiver Adapter but that only refers to Non-ASCII names and doesn't refer to the payload content.
I would appreciate if anybody can give me pointers on how to resolve this issue.
Thanks,
Pratik

Hi Pratik,
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42?quicklink=index&overridelayout=true
This link might help.
regards
Anupam

Using Direct Input mode: UTF-8 character encoding assumed

Similar Messages

Maybe you are looking for