Symptom
When creating a supplier invoice with reference to the PO, the custom assessable value condition is not populated automatically.
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Open MIRO and start supplier invoice creation.
- Enter a reference PO number.
- Click on simulate or post.
- Observe that the standard condition JCDB is automatically copied from the PO, but assessable value is not populated on entry.
Cause
Cause 1:Manual indicator selected in pricing procedure step. Conditions marked as manual will not be automatically determined by the pricing, nor will their values be copied from purchasing documents.
Cause 2: Incorrect condition category in condition type master data. The custom condition type does not have Condition Category = B (Delivery costs). Only conditions classified as delivery costs are recognized as planned delivery costs and included in the MIRO.
Resolution
Resolution 1: Deselect Manual indicator in pricing procedure
- Open Configuration Activity SSCUI ID 101934 Classify Condition Types.
- Locate the Condition Type for your custom assessable value condition.
- Deselect the Manual checkbox for this Condition.
- Save and publish the configuration change.
Resolution 2: Align condition type master data attributes
- Open Configuration Activity SSCUI ID 101934 Classify Condition Types.
- Compare your custom condition with standard condition JCDB, and ensure the following attributes are identical:
- Condition Category: Set to B (Delivery costs)
- Manual Entries: Set to Not to process manually
Keywords
MIRO, assessable value, condition type, pricing procedure, India GST, IMPCUSTAP, supplier invoice, PO conditions, automatic derivation, copy from PO, , KBA , FI-LOC-SD-IN , India (aka XX-CSC-IN-SD) , Problem
SAP Knowledge Base Article - Public