SAP ABAP Data Element COO_CP1FN (CO obj. planning: FM name to complete UP table (costs))
Hierarchy
BBPCRM (Software Component) BBPCRM
   CRM (Application Component) Customer Relationship Management
     CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       KPLA (Package) Cost Accounting, planning RK-S
Basic Data
Data Element COO_CP1FN
Short Description CO obj. planning: FM name to complete UP table (costs)  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type FUNCNAME    
Data Type CHAR   Character String 
Length 30    
Decimal Places 0    
Output Length 30    
Value Table TFDIR    
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  
Medium  
Long  
Heading  
Documentation

Definition

FUNCTION '<COO_CP1FN>'
IMPORTING
I_KOKRS LIKE TKA01-KOKRS
I_GJAHR LIKE COBK-GJAHR
I_VRGNG LIKE TKA04-ACTIVITY
TABLES
T_COIOB STRUCTURE COIOB
T_COKA STRUCTURE COKA
T_COKAU STRUCTURE RKSTA
T_COKP STRUCTURE COKP
T_COKPU STRUCTURE RKSTA
T_COKS STRUCTURE COKS
T_COKSU STRUCTURE RKSTA

  1. The function module parameter is optional. Using this, the application can enhance fields within the control segments to be posted, or add its own segments.
    However, you cannot change fields used in CO Planning, or remove control segments.
    This applies to control segments for cost element planning, including activity inputs.
  2. The function module name <COO_CP1FN> is freely definable.
  3. Parameter I_KOKRS contains the set controlling area.
  4. Parameter I_GJAHR contains the fiscal year for the control segments.
  5. Parameter I_VRGNG contains the transaction for the control segments.
  6. Table parameter T_COIOB contains the integration data for all object numbers that occur.
  7. The table parameter contains the control segments that are definitely to be posted, which can be used as the basis for enhancements.

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