|
Sun Documentation -
General Ledger
|
|
Journals are used to record ledger and asset transactions. Journals can enter the system in the following ways: - manually entered online
- imported from an external system
- generated automatically by another SunSystems function
|
Manually Entering JournalsA journal can be entered manually into SunSystems. The main transaction entry form is Ledger Entry ( LE). It provides powerful and sophisticated features that enable you to enter journals quickly and easily. The type of journal you want to enter is determined by a user-definable journal type. The journal type is used to tailor the Ledger Entry form appearance and validation rules, to the particular journal's requirements. You can create any number of journal types to meet different needs. You can, for example, use one journal type for local currency receipts, and another for cash received in other currencies where additional currency details are required. Journal presets can be used to predefine some, or all, of the journal transaction details for a manually entered journal. This can speed up the journal input process, and ensure the correct information is entered on each journal transaction. |
|
Read more...
|
|
|
News -
SunSystems News
|
ATLANTA – August 2, 2006 – Infor, one of the largest global providers of enterprise software and a portfolio company of Golden Gate Capital, today announced it has accelerated its strategy of offering customers a choice of integrated enterprise software solutions and standalone best-in-class solutions, by closing three acquisitions which extend its global scale and broaden its offerings for new markets and new territories. In addition to closing the previously announced acquisition of SSA Global on July 28, 2006, Infor has acquired Extensity, a leading financial performance management software company, and Systems Union Group, a UK-based provider of financial and performance management solutions including budgeting, reporting, business intelligence and a comprehensive suite of financial applications.
Read more |
|
|
Sun Documentation -
System Administration
|
|
Overview FSD - Flat Schema Definition Language provides a mechanism for describing the structure of flat data in terms of records, fields and sequences of records. FSD language is based on now widely used XML - Extensible Markup Language standard. Using the FSD, it is possible to describe the structure of flat data in a very a simple and very flexible format understood by SunSystems Transfer Desk ( TD) to convert that data into XML and vice-a-versa. |
|
Read more...
|
|
|
Sun Documentation -
System Administration
|
|
In this example we will create a transformation profile to reverse journal using transformation designer and transfer profile designer. After that we will run transfer desk to reverse a range of journals. This transformation will reverse the sign indicator on journal transaction lines. |
|
Read more...
|
|
|
Sun Documentation -
System Implementation
|
|
In this article I would like to highlight the major system implementation steps required to successfully implemet SunSystems5: |
|
Read more...
|
|
|
Sun Documentation -
System Administration
|
|
Overview The rule engine is the validation routine which checks values entered by the operator based on a set of rules. Actions are then performed automatically depending on whether the rule criteria are fulfiled. For example, data values can be set or calculated automatically, or alternatively, error messages can be displayed so that the operator is forced to amend an incorrect data entry value.
SunSystems contains functions that validate data from manual input, such as from transaction entry functions. You can define business rules by using the functions: - Event Profiles
- Rule Sets
- Rule Messages
- Rule Data Sets
- Rule Data Presets
- Rule Data Set Keys
- Redefined Data Items.
|
In this example we are going to create an Event Profile that checks if a function is Ledger Entry. Then it fires up a rule set, which checks if an account enetered is 11000 and if so it will insert a PROJECT code (Ledger Analysis 3) "P001".
The first step in defining a validation business rule is to set up an event profile. |
|
Read more...
|
|
|
Sun Documentation -
General Ledger
|
|
What Budget Controls are Available? SunSystems budgeting allows you to hold budget values against accounts and analysis codes. These budget values can be used in two different ways in the system: - to control expenditure and warn if any transactions exceed the budget available
- to provide comparative values for actual/budget/forecast reports and inquiries.
|
You can apply the SunSystems Budget Checking facility to transactions as they enter the system. There are two types of budget checking available, depending on the SunSystems modules you are using: expenditure checking - commitment checking.
|
Expenditure CheckingOver expenditure checking monitors actual expenditure against budget, for accounts you select in SunSystems Financials. As you enter ledger transactions for accounts or they are posted using Ledger Import, it checks the total actual expenditure against the allocated budget and warns if a transaction takes an account over its budget. Using expenditure checking, the available budget is calculated as follows: | Budget - Actual expenditure |
A warning appears if the transaction amount exceeds this available budget amount. Commitment Checking
Commitment checking is only available if you are using the P urchasing module in SunSystems Order Fulfilment and SunSystems Financials. Committed expenditure is the total of any outstanding purchase orders raised for the account and represents the amount you are committed to spend for the account.
Over commitment checking is used to check purchase orders are they are entered into Order Fulfilment Purchasing, to prevent orders being raised that would exceed the budget available. It can also be used in Ledger Entry and Ledger Import to check ledger transactions, if the transactions are entered against budget accounts for which commitment checking has been requested. See Defining Budget Checks.
Using commitment checking, the available budget is calculated as follows: | Budget - Actual expenditure - Committed expenditure |
A warning appears if the transaction amount exceeds this available budget amount. |
|
Read more...
|
|
|
Sun Documentation -
General Ledger
|
|
Analysis Dimensions Setup Analysis dimensions are created using Analysis Dimension Setup (ND). An analysis dimension identifies a type of analysis you want to apply to one or more data entities. For example, you may want to analyze by Product, Location, Cost Centre and Employee.
You can define up to 100 analysis dimensions. Each analysis dimension is identified by its Short Heading i.e. product or cost centre, and a separate lookup code is also available.
Up to ten analysis dimensions can be used to analyze any of the analyzable static or transactional entities. A single analysis dimension can be used to analyze many different types of entity throughout the SunSystems modules.
When you define a new analysis dimension you can also determine some of the characteristics of analysis dimension codes. You can: set the maximum length of the analysis codes for the dimension. This is used to automatically adjust the length of the input field when the analysis code is requested, displayed or printed. An analysis code can include up to fifteen characters. identify the valid analysis codes by referring to an existing SunSystems data table (referred to as an analysis table). For example, if an analysis dimension represents Employees you would choose the Employee data table which is identified by Analysis Table Id 0132. See Linking Existing Codes to an Analysis Dimension for a list of these data tables. control whether or not the analysis codes for the dimension can be changed on ledger transactions using Account Allocation (AA). determine whether or not the analysis codes entered on transactions must be predefined, by choosing whether the codes are validated when they are entered.
|
|
|
Read more...
|
|
|
Sun Documentation -
System Administration
|
|
In this session we look at how Business Units are created and administered, using the following functions: - Business Unit Create
- Business Unit Setup
- Business Unit Copy
- Business Unit Delete
|
Business Unit CreateBusiness Unit Create (BUC) is used to create the database tables for a new business unit. You identify the code you want to use as the business unit. This is the three-character code that uniquely identifies the operating unit. You must use all three characters, and the first character must not be numeric. The SQL file group defaults to Primary and cannot be altered. The Business Unit Create function is only available to Super Users. Click here to see the screenshot |
|
Read more...
|
|
|
|
<< Start < Previous 1 2 3 4 5 Next > End >>
|
