4
…Message Box ( Arial, Font size 18 Bold) 63 Presentation Title ( Arial, Font size 28 ) Date, Venue, etc..( Arial, Font size 18 ) Project Saarthi Naming Conventions Oct-2013

Naming Conventions FS,TS and TR

Embed Size (px)

DESCRIPTION

Naming Conventions FS,TS and TR

Citation preview

Page 1: Naming Conventions FS,TS and TR

…Message Box ( Arial, Font size 18 Bold)

63

Presentation Title ( Arial, Font size 28 )

Date, Venue, etc..( Arial, Font size 18 )

Project SaarthiNaming Conventions

Oct-2013

Page 2: Naming Conventions FS,TS and TR

…Message Box ( Arial, Font size 18 Bold)

Functional Specification

2

Saarthi_FS_<Module Name>_Two char WRICEF Type & Object serial number>_ <Meaningful Description of particular Object>_<Changed Version >

FS-Stands for Functional Specification. <Module Name> is two character SAP module name like SD, MM, FI etc.

<Sub-Module Name> is two character sub-module name AP/AR/CO are the sub modules of Finance module (FI)

<WRICEF TYPE> refers to which type of development it is. like REPORT(RP),FORM(FR), ENHANCEMENT(EN), Interface (IF) and Workflow (WF).

<Object Serial number> refers to sequence of WRICEF like three digit number like 001, 002 etc.

<Meaning Description of particular Object> refers to unique meaningful description of Object <Changed Version > Updated design document carrying new version like ‘V1.0, V1.1’ etc.

NOTE: FS storage and version control needs to be maintained as per below object ID naming convention example TPC_FS_SDEN001.

For example:• Saarthi_FS_SDEN001_ Solar Sales_V1.0

•In case of where there are multiple sub modules within a module, sub module name will be used in naming convention Saarthi_FS_APFR007_ Contractors' Bills Verification_V1.0

Page 3: Naming Conventions FS,TS and TR

…Message Box ( Arial, Font size 18 Bold)

Technical Specification

3

Saarthi_TS_<Module Name><Sub-Module Name>_<Two char WRICEF Type & Object serial number>_<Meaning Description of particular Object>_<Changed Version >

Everything is same as above (Refer to Naming convention for FS), except the constant keyword ‘TS’ will be used for technical specification instead of ‘FS'.

For example:

1. Saarthi_TS_SDEN001_ Solar Sales_V1.0

2.In case of where there are multiple sub modules within a module, sub module name will be used in naming convention Saarthi_TS_APFR007_ Contractors' Bills Verification_V1.0

Page 4: Naming Conventions FS,TS and TR

…Message Box ( Arial, Font size 18 Bold)

Transport Request

4

For SAP Functional: SAARTHI: <Single Space>CUST_<SAP Module>/<Sub-module>_<Transaction code name>_<Meaningful Short Description>

Example: 1.SAARTHI: CUST_AA_AO90_Asset Account Determination

For SAP Technical: SAARTHI: <Single Space >DEVL_<SAP Module>/<Sub-module><RICEF Type & Sequential number>_<Meaningful Short Description>

Example:•SAARTHI: DEVL_AREN007_Asset Account Determination•SAARTHI: DEVL_PMRP008_callibration report

RICEF ID:

For ISU: DMIF007 Where ‘DM’ is the Sub Module name.

For HCM: PARP007 where ‘PA’ is the sub module name.

For ABAP R/3: AREN007, PMRP008 etc.

For SD:SDEN009 where ‘SD’ is the module name.