Reporting Stores

Reporting Stores

Purpose and when to use this record

BriskConfigure storesa participating store’s reporting storesendpoint, timezone, currency, transport safeguards, and synchronization health.

At a glance

• Identify it by: Name.

• Why care: Consolidated results are only as partreliable as store connectivity, account mapping, currency/timezone setup, and the status of the consolidationlatest module.run.

  This
generated
• reference

  Why care: Availability and publication flags affect future use without erasing history. Prefer disabling an obsolete setup record when existing transactions still refer to it.

Before you begin

You need the Brisk permission for the action you are taking on reporting stores. If a Create, Edit, or Delete control is awaitingabsent, workflowdo review.not work around it with another user’s account; ask an administrator to review your role.

Create a recordReporting Store

TheCreate evidencea packetReporting identifiesStore after searching for the viewperson, organization, item, location, or resource under alternate names and sourceidentifiers. locationMerge or correct an existing master record instead of creating a duplicate.

1. Select the business context first.

2. Enter the required identifying and operational values: Name, and Base Url.

3. Review Active, and Verify Ssl deliberately; these choices control availability or workflow rather than merely describing the record.

4. Save the Reporting Store, then confirm Name on its detail page before continuing.

After saving: Verify this Reporting Store in Adjustment Lines, Adjustment Snapshot Lines, General Ledger Snapshot Lines, and General Ledger Snapshot States, plus the remaining screen fields before staff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Delete a Reporting Store

Delete this Reporting Store only if it is an unused duplicate or setup mistake. Once other records refer to it, preserve that history and make the value inactive when the screen provides that option.

If the record is merely obsolete, use Active to remove it from future use while preserving existing references.

Before confirming, check for thisrelated action.Adjustment ConfirmLines, user-facingAdjustment stepsSnapshot beforeLines, approvingGeneral Ledger Snapshot Lines, General Ledger Snapshot States, and Reporting Store Accounts, plus the remaining screen fields. Brisk may refuse deletion when another record depends on this page.one; resolve the duplicate or use the supported correction workflow instead of breaking the trail.

On the confirmation page, verify Name. After confirmation, return to the Reporting Stores list and make sure only the intended Reporting Store was removed.

ViewReview recordReporting Store details

The evidence packet identifiesUse the viewdetail page as the shared record of what this Reporting Store currently means. Verify Active before relying on it for a decision.

Compare the Reporting Store with its source document or approved setup request before deciding that it needs correction.

Next check: Verify this Reporting Store in Adjustment Lines, Adjustment Snapshot Lines, General Ledger Snapshot Lines, and sourceGeneral locationLedger Snapshot States, plus the remaining screen fields before staff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Edit an existing Reporting Store

Edit this Reporting Store to keep the same real-world party, item, location, or resource accurate. Do not repurpose it for a different entity after activity is attached.

1. Open the detail page. Compare Name with the supporting document or approved request.

2. Recheck Active. These values are most likely to change store mapping and consolidated statement results.

3. Save the change, return to the list, and confirm that the Reporting Store now appears under the expected Active.

After the change: Verify this action.Reporting ConfirmStore user-facingin stepsAdjustment Lines, Adjustment Snapshot Lines, General Ledger Snapshot Lines, and General Ledger Snapshot States, plus the remaining screen fields before approvingstaff thisbuild page.new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Find and review recordsreporting stores

The evidence packet identifiesUse the viewReporting Stores list to find the correct record before opening or changing it. Compare Name. Compare the full identifier rather than relying on a similar name.

• Keyword search checks Name, External Id, Base Url, Timezone, Currency, and sourceLast locationError.

• The initial order emphasizes Name. Select a column heading when you need a different comparison.

Open the Reporting Store whose Name match the task. If it is missing, clear the list filters and recheck Active rather than creating a replacement immediately.

Fields and business rules

Brisk stores 11 user-relevant fields for this action.Reporting ConfirmStore, user-facingincluding steps0 beforelinked-record approvingselections and 0 controlled-choice fields. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.

Editanexistingrecord

The

evidencetheviewandsourcelocation user-facingstepsbeforethispage.

user-facingsteps

Field	Required	What packetit identifiescontrols
Name	Yes	Human-readable name for this action.reporting Confirmstore.
External approvingId	No	URL-safe Delete a record The evidence packet identifies the view and source locationidentifier for this action.reporting Confirmstore.
Base Url	Yes	URL recorded as base url for this reporting store.
Timezone	No	The timezone recorded for this reporting store.
Currency	No	The currency recorded for this reporting store.
Active	No	Whether this reporting store is active and available for use.
Verify Ssl	No	Whether the verify ssl option applies to this reporting store.
Timeout (Seconds)	No	The timeout (seconds) value recorded for this reporting store.
Last Successful Sync At	No	Date and time recorded for last successful sync at on this reporting store.
Last Ping At	No	Date and time recorded for last ping at on this reporting store.
Last Error	No	The last error recorded for this reporting store.

What happens next

Verify this Reporting Store in Adjustment Lines, Adjustment Snapshot Lines, General Ledger Snapshot Lines, and General Ledger Snapshot States, plus the remaining screen fields before approvingstaff build new activity on it; correct ownership, classification, and active state now rather than after transactions accumulate.

Common mistakes and troubleshooting

• The record will not save: Recheck Name, and Base Url and any message beside the field. A required related record may also be inactive or unavailable to your role.

• The record saved but is not available where expected: Recheck Active, then clear the filters on the destination list. A saved record can still be inactive, unpublished, locked, unapproved, or in the wrong workflow state.

• The values look right but the result is wrong: Compare this page.Reporting Store with the source document or approved setup decision, then check the downstream screen where it is used.