Service - CommerceAccounting Inventory - Revision history

Sven the Barbarian at 13:00, 16 April 2026

2026-04-16T13:00:48Z

← Older revision		Revision as of 13:00, 16 April 2026
Line 30:		Line 30:
	// businessId		// businessId
	// inventoryId		// inventoryId
	// ~~accountlinkTag~~ // type of link: inventoryAsset\|..		// accountLinkTag // type of link: inventoryAsset\|..
	// accountId		// accountId
	},		},
Line 40:		Line 40:
	{		{
	type: "sortKey",		type: "sortKey",
	fieldName: "~~accountlinkTag~~"		fieldName: "accountLinkTag"
	},		},
	]		]
Line 62:		Line 62:
	"tableName": "comAccInventoryLocationLink",		"tableName": "comAccInventoryLocationLink",
	}		}
	~~"graph": {}~~
	},		},
	fieldNames: {		fieldNames: {
	// businessId		// businessId
	// inventoryLocationId		// inventoryLocationId
	// ~~accountlinkTag~~ // type of link: inventoryAsset\|..		// accountLinkTag // type of link: inventoryAsset\|..
	// accountId		// accountId
	},		},
Line 77:		Line 76:
	{		{
	type: "sortKey",		type: "sortKey",
	fieldName: "~~accountlinkTag~~"		fieldName: "accountLinkTag"
	},		},
	]		]
Line 99:		Line 98:
	"tableName": "comAccInventoryTemplateLink",		"tableName": "comAccInventoryTemplateLink",
	}		}
	~~"graph": {}~~
	},		},
	fieldNames: {		fieldNames: {
	// businessId		// businessId
	// inventoryTemplateId		// inventoryTemplateId
	// ~~accountlinkTag~~ // type of link: inventoryAsset\|..		// accountLinkTag // type of link: inventoryAsset\|..
	// accountId		// accountId
	},		},
Line 114:		Line 112:
	{		{
	type: "sortKey",		type: "sortKey",
	fieldName: "~~accountlinkTag~~"		fieldName: "accountLinkTag"
	},		},
	]		]
Line 136:		Line 134:
	"tableName": "comAccInventoryTypeLink",		"tableName": "comAccInventoryTypeLink",
	}		}
	~~"graph": {}~~
	},		},
	fieldNames: {		fieldNames: {
	// businessId		// businessId
	// inventoryType // goods\|intangibleGoods\|rawMaterial\|asset\|intangibleAsset		// inventoryType // goods\|intangibleGoods\|rawMaterial\|asset\|intangibleAsset
	// ~~accountlinkTag~~ // type of link: inventoryAsset\|..		// accountLinkTag // type of link: inventoryAsset\|..
	// accountId		// accountId
	},		},
Line 151:		Line 148:
	{		{
	type: "sortKey",		type: "sortKey",
	fieldName: "~~accountlinkTag~~"		fieldName: "accountLinkTag"
	},		},
	]		]

Sven the Barbarian at 22:33, 15 April 2026

2026-04-15T22:33:37Z

@@ Line 46: / Line 46: @@
 </syntaxhighlight>
-== comAccDefaultInventoryLink ==
+== comAccInventoryLocationLink ==
 <syntaxhighlight lang="JavaScript">
+{
-	objectType: "comAccDefaultInventoryLink",
+	objectType: "comAccInventoryLocationLink",
 	canDelete: false,
 	belongTo: {
@@ Line 60: / Line 60: @@
 		"dynamo": {
 			"storageType": "dynamoDB",
-			"tableName": "comAccDefaultInventoryLink",
+			"tableName": "comAccInventoryLocationLink",
+		}
 		"graph": {}
@@ Line 67: / Line 141: @@
 		// businessId
 		// inventoryType // goods|intangibleGoods|rawMaterial|asset|intangibleAsset
-		// accountlinkTag // type of link: accountsPayable|..
+		// accountlinkTag // type of link: inventoryAsset|..
 		// accountId
      },

Sven the Barbarian at 22:13, 15 April 2026

2026-04-15T22:13:10Z

@@ Line 1: / Line 1: @@
 = Overview =
-.. maybe not required because purchase/manufacture/sale journal entries are handled in their respective comAcc services.
+Links Inventory objects to Accounting structures.
 = Repository =
@@ Line 10: / Line 10: @@
 ; Additional Information: [[Per Service Schemas]]
-...
+== comAccInventoryLink ==
 == Relationships ==

Sven the Barbarian at 14:37, 23 January 2026

2026-01-23T14:37:01Z

@@ 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">
+...
 == Relationships ==
@@ Line 46: / Line 18: @@
 = flowSchemas =
-== inventoryAssetPurchased ==
+...
 = Working documents =

Sven the Barbarian: /* Object Schemas */

2026-01-21T15:21:38Z

Object Schemas

← Older revision		Revision as of 15:21, 21 January 2026
Line 15:		Line 15:
	canDelete: false,		canDelete: false,
	belongTo: {		belongTo: {
	serviceTag: "~~User~~",		serviceTag: "ComAccLink",
	objectType: "~~user~~"		objectType: "comAccLink"
	},		},
	addOnDataStructure: [],		addOnDataStructure: [],

Sven the Barbarian at 13:59, 12 January 2026

2026-01-12T13:59:45Z

← Older revision		Revision as of 13:59, 12 January 2026
Line 48:		Line 48:
	== inventoryAssetPurchased ==		== inventoryAssetPurchased ==

	* maybe triggered from ComAcc Sale ~~saleCreated~~ flow, because needs to know asset purchase journalId		* maybe triggered from ComAcc Sale saleCommitted flow, because needs to know asset purchase journalId
	* simply saves the link for future actions		* simply saves the link for future actions

Sven the Barbarian at 12:26, 11 January 2026

2026-01-11T12:26:23Z

← Older revision		Revision as of 12:26, 11 January 2026
Line 1:		Line 1:
	= Overview =		= Overview =

	~~Handles changes in inventory in~~ Commerce		Creates connections between Commerce Inventory and Accounting Accounts where needed.

	= Repository =		= Repository =
Line 12:		Line 12:
	<syntaxhighlight lang="JavaScript">		<syntaxhighlight lang="JavaScript">
	{		{
	objectType: "~~comAccInventoryPurchasedLink~~",		objectType: "comAccAssetPurchaseLink",
	canDelete: false,		canDelete: false,
	belongTo: {		belongTo: {
Line 22:		Line 22:
	"dynamo": {		"dynamo": {
	"storageType": "dynamoDB",		"storageType": "dynamoDB",
	"tableName": "~~comAccLink~~",		"tableName": "comAccAssetPurchaseLink",
	}		}
	},		},
	fieldNames: {		fieldNames: {
	// probably have two dynamo tables, one identified by ~~saleLineItemId~~, one by journalId		// probably have two dynamo tables, one identified by inventoryId, one by journalId

	},		},
Line 37:		Line 37:
	</syntaxhighlight>		</syntaxhighlight>

	* maintains a link between ~~saleLineItemId~~ and journalId~~, so can adjust if changes made to purchases~~		* maintains a link between inventoryId and asset purchase journalId
	* can ~~maybe use~~ for ~~all inventory types~~		* required so that depreciation can be accounted for when asset is sold

	== Relationships ==		== Relationships ==
Line 46:		Line 46:
	= flowSchemas =		= flowSchemas =

	== ~~inventoryGoodsPurchased~~ ==		== inventoryAssetPurchased ==

	* ~~accountTag: inventoryGoods~~		* maybe triggered from ComAcc Sale saleCreated flow, because needs to know asset purchase journalId
	* when submitting purchase order, ~~if is inventoryGoods make a positive entry in inventoryGoods(Asset) Accounting Account~~		* simply saves the link for future actions

	~~== inventoryGoodsPurchaseChange ==~~

	* accountTag: inventoryGoods
	* make adjustment to ~~journal entry when~~ purchase ~~saleLineItemId changes~~
	* ~~perhaps handling removal of journal entry also~~

	= Working documents =		= Working documents =

Sven the Barbarian: Created page with "= Overview = Handles changes in inventory in Commerce = Repository = ... = Object Schemas = ; Additional Information: Per Service Schemas { objectType: "comAccInventoryPurchasedLink", canDelete: false, belongTo: { serviceTag: "User", objectType: "user" }, addOnDataStructure: [], storageResources: { "dynamo": { "storageType": "dynamoDB", "tableName": "comAccLink", } }, fieldNames: { // probably hav..."

2026-01-10T13:27:59Z

Created page with "= Overview = Handles changes in inventory in Commerce = Repository = ... = Object Schemas = ; Additional Information: Per Service Schemas <syntaxhighlight lang="JavaScript"> { objectType: "comAccInventoryPurchasedLink", canDelete: false, belongTo: { serviceTag: "User", objectType: "user" }, addOnDataStructure: [], storageResources: { "dynamo": { "storageType": "dynamoDB", "tableName": "comAccLink", } }, fieldNames: { // probably hav..."

New page

= Overview =

Handles changes in inventory in Commerce

= Repository =

...

= Object Schemas =
; Additional Information: [[Per Service Schemas]]

<syntaxhighlight lang="JavaScript">
{
objectType: "comAccInventoryPurchasedLink",
canDelete: false,
belongTo: {
serviceTag: "User",
objectType: "user"
},
addOnDataStructure: [],
storageResources: {
"dynamo": {
"storageType": "dynamoDB",
"tableName": "comAccLink",
}
},
fieldNames: {
// probably have two dynamo tables, one identified by saleLineItemId, one by journalId

},
identifiers: [
{
// see above note
}
]
}
</syntaxhighlight>

* maintains a link between saleLineItemId and journalId, so can adjust if changes made to purchases
* can maybe use for all inventory types

== Relationships ==

...

= flowSchemas =

== inventoryGoodsPurchased ==

* accountTag: inventoryGoods
* when submitting purchase order, if is inventoryGoods make a positive entry in inventoryGoods(Asset) Accounting Account

== inventoryGoodsPurchaseChange ==

* accountTag: inventoryGoods
* make adjustment to journal entry when purchase saleLineItemId changes
* perhaps handling removal of journal entry also

= Working documents =

[[:Category:Working_documents - CommerceAccounting Inventory| CommerceAccounting Inventory]]

[[Category:Backend services| CommerceAccounting Inventory]]