About webdynpro techniques!

I have to read data from reference database(read-only) (SAP) by calling Function to access database then I have to calculate and store it somewhere and other person can access and get this data. I wonder where can I store these data. Does web-dynpro support any techniques to do this?
Edited by: Dinh Thieu Thien on Jun 26, 2008 11:05 AM

You can find information at "Component-based development from Database Table to Web Dynpro using NWDI"

Similar Messages

A quick question about WebDynpro SLD and R/3 with concurrent users

Hello ,
I have a very quick question about Webdynpros and SLD connecting to an R/3 system, when you configure a webdynpro to connect to an R/3 system using SLD, you configure a user name and password from the R/3 for the SLD to use. What I would like to know is when I have concurrent users of my webdynpro, how can I know what one user did in R/3 and what another user did? Is there a way for the users of the web dynpro to use their R/3 credentials so SLD can access the R/3? Like dynamically configuring the SLD for each user?
- I would like to avoid leaving their their passwords open in the code ( configuring two variable to get the users username and password and use these variables as JCO username and password )
Thanks Ubergeeks,
Guy

Hi Guy
You will have to use Single Sign On to achieve this. In the destination you have defined to connect to R/3 , there is an option to 'useSSO' instead of userid and password. This will ensure that calls to R/3 will be with the userid that has logged into WAS. You wont need to pass any passwords because a login ticket is generated from WAS and passed on to R/3. The userid is derived from this ticket.
For this to happen you will have to maintain a trust relation ship between R/3 and your WAS ,there is detailed documentation of this in help files. Configuration is very straight forward and is easy to perform
Regards
Pran

Doubt about webDynpro windows

HI Experts,
I have small doubt about webdynpro windows.
1) If i have only one application in webdynpro DC , what is use of using multiple windows.
2) If i have multiple windows in a DC which has single application, how i can i navigate between windows?
3)if i have multiple applications with multiple windows, then how will i know which window belongs to which application.
4)If i have multiple windows and multiple applications, then how can we navigate between windows? It means navigation betn windows and navigation betn applications...?
Please explain me, i browsed in SDN, i found the threads but they are explaining my doubts exactly
Thanks in advance.
Regards,
Bala

Hi.
Simply the Window is part of Web Dynpros public interfaces, and are needed whenever you want to access a graphic component from outside of your web dynpro component.
Web Dynpro uses the MVC design pattern. Model View Control.
In order to reuse components, Web Dynpro exposes the View and Controller to the outside world.
Internally the View and Control in MVC is just that:
Views
Component Controller and Custom Controller.
Externally the View and Control are exposed as
Interface Controller and Interface Views. The Interface View is the external part of a Window. (When a Window is created, an associated Interface View is created).
So, to be able to actually see anything from a Web Dynpro application. The browser would access a Interface View that opens the Window with some view in it.
An other example is that you have two Web Dynpro projects, where the first one have a View with an integrated view from the second Web Dynpro. The integration would be through the Interface View again.
Internally in your Web Dynpro component, you can use the views directly (i.e. navigate between views).
Opening an external popup would generate a new browser window. In order for the new browser window to display anything it would need to access an interface view. That's why you need to create a separate Window when you want to use a popup.
Regards.
Edited by: Mikael Löwgren on Feb 15, 2008 12:58 PM

Please tell me about Enhancement Techniques used in SAP Other then BADI/Usr

Hi Experts .
Please guide me about Enhancement Techniques used in SAP apart from BADI/User-Exit .
1.) what is set and how to create it ?
2.) What is formula is SAP and How to set it for Enhancement Pupose .
3.) What is BTE (Buisness Transection Events) ? How to create it for Enhancement Pupose ?
Please Elabarate the reply with step by step procedure .
Thanx .
Regards : Rajneesh

Hi Raj,
Check these links
help.sap.com/saphelp_nw04/helpdata/en/eb/3e7ceb940e11d295df0000e82de14a/content.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/207835fb-0a01-0010-34b4-fef1240ba9b7
Regards,
Sana.
reward for useful answers..

Please tell me about Enhancement Technique like BTE , SET and Formula

Hi Experts .
Please guide me about Enhancement Techniques used in SAP apart from BADI/User-Exit .
1.) what is set and how to create it ?
2.) What is formula is SAP and How to set it for Enhancement Pupose .
3.) What is BTE (Buisness Transection Events) ? How to create it for Enhancement Pupose ?
Please Elabarate the reply with step by step procedure .
Thanx .
Regards : Rajneesh

Hi rajneesh mittal ,
Business Transaction Events
Business Transaction Events (Open FI) The Open FI enhancement technique was developed in the Financial Accounting component. Open FI is based upon the following principles: Application developers must define their interface in a function module, an assignment table is read in the accompanying (generated) code, and the customer modules assigned are called dynamically. This technique differentiates between enhancements that are only allowed to have one implementation and enhancements that can call multiple implementations in any sequence desired. Both industry-specific and country-specific enhancements may be defined.
SAP business transaction events are one type of customer enhancements provided by SAP! We can access the business transaction events using FIBF.Next we have to find the process interface for duplicate invoice check!
check this blog for details on SAP business transaction events
Business Transaction Events
Business Transaction Events
http://fuller.mit.edu/user_exits/business_transaction_event.htm
FI Enhancement Technique How-To-Guide on the Usage of Business Transaction Events (BTE)
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/207835fb-0a01-0010-34b4-fef1240ba9b7
Creation of Events via Business Transaction Events
http://help.sap.com/saphelp_nw04/helpdata/en/3b/7f3e8be57c11d1951f0000e82dec10/content.htm
In SAP R/3 you must activate the business transaction events (BTEs) for Availability Check Using SAP R/3. To set this indicator in SAP R/3:........
http://help.sap.com/saphelp_crm40/helpdata/en/b6/de3efc6bbcdc4b948d466857a10323/content.htm
cheers!
gyanaraj
****Pls reward points if u find this helpful

About modularization techniques

hi,,
   can anybody send me the details about modularization techniques ?
   mainly i want differences between INCLUDES and FUNCTION MODULES.
                                                     MACROS and SUBROUTINES.

Hi
Purpose of modularization is: 1) Organizing your ABAP Code 2) Limit maintenance cost by coding every thing only once and making your ABAP code easier to understand.
Modularization techniques:
1) Organizing your ABAP code can be done by using INCLUDE reports and local MACRO's (DEFINE statement). Typical examples can be found in Module Pools and Function Groups with TOP-includes and special includes for PBO events, PAI events et cetera. You can discuss if using subroutines, functions or methods is also part of this type of modularization technique. At this moment, most ABAP programmers use subroutines partly as a means to create some sort of main line in their program, thus limiting large chunks of ABAP code. Regarding MACRO's there are some special problems, especially that they don't improve readability of ABAP coding, and you can not debug them.
2)Here, we are talkin about ABAP PROCEDURES: a) Subroutines, b) Functions and c) Methods
- 2a) Subroutines: can be used locally and globally (external subroutine calls). Subroutines have a formal interface ( USING, CHANGING, TABLES parameters). The interface parameters can be passed BY VALUE or BY REFERENCE. Data that is defined within a subroutine (FROM ... ENDFORM.) is local: lifetime and visibility is limited to the moment the subroutine is called. External Subroutines are subroutines that are called from another program. Typical example can be found in the way SAPscript and SMARTforms printprograms are called by RSNAST00. External Subroutines can be grouped into Subroutine Pools.
- 2b) Functions: are part of function groups. They are designed for global use and have a unique name. Function Modules also have a formal interface using IMPORTING, EXPORTING, CHANGING and TABLES parameters. The interface parameters can be passed BY VALUE or BY REFERENCE. Specific EXCEPTIONS can be defined for error handling. A function module can also have local data.
In theory, a function module can only use data a)from the interface parameters, b) defined locally in the function module and c) defined globally in the function group. However, it is possible to see global data from calling programs using field-symbols.
Remote Function Modules are function modules that can be called from other SAP or NON-SAP systems. BAPI's are examples of RFC-enabled function modules.
Function Groups and Function Modules are maintained using transaction SE37 (or SE80).
- 2c) Methods: are part of CLASSES. Here we are talking about ABAP Objects, supporting inheritance, instantiation, encapsulation, polymorphism, events, Interfaces, visibility sections (PUBLIC, PROTECTED, PRIVATE) and lifetime options STATIC and INSTANCE.
Classes can be defined locally or globally: a) Local Classes are classes, defined as part of an ABAP program. They can be used only within this program. b) The functionality of Global Classes is identical, but these classes are maintained using the Class Builder (SE24 or SE80).
The name of a method is not unique; you always need the name of the object to create the unique name. As a result, several classes will have exactly the same method name.
Methods also have a formal interface using IMPORTING, EXPORTING, CHANGING and RETURNING parameters. The interface parameters can be passed BY VALUE or BY REFERENCE. Specific EXCEPTIONS can be defined for error handling. A method can also have local data.
In general, using classes is considered a much better alternative to using subroutines and function modules, especially with regards to maintenance costs. Actually, you do not need subroutines anymore. Function Modules are only needed is some cases, for example as RFC's because the classes don't support remote calls.
One limitation of ABAP Classes is that they do not support dynpro's. This means that you always need a report/module pool/function group if you want to create screens.
Within methods, several types of obsolete ABAP statements are not allowed like: ON CHANGE OF, TABLES and OCCURS.
Consider that new tools and options like Web Dynpro, Unit Testing, Shared Objects, Exception Classes can only be understood when having the knowledge of ABAP OO. If you are debugging new SAP transactions, you'll see that they are also programmed using ABAP Objects.
Processing blocks that are called from ABAP programs:
   1. Subroutines
   2. Function modules
   3. Methods
      Procedures
      Procedures contain a set of statements, and are called from other ABAP programs.
      The processing blocks that you call from ABAP programs are called procedures
      You define procedures in ABAP programs. When the program is generated, they remain as standalone modules. You can call procedures in the program in which they are defined, or from external programs. Procedures have an interface for passing data, and can also contain local data.
      ABAP contains the following kinds of procedures:
Subroutines
Subroutines are principally for local modularization, that is, they are generally called from the program in which they are defined. You can use subroutines to write functions that are used repeatedly within a program. You can define subroutines in any ABAP program.
Function Modules
Function modules are for global modularization, that is, they are always called from a different program. Function modules contain functions that are used in the same form by many different programs. They are important in the R/3 System for encapsulating processing logic and making it reusable. Function modules must be defined in a function group, and can be called from any program.
Methods
Methods describe the functions and behavior of classes and their instances in ABAP Objects. Methods must be defined in classes. When you call them, you must observe certain special rules of object-oriented programming.
Subroutines
Subroutines are procedures that you can define in any ABAP program and also call from any program. Subroutines are normally called internally, that is, they contain sections of code or algorithms that are used frequently locally. If you want a function to be reusable throughout the system, use a function module.
subroutine is a block of code introduced by FORM and concluded by ENDFORM.
FORM [USING ... [)] ... ] [CHANGING... [)] ... ].
ENDFORM.
subroutines cannot be nested. You should therefore place your subroutine definitions at the end of the program
Calling Subroutines
PERFORM... .
Subroutines can call other subroutines (nested calls) and may also call themselves (recursive calls). Once a subroutine has finished running, the calling program carries on processing after the PERFORM statement. You can use the USING and CHANGING additions to supply values to the parameter interface of the subroutine.
Function Modules
Function modules are procedures that are defined in function groups (special ABAP programs with type F) and can be called from any ABAP program. Function groups act as containers for function modules that logically belong together.
Unlike subroutines, you do not define function modules in the source code of your program. Instead, you use the Function Builder. The actual ABAP interface definition remains hidden from the programmer. You can define the input parameters of a function module as optional. You can also assign default values to them. Function modules also support exception handling. This allows you to catch certain errors while the function module is running.
Function groups are containers for function modules. You cannot execute a function group. When you call an function module, the system loads the whole of its function group into the internal session of the calling program (if it has not already been loaded).
This is used by the system to create the components of the group (main program and corresponding include programs). When you create a function group or function module in the Function Builder , the main program and include programs are generated automatically.
The main program SAPL contains nothing but the INCLUDE statements for the following include programs:
LTOP. This contains the FUNCTION-POOL statement (equivalent for a function group of the REPORT or PROGRAM statement) and global data declarations for the entire function group.
LUXX. This contains further INCLUDE statements for the include programs
LU01, LU02, ... These includes contain the actual function modules.
The include programs LF01, LF02, ... can contain the coding of subroutines that can be called with internal subroutine calls from all function modules of the group.
All of the function modules in a function group can access the global data of the group. For this reason, you should place all function modules that use the same data in a single function group.
Function modules can have the following interface parameters:
Import parameters. These must be supplied with data when you call the function module, unless they are flagged as optional. You cannot change them in the function module.
Export parameters. These pass data from the function module back to the calling program. Export parameters are always optional. You do not have to receive them in your program.
Changing parameters. These must be supplied with data when you call the function module, unless they are flagged as optional. They can be changed in the function module. The changed values are then returned to the calling program.
Tables parameters. You use these to pass internal tables. They are treated like CHANGING parameters. However, you can also pass internal tables with other parameters if you specify the parameter type appropriately.
You can specify the types of the interface parameters, either by referring to ABAP Dictionary types or elementary ABAP types. When you call a function module, you must ensure that the actual parameter and the interface parameters are compatible.
Interface parameters are, by default, passed by value. However, they can also be passed by reference. Tables parameters can only be passed by reference. You can assign default values to optional importing and changing parameters. If an optional parameter is not passed in a function module call, it either has an initial value, or is set to the default value.
Exceptions are used to handle errors that occur in function modules. The calling program checks whether any errors have occurred and then takes action accordingly.
Calling Function Modules in ABAP
To call a function module, use the CALL FUNCTION statement:
CALL FUNCTION [EXCEPTIONS e1 = r 1.... e n = r n ].
You can specify the name of the function module either as a literal or a variable. Each interface parameter is explicitly assigned to an actual parameter . You can assign a return value to each exception . The assignment always takes the form = . The equals sign is not an assignment operator in this context.
After EXPORTING, you must supply all non-optional import parameters with values appropriate to their type. You can supply values to optional import parameters if you wish.
After IMPORTING, you can receive the export parameters from the function module by assigning them to variables of the appropriate type.
After CHANGING or TABLES, you must supply values to all of the non-optional changing or tables parameters. When the function module has finished running, the changed values are passed back to the actual parameters. You can supply values to optional changing or tables parameters if you wish.
You can use the EXCEPTIONS option to handle the exceptions of the function module. If an exception is raised while the function module is running, the system terminates the function module and does not pass any values from the function module to the program, except those that were passed by reference. If is specified in the EXCEPTION option, the calling program handles the exception by assigning to SY-SUBRC. must be a numeric literal.
If you specify of ERROR_MESSAGE in the exception list you can influence the message handling of function modules. Normally, you should only call messages in function modules using the MESSAGE ... RAISING statement. With ERROR_MESSAGE you can force the system to treat messages that are called without the RAISING option in a function module as follows:
Messages of classes S, I, and W are ignored (but written to the log in a background job).
Messages of classes E and A stop the function module as if the exception ERROR_MESSAGE had occurred (SY-SUBRC is set to ).
If you specify OTHERS after EXCEPTIONS, the system assigns a single return code to all other exceptions that you have not specified explicitly in the list.
You can use the same number for several exceptions.
You can trigger exceptions in the function module using either the RAISE or the MESSAGE ... RAISING statement. If the calling program handles the exception, both statements return control to the program. The MESSAGE ..... RAISING statement does not display a message in this case. Instead, it sets the following system fields:
   1. Message class ® SY-MSGID
   2. Message type ® SY-MSGTY
   3. Message number ® SY-MSGNO
   4. SY-MSGV1 to SY-MSGV4 (contents of fields to , included in a message).
      You can use the system fields to trigger the message from the calling program.
Raising Exceptions
There are two ABAP statements for raising exceptions. They can only be used in function modules:
RAISE .
and
MESSAGE..... RAISING .
The effect of these statements depends on whether the calling program handles the exception or not. If the name of the exception or OTHERS occurs in the EXCEPTIONS addition of the CALL FUNCTION statement, the exception is handled by the calling program.
If the calling program does not handle the exception
The RAISE statement terminates the program and switches to debugging mode.
The MESSAGE ..... RAISING statement display the specified message. How the processing continues depends on the message type.
If the calling program handles the exception, both statements return control to the program. No values are transferred. The MESSAGE ..... RAISING statement does not display a message. Instead, it fills the system fields SY-MSGID, SY-MSGTY, SY-MSGNO, and SY-MSGV1 to SY-MSGV4.
Remote Function Modules
To implement a remote function module in ABAP, perform the following steps:
1. Register the module as remotely callable in the RFC server system.
In the function module Administration screen (transaction code SE37), set the field Can be called via REMOTE CALL. Registering a module as remote causes an RFC stub to be generated for it.
Asynchronous remote function calls (aRFCs) are similar to transactional RFCs, in that the user does not have to wait for their completion before continuing the calling dialog. There are three characteristics, however, that distinguish asynchronous RFCs from transactional RFCs:
When the caller starts an asynchronous RFC, the called server must be available to accept the request.
      The parameters of asynchronous RFCs are not logged to the database, but sent directly to the server.
Asynchronous RFCs allow the user to carry on an interactive dialog with the remote system.
The calling program can receive results from the asynchronous RFC.
You can use asynchronous remote function calls whenever you need to establish communication with a remote system, but do not want to wait for the functions result before continuing processing. Asynchronous RFCs can also be sent to the same system. In this case, the system opens a new session (or window) and allows you to switch back and forth between the calling dialog and the called session.
To start a remote function call asynchronously, use the following syntax:
CALL FUNCTION RemoteFunction STARTING NEW TASK taskname
Destination ...
EXPORTING...
TABLES ...
EXCEPTIONS...
The following calling parameters are available:
TABLES
passes references to internal tables. All table parameters of the function module must contain values.
EXPORTING
passes values of fields and field strings from the calling program to the function module. In the function module, the correponding formal parameters are defined as import parameters.
EXCEPTIONS
see Using Pre-Defined Exceptions for RFC
RECEIVE RESULTS FROM FUNCTION func is used within a FORM routine to receive the results of an asynchronous remote function call. The following receiving parameters are available:
   1. IMPORTING
   2. TABLES
   3. EXCEPTIONS
The addition KEEPING TASK prevents an asynchronous connection from being closed after receiving the results of the processing. The relevant remote context (roll area) is kept for re-use until the caller terminates the connection.
Call a transaction asynchronally and display it in an amodal window:
DATA: MSG_TEXT(80) TYPE C. "Message text
Asynchronous call to transaction SM59 ->
Create a new session
CALL FUNCTION ABAP4_CALL_TRANSACTION STARTING NEW TASK TEST
DESTINATION NONE
EXPORTING
TCODE = SM59
EXCEPTIONS
COMMUNICATION_FAILURE = 1 MESSAGE MSG_TEXT
SYSTEM_FAILURE = 2 MESSAGE MSG_TEXT
IF SY-SUBRC NE 0.
WRITE: MSG_TEXT.
ELSE.
WRITE: O.K.
ENDIF.
You must not use IMPORTING when calling aRFCs.
Transactional Remote Function Calls
    RfcInstallTransactionControlinstalls four functions to control transactional behaviour.
    RFC_ON_CHECK_TIDis called when a local transaction is starting.
    RfcCreateTransID Get a unique transaction-ID for calling an
    ABAP function module using the transactional RFC Interface
    RfcIndirectCall Call an ABAP function module using the
    transactional RFC Interface
    RFC_ON_COMMIT is called when a local transaction ends.
    RFC_ON_CONFIRM_TID is called when a local transaction is
    completed.
    RFC_ON_ROLLBACK is call
ed when a local transaction ends with
failure.
RFC_ONCALL
INCLUDE AND MACROS:
When you modularize source code, you place a sequence of ABAP statements in a module. Then, instead of placing all of the statements in your main program, you just call the module.
Include programs are global R/3 Repository objects. They are solely for modularizing source code, and have no parameter interface.
They have the following functions:
Library:Include programs allow you to use the same source code in different programs. For example, this can be useful if you have lengthy data declarations that you want to use in different programs.
Order. Include programs allow you to manage complex programs in an orderly way. Function groups and module pools use include programs to store parts of the program that belong together. The ABAP Workbench supports you extensively when you create such complex programs by creating the include programs automatically and by assigning them unique names.
Creating Your Own Include Programs
If you create an include program yourself, you must assign it the type I in its program attributes.
An include program cannot run independently, but must be built into other programs. Include programs can contain other includes.
The only restrictions for writing the source code of include programs are:
Include programs cannot call themselves.
Include programs must contain complete statements.
The INCLUDE statement has the same effect as copying the source code of the include program into the program. In the syntax check, the contents of the include program are also analyzed. Include programs are not loaded at runtime, but are expanded when the program is generated. Once the program has been generated, the load version contains static versions of all of its includes. If you subsequently change an include program, the programs that use it are automatically regenerated.
***INCLUDE STARTTXT.
WRITE: / 'Program started by', SY-UNAME,/ 'on host', SY-HOST, 'date:', SY-DATUM, 'time:', SY-UZEIT.ULINE.
We can then include this program in any other ABAP program to display a standard list header.
PROGRAM SAPMZTST.INCLUDE STARTTXT.
This could produce the following output:
Program started by KELLERH
on host ds0025 date: 03/19/1998 time: 09:00:39
Macros
If you want to reuse the same set of statements more than once in a program, you can include them in a macro. For example, this can be useful for long calculations or complex WRITE statements. You can only use a macro within the program in which it is defined, and it can only be called in lines of the program following its definition.
The following statement block defines a macro :
DEFINE .
END-OF-DEFINITION.
Macros do not belong to the definition part of the program. This means that the DEFINE...END-OF-DEFINITION block is not interpreted before the processing blocks in the program. At the same time, however, macros are not operational statements that are executed within a processing block at runtime. When the program is generated, macro definitions are not taken into account at the point at which they are defined
A macro definition inserts a form of shortcut at any point in a program and can be used at any subsequent point in the program. As the programmer, you must ensure that the macro definition occurs in the program before the macro itself is used. Particular care is required if you use both macros and include programs, since not all include programs are included in the syntax check (exception: TOP include).
To use a macro, use the following form:
When the program is generated, the system replaces by the defined statements and each placeholder &i by the parameter
. You can use macros within macros. However, a macro cannot call itself.
DATA: RESULT TYPE I,N1 TYPE I VALUE 5,N2 TYPE I VALUE 6.
DEFINE OPERATION. RESULT = &1 &2 &3.OUTPUT &1 &2 &3 RESULT.END-OF-DEFINITION.
DEFINE OUTPUT. WRITE: / 'The result of &1 &2 &3 is', &4.END-OF-DEFINITION.
OPERATION 4 + 3.OPERATION 2 ** 7.OPERATION N2 - N1.
The produces the following output:
The result of 4 + 3 is 7
The result of 2 ** 7 is 128
The result of N2 - N1 is 1
Inserting the macro changes nothing in the generated form of the program.
Check this link
http://www.sapbrainsonline.com/FAQs/TECHNICAL/SAP_ABAP_MODULARIZATION_FAQ.html
http://help.sap.com/saphelp_40b/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_40b/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/content.htm
Regards
Pavan
Message was edited by:
        Pavan praveen
Message was edited by:
        Pavan praveen

Give me description about WEBDYNPRO

give me description about WEBDYNPRO

Hi,
https://www.sdn.sap.com/irj/sdn/developerareas/webdynpro
There is a separate section for Webdynpro on SDN.
Web Dynpro is the SAP NetWeaver programming model for user interfaces (UIs).
The Web Dynpro model is based on the Model View Controller paradigm, and has the following features that build on the classic dynpro model:
Clear separation of business logic and display logic
Uniform metamodel for all types of user interfaces
Execution on a number of client platforms.
Extensive platform independence of interfaces
Web Dynpro is available both in the Java and the ABAP development environment.
Regards,
Bhavesh

FYI. Problem about webdynpro embedding

Dear Expert:
I encountered a problem with webdynpro embedded in portal.
Let's make it simple,
the source of a UI element Image in the webdynpro binds to a link   -> ftp://...../test.jpg
in my program I change the link dynamically after some action.
Everything works fine if I run this webdynpro.
But the strange thing is when I embed the webdynpro into portal, the image could not be displayed, even
it could not be shown if I bind it to the fixed link. (ftp:///)
I tried other source like http://///test.jpg, it works in portal,   but how FTP source fails?   I check there is no cache.
Thanks very much for your insight.
Ray

Ray Lei wrote:Hi Ray,
>
>
> I tried other source like http://///test.jpg, it works in portal,   but how FTP source fails?   I check there is no cache.
>
Please check your application log and/or default trace to see what exactly happened. It might have something to do with security (depending on your landscape between portal, Web AS, FTP site), how you generated the URL in your WD application. Please refer to this doc (p.18)
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b031c874-9616-2a10-cfb5-ac936df54efa?QuickLink=index&overridelayout=true
Hope it helps.
Regards,
Dao

About webdynpro actions

hi to all
iam little but confusion among
ACTION ,, EVENT., EVENT HANDLER METHODS
can any one give me description about all these
thank u inadvance
ratan

Hi Ratan,
Method can be void and it can be return type.
Method with Event: it perform some system actions such as click, enter etc..
Action it performs system events. for example. You can use actions with UI Elements where as methods are not.
For example: Submit Button
onActionSubmit()
Note: Method with event and Action both are almost Similar
To avoid Confusion:
Use actions when use UI Elements
Use methods if you want write individual methods

About datatransfer technique

which bdc method mostly we use in real time.
Now projects are using bdc or bapi.
Edited by: madhu sudhan on Feb 26, 2008 1:22 PM

>
madhu sudhan wrote:
> which bdc method mostly we use in real time.
> Now projects are using bdc or bapi.
>
> Edited by: madhu sudhan on Feb 26, 2008 1:22 PM
Hi,
Now a days companies are using bdc as well as bapi.
most of the companies are using bdc only.
because bapis are related to oops concept and there is less resources on bapis as compare to bdc.
here iam givina session method and call transaction method procedures.
When you create a batch input session, it remains in the batch input queue until it is explicitly started. Session processing can be started in two ways:
An on-line user can start the session using the batch input menu options. (To access the batch input options, choose System>Services>Batch Input.)
You can submit the background job RSBDCSUB to start a session in background processing. If several sessions have the same name, RSBDCSUB starts them all.
It's possible to coordinate the generation and execution of a session in the background processing system.
You can, for example, schedule both the batch input program and RSBDCSUB in the background. If you designate the batch input job as the predecessor for RSBDCSUB, then RSBDCSUB will be started automatically when the batch input job successfully completes.
Alternatively, you can schedule both the batch input program and RSBDCSUB as job steps in a single background job. In this case, however, RSBDCSUB is started even if the batch input program should terminate abnormally.
For detailed information about processing batch input sessions, see MANAGING BATCH INPUT SESSIONS(B) in the System Services guide. You'll find this guide in the Basis library, system administration section, on the SAP documentation CD-ROM.
(19) USING CALL TRANSACTION USING FOR BATCH INPUT:
Processing batch input data with CALL TRANSACTION USING is the faster of the two recommended batch input methods. In this method, batch input data is processed inline in your batch input program.
Error recovery, restarting, and management of batch input processing are all more comfortable if you use "classical" batch input processing by way of batch input sessions. CALL TRANSACTION USING is therefore recommended only if batch input sessions do not run fast enough to meet your requirements.
For more information on choosing a batch input method, please see Selecting a Batch-Input Method(11) .
A program that uses CALL TRANSACTION USING to submit batch input should perform the following steps:
1. Prepare a BDCDATA structure for the transaction that you wish to run. The requirements for filling the BDCDATA structure are the same as for "classical" batch input using sessions. For more information, please see Using the Batch Input Data Structure(12).
2. With a CALL TRANSACTION USING statement, call the transaction and pass the BDCDATA structure to it as batch input. For example:
CALL TRANSACTION 'SE38' USING BDCDATA
MODE 'A'
UPDATE 'S'.
MESSAGES INTO MESSTAB.
The Mode Parameter
The MODE parameter lets you specify whether the batch input processing should be displayed to you as it happens. You can choose between three modes:
A Display everything.
All screens and the data that goes in them appear when you run your program. This is the default setting for MODE in CALL TRANSACTION USING.
N Display nothing.
All screens are processed invisibly, regardless of whether there are errors or not. Control returns to your program as soon as transaction processing is finished. (Database updates however, may have taken place or may have not have taken place, depending on the value of the UPDATE parameter.)
E Display errors only. The transaction goes into display mode as soon as an error in one of the screens is detected. You can then correct the error.
The display modes are the same as those that are available for processing batch input sessions.
The Update Parameter
The UPDATE parameter lets you specify how updates produced by a transaction should be processed. You can select between these modes:
A Asynchronous updating.
In this mode, the called transaction does not wait for any updates it produces to be completed. It simply passes the updates to the SAP update service.Asynchronous processing therefore usually results in faster execution of your batch input program.
Asynchronous processing is NOT recommended for processing any larger amount of data. This is because the called transaction receives no completion message from the update module in asynchronous updating. The calling batch input program, in turn, cannot determine whether a called transaction ended with a successful update of the database or not.
If you use asynchronous updating, then you will need to use the update management facility (transaction SM12) to check whether updates have been terminated abnormally during session processing. Error analysis and recovery is less convenient than with synchronous updating.
S Synchronous updating.
In this mode, the called transaction waits for any updates that it produces to be completed. Execution is slower than with asynchronous updating because called transactions wait for updating to be completed. However, the called transaction is able to return any update error message that occurs to your program. It's much easier for you to analyze and recover from errors.
L Local updating.
If you update data locally, the update of the database will not be processed in a separate process, but in the process of the calling program. (Refer to the keyword documentation of SET UPDATE TASK LOCAL for more information.)
The Messages Parameter
The MESSAGES specification indicates that all system messages issued during a CALL TRANSACTION USING are written into the internal table . The internal table must have the structure BDCMSGCOLL.
Example
You can have system messages issued by transaction SE38 (bottom of example) collected in table MESSTAB with the following coding:
DATA BEGIN OF BDCDATA OCCURS 100.
INCLUDE STRUCTURE BDCDATA.
DATA END OF BDCDATA.
DATA BEGIN OF MESSTAB OCCURS 10.
INCLUDE STRUCTURE BDCMSGCOLL.
DATA END OF MESSTAB.
DATA REPORT(8).
BDCDATA-PROGRAM = 'SAPMS38M'.
BDCDATA-DYNPRO = '0100'.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
CLEAR BDCDATA.
BDCDATA-FNAM = 'RS38M-PROGRAMM'.
BDCDATA-FVAL = REPORT.
APPEND BDCDATA.
CALL TRANSACTION 'SE38' USING BDCDATA MODE 'N'
MESSAGES INTO MESSTAB.
The following figures show the return codes from CALL TRANSACTION USING and the system fields that contain message information from the called transaction. As the return code chart shows, return codes above 1000 are reserved for batch input.
If you use the MESSAGES INTO option, then you do not need to query the system fields shown below; their contents are automatically written into the message table. You can loop over the message table to write out any messages that were entered into it.
Regards,
swami.

HELP???Question about the technique RM COPY. Please Help

PLEASE HELP
Im wondering if anyone can help me. I recently got a reply to a post that I wrote about deleting duplicated files. Mainly MP3s. I have not done this method yet though. Does it work? I have around 9000 mp3s that Itunes seems to always duplicate and I need to get rid of them. Can I open one of my ex-Harddrives that pretty much hold mp3s and run this command? Im looking for a completely faster method than individually deleting them in Itunes. One last question too. Where do I type this command? How do I access the directorys where my mp3s are in my ex-HD? If anyone can help me Id greatly appreciate it. The reply is below my name
Jamie
posternut:
If none of the original filenames contains the lettering " copy", you can do what you want quite easily.
Open Terminal, navigate to the folder that contains the files, and enter the following command (exactly as it appears here):
rm *" copy"*
That's all there is to it. All 9000 duplicate files will be removed very quickly.
If you need help "navigating to the folder" or if some of your original filenames contain the lettering “ copy”, then post back here.
Greg

Launch Terminal.app
Type cd followed by a space. Do not hit return key just yet.
In Finder, navigate to folder containing the files you want to blow away.
Drag and drop that folder (in the finder) into the Terminal.app window. It'll autofill the path to the directory containing the files you're wanting to blow away. Now hit the return key.
You could type ls (that's a lower-case ell) and see the directory listing of all the files in your current directory. Probably a good idea to do just to doublecheck that you really are in the directory that you want to blow away all these files from.
Now do what Greg said.
Don't get impatient because Terminal is just sitting there and you're not getting an immediate command prompt. It'll take a while to blow away 9000 files.
For entertainment, instead of rm *" copy"* use rm -v *" copy"* so you can watch all 9000 file names be printed in your terminal window as they are being deleted.
Will it work? Oh yes .... irreversibly (if it doesn't, that's coz' there are some file ownership and/or file permission issues that need to be looked at, but assuming those are "compatible" with your current Terminal user environment, those guys'll be toast. Any file that's in the working directory where you are in Terminal that has the five characters " copy" in its filename will be history.
The assumption in Greg's command is that all the files you want to blow away all reside in the one directory that you have navigated to.

HELP???Question about the technique RM COPY

Im wondering if anyone can help me. I recently got a reply to a post that I wrote about deleting duplicated files. Mainly MP3s. I have not done this method yet though. Does it work? I have around 9000 mp3s that Itunes seems to always duplicate and I need to get rid of them. Can I open one of my ex-Harddrives that pretty much hold mp3s and run this command? Im looking for a completely faster method than individually deleting them in Itunes. One last question too. Where do I type this command? If anyone can help me Id greatly appreciate it. The reply is below my name
Jamie
posternut:
If none of the original filenames contains the lettering " copy", you can do what you want quite easily.
Open Terminal, navigate to the folder that contains the files, and enter the following command (exactly as it appears here):
rm *" copy"*
That's all there is to it. All 9000 duplicate files will be removed very quickly.
If you need help "navigating to the folder" or if some of your original filenames contain the lettering “ copy”, then post back here.
Greg

Launch Terminal.app
Type cd followed by a space. Do not hit return key just yet.
In Finder, navigate to folder containing the files you want to blow away.
Drag and drop that folder (in the finder) into the Terminal.app window. It'll autofill the path to the directory containing the files you're wanting to blow away. Now hit the return key.
You could type ls (that's a lower-case ell) and see the directory listing of all the files in your current directory. Probably a good idea to do just to doublecheck that you really are in the directory that you want to blow away all these files from.
Now do what Greg said.
Don't get impatient because Terminal is just sitting there and you're not getting an immediate command prompt. It'll take a while to blow away 9000 files.
For entertainment, instead of rm *" copy"* use rm -v *" copy"* so you can watch all 9000 file names be printed in your terminal window as they are being deleted.
Will it work? Oh yes .... irreversibly (if it doesn't, that's coz' there are some file ownership and/or file permission issues that need to be looked at, but assuming those are "compatible" with your current Terminal user environment, those guys'll be toast. Any file that's in the working directory where you are in Terminal that has the five characters " copy" in its filename will be history.
The assumption in Greg's command is that all the files you want to blow away all reside in the one directory that you have navigated to.

About webdynpro

hi guysfirst of all i thank u all guys out there..
for extending ur support.
here i have a doubt
we can develop webdynpros for abap on following environment
1. ecc6 or crm 5( i mean which are on was abap 7)
2. the two files which i have downloaded from sdn.sap.com
that is was 7 + webdynpro UI
so here my doubt is what is the difference in therse two environments
ok.. some how we have developed webdynpros for abap then what we do with that webdynpro for abap? do we need publish its url so that people can have access to our server which is ecc6 or crm5?

hi,
I suggest you to kindly go to the elearning link in sdn.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/b1203f5e-0501-0010-bb88-915402c954f2 [original link is broken]
there are a lot of documentation and saptutors available.
you do not require to publish webdynpro abap applications.
If you are providing it as iview links in portal.
Or if you check sicf transaction you will get the node of your webdynpro abap application.
Regards,
Manish
reward points would be appreciated

Question about sort technique

we have a report that shows a list of contacts and we have an sub-report that displays (1) one field max(history completed date) so we can see that last time the contact was talked to. The issue is: if we want to have a sort parameter sorts on the max(history completed date) field. How would we do this?
1) pass the field value from the sub-report to the main report?
2) don't created a sub-report, create field value in the main report using sql
Please comment on the approaches above or any other methods that I might not have thought of.

Better yet, here's a sample of what your query should look like.
Insert it into 'Add Command'
select contact_names,
(select max(lasttime) from time.table b where a.contactID=b.contactID)
from table.contacts a
Enjoy,
Zack H.

About WebDynpro Study

Hi, All
How can i get the NET310 for Web Dynpro ABAP?
Thanks for your help!

hi,
you can get all related tutorials and materials in this link..plz go thru all the links..
https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=webdynproabap+tutorials&adv=false&sortby=cm_rnd_rankvalue
thanks
jaideep
*reward points if useful..

About webdynpro techniques!

Similar Messages

Maybe you are looking for