Credit management (necessary settings in the module FI-AR) (S/4 1709)
This article describes the mechanism of integration of FSCM-CR and FI-AR modules. FSCM-CR can be integrated with the FI-AR module located in the same system as well as in different ones. In this article, we consider the scenario where FSCM-CR and FI-AR are located in the same system.
Integration of FSCM-CR and FI-AR modules is carried out in the following areas:
- Transferring Payment Behavior Summaries
In open fi 5010 for documents with the customer line items when you save the FI document, the system writes the document number in the table UKM_TRANSFER_ARV.
Before adding a record, the system checks if there is an entry in the UKM_TRANSFER_ARV table with such business partner. If there is, the new one is not added.The Payment Behavior in FSCM-CR is updated using the transaction UKM_TRANSFER_VECTOR. The transaction contains an option for delta and full data update in FSCM-CR.Service UKM_CREDITPAYMBEHAVSUMNO is used for data transfer from FI-AR to FSCM-CR.Description of the message format is given by reference http://fmis.minfin.bg/help/EN/42/cb899bfc0a136be10000000a1553f7/content.htm.In BADI_UKM_VECTOR_CALCULATE, it is possible to change the algorithm for updating Payment Behavior on the FSCM-CR side.In the method, FILL_VECTOR BADI UKM_FILL possible to change Payment Behavior data sent from FI-AR.
The Payment Behavior data is displayed in the master record of the business partner in the view of the credit segment (technically, the data is stored in the table UKMBP_VECTOR_IT).
The information is presented in sections.
Highest Dunning Level. The calculation is performed in the UKM_TRANSFER_VECTOR program in the form Calc_highest_dunning_level. The system selects the Dunning Notice with highest level from the table KNB5.
Oldest Open Item. The calculation is performed in the UKM_TRANSFER_VECTOR program in the form calc_oldest_item. The system selects records from BSID with the condition shkzg = ‘s’ and rebzt not ‘Z’. If Special GL is specified in the open position, the system checks whether it is relevant for the credit management (t074u-klimp is not space). After that, the system calculates the position with the earliest Due Date.
Last payment ,
The calculation is performed in the UKM_TRANSFER_VECTOR program in the form calc_last_payment. The system selects the last payment from the table FDM_COLL_LASTPAY. Useful details exist at the note 2590205 – Last payment date in FSCM Credit Management.
Key figures: DSO (UKMBP_VECTOR_IT-IDX_FIGURE)
The calculation is performed in the UKM_TRANSFER_VECTOR program in the form Calc_dso.
DSO is calculated by the formula: DSO = AR / (NS / DAP). Where:
AR – the balance of accounts receivable at the current moment. The balance of accounts receivable is calculated according to the table KNC1 as the balance at the beginning of the year (KNC1-UMSAV) + Total of the Debit Postings for the Month (KNC1-UMXXS) – Total of the Credit Postings for the Month (KNC1-UMXXH).
NS – Revenue for the DSO calculation period (DAP formula indicator). The calculation is performed on the field KNC1-UMXXU “Sales in the reporting period “. To fill in the field KNC1-UMXXS, postings with posting codes with the indicator “Sales-related”.
DAP – The value is pre-set as the number of days for the last 3 full months + the number of days of the current month.
Key figures: Sales of Last 12 Months (UKMBP_VECTOR_IT-SALES_VOL), Highest Monthly Sales in Last 12 Months (UKMBP_VECTOR_IT-SALES_MAX)
The calculation is performed on the field KNC1-UMXXU “Sales in the reporting period” in the functional module UKM_GET_IDX_FIGURES.
Key figures: Average arrears with payments without cash discount taken (UKMBP_VECTOR_IT-SL_ARR_WO), Gross Total of Cleared Items with Cash Discount Not Taken (UKMBP_VECTOR_IT- SL_ARR_WO_AMOUNT), Average Arrears with Cash Discount Payments (UKMBP_VECTOR_IT-SL_SLARR_W), Gross Total of Cleared Items without Cash Discount Loss (UKMBP_VECTOR_IT-SL_ARR_W_AMOUNT).
The calculation is performed in the functional module UKM_GET_IDX_FIGURES.
The system calculates the average values of delinquencies and amounts of the receipts of payments made on the basis of the table knb4.
Note 2172419 «RFDOPR20 Customer payment is not updated in Payment History» shows the conditions under which payments from the debtor are updated in the KNB4 table.
- Transferring Commitments.Documents of accounts receivable are updated in FSCM-CR with Credit Exposure Categories equal to 200 “Open Items”. This reduces the amount of the previous document of 500 “Billing Document Value”.
There are 2 ways to update credit exposure:Direct update. If the BADI UKM_R3_ACTIVATE FI_AR_UPDATE_MODE method is not implemented (or implemented and filled with the value of X), then the credit exposure is taken directly from BSEG (CDS IFIRECPAYITEM). An example of use can be found in the code – cl_ukm_facade_local=>pull_commitment_ar.Update with transaction UKM_TRANSFER_ITEMS “Liability Update”. If you want Credit exposure data to be taken from Credit management tables (for example, if some enterprises are running on a different SAP system, or if you want to integrate with a non-SAP system), you need to create your own BADI ukm_r3_activate IMPLEMENTATION of the FI_AR_UPDATE_MODE method. In this case, using the transaction UKM_TRANSFER_ITEMS “Liability Update”, the system selects data from the table UKM_TRANSFER_ARV and generates entries in the tables UKM_ITEM, UKM_TOTALS, UKM_PM_BALANCE.
Credit exposure category 300 «Special Credit Exposure». If necessary, you can set up the filling of credit exposure category 300 using UKM_FILL (method FILL_FIELDS). A detailed description is given in note 2578434 – “Special G / L posts in FSCM – Credit Exposure type 300”.
Recreating Data. The following reports are available to recreate the credit exposures from an SD system from SAP ERP 6.0:
– UKM_RFDKLI20 to recreate the credit exposure after organizational changes
– UKM_RVKRED77 to recreate the credit exposure where you have removed the cause of the error in the case of data inconsistencies
– UKM_RVKRED88 to simulate report UKM_RVKRED77 without setting blocks on the documents affected. This report prepares an update run of report UKM_RVKRED77 to determine suitable selection parameters, for example.
Troubleshooting. In the notes:
– 2576445 – “Difference between FI-AR and credit exposure type 200”
– 1124271 – “Operational concept SAP Credit Management”
possible reasons for non-compliance of credit exposure and FI-AR data are described.
Hi Sergey Pryanishnikov,
I have a requirement to update UKM_ITEM-STATUS when sales order gets created. FSCM related BADI’s are active.
I have used BADI – IF_EX_BADI_SD_CM~FSCM_COMMITMENT_UPDATE_ORDER to update STATUS field in table GT_DELTA_ORDER, but didnt work.
Also checked UKM_FILL BADI methods but none of methods have field STATUS.
Please let me know how to update the field.
Thanks & Regards,
Thinks for your sharing. and did anyone can share us, which table store data of Credit Exposure Categories 200.
Hi Da Thang,
Where the Credit Exposure Categories 200 Open Items is stored, depends on the settings in the implementation of BAdI UKM_R3_ACTIVATE - FI_AR_UPDATE_MODE.
- If standard implementation is used, E_READ_VIEW = 'X' -> FI data is read on the fly from the source table (BSEG).
- If E_DIRECT_UPDATE = 'X' -> FI is stored in the UKM_ITEM table.
See also note ##2868484-FSCM Credit Management in S/4: How are the commitments selected or transferred from FI and SD
Thanks for the explanation.
In my case, the amount is going to AMOUNT_SEC (guaranteed commitment) instead of AMOUNT (Real amount)
To send to the correct field (AMOUNT), in sales order (Type 100), I solved the problem cleaning the field ABGES from table VBEP in userExit MV45AFZZ.
And the in INVOICE (Type 200), I had to clean the field ABSBT from BSEG table in function POST_DOCUMENT. Worked fine to me.
To fix all open documents, I ran the t-code UKM_COMMITMENTS deleting the lines, and after this, ran the program UKM_RVKRED77 to fix all commitents.
Hope this helps.
Signed: Luis Tacioli Cavaglieri