0% found this document useful (0 votes)
16 views3 pages

Real Time Errors CCMS LOAB

The document outlines various issues and fixes related to rebate accruals and commission calculations in CCS/CCM and LO-AB systems. Key problems include incorrect rebate postings, missing condition records, and failures in settlement processes, with specific solutions provided for each issue. The document emphasizes the importance of proper configuration, user training, and validation checks to ensure accurate financial postings and calculations.

Uploaded by

shreetesh222
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
16 views3 pages

Real Time Errors CCMS LOAB

The document outlines various issues and fixes related to rebate accruals and commission calculations in CCS/CCM and LO-AB systems. Key problems include incorrect rebate postings, missing condition records, and failures in settlement processes, with specific solutions provided for each issue. The document emphasizes the importance of proper configuration, user training, and validation checks to ensure accurate financial postings and calculations.

Uploaded by

shreetesh222
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

In CCS/CCM, a common issue is incorrect rebate accruals (e.g.

, $250 for 500


lemons at 5% with ZSCB not posting to 200100). This happened because
the condition type ZSB1 wasn’t linked to the pricing procedure ZMM001 in
SPRO > Materials Management > Purchasing > Conditions > Define
Calculation Schema. I fixed it by adding ZSB1 to ZMM001, ensuring GR-
based accruals in MIGO, and verifying postings in FBL3N. Another CCS/CCM
issue was a vendor-funded rebate (ZPROM, $100 for a sign) not settling in
WLF1 due to missing promotion proof. I updated the contract 1000003 in
WCCR with a custom field for proof, used BADI BADI_CCS_CONTRACT to
enforce verification, and tested settlement in WLF1. In LO-AB, commissions
(e.g., 4% for $50,000 sales) weren’t calculated in WB2R_SV because the
agent wasn’t set in the sales order’s “Header Partners” (VA01). I fixed it by
training users to enter the agent (AG role) and added a check in user exit
EXIT_SAPMV45A_004 to validate. Another LO-AB issue was iDocs for
commission statements (ZCOM via WE20) failing due to incorrect partner
profiles. I corrected the INVOIC02 settings in WE20, tested in WE19, and
monitored in WE02

1. CCS/CCM: Incorrect Rebate Accruals - The system doesn’t post the


right rebate (e.g., $250 for ZSB1 not in 200100). Cause: Condition
type ZSB1 or ZFX1 not in pricing procedure ZMM001 in SPRO >
Materials Management > Purchasing > Conditions > Define
Calculation Schema. Fix: Add ZSB1/ZFX1 to ZMM001, ensure GR-
based accruals in MIGO, and verify in FBL3N. Analogy: Like fixing my
cashier’s mistake in noting a bulk discount.

2. CCS/CCM: Rebate Not Triggering in MIGO - Rebates (e.g., $50 for


ZFIX) don’t calculate during goods receipt. Cause: Missing condition
records in MEK1 for ZSB1/ZFX1. Fix: Create condition records in
MEK1 for supplier and contract (1000001, 1000002), test in MIGO,
and check accruals in FBL3N. Analogy: Like ensuring my cashier has
the discount coupon list.

3. CCS/CCM: Settlement Fails in WLF1 - Credit memo (e.g., $100 for


ZPROM) not created. Cause: Missing promotion proof or incorrect
contract status in WCCR. Fix: Update contract 1000003 in WCCR with
proof (e.g., sign photo) using BADI BADI_CCS_CONTRACT, ensure
contract is released, and test settlement in WLF1. Analogy: Like
confirming I put up the ad sign before getting paid.

4. CCS/CCM: Wrong FI Postings - Accruals post to incorrect accounts


(not 200100/400200). Cause: Wrong G/L account mapping in SPRO >
Sales and Distribution > Billing > Revenue Account
Determination. Fix: Map ZSB1, ZFX1, ZPR1 to 200100 (accrual)
and 400200 (settlement), verify in FB03. Analogy: Like fixing my
accountant’s mistake in putting rebate money in the wrong jar.

5. CCS/CCM: iDoc Fails for Credit Memo - Supplier doesn’t receive


credit memo via iDoc (WE20). Cause: Incorrect partner profile or
output type ZOUT settings. Fix: Update WE20 with iDoc type
INVOIC02, message type INVOIC, and supplier (LI), set condition
records in VV31 for ZOUT, test in WE19, and monitor in WE02.
Analogy: Like fixing a mail error so my supplier gets the rebate bill.

6. CCS/CCM: Scales Not Applied Correctly - Wrong rebate percentage


(e.g., 2% instead of 5% for 500 lemons). Cause: Incorrect scale setup in
WCCR for ZSB1. Fix: Update contract 1000001 in WCCR with correct
scales (2% at 100, 5% at 500), debug in SE80 using user exit
EXIT_SAPLM61O_001, and test in MIGO. Analogy: Like correcting my
discount chart for bulk buys.

7. CCS/CCM: Performance Issues in WLF1 - Settlement takes too long


for large contracts. Cause: Large data volume in /CCS/ACCRUALS. Fix:
Add indexes to /CCS/CONTRACT and /CCS/ACCRUALS in SE11,
optimize program in SE38, and check performance in STAD. Analogy:
Like speeding up my cashier’s calculator for big orders.

8. LO-AB: Commission Not Calculated in WB2R_SV - No commission


(e.g., $2,000 for $50,000 sales) calculated. Cause: Agent not specified
in sales order’s “Header Partners” (VA01). Fix: Train users to enter
agent (AG role) in VA01, add validation in user exit
EXIT_SAPMV45A_004, and verify sales in WB2R_S_BUS_VL.
Analogy: Like ensuring my agent’s name is on the sales receipt.

9. LO-AB: Incorrect Sales Volume in WB2R_S_BUS_VL - Sales


($50,000) not linked to contract 1000001. Cause: Missing sales
organization link in WCOCO. Gem*: Update contract 1000001 in
WCOCO with correct sales organization, test sales order in VA01, and
verify in WB2R_S_BUS_VL. Analogy: Like fixing a mix-up in tracking
who sold which lemonade.

10. LO-AB: iDoc Output Failure for Commission Statement -


Agent doesn’t receive commission statement (ZCOM). Cause: Incorrect
partner profile in WE20 or condition records in VV31. Fix: Update
WE20 with INVOIC02, INVOIC, and agent (KU, AG), set ZCOM
records in VV31 for sales organization, test in WE19, and check in
WE02. Analogy: Like correcting a wrong address on my agent’s
payment letter.

11. LO-AB: Wrong Commission Percentage - Commission


calculated at 1% instead of 4% for $50,000. Cause: Incorrect condition
scales in RCS1 (WCOCO). Fix: Update contract 1000001 in WCOCO
with correct tiers (1% at $10,000, 4% at $50,000), test in WB2R_SV,
and verify in FB03. Analogy: Like fixing my agent’s pay scale for big
sales.

12. LO-AB: Settlement Posting Errors - Commission not posted to


agent’s account in WB2R_SV. Cause: Incorrect account determination
in SPRO > Logistics > Agency Business > Billing > Revenue
Account Determination. Fix: Map commission condition to correct
G/L accounts (e.g., expense account 500100), verify in FB03. Analogy:
Like ensuring my accountant pays the agent from the right fund.

13. LO-AB: Output Form Missing Data - Commission statement


(ZCOM) lacks sales details. Cause: Form ZCOM_FORM logic error in
SE71. Fix: Enhance form in SE71 to pull data from WBRK and VBRK
using user exit EXIT_SAPLWLF2_002, test in WB2R_SV. Analogy: Like
fixing my agent’s report card to show all sales.

14. CCS/CCM & LO-AB: Integration Failure with FI/CO -


Rebates/commissions not posting to 200100/400200 or cost centers.
Cause: Missing account assignment in SPRO > Sales and
Distribution > Billing > Revenue Account Determination. Fix:
Assign ZSB1, ZFX1, ZPR1, and commission conditions to 200100,
400200, and cost center CC1000, verify in FBL3N. Analogy: Like
ensuring my accountant tracks all discounts and payments correctly.

15. CCS/CCM & LO-AB: User Errors in Data Entry - Wrong


supplier or agent entered in WCCR/WCOCO. Cause: Lack of input
validation. Fix: Implement checks in user exits (EXIT_SAPLWLF2_002
for CCS, EXIT_SAPMV45A_004 for LO-AB), train users, and test in
MIGO/VA01. Analogy: Like teaching my staff to double-check
customer names.

You might also like