sapscript sapscript billoflading documentnt v1.0

Note: As this is a case study that simulates a real life development object, some fields will be marked as TBD and highlighted

SAP Implementation Of PILSAP Script Functional Specification

SAP Implementation Of PILSAP 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 LadingDocument Reference:TBDVersion:

v1.0

Document Status:

Signed offAuthor:

Jitendra Guha NeogiLast Revision Date:

19-Dec-2006Date Created:

19-Dec-2006Date Printed:

19-Dec-2006Document 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 byNameRoleSignatureDate

Process Team LeadTBDTBDTBDTBD

Development Team Lead TBDTBDTBDTBD

Document History

VersionReason for changeDate

1.0Initial Version19.12.2006

1.1

1.2

1.3

Table of Contents1.General Information

PAGEREF _Toc152083831 \h

42.Business Needs & Requirements


5

3.Issues


6

4.SAP Script/Forms


7

4.1Current Functionality


7

4.2Printing Existing Solution


7

4.3Desired Functionality


7

4.4Customizing requirements


7

5.Form Layout


8

6.Technical Details


13

Layout windows


13

Field Mapping


13

7.Standards Texts/Text Modules


30

4.2Translation


30

8.Layout Detail


30

9.Custom Tables/Structure in SAP


32

10.Assumptions


33

11.Error Handling


33

12.Language of texts


33

13.Testing Scenarios


33

1. General Information

Area (SAP System components):SDDate:15.11.2006

Short description:Bill of Lading

Requested by:TBDTel no:TBD

Author:Jitendra Guha NeogiTel no:TBD

Program Transaction code:SAP Script

Task ID/Demand Number:TBD

Project Name:SAP Implementation at PIL

Priority: FORMCHECKBOX High/mandatory FORMCHECKBOX Medium/recommended FORMCHECKBOX Low/optional

Complexity: FORMCHECKBOX High FORMCHECKBOX Medium FORMCHECKBOX Low

Volume of data:MediumDate available from:TBD

Mode: FORMCHECKBOX Online FORMCHECKBOX Background

Frequency: FORMCHECKBOX Daily FORMCHECKBOX Weekly FORMCHECKBOX Monthly FORMCHECKBOX Biweekly

FORMCHECKBOX Others (Specify) :

Technical information:

1. Layout created using:

FORMCHECKBOX Sapcript FORMCHECKBOX Smartform FORMCHECKBOX Subroutine pool

FORMCHECKBOX Text Elements FORMCHECKBOX Standard Texts

FORMCHECKBOX Text Id FORMCHECKBOX Print Program

General information:

1. Results if no conversions are created: FORMCHECKBOX Legal requirements not fulfilled

FORMCHECKBOX Lack of essential business information

FORMCHECKBOX Lack of functions compared to legacy system

FORMCHECKBOX Others (Specify):

duration of Development work

(in man-days):12 Days

Is there an alternative in the standard system? FORMCHECKBOX Yes FORMCHECKBOX No

Description of alternative:

Reasons why alternative is not acceptable: FORMCHECKBOX Performance problems FORMCHECKBOX Complexity

FORMCHECKBOX Others (Specify) :

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 process2. Establishing an Integrated information repository3. Improvement in the area of Planning4. 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

3. Issues

None

Issue #Issue

ownerDate RaisedIssue DescriptionIssue ResolutionResolved By & Date

4. SAP Script/Forms4.1 Current FunctionalityOutput typeCMR1

Program NameRVADTR01

Layout Form NameSD_SHIPMENT_CMR

IMG path to access output type and layout set assignmentIMG ( Logistics ( Logistics Execution ( Transportation ( Basic Transportation Functions (Output Control (Maintain Output Determination for Shipments (Maintain Output Types.

Type of solution (Standard R/3, custom ABAP)R/3

4.2 Printing Existing Solution

Menu Path for transaction:VT01N/ VT02N

Values to be used and output type:Output Type CMR1

Actions to be taken:

4.3 Desired Functionality

Output type(s):ZBOL

Form Types:CRM Bill of Lading

Transmission medium:Print

Legal requirements:

Type of printer:

Paper Size:Letter A4: 8 x 11

Orientation: Portrait/Landscape:Portrait

Special stationary to be used: Will be printed on plain white paper.

4.4 Customizing requirements

The functional consultant will customize the following output types:

Output typeZBOL

Program NameThe standard SAP program RVADTR01 has to be copied to the program ZRVPAF_ RVADTR01.

Layout Form NamesThe 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.

Development system TBD

5. Form Layout

Refer to the following for an output samples for Window mapping, Label Description and Field mapping.

PositionField NameOutput LengthNotesSAP Technical Ref. Field

99aCompany LogoFixed text

99bQuality LogoFixed text

99cABN TextFixed text

99dReprint LabelIf this output has been produced before from this shipment, the REPRINT label should be printed. Supress label on first printing of the output.Reprint

1Carrier Name40NAME1

23Carrier Street Number10HOUSE_NUM1

40Carrier Street60STREET

24Carrier Town40CITY1

25Carrier State3REGION

26Carrier Post Code10POST_CODE1

27Carrier Telephone30TEL_NUMBER

28Carrier Fax30FAX_NUMBER

2TPP Name 140VTTK-TPLST = V_TTDS-TPLST

V_TTDS-ADRNR = ADRC-ADDRNUMBERADRC-NAME1

29TPP Name 240ADRC-NAME2

40TPP Street Number10ADRC-HOUSE_NUM1

30TPP Street60If necessary, wrap the address within the output window.ADRC-STREET

31TPP Town40ADRC-CITY1

32TPP State3ADRC-REGION

33TPP Post Code10ADRC-POST_CODE1

34TPP PO Box10PO_BOX

35TPP PO Box City40PO_BOX_LOC

36TPP PO Box State3PO_BOX_REG

37TPP PO Box Pcode10POST_CODE2

38TPP Phone30TEL_NUMBER

39TPP Fax30FAX_NUMBER

3Shipment Number10VTTK-TKNUM

4Shipment DateVTTK- DTABF

5Shipment Truck Rego20VTTK- SIGNI

43Shipment Route6VTTK-ROUTE

44Route Description

8Header Text 1Text Type Z004 assigned to shipment VTTK-TKNUM



12DropFor each VTTP where VTTP-TKNUM = VTTK-TKNUMVTTP-TPNUM

42Delivery NumberFor each VTTP where VTTP-TKNUM = VTTK-TKNUMVTTP-VBELN

13Name40Look-up delivery (LIKP) using VTTK-VBELN

Customer number is LIKP-KUNNR

Look up KNA1 where KNA1-KUNNR = LIPS-KUNNR

Look up VBPA where VBELN = LIKP-VBELN and PARVW = SH

Look up ADRC where ADRC-ADRNR = VBPA-ADRNRADRC-NAME1

45Customer Street Number10As per 13ADRC-HOUSE_NUM1

46Customer Street60As per 13ADRC-STREET

47Customer City40As per 13ADRC-CITY1

48Customer State3As per 13ADRC-REGION

49Customer Post Code10As per 13ADRC-POST_CODE1

15Route6LIKP-ROUTE

16Weight (KG)5.2LIKP-BTGEW

17Volume (M3)5.2Calculating the total volume of a delivery will take several steps. Use method 1, if the net result is zero, then use method 2

Method 11. 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 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-VBELNCalculated

18Pallet Count3The 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.

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 psuedo-code 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.

COUNT VEPO where VBELN = LIPS-VBELN and POSNR = LIPS-POSNR

41Shipment InstructionText Type 0012 assigned to delivery LIKP-VEBLN

19Agent-Carrier NotesText Type Z001 assigned to shipment VTTK-TKNUM

20Driver InformationText Type Z003 assigned to shipment VTTK-TKNUM

Note 2Note 4Note 5Note 10Note 11

5Sales Order10-VBAK-VBELN

6. Technical Details

Layout windows

Field Mapping

LabelR/3 FieldCalculation LogicPrint-on-PageLabel PositionFontFont Format

Company LogoFixed Logo

Quality LogoFixed Logo

ABN TextFixed TextCourier8 pt

Form TitleVEHICLE MANIFESTLeftCourier18 pt, Bold

ReprintREPRINTLeftCourier14 pt, Bold

Carrier nameTable: LFA1

Screen: L_CARRIER_LFA1_ NAME1Getting 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 pageCourier10 pt

Carrier Street NameTable: ADRC

Screen: L_ CARRIER_ADRC_HOUSE_NUM1Getting VTTK-TDLNR from VTTK and retrieve LFA1 where LIFNR = VTTK-TDLNR.

Get the field HOUSE_NUM1 from ADRC where ADDRNUMBER = LFA1- ADRNR

Pass the retrieved field back to the layout using L_ CARRIER_ADRC_ HOUSE_NUM1.This will appear only in the first pageCourier10 pt

Carrier StreetTable: ADRC

Screen: L_ CARRIER_ADRC_STREETGetting VTTK-TDLNR from VTTK and retrieve LFA1 where LIFNR = VTTK-TDLNR.

Get the field STREET from ADRC where ADDRNUMBER = LFA1- ADRNR

Pass the retrieved field back to the layout using L_ CARRIER_ADRC_ STREET.This will appear only in the first pageCourier10 pt

Carrier TownTable: ADRC

Screen: L_ CARRIER_ADRC_ CITY1Getting VTTK-TDLNR from VTTK and retrieve LFA1 where LIFNR = VTTK-TDLNR.

Get the field CITY1 from ADRC where ADDRNUMBER = LFA1- ADRNR

Pass the retrieved field back to the layout using L_ CARRIER_ADRC_ CITY1.This will appear only in the first pageCourier10 pt

Carrier StateTable: ADRC

Screen: L_ CARRIER_ADRC_ REGIONGetting VTTK-TDLNR from VTTK and retrieve LFA1 where LIFNR = VTTK-TDLNR.

Get the field REGION from ADRC where ADDRNUMBER = LFA1- ADRNR

Pass the retrieved field back to the layout using L_ADRC_ REGION1.This will appear only in the first pageCourier10 pt

Carrier Post CodeTable: ADRC

Screen: L_ CARRIER_ADRC_POST_CODE1Getting VTTK-TDLNR from VTTK and retrieve LFA1 where LIFNR = VTTK-TDLNR.

Get the field POST_CODE1 from ADRC where ADDRNUMBER = LFA1- ADRNR

Pass the retrieved field back to the layout using L_ CARRIER_ADRC_ POST_CODE1.This will appear only in the first pageCourier10 pt

Carrier telephoneTable: ADRC

Screen: L_ CARRIER_ADRC_ TEL_NUMBERGetting VTTK-TDLNR from VTTK and retrieve LFA1 where LIFNR = VTTK-TDLNR.

Get the field TEL_NUMBER from ADRC where ADDRNUMBER = LFA1- ADRNR

Pass the retrieved field back to the layout using L_ CARRIER_ADRC_ TEL_NUMBER.This will appear only in the first pageCourier10 pt

Carrier FaxTable: ADRC

Screen: L_ CARRIER_ADRC_ FAX_NUMBERGetting VTTK-TDLNR from VTTK and retrieve LFA1 where LIFNR = VTTK-TDLNR.

Get the field FAX_NUMBER from ADRC where ADDRNUMBER = LFA1- ADRNR

Pass the retrieved field back to the layout using L_ CARRIER_ADRC_ FAX_NUMBER.This will appear only in the first pageCourier10 pt

TPP Name1Table: ADRC

Screen: L_DISP_ADRC_NAME1Getting VTTK-TPLST from VTTK for Transportation Planning Point and retrieve from V_TTDS where TPLST = VTTK-TPLST.

Get the field NAME1 from ADRC where ADDRNUMBER = V_TTDS ADRNR

Pass the retrieved field back to the layout using L_DISP_ADRC_ NAME1.This will appear only in the first pageCourier10 pt

TPP Name2Table: ADRC

Screen: L_DISP _ADRC_ NAME2Getting VTTK-TPLST from VTTK for Transportation Planning Point and retrieve from V_TTDS where TPLST = VTTK-TPLST.


Pass the retrieved field back to the layout using L_DISP_ADRC_ NAME2.This will appear only in the first pageCourier10 pt

TPP Street NumberTable: ADRC

Screen: L_DISP _ADRC_ HOUSE_NUM1Getting VTTK-TPLST from VTTK for Transportation Planning Point and retrieve from V_TTDS where TPLST = VTTK-TPLST.


Pass the retrieved field back to the layout using L_DISP_ADRC_ HOUSE_NUM1.This will appear only in the first pageCourier10 pt

TPP StreetTable: ADRC

Screen: L_DISP _ADRC_ STREETGetting VTTK-TPLST from VTTK for Transportation Planning Point and retrieve from V_TTDS where TPLST = VTTK-TPLST.


Pass the retrieved field back to the layout using L_DISP_ADRC_ STREET.This will appear only in the first pageCourier10 pt

TPP TownTable: ADRC

Screen: L_DISP _ADRC_ CITY1Getting VTTK-TPLST from VTTK for Transportation Planning Point and retrieve from V_TTDS where TPLST = VTTK-TPLST.


Pass the retrieved field back to the layout using L_DISP_ADRC_ CITY1.This will appear only in the first pageCourier10 pt

TPP StateTable: ADRC

Screen: L_DISP _ADRC_ REGIONGetting VTTK-TPLST from VTTK for Transportation Planning Point and retrieve from V_TTDS where TPLST = VTTK-TPLST.


Pass the retrieved field back to the layout using L_DISP_ADRC_ REGION.This will appear only in the first pageCourier10 pt

TPP Post CodeTable: ADRC

Screen: L_DISP _ADRC_ POST_CODE1Getting VTTK-TPLST from VTTK for Transportation Planning Point and retrieve from V_TTDS where TPLST = VTTK-TPLST.


Pass the retrieved field back to the layout using L_DISP_ADRC_ POST_CODE1.This will appear only in the first pageCourier10 pt

TPP PO BoxTable: ADRC

Screen: L_DISP _ADRC_ PO_BOXGetting VTTK-TPLST from VTTK for Transportation Planning Point and retrieve from V_TTDS where TPLST = VTTK-TPLST.


Pass the retrieved field back to the layout using L_DISP_ADRC_ PO_BOX.This will appear only in the first pageCourier10 pt

TPP PO Box CityTable: ADRC

Screen: L_DISP _ADRC_ PO_BOX_LOCGetting VTTK-TPLST from VTTK for Transportation Planning Point and retrieve from V_TTDS where TPLST = VTTK-TPLST.


Pass the retrieved field back to the layout using L_DISP_ADRC_ PO_BOX_LOC.This will appear only in the first pageCourier10 pt

TPP PO Box StateTable: ADRC

Screen: L_DISP _ADRC_ PO_BOX_REGGetting VTTK-TPLST from VTTK for Transportation Planning Point and retrieve from V_TTDS where TPLST = VTTK-TPLST.


Pass the retrieved field back to the layout using L_DISP_ADRC_PO_BOX_REG .This will appear only in the first pageCourier10 pt

TPP PO Box PcodeTable: ADRC

Screen: L_DISP _ADRC_ POST_CODE2Getting VTTK-TPLST from VTTK for Transportation Planning Point and retrieve from V_TTDS where TPLST = VTTK-TPLST.


Pass the retrieved field back to the layout using L_DISP_ADRC_ POST_CODE2.This will appear only in the first pageCourier10 pt

TPP PhoneTable: ADRC

Screen: L_DISP _ADRC_ TEL_NUMBERGetting VTTK-TPLST from VTTK for Transportation Planning Point and retrieve from V_TTDS where TPLST = VTTK-TPLST.


Pass the retrieved field back to the layout using L_DISP_ADRC_ TEL_NUMBER.This will appear only in the first pageCourier10 pt

TPP FaxTable: ADRC

Screen: L_DISP _ADRC_ FAX_NUMBERGetting VTTK-TPLST from VTTK for Transportation Planning Point and retrieve from V_TTDS where TPLST = VTTK-TPLST.


Pass the retrieved field back to the layout using L_DISP_ADRC_ FAX_NUMBER.This will appear only in the first pageCourier10 pt

Shipment NumberTable: VTTK

Screen: L_VTTK_ TKNUMGetting VTTK-TKNUM from VTTK and Pass the retrieved field back to the layout using L_VTTK_TKNUM.This will appear only in the first pageCourier10 pt

Shipment DateTable: VTTK

Screen: L_VTTK_ DTABFGetting VTTK-DTABF from VTTK and Pass the retrieved field back to the layout using L_VTTK_DTABF.This will appear only in the first pageCourier10 pt

Shipment Truck RegoTable: VTTK

Screen: L_VTTK_ SIGNIGetting VTTK-SIGNI from VTTK and Pass the retrieved field back to the layout using L_VTTK_SIGNI.This will appear only in the first pageCourier10 pt

Shipment RouteTable: VTTK

Screen: L_VTTK_ ROUTEGetting VTTK-ROUTE from VTTK and Pass the retrieved field back to the layout using L_VTTK_ROUTE.This will appear only in the first pageCourier10 pt

Route DescriptionTable: TVRO

Screen: L_TVRO_ ROUTIDGetting VTTK-ROUTE from VTTK and retrieve the field ROUTID from TVRO where ROUTE = VTTK-ROUTE.

Pass the retrieved field back to the layout using L_TVRO_ROUTID.This will appear only in the first pageCourier10 pt

Header Text 1The Function Module READ_TEXT is used with the Import parameters as Object (VTTK-TKNUM), Name (Shipment Number), and ID as Z004This will appear only in the first pageCourier10 pt



Shipment Item (Drop)Table: VTTP

Screen: L_VTTP_ TPNUMGetting VTTK-TKNUM from VTTK and retrieve the field TPNUM from VTTP where TKNUM = VTTK-TKNUM.

Pass the retrieved field back to the layout using L_VTTP_TPNUM.This will appear in the first page and also in the consequent pages if page overflow occursCourier10 pt

Delivery NumberTable: VTTP

Screen: L_VTTP_ VBELNGetting VTTK-TKNUM from VTTK and retrieve the field VBELN from VTTP where TKNUM = VTTK-TKNUM.

Pass the retrieved field back to the layout using L_VTTP_VBELN.This will appear in the first page and also in the consequent pages if page overflow occursCourier10 pt

Customer NameTable: ADRC

Screen: L_ADRC_ NAME1Getting 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 = KNA1-ADRNR.

Pass the retrieved field back to the layout using L_ADRC_NAME1.This will appear in the first page and also in the consequent pages if page overflow occursCourier10 pt

Customer Street NumberTable: ADRC

Screen: L_ADRC_ HOUSE_NUM1Getting VTTP-TKNUM from VTTP and retrieve from VTTP where TKNUM = VTTK-TKNUM and further from LIKP where VBELN = VTTP-VBELN.


Pass the retrieved field back to the layout using L_ADRC_HOUSE_NUM1.This will appear in the first page and also in the consequent pages if page overflow occursCourier10 pt

Customer StreetTable: ADRC

Screen: L_ADRC_ STREETGetting VTTP-TKNUM from VTTP and retrieve from VTTP where TKNUM = VTTK-TKNUM and further from LIKP where VBELN = VTTP-VBELN.


Pass the retrieved field back to the layout using L_ADRC_STREET.This will appear in the first page and also in the consequent pages if page overflow occursCourier10 pt

Customer CityTable: ADRC

Screen: L_ADRC_ CITY1Getting VTTP-TKNUM from VTTP and retrieve from VTTP where TKNUM = VTTK-TKNUM and further from LIKP where VBELN = VTTP-VBELN.


Pass the retrieved field back to the layout using L_ADRC_CITY1.This will appear in the first page and also in the consequent pages if page overflow occursCourier10 pt

Customer StateTable: ADRC

Screen: L_ADRC_ REGIONGetting VTTP-TKNUM from VTTP and retrieve from VTTP where TKNUM = VTTK-TKNUM and further from LIKP where VBELN = VTTP-VBELN.


Pass the retrieved field back to the layout using L_ADRC_REGION.This will appear in the first page and also in the consequent pages if page overflow occursCourier10 pt

Customer Post CodeTable: ADRC

Screen: L_ADRC_ POST_CODE1Getting VTTP-TKNUM from VTTP and retrieve from VTTP where TKNUM = VTTK-TKNUM and further from LIKP where VBELN = VTTP-VBELN.


Pass the retrieved field back to the layout using L_ADRC_POST_CODE1.This will appear in the first page and also in the consequent pages if page overflow occursCourier10 pt

RouteTable: LIKP

Screen: L_LIKP_ RouteGetting VTTP-TKNUM from VTTP and retrieve from VTTP where TKNUM = VTTK-TKNUM and further from LIKP where VBELN = VTTP-VBELN.


Pass the retrieved field back to the layout using L_ADRC_ROUTE.This will appear in the first page and also in the consequent pages if page overflow occursCourier10 pt

WeightTable: LIKP

Screen: L_LIKP_ BTGEWGetting VTTP-TKNUM from VTTP and retrieve from VTTP where TKNUM = VTTK-TKNUM and further from LIKP where VBELN = VTTP-VBELN.

Pass the retrieved field back to the layout using L_LIKP_BTGEW.This will appear in the first page and also in the consequent pages if page overflow occursCourier10 pt

VolumeScreen: L_VOLUMEFor 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 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.This will appear in the first page and also in the consequent pages if page overflow occursCourier10 pt

Pallet CountScreen: L_PALLET_COUNTThe total Pallet Count will be the SUM of the pallet count field for all items (LIPS) on a delivery (LIKP)This will appear in the first page and also in the consequent pages if page overflow occursCourier10 pt

Shipment InstructionScreen: L_SHIP_INSTThe Function Module READ_TEXT is used with the Import parameters as Object (LIKP-VELN), Name (Delivery Number), and ID as 0012This will appear in the first page and also in the consequent pages if page overflow occursCourier10 pt

Agent-Carrier NotesScreen: L_AGENT_NOTESThe Function Module READ_TEXT is used with the Import parameters as Object (VTTK-TKNUM), Name (Shipment Number), and ID as Z001This will appear in the first page and also in the consequent pages if page overflow occursCourier10 pt

Driver InformationScreen: L_DRIVER_INFOThe Function Module READ_TEXT is used with the Import parameters as Object (VTTK-TKNUM), Name (Shipment Number), and ID as Z003This will appear in the first page and also in the consequent pages if page overflow occursCourier10 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 pageNote C:If the position of this field on Paper is important then specify this measure here along with the unitNote 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)

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.

ReferenceDescription of use (in Language1)Description of use (in Language2)Description of use (in Language3)Text module NameNotes

NANANANANANA

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 Logo10.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 WindowLeft Margin: 0.5 CM Window Width: 8.6 CM


Position of DISPATCH WindowLeft Margin: 9.1 CM Window Width: 8.4 CM


Position of SHIPMENT WindowLeft Margin: 17.5 CM Window Width: 8.2 CM


Position of FOOTER1 WindowLeft Margin: 0.5 CM Window Width: 12.7 CM


Position of FOOTER2 WindowLeft Margin: 13.2 CM Window Width: 12.7 CM


Position of INFO WindowLeft Margin: 0.5 CM Window Width: 25.7 CM


9. Custom Tables/Structure in SAPNo Such Custom Tables required.

Table NameNA

Short textNA

Size categoryNA

Table maintenance allowedNA

Data classNA

BufferingNA

Table maintenance generatorNA

Authorization GroupNA

Field NameData ElementDomainTypeLengthCheck Table-FieldKey FieldForeign KeyDescription

NANANANANANANANANA

Comments

10. Assumptions11. Error Handling

None

12. Language of texts

English EN.

13. Testing Scenarios

Normal Functionality - test cases that ensure the report functions as it should.

IDDescription

1The 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

8

BillOfLading_Document_v1.0 19-Dec-2006

18BillOfLading_Document_v1.0 19-Dec-2006

_1228125746.doc99a99b

99c Division of PIL India Ptv Ltd

8 Instructions from the shipment header (Header1)

9 Header 2 text

10 Header 3 text

Drop

12

Delivery

(42)

Ship To Party

(50)

Name

13

Delivery Address

Route

15

Weight

(KG)

16

Volume

(M3)

17

Pallet

Count

18

01

8000000321

xxxxxxxxxx

Cadbury Confectionary

(45) 444 (46) Overbank Road, (47)LAUNCESTON, (48) TAS, (49) 7698

ZTAS23001

1354.22

100.23

90

41 Shipment Instructions from Delivery header

XX

XXXXXX

xxxxxxxxxx

XXXXXXXXXXXXXXXXXXXXXXXXX

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX, XXX, XXXX

XXXXXXX

XXXX.xx

XXX.XX

XXXX

Shipment Instructions from Delivery header

XX

XXXXXX

xxxxxxxxxx


XXXXXXXXXXXXXXXXXXXXXXXXXXX

XXXXXXXXXXXXXXXXXXX, XXX, XXXX

XXXXXXX

XXXX.xx

XXX.XX

XXXX


XX

XXXXXX

xxxxxxxxxx


XXXXXXXXXXXXXXXXXXXXXXXXXXXX


XXXXXXX

XXXX.xx

XXX.XX

XXXX


XX

XXXXXXX

xxxxxxxxxx


XXXXXXXXXXXXXXXXXXXXXXXXXXXX


XXXXXXX

XXXX.xx

XXX.XX

XXXX


Dispatched By

(2) Amcor Fibre Packaging

(29) Launceston Finished Goods Dispatch

(40) 321 (30)Remount Road,

(31) MOWBRAY, (32) Tasmania, (33) 7248

(34) PO Box 962

(35) Launceston, (36) TASMANIA, (37) 7250

Tel: (38) 03 6326 0666 Fax: (39) 03 6326 6857

Shipment Details

3 Shipment no:XXXXXXXXXX

4 Date: XX/XX/XXXX

5 Truck Reg:XXXXXXXXXX

43 Shipment Route:XXXXXX

44 XXXXXXXXXXXXXXXXXXXXXXX

Carrier

(1) Toll Holdings

(23) 123 (40) Generic Road

(24) Launceston, (25) TAS, (26)7250

Tel. (27) (XX) XXXXXXXX

Fax. (28) (XX) XXXXXXXX

6 VEHICLE MANIFEST

Page (7) XX of (21) XX(22)

99d REPRINT

19 Notes to Agent / Carrier

From the Shipment Header texts

20 Driver Information

From the Shipment Header texts

sapscript sapscript billoflading documentnt v1.0

Documents

sap pageref

toc152083836 h

toc152083831 h

toc152083841 h

toc152083835 h

toc152083843 h

toc152083842 h

toc152083837 h