Professional Documents
Culture Documents
PDD PP .01.02.03 Bom V1.0.0
PDD PP .01.02.03 Bom V1.0.0
PDD PP .01.02.03 Bom V1.0.0
Document Details
Project IMPACT
If you are reading a copy of this document (i.e. print out of controlled electronic document or an electronic
copy of a wet ink signed paper document) you may be reading an uncontrolled version. Before making
updates, please ensure that you are using the latest version.
Page 1 of 8
Version Control
Description
Version Date Author Remarks
of Changes
Draft
1.0.0 13.05.2014 Amit Aggarwal
Preparation
Document Scope
Process Scope This document describes process for BOM creation in AVBV
Scope Exclusion
Page 2 of 8
1. INTRODUCTION..................................................................................................................................... 4
1.1. WHAT IS THE BUSINESS BLUEPRINT?.................................................................................................. 4
1.2. DOCUMENT AVAILABILITY.................................................................................................................... 4
1.3. DOCUMENT SIGN OFF........................................................................................................................ 4
2. PROCESS DESCRIPTION...................................................................................................................... 5
2.1. SUMMARY.......................................................................................................................................... 5
2.2. KEY EXPECTATIONS........................................................................................................................... 5
3. PROCESS DESIGN IN SAP...................................................................................................................... 5
3.1. BUSINESS PROCESS DESCRIPTION..................................................................................................... 5
3.2. BUSINESS PROCESS STEP: BOM CREATION........................................................................................ 6
3.3. BUSINESS PROCESS FLOW MAP: BOM CREATION PROCESS................................................................6
4. KEY DATA ELEMENTS (KDS).................................................................................................................. 6
5. INTEGRATION POINT............................................................................................................................... 6
6. INTERFACES.......................................................................................................................................... 6
7. GAPS AND SOLUTIONS........................................................................................................................... 7
8. REPORTING REQUIREMENTS.................................................................................................................. 7
9. DATA MIGRATION/CONVERSION................................................................................................................ 7
10. AUTHORIZATION................................................................................................................................. 7
Page 3 of 8
1. Introduction
The purpose of this document is to document To-Be design of Apollo business processes. The blueprint
also finalizes the detailed scope of the project.
This document is readily available to all people on the project for understanding and can access through the
controlled environment as well as through a hard copy.
Business Blue Print Document will be submitted to process owners for final sign off. Process owners are
requested to respond within three (3) business days from the date of submission, after which a discussion
on the changes required will be initiated. The document must be signed-off within five (5) business days
after the same is submitted to the process owner for the first time. If no response is received from the
Process Owner within five (5) business days, then the document will be deemed signed-off.
Page 4 of 8
Page 5 of 8
2. Process Description
2.1. Summary
This process covers the creation of multi level BOM of Finished Product and includes
the list of components with quantity required to produce the parent material.
There are many levels in BOM for Apollo Group to keep track of critical
inventory points.
The BOM is exploded and the dependent requirements are determined within
Material Requirement Planning during the planning run, after the system has
performed the procurement quantity calculation, lot-size calculation and
scheduling.
The BOM for a material can be created with multiple BOM Usage which defines
the area (such as, production or costing etc) where a BOM can be used.For
Apollo Group , Production BOM is used.
Component Scrap defined in BOM is the percentage of scrap that occurs during
production of the parent material. Component scrap is used in material
requirements planning (MRP) to determine the quantities of components
required. When exploding the bill of material (BOM), the system increases the
required quantities of the components by the calculated scrap quantity. If
component scrap has been entered in the BOM, this value applies; otherwise,
the value specified in the material master record is used.
Scrap material code can also be incorporated in BOM with ve quantity so that
during production confirmation, scrap can be receipted automatically along
with production confirmation.
Page 6 of 8
Alternate BOM can also be made for single parent material.SAP allows for the
creation of maximum 99 BOMs. Alternative Boms can be created depending
upon the business case.
Following data elements are required from INTERSPEC to create BOM in SAP.
NA
5. Integration Point
Page 7 of 8
6. Interfaces
S. Description Identification
No.
1 INTERSPEC to SAP
8. Reporting Requirements
9. Data migration/conversion
S. Description Identification
No.
10. Authorization
Page 8 of 8