Service - CommerceAccounting Inventory: Difference between revisions
Jump to navigation
Jump to search
(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...") |
No edit summary |
||
| Line 1: | Line 1: | ||
= Overview = | = Overview = | ||
Creates connections between Commerce Inventory and Accounting Accounts where needed. | |||
= Repository = | = Repository = | ||
| Line 12: | Line 12: | ||
<syntaxhighlight lang="JavaScript"> | <syntaxhighlight lang="JavaScript"> | ||
{ | { | ||
objectType: " | objectType: "comAccAssetPurchaseLink", | ||
canDelete: false, | canDelete: false, | ||
belongTo: { | belongTo: { | ||
| Line 22: | Line 22: | ||
"dynamo": { | "dynamo": { | ||
"storageType": "dynamoDB", | "storageType": "dynamoDB", | ||
"tableName": " | "tableName": "comAccAssetPurchaseLink", | ||
} | } | ||
}, | }, | ||
fieldNames: { | fieldNames: { | ||
// probably have two dynamo tables, one identified by | // probably have two dynamo tables, one identified by inventoryId, one by journalId | ||
}, | }, | ||
| Line 37: | Line 37: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
* maintains a link between | * maintains a link between inventoryId and asset purchase journalId | ||
* can | * required so that depreciation can be accounted for when asset is sold | ||
== Relationships == | == Relationships == | ||
| Line 46: | Line 46: | ||
= flowSchemas = | = flowSchemas = | ||
== | == inventoryAssetPurchased == | ||
* | * maybe triggered from ComAcc Sale saleCreated flow, because needs to know asset purchase journalId | ||
* simply saves the link for future actions | |||
* | |||
= Working documents = | = Working documents = | ||
Revision as of 12:26, 11 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: "User",
objectType: "user"
},
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 saleCreated flow, because needs to know asset purchase journalId
- simply saves the link for future actions