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
Customer Project Manager

Date (MM-DD-YYYY)

1 of 13

Name
SAP Project Manager

Date (MM-DD-YYYY)

Name
Key Stakeholder

Date (MM-DD-YYYY)

Name
Key Stakeholder

Date (MM-DD-YYYY)

2 of 13

TABLE OF CONTENT
1.

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

2.

GENERAL OBJECT OVERVIEW.........................................................................................................4

3.

2.1

Process Requirements Reference.................................................................................................5

2.2

Generic WRICEF .......................................................................................................................... 5

OBJECT SPECIFIC DESIGN............................................................................................................... 6

3.1

4.

Output (e.g. forms)........................................................................................................................ 6

TEST CONDITIONS........................................................................................................................... 12

3 of 13

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

Object ID

RICEF_SD_015

Business
Process

Invoicing of the sales transaction

SAP
Module

Sales and Distribution

SAP Release

ECC 6.0

Object Type

() Report
() Interface
() Conversion
() Enhancement
(X) Form
() Workflow

Object Title

Invoice Creation

Object Description

Invoicing of the sales transaction

Mock Up ID / Name

INT-001

Cycle of Testing /
Sprint Cycle

C1 / C2 / C3 / C4

Required
Development
Completion Date

DDMONYY

Complexity of Object

Simple / Medium / Complex

Priority

Low / Medium / High

SAP Transaction
Name

VF01,VF02

SAP Program
Name

Similar SAP
Transaction

Similar SAP
Program

FS Control

4 of 13

Honge Gowda, Naveen

<Customer>
Process Owner
and Phone
Number

Last Name, First Name

Planned Date of FS
Completion

DDMONYY

Actual Date of FS
Completion

DDMONYY

FS Approved By

Last Name, First Name

FS Approval date

DDMONYY

Functional Consultant
Author and Phone
Number

Other Contact and

Phone Number

Other Contact and

Phone Number

2.1 Process Requirements Reference

Process Reference
Requirement ID

RICEF_SD_015

Requirement
Description
Gap to be addressed
Alternative SAP
Standard Solution

Request is to develop an output form which captures the details of the

materials that are billed capturing the prices and costs in the process
N/A
N/A

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 13

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

RICEF_SD_015
:

Invoicing of the
sales
transaction

Data Object
(Sales Order)
Invoice

Output Type
(Form, EDI, etc.)
SmartForm

Frequency

Volumes

Real Time

HIGH

Owner

Process Flow Diagram

6 of 13

Sales
Order

Delivery

Invoice

Invoice printout

Form Layout

7 of 13

Example:
Invoice number
Invoice Date: xxxxx
Reference document numbers
Order type
Sales Representative

Bill to Party Address

Delivery Address

Ship Via
Terms of payment
Terms of delivery
Contact

Remit To Details

PosQ Pos qntyUnit Item(Description)unit pricetotal

Hardcoded Text

Invoice_Z396331.pd
f

8 of 13

Output Field
Invoice No
Invoice Date
Customer

Programming
VBRK-VBELN

Conditions

VBRK-ERDAT
VBRK-KUNNR

Order No

Pass VBRK-VBELN into

VBFA as follow on
document and fetch VBFAVBELV where VBTYP_V =
C

Customer PO number

Pass VBELV into VBKD

and fetch VBKD-BSTKD

Sales Representative

Logic Description

VBPA- KUNNR

Where VBPAVEBLN=VBRK-VBELN and

the PARVW=Y1

Order Type

Hard coded based on the

Delivering Plant

For

Pass VBRK-KUNRG into

KNA1-KUNNR and fetch
KNA1-ADRNR. Pass
KNA1-ADRNR into ADRCADDR NUMBER and fetch
ADRC- NAME1, ADRCNAME2, ADRC- NAME3,
ADRC-CITY1, ARDCCITY2, ADRCTEL_NUMBER, ADRCREGION, ADRCCOUNTRY

Pass VBRK-VBELN and fetch

VBRK- KUNRG.

9 of 13

Delivery Address

Pass VBRK-VBELN into

VBFA as follow on
document and fetch VBFAVBELV where VBTYP_V =
J
Pass VBFA-VBELV into
LIPS-VBELN and fetch
LIPS-KUNNR and pass it in
KNA1 where KNA1KUNNR and fetch KNA1ADRNR. Pass KNA1ADRNR into ADRCADDR NUMBER and fetch
ADRC- NAME1, ADRCNAME2, ADRC- NAME3,
ADRC-CITY1, ARDCCITY2, ADRCTEL_NUMBER, ADRCREGION, ADRCCOUNTRY

Remit To

Hard Coded based on Plant

Remit To (ACH/EFT)

Hardcoded based on
company code

Terms of Payment

VBRK-ZTERM

Terms of delivery

VBRK-INCO1,VBRKINCO2

Ship Via

VBKD-VSART

Pass VBRK-VBELN into

VBRP-VBELN and fetch VBRPWERKS

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
Contact

Hardcoded
KNVK-NAMEV

Pass VBRK-KUNRG into

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

10 of 13

POS

VBRP-POSNR

Where VBRKVBELN=VBRP-VBELN

VBRP-MATNR

Where VBRKVBELN=VBRP-VBELN

QUOTE POS
Material

Description

Quantity

Pass VBRK-VBELN into

VBRP-VBELN and fetch
VBRP- ARKTX
VBRP- FKIMG

Pass VBRK-VBELN into

VBRP-VBELN and fetch
VBRP- FKIMG

Rate

Pass VBRK-VBELN into

VBRK and fetch VBRKKNUMV. Pass VBRKKNUMV into KONVKNUMV and fetch KONV
where KONVKSCHL=ZPR1

Amount

Pass VBRK-VBELN into

VBRK and fetch VBRKKNUMV. Pass VBRKKNUMV into KONVKNUMV and fetch NETWR

Bank Name

Hard Coded

Account No

Hard Coded

IFSC No

Hard Coded

Declaration Text

Hard Coded

TOTAL

Sum of all NETWR

11 of 13

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

12 of 13

4. Test Conditions
BUSINESS TEST CONDITIONS (TO BE FURNISHED BY THE FUNCTIONAL CONSULTANT)
Scenario #

Input Selection Criteria

Expected Result

13 of 13