Sap Crm Web Ui Cookbook

SAP CRM 2006sThe Fast Track to SAP Knowledge Introduction to Web Client UI Architecture Frederic Heinemann CRM Consulting EMEA Hub AGENDA Layer Overview BOL/Genil UI Component Concept UI Component Elements UI Component Interface and Usage Cross Component Navigation Component Enhancement Concept Concepts Technical Basics © SAP AG 2007, SAP Skills Knowledge The Fast Track to SAP 2007 Conference / F4 / 2 AGENDA Layer Overview BOL/Genil UI Component Concept UI Component Elements UI Component Interface and Usage Cross Component Navigation Component Enhancement Concept Concepts Technical Basics © SAP AG 2007, SAP Skills Knowledge The Fast Track to SAP 2007 Conference / F4 / 3 g. Interfaces (APIs) Tables Layers of underlying Business Application Business Engine (e. Progr. SAP Skills 2007 Conference / F4 / 4 .Layers of SAP CRM 2006s/2 Applications Web Browser CRM WebClient Presentation Controller Layer Model CRM WebClient specific Layers View Business Server Pages (BSPs) Business Layer Business Object Layer (BOL) Generic Interaction Layer (GenIL) Appl. mySAP CRM) © SAP AG 2007. Layers of CRM 5. mySAP CRM) © SAP AG 2007.g. SAP Skills 2007 Conference / F4 / 5 . Interfaces (APIs) Tables Layers of underlying Business Application Business Engine (e.1 Applications Web Browser CRM WebClient Presentation Controller Layer Model CRM WebClient specific Layers View Business Server Pages (BSPs) Business Layer Business Object Layer (BOL) Generic Interaction Layer (GenIL) Appl. Progr. Component – General Parts NavBar (Profile) Logical Link Main Component M Technical ID = (Target-ID) Display IP IP IP Sub component Search Window Sub component Header Search IP OP Window ViewSet ViewSet View OP View OP OP © SAP AG 2007. SAP Skills 2007 Conference / F4 / 6 . Marketing) have own naming conventions – GS<speaking string> = General Services ( Reusable Components) – BT<speaking string> = reusable components for Transactions © SAP AG 2007.UI Component is the logical grouping for UI implementation is assigned to a package SAP Naming conventions – Oneorder . „H“. SAP Skills 2007 Conference / F4 / 7 .g.BT<object><type>_<speaking string> where <type> is „S“. Business Partner. „I“ or „M“ – Other components ( e. SAP Skills 2007 Conference / F4 / 8 .Component Workbench: View. Controller and Model Controller: Class Model: Context & Context Nodes Controller: Event Handling & Navigation View: Layout Transaction Code BSP_WD_CMPWB © SAP AG 2007. Component Workbench: Context Nodes. SAP Skills 2007 Conference / F4 / 9 . Attributes Context Context Nodes Attributes (Fields) © SAP AG 2007. SAP Skills 2007 Conference / F4 / 10 . There is no longer one central repository. © SAP AG 2007.Component Workbench (I) Browser Application Structure Inventory of all items – Views – Component Controllers – Custom Controllers – Windows – Runtime Repository* * Each UI Component has it’s own Runtime Repository. g. navigational links.Component Workbench (II) Runtime Repository Editor Inventory of all items – Windows – View sets – Navigational Links – Component Interface – Component Usage The runtime repository editor is not only a visualization tool for the xml file. SAP Skills 2007 Conference / F4 / 11 . © SAP AG 2007. but offers a set of functionality as wizards to create e. SAP Skills 2007 Conference / F4 / 12 .Component Workbench (III) BOL Model Browser Access BOL Model from Component Workbench Direct testing of component (or with alternative Test Application) © SAP AG 2007. SAP Skills 2007 Conference / F4 / 13 .g. Progr.Layers of CRM 5.1 Applications Web Browser CRM WebClient Presentation Controller Layer Model CRM WebClient specific Layers View Business Server Pages (BSPs) Business Layer Business Object Layer (BOL) Generic Interaction Layer (GenIL) Appl. Interfaces (APIs) Tables Layers of underlying Business Application Business Engine (e. mySAP CRM) © SAP AG 2007. SAP Skills 2007 Conference / F4 / 14 .BOL and GenIL: Tools Presentation Controller Layer View BSP Model BOL Display BOL Model Business Layer GenIL Transaction: BSP_WD_CMPWB or GENIL_MODEL_BROWSER GenIL IMG: Generic Interaction Layer/Object Layer Basic Settings test data retrieval from database to BOL through the GENIL Transaction: GENIL_BOL_BROWSER Business Engine API API API © SAP AG 2007. BOL and GenIL: Tools Model Browser: Visualizing BOL Model Presentation Layer (BSP) Layers of new UI Framework Business Layer (BOL) Interaction Layer (GenIL) BOL Browser: Testing Data retrieval from DB to BOL Layers of Business API underlying Engine Business (e.g. mySAP CRM) Application Tables © SAP AG 2007. SAP Skills 2007 Conference / F4 / 15 . SAP Skills 2007 Conference / F4 / 16 .© SAP AG 2007. SAP Skills 2007 Conference / F4 / 17 . © SAP AG 2007. The navigation direction is a characteristic of the relation.Definitions 1 Business Object (BO): Smallest unit of an object model with exclusively unstructured attributes. Each BO is assigned a unique name. crosscomponent name. Object model: Number of BOs and their relations. a dependent object or a query object. Relation: A relationship between two BOs that is assigned a unique. The relation is assigned “a cardinality value” for each BO. BO instance: Instance of a BO that is uniquely identified by the name of the BO and an identifier (ID). A BO can be either an access object. whose attributes cannot be determined solely from the ID of this BO. Each root object is also an access object. The result object of a search request is an associated access object at the uppermost level of the hierarchy. whose ID can be used to determine both the attributes of the access object itself and those of its dependent objects. Dynamic Search-Object: Search Result Object: A dynamic query object is a type of BO whose attributes are the parameters of a search request.Definitions 2 Access Object: An access object is a special type of BO. SAP Skills 2007 Conference / F4 / 18 . but instead. Root object: A root object is a special element within a group of objects that are linked to one another in a hierarchy structure via aggregations. Search-Object: A query object is a special type of BO whose attributes are the parameters of a search request. The root object is the only object within this structure that is assigned as a superior object to all other objects. only or together with the ID of the superior access object. It is possible to create select options for these parameters. Dependent Object: A dependent object is a special type of BO. © SAP AG 2007. . SAP Skills 2007 Conference / F4 / 19 ..Getting to know the GENIL. Access the GENIL Component Details Transaction: SPRO ->IMG -> Customer Relationship Management -> CRM Cross-Application Components -> Generic Interaction Layer/Object Layer -> Basic Settings © SAP AG 2007. Component Set A component set is a collection of components that build a business context for a specific application that uses the business layer as its framework. Each component must have a unique root object.Definitions 3 Component: A component is an ABAP OO class which implements the component interface. © SAP AG 2007. which form an aggregation hierarchy. SAP Skills 2007 Conference / F4 / 20 . It exposes a set of CRM business objects to the Generic IL. SAP Skills Knowledge The Fast Track to SAP 2007 Conference / F4 / 21 .AGENDA Layer Overview BOL/Genil UI Component Concept UI Component Elements UI Component Interface and Usage Cross Component Navigation Component Enhancement Concept Concepts Technical Basics © SAP AG 2007. . mandatory . hidden. © SAP AG 2007.BOL Services Buffering service – any data is only read once until it is changed – all changes are buffered and will be send together – automatic buffer synchronization in almost all cases Transaction service – objects may be saved individually or all together – all changed/created object will be saved or reverted Query services – New Query service for dynamic searches with CRM 2006 Simple sorting and filtering on object lists (collections) Attribute properties – for each attribute of an entity a property is available – possible properties: read-only.. SAP Skills 2007 Conference / F4 / 22 . Once it was created it ends with either – Saving all covered entities. A transaction context can have several kinds of granularity – The smallest granularity of a transaction context is a root entity instance – The biggest granularity are all changed/created entity instances – The custom transaction context allows any granularity in between Each transaction context has a defined life cycle. SAP Skills 2007 Conference / F4 / 23 .BOL Transaction Model The transactional behavior of BOL objects is modeled in the transaction context. but not yet existing. A transaction context is created: – when an entity is locked. or – Reverting all covered entities © SAP AG 2007. or – if it is requested. BOL Transaction Model 2 Data is always saved synchronously. if this is not possible. SAP Skills 2007 Conference / F4 / 24 . with COMMIT WORK and WAIT After saving the BOL buffer is invalidated and refreshed on the next access After reverting data the BOL buffer is actively refreshed © SAP AG 2007. Either within the dialog process (local update). or. Additionally one global message container exists were all non-business object (BO) instance-related messages should go to. CL_CRM_BOL_CORE 1 1 CL_CRM_GENIL_MESS_CONT_MANAGER 1 * IF_GENIL_MESSAGE_CONTAINER © SAP AG 2007.BOL Services – Message Service Message Service There is one message protocol/container per root object instance and the message container manager handles them all. SAP Skills 2007 Conference / F4 / 25 . SAP Skills 2007 Conference / F4 / 26 .Architectural Overview Browser Client R UI Controller / BSP page R R BOL R Cache R Application Model R Generic IL Data Contai ner R R R R GENIL Order Component R GENIL IBase Component R Other GENIL component R Order API IBAse API Other API © SAP AG 2007. .. SAP Skills 2007 Conference / F4 / 27 .Business Object Layer vs. R R Component IF genIL Component n R API 1 API 2 API .. Generic Interaction Layer Business Object Layer Entities Query Services Core Cache R Generic Interaction Layer Application Interface Generic Interaction Layer R Component IF genIL Component 1 R R Component IF genIL Component 2 R R Component IF genIL Component .. API n Database(s) © SAP AG 2007. SAP Skills 2007 Conference / F4 / 28 .© SAP AG 2007. SAP Skills Knowledge The Fast Track to SAP 2007 Conference / F4 / 29 .AGENDA Layer Overview BOL/Genil UI Component Concept UI Component Elements UI Component Interface and Usage Cross Component Navigation Component Enhancement Concept Concepts Technical Basics © SAP AG 2007. Views of the CRM Web Client Other persistent views Navigation Bar (persistent) view Work area view set view © SAP AG 2007. SAP Skills 2007 Conference / F4 / 30 . AGENDA Layer Overview BOL/Genil UI Component Concept UI Component Elements UI Component Interface and Usage Cross Component Navigation Component Enhancement Concept Concepts Technical Basics © SAP AG 2007. SAP Skills Knowledge The Fast Track to SAP 2007 Conference / F4 / 31 . public context nodes … can have multiple instances at runtime … technically is mapped to a BSP application – thus it is the organizational unit in the development logistic that is assigned to a package © SAP AG 2007. SAP Skills 2007 Conference / F4 / 32 .windows (as interface views) .Own runtime repository . A Component.. …is a meaningful bundle of view sets.Exposes clear interface to the outside: . views and custom controllers …is a self-contained reusable unit – black box approach: ..New Component Concept With the new CRM UI Framework a new concept is introduced valid for all Applications which are based on this Framework. New Window Concept Each component must have one or more windows which are hosting the views A Window. mediates between the embedding and the embedded component during runtime – has the character of a view to the inside (window aspect) – has the character of a simple view to the outside (interface view aspect) © SAP AG 2007. SAP Skills 2007 Conference / F4 / 33 .. … is part of a component and defines a root for a hierarchy of view sets and views in the runtime repository – A viewset or view can only be part of exactly one window (still no direct reuse of views) – Navigation between views is only possible within a single window ….. ViewArea and View ViewSet ViewArea View ViewArea View ViewSet © SAP AG 2007.UI-Elements: ViewSet. SAP Skills 2007 Conference / F4 / 34 . Runtime Repository Each component has its own runtime repository file It acts a a catalogue containing – views. Technically stored as . SAP Skills 2007 Conference / F4 / 35 .xml file Can be displayed and maintained in the Runtime repository editor of the Component workbench © SAP AG 2007. viewsets and the composition of views within viewsets – Navigational links (with target and source view) – Inbound and outbound plugs definitions – etc. HTM *_CN00 *_CN01 e.g. Partner e. SAP Skills 2007 Conference / F4 / 36 .DO _IMPL WD_CREATE_CONTEXT SET_MODELS After Input DO_HANDLE_DATA DO_HANDLE_EVENT Model Context Context Nodes *_ CTXT Method CREATE_CONTEXT_NODES View data output *. Bus. Address Layout: ABAP/HTMLB-code Method GET_S_STRUCT Address Field Structure Response describing the view layout BOL DB Tables © SAP AG 2007.Model View Controller in WebClient BSPs user input Request Controller Class Methods: Before Output * .g. CRM Web Client: View Details In contrast to former implementations the CRM Web Client views can be based on a minimal amount of coding Each configurable view is based on: A page type related configuration tag Structural setters/getters Specific implementations possible via: Dedicated setter/getter implementation Additional usage of base tags © SAP AG 2007. SAP Skills 2007 Conference / F4 / 37 . Attributes (II) Generic Setter Getter methods Explicitly create setter and getter with additional methods: Get_V_ (Value Help) Get_P_ (Properties) © SAP AG 2007. SAP Skills 2007 Conference / F4 / 38 .Component Workbench: Context Nodes. […] WHEN 'new'. …. * navigate op_detailsov( ).Navigation Between Views (in Same Window) Source View DetailsEF …. CALL METHOD eh_onNew. …. © SAP AG 2007. …. […] method OP_DETAILSOV view_manager->navigate( SOURCE_REP_VIEW = rep_view OUTBOUND_PLUG = ‘ToDetailsOV' ). […] […] Button back Method: EH_ONDONE Outbound Plug Method: OP_DETAILSOV Target View DetailsOV …. method EH_ONDONE. Navigation Flow Method: DO_HANDLE_EVENT method DO_HANDLE_EVENT . …. …. …. SAP Skills 2007 Conference / F4 / 39 Inbound Plug Method: IP_FROMDETAILSEF method FROMDETAILSEF . …. …. SAP Skills 2007 Conference / F4 / 40 . GenIL) Database © SAP AG 2007.Custom Controller Presentation Layer (BSP) Lifespan Lifespan Controller View 1 Model Context Node Custom Controller Model Context Node Lifespan Controller View 2 Model Context Node Business Layer (BOL. SAP Skills 2007 Conference / F4 / 41 .© SAP AG 2007. AGENDA Layer Overview BOL/Genil UI Component Concept UI Component Elements UI Component Interface and Usage Cross Component Navigation Component Enhancement Concept Concepts Technical Basics © SAP AG 2007. SAP Skills Knowledge The Fast Track to SAP 2007 Conference / F4 / 42 . Inside perspective A component is represented by a component controller – has a context that is partially public to the outside A component consists of custom controllers and one or more windows that host the views Outside perspective A component can be (re-)used by one or more other components The embedding component defines a component usage in it’s runtime repository to formally declare the dependency Also at runtime the component has access to the component usage to get access to the Interface of the embedded component Each component usage gets it’s own component instance at runtime © SAP AG 2007. SAP Skills 2007 Conference / F4 / 43 .New Component Concept: Inside and Outside View Each component could be looked at from the inside as well as from the outside. but what can be seen is different. Component Controller highest level of all controllers is loaded at initial load of component can serve as data container manages binding of usages manages data transfer between components Binding of Context Node from custom controller to component controller Coding not done by wizard. SAP Skills 2007 Conference / F4 / 44 . has to be inserted manually © SAP AG 2007. SAP Skills 2007 Conference / F4 / 45 . if view request so) to request navigation on the level of the embedding component -> navigation destination is determined by embedding component (runtime repository) © SAP AG 2007.g. Inside: (window aspect) Technically a window is a special type of view – hosts (serves as root viewset ) views and viewsets of the component – has a context that contained views and viewsets can bind to – can trigger navigation inside the window Outside: (Interface view aspect) has inbound and outbound plugs as entry and exit points from the view of the embedding component – inbound plugs are called when the embedding component navigates to the view – can fire an outbound plugs (e.New Window Concept: Inside and Outside View Each Window can as well be seen from the inside as well as from the outside. Component Interface Needs to be defined if a component shall be reusable is defined in the runtime repository editor Context nodes of component controller are made visible to outside Window is made visible to outside © SAP AG 2007. SAP Skills 2007 Conference / F4 / 46 . SAP Skills 2007 Conference / F4 / 47 .Component Usage(1) Components with a component interface can be included in other components (reuse) usages are defined in the runtime repository editor © SAP AG 2007. SAP Skills 2007 Conference / F4 / 48 .Component Usage(2) Component controllers need to be bound against each other this is done in method WD_USAGE_INITIALIZE of the component controller class © SAP AG 2007. SAP Skills 2007 Conference / F4 / 49 .© SAP AG 2007. SAP Skills Knowledge The Fast Track to SAP 2007 Conference / F4 / 50 .AGENDA Layer Overview BOL/Genil UI Component Concept UI Component Elements UI Component Interface and Usage Cross Component Navigation Component Enhancement Concept Concepts Technical Basics © SAP AG 2007. g.g. Service Ticket Scenario I) Navigation from Navigation Bar Button to a Component (Button = Work Center) NavBar Component: e. Service Ticket Link/Button NavBar Component: e.g. Product Details © SAP AG 2007. SAP Skills 2007 Conference / F4 / 51 . Service Ticket Service ticket Scenario II and III) Cross Workarea Component Navigation (always) through Navigation Bar Component: e.Customizing of Navigation: Overview Overview Navigation Bar (as part of L-Shape) Work Area Component: e.g. 3. Component Main Window IP1 IP2 Other Window IP3 IP4 WorkCenter 1. CRMC_UI_NBLINKS Client dependant Define Logical Links LogLink ID: IC_BT_SVT Type: Work Center Target ID: IC_BT_SVT CRMC_UI_WA_COMP_REP Cross client Component Definition: Component Name ICCMP_BT_SVT Window Name Main 3. Logical Link 2.I) Navigation from the Navigation Bar to a Component NavBar (Profile) 0. Inbound Plug Definition: Target ID: IC_BT_SVT IP: DEFAULT Object Type: IC_BT_SVT Object Action: Display 2. SAP Skills 2007 Conference / F4 / 52 1. . Target ID CRMC_UI_NBLINKS Client dependant Define NavBar Profile: Profile: DEFAULT_IC 0. Assign Work Centers: Work Center IC_BT_SVT Define Work Center Work Center: IC_BT_SVT LogicalLink ID: IC_BT_SVT Title: Service Ticket © SAP AG 2007. Main Component M-Component Wrapper for assigned components Manages subcomponents Customizing stores M-Components only Definition of In. SAP Skills 2007 Conference / F4 / 53 .and outboundPlugs of component © SAP AG 2007. II) Cross Component Navigation (Object Type Determined by Outbound (OP) Plug Definition) Component A Main Window Displ. Product 1. NavBar (Profile) Component C Main Window OP1 OP2 2. Object Type Object Action 3. 4. Create Search Other Window Create Search Component B Other Window OP7 OP8 Technical ID (= Target ID) 2. 1. Hard coded CRMS_UI_TLINK Cross client Component Definition: Component Name ICCMP_BT_SVT Window Name Main Outbound Plug Definition: Source ID: OP_SVT_PRO OP: PRODUCT Object Type: IC_PRODUCT 2. Object Action: Display CRMC_UI_NBLINKS Client dependent Define NavBar Profile: Profile: DEFAULT_IC Define Generic OP Mapping: Object Type: IC_PRODUCT ObjAction: Display 3. Target ID: IP_PRODUCT CRMS_UI_TLINK Cross client Component Definition: Component Name ICCMP_PRODUCT Window Name Main Inbound Plug Definition: Target ID: IP_PRODUCT IP: DEFAULT Object Type: IC_PRODUCT Object Action: Display 4. © SAP AG 2007, SAP Skills 2007 Conference / F4 / 54 III) Cross Component Navigation (Object Type Determined by Descriptor Object) Component A Main Window Displ. Ticket Displ. Order Displ. EMail Displ. Prod. 1. 2. NavBar (Profile) 3. 4. Component C Main Window Create Search Technical ID (= Target ID) OP_DEFAULT Object Type Object Action Target ID Target ID 1. Descriptor Object: e.g. Hard coded CL_CRM_UI Obj.Action + a) ObjType or b) BOR Obj Type, Key, Log Sys or c) BOL Obj instance Add to collection hand over to OP Target ID CRMC_UI_NBLINKS Cross client Define NavBar Profile: Profile: DEFAULT_IC CRMS_UI_TLINK Cross client Component Definition: Component Name ICCMP_PRODUCT Window Name Main Inbound Plug Definition: Target ID: IP_PRODUCT IP: DEFAULT Object Type: IC_PRODUCT Object Action: Display 2. In case of b) or c) hard coded* Determination of Object Type * with mapping class in case of b) or c): CRMC_UI_OBJ_MAP or CRMS_UI_OBJ_MAP Define Generic OP Mapping: Object Type: IC_PRODUCT ObjAction: Display Target ID: IP_PRODUCT 4. 3. © SAP AG 2007, SAP Skills 2007 Conference / F4 / 55 Navigation Between M-Components Navigation via Navigation Bar from M to M components CL_CRM_UIU_BT_NAVIGATE=>prepare_col_for_navigate. © SAP AG 2007, SAP Skills 2007 Conference / F4 / 56 SAP Skills 2007 Conference / F4 / 57 .© SAP AG 2007. SAP Skills Knowledge The Fast Track to SAP 2007 Conference / F4 / 58 .AGENDA Layer Overview BOL/Genil UI Component Concept UI Component Elements UI Component Interface and Usage Cross Component Navigation Component Enhancement Concept Concepts Technical Basics © SAP AG 2007. the standard view will be replaced by the copied and modified view This process is supported by wizards © SAP AG 2007.Component Enhancement Principle a ied p Co nd d ifie d mo w Vie r nda Sta w Vie d Views from an existing component can be copied into a customer component The copy can be modified (new context nodes.) At runtime. new buttons. SAP Skills 2007 Conference / F4 / 59 . navigation etc. Component Enhancement Concept: 1 SAP Component Context Comp. Controller Window Main View 1 View 2 View 3 Configure Views Runtime Repository Component Usages View Set Composition Navigation Enhance Component (wizard supported) © SAP AG 2007. SAP Skills 2007 Conference / F4 / 60 . Component Enhancement Concept: 2 SAP Component Context Comp. Controller Customer Component Context Comp. Controller Window Main View 1 View 2 View 3 Window Main View 1 View 2 View 3 Runtime Repository Component Usages View Set Composition Navigation Element Element © SAP AG 2007. SAP Skills 2007 Conference / F4 / 61 Runtime Repository Component Usages View Set Composition Navigation Referenced Copied automatically . Controller Customer Component Context Comp.Component Enhancement Concept: 3 SAP Component Context Comp. SAP Skills 2007 Conference / F4 / 62 Runtime Repository Component Usages View Set Composition Navigation Referenced Copied automatically Inherited if required . Controller Window Main View 1 View 2 View 3 Window Main View 1 View 2 View 3 Runtime Repository Component Usages View Set Composition Navigation Element Element Element © SAP AG 2007. © SAP AG 2007. SAP Skills 2007 Conference / F4 / 63 . AGENDA Layer Overview BOL/Genil UI Component Concept UI Component Elements UI Component Interface and Usage Cross Component Navigation Component Enhancement Concept Concepts Technical Basics © SAP AG 2007. SAP Skills Knowledge The Fast Track to SAP 2007 Conference / F4 / 64 . do CL_BT111H_O_ DETAILSEF_IMPL BT111H_OPPT/ DetailsEF.htm via page attribute and Getter/Setter Create nd ate a Cre d to CL_BT111H_O_ bin L BO DETAILSEF_CN00 BTAdminH OBJECT_ID DESCRIPTION CL_BT111H_O_ DETAILSEF_CTXT C bin reat dt ea o B nd OL BTHeaderOpportunityExt BTOpportH CL_BT111H_O_ DETAILSEF_CN01 BUDGET REVENUE © SAP AG 2007. SAP Skills 2007 Conference / F4 / 65 . Controller.View. Context and Context Node BT111H_OPPT/ CL_BT111H_O_ DETAILSEF Inherit Call Call DetailsEF. htm //CustomerH/attr Call ZCL_ CL_BT111H_O_ Call Inherit DETAILSEF_IMPL DETAILSEF_IMPL WD_CREATE_CONTEXT via page attribute and Getter/Setter Create nd ate a Cre d to CL_BT111H_O_ bin L BO DETAILSEF_CN00 BTAdminH OBJECT_ID DESCRIPTION CL_BT111H_O_ ZCL_DETAILSEF_CTXT DETAILSEF_CTXT CREATE_CONTEXT_NODES Cre bin ate a d to n BO d L BTHeaderOpportunityExt CL_BT111H_O_ DETAILSEF_CN01 BTOpportH BUDGET REVENUE BTHeaderCustExt ZCL_ DETAILSEF_CN00 BTCustomerH attr © SAP AG 2007.Enhancing Context and Context Nodes CL_BT111H_O_ DETAILSEF BT111H_OPPT/ ZCUST/ DetailsEF.do BT111H_OPPT/ ZCUST/DetailsEF.htm DetailsEF. SAP Skills 2007 Conference / F4 / 66 .do DetailsEF. © SAP AG 2007. SAP Skills 2007 Conference / F4 / 67 . OS/400.com. PostScript. OS/390. including but not limited to the implied warranties of merchantability. © SAP AG 2007. DB2 Universal Database. HTML. This document is provided without a warranty of any kind. zSeries. System p5. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages. Sweden. POWER. copied. All Rights Reserved No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. Oracle is a registered trademark of Oracle Corporation. Inc. MVS/ESA. The statutory liability for personal injury and defective products is not affected. The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. Java is a registered trademark of Sun Microsystems. i5/OS. the Adobe logo. and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. and PowerPoint are registered trademarks of Microsoft Corporation. ICA. PartnerEdge. Citrix. z/OS.. SAP NetWeaver. Massachusetts Institute of Technology. pSeries. AS/400. Tivoli. System i. System x. XML. World Wide Web Consortium. SAP assumes no responsibility for errors or omissions in this document. links. used under license for technology invented and implemented by Netscape. text. developments. IBM. WinFrame. X/Open. MetaFrame. or other items contained within this material. graphics. Netfinity. Inc. xApps. or consequential damages that may result from the use of these materials. SAP. All other product and service names mentioned are the trademarks of their respective companies. System i5. This document contains only intended strategies. mySAP. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. S/390. and/or development. Duet. DB2. POWER5+. XHTML and W3C are trademarks or registered trademarks of W3C®. National product specifications may vary. Informix. or non-infringement. either express or implied. Intelligent Miner. and MultiWin are trademarks or registered trademarks of Citrix Systems. System z9. and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Please note that this document is subject to change and may be changed by SAP at any time without notice. POWER5. and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business. xApp. OS/2. System p. Parallel Sysplex. WebSphere. Program Neighborhood. Microsoft. AIX. This limitation shall not apply in cases of intent or gross negligence. Outlook. UNIX. Acrobat. mySAP. SAP Skills 2007 Conference / F4 / 68 . and Motif are registered trademarks of the Open Group. JavaScript is a registered trademark of Sun Microsystems. SAP shall have no liability for damages of any kind including without limitation direct. SAP does not warrant the accuracy or completeness of the information. product strategy. VideoFrame. Excel. iSeries. System z. OSF/1. MaxDB is a trademark of MySQL AB. R/3. AFP. No part of this document may be reproduced. Adobe. Windows.Copyright 2007 SAP AG. The information contained herein may be changed without prior notice. special. Data contained in this document serves informational purposes only. Inc. xSeries. fitness for a particular purpose. OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. indirect. or transmitted in any form or for any purpose without the express prior written permission of SAP AG.