Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
MG (Package) Application development R/3 material master prior to 3.0
Basic Data
| Data Element | PSTAT_D |
| Short Description | Maintenance status |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | PSTAT | |
| Data Type | CHAR | Character String |
| Length | 15 | |
| Decimal Places | 0 | |
| Output Length | 15 | |
| 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 | Status |
| Medium | 15 | Maint. status |
| Long | 20 | Maintenance status |
| Heading | 15 | Maint. status |
Documentation
Use
The maintenance status records:
- Which user departments may maintain a material master record of a particular material type
- Which user departments have already maintained the material master record at a particular hierarchy level
The overall maintenance status is made up of the individual maintenance statuses. The individual maintenance statuses have the following meaning:
User department Maintenance status
Work scheduling A
Accounting B
Classification C
MRP D
Purchasing E
Production resources/tools F
Costing G
Basic data K
Storage L
Forecasting P
Quality management Q
Warehouse management S
Sales V
Plant stocks X
Storage location stocks Z
Supplementary Documentation - PSTAT_D 0001
Procedure
Enter here the maintenance status indicator that you want to encode in the version nnumber.
Supplementary Documentation - PSTAT_D 0002
Use
You must choose the maintenance status of a screen in accordance with the fields on the screen (on all subscreens); that is, each field on the screen must have at least one of the maintenance statuses that the screen itself has. If not, an abend will occur when maintaining data on the incorrect screen.
Procedure
Examples
If you also include the field MARA-BSTME (order unit) on the Basic Data screen, you must assign status "E" for "Purchasing" to this screen too.
Dependencies
History
| Last changed by/on | SAP | 19981111 |
| SAP Release Created in |
