F350: ARM REPORTS · of row sets / column sets / unit sets Analytical Report Manager Financial...

Post on 16-Mar-2020

23 views 0 download

Transcript of F350: ARM REPORTS · of row sets / column sets / unit sets Analytical Report Manager Financial...

F350: ARM REPORTSInstructor: Maja Talevska Milenkovska

October 2018

CLASS SYLLABUS

2

▪ Day 1, Monday, October 8, 2018, 09 AM- 11 AM PDT: Let’s get to know Analytical Reports – ARM Overview

▪ Day 2, Tuesday, October 9, 2018, 09 AM -11 AM PDT:

Let’s put theory in practice – ARM Examples

ADVANCED PREPARATIONS

3

▪ Acumatica ERP 2017 R2, version 17.213.0031

▪ I100 demo data preinstalled

▪ Downloaded training guide and files for training

SESSION RULES

4

▪ All Attendees will be in Mute mode

▪ If you have a question, write your message in a chat and click Raise

Hand

▪ Polling questions will be asked at random moments without advance

notice

▪ Acumatica certification should be done through Acumatica

University

DAY 1ANALYTICAL REPORTS OVERVIEW

GOALS FOR THE DAY

6

▪ Get to know the Analytical Reports Manager Toolkit

▪ Analytical Reports elements

▪ Tips and Tricks

OBJECTIVES

7

In this lesson you will learn how to...

▪ Work with the ARM Toolkit

▪ Create a Row Set

▪ Create a Column Set

▪ Create Report Definition

WHAT IS ARM

8

The Analytical Report

Manager is a web-

based report access

and management tool

for

creating and modifying

analytical reports.

▪ Reporting tool consisting

of row sets / column sets

/ unit sets

▪ Analytical Report

Manager

▪ Financial Reports:

Ledger history tables

▪ Project Reports: Project

history tables

ARM: KEY DATA

9

GL History Table

▪ Ledger ID

▪ Branch ID

▪ Account ID

▪ Sub ID

▪ FinPeriod ID

PM History Table

▪ Project ID

▪ Project Task ID

▪ Cost Code ID

▪ Account Group ID

▪ Inventory ID

▪ Period ID

ARM REPORT LAYOUT

10

Unit Set

Row Headers

Report Header (column set)

Column Headers

REPORT DEFINITION

11

ROW SET

12

COLUMN SET

13

DATA SOURCES

14

REMEMBER

15

▪ Save regularly

▪ Use report description that matches title

▪ Save parameters as a template

▪ Use upper-case references to codes of row/units in formulas (@ROWCODE1)

▪ Use caution when deleting columns in column sets

▪ Always use Upper Case references for rows and units in formulas

▪ Do Not use @ symbol for row codes

▪ Use numbers for Row Codes and leave a set of numbers in between to insert rows at a later

time. E.g. 0010, then 0020

DAY 2GET TO LOVE ARM

GOALS FOR THE DAY

17

▪ Continue working on the ARM report from previous day

▪ Use some more advanced features

▪ Review examples of Support cases

▪ Print columns based on Period parameter

▪ Calculate percent of section Totals

▪ Create a table in ARM

OBJECTIVES

18

In this lesson you will learn how to...

▪ Filter reports using Unit Sets

▪ Use overlapping Data Sources

▪ Use the MergeNext function

▪ Create formulas for columns visibility

▪ Use Masks in Data Sources

UNIT SET

19

FILTERING DATA USING UNIT SETS

20

Setting values versus

Data Source

▪ Values (@U1+@U2) layeredroll-ups, but no hyperlink drill down

▪ Data Source filters data and allows drill down

Printing Groups

▪ Add to column set to hide

▪ Match in unit set to show

OVERLAPPING DATA SOURCES

21

Overlapping / merged data▪ Accounts, Subaccounts, branches

▪ Row set gets 100 – 600

▪ Column set gets 400 – 900

▪ Result: 400 – 600

Non-overlapping data▪ Ledger, Account Class, Financial Periods, Offers,

Amount are used from a single data source▪ Unit Set (if available)

▪ Row Set (if available)

▪ Column Set (if available)

▪ Report definition

ACCOUNT RANGES

22

Start Account, Start Sub and Start

Branch allows you to specify an

account list, account range, or both▪ Syntax is similar to Microsoft Excel

ranges: 400000:420000

▪ You can combine multiple ranges or accounts, separate them with coma:

400000:420000,425000,426000:426099

▪ Wildcards are supported in ranges:

4260??

HANDLING OF NAN/INFINITY VALUES

23

Scenario: Variance in Comparative Balance Sheet

Detects and

eliminates divide

by zero errors

REMEMBER

24

▪ When modifying report, create a copy of the report

▪ Use account classes instead of complicated masks

▪ Masks can be used only for non-segmented accounts and subaccounts

▪ Cannot use Account Types in ARM reports

▪ Overlapping Data Sources:

▪ Accounts, subaccounts, branches are merged

▪ Account classes, ledgers, financial periods are used from only one data source

HTTPS://WWW.SURVEYMONKEY.COM/R/ONLINESESSIONS2018

THANK YOU!