SAP ABAP Data Element JBRKZEIT (Costing Event)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ JBA (Package) Application developmnet IS-B General Development
Basic Data
Data Element JBRKZEIT
Short Description Costing Event  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type JBRKZEIT    
Data Type CHAR   Character String 
Length 2    
Decimal Places 0    
Output Length 2    
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 Cost.Event 
Medium 15 Costing Event 
Long 21 Costing Event 
Heading 2 CE 
Documentation

Definition

In addition to the 'general' valuation strategy, which you can assign directly to the costing rule, you have the possibility of assigning further valuation strategies based on the business transaction event at which the costing calculation is triggered (this could be a loan rollover, or a type 2 cash flow disturbance, for example).

Various events are possible depending on the type of transaction and the procedure group.

Input values

  • General business transaction events
    • Transaction start
    • Current
    • Transaction end

      The events "transaction start" and "transaction end" are fulfilled when the corresponding transaction start or transaction end date falls in the period currently being costed. The business transaction event "current" always applies.

      In the events "transaction start" and "transaction end", the system uses the "transaction start" or "transaction end" date to check conditions 401 through 403 which can be used when the costing sheet is defined.

      With the "transaction start" or "transaction end" events, the "transaction start" or "transaction end" date is used as the valuation key date. With the event "current", the current costing key date is used as the valuation key date.

  • Cash flow-related business transaction events
    • Commitment
    • 1st fixed-term period
    • Settlement
    • Rollover
    • Type 1 cash flow disturbance

      The cash flow-related events are fulfilled when the corresponding cash flow was costed in the current period (this is also the period in which the NPVs are set).

      The system uses the validity date of the cash flow and the date of the last flow in the cash flow to check conditions 401 through 403 which can be used when the costing sheet is defined.

      The costing date of the cash flow is used as the valuation key date.

  • Event-oriented business transaction events
    • Payment
    • End of fixed-term period
    • Type 2 cash flow disturbance

      The event-oriented business transaction events are fulfilled when a corresponding event occurs in the current costing period.
      Conditions 401 through 403 cannot be used for event-oriented business transaction events.

      The date of the corresponding event (such as the date of the payment) is used as the valuation key date. If an event occurs several times within the period, the assigned valuation strategy is also called several times (together with the corresponding valuation event).

In the course of the costing run, the system first executes the fixed procedures, then the 'general' valuation strategy, then the event-related valuation strategies.

If the same value field is filled in several valuation strategies, the results are added together.

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