SQL Server administration and T-SQL development, Web Programming with ASP.NET, HTML5 and Javascript, Windows Phone 8 app development, SAP Smartforms and ABAP Programming, Windows 7, Visual Studio and MS Office software SAP ABAP Programming and HANA Database Tutorials
Development resources, articles, tutorials, code samples and tools and downloads for ASP.Net, SQL Server, R Script, Windows, Windows Phone, AWS, SAP HANA and ABAP, like SAP UI5, Screen Personas, etc.




Install SAP Free


TABL VAKCR: Syntactically incompatible change of existing functionality


Due to Credit Management changes in SD on S/4 HANA, SAP table VAKCR is no more populated with data and ABAP Test Cockpit ATC checks display error for such cases titled as Syntactically incompatible change of existing functionality under Search for usages of simplified objects
Besides ATC error listed in the checks SAP Note 2217124 is also referred for use of ABAP programmers

S/4HANA: Search for usages of simplified objects
Syntactically incompatible change of existing functionality
(TABL VAKCR, see Note(s): 0002217124)
S/4 HANA: Credit Management Changes in SD

ATC error for VAKCR table Syntactically incompatible change of existing functionality

This types of ATC errors cannot be set as hidden by using a pragma or pseudo-comment in ABAP codes.

When I checked the ABAP table VAKCR (Sales Index: Orders in Credit Management), I see that although the table exists in ABAP Dictionary it is not populated with data any more.
So I download SAP Note 0002217124 and realized that there is an ABAP program named VAKCR_REBUILD.
Instead of running the report, because it caused dumps on my SAP system I thought it will be better to implement the ABAP codes within the program.

I detect that following ABAP codes can be used instead of using VAKCR table in SAP

SELECT * FROM vbak
WHERE
gbstk IN ('A', 'B') AND
cmgst IN ('B', 'D').

GBSTK field is for Overall Processing Status of Document
Possible values for GBSTK is as follows where we deal with A and B for VAKCR data:
Not Relevant
A Not yet processed
B Partially processed
C Completely processed

CMGST field is for Overall Status of Credit Checks
And data element's value range can be listed as follows where we look for B and D status items:
Credit check was not executed/Status not set
A Credit check was executed, document OK
B Credit check was executed, document not OK
C Credit check was executed, document not OK, partial release
D Document released by credit representative

And it seems that the SAP view V_VMVAH "Blocked/Released orders (credit control)" can be used to fetch similar data like VAKCR table provides

SELECT * FROM v_vmvah

Maybe using V_VMVAH view can be easier for replacing SAP VAKCR table data






SAP Tutorials

SAP Tutorial

SAP Forums

SAP Tools

SAP Transaction Codes Table


Meetup Sunumu 1 meetup






Copyright © 2004 - 2020 Eralper YILMAZ. All rights reserved.
Community Server by Telligent Systems