on 2024 Oct 08 9:58 AM
Dear Experts ,
Hope every one doing well as usual...!
One of our clients which we are in the process of implementation the latest version of SAP Customer Checkout (FP20) having the requirement to have service charge on the sales receipt . So we have used the charge_element_config.json file as instructed and it has done the job we required . But the issue is the percentage we had given in the file will be calculate not only for sales receipts but also all other receipt types as well . So it's really appreciated if some one can kindly advice how we can include only sales receipts for this service charge calculation .
[{
"id": "SC",
"name": "Service Charge",
"sequence": 1,
"rules": [{
"name": "SC_RULE",
"sequence": 1,
"baseCalculationValue": "PAYMENT_NET_AMOUNT",
"factor": 0.1,
"summand": null,
"lowerLimit": null,
"limit": null,
"inclusions": [{
"@type":"TypeBased",
"conditionType": "SALES_ITEM_TYPE_CODE",
"ids": [
"13"
]}
]}
],
"chargeElementType": "SERVICE_CHARGE",
"journalAccount": "SC",
"taxRateTypeCode": "VAT0"
}]
Thanks in advance
Best Regards,
Tharindu.
Request clarification before answering.
Hi Tharindu,
The service charge configuration provided in the tools folder currently considers sales items of type 1 (normal article), 3 (special article), and 13 (expenses). This setup should fulfill the requirements you are looking for.
The rules check each sales item individually and not the receipt type as a whole. This is not an issue; for example, in a "Cash-In" receipt, the sales item used will be of type code 4 (CASH_IN_OUT) and therefore not included in the considerations. Please refer to the attached picture where I have listed all the supported sales item type codes.
In your example, you removed the most important type code 1 and the less important type code 3. I recommend you at least revert type code 1 to ensure proper functionality.
If I misunderstood your situation, please provide a concrete example of what issues you are encountering on your site.
Best regards,
Martin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Tharindu, to avoid having charges on returns, just add the following exclude:
"exclusions": [{
"@type":"AmountBased",
"compareValueField": "GROSS_AMOUNT",
"compareOperator": "LESS",
"value": 0,
"onSalesItemLevel": true
}]
User | Count |
---|---|
18 | |
10 | |
9 | |
9 | |
7 | |
6 | |
6 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.