📊 MNO Logs B2B

Operation Title: MNO Logs

Overview: Track and Analyze Mongo-Based Utility Logs in Real Time

Key Features:

List of Figures:

📋 Overview

The MNO (Mobile Network Operator) logs section provides a comprehensive overview of M-Pesa B2B transaction activity. It captures detailed records of both incoming requests and outgoing responses, allowing users to track the flow of transactions between systems in real time. These logs are essential for validating transaction data, performing audits, and resolving issues efficiently. By offering clear visibility into each step of the transaction process, the MNO logs enhance transparency and support effective monitoring. Overall, this section plays a crucial role in ensuring the reliability and accuracy of M-Pesa B2B operations.

⚡ Introduction

The MNO (Mobile Network Operator) logs section is designed to capture and display detailed records of M-Pesa B2B transactions. It includes both request and response data exchanged between systems, providing valuable insights into transaction flow. This information is essential for tracking activity, validating data, and identifying any issues in real time. The logs serve as a key resource for maintaining transparency and operational efficiency within the M-Pesa B2B integration.

⚙️ Functionality
Figure: 18.1
  • 1 Search Bar: Users can search for specific files by entering text like a case ID or filename. This makes it easier to quickly find the needed file without browsing through the whole list.
  • 2 Refresh button: Red Circular Arrows: Refreshes the table to display the latest updated data.
🔧 Mongo Utility Logs Form

➤ In this section, users can select the desired execution collection, which specifies the dataset the system will act upon. This selection is essential for ensuring that the correct data is processed during the execution of utility requests.

Figure: 18.2
📊 Mongo Utility Logs Records Table
  • Transaction ID: A unique identifier used to track and reference a specific transaction within a system.
  • Record Status: Indicates the current state or condition of a data record within the system (e.g., active, pending, or completed).
  • FCCREF: A unique reference code used to identify and track a specific transaction or request within the FCC (Financial Control Center) or related system.
Figure: 18.3
Figure: 18.4
📝 PRC B2B Request

➤ PRC b2b_request: In this section, the user can access the XML view of the B2B request associated with the corresponding Xref (Cross Reference). The CBS reference is automatically fetched from the related Flex Request. This XML view provides a structured representation of the request data, which is useful for reviewing, validating, and troubleshooting transaction details within system-to-system communication.

Figure: 18.5
📤 B2B Response for XREF

➤ b2b_response for XREF: In this section, you can view the B2B response in XML format for the corresponding Xref (Cross Reference). The CBS reference is automatically fetched from the associated Flex Request. This view allows users to examine the structured response data returned by the system, which is useful for validating transaction outcomes and troubleshooting issues related to system integration.

Figure: 18.6
🔄 CBS B2B Flex Request

➤ CBS_B2B_flex_request for EXTFTF0002 XREF: In this section, user can view the B2B request in XML format associated with the corresponding Xref (Cross Reference). This request contains the data sent to the CBS system, allowing users to review the structured information for validation, auditing, or troubleshooting as part of system-to-system communication. The relevant collection used in the request is automatically fetched from the RTGS request.

  • Shows B2B request in XML format linked to the Xref.
  • Uses RTGS collection and supports validation, auditing, and troubleshooting.
Figure: 18.7
📥 CBS B2B Flex Response

➤ CBS_B2B_flex_response for EXTFTF0002 XREF: In this section, you can view the CBS response associated with the corresponding Xref (Cross Reference). The response data is fetched based on the collection derived from the RTGS request. This allows users to review the structured response information received from the CBS system, which is useful for validating transaction outcomes and supporting system-to-system communication.

User can also view the data in table format here.

Figure: 18.8

🎯 Final Output:

The MNO Logs B2B section provides comprehensive transaction monitoring capabilities through detailed logging of M-Pesa B2B operations. Users can efficiently search, refresh, and analyze transaction data through structured tables displaying transaction IDs, status updates, timestamps, and cross-references. The system offers XML views for both requests and responses, enabling thorough validation and troubleshooting. With integrated CBS communication tracking and RTGS collection management, this tool ensures complete transaction transparency and operational efficiency for M-Pesa B2B integrations.