Tp Eng Rdrm 08 Business Requirements Mapping(Br.030)

7/29/2019 Tp Eng Rdrm 08 Business Requirements Mapping(Br.030)

1/17

Business Requirements Mapping BR.030

(TP-ENG-RDRM-08)

Version Control Sheet

Project Name :

Document Name : Business Requirements Mapping BR.030(TP-ENG-RDRM-0

Effective date :

Author: Reviewer: Approver:

Signature Signature Signature

Electronic copies valid without signature

Document revision history

Version

No.Effective date Last Updated By Nature of modification

Master files are stored electronically and are available to all associates

Printed copies of the master files are for reference only.

Company ConfidentialTemplate Ver. 1.0

Last update on : 20-Jan-2010 Page: 1 of 17


2/17

Change Record

##################

Date Version

Reviewers

Distribution

Note To Holders:

If you receive an electronic copy of this document and print it out, please write your name

on the equivalent of the cover page, for document control purposes.

If you receive a hard copy of this document, please write your name on the front cover,

for document control purposes.

Contents

Document Control

BRS Solution - Salary Structure

BRS Solution Earnings Components

BRS Solution Organization Structure

BRS Solution Additional Organization Requirements

Open and Closed Issues for this Deliverable

Author Change Reference

Name Position

Copy Number Name Location


3/17

BRS Solution-

Functional

Area Description of Functional Area

Functional Map: Standard/ Recommended

Solution

Extension/

Customization Gap


4/17

BRS Solution-

Earnings

Components

Functional



Solution

Extension/

Customization Gap


5/17

Open and Closed Issues

Open Issues

ID

Closed Issues

ID

Issue Resolution Responsibility Target Date

Issue Resolution Responsibility Target Date


6/17


7/17

Change Record

##################

Date Version

Reviewers

Distribution

Note To Holders:

If you receive an electronic copy of this document and print it out, please write your name

on the equivalent of the cover page, for document control purposes.

If you receive a hard copy of this document, please write your name on the front cover,

for document control purposes.

Contents

Document Control

BRS Solution - Salary Structure

BRS Solution Earnings Components

BRS Solution Organization Structure

BRS Solution Additional Organization Requirements

Open and Closed Issues for this Deliverable

Copy Number Name Location

Position

Author Change Reference

Name


8/17

BRS Solution-

Functional



Solution

Extension/

Customization Gap


9/17

BRS Solution-

Earnings

Components

Functional



Solution

Extension/

Customization Gap


10/17

Open and Closed Issues

Open Issues

ID

Closed Issues

ID Issue Resolution Responsibility Target Date

Target DateIssue Resolution Responsibility


11/17


12/17

Application Replacement Mapping

This section describes the approximate replacement mapping of existing to new applications.

Application Vendor Application Vendor

MANMAN/GL ASK General Ledger Oracle

MANMAN/AP ASK AP Oracle

Payroll ADP *Retained*

External Integration Point Replacement Mapping

Application 1 Application 2 New/ Replace/

Subsume

Application 1 Application 2 Supported

Application

Interface Points?

ADP Payroll MANMAN/GL Replace ADP Payroll Oracle GL Oracle: Journal

Import Open I/F

Note:Perform the approximate replacement mapping of the applications below. If developed in-

application is the internal organization that developed the application, usually the IS organization.

list of the application mapping, you should include the non-replaced applications, with a status of

The intention of this analysis of replaced and retained applications is not to replace the rigorous a

Existing Replacement

Note:In the following table, if an existing integration point (interface) is going to need replacemen

integration point as Replace. If you designate Subsume, this implies that application functions o

contained within a single application in the new system. In some cases, it designates that we no

is New, it has no counterpart in the existing system. The suggestion is that you only draw a distin

supported interface does not exist. For example Oracle OE and AR have a supported interface

applications map onto OE or AR - merely, that they map onto Oracle Applications. It depends on

all the interface points in a complex ERP suite of applications like Oracle Applications would req

Existing Integration Point Replacement Integration Point


13/17

External Integration Point Diagram

Note:Diagrams should be a mandatory component of this deliverable. They are the best means

application map (and new interfaces required). The standards and the complexity of the implem

working on will affect this diagram.

ORACLE APPLICATIO

Supplier andPerformance

MSMBar

La

MFAR

FYPLAN

Excel

MCORPSYSTEM

AOP

JournalExpenses

Balances

Corporate

BalancesSheet

MasterDemand

Schedule

Supplier and

ProductConfig

Payroll

JournalEntries


14/17

DRP and

DemandForecast

Payroll


15/17

ouse, the vendor of the existing

If you wish to create a complete

Retained.

nalysis of application usage

t with another integration point between applications, designate the

nce performed on either side of an application interface are now

longer need the functions in the new system. If the integration point

ction between application modules in the same suite where a vendor-

oint so that you would not need to highlight whether the existing

the level of detail you wish to include in your analysis. Documenting

ire a lot of work.


16/17

to convey the future

ntation you are

NS

Codebels

EDI

Electronic Data

Interchange Inbound

Messages

Electronic Data

Interchange Outbound

Messages

InformationWarehouse

Operational Data

TRAFFICSYSTEMReceipts

MPTS

Balances and S/N's

Engineering

Change

Orders


17/17

EC System

Tp Eng Rdrm 08 Business Requirements Mapping(Br.030)

Documents

Transcript of Tp Eng Rdrm 08 Business Requirements Mapping(Br.030)