SAP ABAP Data Element PRTDIM (Partner field)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ GBAS (Package) FI-SL Customizing / integration / Basis
Basic Data
Data Element PRTDIM
Short Description Partner field  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type FDNAME    
Data Type CHAR   Character String 
Length 30    
Decimal Places 0    
Output Length 30    
Value Table DD03L    
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 Prtn field 
Medium 15 Partner field 
Long 20 Partner field 
Heading 10 Prtn field 
Documentation

Definition

This is the partner field of a field (such as PRCTR and PPRCTR).

  1. Use in allocation

If you have determined (in allocation Customizing in the "Partner object update" view for a summary table) that partner objects are to be updated, the partner object belonging to an object in the partner field is written in each summary record during allocation.

Example:

Cost centers (RCNTR) 1000 and 2000 distribute costs to cost centers 3000 and 4000.

After allocation, the following records would be in your summary table:

  • With partner object update:
    RCNTR SCNTR
    3000 1000
    3000 2000
    4000 1000
    4000 2000
  • Without partner object update:
    RCNTR SCNTR
    3000
    4000

The number of database records is thus twice as large with partner object update than without.

Note:

The system first searches the partner field from the "Integrated master data" view.

Afterwards, the system searches for additional partner objects using R/3 logic (that is, field data in the data dictionary). Here, all fields are filled in as sender fields, if they begin with an S and have a corresponding R field in the summary table definition (such as RBUSA-SBUSA).

  1. Use in rollup

Using this field, the internal business volume within an area can be eliminated during the hierarchial summarization.
Example:
Field: RBUSA (business area)
Partner dimension: SBUSA (sending business area)
If there are sender-receiver relationships between these two fields within an area, this internal business volume is eliminated during the rollup.

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