C_SuplrPaytBlockingReasonVH
Payment Blocking Reason
C_SuplrPaytBlockingReasonVH is a Consumption CDS View that provides data about "Payment Blocking Reason" in SAP S/4HANA. It reads from 1 data source (I_PaymentBlockingReason) and exposes 2 fields with key field PaymentBlockingReason. It has 1 association to related views. It is exposed through 2 OData services (ASQL_F0593A, SUPPLIERPAYMENTBLOCK). It is used in 1 Fiori application: Manage Payment Blocks V2. Part of development package ODATA_MANAGE_PAYMENT_BLOCKS_V2.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| I_PaymentBlockingReason | I_PaymentBlockingReason | from |
Associations (1)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [0..*] | I_PaymentBlockingReasonText | _Text | $projection.PaymentBlockingReason = _Text.PaymentBlockingReason |
Annotations (9)
| Name | Value | Level | Field |
|---|---|---|---|
| AccessControl.authorizationCheck | #NOT_REQUIRED | view | |
| ObjectModel.resultSet.sizeCategory | #XS | view | |
| ObjectModel.usageType.serviceQuality | #A | view | |
| ObjectModel.usageType.dataClass | #MASTER | view | |
| ObjectModel.usageType.sizeCategory | #S | view | |
| ObjectModel.dataCategory | #VALUE_HELP | view | |
| ObjectModel.representativeKey | PaymentBlockingReason | view | |
| VDM.viewType | #CONSUMPTION | view | |
| EndUserText.label | Payment Blocking Reason | view |
OData Services (2)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| ASQL_F0593A | ASQL_F0593A | C2 | NOT_RELEASED | |
| SUPPLIERPAYMENTBLOCK | SUPPLIERPAYMENTBLOCK | V2 | C1 | NOT_TO_BE_RELEASED_STABLE |
Fiori Apps (1)
| App ID | App Name | Type | Description |
|---|---|---|---|
| F0593A | Manage Payment Blocks V2 | Transactional | An application to set and remove payment blocks on vendor accounts and open payable items. |
Manage Payment Blocks V2
Business Role: Accounts Payable Accountant
With this app, you can set and remove payment blocks on invoices or supplier accounts. You can use various search, sorting, and grouping functions to select and display invoices and view their status.
Key Features: Search and filter for supplier accounts and open invoices Fuzzy searchTwo search bars are available in this app. One is on the supplier list page, and the other is on the supplier object page. You can use both search bars to make fuzzy searches for supplier accounts or open invoices by supplier name, supplier ID, invoice number, journal entry number, purchase order, or external reference.After you enter a search term in the first search bar and choose a search result in the supplier list, the system navigates you to the supplier object page, where the second search bar is automatically filled with the same search term. You can also use the second search bar independently to search for the open invoices for a specific supplier. FilterOn the supplier list page, you can use the default filters (Supplier, Company Code, Status, and Payment Block Reason) to filter the worklist effectively. You can customize the filter bar by removing basic filters and adding more filters (Blocked Amount, Company Code Currency, and more). Display supplier accounts and open invoices and view their status Display supplier accounts and view the general information and all the open invoices for a specific supplier. Display open invoices with their payment details and related documents. View the status of supplier accounts and open invoices. Set and remove payment blocks Choose a specific supplier account or one or more open invoices to block them for payment.When you set a payment block, a pop-up dialog box appears in which you can select a payment block reason and add some notes. Remove payment blocks on supplier accounts and open invoices.
Fields (2)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | PaymentBlockingReason | Pmnt block | ||
| _Text | _Text |
Derived SQL interpretation, reconstructed from the parsed view metadata (data sources, associations, and field mappings). SAP annotations are omitted and the structure is reformulated as SQL — this is a functional approximation, not the verbatim SAP source.
-- Derived SQL interpretation of CDS view C_SuplrPaytBlockingReasonVH.
-- Reconstructed from parsed metadata (data sources, associations, fields).
-- SAP annotations are omitted and the structure is reformulated as SQL;
-- this is a functional approximation, not the verbatim SAP source. Some join
-- conditions may be unavailable and a few CDS constructs are kept as-is.
CREATE VIEW C_SuplrPaytBlockingReasonVH AS
SELECT
cast (PaymentBlockingReason as farp_dzlspr) AS PaymentBlockingReason
FROM I_PaymentBlockingReason
LEFT OUTER JOIN I_PaymentBlockingReasonText AS _Text ON PaymentBlockingReason = _Text.PaymentBlockingReason -- association [0..*]
;
Learn More
- VDM (Virtual Data Model) in SAP S/4HANA Explained
- Types of CDS Views: Basic, Composite, Consumption, and Transactional
- OData Services in SAP S/4HANA Explained
- Service Bindings and Service Definitions in SAP S/4HANA
- SAP Fiori Apps Architecture — How Fiori Apps Connect to Data
- CDS View Annotations — A Complete Guide
- What Is a CDS View in SAP S/4HANA?
- SAP Tables vs CDS Views — Key Differences
- Understanding Data Lineage in SAP S/4HANA
- CDS View Field Mapping and Associations
- Understanding the SAP S/4HANA Data Model
- CDS View Extensions and Custom Fields in SAP S/4HANA
- Released APIs and Stability Contracts in SAP S/4HANA
- BSEG to ACDOCA: The Universal Journal Migration
- Business Partner Migration: KNA1/LFA1 to BUT000
- Material Document Migration: MSEG/MKPF to MATDOC
- How to Find the Right CDS View for an SAP Table
- BW Extractor to CDS View Migration Guide
- S/4HANA CDS View Deprecation: What You Need to Know
- ABAP CDS View Tutorial — From Basics to Real-World Examples
- RAP and CDS Views — Building Transactional Apps in SAP S/4HANA
- Sales Document Status Migration: VBUP/VBUK Removal in S/4HANA
- CO Tables in S/4HANA: COEP, COBK, COSS, COSP to ACDOCA