addCategory
- Description
- This transaction adds a category to a category hierarchy. Categories are entities that define the product categories into which products can be categorized.
- Web Services
- Operation name: addCategory
- Example
- Add an Investments category to the product hierarchy of a financial services organization.
- Usage information
- The addCategory transaction cannot be used to add another root
category. Root categories can only be added as part of a coarse-grained addCategoryHierarchy transaction.
CategoryCode is an optional input. If it is provided, it must be unique within the category hierarchy.
If a category is designated as a Leaf node by setting the LeafIndicator element to Y, then it cannot be a parent category to other subcategories.
Products can only be directly classified into categories in which the AssociationIndicator element is set to Y.
You can use this transaction to add localized content for the CategoryName and CategoryDescription elements.
This transaction can be used as a coarse-grained transaction to add category relationships, category administrative system keys, and category entity spec uses. When using addCategory as a coarse-grained transaction, the following transactions may also apply:The following transactions relate to the categorization of products into categories: - Preconditions
- A category hierarchy must exist.
- Mandatory input
-
- CategoryName
- CategoryHierarchyId
- Inquiry levels
- Not applicable
- Filter values
- Not applicable
- Transaction behavior
The StartDate of the category must be equal to or greater than the StartDate of the category hierarchy to which it belongs. If the StartDate is not supplied, the current system date is used by default.
The EndDate of the category must be equal to or less than EndDate the category hierarchy to which it belongs.
If the RootIndicator is not supplied, the default value of N is used.
If the LeafIndicator is not supplied, the default value of N is used.
If the AssociationIndicator is not supplied, the default value of Y is used.
- Request message
<TCRMTxType> addCategory
<TCRMTxObject> CategoryBObj
<TCRMObject> CategoryBObj
with optional business objects:- Response objects
- CategoryBObjwith optional business objects:
- Special note
- Not applicable