Financial Doc Status

Technical Specification
Technical Evaluation Report

Last Updated On: 25 Oct 2014 Page 1 of 17 Version: 1

 Financial Doc Status

Document Information

Deliverable Name TER Screen

Author Ajay Gulati
SAP Module/Team MM
FS Shivraj Anvikar / Rahul Jain
Priority High
Complexity Level Medium
Program Type Enhancement
Version V1.0
Status Completed

Revision History

Version
Date Author Revision Description
No.
V1.0 20/11/2014 Ajay Gulati

Other Related Documents

Related Document Comment

MM_FS_009_TER

1 Development Overview

1.1 Requirements Summary

As per the business requirement “The Technical Evaluation will be used for quotations and award
the respective bidder”. The scope of this functional enhancement is that the business user should
be able to send the TR to approver for approving it.

Last Updated On: 25 Oct 2014 Page 2 of 17 Version: 1

 Financial Doc Status

1.2 Assumptions

1.3 Dependencies / Constraints

1.4 Objects or Transactions Affected

1.5 Transaction Volume

1.6 Standards

1.7 Security, Integrity, and Controls

1.8 Error Messages

Error Number Error Message Corrective Action
001 Email ID not maintained for recipient Check the value
002 Already created Check the value
003 Changes aborted ‘authorization missing’ Check the value
004 Error in posting Check the value
005 Error in sending mail Check the value
006 You have not put your remark Check the value
007 You have not complete your review Check the value
008 You have not update your rejection code Check the value
009 You have processed this Doc Check the value
010 User id not mapped with PRF system Check the value
011 No value found Check the value
012 Not refreshed Check the value
013 Select record first Check the value
014 Please pass fund center to proceed Check the value
1.9 Estimation of Effort

1.10 SAP Objects

Last Updated On: 25 Oct 2014 Page 3 of 17 Version: 1

 Financial Doc Status

Name Type Description

Program ZMM_TER_WF_MGMT
Include ZMM_TER_WF_INC_TOP
ZMM_TER_WF_INC_FORMS
ZMM_TER_WF_INC_STD
ZMM_TER_WF_INC_PBO
ZMM_TER_WF_INC_PAI
Transaction ZMM_TR
Table
Project
User Exit
BADI Implementation
Method
Implementing class
SAP Script
Adobe Form
Message Class
BOR Object
Workflow Template
Enhc. Implementation

2 Detailed Technical Specifications

2.1 Technical Flow Diagram

2.2 Selection Screen Details

NA

Last Updated On: 25 Oct 2014 Page 4 of 17 Version: 1

 Financial Doc Status

2.3 Technical Flow Description

1. Create a program for workflow in TER and first create a main screen 1000 and as
Per business requirement use the parameters in the screen as shown below:

2. Create a module in PBO and write a code for fetch the PO item data
‘MODULE FETCH_PO_ITM_DATA’

3. Check if work area WA_EKKO is initial then fetch all the fields from EKKO into
WA_EKKO where EBELN = GV_EBELN

4. If WA_ZNFA_PO_HDR_NFASTATUS is initial
WA_ZNFA_PO_HDR_NFASTATUS = ‘I’

5. If internal table IT_EKPO is initial then fetch all the data from EKPO into internal
Table IT_EKPO where EBELN = GV_EBELN

6. Now loop at internal table IT_EKPO into work area WA_EKPO then

WA_ZNFA_PO_HDR-NFAAMT = WA_ZNFA_PO_HDR-NFAAMT + WA_EKPO-NETWR

Last Updated On: 25 Oct 2014 Page 5 of 17 Version: 1

 Financial Doc Status

7. Now create F4 help for ‘TER NUMBER’ and ‘DISPLAY RFQ’ and call the function module
For F4 help of TER NUMBER and DISPLAY RFQ as shown below:

Fetch SUBMI from EKKO into corresponding field of table GV_HELP_SUBMI

If GV_HELP_SUBMI is not initial then call the function module:

(a) F4 help for ‘TER NUMBER’

Call function 'F4IF_INT_TABLE_VALUE_REQUEST'

Exporting
Retfield = 'SUBMI'
Dynpprog = lv_progname
Dynpnr = lv_dynnum
Dynprofield = 'WA_EKKO_RFQ_SEL-SUBMI'
Value_org = 'S'
Tables
Value_tab = gv_help_submi
Return_tab = lt_return
Exceptions
Parameter_error = 1
No_values_found = 2
Others =3

If gv_help_submi is initial then throw the message ‘NO VALUE FOUND’ and read the
Dynpro value by use the function module ‘DYNP_VALUES_UPDATE’

(b) F4 help for ‘DISPLAY RFQ’

Call function 'F4IF_INT_TABLE_VALUE_REQUEST'

Exporting
Retfield = 'RFQ_NO'
Dynpprog = lv_progname
Dynpnr = lv_dynnum
Dynprofield = 'GV_RFQ'
Value_org = 'S'
Tables
Value_tab = gt_rem_rfq
Return_tab = lt_return
Exceptions
Parameter_error = 1
No_values_found = 2
Others =3

Last Updated On: 25 Oct 2014 Page 6 of 17 Version: 1

 Financial Doc Status

If gt_rem_rfq is initial then throw the message ‘NO VALUE FOUND’ and read the
Dynpro value by use the function module ‘DYNP_VALUES_UPDATE’

8. When click on the ‘CREATE’ button then check if TER NUMBER is initial then
Throw the error message ‘Please enter collective number’

If TER Number is not initial then fetch all the field into work area WA_EKKO_SUBMI
From EKKO where SUBMI = WA_EKKO_RFQ_SEL-SUBMI

If OK_CODE = ‘CREATE’ then fetch all the field from ZMM_REM_ITEM into
WA_FINAL where SUBMI = GV_SUBMI and when condition is false then throw
The error message ‘TER not yet created for ‘WA_EKKO_RFQ_SEL-SUBMI’

9. When enter the remark text then click on the ‘SAVE_REM’

Wa_znfa_po_rem-ebeln = gv_ebeln
Wa_znfa_po_rem-usnam = gv_userid

Wa_znfa_po_rem-remark_code = wa_remark_code
Wa_znfa_po_rem-remark1 = wa_remark1
Wa_znfa_po_rem-remark2 = wa_remark2
Wa_znfa_po_rem-remark3 = wa_remark3
Wa_znfa_po_rem-c_flag = wa_flag

Wa_znfa_po_rem-budat = sy-datum
Wa_znfa_po_rem-a_hier = gv_hier
Wa_znfa_po_rem-role = gv_role

MODIFY ZNFA_PO_REM from WA_ ZNFA_PO_REM

If condition is true then throw the message ‘REMARKS UPDATED’ and if condition is
False then throw the message ‘REMARKS NOT UPDATED’

10. Now create a TAB SCREEN ‘1001’ and write code inside the PBO event
And PAI event as shown below:

Last Updated On: 25 Oct 2014 Page 7 of 17 Version: 1

 Financial Doc Status

11. Now create a ‘RFQ AND PR SCREEN’ ‘1002’ and write code inside the PBO event
And PAI event as shown below:

Last Updated On: 25 Oct 2014 Page 8 of 17 Version: 1

 Financial Doc Status

12. Now create a ‘PO_LINE DETAIL’ ‘1003’ and write code inside the PBO event
And PAI event as shown below:

Last Updated On: 25 Oct 2014 Page 9 of 17 Version: 1

 Financial Doc Status

13. Now create a ‘APPROVE_TAB’ ‘1004’ and write code inside the PBO event
And PAI event as shown below:

14. Now create a ‘LONG COMMENT TEXT HISTORY’ ‘1005’ and write code inside the PBO event
And PAI event as shown below:

Last Updated On: 25 Oct 2014 Page 10 of 17 Version: 1

 Financial Doc Status

15. Now create a ‘OLD RFQ AND PR SCREEN’ ‘1022’ and write code inside the PBO event
And PAI event as shown below:

16. Now create a ‘APPROVAL HIERARCHY’ ‘1400’ and write code inside the PBO event
And PAI event as shown below:

Last Updated On: 25 Oct 2014 Page 11 of 17 Version: 1

 Financial Doc Status

17. Now the process for ‘SENT FOR APPROVAL’ write code for sent for approval as shown below:

Fetch all the fields from ZNFA_PO_REM into WA_ ZNFA_PO_REM where
USNAM = GV_USERID
EBELN = GV_EBELN

If WA_ZNFA_PO_REM is initial then

WA_znfa_po_rem-ebeln = gv_ebeln
WA_znfa_po_rem-usnam = gv_userid
WA_znfa_po_rem-a_hier = gv_hier
WA_znfa_po_rem-role = gv_role
WA_znfa_po_rem-remark_code = ' '
WA_znfa_po_rem-remark1 = 'OK'
WA_znfa_po_rem-c_flag = 'X'
WA_znfa_po_rem-budat = sy-datum

MODIFY ZNFA_PO_REM from WA_ZNFA_PO_REM

Now fetch all the data from ZNFA_PO_APS_STS into WA_ZNFA_PO_APS_STS

Where EBELN = GV_EBELN
USNAM = GV_USERID
APP_CAT = ‘O’

If WA_ZNFA_PO_APS_STS is not initial then fetch all the data from ZNFA_PO_APS_STS into
WA_ZNFA_PO_APS_ST where EBELN = GV_EBELN
APR_TYPE = ‘A’
APR_CAT = ‘A’
EDIT_NFA = ‘X’
If WA_ZNFA_PO_APS_STS is not initial then throw the information message ‘Its still
Not approved from additional approver’

Now fetch all the fields from ZNFA_PO_REM into work area WA_ ZNFA_PO_REM

Last Updated On: 25 Oct 2014 Page 12 of 17 Version: 1

 Financial Doc Status

Where EBELN = GV_EBELN

USNAM = GV_USERID
C_FLAG = ‘X’

WA_ZNFA_PO_REM-ACTIVITY = ‘APPROVED’

Now fetch all the fields from ZNFA_APPROVER into WA_ ZNFA_APPROVER
Where USNAM = GV_USERID

If WA_ ZNFA_APPROVER-APR_CAT = ‘I’

WA_ZNFA_PO_REM-ACTIVITY = ‘SENT FOR APPROVAL’

If WA_ ZNFA_APPROVER-APR_CAT = ‘R’

WA_ZNFA_PO_REM-ACTIVITY = ‘REVIEWED’

Wa_znfa_po_rem_hist-activity = wa_znfa_po_rem-activity
Wa_znfa_po_rem_hist-timestamp = cur_time_stamp
Wa_znfa_po_rem_hist-budat = sy-datum
Wa_znfa_po_rem_hist-btime = sy-timlo

MODIFY ZNFA_PO_REM_HIST from WA_ ZNFA_PO_REM_HIST

Now submit the report ‘ZMM_SEND_NOTIFICATION’ to send the mail

18. Now the process for ‘REJECTION’ write code for rejected as shown below:

Fetch all the fields from ZNFA_PO_REM into WA_ ZNFA_PO_REM where
USNAM = GV_USERID
EBELN = GV_EBELN

If WA_ ZNFA_PO_REM-REMARK_CODE is initial then throw the information

Message ‘You have not updated your rejection code’

Now fetch all the fields from ZNFA_PO_REM into work area WA_ ZNFA_PO_REM
Where EBELN = GV_EBELN
USNAM = GV_USERID
C_FLAG = ‘X’

WA_ZNFA_PO_REM-ACTIVITY = ‘REJECTED’

Wa_znfa_po_rem_hist-timestamp = cur_time_stamp
Wa_znfa_po_rem_hist-budat = sy-datum
Wa_znfa_po_rem_hist-btime = sy-timlo

MODIFY ZNFA_PO_REM_HIST FROM WA_ ZNFA_PO_REM_HIST.

Now submit the report ‘ZMM_SEND_NOTIFICATION’ to send the mail and throw
The message ‘Rejection mail sent to all concerned user’

Last Updated On: 25 Oct 2014 Page 13 of 17 Version: 1

 Financial Doc Status

2.4 Security and Authorization

To be authorized to the concerned person having right to execute the transaction
2.5 Processing and Operational Considerations

2.5.1 Dependencies
NA
2.5.2 Batch Requirements

NA

2.5.3 Restart / Recovery Procedures

2.5.4 Data Maintenance Requirements

2.5.5 Re-use Details

2.5.6 Multi-Company, Multi-Jurisdiction Considerations

N/A

3 Technical Requirements
3.1 Database Tables
NA
3.2 External Programs
NA
3.3 Development Class
ZMM01
3.4 Message Class
NA
3.5 Program ID
NA
3.6 Program Type
NA
3.7 Module
MM
3.8 Transport Number(s)
CR Request Number Task Number

Last Updated On: 25 Oct 2014 Page 14 of 17 Version: 1

 Financial Doc Status

3.9 Detailed Design

3.9.1 SAP Objects

Name Type Transport No. Description
Transaction Code Transaction Code
Executable Program Main Program
Include Program Top Include
Include Program Selection Screen
Include Program Processing routine
3.9.2 Request Mechanism / Trigger
NA
3.9.3 Configuration (optional)
NA
3.9.4 Pseudo Code

3.9.5 ABAP Development

3.9.6 Workflow
N/A

3.9.7 Dialog Program

N/A

3.9.8 Custom Table Development

 Table Field Definitions
Field Name Character Key Description
N/A

 Table Validation Rules

Event Form Routine Include
N/A

Last Updated On: 25 Oct 2014 Page 15 of 17 Version: 1

 Financial Doc Status

3.9.9 User Exit

3.9.10 Field Exit

N/A

3.9.11 Technical Design Constraints

N/A

3.9.12 Programmer’s Notes

4 Testing Requirements
4.1 Key Unit/Assembly Test Conditions
Unit Test Log
Test Objective

Step Date Description Expected Actual Requirement ID Sign-off

No. Output/Results Output/Results

Notes

5 Outstanding Issues
Issue No Description Assigned To Status Impact Resolution
001
002

6 Appendix
6.1 Glossary of Terms
Term Definition

6.2 Additional Supporting/Reference Documentation

Last Updated On: 25 Oct 2014 Page 16 of 17 Version: 1

 Financial Doc Status

6.3 Report Output

Last Updated On: 25 Oct 2014 Page 17 of 17 Version: 1