Professional Documents
Culture Documents
FS For New SD Invoice Layouts
FS For New SD Invoice Layouts
CONNECT
SD FI
MM CO
PP AM
QA R/3 PS
PM WF
HR IS
FUNCTIONAL SPECIFICATION
TCS Internal
Document ID : Invoice Layout Project Connect PAGE 2 OF 14
DESCRIPTION: INVOICE LAYOUT MODULE: SD
APPROVAL
1. Table of contents
1. TABLE OF CONTENTS..............................................................................................................................................................................................................2
2. RELATED DOCUMENTS..........................................................................................................................................................................................................2
3. TERMINOLOGY..........................................................................................................................................................................................................................2
4. FUNCTIONAL SPECIFICATION..............................................................................................................................................................................................2
4.1. SCOPE.......................................................................................................................................................................................................................... 2
4.1.1. Overview..........................................................................................................................................................................................................................2
4.1.2. Description.......................................................................................................................................................................................................................2
4.2. LOGIC AND DATA FLOW............................................................................................................................................................................................... 2
4.3. TRIGGER EVENTS/FILE LOCATIONS............................................................................................................................................................................... 2
4.4. PROCESSING MODE....................................................................................................................................................................................................... 2
4.5. FILE TRANSFER MECHANISM (INTERFACES ONLY)......................................................................................................................................................... 2
4.6. FREQUENCY (INTERFACES ONLY).................................................................................................................................................................................. 2
4.7. VOLUMETRICS (CONVERSIONS AND INTERFACES ONLY)................................................................................................................................................. 2
4.8. DEPENDENCIES............................................................................................................................................................................................................. 2
4.9. CONTROLS APPROACH (CONVERSIONS AND INTERFACES ONLY)..................................................................................................................................... 2
4.10. INTEGRITY MECHANISM............................................................................................................................................................................................ 2
4.11. PROGRAM ASSUMPTIONS........................................................................................................................................................................................... 2
4.12. PROGRAM ISSUES...................................................................................................................................................................................................... 2
4.13. ERROR HANDLING.................................................................................................................................................................................................... 2
APPENDIX 1 – DATA MAPPING (CONVERSIONS AND INTERFACES ONLY)....................................................................................................................2
2. Related Documents
The following documents are related to this document:
3. Terminology
<Naming conventions and acronyms used in this document>
Acronym Explanation
4. Functional Specification
4.1. Scope
4.1.1. Overview
<Short tabular overview of Program, feel free to add any.>
Information
What kind of development (report,
interface, conversion, extension, form) Form
New or modification of existing Modification
SAP Module(s) involved SD
SAP Menu Path involved
SAP Transaction Code(s) (if any VF01/VF02
involved)
Inbound/Outbound/Both (if interface) NA
Legacy System (if any involved) NA
Reference Document NA
4.1.2. Description
Business Requirement:
Modifications of the existing Invoice Layouts to include different formats for the Retail and Tax Invoices.
J_1IMOCOM
VAT/TIN N0. P J_1ILSTNO
Registration Date:
J_1IMOCOM
CST Reg No: P J_1ICSTNO
Registration Date:
Dealer Name and Address:
Invoice No. VBRK VBELN
Date VBRK FKDAT
Delivery No VBRP VGBEL
Delivery Date LIKP WADAT_IST
PO Number VBKD BSTKD
PO Date VBKD BSTDK
Despatch Document
Despatch Date
Terms of Delivery
Name and Add of Customer KNA1 NAME1
Telephone No: KNA1
Mobile KNA1
Fax KNA1
Email KNA1
Vat/Tin No KNA1 STCEG
Vat/Tin No Registration
Date
CST Reg No. KNA1 STCD1
CST Reg Date
Transporter Destination
LR/RR/GR/CR No.
Weight/No. of packages
Line Item
Serial Number Number(1,2,3….ect)
1. The fields in the first box of the excel sheet have to entered in the corresponding fields in the Layout.
2. Go to VBRK Table; pick up VBRK-VBELN, FKDAT, and KUNNR.
3. Go to VBRP, Pass VBRK-VBLN and get the VBRP-VGBEL (more than one delivery document might
exist).
4. Go to LIKP, pass VBRP-VGBEL and pick LIKP-WADAT_IST.
5. Pick VBRP-AUBEL and pass it in VBKD, pick BSTKD and BSTKD.
6. The Customer details are picked up from table KNA1 by passing the Customer code VBRK-KUNNR to
get the address details (refer attached excel).
7. Leave Transporter destination, LR/RR/CR/GR/No. and weight /no. of packages etc blank.(for manual
entries).
8. Go to VBRK, Pick VBRK-KNUMV (Document Condition) and pass it to table KONV to pick the KONV-
KSCHL and POSNR.
9. Pick the Condition types as mentioned in Excel for each POSNR.
CREATION DATE: LAST UPDATE: PRINTED: File
14/07/2006 14/07/2006 AUTHOR: MANOHAR REDDDY
IESL Confidential
Document ID : Invoice Layout Project Connect PAGE 10 OF 14
DESCRIPTION: INVOICE LAYOUT MODULE: SD
10. Now for the Billing Document, for the given POSNR, in VBRP, Pick VBRP-MATNR and ARKTX.
11. The text data has to be displayed as shown in the Invoice Format (plant wise).
12. When the KONV-KSCHL= “ZVAT” or “ZIN2”, the VAT Column in the Tax Invoice will be changed
correspondingly as VAT or LST.
4.8. Dependencies
Mapping Details
ID Field Description Type Length Default Mandatory Error Matc Add. criteria Reference
value (Mark X) Check h code field
(Mark X)