Functional and Technical Specification

PROJECT IDENTIFICATION
Project Name
Project KOJO

Organization
Advanced Composite

Project Manager Work Stream

Hanif Rajpurkar  Supply Chain Management

DOCUMENT IDENTIFICATION
Document Name Document Location (repository/path/name)
/conversion/tmp/activity_task_scratch/
FSTS-SP-OP-F-23-Purchase Order Form
647676555.docx

Document
Version Status Date (YYYY-MM-DD)
Classification
1.0 Initial 04/15/2022 Shared

Functional Author Sarvesh Gupta

Technical Author

REVISION HISTORY
Revision Date Revised By Comments

APPROVAL HISTORY
Date Name Comments
06/24/2022 Don

1
Functional and Technical Specification

Contents
1 General Information.............................................................................................................................. 3
1.1 Overview...................................................................................................................................... 3
1.2 Business Requirements............................................................................................................... 3
1.3 Assumptions................................................................................................................................ 4
1.4 Integration Points and Dependencies.......................................................................................... 4
1.5 Security and Control Considerations............................................................................................ 4
1.6 Other Relevant Information.......................................................................................................... 4
2 Functional Unit Test Scenarios............................................................................................................. 5
3 Output Forms........................................................................................................................................ 6
3.1 Form Layout (Sort/Sequencing Criteria)......................................................................................6
3.2 Print program special consideration............................................................................................. 6
3.3 Form logic.................................................................................................................................... 6
3.4 Detailed Technical Design........................................................................................................... 6

2
Functional and Technical Specification

1 General Information
1.1 Overview

Formal request or instruction from a purchasing organization to a vendor or a plant to supply or

provide a certain quantity of goods or services at or by a certain point in time. A purchase order
consists of a document header and a number of items.

The information shown in the header relates to the entire purchase order for example, the
terms of payment and the delivery terms are defined in the header. A procurement type is
defined for each of the document items. The following procurement types exist:

 Standard Purchase order (Direct Purchase Order)

 Material Subcontracting
 Dropship Subcontracting Purchase order
 Indirect Purchase Order

IDI will need a Purchase order form that would be used to communicate Purchase Order
information to the Supplier. The PO form should display details that are being displayed on the
current/ legacy purchase order form.
This form should also include,
 ACP Logo
 Supplier address
 Delivery address.
 Invoice To
 Delivery date,
 PO number,
 Item number,
 Item description
 currency code,
 Price,
 Special instructions,
 Payment Terms,
 Header Text
 Item Text
 Subcontracting Component

This form will be standard for all ACP plants, except for the Plant name, addresses and any
company / plant specific terms and conditions.

3
Functional and Technical Specification

1.2 Business Requirements

As per the PO copy, po form will be custom one similar to exiting ACP PO form

1.3 Assumptions
<List any system or business assumptions>

Same purchase order form will be utilized for direct purchase order, special procurement such
as subcontracting order and subcontracting dropship .

1.4 Integration Points and Dependencies

<List key integration points between this unit of work and other business processes, WRICEF objects,
etc. Include both upstream and downstream impacts>

NA

1.5 Security and Control Considerations

<List data security or sensitivity considerations, a proposed business role for the transaction, and any
business process controls that will need to be validated as part of this WRICEF>

 Initial print will be at the time of purchase order save event.

 Authorized users/buyers will be given reprint / resend access.

1.6 Other Relevant Information

4
Functional and Technical Specification

PO form will be developed by copying the SAP standard form “MM_PUR_PURCHASE_ORDER” &
BRF+ rules

5
Functional and Technical Specification

2 Functional Unit Test Scenarios

Test Case Description Fiori Tile / Navigation Expected Results
Create purchase Enter the vendor, Manage Purchase Able to display / Print
order of document Purchasing group, Order purchase order output
type ‘NB’ plant, Material number,
quantity and price.
Save the PO.
Change Purchase Existing purchase Manage Purchase Able to display / Print
Order of document order. Choose PO for Order purchase order output
type ‘NB’. which the vendor has
transmission medium
as external send.
Create return Mark returns indicator Able to display / Print
purchase order as ‘X; in the PO line purchase order output
item
Print and Reprint PO Enter the vendor, Manage Purchase Should be able to print
from Purchasing group, Orders purchase order form
plant, Material number,
quantity and price.
Save the PO.
Create purchase Enter the vendor, Manage Purchase Able to Email purchase
order of document Purchasing group, Order order with output
type ‘NB’ plant, Material number,
quantity and price.
Save the PO.
Change Purchase Existing purchase Manage Purchase Able to Email purchase
Order of document order. Choose PO for Order order with output
type ‘NB’. which the vendor has
transmission medium
as external send.
Create return Mark returns indicator Able to Email purchase
purchase order as ‘X; in the PO line order with output
item

6
Functional and Technical Specification

3 Output Forms
Form Type ☐ SmartForm, ☐ SAPscript, ☒ Adobe, ☐ Other
Form Name(s) If multiple forms
Print Program
Initiating Fiori Tile <Created Purchase Order – advanced /Manage purchase orders
Source Form if Copying
Source Print Program if
Copying
Output Type ☐ Letter (8.5 x 11), ☒ A4, ☐ Label, ☐ Other
Label Output Size
Intended Audience Customer, Internal staff/dept, Vendor, etc
Intended Localizations U

3.1 Form Layout (Sort/Sequencing Criteria)

<Details of form layout, including requirements for barcodes, page breaks, paper type (blank, pre-printed,
etc.), and totaling. Provide a scan of an existing version if available for as-is comparisons.>

3.2 Print program special consideration

<Checks the print program needs to perform, including if the program needs to select a slightly different
version of the form than is defined in config>

 Return box is checked, then Form Header is Return Purchase Order

3.3 Form logic

<Logic or calculations required to produce specific values that do not have obvious sources>

3.4 Detailed Technical Design

<All objects created for this WRICEF
Specific Code logic that needs to be understood to support
Technical dependencies>

7
Functional and Technical Specification

• Application Object type PURCHASE_ORDER

• Output Type PURCHASE_ORDER
• Form Type 1-Output Forms (Gateway interface)
• Form Template ID MM_PUR_PURCHASE_ORDER

Content Form Creation:

1. Standard Form Template: MM_PUR_PURCHASE_ORDER

2. Form Name: ZZ1_MM_PUR_PURCHASE_ORDER_E

Maintain the below text id to appear in Output in SPRO

8
Functional and Technical Specification

Master Form Creation:

To update new logo we have created custom Master page
1. Master Form: ZZ1_APOC_DEMO_FORM_MASTER_US

2. ACP LOGO:

Configuration for Update Master Form template respect to the Content Form
Template

9
Functional and Technical Specification

10