Functional Specification Document

Module: MM

Development Description: FMS – Get PO ELIGIBLE ITEMS (Inbound and

Outbound)

Get PO Eligible Items.

Document No.: FS_003_PO_ELIGIBLE_ITEMS

Version No.: V1.0

 Functional Specification Document – RETAIL
Document No: FS_003_Get PO Eligible Items Get PO Eligible Items.

Effective Date: 13.07.2018

Table of Contents

1.0 DOCUMENT HISTORY............................................................................................................................3

1.1 DOCUMENT VERSION..............................................................................................................................3
1.2 DOCUMENT APPROVAL / REVIEW DETAILS..................................................................................................3
1.1 REFERENCE DOCUMENT DETAILS...............................................................................................................3
1.2 ABBREVIATIONS USED (IF ANY).................................................................................................................3
1.3 DEFINITIONS USED (IF ANY).....................................................................................................................4
2.0 FUNCTIONAL SPECIFICATION................................................................................................................4
2.1 DEVELOPMENT SUMMARY.......................................................................................................................4
2.2 APPLICABILITY........................................................................................................................................5
2.3 OBJECTIVE OF THE DEVELOPMENT.............................................................................................................5
2.4 DEPENDENCIES AND CONSTRAINTS............................................................................................................6
2.5 ASSUMPTIONS AND NOTES.......................................................................................................................6
2.6 RELEVANT TRANSACTION CODES...............................................................................................................6
2.7 REFERENCE SAP PROGRAMS....................................................................................................................6
2.8 SELECTION PARAMETERS TO EXECUTE THE TRANSACTION / PROGRAM.............................................................6
2.9 OUTPUT LAYOUT (FOR REPORT, INTERFACE, ENHANCEMENT AND FORM ONLY)................................................6
2.10 ERROR HANDLING...................................................................................................................................7
2.11 USER EXIT/ENHANCEMENT......................................................................................................................7
2.12 BATCH SCHEDULE REQUIREMENT..............................................................................................................7
3.0 PROGRAM LOGIC / PSEUDO CODE / FIELD MAPPINGS.......................................................................8
3.1 AUTHORIZATION CHECK REQUIREMENT......................................................................................................9
3.2 OTHER SPECIAL REQUIREMENT (SUCH AS GRC REQUIREMENTS).....................................................................9
3.3 FUNCTIONAL VALIDATION REQUIREMENT (IF ANY).......................................................................................9
3.4 FLOW CHART (IF ANY).............................................................................................................................9
4.0 ATTACHMENTS & ANNEXURE...............................................................................................................9

Confidential Page 2 of 14
 Functional Specification Document – RETAIL
Document No: FS_003_Get PO Eligible Items Get PO Eligible Items.

1.0 Document History

Document Category Functional Specification Document
Document title FMS- Get PO Eligible Items.
Author Subhojit Banerjee
Lead Consultant

1.1 Document Version

Date Version Author Status - Description

13.07.2018 V1.0 Subhojit Banerjee Draft

1.2 Document Approval / Review Details

Function Name Department Sign & Date

Subhojit Banerjee MM
Prepared By

Reviewed By

1.1 Reference Document Details

Department /
Title of the Document Version No Organization Reference / Remarks

Confidential Page 3 of 14
 Functional Specification Document – RETAIL
Document No: FS_003_Get PO Eligible Items Get PO Eligible Items.

1.2 Abbreviations Used (If any)

Abbreviation Description

1.3 Definitions Used (If any)

Definitions Description

2.0 Functional Specification

2.1 Development Summary

Function Description
Development ID
Gap ID
Author Subhojit Banerjee
Name of Development FMS- PO Eligible Items Details
Short Description FMS- PO Eligible Items Details
Development Type (RICEFW) Interface
Module/Business Process Retail
Required Transaction Code ME23N
Complexity (L/M/H) M
Priority (L/M/H) M
Frequency Once a Day
Functional Consultant Subhojit Banerjee
Process Owner

Confidential Page 4 of 14
 Functional Specification Document – RETAIL
Document No: FS_003_Get PO Eligible Items Get PO Eligible Items.

2.2 Applicability
The process described in this document are applicable to the below mentioned entities / tracks.

Business Vertical Applicability

N
Water Vertical
N
Telecom Vertical
N
Anup Engineering
N
Textile Vertical
Y
Brands & Retail
N
Garment Export Division

2.3 Objective of the Development

Business Need:
The objective of this development is to initiate the information for the difference in quantity between PO
quantity, Inbound Delivery quantity and the goods receipt quantity once the API received from the
vendor portal into FMS. Vendor Portal will provide the ETA date and PO number based on these two
inputs the FMS system will provide the information to Vendor Portal.

Business Requirement:
Vendor Portal will trigger the API as an Inbound IDOC to SAP FMS system which contains the ETA date
and Purchase Order number. Based upon the request SAP FMS system will provide the information of the
Vendor PO eligible items as an Outbound IDOC to the Vendor Portal.

Objective:

Confidential Page 5 of 14
 Functional Specification Document – RETAIL
Document No: FS_003_Get PO Eligible Items Get PO Eligible Items.

Vendor Portal will trigger the API fetch the details from SAP FMS which is to be an Inbound IDOC for SAP
FMS system. In response SAP FMS system will provide the details to Vendor Portal through Outbound
IDOC.

2.4 Dependencies and Constraints

Dependencies:
 Partner Profile (WE20) & Distribution Model (BD64)
 Creation of extension basic type (WE30) & creation of message type (WE80)
2.5 Assumptions and Notes
 N/A
2.6 Relevant Transaction Codes
Transaction Code Description
Purchase Order
ME23N, ME22N, WPOHF4X

2.7 Reference SAP Programs

Program Name Description
ORDERS through WE80.
IDOC Message Type
FSHORD03 through WE30.
IDOC Basic Type

Confidential Page 6 of 14
 Functional Specification Document – RETAIL
Document No: FS_003_Get PO Eligible Items Get PO Eligible Items.

2.8 Selection Parameters to execute the Transaction / Program

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

2.9 Output Layout (For Report, Interface, Enhancement and Form only)
(Detail the output layout of the development)

2.10 Error Handling

 Error as part of the IDOC tracking.

* WE02: IDOC monitoring

* BD87: Status Monitor for ALE Messages

* WE05: IDoc Lists
* WE09: Search for IDoc in Database

 Outbound IDOC Error Tracking:

1. PO IDOC successfully processed
2. PO IDOC not processed
Outbound IDOC can be tracked through Status record.
Status can be identified through the Status Record Number.

Please find the list of status numbers.

01 Success Outbound IDoc 30 29    

created

02 Error Error passing data     Correct the error and

Confidential Page 7 of 14
 Functional Specification Document – RETAIL
Document No: FS_003_Get PO Eligible Items Get PO Eligible Items.

to port Execute RSEOUT00

program again

03 Success Outbound IDoc None,    

successfully sent 32
to port

04 Error within control in-      

formation on EDI
subsystem

05 Error during translation      

12 Success Dispatch OK   Changed from  

status 03 by
BD75 transaction
(see below)

25 Success Processing out-      

bound IDoc des-
pite syntax errors

26 Error during syntax   Missing mandat- You may edit the

check of outbound ory segment for IDoc or force it to be
IDoc example processed

29 Error ALE service (for ex- 29, 31    

ample

30 Success Outbound IDoc 03 02 Partner profile cus- Execute

ready for dispatch tomized to not run RSEOUT00 pro-
(ALE service) gram

31 Error no further pro-

cessing

32 Success Outbound IDoc   There was a  

was edited manual update
of the IDoc in
SAP tables, the
original was
saved to a new
IDoc with status
33

Confidential Page 8 of 14
 Functional Specification Document – RETAIL
Document No: FS_003_Get PO Eligible Items Get PO Eligible Items.

33 Success Original of an IDoc None None Backup of another  

which was edited. IDoc manually up-
It is not possible to dated, see status 32
post this IDoc

35 Success IDoc reloaded

from archive. Can't
be processed

37 Error Erroneous control None,    

record (for ex- 37
ample, "reference"
field should be
blank for out-
bound IDocs)

42 Success Outbound IDoc 01 37    

manually created
by WE19 test tool

50 Success Inbound IDoc cre- 64 65    

ated

51 Error inbound IDoc data 53, 64 51, 66, 68, 69 Error triggered by Ask functional
contains errors SAP application, in- people, modify
correct values in the erroneous values
IDoc data in the IDoc
(WE02 for ex-
ample) and run it
again using BD87

53 Success inbound IDoc pos- None,    

ted 53

56 Error IDoc with errors 50, 51,    

added (You should 56, 62,
never see this er- 68
ror code)

60 Error syntax check of in- 56, 61,    

bound IDoc 62

61 Error Processing in- 64    

bound IDoc des-

Confidential Page 9 of 14
 Functional Specification Document – RETAIL
Document No: FS_003_Get PO Eligible Items Get PO Eligible Items.

pite syntax error

62 Success inbound IDoc 53 51  

passed to applica-
tion

63 Error passing IDoc to ap-      

plication

64 Success Inbound IDoc 62 51, 60, 63, 68, 69   execute BD20

ready to be passed transaction (RBD-
to application APP01 program)

65 Error ALE service - incor- 64, 65    

rect partner pro-
files

66 Waiting Waiting for prede-   51

cessor IDoc (Serial-
ization)

68 Success no further pro- 68 None The IDoc was cre-  

cessing ated using inbound
test tool (WE19) and
written to file to do
file inbound test. An-
other IDoc is created
if immediate pro-
cessing is chosen

69 Success IDoc was edited 64 51, 68, 69 There was a manual  

update of the IDoc in
SAP tables, the ori-
ginal was saved to a
new IDoc with status
70

70 Success Original of an IDoc None None Backup of another  

which was edited. IDoc manually up-
It is not possible to dated, see status 69
post this IDoc

71 Success Inbound IDoc re-

loaded from

Confidential Page 10 of 14
 Functional Specification Document – RETAIL
Document No: FS_003_Get PO Eligible Items Get PO Eligible Items.

archive. Can't be
processed

74 Success Inbound IDoc 50, 56    

manually created
by WE19 test tool

2.11 User Exit/Enhancement

User Exit Name Component name Description

2.12 Batch Schedule Requirement

3.0 Program Logic / Pseudo Code / Field Mappings

Vendor Portal to SAP FMS (Inbound IDOC)

Vendor Portal trigger the API to SAP FMS as an Inbound IDOC as a request.

Inbound IDOC will contains two information.

1. ETA Date

2. Purchase Order

Structure for Inbound IDOC given below

Inbound IDOC Structure for VENDOR PO ELIGIBLE

ITEMS
TABL
TEXT FIELD
E
ETA DATE LIKP BEDAT
PURCHASE ORDER  EKKO EBELN
Confidential Page 11 of 14
 Functional Specification Document – RETAIL
Document No: FS_003_Get PO Eligible Items Get PO Eligible Items.

Below logic for fetching the details

Pass Purchase Order Number EKKO-EBELN into EKKO.

Pass Purchase Order Number EKPO-EBELN into EKET and get EKET-EINDT.

SAP FMS to Vendor Portal (Outbound IDOC)

SAP FMS will process the outbound Idoc open PO eligible items via Message Output Types in SAP.

In SAP, PO eligible items details IDOC will be configured to generate an IDOC with respective information via
message output types.

As per business requirement, IDOC can be processed on two ways – either through Manual push or
Automatic Push via Output Types for selective Vendor.

Before the IDOC is generated, following functions should be completed:

 One IDOC will be having multiple PO eligible line items.

Confidential Page 12 of 14
 Functional Specification Document – RETAIL
Document No: FS_003_Get PO Eligible Items Get PO Eligible Items.

Based on API, FMS system will give the real time data.

Outbound IDOC Structure for PO Eligible Items

TABL
TEXT FIELD
E
SERIAL_ID    
 EKK
PO_NUMBER EBELN
O
 EKP
PO_ITEM_NO EBELP
O
 EKP
MATERIAL_NUMBER MATNR
O
 EKP
MATERIAL _ DETAILS TXZ01
O
 EKP WRF_CHARSTC
GRID_VALUE
O 2
 EKP
EAN EAN11
O
 
EKPO
MENGE
LIPS
QUANTITY LFIMG
MSE
MENGE
G

Logic of each field is given below.

PO_NUMBER- Pass EKPO-EBELN

PO_ITEM_NO- Pass EKKO-EBELN into EKPO and EKPO-EBELP.

MATERIAL_NUMBER- Pass EKPO-EBELN and EKPO-EBELP into EKPO and EKPO-MATNR.

MATERIAL_DETAILS- Pass EKPO-EBELN and EKPO-MATNR into EKPO and get EKPO- TXZ01.

GRID_VALUE - Pass EKPO-EBELN and EKPO-MATNR into EKPO and get EKPO- WRF_CHARSTC2.

EAN- Pass EKPO-EBELN and EKPO-MATNR into EKPO and get EKPO-EAN11.

QUANTITY- PO Quantity – (ASN Quantity where GRN not done + GRN Quantity)

Confidential Page 13 of 14
 Functional Specification Document – RETAIL
Document No: FS_003_Get PO Eligible Items Get PO Eligible Items.

For getting PO quantity pass EKKO-EBELN into EKPO table and get EKPO-MENGE.

For getting ASN Quantity if GRN has not done should be considered then that quantity will not be considered.
Pass EKPO-EBELN and EKPO-EBELP into LIPS-VGBEL and get LIKP-VBELN. Then pass LIPS-VBELN and get LIPS-
LFIMG. Now checking whether GRN has been done for that ASN or not in that case pass LIKP-VBELN into MKPF-
XBLNR and get MKPF-MBLNR. Then pass MKPF-MBLNR into MSEG and get MSEG-MENGE.

If MSEG-MENGE is initial then consider full LIPS-LFIMG. If it is not initial then do not consider LIPS-LFIMG.
If MSEG-MENGE is partial then consider LIKPS-LFIMG - MSEG-MENGE quantity.

3.1 Authorization Check Requirement

(Detail the organization element and authorization object that involve in authorization check)
3.2 Other Special Requirement (such as GRC requirements)
(Detail any other special requirement of the specification)
N/A
3.3 Functional Validation Requirement (If any)
3.4 Flow Chart (If any)

4.0 Attachments & Annexure

NA

Confidential Page 14 of 14