Prepare files in Build
Build prepares draft implementation files for review. It keeps the requirement, generation result and available source context together. This guide follows the current V2 interface; its older Studio URL remains available for bookmarks.
1 · Bring a requirement
Section titled “1 · Bring a requirement”Select your project and open Build, or continue from an answer’s Build action. When continuing an investigation, review the original question and available source context alongside the editable requirement.
Describe the work precisely. For example:
Show purchasing spend by plant and purchasing organization, with drill-down to purchase-order items. Preserve the source currency and enforce purchasing-organization access.
Use project files when they help define the requirement. Review their versions and any source limitations before submitting.
2 · Follow the run
Section titled “2 · Follow the run”Submit the requirement using the composer. Read the reported progress and any limitations. If the run fails or its stream is interrupted, use the recovery controls and check the requirement before retrying. Do not treat partial output as a successfully completed bundle.
Generation depends on the services available to your project. The interface does not guarantee that every SAP task can be implemented automatically.
3 · Read the actual files
Section titled “3 · Read the actual files”When the run completes, Review your draft presents the returned files and review information. Select a file to inspect its text. Copy or download the files you need; SAP identifiers and whitespace are preserved.
The reader is for inspection. It does not edit a generated file in place, execute it or install it in an SAP system. Review source support separately from estimates, sequencing and risks.
4 · Save and reopen
Section titled “4 · Save and reopen”Use Save change to preserve the result in Changes. Open the saved change’s Files tab to read the bundle again. Available originating inquiry and source references remain attached to the saved work.
A failed save is not confirmation that the change exists. Follow the error’s recovery action and verify the saved change before leaving the work.
5 · Validate in your environment
Section titled “5 · Validate in your environment”Review the draft against your SAP release, data model, authorization requirements and acceptance criteria. Development-system checks and transport remain part of your delivery process. An Atlas review or file download does not replace them.