Functional

Specification

RICEF Name
Purchase Order Release at Gross Value

1|Page
 Functional
Specification

Table of Contents

1. General Information________________________________________________________3
2. Overview_________________________________________________________________4
3. Logic_____________________________________________________________________4
4. Technical Details___________________________________________________________5

2|Page
 Functional
Specification

1. General Information
1.1 Status
Reference ID. EILMM19
Priority High
Version 1.0
Business Owner K.K. Mishra
Description Purchase Order Release Strategy at gross value
Prepared By Deepak Kumar Bhagat
Date of Creation 21.09.2018

1.2 Approvals
Signature and Date

Deepak Kumar Bhagat

Consultant Project Manager Business Owner

1.3 Revision History

Version Date Modified Modified By Brief Description of Change
1.0 21.09.2018 Deepak Kumar Bhagat Initial draft

3|Page
 Functional
Specification

2. Overview
On day to day business internal planning is done and based on that goods are ordered to
external vendor for which Purchase Order is created and approved by purchase department

In current business practice for approval of Purchase Order is based on total PO net value

Now business requirement is that for approval of Purchase Order should be based on total PO gross
value

3. Logic
Enhancement: M06E0004 (Changes to communication structure for release purch. doc.)
FM: EXIT_SAPLEBND_002
Exit: ZXM06U22

Loop at table BEKPO (only exclude mark for deletion line item) and collect EFFWR (Gross Value) into one
variable.
Endloop.

If variable is not blank (not initial) and CEKKO-GNETW (Net value) is not blank (not initial)
Delete the value available in CEKKO-GNETW (Net value)
Modify the value available from variable to CEKKO-GNETW (Net value).
Endif.

4|Page
 Functional
Specification

3.1 Test Specification

3.2.1 Functional Test Scenarios

ID Test Scenario Expected Results Comments
Total PO Net Value is
less then release
Release Strategy should strategy set value in
1 PO creation
be trigerred CL20n but gross value is
equal to or more then
set value in CL20n
Total PO Net Value is
less then release
Release Strategy should strategy set value in
2 PO changed via ME22n
be trigerred CL20n but gross value is
equal to or more then
set value in CL20n
Total PO Net Value is
less then release
Release Strategy should strategy set value in
3 PO changed via ME23n
be trigerred CL20n but gross value is
equal to or more then
set value in CL20n
Total PO Net Value is
less then release
Release Strategy should strategy set value in
4 PO changed via ME29n
be trigerred CL20n but gross value is
equal to or more then
set value in CL20n

3.2.2 Test System & Environment

Test System: ESB
Client: 900
Test Data :
Purchase Order 40008317, 40008316 & 40008318
Numbers

5|Page
 Functional
Specification

4. Technical Details
4.1 SAP Dictionary Used
Table Name Table Description Notes

4.2 SAP Standard Table Details

Table Name
Technical Type Length Field Name
Name

6|Page