Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
NMED (Package) R/3MED: Medical documentation GSD
Basic Data
| Data Element | PCSTORELOC_2 |
| Short Description | Storage Using KPro |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| 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 | 10 | KPro |
| Medium | 14 | KPro |
| Long | 20 | KPro |
| Heading | 1 | K |
Documentation
Definition
By storing using KPRO you can use the infrastructure of the SAP Knowledge Provider. The Content Management Service (CMS) is an important service of the KPro. The central component of the CMS is the orientation towards and the openness for various types of storage media. The CMS therefore serves as an interface between content servers and the SAP system. In addition, the CMS enables the caching of documents via the integration of cache servers.
The concept of the SAP content server allows the integration of the SAP database and external content server. An external archive system is one possible characteristic of a content servers.
You can find a detailed description under Documentation: Basis --> Basis Services / Communication Interface (BC-SRV) --> SAP Knowledge Provider (BC-SRV-PKR).
Use
Dependencies
When storing using KPro, you should ensure that the KPro storage indicator is set in Document Type Customizing.
Example
History
| Last changed by/on | SAP | 20050409 |
| SAP Release Created in | 471 |
