FS - FR - R8398-OTC-New File For Monthly Sales Reps Allocation - HEPPNER

Prepared By:
Approved By:
Date Prepared:
Date Approved:
Page 1 of 16
0.0 Table of Contents

0.0 TABLE OF CONTENTS.........................................................................................................................................1
1.0 GENERAL INFORMATION AND HISTORY:............................................................................................................3
1.1 DESCRIPTIVE INFORMATION...............................................................................................................................3
1.2 SPECIFICATION CHANGE HISTORY.....................................................................................................................3
1.3 SIGN OFF............................................................................................................................................................4
2.0 BUSINESS REQUIREMENTS:................................................................................................................................5
2.1 FUNCTIONAL REQUIREMENTS............................................................................................................................5
2.2 SCOPE................................................................................................................................................................5
3.0 FUNCTIONAL SPECIFICATION:............................................................................................................................5
3.1 ERROR HANDLING.............................................................................................................................................5
3.2 RUN DETAILS.....................................................................................................................................................5
3.2.1 Inputs..........................................................................................................................................................5
3.2.2 Output........................................................................................................................................................8
3.2.3 Run Options...............................................................................................................................................9
3.3 CRITICAL DEPENDENCIES & END USER IMPACT:..............................................................................................9
3.4 SPECIFIC DEVELOPMENT OBJECT TYPE INFORMATION:....................................................................................9
3.4.1 SAPscript/SmartForms related information:...........................................................................................10
3.4.2 Report and Form Specific Information....................................................................................................10
3.4.3 Interface Specific Information..................................................................................................................11
3.4.4 Conversion Specific Information..............................................................................................................11
3.4.5 Enhancement Specific Information..........................................................................................................12
3.4.5 Workflow Specific Information.................................................................................................................12
3.4.6 Other Information....................................................................................................................................12
3.5 PROCESSING LOGIC:........................................................................................................................................13
3.6 ASSUMPTIONS/CONSTRAINTS/ FUNCTIONAL DEPENDENCIES..........................................................................13
3.7 LANGUAGE CONSIDERATION (REQUIRED).......................................................................................................13
3.8. CURRENCY AND UNIT OF MEASURE...............................................................................................................13
3.9 SECURITY.........................................................................................................................................................13
3.10 CUSTOMIZING................................................................................................................................................14
3.11 AREA MENU...................................................................................................................................................14
4.0 TECHNICAL SPECIFICATION:............................................................................................................................14
4.1 HIGH-LEVEL TECHNICAL DESIGN FLOW.........................................................................................................14
4.2 PSEUDO-CODE.............................................................................................................................................14
5.0 SPECIFIC DEVELOPMENT OBJECT TYPE INFORMATION:..................................................................................14
5.1 OBJECT INFORMATION.....................................................................................................................................14
5.2 TRANSPORT STRATEGY....................................................................................................................................15
5.2 REPORT AND FORM SPECIFIC INFORMATION...................................................................................................15
5.3 INTERFACE SPECIFIC INFORMATION.................................................................................................................15
5.4 CONVERSION SPECIFIC INFORMATION.............................................................................................................16
_______________________________________________________________________________________________________
/var/www/apps/conversion/tmp/scratch_6/324462363.doc
Prepared By:
Approved By:
Date Prepared:
Date Approved:
Page 2 of 16
5.5 ENHANCEMENT/MODIFICATION SPECIFIC INFORMATION .................................................................................16

5.6 WORKFLOW SPECIFIC INFORMATION...............................................................................................................17
5.6 SCREENS..........................................................................................................................................................19
5.7 DATA/TABLES/LOGICAL DATABASES...............................................................................................................19
5.8 COMMON PROGRAMMING TASKS....................................................................................................................19
5.9 SECURITY.........................................................................................................................................................19
6.0 ATTACHMENTS AND DOCUMENTATION:...........................................................................................................20
_______________________________________________________________________________________________________
Prepared By:
Approved By:
Date Prepared:
Date Approved:
Page 3 of 16
1.0 General Information and History:
1.1 Descriptive Information
Short Description
New file for Monthly Sales Reps allocation - HEPPNER

8398
FRICEW #
Development Type
SAP Release
New Report
Business Process
Owner
CIT Document #
CIT_L-200_Shipping for
Standard Delivery
Technical Owner
1.2 Specification Change History

Version
Number
1.1
1.2
Reference
Change
Request
700137
Date
Modified
24/01/2011
Modified By
Joydeep
Sarkar
Brief Description of Change

Document and FS creation
High level technical design has been
updated in sec 4.1, FS and Technical
design has been updated.
_______________________________________________________________________________________________________
Prepared By:
Approved By:
Date Prepared:
Date Approved:
Page 4 of 16
1.3 Sign off

Process Step
Name
Functional Spec
<Affiliate team member >
Functional QA
< Delivery Team member>
Date
(DD/MM/YY)
Attachment
Attach completed
Functional QA checklist
"Functional Spec QA
Checklis t.doc"
Technical QA of FS
Technical Spec
Joydeep Sarkar
09.01.2011
Development
Joydeep Sarkar
09.01.2011
Technical QA of
development & Specs
_______________________________________________________________________________________________________
Prepared By:
Approved By:
Date Prepared:
Date Approved:
Page 5 of 16
2.0 Business Requirements:

1) From the middle of this year affiliate suppose to work with a new forwarder HEPPNER for the monthly sales
rep allocation.
2) Affiliate has to use a specific application provided by Heppner called ChargeurOnline.
3) Each month the warehousemen have to enter manually in ChargeurOnline all the data related to the Sales
Orders/Outbound Deliveries for each sales representative (more than 200 pax).
4) In ChargeurOnline a functionally allows to load a .csv file in order to automate this task : important saving time
and reliability of data.
5) Needs to develop a new SAP report in order to extract the data and create this .csv file (naming convention :
DDMMYYYYHEP.csv)
2.1 Functional Requirements
2.2 Scope
3.0 Functional Specification:

1) From the middle of this year affiliate suppose to work with a new forwarder HEPPNER for the monthly sales
rep allocation.
2) Affiliate has to use a specific application provided by Heppner called ChargeurOnline.
3) Each month the warehousemen have to enter manually in ChargeurOnline all the data related to the Sales
Orders/Outbound Deliveries for each sales representative (more than 200 pax).
4) In ChargeurOnline a functionally allows to load a .csv file in order to automate this task : important saving time
and reliability of data.
5) Needs to develop a new SAP report in order to extract the data and create this .csv file (naming convention :
DDMMYYYYHEP.csv)
3.1 Error Handling

Possible Errors and Error Handling:
Error
Impact
Cause
Resolution
3.2 Run Details

3.2.1 Inputs
1.
2.
3.
Sales organization : VKORG (Mandatory)

Delivery
: VBELN
Creation Date
: ERDAT(Mandatory)
Selection Screen
_______________________________________________________________________________________________________
Prepared By:
Approved By:
Date Prepared:
Date Approved:
Page 6 of 16
Screen Field Information

Frame Selection screen
Name
Field
Sales Organization
VKORG
Delivery
VBELN
Created On
ERDAT
Source
LIKP-VKORG
LIKP-VBELN
LIKP-ERDAT
Other Info
Mandatory
Mandatory
Display options:
Display for the report on monthly basis.
_______________________________________________________________________________________________________
Prepared By:
Approved By:
Name
Business
description
Date Prepared:
Date Approved:
Field
Technical field
name
Source
Table name
Page 7 of 16
Other Info
Screen Flow / Field Mapping

Field Mapping:
Num
Field
Source
Other Info
3.2.2 Output
The output fields are as following:
1. Date on Which Record Was Created
2. Carrier code
3. Route
4. Product of carrier
5. Handling unit
6. Ship-to party
7. Name 1
8. Street
9. House Number
10. Country Key
11. City postal code
12. City
13. Total number of packages in delivery
14. Total Weight
15. Port type
16. Delivery
17. Concatenated tel no and text
18. Picking Date
The ALV output in GRID display

_______________________________________________________________________________________________________
Prepared By:
Approved By:
Date Prepared:
Date Approved:
Page 8 of 16
On pressing the custom button

on the application toolbar the
destination folder location can be browsed to save the file. After selecting the folder and
clicking the save button the file is saved in the DDMMYYYYHEP.CSV format.
A CSV file is attached below for reference:
C:\Documents and
Settings\jsarkar\Desktop\24012011HEP.CSV
3.2.3 Run Options
_______________________________________________________________________________________________________
Prepared By:
Approved By:
Date Prepared:
Date Approved:
Page 9 of 16
Print Requirements (printer/spool): Output should be in ALV format with standqard ALV functionalities. The
report should be downloaded to .CSV format.
Distribution List: N/A
Run Type: Foreground
Run Frequency & Run Time: Once in a month.
Volume:
Others: N/A
3.3 Critical Dependencies & End User Impact:

Critical Dependencies:
End User Impact:
3.4 Specific Development Object Type Information:

Feel free to delete or add any of the points below which are not relevant to your development object type.
3.4.1 SAPscript/SmartForms related information:
Existing SAP Layout
Output type
Program Name
Layout Form Name
IMG path to access output type and
layout set assignment
Type of solution (Standard R/3,
Standard R/3
custom ABAP)
Owner of existing solution
SAP
New Requirements
Output type(s):
Form Types:
Transmission medium:
Legal requirements:
Type of printer:
Paper Size:
Orientation: Portrait/Landscape:
Special stationary to be used :
e.g. Invoice, Proforma Invoice, Credit Memo, Sales

Order, Picking Label, etc.
"PostScript" or "Label printer" or other (specify)

(standard A4 laser printers will always be PostScript)
A4, Letter, Legal, others, please provide exact
dimensions.
Please mention any pre-printed stationary this output
will be printed, and the dimensions of that stationary.
_______________________________________________________________________________________________________
Prepared By:
Approved By:
Date Prepared:
Date Approved:
Page 10 of 16
3.4.2 Report and Form Specific Information

Report Name/Title
Description
Owner
Field Name for
StartDisplay
position,
Size
Description
Source / Selection
criteria (if
applicable)
Special
Processing
Condition (if
applicable)
..
..
..
Summary Level:
Field Descriptions:
Main Heading:
Sub-Heading:
Totals:
Sorting:
Breaks:
Formulas:
Interactive Capabilities:
3.4.3 Interface
Specific Information
Name
Description of the interface
Physical file name
SAP Logical file name
( optional )
File format
IDOC/ALE Details
(Flat file .txt, Tab delimited .prn etc)
General Details
Name & reference of IDOC
Short Description
Type of IDOC
Source
Destination
Frequency
Field Mappings and conversion (relevant fields only)
Field Description
SAP Field Sample Value
Conversion
Issues
_______________________________________________________________________________________________________
Prepared By:
Approved By:
Fields reworked in User-Exits

Field /User Exit Description
Date Prepared:
Date Approved:
SAP Field
Page 11 of 16
Sample Value
Conversion
3.4.4 Conversion Specific Information

SAP Standard Load:
Data Cleansing Process:
Data Mapping:
Conversion Strategy:
3.4.5 Enhancement Specific Information
User Exit Strategy Request Document :
To be filled and sent to PMI ,P1 European Roll-in FRICEW team to implement user exit strategy.
S:\P1 Roll-in\12
Central Team\090 Technical Office Team\FRICEW Team\Work In Progress\User Exit Strategy\User Exit Strategy request.doc
User Exit / Enhancement Details
Type of Exit
Name of Exit / Business Add-In /
Business Transaction Event
Project
Enhancement
Component(s)
SAP Program
Function Module
Transactions impacted
Include(s)
Screen Number(s)
Menu/Path
Function module, Screen or Menu exits are supported

by SAP 4.6C
Name of user exit, business add-in or business
transaction event provided by SAP
SAP enhancement that contains the exit.
Main SAP program where the exit is called from
Function Module where the code sits within the user exit
Transactions where the user exit is called
SAP program where the exit code will be placed
Relevant for Screen exits
Relevant for Menu exits
3.4.5 Workflow Specific Information

3.4.6 Other Information
_______________________________________________________________________________________________________
Prepared By:
Approved By:
Date Prepared:
Date Approved:
Page 12 of 16
New Table Information

Table Name
Description
Functional- Area
Maintenance Allowed
Field
Field size
Name
/Data type
(Yes/No)
Description
Data Element
Key Field
Yes/No
Yes
Yes
Yes
..
..
Search Helps
Field
Name/ParameterDescription
Import/Export Key Field

(I/E)
(Y/N)
Data Element Type Length

(Char, Num)
Default
Value
3.5 Processing Logic:
3.6 Assumptions/Constraints/ Functional Dependencies
3.7 Language Consideration (Required)

No language considerations
Yes. ( Please specify if data needs to be displayed in user logon language )
Translation requirements
No translation requirements Development will be used in English only
Translation required:
Comments
Write the information like what is the translated text in other language.
3.8. Currency and Unit of Measure
3.9 Security
An authorization object is assigned against the sales organization as follows:
_______________________________________________________________________________________________________
Prepared By:
Approved By:
Date Prepared:
Date Approved:
Report Name
ZWFRSR_MONTHLY_SALES_HERPNER
Tcode: ZWFRS_L200_001
Page 13 of 16
Authorization
Object
V_VBRK_VKO
S_TCODE
V_VBRK_VKO
Field
Values
ACTVT
VKORG
03
Display
ACTVT
03
How should access to run the development be restricted.

No specific restrictions ( Please state the reason why security is not required. E.g. User Exit )
Restriction on authorization on development-specific transaction code only (STANDARD OPTION) FOR
EXECUTABLE DEVELOPMENTS)
Restrictions based on certain criteria. Please specify criteria (e.g. Access based on company code, plant or
combinations of different criteria) and activity for which authorization should be there.
Other: Please specify
Comments:
3.10 Customizing
List and describe here any technical customizing required for the development. Specify if the customizing is
needed before the development starts.
Standard customizing table (specify table name and transaction)

Customer specific (Z*) table (specify table name and transaction)
Workflow configuration
Report painter configuration, Sets and Hierarchy
3.11 Area Menu

If required, specify the exact position of the Area Menu entry.
Describe the path in the area menu as follows
PMI Information system / Order to Cash / Master Data / Benelux / Maintenance

If required format in Red/Bold any node that must be created.
Note that in principle the area menu structure is fixed and cannot be changed. Any node creation (except
affiliates local folders) request must be documented and approved by BPO.
If new entries must be inserted between existing entries describe as precisely as possible the exact
positions. For instance use screen shots and arrows.
4.0 Technical Specification:

Technical details associated with the development.
4.1 High-level Technical Design Flow
_______________________________________________________________________________________________________
Prepared By:
Approved By:
Date Prepared:
Date Approved:
Page 14 of 16
Selection Screen
Name
Sales Organization
Delivery
Created On
Field
VKORG
VBELN
ERDAT
Source
LIKP-VKORG
LIKP-VBELN
LIKP-ERDAT
Other Info
Mandatory
Mandatory
Output screen (ALV grid display)

Description
Field
Table
Date on Which Record Was Created

(Date expdition)
Carrier code (Code transporteur)
ERDAT
LIKP
carrier_code
Route (Code expediteur)
route
Custom field
CHAR 4
LIKP
Product of carrier
(Produit du Transporteur)
prod_carir
Custom field
CHAR2
Handling unit (Unit de manutention)
handlng_unit
Ship-to party (Code destinataire)

Name 1 (Nom destinataire)
Street (Adresse 1)
House Number (Adresse 2)
Country Key (Pays destinataire)
City postal code (Code Postaux)
City (Localit)
Total number of packages in delivery
(Nombre colis/palettes)
Total Weight (Poids rel total)
Port type (Type de Port)
kunwe
ad_name1
ad_street
ad_hsnm1
land1
ad_pstcd1
ad_city1
anzpk
Custom field
CHAR3
LIKP
ADRC
ADRC
ADRC
ADRC
ADRC
ADRC
LIKP
Delivery (Rfrence Expdition)

Concatenated tel no and text (Instruction
de livraison)
vbeln
tel_no1
btgew
port_typ
LIKP
Custom field
CHAR1
LIKP
Custom field
STRING
Calculation/Default Value
HEPP
If LIKP-ANZPK > 3
then "384170"
else if VBAP-ROUTE =
FRFR35
then "714490"
FRFR36 or FRFR33
then "984618"
FRFR31
then "984619"
else "error"
end if
end if
end if
end if
If LIKP-ANZPK > 3 then
"05"
else "01"
end if
PAL
if "Header SO Warehouse Instructions"

is empty
them SZA1_D0100MOB_NUMBER and "Livr
entre 8 et 9h"
else SZA1_D0100MOB_NUMBER and
_______________________________________________________________________________________________________
Prepared By:
Approved By:
Date Prepared:
Date Approved:
Page 15 of 16
"Header SO - Warehouse
Instructions"
end if
Picking Date (Rfrence Expdition)
kodat
LIKP
5.0 Specific Development Object Type Information:

Feel free to delete or add any of the points below which are not relevant to your development object type.
5.1 Object Information

Report
Development Type
Transaction Code
Development Class
Message Class
Program
Includes
Structure
Custom Table
Data Element
Error Messages
Function group
5.2 Transport Strategy

Transport Number FRICEW #
#
Description
Dependency / Related
Configuration CTS
5.7 Data/Tables/Logical Databases

Data Elements/Domains/Structures/Logical Databases/Views:
5.9 Security
Security:
6.0 Attachments and Documentation:
_______________________________________________________________________________________________________
Prepared By:
Approved By:
Date Prepared:
Date Approved:
Page 16 of 16
_______________________________________________________________________________________________________

FS - FR - R8398-OTC-New File For Monthly Sales Reps Allocation - HEPPNER

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

FS - FR - R8398-OTC-New File For Monthly Sales Reps Allocation - HEPPNER

Загружено:

Авторское право:

Доступные форматы

Prepared By:

0.0 Table of Contents

5.5 ENHANCEMENT/MODIFICATION SPECIFIC INFORMATION .................................................................................16

1.0 General Information and History:

1.1 Descriptive Information

New file for Monthly Sales Reps allocation - HEPPNER

1.2 Specification Change History

Brief Description of Change

1.3 Sign off

<Affiliate team member >

< Delivery Team member>

2.0 Business Requirements:

3.0 Functional Specification:

3.1 Error Handling

3.2 Run Details

Sales organization : VKORG (Mandatory)

Screen Field Information

Screen Flow / Field Mapping

The ALV output in GRID display

On pressing the custom button

A CSV file is attached below for reference:

3.2.3 Run Options

3.3 Critical Dependencies & End User Impact:

3.4 Specific Development Object Type Information:

e.g. Invoice, Proforma Invoice, Credit Memo, Sales

"PostScript" or "Label printer" or other (specify)

3.4.2 Report and Form Specific Information

(Flat file .txt, Tab delimited .prn etc)

Fields reworked in User-Exits

3.4.4 Conversion Specific Information

User Exit / Enhancement Details

Function module, Screen or Menu exits are supported

3.4.5 Workflow Specific Information

New Table Information

Import/Export Key Field

Data Element Type Length

3.5 Processing Logic:

3.6 Assumptions/Constraints/ Functional Dependencies

3.7 Language Consideration (Required)

3.8. Currency and Unit of Measure

How should access to run the development be restricted.

Standard customizing table (specify table name and transaction)

3.11 Area Menu

Describe the path in the area menu as follows

PMI Information system / Order to Cash / Master Data / Benelux / Maintenance

4.0 Technical Specification:

Output screen (ALV grid display)

Date on Which Record Was Created

Route (Code expediteur)

Handling unit (Unit de manutention)

Ship-to party (Code destinataire)

Delivery (Rfrence Expdition)

if "Header SO Warehouse Instructions"

5.0 Specific Development Object Type Information:

5.1 Object Information

5.2 Transport Strategy

5.7 Data/Tables/Logical Databases

6.0 Attachments and Documentation:

Вам также может понравиться