Hierarchy
SAP_BS_FND (Software Component) SAP Business Suite Foundation⤷
AP-RC-BOF-CFN (Application Component) Business Object Processing Framework Configuration⤷
/BOBF/CONFIGURATION (Package) Business Object Processing Configuration
Basic Data
| Data Element | /BOBF/OBM_USE_PROXY_TYPE |
| Short Description | Use proxy data types in internal model |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | BOOLE | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 0 | |
| Medium | 0 | |
| Long | 0 | |
| Heading | 50 | Use proxy data types in internal model |
Documentation
Definition
An indicator that the proxy data type is also used in the internal model.
Use
The business object processing framework works on a data model that does not need to be equal to the proxy model. However, in some cases, a separate internal model such as the inclusion of a dependent object should not be created. In this case, the indicator should be set accordingly.
Dependencies
The direct usage of the proxy model is mandatory for dependent object nodes, but can be used in general for all nodes.
The usage of the proxy model is not possible or recommended for nodes with a persistence or database because the proxy types are structured and the attribute names might be too long. If this is not the case or the mapping to the persistency is done, then the buffer can work on the proxy types.
Example
It does not make sense to create an internal model in a transformed object to allow the proxy model can be used directly.
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 702 |
