Skip to Content
avatar image
Former Member

how as a sap sd consultant u know

hi

This was the question recently asked by the panel how do u find as a sap sd consultant which field belongs to which table and how will u give the funcitonal spec to the development team to prepare a technical specification.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Aug 22, 2007 at 05:24 AM

    t.cadese11 to find table belongs to field

    enter fieldname- and select icon where is used list, then you will get pop up screen in which you have to select table or structure , fields etc

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 22, 2007 at 05:27 AM

    Hi ,

    Just go to that field and press F1 and then check the technical details.

    There you will find the technical field name and also the table name.

    Reward points if it helps.

    Nilesh

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 22, 2007 at 05:30 AM

    HI

    unctional specification

    Func Spec basically contains the information about the business process which needs to be mapped on to the IT system (SAP). It encompasses all the related function points which will be part of the business process.

    It also mentions the programs or utilities which can be enhanced/modified/copied to achieve the end result (in case the functional consultant is aware of the program/utility)

    Function Specs is a document which a functional consultant prepares to be given to Abaper. This Document contains details like Tables & fields name, Table joints, Logic for development, along with test case in sand box / test server to verify the development.

    Format for Functional Specs:

    Document Control

    Change History

    Issue No

    Date

    Name

    Change

    Initial Draft

    Authorizations

    Role

    Name

    Signed

    Date

    Business Process Lead (customer)

    Functional Analyst (specification author)

    Technical Lead

    Developer (if known)

    Select program type below and then use menu option tools > unprotect to

    open other fields for input

    Type

    Table of Contents

    Document Control 1

    Overview. 3

    1.1 Short Description. 3

    1.2 Business Process. 3

    1.3 Terminology. 3

    1.4 New Custom Objects Required. 3

    1.5 Impacted SAP Transactions/Tables. 4

    Process Decomposition. 5

    2.1 Process Flow. 5

    2.2 New Tables/Structures Required. 5

    2.3 Sub-Process Description. 5

    2.4 Error Handling. 5

    2.5 Security Considerations. 5

    2.6 Database Considerations. 5

    2.7 Conversion Implications. 5

    2.8 Batch Processing. 6

    2.9 Functional Test Requirements. 6

    Overview

    1.1 Short Description

    1.2 Business Process

    1.3 Terminology

    1.4 New Custom Objects Required

    Include all new tables, key new fields/domains, new lock objects, new

    match-codes, new transaction codes, new authorization objects, new

    function groups, reports and module pools (transaction programs). Don't

    specify all includes, function modules, routines etc. here.

    Type (table, transaction etc.)

    Description

    Naming convention

    1.5 Impacted SAP Transactions/Tables

    List SAP objects updated/impacted by this specification (do not include

    read only impacts)

    Object(s)

    Type (table, transaction etc.)

    Description of Impact

    Process Decomposition

    2.1 Process Flow

    2.2 New Tables/Structures Required

    Specify new tables and structures required. If appropriate, you may

    defer detailed field list/specification to the technical specification

    (e.g. for secondary tables and structures).

    Table id

    Description

    Type

    Master, transaction, customizing, staging

    Expected size

    Maint. dialog

    None, SM30, custom

    Fields

    Key

    Domain/data element names

    Domain format (if new)

    Description

    2.3 Sub-Process Descriptio

    2.4 Error Handling

    Specify what to do if a condition passes AND fails (e.g. - what happens

    if a customer record is found, or is not found). Specify messages and

    type.

    Specify any special error logging or table storage, including use of

    standard application log where appropriate.

    Field

    Validation

    Message type/no.

    Message text

    2.5 Security Considerations

    2.6 Database Considerations

    2.7 Conversion Implications

    2.8 Batch Processing

    2.9 Functional Test Requirements

    Consider all the conditions that need testing for this enhancement and

    document below. For each logic branch in theory both (or more)

    conditions of the branch should be tested. For each scenario that could

    impact program execution, all situations must be tested.

    No.

    Test condition

    Expected result

    Data set-up reqt.

    Dependencies

    <b>SE11 </b>allows you to view the table structure, SE16 allows you to see the table data.

    Put V* in database table field & click on disply. you will find maximum sales tables over there.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 22, 2007 at 05:45 AM

    Dear nag nageshwar,

    Use Transaction Code SE11 which will allow you to view the table structure.

    Use Transaction Code SE16 which will allow you to see the table data.

    Put V* in database table field & click on display and you will find maximum sales tables over there.

    Hope this helps you.

    Do award points if you found them useful.

    Regards,

    Rakesh

    P.S. you can send me a mail at my mail id rakeshsinghchauhan@gmail.com for any specific details

    Add comment
    10|10000 characters needed characters exceeded