Regarding type c

hi,
i have defined a input field " type c "for the selection screen in which the user can write his name ,after giving the name in the lower case when i press enter it will converted to upper case why this is happening as i m passing this variable to smartforms there it is also showing in upper case which i dont want,plz help me....i want the name in the same name as i enter in the selection screen ........
Message was edited by:
ravi

Hi,
PARAMETERS: p_name TYPE c LOWER CASE.
use this it will work.
Reward points if useful.
Regards,
Vimal

Similar Messages

Variant to data: Need info regarding type of data

Hello,
What I want to do is very basic. I will acquire the image using CCD camera. The
image is a raw data type: 2D array of type long (4 bytes per element) or integer (2 bytes per element). I can save the image even as .tiff file. Using Variant To Data, I am converting the image so that labview can handle it (I am not sure whether I really need this) before I write that data to some file and save it. I have to define data type for Variant To Data. I tried to define the data type. However, I am confused. Would anybody give me some suggestion?
Thanks a lot,
Dushyant

Hrm, you'll need to be more specific about your actual question in order for us to give you a good answer, but, without more information, I'd say you should just define the type as a 2-d array of either longs or words. (i.e. get an array constant, place a numeric constant inside of it, right click the numeric constant, and select Representation->Long or Representation->Word then wire the constant to the Type input of the Variant to Data).
If you're dealing with variants, I'd guess you are probably calling an ActiveX control or server to communicate with your camera?
Regards,
Ryan K.

Regarding types statement in ECC 6.0...plz reply..urgent

Hi,
I am copying a program which is in 4.7 to ECC 6.0,i am facing error regarding structures with types...
The following code in 4.7
DATA:BEGIN OF W_BMM00.
 INCLUDE STRUCTURE BMM00.
DATA:END OF W_BMM00.
DATA:BEGIN OF W_BMMH1.
 INCLUDE STRUCTURE BMMH1.
DATA:END OF W_BMMH1.
DATA:BEGIN OF W_BMMH7.
 INCLUDE STRUCTURE BMMH7.
DATA:END OF W_BMMH7.
DATA : BEGIN OF TAB_TLINE OCCURS 0.
 INCLUDE STRUCTURE TLINE.
DATA : END OF TAB_TLINE.
i have written the same in ECC6.0 as below
TYPES:BEGIN OF tw_bmm00.
 INCLUDE STRUCTURE bmm00.
TYPES:END OF tw_bmm00 ,
 tt_bmm00 TYPE STANDARD TABLE OF tw_bmm00.
TYPES:BEGIN OF tw_bmmh1.
 INCLUDE STRUCTURE bmmh1.
TYPES:END OF tw_bmmh1 ,
 tt_bmmh1 TYPE STANDARD TABLE OF tw_bmmh1.
TYPES:BEGIN OF tw_bmmh7.
 INCLUDE STRUCTURE bmmh7.
TYPES:END OF tw_bmmh7 ,
 tt_bmmh7 TYPE STANDARD TABLE OF tw_bmmh7.
TYPES:BEGIN OF tw_TAB_TLINE.
 INCLUDE STRUCTURE TLINE.
TYPES:END OF tw_TAB_TLINE,
 tt_tab_tline TYPE STANDARD TABLE OF tw_tab_tline.
lw_bmm00 TYPE tw_bmm00,
 lt_bmm00 TYPE tt_bmm00,
 lw_bmmh1 TYPE tw_bmmh1,
 lt_bmmh1 TYPE tt_bmmh1,
 lw_bmmh7 TYPE tw_bmmh7,
 lt_bmmh7 TYPE tt_bmmh7,
 lw_tab_thead TYPE tw_tab_thead,
 lt_tab_thead TYPE tt_tab_thead,....
when i check SLIN errors i am getting the following errors...plz resolve..
The current ABAP command is obsolete
Within classes and interfaces, you can only use "TYPE" to refer to ABAP Dictionary
types (not "LIKE" or "STRUCTURE").


include strture not allowed.
rules.
ABAP Development under Unicode
Prior to Unicode the length of a character was exactly one byte, allowing implicit typecasts or memory-layout oriented programming. With Unicode this situation has changed: One character is no longer one byte, so that additional specifications have to be added to define the unit of measure for implicit or explicit references to (the length of) characters.
Character-like data in ABAP are always represented with the UTF-16 - standard (also used in Java or other development tools like Microsoft's Visual Basic); but this format is not related to the encoding of the underlying database.
A Unicode-enabled ABAP program (UP) is a program in which all Unicode checks are effective. Such a program returns the same results in a non-Unicode system (NUS) as in a Unicode system (US). In order to perform the relevant syntax checks, you must activate the Unicode flag in the screens of the program and class attributes.
In a US, you can only execute programs for which the Unicode flag is set. In future, the Unicode flag must be set for all SAP programs to enable them to run on a US. If the Unicode flag is set for a program, the syntax is checked and the program executed according to the rules described in this document, regardless of whether the system is a US or a NUS. From now on, the Unicode flag must be set for all new programs and classes that are created.
If the Unicode flag is not set, a program can only be executed in an NUS. The syntactical and semantic changes described below do not apply to such programs. However, you can use all language extensions that have been introduced in the process of the conversion to Unicode.
As a result of the modifications and restrictions associated with the Unicode flag, programs are executed in both Unicode and non-Unicode systems with the same semantics to a large degree. In rare cases, however, differences may occur. Programs that are designed to run on both systems therefore need to be tested on both platforms.
Other Changes
1. Bit Statements
2. Adding Field Sequences
3. Loops with VARY and VARYING
4. Creating Subroutines
5. Saving Programs
6. Assigning Types for GET/SET PARAMETER
7. Unreachable Statements
8. Function Modules with Incorrect Parameter Names
1. Bit Statements
Previously, the system checked for the bit statements SET BIT i OF f [TO g] and GET BIT i OF f [INTO g]whether the field f is character-type; X fields, X strings, and flat structures are usually regarded as character-type. For Unicode programs this is no longer useful, because the types X and XSTRING no longer count as character-type and the bit by bit access to character-type fields or structures is no longer platform-independent. Therefore, with these operations in Unicode programs, the field f must be type X or XSTRING.
For the bit mask operations f O x, f Z x, and f M x you could previously use all number-type and hence all character-type types for the left operand f. In Unicode programs, the f operand must now be type X or XSTRING.
2. Adding Field Sequences
When adding field sequences, restrictions apply to the following statements in Unicode:
ADD n1 THEN n2 UNTIL nz [ ACCORDING TO sel ] GIVING m ...
ADD n1 THEN n2 UNTIL nz TO m [ RANGE str ].
1. The operands n1, n2, and nz must be type-compatible with one another.
2. The distance between nz and n1 must be an integral multiple of the distance between n2 and n1.
3. A syntax or runtime error occurs if the fields n1, n2, and nz are not in a structure. This structure must be recognizable statically or its valid area must be marked explicitly using the RANGE addition.
4. At runtime, the system ensures that the RANGE area is not left.
ADD n1 FROM i1 GIVING m [ RANGE str ].
1. Field n1 must be within the structure. The structure must be explicitly defined using the RANGE addition if it is not recognizable statically.
2. For this variant, the system also checks at runtime whether n1 and the addressed values are within the structure.
3. Loops
Loops with the VARY or VARYING addition are also problematic in Unicode, since a type-a access to memory contents cannot be ensured and memory can be overwritten inadvertently.
DO ... VARYING f FROM f1 NEXT f2.
For this statement, the fields f, f1, and f2 must be type-compatible with each other. To prevent memory contents being overwritten, a RANGE for valid accesses is introduced implicitly or explicitly for the following statements:
DO ... TIMES VARYING f FROM f1 NEXT f2 [ RANGE f3 ].
WHILE ... VARY f FROM f1 NEXT f2 [ RANGE f3 ].
A syntax or runtime error is caused if f1 or f2 are not included in f3. If the RANGE addition is missing, it is defined implicitly from FROM f1 NEXT f2 as follows:
1. If both f1 and f2 are statically recognizable components of the same structure, the valid RANGE area is defined from the smallest structure that comprises f1 and f2.
2. A syntax error is triggered if it is recognizable statically that f1 and f2 are not part of the same structure.
3. A valid area must be defined explicitly using the RANGE addition if the connection between f1 and f2 is not recognizable statically.
If you specify a deep structure as the RANGE addition, the system checks for every loop pass that there are no field references, object references, tables, or strings in the area read.
4. Creating Subroutines
When automatically generating subroutines using the statement GENERATE SUBROUTINE POOL itab NAME name, the generated program inherits the content of the Unicode flag of the generating program.
5. Saving Programs
When automatically generating programs using the statement INSERT REPORT prog FROM itab, default values are set for the TRDIR entry as before. Amongst other things, this statement has the new addition UNICODE ENABLING uc, with which the Unicode flag of the inserted report receives the value of uc. If this addition is missing, the following applies:
1. A Unicode program creates a Unicode program.
2. A non-Unicode program in turn creates a non-Unicode program.
3. A non-Unicode program becomes a Unicode program if it is overwritten by a Unicode program.
4. A Unicode program remains a Unicode program if it is overwritten by a non-Unicode program.
6. Assigning Types for GET/SET PARAMETER
For the statements GET PARAMETER ID pid FIELD f and GET PARAMETER ID pid FIELD f, f must be character-type. You can use the EXPORT and IMPORT statements for storing non-character-type fields and structures.
7. Unreachable Statements
In Unicode programs, unreachable statements cause a syntax error. In non-Unicode programs, there was previously only a syntax warning.
8. Function Modules with Incorrect Parameter Names
In Unicode programs, calling a function module, whose parameter names are specified statically as a literal or constant, causes an exception that can be handled if an incorrect parameter name was specified. This only applies to function modules that are not called via Remote Function Call. In non-Unicode programs, an incorrect name was previously ignored.
http://service.sap.com/instguides
--> SAP Business Suite Applications
--> SAP ERP
--> mySAP ERP 2005
--> Upgrade
--> Upgrade Documentation - mySAP ERP 2005 SR2
There choose your database and operating system.
If you're looking for functional details check
http://service.sap.com/releasenotes

Regarding Types of reports

Hi friends
Help me to find the tutorial for ABAP Reports(Types and their applications)

Hi Friend,
Programs that can be run
These programs can be run by a user by entering the program name or a transaction code. They are they actual application programs within the R/3 System, and are explained in more depth later on.
Type 1
You can start a type 1 program by entering its program name. For this reason, they are also known as executable programs. When you start a type 1 program, processors are started in the runtime environment that call a series of processing blocks (event blocks) in a predefined sequence. The sequence is oriented towards reporting tasks. This is why executable programs are also known as reports. For further information, refer to Running Programs Directly - Reports.
A special type of type 1 program is a logical database. You can start logical databases together with reports. A logical database contains subroutines that are called by an invisible system program in a prescribed sequence for type 1 programs. The subroutines make certain reporting functions reusable. For further information, refer to Logical Databases.
Type M
Type M programs can only be started using a transaction code. A transaction code starts a screen, which consists of the screen itself and its flow logic. Screen flow logic can call special processing blocks (dialog modules) in the corresponding ABAP program. Since type M programs contain mostly dialog modules, they are known as module pools. For further information about running module pools, refer to Dialog-controlled Program Execution - Transactions.
Programs that Cannot Be Run Directly
These programs cannot be started directly by a user. Instead, they contain processing blocks or other source code that can only be used by an application program that is already running. They are described in more detail in a later section.
Type F
Type F programs are not executable. They serve as a container for function modules. When you call a function module from an ABAP program, the entire main program is loaded into the internal session of the current program. Since type M programs contain mainly function modules, they are known as function groups. Function modules are a type of procedure. They are described in more detail in the Procedures section.
Type K
Type K programs are not executable. They are container programs for global classes, and are known as class definitions. Classes belong to ABAP Objects and are described in more detail in that section.
Type J
Type J programs are not executable. They are container programs for global interfaces, and are known as interface definitions. Interfaces belong to ABAP Objects and are described in more detail in that section.
Type S
Type S programs are not executable. They are container programs for subroutines that should only be called externally. When you call a subroutine from an ABAP program, the entire main program is loaded into the internal session of the current program. Since type S programs contain mainly subroutines, they are known as subroutine pools. Subroutines are a type of procedure. They are described in more detail in the Procedures section.
Type I
Type I programs cannot be run directly, and contain no callable processing blocks. They are used exclusively for modularizing ABAP source code, and are included in other programs. Include programs are described in more detail in the Source Code Modules section.
Reward point, if helpful.
Regards,
Atin

Regarding types of bridging/bridges

Hi All,
I'm reading Richard Deals book for my CCNA. While i was re-reading the bridging part. I came across the below shaded lines.
Do we still use such types of bridges/bridging methods ? Is it useful to dig into understand these type of bridging operations too not only for my ccna but also for my networking knowledge?
Can someone please explain ?
Thanks in advance.
Regards,
Chandu

I don't think it's very common today as IP and Ethernet have taken almost all of the market. Cisco devices support fallback bridging and IRB.
Fallback bridging:
http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/12.2_35_se/configuration/guide/swfallbk.pdf
This can be used to bridge between routed ports or SVIs for non routable traffic from legacy protocols.
IRB:
http://www.cisco.com/en/US/tech/tk389/tk815/technologies_tech_note09186a0080094663.shtml
IRB can be used to bridge on some interfaces and also route traffic for remote networks.
One application could be to bridge VLANs towards a firewall and still route traffic for other networks.
Daniel Dib
CCIE #37149
Please rate helpful posts.

Regarding types

HI after upgrade iam using an include in my program
where iam getting and syntax error stating
In Unicode, DESCRIBE LENGTH can only be used with the IN BYTE MODE or
IN CHARACTER MODE addition.
FOR THE BELOW CODE IN THE INCLUDE.
DATA: L_LENGTH TYPE I.
DESCRIBE FIELD L_MSGTX LENGTH L_LENGTH.

4.7 and above Ver:
describe field pdf_data length v_length in byte mode.
Byte Mode is an addition in Unicode system (4.7).Byte mode will generally give the length in bytes
1 Character holds one byte and an integer is of 4 bytes.
There is anther addition also character mode which is used for flat and character types.
4.6b Ver:
describe field pdf_data length v_length.
It is for non unicode system.this will not work in unicode systems.(i.e4.7).
It will give you also lenght in bytes.
Only difference is Unicode and Non-Unicode system..
Hope this will resolve your query.
Regards,
Gurpreet

Regarding "TYPES & "CONVERSION ROUTINES"............

Hi abapers,
Can we have a code snippet as given below,
TYPES : NUMB TYPE I VALUE 100.
DATA : NUM1 TYPE NUMB.
WRITE : / NUMB, NUM1.
what will be the output?. Will the value 100 be copied to the field NUM1?
Next question is regarding "conversion routines". I read that "conversion routines" can be assigned to fields(variables) in abap?. What are "conversion routines"? What are their purpose? Also explain me the purpose of "EDIT MASK"?
Thanks in advance.
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Jun 27, 2008 1:29 PM

Hi,
Conversion Routine..
I will just give you an example.....
For us in user interface English language is EN... but for system it is Just 'E'...
There conversion will happen from user to system and while retrieving from system to user..
So there are two routines for that.
CONVERSION_EXIT_ <conversion routine name> _OUTPUT
CONVERSION_EXIT_ <conversion routine name> _INPUT.
These coversion routines do the conversion job
check this link..
http://help.sap.com/saphelp_erp2004/helpdata/en/33/206bc8012e11d3b495006094192fe3/content.htm
Hope this would help you..
Regards
Narin Nandivada.

Regarding type of file

hi,
which function module is used to know type of file(like DAT,TXT,ASCII...).
Thanks & Regards,
Rajani.

Hi Rajni,
The Function Module FILE_GET_NAME will give the logical file path, fromwhich you can know the file type, I think.
Just check it out.
Thanks and regards
Vipin Das

Regarding Type of the RFC Connections

Hi Experts,
While We r Creating the RFC Destination in SM 59,
When We will Create the Connection Type as --3
--H
--T
Can Any body Please explain When to go for which connection Type.....
Regards
Khanna

Hi Rajesh,
Type 3 ABAP Connection :
ex 1) If we want to execute any function module from one SAP system in another , we need type 3.
We define an RFC destination say ECC6CLNT100 with required parameters.
and to test it go to SE37, select any common sap function module and when you execute that it will ask for RFC destination. you provide this destination and the function module will be executed in the target system.
ex2) when you create a partner profile, you need to create a port and for creating a port, we need to specify an RFC destination. here also we use type 3.
Type H.
ex1) when we need to send xml messages from an SAP system to any other system, we need this.
For example when we send messages using proxy from SAP system to the integration engine of XI, we need type H.
Type T.
ex1) To we make an RFC call from R/3 to XI , we use sender RFC adapter in XI.
In R/3 system we need to create an RFC destination of type T.
Rajesh, I hope it answers all your queries.
& dont forget to award SDN points..:)
Regards
Pushkar

Regarding: type pools

hello sir,
slis_fieldcat_alv
slis_T_fieldcat_alv
what it means, what is the difference between those two
i am expecting tour replay

slis_fieldcat_alv is a structure
slis_t_fieldcat_alv is internal table which has structure of slis_fieldcat_alv
goto se11 -> type group : SLIS
find : slis_fieldcat_alv then slis_T_fieldcat_alv.
Addition :
slis_T_fieldcat_alv
1. encapsulate slis_fieldcat_alv structure.
2. this is the one that you should pass when you call REUSE_ALV_LIST_DISPLAY (one of function to build alv report)
slis_fieldcat_alv = it's a structure for internal use to build slis_T_fieldcat_alv.
regards,
sandi
Message was edited by: Sandi Wijaya

Data regarding types of erros

Hi All,
Can anyone give me the data and error codes of all types of errors occurs in CANOPEN functions.
Thanks in advance

There is only a small number of errors defined with the CANopen functions. You can find thye file attached. It comes with the driver. Normaly you would face normal NI-CAN errors which are defined within the NI-CAN help.
DirkW
Attachments:
CANOPEN-ERRORS.TXT ‏1 KB

Regarding types of projects

what is a rollout project?

The only thing that differentiates implimentation to Roll-out is,
say for ex: your client has business units in more than 1 country/location. the country/location where the strategic business consuting is done, business rules are based,gap analysis if done, requirements are mapped into SAP implimentations blue prints are drawn for the impliementation, the company code which is the basis of entire company's business logic, meaning in which ever country the first implementtaion is done..its implementation, but extending same rules and processes and mapping the same to other countries/location it would thn be called roll-out.
say, first you impliment in ex: COCA COLA,USA...it wld be implmentation, then you extend to COCACOLA ,India its wld be called ROLL-OUT.
ex: NAGARJUNA CEMENTS first implementation then extend the same to NAGARJUNA FERTILISERS.
the key thing is it is a roll-out only if there are similarities in business logic...ex: in HR side the employee groups etc.
ROLL-OUT projects are relatively easy, as u already have referencable data in the system to check incase u want to check, how it was done. especially rules in payroll,,its easier to look n copy.
Check this document:
http://www.open.hr/hiz/hrusko/RolloutPresCASE3.pdf
Regards.
Edited by: Sravan Prakash.V on Jan 11, 2008 11:37 AM

Regarding type group

HI Friends please help me on what is type group urgently.

Type Groups
Type groups or type pools are created using the ABAP Dictionary tool and are introduced with the TYPE-POOL statement. They may not contain any screens of their own or any processing blocks. Type groups are exclusively used as containers for global data types which can be made visible in any ABAP program using the TYPE-POOLS statement.
TYPE-POOL
Basic form
TYPE-POOL typepool.
Effect
Introduces a type group. You can only maintain a type group via the ABAP/4 Dictionary (using Transaction SE11 ). The name typepool must match the name in the ABAP/4 Dictionary . You can only define types and constants in type groups. The names of all these types and constants must begin with the name of the type group and an underscore.
Example
TYPE-POOL ABCDE.
TYPES: ABCDE_PACKED TYPE P,
ABCDE_INT TYPE I.
TYPE-POOLS
Basic form
TYPE-POOLS typepool.
Effect
Includes the types and constants of a type group. If the type group typepool has already been included, the statement is ignored. You can only maintain a type group via the ABAP/4 Dictionary (using Transaction SE11 ). You introduce a type group with the TYPE-POOL statement. Since the types and constants specified in a type group have global validity, you cannot use the statement within a FORM or FUNCTION .
Example
TYPE-POOLS VERI1.
DATA X TYPE VERI1_TYP1.
reward points if it is usefull ...
Girish

Types Reports

Hi
Could any body send the information regarding Types of reports(How many types of reports is there and what is it )
Anser 'll be rewarded.
Regards
Satya.
Message was edited by:
satya G

You can have Web report, RRI and Regular report.
chk:
BI 7.0 reporting features
http://searchsap.techtarget.com/cgi-bin/rd.pl/ftID-1121728-ctID-1064004?//expert/KnowledgebaseAnswer/0,289625,sid21_gci1064004,00.html
mastering SAP BW Reporting:
http://www.researchsummary.ca/bw/Sample_Ch10.pdf
Also check:
Good Knowledge in BW Reporting
https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/a8cd1f71-0a01-0010-4783-f119b6132d25 [original link is broken]
Hope it helps.
Regards

Types of Background jobs

Hi,
Can anybody pl tell me the difference between Scheduled Job and Released job in background processing. Or send me some doc regarding types of background jobs.
Thanks...
Hardik

There are two ways to schedule a job from a program:
1. the "express" method using the BP_JOBVARIANT_SCHEDULE function module
2. the "full-control" method using the JOB_OPEN, JOB_SUBMIT, and JOB_CLOSE function modules.
With this method, you have full control over such job options as printing, start time options, and so on.
To schedule a job from within a program using the express method, you need only call the BP_JOBVARIANT_SCHEDULE function module.
With BP_JOBVARIANT_OVERVIEW, you can offer your users a simplified display and management function for their "express-method" jobs.
call function 'BP_JOBVARIANT_SCHEDULE'
exporting
title_name = 'Documentation Check' " Displayed as title of
" of scheduling screens
job_name = 'DocuCheck' " Name of background
" processing job
prog_name = 'RSTWGZS2' " Name of ABAP
" report that is to be
" run -- used also to
" select variants
exceptions
no_such_report = 01. " PROG_NAME program
" not found.
call function 'BP_JOBVARIANT_OVERVIEW' " List the jobs that
exporting " have been scheduled
title_name = 'Documentation Check' " Displayed as title
" of overview screen
job_name = 'DokuCheck' " Jobs with this name
" are listed
prog_name = 'RSTWGZS2'
exceptions
no_such_job = 01.
For further information check the link below
http://help.sap.com/saphelp_nw2004s/helpdata/en/c4/3a80eb505211d189550000e829fbbd/frameset.htm

Regarding type c

Similar Messages

Maybe you are looking for