Other Reporting Configurations

The first step to setting up the Reporting application is to complete configuration tasks. Configuration tasks allow you to set parameters by which you will build your Reporting application upon to create your personalized Reporting experience.

Access the Configuration Task List page by navigating to Maintenance > Admin > Configuration Tasks.

1. Access and complete each task under General Financial Configuration.

   Define Financial Segments - Define the name and number of business segments for your Planful application. Segments are also referred to as dimensions and make up your Chart of Accounts. You must define at least two segments, but no more than eight apart from the system-defined segments (i.e. Time, Measure, Scenario). Out of the eight user-defined segments, one segment must represent a legal entity and the other segment must represent a natural account.

   Define Financial Budget Entity - Define business segments. Your budget hierarchy entity selections will be populated based on the segments selected here.

   Define Fiscal Year - Establish the start and end of your organization’s fiscal year, including the number of periods associated with the fiscal year. Define roll-up levels and quarter members. Roll-up levels allow for additional time frequencies in a calendar. The lowest level is month. You will not be able to edit the names of the levels unless the periods per fiscal year is great than 12.

   Define Budget Parameters - Define the number of years budgeted at one time and the number of compare scenarios accessible while entering a budget. Compare scenarios allow you to compare historical actuals, data from a prior period in the budget cycle, etc. This is used for the Planning module.

   Define Currency Parameters - Define common currency, conversion basis, and interim currency parameters

2. Now that you've defined the structure, you've got to decide how you will your load data to the Planful structure. Under Data Integration Configuration, configure the appropriate task based on your data load plan. There are several options to load data to Planful in addition to Web and Cloud Services.

   For information on all options available to load data to Planful, see Loading Data to Planful.

   Web Service Access - Define security access to import data from an external source into the Planful application through Web Services. Additionally use the Web Service Access page to notify users when data is loaded to Planful via Web Services.

   Descriptions of fields on this page are provided below.

   • API - Enable or disable Web Service Access.

   • Web Service URL - Default URLs needed to connect with the Planful application through a session-state or state-free authentication.

   • Available User(s) - A list of all users created via User Management or loaded via Data Load Rules.

   • Email User(s) - A list of all users who will receive emails whenever data is loaded into the Planful application through Web Services. Use the arrow buttons to add or remove email users.

   • More information on Web Services is provided in the Loading Your Data to Planful section.
   • 
     
   • 
     
   • 
     
   • 
     
   • 
     
   • 
     
   • 
     
   • 
     
   • 
     
   • 
     
   • 
     
   • 
     
   • 
     
   • 
     
   • 
     
   • 
     
   • 
     
   • 
     
   • 
     
   • 
     
   • 
     
   • 
     
   • 
     
   
   

   Cloud Services - Access the Cloud Services page to configure Box integration. Planful Cloud Scheduler - Data Load Rule functionality is fully integrated with Box. This means that you can place a file on Box and schedule a data load rule in Planful to load the file (and all contents) to the Planful application.

   You can load data to Planful from Google Drive. Additionally, you can use the NetSuite data connector to integrate Planful with NetSuite.

3. Define the Reporting Areas (Reporting Cube). Planful Reporting Cubes are multi-dimensional structures defined by a set of dimensions and measures used to analyze data for reporting purposes.

Configure the Workforce Reporting Area if you plan to report on Workforce data.

See the Workforce Reporting topic.

Configure this task to limit users to a maximum number of parallel sessions per user ID. Exceeding the maximum number will result in a message indicating that the user has exceeded the maximum number of sessions and return the user to the login page.

Planful allows a user ID to be logged in from multiple locations and multiple devices. Administrators have the option to restrict the number of parallel sessions a user is logged into in order to comply with security policies.

Access the Configuration Task List page by navigating to Maintenance >Admin >Configuration Tasks. Select Define Login Restrictions - Configure IP Restrictions.

This configuration is optional and is applicable to login requests from a web browser only. By default, no restrictions are configured.

1. Select the Enable IP Restrictions checkbox.

2. For Add IP address, enter the address or address range you want to restrict. Enter an IP address (IP4 format), range of IP addresses, or CIDR (Classless Inter-Domain Routing) in which you want to restrict access to your Planful application.
   Note:

   Classless Inter-Domain Routing is a method for allocating IP addresses and routing Internet Protocol packets.

3. Click the Add button to add the IP address, range of IP addresses, or CIDR to the Trusted IP addresses box. Users in this list logging in with a support IP address will be allowed to access Planful. If the IP address is not listed here, the user will be denied access. Select an IP address and click the Delete button to remove the address from the Trusted IP addresses box.

4. Select the Exempt All External User(s) checkbox so that external users are not required to meet IP address restrictions. For example, if you need a Planful Support employee to access your application, that person is considered an external user. For a list of external users, access the User Management page under Maintenance.

• Unmapped User/User Group– a list of all users and user groups. Select a user and click the forward arrow to provide that user or user group with exempted restriction.

• Mapped User/User Group - a list of all users and user groups that are exempt from the restriction. To remove a user, select the user and click the back arrow.

With Collaboration, (Socialcast's integration into Planful) you will be able to communicate and collaborate on a particular artifact (Scenarios, Reports). User communications are enabled at a granular level.

For detailed information on everything related to configuring, setting up and using Collaboration, click here.

Access the Security Administration page by navigating to Maintenance > Admin > Security Administration. Define application access security settings. For example, enable IP (Internet Protocol) Logging to create logs containing IP address information, which tracks users logging into the system.

Topics highlighted in gray are applicable for Reporting.

Tenant Group Security Settings - Application Access

Settings are inherited from the Tenant Application and can only be edited if you have security privileges.

• You can force users to change their password after x number of days.

• Define parameters around the password (like number of characters required).

• Select the number of failed login attempts before the user is locked out of the application.

• Deactivate user accounts if inactive for x number of days.

• Specify the number of previously used passwords that cannot be used when a user is resetting their password.

Tenant Security Settings - Application Access

Select the appropriate settings. The default settings are enable IP Logging and enable Employee Review %.

• Enable IP Logging – An IP (Internet Protocol) address in a unique set of numbers that represent the computer connected to the system. IP logs contain recordings of IP addresses representing members who have logged on to the system.

• Enable Snapshot in Data Input Templates - Allows users to take snapshots of the Input Template.

• Enable Email in Data Input Templates - Allows users to send emails with input template data attached.

• Enable Snapshots in Reports - Allows users to take snapshots of reports.

• Enable Email in Reports - Allows users to send emails with reporting information attached.

• Enforce changing the account properties when the data is available- Allows account properties to be edited even when data exists. For Segment Hierarchies, the system properties (i.e. Account Type, Currency Type, Credit/Debit, Normal Data Input Type, and Variance) are disabled for account members if data has already been loaded for these members and the configuration is turned off (for you, the customer). However, if the configuration is turned on, these properties are opened to edit (even when data exists for the members). It's important to reload Data Loads and rerun Consolidations to avoid data discrepancies.

• Enable Employee Review % at- Allows the configuration of Review % at the Employee/Employee Type level. If set at the Employee level, Review % may be overridden for each employee in the template.

• Enable Email on Budget Approval Workflow- Allows users to send emails during the budget approval workflow with budget information attached.

• Enable Access to Planful Support Usersuntil- Allows Planful Support Users to access your application to better help you facilitate necessary tasks or provide additional assistance. If you turn off (do not select this checkbox) Support Access, Planful Support Users will not have access to your application. If you disable this option during a Support User session, the Support User is allowed to continue the session, but may not log in again. Planful Support User information is not available for viewing by your users. The system keeps audit logs of all Support Users that log in to your application.

  • Click the calendar button to provide a date until which Support User access is valid. By default, this option is opened and the date is set to 10 years out. You may edit this date at any time.

• Enable cross sheet reference account update in offline planning workbook - Allows you to indicate whether or not you want the system to automatically populate the updated reference account line data in the dependent templates without connecting to the online template. For example, if you have two templates checked out for offline input with reference mapping (one template referencing data from another), you may automatically populate the reference account line data, or not, based on performance needs.

• Check cube process status after every _ minutes - Checks the status of the reporting cubes every number of minutes selected and updates the cube icon.