Scribd Logo
Upload

Welcome to Scribd!

  • 1 views

    FS Kiit BBP MM 21

    Uploaded by

    sahewaz786

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    FS Kiit BBP MM 21

    Uploaded by

    sahewaz786
    1 views9 pages

    Original Title

    FS_KIIT_BBP_MM_21

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    1 views9 pages

    FS Kiit BBP MM 21

    Uploaded by

    sahewaz786

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 9

    FUNCTIONAL SPECIFICATION(SERACH HELP

    IN TRACKING NUMBER FEILD)

    PROJECT IDENTIFICATION

    Project Name CPI/Project Number Project Type


    (CBI, Implementation, CSS, Upgrade, Internal, other)

    EKALABYA Implementation
    Customer Name Customer Number Planned Start/Finish

    SAP Customer Partner Project Sponsor Program Manager


    DR. ACHYUTA SAMANTA PROFF. NIHAR BUERA

    SAP Project Manager Customer Project Manager Partner Project Manager


    SUSANTA PATRO RATNA KABIRAJ

    How to use the Template


    This document is intended to specify RICEFW object from a functional perspective. It will be followed by a technical
    specification during Realization. A Functional Specification has three main sections
     General Object information, to be filled in for all RICEFW objects
     Object specific details
     Test conditions and considerations

    This document builds and refers to two preceding documents


     Requirements - BPR
     Solution design – BPD

    In addition, all RICEFW object are consolidated in the RICEFW list


    [Please note: The project manager and the quality manager have to revise this template before it is used for the project
    and especially before it is given to the customer. Sometimes instructions, guidelines, explanations, hints, and tips are
    provided. It should always be removed from the template for the project.
    Top-level chapters may not be deleted or inserted; required additions should be made as sub-chapters to existing
    chapters to provide a consistent representation of this document to the customer. ]
    TABLE OF CONTENTS
    How to use the Template.................................................................................................................1
    General Object Overview................................................................................................................ 3
    Process Requirements Reference.....................................................................................................4
    Generic WRICEF Descriptions.......................................................................................................... 4
    Object Specific Design....................................................................................................................6
    Forms / Output................................................................................................................................... 6
    Test Conditions................................................................................................................................8
    Document History............................................................................................................................ 9

    2
    General Object Overview

    OBJECT OVERVIEW

    KIIT_FS_MM_21
    Business Purchase Requisition
    Object ID
    Process

    ECC6 SAP SAP Material Mangement


    SAP Release
    Module
    ( ) Report
    ( ) Interface
    ( ) Conversion
    Object Type ( X ) Enhancement
    ( ) Form
    ( ) Workflow

    Object Title Purchase Requisition ( Additional fields in PR)

    Object Description Purchase Requisition ( Additional fields in PR)

    Mock Up ID / Name N/A

    Required
    Cycle of Testing / C1 / C2 / C3 / C4 DDMONYY
    Development
    Sprint Cycle
    Completion Date
    Simple / Medium / Complex Low / Medium / High
    Complexity of Object Priority

    SAP Transaction ME51N SAP Program


    Name Name

    Similar SAP Similar SAP


    Transaction Program

    FS CONTROL

    <Customer>
    Functional Consultant
    RAIKAR.SAINATH Process Owner PANDA, SUPRIYA
    – Author and Phone
    and Phone
    Number
    Number

    Planned Date of FS 30.08.2013 Actual Date of FS 30.08.2013


    Completion Completion

    FS Approved By FS Approval date

    Other Contact and Other Contact and


    Phone Number Phone Number

    3
    Process Requirements Reference
    PROCESS REFERENCE
    Requirement ID KIIT_FS_MM_21

    Requirement Purchase Requisition ( Additional fields in PR)I.E SEARCH HELP IN TRACKING


    Description NUMBER(CONTACT PERSON TAB)
    Gap to be addressed
    Alternative SAP
    Standard Solution

    Generic WRICEF Descriptions


    JUSTIFICATION

    Purchase Requisition ( Additional fields in PR)I.E SEARCH HELP IN TRACKING NUMBER(CONTACT PERSON TAB)
    which will be used in release startgy

    FUNCTIONAL DESCRIPTION / DESIGN


    Purchase Requisition ( Additional fields in PR)I.E SEARCH HELP IN TRACKING NUMBER(CONTACT
    PERSON TAB) which will be used in release strategy

    To meet the requiremnt here ztable will be created and any value entered in tracking number will be
    checked in this ztable.

    Note:- User exit will used to meet the requirement.

    TRANSACTION VOLUME
    N/A

    4
    FREQUENCY & TIMING
    N/A

    DEPENDENCIES
    N/A

    AUTHORIZATION REQUIREMENTS

    <Every authorization object needs to be documented to provide the security administrator information
    on the purpose and use of the object. The following sections are the minimal documentation
    requirements.>

    RELATED DOCUMENTATION (ATTACH OSS NOTES, EMAILS, DOWNLOAD OF EXISTING


    REPORT, ETC)

    N/A

    5
    Object Specific Design
    Forms / Output
    <Identify outputs and forms>

    OUTPUT
    WRICEF-ID Description Data Output Type Frequency Volumes Owner
    Object (Form, EDI,
    (Sales etc.)
    Order)
    KIIT_NA_MM_21 Additional Dept
    fields in PR

    PROCESS FLOW DIAGRAM


    N/A

    FORM LAYOUT
    N/A

    6
    PRINTER REQUIREMENTS
    N/A

    LEGAL REQUIREMENTS
    Determine if there is any text that is required legally on the form, including font size, text to be printed
    on the back of documents,

    EXISTING SAMPLE FORMS

    N/A

    7
    Test Conditions
    BUSINESS TEST CONDITIONS (TO BE FURNISHED BY THE FUNCTIONAL CONSULTANT)
    [

    Scenario # Input Selection Criteria Expected Result


    1 Search help in tracking Number
    Purchase Requistion No

    8
    Document History
    AUTHORS & PARTICIPANTS
    Role Name
    Business System Analyst

    Project Process Owner

    Business Unit Process Owner

    Consultant

    Workshop Participant

    REVISION HISTORY
    Date Document Version Document Revision Author
    Description
    << Date >> 1.0 Draft for customer << Name >>
    review

    REVIEWED AND APPROVED BY


    Name Title Date Approved

    <<NAME>> Business System Analyst


    <<NAME>> Project Process Owner
    <<NAME>> Business Unit Process
    Owner
    <<NAME>> Corporate Process Owner
    <<NAME>> Internal Audit

    You might also like