WHAT ARE CONVERSIONS?

Hi
Conversion Rules for References
ABAP currently uses class and interface variables within ABAP Objects. Both are pointers to objects. You can assign values to them in the following combinations:
If the two class references are incompatible, the class of the target field must be the predefined empty class OBJECT.
When you assign a class reference to an interface reference, the class of the source field must implement the interface of the target field.
If two interface references are incompatible, the interface of the target field must contain the interface of the source field as a component.
When you assign an interface reference to a class reference, the class of the source field must be the predefined empty class OBJECT
simply refer to this link
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3427358411d1829f0000e829fbfe/content.htm
Reward if usefull

Similar Messages

What are Conversions and Extensions

Hey ,
I want to know what are Conversions and Extensions. Can i get any material where i can get information on these.
Thanks in advance

The conversion programs were used to take the extract data from the legacy system and re-format for SAP and load the data into SAP.
Conversions are one-time programs used to transfer data from the legacy system into SAP. For example, you can transfer master data like vendors, customers etc.
SAP provides enhancement to BAPIs thru EXTENSION IN AND EXTENSION OUT .these are structure parameters.suppose example: one BAPI released to update the mara table.then u modified the table mara thru append structure.this changes will not be reflected in BAPIs.So thats why in that case we have to use EXTENSION IN AND EXTENSION OUT structures to fill and work.

Hi What are topics involved in Interfaces,Conversions in ABAP?

Please Explain me.
Thank u in advance

Actually I am asking What are Interfaces?
What are Conversions in the sense of ABAP?
mean WE r using BDC for transferring from legacy to SAP, Does this a conversion technique?
Edited by: Srinivasa RAo on Oct 8, 2009 10:15 PM

What are the special conversions for time in update rules?

What are the special conversions for time in update rules?

Hello,
Special conversions for time in update rules are automatically conversion rules.
Example: If the cube contains calendar month and your transfer structure contains date, the date to month is converted automatically.
Assign points if this helps,
Regards,
Jorge Diogo

What are the content conversion parameters

Hi All
This link contains the text file.
http://www.census.gov/foreign-trade/schedules/d/dist.txt
what are the content conversion parameters are required to convert that text to xml.

<sen_dt>
 <prefix>
 <heads>
 <dc>
 <pc>
 <name>
 <main>
 <dcno>
 <pcno>
 <name1>
<rec_dt>
 <prefix>
 <District_code> District code optional
 <port_code> port code 1
 <name> name
 <main>
 <District_code_no>
 <port_code_no>
 <name1>
content conversion
 document name:<sen_dt>
 document namespace:http::----
 document offset:--
 recordset name:input
 recordset structure:heads,1,main,*
 recordset sequence:Ascending
 recordset per message:----
 keyfield name:---
prefix.fieldfixedlengths:---
prefix.endSeparator:---
prefix.fieldNames;---
prefix.keyFieldvalue:--
prefix.keyFieldlnStructure:---
main.fieldFixedLengths:9,
main.fieldSeparator:|
main.endSeparator:'nl'
main.fieldNames:district code,port code,name
main.keyFieldValue:
main.keyFieldlnStructure:

What are the content conversion parameters for this structure

Hi All,
The below file is the text file. what are the content conversion parameters are required and what is the structure to create in the IR to convert into xml.
Schedule D - District/Port List (by District Code) [Produced13APR11]
District |    Port      |    Name
Code     |    Code      |
01       |              |    PORTLAND, ME
         |    0101      |    PORTLAND, ME
         |    0102      |    BANGOR, ME
         |    0103      |    EASTPORT, ME
         |    0104      |    JACKMAN, ME
         |    0105      |    VANCEBORO, ME
         |    0106      |    HOULTON, ME
         |    0107      |    FORT FAIRFIELD, ME
         |    0108      |    VAN BUREN, ME
         |    0109      |    MADAWASKA, ME
         |    0110      |    FORT KENT, ME
         |    0111      |    BATH, ME
         |    0112      |    BAR HARBOR, ME
         |    0115      |    CALAIS, ME
         |    0118      |    LIMESTONE, ME
         |    0121      |    ROCKLAND, ME
         |    0122      |    JONESPORT, ME
         |    0127      |    BRIDGEWATER, ME
         |    0131      |    PORTSMOUTH, NH
         |    0132      |    BELFAST, ME
         |    0152      |    SEARSPORT, ME
         |    0181      |    LEBANON AIRPORT
         |    0182      |    MANCHESTER USER FEE AIRPORT, NH
02       |              |    ST. ALBANS, VT
         |    0201      |    ST. ALBANS, VT
         |    0203      |    RICHFORD, VT
         |    0206      |    BEECHER FALLS, VT
         |    0207      |    BURLINGTON, VT
         |    0209      |    DERBY LINE, VT
         |    0211      |    NORTON, VT
         |    0212      |    HIGHGATE SPRINGS/ALBURG

since in this case you dont seem to have a key value to figure out what your header is, it is better to go for a two level mapping. i.e first read all the data - each line as an xml tag. and in the first mapping group it as required and then use it for your original mapping.
Regards,
Ninu

What are the right content conversion parameter in this receiver ?

Hi experts,
Can someone help me with setting right Content conversion parameter in the Receiver of File adpater(FCC).The output file must be fixed length text file.
Here is the receiver structure:
<Recordset>
 <Header>
 <f1>01</f1>
 <f2> </f2>
 <f3> </f3>
 </Header>
 <Body>
 <SubBody1>
 <field1 />
 <field2 />
 <field3 />
 <field4 />
 <field5 />
 </SubBody1>
 <SubBody2>
 <field6 />
 <field7 />
 <field8 />
 <field9 />
 <field10/>
 </SubBody2>
 </Body>
 <Trailer>
 <f1>03</f1>
 <f2> </f2>
 <f3> </f3>
 </Trailer>
</Recordset>
Also Body can occure multiple times in the file but still will have this structure...Header and Trailer can occure only once in file.
What are the right content conversion perameters in this case?
Appreciate your help asap!T
Thanks
Jon

<Recordset>
 <Header>
 <f1>01</f1>
 <f2> </f2>
 <f3> </f3>
 </Header>
 <Body>
 <SubBody>
 <field1 />
 <field2 />
 </SubBody>
 <SubBody>
 <field1 />
 <field2 />
 </SubBody>
 <SubBody>
 <field1 />
 <field2 />
 </SubBody>
 </Body>
 <Trailer>
 <f1>03</f1>
 <f2> </f2>
 <f3> </f3>
 </Trailer>
</Recordset>
if this is the input structure then FCC goes like this ....
Recordset:Header,Body,SubBody,Trailer
Header.fieldFixedLengths 10,20,30.. (based on you are structure fixed lengths)
Header.endSeparator - 'nl'
SubBody.fieldFixedLengths 10,20,20 (based on you are structure fixed lengths)
Body.endSeparator - 'nl'
Trailer.fieldFixedLengths 10,20,30.(based on you are structure fixed lengths)
Trailer.endSeparator - 'nl'
We might have to try out SubBody.endSeparator - 'nl' if Body.endSeparator - 'nl' does not insert a new line after each body record.
Cheer's

What are the most challenging conversions in Oracle apps...

Can any one tell me what are the most challenging conversions in oracle apps.
Thanks
Sambit

d1acf245-8019-40c9-a1df-fdc9374b36b2 wrote:
Can any one tell me what are the most challenging conversions in oracle apps.
Thanks
Sambit
https://forums.oracle.com/message/10705767
Thanks,
Hussein

What are the MMO3 CONVERSIONS AVAILABLE and o know?what's the logic t

Hi Experts ,
Could you plz tell me, what are the mm03 conversions?
My requitement is i have to convert the Quantity into PC,LM and M2.
Before that i have to check wether the quantity has the conversions availble in
mmo3. could you plz give me idea.
Thanks
Suresh.

question is not clear MMO3 is used to display material

What are forms, interfaces, conversions and enhancements?

Hello Experts,
Please enlighten me on what are those terms. Any examples would be highly appreciated. Thanks guys and take care!

hi ,
Forms :
1. They r Client Independent.
2. It contains more than one main window.
3. Multiple layout is possible in smart form.
4. Colors can be given in script form.
5. Function modules can be generated automatically.
6. background is possible.
coming up to an Interface:
Interface is a system or a device that is used to connect two unrelated or non-understanding entities.
This definition to an interface could be the key to your answer.
As you might already know, Interface does not provide any implementation but just defines a set of protocols that can be implemented by any class.
Let us consider a few examples...
You and the bicycle. Both of you are not related in anyway. But you want to ride the bicycle. How do you interact with the bicycle? You do it via the pedal which is an interface between you and the bicycle.
You could extend this concept to 'You' and the 'Television' where the interface is a remote control.
conversions :
SAP provides a conversion for SAPscript documents to SMARTforms.
This is basically a function module, called FB_MIGRATE_FORM. You can start this function module by hand (via SE37), or create a small ABAP which migrates all SAPscript forms automatically.
You can also do this one-by-one in transaction SMARTFORMS, under
Utilities -> Migrate SAPscript form.
You could also write a small batch program calling transaction SMARTFORMS and running the migration tool.
Enhancements :
CMOD is the Project Management of SAP Enhancements (i.e., SMOD Enhancements). SMOD contains the actual enhancements and CMOD is the grouping of those SMOD enhancements.
User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a function module. The code for the function module is written by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.
The naming standard of function modules for function module exits is:
EXIT_<program name><3 digit suffix>
The call to a functionmodule exit is implemented as:
CALL CUSTOMER.-FUNCTION <3 digit suffix>
For Example:
The program for transaction VA01 Create salesorder is SAPMV45A
1. If you search for CALL CUSTOMER-FUNCTION program SAPMV45A you will find ( Among other user exits):
CALL CUSTOMER-FUNCTION '003'
exporting
 xvbak = vbak
 xvbuk = vbuk
 xkomk = tkomk
importing
 lvf_subrc = lvf_subrc
tables
 xvbfa = xvbfa
 xvbap = xvbap
 xvbup = xvbup.
The exit calls function module EXIT_SAPMV45A_003
2. How to find user exits
Display the program where you are searching for and exit and search for CALL CUSTOMER-EXIT
If you know the Exit name, go to transaction CMOD. Choose menu Utillities->SAP Enhancements.
Enter the exit name and press enter.
You will now come to a screen that shows the function module exits for the exit.
or use this ABAP program to search for user exits :-
Finding the user-exits of a SAP transaction code
3. Using Project management of SAP Enhancements
You want to create a project to enhance transaction VA01
- Go to transaction CMOD
- Create a project called ZVA01
- Choose the Enhancement assign radio button and press the Change button
In the first column enter V45A0002 Predefine sold-to party in sales document . Note that an enhancement can only be used for 1 project. If the enhancement is allready in use, and error message will be displayed
- Press Save
- Press Components. You can now see that enhancement uses user exit EXIT_SAPMV45A_002.
- Double Click on the exit.
Now the function module is displayed. Double click on include ZXVVAU04 in the function module
Insert the following code into the include: E_KUNNR = '2155'.
Activate the include program. Go back to CMOD and activate the project.
Goto transaction VA01 and create a salesorder. Note that Sold-to-party now automatically is "2155"
if u find tht its an helpful answer dont forget to reward points for it.
with regards,
madhuri

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

What is Data conversion ? What are data conversion programs ? please give

What is Data conversion ? What are data conversion programs ? please give me some sample code?

Hi,
I think you mean "Data Acquisition"...
"The Data Acquisition IT process allows you to connect heterogeneous sources (SAP systems, database management systems, files, relational data, multidimensional data) to BI. You can transfer data straight into BI from the source or use SAP NetWeaver XI to transfer data. Furthermore, the process supports direct access to source data, without having to load it into BI."
http://help.sap.com/saphelp_nw04s/helpdata/en/aa/1fb042e745ca6ae10000000a155106/frameset.htm
[Data AcquisitionTechniques in SAP NetWeaver BI|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/329fcd87-0c01-0010-4a9c-86f038e11d23]
Regards
Andreas

G10 Aperture RAW conversion: what are your impressions?

the wait is over!
2.4 RAW Compatibility update includes Canon G10.
what are your impressions?
what Aperture settings yield best results?
how do they compare to Camera RAW and DPP?

When you compare photos that were photographed at ISO 100 they all do a good job. When you stat going up in the ISO is where I think Aperture does a great job. I've attached a screen capture of the same photos processed with 3 different applications. No adjustments were added to the photos. The default settings were used then the photo was passed on to photoshop as a Tiff. I think it's clear why I don't like ACR. Aperture and DPP are much closer. DPP has some noise reduction on by default so the photo looks like it has less noise then Aperture. I feel that the default noise reduction just makes the photo look a little soft and out of focus. If I turn off the default noise reduction in DPP the photo looks noisy. So I like Aperture better because of the way the noise looks, the sharpness and detail of the photo. Another area to look at is the neck and chest area. Aperture holds the most amount of detail before blowing out. I know that all 3 programs have adjustments that will help fix the problems in the photo. Even after doing that to the photo in all 3 programs I still felt that Aperture was clearly better. As the previous poster said it is subjective to each persons taste.
I've never used this way of posting a screen grab so if it doesn't work forgive me. Make sure to click on the photo to view the large file.

What are the importent transaction codes in edi

what are the importent transaction codes in edi

hi,
=>sale - ALE Customizing
=>bale - Distribution Administration (ALE)
=>wedi - IDOC Type and EDI Basis
=>shdb - BDC (Transaction Recorder)
=>lsmw - LSMW
=>bapi - BAPI
=>spau - Display Modified DE Objects
=>spdd - Display Modified DDIC Objects
=>sara - central idoc archiving
=>stms - Transport Management System
=>wedi - IDOC Type and EDI Basis (IDOC Configuration)
=>bd21 - Analyze change pointers - create IDOC from change pointer
=>bd10 - Send Material Master
=>bd12 - Send Customer Master
=>bd14 - Send Vendor Master
=>bd50 - Activate Change Pointer for Message Type
=>bd55 - Conversion rule user exit (Link conversion rule user exit to the different system \ partner combinations)
=>bd54 - Maintain Logical Systems
=>bd71 - Distribute Customer Model
=>bd87 - Process Inbound IDOCs
=>bd88 - Process Outbound IDOCs
=>bdm2 - Cross-system IDOC Reporting
=>bdm7 - ALE Audit - statistical analyses
=>bdm8 - ALE Audit - sending confirmations
=>bd61 - Activate Change Pointer generally
=>bmv0 - Direct Input Data Transfer Administration
=>rz04 - Operation Mode
=>rz12 - RFC Server Group Maintenance
=>sar3 - Archiving object customizing
=>s001 - SAPoffice Inbox
=>s010 - Standards Texts (SAP Script)
=>se01 - Transport Organizer (Extended View - Performing and managing the transport of development object across different systems)
=>se09 - Transport (Workbench) Organizer (Controlling and keeping track of Development work and Development Objects)
=>se78 - Administration of Form Graphics (Import Graphics into SAP System)
=>se84 - ABAP Repository Information (search for SAP objects)
=>su01 - User Maintenance (Security)
=>su02 - Maintain Authorization Profiles
=>su03 - Maintain Authorizations
=>sm36 - Background Job Scheduling
=>sm37 - Background Job Monitoring (display batch jobs)
=>sm31 - Table Maintenance
=>sm30 - Calling View Maintenance
=>sm35 - Batch Input Monitoring (Error Logs)
=>sm50 - Process Overview
=>sm58 - Transactional RFC Monitoring
=>sm59 - Maintain RFC Destinations (Define RFC Configuration)
=>snro - Number Range Objects (for IDOCs)
=>we02 - Display IDOC
=>we05 - IDOC lists
=>we07 - IDOC statistics
=>we12 - Inbound processing of outbound file - convert outbound to inbound file
=>we14 - Process (dispatch) IDOCs through Port - RSEOUT00
=>we15 - Outbound IDOC from NAST - message control
=>we16 - Inbound File
=>we18 - Generate status file
=>we19 - Test tool
=>we20 - Add new Message Type to Partner Profile
=>we21 - Maintain Port Definition
=>we30 - IDOC Type development
=>we31 - IDOC Segment development
=>we41 - Process Code Outbound
=>we42 - Process Code Inbound
=>we46 - IDoc Administration
=>we47 - Status Code Maintenance
=>we57 - Assign function module to logical message and IDoc type
=>we63 - IDOC Type for Parser Output
=>we82 - Assign IDOC to Message Type
=>we60 - IDOC Documentation - IDOC Types
=>we61 - IDOC Documentation - IDOC Record Types
=>we81 - Create new IDOC Message Types
=>we82 - Assign IDOC to Message Type
=>pa20 - Display HR Master Data
=>pa30 - Maintain HR Master Data
=>bd59 - Create and assign Filter Object Type for Message Type
=>bd64 - Maintenance of ALE or any other Distribution Model
Hope this helps, Do reward.

What are all the fields covered in the Raw file received from the Card Co

Hi Experts,
I want to know what are all the fields covered in the Raw file received from the credit card company say AMEX before uploading the data into ASP system i.e. CCD format file to be uploaded in T-Code PRCC
Some of the fields I know:
1.     Name of the Employee
2.     Company ID
3.     Credit card number
4.     Currency
5.     Amount
6.     Exchange rate
7.     Date of Transaction
8.     Description
9.     Document no.
10.     Expense type
11.     Expenses paid by company
Waiting for a positive response from your side
Regards,

Hi
The below mention is the possible values/records will be received from Banks regarding credit card expenses
ORGANIZATION / HIERARCHY HEADER RECORD
FIELD NAME
RECORD TYPE
TYPE INDICATOR
COMPANY NAME
COMPANY ID
SUB COMPANY ID
EFFECTIVE / FILE DATE
CCF VERSION
COMPANY NUMBER
TRANSACTION POSTING DATE START
TRANSACTION POSTING DATE END
FILLER
TRX CONTROL DATA
ORGANIZATION / HIERARCHY DETAIL RECORD
FIELD NAME
RECORD TYPE
TYPE INDICATOR
COMPANY ID
SUB COMPANY ID
CORP PARENT NODE
CORP CHILD NODE
PAST DUE BUCKETS RECORD
FIELD NAME
RECORD TYPE
TYPE INDICATOR
COMPANY ID
SUB COMPANY ID
STATEMENT DATE
AMOUNT PAST DUE
30 DAYS PAST DUE
60 DAYS PAST DUE
90 DAYS PAST DUE
120 DAYS PAST DUE
150 DAYS PAST DUE
180 DAYS PAST DUE
180 PLUS DAYS PAST DUE
PREVIOUS BALANCE
FILLER
TRX CONTROL DATA
CARDHOLDER HIERARCHY RECORD
FIELD NAME
RECORD TYPE
TYPE INDICATOR
COMPANY ID
SUB COMPANY ID
NODE ID
ACCOUNT NUMBER
FILLER
TRX CONTROL DATA
ACCOUNT HEADER RECORD 1
FIELD NAME
RECORD TYPE
TYPE INDICATOR
COMPANY ID
SUB COMPANY ID
PROCESSOR
ACCOUNT NUMBER
ACCOUNT TYPE
LAST NAME
CARDH FIRST NAME
CARDH MIDDLE NAME
ADDRESS LINE1
ADDRESS LINE2
ADDRESS LINE3
ADDRESS LINE4
ADDRESS LINE5
CITY
STATE / COUNTY/ PROVINCE
POSTAL CODE
COUNTRY
NATIONAL ID
TELEPHONE NUMBER
WORK PHONE NUM
ID VERIFICATION CODE
DATE OF BIRTH
CYCLE CODE
FAX NUMBER
E MAIL ADDRESS
EMPLOYEE ID
CLIENT ID / CUSTOMER NUMBER
CUSTOMER VAT NUMBER
TITLE
STMT DATE
GENDER
FILLER
TRX CONTROL DATA
MAIN TRANSACTION RECORD
FIELD NAME
RECORD TYPE
TYPE INDICATOR
COMPANY ID
SUB COMPANY ID
CBS TR RUN DATE
ACCOUNT NUMBER
TRANS DATE
TRANS TIME
POST DATE
FILLER
AUTH REQUIRED
AUTH ID
CONVERS DATE
POS ENTRY
POS COND CODE
ACQUIRER ID
REFERENCE NUM
TRACE NUMBER
FILLER
TRANS ID
MCC
MCC INFO DATA
MERCH ACCEPTOR ID
MERCH DESCRIPTION
MERCHANT CITY
MERCHANT STATE / PROVINCE
MERCHANT POSTAL CODE
MERCH COUNTRY
MERCHANT VAT NUMBER
MERCH DESC FLAG
MERCHANT REFERENCE NUMBER
SOURCE CURRENCY
SOURCE AMOUNT
BILLING CURRENCY
BILLING AMOUNT
SETTLEM CURRENCY
SETTLEM AMOUNT
US DOLLAR CURR
US DOLLAR AMT
GB POUND CURR
GB POUND AMT
EURO CURRENCY
EURO AMOUNT
ASIA YEN CURR
ASIA YEN AMT
SWED KRON CURR
SWED KRON AMT
CANADIAN CURR
CANADIAN AMT
CONVERSION RATE
DB CR FLAG
MEMO FLAG
CORP ACCT NO
SALES TAX
SALES TAX FLAG
VAT TAX
VAT TAX FLAG
PURCHASE ID
PURCH ID FLAG
TRAN TYPE
NO OF ADDENDUMS
VISA_MCI TRAN CODE
ADDENDUM KEY
TICKET NUMBER
MSG TYPE
FILLER
VAT EVIDENCE FLAG
CUSTOMER REFERENCE NUMBER
DISCOUNT AMOUNT
MESSAGE ID
SUMMARY COMMODITY CODE
CUSTOMER VAT NUMBER
FILLER
TRX CONTROL DATA
The above mentioned is Just 50% of data will be received form the banks. Still footer details have to added.
Thanks,
Nandagopal C
Edited by: Nandagopal Chiranjeevi on Feb 6, 2009 5:40 AM

WHAT ARE CONVERSIONS?

Similar Messages

Maybe you are looking for