Sapscript SAPScript BillOfLading Documentnt v1.0

SAP Implementation Of PIL
SAP Script Functional Specification
Note: As this is a case study that simulates a real life development object, some fields will be marked as
TBD and highlighted in Blue. These fields should be having real values, in customer development
specifications.
Functional Specification SAP Script

Bill of Lading
Document Reference:
Version:
Document Status:
TBD
v1.0
Signed off
Author:
Jitendra Guha Neogi
Last Revision Date:

Date Created:
Date Printed:
19-Dec-2006
19-Dec-2006
19-Dec-2006
BillOfLading_Document_v1.0
19-Dec-2006
<Page 1 of 33>
Document Control
Business Area
Bill of Lading
GAP ID
TBD
FS Definition Form ID
TBD
SAP R/3 Version
ECC 5.0
Location / Site
TBD
Approval and Distribution

Approved by
Process Team
Lead
Development
Team Lead
Name
TBD
Role
TBD
Signature
TBD
Date
TBD
TBD
TBD
TBD
TBD
Document History
Version
1.0
1.1
1.2
1.3
Reason for change

Initial Version
Date
19.12.2006
19-Dec-2006
<Page 2 of 33 >
Table of Contents
1.
2.
3.
4.
4.1
4.2
4.3
4.4
5.
6.
7.
4.2
8.
9.
10.
11.
12.
13.
GENERAL INFORMATION..................................................................................................................................................................4
BUSINESS NEEDS & REQUIREMENTS................................................................................................................................................5
ISSUES...........................................................................................................................................................................................6
SAP SCRIPT/FORMS.......................................................................................................................................................................7
CURRENT FUNCTIONALITY...............................................................................................................................................................7
PRINTING EXISTING SOLUTION.........................................................................................................................................................7
DESIRED FUNCTIONALITY................................................................................................................................................................7
CUSTOMIZING REQUIREMENTS.........................................................................................................................................................7
FORM LAYOUT................................................................................................................................................................................8
TECHNICAL DETAILS......................................................................................................................................................................13
LAYOUT WINDOWS.........................................................................................................................................................................13
FIELD MAPPING............................................................................................................................................................................13
STANDARDS TEXTS/TEXT MODULES...............................................................................................................................................30
TRANSLATION...............................................................................................................................................................................30
LAYOUT DETAIL.............................................................................................................................................................................30
CUSTOM TABLES/STRUCTURE IN SAP............................................................................................................................................32
ASSUMPTIONS..............................................................................................................................................................................33
ERROR HANDLING.........................................................................................................................................................................33
LANGUAGE OF TEXTS....................................................................................................................................................................33
TESTING SCENARIOS.....................................................................................................................................................................33
19-Dec-2006
<Page 3 of 33 >
1. General Information
AREA (SAP SYSTEM
COMPONENTS):
Short description:
SD
REQUESTED BY:
Date:
15.11.2006
TBD
Tel no:
TBD
AUTHOR:
Program Transaction code:
Task ID/Demand Number:
Jitendra Guha Neogi
Tel no:
TBD
Project Name:
SAP Implementation at PIL
Bill of Lading
SAP Script
TBD
Complexity:
High/mandatory
Low/optional
High
Volume of data:
Medium
Priority:
Mode:
Frequency:
Technical information:
1. Layout created using:
General information:
1. Results if no conversions
are created:
DURATION OF
WORK
Medium/recommended
Medium
Low
DATE AVAILABLE
TBD
FROM:
Online
Background
Daily
Weekly
Monthly
Biweekly
Others (Specify) :
Sapcript
Smartform
Subroutine pool
Text Elements
Standard Texts
Text Id
Print Program
Legal requirements not fulfilled
Lack of essential business information
Lack of functions compared to legacy system
Others (Specify):
DEVELOPMENT
(IN MAN-DAYS):
Is there an alternative in the
standard system?
Description of alternative:
Reasons why alternative is
not acceptable:
12 Days
Yes
No
Performance problems
Others (Specify) :
19-Dec-2006
Complexity
<Page 4 of 33 >
2. Business Needs & Requirements

Power India Limited started its operation in the year 1965. From its humble beginning in a small
town of Maharashtra called Ranjangaon PIL has achieved several milestones and today it is one
of the largest manufactures of storage batteries in India. Currently the company is having seven
production facilities in India namely Ranjangaon, Pune, Nashik, Chennai, Hosur, Gurgaon and
Durgapur respectively.
Power India Limited, the flagship company of the Oscar group is the market leader in the storage
battery industry. It manufactures wide range of batteries from 2 Ah capacities to 10500 Ah to
cover the broadest spectrum of applications.
The SAP Implementation at Power India Limited (PIL) will achieve the following:
1. Standardize and streamline the business process
2. Establishing an Integrated information repository
3. Improvement in the area of Planning
4. Complete visibility of stock
The Bill of Lading (or Manifest) is an output that is produced once a Shipment document
reaches the COMPLETED stage.
The Bill of Lading contains
The Carrier name & address details
The dispatch office details
Identifying information related to the shipment
Shipment Number
Shipment Date
Truck Registration number
Textual information contained on the shipment header
Information related to each of the deliveries on the shipment
Stop number
Name of the ship to company
Address of the Ship To location
Route
Weight
Volume
Pallet Count
Any general delivery instructions
Text notes to the agent or carrier
Text notes containing driver information
19-Dec-2006
<Page 5 of 33 >
3. Issues
None
Issue
#
Issue
owner
Date
Raised
Issue Description
19-Dec-2006
Issue Resolution
Resolved
By & Date
<Page 6 of 33 >
4. SAP Script/Forms
4.1
Current Functionality
Output type
Program Name
Layout Form Name
IMG path to access output type
and layout set assignment
Type of solution (Standard R/3,

custom ABAP)
4.2
Printing Existing Solution
Menu Path for transaction:

Values to be used and output
type:
Actions to be taken:
4.3
VT01N/ VT02N
Output Type CMR1
Desired Functionality
Output type(s):
Form Types:
Transmission medium:
Legal requirements:
Type of printer:
Paper Size:
Orientation: Portrait/Landscape:
Special stationary to be used:
4.4
CMR1
RVADTR01
SD_SHIPMENT_CMR
IMG Logistics Logistics Execution Transportation
Basic Transportation Functions Output Control Maintain
Output Determination for Shipments Maintain Output
Types.
R/3
ZBOL
CRM Bill of Lading
Print
Letter A4: 8 x 11
Portrait
Will be printed on plain white paper.
Customizing requirements
The functional consultant will customize the following output types:

Output type
Program Name
Layout Form Names
Development system
ZBOL
The standard SAP program RVADTR01 has to be copied to the
program ZRVPAF_ RVADTR01.
The layout set name is ZRV_BOL_SHIPMENT. The additional
data needed by the Layout, are got from subroutines present in a
new custom program ZRVPAF_ RVADTR01_ROUTINE.
TBD
19-Dec-2006
<Page 7 of 33 >
5. Form Layout
Refer to the following for an output samples for Window mapping, Label Description and Field
mapping.
C:\Documents and
Settings\Administrator\Desktop\Fast Trak Case Study\BOL Layout Document v1.doc
Position Field Name
Output Notes
Length
SAP Technical Ref.

Field
99a
Company Logo
Fixed text
99b
Quality Logo
Fixed text
99c
ABN Text
Fixed text
99d
Reprint Label
If this output has been

Reprint
produced before from this
shipment, the REPRINT
label should be printed.
Supress label on first
printing of the output.
Carrier Name
40
NAME1
23
Carrier Street
Number
10
HOUSE_NUM1
40
Carrier Street
60
STREET
24
Carrier Town
40
CITY1
25
Carrier State
REGION
26
Carrier Post Code
10
POST_CODE1
27
Carrier Telephone
30
TEL_NUMBER
28
Carrier Fax
30
FAX_NUMBER
TPP Name 1
40
VTTK-TPLST = V_TTDSTPLST
ADRC-NAME1
V_TTDS-ADRNR = ADRCADDRNUMBER
29
TPP Name 2
40
ADRC-NAME2
19-Dec-2006
<Page 8 of 33 >
Position Field Name
Output Notes
Length
SAP Technical Ref.

Field
40
TPP Street Number
10
ADRC-HOUSE_NUM1
30
TPP Street
60
31
TPP Town
40
ADRC-CITY1
32
TPP State
ADRC-REGION
33
TPP Post Code
10
ADRC-POST_CODE1
34
TPP PO Box
10
PO_BOX
35
TPP PO Box City
40
PO_BOX_LOC
36
TPP PO Box State
PO_BOX_REG
37
TPP PO Box Pcode
10
POST_CODE2
38
TPP Phone
30
TEL_NUMBER
39
TPP Fax
30
FAX_NUMBER
Shipment Number
10
VTTK-TKNUM
Shipment Date
VTTK- DTABF
Shipment Truck Rego 20
VTTK- SIGNI
43
Shipment Route
VTTK-ROUTE
44
Route Description
Header Text 1
Text Type Z004 assigned to

shipment VTTK-TKNUM
Header Text 2

shipment VTTK-TKNUM
10
Header Text 3

shipment VTTK-TKNUM
12
Drop
For each VTTP where VTTPTKNUM = VTTK-TKNUM
VTTP-TPNUM
42
Delivery Number
For each VTTP where VTTPTKNUM = VTTK-TKNUM
VTTP-VBELN
13
Name
Look-up delivery (LIKP) using

VTTK-VBELN
ADRC-NAME1
If necessary, wrap the

ADRC-STREET
address within the output
window.
40
Customer number is LIKP-KUNNR

Look up KNA1 where KNA1KUNNR = LIPS-KUNNR
19-Dec-2006
<Page 9 of 33 >
Position Field Name
Output Notes
Length
SAP Technical Ref.

Field
Look up VBPA where VBELN =

LIKP-VBELN and PARVW = SH
Look up ADRC where ADRCADRNR = VBPA-ADRNR
45
Customer Street
Number
10
As per 13
ADRC-HOUSE_NUM1
46
Customer Street
60
As per 13
ADRC-STREET
47
Customer City
40
As per 13
ADRC-CITY1
48
Customer State
As per 13
ADRC-REGION
49
Customer Post Code
10
As per 13
ADRC-POST_CODE1
15
Route
LIKP-ROUTE
16
Weight (KG)
5.2
LIKP-BTGEW
17
Volume (M3)
5.2
Calculating the total

volume of a delivery will
take several steps. Use
method 1, if the net
result is zero, then use
method 2
Calculated
Method 1
1. For each item on a
delivery the total delivery
volume needs to be
calculated.
Look up the Length, Width
and Height characteristics
that are recorded on a
delivery item and multiply
these to reach a Delivery
Pallet volume.
Multiply this Delivery
Pallet Volume by the
number of pallets on the
delivery. The number of
pallets on the delivery is
recorded in item 18
(COUNT VEPO where
VBELN = LIPS-VBELN and
POSNR = LIPS-POSNR)
This will give you a
19-Dec-2006
<Page 10 of 33 >
Position Field Name
Output Notes
Length
SAP Technical Ref.

Field
volume for the delivery

item (including the pallet)
2. The volume for each
item needs to be added to
reach the delivery
volume.
Method 2
SUM LIPS-VOLUM for all
items where LIPS-VBELN =
LIKP-VBELN
18
Pallet Count
The pallet Count field is

being added to LIPS as a
custom development in
EN092. At the time of
writing the field name is
not known.
COUNT VEPO where

VBELN = LIPS-VBELN and
POSNR = LIPS-POSNR
The total Pallet Count will

be the SUM of the pallet
count field for all items
(LIPS) on a delivery (LIKP)
The most accurate way to
get the pallet count will
be to count the HUMs that
contain that delivery
item. HUM's are contained
in table VEPO, in psuedocode I would express this
as follows:
COUNT VEPO where VBELN
= LIPS-VBELN and POSNR =
LIPS-POSNR
The number of pallets
equals the number of
VEPO records that share a
common delivery number
and position number as
the delivery item in
question.
41
Shipment Instruction
Text Type 0012 assigned to

delivery LIKP-VEBLN
19-Dec-2006
<Page 11 of 33 >
Position Field Name
Output Notes
Length
SAP Technical Ref.

Field
19
Agent-Carrier Notes

shipment VTTK-TKNUM
20
Driver Information

shipment VTTK-TKNUM
Note 2
Note 4
Note 5
Note 10
Note 11
Sales Order
10
VBAK-VBELN
19-Dec-2006
<Page 12 of 33 >
6. Technical Details
Layout windows
Field Mapping
Label
R/3
Field
Calculation Logic
Company
Logo
Fixed Logo
Quality
Logo
Fixed Logo
ABN Text
Fixed Text
PrintonPage
Label
Position
Font
Font Format
Couri
er
8 pt
Form Title
VEHIC
LE
MANIFE
ST
Left
Couri
er
18 pt, Bold
Reprint
REPRI
NT
Left
Couri
er
14 pt, Bold
Carrier
name
Table:
LFA1
Couri
er
10 pt
Screen:
L_CARR
IER_LF
A1_
NAME1
Getting VTTK-TDLNR
from VTTK and retrieve
the field NAME1 from
table LFA1 where LIFNR =
VTTK-TDLNR.
Pass the retrieved field
back to the layout using
L_ CARRIER_LFA1_
NAME1.
This
will
appear
only in
the
first
page
19-Dec-2006
<Page 13 of 33 >
Carrier
Street
Name
Carrier
Street
Table:
ADRC
Screen:
L_
CARRIE
R_ADR
C_HOU
SE_NU
M1
Table:
ADRC
Screen:
L_
CARRIE
R_ADR
C_STRE
ET
Getting VTTK-TDLNR
LFA1 where LIFNR =
VTTK-TDLNR.
Get the field
HOUSE_NUM1 from ADRC
where ADDRNUMBER =
LFA1- ADRNR
This
will
appear
only in
the
first
page
Couri
er
10 pt
This
will
appear
only in
the
first
page
Couri
er
10 pt
This
will
appear
only in
the
first
page
Couri
er
10 pt

L_ CARRIER_ADRC_
HOUSE_NUM1.
Getting VTTK-TDLNR
LFA1 where LIFNR =
VTTK-TDLNR.
Get the field STREET
from ADRC where
ADDRNUMBER = LFA1ADRNR
L_ CARRIER_ADRC_
STREET.
Carrier
Town
Table:
ADRC
Screen:
L_
CARRIE
R_ADR
C_
CITY1
Getting VTTK-TDLNR
LFA1 where LIFNR =
VTTK-TDLNR.
Get the field CITY1 from
ADRC where
L_ CARRIER_ADRC_
CITY1.
19-Dec-2006
<Page 14 of 33 >
Carrier
State
Table:
ADRC
Screen:
L_
CARRIE
R_ADR
C_
REGION
Getting VTTK-TDLNR
LFA1 where LIFNR =
VTTK-TDLNR.
Get the field REGION
from ADRC where
This
will
appear
only in
the
first
page
Couri
er
10 pt
This
will
appear
only in
the
first
page
Couri
er
10 pt
This
will
appear
only in
the
first
page
Couri
er
10 pt

L_ADRC_ REGION1.
Carrier
Post Code
Table:
ADRC
Screen:
L_
CARRIE
R_ADR
C_POST
_CODE
1
Carrier
telephone
Table:
ADRC
Screen:
L_
CARRIE
R_ADR
C_
TEL_N
UMBER
Getting VTTK-TDLNR
LFA1 where LIFNR =
VTTK-TDLNR.
Get the field
POST_CODE1 from ADRC
where ADDRNUMBER =
LFA1- ADRNR
L_ CARRIER_ADRC_
POST_CODE1.
Getting VTTK-TDLNR
LFA1 where LIFNR =
VTTK-TDLNR.
Get the field
TEL_NUMBER from ADRC
where ADDRNUMBER =
LFA1- ADRNR
L_ CARRIER_ADRC_
TEL_NUMBER.
19-Dec-2006
<Page 15 of 33 >
Carrier Fax
Table:
ADRC
Screen:
L_
CARRIE
R_ADR
C_
FAX_NU
MBER
TPP
Name1
Table:
ADRC
Screen:
L_DISP
_ADRC
_NAME
1
Getting VTTK-TDLNR
LFA1 where LIFNR =
VTTK-TDLNR.
Get the field
FAX_NUMBER from ADRC
where ADDRNUMBER =
LFA1- ADRNR
This
will
appear
only in
the
first
page
Couri
er
10 pt
This
will
appear
only in
the
first
page
Couri
er
10 pt
This
will
appear
only in
the
first
page
Couri
er
10 pt

L_ CARRIER_ADRC_
FAX_NUMBER.
Getting VTTK-TPLST from
VTTK for Transportation
Planning Point and
retrieve from V_TTDS
where TPLST = VTTKTPLST.
Get the field NAME1 from
ADRC where
ADDRNUMBER = V_TTDS
ADRNR
L_DISP_ADRC_ NAME1.
TPP
Name2
Table:
ADRC
Screen:
L_DISP
_ADRC
_
NAME2

Planning Point and
ADRC where
ADDRNUMBER = V_TTDS
ADRNR
L_DISP_ADRC_ NAME2.
19-Dec-2006
<Page 16 of 33 >
TPP Street
Number
Table:
ADRC
Screen:
L_DISP
_ADRC
_
HOUSE
_NUM1

Planning Point and
ADRC where
ADDRNUMBER = V_TTDS
ADRNR
This
will
appear
only in
the
first
page
Couri
er
10 pt
This
will
appear
only in
the
first
page
Couri
er
10 pt
This
will
appear
only in
the
first
page
Couri
er
10 pt

L_DISP_ADRC_
HOUSE_NUM1.
TPP Street
Table:
ADRC
Screen:
L_DISP
_ADRC
_
STREET

Planning Point and
ADRC where
ADDRNUMBER = V_TTDS
ADRNR
L_DISP_ADRC_ STREET.
TPP Town
Table:
ADRC
Screen:
L_DISP
_ADRC
_ CITY1

Planning Point and
ADRC where
ADDRNUMBER = V_TTDS
ADRNR
L_DISP_ADRC_ CITY1.
19-Dec-2006
<Page 17 of 33 >
TPP State
Table:
ADRC
Screen:
L_DISP
_ADRC
_
REGION

Planning Point and
ADRC where
ADDRNUMBER = V_TTDS
ADRNR
This
will
appear
only in
the
first
page
Couri
er
10 pt
This
will
appear
only in
the
first
page
Couri
er
10 pt
This
will
appear
only in
the
first
page
Couri
er
10 pt

L_DISP_ADRC_ REGION.
TPP Post
Code
Table:
ADRC
Screen:
L_DISP
_ADRC
_
POST_C
ODE1

Planning Point and
ADRC where
ADDRNUMBER = V_TTDS
ADRNR
L_DISP_ADRC_
POST_CODE1.
TPP PO
Box
Table:
ADRC
Screen:
L_DISP
_ADRC
_
PO_BO
X

Planning Point and
ADRC where
ADDRNUMBER = V_TTDS
ADRNR
L_DISP_ADRC_ PO_BOX.
19-Dec-2006
<Page 18 of 33 >
TPP PO
Box City
Table:
ADRC
Screen:
L_DISP
_ADRC
_
PO_BO
X_LOC

Planning Point and
ADRC where
ADDRNUMBER = V_TTDS
ADRNR
This
will
appear
only in
the
first
page
Couri
er
10 pt
This
will
appear
only in
the
first
page
Couri
er
10 pt
This
will
appear
only in
the
first
page
Couri
er
10 pt

L_DISP_ADRC_
PO_BOX_LOC.
TPP PO
Box State
Table:
ADRC
Screen:
L_DISP
_ADRC
_
PO_BO
X_REG

Planning Point and
ADRC where
ADDRNUMBER = V_TTDS
ADRNR
L_DISP_ADRC_PO_BOX_R
EG .
TPP PO
Box Pcode
Table:
ADRC
Screen:
L_DISP
_ADRC
_
POST_C
ODE2

Planning Point and
ADRC where
ADDRNUMBER = V_TTDS
ADRNR
L_DISP_ADRC_
POST_CODE2.
19-Dec-2006
<Page 19 of 33 >
TPP Phone
Table:
ADRC
Screen:
L_DISP
_ADRC
_
TEL_N
UMBER

Planning Point and
This
will
appear
only in
the
first
page
Couri
er
10 pt
This
will
appear
only in
the
first
page
Couri
er
10 pt
Getting VTTK-TKNUM
from VTTK and Pass the
retrieved field back to
the layout using
L_VTTK_TKNUM.
This
will
appear
only in
the
first
page
Couri
er
10 pt
Getting VTTK-DTABF
the layout using
L_VTTK_DTABF.
This
will
appear
only in
the
first
page
Couri
er
10 pt

ADRC where
ADDRNUMBER = V_TTDS
ADRNR
L_DISP_ADRC_
TEL_NUMBER.
TPP Fax
Table:
ADRC
Screen:
L_DISP
_ADRC
_
FAX_NU
MBER

Planning Point and
ADRC where
ADDRNUMBER = V_TTDS
ADRNR
L_DISP_ADRC_
FAX_NUMBER.
Shipment
Number
Table:
VTTK
Screen:
L_VTTK
_
TKNUM
Shipment
Date
Table:
VTTK
Screen:
L_VTTK
_
DTABF
19-Dec-2006
<Page 20 of 33 >
Shipment
Truck Rego
Table:
VTTK
Screen:
L_VTTK
_ SIGNI
Shipment
Route
Table:
VTTK
Screen:
L_VTTK
_
ROUTE
Route
Descriptio
n
Table:
TVRO
Screen:
L_TVR
O_
ROUTID
Getting VTTK-SIGNI from

VTTK and Pass the
the layout using
L_VTTK_SIGNI.
This
will
appear
only in
the
first
page
Couri
er
10 pt
Getting VTTK-ROUTE
the layout using
L_VTTK_ROUTE.
This
will
appear
only in
the
first
page
Couri
er
10 pt
Getting VTTK-ROUTE
the field ROUTID from
TVRO where ROUTE =
VTTK-ROUTE.
This
will
appear
only in
the
first
page
Couri
er
10 pt

L_TVRO_ROUTID.
Header
Text 1
The Function Module

READ_TEXT is used with
the Import parameters as
Object (VTTK-TKNUM),
Name (Shipment
Number), and ID as Z004
This
will
appear
only in
the
first
page
Couri
er
10 pt
Header
Text 2
The Function Module

Name (Shipment
This
will
appear
only in
the
first
page
Couri
er
10 pt
Header
Text 3
The Function Module

Name (Shipment
This
will
appear
only in
the
first
page
Couri
er
10 pt
19-Dec-2006
<Page 21 of 33 >
Shipment
Item
(Drop)
Delivery
Number
Table:
VTTP
Screen:
L_VTTP
_
TPNUM
Table:
VTTP
Screen:
L_VTTP
_
VBELN
Getting VTTK-TKNUM
the field TPNUM from
VTTP where TKNUM =
VTTK-TKNUM.
L_VTTP_TPNUM.
Getting VTTK-TKNUM
the field VBELN from
VTTP where TKNUM =
VTTK-TKNUM.
L_VTTP_VBELN.
This
will
appear
in the
first
page
and
also in
the
conseq
uent
pages
if page
overflo
w
occurs
Couri
er
10 pt
This
will
appear
in the
first
page
and
also in
the
conseq
uent
pages
if page
overflo
w
occurs
Couri
er
10 pt
19-Dec-2006
<Page 22 of 33 >
Customer
Name
Table:
ADRC
Screen:
L_ADRC
_
NAME1
Getting VTTP-TKNUM
from VTTP and retrieve
from VTTP where TKNUM
= VTTK-TKNUM and
further from LIKP where
VBELN = VTTP-VBELN.
Then get from KNA1
where KUNNR = LIKP
KUNNR and get the field
NAME1 from ADRC where
ADDRNUMBER = KNA1ADRNR.
L_ADRC_NAME1.
Customer
Street
Number
Table:
ADRC
Screen:
L_ADRC
_
HOUSE
_NUM1
Getting VTTP-TKNUM
= VTTK-TKNUM and
VBELN = VTTP-VBELN.
Then get from KNA1
where KUNNR = LIKP
L_ADRC_HOUSE_NUM1.
This
will
appear
in the
first
page
and
also in
the
conseq
uent
pages
if page
overflo
w
occurs
Couri
er
10 pt
This
will
appear
in the
first
page
and
also in
the
conseq
uent
pages
if page
overflo
w
occurs
Couri
er
10 pt
19-Dec-2006
<Page 23 of 33 >
Customer
Street
Table:
ADRC
Screen:
L_ADRC
_
STREET
Getting VTTP-TKNUM
= VTTK-TKNUM and
VBELN = VTTP-VBELN.
Then get from KNA1
where KUNNR = LIKP
L_ADRC_STREET.
Customer
City
Table:
ADRC
Screen:
L_ADRC
_ CITY1
Getting VTTP-TKNUM
= VTTK-TKNUM and
VBELN = VTTP-VBELN.
Then get from KNA1
where KUNNR = LIKP
L_ADRC_CITY1.
This
will
appear
in the
first
page
and
also in
the
conseq
uent
pages
if page
overflo
w
occurs
Couri
er
10 pt
This
will
appear
in the
first
page
and
also in
the
conseq
uent
pages
if page
overflo
w
occurs
Couri
er
10 pt
19-Dec-2006
<Page 24 of 33 >
Customer
State
Table:
ADRC
Screen:
L_ADRC
_
REGION
Getting VTTP-TKNUM
= VTTK-TKNUM and
VBELN = VTTP-VBELN.
Then get from KNA1
where KUNNR = LIKP
L_ADRC_REGION.
Customer
Post Code
Table:
ADRC
Screen:
L_ADRC
_
POST_C
ODE1
Getting VTTP-TKNUM
= VTTK-TKNUM and
VBELN = VTTP-VBELN.
Then get from KNA1
where KUNNR = LIKP
L_ADRC_POST_CODE1.
This
will
appear
in the
first
page
and
also in
the
conseq
uent
pages
if page
overflo
w
occurs
Couri
er
10 pt
This
will
appear
in the
first
page
and
also in
the
conseq
uent
pages
if page
overflo
w
occurs
Couri
er
10 pt
19-Dec-2006
<Page 25 of 33 >
Route
Table:
LIKP
Screen:
L_LIKP
_ Route
Getting VTTP-TKNUM
= VTTK-TKNUM and
VBELN = VTTP-VBELN.
Then get from KNA1
where KUNNR = LIKP
L_ADRC_ROUTE.
Weight
Table:
LIKP
Screen:
L_LIKP
_
BTGEW
Getting VTTP-TKNUM
= VTTK-TKNUM and
VBELN = VTTP-VBELN.
L_LIKP_BTGEW.
This
will
appear
in the
first
page
and
also in
the
conseq
uent
pages
if page
overflo
w
occurs
Couri
er
10 pt
This
will
appear
in the
first
page
and
also in
the
conseq
uent
pages
if page
overflo
w
occurs
Couri
er
10 pt
19-Dec-2006
<Page 26 of 33 >
Volume
Screen:
L_VOL
UME
For each item on a

delivery the total
delivery volume needs to
be calculated.
Look up the Length,
Width and Height
characteristics that are
recorded on a delivery
item and multiply these
to reach a Delivery Pallet
volume.
Multiply this Delivery
Pallet Volume by the
number of pallets on the
delivery.
This
will
appear
in the
first
page
and
also in
the
conseq
uent
pages
if page
overflo
w
occurs
Couri
er
10 pt
This
will
appear
in the
first
page
and
also in
the
conseq
uent
pages
if page
overflo
w
occurs
Couri
er
10 pt
This will give you a

volume for the delivery
item (including the
pallet)
The volume for each
item needs to be added
to reach the delivery
volume.
Pallet
Count
Screen:
L_PALL
ET_CO
UNT
The total Pallet Count

will be the SUM of the
pallet count field for all
items (LIPS) on a delivery
(LIKP)
19-Dec-2006
<Page 27 of 33 >
Shipment
Instruction
Screen:
L_SHIP
_INST
The Function Module

Object (LIKP-VELN),
Name (Delivery Number),
and ID as 0012
This
will
appear
in the
first
page
and
also in
the
conseq
uent
pages
if page
overflo
w
occurs
Couri
er
10 pt
AgentCarrier
Notes
Screen:
L_AGE
NT_NO
TES
The Function Module

Name (Shipment
This
will
appear
in the
first
page
and
also in
the
conseq
uent
pages
if page
overflo
w
occurs
Couri
er
10 pt
19-Dec-2006
<Page 28 of 33 >
Driver
Informatio
n
Screen:
L_DRIV
ER_INF
O
The Function Module

Name (Shipment
This
will
appear
in the
first
page
and
also in
the
conseq
uent
pages
if page
overflo
w
occurs
Couri
er
10 pt
Note A:
If this field has to be calculated from some other field then please provide the detailed
logic with an example. If you think there is logic behind this field provide the information here.
Note B:
Provide the information like
This field will appear in all the pages
This will appear only in the first page
This will not appear in first page but will appear on every other page
Note C:
If the position of this field on Paper is important then specify this measure here along
with the unit
Note D:
Helvetia (H) or Times (T)
Note E:
Bold (B), Italics (I), Underlined (U). Also size, such as 10, 11, 12, etc.
Note F: Special formatting requirements (eg.: do not display leading zeroes, date format
YYYYMMDD)
19-Dec-2006
<Page 29 of 33 >
7. Standards Texts/Text Modules
4.2
Translation
No Translation required. If some translation needs to be done then we can translate the standard texts
through SE63 transaction and by providing the source and destination language.
Reference
Description of use
(in Language1)
Description of use
(in Language2)
Description of use
(in Language3)
NA
NA
NA
NA
Text
module
Name
NA
Notes
NA
8. Layout Detail
Position of Left Margin
(Specify Unit)
0.5 CM from Left border
Position of Right Margin

(Specify Unit)
0.5 CM from right border
Position of Logo
(Specify Unit)
0.5 CM from the top Within HEADER WINDOW
Position of Logo1
0.5 CM from the top Within HEADER WINDOW
Position of MAIN Window

(Specify Unit)
Left Margin: 0.5 CM
Window Width: 25.7 CM
Upper Margin: 10.0 CM
Window Height: 7.9 CM
Position of CARRIER
Window
Left Margin: 0.5 CM
Position of DISPATCH
Window
Left Margin: 9.1 CM
Position of SHIPMENT
Window
Left Margin: 17.5 CM
Position of FOOTER1
Window
Left Margin: 0.5 CM
Position of FOOTER2
Window
Left Margin: 13.2 CM
Position of INFO Window
Left Margin: 0.5 CM
19-Dec-2006
<Page 30 of 33 >
19-Dec-2006
<Page 31 of 33 >
9. Custom Tables/Structure in SAP

No Such Custom Tables required.
Table Name
Short text
Size category
Table maintenance
allowed
Data class
Buffering
Table maintenance
generator
Authorization Group
Field
Data
Name
Element
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA
Domain Type
NA
Length Check
TableField
NA
NA
Key
Field
Foreign Description
Key
NA
NA
NA
Comments
19-Dec-2006
<Page 32 of 33 >
10. Assumptions
11. Error Handling
None
12. Language of texts

English EN.
13. Testing Scenarios

Normal Functionality - test cases that ensure the report functions as it should.
ID Description
1
The Proforma invoice layout with all the header and item details would be displayed.
2
3
4
Exception - special logic or exceptions (e.g. report should exclude certain specific condition)
5
6
Error Handling - functionality in case of errors (e.g. Error Message or Error Log )
7
19-Dec-2006
<Page 33 of 33 >

Sapscript SAPScript BillOfLading Documentnt v1.0

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Sapscript SAPScript BillOfLading Documentnt v1.0

Caricato da

Copyright:

Formati disponibili

SAP Implementation Of PIL

SAP Script Functional Specification

Functional Specification SAP Script

Jitendra Guha Neogi

Last Revision Date:

SAP Implementation Of PIL

SAP Script Functional Specification

SAP R/3 Version

Approval and Distribution

Reason for change

SAP Implementation Of PIL

SAP Script Functional Specification

SAP Implementation Of PIL

SAP Script Functional Specification

Jitendra Guha Neogi

SAP Implementation at PIL

SAP Implementation Of PIL

SAP Script Functional Specification

2. Business Needs & Requirements

SAP Implementation Of PIL

SAP Script Functional Specification

SAP Implementation Of PIL

SAP Script Functional Specification

Type of solution (Standard R/3,

Printing Existing Solution

Menu Path for transaction:

The functional consultant will customize the following output types:

SAP Implementation Of PIL

SAP Script Functional Specification

Position Field Name

SAP Technical Ref.

If this output has been

Carrier Post Code

SAP Implementation Of PIL

SAP Script Functional Specification

Position Field Name

SAP Technical Ref.

TPP Street Number

TPP Post Code

TPP PO Box City

TPP PO Box State

TPP PO Box Pcode

Shipment Truck Rego 20

Text Type Z004 assigned to

Text Type Z005 assigned to

Text Type Z006 assigned to

For each VTTP where VTTPTKNUM = VTTK-TKNUM

For each VTTP where VTTPTKNUM = VTTK-TKNUM

Look-up delivery (LIKP) using

If necessary, wrap the

Customer number is LIKP-KUNNR

SAP Implementation Of PIL

SAP Script Functional Specification

Position Field Name

SAP Technical Ref.

Look up VBPA where VBELN =

Customer Post Code

Calculating the total

SAP Implementation Of PIL

SAP Script Functional Specification

Position Field Name

SAP Technical Ref.

volume for the delivery