C_EarmarkedFundsDocumentTP
Manage Earmarked Funds
C_EarmarkedFundsDocumentTP is a Consumption CDS View that provides data about "Manage Earmarked Funds" in SAP S/4HANA. It reads from 1 data source (R_EarmarkedFundsDocumentTP) and exposes 60 fields with key field EarmarkedFundsDocument. It is exposed through 3 OData services (ASQL_F4657, ASQL_F7334, UI_EMRKDFNDSDOC_MANAGE). It is used in 2 Fiori applications: Manage Earmarked Funds Documents, Display Earmarked Funds Documents. Part of development package PSM_S4C_EARMARKED_FUNDS.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| R_EarmarkedFundsDocumentTP | R_EarmarkedFundsDocumentTP | projection |
Annotations (10)
| Name | Value | Level | Field |
|---|---|---|---|
| Metadata.ignorePropagatedAnnotations | true | view | |
| Metadata.allowExtensions | true | view | |
| AccessControl.authorizationCheck | #CHECK | view | |
| VDM.viewType | #CONSUMPTION | view | |
| ObjectModel.representativeKey | EarmarkedFundsDocument | view | |
| ObjectModel.usageType.sizeCategory | #XL | view | |
| ObjectModel.usageType.serviceQuality | #C | view | |
| ObjectModel.usageType.dataClass | #TRANSACTIONAL | view | |
| Search.searchable | true | view | |
| EndUserText.label | Manage Earmarked Funds | view |
OData Services (3)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| ASQL_F4657 | ASQL_F4657 | C2 | NOT_RELEASED | |
| ASQL_F7334 | ASQL_F7334 | C2 | NOT_RELEASED | |
| UI_EMRKDFNDSDOC_MANAGE | UI_EMRKDFNDSDOC_MANAGE | V2 | C1 | NOT_RELEASED |
Fiori Apps (2)
| App ID | App Name | Type | Description |
|---|---|---|---|
| F4657 | Manage Earmarked Funds Documents | Transactional | |
| F7334 | Display Earmarked Funds Documents | Transactional | App Variant of the Manage Earmarked Funds app to be displayed in the My Inbox App. With this app you can display contextual information about the earmarked funds business object. |
Manage Earmarked Funds Documents
Business Role: Budget Specialist - Funds Management
You can use this SAP Fiori app to create, change or display earmarked funds in their function as a funds reservation, funds precommitment, or funds commitment. At line item level, you can preselect part of the budget as an expense for specific account assignments and reserve it from the total budget. Subsequent consumption or reduction of this budget by comprehensive accounting or purchasing documents is shown in the document items. For this purpose, you can reference an earmarked fund in the purchasing and accounting documents.
Key Features: Create an earmarked fund as a funds reservation, funds precommitment or funds commitment. Perform account assignment-related reservation of amounts in the document items. Display entries under Consumption if earmarked funds were referenced in purchasing or comprehensive accounting documents. Display or create entries under Manual Reduction if the consumption is subsequently created in the earmarked funds item with reference to the purchasing or accounting document. Display the initial earmarked funds amount and the remaining budget for each document item. Use the Account Assignment Changeable indicator to improve the flexibility for consuming purchasing or accounting documents and their account assignments. Return the remaining unconsumed budget that has not been used using the Item Completed indicator. Prevent further consumption postings using the Block Item indicator. Upload attachments. Log changes to the document header and the document items. Use the unified SAP S/4HANA Output Control solution for all output-related tasks for earmarked funds documents under Output Items.
Display Earmarked Funds Documents
Business Role: Budget Specialist - Funds Management
You can access the Manage Workflows for Earmarked Funds app using the business role SAP_BR_BPC_EXPERT. You can use this app to create and configure workflows to optimize the approval and rejection process when an earmarked fund document is created or if the account assignment fields or amount for an existing earmarked funds document is changed. This app provides you with several options for defining preconditions for the overall release of an earmarked funds document approval or rejection. The approval or rejection process starts when a workflow with one or more steps is activated and the preconditions you have assigned to it are met. To enable a workflow for a particular document type, you need to make the necessary configuration using the configuration activity Define Document Types for Earmarked Funds. Once the earmarked funds document is found in the workflow, you cannot change or edit the account assignment fields or the changed amount field in the app Manage Earmarked Funds. These fields have the non-editable status until the earmarked funds document is approved or rejected. This app also delivers a predelivered workflow content for automatic approval when an earmarked funds document is created or if the account assignment fields or amount for an existing earmarked funds document is changed. By default, the predelivered workflow has the active status. You can access the existing app Manage Earmarked Funds using the business role SAP_BR_BUDGET_SPECIALIST or SAP_BR_GRANT_SPECIALIST. Using this app, you can create or change an earmarked funds document and based on the workflow configured, it is either approved automatically or is sent to the user responsible related to the role set in the workflow configuration. You can find the following roles in the section Role on the Recipients tab in the app Manage Workflows for Earmarked Funds: Approve Earmarked Funds (Team Function): If you use this role, the recipient is determined based on the users assigned to the function Approve Earmarked Funds (Team Function) in the team created in the app Manage Teams and Responsibilities for the team category EARMFUND. Cost Center Responsible with Highest Debit: This role triggers the approval for the respective user responsible maintained for the specified cost center. Funds Responsible with Highest Debit: This role triggers the approval for the respective user responsible maintained for the specified fund in the App Manage Funds. Grant Responsible with Highest Debit: This role triggers the approval for the respective user responsible maintained for the specified grant in the App Manage Grants. Users with Business Catalog: Earmarked Funds - Document Approval: This role triggers the approval for the respective users with a business role that includes the business catalog Earmarked Funds - Document Approval (SAP_PSM_BC_EF_DOC_APPROVE_PC). WBS Element Responsible with Highest Debit: This role triggers the approval for the respective user responsible maintained for the specified WBS element. Note If no agent is determined for a workflow triggered, the earmarked funds document is identified as containing errors. The user ADMINISTRATOR can identify and reprocess the workflow using the app Work Items Without Agents once the correct agents have been maintained in the master data app, like Manage Teams and Responsibilities, Manage Grants or Manage Funds. If the user ADMINISTRATOR cancels an earmarked funds document in the workflow using the app Flexible Workflow Administration, then the earmarked funds document is canceled and the amount fields are reset to the previously approved state. Designated approvers with the business roles mentioned above can access the SAP Fiori app My Inbox and receive the approval request for the earmarked funds in the My Inbox app and as notifications.Whenever you access work items that are related to earmarked fund documents from the My Inbox App, you can see details related to that particular earmarked fund document on the object page.
Key Features: Create a new workflow. Display details of a workflow. Copy an existing workflow. Activate or deactivate a workflow. Define properties, such as the workflow name, description, and validity period Define the start conditions for a workflow that determine when a particular workflow should be activated. In the Start Conditions section, choose the relevant entry from the dropdown menu and make entries in the required fields. Define the step sequence by adding and configuring the approval steps in the workflow. Note Only active workflows are processed. It is not possible to edit a workflow once it has been activated. Delete a workflow if it is no longer required. You can only delete inactive workflows. If you want to delete an active workflow, you have to deactivate it first. A standard pre-delivered (default) workflow exists that must not be deleted and this workflow is executed if no other workflow conditions are satisfied. The order of the workflow is also significant. The program uses the order to go through the workflows one by one. The first workflow in the order where the conditions are true is used. This ensures that only one workflow in the list of your defined workflows is started, even if several workflows have matching start conditions.
Fields (60)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | EarmarkedFundsDocument | EarmarkedFundsDocument | Earmarked Funds | |
| virtualEarmarkedFundsDocIntNumberchar10 | ||||
| EarmarkedFundsDocumentForEdit | EarmarkedFundsDocumentForEdit | External Document Number | ||
| EarmarkedFundsDocumentCategory | EarmarkedFundsDocumentCategory | Document Category | ||
| EarmarkedFundsDocumentType | EarmarkedFundsDocumentType | Document Type | ||
| CompanyCode | CompanyCode | Receiver Company Code | ||
| CompanyCodeName | _CompanyCode | CompanyCodeName | Company Name | |
| virtualLedgerfins_ledger | ||||
| virtualSourceLedgerfins_ledger_pers | ||||
| virtualIsCommitmentfis_xcommitment | ||||
| TransactionCurrency | TransactionCurrency | Transaction Currency | ||
| CompanyCodeCurrency | CompanyCodeCurrency | Local Currency | ||
| ControllingArea | ControllingArea | Controlling Area | ||
| FinancialManagementArea | FinancialManagementArea | FM Area | ||
| virtualEmrkdFndsFldReferenceIsHidboolean | ||||
| EarmarkedFundsDocReference | EarmarkedFundsDocReference | Reference | ||
| EarmarkedFundsHeaderText | EarmarkedFundsHeaderText | Document Text | ||
| PostingDate | PostingDate | Posting Date for GR | ||
| DocumentDate | DocumentDate | Journal Entry Date | ||
| virtualEmrkdFndsFldExchDataIsHidboolean | ||||
| ExchangeRateDate | ExchangeRateDate | Translatn Date | ||
| AbsoluteExchangeRate | AbsoluteExchangeRate | Absolute Exchange Rate | ||
| ExchRateIsIndirectQuotation | ExchRateIsIndirectQuotation | Exchange Rate Is Indirect Quotation | ||
| EmrkdFndsDocCreatedByUser | EmrkdFndsDocCreatedByUser | Entered By | ||
| CreatedByUserDescription | ||||
| EmrkdFndsDocCreationDate | EmrkdFndsDocCreationDate | Entered On | ||
| EmrkdFndsDocLastChangedByUser | EmrkdFndsDocLastChangedByUser | Last Changed By | ||
| LastChangedByUserDescription | ||||
| EmrkdFndsDocLastChangeDate | EmrkdFndsDocLastChangeDate | Changed On | ||
| EmrkdFndsDocLastChangeDateTime | EmrkdFndsDocLastChangeDateTime | Last Changed On | ||
| EmrkdFndsIsMarkedForArchiving | EmrkdFndsIsMarkedForArchiving | Can Be Archived | ||
| EmrkdFndsIsBlockedAgainstUsage | EmrkdFndsIsBlockedAgainstUsage | Doc.Blocked | ||
| EarmarkedFundsIsCompleted | EarmarkedFundsIsCompleted | Doc.Completed | ||
| EarmarkedFundsManualEditBlock | EarmarkedFundsManualEditBlock | Document Block | ||
| EarmarkedFundsStartWorkflow | EarmarkedFundsStartWorkflow | Start Approval by Workflow | ||
| EarmarkedFundsIsApproved | EarmarkedFundsIsApproved | Doc. Approved | ||
| EmrkdFndsWasAlreadyAprvdOnce | EmrkdFndsWasAlreadyAprvdOnce | Already Apprvd | ||
| EmrkdFndsTotalInTransCrcy | EmrkdFndsTotalInTransCrcy | Total Amount | ||
| EmrkdFndsChgdTotalInTransCrcy | EmrkdFndsChgdTotalInTransCrcy | Amount Changed | ||
| EmrkdFndsOpenTotalInTransCrcy | EmrkdFndsOpenTotalInTransCrcy | Open Amount | ||
| EmrkdFndsTotalInCCCrcy | EmrkdFndsTotalInCCCrcy | Total Amount in Local Currency | ||
| EmrkdFndsChgdTotalInCCCrcy | EmrkdFndsChgdTotalInCCCrcy | Amount Changed in Local Currency | ||
| EmrkdFndsOpenTotalInCCCrcy | EmrkdFndsOpenTotalInCCCrcy | Open Amount in Local Currency | ||
| virtualEmrkdFndsFldGLAccountIsHidboolean | ||||
| virtualEmrkdFndsFldFundIsHidboolean | ||||
| virtualEmrkdFndsFldBdgtPerdIsHidboolean | ||||
| virtualEmrkdFndsFldGrantIDIsHidboolean | ||||
| virtualEmrkdFndsFldSupplierIsHidboolean | ||||
| virtualEmrkdFndsFldItemTextIsHidboolean | ||||
| virtualEmrkdFndsFldDueDateIsHidboolean | ||||
| virtualEmrkdFndsFldResDocIsHidboolean | ||||
| _FiscalYearForCompanyCode | _FiscalYearForCompanyCode | |||
| _EarmarkedFundsDocCategory | _EarmarkedFundsDocCategory | |||
| _EarmarkedFundsDocType | _EarmarkedFundsDocType | |||
| _EarmarkedFundsMnlEditBlk | _EarmarkedFundsMnlEditBlk | |||
| _CompanyCodeCurrency | _CompanyCodeCurrency | |||
| _TransactionCurrency | _TransactionCurrency | |||
| _CompanyCode | _CompanyCode | |||
| _EmrkdFndsDocLastChangedByUser | _EmrkdFndsDocLastChangedByUser | |||
| _EmrkdFndsDocCreatedByUser | _EmrkdFndsDocCreatedByUser |
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_EarmarkedFundsDocumentTP.
-- 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_EarmarkedFundsDocumentTP AS
SELECT
EarmarkedFundsDocument,
virtual EarmarkedFundsDocIntNumber : char10 AS virtualEarmarkedFundsDocIntNumberchar10,
EarmarkedFundsDocumentForEdit,
EarmarkedFundsDocumentCategory,
EarmarkedFundsDocumentType,
CompanyCode,
_CompanyCode.CompanyCodeName AS CompanyCodeName,
virtual Ledger : fins_ledger AS virtualLedgerfins_ledger,
virtual SourceLedger : fins_ledger_pers AS virtualSourceLedgerfins_ledger_pers,
virtual IsCommitment : fis_xcommitment AS virtualIsCommitmentfis_xcommitment,
TransactionCurrency,
CompanyCodeCurrency,
ControllingArea,
FinancialManagementArea,
virtual EmrkdFndsFldReferenceIsHid : boolean AS virtualEmrkdFndsFldReferenceIsHidboolean,
EarmarkedFundsDocReference,
EarmarkedFundsHeaderText,
PostingDate,
DocumentDate,
virtual EmrkdFndsFldExchDataIsHid : boolean AS virtualEmrkdFndsFldExchDataIsHidboolean,
ExchangeRateDate,
AbsoluteExchangeRate,
ExchRateIsIndirectQuotation,
EmrkdFndsDocCreatedByUser,
cast( _EmrkdFndsDocCreatedByUser.UserDescription as vdm_createdbyuserdescription preserving type ) AS CreatedByUserDescription,
EmrkdFndsDocCreationDate,
EmrkdFndsDocLastChangedByUser,
cast( _EmrkdFndsDocLastChangedByUser.UserDescription as vdm_lastchangedbyuserdescripti preserving type ) AS LastChangedByUserDescription,
EmrkdFndsDocLastChangeDate,
EmrkdFndsDocLastChangeDateTime,
EmrkdFndsIsMarkedForArchiving,
EmrkdFndsIsBlockedAgainstUsage,
EarmarkedFundsIsCompleted,
EarmarkedFundsManualEditBlock,
EarmarkedFundsStartWorkflow,
EarmarkedFundsIsApproved,
EmrkdFndsWasAlreadyAprvdOnce,
EmrkdFndsTotalInTransCrcy,
EmrkdFndsChgdTotalInTransCrcy,
EmrkdFndsOpenTotalInTransCrcy,
EmrkdFndsTotalInCCCrcy,
EmrkdFndsChgdTotalInCCCrcy,
EmrkdFndsOpenTotalInCCCrcy,
virtual EmrkdFndsFldGLAccountIsHid : boolean AS virtualEmrkdFndsFldGLAccountIsHidboolean,
virtual EmrkdFndsFldFundIsHid : boolean AS virtualEmrkdFndsFldFundIsHidboolean,
virtual EmrkdFndsFldBdgtPerdIsHid : boolean AS virtualEmrkdFndsFldBdgtPerdIsHidboolean,
virtual EmrkdFndsFldGrantIDIsHid : boolean AS virtualEmrkdFndsFldGrantIDIsHidboolean,
virtual EmrkdFndsFldSupplierIsHid : boolean AS virtualEmrkdFndsFldSupplierIsHidboolean,
virtual EmrkdFndsFldItemTextIsHid : boolean AS virtualEmrkdFndsFldItemTextIsHidboolean,
virtual EmrkdFndsFldDueDateIsHid : boolean AS virtualEmrkdFndsFldDueDateIsHidboolean,
virtual EmrkdFndsFldResDocIsHid : boolean AS virtualEmrkdFndsFldResDocIsHidboolean
FROM R_EarmarkedFundsDocumentTP
;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