AC 10.0 Customizing Workflows for Access Management Customer Solution Adoption June 2011 ae A)ey Purpose of this document This document allows implementation consultants and administrators to setup the required functionality for enabling the workflow engine in AC 10.0. You will learn the main components of the new workflow engine and how to customize them, also how to create agents and initiators using Function Modules and BRFplus.Disclaimer This presentation outlines our general product direction and should not be relied on in making a purchase decision. This presentation is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to develop or release any functionality mentioned in this presentation. This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non- infringement. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent.Agenda Workflows in Access Control Streamlined User Access Management in SAP BusinessObjects Access Control 10.0 Configuring MSMP Workflows Extending Workflows Using Function Modules Extending Workflows Using BRFplus Wrap-UpWorkflows in Access ControlStructure of a Workflow Access Control’s Compliant User Provisioning Functionality Standard Path ===> 9 Detour Path “alStreamlined User Access Management in SAP BusinessObjects Access Control 10.0New Feature Highlights Streamlined User Access Management Le ee 3 Sauk ee Rom gee 2c) ~ Unifies all Access Control capabilities on a standardized ABAP platform, offering enterprise supportabilty, granular security, transport, and archiving, Harmonizes Access Control with Risk Management & Process Control offers shared processes, data, and user interface across the GRC suite. Standardizes on improved workflow that ‘supports flexible, multi-tiered routing and ‘approval matrices. Dynamic user request forms based on user or system selected Provides a standardized role compliance tramework, centralized across organizations, systems, and applications, Translates roles into terms business users can understand Centralizes frefighting and administration across all systems. New workflow provides an auditable process for tracking log report approval Improves compliant provisioning for customers already using IdM. Allows for initiation of risk analysis and remediation from IdM or enables use of IdM to provision compliant requests, Lowers TOO by eliminating redundancy in administration, configuration, setup, and end-user training ‘An enterprise GRC platform approach allows you to have complete management of all risks and controls from a single environment. Tailoring of routing requirements for simple to highly complex organizations. New request forms improve user adoption and usabilty. ‘Sireamiines management of echnical roles and eases identification and selection of appropriate roles for users, positions, and jobs. Reduces the etfort requited to grant and provision emergency access to multiple systems. Provides a structured, documented process around emergency Provides flexibility to ensure an enterprise ‘wide, compliant provisioning process.Streamlined User Access Management SAP BusinessObjects Access Control 10.0 Business workflow technology and supports more flexible and tailored = Standardized on SAP Business Business workflow reduces ‘Workflow technology manual tasks and streamlines access request and approver views decoss request processing simplifying the provisioning process. ®= Access requests enhancements: = New customizable access | everage existing resources for feauesl oor workflow administration and m New template-based access sects ee configuration. a |= New position-based role i Senet = Faster and easier for users to = = Seem = New end-user display of request the roles they need —— = profile, access assignments, and request history ® Utilize existing HR structure for automated and compliant position-based role assignment Enhanced search for roles, groups, and system based on authorization 1 Improved securty and richer = New customizable approver request context Tae Sera New multiple rule set support = Enhanced periodic reviews for user access and access risksWorkflow Key Terms in SAP BusinessObjects AC 10.0 Mapping Previous Workflow Terms to the New Workflow Functionality SAP SAP BusinessObjects | BusinessObjects One process ID can have AC5.X AC 10.0 multiple request types Access Request: Create Request, Change Request, ete. Function Approval: Update Function. Delete Function, etc. One initiator rule is able to trigger multiple paths based on the rule result value = =» =» »> =» iConfiguring MSMP WorkflowsPrerequisites The following configuration should have been completed as part of the initial post- installation steps: = GRC_MSMP_CONFIGURATION BC Set has been enabled + Perform Automatic Workflow Customizing + Perform Tasks Specific Customizing * Activate Event Linkage * Define number ranges for Access Requests * Connectors assigned to the PROV integration scenarioRoles and Users Please create users and roles as required. You need at least the admin for configuration, an approver and a standard business user for request creation. For workflow maintenance: + SAP_GRAC_MSMP_WF_ADMIN_ALL Administrator role for MSMP workflows + SAP_GRAC_MSMP_WF_CONFIG_ALL Configuration role for MSMP workflows For workflow management: + SAP_GRAC_ACCESS_APPROVER Approver for Access Request and User Access Review + SAP_GRAC_CONTROL_APPROVER Approver for Control Maintenance and Assignments requests + SAP_GRAC_SUPER_USER_MGMT_OWNER Approver for Firefighter Log + SAP_GRAC_FUNCTION_APPROVER Approver for Function Maintenance + SAP_GRAC_RISK_OWNER Approver for Risk Maintenance and SoD Risk Review + SAP_GRAC_ROLE_MGMT_ROLE_OWNER Approver for Role MaintenanceConfiguration Parameters The configuration parameters are set in IMG under Governance, Risk and Compliance > Access Control > Maintain Configuration Settings. Make sure they reflect your needs. Change View "AC Configuration settings": Overview ‘AC Configuration settings Pam Group Param iD i072 2032 200 > 2035 2038 201 REQUEST Descrpton Enabler analyst on form submission Meigaton of crical ek requred before approving the request ‘Alow Al Roles for Anprover Aoprover Role Restricton Attrbute ‘Alow Al Roles for Requestor Requestor Role Restcton Attbute ‘low Role Coreents Role Comments Mandatory Debby expred roles for exstng roles ‘Auto Approve Roles without Approvers ‘Consder Defaut Roles Defaut Role Level Enable Role Mapping ‘Applicable to Role RemovalsProvisioning Settings The provisioning settings are configured in IMG under Governance Risk and Compliance > Access Control > User Provisioning > Maintain Provisioning Settings. Maintain at least the Global Provisioning settings Change View "Maintain Global Provisioning Configuration”: Detalls From OS OT BEa Maintain MSMP Workflow Overview The configuration tool can be launched in IMG under Governance, Risk and Compliance > Access Control > Workflow for Access Control > Maintain MSMP Workflows These activities allow you to customize and maintain the Multi-Stage Multi-Path (MSMP) process workflows for Access Control 10.0 » om 2 3 ‘ 5 . m4 Process Global Stings arian Aes aan Agents Vara 8 TenpiessttanPate Mart Routeappng_GeverlaVersons Ready to use components are delivered by SAP under BC Set GRC_MSMP_CONFIGURATIONMaintain MSMP Workflow 1. Process Global Settings 2 a 4 5 6 1 Process Global Settings arian ules antan Agents Varables ATersixes Manian Pats Mant Rowe Wapping Gereate Versions In this step settings that apply to all process IDs are configured, such as escape conditions and notifications settings Se Predelivered Process IDs: —— * Access Request Approval Workflow + Access Request Approval Workflow for HR OM Objects Control Assignment Approval Workflow Mitigation Control Maintenance Workflow Fire Fighter Log Report Review Workflow Function Approval Workflow Risk Approval Workflow Role Approval Workflow SOD Risk Review Workflow User Access Review Workflow i |Maintain MSMP Workflow 1. Process Global Settings Process Global Settings Enable Escalation: —_[ Escalation Date: * EOR Template D: a EOR Recipient 1: Submission Temp. 1: ‘Submission Recpt. D: Escape Conditions Escape Condition Set Escape Routing | Escape Path | Escape Stage Approver Not Found 000 Auto Provisioning Failure 000Maintain MSMP Workflow 1. Process Global Settings Process Global Settings Enable Escalation’ Escalation Date: * EOR Template D: a EOR Recipient 1: Submission Temp. 1: ‘Submission Recpt. D: Escape Conditions Escape Condition Set Escape Routing | Escape Path | Escape Stage Approver Not Found 000 Auto Provisioning Failure 000Maintain MSMP Workflow 1. Process Global Settings Process Global Settings Enable Escalation: —_[ Escalation Date: * EOR Template D: EOR Recipient 1: Submission Temp. 1: ‘Submission Recpt. D: Escape Conditions Escape Condition Set Escape Routing | Escape Path | Escape Stage Approver Not Found 000 Auto Provisioning Failure 000Maintain MSMP Workflow 1. Process Global Settings Process Global Settings Enable Escalation: —_[ Escalation Date: * EOR Template D: a EOR Recipient 1: Submission Temp. 1: ‘Submission Recpt. D: Escape Conditions Escape Condition Set Escape Routing | Escape Path Approver Not Found Auto Provisioning Failurea Maintain MSMP Workflow 2. Maintain Rules 4 {2} 3 ‘ 5 . 7 Process GotalSetngs Maintain Rules Maan Agents Varables A Temples, arian Paths Mant Route Wapping Generate Versions Maintain Rules includes a list of all available rules to be used when configuring a workflow. If a new rule is created it must be added to this list. This is also where the default initiator is configured. There are different Rule Kinds according to the rule’s objective: testi * Initiator Rule * Agents Rule = Routing Rule * Notification Variables Rule Rules can be coded in different leba Rae ways, these are the different Rule 3 ee Types: + Function Module Based Rule + ABAP Class Based Rule + BRFplus RuleMaintain MSMP Workflow 2. Maintain Rules: Rule Kinds Rule Kinds: + Initiator Rule - determines the path upon submission of the request + Agents Rule — determines the recipients of a stage + Routing Rule — determines a detour routing based upon an attribute of the request (for example, SoD Violations Exist, Training Verification, No Role Owner) + Notification Variables Rule — determines the variable values at runtime used in the notification e-mails.Maintain MSMP Workflow 2. Maintain Rules: Rule Types Rule Types: + BRFplus Rule: is a rule defined in the BRFplus application to fetch rule results, depending on conditions inside the rule + Function Module Based Rule: Function module is coded to output rule results. + ABAP Class Based Rule: ABAP Class is coded to output rule results + BRFplus Flat Rule (Line-item by Line-item): BRFplus rule which is defined for only one line item (rule will be called once for each line-item in the request). Also referred to as BRF+ Easy.Maintain MSMP Workflow 2. Maintain Rules: Results for Initiator and Routing Rules It is required to maintain a list of all possible results returned by an initiator/routing rule by using the Results button. These values will be mapped to a path on step 6.Maintain MSMP Workflow 3. Maintain Agents Process GoblSeings lsrian Rules Maintain Agents Varables 4 Terpises st Paths ait Rost lapping Ganerte Versions A list of all available agents for a workflow is maintained in step 3. Agents have a type and a purpose assigned. Agent Purpose + Notification: Recipients for email + Approval: Recipients to process request Agent Types » API Rules, coded as per rule’s type * Directly Mapped Users + PFCG Roles, and * User GroupsMaintain MSMP Workflow 3. Maintain Agents: Agent Types AgentType:* [Brecy nope Users [> Asprover Goup * a Directly Mapped Users Agent: * Agent Agena: * Agectnae: = AgertPupose* ¥ Agent upon“ x gertTyne: * (FFCO ROK > AgestType "(FEB UserGrows_—_v fe. 4 vaer ou. = 2 PFCG Roles PFCG User Groups Agent = Agente: = get Prose” = Aaeettyoe ~ (GRCAR Res = setae: * a GRC API RulesMaintain MSMP Workflow 3. Maintain Agents: Directly Mapped Users Directly Mapped Users allows you to define static user groups Agent: = Agent ane: =| Agent Purpose: ~ = AseetType:* —— [Dresy upped Users —~1 ‘Approver Group D:* o<—Maintain MSMP Workflow 3. Maintain Agents: PFCG Roles and User Groups These two agent types will determine the recipients of a workflow based on a role or a user group assignment Agent: = Asestname = Ageot Purpose: * = AsestType ® [PFC Roles =] ot: * al Agen 0: * Agen'Type:* [PFCGUse- Groups = User Grou * aMaintain MSMP Workflow 3. Maintain Agents: GRC API Rules This agent type will determine the recipients based on a rule maintained in step 2. Agents (as [Meaty | Dette ] ‘Apert ‘Agent ime ‘Agent Type ‘GRAC_PONT_CONTACT PONT_CONTACT GRC APA Rules (ORAC_REQUESTER REQUESTER (ORC APRs | ‘orAC_seCURTY secunry CRC APA Ruin | ‘GRAC_SPU_OWNER sPu_OwnER ‘ORC APA Rus (GRAC_USER USER (ORC APRs | Agen'Type * — (GREAPRues | Agent Rue B:* (Seve) tance] ‘Agent Purpose Nestemtan Asoroual Arava! Neteatan re et Pe POC pm SAP GAA)Maintain MSMP Workflow 4. Variables and Templates Process GioblSefings arian Res Maina Agents. Variables A Templates Mais Potts abt Rate ageing Generate Versions In this step all templates for email notifications are maintained. The templates are created using transaction SE61 econ Topas Not lions can be sent on fears) different events, such as: cata 2 » New Work Item — * Approval * Rejection » Escalation nd » Request submission a * Request closure pera) * Reminder ae SS This topic is covered in a separate guide in ieee detail, please check the references at the end of the presentationMaintain MSMP Workflow 5. Maintain Paths Process GoblSeings seta Res aiah Agents Varies TerpltesMainfnin Pathe ‘lant Rou lapping Generate Verne Here the actual workflows are configured. Multiple paths relevant to a specific Process issue ID are configured by smn assigning a sequence of stages. Each stage is configured in this screen as well as notifications settings specific ot amg magmas emegeanee to stageMaintain MSMP Workflow 5. Maintain Paths: Stage Details Stage details can be configured globally for the specific process ID and can be overwritten at a specific path/stage sequence.ee Maintain MSMP Workflow 5. Maintain Paths: Modify Task Settings When adding a stage to a path it is possible to configure all stage settings by clicking on Modify Task Settings. These settings will apply to the stage anytime this is used in a particular path. we naceMaintain MSMP Workflow 6. Maintain Route Mapping Process GoblSeings lsrian Rules nian Azets Varies ATerplates shia Patts— ‘Maint Route Mapping Generate Versons In this step you define the mapping between rule results and paths to route the requests Always the Global Initiator must be used, if multiple paths are required the Global Initiator must return different result values Routing rules for detours can be added here as well Hartan Route aang (asa) [=]Maintain MSMP Workflow 7. Generate Versions ‘ 2 a 4 . . = Manton Ages Veraies ATenpes UsbisPabe st Rote Mapping Generate Versions In the last step all changes will be saved and activated. If necessary, a transport request can be configured. Save & Activate Cee ee Bang Taner Requsiast crete New Transport ResinsExtending Workflows Using Function ModulesCreating a Function Module Rule Overview Function Module rules allow developers - ‘Access Control to create complex rules by using ABAP * By @ Hintan Configuration Settings * BB @ kantan Mapping for Actions and Connector Groups Code. These are the activities needed + By © maintain connector Settings for creating a FM rule: 1B © antah Otes et Smee cer + By © Destrbute Jobs for Paralel Processing * Create Function Group in SE37: a ear ce ka + By & maintain ac Applications and BRFplus Functon Mapping Function Modules will be added to ‘26 aaa ts coucar oakasicd 2 the group + By mantan custom user Group + BB © mata Master User Mapong + B® tantan Excide Objects for Batch Rik Anas * Define Workflow Related MSMP z Workfiow for Access Contol * BB & crate Event Untage for AC Workows Rules: For generating the FM rule + By ® Actnate msiap Content for AC content from a template before : a . maintaining it TTBS pete ausness Rue Fomewore + B® wanton notation Messages * Maintain Function Module in E37: For maintaining the FM rule contents.Create Function Group in SE37 Preparing for creating a Function Module Go to SE37 and create a Function Group as shown below. & Eincton Vode E6t [Got] UeiestD) Enitonmant Sistem i © ebioe shore hy 8 Main Progam —ctisshfeara | Function Builders. spcanvas +) umn a Be TE MIC Orector Entry Change Group Documentation >| Dapiay Group Taansation Delete Group nine Manual care End Group Function Module Teck ADefine Workflow Related MSMP Rules Generating a Function Module Generate each Rule ID (FM) to the Function Group created in the previous step. Testing of the rule is optional and will be done when the rule is generated. After generation the FM will be ready to be maintained Generate HSHP Rule for Process ° =n a corm feo he ‘Gneaton of pte Zen Rent Woscwea (0+) vere BF Aktion Tox Das as 22 Funcion module Function group Aas al net Une RasMaintain Function Module in SE37 Customizing the ABAP code Now you can maintain the FM content in SE37. A default template is created on generation. ‘Function Builders Change ZTEST_INITFH oo PRER Bray Ci ee)Extending Workflows BRFplusBusiness Rule Framework Overview BRF plus Workbench + The BRFplus Workbench is a User Interface (Ul) that enables users to define, test and maintain rules for various business scenarios without the need of ABAP cade. Rules can be created for initiators, agents, and also for routing workflows on specific conditions. Kae) (aoa) onealCreating a BRFplus Rule Overview There are two main activities that are relevant to maintaining BRFplus rules, they are located in IMG under Governance, Risk and Compliance > Access Control > Workflow for Access Control * Define Workflow Related MSMP Rules: For generating the rule before maintaining it * Define Business Rule Framework: Launches the UI for maintaining the rule’s conditions using BRFplus B ‘B “B B B B Access Conte + B @ mantan Configuration settings BB & mantan mapping for Actors and Connector Groups B ® mantan connector Settings By © iantan Pus-n Settings + B @ mannan crcaity Levels for Superuser Management: + By detrbute Jobs for Paral Processing + BB mannan Access ek Levels © mantan Business Processes and Subprocesses © Mantan AC Appications and BRFplus Function Mapping @ mantan Data Sources Configuration ® mantan custom User Group ® Mantan Master User 1D Mapping © mantan Excude Objects for Batch Reke Anais ‘Workflow for Access Control BB © Actvate Event Linkage for AC WorkFows BB & Acevate MSMP Content for AC + BO Maintain MSUP Worktlowsee... Define Workflow Related MSMP Rules Overview Using this activity you can create rules for initiators, agents, and for routing. This will only create an empty rule that will be maintained later Generate MSMP Rule for Process & SW Broce D ‘le Tne a ule kd neste le 3] opistnfFne. Grou me “Generation of optons 2 Ger Read Workare (6) Over Bf epeaton Tex vate ue Exeaton aki w. tara Suet cat Ride wth Eno notDefine Workflow Related MSMP Rules Rule Info Generate each Rule ID (Function) to its own unique application/Funct. Group when using BRF rules. Generate MSMP Rule for Process Woven (RF) vende S8F+ Appleton TexDefine Workflow Related MSMP Rules Generation of Options Select both Generate Rule and Generate Result Work-Area vende S8F+ Appleton TexDefine Workflow Related MSMP Rules Test Rule FM Rules can be tested on generation. Testing for BRF Rules can be executed once the rule has been activated Generate MSMP Rule for Process & SW Broce D ‘le Tne ule kd neste le opistnfFne. Grou me “Generation of optons 7 Gen. Ret Wore (RFs) vende S8F+ Appleton Tex vate ue Exeaton aki w. tara Suet cat Ride wth Eno notDefine Business Rule Framework Maintaining Conditions Using this activity you maintain the request fields that will be checked in a decision table The decision table is empty by default and is located under Expression > Decision Table where the necessary request fields can be added by inserting columns ines) (Geom) Boea|(ELie) iacemse os) (Seman omame (Roatc] (eat ou) - (Bose monn e) wear nue [tec se eto tsSetting up an Initiator/Agent Rule Table Settings By using the Table Settings button the condition columns can be maintainedSetting up an Initiator/Agent Rule Condition Columns In the Conditions Columns, click Insert Column, then select Context Data Objects in order to add items that will be used as the Condition Factors in the Decision Table: Moncatry pt Coture eccesstySetting up an Initiator/Agent Rule Condition Columns Navigate to the structure that contains the Condition Items: GRAC_S_REQUEST_RULE_HEADER, Notice that custom fields will only be available to rules created AFTER the creation of the custom field. TEST Aco a (casa cw)Setting up an Initiator/Agent Rule Condition Columns Items can be selected from multiple structures, role line items are located in structure GRAC_S_REQUEST_RULE_LINE.Setting up an Initiator/Agent Rule Table Settings The Condition columns are now selected into the Decision Table settings. * Click OK, an the bottom of the screen, to complete Table Settings:Setting up an Initiator/Agent Rule Decision Table Values Click on Inserf New Row to configure new conditions statements and results: Je DECISION IMITIATORS | chenge tose | > active [Gcdeper] [gbcheck [EM Seve] [Acie hottest: [DEDSON_ATIATORS Detail, ([Exsert Te Excet|Lmeor From Exes!) [Table Setings | Beare OLE NAME PRR enervre een xey ULE RESULT [Tobie contans no rows. Use her Row" fo add codonsSetting up an Initiator/Agent Rule Decision Table Values Now the Condition Statement can be configured © Click the icon in each field. Select Direct Value Input to enter value(s) for the Condition: Show More a Detail Insert New Row || Edit Roy Table Contents }° BH REQTYPE Default Objects » Direct Value Input Select Context Parameter Select Expression. Create Expression.Setting up an Initiator/Agent Rule Decision Table Values Input each Condition Statement: * Choose the Expression Type (is equal to, is not equal to) from the dropdown list. * Enter the value that the Condition should match. User the icon to continue to enter, OR, more Condition Values, if needed, to complete the Condition Statement. + Repeat, as needed, for other Condition fields: Detail (eeernees foe [es fom [inemere fon) [sepzfen] ied Tobie Contents =0 DE | Cane Senate: wa WREGIVEEG] (Type) wa Dake Account os Lock Account Of eausito | Gee [00H] 5) cnange, os undo ser and uniess 3 a fol Rest then fun Vou is true otherwise its fle, 0 rete Lock User [orc] [ence]Setting up an Initiator/Agent Rule Condition Statements Table Contents | REQTYPE ROLE_NAME PRIORITY EMPTYPE L The condition statement above means: » Request Type is equal to 001 and Priority is NOT equal to 001, and Employee Type is between 000 and 999 © Ifall of the conditions are true, then the statement is true and will return the result value(s) Note: + All condition statements can be easily imported and exported to Microsoft ExcelSetting up an Initiator/Agent Rule Result Columns Finally, set the results column values. The result objects are highlighted in green, + Initiator/Routing Rules: the result column is RULE_RESULT which will be used for mapping the path in the MSMP Workflow Configuration + Agent Rules: the result column is USER_ID, which will return an agent (notification or approval). etait Table Contes Rearvee or -a OLE WA roa ‘220163 Notes: + Always configure LINE_ITEM_KEY with Context Parameter ITENNUM. » Remember to add a “catch-all” entry with no values if neededSetting up an Initiator/Agent Rule Save Changes You need to make sure there is a green light next to the decision table and function names. You need to click on Save and then Activate to achieve this. Now you are ready to use your BRFplus rule in MSMP Workflows. Notice that you will use the Function ID instead of the rule name.Wrap-UpResources AC 10.0 How to Customize Notification Templates http:/Awww.sdn. sap. com/irj/bpx/go/portal/prtroot/docs/library/uuid/605077fc-3577- 2e1 a6-a743514d4eb3 SAP Community Network http://www.sdn.sap.com/irj/bpx Go to Key Topics > Access Control SAP Service Marketplace Documentation * https://service.sap.com/instquides SAP Help http://help.sap.com Go to SAP Business User > GRC Solutions SAP BusinessObjects GRC Solutions http:/Awww.sap.com/grc * Requires login credentials to the SAP Service MarketplaceWrap-Up ©Ooooodco SAP's comprehensive approach to GRC leverages the standard SAP Business Workflow technology SAP provides ready to use content for configuring basic workflow scenarios Complex criteria can be coded for routing requests and determining workflow and notification recipients by using ABAP code No ABAP development skills are required for setting up rules using the SAP Business Rule Framework Workflow recipients can be easily determined by using role and user group assignments Email notification can be customized on specific events New request form improves user adoption with a consistent user experience in all GRC componentsThank You! Contact information: Luis Bustamante Customer Solution Adoption (GRC) luis.bustamante@sap.com© 2011 SAP AG. All rights reserved 'No-par of his pubicatin maybe reproduces transmit in any fom oar any purse Yiout ihe mires pemson of SAP AG Thenormton conned nae ny fe {arged winout pr nace eros Windows, Exe, Cock, end PowerPoc ae rageseed ademas of Nose Ip DE2. D2 Ursa Otsbase, Siam Sytem S, Sion, Sytem PE, System Sinem System 210, Systm 20 £902) aren pier wre, zSeros eGower ekat'05, 1803, 80 O80, O80 ASAD 60 Poa! Ener Sore Powers, Por Achvacure POWERG-, POWERS POMERSY, POINERS, POWER, RETAN Dbz connec RAGE Fedvoos. O82 Patt! S)spieu aVSIESA ix Init ine Webspnere Nest Two! ar ntmis we Yada 0” ensired trae of Corgan ‘apsiad darn of Adobe Sysore rcorpsoid fh sd Sine ander other [Nx x10pen, SF, and Mot ae reqs ademas ofthe Open Group HTML 2, XHTML are WC ao aes oF Stn ra of WOR: Wo lease ogre ror of Sun Mossi, es ‘SrsanWion ang ober SAP orocucts and services mentored here as well @s re cone for Business Objects nd ne Bites toga, SsnessOppcs, Cyl Report, cys resins, Web ligence, abs, and ler Busness Obes pros ana sees Frnt ar as Wl ns et esc egos eras or este Pooks ‘lBusness Obert Soars Lia Eeness Obes ean SAP company Syaan ane ape Stove Ann Sais 255, SOL Anat a Sas Fagtard tadanark ot Syeesa, ne Syeassiean SaPcamgany. . Aloo pod and srw names montoned ar adams fh rode spectienons may vary ‘The infomation nts documets poplar SAP. No ert of acumen maybe Witten permissenc@SAPAG “ {iter apeumert wih SAP. Ths documenl nia cy nlended staaes, davelooment, Paral course ofbucness. dul stato. endo eiopmet Plone nts that his orien sb to shange mayb Pnged SAE aay be hs nae respective infomatonas puposes ny Naor warant ie ac uc or coolness oe near, txt. gaghics, ks, Or eter rs ‘Ser eigrese or moled. clang anol fed tote pled wararogs of Frorcharabiy, tess fora parc purse, cen iegomor Sens omar try fn i of So os Tho slay lity fr personal iy an civ prcts snl alot, SAP aso palenals and doesnot endorse your use of rd party Web pages nex provide eran wnetscever ting ere party Wee paps