Symptom
- The expected custom pricing procedure (for example, Custom Pricing Procedure A) is not determined when creating a purchase contract.
- The system determines a different pricing procedure (for example, Standard Pricing Procedure) instead of the expected custom pricing procedure.
- Custom condition types associated with the expected pricing procedure are not available in the purchase contract.
- No error message is displayed during purchase contract creation.
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Create a purchase contract.
- Ensure a custom pricing procedure is configured for the purchasing document.
- Observe that the system determines a different pricing procedure instead of the expected custom pricing procedure.
Resolution
- Create the required custom purchasing condition type(s).
- Create or use a custom purchasing calculation schema (pricing procedure) and include the custom condition type(s).
- Assign the custom calculation schema to the relevant determination entry (supplier schema group + purchasing organization schema group) in the configuration activity "Set Schema Determination for Purchasing."
- Ensure the supplier and purchasing organization master data use the intended schema groups associated with the custom schema.
- Create a new purchase contract and verify that the custom schema is determined and the custom condition types are available.
Keywords
purchase contract, pricing procedure, calculation schema, schema determination, condition type, custom condition type, purchasing pricing, condition technique, not determined, defaults to different schema, contract conditions, z schema, axx001, z33001, s/4hana cloud public edition , KBA , MM-PUR-GF-PR-2CL , Price Determination (Public Cloud) , Problem
Product
SAP S/4HANA Cloud Public Edition all versions
SAP Knowledge Base Article - Public