Functional Specification

Project Name: BBX – S/4 Hana SAP Implementation

Process Area: Accounts Payables
Document GR notification to Account Payables
Name:
Document ID: GR notification to Account payables Version: V0
Prepared by: Manoj Raut Role MM Date: 10/28/2024
Consultant
Reviewed by: Role Module Lead Date:
Approved by: Role Project Date:
Manager
Released by: Role SD Date:
Consultant

Revision History

SR. VERSI DATE OF SECTION DESCRIPTION OF REASON FOR CHANGE REVIEWED BY

NO. ON CHANGE CHANGE MADE BY
REVISION NUMBER
NO.
1.0 V0 10/28/20 Initial Release
24

Page 1 of 15

826564745.docx
Table of contents
1 Development Summary........................................................4
2 Scope Summary...................................................................5
2.1 Business Background.................................................................................................................. 5
2.2 High Level Business Requirements............................................................................................. 5
2.3 Overview of Solution.................................................................................................................... 5
2.4 Assumptions................................................................................................................................ 5
3 Key Considerations..............................................................6
3.1 Open Issues................................................................................................................................. 6
3.2 Reference Programs.................................................................................................................... 6
3.3 Dependency on Other Development or Interface.........................................................................6
3.4 Development Objects (per System)............................................................................................. 6
4 Other considerations/Impacts..............................................7
4.1 Volume of Data............................................................................................................................ 7
4.2 Language Considerations............................................................................................................ 7
4.3 Cross module Impact................................................................................................................... 7
4.4 Others.......................................................................................................................................... 7
5 Development Scope.............................................................8
5.1 Reports........................................................................................................................................ 8
5.1.1 Selection Screen............................................................................................................................... 8
5.1.2 Processing Logic.............................................................................................................................. 8
5.1.3 Authorisations................................................................................................................................... 9
5.1.4 Output Format................................................................................................................................... 9
5.1.5 Output Medium............................................................................................................................... 10
5.1.6 Run Mode....................................................................................................................................... 10
5.1.7 Error Handling................................................................................................................................. 10
5.2 Outputs/Forms........................................................................................................................... 10
5.2.1 Business Logic for Data Retrieval...................................................................................................10
5.2.2 Triggering Mechanism....................................................................................................................10
5.2.3 Special Considerations...................................................................................................................11
5.2.4 Error Handling................................................................................................................................. 11
5.2.5 Printing Special Considerations......................................................................................................11
5.2.6 Authorizations................................................................................................................................. 11
5.3 Enhancements........................................................................................................................... 11
5.3.1 Associated SAP Transaction(s)......................................................................................................11
5.3.2 Input Data / Output Data.................................................................................................................11
5.3.3 Business Logic................................................................................................................................ 11

Page 2 of 15

826564745.docx
 5.3.4 Error Handling................................................................................................................................. 12
5.4 Function Module / RFC / BAPI................................................................................................... 12
5.4.1 Business Object.............................................................................................................................. 12
5.4.2 Input / Output Parameters..............................................................................................................12
5.4.3 Business Logic................................................................................................................................ 12
5.4.4 Authorisations................................................................................................................................. 12
5.4.5 Error Handling................................................................................................................................. 12
5.5 Data Dictionary Objects............................................................................................................. 12
5.5.1 Bespoke Table................................................................................................................................ 12
5.5.2 Search helps................................................................................................................................... 13
5.6 Workflow Development.............................................................................................................. 13
5.6.1 Configuration.................................................................................................................................. 13
5.6.2 Triggering Mechanism....................................................................................................................13
5.6.3 Authorisations................................................................................................................................. 14
5.6.4 Creation/Change of Workflow.........................................................................................................14
5.6.5 Workflow Business Logic................................................................................................................14
5.6.6 Action Agents / Responsable Person Determination Logic............................................................14
5.6.7 Error Handling................................................................................................................................. 14
5.7 Dialog program / Web Development ( Webdynpro) / Web UI)...................................................14
5.7.1 Screen Field and Layout Details.....................................................................................................14
5.7.2 Screen Sequence........................................................................................................................... 14
5.7.3 Business Logic................................................................................................................................ 14
5.7.4 Bespoke Tables Updated...............................................................................................................14
5.7.5 Authorisations................................................................................................................................. 14
5.7.6 Error Handling................................................................................................................................. 15
5.8 Portal Developments.................................................................................................................. 15
5.9 Unit Test information.................................................................................................................. 15
Disclaimer............................................................................... 16

Page 3 of 15

826564745.docx
1 Development Summary
10/28/2024
Development ID: Release
GR notification to Account payables team
Title :
Function Consultant : Manoj Raut Business Owner :

Comments :

Business Criticality: Medium Complexity : Medium

Type : Enhancement

Page 4 of 15

826564745.docx
2 Scope Summary
2.1 Business Background

Account payable team is receiving invoices from Suppliers for this they need to check if GR is posted
against Purchase orders. This is manual work and many times GR is not posted when is invoice is
received. So it causes inefficient way of working for Account payables team. Instead, proposal is to
work in reverse order. When GR is posted, a notification will be sent to A/P and they will check the
supplier invoice against the GR.

2.2 High Level Business Requirements

Business requirement here is to receive the auto notification as and when the GR is entered by the
procurement team for TPS Purchase Orders.

The notification should be sent to [email protected] for EMEA TPS Company Codes and for
US & Canada TPS - [email protected]

2.3 Overview of Solution

Create a new output type which should be triggered when GR is posted for againt a
TPS Purchase order. Here, transmission medium used will be 5 External send. Email
ID above will be stored in TVARVC table.

When GR is posted following mail should be sent.

Following is email subject and content of email.

Subject - A goods receipt for your purchase order’MSEG-EBELN’ & item ‘MSEG-EBELP’
has been entered.

 Purchase Order Number: ( MSEG-EBELN)

 Line item: [MSEG-EBELP]
 Vendor Name & Code: [LFA1-NAME1/LFA1-LIFNR]
 Goods Receipt Number: [MSEG-MBLNR]
 Goods Receipt Date: [MSEG- BUDAT_MKPF)
 Material: (MSEG-MATNR& &EKPO-TXZ01)
 Quantity Received:MSEG-ERFMG

Page 5 of 15

826564745.docx
2.4 Assumptions

N/A

Page 6 of 15

826564745.docx
3 Key Considerations

3.1 Open Issues

[Aim is to detail the key open issues/questions that the developers (or functional consultants) may need to
confirm/address prior to development]

Issue Owner Target Date Comments / Status

E.g. unresolved functional
questions

3.2 Reference Programs

N/A

3.3 Dependency on Other Development or Interface

N/A

3.4 Development Objects (per System)

[Please note this section can be filled with the help of technical consultant in case of prototyping
requirement.

S.No System Object Type Description

1 SAP S/4 Function module ME_PO_Confirm
Hana
2 SAP S/4 Bespoke table
Hana

Page 7 of 15

826564745.docx
4 Other considerations/Impacts
4.1 Volume of Data

N/A

4.2 Language Considerations

N/A

4.3 Cross module Impact

N/A

4.4 Others

N/A

5 Development Scope
Detailed Solution Description

5.1 EDI Interface

5.1.1 Mapping document

Page 8 of 15

826564745.docx
5.1.2 Processing Logic

5.1.3 Authorisations
N/A

5.1.4 Output Format

N/A

5.1.5 Output Medium

N/A

5.1.6 Run Mode

N/A

5.1.7 Error Handling

N/A

5.2 Outputs/Forms

5.2.1 Business Logic for Data Retrieval

5.2.2 Triggering Mechanism

N/A

5.2.3 Special Considerations

N/A

Page 9 of 15

826564745.docx
5.2.4 Error Handling

N/A

5.2.5 Printing Special Considerations

N/A

5.2.6 Authorizations

N/A

5.3 Enhancements
N/A

5.3.1 Associated SAP Transaction(s)

N/A

5.3.2 Input Data / Output Data

N/A

5.3.3 Business Logic

N/A

5.3.4 Error Handling

N/A

5.4 Function Module / RFC / BAPI

ME_PO_Confirm

Page 10 of 15

826564745.docx
5.4.1 Business Object

N/A

5.4.2 Input / Output Parameters

N/A

5.4.3 Business Logic

N/A

5.4.4 Authorisations
N/A

5.4.5 Error Handling

N/A

5.5 Data Dictionary Objects

N/A

5.5.1 Bespoke Table

5.5.1.1 Table Type

N/A

5.5.1.2 Number of Records

N/A

5.5.1.3 Field List

[Please mark the key fields with ‘X’ in ‘Key Field’ column]
S.No Field name Key Field Field Type Field Comments
Length

5.5.1.4 Table Maintenance

Page 11 of 15

826564745.docx
 N/A

5.5.1.5 Authorisations

N/A

5.5.2 Search helps

5.5.2.1 Data Source

N/A

5.5.2.2 Search Fields

N/A

5.5.2.3 Output and Selectable Fields

N/A

5.6 Workflow Development

5.6.1 Configuration

N/A

5.6.2 Triggering Mechanism

N/A

5.6.3 Authorisations

N/A

5.6.4 Creation/Change of Workflow

N/A

5.6.5 Workflow Business Logic

N/A

Page 12 of 15

826564745.docx
5.6.6 Action Agents / Responsable Person Determination Logic

N/A

5.6.7 Error Handling

N/A

5.7 Dialog program / Web Development (Webdynpro /

Web UI)
5.7.1 Screen Field and Layout Details

N/A

5.7.2 Screen Sequence

N/A

5.7.3 Business Logic

N/A

5.7.4 Bespoke Tables Updated

N/A

5.7.5 Authorisations

N/A

5.7.6 Error Handling

N/A

5.8 Portal Developments

N/A

5.9 Unit Test information

1) Create PO

Page 13 of 15

826564745.docx
 2) Update AB confirmation via PI interface.

Page 14 of 15

826564745.docx
Disclaimer
 Please note that the signing off of the document by BBX refers to
only the sections mentioned below. Duly signed off Supporting
documents to inputs shall be provided by the Process Owners.

2.1 Business Background

2.2 High Level Business Requirements
2.3 Overview of Solution
2.4 Assumptions
3.1 Open Issues
4.1 Volume of Data
4.2 Language Considerations
5.1.4 Output Format
5.2.1 Layout Details / Sample Formats
5.2.6 Printing Special Considerations
5.6.6 Action Agents / Responsable Person Détermination Logic

 Atos SMEs are accountable for overall Solutioning including RICEFW

developments

Page 15 of 15

826564745.docx