I-009 Interface and Mapping SAP ECC to Hyperion Upstream 2011_0228 1600

I-009 Interface and Mapping SAP ECC to Hyperion UpstreamInterface Functional Specification

IHS Vanguard Project

Functional Specification - InterfaceI-009 Interface and Mapping SAP ECC to Hyperion

Upstream (Extract Program)

Document Reference: Month-End Closing ProcessVersion: 1.2Document Status: Draft

Author: Jim ChinContributor: <IHS FA>

Last Revision Date: February 18, 2011Date Created: January 12, 2011Date 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 DateProcess LeadApproval

Mike Moreno R2R Process Lead

Development Team Lead

Raghuveer Bhandarkar

Cognizant Technical Lead

Functional Team Lead

Jim Chin Cognizant R2R Lead

IT Team LeadBusiness OwnerBusiness OwnerBusiness OwnerBusiness Owner

Document History

Version Reason for change Date1.0 New 14-Jan-20111.1 Revision 17-Jan-20111.2 Revision 21-Jan-20111.3 Revision 30-Jan-20111.4 Revision 06-Feb-2011

2


Hyperion Upstream

1.5 Revision 18-Feb-20111.6 Revision – Removed all information relating to Table TVARV;

modified extract layout28-Feb-2011

3


Hyperion Upstream

Table of Contents1 INTERFACE TRACKING..........................................................................................................................................................................5

1.1 INTERFACE CLASSIFICATION......................................................................................................................................................5

2 INTERFACE FUNCTIONALITY REQUIREMENTS..........................................................................................................................................6

2.1 DESCRIPTION............................................................................................................................................................................62.2 BUSINESS JUSTIFICATION..........................................................................................................................................................62.3 DATA FILTER RULES.................................................................................................................................................................62.4 OTHER BUSINESS RULES..........................................................................................................................................................62.5 PROCESS FLOW / DATA FLOW...................................................................................................................................................62.6 ASSUMPTIONS..........................................................................................................................................................................82.7 CONSTRAINTS...........................................................................................................................................................................82.8 OUT OF SCOPE.........................................................................................................................................................................8

3 INTERFACE DATA REQUIREMENTS.........................................................................................................................................................8

3.1 SOURCE INTERFACE DATA LAYOUT............................................................................................................................................83.2 TARGET INTERFACE DATA LAYOUT..........................................................................................................................................133.3 SOURCE / TARGET DATA MAPPING..........................................................................................................................................233.4 SPECIAL CASE: BI-DIRECTIONAL REAL-TIME INTERFACE...........................................................................................................233.5 SAMPLE DATA.........................................................................................................................................................................233.6 DATA RETENTION....................................................................................................................................................................23

4 SAP REQUIREMENTS.........................................................................................................................................................................23

4.1 INTERFACE TRIGGER IN SAP AND/OR MIDDLEWARE..................................................................................................................234.2 SAP TRANSACTION.................................................................................................................................................................234.3 SAP SCHEDULING / PERFORMANCE REQUIREMENTS / SERVICE LEVEL AGREEMENT...................................................................244.4 SAP SPECIAL REQUIREMENTS.................................................................................................................................................244.5 CUSTOM TABLES / STRUCTURE IN SAP....................................................................................................................................24

5 M/W SOLUTION (IF APPLICABLE).........................................................................................................................................................24

5.1 MIDDLEWARE SOLUTION..........................................................................................................................................................245.2 MAPPING RULES & CONVERSION CRITERIA...............................................................................................................................25

6 INTERFACE CONTROLS.......................................................................................................................................................................25

6.1 COMPLETENESS CONTROL......................................................................................................................................................256.2 ACCURACY CONTROL..............................................................................................................................................................256.3 DUPLICATE RECORDS CONTROL..............................................................................................................................................256.4 ERROR DETECTION AND COMMUNICATION CONTROL................................................................................................................256.5 INTEGRITY OF DATA TRANSFORMATION CONTROL.....................................................................................................................276.6 STANDARD FILE FORMAT CONTROL.........................................................................................................................................276.7 INTERFACE DATA SECURITY....................................................................................................................................................27

7 TESTING SCENARIOS..........................................................................................................................................................................27

4


Hyperion Upstream

1 Interface Tracking

1.1 Interface Classification

Interface Number

I-009

Interface Name

Interface and Mapping SAP ECC to Hyperion Upstream

Direction(with respectto SAP R/3)

Inbound Interface data flows inbound to SAP R/3X Outbound Interface data flows outbound from SAP R/3

Other Specify:

InterfaceType

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.Real-Time Immediate transfer of small data set; Usually triggered by event.Excel Upload Manually invoked from SAP session; Local spreadsheet file uploaded from PC.

X Other Specify: Extract from SAP ECC to Excel CSV File

InterfaceFrequency

Hourly Details:Daily Details:Weekly Details:

X Monthly Details: Monthly extractQuarterly Details:Yearly Details:

X On-Demand How often: At month end and then on demandOther Specify:

Type ofRecords

Sent

X Full record load Send all records every time interface is executedDelta full records Only send records where one or more fields have changed since previous executionDelta records Only send fields (and keys) that changed since previous interface execution

X Other Specify: First time the interface is run, all records will be sent. On demand execution, all records will be sent

Volume(per singleexecution)

Average Volume: TBDPeak Volume:

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

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 ofConstraint

Constraint Reported By

Constraint Type(Data or Business)

Comment

2.8 Out of Scope Not Applicable

Description ofOut-of-Scope Item

ItemReported By

Type(Data or Business)

Comments

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 Number

CHAR 10

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 DelimitedX 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.

Company Code

GL AccountProfit

CenterShip-to Region

Cost Center

Item Text

Opening Balance

Total Debits Total Credits

Year to Date

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.

The program will write to the table ZTFI_HYP_EXTRACT Hyperion Extract Details table the summary 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.

Company Code

GL AccountProfit


Cost Center

Item Text

Opening Balance


Year to Date

Ending 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.

The program will write to the table ZTFI_HYP_EXTRACT Hyperion Extract Details table the summary 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.

Company Code

GL AccountProfit


Cost Center

Item Text

Opening Balance


Year to Date

Ending 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, EMEA & APAC)

CHAR 8

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 currency (Opening balance for month)

CURR 23

15


Hyperion Upstream


ZTFI_HYP_EXT_SUM TOT_DEBITS Balance carried forward in local currency (Total debits)

CURR 23

ZTFI_HYP_EXT_SUM TOT_CREDITS Balance carried forward in local currency (Total credits)

CURR 23

ZTFI_HYP_EXT_SUM YR_TO_DT_BAL Balance carried forward in local currency (Year-to-Date balance)

CURR 23

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:

[email protected]@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

mailto:[email protected]

mailto:[email protected]


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

PeriodCompany Code

GL Account

Profit Center

Ship-to Region

Cost Center

Item Text

Opening Balance

Total Debits

Total Credits

Year to Date

Ending Balanc

e

Currency

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

Table Field Element DescriptionData Type

Length

Z ZTFI_HYP_EXTRACT

MANDT Client CLNT 3 X

Z ZTFI_HYP_EXTRACT

KTOPL Chart of Accounts CHAR 4

Z ZTFI_HYP_EXTRACT

GJAHR Fiscal Year NUMC 4

Z ZTFI_HYP_EXTRACT

MONAT Fiscal Period NUMC 2

Z ZTFI_HYP_EXTRACT

BUKRS Company Code CHAR 4

Z ZTFI_HYP_EXTRACT

HKONT General Ledger Account CHAR 10

Z ZTFI_HYP_EXTRACT

PRCTR Profit Center CHAR 10

Z ZTFI_HYP_EXTRACT

SUPREG Super region per country (Americas, EMEA & APAC)

CHAR 8

Z ZTFI_HYP_EXTRACT

SHKZG Debit/Credit Indicator CHAR 1

Z ZTFI_HYP_EXTRACT

ZCOUNT Line Count for Data Uniqueness

INT4 10

19


Hyperion Upstream


Length

Z ZTFI_HYP_EXTRACT

WAERS Currency Key CUKY 5

Z ZTFI_HYP_EXTRACT

SGTXT Item Text CHAR 50

Z ZTFI_HYP_EXTRACT

HSLVT00 Balance carried forward in local currency

CURR 23

Z ZTFI_HYP_EXTRACT

HSLVT01 Balance carried forward in local currency (Period 1)

CURR 23

Z ZTFI_HYP_EXTRACT


CURR 23

Z ZTFI_HYP_EXTRACT


CURR 23

Z ZTFI_HYP_EXTRACT


CURR 23

Z ZTFI_HYP_EXTRACT


CURR 23

Z ZTFI_HYP_EXTRACT


CURR 23

Z ZTFI_HYP_EXTRACT


CURR 23

Z ZTFI_HYP_EXTRACT


CURR 23

Z ZTFI_HYP_EXTRACT


CURR 23

Z ZTFI_HYP_EXTRACT


CURR 23

Z ZTFI_HYP_EXTRACT


CURR 23

Z ZTFI_HYP_EXTRACT


CURR 23

Z ZTFI_HYP_EXTRACT

HSL01 Total of transactions of the period in local currency (Period 1)

CURR 23

Z ZTFI_HYP_EXTRACT


CURR 23

Z ZTFI_HYP_EXTRACT


CURR 23

Z ZTFI_HYP_EXTRACT


CURR 23

20


Hyperion Upstream


Length

Z ZTFI_HYP_EXTRACT


CURR 23

Z ZTFI_HYP_EXTRACT


CURR 23

Z ZTFI_HYP_EXTRACT


CURR 23

Z ZTFI_HYP_EXTRACT


CURR 23

Z ZTFI_HYP_EXTRACT


CURR 23

Z ZTFI_HYP_EXTRACT


CURR 23

Z ZTFI_HYP_EXTRACT


CURR 23

Z ZTFI_HYP_EXTRACT


CURR 23

Z ZTFI_HYP_EXTRACT


CURR 23

Z ZTFI_HYP_EXTRACT


CURR 23

Z ZTFI_HYP_EXTRACT


CURR 23

Z ZTFI_HYP_EXTRACT


CURR 23

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

SourceElement

TransformationTarget

ElementComments

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 interface7 days15 days (default)30 daysOther 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 decideCustom SAP Transaction (Existing) Name:Standard SAP Transaction Name:None

4.3 SAP Scheduling / Performance Requirements / Service Level Agreement

N/A

22


Hyperion Upstream

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 NameShort textSize categoryTable maintenance allowedData classBufferingTable maintenance generationAuthorization GroupField Name

Data Element Domain Type Length Check Table-Field

Key Field

Foreign Key

Description

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 share folder

Delivery of .csv file for upload by user into Upstream.

Extract program fails to deliver file is to share folder

If any records fail in during the extract, the log file will indicate the type of error and send a notification to the user with a link to the file log.

6.2 Accuracy Control



An Online Audit Report of the data will be generated with each 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 SAP system and produces new extract file

New load file is produced for any updates in a period.


An Online Audit Report of the data will be generated with each 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: [email protected] and [email protected]

Other Specify:

24


Hyperion Upstream

Urgency:X Immediate

Next Business DayBefore 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 descriptionOther Specify:

Urgency:ImmediateNext Business DayBefore Specific Event Specify:

Impact to business in the event of this error:

6.4.3 Fatal Execution Error Notification

Email Notification Send To: <E-Mail ID>Write to Error Log Elements:Other Specify:

Urgency:ImmediateNext Business DayBefore Specific Event Specify:

Impact to business in the event of this error: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 apendBack Out Progress All records from this interface execution are removed from target system even if they were successfulOther 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 role interface path access have the ability to access the data for this interface.”>

<e.g. “All data sent between sending and receiving systems are saved to a secure subdirectory that no individuals have access to. This follows IHS IT Compliance Policies.”>

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 Description1 Execute custom transaction code 2 Select execute button to extract file3 Confirm email validation4 Retrieve .csv file from share folder5 Upload Hyperion extract file into Upstream.6 Validate balances between online audit report and HyperionException - special logic or exceptions (e.g. report should exclude certain specific condition)

56Error 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 Finance9 Error: Unable to update table10 Send email to IT and Finance11 Error: Unable to write to file12 Send email to IT and Finance

27

I-009 Interface and Mapping SAP ECC to Hyperion Upstream 2011_0228 1600

Documents

interface data requirements

interface trigger

na interface

interface classification

source interface data

target interface data

mapping sap ecc

sap requirements