I_PhysInvtryReasonCode
Physical Inventory Reason Type
I_PhysInvtryReasonCode is a Basic CDS View that provides data about "Physical Inventory Reason Type" in SAP S/4HANA. It reads from 1 data source (t157d) and exposes 4 fields with key fields GoodsMovementType, ReasonForPhysInvtryDifference. It has 2 associations to related views.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| t157d | t157d | from |
Associations (2)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [0..1] | I_GoodsMovementType | _GoodsMovementType | $projection.GoodsMovementType = _GoodsMovementType.GoodsMovementType |
| [0..*] | I_PhysInvtryReasonCodeText | _PhysInvtryReasonCodeText | $projection.GoodsMovementType = _PhysInvtryReasonCodeText.GoodsMovementType and $projection.ReasonForPhysInvtryDifference = _PhysInvtryReasonCodeText.ReasonForPhysInvtryDifference |
Annotations (17)
| Name | Value | Level | Field |
|---|---|---|---|
| AbapCatalog.sqlViewName | IPIREASON | view | |
| AbapCatalog.preserveKey | true | view | |
| AbapCatalog.compiler.compareFilter | true | view | |
| AbapCatalog.buffering.status | #ACTIVE | view | |
| AbapCatalog.buffering.type | #FULL | view | |
| EndUserText.label | Physical Inventory Reason Type | view | |
| AccessControl.authorizationCheck | #NOT_REQUIRED | view | |
| ClientHandling.algorithm | #SESSION_VARIABLE | view | |
| ObjectModel.usageType.sizeCategory | #S | view | |
| ObjectModel.usageType.serviceQuality | #A | view | |
| ObjectModel.usageType.dataClass | #CUSTOMIZING | view | |
| ObjectModel.representativeKey | ReasonForPhysInvtryDifference | view | |
| ObjectModel.modelingPattern | #ANALYTICAL_DIMENSION | view | |
| ObjectModel.sapObjectNodeType.name | ReasonForPhysicalInventoryDiff | view | |
| VDM.viewType | #BASIC | view | |
| VDM.lifecycle.contract.type | #PUBLIC_LOCAL_API | view | |
| Metadata.ignorePropagatedAnnotations | true | view |
Fields (4)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | GoodsMovementType | bwart | ||
| KEY | ReasonForPhysInvtryDifference | grund | ||
| _PhysInvtryReasonCodeText | _PhysInvtryReasonCodeText | |||
| _GoodsMovementType | _GoodsMovementType |
@AbapCatalog: {
sqlViewName: 'IPIREASON',
preserveKey: true,
compiler.compareFilter: true,
buffering : { status : #ACTIVE, type: #FULL }
}
@EndUserText.label: 'Physical Inventory Reason Type'
@AccessControl.authorizationCheck: #NOT_REQUIRED
@ClientHandling.algorithm: #SESSION_VARIABLE
@ObjectModel: {
usageType: {
sizeCategory: #S,
serviceQuality: #A,
dataClass:#CUSTOMIZING
},
representativeKey: 'ReasonForPhysInvtryDifference',
modelingPattern: #ANALYTICAL_DIMENSION,
supportedCapabilities: [#ANALYTICAL_DIMENSION, #CDS_MODELING_ASSOCIATION_TARGET, #SQL_DATA_SOURCE, #CDS_MODELING_DATA_SOURCE],
sapObjectNodeType.name: 'ReasonForPhysicalInventoryDiff'
}
@VDM: {
viewType: #BASIC,
lifecycle.contract.type: #PUBLIC_LOCAL_API
}
@Metadata: {
ignorePropagatedAnnotations: true
}
define view I_PhysInvtryReasonCode
as select from t157d
association [0..1] to I_GoodsMovementType as _GoodsMovementType on $projection.GoodsMovementType = _GoodsMovementType.GoodsMovementType
association [0..*] to I_PhysInvtryReasonCodeText as _PhysInvtryReasonCodeText on $projection.GoodsMovementType = _PhysInvtryReasonCodeText.GoodsMovementType
and $projection.ReasonForPhysInvtryDifference = _PhysInvtryReasonCodeText.ReasonForPhysInvtryDifference
{
@ObjectModel.foreignKey.association: '_GoodsMovementType'
key bwart as GoodsMovementType,
@ObjectModel.text.association: '_PhysInvtryReasonCodeText'
key grund as ReasonForPhysInvtryDifference,
_PhysInvtryReasonCodeText,
_GoodsMovementType
}
/*+[internal] {
"BASEINFO":
{
"FROM":
[
"T157D"
],
"ASSOCIATED":
[
"I_GOODSMOVEMENTTYPE",
"I_PHYSINVTRYREASONCODETEXT"
],
"BASE":
[],
"ANNO_REF":
[],
"SCALAR_FUNCTION":
[],
"VERSION":0,
"ANNOREF_EVALUATION_ERROR":""
}
}*/
Learn More
- What Is a CDS View in SAP S/4HANA?
- Types of CDS Views: Basic, Composite, Consumption, and Transactional
- SAP Tables vs CDS Views — Key Differences
- Understanding Data Lineage in SAP S/4HANA
- VDM (Virtual Data Model) in SAP S/4HANA Explained
- CDS View Annotations — A Complete Guide
- 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