Describe your experience configuring SAP SD and Vistex, and how you use those configurations to support business requirements.
For this SQL exercise, assess which active SAP SD requirements have valid Vistex configuration coverage as of June 30, 2025. Include requirements due by that date, excluding closed requirements and configuration records that are inactive, unapproved, or outside the effective period.
requirement_id, requirement_name, sales_org, priority, configuration_status, and configuration_count.Configured, Needs validation, or No configuration.required_by ascending, then requirement_id ascending.| Column | Type | Description |
|---|---|---|
| requirement_idPK | INT | Unique SAP SD business requirement identifier |
| requirement_name | VARCHAR(120) | Business requirement name |
| sales_org | VARCHAR(20) | SAP sales organization |
| priority | VARCHAR(20) | Requirement priority |
| requirement_status | VARCHAR(20) | Current lifecycle status |
| required_by | DATE | Date by which the requirement is needed |
| Column | Type | Description |
|---|---|---|
| config_idPK | INT | Unique Vistex configuration identifier |
| requirement_id | INT | Referenced SAP SD requirement |
| module_name | VARCHAR(50) | Configured Vistex module |
| config_status | VARCHAR(20) | Configuration lifecycle status |
| approval_status | VARCHAR(40) | Business approval status |
| effective_from | DATE | Configuration start date |
| effective_to | DATE | Configuration end date, null means ongoing |