Can i know what are the thumb rules of sap r/3

hi,
sap gurus,
good afternoon to all,
can i know what are the list of thumb rules of sap r/3.
plz
regards,
balaji.t
09990019711

Hi,
Please Follow link
http://www.dbis.ethz.ch/research/publications/19.pdf
Thanks,
Raja

Similar Messages

What are the prerequisites to monitor SAP ENVIROMENT with grid control

anybody know what are the prerequisites to monitor SAP ENVIROMENT with grid control
its necessary another software
thanks

There's currently no way to monitor a whole SAP system through gridcontrol. Of course you can monitor the underlying database.
Werner

Is there any way I can know what are the list of patches installed on Indesign Server CS5

Hi All,
Is there any way I can know what are the list of patches installed on Indesign Server CS5?
Please let me know if the there is any command to do so.
Thanks,
Manjunath

Is this link any help?
http://www.btvision.bt.com/on-demand/?cat=filmclub
It seems to give the film club info.
If you sort the list by "ending" date, shoul should be able to find recently added ones.
There are some useful help pages here, for BT Broadband customers only, on my personal website.
BT Broadband customers - help with broadband, WiFi, networking, e-mail and phones.

What are the conversion rules

what are the conversion rules?can anybody give information on that?points wil be rewarded?

hI..
From sap help....
Conversion Rules for Elementary Data Types
There are ten predefined ABAP data types. There are 100 possible type combinations between these elementary data types. ABAP supports automatic type conversion and length adjustment for all of them except type D (date) and type T (time) fields which cannot be converted into each other.
The following conversion tables define the rules for converting elementary data types for all possible combinations of source and target fields.
C D F I N P STRING T X XSTRING
Source Type Character

Conversion table for source type C
Target
Conversion
C
The target field is filled from left to right. If it is too long, it is filled with blanks from the right. If it is too short, the contents are truncated from the right.
D
The character field must contain an 8-character date in the format YYYYMMDD .
F
The contents of the source field must be a valid representation of a type F field as described in Literals.
N
Only the digits in the source field are copied. The field is right-justified and filled with trailing zeros.
I, P
The source field must contain the representation of a decimal number, that is, a sequence of digits with an optional sign and no more than one decimal point. The source field can contain blanks. If the target field is too short, an overflow may occur. This may cause the system to terminate the program.
STRING
The occupied length of the source field is copied. All trailing spaces are truncated.
T
The character field must contain a six-character time in HHMMSS format.
X
Since the character field must contain a hexadecimal string, the only valid characters are 0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F. This string is packed as a hexadecimal number, transported left-justified, and filled with zeros or truncated on the right.
XSTRING
As for fields of type X, except that the target field is not filled with zeros.
Source Type Date
Conversion table for source type D
Target
Conversion
C
The date is transported left-justified without conversion.
D
Transport without conversion.
F
The date is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The date is transported left-justified without conversion and, if necessary, filled with zeros on the right.
I, P
The date is converted to the number of days since 01.01.0001.
STRING
The date is converted to a character field, which is then converted to a character string.
T
Not supported. Results in an error message during the syntax check or in a runtime error.
X
The date is converted to the number of days since 01.01.0001 in hexadecimal format.
XSTRING
As for fields of type X, except that only significant bytes are copied.
Source Type Floating Point Number
Conversion table for source type F
Target
Conversion
C
The floating point number is converted to the <mantissa>E<exponent> format and transported to the character field. The value of the mantissa lies between 1 and 10 unless the number is zero. The exponent is always signed. If the target field is too short, the mantissa is rounded. The length of the character field must be at least 6 bytes.
D
The source field is converted into a packed number. The packed number is then converted into a date field (see corresponding table).
F
Transport without conversion.
N
The source field is converted into a packed number. The packed number is then converted into a numeric text field (see corresponding table).
I, P
The floating point number is converted to an integer or fixed point value and, if necessary, rounded.
STRING
As for fields of type C, except that the maximum number of places is used for the mantissa (maximum precision). Despite this, different signs or exponents can lead to different string lengths.
T
The source field is converted into a packed number. The packed number is then converted into a time field (see corresponding table).
X
The source field is converted into a packed number. The packed number is then converted into a hexadecimal number (see corresponding table).
XSTRING
As for fields of type X, except that leading zeros are not copied.
Source Type Integer
Type I is always treated in the same way as type P without decimal places. Wherever type P is mentioned, the same applies to type I fields.
Source Type Numeric Text
Conversion table for source type N
Target
Conversion
C
The numeric field is treated like a character field. Leading zeros are retained.
D
The numeric field is converted into a character field. The character field is then converted into a date field (see corresponding table).
F
The numeric field is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The numeric field is transported right-justified and filled with zeros or truncated on the left.
I, P
The numeric field is interpreted as a number, and transferred to the target field, where it is right-justified, and adopts a plus sign. If the target field is too short, the program may be terminated.
STRING
As for fields of type C. The length of the character string matches the length of the numeric text.
T
The numeric field is converted into a character field. The character field is then converted into a time field (see corresponding table).
X
The numeric field is converted into a packed number. The packed number is then converted into a hexadecimal number (see corresponding table).
XSTRING
As for fields of type X, except that leading zeros are not copied.
Source Type Packed Number
If the program attribute Fixed point arithmetic is set, the system rounds type P fields according to the number of decimal places or fills them out with zeros.
Conversion table for source type P
Target
Conversion

C
The packed field is transported right-justified to the character field, if required with a decimal point. The last position is reserved for the sign. Leading zeros appear as blanks. If the target field is too short, the sign is omitted for positive numbers. If this is still not sufficient, the field is truncated on the left. ABAP indicates the truncation with an asterisk (*). If you want the leading zeros to appear in the character field, use UNPACK instead of MOVE.
D
The packed field value represents the number of days since 01.01.0001 and is converted to a date in YYYYMMDD format.
F
The packed field is accepted and transported as a floating point number.
N
The packed field is rounded if necessary, unpacked, and then transported right-justified. The sign is omitted. If required, the target field is filled with zeros on the left.
I, P
A packed field is converted to type I. The resulting four bytes are placed into the target field right-justified. If the target field is too short, an overflow occurs. If the target field is longer, it is filled with zeros on the left.
STRING
As for fields of type C, except that leading zeros are not generated.
T
The packed field value represents the number of seconds since midnight and is converted to a time in HHMMSS format.
X
A packed field is converted to type I. The resulting four bytes are placed into the target field right-justified and in big-endian format. If the target field is too short, it is truncated from the left. If the target field is longer than 4, it is filled with zeros on the left. Negative numbers are represented by the two's complement (= bit complement +1).
XSTRING
As for fields of type X, except that leading zeros are not generated.
Source Type String
Conversion table for source type STRING
Target
Conversion
C
The target field is filled from left to right. If it is longer than the string, it is filled with trailing spaces. If it is too short, the contents are truncated from the right.
D
The string must contain an 8-character date in the format YYYYMMDD .
F
The contents of the string must be a valid representation of a type F field as described in Literals.
N
Only digits in the string are copied. The field is right-justified and filled with trailing zeros. If the target field is too short, it is truncated from the left.
I, P
The string must contain the representation of a decimal number, that is, a sequence of digits with an optional sign and no more than one decimal point. The source field can contain blanks. If the target field is too short, an overflow may occur. This may cause the system to terminate the program.
STRING
The source string is copied to the target string unconverted.
T
The string must contain a six-character time in HHMMSS format.
X
Since the character field must contain a hexadecimal-character string, the only valid characters are 0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F. This character string is packed as a hexadecimal number, transported left-justified, and filled with zeros or truncated on the right.
XSTRING
As for target fields of type X, except that the field is not filled with zeros.

Source Type Time
Conversion table for source type T
Target
Conversion
C
The source field is transported left-justified without conversion.
D
Not supported. Results in an error message during the syntax check or in a runtime error.
F
The source field is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The date is converted into a character field. The character field is then converted into a numeric text field (see corresponding table).
I, P
The date is converted to the number of seconds since midnight.
STRING
The time is converted to a character field, which is then converted to a character string.
T
The date is transported left-justified without conversion and, if necessary, filled with zeros on the right.
X
The date is converted to the number of seconds since midnight in hexadecimal format.
XSTRING
As for fields of type X, except that only significant bytes are copied.
Source Type Hexadecimal Field
Conversion table for source type X
Target
Conversion
C
The value in the hexadecimal field is converted to a hexadecimal character string, transported left-justified to the target field, and filled with zeros.
D
The source field value represents the number of days since 01.01.0001 and is converted to a date in YYYYMMDD format.
F
The source field is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The source field is converted into a packed number. The packed number is then converted into a numeric text field (see corresponding table).
I, P
The value of the source field is interpreted as a hexadecimal number. It is converted to a packed decimal number and transported right-justified to the target field. If the hexadecimal field is longer than 4 bytes, only the last four bytes are converted. If it is too short, a runtime error may occur.
STRING
As for target fields of type C, except that the field is not filled with zeros. The length of the string is twice the length of the hexadecimal field.
T
The source field value represents the number of seconds since midnight and is converted to a time in HHMMSS format.
X
The value is transported left-justified and filled with X'00' on the right, if necessary.
XSTRING
The hexadecimal field is copied completely that is, trailing zeros are not truncated.
Source Type Byte Sequence
Conversion table for source type XSTRING
Target
Conversion
C
The value in the byte sequence is converted to a hexadecimal character string, transported left-justified to the target field, and filled with zeros.
D
The byte sequence value represents the number of days since 01.01.0001 and is converted to a date in YYYYMMDD format.
F
The content of the byte sequence is converted into a packed number. The packed number is then converted into a floating point number (see corresponding table).
N
The content of the byte sequence is converted into a packed number. The packed number is then converted into a numeric text field (see corresponding table).
I, P
The content of the byte sequence is interpreted as a hexadecimal number. It is converted to a packed decimal number and transported right-justified to the target field. If the byte sequence is longer than 4 bytes, only the last four bytes are converted. If it is too short, a runtime error may occur.
STRING
As for target fields of type C, except that the field is not filled with zeros. The length of the string is twice the length of the byte sequence.
T
The byte sequence value represents the number of seconds since midnight and is converted to a time in HHMMSS format.
X
The byte sequence is transported left-justified and filled with X'00' on the right, if necessary.
XSTRING
The source byte sequence is copied to the target byte sequence unconverted.
Conversion Rules for Internal Tables
Internal tables can only be converted into other internal tables. You cannot convert them into structures or elementary fields.
Internal tables are convertible if their line types are convertible. The convertibility of internal tables does not depend on the number of lines.
Conversion rules for internal tables:
Internal tables which have internal tables as their line type are convertible if the internal tables which define the line types are convertible.
Internal tables which have line types that are structures with internal tables as components are convertible according to the conversion rules for structures if the structures are compatible.
Conversion Rules for Structures
ABAP has one rule for converting structures that do not contain internal tables as components. There are no conversion rules for structures that contain internal tables. You can only make assignments between structures that are compatible.
You can combine convertible structures in the following combinations:
Converting a structure into a non-compatible structure
Converting elementary fields into structures
Converting structures into elementary fields
In each case, the system first converts all the structures concerned to type C fields and then performs the conversion between the two resulting elementary fields. The length of the type C fields is the sum of the lengths of the structure components. This rule applies to all operations using structures that do not contain internal tables.
If a structure is aligned, the filler fields are also added to the length of the type C field.
A non-aligned structure without filler fields:
If you convert a structure into a shorter structure, the original structure is truncated. If you convert a structure into a longer one, the parts at the end are not initialized according to their type, but filled with blanks.
It can make sense to assign a structure to another, incompatible, structure if, for example, the target structure is shorter than the source, and both structures have the same construction over the length of the shorter structure. However, numeric components of structures that are filled in incompatible assignments may contain nonsensical or invalid values that may cause runtime errors.
DATA: BEGIN OF FS1,
INT TYPE I VALUE 5,
PACK TYPE P DECIMALS 2 VALUE 2.26,
TEXT(10) TYPE C VALUE Fine text,
FLOAT TYPE F VALUE 1.234e+05,
DATA TYPE D VALUE 19950916,
END OF FS1.
DATA: BEGIN OF FS2,
INT TYPE I VALUE 3,
PACK TYPE P DECIMALS 2 VALUE 72.34,
TEXT(5) TYPE C VALUE Hello,
END OF FS2.
WRITE: / FS1-INT, FS1-PACK; FS1-TEXT, FS1-FLOAT, FS1-DATE.
WRITE: / FS2-INT, FS2-PACK, FS2-TEXT.
MOVE FS1 TO FS2.
WRITE: / FS2-INT, FS2-PACK, FS2-TEXT.
Message was edited by:
Rammohan Nagam

How to know what are the T Codes used by client in SAP HR module in qualit

hi experts,
i have a access of quality server given by my client in SAP HR.I dont know what are the Tcodes used by client.So how i can know what are the Tcodes client is using frequently.i have to list out all TCodes urgently.
PLZ reply ASAP.
Thanx in advance..

Hi
You can do this by going to SUIM-Transactions-Executable for User
Then give the user name/id as in user master record and execute. Now the system will display the list of transaction codes used by that particular user.
Regards
Santhosh.S

What are the supported Macintosh Operating System versions for IBM SPSS Statistics 18,19 and 20? Question I would like to know what are the supported Macintosh Operating system versions for IBM SPSS Statistics versions 18, 19 and 20? Answer Please see

What are the supported Macintosh Operating System versions for IBM SPSS Statistics 18,19 and 20?
Question
I would like to know what are the supported Macintosh Operating system versions for IBM SPSS Statistics versions 18, 19 and 20?
Answer
Please see the list below:
- IBM SPSS Statistics 18 and 19 releases are supported on Apple Macintosh OS 10.5 (Leopard) and 10.6 (Snow Leopard) with Intel processor.
- IBM SPSS Statistics 20 release is supported on Apple Macintosh OS 10.6 (Snow Leopard) and 10.7 (Lion) with Intel processor.
- The IBM SPSS Statistics versions 18 and 19 are not supported on Mac OS 10.7 (Lion).
THIS MEANS THAT TO USE LION ONE FIRST HAS TO UPGRADE TO SPSS STATISTICS 20.

Whilst the 2012-02-15 edition of IBM's matrix does not mention Lion, a few users have noted that:
• 18.0 can be troublesome
• an updated version of 18.x should be better.
Related files
PASWStatistics_1 803_Mac_Patch.dmg and IBM SPSS Statistics 18.0.3.4 Hotfix Mac.zip are no longer available from the spss.com domain, and I could not find them in an IBM domain. If you download from unofficial sources, proceed with caution.
Related pages
In Apple Support Communities:
• will PASW (SPSS) 18 work with LION
• PASW statistics 18 crashes every time
• Java Virtual Machine & SPSS 18 with a question from me.
Elsewhere:
• SPSS on Lion « Decorator Pattern
• SPSS / PASW Mac Patch 18.0.3 and Graphing Fix | The Personal Website of Philip Fizur
• Patching PASW 18 (or SPSS 18) for Mac OS X (Leopard, Snow Leopard, Lion) to version 18.0.3.1
• and other sources, including one domain that I treat as reputable but I'll respectfully not share that link here.
At a glance, you might find that 18.0.3.4 is compatible with Lion.

Hi, my name is Laith I'm from Iraq I just want to know what are the steps for buying a new iphone 5 from apple store and how to ship it to Iraq ???? and I would be grateful for you

hi, my name is Laith I'm from Iraq I just want to know what are the steps for buying a new iphone 5 from apple store and how to ship it to Iraq ???? and I would be grateful for you

Legality aside (I'm not a lawyer and have no opinion on the matter) in order to make a purchase of an iPhone 5 you would need to travel to a country where they are for sale and purchase it there. Be sure to get one that is officially unlocked or you would not be able to use it with your cell carrier. Be sure that your carrier supports use of the iPhone before you buy. Also note that the warranty of the iPhone is only valid in the country of purchase.
Appe does not ship outside of the countries where it sells the phones.

How can L identify what are the not null fields of a table in a stored procedure ?

How can L identify what are the not null fields of a table in a stored procedure ?

You could query the data dictionary:
SELECT column_name
FROM all_tab_columns
WHERE owner = '...'
AND table_name = '...'
AND nullable = 'N'

Hi this pandu can i know what is the diff between pnp &pnpce ldb

hi,
this pandu can i know what is the diff between pnp &pnpce logical database.
thanks and regards,
pandu.

pretty much the same.. except that PNPCE has additional functionality to deal with Concurrent Employment.. PL go through <a href="http://help.sap.com/saphelp_erp2005/helpdata/en/c6/8a15381b80436ce10000009b38f8cf/frameset.htm">SAP Help</a> for more info.
~Suresh

Can I know what is the process for us to do Good Return from customer?

Can I know what is the process for us to do Good Return from customer?

hi
this ques need to be posted in sd forum..
to answer this u can use order type RE to create Return order and then u can do the goods receipt..
or u can use the process mentioned in first reply.
regards
CMM

Who can tell me what are the functions of the following subdirectories?

Who can tell me what are the functions of the following subdirectories? How are they classified?
oracle@hostp ~$ cd $ORACLE_HOME
oracle@hostp db_1$ ls
{color:#0000ff}
assistants demo jdbc network oui slax
bin diagnostics jdk nls owm sqlj
cdata has jlib oc4j perl sqlnet.log
cfgtoollogs hostp_db10g jre odbc plsql sqlplus
clone hostp_rcatalog ldap olap precomp srvm
config hs lib OPatch racg sysman
crs install log opmn rdbms uix
css {color:#000000}install.platform{color} md oracore relnotes wwg
ctx inventory mesg oraInst.loc {color:#ff6600}root.sh{color} xdk
dbs javavm mgw {color:#ff6600}ord root.sh.old{color}
{color}
dbs javavm mgw ord root.sh.old

Hi,
Here we go:
- assistants:      configuration Assistants
- bin:      binaries for all products
- ctx:      interMedia Text cartridge
- dbs :     contain initsid.ora, lksid (initiation files, password files,etc)
- instal:l      install related files
- lib:      Oracle product libraries
- jlib:      Java classes
- md:      Spatial cartridge
- mlx      Xerox: Stemmer (for interMedia Text cartridge)
- network:      Net8
- nlsrtl :      NLS run-time loadable data
- ocommon:      common files for all products
- odg:      data gatherer
- opsm:      Parallel Server Manager Components
- oracore:      core libraries
- ord:      data cartridges
- otrace:      Oracle TRACE
- OPatch: Patches to the DB
- plsql :     PL/SQL
- precomp:      precompilers
- rdbms :      server files and libraries required for the database
- slax:      SLAX parser
- sqlplus :     SQL*Plus
For more Information you can refer to:
- http://www.stanford.edu/dept/itss/docs/oracle/10g/em.101/b12140/3_oui_oracle_homes.htm
- http://www.dba-oracle.com/linux/important_files_directories.htm
Cheers,
Francisco Munoz Alvarez
http://www.oraclenz.com

How to know what are the privs for one custom schema?

how to know what are the privs for one custom schema?
please suggest me......

Hi,
Check this user_sys_privs
Cheers
Pavan Kumar N

HT4718 why did not i get installation CD with my mac book retina display 13", and let me know what are the tings i get with my mac book pro with free of cost?

why did not i get installation CD with my mac book retina display 13", when i bought. and let me know what are the tings i get with my mac book pro with free of cost?

MacBook Pro
http://store.apple.com/us/buy-mac/macbook-pro
What’s in the box.
MacBook Pro
Power adapter, AC wall plug, and power cord
No install media (CDs or DVDs) are included with Macs anymore.

Recently bought a MacBook Pro And sometimes Delete key is detached (loose). I would like to know what are the steps to take to repair it?

Recently bought a MacBook Pro And sometimes Delete key is detached (loose). I would like to know what are the steps to take to repair it?

If it is within the warranty period, take it in to an Apple store genius bar for repair.
Ciao.

What are the master Data in SAP SD

Hi All,
I have a question. Even though its a naive question please bear with me.
what are the master data in SAP SD.
These are the one's i know.
1) Customer Master Data
2) Material Master Data
But what i want to know is does the following ones come under master data?
1) Price master data
2) Transporters master data(we are using transportation management)
3) Route master data
4) Customer material info records
5) Credit master data(iam using credit management)
What will be the master data for Transportation management(module), CIN(country India version), credit management & rebate processing
Thanks for your valuable time & knowledge.
Regards,
Pavan

Hi Pavan,
 Just to add some more valuable information.
Organisational master data : Every company is structured in a certain way. In order to work with the SAP System your company structure has to be represented in the system. This is done with the help of various organizational structures.
Condition master data : In sales and distribution, products are sold or sent to business partners or services are performed for them. Data about the products and services as well as about the business partners is the basis for sales processing. Sales processing with the SAP R/3 System requires that the master data has been stored in the system.
Material master data : In addition to sales and distribution, other departments of the company such as accounting or materials management access the master data. The material master data is stored in a specific structure in order to allow access from these different views.
Document master data : The processing of business transactions in sales and distribution is based on the master data. In the SAP R/3 System, business transaction are stored in the form of documents. These sales and distribution documents are structured according to certain criteria so that all necessary information in the document is stored in a systematic way.
Customer Master Data : or for that matter various business partners, we maintain data for them also called as the customer master data or vendor master data like that.
Thanks & Regards
Sadhu Kishore

Can i know what are the thumb rules of sap r/3

Similar Messages

Maybe you are looking for