What's the purpose of the table sn_cmp_stack_item in CPG?

[Lisa71]

What's the purpose of the table sn_cmp_stack_item? If we want to archive sn_cmp_stack table, do we need to archive the stack item sn_cmp_stack_item table as well? Also the sn_cmp_order table needs archived together in the related record?

[GopalBarde]

1. In ServiceNow, the sn_cmp_stack_item table is used to store the individual items (or components) that are part of a stack in the Cloud Management application.

2. When you archive the sn_cmp_stack table, which stores the stacks themselves, it's generally recommended to also archive the related records in the sn_cmp_stack_item table. This ensures data integrity and consistency, as archiving the stack without its associated items could lead to incomplete or inconsistent data.

[Lisa71]

Thank you for your answer. I know where stack is used, however didn't get what stack item exactly is and how it's used. 

[Dr Atul G- LNG]

@AJ-TechTrek any thoughts here.

[AJ-TechTrek]

Hi @Lisa71 ,

The request of a cloud catalog item will generate a stack, a request and request items that are important in the following steps.

- Stack (sn_cmp_stack): It is the main object generated when a user requests a cloud catalog item and that hosts information on what has been provisioned. The stack will contain all information from the original cloud catalog item and the associated deployed resources (Virtual machines, Network Interface, Disks...). It will contain in a related list all requested items associated to it (the original one from the first provisioning request and the other ones associated to the day2 operations). Each stack belongs to a user and a user group and has a cost field (which is not used by default).

- Request (sc_request):This is the object generated after each catalog item request. It is generally followed by agents to fulfil the user request and respond to some procedures like approvals etc... The request will contain associated requested item also

- Requested item (sc_req_item): The requested item is generated for each item requested by the user. For the objective of this article, the most important thing is that these requested items will host the pricing information coming from the original Cloud Catalog item for each step of the stack lifecycle (provisioning, CPU increase...). These requested items will be part of the Stack

Refer the below article, which may help you.

https://www.servicenow.com/community/itom-articles/servicenow-cloud-provisioning-and-governance-how-...

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

Thanks

AJ

Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/

ServiceNow Community Rising Star 2024