Skip to main content

Incorrect Determination of Manual Credit Limit Changes Due to Timestamp Differences

The system incorrectly classifies automatically triggered credit limit changes as manual changes due to small timestamp deviations between FS² Credit Management and FD32.

S
Written by Strutzke, Marcel

Product Area

FS² CCC

Problem

In certain scenarios, the system flags a credit limit change as manual, although it was executed automatically by the FS² Credit Management (CM) component.

Why does this happen?

  • The system compares:

    • The timestamp from the FS² CM tables (planned update)

    • The timestamp of the FD32 posting (actual update)

  • If the timestamps are not identical, the system assumes a manual change.

Technical Limitation (Previous Logic)

  • Only hours and minutes were compared.

  • This leads to false positives, for example:

    • FS² CM update: 10:15:59

    • FD32 posting: 10:16:05

    • Result: incorrectly identified as manual change

Solution Steps

You can implement a customer-specific pre-correction to avoid incorrect classifications.

Recommended Approach

  1. Calculate the timestamp difference in seconds

    • Compare:

      • FS² CM timestamp

      • FD32 timestamp

  1. Introduce a tolerance threshold

    • Allow a difference of up to 30 seconds

  1. Adjust the logic

    • If the difference is ≤ 30 seconds, treat the change as automatic

    • If the difference is > 30 seconds, treat the change as manual

Logic Adjustment (ABAP Concept)

Expected Result

  • Eliminates false manual classifications

  • Improves accuracy of credit management tracking

Known Limitations

  • This solution is not part of the standard product.

  • As of December 5, 2025, there is:

    • No standard SAP correction

    • No Jira ticket for product inclusion

  • Implementation must be done as a custom enhancement

Did this answer your question?