FUNCTIONAL SPECIFICATION – BILL OF LADING

PROJECT IDENTIFICATION DETAILS

Project Name Customer Number Project Start Date

RDS Implementation using

A2O Methodology 28-Oct-13 30-May-14
PMIS Code GD Regional Delivery Head GD Project Manager

PR13_003602 Amarnath Jayaraman Bhupendra Bahadur Singh

GD QC Member GD QA Lead SAP Subsidiary Name

Chendil Kumar Amit Singh SAP North America

DOCUMENT REVISION, REVIEW, & APPROVAL HISTORY

VER DATE AUTHOR REVIEWER/APPROVER REMARKS

1.0 24th Jan 14 B.Hari Kumar Draft Version

2.0 29th Jan 14 Christina Brink

2.1 June 4th, 2014 Grace Laut Defect 326 - VERP

Logic
Functional Specification_ F_OTC-005_Bill Of Loading Page 2 of 15

Table of contents
1. Program Summary...................................................................................................................3
1.1. Program Control Delivery Sheet................................................................................................3
2. Functional Description............................................................................................................4
3. Assumptions............................................................................................................................4
4. Processing Type......................................................................................................................4
5. Functional Design....................................................................................................................4
6. Authorization Requirements..................................................................................................4
6.1. Definition....................................................................................................................................4
6.2. Defined Fields............................................................................................................................4
6.3. Procedure..................................................................................................................................4
7. Process Flow Diagram............................................................................................................5
8. SAP Transaction......................................................................................................................5
9. Form Layout.............................................................................................................................5
10. Printer Requirements..............................................................................................................5
11. Legal Requirements................................................................................................................5
12. Form Fields...............................................................................................................................6
12.1. Sub Heading...........................................................................................................................6
12.2. Totaling...................................................................................................................................6
12.3. Sorting....................................................................................................................................6
12.4. Page Breaks...........................................................................................................................6
12.5. Stationery...............................................................................................................................6
12.6. Logo(s)...................................................................................................................................6
12.7. Bar Coding Requirements......................................................................................................6
12.8. Configuration Dependencies..................................................................................................7
13. Existing Sample Forms...........................................................................................................7
14. Assumptions in Functional Design.......................................................................................7
15. Open Issues in Functional Design.........................................................................................7
16. Business Test Conditions (Functional Consultant).............................................................7
17. Related Documentation (Attach Notes, emails, existing report, etc.)................................7
18. Appendix....................................................................................................................................7

2
Functional Specification_ F_OTC-005_Bill Of Loading Page 3 of 15

1. Program Summary
1.1. Program Control Delivery Sheet

OBJECT OVERVIEW
Business
Object ID F-OtC-005 Bill Of Lading
Process
Object Description BILL OF LADING

SAP Release SAP Module OTC

Required
Cycle of Testing Development
Completion Date

Complexity of Object Form run

Layout set / Smart

Form Type Priority
forms / Adobe / Labels
Volume Frequency

PDF Version Fax

Yes No
Required Requirements
SAP Transaction
Email Requirements Yes VL01N,VL02N,VL03N
and Menu Path
FS CONTROL

Planned Date of FS 1/24/2014 Actual Date of FS

Completion Completion

FS Approved By FS Approval date

Other Contact
Other Contact and
and Phone
Phone Number
Number

3
Functional Specification_ F_OTC-005_Bill Of Loading Page 4 of 15

2. Functional Description
The BOL will be provided to truck drivers at time of shipment to sign and take with them to the next
destination. The BOL lists the materials and ship-to information required to get the product to the appropriate
place.

Two output types will need to be created for the BOL. One that allows batches to be displayed and one that
does NOT allow batches to be displayed.

3. Assumptions
The output is printed in Letter size on blank stationary. For go-live the output will be printed via the users
local printer (LOCL) however,

4. Processing Type
The output type will be executed in the Real time after saving the Delivery document.

5. Functional Design
The bill of lading will use the standard BOL output type – YBL1  this one will show batches
ZBL1 – output type must NOT show batches.

Only Delta changes to the standard form will be shown below.

Logic: Table and Fields are provided below.

4
Functional Specification_ F_OTC-005_Bill Of Loading Page 5 of 15

5
Functional Specification_ F_OTC-005_Bill Of Loading Page 6 of 15

Srl Field Description Table-Field YBL1 Logic Logic to appear or not

No to appear

Green dotted line Please note that the green

dotted line corresponds with
what should appear on each
additional page of the output.
Thanks!

1. Company Address Standard logic that form

already uses

2. Page 1 of 1 the total page the total page numbers and

numbers and current page number to appear
current page at top of the page.
number to appear
at top of the page.

2.a Bill Of Lading Hardcode the Text Hardcode the Text If more than 1 sales
order number (VGBEL)
exists in the delivery,
then the title should
display “Master Bill Of
Lading”

3. Ship to Party Hardcode the Text Hardcode the Text

3.a Customer Number VBPA_VBELN Pass the VBELN and

PARVW=WE into the table
VBPA and get the KUNNR

3.b Tax ID when it is required KNA1- STCD1 or First look for STCEG – if value
KNA1- STCEG is maintained then print the
where PARVW = value with “VAT Reg:” before it.
SH(WE) If no value is maintained in
STCEG, then look at STCD1. If
no value is maintained –
suppress the field. If a value is
maintained, Use Z-table below
to maintain the correct Tax title
before the value of the field

4. BOL Number LIKP – BOLNR Pass the VBELN into the table
LIKP and get the BOLNR

4.a P.O Number LIPS-VGBEL Pass the VBELN into the table
LIPS and get the VGBEL and
pass the VGBEL into the table
VBKD and get the BSTDK.
If more than 1 sales
order number (VGBEL)
exists in the delivery,
then this field should
just display “See Below”
so the PO is displayed

6
Functional Specification_ F_OTC-005_Bill Of Loading Page 7 of 15

at line item level

instead.

4.b Ref order Number LIPS-VGBEL Pass the VBELN into the table If more than 1 sales
LIPS and get the VGBEL order number (VGBEL)
exists in the delivery,
then this field should
just display “See Below”
so the Sales order # is
displayed at line item
level instead.

4.c Ship Date LIKP- WADAT_IST Pass the VBELN into the table
LIKP and get the WADAT_IST

4.c Delivery Date LIKP-LFDAT Pass the VBELN into the table
part LIKP and get the LFDAT
2

4.d Freight term Add this logic within Find LIKP-INCO1 and print the
the form value (or suppress the row)
based on what appears in 2nd
column:
LIKP-
INC01 Output_display
EXW Collect
FOB Collect
AIR Suppress Row
DHL Suppress Row
EMY Suppress Row
FED Suppress Row
FH Suppress Row
UN Suppress Row
UPS Suppress Row
USP Suppress Row
CFR Prepaid
CIF Prepaid
CIP Prepaid
CPT Prepaid
DAF Prepaid
DDP Prepaid
DDU Prepaid
DEQ Prepaid
DES Prepaid
FAS Prepaid

7
Functional Specification_ F_OTC-005_Bill Of Loading
FCA Prepaid
4.e Inco terms LIKP-INC01 Pass the VBELN into the table
&INC02 LIKP and get the INC01 &
INC02
4.f Carrier VBPA-KUNNR Pass the LIKP- VBELN into the
table VBPA –PARVW=CR and
get the KUNNR pass the
KUNNR into LFA1 and get the
NAME1
4.g Pro No LIKP-TRAID Pass the VBELN into the table
LIKP and get the TRAID
5 Export Details Hardcode the Text Hard code the text
5.a Vessel Name VTTK-EXTI2 Pass LIKP-VBELN in to VTTP-
VBELN and get TKNUM, pass
VTTP-TKNUM into VTTK-
TKNUM and get VTTK-EXTI2
5.b Last Rec date VTTK- DPLEN Pass the VBELN into the table
VTTP and get VTTP-TKNUM
and pass in to VTTK-TKNUM
and get DPLEN
5.c Est Time of ship – Please VTTK-DPTBG Pass the VBELN into the table
change this title to Est VTTP and get VTTP-TKNUM
Time of Departure and pass in to VTTK-TKNUM
and get DPTBG
5.d Est Time of arrival VTTK- DPTEN Pass the VBELN into the table
VTTP and get VTTP-TKNUM
and pass in to VTTK-TKNUM
and get DPTEN
5.e Ocean Booking No VTTK-EXTI1 Pass the VBELN into the table
VTTP and get VTTP-TKNUM
and pass in to VTTK-TKNUM
8
Page 8 of 15
If not maintained, leave
blank and remove row
If not maintained, leave
blank and remove row
VERY IMPORTANT - If
no values for the
fields in this section
are found, the remove
the entire box and
move lines up./ Export
details window as if
no value is there for
fields only the outline
will be shown in
output
If not maintained, leave
blank and remove row
If not maintained, leave
blank and remove row
If not maintained, leave
blank and remove row
If not maintained, leave
blank and remove row
If not maintained, leave
blank and remove row
Functional Specification_ F_OTC-005_Bill Of Loading Page 9 of 15

and get EXTI1

5.f Port of Discharge EIKP-ZOLLB Pass VBELN into table EIKP- If not maintained, leave
REFNR and get ZOLLB and blank and remove row
T615-BEZEI
pass into T615-ZOLLA and get
BEZEI

5.g Port of Loading EIKP-AZOLL Pass VBELN into table EIKP- If not maintained, leave
T615-BEZEI REFNR and get AZOLL. Pass blank and remove row
AZOLL to T615-ZOLLA and get
‘Export customs off’
BEZEI, TEXT2, TEXT3, TEXT4

5.h Container No. VEKP-EXIDV2 Pass VBELN into table VEKP- If not maintained, leave
VBELN_GEN and get VEKP- blank and remove row
EXIDV2

MARA_MTART = VERP Material Types

VEKP_VHILM (HU0020, HU0020R,
HU0040, HU0041)
VHART=YB04

5.i Seal No VEKP-INHALT Pass VBELN into table VEKP- If not maintained, leave
VBELN_GEN and get VEKP- blank and remove row
INHALT

6. Freight Class LIPS-MFRGR Per line pass the value

6.a Net Weight LIPS- Per line pass the value

NTGEW/GEWEI

6.b Gross Weight LIPS- Per line pass the value

BRGEW/GEWEI

6.c Material Sales Text Text ID: Z001 Delivery Item – Text
determination
Procedure: Z1

6.d Item level Text Field Text ID: Z006 Delivery Item – Text
determination
Procedure: Z1

6.e Batch logic Remember YBL1 can keep the

standard BOL logic to print
batch numbers with qty and

9
Functional Specification_ F_OTC-005_Bill Of Loading Page 10 of 15

weight. But PLEASE REMOVE

the batch expiration date lines.
Remember output ZBL1 must
NEVER display batch number
rows.

6.f Sales order/PO logic The standard logic to print

sales order and PO numbers
can remain on form for both
output types, however, please
remove the date fields

7 Volume LIKP-VOLUM/ Pass VBELN into LIKP and get

VOLEH VOLUM and VOLEH
*NOTE – please remove
the “Cubed” part and just
call it Volume

7.a Total Quantity Cumulate all the Cumulate all the line item
line item quantity’s quantity’s

7.b Total Net LIKP- Pass VBELN into LIKP and get
NTGEW/GEWEI NTGEW and GEWEI

7.c Gross LIKP- Pass VBELN into LIKP and get

BTGEW/GEWEI BTGEW and GEWEI

7.d Header text Text ID: Z100 Delivery Header – text

determination:
Text ID: Z100

New Sales Order When more than Pass the VBELN into the table We need to pull each
one order on LIPS and get the VGBEL unique sales order that
delivery exists: (see is attached to the
image below table delivery (not each SO
as example) per line, just the unique
ones)

New PO No When more than Pass the VBELN into the table We need to pull each
one order on LIPS and get the VGBEL and unique PO no. that
delivery exists: (see pass the VGBEL into the table corresponds with each
image below table VBKD and get the BSTDK. unique sales order
as example)

New Total Qty When more than Cumulate all the line item We need to pull the total
one order on quantity’s – per Sales order qty count that
delivery exists: (see corresponds with each
image below table unique sales order
as example)

10
Functional Specification_ F_OTC-005_Bill Of Loading Page 11 of 15

8. The terms and conditions S010 text object to

be created

For Master BOL – when more than one sales order is on the delivery, the “New” values above should appear in this
form at bottom of output right before the Terms and Conditions:

Sales Order PO No. Total Qty

93649302 45028460321 120 Count

93649302 45028460321 120 Count
93649302 45028460321 120 Count
93649302 45028460321 120 Count

Z-Table for Customer Tax ID number – The following table should be created to maintain the Tax ID title that should
appear before KNA1- STCD1:

KNA1-LAND1 where PARVW = partner listed in table Then Print

above.
Argentina CUIT:
Brazil CNPJ:
Chile RUT:
China VAT:
Colombia NIT:
Mexico RFC:
Peru RUC:
Taiwan GUI:
Venezuela RIF:
All Others Tax ID:

6. Authorization Requirements
N/A

6.1. Definition
<The definition establishes the purpose and or use for the object. Is there a standard object available to be
used or custom authorization object to be created.>

11
Functional Specification_ F_OTC-005_Bill Of Loading Page 12 of 15

6.2. Defined Fields

<The defined fields should be listed with the valid values to be used. (Like Activity 01/02/03)>

6.3. Procedure
<The procedure section helps to explain how this object is to be used. Examples with field values and
explanations should be provided.>

7. Process Flow Diagram

12
Functional Specification_ F_OTC-005_Bill Of Loading Page 13 of 15

8. SAP Transaction
VL01n(After saving the document) VL02n ( Change delivery) and VL03N ( Display the delivery)

9. Form Layout

Old version:

Bill of
Lading_YBUS_SDBOL.pdf

New Version:

BOL_with
Batches.docx

10. Printer Requirements

Printing on A4 size

11. Legal Requirements

Determine if there is any text that is required legally on the form, including font size, text to be printed on the back of
documents
ZTERMS – SO10 text should be used.

T&C’s will be provided by the customer.

13
Functional Specification_ F_OTC-005_Bill Of Loading Page 14 of 15

12. Form Fields

[Please provide the fields and their descriptions in the Form layout]

Form SAP Table SAP Field SAP Technical Max Output Calculations/Rules/Notes
Field ID Name Field Name Length

Main Heading
[Provide the main heading field for the Form]

15.1 Sub Heading

[Provide any required sub-headings and breaks required in the Form]

15.1 Totaling
[List any totalling or other calculation requirements for the Form]

15.1 Sorting
[List any sorting requirements for the Form]

15.1 Page Breaks

[Provide details of any page breaking requirements that should be used in addition to field breaks]

15.1 Stationery
[e.g. Plain A4 or pre-printed with logo. This stationery should be used when created example layout]

15.1 Logo(s)
[Where pre-printed stationery will not be used, provide file containing each Logo to be included on the form
printed output]

15.1 Bar Coding Requirements

Code i.e. 3 of 9 or ean128, etc

15.1 Configuration Dependencies

Please include any specific configuration details that triggers this Form

14
Functional Specification_ F_OTC-005_Bill Of Loading Page 15 of 15

13. Existing Sample Forms

[If an existing program is available to be enhanced, provide details in this section]
 Program Name
 Menu / Transaction
 Legacy Form name
 Legacy Program Title
 Legacy Form Number
 Related Transactions

14. Assumptions in Functional Design

15. Open Issues in Functional Design

16. Business Test Conditions (Functional Consultant)

[Please indicate the business level test conditions that should be used to verify successful operations of the Form]

[Document all technical scenarios associated with this development. Examples would include 1) testing an error-free
run; 2) testing the exception processes; 3) testing the error handling.]

[Document all control scenarios associated with this development. Examples would include 1) Rounding of dollars and
cents; 2) Audit trail processing; 3) Reconciliation reporting]

17. Related Documentation (Attach Notes, emails,

existing report, etc.)

18. Appendix

15