SAP ABAP Data Element NOSENDER (Flag for suppressing the partner object update)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ GALC (Package) FI-SL allocation
Basic Data
Data Element NOSENDER
Short Description Flag for suppressing the partner object update  
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 No prtnr o 
Medium 20 No partner objects 
Long 34 No partner objects update 
Heading 27 No partner object update 
Documentation

Definition

You should select this switch if you do not want to update partner objects for the table in question.

If the partner objects are to be updated (standard setting), an update is carried out for each totals record that was created by the allocation: for the sender object and for the receiver object.

This enables you to know precisely which object has been assessed/distributed to which object.

Example:

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

After allocation, the following lines would appear in your summary table:

  • With partner object update:
    RCNTR SCNTR Amount Debit/Credit
    3000 1000 100 D
    1000 3000 -100 C
    3000 2000 200 D
    2000 3000 -200 C
    4000 1000 300 D
    1000 4000 -300 C
    4000 2000 400 D
    2000 4000 -400 C
  • Without partner object update:
    RCNTR SCNTR
    3000 300 D
    4000 700 D
    1000 -400 C
    2000 -600 C

In this example, the number of data records is twice as large with partner object update than without it.

Note:

Only with partner object object are you assured that the total of all line items of an allocation document will equal (that is, the allocation document has a zero balance), since only in this case are the receiver and sender records stored next to each other in the document (see example above). If partner object update is not active, it may be that the reciever and sender are saved in different documents.

Procedure

Check whether you want to set the partner object update to inactive based on the requirements and restrictions listed above. If so, set the indicator.

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