Custom Stored Procedure

We'll need to add a new custom stored procedure to pull gl accounts. This procedure should pass ERP GL accounts as they are saved in ERP. We're going to stage them in their entirety, and in the stage log all of the ids to show what accounts got consolidated into.  

Configuration

Settings → User Profiles

For each user that can review these batches, we'll need to grant them security access.

Settings → Product Configurations → Aeros Connect

In the system configurations, we'll need to specify what validator we will use to export records under, and what custom stored procedure we will use from ERP to stage values with.

We'll set the connection target to "17", and the custom procedure name to match the procedure we added in the beginning. We must not include the schema "cust." in the configuration- that will be automatically appended to the procedure whenever we reference this in code. 

Managing Accounts in ERP

Master → GL → GL Account

In ERP, there is a master records form that will allow us to manage our GL accounts. These accounts are not normalized- they are listed out in a five segment sequence and each account has a record in the database.

We'll add and edit accounts in this form, to trigger their being staged to send to VROOZI. 

Staging ERP Accounts

Sync Data → General Ledger → New Batch

When we want to import records from ERP, we'll create a new batch. When we do, we'll see some stats about the last batch we created. By default, the date of that last batch will be the start date to look for records for this batch. It can be overridden, if we suspect there are some records that may have not made it into an earlier batch, that we want to try to include.

When we are ready to proceed, we'll click "Import / Create batch".

Any accounts that we have created or updated since the last import batch date will be included in the batch. We use the record's ERP "RowModifyDate" to determine which to batch.

All rows on the grid are read-only, except for "Include in Batch". Should we only want to send over a select group of records, we can uncheck the ones that we don't.

• Save: Saves any changes made to the batch. Users can update the batch code and the include in batch fields.

• Close: Closes the form.

• Delete Batch: Deletes an uncommitted batch.

• Reload Batch: Reloads the batch from its last saved state. Any changes made since then are undone.

• Commit Batch: Commits the batch to Manager Plus.

• Test Commit: Runs the commit validation without performing the commit.

When we commit, the records will be passed to VROOZI, and marked and time stamped as sent. When this happens, all valid rows will be grayed out in the view.

If a row fails to send, we can see any error messages in the "Commit Results" tab.

Committing Batches

When we commit accounts, we validate that all segments are populated. If they are not, they will not be committed to VROOZI. Instead, they will return messages on the "Commit Results" tab after a commit.

When we commit the records, we'll see that the "Merge Type" field was updated. This will give us an indicator that the record was newly inserted into Manager Plus, or updated because it had already existed.

Committed records will be greyed out, while uncommitted records will not be. We can review any error messages for these records on the "Commit Messages" tab.

ERP General Ledger accounts are not normalized, but are made so when they are sent to VROOZI. When they are sent, we can see a what values were passed and what unique ID they were assigned to in VROOZI. We can use these to group accounts to make sure that CONNECT is consolidating them correctly, or deal with any exceptions that we think are caused by a GL that is incorrect and therefore is consolidated into the wrong group.

Validating Imports

Master Data → Organization → Company Codes

Company Codes are a combination of sequences 1 and 2 from the ERP GL Master.

Master Data → Organization → Plants

Plant codes are analogous to Company codes. We create maintain one for every company code that we create. 

Master Data → Accounting → Cost Centers

Cost Centers are based on segment 3 from the GL Master. We assign the Company code to it based on what companies and Divisions we find them under in ERP. We may see the same cost centers in VROOZI, but never for the same company. 

Master Data → Accounting → GL Accounts

ERP Segments 4 and 5 become the accounts. Like Cost Center, we will create one for every company/division we can find one under.

Their External ID consists of the company code and account code. 

Scheduling the Batches

Settings → Scheduled Tasks

We'll add records to the schedule list if we want to schedule these batches

• DataSyncGeneralLedgerPull: Add and schedule a record for this job type to automatically create batches of accounts pulled from ERP.

• DataSyncGeneralLedgerPush: Add and schedule a record for this job type to automatically send created batches of accounts to VROOZI as suppliers.

Accounting Strings

With the existing feature to sync ERP GLs to Vroozi, Vroozi was having some issues with GL selection. There would be duplicates in the dropdown selection.

Vroozi added the accounting string feature to resolve their issue above.

We added support for accounting strings. This addition piggy-back on the existing data sync for GLs. Besides sending over the GLs, we are also sending over accounting strings.

In the screenshot on the right, this is where the accounting strings are located.

NOTE: CONNECT won’t be able to update the accounting strings in Vroozi if the accounting string was not initially created by CONNECT. This is mentioned in the ticket AAI-1773.