FUNCTIONAL SPECIFICATION WRICEF

SCENARIO (BUSINESS AREA): <OTC/INVOICE PROCESS >

BUSINESS PROCESS: < OTC/INVOICE PROCESS >

PROJECT IDENTIFICATION

Project Name CPI Project Number

IPEG PROJECT
Customer Name Customer Number
IPEG
SAP Project Manager Customer Project Manager
SHIVAJI SINGH/RAJA PREMKUMAR

Author Document Location (repository/path/name)

<Author> <Document location>
Version Status Date (MM-DD-YYYY) Document Classification
0.1 Final 10-18-2014 Confidential

REVISION HISTORY

Version Date Description

0.1 October 22, 2014 <Text here>
0.2

REVIEW AND APPROVAL

Name Date (MM-DD-YYYY)

Customer Project Manager

1 of 12
Name Date (MM-DD-YYYY)
SAP Project Manager

Name Date (MM-DD-YYYY)

Key Stakeholder

Name Date (MM-DD-YYYY)

Key Stakeholder

` 2 of 12
TABLE OF CONTENT

1. PURPOSE OF THIS DOCUMENT ...................................................................................................... 4

2. GENERAL OBJECT OVERVIEW ....................................................................................................... 4
2.1 Process Requirements Reference ................................................................................................ 5
2.2 Generic WRICEF ......................................................................................................................... 5
3. OBJECT SPECIFIC DESIGN .............................................................................................................. 6
3.1 Output (e.g. forms) ....................................................................................................................... 6
4. TEST CONDITIONS .......................................................................................................................... 12

` 3 of 12
1. Purpose of this document
With the implementation of the SAP solution, the invoicing activities will be carried out entirely in SAP.
To have a better visibility of the material and goods that are shipped out of the plant and billed, the
processes like printing the Invoices will be carried out in SAP. This would require that the invoice due list and
the invoicing and posting is done in SAP

The document here details about the Design and Solution for the required output form.

2. General Object Overview

Object Overview

RICEF_SD_015 Business
Object ID Invoicing of the sales transaction
Process

ECC 6.0 SAP Sales and Distribution

SAP Release
Module
() Report
() Interface
() Conversion
Object Type () Enhancement
(X) Form
() Workflow

Object Title Invoice Creation

Object Description Invoicing of the sales transaction

Mock Up ID / Name INT-001

Required
Cycle of Testing / C1 / C2 / C3 / C4 DDMONYY
Development
Sprint Cycle
Completion Date
Simple / Medium / Complex Low / Medium / High
Complexity of Object Priority

SAP Transaction VF01,VF02 SAP Program

Name Name

Similar SAP Similar SAP

Transaction Program

FS CONTROL

` 4 of 12
 <Customer>
Functional Consultant
Honge Gowda, Naveen Process Owner
Author and Phone Last Name, First Name
and Phone
Number
Number

Planned Date of FS DDMONYY Actual Date of FS DDMONYY

Completion Completion
Last Name, First Name DDMONYY
FS Approved By FS Approval date

Other Contact and Other Contact and

Phone Number Phone Number

2.1 Process Requirements Reference

Process Reference
Requirement ID RICEF_SD_015

Requirement Request is to develop an output form which captures the details of the
Description materials that are billed capturing the prices and costs in the process
Gap to be addressed N/A
Alternative SAP N/A
Standard Solution

2.2 Generic WRICEF Descriptions

Justification

The form layout of the form is designed according to the organizational requirements. The data displayed in the
form is mapped to and retrieved from the transaction in general and the line items in the delivery and order in
particular

FUNCTIONAL DESCRIPTION / DESIGN

The invoice details with respect to the material being delivered to the customer and the prices
maintained in the sales order,

TRANSACTION VOLUME
The data is created real-time and the records are created continuously in the normal course of the business

` 5 of 12
FREQUENCY & TIMING

This output form will be created and printed on a daily basis for the transactions done daily.

DEPENDENCIES

AUTHORIZATION REQUIREMENTS

RELATED DOCUMENTATION (ATTACH OSS NOTES, EMAILS, DOWNLOAD OF EXISTING FORM,

ETC)

3. Object Specific Design

3.1 Output (e.g. forms)
Output
WRICEF-ID Description Data Object Output Type Frequency Volumes Owner
(Sales Order) (Form, EDI, etc.)
RICEF_SD_015: Invoicing of the Invoice SmartForm Real Time HIGH
sales
transaction

Process Flow Diagram

Sales Delivery Invoice

Order

Invoice printout

` 6 of 12
Form Layout

Example:
Invoice number
Invoice Date: xxxxx
Reference document
numbers
Order type
Bill to Party Address Sales Representative

Ship Via
Terms of payment
Delivery Address Terms of delivery
Remit To Details
Contact

Pos Q Pos qnty Unit Item(Description)unit price total

Hardcoded Text

Invoice_Z396331.pd
f

` 7 of 12
Output Field Programming Conditions Logic Description
VBRK-VBELN
Invoice No
VBRK-ERDAT
Invoice Date
VBRK-KUNNR
Customer

Order No Pass VBRK-VBELN into

VBFA as follow on
document and fetch VBFA-
VBELV where VBTYP_V =
C

Customer PO number Pass VBELV into VBKD

and fetch VBKD-BSTKD
VBPA- KUNNR
Sales Representative Where VBPA-
VEBLN=VBRK-VBELN and
the PARVW=Y1

Order Type Hard coded based on the

Delivering Plant

For Pass VBRK-KUNRG into Pass VBRK-VBELN and fetch

KNA1-KUNNR and fetch VBRK- KUNRG.
KNA1-ADRNR. Pass
KNA1-ADRNR into ADRC-
ADDR NUMBER and fetch
ADRC- NAME1, ADRC-
NAME2, ADRC- NAME3,
ADRC-CITY1, ARDC-
CITY2, ADRC-
TEL_NUMBER, ADRC-
REGION, ADRC-
COUNTRY

` 8 of 12
Delivery Address Pass VBRK-VBELN into
VBFA as follow on
document and fetch VBFA-
VBELV where VBTYP_V =
J
Pass VBFA-VBELV into
LIPS-VBELN and fetch
LIPS-KUNNR and pass it in
KNA1 where KNA1-
KUNNR and fetch KNA1-
ADRNR. Pass KNA1-
ADRNR into ADRC-
ADDR NUMBER and fetch
ADRC- NAME1, ADRC-
NAME2, ADRC- NAME3,
ADRC-CITY1, ARDC-
CITY2, ADRC-
TEL_NUMBER, ADRC-
REGION, ADRC-
COUNTRY

Remit To Hard Coded based on Plant Pass VBRK-VBELN into

VBRP-VBELN and fetch VBRP-
WERKS

Remit To (ACH/EFT) Hardcoded based on

company code

Terms of Payment VBRK-ZTERM

Terms of delivery VBRK-INCO1,VBRK-

INCO2

Ship Via VBKD-VSART Pass VBRK-VBELN into

VBFA as follow on
document and fetch VBFA-
VBELV where VBTYP_V =
C

Pass VBELV into VBKD

and fetch VSART

TEXT Hardcoded

Contact KNVK-NAMEV Pass VBRK-KUNRG into

KNVK-KUNNR and fetch
KNVK-NAMEV and
KNVK-NAME1-

` 9 of 12
POS VBRP-POSNR Where VBRK-
VBELN=VBRP-VBELN

QUOTE POS

Material VBRP-MATNR Where VBRK-

VBELN=VBRP-VBELN

Description Pass VBRK-VBELN into

VBRP-VBELN and fetch
VBRP- ARKTX

Quantity VBRP- FKIMG Pass VBRK-VBELN into

VBRP-VBELN and fetch
VBRP- FKIMG

Rate Pass VBRK-VBELN into

VBRK and fetch VBRK-
KNUMV. Pass VBRK-
KNUMV into KONV-
KNUMV and fetch KONV
where KONV-
KSCHL=ZPR1

Amount Pass VBRK-VBELN into

VBRK and fetch VBRK-
KNUMV. Pass VBRK-
KNUMV into KONV-
KNUMV and fetch NETWR

Bank Name Hard Coded

Account No Hard Coded

IFSC No Hard Coded

Declaration Text Hard Coded

TOTAL Sum of all NETWR

` 10 of 12
Printer Requirements

Default printer should have to be considered LP01 also required the PDF print option.

Legal Requirements

NA

Existing Sample Forms

Refer attachment earlier

` 11 of 12
4. Test Conditions
BUSINESS TEST CONDITIONS (TO BE FURNISHED BY THE FUNCTIONAL CONSULTANT)

Scenario # Input Selection Criteria Expected Result

` 12 of 12