Hierarchy
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services⤷
IS-B-PA-STC (Application Component) Single Transaction Costing⤷
JBT (Package) Application development IS-B Transaction Costing
IMG Activity
| ID | JBT_FTP_CALCULATR_PA | BAdI for Procedures: Weighted Independent Tranches |
| Transaction Code | S_PLN_62000790 | (empty) |
| Created on | 20040707 | |
| Customizing Attributes | JBT_FTP_CALCULATR_PA | BAdI for Procedures: Weighted Independent Tranches |
| Customizing Activity | JBT_FTP_CALCULATR_PA | BAdI for Procedures: Weighted Independent Tranches |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | JBT_FTP_CALCULATR_PA |
Use
You can choose the Weighted, Independent Tranches procedure as the opportunity interest procedure in the costing rule. You can then make further, extensive settings for this procedure in the costing rule. The Business Add-In allows you to refine these settings at single transaction level.
The Business Add-In implementation is called for several transactions that are assigned to the same costing rule.
You use the Business Add-In implementation to change the changing parameters. The Business Add-In is provided with additional input parameters from which the system can derive the tranche setting using the implementation. If these input parameters are not sufficient, you can read user-defined Customizing tables in the Business Add-In. Because you can call a Business Add-In for several transactions at the same time, this does not usually have any negative effects on performance.
In the changing table CT_TRAN_FTP_TRANCHE_CUST of the interface for the method CHANGE_FTP_PARAMETERS, the settings listed in the costing rule are transferred to the implementation. This changing table contains in turn two tables from the tranches for each transaction; one for the transaction currency, and one for the local currency. The local currency table is, however, only filled if the currency translation contribution is calculated and a separate opportunity interest rate setting exists for the transaction currency and the local currency.
The implementation only changes the parameters of the tranche that cannot be set at costing rule level. The parameter tranche number (TRANCHE_NR) must not be changed. Similarly, you must not change the sequence of the tranches. This is because the system requires the tranche numbers to be arranged in descending order.
Because the Business Add-In implementation uses the operating concern as a filter, you can carry out different implementations for each operating concern.
Tranche Parameters
In comparison to the settings available in the costing rule, the Business Add-In has several tranche parameters. The mark ups or mark downs for the opportunity interest rate (MARKUP_FTR), the fixed opportunity interest rate (FIXED_FTR) and the interest calculation method (INTEREST_METHOD) all belong to these parameters. The interest calculation method is particulary important to the fixed opportunity interest rate. If the method and the interest rate have been specified, then interest is calculated on volume together with them. The fixed interest rate means that you do not have to specify a reference interest rate or a yield curve. If you have already filled out these parameters, you must delete them before you can use the fixed interest rate. If the fixed interest rate is filled in the Business Add-In, but the yield curve has not been deleted, the system ignores the fixed interest rate and automatically reads directly from the yield curve.
Furthermore, the Business Add-In has the following optional tranche parameters: End Date of Adjustment (ADJUSTMENT_END_DATE), Reference Date of Adjustment (ADJUSTMENT_REFERENCE_DATE) and Reference Time of Adjustment (ADJUSTMENT_REFERENCE_TIME). If you fill in the End Date of Adjusment and the Step Range of Adjustment, no date of adjustment exists after the end date. If you enter a specific date as the Reference Date, then the system uses this date as the reference date. In this case, it is not necessary to have several adjustment dates because the interest rates are calculated with reference to this date. If you fill in the Reference Time of Adjustment, the system always reads from the yield curve at this particular time (instead of at the standard time of 23:59:59).
You can derive the meaning of the remaining tranche parameters from their respective tranche settings in the costing rule.
The tranches from the change table of the interface have the Use Business Add-In for Weighted Independent Tranches (USE_FTP_CALCULATOR_BADI) parameter. During the Business Add-In implementation you must make sure that the tranches, for which this parameter is not set, are not modifed.
Requirements
Standard settings
Activities
Example
method if_ex_jbp_ftp_calculatr_pa~change_ftp_parameters.
data:
t_opportunity_conditions type jbp_tab_fo_oc.
field-symbols:
<tran> type jbp_str_tran_ftp_tranche_cust,
<tranche> type jbp_str_ftp_tranche_cust,
<costing_data> type jbp_str_costdata,
<oppcond> type jbp_str_fo_oc,
<oppconditem> type jbp_str_fo_oc_pos.
loop at ct_tran_ftp_tranche_cust assigning <tran>.
read table it_costing_data assigning <costing_data> index sy-tabix.
loop at <tran>-t_ftp_tranche_cust_trans_curr assigning <tranche>
where use_ftp_calculator_badi <> ''.
if <tranche>-tranche_nr = '1'.
* Find the Most Recent Opportunity Condition
t_opportunity_conditions = <costing_data>-fo-oc.
sort t_opportunity_conditions by hdr-dguel_kk descending.
read table t_opportunity_conditions assigning <oppcond> index 1.
if sy-subrc <> 0. <tran>-error_found = 'X'. exit. endif.
* Find the Most Recent Opportunity Condition Item
sort <oppcond>-pos by dguel_kp descending.
read table <oppcond>-pos assigning <oppconditem> index 1.
if sy-subrc <> 0. <tran>-error_found = 'X'. exit. endif.
* Set Individual Term from Opportunity Condition Item
<tranche>-interest_term_nr_units = <oppconditem>-nozgew.
<tranche>-interest_term_unit = <oppconditem>-xozgew.
endif.
endloop.
if <tran>-error_found <> ''.
call function 'ISB_DETAILPROT_MESSAGE'
exporting i_objnr = <tran>-object_number
i_severity = 'E'
i_arbgb = 'J2'
i_msgnr = '745'
tables i_sprot_k_tab = ct_error_log
exceptions others = 1.
endif.
endloop.
endmethod.
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-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 | JBT_FTP_CALCULATR_PA | 0 | I070004707 | Single Transaction Costing |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20040707 |
| SAP Release Created in | 500 |
