Copyright©2025 Yonyou Group All rights reserved.Without the written permission of Yonyou Group, no part or whole of the content of this user manual may be copied, reproduced, translated, or reduced for any purpose. The content of this user manual may change without notice, please be aware.Please note: The content of this user manual does not represent any commitments made by Yonyou.Operation GuideCost ModelingApp ModelFunction DescriptionThe application model is the foundation for the application of Activity-based Cost Analysis. The model defines the dimensions/dimension system that need to be used. Multiple application models can be defined for different cost allocation applications.Business RuleSupport for adding new app modelsSupport for modifying the app modelSupport for setting allocation modelsSupport for deleting app modelsColumn DescriptionColumn NameDescriptionCodeThe code of the application model, unique under the tenant, cannot be changed once created. Limited to letters, numbers, and underscores.NameThe name of the application model, can be modified after creation.AbbreviationAbbreviated dimension code, can be used to replace the code in calculation rules/validation rules when coding dimensions.Summary StructureThe hierarchy structure of the current dimension in the current model during data aggregation, single-choice dimension system.Is ConvolutionIf the dimension is set to automatic convolution, base node data will automatically convolve to the parent node members.Operation InstructionsAdd/Edit App ModelCode: Required field, cannot be modified after addition;Name: Required field, can be modified after addition;Summary Structure: The text box for displaying references needs to specify the summary structure (dimension system) for the selected dimension, single choice, and cannot be modified after being added.Whether Convolution: Each dimension of the application model can be set to whether it is convoluted, with the allocation lead dimension automatically convoluted;If it is an allocation model, then the dimensions must simultaneously include both allocation leads and data columns.App model deletionIf the application model has no data forms, it can be deleted. When deleting, the public parameters, business rules, and multidimensional data set will be deleted together.Allocation DriversFunction DescriptionUsed to set the cost allocation driver formula.Business RuleSupports preset motive allocation, percentage allocation, and weighted allocation.Support for setting custom drivers.Column Description
: The basis for cost allocation, divided into "Resource Drivers" and "Task Drivers" based on Activity-Based Costing. Common allocation drivers include: product business volume, actual task volume, task quotas/resource quotas, weight coefficients, etc. Two types of allocation drivers are preset: allocation percentage and average allocation.: "Target = (Data to be Allocated - Accession Fixed Amount) * Allocation Driver Ratio": Determine the driver amount based on the configured "Driver + Accession Dimension Member."Operation InstructionsLeft tree: Displays the two root directories of [Allocation Factors] and [Preset Factors].Predefined DriversThe system has preset allocation drivers, which can only be viewed and cannot be added, modified, or deleted:: The sender's data is allocated evenly based on the number of recipients;: Allocation Rules manually specify the accession factor quantity for the recipient.: Allocation Rules manually specify the proportion of the receiving party's driver. The total sum of driver proportions is 100;Custom DriverAllocation factors support [Add], [Delete], [Export], [Import], [Edit] If the allocation factor is referenced by allocation rules, it cannot be [Deleted]The exported file and the imported file template can be used for user migration.[Export]: When not checked, export all current allocation factors;【Import】: Overwrite import when codes are consistent; file limit 1OMHover over the allocation reason with the mouse, click “+” to add a subdirectory.You can continue to add subdirectories, or headcount names, and perform delete operations.Click to add, enter the code and name, select the negative value type (treat as 0 / treat as absolute value). The negative value type refers to the handling method for negative numbers when calculating the driving quantity.Choose whether to enable. When enabled, it allows the allocation rules to reference the driver; when disabled, it checks if it is being referenced; if it is being referenced, disabling the driver is not allowed.Region setting formula left-side variable region descriptionHover over the variable with the mouse, click "Insert," and directly insert the "Data Column." The format displayed in the calculation formula is for example $(‘DATALINE’:’ACTNumber’). Click "Specify Member," and in the reference pop-up, select the unique dimension member to insert it into the formula editor.Formula expressionSupport expression settings for four arithmetic operations: +, -, ×, ÷, (, ).Display the formula for inserting variables and arithmetic operations.In the region, manual input can be done directly.Calculation method for the allocation factor of custom allocation driversUsing the "Designated Dimension # Data Column" of the allocation driver + [Receiving Party] dimension slice + allocation lead [Step0_I] to determine the driver amount (other unspecified dimensions are None members);If there is a conflict between the [Accession Party] and the "Allocation Driver" dimension, the specified dimension member of the "Allocation Driver" shall prevail;When querying multi-dimensional data for driving factors, use "specified dimension#data column" + "accession dimension member slice range" + "[Step0_I] + variable (period, entity)" to query multi-dimensional data;Calculate the proportion of the accession amount for the receiving party by dividing the accession amount of each industry by the total accession amount.ExampleCalculation formula for allocation factors: "Cost project: SMS volume, Data column: Number of entries"Accession dimension member slice: "Cost Center: A01, Task: Leaves (“ACTIVITY”, “ACT001”)”Calculate the driving quantity based on the settings above:Total Driving Quantity (Denominator) = "Cost Project: SMS Volume, Data Column: Count, Cost Center: A01, Task: Leaves (“ACTIVITY”, “ACT001”), Allocation Lead: [Step0_I]"Accession Factor = "Cost Project: SMS Volume, Data Column: Count, Cost Center: A01, Task: XX, Allocate Lead: [Step0_I]"Accession party motivation ratio = Accession party numerator / Total motivation (denominator)Business RuleFunction DescriptionBusiness rules are used to define various calculation/validation rules for data within the system, enabling the extraction, conversion, and validation processing of data records. It supports MDR calculation rules and validation rules.Business RuleSupport rule to add directorySupport for adding, editing, deleting, importing, and exporting business rules.Support for MDR calculation and verification business rules, requires trigger-based execution.Operation InstructionsThe directory under Business Rule is the configured App model.Create New RuleClick to create a new rule - Script Rule, enter the name, select the App model, and this rule will automatically be categorized into the relevant model after Preservation. For details on writing rules, please refer to "Rule Description."PreservationPreserve the current rules, and verify compliance during preservation.CancelCancel current rule preservation.ExportExport selected rules as needed.Click the [Export] button, select the business rules to be exported (you can select all or select some), and generate a compressed file.Export the calculation rules and validation rules listed in the selection list, and export them all at once.ImportClick the [Import] button under the root node and at the single rule location, select the exported Business Rule file, and execute the import operation.Import Validation: Sequentially validate rule type, app model name, dimension information, business rule name;Different rule names, new import;Same rule name, execute overwrite import;Allocation Rules SettingsFunction DescriptionDefine data allocation rules, automatically allocating the sender's data to the receiver's data granularity according to the configured allocation drivers (average allocation, weighted allocation, percentage allocation, custom allocation drivers) proportion. The specific logic is: Target [Receiver] = ([Sender] Data Source - [Receiver] Fixed Amount) * [Allocation Driver] proportion of the driver amount. The system will automatically record each step of the allocation chain, and the allocation results can be traced back.Business RuleSupport for adding new Allocation Rules directory;Allocation Rules support visual configuration, allowing for [Add], [Delete], [Copy], [Export], [Import], and [Edit] functions;Column Description【Basic Information】Configuration InstructionsFieldStyleRange/LimitDescriptionAllocation Rules CodeRequiredLimited to "letters, numbers, underscores";Limit 50 characters | Allow modification of allocation rules code, but if referenced by "Collection and Allocation Definition," modification of the rules code is not allowed ||Allocation Rule Name|Required in Chinese|Limit 200 characters|||Cost Model|Required|Display "Allocation Model" only||| Sender Dimension | Required | After selecting the dimension, the [Sender] region displays dimension code and name | Dimension Reference: All dimensions in this model except for cost projects and resources (excluding period, currency, measurement dimension, and data columns) ||Receiving Party Dimension|Required|After selecting the dimension, the [Receiving Party] region displays dimension code and name|Dimension Reference: Other dimensions of this model excluding cost projects and resources (excluding period, currency, measurement dimension, and data columns)||Default Allocation Factor|Required|Reference comes from [Allocation Factor]; Only "Enabled" allocation factors are displayed in the options|Sender: When no allocation factor is specified, the default allocation factor is used for allocation|| Accession Cost Element Transfer | Yes/No | "Yes": The recipient list displays "Cost Project""No": Do not display cost project |||Rounding Difference Handling|Max/Min/Specified|Max: Rounding difference included in the maximum value;Minimum: Rounding Difference included in the minimum value;Specification: Allow the designated unique accession to be included in the rounding difference; the accession list displays the "Rounding Difference" radio button | Maximum/Minimum: When there are data of the same size, the last entry accepts the rounding difference according to the calculation result order of the accession. || Allocation Data Column | Required | Reference from the current model's data column | As members of the allocation data column dimension. ||Enable|Switch|On/Off|Allocation rules that are only in the enabled state, available for reference in [Collection and Allocation Transaction Definition];||Description|Optional|Text Input Box|Length Limit 300 Characters||Collapse||The query area allows for folding and unfolding|||Visual View/Script Edit||Default "Visual View":Visual View: Display Sender, AccessionScript Editing: Display the rules script for visual configuration, allowing editing.【Sender】Configuration InstructionsField/ButtonScope/LimitationsDescriptionCost Project CodeReference sourced from "Cost Project" dimension members;Supports selection of dimension members;Support rule members;||Cost Project Name...
