FS For Purchase Order Output

FSTS_O2I_FRM_Invoice _ ZO2ISF_225_INVOICE_NL
FS_TS FSTS_O2I_FRM_ MMPO _ ZO2ISF_225_ MMPO_NL

REFERENCE
FRICE REF./CCB / Gap ID :

INCIDENT REF
DOCUMENT ORIGIN
AUTHOR DATE
Vaishnavi – MM 07/08/2015
07/08/2015
VERSION CONTROL AND CHANGE HISTORY
VERSION REVISION AUTHOR SUMMARY OF CHANGES (to include

DATE FRICE/ CCB /incident reference)
1.0 21/01/2022 vaishnavi
REVIEW AND APPROVAL – ACCEPTANCE AND APPROVAL LOG

(This deliverable requires review and approval from the following individuals)
NAME ROLE DATE ACCEPT Email contact

ED (Y/N)
Originator/
User
BA
BSM
RGL
INTRODUCTION AND PURPOSE

This document will define the business requirements and how they will be supported within SAP.
This specification will be used to direct the technical team to build both custom requirements
and any formally approved functional specifications used to verify the test phase and user
acceptance testing.
Page 1 of: 23
TABLE OF CONTENTS
1. Business Process overview 3
2. Requirement 3
3. Assumptions 3
4. Dependencies and Constraints 3
5. Functional Overview 4
5.1. Report / Program / Transaction / Form Name: 4
5.2. Affected Application Areas 4
5.3. Detailed Functional Logic 4
5.4. Standard/Alternative Options considered 4
5.5. Selection/ Layout Criteria 4
5.5.1. Report Selection screen Criteria 4
5.5.2. Custom Table involved in report generation 4
5.5.3. Report /Form Layout Criteria 4
6. Security and Authorizations 6
6.1. Authorisation objects 6
6.2. Roles to be updated with new transaction codes 6
7. Technical Specification 7
7.1. Development Attributes 7
7.2. Function Modules 7
7.3. User Exits 8
7.4. SAP Database tables 8
7.5. Custom Table definition (if any) 8
7.6. External files used 8
7.7. Processing Logic 8
7.7.1. Process (overview) 8
7.7.2. Processing Flow Diagram 8
7.7.3. Selection Screen – Input fields 9
7.7.4. Implemented Layout and Design: 9
7.7.4.1. Print Program and Form Details 9
7.7.4.2. Form Layout Details 9
7.7.4.3. Layout Field Details 10
7.7.4.4. Form Layout diagram 10
7.7.5. Output Field Details 10
8. Security and Authorizations (Technical) 10
9. Error handling/Validations 11
10. Testing Requirements 11
10.1. Positive Test Cases 11
10.2. Negative Test Cases 11
11. Additional Information/Appendix ( if any) 11
Page 2 of: 23
Page 3 of: 23
1. Business Process overview
We require a form that can be used to send purchase order documents to our Netherlands vendor.
Each time a purchase order is created, an output record will be generated to print the purchase
order document. It is the output record that is required in the specified print formats defined
within this document.
.
2. Requirement
The Purchase Order Document is required to ensure the vendor to be aware of the goods that
need to be delivered to company and thus ensure the delivery of good in time.
1. The Purchase Document is required to have the PO order number, date, company address,
vendor address, currency, materials, price per unit total value of the purchase Order.
.
3. Assumptions
Sr.No. Description
A1 Purchase Order are printed locally by ABInBev in NL.
A2 NL will provide pre-printed and ABInBev logo stationery for all
Purchase documents.
A3 Vendor and company address details will be formatted to a uniform
format in SAP.
A4 The Purchase Order Number and terms of payment is required on the
Purchase document for NL.
A4 Contact details of vendor are required for NL
A4 The agreed transmission medium for NL Purchase document is Print.
A7 The program will format the address fields and remove any blank
fields from the Purchase Order Document
A8 There is no requirement to display times on the Purchase order
document; just the dates will be required.
A9 There is no requirement for colour print, black and white is sufficient.
A10 The SAP standard program SAPFM06P (Print program for purchase
order) will be copied and modified to meet BEIG requirements).
Page 4 of: 23
4. Dependencies and Constraints
Sr.No. Description
D1 The configuration entries must be maintained for each purchase order
that requires output for purchase order document print.
D2 The master data for the output record must be maintained via
transaction NACR (Create Output – Condition Records: purchase).
5. Functional Overview
In Netherlands, the vendor is to be aware of the goods that must be delivered to company. This
form will be printed and sent out to the vendors.
.
Transaction Volume
There are approximately 50 Purchase Order documents created each day in Netherlands, this
figure includes all the special procurement purchase orders.
Frequency and Timing
There are approximately 50 Purchase documents sent each day in Netherlands, this figure
includes figure includes all the special procurement purchase orders.
The Purchase Order document is required to ensure the vendor to be aware of goods and its
value that must be delivered to the company on the agreed delivery date.
Processing Type
Online
Form format (Online/Printout/Sheet)
In Netherlands, this form will be printed and sent out to the Vendor.
Page 5 of: 23
6. Report / Program / Transaction / Form Name:
7. Affected Application Areas
SAP Module Impact

Material Management Purchase Order output
External System ID Impact
8. Detailed Functional Logic
SAP Form Details

Description Values
Sap Transaction Name and its Menu ME21N
Path
Output Type ZEML
Program Name (Standard/Custom) SAPFM06P
Layout Form Name (Standard/Custom)
/SMB40/MMPO_NL
IMG path to access output type and SPRO->Material Management->
layout set assignment Purchasing -> Message -> Output
Control->Message Types->Define
Message Type for Purchase Order
Type of solution (Standard R/3, custom Standard R/3

ABAP)
Type of printer
Paper Size A4
Orientation: Portrait/Landscape Portrait
Special stationery to be used Pre-printed with logo. This
stationery should be used when print
layout
Language of Form output The language requirements do differ
for each country.
Form Layout
This section contains a document with attachment that detail the layout of the Purchase Order
document summary. This document also contains the SAP field values and the logic required by
Page 6 of: 23
the developer, so that the Purchase Order document Summary can be delivered. In all cases the
form layout will be portrait and the paper size will be A4.
Layout Detail
Position of Left Margin 0,44 CM
(Specify Unit)
Position of Right Margin 29,13 CM
(Specify Unit))
Position of Top Margin 0,37 CM
(Specify Unit)
Position of Bottom Margin 20,41 CM
(Specify Unit)
Logo To be used <Y/N>
Logo Position and <Include location of bitmap file (.bmp, .tif, .pcx) or standard text ID.>
occurrence
Footer detail Eg. <Page number/signature etc.>
Fields (Data Mapping Table) (FO + TO)

SAP Field Mappings and Logic for program
ID Description Field Logic Print- Font

of on- and
field Page Font
for Size
m
Label 1 PO Number EKKO -EBELN From the Run Time pick the EKKO-EBELN and All Arial
display it in this field pages 10
Label 2 Date EKKO -AEDAT Pass the PO number to EKKO_EBELN and fetch All Arial
the EKKO_AEDAT value and display in this field pages 10
Label 3 Telephone EKKO-TELF1 Pass the PO number to EKKO_EBELN and fetch All Arial
the EKKO_TELF1 value and display in this field pages 10
Label 4 Domestic Purchase Domestic hard copied All Arial

purchase pages 10
Label 5 Company EKKO-ANRED Pass the PO number to EKKO-EBELN and fetch All Arial
the EKKO-LIFNR and pass the value to LFA1- pages 10
LIFNR and fetch the LFA1-ANRED and display it
in the field
Label 6 Name EKKO-NAME1 Pass the PO number to EKKO-EBELN and fetch All Arial
LIFNR and fetch the LFA1-NAME1 and display in
the field
Label 7 Street Address EKKO-STRAS Pass the PO number to EKKO-EBELN and fetch All Arial
LIFNR and fetch the LFA1-STRAS and display in
the field
Label 8 City, Region, Postal EKKO-ORT01, Pass the PO number to EKKO-EBELN and fetch All Arial
Code EKKO-REGIO, the EKKO-LIFNR and pass the value to LFA1- pages 10
EKKO-PSTLZ LIFNR and fetch the LFA1-ORT01, LFA1-REGIO,
LFA1-PSTLZ and display in the field. Values to be
concatenated.
Page 7 of: 23
Label 9 Vendor Number EKKO-LIFNR Pass the PO number to EKKO-EBELN and fetch All Arial
the EKKO-LIFNR. Remove preceding zeros. pages 10
Label 10 Please Deliver to: Deliver to hard copied All Arial

pages 10
Label 11 Plant Name1 T001W-WERKS Pass the PO number to EKPO-EBELN and fetch All Arial
the EKPO-WERKS and pass the value to T001W- pages 10
WERKS and fetch the T001W-NAME1 and display
it in the field
Label 12 Plant Name2 T001W-NAME Pass the PO number to EKPO-EBELN and fetch All Arial
WERKS and fetch the T001W-NAME2 and display
it in the field
Label 13 address T001W-STRAS Pass the PO number to EKPO-EBELN and fetch All Arial
WERKS and fetch the T001W-STRAS and display
it in the field
Label 14 Region, Postal code T001W-REGIO, Pass the PO number to EKPO-EBELN and fetch All Arial
T001W-PSTLZ the EKPO-WERKS and pass the value to T001W- pages 10
WERKS and fetch the T001W-REGIO,T001W-
PSTLZ and display it in the field. Values to be
concatenated.
Label 15 Terms of payment Terms of hard copied All Arial

payment: pages 10
Label 16 Terms of payment EKKO-ZTERM Pass the PO number to EKKO_EBELN and fetch All Arial
the EKKO_ZTERM value and display in this field pages 10
beside terms of payment hard coded
Label 16 Currency: Currency hard copied All Arial

pages 10
Label 17 Currency: EKKO-WAERS Pass the PO number to EKKO_EBELN and fetch All Arial
the EKKO_WAERS value and display in this field pages 10
beside currency hard coded on the left side of the
PDF
Label 18 item order EKPO-EBELP Pass the PO number to EKPO_EBELN and fetch All Arial
the EKPO_EBELP value and display in this field pages 10
below item hard coded in the next line
Label 19 material EKPO-MATNR Pass the PO number to EKPO_EBELN and fetch All Arial
the EKPO_MATNR value and display in this field pages 10
below material hard coded
Label 20 description MAKT-MAKTX Pass the PO number to EKPO_EBELN and fetch All Arial
the EKPO_MATNR value and pass to MAKT- pages 10
MATNR and fetch the MAKT-MAKTX value and
display in this field below description hard coded
Label 21 unit EKPO-MEINS Pass the PO number to EKPO_EBELN and fetch All Arial
the EKPO_MEINS value and display in this field pages 10
below unit hard coded
Label 22 Quantity EKPO-MENGE Pass the PO number to EKPO_EBELN and fetch All Arial
the EKPO_MENGE value and display in this field pages 10
below quantity hard coded
Label 23 price per unit EKPO-NETPR Pass the PO number to EKPO_EBELN and fetch All Arial
the EKPO_NETPR value and display in this field pages 10
below Price per unit hard coded
Page 8 of: 23
Label 24 net value EKPO-NETWR Pass the PO number to EKPO_EBELN and fetch All Arial
the EKPO_NETWR value and display in this field pages 10
below net value hard coded
Label 25 Total Net Value Total hard copied All Arial

pages 10
Label 26 Total Net Value EKKO-RLWRT Pass the PO number to EKKO_EBELN and fetch All Arial
the EKKO-RLWRT value and display in this field pages 10
beside total Net Value:
Name and Address of the vendor.
The information box on the left side should be used to print the information of
(Purchase order Number / Date / Contact person
Title – Domestic Purchase must be displayed.
The vendor number with us: EKKO-LIFNR
The address to which the good must be delivered.
The payment terms with the currency should be entered.

Transactional Line items:
Get all the item data from the DB table EKPO based on PO number (EBELN).
The different columns required are:
Item No: get the value form EKPO_EBELP
Material: get the value form EKPO_MATNR
Description: get the value from MAKT-MAKTX
Order Qty: get the value from EKPO_MENGE
Price per Unit: get the value from EKPO_NETPR
Net Value: get the value from EKPO_NETWR
Total Net Value: get the value form EKKO-RLWRT
Please see Excel document “MMPO_MESSAGES”:

Tab “SAMPLE” has the purchase order summary format, and Tab “LOGIC” for the purchase
order documents logic details.
9. Standard/Alternative Options considered NA
10. Selection/ Layout Criteria NA
11. Report Selection screen Criteria
Sr. Field Text on Selection Table and Mandatory Default

Page 9 of: 23
No Screen Field Name (Y/N) Value

12. Custom Table involved in report generation
Sr. Field Description Field Table

No Names Name Remarks

13. Report /Form Layout Criteria
Sr. Field Table Total/ Sub Total

No Field Text on layout Names Name field

Model for Standard Form / Output

If this form is a copy of the standard form or is a template from the legacy system, please
insert a screenshot or copy here. Enter the name of the standard form, the corresponding
path in Customizing and the transaction in the SAP System below.
Name of standard form :

Path in Customizing :
SAP Transaction Code :
SAP Standard Print Program :
Existing / Sample Reports

(This sub-section provides complete details of the report name, the transaction or menu
being affected. The program name indicates whether modification or copy made to the
existing program)
SAP Program Name :
SAP Menu / Transaction :
Page 10 of: 23
Legacy Report Name / Title : If Applicable
Related SAP Transaction(s) : If Applicable
14. External file Format
File Name File Description Usage
External File Layout

Field Name Key Declaration Description
15. Security and Authorizations
Is a new transaction code required? Yes No ☒

If yes, please complete roles required ☐
For new transactions: Yes No

Is a new authorisation object required? ☐ ☐
For both yes and no please indicate which kind of authorisations will be
used in authority check
For new Table maintenance transactions: Yes No
Is a new authorisation group required for S_TABU_DIS? ☐ ☐
For both yes and no please indicate which type of authorisation group is
to be used
16. Authorisation objects
Sr.No. Description
1.
2.
3
17. Roles to be updated with new transaction codes
Business Roles to be changed: Master role to be Derived roles to be

(List Master and Derived roles) updated updated
Support Roles to be updated:
Page 11 of: 23
18. Technical Specification
19. Development Attributes
Object ID :
Object Name ZO2ISF_225_INVOICE_NL
Title Invoice
Description
Development Class ZO2I
Message Class
Program Type
Program
Location/Server
Development Type Smartforms
Processing Type E.g. foreground
Frequency
Output Type
Application Area SAP System components
Report ☐ Drilldown ☐ Buttons ☐ Sort
Characteristics
☐ Entry file ☐ Others:
Report Created ☐ Report Painter ☐ Report Writer ☐ SAP Query
using
☒ ABAP program ☐ Info system
☐ BW ☐ Crystal Reports
Page 12 of: 23
20. Function Modules
Function module Func. Application Description

Name Group Area (Short text, expected usage, import &
export parameters)
21. User Exits NA
Type of User Exit : Screen/ Menu / User Type/BADI (Not Applicable)

Related SAP Transaction(s) : Not Applicable
SAP/Customer Enhancement : Not Applicable
22. SAP Database tables
S.No Table Name Description Remark
23. Custom Table definition (if any)
S.No Table Name Field Name Description Remark
24. Processing Logic
25. Process (overview)
26. Processing Flow Diagram
Page 13 of: 23
27. Selection Screen – Input fields NA
Field name Field description Single/ Mandatory Default

Range/ (Y/N) value
Check box /
Radio
button
NA - - - -
28. Layout and Design:
29. Print Program and Form Details

SAP Print SAP Menu / Mode of SAP Form New Print New Form
Program Transactio execution Form Routine Program Layout /
Name n Layout / program Name Smart form
Smart name name
form
name
RVADOR01 VA01/VA02/
VA03
RLB_INVOI
CE VF01 Online
Styles and Standard texts

Style name Style description Standard Paragraph Character format
settings format
ZO2ISS_226_ SmartStyle for Invoice 226 Standard
INVOICE_ST Paragraph -
YLE_BEL T3, Tab Stop
- 1 CM
Characters
per Inc - 10,
Lines per
Inch - 6,
Font -
Courier, Font
style - 11pt
Paragrap Description Indents and spacing Font Tabs Numberin

h Format g and
outline
A1 For Additional Alignment - Left- Helve - 08
information Aligned pt
Left Margin - 0,10 CM
Right Margin - 0,00 CM
Indent First Line 0,00
Page 14 of: 23
CM
Space before -0,10 CM
Space after - 0,00 CM
Line Spacing -0,75 LN
C Centered Alignment- Centred Helve - 08
Remaining all Default Pt Bold
Character Description Standard settings Font

format
AR Arial Arial 10 pt
B Bold Bold
T1 Title Helve 12 pt Bold
T2 Character T2 Arial 12 pt Bold
30. Form Layout Details
Form Layout ZO2ISF_226_INVOICE_BE

Description Invoice
Page Size
Orientation
Default Font Size 10,00
Pre-printed
stationary
Language The language requirements do differ for each country.
Printer Specification
Pre-Printed
stationary (yes/No)
Number of copies
per print
Transmission Printer
medium
Legal Requirements
31. Layout Field Details
SAP Field Mappings and Logic for program
● The user enters the values for the fields in the selection screen of the transaction VF01.
On submitting, the print program RLB_INVOICE program is called.
Page 15 of: 23
● The program checks if the document type entered is Invoice, Credit memo, Debit memo
or Cancellation document for the selected customer, and depending on that particular
billing Document type the program calls the form and displays the particular data.
● In the driver program call the function module

CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
EXPORTING
FORMNAME = '<form name>'
IMPORTING
FM_NAME = fm_name
EXCEPTIONS
NO_FORM = 1
NO_FUNCTION_MODULE = 2
OTHERS = 3.
The logic for populating the Different Windows is explained in detail below:
S. Window Field Font– SAP/ Logic for Additional

No Name Length Reference obtaining Information
eg. Arial Field Name Field Value
(10)
1 Page Secondary
Window/New
2 IGLO_BELG
Secondary
Window/New
3 HEADER Secondary
Window/New
4 SHIP_TO_ADDR Secondary
ESS Window/New
5 PAYER Secondary
Window/New
6 DUE_DATE Secondary
Window/New
7 FREE_TEXT Secondary
Window/New
8 MAIN MAIN
9 RATE_TAXABLE Secondary
_AMOUNTTAX Window/New
10 CASES_KG Secondary
Window/New
11 NET_VAT_AMO Secondary
UNTPAYABLE Window/New
12 FOOTER_WIND Secondary
OW Window/New
● Title of Form: Invoice / Credit Note / Debit Note / Cancellation of Invoice

● Global Definitions Node:
Since only one form is used for three different Countries and it will be displayed based on
the Language Key (KNA1-SPRAS).
● Header Window:
Page 16 of: 23
For Invoice the title of the window should be Invoice, for Credit memo it should be Credit
Note, for Debit memo it should be Debit Note and for Cancellation it should be as
Cancellation Of ... and in this place the origin of cancellation should be replaced mean if it is
cancellation of invoice then it should be Cancellation of Invoice.
IF IS_BIL_INVOICE-HD_GEN-BIL_CAT = 'P'.
TITLE = 'Anzahlungsanforderung'.
ELSE.
CASE IS_BIL_INVOICE-HD_GEN-BIL_VBTYPE.
When 'M'.
TITLE = 'Invoice'.
When 'P'.
TITLE = 'Debit Memo'.
When 'O'.
TITLE = 'Credit Memo'.
When 'N'.
TITLE = 'Cancellation of Invoice'.

Endcase.
This part will contain the details of the Invoice Number, date, and more such as purchase order
etc.
The last field is only to be populated when the billing document type is = N (Cancellation
Invoice). For all other document types this is a blank field.
This window is needed to be framed within a box.
Font Size /
Field Description Field name Referring Structure Field Alignment
Title(Invoice/Debit
note/Credit Helve 12pt
note/Cancellation of Standard Left-
invoice) Text Logic required Alignment
VBRK-
VBELN/ Is_bil_invoice-HD_GEN- Helve 8pt
VBRK- BIL_NUMBER / Is_bil_invoice- Left-
Invoice number/date FKDAT HD_GEN-BIL_DATE Alignment
VBAK-
BSTNK is_bil_invoice-HD_REF- Helve 8pt
Purchase order VBAK- PURCH_NO / is_bil_invoice- Left-
number/date BSTDK HD_REF-PURCH_DATE Alignment
VBAK-
VBELN IS_BIL_INVOICE-HD_REF- Helve 8pt
VBAK- ORDER_NUMB / IS_BIL_INVOICE- Left-
Sales order number/date AUDAT HD_REF-ORDER_DATE Alignment
LIKP-
VBELN Helve 8pt
LIKP- Left-
Delivery number/date LFDAT Alignment
Page 17 of: 23
Helve 8pt
VBRK- Left-
Currency WAERK is_bil_invoice-HD_GEN-BIL_WAERK Alignment
Helve 8pt
Left-
Cancellatin doc refer to is_bil_invoice-HD_GEN-KIDNO Alignment
● Page Number Window:
For Belgium the page numbering will be displayed as Page 1 of 1, Page 1 of 2, Page 2 of 2
ect. For France the page numbering will be displayed as Numéro de page 1 De 1, Numéro de
page 1 De 2, Numéro de page 1 De 2 etc.
For Netherlands the page numbering will be displayed as Het Aantal van de pagina 1 Van 1,
Het Aantal van de pagina 1 Van 1, Het Aantal van de pagina 1 Van 2 etc.
Use the following system fields for from and to. (FROM)&SFSY-PAGE&, (TO) &SFSY-
JOBPAGES&
● Address Window:
Iglo Belgium SA /
NV
● Ship to Address Window:

For France the Ship to must be displayed as Bateau: For Netherlands the Ship to must be
displayed as Schip:
Select the following fields from KNA1 table for the importing parameter VBRK-VBELN
and KNA1-PARVW = WE in the where clause.
Field Name
NAME1
NAME2
STRAS
ORT01
PSTLZ
Or use the following logic.
Using the Billing Document number (VBRK-VBELN), go to the table (VBPA). Find the
entries for the Billing document number (VBPA-VBELN). Using the field (VBPA-PARVW)
find the entry for the value 'WE' and retrieve the partner number held in (VBPA-KUNNR).
Finally go to table (KNA1) and retrieve the following field for the address: KNA1-NAME1,
KNA1-NAME2, KNA1-STRAS, KNA1-ORT01 and KNA1-PSTLZ.
Ship to number: GS_HD_ADR-PARTN_NUMB
VAT Number: Kna1-stceg
Page 18 of: 23
● Payer Address Window:

For France the Ship to must be displayed as Adresse de débiteur : For Netherlands the Ship
to must be displayed as Het Adres van de betaler:
Select the following fields from KNA1 table for the importing parameter VBRK-VBELN
and KNA1-PARVW = RG in the where clause.
Field Name
NAME1
NAME2
STRAS
ORT01
PSTLZ
Or use the following logic.
Using the Billing Document number (VBRK-VBELN), go to the table (VBPA). Find the
entries for the Billing document number (VBPA-VBELN). Using the field (VBPA-PARVW)
find the entry for the value 'RG' and retrieve the partner number held in (VBPA-KUNNR).
Finally go to table (KNA1) and retrieve the following field for the address: KNA1-NAME1,
KNA1-NAME2, KNA1-STRAS, KNA1-ORT01 and KNA1-PSTLZ.
Bill to number: GS_HD_ADR-PARTN_NUMB
Due Date: BSEG-ZFBDT (Referring Structure field IS_BIL_INVOICE-
HD_GEN_DESCRIPT-ZFBDT)
Additional Information: Free Text will be displayed for those create include text in which
mention required fields like
Text Name - V_BIL_NO
Text object - VBBK
Text ID - 002
Language - EN and write the logic v_bil_no = is_bil_invoice-hd_gen-bil_number.
Invoice line Items data window:
It's a main window, and comprises of billing document item data.
Referring Font Size/
Item Name Field Name Structure Field Alignment
EAN Customer GS_IT_GEN_W- Helve 8 pt
Unit VBRP-EAN11 EAN_UPC Centred
EAN Consumer Helve 8 pt
Unit ? Inputs Required Centred
Material GS_IT_GEN_W- Helve 8 pt
Number VBRP-MATNR MATERIAL Centred
GS_IT_GEN_W- Helve 8 pt Left-
Description VBRP-ARKTX SHORT_TEXT Alignment
GS_IT_GEN_W- Helve 8 pt Right-
Quantity VBRP-FKIMG FKIMG Alignment
Weight/ GS_IT_GEN_W- Helve 8 pt Right-
Consumer Unit VBAP-BRGEW GROSS_WT Alignment
CUs within Helve 8 pt Right-
Customer Unit ? Inputs Required Alignment
Net Weight VBRP-NTGEW GS_IT_GEN_W- Helve 8 pt Right-
Page 19 of: 23
NET_WEIGHT Alignment
GS_IT_KOND_W- Helve 8 pt Right-
Unit Price VBRP-NETWR KBETR Alignment
Discount per Helve 8 pt Right-
unit1 ? Inputs Required Alignment
Refers to SAP Field Mappings GS_IT_PRICE- Helve 8 pt Right-
Net Amount and Logic for program NETWR Alignment
Refers to SAP Field Mappings GS_IT_PRICE- Helve 8 pt
VAT and Logic for program MWSBP Centred
Calculate the Vat in Percentage i.e GS_IT_PRICE-MWSBP * 100 / GS_IT_PRICE-

NETWR.
Taxable Amount:
This field is a sum of the following: Add together each (VBRP-NETWR) on the billing
document lines, where the VAT Code (VBRP-TAXM1) = 0.
Amount Tax:
This field is a sum of the following: Add together each (VBRP-MWSBP) on the billing
document lines, where the VAT Code (VBRP-TAXM1) = 1.
Cases & KGs Window:
Calculate total item quantities based on unit of measure (i.e. cases)

Calculate the total net weight of the ordered goods using the quantity ordered multiplied
by the
Values found in the net weight column.
● Net Value:
This field is a sum of the following: Add together each (VBRP-NETWR) on the billing
document lines, where the VAT Code (VBRP-TAXM1) = 0 (Nothing but Taxable Amount).
● VAT:
This field is a sum of the following: Add together each (VBRP-MWSBP) on the billing
document lines, where the VAT Code (VBRP-TAXM1) = 1 (Nothing but Taxable Amount
Tax).
● AMOUNT PAYABLE:
Add Net Value and VAT.
Display the standard text in a separate template.

Footer Window:
This template is used to display the standard text comprising of the details of Payment to.
A box is drawn around the whole standard text details.
Page 20 of: 23
This transaction is subject to the Terms and Conditions of Sale overleaf

Payment to:
According CCB address changes are made to address window of the Smart form as shown
below:
32. Form Layout diagram
33. Output Field Details NA

<This sub-section to provide all output fields details built for the report)
Sorting:
Totalling:
Page Break requirement:
34. Security and Authorizations (Technical)
Authorisation Object have the following values:

Transaction Programme Authorisation Field Value
code code Object
Has SU24 been updated with t-code and Authorisation objects Yes No
☐ ☐
Change Order numbers:
Have Business and Support roles been changed? Yes No
☐ ☐
Change Order numbers:
Page 21 of: 23
35. Error handling/Validations NA
Screen / Report / Error Condition Error Remarks

Form Result/Message
36. Testing Requirements
Related Business Scenario and Business Transaction
Identify the business scenario and business transactions this development will be tested with.
37. Positive Test Cases

Test Case Test Case Expected Result Actual Result
Description
1 Enter Transaction Invoice / Debit Note
Code VF02 or VF03 / Credit note /
in Client 110 and Cancellation of
Enter the Billing Invoice will be
Document Number displayed based on
the billing document
Number

Number
Number
38. Negative Test Cases
Test Case Test Case Expected Result Actual Result

Description
1 Billing Document
Enter Transaction number does not
Code VF02 or VF03 exist
in Client 110 and
Enter the Billing
Document Number
Page 22 of: 23
39. Additional Information/Appendix ( if any)
Ref. Title Sample Date Author(s)

files
Page 23 of: 23

FS For Purchase Order Output

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FS For Purchase Order Output

Uploaded by

Copyright:

Available Formats

FSTS_O2I_FRM_Invoice _ ZO2ISF_225_INVOICE_NL

FS_TS FSTS_O2I_FRM_ MMPO _ ZO2ISF_225_ MMPO_NL

FRICE REF./CCB / Gap ID :

VERSION CONTROL AND CHANGE HISTORY

VERSION REVISION AUTHOR SUMMARY OF CHANGES (to include

1.0 21/01/2022 vaishnavi

REVIEW AND APPROVAL – ACCEPTANCE AND APPROVAL LOG

NAME ROLE DATE ACCEPT Email contact

INTRODUCTION AND PURPOSE

1. Business Process overview

4. Dependencies and Constraints

Frequency and Timing

Form format (Online/Printout/Sheet)

6. Report / Program / Transaction / Form Name:

7. Affected Application Areas

SAP Module Impact

External System ID Impact

8. Detailed Functional Logic

SAP Form Details

Type of solution (Standard R/3, custom Standard R/3

Fields (Data Mapping Table) (FO + TO)

ID Description Field Logic Print- Font

Label 4 Domestic Purchase Domestic hard copied All Arial

Label 10 Please Deliver to: Deliver to hard copied All Arial

Label 15 Terms of payment Terms of hard copied All Arial

Label 16 Currency: Currency hard copied All Arial

Label 25 Total Net Value Total hard copied All Arial

Name and Address of the vendor.

The vendor number with us: EKKO-LIFNR

The address to which the good must be delivered.

The payment terms with the currency should be entered.

Total Net Value: get the value form EKKO-RLWRT

Please see Excel document “MMPO_MESSAGES”:

9. Standard/Alternative Options considered NA

10. Selection/ Layout Criteria NA

11. Report Selection screen Criteria

Sr. Field Text on Selection Table and Mandatory Default

No Screen Field Name (Y/N) Value

12. Custom Table involved in report generation

Sr. Field Description Field Table

13. Report /Form Layout Criteria

Sr. Field Table Total/ Sub Total

Model for Standard Form / Output

Name of standard form :

Existing / Sample Reports

SAP Program Name :

SAP Menu / Transaction :

Legacy Report Name / Title : If Applicable

Related SAP Transaction(s) : If Applicable

14. External file Format

File Name File Description Usage

External File Layout

15. Security and Authorizations

Is a new transaction code required? Yes No ☒

For new transactions: Yes No

16. Authorisation objects

17. Roles to be updated with new transaction codes

Business Roles to be changed: Master role to be Derived roles to be

Support Roles to be updated:

18. Technical Specification

19. Development Attributes

20. Function Modules