Prepare and track a change
Changes is the project register for WRICEF and configuration work. Keep the business requirement, scope and acceptance criteria together with the delivery material. This guide follows the current V2 interface; the URL is retained for older bookmarks that called a change a case.
1 · Open the register
Section titled “1 · Open the register”Choose the project in the header and open Changes. Search by name, process or module, or narrow the register by work type and status. Open an existing row to resume work.
An empty register is an invitation to define the work, not evidence that the project has passed a review.
2 · Define the business requirement
Section titled “2 · Define the business requirement”Choose New change. The full-page editor keeps the requirement, SAP scope, acceptance criteria and files in one place. Give the change a specific name and describe the outcome you need. For example:
Add project costs alongside open purchase orders, with access limited to the purchasing organizations the user may view.
Choose the appropriate work type and record the relevant system and process context. Define what a reviewer must be able to check. Save using Create change; if saving fails, retain your draft and use the displayed recovery action.
3 · Review the saved brief
Section titled “3 · Review the saved brief”Open the Brief tab to read the saved requirement and scope. Use the editing action to update the brief. The other tabs expose delivery, files, review, evidence and activity for this change; open the information you need rather than treating tabs as mandatory stages.
Assess change requests an assessment. Its result and supporting material require review; an assessment is not an approval or a transport into SAP.
4 · Prepare and inspect delivery files
Section titled “4 · Prepare and inspect delivery files”Use Build when you need generated implementation material, then Save change to preserve the returned bundle. In a saved change, Files presents the available artifacts. Inspect the actual file contents before copying or downloading them.
Follow an originating investigation link when one is available for this project. Source references retain their versioned context; a saved bundle does not silently become a new review of changed source files.
5 · Return to the work
Section titled “5 · Return to the work”Reopen the change from the register. Review its brief, saved files and available evidence before making a delivery decision. Perform development, testing and transport in the appropriate SAP environment; downloading a draft does not execute it there.