Data Import/Period Approval - Revision history

Scarpenter at 02:06, 16 October 2017

2017-10-16T02:06:23Z

Scarpenter: /* Period Approval Import Data Definition */

2016-03-22T00:20:52Z

‎Period Approval Import Data Definition

Scarpenter: /* Period Approval Import Data Definition */

2016-03-21T22:05:19Z

‎Period Approval Import Data Definition

Scarpenter at 22:04, 21 March 2016

2016-03-21T22:04:40Z

Scarpenter: /* Importing your Data */

2016-03-21T06:05:35Z

‎Importing your Data

Scarpenter: Scarpenter moved page Data Import/Bulk Period Approval to Data Import/Period Approval without leaving a redirect: to match wiki icon code

2016-03-21T06:00:19Z

Scarpenter moved page Data Import/Bulk Period Approval to Data Import/Period Approval without leaving a redirect: to match wiki icon code

Scarpenter: Created page with "== Bulk Period Approval == This feature provides an easy and fast way to approve periods in bulk. The system utilises the '''Bulk upload processing notification''' event to..."

2016-03-21T05:59:48Z

Created page with "== Bulk Period Approval == This feature provides an easy and fast way to approve periods in bulk. The system utilises the '''Bulk upload processing notification''' event to..."

New page

== Bulk Period Approval ==

This feature provides an easy and fast way to approve periods in bulk.

The system utilises the '''Bulk upload processing notification''' event to send a notification with the results of the bulk approval attempt. You must set up this event and enable it before you use this tool.

If the bulk approval is successful, the email notification will advise you when the process is complete.
If the bulk approval is not successful, the email notification will send details of the records that failed to be approved and why.

== Access Control ==
Access to this tool is granted by enabling the '''Period approval''' power.

== Preparing your Data ==

To approve periods in bulk you will need to create a CSV data file or you can download the data file below to use as a template. You will need to extract the csv file and save it.

[[media:sample-period-approval.csv | Period Approval Import CSV template]]

Enter the data into the import sheet. Leave no rows blank. You must ensure the data meets all validation requirements. These are contained in the data definition table below. When you submit the data file for import, the system will parse the file looking for errors. If the system finds no errors, the system will import the notes into the system. The file needs to be error-free in order to import the data. In the event errors are found, no data will be imported into Emersion. Review the bulk upload processing notification email, correct the file and try again.

== Importing your Data ==

To access the bulk invoice approval tool:

# Log into Cumulus.
# '''Nav: Admin > Bulk Import > Cardline'''.
# Click the '''Browse''' button and select the csv file containing the list of card lines you want to import.
# If you want the bulk upload processing notification email to be sent to a different email address than the address defined in the event template, tick the '''Override?''' check box and enter an alternative email address. This will only apply for this upload. To change the email address for all future imports, you will need to change the recipient defined in the event template.
# Press '''Submit'''

The system will validate the data and if no errors are found, the system will approve the invoices. When the notification email is received, the process has been completed.

<strong>'''It is strongly recommended that you check a few random records to ensure that bulk approval process was a success. If you find an problem, you cannot roll back the bulk approval.'''</strong>

You have two options should this occur:

# Manually correct the data.
# Request Emersion fix the errors for you. This can be submitted via [[Support_and_help_from_Emersion#Work_Orders | work order ticket]]. Please include a new csv data file with the records that need to be corrected. Do not include any records that do not need correcting.

== Card line Import Data Definition ==
This section contains a list of the required fields and a definition of what the system considers as valid data.

{| class="wikitable"
|+Card line Import Data Definition table
|Data field || Description
|-
| TRANSACTION_DATE || This field is mandatory. The format = YYYY-MM-DD.
|-
| TAX_AMOUNT || This field is mandatory. This field represents the EX TAX portion of your charge and must be rounded to two decimal places.
|-
| DESCRIPTION || This field is mandatory and has a 255 character limit. This is the description for the charge that will appear on the customers invoice or service information record (SIR).
|-
| LEDGER_CODE || This field is mandatory and is the a ledger code name from the Emersion system for the card line. You can obtain a list of available ledger codes at the following location: < /br>
Nav: '''Reports > List > Reference > Ledger Codes (and Mapping) report'''. Ensure you use the ledger code NAME, not the MAPPING_NAME or SIMPLE_CODE.
|-
| ACCOUNT_ID || This is a mandatory field. and is the account you wish to have the card line assigned against.
|-
| SERVICE_ID || This field is optional. It is service ID you want this charge to be assigned against.
|-
| BILLING_TYPE_ID || Defines if the charge is an advance charge or an arrears charge (2). Valid entries are:
1 = advance, 2 = in arrears < /br>
It is not mandatory. The default setting is 1 (advance).
|-
| COVERS_FROM || A mandatory start date for the period of which the card line covers. Format = YYYY-MM-DD.
|-
| COVERS_TO || The end date for the period that the card line covers. Format = YYYY-MM-DD.
The field is not mandatory but if a date is not supplied, the system will use the COVERS_FROM date.
|-
|}

Your finished data file should look like the following example.

{| class="wikitable"
|+Card line Import Data File Example
| ACTUAL_VALUE || 10 || 1 || "Test Transaction, Blah" || LEDGER_CODE || 111377 || 171519 || 1 || 2010-12-30 || 2010-12-30
|-
| 2010-02-01 || 33 || 3 || "Blah Transaction, Blah" || || 111377 || || 1 || 2010-12-30 || 2010-12-30
|-
| 2010-12-30 || 22 || 2.2 || Test Transaction || MY_TRANSACTION || 111683 || 173038 || 2 || 2010-12-30 || 2010-12-30
|-
|}

= See Also =

* [[Events|Events]]

@@ Line 1: / Line 1: @@
-== Bulk Period Approval ==
+{{DISPLAYTITLE:Bulk Period Approval}}
-This feature provides an easy and fast way to approve periods in bulk.
+This article has been moved to our new home for documentation and help content, the new Emersion Knowledge Base.
-The system utilises the '''Bulk upload processing notification''' event to send a notification with the results of the bulk approval attempt. You must set up this event and enable it before you use this tool.
+We are sorry for the untidiness while we are shifting locations and we appreciate your patience during the transition to out new home.
-If the bulk approval is successful, the email notification will advise you when the process is complete.
+[https://resources.emersion.com/display/EKB/Period+Approval Take me to the Emersion Knowledge Base article]
-== Access Control ==
+[[file:new_home_sm.jpg|900px]]

@@ Line 39: / Line 39: @@
 == Period Approval Import Data Definition ==
 This section contains a list of the required fields and a definition of what the system considers as valid data.
 {| class="wikitable"
-|+Period Approval Import Definition table
+|+Bulk Period Approval Data Definition table
 |Data field || Description
 |-
-| TRANSACTION_DATE ||  This field is mandatory. The format = YYYY-MM-DD.
+| PERIOD_ID ||  This field is mandatory. The format = YYYY-MM-DD.
 |-
-| TAX_AMOUNT || This field is mandatory. This field represents the EX TAX portion of your charge and must be rounded to two decimal places.
+| SERVICE_SUBSCRIPTION_ID || This field is mandatory. This field represents the EX TAX portion of your charge and must be rounded to two decimal places.
 |-
 |}

@@ Line 9: / Line 9: @@
 == Access Control ==
-Access to this tool is granted by enabling the '''Period approval''' power.
+Access to this tool is granted to users of your service provider account by enabling the '''Period approval''' power.
 == Preparing your Data ==
@@ Line 38: / Line 38: @@
 # Request Emersion fix the errors for you. This can be submitted via [[Support_and_help_from_Emersion#Work_Orders | work order ticket]]. Please include a new csv data file with the records that need to be corrected. Do not include any records that do not need correcting.
-== Card line Import Data Definition ==
+== Period Approval Import Data Definition ==
 This section contains a list of the required fields and a definition of what the system considers as valid data.
 {| class="wikitable"
-|+Card line Import Data Definition table
+|+Period Approval Import Definition table
 |Data field || Description
 |-
@@ Line 66: / Line 66: @@
 | COVERS_TO || The end date for the period that the card line covers. Format = YYYY-MM-DD.
 The field is not mandatory but if a date is not supplied, the system will use the COVERS_FROM date.
 |-
 |}

@@ Line 24: / Line 24: @@
 # Log into Cumulus.
-# '''Nav: Admin > Bulk Import > Cardline'''.
+# '''Nav: Admin > Bulk Import > Period Approval Import'''.
 # Click the '''Browse''' button and select the csv file containing the list of card lines you want to import.
 # If you want the bulk upload processing notification email to be sent to a different email address than the address defined in the event template, tick the '''Override?''' check box and enter an alternative email address. This will only apply for this upload. To change the email address for all future imports, you will need to change the recipient defined in the event template.

← Older revision	Revision as of 06:00, 21 March 2016
(No difference)