Solution Documentation: Libraries & Process Model

What is a composite interface, and what does it describe?

What is the Business Processes area, and what's the guidance on end-to-end versus modular flows?

What is the Alerting Library for, and why build alert objects in the Business Process area rather than in the library?

How is a modular process scoped and structured?

What does the Development Library hold, and how does its content differ from the Executable Library?

What does the Configuration Library centralize, and what's the best-practice folder structure?

What is the Interface Library, and how are interfaces refined in 7.2?

What does the Executable Library hold, and how is it organized?

What's the difference between a process step 'original' and a 'reference' in the Process Step Library?

What characterizes an end-to-end process, and why is it both the highest-value and the hardest to align?

What does the Analytics Library provide, and where does the actual analysis happen?

To avoid double-maintenance, what documentation goes on a process step original versus on a reference?

What are SOLDOC's two main folders, and what five libraries make up the reusable side?

How does SAP Solution Documentation 7.2 represent the system landscape, and what three levels does it cover?