Enterprise Resource Planning Blogs by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
cancel
Showing results for 
Search instead for 
Did you mean: 
0 Kudos
In the world of business, efficiency is key. But what happens when the tools you rely on become sources of frustration? That's where we step in. In this blog, we're diving into the nitty-gritty of two essential transactions, WB2R_SV and WB2R_SC. These may sound like a bunch of letters and numbers, but they play a crucial role in Supplier / Customer Contract Settlement. We won't bore you with complicated business jargon, but instead, we'll tackle the common issues and problems users face when working with these transactions.




List of Issues Aimed to Solve with this Blog





    • Shortdump: DBSQL_DUPLICATE_KEY_ERROR

    • Shortdump: EXPORT_TOO_MUCH_DATA

    • Shortdump: CONVT_NO_NUMBER

    • Shortdump: SAPSQL_PARSE_ERROR

    • Shortdump: DBSQL_STMNT_TOO_LARGE

    • Shortdump: TSV_TNEW_PAGE_ALLOC_FAILED

    • Performance

    • Error FF765 - Transaction key does not exist

    • Error WAB205 - Cannot save; diff. attribute in &1 and altern. &2

    • Error WAB208 - No reference information for reference document category &1 passed.

    • Error WB2R111 - Internal error: Not all partial settlements could be distributed

    • Error WS118 - Document &1 has status &2 and is complete.

    • Field POSNR is wrong in tables WBRP and/or WB2_D_BVDETAIL








DBSQL_DUPLICATE_KEY_ERROR


Program SAPLWB2_REBATES_POST


Please review the content of article number 3394884.







EXPORT_TOO_MUCH_DATA


Please review the content of article number 3394978.







CONVT_NO_NUMBER


Make sure you have implemented the provided notes:





SAPSQL_PARSE_ERROR


Program CL_WB2_REBATE_SETTLEMENT


Please review the content of article number 3394962.



Program SAPLV61Z


Please review the content of article number 2682781.







DBSQL_STMNT_TOO_LARGE


Program CL_WB2_REBATE_SETTLEMENT======CP


Please review the content of article number 3403729.







TSV_TNEW_PAGE_ALLOC_FAILED


Please review the content of article number 3403770.







Performance


Please review the content of article number 3405529.




Error FF765


In the pricing schema used, check what is the tax condition type. Then review if an accounting key was maintained. If not maintained, the system cannot pass the data to accounting.

Also, read the article 2535889.




Error WAB205


The error is usually caused by missing "Document Schema Group" in table TMKV.

To fix it, follow the instructions described in article 2893326.




Error WB2R111


Please review the content of article number 3405475.




Error WS118


You received this error message because you executed the report in a check run. In this case, the system couldn't give a number for the settlement. Please execute the report in the live run to avoid this error message.




Field POSNR


Please review the content of article number 3405508.
3 Comments
aditya_palekar
Advisor
Advisor
0 Kudos
Hello Rodrigo,

The settlement run table grows over period of time. Is there a note/documentation that describes the archiving/deletion of data which can be performed?

Regards,
Aditya
0 Kudos
Hi Aditya,

You can use the archive object WZR for settlement documents. See also the following link from SAP Help:

https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/21e3d34f140b454c9c5c6f9e16fd9394/b98ee7c98fb24ad587b...

Regards,

Rodrigo
aditya_palekar
Advisor
Advisor
0 Kudos
Thank you Rodrigo!