Ansicht
Dokumentation

CRMV_ATP_MSG - Control Iterative Availability Check for Excluded Products

CRMV_ATP_MSG - Control Iterative Availability Check for Excluded Products

BAL Application Log Documentation   ABAP Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

When availability check is carried out in SAP APO, and the system carries out product or location substitution, the situation could arise that the system substitutes a product or location that is not allowed for the customer.

In this case, ATP check is carried out again automatically, this time excluding this product or location.

Products and locations that are not allowed for the customer are entered in listings or in partner/product ranges (PPRs), and are marked as excluded.

If SAP APO substitutes a product or a location that is not allowed for the customer, then the system issues an error message for the sales order item.

In this step you

  • Enter the message class and the message ID of this error message
    You can enter any of the following combinations of message classes and message IDs:
  • CRM_LISTING (001)

  • CRM_PRP_CHECK (500)

  • CRM_PRP_CHECK (501)

  • CRM_PRP_CHECK (502)

  • CRM_PRP_CHECK (503)

  • Specify what must be excluded from the next ATP check, in the (Exclusion) Rule column:
  • A Product

  • C Product and location

  1. In this table you enter a message class and a message ID, for example message class CRM_PRP_CHECK(this message class is used for PPRs), and message ID 500.
In the Rule column, enter A (product).
  1. You create a PPR for business partner ABC and product X. Product Yis marked as an exclusion.
  2. You create a sales transaction for a business partner ABCwith a sales order item with product X.
  3. During ATP check, SAP APO replaces product Xwith product Y. Based on an existing PPR, Product Yis not allowed for the business partner, so the system issues an error message with the above message class and ID.
  4. On the basis of this error message, this table is accessed. Since A (product) is assigned to this message class and ID, ATP check is carried out again in SAP APO, but this time with the information that product Yshould not be taken into consideration.
  5. The ATP check now substitutes product Xwith Z.
  6. If product Z is not allowed for the customer either, then ATP is carried out again, this time with the information that the results may not include products Yor Z.
You can limit the number of iterative ATP checks in the next step.





BAL_S_LOG - Application Log: Log header data   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 3581 Date: 20240523 Time: 174505     sap01-206 ( 47 ms )