Scribd
Upload
4 views

05_FS_TAB Enhancement

The document outlines a functional-technical specification for an ABAP development project aimed at enhancing the MIGO transaction in the MM module. The enhancement includes capturing additional fields such as Vehicle Number, DMR Number, Declaration Form, and others during Goods Receipt. The document details the objectives, relevant transaction codes, program logic, and the necessary technical specifications for implementation.

Uploaded by

jyotiba1127
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
4 views

05_FS_TAB Enhancement

The document outlines a functional-technical specification for an ABAP development project aimed at enhancing the MIGO transaction in the MM module. The enhancement includes capturing additional fields such as Vehicle Number, DMR Number, Declaration Form, and others during Goods Receipt. The document details the objectives, relevant transaction codes, program logic, and the necessary technical specifications for implementation.

Uploaded by

jyotiba1127
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

Functional-Technical Specification

for ABAP Development

Development Summary

Development ID To be filled by ABAP


Author & Testing By
Name of Development
Tab Enhancement in MIGO
(Short Description)
Development Type Enhancement
Module/Business Process MM
Required TCode MIGO

Technical Summary

Name of Technical
Consultant
Request No
Start Date
Completion Date
Approval Date

Version History

Change
Versio Date Revision
Request Reason for Revision
n No Updated Author
No

Company Confidential Ver. <Latest version no. > Page 1 of 5


Functional-Technical Specification
for ABAP Development

Table of Content

Contents
1. Functional Specification:....................................................................3
1.1. Objective of Development...............................................................3
1.2. Relevant Transaction Codes (Mandatory).........................................3
1.3. Selection Parameters (for reports)..................................................3
1.4. Enhancements / Interface details (for User-Exit / BADI / BAPI / BDC). .3
1.5. Pre-requisite, if any........................................................................3
1.6. Tables & Fields used.......................................................................3
1.7. Program Logic/Pseudo Code............................................................4
1.8. Report / Screen Layout....................................................................4
1.9. Special Requirement.......................................................................4
2. Technical Specification (By ABAP Team)..............................................5
2.1. Objects Used..................................................................................5
2.2. Logic Applied..................................................................................5
2.3. Assumption/Notes...........................................................................5

Company Confidential Ver. <Latest version no. > Page 2 of 5


Functional-Technical Specification
for ABAP Development

1. Functional Specification:

1.1.Objective of Development

As per Company’s requirement certain fields have to be captured in Goods


Receipt which is not available in the standard format of the Goods Receipt screen.
Hence these fields have to be enhanced so that the same will be captured in the
print layout.

1.2.Relevant Transaction Codes (Mandatory)

Transaction Code Description


MIGO Goods Receipt
1.3.Selection Parameters (for reports)

(M)andato
Table (P)arameter
Field Name Description ry
Name (S)elect Option
(O)ptional

1.4.Enhancements / Interface details (for User-Exit / BADI / BAPI / BDC)

Name Description
NA

1.5. Pre-requisite, if any

1.6.Tables & Fields used

Table Name Field Name Description Remarks

Note: Parameter is single input and Selection option is range of input

1.7.Program Logic/Pseudo Code

In Company , Goods Receipt Note (Material Receipt Note) is prepared by Store


Person. The Goods received at Gate will be transferred into Main Stores. The Store
person checks the quantity of goods received and creates Goods Receipt Note
(Material Receipt Note) in the system. In Standard SAP the same is done through T
code MIGO. However there are some limitations in standard SAP for capturing certain
details during Goods Receipt.

Company Confidential Ver. <Latest version no. > Page 3 of 5


Functional-Technical Specification
for ABAP Development

In order to fulfil the business requirement, certain fields need to be enhanced in


transaction code MIGO.

The details of fields to be enhanced is given below,

 Vehicle Number – Vehicle number in which the material is shipped by


vendor. This should be optional, as some materials will be shipped in person
also. The field should be alpha-numeric with maximum 15 characters.

 DMR Number- This is an alpha-numeric number given at the time of entry of


goods.

 Declaration Form – Declaration form can be “C” form or “F” form under
which material has been sent by the supplier. The number of the Declaration
forms received need to be captured in order to track and close the same. The
field should be alpha-numeric with maximum 30 characters.

 Gate Entry Number – This is a manual input number. The field should be
maximum 20 characters.

 Gate Entry Date- This is a manual input date. The field should be maximum
10 characters

 Invoice/Bill Number - Invoice/bill number which has been sent by vendor


along with material is captured in this field. It should be alpha-numeric with
maximum 20 characters.

 Remarks: A field has to be enhanced to give details as per requirement.


Characters will be decided as per flexibility on screen

1.8.Report / Screen Layout

1.9.Special Requirement

A tab enhancement for MIGO will be done. Few fields have to be captured from
those to print. Field details will be mentioned after enhancing tab in MIGO

1.10. Assumption/Note

Company Confidential Ver. <Latest version no. > Page 4 of 5


Functional-Technical Specification
for ABAP Development

2. Technical Specification (By ABAP Team)

2.1.Objects Used

Logical Database

Tables

Secondary Indexes (if exist / created)

Includes

Function Modules / RFC

BAPI / BDC Type

Message Class

Called Screens / TCode / Programs

Implementation Name / Project

Package

2.2.Logic Applied

2.3.Assumption/Notes

Company Confidential Ver. <Latest version no. > Page 5 of 5

You might also like