SD_GenericLabel
Project:
By:
Page 1 of 10
FUNCTIONAL SPECIFICATION FORMS
Section I: Object General Information Title (RICEF No):
Generic Label
Date:
06-21-12
m
Short description: SAP Module/Team:
SD
Release/Region:
Business process owner
Tel no:
Email:
Functional Contact:
Tel no:
Email: r m
Business Contact:
Tel no:
Email:
SAP ABAP Developer:
Tel no:
Email:
Priority:
High
Medium
Low
Complexity
High
Medium
Low
Pre-printed Forms
Yes
Frequency:
On demand
Form Type
Standard
No Daily
Weekly
Biweekly
Monthly
Others:
Custom
Change History SL. No
Date of Change
Description of Change
Author
Authorized by
0 7/
Last Revised:
Page 1 of 10
SD_GenericLabel
Project:
By:
Page 2 of 10
Table of Contents
Section I: Object General Genera l Information ...................................................... ....................................................................................... ................................. 1 Section 2: Detailed Business Purpose & Process: .............................................. ........................ 3 Section 3: Detailed functional design .......................................................................................... 3 3.1 General functional functional requirements: requirements:................................................ .......................................... 3 3.2 Detailed Functional Functional Requirements:....................................................................................... 3 3.3 Assumptions:......................................................................................................................... 5 3.4 Custom tables / Miscellaneous Miscellaneous requirements requirements if any: ............................................................ 6 Section 4: Output .......................................................................................................................... 6 4.2 Page Header and Footer: ..................................................... ....................................................................................................... .................................................. 6 4.3 Header Elements: ............................................. ..................................................... ..................................................................... ................ 7 4.3 Line Items: .............................................. ...................................................... .............................................................................. ........................ 8 4.4 Totals: ................................................................................................................................... 8 4.5 Footer: ..................................................... ........................................................................................................... .............................................................................. ........................ 9 4.6 Barcode Details (where applicable): applicable): .................................................... ..................................................................................... ................................. 9 Section 5: Additional Details ...................................................... ........................................................................................................ .................................................. 9 5.1 Risks:..................................................................................................................................... 9 5.2 Unit Test requirements........................................................ .......................................................................................................... .................................................. 9 5.3 Dependencies: Dependencies: .................................................. ..................................................... ..................................................................... ................ 9 5.4 References:.............................................. ...................................................... .............................................................................. ........................ 9 5.5 Dictionary of Terms: .................................................. .................................................... ......................................................... ..... 10
Last Revised:
Page 2 of 10
SD_GenericLabel
Project:
By:
Page 3 of 10
Section 2: Detailed Business Purpose & Process: (Provide detailed description of what triggers the form.)
2.1 Purpose and Process
(Explain the detailed business process. ):
This form will be used to generate a label for packaged goods at delivery after the final analysis has been performed.. This form will identify the final analysis of the material, receiving receiving party, the packaging material, the material number & description, customer material number & description, size, size, net weight, customer sales order number, customer text, text, and delivery number.
Section 3: Detailed functional design 3.1 General functional requirements:
Output medium: Print (Letter, A4), Fax, Email
Language requirements: English
Paper requirements: Letter, A4
Special Printer requirements: none
Trigger (Output logic/doc type etc): SAP output triggered via output condition or manually
3.2 Detailed Functional Requirements: Generic lable is needed to identify package material in the warehouse. The form will be completely custom Transaction code VL03N will be used to generate the generic label for the material from the delivery document. To capture color code: A Z table to be created created with fields fields
Last Revised:
Page 3 of 10
SD_GenericLabel
Project:
By:
Page 4 of 10
1) Customer Number (KNA1-KUNNR) 2) Material Number (MARA-MATNR) 3) Color Code ( Numberic/Number Numberic/Numbe r see attached attached pdf ) 4) Description of color code ( Red, Blue etc.. see attached pdf)
Read analysis from QA From table QAVE – QAVE – get VCODE by query on field PRUEFLOS with inspection lot from LIPS-QPLOS. If VCODE = A. (indicates inspection results accepted). Read batch characteristics using function module „ QC01_BATCH_VALUES_READ ‟ – by feeding FM with material, plant, batch values. Read the content of all characteristics from field ATINN and for value read from field ATWRT. Display Display results like attached. attached. Display Plant Logo only for plant US15 – West Virginia Alloys Show ShipTo party address by reading ship to customer from delivery document and picking address from address table. Add the “To” “To” text beside beside displaying displaying address. address. Below the Address show Text
“THIS SHIPMENT CONTAINS:” Packaging material qty “(“ Packaging material used “)” Logic to get packaging material qty and packaging material: Packaging material qty used – get this field value by quering table VEKP with delivery document number(LIPS-VBELN) in field VPOBJKEY and get VENUM, VHILM( packaging material) Query table VEPO with VENUM from above to get quantity ( VEANZ where UNVEL is null).
Last Revised:
Page 4 of 10
SD_GenericLabel
Project:
By:
Page 5 of 10
Show the finished goods material description LIPS-ARKTX or from Mara-MAKTX for LIPSMATNR. – MATNR. – Display this in Bold Font. Show “Size :” Get the size from MARA-GROES “Net Weight”: LIKPLIKP - NTGEW (by delivery number feed) “Customer Order Number”: PO number from sales order (VBKD -BSTKD) “Customer Note”: Get this from sales order „header text‟ – standard text-id “Xxxxxxxxxxxx Shipment No:” Get this from VBAK -VBELN for VBTYP = C for the delivery concernted If there is a customer material info record – please read the customer material number and display below xxxxxxxxxxxx shipment from table KNMT by querying on fields KUNNR, VKORG, VTWEG and MATNR for field KDMAT. ( Get KUNNR, VKORG,VTWEG,MATNR by joining LIPS, VBAK). Show the value of KDMAT in bold. Show the color code like for ex: Black Solid – Solid – Soldi Black colored square box Black Stripe – Stripe – Black Striped box (See the attached pdf for stiped)
Note: The form should be triggered only if quality inspection results are accepted( If VCODE = A.) Should Should get triggered either through VL03N or through a custom transaction which accepts delivery document number to display the form.
3.3 Assumptions: Materials are set up with QM view and assigned to
inspection Plan -
The user will have a saved sales outbound delivery document in the system.
-
Material should be Batch managed.
-
02,03,04 Inspection Type should be enbabled for GI Inspection
Last Revised:
Page 5 of 10
SD_GenericLabel
Project:
By:
Page 6 of 10
3.4 Custom tables / Miscellaneous requirements if any: 1.
Custom table: (Mention table details, key fields, other fields, field lengths etc): A custom z table to store the color labels per customer/material customer/material combination. The table will be generated as a part of the output procedure for this generic label form. See below a sample of output with color label.
Data Dictionary Requirements < Please provide the data dictionary requirement details, which include table names and field names along with the primary keys. If required attach the excel spreadsheet with details. > < Responsible person: IBM Interface Analyst in consultation with Functional Analyst. > DDIC Name DDIC Type Field Name
2.
Description
Primary Key
Description Additional Details Data Type
Length
Data Element
Comments
Miscellaneous requirements:
Section 4: Output 4.1 Layout:
(Insert a screen shot of sample doc)
Label with color codes
4.2 Page Header and Footer: Attachment has logo to be placed placed at header and text text in footer. The Analysis from CoA needs to be placed at the header. Below fields from Certificate profile from associated batch will be inserted on form header.
Last Revised:
Page 6 of 10
SD_GenericLabel
Project:
Cert. profile no.
By:
Certificate type
QC_SAPCOLO R
Page 7 of 10
Layout set
Short text
QM_QCERT_01
Certificate of Analysis SAP
Form Display SE71.Form QM_QCERT_01
The profile contains the following inspection characteristics:(MIC will be created) Characteristics Plant Description Results Origin 04 Inspection / batch from MIC-%Fe ---Iron Contain production chain (certificate inspection) 04 Inspection / batch from MIC-%Al ---Aluminum Contain production chain (certificate inspection ) 04 Inspection / batch from MIC-%Ca ---Calcium contain production chain (certificate inspection ) 04 Inspection / batch from MIC-%Si ---Silicon Contain production chain (certificate inspection ) Cert. profile no.
Certificate type
QC_
Layout set
Short text
QM_QCERT_01
Certificate of Analysis GranuSAP
Color coded label to be inserted based on customer-material customer-mate rial combination. List of color options attached.
4.3 Header Elements: i)
Logo: XXXXXXXXXXXX logo
ii) Sl No
Field details: SAP Field name
Last Revised:
Sap Technical name
Comments
Page 7 of 10
SD_GenericLabel
Project:
Sales Organization Shipping point
By:
Page 8 of 10
LIKS- VKORG LIKS-VSTEL
“From:” before field
Customer PO number
Note: If it is a custom form, provide the details of all the fields used. If it is the enhancement of a standard form, provide the details of the delta fields.
4.3 Line Items: Sl No
SAP Field name
Sap Technical name
Delivery Number
LIPS-VBELN
Sort sequence
Comments
Customer Material number Item number
LIPS-POSNR
Batch number Sales Unit Net Weight Sales Order
LIPS-CHARG LIPS-VRKME LIPS-NTGEW
SO line item # Material Group Packaging Material
LIPS-KDAUF LIPS-KDPOS LIPS-MAGRV
Note: If it is a custom form, provide the details of all the fields used. If it is the enhancement of a standard form, provide the details of the delta fields.
4.4 Totals: Sl No
Field
Last Revised:
Sort
Comments
Page 8 of 10
SD_GenericLabel
Project:
By:
Page 9 of 10
4.5 Footer: Sl No
Field
Comments
4.6 Barcode Details (where applicable):
Section 5: Additional Details
5.1 Risks:
5.2 Unit Test requirements Once the report is ready, it needs to be tested with test cases defined by Functional Team.
Test Case Condition 1
Description What to test
5.3 Dependencies: 5.4 References:
Last Revised:
Page 9 of 10
SD_GenericLabel
Project:
By:
Page 10 of 10
5.5 Dictionary of Terms: Definitions should be used to explain the terms relevant to this use-case
Term
Last Revised:
Description
Page 10 of 10
