1. Conversion Rules: Requirement Scenarios

• A single conversion relationship can include multiple conversion rules to support multi-way propagation.
• Conversion rules can be duplicated to speed up configuration.
• Specify which Primary Object fields need tracking and back-write. The rule must associate with the Primary Object to support data backflow.
• Define mappings between Record Types of two objects to enable Record Type conversion between specified entities.
• Specify target field mappings; the system performs smart auto-matching to simplify configuration.
• Configure split-and-merge strategies for scenarios where child-object data must be consolidated. (To be supported)
• Define back-write field settings and source-document-closing strategies so that when the target object is processed, the source object synchronizes automatically.

2. Example Business Scenarios for Conversion Rules

Purchase Requisition -> Purchase Order: - Company A’s procurement policy: core frequently used items (supplier and price pre-agreed annually) are bought on demand. Workflow: the consuming Dept. initiates a Purchase Requisition -> after approval -> the system automatically generates an official Purchase Order. - In one Purchase Requisition, items A and B may belong to different Suppliers. After approval, the system splits the requisition according to rules and automatically creates two Purchase Orders for the respective Suppliers.

Create Purchase Order by referencing multiple Purchase Requisitions: - Company B centralizes procurement for MRO and office supplies. Individual Depts. submit many Purchase Requisitions throughout the month. At month-end, the centralized procurement team pulls all pending requisitions and consolidates requests with the same item classification and required date. Multiple requisitions merge into a single Purchase Order for centralized quotation and procurement processing.