Sie sind auf Seite 1von 12

Page 1 of 12

Verizon

Functional Specifications Design Document

06/05/06
Version 1.0
Physical Inventory Document Report

Project: Verizon Communication


Process: SAP SCM Planning
Variant:
Title: Physical Inventory Document Report
Type: Report

©Copyright IBM Corporation 2003

International Business Machines Corporation


Route 100
Somers, NY, 10589

USA
Printed in the United States of America
10-02

All Rights Reserved


IBM and the IBM logo are trademarks or registered trademarks
of International Business Machines Corporation in the United
States other countries, or both.

Other company, product and service names may be


trademarks or service marks of others.
CONFIDENTIALITY STATEMENT
The information in this document contains trade secrets and commercial information that are privileged or confidential and may not be disclosed unless such disclosure is required by federal or state law or regulations. In
any event, persons to whom the information is disclosed must be informed that the information is privileged or confidential and may not be further disclosed by them. These restrictions on disclosure will apply equally to
all future information supplied to you which is indicated as privileged or confidential.
Page 2 of 12

Document Control

Version Revision Revised By Revision


Date Description
1 06/05/2006 Rajkumar Abbu Initial

Approval Authority for

Name Signature Date

CONFIDENTIALITY STATEMENT
The information in this document contains trade secrets and commercial information that are privileged or confidential and may not be disclosed unless such disclosure is required by federal or state law or regulations. In
any event, persons to whom the information is disclosed must be informed that the information is privileged or confidential and may not be further disclosed by them. These restrictions on disclosure will apply equally to
all future information supplied to you which is indicated as privileged or confidential.
Page 3 of 12

Table of Contents

1.0 DOCUMENT RELATIONSHIP ENTITIES................................................................... ................5

2.0 FUNCTIONAL DETAILS.................................................................................... .........................5

3.0 ADDITIONAL DETAILS..................................................................................................... ..........6

4.0 REFERENCES................................................................................................... .........................6

5.0 CUSTOMIZED SOFTWARE DESIGN................................................................................ .........6

5.1 REPORTS: SEE ABOVE................................................................................. ..........................6

5.2 INTERFACES N/A......................................................................................................... ..............6

5.3 CONVERSION N/A................................................................................................................... ...7

5.4 ENHANCEMENTS N/A............................................................................................................... .7

5.5 FORMS: N/A.............................................................................................................................. .7

5.6 SAP WORKFLOW N/A............................................................................................................. ...7

5.7 QUESTIONS.............................................................................................................................. ..7

6.0 TECHNICAL SPECIFICATION................................................................................................. ...7

6.1 DESIGN ALTERNATIVE............................................................................................................ ..7

6.2 ISSUES.................................................................................................................................. .....8

6.3 PHYSICAL DATA MODEL....................................................................................................... ....8

6.4 PHYSICAL SOFTWARE MODEL ................................................................... ...........................8

6.5 DIAGRAMS................................................................................................................................. .8

6.6 PHYSICAL SPECIFICATION................................................................................ ......................8

6.7 DATA (INPUTS/OUTPUTS).................................................................................................... ...10

6.8 SECURITY....................................................................................................................... ..........11


CONFIDENTIALITY STATEMENT
The information in this document contains trade secrets and commercial information that are privileged or confidential and may not be disclosed unless such disclosure is required by federal or state law or regulations. In
any event, persons to whom the information is disclosed must be informed that the information is privileged or confidential and may not be further disclosed by them. These restrictions on disclosure will apply equally to
all future information supplied to you which is indicated as privileged or confidential.
Page 4 of 12

6.9 STANDARDS............................................................................................................... ..............11

6.10 OPERATION MODEL (JOB FLOWS, BUILDS, COMPONENT LIST)................................11

Functional Specification Document

CONFIDENTIALITY STATEMENT
The information in this document contains trade secrets and commercial information that are privileged or confidential and may not be disclosed unless such disclosure is required by federal or state law or regulations. In
any event, persons to whom the information is disclosed must be informed that the information is privileged or confidential and may not be further disclosed by them. These restrictions on disclosure will apply equally to
all future information supplied to you which is indicated as privileged or confidential.
Page 5 of 12

1.0 Document Relationship Entities


Related PDDs Related BPRs (Line Items)

2.0 Functional Details

FUNCTIONAL REQUIREMENTS DEFINITION

Introduction/Background:
The Springfield / Merrick Cable cut operation in NY supplies the majority of Verizon’s cable
requirements. The CARMS system in place today currently receives planning and inventory
feeds from MMIS and is the user interface for all daily operations at the facility. Cut machine
assignment, reports, forms and labels are managed in this system today. This spec will address
the Physical Inventory Report, which conducts the upcoming annual physical inventory count.

Scope/Detailed Description:

Create an ALV report that can be executed by the user to print and/or download to Excel the
physical inventory documents needed to conduct the upcoming annual physical inventory count.
The report should be executable via new transaction code ZMI21.

1. Link IKPF (Header: Physical Inventory Document) to ISEG (Physical Inventory


Document Items), via:

a. IKPF-MANDT to ISEG-MANDT
b. IKPF-IBLNR to ISEG-IBLNR
c. IKPF-GJAHR to ISEG- GJAHR

2. Link ISEG (Physical Inventory Document Items) to MAKT (Material Descriptions), via:

a. ISEG-MANDT to MAKT-MANDT
b. ISEG-MATNR to MAKT-MATNR
c. Only return records where MAKT-SPRAS = ‘EN’

3. If ISEG-CHARG value is NOT blank, link ISEG (Physical Inventory Document Items) to
MCH1 (Batches), via:

a. ISEG- MANDT to MCH1- MANDT


b. ISEG-MATNR to MCH1-MATNR
c. ISEG-CHARG to MCH1-CHARG

4. Link MCH1 (Batches) to AUSP (Characteristic Values), via:


a. MCH1-MANDT to AUSP-MANDT
MCH1-CUOBJ_BM (with leading zeros to 18 total bytes) to AUSP- OBJEK

Dependencies: Include predecessor and successor processes.

CONFIDENTIALITY STATEMENT
The information in this document contains trade secrets and commercial information that are privileged or confidential and may not be disclosed unless such disclosure is required by federal or state law or regulations. In
any event, persons to whom the information is disclosed must be informed that the information is privileged or confidential and may not be further disclosed by them. These restrictions on disclosure will apply equally to
all future information supplied to you which is indicated as privileged or confidential.
Page 6 of 12

Predecessor:

Successor:

Business Process Detail:

Business Rules/Assumptions:

Capacity Planning
Estimates
Peak Volume
Average Volume
Frequency
Record Size
Processing time (per
record)

3.0 Additional Details

Unit Test Suggestions:


Security/
Authorizations
Error handling
Archiving Back Up
Plan:

4.0 References

Primary BP Contact 1 Additional Contact 2


Contact: Contact:
Type: Complexity

5.0 Customized Software Design

5.1 Reports: See Above

5.2 Interfaces N/A

INTERFACE
Complete for Interfaces Only.
Inbound/Outbound

CONFIDENTIALITY STATEMENT
The information in this document contains trade secrets and commercial information that are privileged or confidential and may not be disclosed unless such disclosure is required by federal or state law or regulations. In
any event, persons to whom the information is disclosed must be informed that the information is privileged or confidential and may not be further disclosed by them. These restrictions on disclosure will apply equally to
all future information supplied to you which is indicated as privileged or confidential.
Page 7 of 12

Reconciliation Process
Error Handling Method
Notification Details

Scheduling Considerations:
Immediate or ASAP or Batch
Time window for execution

Legacy System Details


Contact (name/phone)
Operating System
Application System
File Locations/File name

5.3 Conversion N/A

5.4 Enhancements N/A

5.5 Forms: N/A

5.6 SAP Workflow N/A

5.7 Questions

Description Raised By Assigned To

6.0 Technical Specification

6.1 Design alternative


N/A

CONFIDENTIALITY STATEMENT
The information in this document contains trade secrets and commercial information that are privileged or confidential and may not be disclosed unless such disclosure is required by federal or state law or regulations. In
any event, persons to whom the information is disclosed must be informed that the information is privileged or confidential and may not be further disclosed by them. These restrictions on disclosure will apply equally to
all future information supplied to you which is indicated as privileged or confidential.
Page 8 of 12

6.2 Issues
Issue Owner Status Issue Description Issue Resolution
Number

6.3 Physical Data Model


N/A

6.4 Physical Software Model


N/A

6.5 Diagrams
N/A

6.6 Physical Specification

6.6.1 Pseudo Code


6.6.1.1 Read the data from IKPF and ISEG tables using inner join and put the data into
GI_PHYDOCU internal table for given selection criteria.

SELECT a~werks
a~lgort
a~iblnr
a~gjahr
a~bldat
a~gidat
a~invnu
a~xblni
a~zstat
b~zeili
b~matnr
b~meins
b~charg
b~bstar
b~buchm
FROM ( ikpf AS a INNER JOIN iseg AS b ON
a~iblnr = b~iblnr AND
a~gjahr = b~gjahr )
INTO TABLE li_phydocu
WHERE a~iblnr IN s_iblnr AND
a~gjahr IN s_gjahr AND
a~werks IN s_werks AND
a~lgort IN s_lgort AND
CONFIDENTIALITY STATEMENT
The information in this document contains trade secrets and commercial information that are privileged or confidential and may not be disclosed unless such disclosure is required by federal or state law or regulations. In
any event, persons to whom the information is disclosed must be informed that the information is privileged or confidential and may not be further disclosed by them. These restrictions on disclosure will apply equally to
all future information supplied to you which is indicated as privileged or confidential.
Page 9 of 12

a~bldat IN s_bldat AND


a~gidat IN s_gidat AND
a~invnu IN s_invnu AND
a~xblni IN s_xblni AND
a~zstat IN s_zstat.

6.6.1.2 To get the Material Description read MAKT table for the given material.

IF li_phydocu1 IS NOT INITIAL.


SELECT matnr
maktx
FROM makt
INTO TABLE li_mat
FOR ALL ENTRIES IN li_phydocu1
WHERE matnr = li_phydocu1-matnr.

IF sy-subrc = 0.
SORT li_mat BY matnr.
ENDIF.

ENDIF.

6.6.1.3 To get serial number details for the material and batch : -

6.6.1.3.1 To read the INOB table we need to prepare internal table (LI_OBJEK) for key
object which is combination of material and batch.

LOOP AT li_phydocu1 INTO lw_phydocu1.

lw_objkey-matnr = lw_phydocu1-matnr.
lw_objkey-charg = lw_phydocu1-charg.
lw_objkey-objek+0(18) = lw_phydocu1-matnr.
lw_objkey-objek+18 = lw_phydocu1-charg.
APPEND lw_objkey TO li_objkey.
CLEAR : lw_phydocu1,lw_objkey.

ENDLOOP.

6.6.1.3.2 Get OBJEK from table INOB for all entries in the internal table LI_OBJEK
and put those object keys into LI_INOB internal table.

IF NOT li_objkey IS INITIAL.

* Read INOB table for Object key


SELECT cuobj
objek
FROM inob
INTO TABLE li_inob
FOR ALL ENTRIES IN li_objkey
WHERE klart = c_klart AND
obtab = 'MCH1' AND
objek = li_objkey-objek.

IF sy-subrc = 0.
SORT li_inob BY objek.
ENDIF.

CONFIDENTIALITY STATEMENT
The information in this document contains trade secrets and commercial information that are privileged or confidential and may not be disclosed unless such disclosure is required by federal or state law or regulations. In
any event, persons to whom the information is disclosed must be informed that the information is privileged or confidential and may not be further disclosed by them. These restrictions on disclosure will apply equally to
all future information supplied to you which is indicated as privileged or confidential.
Page 10 of 12

ENDIF.

6.6.1.3.3 Read the CABN table for serial number characteristic .

SELECT SINGLE atinn


FROM cabn
INTO lv_atinn
WHERE atnam = ‘RELL_SN’. "#EC *

6.6.1.3.4 Now read AUSP table (serial number characteristic ) value for all entries in
LI_INOB and put those entries into LI_AUSP internal table.

SELECT objek
atwrt
FROM ausp
INTO TABLE li_ausp
FOR ALL ENTRIES IN li_inob
WHERE objek = li_inob-cuobj AND
atinn = lv_atinn AND
klart = c_klart.

IF sy-subrc = 0.
SORT li_ausp BY objek.
ENDIF.
6.6.1.3.5. Now prepare GI_BATCH internal table by using all LI_INOB and LI_AUSP which
contains only material , batch and serial number.

6.6.1.4 Process the data:-

6.6.1.4.1 Generate the FIELD CATOLOG for the output table.

6.6.1.4.2 Put a loop on GI_PHYDOCU and read the LI_MAT and LI_BATCH table for
material description and serial number value. Prepare final internal table
GI_FINAL.

6.6.1.5 To display the output.

Call function module REUSE_ALV_GRID_DISPLAY and pass the field catalog


and output table.

6.7 Data (Inputs/Outputs)

Input

Select-option:

1. Physical Inventory Doc IKPF-IBLNR


2. Fiscal Year IKPF-GJAHR Required Input
3. Plant IKPF-WERKS Required Input
4. Storage Location IKPF-LGORT
5. Document Date IKPF-BLDAT
6. Planned Count Date IKPF-GIDAT
7. Physical Inventory Number IKPF-INVNU
8. Physical Inventory Ref. IKPF-XBLNI
9. Count Status IKPF-ZSTAT

CONFIDENTIALITY STATEMENT
The information in this document contains trade secrets and commercial information that are privileged or confidential and may not be disclosed unless such disclosure is required by federal or state law or regulations. In
any event, persons to whom the information is disclosed must be informed that the information is privileged or confidential and may not be further disclosed by them. These restrictions on disclosure will apply equally to
all future information supplied to you which is indicated as privileged or confidential.
Page 11 of 12

Output

1. Default Display Variant (in the order specified):

a. Plant IKPF-WERKS
b. Storage Location IKPF-LGORT
c. Physical Inventory Doc IKPF-IBLNR
d. Phys. Inv. Line number ISEG-ZEILI
e. Material Number ISEG-MATNR
f. Material Description MAKT-MAKTX
g. Material UOM ISEG-MEINS
h. Batch Number ISEG-CHARG
i. Serial Number AUSP- ATWRT
j. Stock Type ISEG-BSTAR
l. Book Qty ISEG-BUCHM

2. Additional Available Fields:

a. Fiscal Year IKPF-GJAHR


b. Document Date IKPF-BLDAT
c. Planned Count Date IKPF-GIDAT
d. Physical Inventory Number IKPF-INVNU
e. Physical Inventory Ref. IKPF-XBLNI
f. Count Status IKPF-ZSTAT

6.8 Security

Authorization will be provided at the transaction code level

6.9 Standards

Development Standards and Guidelines for VERIZON Supply Chain


Transformation Project

6.10 Operation Model (Job Flows, Builds, Component List).

6.10.1 Module/Job Flows

6.10.2 Component Lists


Program Name: Z_PHY_INV_DOCUMENT

CONFIDENTIALITY STATEMENT
The information in this document contains trade secrets and commercial information that are privileged or confidential and may not be disclosed unless such disclosure is required by federal or state law or regulations. In
any event, persons to whom the information is disclosed must be informed that the information is privileged or confidential and may not be further disclosed by them. These restrictions on disclosure will apply equally to
all future information supplied to you which is indicated as privileged or confidential.
Page 12 of 12

Transaction Code: ZMI21

6.10.3 Environment Configuration


N/A

6.10.4 User Interface Design


N/A

6.10.5 User Profile Assessment


N/A

6.10.6 Data and Software Communication Interface Model


N/A

6.10.7 Interface File Layout and Mapping (Interface/Physical


Model Cross-reference)
N/A

6.10.8 Network Communication Protocol


N/A

6.10.9 Workflow Template Appendix


N/A

6.10.10 Business Warehouse Template Appendix:


N/A

CONFIDENTIALITY STATEMENT
The information in this document contains trade secrets and commercial information that are privileged or confidential and may not be disclosed unless such disclosure is required by federal or state law or regulations. In
any event, persons to whom the information is disclosed must be informed that the information is privileged or confidential and may not be further disclosed by them. These restrictions on disclosure will apply equally to
all future information supplied to you which is indicated as privileged or confidential.

Das könnte Ihnen auch gefallen