Difference between url iveiw and BSP iveiw

hi,
     What are the parameters we need for BSP iveiw and URL iveiw. What is the difference between these.

hi,
IViewLauncher          
IViewLaucher can be used to launch any IView or Portal Component or a Page in the portal.  Portal Component launching is supported only in NW04.
Provider specific Information
IViewLauncher is Provider agnostic. Items may belong to any connector.
Supported Actions
Action name can be anything.
Properties
IViewLauncher expects one  of the following two mandatory properties:
iview - iView id or Portal Component name to be launched
page - page id of the page to be launched
All other properties will be passed as name=URL encoded value to the target iView.  The dynamic properties can also be passed to an iView via the following property (since NW04 SPS18, NW04s SPS09, NY AP7):
iviewDynamicParameter - optional; name/value pairs of dynamic parameters to be passed to the iView/page.  The expected format is name1=value1&name2=value2 etc.
Example
Following is the definition of an action that launches an IView with id ROLES://portal_content/com.sap.pct/every_user/general/iViews/myDemoIView.
<Action name="launchIView" handler="IViewLauncher">
  <Properties>
   <Property name="iview" value="ROLES://portal_content/com.sap.pct/every_user/general/iViews/myDemoIView"/>
  </Properties>
</Action>
Example on how to configure an action to launch a Portal Component com.sap.netweaver.bc.uwl.ui.DemoIView:
<Action name="launchIView" handler="IViewLauncher">
  <Properties>
   <Property name="iview" value="com.sap.netweaver.bc.uwl.ui.DemoIView"/>
  </Properties>
</Action>
Example on how to configure an action to launch a Portal Page with id ROLES://portal_content/com.sap.pct/every_user/general/Pages/com.sap.km.MyInfoDiscussions:
<Action name="launchIView" handler="IViewLauncher">
<Properties>
  <Property name="page" value="ROLES://portal_content/com.sap.pct/every_user/general/Pages/com.sap.km.MyInfoDiscussions"/>
</Properties>
</Action>
Description
The following parameters are optionally passed on to the iView, WHEN no parameters are explicitly defined.
wi_id - work item id in the provider system
destination - system alias in the Portal system landscape of the provider system
item_id - internal UWL item id
task - provider task item type
uname - backend user id for webflow connector, alert connector and generic ABAP connector, otherwise Portal user id
langu - user language in upper case ISO language code
Additional custom defined parameters are also supported. They can be static and dynamic, i.e., substituted with an actual value during the run time.
Example of a static parameter:
<Action ...>
<Properties>
<Property name="fruit" value="apple"/>
</Properties>
</Action>
This will append &fruit=apple to the constructed url.
Dynamic property values should start with ${ . These values could come from either the Item or some common values like user.
${item.attributeName}
$ - a backend user id corresponding to the logged in Portal user if the provider system is an R3 system
attributeName is case sensitive, and must be either a custom attribute for the item, or one of the following already defined attributes:
appContext attachmentCount completedDate connectorId createdDate creatorId description dueDate  escalatedBy executionUrl expiryDate externalId externalObjectId externalType forwardedBy forwardedDate internalId isEscalated itemType memoCount parentItemId priority processDueDate processor status subject  subprocessId substitutedFor systemId userId (see description).
An example of using dynamic properies:
<Action ...>
<Properties>
<Property name="workitemId" value="${item.externalId}"/>
<Property name="system" value="${item.systemId}"/>
</Properties>
</Action>
This will result in passing workitemId and system parameters to the target page/iView.  This is the same as specifying iviewDynamicParameter property:
<Action ...>
<Properties>
<Property name="iviewDynamicParameter" value="workitemId=${item.externalId}&amp;system=${item.systemId}"/>
</Properties>
</Action>
Note.  For webflow connector iViewLauncher can be configured on the backend using SWFVISU transaction.  The table below summarizes the mapping between the launcher parameters and the visualization parameters.
Launcher parameter Visualization Type Visualization Parameter
page Portal Page ID
iview iView ID
iviewDynamicParameter iView/Portal Page DYNPARAM
UrlLauncher  
UrlLauncher can be used to launch any url.
Provider specific Information
UrlLauncher is Provider agnostic. Items may belong to any connector.
Supported Actions
Action name can be anything.
Properties
UrlLauncher expects the following property:
url mandatory; url to be launched.
All other properties will be passed as name=URL encoded value to the target url.
Example
Following is the definition of an action that launches a url my.web.com and passes to it the parameter workitem_id, which is filled with the work item id during run time:
<Action name="launchUrl" handler="UrlLauncher">
<Properties>
  <Property name="url" value="http://my.web.com"/>
  <Property name="workitem_id" value="${item.externalId}"/>
</Properties>
</Action>

Similar Messages

  • Difference between url-pattern / and /*  ?

    There appears to be a subtle difference between:
    <url-pattern>/</url-pattern>and
    <url-pattern>/*</url-pattern>Both seem to send all requests through the servlet I'm aming for, but the /* on messes up forwards to JSP files. My app works as I expect when I use the "/" version (I don't need suffixes or prefixes since I've written some routing code). I'm wondering if they are supposed to be behave differently or if my Tomcat container has a little bug I'm exploiting wrongly?
    If you use the "/" version, would you expect a URL like this to map to it....
    http://mysite.com/
    ... and also ones like this...
    http://mysite.com/some/arbitrary/path/here
    ?

    Same question appears here:
    http://saloon.javaranch.com/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic&f=7&t=019661
    And with lot of discussion.

  • What is difference between bex analyser and bex browser

    what is difference between bex analyser and bex browser . please explain what are use of both and what we do in both.

    hi
    Bex Browser
    The Business Explorer Browser (BEx Browser) makes it possible for you to access all document types of the Business Information Warehouse that are assigned to your role or that you have stored in your favorites. You can select and open documents assigned to you in the BEx Browser or store and manage new documents in the BEx Browser.
    Document types that you can work with in the BEx Browser are:
    · BW workbooks
    · Documents that are stored in the Business Document Service (BDS)
    · Links (references to file system, shortcuts)
    · Links to internet sites (URLs)
    · SAP transaction calls.
    · Web applications and Web templates
    · Crystal Reports
    Bex Analyser
    The Business Explorer Analyzer (BEx Analyzer) is the analysis and reporting tool of the Business Explorer that is embedded in Microsoft Excel.
    Features
    You can call up the BEx Query Designer in the BEx Analyzer, in order to define queries. Subsequently, you can analyze the selected InfoProvider data by navigation to the query created in the Query Designer and create different query views of the data. You can add the different query views for a query or for different queries to a work book and save them there. You can save the workbook in your favorites or in your role on the BW Server. You can also save the workbook locally on your computer.
    Beyond that, you can precalculate the workbook and distribute it by e-mail to recipeients or you can export it to the Enterprise Portal and make it accessible to other employees in the company.
    You can start queries in a standard view (with a Standard Web Template set up in Customizing) in the Web browser and forward the URL or continue to navigate on the Web. Similarly, you can export the Web query to MS Excel 2000.
    Overview of the Functional Area of the BEx Analyzer:
    ·        BEx toolbar
    You access the functions of the BEx Analyzer from the BEx toolbar, which takes you to the BEx Open dialog box where you can open existing queries, or to the BEx Query Designer where you can create new queries or change existing queries.
    ·        Evaluating Query Data
    The BEx Analyzer offers convenient functions for evaluating and presenting InfoProvider data interactively. In the BEx Analyzer, you can add queries to workbooks, navigate within them and refresh the data. You can also process the queries further in Microsoft Excel or display them in the Web browser in a default view.
    Navigation of a query allows you, for example, to filter characteristics on a single value, drilldown on all values for a characteristic, regroup characteristics and key figures in the rows and columns of the results area, or hide key figures. Navigation results in different views of the InfoProvider data. In addition, a range of further functions is available which allow you to edit a query interactively (for example, sorting, cumulated output, among others). In addition, you can use the editing functions in Microsoft Excel in order to set up individual format templates, to print results areas, or to create graphics.
    ·        Queries in Workbooks
    Queries are inserted into workbooks so you can display them. When you insert a query, a link is made between the cell areas of the worksheet and the data of the InfoProvider upon which the query is based. A link therefore exists between the Business Explorer and the Business Information Warehouse Server (BW Server).
    When inserting a query into the workbook, a VBA routine is automatically generated in the workbook. You can also connect the Business Explorer with your own VBA programs (Visual Basic for Applications).
    You can create workbook templates, into which you can insert your queries. Workbook templates can contain pre-determined items for the area of the query, formatting settings, logos, VBA macros, and so on.
    ·        Precalculating workbooks
    You can precalculate and distribute workbooks with the BEx Broadcaster, which is a Web application you get to form the BEx toolbar. The system generates MS Excel workbooks with historical data. You determine the time for precalculation yourself: You can have workbooks precalculated at a predefined time or they can be precalculated whenever data in the underlying InfoProvider changes. You can have the precalculated workbooks sent by e-mail or you can export them into the Enterprise Portal, where you can make them available to employees within your company.
    Activities
    To start the BEx Analyzer, choose Start ® Programs ® SAP Front-end Business Information Warehouse ® SAP Business Explorer Analyzer.
    You can also access the BEx Analyzer via SAP Easy Access ® SAP Business Information Warehouse ® SAP Menu ® Business Explorer ® Analyzer or in the Business Explorer Browser using the Business Explorer Analyzer symbol in the menu bar.
    Hope this will solve your issu
    nagarjuna

  • Difference between connection pooling and simple connection

    Anybody please tell me what is the Difference between connection pooling and simple connection and also where we define connection pooling and how.
    Thanks
    Please reply soon
    amitindia

    Creating and closing connection to the database is a relatively slow process. Equally connections use database resources so you can't just open as many as you want.
    A connection pool maintains a number of open connections throughout the lifetime of the application. Instead of opening and closing the connections your application just "borrows" them from the pool when they're needed.
    If the pool runs out of connections it will usually create new ones as needed until you reach some predefined upper limit.
    A good connection pool will also manage connections which have failed for any reason, and report code which fails to return connections to the pool (ie connection leaks).
    The number of connections created at startup is referred to as the "low water mark" and the maximum number that the pool will allow to be opened at any given time is the "high water mark". If no connections are available client code will generally block until one is released.
    If by "defined" you mean where can you get a working implementation then your database or application server vendor is likely to provide one. Also the Apache Jakarta Commons includes [url http://jakarta.apache.org/commons/dbcp/]an implementation which you can use with any JDBC driver.
    Dave.

  • Question about main difference between Java bean and Java class in JSP

    Hi All,
    I am new to Java Bean and wonder what is the main difference to use a Bean or an Object in the jsp. I have search on the forum and find some post also asking the question but still answer my doubt. Indeed, what is the real advantage of using bean in jsp.
    Let me give an example to illustrate my question:
    <code>
    <%@ page errorPage="errorpage.jsp" %>
    <%@ page import="ShoppingCart" %>
    <!-- Instantiate the Counter bean with an id of "counter" -->
    <jsp:useBean id="cart" scope="session" class="ShoppingCart" />
    <html>
    <head><title>Shopping Cart</title></head>
    <body bgcolor="#FFFFFF">
    Your cart's ID is: <%=cart.getId()%>.
    </body>
    <html>
    </code>
    In the above code, I can also create a object of ShoppingCart by new operator then get the id at the following way.
    <code>
    <%
    ShoppingCart cart = new ShoppingCart();
    out.println(cart.getId());
    %>
    </code>
    Now my question is what is the difference between the two method? As in my mind, a normal class can also have it setter and getter methods for its properties. But someone may say that, there is a scope="session", which can be declared in an normal object. It may be a point but it can be easily solved but putting the object in session by "session.setAttribute("cart", cart)".
    I have been searching on this issue on the internet for a long time and most of them just say someting like "persistance of state", "bean follow some conventions of naming", "bean must implement ser" and so on. All of above can be solved by other means, for example, a normal class can also follow the convention. I am really get confused with it, and really want to know what is the main point(s) of using the java bean.
    Any help will be highly apprecaited. Thanks!!!
    Best Regards,
    Alex

    Hi All,
    I am new to Java Bean and wonder what is the main
    difference to use a Bean or an Object in the jsp. The first thing to realize is that JavaBeans are just Plain Old Java Objects (POJOs) that follow a specific set of semantics (get/set methods, etc...). So what is the difference between a Bean and an Object? Nothing.
    <jsp:useBean id="cart" scope="session" class="ShoppingCart" />
    In the above code, I can also create a object of
    ShoppingCart by new operator then get the id at the
    following way.
    ShoppingCart cart = new ShoppingCart();
    out.println(cart.getId());
    ...Sure you could. And if the Cart was in a package (it has to be) you also need to put an import statement in. Oh, and to make sure the object is accessable in the same scope, you have to put it into the PageContext scope. And to totally equal, you first check to see if that object already exists in scope. So to get the equivalant of this:
    <jsp:useBean id="cart" class="my.pack.ShoppingCart"/>Then your scriptlet looks like this:
    <%@ page import="my.pack.ShoppingCart %>
    <%
      ShoppingCart cart = pageContext.getAttribute("cart");
      if (cart == null) {
        cart = new ShoppingCart();
        pageContext.setAttribute("cart", cart);
    %>So it is a lot more work.
    As in my mind, a normal class can also
    have it setter and getter methods for its properties.True ... See below.
    But someone may say that, there is a scope="session",
    which can be declared in an normal object.As long as the object is serializeable, yes.
    It may be
    a point but it can be easily solved but putting the
    object in session by "session.setAttribute("cart",
    cart)".Possible, but if the object isn't serializable it can be unsafe. As the point I mentioned above, the useBean tag allows you to check if the bean exists already, and use that, or make a new one if it does not yet exist in one line. A lot easier than the code you need to use otherwise.
    I have been searching on this issue on the internet
    for a long time and most of them just say someting
    like "persistance of state", "bean follow some
    conventions of naming", "bean must implement ser" and
    so on. Right, that would go along the lines of the definition of what a JavaBean is.
    All of above can be solved by other means, for
    example, a normal class can also follow the
    convention. And if it does - then it is a JavaBean! A JavaBean is any Object whose class definition would include all of the following:
    1) A public, no-argument constructor
    2) Implements Serializeable
    3) Properties are revealed through public mutator methods (void return type, start with 'set' have a single Object parameter list) and public accessor methods (Object return type, void parameter list, begin with 'get').
    4) Contain any necessary event handling methods. Depending on the purpose of the bean, you may include event handlers for when the properties change.
    I am really get confused with it, and
    really want to know what is the main point(s) of
    using the java bean.JavaBeans are normal objects that follow these conventions. Because they do, then you can access them through simplified means. For example, One way of having an object in session that contains data I want to print our might be:
    <%@ page import="my.pack.ShoppingCart %>
    <%
      ShoppingCart cart = session.getAttribute("cart");
      if (cart == null) {
        cart = new ShoppingCart();
        session.setAttribute("cart", cart);
    %>Then later where I want to print a total:
    <% out.print(cart.getTotal() %>Or, if the cart is a JavaBean I could do this:
    <jsp:useBean id="cart" class="my.pack.ShoppingCart" scope="session"/>
    Then later on:
    <jsp:getProperty name="cart" property="total"/>
    Or perhaps I want to set some properties on the object that I get off of the URL's parameter group. I could do this:
    <%
      ShoppingCart cart = session.getAttribute("cart");
      if (cart == null) {
        cart = new ShoppingCart();
        cart.setCreditCard(request.getParameter("creditCard"));
        cart.setFirstName(request.getParameter("firstName"));
        cart.setLastName(request.getParameter("lastName"));
        cart.setBillingAddress1(request.getParameter("billingAddress1"));
        cart.setBillingAddress2(request.getParameter("billingAddress2"));
        cart.setZipCode(request.getParameter("zipCode"));
        cart.setRegion(request.getParameter("region"));
        cart.setCountry(request.getParameter("country"));
        pageContext.setAttribute("cart", cart);
        session.setAttribute("cart", cart);
      }Or you could use:
    <jsp:useBean id="cart" class="my.pack.ShoppingCart" scope="session">
      <jsp:setProperty name="cart" property="*"/>
    </jsp:useBean>The second seems easier to me.
    It also allows you to use your objects in more varied cases - for example, JSTL (the standard tag libraries) and EL (expression language) only work with JavaBeans (objects that follow the JavaBeans conventions) because they expect objects to have the no-arg constuctor, and properties accessed/changed via getXXX and setXXX methods.
    >
    Any help will be highly apprecaited. Thanks!!!
    Best Regards,
    Alex

  • Portal eventing between WD java and BSP popup

    Hi guys,
    I have a WebDynpro application that opens a BSP popup like that :
    WDPortalNavigation.navigateAbsolute(
              wdContext.currentURLElement().getEvaluationURL(),
              WDPortalNavigationMode.SHOW_EXTERNAL,
              "directories=no location=no menubar=no resizable=yes status=no toolbar=no",
              "evaluationdeformation",
              WDPortalNavigationHistoryMode.NO_DUPLICATIONS,
              urlParam.toString()
    When the popup is closed, I want to update the content of my webdynrpo application. I tried using portal eventing but it didn''t worked because the popup doesn't seem to know its opener....
    Is anybody have an idea ?
    Thanks in advance.
    Julien.

    Hi Julien,
    have you made sure that your BSP application is using EPCF? There is a flag you need to set to X in your BSP app for this to take effect. Also, you can not add javascript to a WD app, so calling the window.opener will not make any difference. However, you can subscribe to an event raised by another application in your WD app. It is possible to raise events between windows, one being a bsp and the other a WD or portal application. Check the following threads.
    [Portal Eventing: EPCMPROXY calls between two browser windows;
    [Client side eventing between MSS teamviewer and BSP application;
    Cheers,
    Dion

  • Difference between IDOC Bundling and IDOC Packaging

    Hi,
    Can anybody please explain the difference between IDOC bundling and IDOC packaging?
    Thanks,
    Loveena.

    Hi,
    IDoc Bundling is the changing the occurance of IDoc.
    In a scenario If there is a necessitity for changing the Occurance of some segment of the IDOC u have to perform this steps
    1.Import the IDoc to XI.
    2.Export the IDoc(i.e XSD format) and save it to the local machine.
    3.Make changes to the IDoc structure by modifying the XSD file in the local machine.
    4.Save it as an XSD file Itself.
    5.Import the XSD file in the IR under the External Defination.
    6.Use this XSD in your Message Interface/Mapping which is same as IDoc structure but with some changes that u have made.
    Go Thru this Blog <a href="/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change Bundling - Trick without BPM</a> BY Michal Krawczyk where the Occurance of the IDoc is changed to 1...Unbounded from 1...999999999 by using the XSD.
    IDoc Packing is collecting of IDoc
    <a href="/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm of Multiple type IDOCs in BPM</a> BY Pooja
    Regards
    Santhosh
    Remember to set the thread to solved when you have received a solution
    [url=Use a Good Subject Line, One Question Per Posting - Award Points;  Use a Good Subject Line, One Question Per Posting - Award Points[/url]

  • Differences between PT8.51 and PT8.52 versions

    Hi,
    Can I get some documentation or reference URL for differences between PT8.51 and PT8.52 versions?
    Thank You!
    Regards
    Soundappan

    In addition, specially for the YouTube generation, Gray Sparling has created a great webinar on the features of PeopleTools 8.52
    http://www.youtube.com/playlist?list=PL9B370AEEF80F8C10&feature=plcp
    I have also written a couple of blogs on some feaures of PeopleTools 8.52
    http://bloggingaboutoracleapplications.org/bi-publisher-enhancements-peopletools-852/
    http://bloggingaboutoracleapplications.org/create-interactive-dashboard-interwindow-communication-iwc/
    http://bloggingaboutoracleapplications.org/create-apealing-dashboards-peopletools-852/
    http://bloggingaboutoracleapplications.org/peoplesoft-oracle-secure-enterprise-search-ses/
    http://bloggingaboutoracleapplications.org/peopletools-852-generally/
    That should keep you busy for some wile :)

  • Difference between webservices model and adaptive  webservices model

    hi
        Can any one explain me regarding Difference between webservices model and adaptive  webservices model.
    Thanks

    Hi,
    In old WS Model, ithere was no concept of logical destinations.
    There if you are using a WSDL located on a server and if the location of the WSDL
    changes, your application won't run. The deployed application using the WS Model will have trouble finding
    the WSDL. As a result you'll have to again import the
    model. Moreover old WS Model does not have re-import functionality.
    But incase of AWS Model, you can desine logical destinations and even if the location of the WSDL changes, all you have to do is change the new url in the Visual Admin and not import the model again.
    You can visit the following link for more details:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b04308ed-62d5-2910-b3a6-c26771b1c78e
    Regards,
    Nidhi

  • Differences between Netweaver 2004 and Netweaver 2004s?

    Hi All,
    Can anyone please explain me in details the major differences between Netweaver 2004 and Netweaver 2004s.
    Thanks in advance
    Regards
    Henry

    Hi Henry,
      This content i got from experts:
      The code developed on 2004 will work on 2004s.
    Some minor changes have been made refer to the documentation for specific details
    SAP NW2004s is the mySAP Business Suite edition of SAP NW 2004.it is a minor release that delivers on specific needs of the mySAP and xapps solutions delivered by SAP in 2005. the "s" stands for "mySAP Business Suite Edition".
    The next major release of NW will deliver on Business Process Platform(BPP) it will be released in 2006.
    Few of the New capabilities in NW2004s
    1)Developing a web based user interface with Web Dynpro fro ABAP.
    2)Enhancements to enabling B2B processes
    3)Enhancements to business task management
    4)Enhancements to business planning
    5)Enhancements to enterprise data warehousing
    6)mass setup of mobile devices
    7)implementing a global portal
    Refer the link for more info
    http://help.sap.com/saphelp_nw04s/helpdata/en/5b/8c3842bb58f83ae10000000a1550b0/frameset.htm
    http://help.sap.com/saphelp_nw04s/helpdata/en/57/a21f407b402402e10000000a1550b0/frameset.htm
    NW04 is a 'Java version' which means you can develop applications using Java and export them to portal.
    NW04s is a 'ABAP version'.Here you can develop ABAP reports and transactions and export them to portal. There you can create iViews using them.
    Netweaver 04s, includes both the ABAP and Java stacks. The Sneak preview for NW04s is only for the ABAP stack, and the Sneak Preview NW04 SP15 is only the java stack. If you are using the sneak preview for ABAP, you can develop WDA applications and BSP applications, they run directly in the engine, not in a portal. But they can be embeded in an iView in some portal. You don't have to have a portal to run your application. If you are using the java side, you can develop WDJ applications and JSP applications. Same applies here, they run on the java engine, not in a portal, but can be embeded into an iView which runs on the portal. But you don't need a portal for your application to run. The portal is just a frontend UI, the apps themselves run on the underlying engine, whether its ABAP or JAVA.
    Refer to the following threads for more information
    Re: What is NW04 s?
    Re: Differences between NW04 SP11 and NW04 SP15
    I hope this will help you
    Regards
    Suresh

  • Difference Between SDM Deployment and JSPM

    Hello All,
    Can anybody tell me the difference between SDM Deployment and JSPM.
    please guide me in brief or guide any URL
    Thanks & Regards
    Shishir

    Shishir,
    Do refer the following links
    Java Support Package Manager (JSPM) - http://help.sap.com/saphelp_nw04s/helpdata/EN/87/4797422930c56ae10000000a155106/frameset.htm
    Software Deployment Manager (SDM) - http://help.sap.com/saphelp_nw04/helpdata/en/22/a7663bb3808c1fe10000000a114084/frameset.htm
    The first page of the links itself describes the purpose of the tools. Also, do use the search features of the forum and search on help.sap.com. Most of the queries are already asked or present in the help documentation.
    Thanks,
    GLM

  • Difference between RFC adapter and a proxy

    Can any one tell me the technical difference between RFC adapter and a proxy?
    reg

    There are advantages / disadvantages for RFC / Proxies / Idocs. So if I am in your position depending upon the requirement I will choose one. Some of the differences are:
    RFC and Proxy:
    RFC/BAPI has its own overhead of function call.
    Proxies communicate with the XI server by means of native SOAP calls over HTTP .RFC does not, so you have to convert from SOAP to RFC calls and vice versa. So XML conversion is required.
    ABAP Proxies uses Webservice and Http Protocols.
    If you use ABAP Proxy , you can reduce the overhead calling the function again and again.
    Proxy and Idoc:
    IDOC : After recieving the strucutred data It processes it using a Function Module associated with it.
    Proxy : Proxy is a structure where there is no processing function module associated. You need to explicitly write the Business Logic/Call the subroutines here
    This is my absolutely my view. Another guy has his own response. So first go through your requirements and then you can decide for what to go.
    Also go through this urls which may help you:
    /people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachments
    RFC VS PROXY
    /people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
    Re: IDOC and RFC
    Re: Proxy Vs IDOC
    Thanks
    Rodrigo

  • Difference between jsp:include and %@ include

    what is the difference between <jsp:include> and <%@ include %>? which has better performance? When to use which? suppose i have a menu that should be included in every page, which should I use?
    Thank you
    Cal

    <%-- some date this page was last updated with that particular version of JSP file --%>
    <% include file="relative URL" %>
    You use the include directive, as indicated, to include a file in the main JSP file at the time the file is translated into a servlet. This is done at translation time and therefore if the included JSP file changes, all the JSP files that use this included file will need tobe updated. If you use this include statement then i would suggest that you add a date descriptor of the last time it was modifed so that you can go back and tell if you have updated a particular JSP file or not.
    <jsp:include page="relative url" flush = "true" />
    When you use the JSP descriptor like this, you are getting the requested JSP file at REQUEST time and therefore you do not hae to worry about updating the calling JSP page.
    Hope this helps

  • Difference between line type and table type

    hi,
    can any one explain the difference between line type and table type . and how to declare a internal table and work area in BSP's

    hi,
    Go through this blog, this might help you.
    /people/tomas.altman/blog/2004/12/13/sdn-blog-how-to-do-internal-tables-in-bsp
    People who have worked with ABAP for a while sometimes forget that the internal table concept is rather different than what exists in most programming languages. It is very powerful, but at the same time can be confusing.
    In SAP it is possible to have a table which is the rows and a headerline which is the working area or structure which can then be commited to the table.
    With a BSP, if we try to create an internal table within the BSP event or layout we will get the following error: mso-bidi-
                            "InternalTableX" is not an internal table - the "OCCURS n" specification is mso-bidi- missing.
    class="MsoNormal"><![if !supportEmptyParas]>The problem we are seeing as an inconsistency has to do with the difference between classic ABAP and ABAP Objects. When SAP introduced ABAP Objects they decided to clean up some of the legacy syntax and create stricter rules. However they didn't want to break the millions of line of code that already existed, so they only implemented these stricter checks when OO is being used. Therefore you can declare a table with a header line in a regular ABAP program or Function Module but you can't have one with a header line in OO.
    Because everything in BSP generates ABAP OO classes behind the scenes, you get these same stricter syntax checks. My suggestion is that you have a look in the on-line help at the section on ABAP Objects and always follow the newer syntax rules even when writing classic ABAP programs.
    In a BSP when we need to work with a table we must always do the following:
    1, in the Types definitions create a structure:
                            types : begin of ts_reclist,
    mso-bidi-        style='mso-tab-count:2'>                            receiver type somlreci1-receiver,
    mso-bidi-        style='mso-tab-count:2'>                 style='mso-tab-count: 1'>             rec_type type somlreci1-rec_type,
    mso-bidi-         style='mso-tab-count:2'>                            end of ts_reclist.
    mso-bidi- <![if !supportEmptyParas]> <![endif]>
    but we must remember this is only a structure definition and we cannot store anything in it, although we can use it elsewhere as a definition for Structures(WorkAreas)
    2, in our Types definitions (this is the best place for this one as we can then access it from many areas without having to create it locally) so in the Types definitions we must create a TableType:
    class="MsoNormal">                         types : tt_reclist type table of ts_reclist.
    class="MsoNormal"><![if !supportEmptyParas]> <![endif]> this TableType is our table definition and again we cannot store anything in it, but we can use it elsewhere as a definition for InternalTables
    3, now that you have laid the foundations you can build and in the event handler, it is now simply a case of creating the InternalTable based upon the Table definition:
                           data: t_reclist type tt_reclist.
    and creating the structure based upon the structure definiton:
    <![if !supportEmptyParas]>   <![endif]>                         data: s_reclist type ts_reclist.
    as described above, the structure becomes the work area and this is where you assign new values for elements of the table eg:<![endif]>
                            s_reclist-receiver = '[email protected]'.   "<-- change address
    mso-bidi- <![if !supportEmptyParas]> <![endif]>
    mso-bidi-                         s_reclist-rec_type = 'U'.
    and then once the data is in the elements of the structure, the structure can be appended to the internal table as follows: class="MsoNormal">
                            append s_reclist to t_reclist.
    <![if !supportEmptyParas]> <![endif]>
    the internal table will then be readable for the ABAP function and can be applied for example as follows: class="style1">           style='mso-tab-count:1; font-family: "Courier New", Courier, mono;'>          
    class="style1">CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
                            EXPORTING
    style='mso-tab-count:2'>                                    document_data = docdata
    style='mso-tab-count:2'>                                    DOCUMENT_TYPE = 'RAW'
    style='mso-tab-count:2'>                                    PUT_IN_OUTBOX = 'X'
    style='mso-tab-count:2'>                                    COMMIT_WORK = 'X' "used from rel.6.10
                            TABLES
    mso-bidi-font-size: style='mso-tab-count:2'>                                    receivers = t_reclist
    class="style1"> <![if !supportEmptyParas]>   <![endif]>
    <![if !supportEmptyParas]>F inally, a comment from Thomas Jung,
    <![if !supportEmptyParas]> “when defining my work area for an internal table I like to use the like line of statement. That way if I change the structure of my table type, I know that my work area will still be OK. Second, your types and table types don't have to just be declared in your code. You can create a table type in the data dictionary and use it across multiple programs(also great for method and function parameters). I really push hard for the other developers at my company to use the Data Dictionary Types more and more.”
    Hope this helps, Do reward.

  • Major and minor Functional difference between 4.6c and ecc 6 in SD module

    Hi Gurus,
    Will anyone will mail me doc or url that shows the Major and minor Functional difference between 4.6c and ecc 6 in SD module.  Mail me at [email protected]
      full points for helpful answer
      Regards,
    PV

    Hi,
    This website is very helpfull for version comparision, have a look at it.
    <a href="http://solutionbrowser.erp.sap.fmpmedia.com/">Compare_Versions</a>
    Cheers...
    Santosh

Maybe you are looking for