Service - CommerceAccounting Inventory: Difference between revisions

From Izara Wiki
Jump to navigation Jump to search
No edit summary
Line 15: Line 15:
canDelete: false,
canDelete: false,
belongTo: {
belongTo: {
serviceTag: "User",
serviceTag: "ComAccLink",
objectType: "user"
objectType: "comAccLink"
},
},
addOnDataStructure: [],
addOnDataStructure: [],

Revision as of 15:21, 21 January 2026

Overview

Creates connections between Commerce Inventory and Accounting Accounts where needed.

Repository

...

Object Schemas

Additional Information
Per Service Schemas
{
	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
		}
    ]
}
  • maintains a link between inventoryId and asset purchase journalId
  • required so that depreciation can be accounted for when asset is sold

Relationships

...

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

CommerceAccounting Inventory