Skip to main content

Credit Management Reports - S/4 HANA

Display Credit Exposure - UKM_BOL_COMMITMENTS_1

This gives the list of open document and levels at which they are in  open status i.e., order, delivery or Billing

Table - V_UKM_TOTALS

This table gives the commitment amount and the exposure perceived

Report - UKM_RVKRED06

The report checks all blocked documents from the credit view

Report - UKM_RVKRED77

This is used for the reorganization of credit data after update errors


Comments

  1. Nathanial18 December 2018 at 22:49

    What a nice post. I appreciate about it. Do you know about evans pughe strings of hitchin ltd then tell me. Or have another site like this share with me.
    Thanks a lot!!!

    ReplyDelete
  2. Home Services5 August 2021 at 01:24

    We’re sure you’ve come across lousy management reports. Those reports, once read, you’ll never hear back. Or report that no one acts on its recommendations despite the high stakes. Before we delve into the management reports examples, let’s go through the definition.
    https://ppcexpo.com/blog/management-reports-examples

    ReplyDelete
  3. Chris Lesnar14 August 2021 at 11:56

    Thanks for the amazing blog. Nice Information has been depicted. Keep posting.
    quick credit check

    ReplyDelete

Post a Comment

Popular posts from this blog

Add Custom fields to sales order screen in Additional Tab B - Header

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1>         VBAK-<Custom Field 2>         VBAK-<Custom Field 3> ENDCHAIN. Thank you.
Post a Comment
Read more

User Exits in Delivery

FORM routine USEREXIT_REFRESH_DOCUMENT (include MV50AFZ1) Purpose The FORM routine USEREXIT_REFRESH_DOCUMENT is used for the initialization of your own data areas before the processing of a new delivery document. Call The routine is called from within the standard routine BELEG_DATEN_INIT (SAPMV50A). Basically, the data initialization is called on the following occasions: FORM routine USEREXIT_DELETE_DOCUMENT (include MV50AFZ1) Purpose If a delivery is deleted, you can delete your own dependent data using this FORM routine. Call The FORM routine is called from the FORM routine BELEG_LOESCHEN (SAPMV50A) if the document can be deleted completely. Immediately after the FORM routine  USEREXIT_DELETE_DOCUMENT is called, the document backup is called for which the logically deleted delivery is removed from the database. FORM routine USEREXIT_READ_DOCUMENT (include MV50AFZ1) Purpose The exit is used to make your own data availabl...
1 comment
Read more

How to change records in SAP using debug mode

This post explains how database update can be performed through transaction codes SE16N and SE16. At times, there might be a situation in the test environment where we are required to perform database updates in order to manipulate or try to replicate a case in a lower environment. Database contents in SAP can be viewed through transaction codes SE16N or SE16. This post explains how the database update can be performed for both transaction codes through debug mode. Case 1: Transaction Code SE16 In this case, I have taken a sample example to update the VBAK table entry through debug mode. Enter Sales Order Number Select the entry displayed enter '/H' in the command bar and click on ok or enter button. Then click on entering again after debugging activation to enter into debugging screen Click on the 'Code' then display as 'SHOW' on the right side of the screen. Then we will change it to 'EDIT' as we are trying to change th...
1 comment
Read more