Cleint Name

Functional Specification

Realization Version 1.0

FS DOC NUMBER TITLE LAST UPDATED DOCUMENT CONTROL

DRF Creation Date Author Complexity Document Status

: CRM_FS_CRM_MKT_E_007_V1.0. : External Event Management : 22-Apr-09

CRM_FS_CRM_MKT_E_007_V1.0.

14-Apr-2009
High Drafted

REVISION HISTORY:
Version # 1.0 Date Modified 3-May-2009 Modified By Consultnat Brief Description of Change Added required information as per technical request

FS Approval
Action Approved Approved Approved Name Signature Date

Cleint Name

Functional Specification

Realization Version 1.0

TABLE OF CONTENTS: INTRODUCTION..............................................................................................................................................3

PURPOSE OF THE DOCUMENT....................................................................................................................................................................3 REQUEST OVERVIEW..............................................................................................................................................................................3

OVERVIEW.......................................................................................................................................................4
BUSINESS DRIVER .................................................................................................................................................................................4 KEY BUSINESS REQUIREMENTS: ................................................................................................................................................................4

DETAILS..........................................................................................................................................................5
SELECTION SCREEN : ............................................................................................................................................................................5 SCREEN LAYOUT / VALIDATIONS FOR EACH SCREEN : .................................................................................................................................5 DETAIL PROCESSING LOGIC:..................................................................................................................................................................12 USER COMMAND :...............................................................................................................................................................................13 REPORT/FORM LAYOUT: ......................................................................................................................................................................13 INTERACTIVE REPORT LEVEL (1.N) :....................................................................................................................................................13 CUSTOMIZING PATH FOR FORMS/SCRIPT AND NAME:..................................................................................................................................13 PAPER REQUIREMENTS:.........................................................................................................................................................................14 PRINT REQUIREMENT:...........................................................................................................................................................................14 PDF OUTPUT REQUIREMENTS:..............................................................................................................................................................14 SPECIAL CHARACTERISTICS:..................................................................................................................................................................14 DATA SAVING CRITERIA.......................................................................................................................................................................14 DATA MAPPING REQUIREMENTS............................................................................................................................................................14 CONVERSION TABLES .........................................................................................................................................................................14 ROUTING TABLE .................................................................................................................................................................................17 TRIGGER EVENT FOR THE WORKFLOW .....................................................................................................................................................17 TERMINATION EVENT FOR THE WORKFLOW...............................................................................................................................................17

OTHER DETAILS............................................................................................................................................17
EXCEPTION HANDLING RULES...............................................................................................................................................................17 SPECIAL REQUIREMENTS.......................................................................................................................................................................17 DEPENDENCIES....................................................................................................................................................................................17 CONSTRAINTS .....................................................................................................................................................................................17 TEST SPECIFICATION.............................................................................................................................................................................18

Functional Test Scenarios.........................................................................................................18 Test Data & Other Needs...........................................................................................................18 Test System & Environment......................................................................................................18
SECURITY/AUTHORIZATION REQUIREMENTS.............................................................................................................................................18

Cleint Name

Functional Specification

Realization Version 1.0

INTRODUCTION
Purpose of the document
The purpose of this document is to document any SAP code modification or additional processing logic requirements to further enhance the standard SAP delivered functionality. This document once approved by the appropriate authorities as mentioned in section Document Control forms the basis of Technical specification and the development work by the Development team.

Request Overview
Type: Module pool program Table ABAP Report Form Other_________________ Tools used SAP Forms Interface Type: Direction: Data latency: ABAP Program Information System Smart form XI Inbound Real-time ALE Outbound Batch Report Writer ALV Sap script Other ________ Others (Specify) Both (Synchronous) On-demand BADI Search Help Query User Exit

Conversion Methodology: Data Volume: Frequency:

LSMW

ABAP Development

Other ____

Annually Daily Other CO SD

Quarterly

Monthly

Weekly

Modules Impacted:

FI HR

MM

PP

PM

BW

IS OIL

Other____________ Medium Low

Complexity

High

Cleint Name

Functional Specification

Realization Version 1.0

OVERVIEW
Business Driver ABC of science and technology is implementing SAP CRM to automate their business process of grants/aid information using Grants Management system, area in CRM. in Grants Mgmt built combination of Grantor Management and Grantee Management. Grantor is implemented in SAP CRM Technology, Grantee process will be mapped in ECC/R/3. Key business requirements: ABC CLIENT can execute various events for internal or external people, when they wanted to communities these events information to external entities SAP CRM has provided a functionality in Marketing areas with the help of Marketing Planning, Campaign Management , Target groups etc., Using these functionalities they will send the communication to Targeted people. Once ABC CLIENT send the information about the Event if they are interested they will register and they will provide additional details as requested by ABC CLIENT like passport information and valid visa information. Once ABC CLIENT received the data from targeted audience then they will do necessary actions like if target audient is out side of the KSA taken care about visa process, once they arrive to KSA accommodation and Transportation all the things will be taken care by various other departments. High level Process overview ABC CLIENT can use this business scenario to cover the complete process for running a Campaigns(Events) starting with market analysis, continuing with execution of the Campaigns, and ending with the closure of the events and analysis of the results. Campaigns serve as operative marketing planning. They describe actions that are carried out, for example, mailing actions, product promotions and telemarketing. Once a campaign has been set up, it can be tracked throughout its duration and the results used in future planning. Criteria such as target groups, products, documents, responsible employees and the budget are defined in the campaign for these activities. The scenario shows the possible steps that are involved in a complex campaign. Here we see, for example, how the different systems interact with the SAP Customer Relationship Management (CRM) System; how you can analyze campaign attributes and carry out the necessary budgeting and performance monitoring in SAP Business Information Warehouse (BI).

Cleint Name

Functional Specification

Realization Version 1.0

DETAILS
Selection Screen :
< Specify the selection screen details here>
Screen Label Referenced Field Range of Value Attributes, Default Values Validations / Checks Comments/ Selection Criteria (select options, parameters, radio buttons, checkboxes)

Screen Layout / Validations for each screen :

<Define the field orientation in the screens> SCREEN NO: Sl NO Field Name Label Reference Input/Output/Ma ndatory/Length/ F4 Help/ Radio Button/Check Box/Push Buttons Description

1. 2. 3. SPECIFIY VALIDATIONS FOR EACH FIELD: When Campaign is executed an Email should triggered to the respect Target group, This link should contains 5 views and each view should be followed by various fields.

Personal Information

Cleint Name

Functional Specification

Realization Version 1.0

Note: All the Personal Information view fields are already available in every BP Role Address Tab.

Contact Information

Cleint Name

Functional Specification

Realization Version 1.0

Note: All the Contact Information view fields are already available for all BP Roles Address Tab. Visa Information

Cleint Name

Functional Specification

Realization Version 1.0

Note: These all the fields are we need to enchance as per the ABC CLIENT Requirement.

Travel Requirments 8

Cleint Name

Functional Specification

Realization Version 1.0

Note: These all the fields are we need to enchance as per the ABC CLIENT Requirement.

Special Instructions

Cleint Name

Functional Specification

Realization Version 1.0

Note: These all the fields are we need to enchance as per the ABC CLIENT Requirement.

SPECIFIY F1 HELP REQUIREMENTS FOR EACH FIELD: SPECIFY VALUE REQUEST FOR REQUIREMENTS FOR EACH FIELD:

10

Cleint Name

Functional Specification

Realization Version 1.0

I will Attend Yes/No (Radio Button)

No, I am not attending Please keep me in the database (DEFAULT Check Box) No, I am not attending Keep me in the data based but I like to send alternate in my place o Would need to input First Name, Last Name, Position, Organization, Phone, Mobile Phone and email. (separate Sub view) No, I am not attending, please unsubscribe me from all ABC CLIENT Communication (this email get flag and not message get sent to them)

The mail BP related Table is BUT000 in this table we will get most of the fields were available,

Personal Information (In this view some of the fields data already available with BP Number, when ELM is executed all these
data uploaded to CRM data available fields should display data, bp should not have change access)

- Title - Job Title - First name - Middle Name - Last Name - Organization - Nationality - Country of the Residence

(BUT000.Title) (BUT000.JobGr) (BUT000.Name_First) (BUT000.Namemiddle) (BUT000.Name_Last) (BUT000.Name_org1) (ADRC.country) ztable

Contact Information ( All these field are available in ADRC table) - Preferred Email Id (ADRC.FLAGCOMM6) - Telephone (ADRC.TEL_NUMBER) - Mobile (SZA11_0100.MOB_NUMBER) - Fax (ADRC.FLAGCOMM3) - Mailing Address (ADRC.ADDRESS_ID) - City (ADRC.CITY1) - Postal Code (ADRC.POST_CODE1) - State/Region (ADRC.REGION) - Name ztable - Telephone ztable - Email ztable Visa Information ( There is standard data structure available VBUT0ID, it should store all these data in this structure) - I require Visa ztable - Passport Number (VBUT0ID.fs0002.idnumber) - Sex (BUT000.XSEXU) - Passport Expiry (VBUT0ID.fs0002.valid_date_to) - Age ztable - Visa pick up country ztable

11

Cleint Name

Functional Specification

Realization Version 1.0

Date of Birth (BUS000FLDS.BIRTHDT) Nearest Saudi Embassy ztable Region ztable Attach copy of the photo ztable Travel Requirement - Departure Date ztable - Departure City ztable - Returning date ztable - Notes ztable Special Instruction -Is there anything else you think we should know? Ztable

SPECIFY APPLICATION TOOL BAR BUTTONS / LOGIC: SPECIFY ALV TOOL BAR BUTTONS / LOGIC: SPECIFY OTHER BUTTONS (Push buttons/Radio Buttons/ Check Box) LOGIC:

Detail Processing Logic:

<Specify the logic in detail > TO BE PROCEASS Identified To Be process 1. Through ELM BP will be uploaded into CRM System, then each record will be created by BP with Unique Id. 2. When Bp creation Target group will be assigned. 3. Once campaign is executed automatically mails should triggered to the respected Target group related Mail Id(BP) 4. Target Groups are defined based on the requirement. 5. We need to define various smart forms(Mail Form) as per the requirement of External Events Student Affairs Public Relations Research 6. A mail will be triggered to BP for more details in http link along with User and password(User name is BP Number and pwd should generated by system automatically). 7. Link contains one Web Form which contains multiple views, each view should followed by number of fields. 8. BP will click on link 9. Using User/password BP will log in to the web form (Link), and fill all information when click on submit, BP will be updated with all the update information. 10. An Email should triggered Once BP is updated. 11. As per the requirement one more mail can be triggered for further more details.

12

Cleint Name

Functional Specification

Realization Version 1.0

User command :
<Specify the user command details >

Report/Form Layout:
<Specify the details of reports and layouts ,Please attach the sample output format >

Bp should log in with his BP number and system generated password.

Once he log in to Web form all above mentioned views and fields should be displayed, once he provide the date and save the form automatically data should be saved in the respect tables.

Interactive report level (1.n) : Customizing path for forms/script and Name:
<Specify the customizing path required to configure for this development >

13

Cleint Name

Functional Specification

Realization Version 1.0

Paper Requirements:
<Specify if any specific paper requirement is there >

Print Requirement:
<Specify if any print requirement is there >

PDF Output Requirements: Special Characteristics:

<Specify here if any special characteristics is required >

Logical data base

<Specify details of LDB here >

Info types
<Specify Info type details>

Default selection screen Data Saving Criteria

<Specify any validations to be done before saving data, Logic to be performed after saving the data if any> When BP receive mail along with the link, as soon as hi opens link it should have multiple views and each view should followed by multiple fields, when Bp fill the save and submit the data it should be updated In the contact details

Data Mapping Requirements

TRANSFORMATION RULES Source System Target System Table-Field Table-Field Required/ Optional Field Conversion Type (Direct mapping, Logic, Table, Constant) Conversion Rules Validation

[Direct One to one mapping; Logic derived value from one or more source fields; Table One-to-One and Many-to-One mapping based on table below; Constant Does not depend on source data]

Conversion Tables Conversion Table 1: Source Value Converted Value

14

Cleint Name

Functional Specification

Realization Version 1.0

User exits / Badi / Field exit/Enhancements

Name: Detail Processing Logic Data Elemen t Data Type
Char Numaric Char Numaric Char Yes/No Char Char

Table name
ZCONADDTDATA ZCONADDTDATA ZCONADDTDATA ZCONADDTDATA ZCONADDTDATA ZCONADDTDATA ZCONADDTDATA ZCONADDTDATA ZCONADDTDATA ZCONADDTDATA ZCONADDTDATA ZCONADDTDATA ZCONADDTDATA ZCONADDTDATA

Field
ZContact Name ZTelephone ZEmail zAge Zvisa pick up country ZI Require Visa ZNearest Saudi Embassy ZRegion ZAttached scanned copy ZDepature date ZDepature city Zreturning date Znotes Zspecial instruction

Key
-

Initial

Length

Char

Date Char Date Char Char 200

15

Cleint Name

Functional Specification

Realization Version 1.0

Other developments

1. Tables: Specify the name of the Standard SAP table to be enhanced or mention new tables to be created. Specify Name (Short, Medium, Long), data element, domain, Reference field, length, F1 Help document

BUT000 is the standard table where all the BP data will be saved, we need to define a table where all the enhancement data should stored and linked to this standard table. 2. Matchcode ID or search help: Specify the new matchcode ID, which has to be entered or changed. Provide details about the fields to be selected and the path in the SAP System, where the matchcode ID can be found.

3.

Modification:

Provide exact details of changes to be made (program name, transaction).

16

Cleint Name

Functional Specification

Realization Version 1.0

4.

Other Objects:

Flow Charts: Routing Table

<Describe in detail the Business Process and the Levels of Approval) Sl No Workflow Level 1 Level 2 Level 3 Level 4 Level 5

Trigger event for the workflow When Bp Details updated for BP record one work flow should triggered and thanks mail should go to BP. Termination event for the workflow
<Specify Transaction / Event relevance/ Dead line monitoring for the termination of workflow>

OTHER DETAILS
Exception Handling Rules Special Requirements
<Provide any special requirements related to this development effort such as language translations, configurability or personalization allowed, etc.>

Dependencies Constraints
<Discuss all the constraints or the limitations if any for this technical object>

17

Cleint Name

Functional Specification

Realization Version 1.0

Test Specification
<This portion of the document is used to plan the unit testing. It includes items such as defining the test participants, the test environment, the schedule, and scope of the testing event.>

Functional Test Scenarios

<Document test scenarios to test all of the functional requirements. Include a test scenario for each different business scenario that may occur.> ID
1

Test Scenario

Expected Results

Comments

2 3

Test Data & Other Needs

<If any, specify test data set-up & refresh needs, volume of data, timeliness of data, etc.>

Test System & Environment

<Identify test system and client.>
Test System: Client:

Security/Authorization Requirements
<Provide any special authorization checking or data security provisions required.>

18