Report Properties

Summary/General Information

The following is a summary of general information about the report.
Report general information:
Report file name https://cs4.xbrlcloud.com/user/charleshoffman@olywa.net/share/private/Master/BusinessUseCases/2013-05-15/BUC36-Flow/Flow-SampleInstance.xml
Report identifier (target namespace) http://www.xbrlsite.com/DigitalFinancialReporting/BusinessUseCase/Flow
Prefix pattern
Taxonomy version:
Taxonomy version http://www.xbrlsite.com/Schemas/frm, http://www.xbrlsite.com/Schemas/brm

Automated Verification Summary

The goal is to create a verifiably correct true and fair representation of a reporting entity's financial information. The report should be complete, correct, consistent, accurate. The report should have fidelity and integrity.
List List List List
Status Count of Relations XBRL Technical Syntax Rules Model Structure Rules Business Rules Roll Up Rules (a)
Summary of all components (networks/tables) Completed 38 OK OK OK UNKNOWN
 
Automated rules defined 205 7 3 0
Automated rules executed which PASSED 205 7 7 0
Automated rules executed which FAILED 0 0 0 0

Manual Verification Summary

List List List
Status Count of Relations Roll Up Tasks (a) Other Manual Review Tasks Other Rules and Best Practice Tasks
Summary of all components (networks/tables) Completed 38 UNKNOWN UNKNOWN OK
Manual rules defined 0 0 31
Manual rules executed which PASSED 0 0 31
Manual rules executed which FAILED 0 0 0
(a) Roll ups are expressed using the XBRL calculations technical syntax. Roll ups which pass are listed in automated testing results as "OK". Roll ups which fail are listed in the manual verification rules as requiring manual verification. This is because XBRL calculations verification can properly detect roll ups which pass, but due to a known limitation of XBRL calculation validation, such validation cannot be certain that a roll up which is not deemed to work correctly is a failure. As such, to avoid false interpretation of non-passing XBRL calculation results as failures; they are deemed to be "inconsistencies" by the XBRL specification. Therefore, calculation inconsistencies must be manually examined to verify whether a non-passing calculation is a true error or a validation test which is not applicable to facts within a particular network.

Report Objects Summary

The report objects of an SEC XBRL financial report can be grouped into categories. The different report objects have different properties. Categorizing these report objects and using those groupings can help in the verification process. Relations between report objects can be better understood when leveraging these categories.
Components 3
Networks 3
Tables 3
Axes 5
Members 11
Line Items 3
Abstracts 3
Concepts 1
Facts 27
Parenthetical explanations 0
Structural relations 38
Business rules 3

Component Summary

A component is a combination of a network and a table. All facts exist within one or more networks. All facts also exist within one or more tables, be that table an explicitly defined [Table] or an implied table.
# Title URI Table (Explicit or Implied)
1 1001 - Table - Sales Analysis, Summary http://www.xbrlsite.com/DigitalFinancialReporting/BusinessUseCase/Flow/SalesAnalysisSummary Sales Analysis, Summary [Table]
2 2001 - Table - Sales Analysis, by Geographic Area http://www.xbrlsite.com/DigitalFinancialReporting/BusinessUseCase/Flow/SalesAnalysisByGeographicArea Sales Analysis, by Geographic Area [Table]
3 3001 - Table - Sales Analysis, by Business Segment http://www.xbrlsite.com/DigitalFinancialReporting/BusinessUseCase/Flow/SalesAnalysisByBusinessSegment Sales Analysis, by Business Segment [Table]