Documentation
Item Categories
Item Categories classifies Items into an Organization-scoped hierarchy and can provide category-level Business Unit and Cost Center defaults for downstream financial-dimension resolution. Treat categories as controlled master data because Items and other ERP functions can depend on them.
What Item Categories controls
Item Categories gives Inventory Items a reusable business classification. A category can be top-level or can sit below another category, allowing structures such as Raw Materials → Metals → Steel or Books → Language → Telugu.
A category is more than a display label. Items can reference it, financial-dimension behavior can use it, and connected functions can use Item Category as a rule, mapping or assignment condition. Category design should therefore be treated as controlled master-data work.
Quick Reference
| Task | What to do | Control to remember |
|---|---|---|
| Create | Inventory → Item Categories → Create. | Organization is taken automatically from the active ERP context. |
| Find | Use list search, sorting and paging. | Only categories in the active Organization are returned. |
| Edit | Click the category row. | Review downstream impact before changing hierarchy or accounting defaults. |
| Create a child | Select an active Parent Category. | Parent must belong to the same Organization and cannot create a circular hierarchy. |
| Retire | Clear Active and Save. | Preferred for a category that has been used historically. |
| Reactivate | Select Active and Save. | Recheck hierarchy and defaults before returning the category to active use. |
| Delete | Select an unused category and choose Delete. | Deletion is blocked when the category is already in use; deactivate it instead. |
| Set accounting defaults | Select Default Business Unit and/or Default Cost Center. | These are dynamic business-master lookups, not free text or Value Sets. |
Before you start
- Confirm the correct Organization is active in AkshaERP.
- Search for an existing Category Name and Category Code before creating a new record.
- Decide the hierarchy and code convention before creating a large category tree.
- Create or activate the required Business Unit before using Default Business Unit.
- Create or activate the required Cost Center before using Default Cost Center.
Organization context – how ownership works
Every Item Category belongs to the Organization active in the ERP session. The user does not manually type or select Organization on the Item Category page.
The same Organization scope applies to the category list, Parent Category choices and the Business Unit and Cost Center values that can be used with the category.
List page – what you can see and do
The Item Categories list is the operating entry point for the active Organization. It supports search, sorting, paging, row selection, Create, Edit and controlled Delete.
| Column | Meaning | How to use it |
|---|---|---|
| Category | Business-readable Category Name. | Use this for normal recognition and searching. |
| Category Code | Stable controlled code. | Use this to distinguish similar names and confirm the category used by integrations or rule setup. |
| Parent Category | Immediate parent in the hierarchy. | Blank means the category is top-level. |
| Description | Optional explanation of scope. | Useful when similar category names could otherwise be ambiguous. |
| Active | Yes / No lifecycle state. | Inactive categories remain for history but should not be selected for new hierarchy setup. |
Create / Edit page – screen behavior
Choose Create for a new category or click an existing list row to edit it. Create and Edit use the same business fields while Organization is supplied by ERP context.
Save checks required fields, Organization ownership, hierarchy and selected financial-dimension references. Close returns to the Item Categories list.
| Field | Requirement | Source / type | What to enter or select | Why it matters |
|---|---|---|---|---|
| Category Name | Hard-save mandatory | Manual text | Clear business name, maximum 255 characters. | Displayed throughout AkshaERP wherever the category is referenced. |
| Category Code | Hard-save mandatory | Manual stable code | Up to 50 characters. Letters are normalized to uppercase and separators are represented using underscores. | Controlled identifier that must be unique inside the active Organization. |
| Description | Optional | Manual text | Explain what belongs in the category or clarify scope. | Improves master-data understanding without changing hierarchy. |
| Parent Category | Optional / conditional | Dynamic Item Category lookup | Select an existing active category from the same Organization. | Places this category under the selected parent. Leave blank for a top-level category. |
| Active | Operational lifecycle control | Checkbox | Selected means active; new categories start active. | Controls whether the category remains available for active hierarchy selection while preserving existing references. |
| Default Business Unit | Optional / accounting control | Dynamic Business Unit lookup | Select an active Business Unit available to the user in the same Organization. | Can provide a category-level Business Unit fallback where applicable. |
| Default Cost Center | Optional / accounting control | Dynamic Cost Center lookup | Select an active Cost Center in the same Organization. | Can provide a category-level Cost Center fallback where applicable. |
The selectable fields on Item Categories are dynamic business-data lookups. They are not Application Management Value Sets. If a value is missing, maintain the owning master and then return to Item Categories.
| Field | Lookup source | Filtering / dependency | Where to maintain a missing value |
|---|---|---|---|
| Parent Category | Existing Item Categories | Active categories in the current Organization; the current category and its descendants are not valid parent choices while editing. | Inventory → Item Categories. Create or reactivate the correct parent only when the hierarchy is genuinely valid. |
| Default Business Unit | Business Unit master | Active Business Units in the current Organization and subject to user/role Business Unit access. | Access Management → Business Units. Also verify that the user has access to the Business Unit. |
| Default Cost Center | Cost Center master | Active Cost Centers in the current Organization. | Access Management → Cost Centers. |
Parent Category – hierarchy rules
Parent Category builds the classification tree. Leave it blank for a root category or select an existing active category to place the record below that parent.
AkshaERP prevents direct self-parenting and circular relationships. When editing a category, its descendants are not valid parent choices because placing a category below its own descendant would create a loop.
| Example | Allowed? | Reason |
|---|---|---|
| Books → Telugu Books | Yes | Normal parent-child classification. |
| Raw Materials → Metals → Steel | Yes | Multi-level hierarchy is valid. |
| Books → Books | No | A category cannot be its own parent. |
| A → B → C, then set A parent to C | No | This creates a circular hierarchy. |
| Organization A child → Organization B parent | No | Parent and child must belong to the same active Organization. |
| Select an inactive parent for new setup | No | Inactive categories are retained for history but are not active parent candidates. |
Financial Dimension defaults – how Category defaults participate
Default Business Unit and Default Cost Center let an Item Category contribute accounting defaults when an Item or transaction needs Financial Dimensions.
The category value is a reusable fallback rather than an unconditional override. More specific transaction, source-document or Item information can take precedence.
How Category defaults participate
| Priority concept | Meaning |
|---|---|
| Transaction / source context | Explicit values or values already established for the transaction normally take priority. |
| Item-specific setup | A more specific Item default can take priority over its Category. |
| Item Category | Category Business Unit / Cost Center can be used as a reusable fallback where applicable. |
| Other configured defaults | AkshaERP may then use other applicable Organization, location, party or configured Financial Dimension controls. |
| State | Meaning | Recommended use |
|---|---|---|
| Active | Available for current setup and active hierarchy selection. | Use while the classification is valid for new business. |
| Inactive | Retained for existing references and history but not offered as a new Parent Category. | Use when a category is retired but must remain because Items or other records already reference it. |
Actions – what each one means
| Action | Where | Effect | Control boundary |
|---|---|---|---|
| Create | List page | Opens a new category using active Organization context. | Search first and confirm context. |
| Save | Create/Edit | Checks and stores the category. | Invalid hierarchy, Organization ownership or dimension references are rejected. |
| Close | Create/Edit | Returns to the category list. | Save first when changes should be retained. |
| Edit | Click a list row | Opens the selected category. | The list remains scoped to the active Organization. |
| Deactivate | Edit page via Active | Retains the record but retires it from active hierarchy selection. | Preferred lifecycle action for historically used categories. |
| Delete | List page | Permanently removes an unused category. | Blocked when known dependencies or child categories exist. |
| Multi-delete | List page | Attempts deletion of selected unused categories as one operation. | If one selected category is blocked, the operation is rejected rather than partially deleting the selection. |
- An active Organization context is required.
- Category Name is required and is limited to 255 characters.
- Category Code is required, limited to 50 characters and normalized into a stable uppercase identifier format.
- Category Code must be unique within the active Organization.
- Parent Category must belong to the same Organization.
- A newly selected Parent Category must be active.
- A category cannot be its own parent.
- A category cannot be moved below one of its descendants because that would create a circular hierarchy.
- Default Business Unit must be active for the same Organization and must be available to the current user where Business Unit access restrictions apply.
- Default Cost Center must be active for the same Organization.
- Delete is rejected when known dependent setup or business records still reference the category.
Delete versus deactivate – choose the safe lifecycle action
Delete and Deactivate solve different problems. Delete is for a master-data mistake that was never used. Deactivate retires a valid historical category without breaking records that still depend on it.
| Situation | Recommended action | Why |
|---|---|---|
| Created by mistake and never used | Delete | No history or downstream dependency needs to be preserved. |
| Used by one or more Items | Deactivate | Items and historical documents still need the classification. |
| Has child categories | Restructure children first or deactivate | Deleting a parent directly would break the hierarchy. |
| Referenced by accounting/rule setup | Review the rule and normally deactivate | The category remains part of configured financial logic. |
| No longer wanted for new business | Deactivate | Stops new active use while preserving history. |
Downstream impact – what can change when this master changes
Item Categories is shared master data. The exact downstream effect depends on which AkshaERP modules are configured, but the following relationships are important when reviewing a category change.
| Connected area | How Item Category can be used | What to review before changing |
|---|---|---|
| Items | Items can reference the category. | Changing hierarchy or retiring a category changes how those Items are classified for future use. |
| Financial Dimensions | Category can provide Business Unit / Cost Center defaults and participate in configured dimension behavior. | Review whether future financial attribution should change. |
| Ecommerce | Inventory category identity/hierarchy can be used for catalog category projection where Ecommerce is enabled. | Review storefront/catalog classification before renaming, reparenting or deactivating a mature category. |
| Quality Management | Inspection-plan assignments can target Item Category where QMS is configured. | Review whether inspection routing still matches the revised category structure. |
| Manufacturing | Category-aware capability or other setup can target Item Category where Manufacturing is configured. | Review the connected setup before significant category changes. |
Common operating tasks
Create a top-level category
| Step | Action |
|---|---|
| 1 | Confirm the correct Organization is active. |
| 2 | Open Inventory → Item Categories and search for the category first. |
| 3 | Choose Create. |
| 4 | Enter Category Name and stable Category Code. |
| 5 | Leave Parent Category blank. |
| 6 | Add Description and optional Financial Dimension defaults where appropriate. |
| 7 | Leave Active selected and Save. |
Create a child category
| Step | Action |
|---|---|
| 1 | Confirm the intended parent exists and is active in the same Organization. |
| 2 | Create the new category and enter Name / Code. |
| 3 | Select Parent Category. |
| 4 | Set optional Business Unit / Cost Center defaults where appropriate. |
| 5 | Save and review the category in the list. |
Retire an existing category
| Step | Action |
|---|---|
| 1 | Open the category and review children and known downstream use. |
| 2 | Correct downstream setup only where the business relationship itself is wrong. |
| 3 | Clear Active rather than deleting when the category has history or references. |
| 4 | Save. |
| 5 | Review connected accounting, Ecommerce, Quality or Manufacturing setup when those modules use the category. |
Practical examples
Publishing / book business example
| Level 1 | Level 2 | Level 3 |
|---|---|---|
| Books | Language | Telugu |
| Books | Language | English |
| Books | Genre | Literature |
| Books | Genre | Children |
Manufacturing example
| Level 1 | Level 2 | Level 3 |
|---|---|---|
| Raw Materials | Metals | Steel |
| Raw Materials | Electrical | Components |
| Finished Goods | Product Family A | Model Group |
| Spares | Mechanical | Bearings |
Troubleshooting
| Problem | Likely reason | What to do |
|---|---|---|
| Parent Category is missing | It is inactive, in another Organization, is the current category, or is one of its descendants. | Confirm Organization context and hierarchy. Create or reactivate only the genuinely correct parent. |
| Default Business Unit is missing | It may be inactive, in another Organization, or not available to the user through Business Unit access. | Review Access Management → Business Units and the user/role Business Unit access configuration. |
| Default Cost Center is missing | It may be inactive or owned by another Organization. | Review Access Management → Cost Centers for the active Organization. |
| Save says Category Code already exists | The normalized code is already in use in the active Organization. | Search for the existing category and reuse it, or choose a genuinely different stable code. |
| Parent selection is rejected | The relationship would create self-parenting, a circular hierarchy or an Organization mismatch. | Choose a valid active parent outside the current category descendant tree. |
| Delete is blocked | The category has children or is referenced by another function. | Review the dependency message and normally make the category inactive instead. |
| Category was created in the wrong Organization | The wrong ERP Organization context was active during creation. | If completely unused, delete it; otherwise preserve history and review corrective setup. Switch context before creating the correct category. |
| Control | Remember |
|---|---|
| Organization | Automatic from active ERP context; not selected on the Item Category form. |
| Category Code | Required, stable, uppercase-normalized, maximum 50 characters and unique per Organization. |
| Parent Category | Optional; active; same Organization; no self/circular hierarchy. |
| Active | Use Inactive to retire used categories while preserving historical references. |
| Default Business Unit | Optional dynamic business master with Organization and user/role access controls. |
| Default Cost Center | Optional dynamic business master; active in the same Organization. |
| Delete | Only for unused categories; referenced categories should normally be deactivated. |
| Multi-delete | All-or-nothing: one blocked selected category prevents partial deletion. |
Related pages
Frequently asked questions
Do I select Organization when creating an Item Category?
No. AkshaERP takes Organization from the active ERP context and applies that same Organization to the Item Category and its related lookups.
Can two Organizations use the same Category Code?
Yes when each Organization owns its own category. Category Code uniqueness is enforced within the active Organization.
Can an Item Category have another Item Category as its parent?
Yes. The parent must be active and in the same Organization, and the relationship cannot create self-parenting or a circular hierarchy.
Why can’t I see an inactive category in Parent Category?
Inactive categories are retained for existing references but are excluded from active Parent Category selection.
Where do Default Business Unit values come from?
They come from active Business Units for the current Organization and are subject to the user/role Business Unit access configuration. Maintain them under Access Management → Business Units.
Where do Default Cost Center values come from?
They come from active Cost Centers for the current Organization. Maintain them under Access Management → Cost Centers.
Are Parent Category, Business Unit and Cost Center Value Sets?
No. They are dynamic business-data lookups supplied by Item Categories, Business Units and Cost Centers respectively.
What do the Business Unit and Cost Center defaults do?
When Financial Dimensions are enabled, they can provide category-level fallback values when the applicable transaction or more specific setup has not already established the dimension. The exact result depends on the transaction and configured Financial Dimension controls.
Can I delete a category that already has Items?
No. Deletion is blocked for categories that are already in use. Make the category inactive instead so existing references remain valid.
What happens if I select several categories for Delete and one is in use?
The delete operation is rejected rather than partially deleting the selection. Remove the blocked row from the selection or deactivate categories that must be retained.
Can changing an Item Category affect Ecommerce?
Yes where Ecommerce is configured to use Inventory category identity or hierarchy. Review connected catalog setup before significant hierarchy, naming or lifecycle changes.
Can Item Categories be used by Quality or Manufacturing?
Yes where those modules are configured. Category-aware quality inspection assignments and manufacturing setup can reference Item Categories.