Join us in Chicago from Oct. 21-23 for this educational event

Register Now! 

Location:

Fairmont
Chicago, Millennium Park
200 North Columbus Drive
Chicago, IL 60601

At the event, SAP will provide you with the knowledge you need to truly understand its treasury management solutions and how they can benefit your organization.  You will also hear from treasury experts who will provide insight into how the solutions can leverage effective treasury management to empower your business to make better-informed decisions.

Hi,

Recently we came across a case where the CO number range were exhausted. This affected postings in various sub modules including treasury.

When i searched i couldnot find any blog for this but only some discussions hence summarising in total to help others.

The below are the possibilities of resolution in KANK :

• If there is no overlapping with other number intervals, you can simply increase the value for the interval upper limit. Number assignment is then continued at the current number level - In our case it was not possible as we have overlapping number ranges but this solution might help others.
• Assign the transaction to a different number range group in which the number interval for internal number assignment has not yet been exhausted. The next document number is issued from this interval. - we had no group in which number ranges were not in use hence created a new one as below.
• Create a new number range group with an interval in which no CO documentnumbers have yet been issued. Then, assign the transaction to this new interval.

           Creation of group

          Creation of number ranges

          Assigning the transactions to the new groups

Please add anything to this if missed. Hope this helps someone.

Regards,

Jyoti

Below is the checklist of settings for payment request generation in sap.

1. In the deal please check the payment request in marked as with in payment details tab
2. Create number ranges for payment requests
3. Define clearing accounts of receiving  banks

4. Define clearing accounts for payment requests for cross country banks

5. Complete config in F11CU

6. If there is still no payment request generated then check t-code FIBLFFP with the same parameters (House bank, GL Account,Payment method etc.); does it create a payment request. Else this will show you the error in your config which you can correct.

7.Check t-code F8BT which will display all open payment requests. If you double click it will show you the complete details

Now you can work with your F111 payments. I will show the steps soon.

Please add any additional details or issue if anyone has faced.

Regards,

Jyoti

Step : 1 - Create Group Category With Following Field Types and Fields

Path -

Group Category : Specify Numeric Group Category

Field Type : Specify user specific additional data type fields

• Customizable filed
• User - defined text filed
• Check box

Field : Specify technical field names of the screen fields for additional data

Fields with unrestricted use :

Technical Field Names                     -     Description

GS_VAL-001 to GS_VAL-011            -     Grouping Number 01 to 11

User defined text fields :

Technical Field Names                    -      Description

GS_FRTXT-101 to GS_FRTXT - 108 - User defined text field no 01 to 08

Checkboxes :

Technical Field Names                     -     Description

GS_CHKBOX-201 to GS_CHKBOX-210           - Check Box Number 01 to 10

Step 2 - Determine values for Group Category

Path :

Note : Values shown for group category is only for example how to use these fields according to the customer requirement.

Group Category 300

Group Category 301

Group Category 302

Step 3 - Customized fields in Business Partner

Customized field control through Business Partner Type (Coming Soon)

Customized field control through Business Partner Role (Coming Soon)

Traders are defined at:

IMG -> FSCM -> TRM -> TM -> General Settings -> Organization -> Define Traders

SAP Users are associated with Traders at:

IMG -> FSCM -> TRM -> TM -> General Settings -> Organization -> Define User Data

This customizing is used to default 'Trader' information during deal capture (FTR_CREATE/FTR_EDIT) based on current user (sy-uname).

Trader authorizations at the level of Contract Type or Product Category or Product Type or Transaction Type can be defined using TCode TBT1.

Data Model

List of Differentiation Terms & their applicability:

Data Model:

Coding References:

• For Differentiation Criteria applicability: Class CL_DIFF_RULES_TRL, Method READ_CRITERIA
• For Checking if IS-PS (Industry Solutions: Public Sectors) is active or not: Function Module  FM00_CHECK_ISPS

When doing posting in Treasury, you can generate FI document as usual. Also you can generate payment request in TRM and then do payment via F111 later.

In order to create payment request, you first need to make sure the relative  indicator is selected in the payment details.

In Transaction management, when you create a transaction in FTR_CREATE, you can set it in the payment details tab.
(For postings from position management, you also need to maintain it)

You can set the group and netting functionality here which can allow you to pay the requests generated from these transaction together, etc.

Then, you need to make sure the relative flow types allow payment request generation.

The customizing is under:

SPRO->Financial Supply Chain Management
          -> Treasury and Risk Management
          ->Transaction Manager
          ->Money Market(Foreign Exchanges, etc)
          -> Transaction Management
          -> Flow Types
          -> Define Flow Types

Here you can control the direction to create payment request, incoming and out going or both, even not allowed at all.

Another important point related here is the payment clearing account
When you do posting with payment request, the FI document will not debit  the bank clearing acount directly(it will be used in the payment program) but the payment clearing account. So you need to set a default clearing account for the posting.

It's set here:

SPRO->Financial Supply Chain Management

          -> Treasury and Risk Management

          ->Transaction Manager

          -> General Setting
          ->Payment Management
          ->Payment Request
          -> Define Clearing Account for Payment Requests

This clearing account is Company Code dependented as shown in the screen, so you need to maintain it for each Company Code.

The last one I  want to write is the bank clearing account PAYRQ-HKBHK which will be used in payment.

When generating payment request from treasury, the default G/L account set in the  master data of house bank- account(FI12) and account determination in the customizing are used together for bank clearing account.

If you have performance issue for transaction TPM1 - Valuation, you may consider the following points to improve it.

1) Update database statistics for related tables starting with:

SLDT_
TRCT_
TRGT_
TRILT_
TRLT_
TRLIT_
TRPRT_
TRACT_
DIFT_POS_IDENT

You can check in transaction SM50 which table is used.

2) Consider soft modification note 1122623. The code may has been included in the system version, but it has to be activated as described in the long text of the note. Futhermore, there have to be done index changes which might be a bit time consuming to activate. The note should improve the performance in the position management transactions, but please read the long text of the note carefully.

3) You may set parallel processing control for TPM1. The number of task 10 is a SAP default setting. You may set it to be 10 or higher in case you have many positions to process. Customizing path:

Financial Supply Chain Management

Treasury and Risk Management

Transaction Manager

General Settings

-> Parallel Processing Control

4) If the most time is spent during update of the derived business transactions, it is sufficient to use the offline processing for the derived business transactions. This will mean that derived business transactions will firstly stay as "not current"/"not updated". Afterwards the TPM27 has to be executed to update them. This will save lot of runtime in TPM1 and the TPM27 supports parallel processing as well.

The customizing is :

Financial Supply Chain Management
Treasury and Risk Management
Transaction Manager
General Settings
Accounting
Derived Business Transactions
Control of Processing of Derived Business Transactions

Alternative: If you don't want to have offline setting, you can use the update period for derived business transaction and set it to several months (1 or 2) in:

Financial Supply Chain Management
Treasury and Risk Management
Transaction Manager
General Settings
Accounting
Organization
Assign Accounting Codes and Valuation Areas

This will mean that you update the derived business transactions automatically, but only given number of months in the future. This will save the runtime as well. Every time derived flows are generated it will check the customizing take the current date plus the period and generate flows. If you later need the flows afterwards you have to execute TPM19 to generate the following flows. You can plan TPM19 as a regular job then.

These two proposals should speed up the TPM1 processing. The second one is a long term solution. The first one is interim to speed up TPM1.

Additionaly, when you encounter performance issue for other functionalities, e.g. TBB1, you may check the above points as well.

Related notes:

2053772 - Poor performance in TPM1 when selecting OTC transactions
2023161 - SAC: valuation reset not considered in Amortization log II

2010667 - Securities: system logic improvement II

1952964 - Enhancement of the log during parallel processing

1836890 - TPM1: Performance improvement of securities

1821679 - TPM1: Performance improvement of OTC deal selection

1777912 - Performance optimization for TPM1

For security positions, the following two kinds of flows will be generated:

1) Flows generated from transaction management (e.g.FTR_CREATE), the main flow, buy or sell; or the other flows.

Please review the customizing "Define Transaction Types". For "Automatic Determination" - Payment details, three options are available:

    1. From Standing Instructions, 2. From Securities Account

A Only from Standing Instructions

B No Automatic Determination

Standing Instructions for business partner are defined in tcode TBI1, you may create entries based on currency, enter detailed information, House bank, Account ID etc, then assign it to relevant products.

If you choose the first option - " 1. From Standing Instructions, 2. From Securities Account", for example the system is checking the standing instructions and if there nothing is found then the payment details from the Securities Account are derived.

2) Flows generated from securities account management, the condition based flow, e.g. nominal interest, dividend, final repayment.

The payment details defined in Securities Account master data (tcode TRS_SEC_ACC) will be used for this kind of flows during posting (tcode FWSO, FWZE, FWBS).

Related notes:

1798804 - BAPI_FTR_SECURITY_CREATE: Payt details from securities acct

1758341 - TS01 Problems in derivation of payment details

1752967 - FWBS:individual payment details for flows are not considered

1746850 - TS01 : Changing Payment Currency doesnt change Pmnt Details

1702718 - Payment details not being re-read on change of security acct

1643459 - TM: payment details can not be deleted for security deals

( SAP Online help for DBT)

Generally there are some points need to check.

1, DBT generating rule setting
  Under customizing:
     SPRO->Financial Supply Chain Management
         -> Treasury and Risk Management
         -> Transaction Manager
         -> General Settings
         -> Accounting
         ->Derived Business Transactions
         ->Control of Processing of Derived Business Transactions.

Offline or Status of Plan maybe set here. So you need to run
TPM18/TPM27 to check it.
  
2,position management procedure setting
    Sometimes the PMP used for the position is not correct.
    Or the customizing of PMP is incorrect.
 
3,Position Change Category setting
   For the orinigal business transaction which will generate the DBT
   flows, if the PCC is not set correctly or not set at all, DBT maynot be updated.

4,DBT generation period setting
  Under customizing
     SPRO->Financial Supply Chain Management
         -> Treasury and Risk Management
         -> Transaction Manager
         -> General Settings
         -> Accounting
         -> Organization
         -> Assign Accounting Codes and Valuation Areas

There are two fields there which can control the DBT generation period
for performance consideration. They also need to be checked.

Related Notes:

1653788 - Performance: Derived business transactions update period

1769446 - Performance: Derived business transactions update period II

2125958 - Derived Business Transactaions are not fully generated for securities positions

If you want to capture different profit center at portfolio level in financial transaction of treasury deals at the time of posting of deals. For these, you can set up derivation rule under Additional Account Assignment settings where source field is Company Code, Portfolio and Target fields: Profit Center.

The configuration steps:

Define Derivation of Additional Account Assignments (T-code -TPM_DERIVE_ACCNT)

IMG ->Financial Supply Chain Management -> Treasury and Risk Management -> Transaction Manager -> General Settings -> Accounting -> Link to Other Accounting Components -> Additional Account Assignments -> Define Derivation of Additional Account Assignments

Please define source fields and target fields.

Then please define the conditions as your business requirement.

After this, please maintain the rule values like below screenshots.

Create deal with Portfolio 1, and Company code 0001

Post the deal by transaction TBB1, you can see the field: "profit center" has been filled.

Related notes:

1755316 - TRAC: Business Area not filled from acct.assign.reference

1731454 - Profit Center determination using OTC portfolio not working

When Price index is defined in the master data of a bond (tcode FWZZ, Basic data tab), sometimes it is not clear how the system calculates the position amount for interest flows. I would like to explain it with an example.

Price Index definition, see customizing:

Financial Supply Chain Management >  Treasury and Risk Management > Basic Functions > Market Data Management > Master Data > Indexes > Define Price Index (table TIDX_PRICE_INDEX)

Index Values are defined in customizing:

Financial Supply Chain Management >  Treasury and Risk Management > Basic Functions > Market Data Management > Manual Market Data Entry > Securities and Indexes > Enter Price Index Values (tcode S_KFM_86000134)

Bond position is created and the cash flow is as below (TPM40):

How does system calculate the Amount in position currency for the interest flow with position value date 01.06.2005) ?

It takes the calculation date as value date, in this case it is 30.05.2005.

1) System will find the related low and high index comparing to this value date:

  wa_priceValueLow

  VALUE_DATE   20050515
  INDEX_VALUE  115.000000

  wa_priceValueHigh

  VALUE_DATE   20050615
  INDEX_VALUE  125.000000

2)  Get the number of days between the low and high index values:

    20050515 ~ 20050615, no.of days 31

3)  Get the number of days between the low index value and the value date:

    20050515 ~ 20050530, no.of days 15

4)  Do the interpolation:

        CALL FUNCTION 'FIMA_INTERPOLIEREN'
    EXPORTING
         
          I_X1          = 0
          I_X2          = nDaysBetweenLow_High         
          I_X3          = nDaysBetweenLow_ValDate
          I_Y1          = IM_LOW_INDEX_VALUE-INDEX_VALUE
          I_Y2          = IM_HIGH_INDEX_VALUE-INDEX_VALUE
     IMPORTING
          E_Y3          = floatIntPolIndexValue

E_Y3 = WRK_Y1 * ( WRK_X2 - I_X3 )

            + WRK_Y2 * ( I_X3 - WRK_X1 ).

WRK_Y1    1.1500000000000000E+02

WRK_X2    3.1000000000000000E+01

I_X3      15

WRK_Y2    1.2500000000000000E+02

I_X3      15

WRK_X1    0.0000000000000000E+00

-> E_Y3      3.7150000000000000E+03

Then E_Y3 = E_Y3 / ( WRK_X2 - WRK_X1 ).
                   = 3.7150000000000000E+03 / (3.1000000000000000E+01 - 0.0000000000000000E+00)
                   =  1.1983870967741936E+02 (float Intpol Index value)

5)   Do the rounding

1.1983870967741936E+02 equal to 119.838710000000

tmpIndexInRatio     1.1983871000000001E+02
tmpRatio                  1.0040000000000001E+02 (Ratio 100.40)

* Index value in No ratio
  indexNoRatio    = tmpIndexInRatio / tmpRatio.

                            = 1.1983871000000001E+02 /  1.0040000000000001E+02
                            = 1.1936126494023904E+00

a. index value in Ratio is rounded to 6 decimals:  119.838710;

b. Check the size of the base ratio, if it is between 100 and 1000 (in this case 100.40),  we add TWO more decimal than the rounding rule states, the real ratio would be rounded to 8 decimals: 1.193612650000.

6)  multiply the position currency amount with the index value

   <l_flow>-index_value =   l_index_value.
multiply <l_flow>-position_amt by l_index_value.

  <l_flow>-index_value  is 1.193612650000

Position amount of interest flow without index (index-clean) is 53000.00.

You will get the position amount of interest: 53000.00 * 1.193612650000 = 63261.47

Related class/method:

CL_STANDARD_CALCULATOR_TRS
    Method  INSERT_PRICE_INDEX

CL_TIDX_PRICE_INDEX_NEW_POS
    Method  IF_TIDX_PRICE_INDEX~GETINDEXFACTOR4DISTFLOWTYPE
    Method   INTERPOLATE
    Method   rounding

Related customizing:

Treasury and Risk Management

> Transaction Manager

> Securities >

Master Data

> Specific Class Data

> Settings for Special Types of

Securities

> Index-Linked Bonds

> Edit Price Index

Here contains the Price index definition, Update Type for Price Index, Values of Price Index. Please find more information in online help.

Related BADI:

BADI   TPM_PRICE_INDEX

Method:

               ADJUST_VALUE_DATE      Adjust Fixing Date (Central)

               ADJUST_INDEX_VALUE    Adjust Interpolated Value (Central)

               ADJ_VALUE_DATE_FOR_COND_FLOW    Adjust Fixing Date for Condition Flows

               ADJ_VALUE_DATE_FOR_DEAL_FLOW     Adjust Fixing Date for Main Transaction Flow

Hope this helps to understand the calculation logic.

What application in treasury can parallel process?

• Valuation (transaction TPM1/TPM2)

• Legacy Data Transfer (transactions TPM61/TPM62/TPM63/TPM64)

• Accrual/Deferral (transaction TPM44)

• Update Planned Records for Securities (transaction FWUP)

• Generate Derived Flows (transaction TPM27)

How to configure parallel processing?

Parallelization of treasury can be activated via customizing ->Financial Supply Chain Management ->Treasury and Risk Management ->Transaction Manager ->General Settings ->Parallel Processing Control (customizing view TRGV_PAR).

1. Choose New Entry.

2. Choose the Application.

3. Enter the Server Name.

4. Enter the Logon/Server Group.

5. Enter the Number of Tasks.

6. Enter the Package Size.

7. When you want to switch off the parallelization, you have to set the Parallelization Off/On indicator.

8. You can set the Allow User to Control Parallelization Parameters in GUI indicator.

9. Save your entries.

Related notes:

1705651 - SEC: parallel processing for planned record update

2044775 - TPM45: parallel processing

1945357 - Enhancement of Framework for Parallel Processing

Below is the checklist of settings for payment request generation in sap.

1. In the deal please check the payment request in marked as with in payment details tab
2. Create number ranges for payment requests
3. Define clearing accounts of receiving  banks

4. Define clearing accounts for payment requests for cross country banks

5. Complete config in F11CU

6. If there is still no payment request generated then check t-code FIBLFFP with the same parameters (House bank, GL Account,Payment method etc.); does it create a payment request. Else this will show you the error in your config which you can correct.

7.Check t-code F8BT which will display all open payment requests. If you double click it will show you the complete details

Now you can work with your F111 payments. I will show the steps soon.

Please add any additional details or issue if anyone has faced.

Regards,

Jyoti

The cash flow of a position may contain many derived business transactions. When the position is changed or the cash flow is recalculated, the system might recalculate all the derived flows,which will take a long runtimes, even cause something wrong.

You can set the derive transaction update Period in T-code SPRO under path:

Treasury and Risk Management -> Transaction Manager -> General Setting -> Accounting -> Assign Accounting codes and Valuation Area

Period for derived business transaction is generated automatically for a position and is to be updated on the database. To determine a standard end date for all positions, the period is added to the year of the period.

In case the setting is maintained, in some special cases might be required to generate the derived business transactions for the whole cash flow of the position.
In order to achieve the option Ignore update period rule is available in the transactions TPM19 and TPM27.

Treasury postings supply only one currency category by default. The document posting in T-code TBB1 or valuation T-code TPM1 in Transaction Manager does not post to 2nd local currency. Generally speaking, in TRM you will need a second valuation area with valuation currency 2^nd local currency. And depending on these settings you can use the amounts in this valuation area to fill the second local currency or to post to a separate ledger in New GL.

There are two possible solutions:

1. via note 1557972. This means
   
      - setup valuation areas for every local currency (lc1 and lc2)
   
      - switch message TPM_TRG219 to warning
   
      - setup additional ledgers at least for postings from TRM
   Then, as described in the note 1557972, the individual ledgers contain the valid information for one specific currency.
   
2. via BAdI TPM_ACCIF_TRAC and note 1441267. This means
   
      - setup valuation areas for every local currency
   
      - implement the BAdI, so that other local currencies are correctly updated
   
      - activate the soft modification from the note 1441267

   This means additional ledgers are not necessary in FI. The additional valuation area fills the second local currency.

If you create a deal, settle it and post it.

Post it by T-code TBB1.

In case you want to reverse some flows of the deal, using T-code FTR_EDIT, click the button of “Change”.

Then select the tab of “Cash flow”, click the Reverse button.

If you want to reverse the deal, using T-code FTR_EDIT, click the button of “Reverse”.

You will face a warning message,

You can ignore it by clicking “Enter”. Select the reverse reason, and save it.

By now, you have reversed flows and a whole deal in TRM. But if you want to reverse the related post documents in FI, you need reverse it
using T-code TPM10.

Postings to vendor accounts are not supported in TRM, only postings to G/L and customer accounts are supported.

If you need a posting to a vendor account for some reason,  you can use the BAdI TPM_ACCIF_TRAC (method ACCIT_EXIT) and replace some fields to create a vendor posting. Let us assume you post to customer in the moment, then you have to replace the following fields:

- BSCHL
- KOART
- KUNNR (set it to blank)
- LIFNR.

In standard postings to vendor accounts are not possible. The use of the BAdI is only a workaround to change the standard posting logic.
You will not find the field vendor in any reporting, not in the posting log nor in TPM20.

Please also note that the BAdI can be used if you do NOT create payment request, if you create payment requests than you may have to post to customer

or G/L account.

There are no plans to provide the vendor field in SAP standard.

Generally interest condition is set in the master data of security, FWZZ.
And the interest is posted after it's due. But sometimes interest is paid partially before it's due.
And I can think there are two options to do that.

Option 1:
Create a new condition type to reflect the partial interest paid.
For example, the interest should be paid on 31.12.2012, but there is partial
interest paid on 30.06.2012. So generally you can create a new condition in the master data for it.
And at the same time, to adjust the original interest condition which is due on
31.12.2012. But this needs to update all cash flow which use this
security, even different company codes. And sometimes it's not practical.

Option 2:
Just post one manual posting via FWBS to reflect the partial interest.
And when posting the real interest in FWZE, change the amount to the interest left.
But it's necessary to make the flow posting in FWBS relevant for accrual/deferral.

When you exercise the option with cash settlement, the settlement amount is calculated on the basis of the difference between the strike and market price.

Case 1, OTC Currency Option is a purchase deal, the flow with leading currency in FX deal has sign “-“.

System will check the underlying transaction, which is the leading currency.

Here the leading currency is EUR , following currency is USD (see Table TCURL). The flow for EUR has sign “-“ as the FX deal is Buy USD and Sale
EUR.

FTR_EDIT, press Exercise button (or Tcode TI86), the current exchange rate (1,318) with the system date will be filled automatically - table TCURR. The payment currency for cash settlement would be the following currency, in this example it is USD. Cash settlement amount will be calculated as below.

First, the difference between Strike and Market price is calculated:

Difference = Strike - Price: 1,350 – 1,318 = 0,032

Cash settlement amount = amount of leading currency flow * difference

                                       = 10.000.000,00 * 0,032
                                       = 320.000,00

This means you have underlying for sale 10.000.000,00 EUR, you can get 13.500.000,00- USD.

On Exercise date, for the sale 10.000.000,00 EUR, only 13.180.000,00 USD will be received. You purchased the Currency option, so you can get cash of the difference 320.000,00 USD in this case.

If you change the Price field (VTIZBMF71A-PRKKURS) manually, the payment amount will be recalculated.

If the manually entered price (e.g. 1,360) is larger than strike price (1,350):

Difference = Strike - Price = 1,350 – 1,360 = -0,010

When the difference is less than 0, the payment amount of cash settlement will be cleared. There is no cash settlement in the sense of the Word (as it should refer to a loss).

Case 2, OTC Currency Option is a purchase deal, the flow with leading currency in FX deal has sign “+“.

The underlying:

FTR_EDIT, press Exercise button, the current exchange rate (1,318) with the system date will be filled automatically.  To calculate the cash settlement amount with following currency, system checks the difference of strike price and current price:

Difference = Price – Strike: 1,318 – 1,350 = - 0,032

As it is less than 0, you will not get cash settlement amount. This means you have underlying for buy 10.000.000,00 EUR, you would like to pay 13.500.000,00- USD.

On Exercise date, for the buy amount, only 13.180.000,00 USD is needed, you cannot get any cash in this case.

If you change the Price to be larger than Strike, e.g. 1,360:

Difference = Price – Strike: 1,360 – 1,350 = 0,010

Cash settlement amount = amount of leading currency flow * difference                                        
                                        = 10.000.000,00 * 0,010
                                        = 10.000,00

This means on Exercise date, for the buy amount, 13.600.000,00 USD is needed, then you get cash of the difference 10.000,00 USD.

Case 3, OTC Currency Option is a sale deal, the flow with leading currency in FX deal has sign “+“.

Difference = Strike – Price

Cash settlement amount = amount of leading currency flow * difference

Case 4, OTC Currency Option is a sale deal, the flow with leading currency in FX deal has sign “-“.

Difference = Price – Strike

Cash settlement amount = amount of leading currency flow * difference

Related coding:

Program SAPMF73E,  MODULE (PBO) PREPARE_CASH_SETTLEMENT

Program SAPMF73E,  FORM CHANGE_CASH_SETTL