Functional Design Document

Functional Design Document

Object NameLAYOUTS OF INVOICE

Description Layouts of invoice

CategoryIndustry

Designer Fazlur Rehaman KhanReviewer

Obligatory Requirements

SAP VersionECC 6.0Support Package

Dependency

Version Control

VersionModified in ResponsibleModification

V1.008.08.2014Fazlur Rehman KhanInitial document

Document Details

Object Number : Description : Remarks: N/A

Program Type

|_| Report |_| Interface |X| Enhancement |_| Form |_| Conversion Load |_| Conversion Extract |_| Legacy Modification |_| Legacy Interface (Legacy to Legacy) |_| Other Manual Conversion______________

Frequency

|X| Real Time |_| Scheduled |_| On Demand(for Scheduled interfaces only )|_| Daily Multiple |_| Weekly |_| Monthly |_| Yearly

Interface Type

|_| ALE |_| EDI |_| BAPI |_| Flat File |_| Others: _________________

Business Criticality

|X| High |_| Medium |_| Low

Programming Language (consult technical team to fill this section)

|X| ABAP |_| JAVA |_| VB |_| Other_______________

Data Flow (for interfaces only)

Source:Destination:Volume:

Table of Content1.Purpose7Scope7Overview72. Matrix of SAP Functionality per Raiply Organisation83.Create Billing Outputs94.Document Control Parameters105.Document Details:14Document Examples: Customer Invoice146.Document Examples: Customer Credit16167. Document Detail: Sales Invoice / Credit / Debit: Language Version - English17178. Roles and responsibilities209. Definitions and Acronyms2010. RiceF-W20Data2111. Interim business processes2112. Nonfunctional requirements2113. external systems & dependencies22

1. PurposeThe purpose of this document is to specify the SAP system functionality that supports the core business requirements for processing billing outputs.

ScopeThe scope of this document covers all functional requirements for the area of Billing Output processing.OverviewThis document contains an outline of the requirements for Billing Document related outputs. This includes processing the following output types: Invoice Output (domestic/export) Credit/Debit memo output

2. Matrix of SAP Functionality per Raiply OrganisationThe matrix below lists the Raiply organisations that are making use of the functionality specified in this document.SAP FunctionalityKwale Organisation

InvoiceManufacturingCommercialPTC

Credit Note/Debit NoteManufacturingCommercialPTC

3.Create Billing OutputsBilling Documents will be produced in the following Business Processes:

SC08 - Sale of Product from Stock SC89 - Sale of Product from Stock with Shipment SC91 - Customer Return of Product with Billing SC92 - Customer Return of Product with Billing and Shipment Functional Design Document

7Controlled Document DO NOT COPY without permissionPage 7 of 22

4.Document Control ParametersThe following table describes the output types and associated information for control of each output type.Output typeOutput Control ByOutputTriggerMethodLangPre-PrintedPaper LogoBar codePage No. formatLegal Required?Paper SizeFont type & sizes

ZINVBilling typeInvoiceInvoice SavedPrintENYesNoX of YYesA4 - LandscapeCorp Std

ZINVBilling typeCredit/Debit MemoInvoice SavedPrintENYesNoX of YYesA4 LandscapeCorp Std

FieldDescriptionWarning message during order entry

Header

VBAK-AUDATDocument date

VBAK-WAERKDocument currency

VBKD-BSTKDPO numberX

VBKD-INCO1Incoterms

VBKD-PRSDTPricing date

VBKD-ZTERMPayment termsX

Item

Checks for standard item category

VBAP-ARKTXDescription

VBAP-BRGEWGross weight

VBAP-KWMENGOrder quantityX

VBAP-NETWRNet value

VBAP-NTGEWNet weight

VBAP-OBJNRObject no.Item

VBAP-PRSOKPricing

VBAP-TECHSStandard variant

VBAP-VSTELShipping point/receiving pt

VBAP-WERKSPlant

VBKD-INCO1Incoterms

VBKD-PRSDTPricing date

VBKD-ZTERMPayment terms

Checks for free of charge item category

VBAP-ARKTXDescription

VBAP-BRGEWGross weight

VBAP-KWMENGOrder quantity

VBAP-PRSOKPricing

VBAP-TECHSStandard variant

VBAP-VSTELShipping point/receiving pt

VBAP-WERKSPlant

Checks for schedule line

VBEP-LDDATLoad.date

VBEP-MBDATMaterial avail.date

VBEP-TDDATTransport.plan.date

VBEP-WADATGoods issue date

FieldDescriptionWarning message during order entry

Header

VBAK-AUDATDocument date

VBAK-GUEBGValid-from dateX

VBAK-GUEENValid-to dateX

VBAK-VSBEDShipping conditions

VBAK-WAERKDocument currency

VBKD-BSTKDPO number

VBKD-INCO1Incoterms

VBKD-KURSKExchange rate

VBKD-PRSDTPricing date

VBKD-ZTERMPayment terms

Item

Checks for standard item category

VBAP-ARKTXDescription

VBAP-NETWRNet value

VBAP-PRSOKPricing

VBAP-TECHSStandard variant

VBAP-VSTELShipping point/receiving pt

VBAP-WERKSPlant

VBAP-ZMENGTarget quantityX

VBKD-INCO1Incoterms

VBKD-PRSDTPricing date

VBKD-ZTERMPayment terms

5.Document Details: Document Examples: Customer Invoice

6.Document Examples: Customer Credit

7. Document Detail: Sales Invoice / Credit / Debit: Language Version - English

Each number in the document layout above corresponds to a value in the following table which explains each value in detail.Print Area / Box NumberField DescriptionColumn Heading / Document Field Data to be printed:Column ContentRemarks

0Document typeInvoice/Heading type will be as company has a Printout pre- printed stationaryInvoice or Debit Note or Credit NoteContent depending from the pre-printed

1SOLD TO PARTY Name and AddressFrom customer master dataRaiply CustomerName and address of customer to whom product is sold.

2Invoice Invoice/Heading type will be as company has a export invoice/ NoneInvoice name should be bold/export

3Raiply PIN and Vat Number.NoneCompany Code details & VAT NumberPIN and VAT of the Company Code associated to the Sales OrganisationVAT Number

4Account number of customer.From customer Master data. Customer details should be mention in heading column of invoiceCustomer account number should me there in invoice column.

4Invoice info.Invoice NoDatePage NoInvoice Number (ODN Official Document Number for tax purpose), Date & page numberStandard Text in form for Column Header.

4Delivery-to DataDelivery-ToDelivery-Date detailsStandard Text in form for Column Header.

4Order numberOrder -DetailOrder numberStandard Text in form for Column Header.

4Sold by personSold by from customer group master data Name of sales personStandard Text in form for Column Header.

5DetailsDetails Master dataTerm Details of payment Separation blockSeparation Block. Standard Text in form for Column Header

6Item Column HeaderItem Column HeaderMaterial Description from line itemUOMQuantityPriceNet AmountVATSeparation Block. Standard Text in form for Column Header

7Totals InformationTotals informationTotal AmountTotal VAT AmountAmount Due

Standard Text in form for Column Header.

8Contact & Bank detailsN/ACompany code detailsBank detailsStandard Text in form for Column Header.

9Text to be printed for Description as shown Description Description has to be printed

10TextDescription as shownText for invoice Standard Text in form for Column Header.

8. Roles and responsibilitiesRolesResponsibilities

SD Functional Consultant Authors this Functional Specification document Ensures this document accurately reflects its intended Purpose and Scope

order Solution Architect Review and approval of this document

Order Business Process Owner Review and approval of this document

Order Process Champion Review and approval of this document

9. Definitions and AcronymsTermDescription

SDSales and Distribution module in the SAP system

OrderOrder business scenarios

Billing TypeThe billing type determines how the system processes billing. For example, depending on the billing type, the system determines which screens to present and which data to request from the user.

10. RiceF-WThe following enhancements are required to support the designed processes:Type FS Ref Description ComplexityApproved

Reportn/aNonen/an/a

Interfacen/aNone n/an/a

Conversionn/aNonen/an/a

Enhancementn/aNonen/an/a

Formn/a Invoice Credit/Debitn/an/a

Workflow n/aNonen/an/a

DataThere are no Data requirements.

RolesResponsibilities

Test Data Cash invoice number 90000091 with multiple line items. Domestic invoice number 90000092 with single line items

Nace configuration ZINV

Sales Invoice table VBRP/VBRK

Amount table/price VBAP/NETPR & VBRP-NETWR

VAT Condition MWST

Changes 20/08/2014 po number: VBRK-BSTNK_VF

Sold by filed: VBAK-VKGRP and pass this to TVGRT and get TVGRT-BEZEI and SPARS

Due for payment on: (T052-ZTAG1 is the No. of Days where ZTERMS = VBKD-ZTERM) Days / (Invoice Date + T052-ZTAG1)Description:1. Material number/Description required only in case of Mombasa and Nairobi VBAP-WERKS to get the sales order number and Plant details from invoice plz fallow the below logic;Pass invoice & Item number in VBELN and Item number in POSNN, VBTYP_N=M and VBTYP_C=C from table VBFA to get sales order AS VBELV and POSNV as item.Get WERKS from VBAP were VBELN =VBFA-VBELV & POSNR=VBFA-POSNVSA.1100-NairobiB. Mombasa 1200.

2. In the remaining cases only material description should be printed...

Price: price =net amount / quantity or Get KNUMV from VBRK were VBELN=invoice number. Pass KNUMV=VBRK-KNUMV & KSCHL=ZPR0 in Table KONV to get the KBETR as price

Vat: Get KBETR from KONV were KNUMV=VBRK-KNUMV & KSCHL=MWST . Vat = KBETR/10

Bank details: Bank details will not be printed for Nairobi /Mombasa and in case of cash sales

Once received, I will send you over the mail.

Description should be printed at the bottom

GOODS ONCE SOLD ARE NOT REFUNDABLE EXCHANGEABLE OR RETRUNABLECBDF3C817589B2D739951B9FD8676D5E9D1346D6 0001 0002194B 1408200934 COS05000393Page no Should be printed at the down right corner of the page eg. PAGE 1/5

AMOUNT DUE: Should be displayed as VBRK-WAERK (DOC CURRENCY) FOLLOWED BY AMOUNT.Eg: KES: 11008900

Change 26/08/2014 Export Invoice

Under export layout the pricing should be taken from condition type ZPR1.The document type for export is ZEXR

The invoice type for Export is ZEXIEg: 0090000099 export invoice number

Order Type for Export Invoice is ZEXR.Currency should come from table/field as in Domestic Invoice. In most of the cases it will be stored as USD.Note - There will No VAT for the Export Invoice.

Also, Text EXPORT should be printed below the text INVOICE.

Debit Memo

Under debit memo layout the pricing should be taken from condition type ZPRC.The document type for debit memo request is ZDR.

The invoice type for Debit Memo is ZL2.Eg: 90000080 Debit memo invoice number

Also, Text DEBIT MEMO should be printed below the text INVOICE.

Credit Memo

Under debit memo layout the pricing should be taken from condition type ZPRC.The document type for Credit memo request is ZCR.

The invoice type for Credit Memo is ZG2Eg: 90000080 Credit memo invoice number

Also, Text DEBIT MEMO should be printed below the text INVOICE.

Return Invoice

Under Return layout the pricing should be taken from condition type ZPR1.The document type for Credit memo request is ZRE.

Also, Text Credit memo should be printed below the text INVOICE.

The invoice type for Return is ZRECEg: 90000126 Return invoice number

11. Interim business processesThere are no Interim Business Process requirements.12. Nonfunctional requirementsThere are no Non Functional requirements.13. external systems & dependenciesThere are no Existing System & Dependencies.

Page 20 of 22