0% found this document useful (0 votes)
44 views11 pages

SAP MM Invoice Receipt Functional Spec

The document outlines the functional design specifications for an Invoice Receipt Z* Interface in SAP MM, detailing the purpose, requirements, and processes involved in creating invoice receipts linked to purchase orders. It includes sections on functional description, input/output parameters, error handling, and testing requirements. The design aims to facilitate efficient processing and reporting of invoice receipts while ensuring data validation and error management.

Uploaded by

Karanpal Singh
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
44 views11 pages

SAP MM Invoice Receipt Functional Spec

The document outlines the functional design specifications for an Invoice Receipt Z* Interface in SAP MM, detailing the purpose, requirements, and processes involved in creating invoice receipts linked to purchase orders. It includes sections on functional description, input/output parameters, error handling, and testing requirements. The design aims to facilitate efficient processing and reporting of invoice receipts while ensuring data validation and error management.

Uploaded by

Karanpal Singh
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Functional Design Form RICEF_FS+Z-Interface-MM- Version: 1.

0
Invoice+Recipt
[Link]
Course Links:

Link1:[Link]
mm-ricefw-objects-functional-spec-
writing/[Link]

Link2:[Link]
sd-ricef-objects-and-development-with-
functional-specs/[Link]

Practice SAP ABAP-MM


Invoice receipt Z* Interface Functional Spec
Functional Design Documents Version: 1.0

Table of Contents

Functional Design ......................................................................................................................................... 3


Document Information ................................................................................................................................... 3
Document History .......................................................................................................................................... 3
Change Log ............................................................................................................................................... 3
Approval/Sign-off ....................................................................................................................................... 3
Overview and Scope ..................................................................................................................................... 4
Functional Description ............................................................................................................................... 4
Assumptions .............................................................................................................................................. 4
Detailed Functional Requirements ................................................................................................................ 4
Functional Specification ............................................................................................................................. 4
Process Flow Diagram .............................................................................................................................. 6
Extension Layout ....................................................................................................................................... 6
Input and Output ........................................................................................................................................ 6
Required SAP Transactions .................................................................................................................. 6
Input Parameters ................................................................................................................................... 6
Method to Retrieve Input Parameters .................................................................................................... 7
Output Parameters................................................................................................................................. 7
Method to Release Output Parameters (Output Type) .......................................................................... 7
Method to Update Existing Run Parameters with Latest Run Information ............................................ 8
Reporting ................................................................................................................................................... 8
Initial Data Set-Up/Conversion Requirements........................................................................................... 8
Existing Sample Program(s) ...................................................................................................................... 9
Process and Operational Considerations .................................................................................................. 9
Network Integration ................................................................................................................................ 9
Performance .......................................................................................................................................... 9
Processing Type .................................................................................................................................... 9
Re-use Details ....................................................................................................................................... 9
Expected Transaction Volumes ............................................................................................................. 9
Error Handling ........................................................................................................................................ 9
Security and Authorization ..................................................................................................................... 9
Purge and Archive Considerations ........................................................................................................ 9
Multi-company, Multi-jurisdiction Considerations .................................................................................. 9
Other ...................................................................................................................................................... 9
Change Management Requirements ........................................................................................................ 9
Testing Requirements ................................................................................................................................. 10
Functional Design Form RICEF_FS+Z-Interface-MM- Version: 1.0
Invoice+Recipt
[Link]
Course Links:

Link1:[Link]
mm-ricefw-objects-functional-spec-
writing/[Link]

Link2:[Link]
sd-ricef-objects-and-development-with-
functional-specs/[Link]

Key Business Test Conditions ................................................................................................................. 10


Technical Test Conditions ....................................................................................................................... 10
Testing Considerations/Dependencies .................................................................................................... 10
Outstanding Issues ..................................................................................................................................... 10
Appendix ..................................................................................................................................................... 11
Glossary of Terms ................................................................................................................................... 11
Additional Supporting/Reference Documentation ................................................................................... 11
Solution Review Board input ....................................................................................................................... 11
Functional Design Form RICEF_FS+Z-Interface-MM- Version: 1.0
Invoice+Recipt
[Link]
Course Links:

Link1:[Link]
mm-ricefw-objects-functional-spec-
writing/[Link]

Link2:[Link]
sd-ricef-objects-and-development-with-
functional-specs/[Link]

Functional Design

Document Information
Extension Name Invoice Receipt
Functional Area MM
Functional Designer Siva
Developer Ram

Document History
Change Log
Name Change Date Version

Approval/Sign-off
Name Role Date Signature
Functional Design Form RICEF_FS+Z-Interface-MM- Version: 1.0
Invoice+Recipt
[Link]
Course Links:

Link1:[Link]
mm-ricefw-objects-functional-spec-
writing/[Link]

Link2:[Link]
sd-ricef-objects-and-development-with-
functional-specs/[Link]

Overview and Scope


This document includes functional requirements and some implementation details. It is possible that
some implementation details might be adjusted in the technical design.

Functional Description
The purpose of this development is to create an invoice receipt reference to a purchase document
created during a period. This enables daily & weekly & monthly based on the Purchase Ordering
activities.

Additional requirements check when an exist IR exist an error to display that the “PO Line item already
exist”.

Provisions for downloading the success and error msg displayed in report and other ALV features are
some of the additional requirements from the report for ease of reporting and usage.

Processing within SAP

A custom transaction code, ZMM_MIRO, will be created and linked to an ABAP program
ZMM_MIRO_CRT_TRN to create an Invoice receipt posting reference to Purchase Orders during a
period.

Dependencies/Constraints

Assumptions

The volume of Purchase orders created and processed in each MIRO document was 6000+ considering
additional line items.

Detailed Functional Requirements


Functional Specification

Source

The source of Purchase Order data comes from different SAP tables extracted from another custom
transaction. The Output will contain Tax codes and data pertaining to multiple Purchase Order lines.

File specification:
Desktop Manual upload

SAP Process
Functional Design Form RICEF_FS+Z-Interface-MM- Version: 1.0
Invoice+Recipt
[Link]
Course Links:

Link1:[Link]
mm-ricefw-objects-functional-spec-
writing/[Link]

Link2:[Link]
sd-ricef-objects-and-development-with-
functional-specs/[Link]

The user logs on the SAP ECC 6.0 and calls the custom transaction ZMM_MIRO, which prompts the user
to enter flat file and after data validation and posting logs updated in output to be displayed.

This program will have the following fields in the selection screen:
• File Name: Input the Flat file name data to process.
Fields entered in selection screen are validated and any errors are reported and processing stopped.

Fields from the following need to be in the Flat file report in the following order:

Purchase order Company code Posting Date Currency Tax code


4500025352 ER00 20230402 GBP V0

Output of the Report: Header_ALV


[Link] 1
Functional Design Form RICEF_FS+Z-Interface-MM- Version: 1.0
Invoice+Recipt
[Link]
Course Links:

Link1:[Link]
mm-ricefw-objects-functional-spec-
writing/[Link]

Link2:[Link]
sd-ricef-objects-and-development-with-
functional-specs/[Link]

Message Detailed description


Status Success/Fail

Log

Process Flow Diagram


Invoice Receipt
PO Creation Goods Receipt (MIGO) ZMM_MIRO
Program

Output Success/Error Msg


Extension Layout
None required.

Input and Output


Required SAP Transactions

ZMM_MIRO_CRT_TRN & SE38.

Input Parameters
Functional Design Form RICEF_FS+Z-Interface-MM- Version: 1.0
Invoice+Recipt
[Link]
Course Links:

Link1:[Link]
mm-ricefw-objects-functional-spec-
writing/[Link]

Link2:[Link]
sd-ricef-objects-and-development-with-
functional-specs/[Link]

Input (Parameters) Needed Description and Prior Dependency Validation


Flat file (Optional) No flat file input at selection screen. Information msg:
WRONG
PARAMETER:
FILE_NAME
Flat file (Optional) Input Purchase order in FF which Goods Error msg: Enter
receipt not completed. goods receipt data
only when working
with GR-based IV
Flat file (Optional) Input Purchase order in FF which Goods Success msg: PO
receipt is completed. invoice document
has been updated
successfully.
Flat file (Optional) Input Purchase order in FF which Goods Error msg: PO xx
receipt & Invoice receipt already processed. PO line
item_xx_xx_already
exist.

Method to Retrieve Input Parameters

Output Parameters

Output (Parameters) Needed Description and Post Dependency


Screen output of report None
ALV report of line item display. None
Download report contents to None
presentation server

Method to Release Output Parameters (Output Type)


Program log may be printed or downloaded to file using standard SAP menu:
Functional Design Form RICEF_FS+Z-Interface-MM- Version: 1.0
Invoice+Recipt
[Link]
Course Links:

Link1:[Link]
mm-ricefw-objects-functional-spec-
writing/[Link]

Link2:[Link]
sd-ricef-objects-and-development-with-
functional-specs/[Link]

Method to Update Existing Run Parameters with Latest Run Information

The program log should be examined to ensure that the right Orders get displayed in the report. For
further details, please see the ‘Error Handling’ section.

Reporting
Report and post Invoice receipts reference to Purchase Order, Company code, Posting date and Tax
code details as a inputs, an option to navigate to post MIRO (Invoice receipt)..

Initial Data Set-Up/Conversion Requirements


No data conversion requirements.
Functional Design Form RICEF_FS+Z-Interface-MM- Version: 1.0
Invoice+Recipt
[Link]
Course Links:

Link1:[Link]
mm-ricefw-objects-functional-spec-
writing/[Link]

Link2:[Link]
sd-ricef-objects-and-development-with-
functional-specs/[Link]

Existing Sample Program(s)


No sample program available.

Process and Operational Considerations


Network Integration
No network integration considerations.

Performance
Performance is dependent on the number of records retrieved. Foreground processing of the report
should not exceed time out setting for online processing. Report can also be run in background.

Processing Type
Foreground & Background processing should be possible.

Re-use Details
Rerun the program for the same selection.

Expected Transaction Volumes

This will vary based on the number of Orders created for the processing period.

Error Handling

In case of errors, rerun the program for the same selection.

Security and Authorization

The transaction code should be featured in the same authorization profiles as Report transaction, SE38.

Purge and Archive Considerations

Multi-company, Multi-jurisdiction Considerations

Other

Change Management Requirements

Range of use
Functional Design Form RICEF_FS+Z-Interface-MM- Version: 1.0
Invoice+Recipt
[Link]
Course Links:

Link1:[Link]
mm-ricefw-objects-functional-spec-
writing/[Link]

Link2:[Link]
sd-ricef-objects-and-development-with-
functional-specs/[Link]

Number of Line items

There is no limit to the number of line items that can be present in an Order and displayed in report
output.

Testing Requirements
Key Business Test Conditions

ID Condition Expected results Actual


Result
1 Input field validations for all fields Input field validation is done and
standard field validation errors
handled.
2 Msg list displayed. Check fields displayed in output after
data validation.
3 Error with program execution Rerun the program for the same
selection.

Technical Test Conditions

ID Condition Expected results Actual


Result

Testing Considerations/Dependencies

Outstanding Issues
Issue Description Assigned To Status Impact Resolution
No
Functional Design Form RICEF_FS+Z-Interface-MM- Version: 1.0
Invoice+Recipt
[Link]
Course Links:

Link1:[Link]
mm-ricefw-objects-functional-spec-
writing/[Link]

Link2:[Link]
sd-ricef-objects-and-development-with-
functional-specs/[Link]

Appendix
Glossary of Terms
Term Definition

Additional Supporting/Reference Documentation

Solution Review Board input


Input Comments
Technical Details This document contains functional requirements and some technical
implementation details. These implementation details are subject to
change in the technical design.
Estimate An estimate of work effort needs to be included in the technical
design. The design of this solution should be kept technical simple
and we should encourage users to minimize the use of the upload
process.

You might also like