SAP ABAP IMG Activity JBP_BADI_AFLEXP (BAdI After Calling Flexible Procedures)
Hierarchy
☛ EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services
   ⤷ IS-B-PA-STC (Application Component) Single Transaction Costing
     ⤷ JBP_COST_BADI (Package) BAdIs in Costing Environment in Profitability Analysis
IMG Activity
ID JBP_BADI_AFLEXP BAdI After Calling Flexible Procedures  
Transaction Code S_PLN_62000769   (empty) 
Created on 20040604    
Customizing Attributes JBP_BADI_AFLEXP   BAdI After Calling Flexible Procedures 
Customizing Activity JBP_BADI_AFLEXP   BAdI After Calling Flexible Procedures 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name JBP_BADIS    

Use

You can use this Business Add-In within the costing process alongside the existing user exits.

You can use it to set up features that are otherwise not included in the standard system.

Requirements

Standard settings

The Business Add-In has the following properties:

  • It is dependent upon the operating concern, which is used as the filter for the BAdI.
  • It contaisn the Change Data method.

The Businss Add-In is based on the following structures and parameters:

  • Operating Concern

    The operating concern field is used as the filter for the BAdI. This means you can create your own separate BAdI implementation for every operating concern.

  • Costing Rule (JBP_STR_COSTRULE)

    This structure contains all the parameters that are needed to define the costing rule. For example, the type of transaction from a costing perspective (JBSGSART), and the costing rule category (JBSKALKT).

  • Costing Information (JBP_STR_COSTCTRL)

    This structure contains general control parameters for costing.

  • Costing Data (JBP_STR_COSTDATA)

    This structure contains the category and the ID for the transaction, and the transaction information that is not specific to one transaction category.

    The costing data structure is based on several substructures.

    • Transaction Key (JBP_STR_TRANSKEY)
      • This substructure contains the transaction ID (JBP_DTE_TRANSTYPE), the financial object number (JBOBJNR), and the internal key (JBP_DTE_INTKEY) and external key (JBP_DTE_EXTKEY) data elements. The structures used to identify the transaction key must not be changed. After calling the BAdI, the system compares the contents of the structures with the content that is displayed. If the two differ, an error message appears on the screen. To identify the transaction, SAP has provided a new domain (JBP_TRANSTYPE). Fixed values, such as 01 (variable transaction), 02 (loan) and so on are assigned to this domain to give it a unique identification. You create the internal and external keys by linking the key fields of the relevant transactions together (concatenation). The transaction key usually consists of several fields, but it is saved in just one field. For this reason, a key structure must be available for every transaction category so that the system can clearly assign the field contents from the external and internal keys to the structure, and fill the key components correspondingly. Similarly, the structure is used to assign the transaction key to the internal or external key. Note that you cannot use the CONCATENATE function, because the system does not recognise the space.
    • Transaction data (JBP_STR_TRANSCTRL)
    • Financial object data (JBP_STR_FO)
      • Financial object data is split into the following substructures:    
      General data (JBP_STR_FO_BASIC)
      This structure contains the company code, the product type, and the origin indicator of the transaction.
      Profitability Analysis part (JBP_STR_FO_PA)
      This structure contains information about the Profitability Analysis part of the transaction, for example, the bank product, the date of the last costing, and the costing rule.
      Profitability Analysis additional data (JBP_STR_FO_PAADD)
      This structure contains the necessary additional information about the Profitability Analysis part, such as the cash flow indicator and cash flow category, the reference rate and the various net present values.
      Commision fields (JBP_STR_FO_PROV)
      External key figures (JBP_STR_FO_EXTCHAR)
      This structure contains the key figure category and the validity date of the transaction.
      Opportunity conditions (JBP_STR_FO_OC_HDR)
      This structure contains the date for which the condition is valid, as well as the interest calculation method. The system provides the JBP_TAB_FO_OC_POS table to determine the item.
    • Mark-up and mark-downs for opportunity interest rates (table JBP_TAB_SPREAD and structure JBP_STR_SPREAD)
      • This table and structure specify the procedure for mark-ups and downs, the type of yield curve and the average opportunity interest rate according to the transaction currency and the local currency yield curves.
    • Cash flows (table type JBP_TAB_CF and structure JBP_STR_CF)
      • This table type and structure are divided into the following substructures:
      Cash flow header (JBP_STR_CF_HDR)
      The header information from the cash flow specfies the validity date of the cash flow, the category of the cash flow, the paid committed capital and the effective interest rate.
      Flows (table JBP_TAB_CF_FLOW and structure JBP_STR_CF_FLOW)
      This table and structure contain all the necessary information about the in- and outflows within a transaction, such as, for example, the flow type of the cash flow, the date of the flow in the cash flow, and the plus/minus sign in the flow.
      Cash flow disturbance type 2 (table JBP_TAB_CF_CFD and structure JBP_STR_CF_CFD)
      This table and structure contain important information if a type 2 cash flow disturbance occurs in a cash flow.
      Effective capital (table JBP_TAB_CF_EFF and structure JBP_STR_CF_EFF)
      This table and structure specify the effective capital at the time of payment and the net interest margin for the interval between the two payment dates.
    • Balances (JBP_TAB_BALANCE)
      • This table contains the balance date and the currency of the transaction, the accounting balance, and the value date balance.
    • Turnover (JBP_TAB_TURNOVER)
      • This table is divided into the structure Turnover (JBP_STR_TURNOVER) and the table turnover position (JBP_TAB_TOPOS).
    • Activity Based Costing (table JBP_TAB_ABC and structure JBP_STR_ABC)
  • Log (SPROT_K)

    The log is assigned to the transaction using the object number. A transaction is considered incorrect ('transaction with errors') by the system when at least one error message appears in the log.

Example

Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20040726 
SAP Release Created in 500