This article covers SAP credit management (FIN-FSCM-CR available in FSCM) functionality from SD perspective mainly keeping in mind the difference between the current credit management (FI-AR-CR) that we are using before S4 HANA Vs the SAP credit management (FIN-FSCM-CR) functionality available in S4 HANA. It only talks about the credit management functionality at high level, may be helps as an outset for someone who is looking to know about S4 HANA credit management config and flow.
When it comes to credit management, we all know that transaction OVA8 which drives the credit check, plays an important role. This has all the checks and validations that is required to perform credit check:
But in SAP credit management (FIN-FSCM-CR available in FSCM), this transaction has less settings, due to the fact the checks are now controlled thru different transaction in FSCM. So, in general, SAP credit management transaction OVA8 will act as a control mechanism to activate/deactivate SAP credit management FIN-FSCM-CR, further the checks on the static, dynamic, max doc value etc are all going to be carried out at in different transaction at FSCM.
Below is the current OVA8 screen:
where the check box “SAP credit management” activates a BADI (BADI_SD_CM) which has 2 methods one for sale order and the other for delivery:
Order: FSCM_CREDIT_CHECK_ORDER
Delivery: FSCM_CREDIT_CHECK_DELVRY
This BADI carries the data to the FSCM credit management during order creation/delivery, thus the checks defined in the FSCM credit management will become effective. So, the OVA8 transaction is now going to act as a trigger point to carry out SAP credit management (FIN-FSCM-CR).
Credit Segment:
Apart from the credit control area hierarchy, we will come across one more hierarchy in credit management organisation structure which is credit segment. Credit segment is a hierarchy in FSCM SAP credit management and therefore you must link the credit control area with the credit segment, which is one to many.
Definition of credit segment as explained by SAP:
Organizational unit of SAP Credit Management that companies can define, for example, by product type or business area.
In a telecommunications company, a subclassification of relevant business transactions according to the following credit segments could be useful:
Fixed network
Internet
Mobile telephones
Where in the above example we can have different credit segment for each sector. Also, there is a partner relationship functionality to link Higher Level Credit Account of or Lower Level Credit Account of; where we can restrict relationship to one credit segment, which acts like a functionality of maintaining credit limit at customer hierarchy level in old credit management.
Above are the some of the main points which explains the difference between FIN-FSCM-CR and FI-AR-CR credit management, now we are going to cover the list of minimum configurations that is required to activate SAP credit management (note credit control area definition/assignment and sales doc /item catg credit activation is not covered here as it follows the existing process).
1.Activation of SAP credit management- SPRO->Financial Supply chain management->Credit Management->Integration with Sales and Distribution->BADI activation of SAP credit Management.
This is an important step, else credit management FIN-FSCM-CR will not be called from SD.
2.Creation of Credit segment:
3.Assignment of credit control area and credit segment:
4: Define “checking Rule”, very important config which holds the static, dynamic, maximum document value etc related checks:
The list of credit checks that is required to be performed is set-up here for a checking rule:
Note: The checks that we see in OVA8 is available in FSCM credit management as shown below in form of steps where the old credit management (right) is also shown as a comparison:
(All the functionalities of OVA8 are not available, please refer to SAP note for missing functionalities).
You can select a step to see the detail set-up where you can fine tune the config:
Example in step 030, dynamic credit check that is included in checking rule 04, has further settings of defining the credit horizon period in days:
Likewise, we have to add other required steps against a checking rule that needs to be checked during credit check.
Since all the required settings are in place, we can now perform the transactions which starts with Master data creation followed by sale order process.
Creation of Credit master data for business partner - Transaction UKM_BP:
Select the BP Role UKM000, and under general->credit profile tab select the Checking Rules that we have defined above which is going to drive the type of credit check,also risk category is now named as risk class which needs to be selected:
Apart from the above, we must enter the credit segment and credit value in the “Credit Segment data” view as shown below, also in the same screen we can also see the credit utilization and credit horizon:
Sale order creation-Credit check:
During sale order creation as usual we get the credit exceeding warning in below format:
In the old credit management, info structures S066 and S067 are used for updating open sales orders and deliveries/billing respectively, as per FSCM these info structures are not used, where as UKM_ITEM is the table which will get updated. Credit exposure category in UKM_ITEM table represents whether it is a sale order or delivery or billing document:
Where 100 stands for Open sale orders:
400 - Open delivery (PGI not done):
500-Open Billing document (w/o accounting document):
Successful posting of invoice will remove the entry from this table.
I hope the above gives an idea on how SD is linked with FSCM SAP credit management, at least to the extent on how it is different from current credit management functionality.
Would welcome your feedback and comments.
When it comes to credit management, we all know that transaction OVA8 which drives the credit check, plays an important role. This has all the checks and validations that is required to perform credit check:
But in SAP credit management (FIN-FSCM-CR available in FSCM), this transaction has less settings, due to the fact the checks are now controlled thru different transaction in FSCM. So, in general, SAP credit management transaction OVA8 will act as a control mechanism to activate/deactivate SAP credit management FIN-FSCM-CR, further the checks on the static, dynamic, max doc value etc are all going to be carried out at in different transaction at FSCM.
Below is the current OVA8 screen:
where the check box “SAP credit management” activates a BADI (BADI_SD_CM) which has 2 methods one for sale order and the other for delivery:
Order: FSCM_CREDIT_CHECK_ORDER
Delivery: FSCM_CREDIT_CHECK_DELVRY
This BADI carries the data to the FSCM credit management during order creation/delivery, thus the checks defined in the FSCM credit management will become effective. So, the OVA8 transaction is now going to act as a trigger point to carry out SAP credit management (FIN-FSCM-CR).
Credit Segment:
Apart from the credit control area hierarchy, we will come across one more hierarchy in credit management organisation structure which is credit segment. Credit segment is a hierarchy in FSCM SAP credit management and therefore you must link the credit control area with the credit segment, which is one to many.
Definition of credit segment as explained by SAP:
Organizational unit of SAP Credit Management that companies can define, for example, by product type or business area.
In a telecommunications company, a subclassification of relevant business transactions according to the following credit segments could be useful:
Fixed network
Internet
Mobile telephones
Where in the above example we can have different credit segment for each sector. Also, there is a partner relationship functionality to link Higher Level Credit Account of or Lower Level Credit Account of; where we can restrict relationship to one credit segment, which acts like a functionality of maintaining credit limit at customer hierarchy level in old credit management.
Above are the some of the main points which explains the difference between FIN-FSCM-CR and FI-AR-CR credit management, now we are going to cover the list of minimum configurations that is required to activate SAP credit management (note credit control area definition/assignment and sales doc /item catg credit activation is not covered here as it follows the existing process).
1.Activation of SAP credit management- SPRO->Financial Supply chain management->Credit Management->Integration with Sales and Distribution->BADI activation of SAP credit Management.
This is an important step, else credit management FIN-FSCM-CR will not be called from SD.
2.Creation of Credit segment:
3.Assignment of credit control area and credit segment:
4: Define “checking Rule”, very important config which holds the static, dynamic, maximum document value etc related checks:
The list of credit checks that is required to be performed is set-up here for a checking rule:
Note: The checks that we see in OVA8 is available in FSCM credit management as shown below in form of steps where the old credit management (right) is also shown as a comparison:
(All the functionalities of OVA8 are not available, please refer to SAP note for missing functionalities).
You can select a step to see the detail set-up where you can fine tune the config:
Example in step 030, dynamic credit check that is included in checking rule 04, has further settings of defining the credit horizon period in days:
Likewise, we have to add other required steps against a checking rule that needs to be checked during credit check.
Since all the required settings are in place, we can now perform the transactions which starts with Master data creation followed by sale order process.
Creation of Credit master data for business partner - Transaction UKM_BP:
Select the BP Role UKM000, and under general->credit profile tab select the Checking Rules that we have defined above which is going to drive the type of credit check,also risk category is now named as risk class which needs to be selected:
Apart from the above, we must enter the credit segment and credit value in the “Credit Segment data” view as shown below, also in the same screen we can also see the credit utilization and credit horizon:
Sale order creation-Credit check:
During sale order creation as usual we get the credit exceeding warning in below format:
In the old credit management, info structures S066 and S067 are used for updating open sales orders and deliveries/billing respectively, as per FSCM these info structures are not used, where as UKM_ITEM is the table which will get updated. Credit exposure category in UKM_ITEM table represents whether it is a sale order or delivery or billing document:
Where 100 stands for Open sale orders:
400 - Open delivery (PGI not done):
500-Open Billing document (w/o accounting document):
Successful posting of invoice will remove the entry from this table.
I hope the above gives an idea on how SD is linked with FSCM SAP credit management, at least to the extent on how it is different from current credit management functionality.
Would welcome your feedback and comments.
- SAP Managed Tags:
23 Comments
