[Issue] Fixed catalog rule price processing when only website-scoped prices are used.

[m2-assistant]

This issue is automatically created based on existing pull request: #40358: Fixed catalog rule price processing when only website-scoped prices are used.

---

Description (*)

This Pull Request resolves an issue in the SQL query generated by Model/Indexer/RuleProductsSelectBuilder.php during catalog price rule indexing. The issue specifically occurs in environments where product prices are managed exclusively at the Website scope, meaning no price entries exist for store_id = 0 (Global/Default Store View) in the database.

The changes include:

1. Removal of Unnecessary Join: The explicit JOIN to the default price table (pp_default with store_id = 0) has been removed from the product selection query. This join was causing issues when the default price entries were absent.
2. Default Value Handling: The logic for the default_price column is updated to use SQL's COALESCE or IFNULL equivalent to return 0 if the website-specific price ($tableAlias.value) is not found. This prevents SQL errors related to missing joined records.

This ensures the price rule indexing mechanism correctly handles scenarios where price attribute scope is set to "Website" and the global default price is non-existent.

Related Pull Requests

...

Fixed Issues (if relevant)

1. Fixes magento/magento2#<issue_number>
   ...

Manual testing scenarios (*)

1. Data Preparation:
   • Ensure the 'Price' attribute scope is set to "Website".
   • Create a new product and set its price only at the Website scope (e.g., $10.00 for Website A).
   • Verify that no price entry exists for this product with store_id = 0 in the catalog_product_entity_decimal table.
2. Verify Issue Reproduction (Before Fix):
   • Attempt to run a full catalog rule reindex: bin/magento indexer:reindex catalogrule_rule.
   • Expected Result: Indexing fails or produces incorrect data due to the missing join result.
3. Verify Fix:
   • Apply the changes from this PR.
   • Run the catalog rule price reindex again: bin/magento indexer:reindex catalogrule_rule.
   • Expected Result: Indexing completes successfully without errors.

Questions or comments

Given the price attribute scope is "Website", the change sets default_price to 0 when no website-specific price is found. Please confirm if setting this value to 0 (instead of attempting to fetch a Global/Default Store value) is acceptable within the indexing context.

Contribution checklist (*)

 - [x] Pull request has a meaningful description of its purpose
 - [x] All commits are accompanied by meaningful commit messages
 - [ ] All new or changed code is covered with unit/integration tests (if applicable)
 - [ ] README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
 - [x] All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.