I_FldLogsUserPlant
Field Logistics:Remote Plant for FL User
I_FldLogsUserPlant is a Basic CDS View that provides data about "Field Logistics:Remote Plant for FL User" in SAP S/4HANA. It reads from 1 data source (flog_plantusr) and exposes 3 fields with key field FldLogsRemotePlant. It has 1 association to related views. It is exposed through 2 OData services (UI_SHIPMENTCONTAINERPACKG, UI_SUPPLIERITEM). It is used in 2 Fiori applications: Manage Logistics - Supplier Items, Pack Container.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| flog_plantusr | flog_plantusr | from |
Associations (1)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [0..1] | I_Plant | _RemotePlantText | $projection.FldLogsRemotePlant = _RemotePlantText.Plant |
Annotations (9)
| Name | Value | Level | Field |
|---|---|---|---|
| AbapCatalog.sqlViewName | IFLUSERPLANT | view | |
| AbapCatalog.compiler.compareFilter | true | view | |
| AccessControl.authorizationCheck | #CHECK | view | |
| ObjectModel.usageType.serviceQuality | #C | view | |
| ObjectModel.usageType.dataClass | #TRANSACTIONAL | view | |
| ObjectModel.usageType.sizeCategory | #M | view | |
| EndUserText.label | Field Logistics:Remote Plant for FL User | view | |
| VDM.viewType | #BASIC | view | |
| ClientHandling.algorithm | #SESSION_VARIABLE | view |
OData Services (2)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| UI_SHIPMENTCONTAINERPACKG | UI_SHIPMENTCONTAINERPACKG | V2 | C1 | NOT_RELEASED |
| UI_SUPPLIERITEM | UI_SUPPLIERITEM | V2 | C1 | NOT_RELEASED |
Fiori Apps (2)
| App ID | App Name | Type | Description |
|---|---|---|---|
| F5082 | Manage Logistics - Supplier Items | Transactional | An application to manage logistics of supplier owned , rental and non-stock items from base plant to remote plant.The non-stock items can be moved to stock after specific number of days which is configurable once received in base plant without sending to remote plant. The move to stock is also supported at the remote as well as when recieved back at base. Ad-hoc items are free flowing items which is created without the purchase order or maintenance order. |
| F5786 | Pack Container | Transactional | An application in Field Logistics to pack the outbound delivery items, handling unit into a container, seal the container and issue the items. Kit is a logical grouping of components required to perform a maintenance operation at a demand plant. A kit could include stock, non-stock, or rental items. Once the delivery for outbound process is fully picked, they can be assigned to a suitable container. The delivery items, handling unit and kit items should be able to assign single or multiple voyage.. |
Manage Logistics - Supplier Items
Business Role: Receiving Specialist (Oil & Gas)
This feature enables you to perform the Move to Stock process for multiple movement types, such as 501, 501K, 561,552, and so on.
Pack Container
Business Role: Warehouse Clerk (Oil & Gas)
With this feature you can view the outbound deliveries that are picked and ready for loading or packing into a container. The status can be set to allow the packing to assign the deliveries to an existing Field Logistics container . You can also include a step for sealing to record upto to 5 seals for the packed container. Trigger the goods issue for all deliveries in the container.
Fields (3)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | FldLogsRemotePlant | plant | Valuation Area | |
| PlantName | _RemotePlantText | PlantName | Plant Name | |
| SupplierPlant | reswk | Supplying Plant |
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 I_FldLogsUserPlant.
-- 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.
-- SQL view name: IFLUSERPLANT
CREATE VIEW I_FldLogsUserPlant AS
SELECT
plant AS FldLogsRemotePlant,
_RemotePlantText.PlantName AS PlantName,
reswk AS SupplierPlant
FROM flog_plantusr
LEFT OUTER JOIN I_Plant AS _RemotePlantText ON FldLogsRemotePlant = _RemotePlantText.Plant -- association [0..1]
;
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