SAP ABAP Data Element PSTATART (Maintenance status determination type for data transfer)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ MGA (Package) Application development R/3 material master from 3.0
Basic Data
Data Element PSTATART
Short Description Maintenance status determination type for data transfer  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type PSTATART    
Data Type NUMC   Character string with only digits 
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 Det. type 
Medium 15 Determin. type 
Long 20 Determination type 
Heading 1 M 
Documentation

Definition

In data transfer, this key defines how the maintenance statuses of a material are determined on the basis of the fields transferred.

Use

This field is required only for data transfer, and only if you have not specified which maintenance statuses are to be created or changed during data transfer.

Note

The maintenance status of a field is stored in table T130F.

In material master maintenance, the maintenance status determines:

  • Whether a maintenance status can be created or changed
  • Whether the authorization exists to create, change, or display a material master record
  • How maintenance statuses not yet created are processed (writing of MOFF records for statuses not yet created)
  • What views are displayed in the Select View(s) dialog box in Display/Change mode (defined by the overall maintenance status)
  • What checks are made

From the data transferred, the system determines the combinations of material master table and maintenance status to be maintained. It does this for each maintenance transaction. You have the following determination types:

  • Determination type 1

    The maintenance statuses of all fields transferred are combined.

  • Determination type 2

    The maintenance statuses of all fields transferred are combined, except general fields for the client or plant.

    • A general field for the client has all maintenance statuses. Examples are the base unit of measure and the material group.
    • A general field for the plant has all maintenance statuses except basic data and classification. An example is the unit of issue.
  • Determination type 3

    The maintenance statuses of all fields transferred are combined that are assigned to a single maintenance status or that are MBEW fields.

    If other fields were transferred that cannot be maintained with the maintenance status determined in this way, they are used to determine a remaining maintenance status that is processed separately. If the required fields are not all transferred for one of these remaining maintenance statuses, and if the Check required fields indicator is not set, the remaining maintenance status concerned is not processed. The system displays a warning to this effect.

Determination type 3 is set in the standard SAP R/3 System.
This has the following consequences:

  • A maintenance status is not created if a single status field has not been transferred for it and if all other fields for the status are already covered by the creation of other maintenance statuses. This can also result in a complete table entry not being created (for example, MLGN/MLGT - only a single maintenance status).

    Normally, this has no effect since the maintained views of productively used materials contain sufficient entries.

  • If accounting data is transferred, the maintenance statuses Accounting and Costing are both created since all accounting fields have both maintenance statuses. (You must have sufficient authorization for this, otherwise only the status for which you are authorized will be created.)

    This is of practical value since there are two separate maintenance statuses essentially for authorization reasons. The data maintained in the Costing view is only proposed in the Accounting view.

  • If warehouse management data is transferred in another transaction separately from the relevant plant, the corresponding MARC is not given the maintenance status Warehouse Management.
  • If document management is active and if document data fields are transferred, they are included in table MARA. This contrasts with the old batch input method, where this was not possible due to either the documents subscreen or the MARA drawing fields subscreen being active.

During data transfer, the screen sequence determined is used to establish the determination type. The screen sequence is in turn determined by the following influencing factors:

  • Transaction code
  • User
  • Material type
  • Industry sector

Procedure

Examples

With determination type 1, the following maintenance statuses are created if you maintain any particular screen and do not specify any organizational levels:

  • Basic data
  • Purchasing
  • Storage
  • Sales

All required fields must be maintained at client level.

Dependencies

If, for a material master table, one status has been transferred completely, and another not, since it is incomplete, the incomplete data is stored in the table nevertheless, since the entry has already been considered. See the documentation for the indicator Check required fields not belonging to the core maintenance status.

See also

In the SAP library:

  • On direct input:

    CA Data Transfer Workbench -> LO Logistics General -> LO Material Master Data: Data Transfer Workbench

  • On Application Link Enabling (ALE)
    • CA ALE Introduction and Overview
    • CA ALE QuickStart
    • CA ALE Programming

History
Last changed by/on SAP  19971006 
SAP Release Created in