GST Purcahse Register SAP MM

1. File Name: Page 1 of 8
Functional specification
Version:
Specification No :
(To be filled by Technical Department)
Issue Date
(dd/mm/yyyy):
13/09/2017
In Preparation Review
Approved Released
Revision History
Version Date Description of changes
01 13/09/2017 ZMMPRG - GST Purchase Register
Responsible
For concept Lapp India For Implementation
Section I: Justification
Area ( Module): MM Lokeshbabu.M Date
(dd/mm/yyyy):
12/09/2017
Requested by: Lokeshbabu.M
Brief description: ZMMPRG - GST Purchase Register
Program type: (select
the check box)
Conversion Batch Interface Online Interface Report
Form Enhancement Extension Dialog
Modification Unknown Others BAPI
ALE/ IDOC Application Development
Charateristics Drill Down ALV Others (pl specify)
Priority: High/mandatory Medium/recommended Low/optional
Only for Interfaces:
Type of interface:
Direction of interface:
Frequency:
Real-Time Batch
Inbound Outbound Both
Daily Weekly Monthly
Biweekly Other:

2. File Name: Page 2 of 8
Only for Reports:
1. The report will be created via:
2. Requested characteristics:
3. Praposed execution is
online/background
4. Any Authority checks are required
5. If any LDB is available? if yes,
which screen to use
Report Painter Report Writer ABAP Query
ABAP Program Info System
Drill-down Pushbuttons Sort
Entry files Others:
Sign off – Functional Specification
Prepared By
Lokeshbabu.M
Date: 13/09/2017
<Name of Core Team
Member>
Comments
Team Lead
Date
<Name of Core Team
Lead>
Lead Consultant
Date:
Approved Integration Manager
Approved by Project Management Team
(in case of Application development)
/ /
/ /
Received Team Lead/ Lead Consultant
Date / /
Section II: (a) Business Requirement (Please use this section for describing the business
requirement in detial preferably with flow diagram)
The Purchase Register as per GST Regime, New fields to be added to existing report ZFI422, you can
see the input screen with multiple fields. None of the field is mandatory and the report should be
able to execute with no entries. All input fields should have multiple selections.
ZFI422_C FORM
DATA_Report.xls
BHEL_ZMMPRG.xls

3. File Name: Page 3 of 8
(b) Detailed Functional Description Concept – Operational Requirements (describe in
detail)
Requirement:
The selection should mainly be based on Z Program ZFI422, New fields are going to be added to existing
report Program ZFI422 (C form data - Transaction code) copy and name it as ZMMPRG (New Z T-code)
Report Logic
1. Company Code - Pass Input Tax Code (MWSKV) in T001 to fetch BUKRS- T001.
2. Invoice DocNo(MIRO) - Pass Purchase order number (EBELN) in RSEG to fetch BELNR-RSEG.
3. Vendor GSTN No - Pass Vendor Code (LIFNR) in LFA1 fetch LFA1-STCD3.
4. Consignee State – Pass Purchase order number (EBELN) and Purchase order item number (EBELP)
in EKPO to fetch Plant (WERKS). Pass Plant (WERKS) in T001W fetch T001W-REGIO.
5. Unloading Point - Pass Goods Receipt number (MBLNR) in MSEG to fetch ABLAD-MSEG.
6. HSN/SAC Code - Purchase order item number (EBELP) in EKPO to fetch Material Number (MATNR).
Pass Material Number (MATNR) in MARC fetch MARC-STEUC.
7. HSN/SAC Code Description - Purchase order item number (EBELP) in EKPO to fetch Material
Number (MATNR). Pass Material Number (MATNR) in MARC fetch MARC-STEUC. Pass HSN/SAC
Code( STEUC) in T604N fetch T604N-TEXT1.
8. Unit of Measurement - Purchase order item number (EBELP) in EKPO to fetch Material Number. Pass
Material Number (MATNR) in MARA to fetch MARA-MEINS.
9. CGST/SGST/IGST/CESS - % of Tax & Amount - use Functional Module
FM GET_TAX_PERCENTAGE and table T_KONV to fetch CGST/SGST/IGST/CESS.
10. Currency - Pass Purchase order number (EBELN) in EKKO to fetch WAERS-EKKO
11. E-way Bill No – Replace E-sugam No. with E-way Bill No.
12. Bill of entry no - Pass Purchase order number (EBELN) in RSEG to fetch BELNR-RSEG. Pass
Invoice DocumentNumber BELNR and XBLNR in RBKP to fetch XBLNR –RBKP.
13. Bill of entry date – Pass Purchase order number (EBELN) in RSEG to fetch BELNR-RSEG. Pass
Invoice DocumentNumber BELNR & XBLNR & BLDAT in RBKP to fetch BLDAT –RBKP.
14. HSN as pr BE – Pass BELNR & EBELN & HSN_SAC in RSEG fetch HSN_SAC-RSEG.
15. Assessable value as per BE - Pass BELNR & GJAHR & EBELN in RSEG fetch CUSTOMS_VAL-
RSEG.
16. Invoicing Party GSTN – Pass Purchase order number(EBELP, LIFRE, LIFNR ) in EKKO fetch LIFRE-
EKKO, Pass Vendor Code ( LIFNR & STCD3 ) in LFA1 fetch LFA1-STCD3.

4. File Name: Page 4 of 8
For Conversion
Tables
involved:
LFA1, T001, RSEG, MARA, MARC, EKPO, EKKO, MSEG, T001W, T604N, KONV, RBKP,
Fields EBELP, LIFRE, LIFNR, MWSKV, BUKRS, WAERS, BELNR, XBLNR, EBELN, HSN_SAC
CUSTOMS_VAL, MATNR, MEINS.
For Interface
Fields Required From Source System:
Field Description Field Name in Source System Data Type
Fields Required From Traget System:
Field Description Field Name in Target System Data Type
Data Mapping:
Field Name in Source System Field Name in Target System
Validation:

5. File Name: Page 5 of 8
Procession Logic:
Error Handling Requirements:
SAP Input Screen (Data Mapping)
Transaction:
Screen
number
R/3 Screen field
name
Legacy field Remarks
Online
Tables
involved:
Consistency checks that must be done:
Item Screen Field Description
1.
2.
Forms
Tables
involved:
Design of desired form – Layout set:
Specify the default layout set if available
Standard Form Model:

6. File Name: Page 6 of 8
Attach copy of existing form as sample. Explain here the detail requirement for Laout viz. usage/ data
volume/ Can it be standardise etc
If this form is a copy of a standard form or if there is a model in the legacy system, please include the
copy here. Include also the name of the standard form and path/transaction where it is in the SAP
System.
Desired output:
Give a pictorial view of the desired output Enclosed below
Enhancement:
Specify the available enhancement name, customizing path and details about what must be done. Please
ensure all customization done w.r.t. testing

7. File Name: Page 7 of 8
Test Case and Test Related Result
specification
Format No/ Rev: TC-ABAP-001/ 00
Number: Prepared on
Test Cases (with expected results)
Section I: Unit Testing
Program name: Test
date:
/ /
Developer
name:
Team Members
(Functional)
Responsible functional team member for testing:
1. File(s) used for test (optional):
2. Does the program comply with the functional specification ?
Yes No
Note: If the program is OK just sign the form. If necessary include some comments in the appropriate section.
3. If the answer to question 2 is "No" please describe the problems that were found in the program.
Sign off after testing
Team Lead
Date / /
Lead Consultant
Date / /
Sign-Off and Acceptance of developed object

8. File Name: Page 8 of 8
Names and Signatures
_______________________________________________________________________________________
Team Lead
_______________________________________________________________________________________
Lead Consultant