S4 Conversion
S4 Conversion
S4 Conversion
This blog is targeted to ABAP technical team working on S4 HANA conversion projects.
This blog is in continuation with my previous blogs on handling of Material Field Length Extension and Amount
Field Length Extension issues during S/4 HANA conversion.
How to handle Amount Field Length Extension scenarios in S/4 HANA conversion
How to handle Material Field Length Extension scenarios in S/4 HANA conversion
In this blog I am going to elaborate how SELECT statements on various simplified tables can be changed at the
time of code remediation activity.
Lets discuss some of the most prominent cases of SELECT scenarios in this blog. I will keep on adding new cases in
my upcoming blogs.
1. SLECT on BSEG.
As per SAP note 2431747 BSEG will not contain the entries of open items . Some postings marked as BKPF-
BSTAT will not be posted in BSEG but in ACDOCA table. Hence the SELECT statements on BSEG table need to
be reviewed and changed.
SELECT bukrs
belnr
gjahr
buzei
INTO TABLE it_bseg
FROM bseg
FOR ALL ENTRIES IN it_bkpf
WHERE bukrs = it_bkpf-bukrs
AND belnr = it_bkpf-belnr
AND gjahr = it_bkpf-gjahr .
Here SELECT on BSEG table can be replaced by API call as below. But before replacing the BSEG Select
statement with API it is recommended to analyze if using of API will impact the functionality since API selects the
data only from BSEG table and some entries are not updated in BSEG but in ACDOCA table.
ENDIF.
SAP note 2198647 provides the details about data model changes in SD area. In below SELECT statement the
document status is being fetched from the table VBUK, this query would work in ECC environment but not in S/4
HANA. In S/4 HANA the document status fields have been removed from the vbuk tables and moved to respective
header table of the document like LIKP, VBAK.
Example 1.
Example 2
For selecting the multiple column data VBUK or VBUP tables following APIs can be used.
SD_VBUK_READ_FROM_DOC
SD_VBUP_READ_FROM_DOC
SD_VBUP_READ_FROM_DOC_MULTI
SD_VBUK_READ_FROM_DOC_MULTI
According to note 2431747 , customizing tables T881, T881T and T881G are made obsolete in S/4 HANA. Hence
the SELECT statements on these tables have to be replaced by API calls as shown in the example below.
This SELECT statement can be corrected by using the class method cl_fins_acdoc_util=>get_t881_emu
cl_fins_acdoc_util=>get_t881_emu(
EXPORTING
iv_rldnr = '90' " Ledger
IMPORTING
es_t881 = DATA(EWA_finsdoc2) " Ledger Master
EXCEPTIONS
not_found = 1
OTHERS = 2 ).
IF sy-subrc = 0.
v_tabela = ewa_finsdoc2-tab .
ENDIF.
According to note 2220005, KONV table has been replaces by PRCD_ELEMENTS table. SELECT on KONV table
can be replaced by API cl_prc_result_factory=>get_instance( )->get_prc_result( ). OR CDS view V_KONV can
also be used in place of KONV table.See the example below.
As per SAP note 2768887 , the where clause in SELECT statements on VBRK and VBRP tables check should have
check for DRAFT field as well to make sure the SELECT will work as before.
If VBRK-DRAFT = space is not added in the where clause , the SELECT statement will return values from FIORI
draft table as well , which in not desired. Since draft values are not posted in the table.
Summary
This blog doesn’t end here since there are many such scenarios which we come across during code remediation
phase. I will keep on adding new blogs for more code remediation scenarios.
Conversion of Credit Management to SAP
S/4HANA
14 37 36,479
In this blog, I tried to provide a high-level perspective of steps involved in the Conversion of Credit Management
(FI-AR-CR) to SAP Credit management in SAP S/4HANA. And will not cover the details of SAP Credit
Management related configuration.
To keep it easy in our understanding, SAP Credit Management may be viewed more of a business governance
feature in relation to Checks and Controls relating to Credit facility extended to Customers, includes various other
features. Effective use of SAP Credit Management results in improved Operational Efficiencies in the areas of
Receivables/Collections and better Working Capital Management, visible impact on DSO.
SAP Credit Management is one of the components of SAP Financial Supply Chain Management in SAP S/4HANA.
To keep it simple in understanding, SAP Credit Management, can be classified into following:
1. SAP Credit Management is a part of SAP Financial Supply Chain Management (FSCM) Module.
2. Business Partner Concept in SAP S/4HANA and SAP Credit Management as a BP Role.
3. Technical and functional – requirements and configuration that would be required for an effective use of SAP
Credit Management.
4. Use of Basic SAP Credit Management do not require additional licence and is a part of SAP S/4HANA System.
I tried to keep this blog simple and also covered some high-level technical aspects for functional consultants. This
blog will not cover the use of Business Partner in Financial Services.
I tried to arrange this blog in a logical sequence. In some places it may look confusing – as such the references
In SAP S/4HANA, Credit Management (FI-AR-CR) is not available, functional equivalent is SAP Credit
Management (FIN-FSCM-CR)
No 1:1 correlation with Old functionality
SAP FI-AR-CR is a purely internal FI credit management application, whereas SAP Credit Management
(FIN-FSCM-CR) provides with a comprehensive, integrated, and cross-system form of credit management.
Several field names used in classic credit management no longer available in SAP S/4HANA
Use of Transaction Code BP or UKM_BP for SAP Credit Management Customer Master Data. Tcode BP,
role: SAP Credit Management
Credit Management Master Data stored in tables: UKMBP_CMS & UKMBP_CMS_SGM
UKM_CASE to process sales documents (eg: releasing blocked sales orders)
Create a relationship with from Credit Analysts to Customers
Documented Credit Decision
Risk category -> Risk class maintained for the whole business partner (not per customer & credit control
area), as the probability of a credit default of your customer does depend on the characteristics of your
customer and not your internal organizational structures.
Maintenance of customer master data in business partner transaction
The credit checks carried out for a customer depend on the assigned check rule in the business partner
transaction. They do not depend on the risk class (formerly risk category).
Releasing blocked documents via Case Management (documents the blocking reason)
Business value
Higher degree of automation, thanks to automatic calculation of credit scores, risk classes and credit limits
Credit events help the credit analyst to focus on exceptions during daily business
Create a relationship from credit analysts to customers
Process of credit limit requests
Documented credit decisions
Higher / lower account relationship of business partners (adds up exposure of lower accounts on higher
accounts)
Less redundant data (reading FI-data via HANA view)
Following tables are no longer used in SAP FSCM and usages in the custom codes are listed as errors during custom
code check.
Direct Mapping is available for the following KNKA table fields with SAP Credit Management Tables fields:
CRBLB(Blocked) XBLOCKED
There is no change in Business processes because of System Conversion, however, some transactions become
obsolete and are replaced by new transactions.
Some Examples:
FD32 UKM_BP
VMK1 UKM_MY_DCDS
FDK43
VKM5 – Deliveries
Maintenance of Customer Master Data relating to SAP Credit Management is performed using the Tcode BP and
Role SAP Credit Management. or Tcode: UKM_BP. We can see the multiple tabs maintained for “Credit Profile”
and “Credit Segment Data”. Pre-requisite is mentioned as we move forward.
*These topics are supported by technical team – as such we will not discuss in this blog. It is good for functional
consultants to know the activities involved.
B. Functional/Business Customizing:
# Activity Relevance Comments
2 Activating the Business Partner Role for Mandatory BP Credit Master data is the
basis for SAP Credit
Credit Management Management.
I have not provided the steps but captured the requirements in screen shot (Shaped Red)
Tcode: BUPT
3. Tcode: SM30 View: V_TBZJ1C
5. Authorization Objects
02
03
Display master data F_UKM_SGMT 03
Edit and display master data of SAP Credit B_BUPA_RLT with the BP role
Management UKM000
Display and/or delete application logs of SAP S_APPL_LOG with the object names 03
Credit Management and subobjects listed above
06
Display and process documented credit S_SCMG_CAS and other authorization
decisions objects of the Case Management
component
The authorization objects provided above, are for information. Further, the authorization concept also mentioned as
we moved forward in this blog.
We are not discussing about Events and follow-on process in this blog as it will not impact the conversion process. It
could be ongoing process, if need be.
We will restrict the blog in understanding the SAP Credit Management from the Conversion stand point and some
related important concepts – but not the entire Configuration/Process relating to SAP Credit Management. And also,
we will not be discussing about connecting CRM System. We will focus more about SAP ECC Conversion to SAP
If Credit Management (FI-AR-CR) was used on the start release, a migration to SAP Credit Management (FIN-
FSCM-CR) is mandatory. The necessary migration steps must be performed after the technical system conversion to
SAP S/4HANA (SUM run).
(FI-AR-CR) Credit Management to SAP S/4HANA
The check on with Main Credit Segmt ☒ has effects on the credit segments and on the master data of the credit
account. Following information will be defaulted
This step migrates your FI/AR customizing to the new configuration of SAP Credit Management.
Note: As a business partner in FIN-FSCM, the customer has only one risk class for all segments. To ensure that the
correct risk class is migrated, you should have one consistent risk category for the customer in all credit control
areas. To understand this, please the BP screen shots captured in the beginning of the blog.
Please also refer the above information in a tabular sequence in this blog.
Below information is only for understanding the concept – Technical team would help for the same.
The sales representative doesn’t need any authorizations in SAP Credit Management.
The documented credit decision is now created by the workflow user SAP_WFRT. To this user, you must
assign a copy of the business role SAP_FIN_CR_DCD_WF. This business role includes all necessary
authorizations for creating documented credit decisions in SAP Credit Management.
If your SAP Credit Managementis running in a one-system-scenario, the system administrator must assign a
copy of the business role SAP_FIN_CR_DCD_WF to the new workflow user SAP_WFRT.
If your SAP Credit Management is running in a one-system-scenario, the system administrator must assign a
copy of the business role SAP_FIN_CR_DCD_WFto the new workflow user SAP_WFRT.
Please note, user SAP_WFRT to be in place and need to coordinate with Technical team for the same.
Prerequisites
In Customizing, the SAP Business Workflow is set up under the following path:
2. Open the object type CL_UKM_DCD_WF_EVENTand set the Linkage Activated field to active.
Field Setting
Define Credit Analyst Optional This help in approvals of .Please refer the IMG
Group as Business Partner Credit Limit based on documentation for detailed
Group Credit Analysts. information.
Assign Credit Optional The above steps is Please refer the IMG
Representative Group to required for this step documentation for detailed
Credit Analyst Group information.
Check and Define Credit Mandatory This steps helps to identify the
Management Customizing consistency of configuration or
issues if any.
Define Credit Master Data in Business Partner – this can be scheduled to a batch job through fiori app or through
program:
Workflow Settings – to be configured based on the requirements. Some concepts mentioned in this blog.
We need to ensure all the FI related Data migration activities are completed in sequence as per SPRO>Conversion to
SAP S/4HANA, before setting it to complete. As this step is very critical.
Please note, to do the testing after the conversion/data enrichment is done, before taking it to production, just to
ensure things are fine and as usual with enhanced functionality/features.
Thought of providing the screen shot about Documented Credit Decision how it looks.
Little background about the structure of DCD – it uses the Case Management component as the technical basis for
processing the DCD.
Transaction code:
The documented credit decision for the document contains a range of specific attributes, such as the business
partner, the credit segment, the open and checked credit value, the key and status of the blocked SD document, and
information about approval process etc. We can find the change layout option to see further information.
The below screen shot indicates the attributes of – these attributes are a part of the configuration.
To sum up, below is the single chart of the above – may be a ready reckon-er!!.
References:
2700336 – RMCS1US1 and RMCS1US3 userexits during credit release from DCDs in SAP Credit Management
2554785 – Upon opening transactions VKM2/VKM3 in an SAP S/4HANA system either a short dump or an error
message occurs
SAP#1043195
https://help.sap.com/viewer/0bfd0ef8ac604566b03299809b86b10e/1909.001/en-US/
9289b956c1db4023e10000000a44147b.html
Hope this blog provided a high level perspective about conversion activities from FI-AR-CR to FSCM-CM. And
regards
naag