How many type of data element exist

How many type of data element exist.
Saurabh

Hi,
Data Element Types
Introduction
The following tables identify and describe the valid data element types that may be specified for the -type option. The first table covers some general data element types. The remaining tables cover data element types specific to each diagram type identified in the Diagram Types table above.
General Data Element Types
The following table covers some general data element types.
Data Element Type Description
Actor Actors on CCDs and DFDs
Class Classes on CDs, CCDs, and STDs
Event Events on SDs and STDs
External Actors on CCDs and DFDs
Flow Control Flows, Data Flows, Result Flows, and Update Flows
Interface Communication Messages, Control Flows, Data Flows, Event Messages, Result Flows, and Update Flows
Message Communication Messages and Event Messages
AD Data Element Types
The following table identifies and describes the data element types for the Activity Diagram (AD).
Data Element Type Description
ADAction Actions on ADs
ADEvent Events on ADs
ADState States on ADs
ActionState Action States
ObjectInState Objects In States
CD Data Element Types
The following table identifies and describes the data element types for the Class Diagram (CD).
Data Element Type Description
ActualType Actual Types
AssocClass Association Classes
CDAggregation Aggregations on CDs
CDAssociation Associations on CDs
CDClass Classes on CDs
CDComposition Compositions on CDs
CDContainer Containers on CDs
CDGeneralization Generalizations on CDs
CDInterface Interfaces on CDs
Package Packages
Propagation Propagations
TemplateClass Template Classes
CCD Data Element Types
The following table identifies and describes the data element types for the Class Communication Diagram (CCD).
Data Element Type Description
CCDActor Actors on CCDs
CCDClass Classes on CCDs
CCDContainer Containers on CCDs
ComMessage Communication Messages
Subject Subjects
COD Data Element Types
The following table identifies and describes the data element types for the Collaboration Diagram (COD).
Data Element Type Description
CODActiveObject Active Objects on CODs
CODActor Actors on CODs
CODMessage MEssages on CODs
MultiObject MultiObjects
NaryLink N-ary Links
RoleEnd RoleEnds
RoleStart RoleStarts
CPD Data Element Types
The following table identifies and describes the data element types for the Component Diagram (CPD).
Data Element Type Description
CPDComponent Components on CPDs
CPDInterface Interfaces on CPDs
DFD Data Element Types
The following table identifies and describes the data element types for the Data Flow Diagram (DFD).
Data Element Type Description
ControlFlow Control Flows
DataFlow Data Flows
DataProcess Data Processes
DataStore Data Stores
DFDActor Actors on DFDs
ResultFlow Result Flows
UpdateFlow Update Flows
DPD Data Element Types
The following table identifies and describes the data element types for the DeploymentDiagram (DPD).
Data Element Type Description
ActiveObject ActiveObjects
Connection Connections
DPDActiveObject Active Objects on DPDs
DPDComponent Components on DPDs
DPDObject Objects on DPDs
Node Nodes
NodeInstance Node Instances
MGD Data Element Types
The following table identifies and describes the data element types for the Message Generalization Diagram (MGD).
Data Element Type Description
MessageDef Message Definitions
SD Data Element Types
The following table identifies and describes the data element types for the Sequence Diagram (SD).
Data Element Type Description
Object Objects
SDInitiator Initiators on SDs
SDMessage Messages on SDs
SDObject Objects on SDs
STD Data Element Types
The following table identifies and describes the data element types for the State Transition Diagram (STD).
Data Element Type Description
CDClass Classes on CDs associated with the STD
EventMessage Event Messages
STDAction Actions on STDs
STDClass Classes on STDs
STDEvent Events on STDs
STDState States on STDs
UCD Data Element Types
The following table identifies and describes the data element types for the Use Case Diagram (UCD)
Data Element Type Description
DirectedComm Directed Communication Association
UCDActor Actors on UCDs
UndirectedComm Undirected Communication Association
UseCase Use Cases
Reward If Helpful
Regards Madhu

Similar Messages

How many types of tables exists and what are they in data dictionary?

hi,
How many types of tables exists and what are they in data dictionary?
regards.

Hello Liu,
Please search in forum before posting any question .
anyhow check the below link :
http://web.mit.edu/sapr3/dev/sap_table_types.htm
Thanks
Seshu

How to use Reference type of Data Element

Hi guys, is there anyone could give me a trace how to use reference type of data element.
More details i'm going to reach is:
I create 2 tables:
eq.
1. table ZFIRST has field X with data element ZFX (Data element i declared).
2. table ZSECOND has field Y.
Here at field Y (second table) I'm going to declare a new data element say it ZFY, but in ZFY I'm going to use the data element as i declared before (ZFX). Is it possible if I do it using reference type data element (SE11)?
I already did this way, but I got error :
Field Y: Reference ZFX to class w/o interface cannot be used in DB table ZSECOND
What does it mean?. Did I miss something about using reference data element type?.
This error occurs when I activate ZSECOND table. However in creating ZFY (reference) to data element ZFX, there is no error occur.
The point is I need to RE-declared existing data element and ot put existing data element(ZFX) to my current table (ZSECOND).
Any helpful will be highly appreciated.
Thanks.
Edited by: dinivian dondi on Nov 4, 2010 8:30 AM

Field Y: Reference ZFX to class w/o interface cannot be used in DB table ZSECOND
What does it mean?. Did I miss something about using reference data element type?.
Apparently system doesn't allow you to type a transparent table field with deep type. This refers to references and tables types as components. The RDBMS (Relational DB Management System) cannot interpret this componenets correclty and mapp them to TABLEs in DB.
So I am affraid you won't be able to type table component with reference to other data element.
The point is I need to RE-declared existing data element and ot put existing data element(ZFX) to my current table (ZSECOND).
Sorry but I don't get it, could you please explain this more clearly. Maybe then we can think of some workaround for you.
Regards
Marcin

How many types of Queues exists and how to identify them.

Hello
can anyone say How many types of Queues exists and how to identify them.
What does R3R* and CSA* stands for.
Regards,
divya

Hi Divya,
The queues R3* and CSA* that you have specified are qRFC queues. qRFC queues are data queues which transport data to and fro different systems.
There are also the tRFC queues which are triggered whenever you make RFC calls to connect to another system.
Queues with prefix R3AD* - for delta download from R3->CRM
Queues with prefix R3AU* - for data upload from CRM->R3
Queues with prefix R3AR* - used to transfer data during request load from R3->CRM
Queues with prefix R3AI* - for initial load from R3->CRM
Queues with prefix CSA* - these are validation object specific queues used for processing/persisting data in CRM tables in a serialized manner. E.g. CSABUPA* for business partner,CSA_ORDER* for sales order etc.
You can administer and monitor the queues in trax. SMQR,SMQS.
Hope this helps you! Pls. do not forget to reward me some points.
Regards,
Sudipta.

How many types of ports are there which we use for data transfe in ale/idoc

friends let me know how many types of ports are there which we use for transfering
data in ale/idocs?

Hello,
you can use file port,trnasactional RFC port.FI you are using IDOC-XML conversion combination,then you can XML port also.
Thanks

How many types of projects exist in sap bw

i heard that there are two types of projects
1.implementation project
2.support project
and what about up gradation project, migration project, and i want to know what all the projects exists and there processes..
if not possible please provide the link to navigate me to there

sb92075 wrote:
how many types of searching is in dbms ?42(What was the question, again? ;-) )
Learn something new every day. I thought there were only 2 - successful (aka correct) and failed (aka wrong).

How many types of transactions in ABAP

How many types of transactions in ABAP

Hi,
Transactions
The normal way of executing ABAP code in the SAP system is by entering a transaction code. Transactions can be accessed via system-defined or user-specific, role-based menus. They can also be started by entering their transaction code (a mnemonic name of up to 20 characters) in the special command field, which is present in every SAP screen. Transactions can also be invoked programmatically by means of the ABAP statements CALL TRANSACTION and LEAVE TO TRANSACTION. Transaction codes can also be linked to screen elements or menu entries. Selecting such an element will start the transaction. The term "transaction" must not be misunderstood here: in the context just described, a transaction simply means calling and executing an ABAP program. In application programming, "transaction" often refers to an indivisible operation on data, which is either committed as a whole or undone (rolled back) as a whole. This concept exists in SAP but is there called a LUW (Logical Unit of Work). In the course of one transaction (program execution), there can be different LUWs.
Letu2019s have a look at the different kind of transactions:
Dialog transaction
These are the most common kind of transactions. The transaction code of a dialog transaction is linked to a Dynpro of an ABAP program. When the transaction is called, the respective program is loaded and the Dynpro is called. Therefore, a dialog transaction calls a Dynpro sequence rather than a program. Only during the execution of the Dynpro flow logic are the dialog modules of the ABAP program itself are called. The program flow can differ from execution to execution. You can even assign different dialog transaction codes to one program.
Parameter transaction
In the definition of a parameter transaction code, a dialog transaction is linked with parameters. When you call a parameter transaction, the input fields of the initial Dynpro screen of the dialog transaction are filled with parameters. The display of the initial screen can be inhibited by specifying all mandatory input fields as parameters of the transaction.
Variant transaction
In the definition of a variant transaction code, a dialog transaction is linked with a transaction variant. When a variant transaction is accessed, the dialog transaction is called and executed with the transaction variant. In transaction variants, you can assign default values to the input fields on several Dynpro screens in a transaction, change the attributes of screen elements, and hide entire screens. Transaction variants are maintained in transaction SHD0.
Report transaction
A report transaction is the transaction code wrapping for starting the reporting process. The transaction code of a report transaction must be linked with the selection screen of an executable program. When you execute a report transaction, the runtime environment internally executes the ABAP statement SUBMITu2014more to come on that.
OO transaction
A new kind of transaction as of release 6.10. The transaction code of an OO transaction is linked with a method of a local or global class. When the transaction is called, the corresponding program is loaded, for instance methods an object of the class is generated and the method is executed.
Reward Points if found helpfull..
Cheers,
Chandra Sekhar.

How many types of function modules are there

hi gurus,
how many types of function modules are there...
what type of function module bapi is....
i don't know much about that...
pls help me...
regards,
praveen

hi
hope it will help you.
<REMOVED BY MODERATOR>
Function Modules Used in Script:
In the Driver Program we must use all or some of the function modules that are listed below to transfer the data.
Open_Form
Close_Form
Start_Form
Write_Form
Write_Form_Lines
End_Form
Control_Form
Read_Form_elements
Read_Form_Lines
Any driver program must contain Open_Form, Close_Form and Write_Form. Other function modules are optional.
OPEN_FORM: This function module opens layout set printing. One must call this function module before he uses any of other layout set function modules like Write_Form, Start_Form, Control_Form etc., You need specify a layout set name in the export parameters of this function module. If nothing is passed to Open_Form then one should use Start_Form function module to open layout set before starting the output. The layout set opened by Open_Form should be closed by Close_Form function module, other wise output doesnt appear. We can use any number of Open_Form, Close_Form functions in one single program. But Close_Form must be there for every Open_Form in the program.
Some of the important export parameters we have to pass to Open_Form function module.
Form: Enter the Layout set name here, which then controls the output formatting. If nothing is specified then we must use Start_Form for opening layout set.
Language: Layout sets are Language dependent. Enter the desired language here. If the entered layout set is not in that language, then the function tries to open the Form entered in its original language. The default value is SY-LANGU.
Device: SAP Script can format a text on different device types. The device can be PRINTER or TELEX, TELEFAX, ABAP and SCREEN.
Dialog: Use parameter DIALOG to determine whether to display a dialog box before printing, in which the user can set several spool parameters for print formatting. Possible values: SPACE displays no print parameter screen. 'X' display print parameter screen. Default value: 'X'
Options: Use parameter OPTIONS to set several options for print formatting. The parameter has the structure ITCPO. The user can change some of the defined settings on the print control screen. The default value for Options is . We will discuss about ITCPO structure in detail later.
Other Export, Import and Exceptions are self-explanatory.
Close_Form: The function module closes the layout set opened using OPEN_FORM. The system executes any terminating processing steps for the last opened layout set. No Export parameters for this Function Module.
Start_Form: In-between the function modules OPEN_FORM and CLOSE_FORM, we can use different layout sets. This allows us to combine several different layout sets into one print output. However, we can combine only those layout sets that have the same page format. To switch layout sets, use the function module START_FORM. If another layout set is still open, we must close it first using END_FORM. If we specify no layout set name when calling START_FORM, the system restarts the last open layout set. If after OPEN_FORM no layout set was activated yet, the system leaves the function module with the exception UNUSED. Some of the important export parameters for this function module are
Form: The parameter contains the name of the layout set you want to use for printing. If you specify no layout set here, the system restarts the last active layout set.
Language: Layout sets are language-dependent. Enter the desired language here. If the layout set does not exist in this language, the system tries to call the layout set in its original language. If the parameter LANGUAGE is empty, the system uses the language of the last active layout set.
Startpage: Usually, SAP script starts with the page specified as start page in the layout set definition. If we want to start output with another layout set page, enter the name of the desired layout set page here. If the desired page is not defined, the system uses the start page defined in the layout set.
Program: To replace program symbols, SAP script must know which active program contains the work areas for the values to be passed. If we omit the parameter, the system searches for the field values in the program that was specified in the parameter OPTIONS (field TDPROGRAM) of OPEN_FORM. If we enter a program name, the system replaces the program symbols with the values from this program up to the next END_FORM.
Exceptions and other Export, Import parameters are self-explanatory.
Write_Form: The system outputs the layout set element specified in parameter ELEMENT into the currently opened layout set. In the parameter WINDOW we can specify the name of a window for the output. Remember that the layout set element must be defined in this window. The parameter FUNCTION specifies how to merge the text lines to be output with any existing contents in the window. In this case, there are differences between the different window types or areas. Some of the important export parameters used in Write_Form.
Element: Specify the name of the text element you want to output into the layout set window specified in the parameter WINDOW. The element must be defined in that layout set window. If you specify no element, the system uses the default element, if one is defined in the layout set.
Window: Specify the name of the window into which you want to output the layout set element specified in the parameter ELEMENT. Default value for Window is MAIN.
Function: The parameter determines how to output the text element into the respective window. The output type depends on the window type and area:
Window Type: MAIN Area: BODY
SET/APPEND: Appends to previous output.
Window Type: Main Area: Top/Bottom and
Window Type: Other than Main and all areas
SET : Delete the old element contents and prints the new elements
APPEND: Appends the new content to existing elements.
Type: The system interprets this parameter only for output to the main window. The parameter determines the area of the main window into which we want to output the element. Possible values: 'TOP' header area
'BODY' main area
'BOTTOM' footer area
Default value: 'BODY'
Write_Form_Lines: This function module outputs the text lines in table LINES into the specified layout set window. The text lines must have the SAP script ITF format. From the data in the text header, the system uses only the field TDSTYLE to apply the formatting attributes defined in the specified style for this text. If the field is empty, the system uses the identically named formatting attributes (character and paragraph formats) of the layout set.
Use parameter WINDOW to specify into which of the windows defined in the layout set we want to output the text. We can specify any window used in the layout set. The parameter FUNCTION determines how to merge the text lines to be output with any existing contents in the window. There are differences between the different window types or areas.
Header: This parameter contains the header of the text module we want to output in the current layout set. For the formatting process, the system uses only the entries in the header fields TDSTYLE and TDFORM. Structure: THEAD
WINDOW: Enter the name of the window into which we want to output the layout set element specified in parameter ELEMENT. Default value: 'MAIN'
FUNCTION: This parameter determines how to output the text element into the respective window. The output type depends on the window type and area: Window type MAIN, area BODY: 'SET' append to previous output 'APPEND' same as SET. DELETE' no effect. Window type MAIN, areas TOP and BOTTOM; all other windows: 'SET' delete old window or area contents and output the element 'APPEND' append the element to the existing elements 'DELETE' no effect Default value: 'SET'
TYPE: The system interprets this parameter only for output to the main window. The parameter determines the area of the main window into which you want to output the element. Possible values: 'TOP' header area 'BODY' main area 'BOTTOM' footer area Default value: 'BODY'
END_FORM: END_FORM ends the currently open layout set and executes the required termination processing. After calling this function module, no more layout set is active. For further output, we must start a new layout set using START_FORM. No Export parameters.
CONTROL_FORM: Use this function module to pass SAP Script Control Commands to the layout set. The Control command is passed through the export parameter COMMAND in quotes.
READ_FORM_ELEMENTS: This function module fills a table with all text elements that appear in one layout set. If we specify no layout set name, the system includes all elements of the currently open layout set. If we specify a layout set, the system uses the information about the active version of the layout set, retrieved from the database. Here we have two export parameters, Form and Language and a table parameter Elements.
READ_FORM_LINES: Use this function module to transfer the lines of a layout set element into an internal table. If we specify no layout set name, the system transfers the text lines of the currently open layout set. If we specify a layout set, the system uses the text lines of the active version of the layout set from the database. The Export parameters are Form, Language, Window and Element. If we pass these 4 parameters the function module returns a table with the lines from layout set.
Function modules are one element. There are no types. However sometimes an RFC enabled function module is referred to as RFC Function module, but really it is just a function module. Also BAPIs are function modules, but are usually referred to as just BAPI as opposed to BAPI Function module.
There is no different function module types , but calling the function module will be different.
check this function calls syntax
1. Calls a function module:
CALL FUNCTION func.
2. Call a function module in a different mode (asynchronous Remote Function Call):
CALL FUNCTION func STARTING NEW TASK taskname.
3. Call a function module in the update task:
CALL FUNCTION func IN UPDATE TASK.
4. Call a function module in a remote system (Remote Function Call, RFC ):
CALL FUNCTION func DESTINATION dest.
5. Asynchronous call to a function module with transactional processing (transactional Remote Function Call):
CALL FUNCTION func IN BACKGROUND TASK.
qRFC with output queue
6. Call a function module that can be activated in the context of enhancements:
CALL CUSTOMER-FUNCTION func.
Cheers,
Chandru
Edited by: Alvaro Tejada Galindo on Feb 27, 2008 11:53 AM

What is buffer? how many types of buffers r there?

how many types of joins r there?
thank u.

Whenever an Open SQL statement is used to read a record,
the data buffer is checked first to see whether it is there. If not, the data is read from the database.
If the table's attributes indicate that the data should be buffered,
the record is saved in RAM on the application server in data buffers.
Later, if that record is read again, it is read from the buffer instead of the database.
By buffering data, you increase performance in two important ways:
The programs using the buffered data run faster because they don't have to wait for it to come from the database. This reduces delays waiting for the database and the network that connects it.
The other programs that need to access the database run faster because there is less load on the database and less traffic on the network.
Three types of buffering are possible:
Full Buffering
With full buffering, either the entire table is in the buffer or the table is not in the buffer at all. All
the records of the table are loaded into the buffer when one record of the table is read.
In this example, a program reads the record highlighted in red from table
SCOUNTER. If the table is fully buffered, all the records of the table are loaded into
the buffer.
Application server
The buffered data records are sorted in the buffer by table key. Accesses to the
buffered data can therefore only analyze field contents up to the last specified key
field for restricting the dataset to be searched.
The left-justified part of the key should therefore be as large as possible in such
accesses. For example, if you do not define the first key field, the system has to scan
the full table. In this case direct access to the database can be more efficient if the
database has suitable secondary indexes [Page 61].
When Should you Use Full Buffering?
When deciding whether a table should be fully buffered, you should take into account the size of
the table, the number of read accesses, and the number of write accesses. Tables best suited to
full buffering are small, read frequently, and rarely written.
Full buffering is recommended in the following cases:
BC - ABAP Dictionary SAP AG
Full Buffering
36 December 1999
Tables up to 30 KB in size. If a table is accessed frequently, but all accesses are read
accesses, this value can be exceeded. However, you should always pay attention to the
buffer utilization.
Larger tables where large numbers of records are frequently accessed. If these mass
accesses can be formulated with a very selective WHERE condition using a database
index [Page 61], it could be better to dispense with buffering.
Tables for which accesses to non-existent records are frequently submitted. Since all the
table records reside in the buffer, the system can determine directly in the buffer whether
or not a record exists.
SAP AG BC - ABAP Dictionary
Generic Buffering
With generic buffering, all the records in the buffer whose generic key fields match this record are
loaded when one record of the table is accessed. The generic key is a part of the primary key of
the table that is left-justified.
In this example, the record highlighted in red is read by a program from table
SCOUNTER. If the table is generically buffered, all the records read whose generic
key fields (MANDT and CARRID) agree are loaded into the buffer.
Application server
When Should you Use Full Buffering?
A table should be buffered generically if only certain generic areas of the table are normally
needed for processing.
Client-specific, fully-buffered tables are automatically generically buffered since normally it is not
possible to work in all clients at the same time on an application server. The client field is the
generic key.
Language-specific tables are another example where generic buffering is recommended. In
general, only records of one language will be needed on an application server. In this case, the
generic key includes all the key fields up to and including the language field.
How Should you Define the Generic Key?
In generic buffering, it is crucial to define a suitable generic key.
BC - ABAP Dictionary SAP AG
Generic Buffering
If the generic key is too small, the buffer will contain a few very large areas. During access, too
much data might be loaded in the buffer.
If the generic key is too large, the buffer might contain too many small generic areas. These can
reduce buffer performance since there is an administrative entry for every buffered generic area.
It is also possible that too many accesses will bypass the buffer and go directly to the database,
since they do not fully define the generic key of the table. If there are only a few records in each
generic area, it is usually better to fully buffer the table.
Only 64 bytes of the generic key are used. You can specify a longer generic key, but the part of
the key exceeding 64 bytes is not used to create the generic areas.
Access to Buffered Data
It only makes sense to generically buffer a table if the table is accessed with fully-specified
generic key fields. If a field of the generic key is not assigned a value in a SELECT statement, it
is read directly from the database, bypassing the buffer.
If you access a generic area that is not in the buffer with a fully-specified generic key, you will
access the database to load the area. If the table does not contain any records in the specified
area ("No record found"), this area in the buffer is marked as non-existent. It is not necessary to
access the database if this area is needed again.
SAP AG BC - ABAP Dictionary
Single-Record Buffering
With single-record buffering, only the records that are actually read are loaded into the buffer.
Single-record buffering therefore requires less storage space in the buffer than generic and full
buffering. The administrative costs in the buffer, however, are greater than for generic or full
buffering. Considerably more database accesses are necessary to load the records than for the
other buffering types.
In this example, the record highlighted in red is read by a program from table
SCOUNTER. If single-record buffering is selected for the table, only the record that
was read is loaded into the buffer.
When Should you Use Single-Record Buffering?
Single-record buffering should be used particularly for large tables where only a few records are
accessed with SELECT SINGLE. The size of the records being accessed should be between 100
and 200 KB.
Full buffering is usually more suitable for smaller tables that are accessed frequently. This is
because only one database access is necessary to load such a table with full buffering, whereas
several database accesses are necessary for single-record buffering.
Access to Buffered Data
All accesses that are not submitted with SELECT SINGLE go directly to the database, bypassing
the buffer. This applies even if the complete key is specified in the SELECT statement.
BC - ABAP Dictionary SAP AG
Single-Record Buffering
40 December 1999
If you access a record which is not yet buffered with SELECT SINGLE, there is a database
access to load the record. This record is marked in the buffer as non-existent if the table does not
contain a record with the specified key.

How many types of inbound process r there

how many types of inbound process r there for a inbound idoc?

Hi,
Creating an Inbound Process Code
The inbound process code, that is, its attributes, indicates how an inbound IDoc is processed. A process code has the following attributes:
·        Processing type (for example, should the inbound function module be called immediately, or should a workflow or work item be started?);
Standard: "ALE, function module called directly"
·        Name of inbound function module;
·        Error processing attributes (objects and events; see the section on objects, and so on, for error handling);
·        Application object type used for ALE links;
¡        the object type created or changed by the inbound function module. Example: An inbound ORDERS IDoc, containing a customeru2019s purchase order, creates a customer order in the receiving SAP System. Here the application object type is BUS2032, the object type for customer orders in the BOR (Business Object Repository).
·        The application event to be triggered (dealt with in the section on advanced techniques) is not generally used.
For an example, have a look at the process code MATM used for material master data.
Reward If Helpfull,
Naresh

How many types of mappings in sap xi

hi,
how many types of mappings in sap xi,what are there can u explain me
bye
phenix

hi suresh,
There are 4 types of mapping in XI
1. Graphical
2. XSLT
3. java
4. ABAP.
There is no hard and fast rule for using the mapping techniques. But, I will try to put things in the right perspective for you.
Graphical Mapping is used for simple mapping cases. When, the logic for your mapping is simple and straight forward and it does not involve any complex logic.
Java and XSLT mapping are used when graphical mapping cannot help you.
When the choice is between Java And XSLT, XSLT is simpler than java mapping and easier. But, it has its drawbacks. One among them being that you cannot use Java APIs and Classes in it. There might be cases in your mapping when you will have to perfrom something like a properties file look up or a DB lookup, such scenarios are not possible in XSLT and so, when you want to use some specific Java API's you will have to go for Java Mapping.
Java Mapping uses 2 types of parsers. DOM and SAX. DOM is easier to use with lots of classes to help you create nodes and elements, but , DOM is very processor intensive.
SAX parser is something that parses your XML one after the other, and so is not processor intensive. But, it is not exaclty easy to develop either.
For further info on each of the mapping, refer to these links,
Graphical Mapping,
http://help.sap.com/saphelp_nw04/helpdata/en/6d/aadd3e6ecb1f39e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/43/c4cdfc334824478090739c04c4a249/content.htm
XSLT Mapping
http://help.sap.com/saphelp_nw04/helpdata/en/73/f61eea1741453eb8f794e150067930/content.htm
http://www.w3.org/TR/xslt20/
Java Mapping
http://help.sap.com/saphelp_nw04/helpdata/en/e2/e13fcd80fe47768df001a558ed10b6/content.htm
DOM parser API
http://java.sun.com/j2se/1.4.2/docs/api/org/w3c/dom/package-frame.html
Also, check this thread for more info,
Different types of Mapping in XI
Regards,
Bhavesh

How many types of RFC's?

how many types of rfc's wat r they?

hi
A remote function call is a call to a function module running in a system different from the caller's. The remote function can also be called from within the same system (as a remote call).
RFC consists of two interfaces : A calling interface for ABAP Programs and a calling interface for Non-SAP programs.
Any ABAP program can call a remote function using the CALL FUNCTION...DESTINATION statement. The DESTINATION parameter tells the SAP System that the called function runs in a system other than the caller's.
RFC CLIENT and RFC SERVER
     RFC client is the instance that calls up the Remote Function Call to execute the function that is provided by an RFC server.
     The RFC Interface takes care of :-
- Converting all parameter data to the representation needed in the remote system
Calling the communication routines needed to talk to the remote system.
Handling communications errors, and notifying the caller, if desired ( using EXCEPTIONS paramater of the CALL FUNCTION).
You can use the CALL FUNCTION statement to call remote functions by including an additional DESTINATION clause.
CALL FUNCTION remotefunction
          DESTINATION dest
               EXPORTING f1 =
             IMPORTING f2 =
           TABLES t1 =
           EXCEPTIONS
The field dest can be either a literal or a variable. Logical destinations are defined in the RFCDES table via transaction SM59 or via the menu path: Tools ->Administration,Administration->Network->RFC destinations.
Calling remote functions locally :-
( i.e. call a remote function within the same system )
The two options to do this are
CALL FUNCTION...DESTINATION = 'NONE'
CALL FUNCTION... [no DESTINATION used]
Calling remote function modules BACK :-
    The remote function can invoke its own caller (if the caller is itself a function module), or any function module loaded with the caller.
    You can trigger this call-back mechanism   using
    CALL FUNCTION... DESTINATION 'BACK.
Synchronous RFC The calling program continues the execution only after the called function is complete.
Asynchronous RFC - The calling program continues the execution without waiting for return from the called function.
       Eg: CALL FUNCTION remotefunction STARTING NEW TASK taskname.
Transactional RFC - The called function module is executed exactly once in the RFC server system.Each function call is seen as a transaction in the target system. Transactional RFCs use the suffix IN BACKGROUND TASK .
       Eg : CALL FUNCTION remotefunction IN BACKGROUND TASK
regards
vijay
reward points if helpfull

How many types of user defined functions are there?

how many types of user defined functions are there?

Hi Ramakrishna,
A user-defined function is only visible in the message mapping in which you created it. You can insert the function in the data-flow editor as a standard function by using the User-Defined function category.
You can use the following user-defined functions:
1.Simple functions, which can process individual field input values for each function call. Simple functions therefore expect strings as input values and return a string.
2.Advanced functions, which can process several field input values for each function call. You can import either all field values of a context or the whole queue for the field in an array before calling the function. For more information, see Advanced User-Defined Functions.
    go through :
http://help.sap.com/saphelp_erp2004/helpdata/en/22/e127f28b572243b4324879c6bf05a0/content.htm
     Advanced user-defined functions, which can process more than just individual field values.Instead, you can import a complete context or an entire queue for a field as an array before your function is called
    go through :
http://help.sap.com/saphelp_erp2004/helpdata/en/f8/2857cbc374da48993c8eb7d3c8c87a/content.htm
*Pls: Reward points if helpful*
Regards,
Jyoti

How many types of tape drive

Hi all;
how many types of tape drive for rman backup.which one is best.
thanks

Hi,
Below Are the factors ...
•The amount of data you must back up
•The interfaces your equipment supports
•The data throughput you need
•The tape standard that is best for your needs
•The cost of the drive and tapes
•The capabilities and compatibility of the included driver and backup software
•Support for disaster recovery
Read below links u will get some help.
http://e-articles.info/e/a/title/How-to-choose-a-Tape-Backup-Drive/
Thanks & Regards
Rahul Sharma

How many types of dunning not levels

hi how many types of dunnig

Hi
Dunning is a reminder to the customer or vendor to make payment on outstanding invoices. It typically consists of a letter that summarizes the invoices that are past due and politely requests payment to be made. When you customize dunning you have to create dunning area like at what level you want to use the dunning, like business area level or company code level. After that you have to make settings for dunning procedure, in that you have to define no of due dates and no of dunning levels. there are maximum 9 levels are there.
the dunning wizard keeps track of a customeru2019s u201Cpayment behavioru201D in the database to deliver this important information to appropriate organizations.
The dunning system covers the following documents:
·        Open A/R invoices, including invoices that are partially credited or partially paid
·        Invoices that include installments
·        A/R credit memos
·        Incoming payments that are not based on invoices
with regards,
ramanuja chary

How many type of data element exist

Similar Messages

Maybe you are looking for