How to use S_KI4_29000110 - IMG-Aktivität: OHIFRPBS053

SAP Transaction Code - Details

• Transaction Code: S_KI4_29000110

  Description: IMG-Aktivität: OHIFRPBS053

  Release: S/4HANA and ECC 6

• • Program: SAPLS_CUS_IMG_ACTIVITY

    Screen: 200

    Authorization Object:

  • Development Package: P06CP1

    Package Description:

    Parent Package:

  • Module/Component:

    Description:

Smart SAP Assistant

• SAP Tcode: S_KI4_29000110 - IMG-Aktivität: OHIFRPBS053

  
  Overview: 
  S_KI4_29000110 is an SAP transaction code used to access the IMG Activity  OHIFRPBS053. This activity is part of the SAP system configuration and is used to define the parameters for the automatic payment program. 
  
  Functionality: 
  The purpose of this transaction code is to define the parameters for the automatic payment program. This includes setting up the payment methods, payment terms, and other related settings. It also allows users to define the criteria for selecting invoices for payment and to set up the payment run schedule. 
  
  Step-by-step How to Use: 
  1. Access the transaction code S_KI4_29000110 in the SAP system. 
  2. Select “Define Payment Methods” from the menu. 
  3. Enter the details of the payment method, such as bank account number, currency, and payment terms. 
  4. Select “Define Payment Terms” from the menu. 
  5. Enter the details of the payment terms, such as due date, discount date, and discount percentage. 
  6. Select “Define Payment Run Schedule” from the menu. 
  7. Enter the details of the payment run schedule, such as frequency and start date/time. 
  8. Select “Define Criteria for Selection of Invoices” from the menu. 
  9. Enter the criteria for selecting invoices for payment, such as invoice amount and due date range. 
  10. Save your changes and exit the transaction code. 
  
  Other Recommendations: 
  It is recommended that users familiarize themselves with all of the settings available in this transaction code before making any changes to ensure that they are properly configured for their needs. Additionally, users should always test their changes in a test environment before applying them to a production system to ensure that they are working correctly and do not cause any unexpected issues or errors.