What the Data for This Category Looks Like
Financial report data for listed baijiu companies mainly comes from periodic reports publicly disclosed by the Shanghai and Shenzhen Stock Exchanges, with fixed update schedules. Annual reports are disclosed by April 30 of the following year, semi-annual reports by August 31 each year, and quarterly reports within one month after the end of the quarter. A single document usually includes modules such as consolidated financial statements, discussion and analysis of operating conditions, and core product production and sales data. Fields cover reporting period, operating revenue, revenue by category, production capacity and output, taxes and fees, etc. Units are mostly RMB yuan and tons, and there are no unified non-standard additional fields.
Constraints Imposed on Model Access and Configuration
The fixed disclosure cycle of baijiu financial reports requires configuring trigger nodes for scheduled synchronization tasks that match the disclosure deadlines of each reporting period. Documents contain structured financial tables and unstructured operational analysis text, requiring model access to support both structured data parsing and long-text context processing. The existence of exclusive fields such as revenue by category and production and sales data requires precise matching of specific business fields when configuring field mapping rules, to avoid confusion between general financial fields and baijiu segmented category data. The relatively long length of single documents requires configuring reasonable segmentation and recall parameters to avoid analysis deviations caused by context truncation.
How to Set Configurations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
PARSE_FILE_TIMEOUT_SECONDS | 600 seconds | Baijiu financial report documents have a relatively long length, and the conventional parsing time may exceed the platform default value. 600 seconds can cover the complete parsing process |
maxContext | 8000–16000 characters | A single financial report contains multiple modules of content, and sufficient context must be retained to correlate financial and operating data across different sections |
RECALL_TOP_N | Top 8–12 entries | Core data of baijiu financial reports is distributed across multiple paragraphs, and a sufficient number of relevant fragments must be recalled to support comprehensive analysis |
FUNCTION_CALL_ENABLE | Enabled | Tools need to be called to complete operations such as multi-period financial report comparison and field extraction, to adapt to the process-oriented requirements of financial report analysis |
UPLOAD_FILE_MAX_SIZE | 500 MB | Annual financial report PDF or Excel files of leading baijiu enterprises usually do not exceed this size, to avoid upload failures |
SYSTEM_PROMPT | Please perform structured extraction and operational analysis based on the provided financial report data of listed baijiu companies, and prioritize core fields such as baijiu product revenue and production and sales data | Guide the model to focus on exclusive data of baijiu segmented categories, and avoid confusion with information from other business segments |
The parameter values provided on this page are common recommended starting points for configuration. Actual values are affected by material form, data volume and business rules. Specific issues require specific analysis, and actual tests on relevant samples should be conducted before finalizing the configuration.
Three Common Configuration Errors
- The symptom is that after configuring the ollama model, the custom system prompt does not take effect, and the model output does not focus on baijiu financial report-specific analysis content. The cause is that the system prompt for baijiu financial reports is not correctly bound in the model access configuration, or the prompt delivery format of the ollama model does not match the platform requirements.
- The symptom is that tool search cannot be triggered when calling the model, and the multi-period financial report comparison process cannot be executed automatically. The cause is that a model version that supports function call is not selected, or the platform's function call configuration switch is not enabled, resulting in the inability to call external tools combined with context to complete analysis.
- The symptom is that the page fails to load when accessing the OneApi proxy address, and the interface displays a 404 error or connection timeout. The cause is that the port mapping and startup parameters of OneApi are not correctly configured, or there is a compatibility conflict between the deployed version and the current platform version.
How to Verify Successful Configuration
- Upload a test baijiu financial report document, and check whether the parsed data fields cover the exclusive business fields for baijiu specified in the configuration.
- Initiate a test request that includes multi-period financial report comparison, and check whether the model can trigger the preset tool call process.
- Review the model output content, and check whether it meets the focus requirements specified in the configured system prompt.
- Check the running status of the OneApi proxy service, and confirm that there are no startup errors or port conflicts.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.