cancel
Showing results for 
Search instead for 
Did you mean: 

Custom Price Value Not Updated in Credit Memo Request w.r.t Billing

HJ45
Newcomer
0 Kudos
158

Hello Everyone,

There is a requirement for an implementation on S/4HANA Public Cloud.

It is to create a credit memo request with reference to a billing, with customized pricing condition types.

The creation of the document is through the interface and manual creation.

A customized pricing condition type, ZUDE, included from the order to the billing.

The value of ‘Net Value 2’, in Euro, is assigned to this condition type.

A customized pricing routine, with the code for value calculation, is assigned to the pricing condition line on the pricing procedure.

When a discount, with condition type DRV1, is added onto the price, the following is observed.

  1. The value of ‘Net Value 2’ is updated accordingly.
  2. The value of ZUDE remains unchanged.

HJ45_5-1736481263398.png

The system assigns condition control ‘E’ (Condition value and basis fixed), as a default value.

HJ45_0-1736480929763.png

The same steps are repeated for the change of standard order, OR.

The value in condition type ZUDE is updated accordingly.

 

HJ45_3-1736481032605.png

The following options were explored for the credit memo request creation without any positive result (setup on Public Cloud).

  1. Item copy control.
    1. Tested manual creation of credit memo request by price update ‘C’ (copy manual price elements and redetermine others). Values are updated accordingly.
    2. Pricing type C is not available in system customizing ‘Pricing Type’ on Public Cloud.

 

  1. Use of BADI PRCG_DOC_ITEM_CONDITION_AMOUNT.
    1. Attempted to update the condition control for ZUDE from ‘E’ to ‘A’, without any success.

 

  1. Tested the same steps with reference billing that has condition type TTX1.
    1. The value of TTX1 is updated accordingly with the added discount, although the condition control value is ‘D’ (Fixed).

 

HJ45_8-1736481784830.png

Best regards,

HJ

 

Accepted Solutions (0)

Answers (1)

Answers (1)

DequanXu
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello,

You may refer to this blog on this topic:

https://community.sap.com/t5/technology-blogs-by-sap/import-credit-memo-requests-introduction/ba-p/1...

When working with credit memo requests and having issues with custom pricing conditions not updating as expected, especially in an SAP S/4HANA Public Cloud environment, there are a few considerations and possible approaches to explore:

1. **Pricing Procedure Configuration**: Ensure that the pricing procedure used in the credit memo request is correctly configured to handle custom condition types like ZUDE. Check if the pricing procedure is correctly assigned and includes your custom condition types and pricing routines.

2. **Condition Control**: The condition control for the custom condition type ZUDE may be causing the issue. You mentioned trying to change it but didn't succeed. Review the configuration of the condition type and verify if any restrictions prevent it from being updated. Condition control setup can impact how certain elements are recalculated or updated.

3. **Copy Control Settings**: The issue might be related to the copy control settings from billing to credit memo request. Review the configuration for item copy control and ensure that the relevant settings allow for proper copying and updating of pricing conditions.

4. **Pricing Type**: You noted that "Pricing Type C" (copy manual price elements and redetermine others) isn't available in the system customizing in the Public Cloud. This limitation might require alternative strategies, like custom logic through available BADIs (Business Add-Ins).

5. **BADI Utilization**: The use of BADI `PRCG_DOC_ITEM_CONDITION_AMOUNT` should be explored further to modify or enhance the behavior of the pricing conditions. Double-check the implementation logic here to ensure it correctly affects the custom condition type ZUDE based on your requirements.

6. **Custom Pricing Routine**: Ensure that the custom pricing routine assigned to ZUDE is working as intended. You might want to debug or log the routine's execution to verify that it is being triggered and calculated correctly.

Best regards,

Dequan Xu