TACRM5 Chapter 1 Introduction (omitted) Chapter 2 Overview (and TACRM1 review)

Four key roles in CRM lifecycle: Prospecting Acquiring Servicing Retaining Channels of customer interaction Face-to-face Contact center Internet: B2B or B2C Sales Area Combo of Sales Org., Dist, Channel, and Division All docs allocated to a sales area Business processes controlled via rules applied to sales area Used for pricing and evaluation Mobile sales may use attributes in addition to sales area to represent sales force structure Mobile Sales Landscape Overview Mobile users work offline using laptops Communication Station provides dial-up link to CRM server CRM Server heart of the mobile system Middleware (resides on CRM server) Distributes data to mobile users Consolidates offline data (Consolidated db) Provides adapters to other systems (e.g. R/3, BW, non-SAP) Bi-directional data exchange between mobile client and CRM server of master and transactional data. CRM Mobile gets customizing data through the Consolidated db from the CRM server, not from R/3 Pre-configured Industry Templates Core/Standard Consumer Packaged Goods Pharmaceuticals Mobile Application Studio used to further customize templates User Interface Navigation Bar main control for navigation, indicates what Tile Set (view) is currently displayed Tile Set Area section of screen for display of Tile Set Tile Set one to six sub-screens of info Hyperlinks may be embedded in tiles Menu & Tool Bars standard SAP navigation / actions Group Hierarchies Built using special type of relationships BP and contact person can be part of different hierarchies Displayed via tree function Maintained on CRM server and display only on mobile client Group hierarchy info also used for search and pricing Products and Services Every material assigned to exactly one Division Products & services can be related to other products/services Typical relationships: Competes with Spare part of Substitute for Service for Some relationships are type dependent, e.g. cant define spare part for competitors product Multiple units of measure Installed Base Management graphical representation of product installations to use as a reference in service processing Set Finished Flag (once flag set, order can no longer be changed on mobile client) Connect to CRM server Order is uploaded to CRM server Order passed to ERP (R/3) system for fulfillment Status changes passed back to Mobile client

Chapter 5 Field Service Scenario

Overview of Functions Order management Absences & Attendances (integrates w/ CATS [crossapplication time sheets] and payroll in R/3) Interexchange resource planning Assignments Progress snapshot overview of project status Products & services Attachments Service confirmation report time spent and material used Printed service receipts Business partners Installed base integration graphic of all products at site Contact persons Activities & calendar Tasks Mobile sales functions may also be implemented Daily Activities Calendar core component of daily service activities Mobile sales and mobile service use same calendar Absences & attendances special service calendar feature Exchanged w/ Workforce Mgt on CRM server Absences reported when not avail to work Attendances = willingness for overtime Assignments special service calendar feature Employee may accept or reject assignments Status uploaded to CRM server Resource Planning Tool (RPT) Used to plan, staff and dispatch service assignments RPT resides on CRM server Bi-directional data exchange between RPT and mobile client Service employee can accept or reject assignments via status Service Process CRM Server Creation of service request Planning (RPT) Release (to mobile) Mobile Service Data download Execution Confirmation Technical completion Data upload CRM Server Billing (note: billing from CRM, not R/3) Settlement Closing Progress Snapshot Displays execution hierarchy when service involves multiple steps and/or technicians or other partners Displays status of all assignments Displays confirmations of all materials or services Technical Backreporting Details of service reported after process completed Can be used for quality assurance purposes Allows update of info on original notification

Chapter 4 Field Sales Scenario

Overview of Functions Business Partners & Contacts Activities and Calendar appointments and tasks Products & Services master data My Infocenter info subscribed to Campaigns initiate, track and carry out Orders create in mobile and upload to CRM server IPC pricing and product configuration Reporting & Analysis SAP BW and Crystal reports Mobile Calendar Used in both Mobile Sales and Service Various views and listing functions Interface to Outlook and Lotus Notes Note: SAP claims bi-directional interface to Outlook or Notes but instructor indicates is one-way (CRM Outlook). There is synchronization for activities but not contacts. Activities Two types Appointments Tasks Both can be business or private Appointments require a start time and date, Tasks do not Sales Cycle and Opportunities Opportunity = possibility for a business transaction Sales cycle begins w/ recognizing an opportunity Opportunity management is the process of editing opportunities Opportunity management forms the framework for sales projects Use Opportunity management if: Large number of sales employees Large order values Long sales cycles Opportunity mgt process ends with an order or cancellation from customer Bi-directional exchange mobile to online (no attachments) Customizing done online and downloaded to mobile Business Partner Marketing Profiles Defined in CRM server Replaces classification of BPs and contacts Maintenance of marketing profiles possible in mobile sales Campaigns Group of actions focused on a sales or marketing goal Have a timeframe Bi-directional data exchange online / mobile Campaigns Target lists Related products (note: no product catalog) Allocations Attachments Only campaigns with released status are downloaded to mobile All campaigns created in mobile are uploaded Allocation: Assigning quantities to a combination of business partners and products. Can be planned online or in mobile. Campaign Generation Process Create Campaign Create Target List Define Mass Generation Rules Direct mailings Opportunities Activities Generate mailings/opportunities/activities Track campaign Sales Configuration Engine (SCE) Based on variant configuration Knowledge Base whole set of configuration rules Can start configuration from document header or line item (typically at item level) Sales Pricing Engine (SPE) Same pricing rules as CRM online Pricing rules set in Online and downloaded to Mobile Item level pricing Manual input of pricing data allowed Header pricing display only, no changes at header Sales Document Status Info, Doc Flow etc Status info downloaded from CRM server and cannot be changed in mobile Document flow downloaded Schedule line info downloaded from CRM server ATP Check Must be connected to run ATP, CRM server actually does check

Chapter 3 Mobile Master Data

Organizational Data Organizational data required by nearly all business components Initial download from CRM server to mobile client and then delta downloads Cannot maintain sales or service org data on mobile client Org data for employee and employee hierarchy also transferred Employees maintained as business partners Employees linked to an organizational unit Mobile Sales client required org attributes: Sales org Dist channel Division Sales office Sales group Responsible sales org (for employees and sales docs) Mobile Service client Service org Responsible service org (for employees and service docs) Service executing org Business Partners Business Partners are all legal entities who are directly involved in a business relationship Data exchanged w/ CRM server Detailed data available on mobile client Contact Persons All people involved in business activities are Contact Persons Contact persons are there own Objects in mobile client Persons in Private Practice dont need primary relationship to business partner CRM Mobile vs. CRM Online: Business Partner (exam) The Same: Central business partner Person can exist w/out organization Flexible relationships between business partners Marketing profile Different: For Mobile, BP can be an organization or person but not a group. For Online, BP can be a group For Mobile, Object drives how BP is used For Online, Role drives how BP used Role concept does not exist in Mobile. Middleware adapter translates role to object connection in mobile. All under the hood, user does not see difference mobile vs. online Note: The difference mobile vs. online stems from fact that mobile based on product purchased by SAP. SAP chose not to (couldnt) change some things. Also Mobile written in VB and middleware translates. Relationship Concept in Mobile Numerous objects (BPs, contacts, docs) can be related to each other Can define relationship categories in customizing Each relationship can have particular attributes and directions Relationships are reversible: if A to B, then B to A Can build relationship hierarchies or networks Can define cardinalities (1 to n) BP may have multiple contacts. A contact may have relationships with multiple BPs. Contacts may have relationships with each other. Networks can be built

Chapter 6 Mobile Shared Components

Inbox Mail and Error messages Reports All users w/ same role (sales rep, technician) receive the same types of reports/workbooks Each user only receives data applicable to them Authorization for which data is determined from replication criteria used by the Middleware CRM reporting comes from BW CRM Business Content is shipped w/ BW and is therefore release dependent (more info cubes in later releases of BW) Reports generated as Excel workbooks Mobile report requests are routed thru CRM server to BW Mobile Client Reporting via Crystal Reports Crystal Reports 8 can be integrated w/ mobile client Reports run directly on mobile client database (i.e. no BW) Reports started directly on mobile client (i.e. no CRM server) Reports may be designed centrally and distributed to mobile Infocenter Used to gather info from numerous sources and replicate it to mobile client Automatically-updating local content repository Examples: Web sites News feeds Legacy systems Databases Infocenter is ready out-of-the-box on mobile client BackWeb Sales Accelerator fully integrated w/ CRM Mobile

BackWeb is a 3rd party product

Chapter 7 Mobile Configuration Components

Note: Very brief chapter Configuration of mobile client done using the Mobile System Maintenance Client

Standard functionality is to run ATP against APO, not R/3 Per instructor: Service Pack 9 or 10 (out in ~3mo?) will allow more ATP checking from R/3 Mobile Sales Sales Order Process Flow Order created on mobile client Run ATP if desired (requires connection to CRM server) Change order if desired

Chapter 8 Mobile Authorization Management Tool

Mobile Authorization Management Can be used w/ any application developed in the Mobile Application Studio (MAS) (i.e. custom code) Role based Role can be assigned to many users Protection of business object data based on: Interaction component (user interface) Business objects Single business object attributes Interaction Component Level Protectable interaction components Application Business Component (e.g. sales order) Tileset Tile Protected hierarchically (e.g. cant access tileset if dont have access to business component) Can control access at Application, Bus. Comp. and Tileset Tile offers finer control of modification, deletion and creation of data Business Object Level By default no business object is protected, must register them in Authorization Management Tool Two approaches to protect business objects Business object class Business object instance Roles, Profiles and Tokens Roles describe particular business task Profile describes how data is accessed Profiles are assigned to Roles Tokens describe how business object data can be accessed Tokens are stored in the Profile Rules maintain the scope of business context Rules allow authorization based on the specific value of a business object Rules are attached to Tokens Section introduction, no content.

Services on the Communication Station SAP DCOM connector / MTS translates DCOM calls from mobile clients into RFC calls COM4ABAP / SAP Gateway used by Admin Console for password encryption SAP OS Collector collects operating sys data Comm Station runs under MS Windows NT or 2000 Note: per instructor there can be lots of problems with MTS / DCOM security settings When installing mobile client must chose to switch replication on or off. If off installation routine provides a pre-filled database for the client (cannot then exchange info w/ middleware broker).

Chapter 11 Administering Sites

Replication Administration Site = local database, not a person Replication and realignment take place for sites via publications and subscriptions Data distribution defined in a replication model Replication model maintained in the Admin Console Replication of data can take place to all sites (mobile clients, but also R/3 or non-SAP systems) Realignment only takes place for Mobile Clients Administration Console Tasks Setting up and maintaining Replication Management of mobile users and their passwords Definition of sites Assignment of employees to sites Definition and administration of organizational structures T-code SMOEAC Employees Employees are created as business partners first, then are available to Admin Console Data is exchanged with a site, not an employee/user Organizational Structures Org structures allow hierarchical subscriptions (e.g. sales mgr gets all data sales reps get) Org structures not integrated into CRM org model Maintained on Admin Console Replication Administration Features Assign additional objects to bulk publications Add (but not remove) criteria fields to existing replication objects Authorization profiles for users

Chapter 9 CRM Middleware for Mobile Chapter 10 Connecting Mobile Clients

CRM Mobile Scenario Components CRM Server SAP Web Application Server (Basis) CRM server applications Middleware broker Database server Communication Station Microsoft Transaction Service (MTS) SAP DCOM Connector Mobile clients CRM mobile applications Transaction layer Connection handler Transfer service Back-end system (e.g. R/3) optional R/3 software Plug-in CRM Middleware Components On CRM Server

Chapter 12 Consolidated Database

Consolidated Database (CDB) Logical database in CRM database Used for data replication and realignment for mobile clients Performance advantages Fast realignment of data Recovery of a mobile client db CDB is not a 1:1 copy of CRM Apps data model R/3 and CDB Tables CDB tables generally have prefix SMO CDB tables that correspond to R/3 tables generally have same table name w/ SMO prefix CDB and R/3 tables are similar CDB tables may less or more fields that R/3, depending on application If help documentation says to check SMOXXXX table, theyre assuming mobile scenario and CDB CRM database tables generally have prefix BUT or CRM Note: R/3 tables KNA1 (cust. mstr general) and KNVK (contact person) are merged into one CDB table, SMOKNA1. If person X contact for two different R/3 customers, then will have two KNVK entries. When download R/3 to CDB, this will result in duplicate SMOKNA1 entries! Must think through this! Table Keys GUIDs (Global Unique Identifiers) serve as keys for all CDB tables GUID generated by algorithm using hardware info, sys time and randomly generated number ==> globally unique GUID technical key and content free Problem: R/3 does not know GUIDs CDB tables can only have one key, GUID

Middleware Broker handles BDoc flow, replication & realignment, communication w/ mobile clients and other apps

Administration Console part of Middleware Broker, handles replication repository and rules for distribution control On Communication Station SAP DCOM Connector converts mobile clients DCOM calls to qRFC calls to Middleware broker On Mobile Client Connection Handler interface for data exchange with CRM server Transaction Layer deals w/ local data access

Client Console admin functions on laptop, e.g. starting connection handler 3 Communication Layers between Middleware Broker and Mobile TCP/IP network connection qRFC/COM+ - enables comm.. between ABAP and Microsoft BDoc messaging layer actual message transfer COM+ Communication Interface COM+ (Component Object Model) open arch for crossplatform development of client/server apps COM+ components written in VB, Java, C++, Cobol etc SAP components written in ABAP DCOM+ (Distributed COM+) enables COM+ components to communicate over network (e.g. mobile to CRM server) MTS (Microsoft Transaction Server) transaction processor, provides better performance Communication Flow MTS makes DCOM call to COM+ object on Comm Station Transfer proxy on Comm Station translates COM+ function calls into qRFC function calls. COM+ and qRFC calls contain BDocs qRFC call passed to Middleware Broker Communication Overview Transaction Layer on mobile client handles access to local db User starts communication process by call ConnTrans program Connection Handler on mobile client establishes connection to server Data is transferred by calling Transfer Proxy on Comm Station SAP DCOM Connector acts as interface between Microsoft and ABAP environments Connection Handler triggers the Transaction Layer to read the inbound queue when new data downloaded

Chapter 13 Replication & Realignment

Mobile Client databases Contain only data the user of that db needs Vary in size Mirror parts of the CDB No two are identical Replication Message (BDoc) forwarding to one or more clients sBDocs used w/ mobile clients Types of Replication Bulk Intelligent Dependent Intelligent-dependent Bulk Replication Simplest replication type No criteria fields Do not cause content-based realignment BDocs are always distributed accordint to their site Ids regardless of their contents or relation to other objects Bulk replication especially suitable for small tables Example bulk-replicated data: customizing, employee data Intelligent Replication More sophisticated than bulk Specific replication rules are necessary Objects distributed depending on their contents and their relation to other replication objects Dependent Replication Only for mobile scenarios Subscribed client receives all BDocs referring to another BDoc received via intelligent replication to the same client (e.g. BOM following material)

Dependent BDoc must contain the types and keys of the BDoc it follows Parent BDoc must be replicated via intelligent replication Intelligent dependent Replication Replication objects are distributed depending on their contents and their dependency on another intelligent replication object The key of the intelligent parent object is assigned to the replication object Example: sales documents follow business partner Publication Grouping BDocs to be distributed Contain: only one intelligent or multiple bulk BDoc types Publications are subscribed to sites Many to many relationship between BDocs and publications Subscriptions Assignment of site Ids to publications Specification of values for the criteria fields Publications & Subscriptions defined in the Admin Console Data Flow: Mobile Client Middleware Broker BDoc message (sBDoc) generated on mobile client and added to outbound queue Dialup connection made to CRM Middleware and BDoc uploaded via ConnTrans program to the inbound queue (for that mobile client on the server) BDoc message is assigned to one or more publications, depending on the type BDoc replicated to the outbound queues (on the server) for the sites that subscribe to the publication(s) the BDoc assigned to Other mobile clients dial in and synchronizeBDoc message is added to their local inbound queues If several sites receive the same data through the same subscription, assign these sites to the subscription at the same time, this allows the data extract to the site queues to be performed only once and improves efficiency Indirect Subscription Assignment Subscriptions of a lower-level site can be made available to another site at a higher hierarchy level BDoc Dependencies Direct Dependencies Dependent replication BDocs follow only one intelligent BDoc (e.g. sales docs follow customer) Intelligent-dependent replication BDocs may follow multiple intelligent BDocs (e.g. activities follow opportunities or customer) Indirect Dependencies (Interlinkages) Flexible scheme to model free dependencies May be cyclic or reflexive May be bi-directional or unidirectional E.g. customers & prospects with contact persons or customers & prospects with opportunities Realignment (exam) Process of redistributing data according to changes Minor realignment triggered by changes in data (e.g. field value change). Applied to single BDoc message. Major realignment triggered by changes to subscriptions (e.g. create new subscription due to change of responsibilities). Not related to a single BDoc. Realignment updates mobile client databases BW Link to CRM Server Linked partly by middleware broker and partly by direct RFC calls and BAPIs Product and Campaign master data are not handled by CRM Middleware The Initial Load to BW does not use the middleware broker Subsequent Delta Loads are performed automatically and do use the middleware broker BW Workbooks for Mobile Clients BW Solution Workbooks (Excel) are used for offline BW reports on Mobile clients Online users (CRM server apps or connected mobile users) can access BW directly Middleware broker manages the requests for workbooks Each workbook may be replicated to several clients Automatic updates to workbooks are delivered on a scheduled basis Workbook contains not only data but also VB code display of data on mobile client Replication maintained in the Admin Console Review Site/Subscription Create site Create employee Assign employee to site Create subscription Assign subscription to site

Chapter 14 Replication Architecture

BDocs Business Documents Data container for processing business objects that logically belong together BDocs used for processing within the CRM system BDocs used for replication to mobile clients Realignment of BDocs used for mobile clients only BDoc type (structure) defined for each business object (e.g. sales order, contact person etc) BDoc instance example of a BDoc containing all field values Only one BDoc instance per business object BDoc message (or just BDoc) contains modified fields May be many BDoc messages per BDoc instance BDoc Types Messaging BDocs (mBDoc) Used for message exchange w/ CRM server apps, R/3 and external systems Only processed on CRM server Synchronization BDocs (sBDoc) Used for communication w/ Mobile Clients

Processed on both Mobile Client and CRM server Stored in CDB Mobile Application BDocs Used by CRM Mobile apps Processed on Mobile Clients only BDoc Structure Header one data segment, the Control segment Contains msg ID, sender ID and info on BDoc instance and type Body Error segment error info Data segment(s) actual table entries First segment (root segment) contains only one key field, all others two keys own and parent segment Each Data Segment contains segment fields (or segment attributes) which are mapped to actual data fields in the physical database tables. BDoc segments are arranged hierarchically to model data dependencies On Mobile Clients, BDocs appear only in the transaction layer BDoc and Replication Object Replication object contains info about how a type of BDoc is replicated and which fields can be used for criteria Every Replication object refers to exactly one BDoc type Not every BDoc type needs a replication object One physical data record belongs to exactly one instance of one BDoc type and therefore to one replication object Replication objects are extensions of the BDoc type One Replication Key in the root segment of each BDoc Replication Methods (exam) Bulk no criteria or dependencies, direct distribution Intelligent according to criteria values Dependent following another object Intelligent Dependent following more than one object Interlinkage distribution according to relationships Look-Up Tables During Realignment, the replication key and the appropriate site ID are written to a look-up table Replication then only has to read this table Look-up table generated when a replication object is created Table is filled by creating subscriptions Basically, the table identifies what info to send which site Data flow between Mobile clients and Middleware Broker is handled by inbound and outbound queues on both sides. Interlinkage Replication BDoc types related via an interlinkage table Interlinkage table belongs to one of BDocs By subscribing to one BDoc the othe BDoc follows automatically Interlinkages are defined in the Admin Console Linked replication objects follow intelligent replication objects in distribution (e.g. opportunities follow customer) Replication and Realignment Replication is initially performed Replication recipient list determined based on site Ids in look-up table BDoc is placed in relevant outbound queues (for transfer to sites) Replication and Realignment Service determines if Realignment is required Relevant BDoc message is copied into a separate realignment queue

Chapter 17 Mobile Application Studio - Intro

Note: MAS used to be called Workbench and Business Application Studio Mobile Application Studio Used to customize Mobile Client application (exam) Designed to be flexible and versatile Customize the following: (exam) User interface Business logic Language Functions Uses an integrated, object-oriented repository Stores metadata Change management support Transport / upgrade support Most development is drag & drop For manual coding (e.g. biz logic) need to know VB Development Landscape MAS client connects to Repository Server May have multiple MAS clients (i.e. multiple developers) Repository Server connects to CRM server via Transport Agent

Chapter 19 Designing Your Screen

Screen elements compose a tile. Example elements: text input; button; image; check box etc. A Tile Set is composed of up to 6 tiles. Tile sets are assigned to Business Components. Business Components are assigned to Applications Tile Design Can drag & drop Can design manually Can use the Tile Wizard Rules for Tile Design No more than 6 tiles per tile set Tiles must always be rectangular Tiles must not overlap Tiles can be maximized and restored, but no minimized Tile Set Design Can drag & drop Can design manually Can use the Tile Set Wizard Screen Design Steps Determine what you want the system to display and select the appropriate business objects Determine how you want the tiles to look and select the appropriate tile types Combine the tiles into a tile set Set the data links Can use relationships from bus. obj model Can use direct link to db

Chapter 18 MAS Overview

Mobile Application Studio (MAS) Set of tools used for development/customizing CRM Mobile Applications Application-specific upgrade data is sent from MAS to CRM Middleware during replication Upgrade data is then distributed from middleware to mobile clients Mobile Application Repository (MAR) Used by developers working w/ MAS Enhancements to mobile clients stored on repository server Enhancements are periodically transferred to middleware via transport agent Runs on NT 4.0 or Windows 2000 w/ SQL Server 7.0 For small project w/ one developer, MAR can reside on same laptop as MAS (i.e. no MAR server is needed) *** Note: this approach is not recommended or supported by SAP, and will work only if one developer If more than one developer, need a repository server. Repository server provide reports of conflicting changes Mobile clients use an application database for storing business data. Each user has there own local copy. MS SQL Server is used. MAS can be used to build both smart and thin clients. Smart Clients All processing is done on the front-end device All layers User Interface, Business objects, BDoc layer, and application db reside on the client Workgroup Smart Client Mobile clients do not have application db All users access a Workgroup Server db instead Laptops require less hard drive and memory Only works for office-based personnel Thin Client (* future release*) Only user interface processing on front end Communicate w/ web server via http protocol Thin client is browser-based allowing apps to run w/ Internet Explorer only Mobile Client System Layers User Interface (UI) layer contains the GUI Business Object layer contains business logic and rules BDoc layer provides client w/ link to application db Object Browser (part of MAS) used to develop UI and Bus. Object layers BDoc Modeler used to develop BDocs layer. As of CRM 3.0, BDoc Modeler integrated into Middleware component of CRM Server User Interface Layer Uses Dynamic HTML (DHTML) ActiveX Data binding mapping of UI elements to db fields Benefits: uses internet technology, easy customizing, standard for MS Windows platforms (98, NT, 2000) Business Object Layer Can design properties, operations, relationships, and business rules. COM/DCOM interface (component object model/ distributed component object model) Visual Basic for Applications (VBA) used for bus. logic Business objects represent logical or physical entities (e.g. bus. partners, sales oppt., sales activity etc) Business objects are linked to UI elements BDoc Layer Responsible for low-level manipulation of physical data in the application database Encapsulates SQL Messaging system between client and CRM server Object Browser Used to design: Business objects Business queries used for search engines Combo engines used for list choices Business rules (e.g. A must precede B) BDoc Modeler Used to design BDocs an atomic entity (e.g. one sales doc) Segments logical groups of data in a BDoc Segment fields equate to table columns Definition of how physical tables and columns map to segments and segment fields is in the MAR Data Binding (at a high level) A screen element on the UI (tile / tile set) is linked to a business object property/attribute which corresponds to a segment field in a BDoc segment. This segment field links to a db table field in the application database. Database Modeling is done on the CRM Server as part of CRM Middleware development.

Chapter 20 Application Business Logic

BDoc Container for messages between mobile and CRM server An interface to the consolidated database Contains all data pertaining to an object (e.g. sales doc) Contains data from more than one table Segment = data of one table Every business object is related to a segment in a BDoc type Business Object Represents a real-world entity (e.g. customer) Has properties which define its state (e.g. first name) Has behavior (business logic) which is exhibited via its methods (e.g. CalculateCustomerAgeInDays) Has relationships to other BOs Properties characterize a BO (e.g. country) Methods are operations that can be performed on a BO Events occur when you create, change, or delete a BO An event handler is a method that is executed on a specific predefined event (e.g. when BO is saved) Business Object Relationships (exam) An Activity can be related to: One business partner Multiple contact persons At least on employee/sales rep must be responsible for an activity Many other objects can be linked to an Activity Attachments, opportunities, sales docs Business Query Properties Characterize object found by query Are not stored in the database Business Collection Container for BOs of same type Can only contain BOs of one type Generated at runtime, not developed Combo Engines Provide input help for value selection Restrict value of a BO Examples: radio buttons, check boxes, built-in filters (e.g. country-state-city) in selection lists Business Rules Implement constraints on a business objects state Insure that a condition is true Prevent deletion of a BO Versioning (high-level, review detail docs for specifics) Name Space: Custom objects must start w/ Y or Z Versioning allows for multiple versions of an object Versioning enables change tracking Repository baseline is a line through the version lists of all MAR objects. When an object is closed (released) the baseline is updated Baseline: Snapshot of MAR available to all developers Only one version per object Only closed objects Change list lists versions of different objects that have been changed for a development task Transport Management Required services for transport MAR - CRM server R/3 Transport Order Service Transport Agent Suggest both services installed on the MAR machine

Chapter 15 Monitoring
Message Tracking in Mobile Scenario CRM Server Inbound & Outbound queues (SMQ2, SMQ1) Replication Queue monitoring (SMOHQUEUE) Communication Station Communication Monitor Mobile Client Qmonitor Inbound & Outbound Queues All calls and data transports take place asynchronously via buffers (queues) Queues insure that if individual components can not be accessed, no info is lost and no delayed in overall schedule Outbound queue = SMQ1; Inbound queue = SMQ2 Five Replication & Realignment Queues AC_Extract extract jobs triggered by Admin Console ExtractBlk bulk-replicated BDocs Extract for replication & realignment Realignment for replication & realignment Subcheck for replication & realignment Replication & Realignment queues may be stopped and started manually Monitor R&R Queues = SMOHQUEUE Communication Station Monitor the data exchange between middleware broker and mobile clients Can monitor data exchange of individual sessions, i.e. between a site and CRM Server Can monitor statistics of data exchange for each site Can get info on Comm Station operating system Mobile Client Queues on the client are db tables in the local db BDoc messages are stored in the client queue Inbound & outbound queues can be viewed w/ Qmonitor Qmonitor called via Client Console Mobile Client Message Recovery status of BDocs sent from CRM server to mobile client and allows reprocessing Section introduction no content

Chapter 16 Mobile Application Studio (MAS)