Service - Inventory Location Manager: Difference between revisions
Jump to navigation
Jump to search
(Created page with "= Overview = Where inventory is located = Repository = ... = Object Schemas = ; Additional Information: Per Service Schemas == objType == === inventoryLocation === <syntaxhighlight lang="JavaScript"> { objectType: "inventoryLocation", canDelete: false, belongTo: { serviceTag: "user", objectType: "user" }, addOnDataStructure: [ type: "propertyValue" ], storageResources: { myGraph: { storageType: "graph", graphServerTag: "GraphHandler" }...") |
|||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
= Overview = | = Overview = | ||
Where inventory is located | Where inventory is located, inventory location also distinguishes whether an inventoryUnit is in stock, is work in progress, was the input to other unit/s through production, or sold to a customer. | ||
To move an inventoryUnit from one location to another (eg to sell it) requires reserving the stock, performing the movement (eg removing/adding links in graph), then confirming the reservation. | |||
= Repository = | = Repository = | ||
| Line 20: | Line 22: | ||
canDelete: false, | canDelete: false, | ||
belongTo: { | belongTo: { | ||
serviceTag: " | serviceTag: "Business", | ||
objectType: " | objectType: "business" | ||
}, | }, | ||
addOnDataStructure: [ | addOnDataStructure: [ | ||
| Line 42: | Line 44: | ||
storageResourceTags: ['myGraph', 'dynamoDB'] | storageResourceTags: ['myGraph', 'dynamoDB'] | ||
}, | }, | ||
inventoryLocationHandlerServiceNameTag: { | |||
type: "string", | type: "string", | ||
optionalOnCreate: true, | |||
storageResourceTags: ['dynamoDB'] | storageResourceTags: ['dynamoDB'] | ||
}, | }, | ||
| Line 50: | Line 52: | ||
identifiers: [ | identifiers: [ | ||
{ | { | ||
type: " | type: "partitionKey", | ||
fieldName: " | fieldName: "inventoryLocationId" | ||
} | } | ||
] | ] | ||
| Line 59: | Line 61: | ||
== Object Relationships == | == Object Relationships == | ||
=== | === atInventoryLocation === | ||
<syntaxhighlight lang="JavaScript"> | <syntaxhighlight lang="JavaScript"> | ||
{ | { | ||
atInventoryLocation: { | |||
storageResources: { | storageResources: { | ||
myGraph: { | myGraph: { | ||
| Line 76: | Line 78: | ||
objType: { | objType: { | ||
serviceTag: "inventoryManager", | serviceTag: "inventoryManager", | ||
objectType: " | objectType: "inventoryUnit" | ||
}, | }, | ||
linkType: "many", | linkType: "many", | ||
Latest revision as of 06:03, 14 March 2026
Overview
Where inventory is located, inventory location also distinguishes whether an inventoryUnit is in stock, is work in progress, was the input to other unit/s through production, or sold to a customer.
To move an inventoryUnit from one location to another (eg to sell it) requires reserving the stock, performing the movement (eg removing/adding links in graph), then confirming the reservation.
Repository
...
Object Schemas
- Additional Information
- Per Service Schemas
objType
inventoryLocation
{
objectType: "inventoryLocation",
canDelete: false,
belongTo: {
serviceTag: "Business",
objectType: "business"
},
addOnDataStructure: [
type: "propertyValue"
],
storageResources: {
myGraph: {
storageType: "graph",
graphServerTag: "GraphHandler"
}
dynamoDB: {
storageType: "dynamoDB",
"tableName": "inventoryLocation",
}
},
fieldNames: {
inventoryLocationId: {
type: "string",
randomOnCreate: true,
storageResourceTags: ['myGraph', 'dynamoDB']
},
inventoryLocationHandlerServiceNameTag: {
type: "string",
optionalOnCreate: true,
storageResourceTags: ['dynamoDB']
},
},
identifiers: [
{
type: "partitionKey",
fieldName: "inventoryLocationId"
}
]
}
Object Relationships
atInventoryLocation
{
atInventoryLocation: {
storageResources: {
myGraph: {
storageType: "graph",
graphServerTag: "GraphHandler"
}
},
links: [
{
storageResourceTags: ["myGraph"],
from: {
objType: {
serviceTag: "inventoryManager",
objectType: "inventoryUnit"
},
linkType: "many",
},
to: {
objType: {
serviceTag: "inventoryLocationManager",
objectType: "inventoryLocation"
},
linkType: "one"
}
}
]
}
}
- handle history of inventoryLocations same as stockLocations