SD_GenericLabel

Project: By: Page 8 of 10

FUNCTIONAL SPECIFICATION FORMS

Section I: Object General Information

Title (RICEF No):Generic LabelDate: 06-21-12

Short description:

SAP Module/Team:SDRelease/Region:

Business process owner Tel no: Email: m

Functional Contact: Tel no: Email: r m

Business Contact: Tel no: Email:

SAP ABAP Developer:Tel no: Email:

Priority:|X| High |_| Medium |_| Low

Complexity|_| High |X| Medium |_| Low

Pre-printed Forms|X| Yes |_| No

Frequency: |X| On demand |_| Daily|_| Weekly |_| Biweekly |_| Monthly |_| Others:

Form Type|_| Standard |X| Custom

Change History

SL. NoDate of ChangeDescription of ChangeAuthorAuthorized by

0

7/

Table of Contents

Section I: Object General Information1Section 2: Detailed Business Purpose & Process:3Section 3: Detailed functional design33.1 General functional requirements:33.2 Detailed Functional Requirements:33.3 Assumptions:33.4 Custom tables / Miscellaneous requirements if any:3Section 4: Output44.2 Page Header and Footer:44.3 Header Elements:44.3 Line Items:44.4 Totals:44.5 Footer:54.6 Barcode Details (where applicable):5Section 5: Additional Details55.1 Risks:55.2 Unit Test requirements55.3 Dependencies:55.4 References:55.5 Dictionary of Terms:6

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 party, the packaging material, the material number & description, customer material number & description, size, net weight, customer sales order number, customer 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 customTransaction 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 with fields 1) Customer Number (KNA1-KUNNR)2) Material Number (MARA-MATNR)3) Color Code ( Numberic/Number see attached pdf )4) Description of color code ( Red, Blue etc.. see attached pdf)

Read analysis from QA

From table 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 results like attached.Display Plant Logo only for plant US15 West Virginia AlloysShow ShipTo party address by reading ship to customer from delivery document and picking address from address table.Add the To text beside displaying 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).

Show the finished goods material description LIPS-ARKTX or from Mara-MAKTX for LIPS-MATNR. Display this in Bold Font.

Show Size : Get the size from MARA-GROESNet Weight: LIKP- 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-idXxxxxxxxxxxx Shipment No: Get this from VBAK-VBELN for VBTYP = C for the delivery concerntedIf 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 Soldi Black colored square boxBlack 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 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

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 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 NameDescription

DDIC TypeAdditional Details

Field NameDescriptionPrimary KeyData TypeLengthData Element Comments

2. 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 at header and 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.

Cert. profile no.Certificate typeLayout setShort text

QC_SAPCOLORQM_QCERT_01Certificate of Analysis SAP

Form Display SE71.Form QM_QCERT_01

The profile contains the following inspection characteristics:(MIC will be created)CharacteristicsPlantDescriptionResults Origin

MIC-%Fe----Iron Contain 04 Inspection / batch from production chain (certificate inspection)

MIC-%Al----Aluminum Contain 04 Inspection / batch from production chain (certificate inspection )

MIC-%Ca----Calcium contain04 Inspection / batch from production chain (certificate inspection )

MIC-%Si----Silicon Contain04 Inspection / batch from production chain (certificate inspection )

Cert. profile no.Certificate typeLayout setShort text

QC_QM_QCERT_01Certificate of Analysis GranuSAP

Color coded label to be inserted based on customer-material combination. List of color options attached.

4.3 Header Elements:

i) Logo: XXXXXXXXXXXX logo

ii) Field details: Sl NoSAP Field nameSap Technical nameComments

Sales OrganizationLIKS- VKORG

Shipping pointLIKS-VSTELFrom: 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 NoSAP Field nameSap Technical nameSort sequenceComments

Delivery NumberLIPS-VBELN

Customer Material number

Item numberLIPS-POSNR

Batch numberLIPS-CHARG

Sales UnitLIPS-VRKME

Net WeightLIPS-NTGEW

Sales OrderLIPS-KDAUF

SO line item #LIPS-KDPOS

Material Group Packaging MaterialLIPS-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 NoFieldSortComments

4.5 Footer:

Sl NoFieldComments

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 CaseDescription

Condition 1What to test

5.3 Dependencies:

5.4 References:

5.5 Dictionary of Terms:Definitions should be used to explain the terms relevant to this use-caseTermDescription

Last Revised:Page 8 of 10