Professional Documents
Culture Documents
FSD-K001-003 - Update Extra Information For Item - Tiitm9200m000
FSD-K001-003 - Update Extra Information For Item - Tiitm9200m000
For
From
Confidentiality
The contents of this Document are provided to Phoenix Contact India Pvt Ltd in confidence
solely for the purpose of implementing Infor Ln 10.8 (with localization) at the Customer site
by Godrej Infotech Limited (hereinafter mentioned as GITL). The contents herein are the
intellectual property of GITL. Any Non-Godrej products mentioned in this document are the
intellectual property of the respective vendors. Distribution of this document outside of the
intended audience or reproduction of its contents by any means requires prior consent from
GITL.
Enquiries
Represented by –
Fax : +91-22-25181728
Email : bibekc@godrej.com
Document Control Information
Document Details
Document Title Functional Specification Document
This document was created to capture the Functional
Background
Specifications of Print Extra Information for Item at Phoenix
Contact India Pvt Ltd.
LN Standard Invoice Report Layout does not meet the business
requirement. Report personalization is required on Standard
Report Output.
Contributors NA
Version History
Ver Date Prepared By Reviewed By Reason for Change
2.0
3.0
Table of contents
1 Introduction.......................................................................................................................................6
Purpose..................................................................................................................................................6
Intended Audience................................................................................................................................6
Terminology...........................................................................................................................................7
Next steps..............................................................................................................................................7
2 Functional Requirement...................................................................................................................8
Background:...........................................................................................................................................8
Requirement:.........................................................................................................................................8
Solution Process:...................................................................................................................................8
Conceptual Design:...............................................................................................................................8
Report Layout:.....................................................................................................................................13
3 Non-Functional Requirement........................................................................................................13
4 Test Scenarios..................................................................................................................................13
5 Test Scripts.......................................................................................................................................13
6 Technical Design.............................................................................................................................13
Definition:.............................................................................................................................................13
Overview of Attributes:.......................................................................................................................13
Indices:..................................................................................................................................................13
Functional Constraints:.......................................................................................................................13
Validations...........................................................................................................................................14
7 References........................................................................................................................................14
Definitions............................................................................................................................................14
Abbreviations.......................................................................................................................................14
1 Introduction
This Functional Specification Document (FSD) is based on discussions that GITL consultants had
with the Phoenix Contact India Pvt. Ltd Team and subsequent Business Process that was
demonstrated to and approved by the Phoenix Contact India Pvt. Ltd team.
This FSD and proposed System Design has been made with reference to the TCP Document No.
GITL/TCP.IMPL_FC2.1 approved on [Approval Date 25.05.2023]
Purpose
The FSD (Functional Specification Document) typically describes what is needed by the system
user as well as requested properties of inputs and outputs. A Functional Specification is the
more technical response to a matching requirements document. It picks up the results of the
Business Process requirements study stage and translates the requirements that require
configuration/development into technical details.
Intended Audience
In the FSD, the requirements from various function owners are addressed. Apart from
management team at Phoenix Contact India Pvt Ltd. various contributors and future users of
the system should form the Audience of this FSD.
Terminology
NA
Next steps
The key users and business process owners at Phoenix Contact India Pvt Ltd. are
requested to review this document in so far as it pertains to their process areas and
provide a sign off in confirmation of completeness and correctness of the process
descriptions, business rules, processes and reporting requirements captured in this
document.
2 Functional Requirement
BACKGROUND:
This FSD has been prepared in context of BaaN IV - Kernel 001 - Extra information for item. This
is the core master data information related to items which are required for the reports published
to PxC - Head quarter (Germany). Since kernel sessions are mandatory for Germany, all the
components related to German Kernel will be migrated to Infor LN 10.8 as it is.
REQUIREMENT:
SOLUTION PROCESS:
A separate session will be created to Update Extra Information for Item (tiitm9200m000) from
BaaN IV to LN 10.8 (as it is with new session codification).
CONCEPTUAL DESIGN:
Click on Drop down - Item From- It will open Display Item Data (tiitm0501s000) from where you can
choose item. The session can be run for a specific range of items or generally.
This session consists of two parts. The first part checks which item is in table tiitm001 and updates table
tiitm900.
Click on Order (From/To)- open the sub session- tdsls4512s000 Display Sales Orders by Orders Numbers.
Here you can choose order number.
With the switch Init table tiitm900 items which are currently not in table tiit900 are imported. The fields
aoes, qlsy, qytd, qltp are set to 0 (zero).
Depending on Parameters in tcpxc0112m000 field sibl will be set to “No”:
If Parameter ti pxc 9200.02 is set to 0 or doesn’t exits, field sibl will not be changed.
If supplier code is set in parameter 9200.01, field sibl remain unchanged. If original sibl is "No", it is "No,
if original sibl is "Yes", it is "Yes"
Note- If supplier code is not set in parameter 9200.01, the tiitm900.sibl are always set to "No".
The new option “Init Dates” of the session allows to initialize the creation date BBG and the launch date.
If the birth date or the launch date of an item is not set already, then it may be filled with an
aproximated value, using the date of the first occurrence of a cost price.
The form fields are relevant for this new option only:If the switch “Overwrite” is set to “Yes” then the
cost price date will also be written to non-empty fields.
Report Layout:
NA
3 Non-Functional Requirement
NA
4 Test Scenarios
Update is happening or not as per as is scenario compared to BaaN IV or not.
5 Test Scripts
NA
6 Technical Design
Field Mapping attached in screen shot.
DEFINITION:
tiitm9200m000
OVERVIEW OF ATTRIBUTES:
NA
INDICES:
NA
FUNCTIONAL CONSTRAINTS:
NA
VALIDATIONS
7 References
DEFINITIONS
ABBREVIATIONS
NA