Cloud ERP Account Identifier Renumbering via Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing cloud ERP systems have limited flexibility to reconfigure account settings after deployment, making it difficult for users to change general ledger account identifiers without compromising system integrity or disrupting operations, often requiring the discarding of historical data and reimplementation of the system.
Innovation Solution
A method and system for changing general ledger account identifiers in a deployed cloud ERP system by receiving a change request, updating the identifiers in backend tables and a reference framework, and maintaining hashed keys to ensure seamless integration and data preservation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If cloud ERP systems are deployed with fixed account settings, then system stability and integrity are maintained, but flexibility to reconfigure accounts after deployment is limited
Solution Approach 1:
The system performs preliminary actions by creating a mapping between old account identifiers and new account identifiers before executing the reconfiguration. This mapping is established in advance and used to guide the systematic replacement of identifiers across all tables and the reference framework, ensuring that the reconfiguration process maintains system integrity while achieving the desired adaptability.
Solution Approach 2:
The patent introduces an intermediary mapping mechanism that mediates between the old account identifier system and the new account identifier system. This mapping structure acts as a bridge, allowing the system to transition from one identifier scheme to another while maintaining references and relationships, thus resolving the contradiction between flexibility and integrity.
2Adaptability or versatility
If general ledger account identifiers are changed in deployed systems, then adaptability is improved, but system operations may be disrupted
Solution Approach 1:
The system performs all identifier mappings and updates in advance before actual system operations resume. By preparing the mapping structure and executing table updates beforehand, the system minimizes disruption to ongoing operations and ensures continuous functionality during the reconfiguration process.
Solution Approach 2:
The patent implements feedback mechanisms that monitor the reconfiguration process and verify the accuracy of identifier replacements. This feedback loop ensures that any discrepancies are detected and corrected promptly, maintaining system operation continuity while enabling identifier changes.
3Ease of manufacture
If account identifiers are reconfigured without preserving historical data, then reimplementation is simplified, but information loss occurs
Solution Approach 1:
The system temporarily discards the old account identifier references during the mapping process but recovers and preserves historical data through the mapping mechanism. The mapping structure stores the relationship between old and new identifiers, allowing historical data to be recovered and maintained while enabling the simplified reimplementation process.
Solution Approach 2:
The patent creates a copy of the historical data structure through the mapping mechanism, preserving the relationships and references while allowing the system to operate with new identifiers. This copying approach enables reimplementation simplicity while preventing information loss.
4Reliability
If comprehensive identifier replacement is performed across all tables and reference frameworks, then system consistency is achieved, but processing time increases
Solution Approach 1:
The patent segments the comprehensive identifier replacement process into distinct phases: first establishing the mapping between old and new identifiers, then systematically applying the mapping to individual tables, and finally updating the reference framework. This segmentation allows for more efficient processing while maintaining system consistency.
Solution Approach 2:
The mapping structure is established as a preliminary action before processing individual tables. This pre-computed mapping serves as a reference that accelerates the subsequent identifier replacement process across all tables and the reference framework, reducing overall processing time while ensuring comprehensive consistency.
Data Source
AI summary
A computer-implemented method is disclosed. In a deployed cloud-based enterprise resource planning system that includes a general ledger account, the method can receive a change request specifying a new account identifier for the general ledger account, wherein the general ledger account is associated with an old account identifier. For a plurality of tables in the deployed enterprise resource planning system, the method can change the old account identifier to the new account identifier. In addition, for a reference framework interfacing with the plurality of tables, the method can change the old account identifier to the new account identifier in the reference framework.