Netweaver Development Form

Form Functional Specification- FS_FRM_AMI_PM_010

1 About the Form

Objective* Design Maintenance order form for PM

Preparation Date* 02/07/2018

Prepared By PM Team
Contact no. Functional
Technical Specialist
Contact no. (Technical reviewer)
Last Change Date
Last Changed By

Priority or need for this form (check one) High Medium Low
If you answered “High,” briefly
explain why you set this priority:

Complexity of this form (check one) High Medium Low

If you answered “High,” briefly
explain why you set this priority:

Date form needed by

1 Form name: Enter a suggested name for the form you want.
Note that for custom Forms, the assigned name will appear in the system.

PM_AMI_MAINT_ORDER

2 Short description: Enter a short description of the desired form (including the benefit of the
form). Note: For custom forms, the short description is included in the documentation.
Purchase Order Form: The Maintenance Order form is required to be printed by Maint department
to start maintenance work by Technician.

Form Functional Page 1 of 8

SBM SAP Implementation JET
Specification
 3 Business decision: Forms enable business decisions. What decisions might be made after using
this form? Based on this decision, what R/3 System functionality might be directly used?

2 Technical Specifications
1 Business data source(s): Enter the name of the application(s) or data area(s) of the form.
Examples: SD-shipping, FI-accounts payable, HR-payroll, and so on.

PM-Maintenance Order

2 Known tables or fields: Specify any known tables or fields in the desired form. Recommendation:
Consult with the form developer or a user who understands the technical aspects of the application
areas.

3 Similar forms in the R/3 System: List any standard R/3 forms you found that are similar to the one
you have requested. Discuss why the standard form does not fit your needs. Hint: If you find a form
that contains some—if not all—of the fields, enter its name below.
Title of the Form Description of form; special features; Program name
features that you do not want to transaction/other
include

Form Functional Page 2 of 8

SBM SAP Implementation JET
Specification
 4 Preferred Tool:

Tool Check if Reasons why preferred

considered?

Adobe From Better layout

Smart Form Better Layout

SAP Script

Other

3 Other Technical Considerations

1 Authorizations

Indicate below the level of authorization control you want to exercise:

Should restrictions be placed on who may use this form? Yes No
Should restrictions be placed on who may see the form output? Yes No
Should certain fields be hidden from certain users? Yes No
To get the form developed and approved, is there a special Yes No
method or procedure that should be used?
Other comments or instructions:

Form Functional Page 3 of 8

SBM SAP Implementation JET
Specification
 2 Upgrades
Are there potential consequences of upgrading this form to a Yes No
newer release of the R/3 System? If yes, use space below to
explain.
Is the development of this form based on function modules used Yes No
in existing forms?

3 Development Considerations and Notes

Are there special internal tables that need to be accessed? Yes No
Are there any other key people in the company who could offer Yes No
additional information or perspectives on this form?
Would other divisions in the company need such a form? Yes No
Have other divisions in the company already created the same Yes No
(or similar) form?

4 Form Selection screen Criteria

Will be linked to the standard output type in T-code OIDF.

4.1 Desired screen design layout (selection possibilities):

Will be linked to the standard output type in T-code OIDF.

4.2 Validation for selection screen & form output

1. N/A

5 Z Table involved in form generation

Sr. Field Field Names Table Name Remarks

Form Functional Page 4 of 8

SBM SAP Implementation JET
Specification
 No Description

6 Form Layout Fields

Field Description in form Table(Structure) Short Description
sequence

1 Company Name Table:- VIAFKOS, Select field BUKRS. Go to T001 table enter
BUKRS and select BUTXT and print here.

2 Order type Table:- VIAFKOS, Select field AUART. Go to T003P enter

AUART and select TXT.. Take care of language

3 AMI Logo Print AMI Logo here.

4 Order No Table VIAFKOS , fetch:- AUFNR. Remove leading Zeros and

print here.

5 Location Table VIAFKOS , fetch:- TPLNR. Go to IFLOTX table enter

TPLNR and take PLTXT and print here.

6 M/C Name Table VIAFKOS , fetch:- EQUNR and EQFNR.

Go to EQKT table enter EQUNR and take EQKTX. Print
EQFNR and EQKTX separated by / here.

7 Requested by Table VIAFKOS , fetch:- QMNUM. Go to VIQMEL table enter

QMNUM and take QMNAM and print here.

8 Request data Table VIAFKOS , fetch:- QMNUM. Go to VIQMEL table enter

QMNUM and take QMDAT, MZEIT. Print here by separating
by / . Ex:- 15-07-2019/ 08:00 . Remove seconds.

9 Request to Table VIAFKOS , fetch:- QMNUM. Go to VIQMEL table enter

QMNUM and take ARBPL field. Go to table CRHD enter
ARBPL in OBJID take ARBPL field and print here.

10 Work Description Table VIAFKOS , fetch:- KTEXT and print here if LTEXT does
not contain any value.
If in VIAFKOS , LTEXT co
ntains value then Use READ_TEXT function module to get long
text.
In READ_TEXT function module pass Client, ID= KOPF,
Language=EN, Name= concatenate client ID and Order number
and Object= AUFK. Note down long text and print here. Print

Form Functional Page 5 of 8

SBM SAP Implementation JET
Specification
 upto 300 characters or 4 lines maximum.

11 Received by Table VIAFKOS , fetch ERNAM field and print here

12 Operations table:- VIAFKOS , select AUFPL field. Go to AFVC table enter

AUFPL and PHFLG- exclude single value "X". Execute.

Note down VORNR and LTXA1. Print here one by one. In

VORNR remove leading zeros.

13 Remarks No Logic leave blank

14 Work Start No Logic leave blank

15 Work End No Logic leave blank

16 Technician Assigned No Logic leave blank

17 Table:- VIAFKOS take GEWRK. Go to table CRHD enter

GEWRK in OBJID take ARBPL field. Print here.

18 Details & Cause No Logic leave blank

19 Activities Done No Logic leave blank

20 Parts Used No Logic leave blank

21 Noted by No logic leave blank

Attached format:

Form Functional Page 6 of 8

SBM SAP Implementation JET
Specification
 new doc 2019-07-15
15.28.51_20190715152944.pdf

Program Flow Steps

Formulas/Calculations/Rules

Assumptions/Notes

Issues # Description Resolution

List all
open
issues

Reviewers
Designation Name Date Signature

SBM

Form Functional Page 7 of 8

SBM SAP Implementation JET
Specification
 Technical Lead

Functional Lead

Approvals
Designation Name Date Signature

Project Manager

Form Functional Page 8 of 8

SBM SAP Implementation JET
Specification