Latest revision as of 14:37, 23 January 2026

Overview

.. maybe not required because purchase/manufacture/sale journal entries are handled in their respective comAcc services.

...

...

...

...

@@ Line 1: / Line 1: @@
 = Overview =
-Creates connections between Commerce Inventory and Accounting Accounts where needed.
+.. maybe not required because purchase/manufacture/sale journal entries are handled in their respective comAcc services.
 = Repository =
@@ Line 10: / Line 10: @@
 ; Additional Information: [[Per Service Schemas]]
-<syntaxhighlight lang="JavaScript">
+...
-{
-	objectType: "comAccAssetPurchaseLink",
-	canDelete: false,
-	belongTo: {
-		serviceTag: "ComAccLink",
-		objectType: "comAccLink"
-	},
-	addOnDataStructure: [],
-	storageResources: {
-		"dynamo": {
-			"storageType": "dynamoDB",
-			"tableName": "comAccAssetPurchaseLink",
-		}
-    },
-    fieldNames: {
-		// probably have two dynamo tables, one identified by inventoryId, one by journalId
-    },
-    identifiers: [
-		{
-			// see above note
-		}
-    ]
-}
-</syntaxhighlight>
-* maintains a link between inventoryId and asset purchase journalId
-* required so that depreciation can be accounted for when asset is sold
 == Relationships ==
@@ Line 46: / Line 18: @@
 = flowSchemas =
-== inventoryAssetPurchased ==
+...
-* maybe triggered from ComAcc Sale saleCommitted flow, because needs to know asset purchase journalId
-* simply saves the link for future actions
 = Working documents =