Requirements Management

A teammate says Requirements Management's SMBR and SMIR transactions are why it 'feels like ChaRM.' Why do they resemble ChaRM, and what does that lineage warn you about when you build customer versions?

A change document tied to a requirement went live in production, but the linked business and IT requirements still show open. What is the most likely root cause, and why is closing them by hand the wrong fix?

Business users create requirements two ways — the Web Client UI form and the Fiori 'My Business Requirements' tile. A user worries the Fiori ones are 'second-class' and need re-entry. Does the entry point change anything downstream?

In final acceptance the solution architect sets the IT requirement to 'implemented'. A new admin treats this as a cosmetic flag. What does it actually trigger, and why is flipping it early costly?

A business manager hits 'Approve' on a business requirement. A junior asks who then creates the matching IT requirement — and what one upstream gotcha can block the requirement from ever reaching approval?

Linking a requirement to a branch's business processes in Solution Documentation looks like busywork. What concrete decision does that link enable, and when does skipping it hurt most?

You built customer Y-versions of the business and IT requirement transaction types, but your custom business requirement keeps generating the STANDARD IT requirement, not yours. What did the copy tool fail to carry over?

A requirement has cleared business validation. Who routes it to the solution architect AND owns awareness of Release Management dependencies — and what distinguishes that role from the business manager?

How does the Release Management link constrain WHEN an accepted IT requirement is delivered, and what must the solution architect do before the business manager can sign off?

Your scenario doesn't use the IT requirement's Checklist block, but the 'each step must be Completed' warning keeps blocking the Submitted for Approval status. What customizing change removes the warning?

A colleague who learned Solution Manager pre-7.2 still wants to log new functional requirements as RfCs 'because that's the change object.' Why was the RfC the wrong tool, and what changed in 7.2 that makes that habit obsolete?