Project : APS Implementation at CMIFPE

Functional Specification -

Document Reference:
Version:
Document Status:

PP
1.0
In Preparation

Author:

Sharat.Sugur- Production Planning Module

Document Control
Business Area

Production Planning

GAP ID

PP

FS Definition Form ID

SAP Data transfer for Gantt Chart from SAP to APS

SAP R/3 Version

ECC 6.0

Global / Market

Gantt chart data .doc

05-12-2012

Page 1 of 9

Project : APS Implementation at CMIFPE

Approval and Distribution

Approved by
Process Team
Lead
Client Project
Manager

Name
Mr. Jaikumar
Subramanian
Mr. Ashutosh
Deshpande

Role
IBM Project
Manager
CMI FPE
Project
Manager

Signature

Date

Document History
Version
1.0
1.1
1.2
1.3

Reason for change

Initial Version

Date
05-12-2012

General Information
Area (SAP System components):
Short description:
Requested by:
Author:

PP
Data transfer from SAP to APS
TBD
Sharat Sugur

Date:

05-12-2012

Tel no:
Tel no:

TBD
TBD

Program Transaction code:

Task ID/Demand Number:

TBD

Project Name:

APS Implementation at CMI FPE

Priority:

High/mandatory
Low/optional

Complexity:
Volume of data:
Mode:
Frequency:
Technical information:
1. Report created using:

2. Characteristics required:

General information:
1. Results if no Reports are
created:

Gantt chart data .doc

High

Medium/recommended
Medium

Low

High
TBD
DATE AVAILABLE FROM:
Online
Background
Daily
Weekly
Monthly
Biweekly
Others (Specify) : On Demand
Report Painter
ABAP program
R/3

Report Writer
Info system
BW

SAP Query
Crystal Reports

Drilldown
Buttons
Sort
ALV Grid
ALV List
Entry file
Others: Call Transaction
Legal requirements not fulfilled
Lack of essential business information
Lack of functions compared to legacy system
Others (Specify):

05-12-2012

Page 2 of 9

Project : APS Implementation at CMIFPE

DURATION OF DEVELOPMENT WORK

(IN MAN-DAYS):

Is there an alternative in the

standard system?
Description of alternative:
Reasons why alternative is not
acceptable:

Gantt chart data .doc

15 days (Coding+Documentation+Testing)
Yes

No

Performance problems
Others (Specify) :

05-12-2012

Complexity

Page 3 of 9

Project : APS Implementation at CMIFPE

1. Business Needs & Requirements

CMI FPE is implementing APS Plan visage tool with interface to SAP which is already in
place. Need is to transfer the different parameter dates required to prepare Gantt chart in APS.

2. Issues
None
Issue
#

Issue
owner

Date
Raised

Issue Description

Issue Resolution

Resolved
By & Date

3. Selection Screen Details

Project

Selection
range

Custom development to be done to meet the requirement.

Desired screen design (selection possibilities):
(Use attachment if necessary):

4. Current Functionality
No System generated Gantt charts available. Currently CMI FPE team is managing with manual
Gantt chart preparation.

5. Desired Functionality
Send the different dates from SAP which are required to prepare Gantt chart in APS.
Functional details are as follows.
Data to be sent to APS server in 2 forms,
1. Project wise data
2. Assembly wise data
These facilities to be enabled in the transaction ZPV_DD and should work independently with check box
and program should process only the data related to check box for the download.
Provision to be made to set these data download in background scheduling job and successful file should
be stored in the desired server path in txt format.

Gantt chart data .doc

05-12-2012

Page 4 of 9

Project : APS Implementation at CMIFPE

As defined in the selection screen entry, if any project is mentioned then perform the process for
defined project only, if not then run the process for all projects.
As per the desired output format, output is divided in 5 major departments like project definition,
procurement data, component manufacturing data, assembly manufacturing data and dispatch actual
data and 17 different date columns.
Below are the steps to be performed for assembly wise and project wise data capture and to be provided
in the output.
Following are the steps to be followed to arrive at the logic:
Step 1: Collect all active projects and WBS structure elements which are active meaning, these Project
definition and WBS elements should not have system status of TECO, CLSD, LKD, DLFL and should not
have user status HOLD.
Step 2: Go to each individual WBS structure and collect the materials associated in each WBS. If material
attached has bill of material, then consider all materials under the attached assembly bill of material. This
has to be done for all the materials attached in WBS element irrespective of plant.
Step 3: Logic for Procurement data
Procurement has 4 dates to be populated. For this following steps to be followed
3.1 For all the materials listed against the WBS element, should be run through the loop for each material
and identify following dates.
3.2 Find out all Purchase requisitions created with reference to WBS element either they are deleted or
open or PR is already converted into purchase order.
Note: If any PR created for this WBS structure without reference of WBS element then that PR can not be
considered.
3.3 Out of all purchase requisitions listed, find out the earliest date (smallest date) of the purchase
requisition requisitions date (creation date) which should appear as procurement plan start date of
this assembly of the WBS element.
3.4 Out of a purchase requisitions listed, find out the latest date (highest date) of the purchase
requisition delivery date which should appear as procurement plan end date of this assembly of the
WBS element.
3.5 Out of all purchase requisitions listed, find out the earliest date (smallest date) of the purchase
requisition release date which should appear as procurement actual start date of this assembly of the
WBS element.
3.6 Out of all purchase orders listed, find out the latest date (highest date) of the purchase order
delivery date which should appear as procurement actual end date of this assembly of the WBS
element, this has to be captured from material document posted through MIGO transaction for this PO.
Step 4: Logic for Component manufacturing data
Component manufacturing tab has 4 dates to be populated. For this following steps to be followed
4.1 For all the materials listed against the WBS element, should be run through the loop for each material
and identify following dates.
4.2 Find out all planned orders created with reference to WBS element either they are converted to
production order or open planned orders.
Note: If any Production order manually created with reference to WBS element then there will not be any
planned order for this in the system, so this order can not be considered in plan.

Gantt chart data .doc

05-12-2012

Page 5 of 9

Project : APS Implementation at CMIFPE

4.3 Out of all planned orders listed, find out the earliest date (smallest date) of the planned order Start
date which should appear as component manufacturing plan start date of this assembly of the WBS
element.
4.4 Out of all planned orders listed, find out the latest date (highest date) of the planned order delivery
date which should appear as component manufacturing plan end date of this assembly of the WBS
element.
4.5 Out of all production orders listed, find out the earliest date (smallest date) of the production order
release date which should appear as component manufacturing actual start date of this assembly of
the WBS element.
4.6 Out of all production orders listed, find out the latest date (highest date) of the production order
delivery date which should appear as component manufacturing actual end date of this assembly of
the WBS element.
Step 5: Logic for Assembly manufacturing data
Assembly manufacturing tab has 4 dates to be populated. For this following steps to be followed
5.1 For all the materials listed against the WBS element, should be run through the loop for each material
and identify following dates.
5.2 Find out all planned orders created with reference to WBS element either they are converted to
production order or open.
Note: If any Production order manually created with reference to WBS element then there will not be any
planned order for this in the system, so this order can not be considered in plan.
5.3 Out of all planned orders listed, find out the earliest date (smallest date) of the planned order Start
date which should appear as Assembly manufacturing plan start date of this assembly of the WBS
element.
5.4 Out of all planned orders listed, find out the latest date (highest date) of the planned order delivery
date which should appear as Assembly manufacturing plan end date of this assembly of the WBS
element.
5.5 Out of all production orders listed, find out the earliest date (smallest date) of the production order
release date which should appear as Assembly manufacturing actual start date of this assembly of
the WBS element.
5.6 Out of all production orders listed, find out the latest date (highest date) of the production order
delivery date which should appear as Assembly manufacturing actual end date of this assembly of
the WBS element.
Step 6: Logic for Dispatch actual data
6.1 For all the materials listed against the WBS element, should be run through the loop for each material
and identify following dates.
6.2 Find out all invoices created for the materials listed in the WBS element either invoices are
assemblies or third party items or outsourcing items.
Note: If any invoices does not have WBS reference they are not considered.
6.3 Out of all invoices listed, find out the earliest date (smallest date) of the invoice date which should
appear as Dispatch actual start date of this assembly of the WBS element.
6.4 Out of all invoices listed, find out the latest date (highest date) of the invoice date which should
appear as Dispatch actual end date of this assembly of the WBS element.

Technical Details

Gantt chart data .doc

05-12-2012

Page 6 of 9

Project : APS Implementation at CMIFPE

6. Starting Conditions
This functionality is process related and not a report. Due to large number of data fields, system
performance and result expectation time will be more and program performance will degrade.

7. Security Requirements/ Authorization Details

None

8. Data Mapping Tables

Field Name

Field Desc

8.1.

Output
Length

Output
Type

Format

Position

SAP screen No./ field name

Desired Report Design/Layout:

C:\Users\
IBM_ADMIN\Desktop\Desired output for Gantt Chart.xls

Attached sheet is the desired output which should be created in the text forma tand this data should be
imported in APS to map the Gantt chart.

8.2.

Report Example:
(use attachment if necessary):

9. Custom Tables/Structure in SAP

Table Name
Short text
Size category
Table maintenance
allowed
Data class
Buffering
Table maintenance
generator
Authorization Group

Gantt chart data .doc

No

05-12-2012

Page 7 of 9

Project : APS Implementation at CMIFPE

Field
Name

Data Element Domain Type

Length Check
Key Foreign
Table-Field Field Key

Description

Comments

Recovery and Restart

If the program fails half way it should not have any impact on any other processes or
programs. It should be simply re-started by the user.

10. Language of texts

The texts for the report should be displayed in Users logon language. If translation is not
maintained in users logon language, he/she should be displayed with English texts.

11. Currency and Units of Measure

NA

12. Assumptions
All data are maintained correctly in the system.

13. Error Handling

Gantt chart data .doc

05-12-2012

Page 8 of 9

Project : APS Implementation at CMIFPE

14. Testing Scenarios

Normal Functionality - test cases that ensure the report functions as it should.
ID Description
1
2
3
4
Exception - special logic or exceptions (e.g. report shold exclude certain specific condition)
5
6
Error Handling - functionality in case of errors (e.g. Error Message or Error Log )
7
8

Gantt chart data .doc

05-12-2012

Page 9 of 9