AP352 AP452 Functional and Technical Design (Report)

ENABLE PROGRAM
AP352 AP452 Function and Technical Design (Report)
RPB025 Extract for IM Load
Document Name:

AP352 AP452 Functional and Technical Design (Report)

Document ID:

RPB025_PB

Document Owner:

Karen Chung

Document Version:

1.0

Document Date:

04/26/2011

Document Status:

Submitted for Approval

Modified: 8/18/2011 12:55:36 a8/p8

Page 1 of 14

AP352 AP452 Functional and Technical Design (Report)

Document Control
Deliverable Information
Deliverable Name

RPB025- Extract for IM Load

Author
Status
Location

Karen Chung
For Review

Revision History
Version No.

Date

Author

Revision Description

Authorisers for sign off

Role

Name

P&B Lead

Tamara Emerson

P&B Lead

Chris Shuart

Date Signed Off in SharePoint

Distribution - in addition to Authorisers

Name

Role

Reference Documents
Document
Location
Design Workplan Estimating https://teams.partners.dvn.com/sites/enable2/Pla
nningandBudgetingHome/designWorkplan/Estim
ating_Scheduling

Table of Contents
Modified: 8/18/2011 12:55:36 a8/p8

Page 2 of 14

AP352 AP452 Functional and Technical Design (Report)

DOCUMENT CONTROL.............................................................................................................................2
PURPOSE OF DOCUMENT........................................................................................................................5
OVERVIEW AND SCOPE...........................................................................................................................5
1.1 REPORT NAME.......................................................................................................................................5
1.2 FUNCTIONAL DESCRIPTION........................................................................................................................5
1.3 FUNCTIONAL AREA(S)..............................................................................................................................5
1.4 OWNERSHIP...........................................................................................................................................5
1.5 DEPENDENCIES / CONSTRAINTS..................................................................................................................5
1.6 ASSUMPTIONS........................................................................................................................................5
1.7 INITIATING PROCESS/TRANSACTION/PROGRAM................................................................................................6
1.8 FREQUENCY AND TIMING...........................................................................................................................6
1.9 PROCESSING TYPES................................................................................................................................6
1.10 OUTPUT TYPE (ONLINE/PRINT/SPREADSHEET)............................................................................................6
1.11 RETENTION REQUIREMENTS.....................................................................................................................6
1.12 AUDIENCE AND DISTRIBUTION...................................................................................................................6
DETAILED FUNCTIONAL REQUIREMENTS.............................................................................................6
1.13 FUNCTIONAL SPECIFICATION....................................................................................................................6
1.14 PROCESS FLOW...................................................................................................................................9
1.15 SOURCE OF DATA.................................................................................................................................9
1.16 REPORT LAYOUT..................................................................................................................................9
1.17 REPORT FIELDS.................................................................................................................................10
1.17.1 Rows ......................................................................................................................................10
1.17.2 Columns..................................................................................................................................10
1.18 FILTERS............................................................................................................................................10
1.19 SELECTION CRITERIA (PROMPTS)...........................................................................................................10
1.20 HISTORY...........................................................................................................................................11
1.21 USAGE FREQUENCY (QUERY EXECUTION FREQUENCY)................................................................................11
1.22 REFRESH RATE OF DATA ...................................................................................................................11
1.23 DEPENDENCIES...................................................................................................................................11
4.12 DRILL DOWN REQUIREMENTS..............................................................................................................11
4.13 CALCULATIONS/ALGORITHMS/DERIVATIONS ..............................................................................................11
1.24 GLOBAL CALCULATED/RESTRICTED KEY FIGURES.......................................................................................11
1.25 REPORT-TO-REPORT INTERFACE REQUIREMENTS........................................................................................12
1.26 CONDITIONS.......................................................................................................................................12
1.27 EXISTING REFERENCE REPORTS.............................................................................................................12
1.28 REPORTING VARIANT REQUIREMENTS (PRE-POPULATED PROMPTS)..................................................................12
1.29 QUERY PROPERTIES AND FORMATTING REQUIREMENTS................................................................................12
1.30 MAIN HEADING...................................................................................................................................12
1.31 SUB HEADING....................................................................................................................................12
1.32 HIERARCHIES.....................................................................................................................................12
1.33 ERROR HANDLING...............................................................................................................................12
1.34 SECURITY AND AUTHORIZATION..............................................................................................................12
1.35 CURRENCIES AND EXCHANGE RATE REQUIREMENT MATRIX .........................................................................12
1.36 PROCESSING AND OPERATIONAL CONSIDERATIONS......................................................................................12
DETAILED TECHNICAL REQUIREMENTS.............................................................................................12
1.37 TECHNICAL FLOW DESCRIPTION .............................................................................................................12
TESTING REQUIREMENTS ....................................................................................................................13
1.38 KEY UNIT TEST CONDITIONS FROM BUSINESS...........................................................................................13
Modified: 8/18/2011 12:55:36 a8/p8

Page 3 of 14

AP352 AP452 Functional and Technical Design (Report)

1.39 TECHNICAL UNIT TEST CONDITIONS........................................................................................................13
1.40 RISK AND CONTROLS UNIT TEST CONDITIONS...........................................................................................13
1.41 UNIT TESTING CONSIDERATIONS/DEPENDENCIES .......................................................................................13
OUTSTANDING ISSUES..........................................................................................................................13
APPENDIX................................................................................................................................................13
1.42 GLOSSARY OF TERMS..........................................................................................................................13
1.43 ADDITIONAL SUPPORTING/REFERENCE DOCUMENTATION...............................................................................14

Modified: 8/18/2011 12:55:36 a8/p8

Page 4 of 14

AP352 AP452 Functional and Technical Design (Report)

Purpose of Document
This document provides the functional and technical design for flat file report, RPB025.

Overview and Scope

1.1

Report Name
RPB025 Extract for IM Load

1.2

Functional Description
This report will be a flat file extract generated by running the Export package from Data
Manager in BPC Interface for Excel. This file can be saved as a comma-delimited text file
(.TXT) or a Comma Separated Value file (.CSV). Because data will be exported from two
applications in BPC, there will be 2 flat files generated. This file will be used to upload
capital budgets by capital type and by field group into IM.

1.3

Functional Area(s)
Finance & Accounting, Planning and Budgeting

1.4

Ownership
Planning & Budgeting

1.5

Dependencies / Constraints

1.6

All data must be current in the E&P Capital and Project Capital applications.

Assumptions

IM will have the corporate cost center hierarchy from ECC.

Data will be loaded to IM at Field Group level.

M&M capital will be at Facility level which is equivalent to Field level which will allow
the data to be extracted at Field Group for M&M as well.

Data will be exported by net capital $ by field group for a total year by budget
version.

IM will be able to upload the BPC generated flat file format.

A user will manually execute the Export package from E&P Capital and Project
Capital applications as needed.

Data will be exported in local currency.

Modified: 8/18/2011 12:55:36 a8/p8

Page 5 of 14

AP352 AP452 Functional and Technical Design (Report)

1.7

Initiating Process/Transaction/Program
The user will initiate the export by selecting Run Package from the Data Manager menu
in BPC Interface for Excel.

1.8

Frequency and Timing

This export will be executed monthly to export the latest forecast for the current month.

1.9

Processing Types
Not applicable to BPC

1.10 Output Type (Online/Print/Spreadsheet)

Flat File (.TXT or .CSV)

1.11 Retention Requirements

Not applicable to BPC

1.12 Audience and Distribution

Audience Group

Use/Distribution

Planning & Budgeting

To provide files for upload into IM

Detailed Functional Requirements

1.13 Functional Specification
There will be 3 files to support the process of extracting the capital data from each application.
E&P Capital and Project Capital applications will have separate Transformation, Conversion and
Data files.
Transformation File
In order to export data from the 2 capital applications to load the data to IM, transformation
files will have to be created and used during the export to generate the upload file with the
dimensions in the target application. This file can be created and maintained from Data
Manager>Maintain Transformations in BPC Interface for Excel.
The following table contains a list of the dimensions in the source and target applications: The
actual field names for IM will have to be determined during build.
Source Application (E&P Capital / Project Capital App)
Target Application (IM)
CATEGORY
CAP_ACCT
EP_COSTCTR
TIME
CURRENCY
DATASRC
Modified: 8/18/2011 12:55:36 a8/p8

SKIPPED
SKIPPED
COSTCTR(Field Group)
YEAR
SKIPPED
SKIPPED
Page 6 of 14

AP352 AP452 Functional and Technical Design (Report)

CAPTYPE
CAPTYPE
IM_ID
SKIPPED
Below is a sample of how to map dimensions from the source application to the target application.

Modified: 8/18/2011 12:55:36 a8/p8

Page 7 of 14

AP352 AP452 Functional and Technical Design (Report)

*OPTIONS
FORMAT = DELIMITED
HEADER = YES
DELIMITER=
VALIDATERECORDS=NO
ROUNDAMOUNT = 7
OUTPUTHEADER=COSTCTR,CAPTYPE,YEAR,AMOUNT
OUTPUTDELIMITER=COMMA
*MAPPING (Note: The value to the left of the = is the name of the new dimension and the value to the right of it is
the original field unless the mapping says NULL. NULL means the BPC dimension is being excluded as a field in
the data file.)
COSTCTR=EP_COSTCTR
CAPTYPE=CAPTYPE
YEAR=TIME
AMOUNT=SIGNEDDATA
DATASRC=NULL
CURRENCY=NULL
CATEGORY=NULL
IM_ID=NULL
*CONVERSION
(The name of the mapping file would be entered here)
Conversion File
The conversion file is the mapping that is used to convert the BPC IDs for each dimension into the Ids in
the target application. The mapping file is an Excel file that is created and maintained from Data
Manager>Maintain Conversions from BPC Interface for Excel. A tab can be created for each dimension
that requires mapping. The file contains 3 columns, INTERNAL (ID in source), EXTERNAL (ID in target)
and FORMULA (any rules for conversion). See sample below.

Modified: 8/18/2011 12:55:36 a8/p8

Page 8 of 14

AP352 AP452 Functional and Technical Design (Report)

For RPB025, the conversion file may be required for the capital types and time, if the IDs are different in
IM. It is assumed that Field Group (Cost Center IDs) will not have to be mapped as they will be the same
in both BPC and IM.

1.14 Process Flow

Not Applicable for BPC

1.15 Source of Data

The data for IM will be exported from the E&P Capital and Project Capital applications in BPC.

1.16 Report Layout

Below is a sample of the possible headings that would be in the flat file that would be generated from the
export package. The exact field names will be determined during build and added to the Transformation
File explained above in section 4.1.

Modified: 8/18/2011 12:55:36 a8/p8

Page 9 of 14

AP352 AP452 Functional and Technical Design (Report)

1.17 Report Fields

1.17.1 Rows
Field Name

Data Element
(Characteristic /
Key Figure)

1.17.2 Columns
Field Name

Data Element
(Characteristic /
Key Figure)

COSTCTR
CAPTYPE
YEAR
AMOUNT

Calculation /
Business Rules
(see section 3.9 for
complex formulas)

Calculation /
Business Rules
(see section 3.9 for
complex formulas)

Restrictions

Display Properties

(values, hierarchies,
variables, etc.)

(hidden, key/text, decimals,

scaling, etc.)

Restrictions

Display Properties

(values, hierarchies,
variables, etc.)

(hidden, key/text, decimals,

scaling, suppress results
etc.)

Prompt Type

Default Value

ID (Field Group)
ID
ID
Value

1.18 Filters
See selection Criteria below

1.19 Selection Criteria (Prompts)

Variable Name

Data Element

Mandatory
or Optional

(Single value, Interval (range),

Multiple Single values, Select by
Hier, by Hier Node)

Time

Mandatory

Package Prompt (TOTAL

YEAR)

ALL

Category

Mandatory

Package Prompt

BUDGET

EP_COSTCTR

Mandatory

Package Prompt (FIELD

GROUPS)

ALL

Currency

Mandatory

Package Prompt

USD

DataSrc

Mandatory

Package Prompt

ALL

Modified: 8/18/2011 12:55:37 a8/p8

Page 10 of 14

AP352 AP452 Functional and Technical Design (Report)

Variable Name

Data Element

Mandatory
or Optional

Prompt Type

Default Value

(Single value, Interval (range),

Multiple Single values, Select by
Hier, by Hier Node)

CAP_ACCT

Mandatory

Package Prompt

ALL

CAPTYPE

Mandatory

Package Prompt

ALL

IM_ID

Mandatory

Package Prompt

ALL

1.20 History
Not Applicable in BPC

1.21 Usage Frequency (Query Execution Frequency)

This query will be executed as needed to feed the latest budget version to IM.

1.22 Refresh Rate of Data

Not applicable to BPC

1.23 Dependencies
See section 3.5

4.12 Drill Down Requirements

Not Applicable in BPC

4.13 Calculations/Algorithms/Derivations
No Calculations

1.24 Global Calculated/Restricted Key Figures

Key Figure Name

Restricted /
Calculated

Modified: 8/18/2011 12:55:37 a8/p8

Restriction / Calculation Details

Page 11 of 14

AP352 AP452 Functional and Technical Design (Report)

1.25 Report-to-Report Interface Requirements

Not applicable in BPC

1.26 Conditions
Not Applicable to BPC

1.27 Existing Reference Reports

Not applicable in BPC

1.28 Reporting Variant Requirements (pre-populated prompts)

Not Applicable in BPC

1.29 Query Properties and Formatting Requirements

Not applicable in BPC

1.30 Main Heading

See report layout in section 4.4.

1.31 Sub Heading

See report layout in section 4.4.

1.32 Hierarchies
Category- Budget / Forecast
Time Total Years
Account: Capital
CapType: All capital types
Cost Center: All Field Group IDs for Total Devon

1.33 Error Handling

Not Applicable to BPC

1.34 Security and Authorization

Please refer to the security documentation for details on how this report will be accessed.

1.35 Currencies and Exchange Rate Requirement Matrix

Not Applicable to BPC

1.36 Processing and Operational Considerations

Not Applicable to BPC

DETAILED TECHNICAL REQUIREMENTS

1.37 Technical Flow Description
Not Applicable in BPC

Modified: 8/18/2011 12:55:37 a8/p8

Page 12 of 14

AP352 AP452 Functional and Technical Design (Report)

Testing Requirements
1.38 Key Unit Test Conditions from Business
ID
1

Condition
Data Manager Menu Accessible

Maintain Transformations

Maintain Conversions

Export Package

Expected Results
The user should have the correct
security to allow access.
The user can manage the existing
transformation file and validate it
successfully.
The user can manage the existing
mapping file and validate it
successfully.
The user has access to the package
and can successfully execute.

Cycle Ref.

1.39 Technical Unit Test Conditions

Not Applicable

1.40 Risk and Controls Unit Test Conditions

Not Applicable

1.41 Unit Testing Considerations/Dependencies

Create an ad hoc report to check for availability of Data before attempting to export the data.
Default logic needs to be run before any comparison for data integrity
Record run time for data export package to ensure adequate performance.
Application must be set to Available
Testing user must have correct security in BPC
BPFs complete (set up) with link to data manager package

Outstanding Issues
Issue
No

Description

Assigned To

Status

Appendix
1.42 Glossary of Terms
Term

Modified: 8/18/2011 12:55:37 a8/p8

Definition

Page 13 of 14

Impact

Resolution

AP352 AP452 Functional and Technical Design (Report)

1.43 Additional Supporting/Reference Documentation

Document Type

Modified: 8/18/2011 12:55:37 a8/p8

Document Name

Page 14 of 14