Professional Documents
Culture Documents
Record of Release
Table of Contents
1 General Information ........................................................................................................................ 4
2 Background ...................................................................................................................................... 5
2.1 Business Requirement ................................................................................................................. 5
3 Detail Level Design ........................................................................................................................... 6
3.1 Design Approach ......................................................................................................................... 6
3.2 Detailed Design ........................................................................................................................... 6
4 Object details ................................................................................................................................... 7
4.1 Object Name 1............................................................................................................................. 7
4.2 Object Name 2........................................................................................................................... 12
4.3 Object Name 3........................................................................................................................... 12
5 Test data and Conditions ............................................................................................................... 13
6 Implementation considerations ..................................................................................................... 14
6.1 Impact Analysis & Dependencies............................................................................................... 14
6.2 Transitional considerations ....................................................................................................... 14
6.3 Related Documents ................................................................................................................... 14
7 Basic assumptions (Notes) and limitations (constraints) of the system .......................................... 15
8 Open Issues.................................................................................................................................... 16
9 ANNEXURE ..................................................................................................................................... 17
1 General Information
Object ID and Description
Program Name Symbol Master data – Update and Report
Transaction ID
Action
Reference to Functional
Specification
Process Area TAMCO Partman Configurator
Type of Development RFC Function Module
Deployment RFC
Data Direction SAP
Reporting Tool ABAP
Presentation R/3
Paper/Screen Size NA
Volume NA
Report Execution Method Manual
Scheduling and Timing NA
Variants NA
Development Class
Project Manager Ajay Poojary
Business Analyst Sameer Ardekar
Developer Gowtham Babu M R
Complexity (L/M/H) H
Priority (L/M/H) H
Effort Estimation (Person 30 days
Hours)
2 Background
2.1 Business Requirement
From business standpoint describe:
Objective – To Create Symbol Master data in the Database and to generate a report of
Daily symbol data changes or log.
Purpose - To Create Symbol Master data in the Database and to generate a report of
Daily symbol data changes or log.
Users – TAMCO Malaysia and LTI Team
NA
Provide pictorial representation of technical design and link it to the list of objects
defined above.
4 Object details
Attributes/Types
Attribute/Type Descirption Level/Visibility/Read Typing Associated Type
Name Only
Methods
Method Name Descirption Level Visibility
Events
Event Name Descirption Type Visibility
Processing logic:
This RFC connects to the SYMBOL MASTER tab in the Configurator. The purpose of this
Function Module: ZTPC_SYMBOL_MASTER is to fetch the input data as drop down and to
show if any symbol data exists for the searched CAT number.
1. The material Number is taken from the User and first checked if it exits in Material Master.
2. If not present, give an error message that Material not found.
3. Symbol data can only be changed for the Electrical CAT numbers, if the material is non
Electrical material, then throw an error that
‘Only Electical Part Number symbol data can be created or changed'.
4. To identify if input is electrical CAT number, if the combination of second third and fourth
digit of the CAT number is greater than or equal to 500 and less than 800, then the CAT
number is of Electrical type. (This is determined based on the nomenclature of TAMCO).
5. If the material is present, check if any symbol data exits in custom table ztpc_symbol_data. If
it exist, return the symbol master parameters and its corresponding symbol master data and
the material description in the response.
6. If symbol master data is not present in table ztpc_symbol_data, return the symbol master
parameters in order to facilitate the input of symbol data.
7. The Input of the Symbol data will be having a set of defined values that are determined by
the characteristics for each symbol parameters.
8. Values of the characteristics are fetched from the CAWN table and its description from
CAWNT table. Input for the above 2 tables will be CABN-ATWRT (internal Characteristic
number) which is fetched by passing the characteristics name (ATNAM) in the CABN table.
9. Below are the characteristics maintained in order to achieve the drop down functionality:
TSM_DEVICE_FAMILY
TSM_LAYOUT_SYMBOL
TSM_CUT_OUT_SYMBOL
TSM_SINGLE_LINE_SYMBOL
TSM_GRAPHICAL_PLAN_SYMBOL
TSM_SCHEMATIC_SYMBOL
TSM_FRONT_DOOR_SYMBOL
TSM_WIRE_DIAGRAM_SYMBOL
TSM_SYMBOL_ID_LAYOUT
TSM_MACRO_LIST
TSM_GRAPHICAL_PARTS_LIST
TSM_XREF_GRAPHIC
Processing logic:
The purpose of this FM is to save the symbol data which the user inputs in the symbol
master in the custom table, ZTPC_SYMBOL_DATA.
1. Input the Material number in the MAKT to get the description (MAKT-MAKTX).
2. Check if the material is already present in the table ZTPC_SYMBOL_DATA. If present update
the changed date and time else update the Created date and time.
3. Get the symbol details from the RFC FM and pass the corresponding values in the table
ZTPC_SYMBOL_DATA.
4. If successful, return a message ‘Data Successfully Updated’ else return ‘Data updation
Unsuccessful’.
Processing logic:
The Purpose of this FM is to generate a report which fetches the CAT numbers whose
symbol data has been created/changed during the day till the user Clicks on the symbol
report in the Configurator.
1. Create a Range of the date which will be execution date (sy-datum) and range for the time
which is from 12:00 AM till the execution time (sy-uzeit).
2. Fetch the symbol data from the custom table: ZTPC_SYMBOL_DATA where created date in
the date range and created time in the time range.
3. Add the symbol data where the change date in the date range and change time in the time
range.
4. If no symbol data is fetched from the point 2 and 3, return a message that
‘Symbol data for any Material not modified or created’. Else continue with Step 5.
5. Fetch the internal object number CUOBJ from the table INOB for all the materials fetched
from the above step and KLART = ‘300’. ( i.e, INOB-objek = ZTPC_SYMBOL_DATA-matnr. )
5. Fetch the internal class number (CLINT) from KSSK table for all the internal object number
(CUOBJ) fetched above.
6. Fetch the engineering description from the table ZTPC_CLASS_DESC for the class numbers
obtained from the KSSK table, and the appl_level = ‘MV2’. (MV2 – Engineering Description)
7. Fetch the material group for the material numbers from MARA table (MARA-MAKTL). Fetch
the material Group description from table T023T. (T023T-WGBEZ).
NA
4.1.7 Events
NA
4.1.8 Screen
Screen
Name
FieldName TableField/Checkbox/RadioButton Comments (Range, Default Value
Single/Multiple
Selection, Patterns,
Required, etc.)
Radio Groups
Check Boxes
Push Buttons for Drilldown reports on different levels
NA
Logo for SAPScript in case of non-pre-printed stationary
NA
Printing of SAPScript
NA
NA
NA
screen,
Popup, etc.]
NA
NA
6 Implementation considerations
6.1 Impact Analysis & Dependencies
1.
8 Open Issues
1.
9 ANNEXURE
Field Description
<ProjID>TS<identifier>
FM Name ZTPC_SYMBOL_MASTER, ZTPC_SYMBOL_INSERT, ZTPC_SYMBOL_REPORT
Module / Program Symbol Master
Description
Project Manager / Project Ajay Poojary
Leader
Developer Gowtham Babu M R
Start Date 28.10.2018
Completion Date 05.01.2019
Logical Database NA
Tables NA
Includes NA
Layout Sets NA
Printer Specific Settings NA
Function Modules NA
Development Class NA
Transactions Called NA
SBDC Sessions NA
PF Keys and Functions NA
Special Requirements NA
Authorization Check NA
Processing Logic Explained in 4.1.4
Assumption / Notes NA
Open Issues NA