SAP ABAP IMG Activity SIMG_CFJB01JBG0 (Edit Operating Concern)
Hierarchy
☛ EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services
   ⤷ IS-B-PA-STC (Application Component) Single Transaction Costing
     ⤷ JBTC (Package) Customizing IS-B Transaction Costing
IMG Activity
ID SIMG_CFJB01JBG0 Edit Operating Concern  
Transaction Code S_KK4_13000055   IMG Activity: SIMG_CFJB01JBG0 
Created on 19990830    
Customizing Attributes SIMG_CFJB01JBG0   Edit Operating Concern 
Customizing Activity SIMG_CFJB01JBG0   Edit Operating Concern 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFJB01JBG0    

In this step you define the operating concerns you are going to use in your system.

First you need to enter a name for each operating concern. Then define the "attributes" and the "data structure":

  1. Attributes

    The attributes are client-dependent parameters. Their significance varies depending on the type of Profitability Analysis you are working in.

  2. Data structure

    Maintaining the data structure is the most important step when you define or change an operating concern. The data structure is stored as a table in the ABAP/4 Dictionary. All entries which you make to define the data structure are valid for all clients. If the operating concern is used in several clients, you only define the data structure once and then just have to specify the attributes in the individual clients.

    In costing-based Profitability Analysis, costs and revenues are sorted according to user-defined value fields.

Example

SAP delivers the operating concern 0MB1 as an example. This operating concern is not yet activated.

Recommendation

You can only delete existing fields from the operating concern if the database tables have not yet been created (i.e. the operating concern has not been generated). If you are not sure about the selected characteristics/value fields, save them without generating the operating concern.

Always use the characteristics in the field catalog if the required reporting criteriaharacteristics. Do not use your own characteristics if the field catalog already contains the characteristics you require.

Standard settings

Several essential characteristics are pre-defined in every operating concern e.g. company code, bank product or customer. You can also choose further characteristics from a field catalog e.g. branch or country. A further alternative is to define your own characteristics to provide a further breakdown of e.g. customer or product groups.

Most of the value fields determined in the fixed procedures within Single Transaction Costing are always available (e.g. NIM contribution, TP contribution and average volume). You can choose further value fields from a field catalog or define your own fields.

Independent of the fields you select, your operating concern structure will also contain certain fixed characteristics which are not immediately visible. You can display these fields within data structure maintenance by selecting Extras -> Fixed fields. In part, these fields are needed for internal processing. Do not change them under any circumstances. The fields with usage 'T' are technical fields which are not available for reporting but can be displayed within line item reporting. The fields with usage 'F' are generally also available for reporting. These fields can be deactivated by means of the segment level characteristics in Customizing however.

  • The following fixed characteristics are currently deactivated:
    • PSPNR WBS element
    • RKALRG Costing rule
    • RKAUFNR CO order
  • The other fixed characteristics which can be used for reporting are:
    • BUKRS Company code
    • GSBER Business area
    • KOKRS Controlling area
    • KSTAR Cost element (in particular for FI/CO postings)
    • PARTNR Partner
    • PRCTR Profit Center
    • RADKEY Transaction differentiation
    • RBPROD Bank product
    • VERSI Version
    • VRGAR Activity type
    • WERKS Plant (not required at present)

To supplement these fixed fields, you can define up to 50 other characteristics for your operating concern.

There are also a number of fixed value fields which are automatically included in the operating concern. These value fields are usually filled by the fixed procedures (depending on the costing rule). If you require further value fields for the costing procedures you have selected, you can add these by means of the 'Copy value fields' function. First take a look at the following lists.


  • The following value fields are fixed:
    • BDSVOL Average volume
    • BDSEFK Periodic effective capital
    • BZINBE Interest revenue
    • BOPPBE Opportunity income from trans.currency yield curve
    • BOPPHW Opportunity income from local currency yield curve
    • BZINKO Net interest margin contribution
    • BMARBW NPV of margin
    • BDIFBW Residual margin with regular withdrawal
    • BWTBBW NPV of currency translation contribution
    • BDSKBW NPV of average effective tied-up capital
    • BMKVOL Market volume on costing key date
    • BMKVLD Average market volume
    • BOPVOL Opportunity volume on costing key date
    • BVERKM Market value of sales in period
    • BKAUFM Market value of purchases in period
    • BRKUGW Realized price gains
    • BRKDGW Realized exchange gains
    • BRKUVL Realized price losses
    • BRKDVL Realized exchange losses
    • BSKUGW Unrealized price gains
    • BSKDGW Unrealized exchange gains
    • BSKUVL Unrealized price losses
    • BSKDVL Unrealized exchange losses
    • BOPKOS Opportunity costs
    • BHKOBE Trading terms contribution
    • AGESCH Number of single transactions
    • BERTRZ Revenue payments
    • BZINAG Interest expense
    • BOPPAG Opportunity cost from transaction currency yield curve
    • BOPPAH Opportunity cost from local currency yield curve
  • The following value fields can be filled automatically within costing. If you want to use these fields for reporting, you can transfer them to your operating concern using the 'Copy value fields' function:
    • BPROV1 Commission expense/revenue
    • BPROV2 Commission expense/revenue
    • BPROV3 Commission expense/revenue
    • BPROV4 Commission expense/revenue
    • BMARHW NPV (margin) according to local currency yield curve
    • BABRHW Settlement NPV (margin) acc. to local curr.yield curve
    • BMRKBW NPV of minimum reserve costs
    • BWATRA Currency translation contribution
    • BMINRK Minimum reserve costs
    • BLSMBW NPV (margin) with CF disturbance acc.to trans.currency
    • BLSMHW NPV (margin) with CF disturbance acc.to local currency
    • BRESBW Residual NPV of CF disturbance
    • BSTERG Disturbance result
    • BPRMBW NPV (margin) with rollover acc.to transaction currency
    • BPRMHW NPV (margin) with rollover acc.to local currency
    • BOPVLD Average opportunity volume
    • BZINKK NIM contribution - correction
    • BEINWE Initial value
    • AVERKS Number of sales in period
    • AKAUFS Number of purchases in period
    • BDISAB Discount accrual

Requirements

First maintain your organizational structures, in particular your operating concerns, in the Organizational Units global settings in the menus for general system settings. Also see the notes for the "Set operating concern" step.

If you have not yet set your operating concern in the global settings, you can do so here under New entries.

Activities

  1. Maintain the attributes by specifying the following parameters for the operating concern you have created:
    1. Currency
      2. If you are using costing-based Profitability Analysis, all of the amounts in CO-PA are stored in the operating concern currency.
      If you are using account-based Profitability Analysis, the system stores the data in the transaction currency, company code currency and controlling area currency. If the company code currency and the controlling area currency are the same, the system stores the object currency for each individual CO object (cost center, order, project, and so on) in place of the company code currency.
    2. Fiscal year variant
      3. The fiscal year variant determines the number of posting periods per fiscal year. Since each controlling area assigned to the operating concern - and each company code assigned to each of those controlling areas - can have its own fiscal year variant, the variant you choose for the operating concern must correspond to the other areas.
      If you want to change the fiscal year variant, you can only do so if the total number of periods increases, for example:
      from 12 posting periods + 2 special periods
      Business Attributes
      ASAP Roadmap ID 203   Establish Master Data 
      Mandatory / Optional 1   Mandatory activity 
      Critical / Non-Critical 1   Critical 
      Country-Dependency A   Valid for all countries 
      Assigned Application Components
      Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
      SIMG SIMG_CFJB01JBG0 0 I070004701 Profitability Analysis 
      Maintenance Objects
      Maintenance object type C   Customizing Object 
      Assigned objects
      Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
      KEA0 T - Individual transaction object JBG0 IS-B CO-PA: Maintain Operating Concern 
      History
      Last changed by/on SAP  20040113 
      SAP Release Created in