I-009 Interface and Mapping SAP ECC To Hyperion Upstream 2011 - 0228 1600

I-009 Interface and Mapping SAP
ECC to Hyperion Upstream

Interface Functional Specification
IHS Vanguard Project
Functional Specification - Interface

I-009 Interface and Mapping SAP ECC to Hyperion
Upstream (Extract Program)
Document Reference: Month-End Closing Process

Version: 1.2
Document Status: Draft
Author: Jim Chin

Contributor: <IHS FA>
Last Revision Date: February 18, 2011

Date Created: January 12, 2011
Date Printed: NA
<File Name> <Date> <Page 1 of 27>

Interface and Mapping SAP ECC to
Hyperion Upstream
Document Control
Business Area Record to Report
GAP ID
FS Definition Form ID I-009
Type of development Interface
SAP R/3 Version ECC 6.0
Global / Market Global
Approval and Distribution
Approved by Name Role Signature Date

Process Lead Mike Moreno R2R Process
Approval Lead
Development Raghuveer Cognizant
Team Lead Bhandarkar Technical
Lead
Functional Jim Chin Cognizant
Team Lead R2R Lead
IT Team Lead
Business
Owner
Business
Owner
Business
Owner
Business
Owner
Document History
Version Reason for change Date

1.0 New 14-Jan-2011
1.1 Revision 17-Jan-2011
1.4 Revision 06-Feb-2011
2
Hyperion Upstream
1.5 Revision 18-Feb-2011

1.6 Revision – Removed all information relating to Table TVARV; 28-Feb-2011
modified extract layout
3
Hyperion Upstream
Table of Contents
1 INTERFACE TRACKING..............................................................................................................................................................................5
1.1 INTERFACE CLASSIFICATION..........................................................................................................................................................5
2 INTERFACE FUNCTIONALITY REQUIREMENTS.............................................................................................................................................6
2.1 DESCRIPTION................................................................................................................................................................................6
2.2 BUSINESS JUSTIFICATION..............................................................................................................................................................6
2.3 DATA FILTER RULES.....................................................................................................................................................................6
2.4 OTHER BUSINESS RULES..............................................................................................................................................................6
2.5 PROCESS FLOW / DATA FLOW......................................................................................................................................................6
2.6 ASSUMPTIONS..............................................................................................................................................................................8
2.7 CONSTRAINTS...............................................................................................................................................................................8
2.8 OUT OF SCOPE............................................................................................................................................................................8
3 INTERFACE DATA REQUIREMENTS............................................................................................................................................................8
3.1 SOURCE INTERFACE DATA LAYOUT...............................................................................................................................................8
3.2 TARGET INTERFACE DATA LAYOUT..............................................................................................................................................13
3.3 SOURCE / TARGET DATA MAPPING.............................................................................................................................................23
3.4 SPECIAL CASE: BI-DIRECTIONAL REAL-TIME INTERFACE..............................................................................................................23
3.5 SAMPLE DATA............................................................................................................................................................................23
3.6 DATA RETENTION.......................................................................................................................................................................23
4 SAP REQUIREMENTS.............................................................................................................................................................................23
4.1 INTERFACE TRIGGER IN SAP AND/OR MIDDLEWARE....................................................................................................................23
4.2 SAP TRANSACTION....................................................................................................................................................................23
4.3 SAP SCHEDULING / PERFORMANCE REQUIREMENTS / SERVICE LEVEL AGREEMENT....................................................................24
4.4 SAP SPECIAL REQUIREMENTS....................................................................................................................................................24
4.5 CUSTOM TABLES / STRUCTURE IN SAP.......................................................................................................................................24
5 M/W SOLUTION (IF APPLICABLE).............................................................................................................................................................24
5.1 MIDDLEWARE SOLUTION.............................................................................................................................................................24
5.2 MAPPING RULES & CONVERSION CRITERIA..................................................................................................................................25
6 INTERFACE CONTROLS...........................................................................................................................................................................25
6.1 COMPLETENESS CONTROL..........................................................................................................................................................25
6.2 ACCURACY CONTROL.................................................................................................................................................................25
6.3 DUPLICATE RECORDS CONTROL.................................................................................................................................................25
6.4 ERROR DETECTION AND COMMUNICATION CONTROL...................................................................................................................25
6.5 INTEGRITY OF DATA TRANSFORMATION CONTROL.......................................................................................................................27
6.6 STANDARD FILE FORMAT CONTROL............................................................................................................................................27
6.7 INTERFACE DATA SECURITY........................................................................................................................................................27
7 TESTING SCENARIOS.............................................................................................................................................................................27
4
Hyperion Upstream
1 Interface Tracking
1.1 Interface Classification
Interface
I-009
Number
Interface
Interface and Mapping SAP ECC to Hyperion Upstream
Name
Inbound Interface data flows inbound to SAP R/3
Direction X Outbound Interface data flows outbound from SAP R/3
(with respect
to SAP R/3)
Other Specify:
Batch One-way transfer of “accumulated” data set; Usually done by scheduled file transfer.
Near Real-Time One-way message-based transfer of data; Usually triggered by event.
Interface Real-Time Immediate transfer of small data set; Usually triggered by event.
Type Excel Upload Manually invoked from SAP session; Local spreadsheet file uploaded from PC.
X Other Specify: Extract from SAP ECC to Excel CSV File
Hourly Details:
Daily Details:
Weekly Details:
X Monthly Details: Monthly extract
Interface
Quarterly Details:
Frequency Yearly Details:
X On-Demand How often: At month end and then on demand
Other Specify:
X Full record load Send all records every time interface is executed
Type of Delta full records Only send records where one or more fields have changed since previous execution
Records Delta records Only send fields (and keys) that changed since previous interface execution
Sent X Other Specify: First time the interface is run, all records will be sent. On demand
execution, all records will be sent
Volume Average Volume: TBD
(per single
Peak Volume:
execution)
5
Hyperion Upstream
2 Interface Functionality Requirements
2.1 Description
Accounting entries posted in the SAP ECC system is to be extracted on a monthly basis and
interfaced the IHS Hyperion.
In addition, an on-line audit report is required by the user to validate the summarized information
loaded into Hyperion.
2.2 Business Justification
Hyperion is a business performance management system which helps businesses to gather,

organize, and analyze business data. IHS uses the Hyperion system to consolidate all financial
information originating on their legacy system. Statutory reporting to the Securities Exchange
Commission at the IHS consolidated level is created from the Hyperion system.
2.3 Data Filter Rules
Not applicable
2.4 Other Business Rules
2.5 Process Flow / Data Flow

The following diagram visually describes the process flow for extracting data from SAP ECC to Hyperion.
An extract file will be produced in the appropriate output format for loading into Upstream. Upstream is
the translation tool that accounting uses to map legacy financial information into Hyperion.
6
Hyperion Upstream
FAGLFLEXA ZTGL_MAILRECVRS ZTGL_MAILTXT T001 ZTFI_HYP_EXT_SUM
BKPF BSEG SKAT ZTFI_SHIP_TO_REG VBPA ADRC
Input selection
parameters
ZTFI_HYP_EXTRACT
Produce extract
Extract File Yes
Update table with file
period results
No
Display period Extract File Email Notification

No
results Successful to Finance & IT
Yes
Send extract file

to Shared Folder
Email Notification
to Finance
End
7
Hyperion Upstream
2.6 Assumptions
 Upstream is the middleware used to load the SAP extract information into the format needed for
Hyperion.
 At time of cut-over, an extract will be performed to start the opening balances
 If the period exists in the ZTFI_HYP_EXTRACT Hyperion Extract Details table and data is
updated in the period then the Z table will be refreshed with the updated data when the
information is extracted to Hyperion.

2.7 Constraints
None known.
Description of Constraint Constraint Type

Comment
Constraint Reported By (Data or Business)
2.8 Out of Scope Not Applicable
Description of Item Type

Comments
Out-of-Scope Item Reported By (Data or Business)
3 Interface Data Requirements
3.1 Source Interface Data Layout
The source data for the interface will be extracted from BKPF Accounting Document Header and BSEG
Accounting Document Segment tables. Text description for the general ledger account will be retrieved
from the SKAT G/L Account Master Record (Chart of Accounts: Description). A field called ship-to region
is a geographical designation that will be associated with a country. This field will be created in custom
table ZTFI_SHIP_TO_REG – Ship to Region with Validity Dates along with its relationship to the country
within a period of time.
The ship-to region needs to be assigned to the line item of the document where a sales order is recorded.
The program will search for the ship-to country by deriving the information from the billing document on
8
Hyperion Upstream
the BSEG table. From the billing document, it will find the corresponding billing document value on VBRP
and find the sales order number on the row line. From the sales order, it will check the partner function in
the VBPA Sales Document: Partner table. If there is a ship to partner function then it will retrieve the
address number. From the address number, it will check the ADRC Address table and find the country
field. From the country field, it will check Table ZTFI_SHIP_TO_REG – Ship to Region with Validity Dates
and find the country key and the ship-to region associated with that country. If there is no ship to partner
function then it will check if there is a sold to function and follow the same procedure in deriving the ship
to region.
The currency key that is needed for online display for each general ledger account will be retrieved from
table T001 Company Codes.
A selection screen is required to input parameters for extraction of the SAP information and for online
display of the extracted information. The input parameters will be Chart of Accounts, company code,
fiscal year and period. The Chart of Accounts field will be pre-populated with IHS1. This screen can be
viewed under the Hyperion Extract Screen section.
When the selection is for extraction of the SAP information(Execute icon), it will follow the Extract Save
Process in Section 3.2 Target Interface Data Layout.
When the extract file is produce, it will follow the Extraction of file and Notifications section.
When the selection is for online display (Audit Report) it will follow the Audit Report Display Process in
the same section.
Source data is available as (Type “X” for all that apply):

X Database Table Name(s): BKP, BSEG , SKAT, Z Table 1, VBPA, ADRC
File Type:
X Procedure Name: Custom transaction code
Other Method:
If indicated “Database” above, please provide the table columns necessary for this interface:
Source: SAP Table Structure – BKPF Accounting Document Header
Table Field Element Description Data Type Length

BKPF MANDT Client CLNT 3
BKPF BUKRS Company Code CHAR 4
BKPF BELNR Accounting Document Number CHAR 10
BKPF GJAHR Fiscal Year NUMC 4
BKPF BUDAT Posting Date in the Document DATS 8
BKPF MONAT Fiscal Period NUMC 2
Source: SAP Table Structure – BSEG Accounting Document Segment

BSEG MANDT Client CLNT 3
9
Hyperion Upstream
Source: SAP Table Structure – SKAT G/L Account Master Record (Chart of Accounts: Description)

SKAT MANDT Client CLNT 3
SKAT SPRAS Language Key LANG 1
SKAT KTOPL Chart of Accounts CHAR 4
SKAT SAKNR G/L Account Number CHAR 10
SKAT TXT20 G/L account short text CHAR 20
Source: SAP Table Structure – T001 Company Codes

SKAT MANDT Client CLNT 3
SKAT BUKRS Company Code CHAR 4
SKAT WAERS Currency Key CUKY 5
Source: SAP Table Structure – ZTFI_SHIP_TO_REG – Ship to Region with Validity Dates

Z Table MANDT Client CLNT 3
Z Table LAND1 Country Key CHAR 3
Z Table ZZ_SUPREG Super region per country CHAR 2
Z Table ZVALID_FROM Valid-From Date DATS 8
Z Table ZVALID_TO Valid To Date DATS 8
Values for Super region per country
Table Field Element Description Value

Z Table ZZ_SUPREG Super region per country 01 - Americas
Z Table ZZ_SUPREG Super region per country 02 - EMEA
Z Table ZZ_SUPREG Super region per country 03 - APAC
Source: SAP Table Structure – VBPA Sales Document: Partner
10
Hyperion Upstream

VBPA MANDT Client CLNT 3
VBPA VBELN Sales and Distribution Document CHAR 10
Number
VBPA POSNR Item number of the SD document NUMC 6
VBPA PARVW Partner Function CHAR 2
VBPA KUNNR Customer Number 1 CHAR 10
VBPA ADRNR Address CHAR 10
Source: SAP Table Structure – ADRC Addresses (Business Address Services)

ADRC MANDT Client CLNT 3
ADRC ADDRNUMBER Address number CHAR 10
ADRC COUNTRY Country Key CHAR 3
If indicated “File” above, please provide the fields here (preserve order): Not Applicable
Field # Field Description Data Type Length
If indicated “Procedure” above, please provide the fields of the result set here:
Hyperion Extract Screen
11
Hyperion Upstream
The Chart of Accounts IHS1 will default in the Chart of Accounts field.
Field Name Field Description Data Type Length

KTOPL Chart of Accounts CHAR 4
BUKRS Company Code CHAR 4
GJAHR Fiscal Year NUMC 4
MONAT Fiscal Period NUMC 2
If indicated “Other” above, please list field detail here:

Not Applicable
If you have preferences or concerns on the information in this section, please mention them here:
Not Applicable
3.2 Target Interface Data Layout
The target interface data layout in the “File” section describes how information is extracted and saved,
where the file is to be extracted to, what notifications are sent and what is displayed online when input
parameters are processed by the program. The Extract and Save Process section describes how the
extracted SAP information is to be saved in Z Table 2 Extract Information and Audit Display. The
Extraction of file and Notifications section describes where the extract file is to be sent and what
notifications are emailed. The Audit Report Layout section provides a visually view of how the
information is to be displayed online.
12
Hyperion Upstream
The target interface data layout in the “Procedure” section lists the table structure of where the extract
information is to be saved. This table is populated when the user selects the Execute icon in the
Hyperion Extract Screen.
Procedurally, the processing of the target interface data layout for the “File” and “Procedure” sections
will be explained in its respective sections below.
Target data can be delivered as (Type “X” for all that apply):
Database Table Name(s):
X File Type: Comma Delimited
X Procedure Name: Z Table 2 Extract Information and Audit Display
Other Method:
If indicated “Database” above, please provide the table columns necessary for this interface: Not
applicable
Table Column Element Description Data Type Length
If indicated “File” above, please provide the fields here (preserve order):
When the input parameters are entered in the Hyperion Extract Screen in the “Procedure” section from
Source Interface Data Layout section and the user selects the Execute icon, the program will update the
table ZTFI_HYP_EXTRACT Hyperion Extract Details based on the instructions in the Extract Save
Process section. Details for the extracting the file and notifications to be sent will be explained in the
Extraction of file and Notification section.
Extract and Save Process
The following section will procedurally explain how the extract information is to be saved in the table
ZTFI_HYP_EXTRACT Hyperion Extract Details for each period extracted.
From the Hyperion Extract screen, the program will select general ledger accounts from the IHS1 Chart of
accounts, the range of company codes entered, the fiscal year and period. If the period is the first period
of the fiscal year then the opening balances will be zero.
If the periods are special periods 13 to 16, then this information will be displayed as period 12 information.
The program will select the documents from tables BKPF, BSEG and FAGLFLEXA. The document
amount will be the local currency amount.
The program will check if there is a billing document number on the document line item. From the billing
document, it will find the corresponding billing document value on VBRP and find the sales order number
on the row line. From the sales order the program will derive the ship-to region by checking the partner
function in the VBPA Sales Document: Partner table. If there is a ship to partner function then it will
retrieve the address number. From the address number, it will check the ADRC Address table and find
the country field. From the country field, it will check the table ZTFI_SHIP_TO_REG – Ship to Region
with Validity Dates and find the country key and the ship-to region associated with that country. If there is
13
Hyperion Upstream
no ship to partner function then it will check if there is a sold to function and follow the same procedure in
deriving the ship to region. The ship-to region will be assigned it to that line item.
It will sort the selected documents first by company code with follow on sorts by general ledger account
within the company, by profit center within the general ledger account, by ship-to region within the profit
center and by cost center within a general ledger account.
During the document selection process, the program will summarize information based on the sorting
process. For each balance sheet account (range 100000 to 399999), there will be a summary value of all
documents associated with that account. For example, the table below shows the summary debit and
credit values for cash (110060) and accrued payable (200020) accounts. It will calculate the Year to Date
Ending Balance by adding the opening balance from the Z table plus the Total Debits minus the Total
Credits. The opening balance is the prior period balance. The Profit Center, Ship-to Region and Cost
Center fields will be zero filled if no value is found during this sort selection.
The program will write to the table ZTFI_HYP_EXTRACT Hyperion Extract Details table the summary
debits and credits by general ledger account. The Year to Date Ending Balance will be the opening
balance for the next period.
Year to
Company Profit Ship-to Cost Item Opening Date
GL Account Total Debits Total Credits
Code Center Region Center Text Balance Ending
Balance
1000 110060 0 0 0 0 1500 -1000 500
1000 200020 0 0 0 0 400 -1400 -1000
For revenue accounts (range 400000 to 499999), there will be a summary value of all documents
associated with that account. However, the summary value will be broken down by ship-to region, profit
center and general ledger relationships on the line item of the document. The table below shows the
summary debit and credit values for the Revenue Consulting (400100) and Revenue Other (400300)
accounts and its relationship to a profit center and ship-to region. It will calculate the Year to Date Ending
Balance by adding the opening balance from the Z table plus the Total Debits minus the Total Credits.
The opening balance is the prior period balance.
debits and credits by general ledger account, profit center and ship-to region. The Year to Date Ending
Balance will be the opening balance for the next period. The Ship-to Region will be populated with the
numeric value 01, 02 or 03 which represents Americas, EMEA and APAC. The Cost Center field will be
zero filled if no value is found during this sort selection.
Year to
Balance
1000 400100 123 01 0 0 0 0 500 -500
1000 400100 123 02 0 0 0 0 600 -600
1000 400100 123 03 0 0 0 0 700 -700
1000 400300 901 0 0 0 0 0 800 -800
14
Hyperion Upstream
For expense accounts (range 500000 to 799999), there will be a summary value of all documents
associated with that account. However, the summary value will be broken down by the cost center and
general ledger relationship on the line item of the document. The table below shows the summary debit
and credit values for the Salary (600000) account and its relationship to a cost center. It will calculate the
Year to Date Ending Balance by adding the opening balance from the Z table plus the Total Debits minus
the Total Credits. The opening balance is the prior period balance. The Ship-to Region field will be zero
filled if no value is found during this sort selection.
debits and credits by general ledger account and cost center. The Year to Date Ending Balance will be
the opening balance for the next period.
Year to
Balance
1000 600000 800 0 10047000 0 0 1000 0 1000
1000 600000 800 0 10047021 0 0 2000 0 2000
1000 600000 800 0 10047026 0 0 3000 0 3000
Extraction of file and Notifications
An extract file will be created in .csv format. Any records that do not have any data in the fields will be
zero filled. All values extracted will be an absolute value. A summary total at the company code level will
be included in the extract. The assumption is that the summary total value will net to zero when all
account detail is added.
The layout of the extract file is listed in the table below.
Extract File Layout
Source: SAP Table Structure – ZTFI_HYP_EXT_SUM Hyperion Extract Summary

ZTFI_HYP_EXT_SUM MANDT Client CLNT 3
ZTFI_HYP_EXT_SUM BUKRS Company Code CHAR 4
ZTFI_HYP_EXT_SUM HKONT General Ledger Account CHAR 10
ZTFI_HYP_EXT_SUM PRCTR Profit Center CHAR 10
ZTFI_HYP_EXT_SUM SUPREG Super region per country (Americas, CHAR 8
EMEA & APAC)
ZTFI_HYP_EXT_SUM KOSTL Cost Center CHAR 10
ZTFI_HYP_EXT_SUM SGTXT Item Text CHAR 50
ZTFI_HYP_EXT_SUM OP_BAL_MTH Balance carried forward in local CURR 23
currency (Opening balance for month)
15
Hyperion Upstream

ZTFI_HYP_EXT_SUM TOT_DEBITS Balance carried forward in local CURR 23
currency (Total debits)
ZTFI_HYP_EXT_SUM TOT_CREDITS Balance carried forward in local CURR 23
currency (Total credits)
ZTFI_HYP_EXT_SUM YR_TO_DT_BAL Balance carried forward in local CURR 23
currency (Year-to-Date balance)
If the extract is successful, the program will send the file to a share folder and send an email to the user.
The share folder will be defined during development.
The naming convention for the extract file will be ZFI_R2R_HYPERION_MMYYYY hh:mm:ss.
ZFI_R2R_HYPERION represents the main body of the file name. MMYYYY represents the month and
year, hh represents the hour, mm represents the minutes and ss represents the seconds of the file
extraction.
The link to the share folder will be in the body of the email standard text sent to Finance. The addressees
to receive the email will reside in the table ZTGL_MAILTXT – Mail Text. The mail addressees to receive
this standard text are:
Mark.hickman@ihs.com
Tim.kennedy@ihs.com
The mail message would read:
<<email addressee>>,
<<subject line>> Hyperion Extract for the period YYYYMM
The Hyperion extract report ZFI_R2R_HYPERION_MMYYYY was successfully created and can
be retrieved at this link <<need URL Address>>.
The subject line and body of the text will reside in the table ZTGL_MAILTXT – Mail Text.
The user will retrieve the extract file from the share folder and upload it in Upstream.
If the extract fails, it will send an email to the above users and to the IT department. The mail message
would read
<<email addressee>>,
The Hyperion extract report ZFI_R2R_HYPERION_MMYYYY was not successfully created for
the following reasons:
16
Hyperion Upstream
<<List error messages>>
Source: SAP Table Structure – ZTGL_MAILRECVRS Mail Receivers

ZTGL_MAILTXT MANDT Client CLNT 3
ZTGL_MAILTXT ZZ_SYST Interface System CHAR 4
ZTGL_MAILTXT ZZ_MSG Interface Message ID CHAR 4
ZTGL_MAILTXT REC_NAM Recipient address NUMC 241
Source: SAP Table Structure – ZTGL_MAILTXT Mail Text

ZTGL_MAILTXT MANDT Client CLNT 3
ZTGL_MAILTXT ZZ_SYST Interface System CHAR 4
ZTGL_MAILTXT ZZ_MSG Interface Message ID CHAR 4
ZTGL_MAILTXT ZZ_LINE Interface Message Line NUMC 3
ZTGL_MAILTXT ZZ_MSG_TEXT Interface Message Text CHAR 132
Audit Report Display
The format structure to display the extract information is described in the Audit Report Layout below. This
information is retrieved from the table ZTFI_HYP_EXTRACT Hyperion Extract Details in the “Procedure”
section.
Audit Report Layout

Year to
Date
Compan GL Profit Ship-to Cost Item Opening Total Total Currenc
Period Ending
y Code Account Center Region Center Text Balance Debits Credits y
Balanc
e
The field characteristics for the Audit Report Layout are filled according to the Table – Audit Report listed
below.
Table – Audit Report
17
Hyperion Upstream
Field # Field Description Data Type Length

1 Period NUMC 2
2 Company Code CHAR 4
3 General Ledger Account CHAR 10
4 Profit Center CHAR 10
5 Super region per country CHAR 8
6 Cost Center CHAR 10
7 Item Text CHAR 50
8 Balance carried forward in local currency CURR 23
9 Total of transactions of the period in local currency (Debits) CURR 23
10 Total of transactions of the period in local currency (Credits) CURR 23
11 Balance carried forward in local currency CURR 23
12 Currency Key CUKY 5
Audit Report Display
The following section will procedurally explain how the Audit Report is to be displayed when the user
selects the Audit Report icon on the Hyperion Extract screen. The program will check the period entered
and select those records from the ZTFI_HYP_EXTRACT Hyperion Extract Details. If the period value
does not exist in the table then the program will display the message – Period ?? does not exist; Create
Extract for Period ??
If there are records that match the period value then the program will display those records from the
custom table and display them in the Audit Report Layout. The Audit Report Layout will display the
information in ALV format. It will be hierarchal with four levels of collapsing folders. These folders will be
grouped for expansion on the company code, GL Account, Profit Center, Ship-to Region and Cost Center.
The table below displays the four levels of summarization. At each summarization level there is a
positive sign icon where the user can click and the lower level information is displayed. The first level
of summarization is at the company code level. The Level 2 summarization is with balance sheet,
revenue and expense accounts. For each general ledger accounts there will be totals value in the
opening balance, total debits, total credits and year to date ending balance. The user will have the
capability to drill down to the general ledger balances. These values should equal the general ledger
balances when the program launches in the background transaction code FAGLB03 - Display Balances
(New). Level 3 summarization is at the profit center level. Level 4 is the lowest level and this information
is broken out by Americas, EMEA and APAC.
18
Hyperion Upstream
If indicated “Procedure” above, please provide the fields of the result set here:
Table ZTFI_HYP_EXTRACT Hyperion Extract Details in the Procedure will receive the summary
information when an extract is created for a period.
Target: SAP Table Structure – ZTFI_HYP_EXTRACT Hyperion Extract Details
Data Lengt
Table Field Element Description
Type h
Z MANDT Client CLNT 3 X
ZTFI_HYP_EXTRACT
Z KTOPL Chart of Accounts CHAR 4
ZTFI_HYP_EXTRACT
Z GJAHR Fiscal Year NUMC 4
ZTFI_HYP_EXTRACT
Z MONAT Fiscal Period NUMC 2
ZTFI_HYP_EXTRACT
Z BUKRS Company Code CHAR 4
ZTFI_HYP_EXTRACT
Z HKONT General Ledger Account CHAR 10
ZTFI_HYP_EXTRACT
Z PRCTR Profit Center CHAR 10
ZTFI_HYP_EXTRACT
Z SUPREG Super region per country CHAR 8
ZTFI_HYP_EXTRACT (Americas, EMEA & APAC)
Z SHKZG Debit/Credit Indicator CHAR 1
ZTFI_HYP_EXTRACT
Z ZCOUNT Line Count for Data INT4 10
ZTFI_HYP_EXTRACT Uniqueness
19
Hyperion Upstream
Data Lengt
Type h
Z WAERS Currency Key CUKY 5
ZTFI_HYP_EXTRACT
Z SGTXT Item Text CHAR 50
ZTFI_HYP_EXTRACT
Z HSLVT00 Balance carried forward in CURR 23
ZTFI_HYP_EXTRACT local currency
ZTFI_HYP_EXTRACT local currency (Period 1)
Z HSL01 Total of transactions of the CURR 23
ZTFI_HYP_EXTRACT period in local currency
(Period 1)
(Period 2)
(Period 3)
(Period 4)
20
Hyperion Upstream
Data Lengt
Type h
(Period 5)
(Period 6)
(Period 7)
(Period 8)
(Period 9)
(Period 10)
(Period 11)
(Period 12)
(Period 13)
(Period 14)
(Period 15)
(Period 16)
If indicated “Other” above, please list field detail here:

Not Applicable
If you have preferences or concerns on the information in this section, please mention them here:
Not Applicable
21
Hyperion Upstream
3.3 Source / Target Data Mapping
Not applicable
Source Target
Transformation Comments
Element Element
3.4 Special Case: Bi-Directional Real-Time Interface
Not applicable
3.5 Sample Data
3.6 Data Retention

In file based interfaces a “backup” copy of interface data can be retained in the middleware for each
execution. This can be useful for reconciliation purposes. Please indicate the retention period for this
interface. If not file based, then the source or target system must fill any data retention requirements.
Heather questions….is this really a backup? If it is, no issue. No issue.
None Data retention is not necessary for this interface
7 days
15 days (default)
30 days
Other Specify:
4 SAP Requirements
4.1 Interface Trigger in SAP and/or Middleware
4.2 SAP Transaction

If the interface uses an SAP transaction to extract or insert data, please capture the details here.
Custom SAP Transaction (New) Name: Development Team will decide
Custom SAP Transaction (Existing) Name:
Standard SAP Transaction Name:
None
22
Hyperion Upstream
4.3 SAP Scheduling / Performance Requirements / Service Level

Agreement
N/A
4.4 SAP Special Requirements
No Special Requirement
4.5 Custom Tables / Structure in SAP

< Please provide information about the custom tables and / or Structure needed.>
Table Name
Short text
Size category
Table maintenance
allowed
Data class
Buffering
Table maintenance
generation
Authorization Group
Field Data Element Domain Type Length Check Key Foreign Description
Name Table- Field Key
Field
Comments
5 M/W solution (if applicable)
5.1 Middleware Solution
Not applicable
5.2 Mapping Rules & Conversion criteria
Not applicable
23
Hyperion Upstream
6 Interface Controls
6.1 Completeness Control
Control Control Addressed

Extract program delivers file is to Delivery of .csv file for upload by user into Upstream.
share folder
Extract program fails to deliver file is If any records fail in during the extract, the log file will indicate
to share folder the type of error and send a notification to the user with a link to
the file log.
6.2 Accuracy Control

Extract program delivers file is to An Online Audit Report of the data will be generated with each
share folder extract. Control totals will be compared between the Audit
Report and the extract. The SAP system will have drill down
capability from this report into the transactional level in order to
facilitate the research of any differences.
6.3 Duplicate Records Control

e.g.
Target system overwrites updates in New load file is produced for any updates in a period.
SAP system and produces new
extract file
Extract program delivers file is to An Online Audit Report of the data will be generated with each
share folder extract. Controls totals will be compared between the Audit
Report and the extract. The SAP system will have drill down
capability from this report into the transactional level in order to
facilitate the research of any differences.
6.4 Error Detection and Communication Control
6.4.1 Data Error (Non-Execution) Notification

Notification Mechanism:
X Email Notification Send To: Mark.hickman@ihs.com and Tim.kennedy@ihs.com
Other Specify:
24
Hyperion Upstream
Urgency:
X Immediate
Next Business Day
Before Specific Event Specify:
Impact to business in the event of this error:

Unable to upload
6.4.2 Non-Fatal Execution Error Notification

Email Notification Send To: <E-Mail ID>
Write to Error Log Elements: Contract number, sold to number, error description
Other Specify:
Urgency:
Immediate
Next Business Day
6.4.3 Fatal Execution Error Notification

Email Notification Send To: <E-Mail ID>
Write to Error Log Elements:
Other Specify:
Urgency:
Immediate
Next Business Day

e.g.
6.4.4 Fatal Execution Error Progress Handling:

Commit Progress Records that were successfully processed before the error are committed to target before the apend
Back Out Progress All records from this interface execution are removed from target system even if they were successful
Other Specify: In case update is in progress, and some error happens, then intention is to have interface do
rollback and resubmit (from SAP) again after correction of the issue.
6.5 Integrity of Data Transformation Control
25
Hyperion Upstream
6.6 Standard File Format Control
6.7 Interface Data Security

<e.g. “Only persons with the security <e.g. “All data sent between sending and receiving systems are
role interface path access have the saved to a secure subdirectory that no individuals have access
ability to access the data for this to. This follows IHS IT Compliance Policies.”>
interface.”>
Security Access Site access is password protected
Data transfer security Interface will use Project data transfer standards
7 Testing Scenarios
<Please provide detail testing scenarios>
Normal Functionality - test cases that ensure the report functions as it should.
ID Description
1 Execute custom transaction code
2 Select execute button to extract file
3 Confirm email validation
4 Retrieve .csv file from share folder
5 Upload Hyperion extract file into Upstream.
6 Validate balances between online audit report and Hyperion
Exception - special logic or exceptions (e.g. report should exclude certain specific condition)
5
6
Error Handling - functionality in case of errors (e.g. Error Message or Error Log )
7 Error: No data extracted
26
Hyperion Upstream
8 Send email to IT and Finance

9 Error: Unable to update table
11 Error: Unable to write to file
27

I-009 Interface and Mapping SAP ECC To Hyperion Upstream 2011 - 0228 1600

Cargado por

Información del documento

Título original

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

I-009 Interface and Mapping SAP ECC To Hyperion Upstream 2011 - 0228 1600

Cargado por

Copyright:

Formatos disponibles

I-009 Interface and Mapping SAP

ECC to Hyperion Upstream

IHS Vanguard Project

Functional Specification - Interface

Document Reference: Month-End Closing Process

Author: Jim Chin

Last Revision Date: February 18, 2011

<File Name> <Date> <Page 1 of 27>

Business Area Record to Report

FS Definition Form ID I-009

Type of development Interface

SAP R/3 Version ECC 6.0

Global / Market Global

Approval and Distribution

Approved by Name Role Signature Date

Version Reason for change Date

1.5 Revision 18-Feb-2011

1.1 Interface Classification

2 Interface Functionality Requirements

2.2 Business Justification

Hyperion is a business performance management system which helps businesses to gather,

2.3 Data Filter Rules

2.4 Other Business Rules

2.5 Process Flow / Data Flow

FAGLFLEXA ZTGL_MAILRECVRS ZTGL_MAILTXT T001 ZTFI_HYP_EXT_SUM

BKPF BSEG SKAT ZTFI_SHIP_TO_REG VBPA ADRC

Display period Extract File Email Notification

Send extract file

Description of Constraint Constraint Type

2.8 Out of Scope Not Applicable

Description of Item Type

3 Interface Data Requirements

3.1 Source Interface Data Layout

Source data is available as (Type “X” for all that apply):

Table Field Element Description Data Type Length

Source: SAP Table Structure – BSEG Accounting Document Segment

Table Field Element Description Data Type Length

Table Field Element Description Data Type Length

Source: SAP Table Structure – T001 Company Codes

Table Field Element Description Data Type Length

Table Field Element Description Data Type Length

Values for Super region per country

Table Field Element Description Value

Source: SAP Table Structure – VBPA Sales Document: Partner

Table Field Element Description Data Type Length

Source: SAP Table Structure – ADRC Addresses (Business Address Services)

Table Field Element Description Data Type Length

Field # Field Description Data Type Length

Hyperion Extract Screen

Field Name Field Description Data Type Length

If indicated “Other” above, please list field detail here:

3.2 Target Interface Data Layout

Table Column Element Description Data Type Length

Extract and Save Process

Extraction of file and Notifications

The layout of the extract file is listed in the table below.

Extract File Layout

Source: SAP Table Structure – ZTFI_HYP_EXT_SUM Hyperion Extract Summary

Table Field Element Description Data Type Length

Table Field Element Description Data Type Length

The mail message would read:

<<subject line>> Hyperion Extract for the period YYYYMM

<<List error messages>>