FTR_CREATE FWTR109 REPO No accrued interest flowtype defined for +/- sign +

Hello
In transaction FTR_CREATE / TRP01 for a repo without colleteral transfer 73B transaction type 200 flow type 2001 Repo: Spot Sale and 2002 Repo: Forward Purchase I get following error:
No accrued interest flow type defined for +/- sign +
Message no. FWTR109
Diagnosis
The system tried to determine a flow type for an accrued interest flow. But there is no appropriate flow type defined in Customizing for this transaction type.
System Response
Further processing is not possible.
Procedure
Assign an accrued interest flow type to the current transaction type in Customizing."
How do I do this?
regards
Arjan
Edited by: Arjan Hogenes on Dec 8, 2009 6:36 PM

Many thanks!
I think I got one step further.
I now get the error
Per 03.12.2009 a negative balance of       20.000.000,00- EUR Nominal exists
Message no. TRQ0001
Diagnosis
This is the position that is characterized by the following details:
CC=BOO1;CV=0001;PT=04I;SA=SECACF;SE=GO82
Explanation of the abbreviations used:
AC Accounting code
PT Product type
VA Valuation area
VC Special valuation class
CV General valuation class
CC Company code
SE Security ID number
SA Securities account
AG Securities account group
PF Portfolio
LC Loan contract
PA Futures account
Procedure
Check the position for key date 03.12.2009 with the Position List for Quantity Ledger Position function."
When I check the quantity ledger I can see the position of 20.000.000,-?

Similar Messages

  • BOND purchase : accrued interest calculation in amortization log

    hello,
    When purchasing a bond, accrued interest is to be paid on top of the clean price.
    Common market practice for day counting of accrued interest is : value date of the purchase - previous coupon date, meaning that the purchaser paid to the seller the coupon days upto but not including the purchase day (seems obvious). Hence, in the transaction in SAP we DE- flag "include" for the calculation date => we are in line with the broker's confirmation.
    We use SAC amortization (with correction for accrued interest).  In the amortization log, we notice that the accrued interest SAP takes on the acquisition date INCLUDES the coupon day of the acquisition date (contrary to what is in the transaction details) , which influences the effective interest rate, which obviously is on its turn not in line with the effective interest rate in the deal (which is the right one, taking into account the correct accrued interest pad to the seller).
    NOTE 1252576 is implemented.
    Questions.
    1. How can I influence (via custo or master data ) the accrued interest calculation as displaid in the amortization log
    2. Are any settings in FWZZ I should double-check ?

    Hello Carl,
    accrued interest adjustment in amortization procedure is used to leverage the effect of interest coupon payments, so it calculates in the same way as interest accruals in TPM44. This is not the same as accrued interest in TS01.
    In TS01 you can define it with the flag, how accrued interest is calculated, but TPM1 calculates always inclusive.
    Otherwise it may lead to inconsistencies.  For example, if you would have two purchases of the same ID and in one deal you set the flag, but in the other not, so which deal should TPM1 consider?
    Still, with the note 1602748 a BAdI method is provided to manipulate the accrued interest adjustment amount.
    Though at the end, why do you need to amortize with accrued interest adjustment? This is not required by IFRS.
    BR,
    Tomislav

  • Need to find BAPI or Function module to calaculate Accrued Interest

    HI All,
      CAn you please help me find BAPI or FM to calculate accrued interest with tcode FTR_EDIT for company code and transaction with cash flow details based on key date user gives. I need to takk all amounts less than key date on selection screen and get transaction details with interest rate and calculate number of days multiply it and then divide by 360 days.
    my formula is like this,
       Principal Amount * Interest rate * Number_ofdays/360.
    The logic is like this ,  Single Key Date -> Multiple Company codes -> Multiple transactions per company code ->multiple payments per transaction with credit/debit indicator.
    But when I run the report with one company code I should get multiple transactions with multiple paymetns calculated  accrued interest.
      After spending lot of time on finding function modules my Treasury functional team asked me to write manual formula to do this, but it works fine when I run for one transaction in one company code. IT's not working in all scenarios.
      I think manual calculation won't be accurate in all cases.
    As I am new to Treasury module, having difficulty to do this.
    Thanks,
    Thanvi.

    check with T-code TPM44
    zashok

  • Accrued Interest

    Which formula should I use when I need to calculate the accrued interest on my Student Loans.
    The payments are deferred so the interest is compounded on the principal balance, how do I get Numbers to calculate the interest?
    I have values for the months that have past, the principal balance, and the interest rate.
    Thanks for any help!!

    Chris,
    I think the function you want is FV. If I understand this correctly, you have a loan on which you have paid nothing to date. FV() will calculate the total amount due after a given number of payment period. Subtracting the original amount borrowed will tell you the amount of interest you are paying.
    In the test table below, $1000 was borrowed three and one-half years ago and 7% interest is compounded semiannually (3.5% per period). The compounded amount is calculated in column B for each period. Then the FV() function is used to verify its valid use here. See also FV in Numbers Help.
    So you have two ways to find the interest given here. Mine is a simple example. I dread to think what your interest amount will be.
    Formula in B3 and down: =1.035*B3
    Formula in C7: =FV(3.5%,7,0,-1000)
    pw

  • My app went from working fine to: Id field not defined for cfc Path.to.my.ORMCfCPag when I restarted

    Hi everyone,
    I have a CF9 ORM problem that I haven't been able to figure out and thought I'd see if you had any idea. I have seen a few postings talking about a "similar" problem but none of them correctly resolved this particular issue. I appreciate any help you can offer.
    I recently created a CF9 app where I generated scripted ORM CFCs for my app using ColdFusion Builder. It worked great and my app was completely working. However, when I was adding some enhancements, I ran into an error when I restarted the CF app server. Here's the message I keep getting:
    "Id field not defined for cfc Path.to.my.ORMCfCPage. Either the table should have a PK column mapped to a cfc field OR at least one field should be specified as id."
    My App.cfc file only had orm enabled (no other mappings) when it was working. I've since tried specifying things like the cfc location etc. and it still hasn't helped.
    // MORE DETAILS:
    - When my app was working, I had moved it to 2 other servers. I had this error on both of those but not on my local copy. They all use the exact same database.
    - The last change I made before the error was adding a generator="identity" field to my generated ORM beans. Once I got the message, I tried changing it back and restarting again but still got the error.
    - I've also made sure all of the Adobe tags are in my web root (as suggested in a prior posting about this problem). I've search all over for a solution and nobody has a solution posted online that works so far.
    Do you have any idea why this is happening?
    Thanks!
    Jeff

    Quick thought and probably not relevant, but do you have this.ormsettings.savemapping set to true in your Application.cfc? I've fallen foul of this before - once CF has generated the hbmxml files and saved them to disk you can make all kinds of changes to your code which won't make a difference as it'll continue to read from the file versions, but only for certain properties and methods at times it seems.
    Long shot I know, but I found CF ORM to be a nightmare for seemingly random caching.

  • Payment order are not defined for extended withholding  tax

    Hi Gurus,
    Would you please help me with the message below. It appears on F110 when I try to pay a vendor open item with extended withholding tax:
    Message FZ626 -Payment orders are not defined for extended withholding tax
    In my company payment orders are created in F110 for accounts payable, as we use another ERP system (Baan) to perform the local accounts payments, and now I've just activated Extended withholding tax functionality With accumulation (necessary in Brazil) but I get this error.
    Is it not possible to user payment order with extended withholding tax + accumulation? I find it hard to believe...
    I've tried to unflag the payment order only for the payment method I'm using in FBZP t.code, but then no payment order were created but instead a payment document were posted with the withholding tax accumulation, but this is not the way we are working, and nothing is sent to Baan
    any help is welcome

    The payment method "Y" the option "payment order only" was marked?
    For a withholding tax type with accumulation in a company code with extended withholding tax payment
    methods that create only payment orders can´t be used. Payment orders can only be created only if there are
    no tax types with accumulation involved in the paid items of the payment run.
    The functionality extended withholding tax works fine for Brazil
    however, you can´t use the payment order with this functionality.
    Please, review your customizing for payment method 'Y" in transaction
    FBZP.
    Best regards,
    Leonardo Vedovelli
    FI Support Engineer
    SAP Active Global Support

  • Interest calculation only for open item for customers

    Hi, do you know how to calculate Interest calculation only for open item for customers?I do not want to see cleared   items. I have problem with customization.
    Best Regards
    Tom

    In the item interest calculation, you can tick the  'open items' for calculation of interest and also select the 'no cleared items'.
    Regards

  • Error : Excise modvat accounts not defined for GRPO transaction and U1 exci

    I have Created Impot PO, After Planned Delivery cost MIRO I am trying to Perform GR then its giving Error "Excise modvat accounts not defined for GRPO transaction and U1 excise group
    Message no. 8I402"
          I have already maintained GL account in "Specify G/L Accounts per Excise Transaction" for Excise group U1
          This problem is coming when Additional Duty on custom condition type JADC is maintained in "Maintain Excise Defaults" node in the column "ADC Cond" . If I remove JADC condition type from this place the this error is not coming but AED column is not fetching any value while doing GR.
    Please help me in this issue , still No answer
    Edited by: shiwanshu singh on Jan 28, 2009 10:26 AM

    Dear sir
    For GRPO have you maintained sub transaction Type IP for your excise group U1. If you not maintained pl maintain . and assign G/L account to modvat clearing account , the G/l account should be same as company code CVD account.
    Regards
    jrp

  • ERROR in MIRO : An exchange rate type is not defined for country IN

    Experts:
    When I try to enter the invoice received from the vendor, I am getting the following message.
    An exchange rate type is not defined for country IN
    Message no. FF802
    Can anyone provide me a solution for this?
    Thanks,
    Vijai

    This is the explanation given in note 974619 for the above error message
    Summary
    Symptom
    When you post an FI document, the system issues error message FF 801 or FF 802.
    Other terms
    Plants abroad, FF 801, FF802
    Reason and Prerequisites
    You use the 'Plants abroad' function.
    See Note 882132 for more information about this.
    Solution
    If the 'Plants abroad' function is active, additional fields appear when you maintain the country global parameters (transaction OY01, table T005):
    - Country currency       (Field WAERS)
    - Exchange rate type     (Field KURST)
    - Net discount base      (Field XSKFN)
    - Net tax base           (Field XMWSN)
    You must maintain the fields 'Country currency' and 'Exchange rate type'.
    Otherwise, the system issues error message FF 801 or FF 802.
    thanks
    G. Lakshmipathi

  • Excise modvat accounts not defined for EWPO

    Dear Experts,
    when I click on 'Balance Choose' tab in J1IIN, it is showing an error message "Excise modvat accounts not defined for EWPO transaction and 60 excise group.Message no. 8I402" though I have maintain 'Excise account assignment table'  in "Tax on goods movement>India>account determination>specify G/L accounts per excise transaction". I searched in that forum, but I didnt get no proper solution.

    Hi
    Check your entries
    'Excise account assignment table' in "Tax on goods movement>India>account determination>specify G/L accounts per excise transaction
    EWPO          CR Credit     CLEAR CENVAT clearing account
    EWPO          DR Debit     RG23AED RG 23 AED account
    EWPO          DR Debit     RG23AT1 RG 23 AT1 Account
    EWPO          DR Debit     RG23BED RG 23 BED account
    EWPO          DR Debit     RG23ECS RG 23 ECS Account
    EWPO          DR Debit     RG23SED RG 23 SED account
    regards
    Prashanth
    Edited by: Prashanth@SD on Apr 12, 2011 2:00 PM

  • Excise modvat accounts not defined for GRPO transaction and 58 Excise group

    Hi Experts,
    When i am doing Goods receipts for Depot for Subcontracting
    i am getting this error message .Excise modvat accounts not defined for GRPO transaction and  Excise group. For Depot no modvat. is there any configuration setting for depot. Please do needful.

    Hi,
    Please maintain
    Hi,
    go to SPRO
    Specify G/L Accounts per Excise Transaction
    SPROLogistics u2013 GeneralTax on Goods MovementsIndia Account Determination  Specify G/L Accounts per Excise Transaction
    Enter excise group -58
    ETT_ GRPO
    and G/L account
    G.Ganesh Kumar

  • Excise modvat accounts not defined for DLFC transaction and excise group

    Dear Experts,
    Iam raising this question after checking all the contents related to Sub Transaction type in SDN.
    My prob is: for raw material sales scenario i have created order delivery and invoice. For Invoice i have done account determination with a different G/L in VKOA. Now i have to create an excise invoice and the accounting entry for central ED on sales should go to different G/L account. for account determination i have done the following settings:
    Maintained Sub transaction type in
    IMG -> Logistics - General -> Tax on Goods movement -> India -> Basic Settings
    ->Maintain Sub Transaction types
    IMG -> Logistics - General -> Tax on Goods movement -> India ->
    Account determination -> Specify Excise Accounts per Excise Transaction.
    Here against DLFC sub transaction Type is maintained..
    Also
    IMG -> Logistics - General -> Tax on Goods movement -> India -> Account determination -> Specify G/L Accounts per Excise Transaction
    Here maintained Excise group with DLFC Company Code subtransaction type, chart of accounts and all required GL Account .
    But when the iam creating Excise Invoice in J1IIN and clicking on Subtransaction type-F4, no entries are shown. No values found is the message in green. Message no. DH801
    If i use subtransaction type and enter billing document and enter, the following error message comes:
    "Excise modvat accounts not defined for DLFC transaction and excise group"
    Iam unable to understand why the subtransaction type maintained is not showing in TCODE J1IIN?
    Regards

    For the error message DH801, please check note 840911
    Excise modvat accounts not defined for
           DLFC transaction and excise group"
    Please check  your G/L assignments "Specify G/L Accounts per Excise Transaction"
    thanks
    G. Lakshmipathi

  • Excise modvat accounts not defined for CAPE transaction and TS excise group

    Hi Guys,
    Suddenly we are facing issue during exicse invoice capturing with MIGO
    system is giving following error
    "Excise modvat accounts not defined for CAPE transaction and TS excise group
    Message no. 8I402
    While in Excise account assignment table CAPE is Linked to Modvat Clearing Account which is further liked to correct GL
    Can any one explain the cause of this issue Points will be awarded
    Regards,
    Ashish

    Hi
    Pls maintain the following:
    1. SPRO->Logistics General -> Tax on Goods Movements -> India -> Account Determination -> Specify Excise Accounts per Excise Transaction
    Pls note the Sub Tansaction type is IP for ETT CAPE.
    ETT  <b>Sub Trn Type</b>   DC Ind                Account Name
    CAPE     IP           CR Credit     ONHOLD CENVAT on hold account
    CAPE     IP           DR Debit     ONHOLD CENVAT on hold account
    CAPE     IP           DR Debit     RG23AED RG 23 AED account
    CAPE     IP           DR Debit     RG23BED RG 23 BED account
    CAPE     IP           DR Debit     RG23SED RG 23 SED account
    CAPE       IP                   DR Debit             RG23ECS RG 23 ECS account
    2. SPRO->Logistics General -> Tax on Goods Movements -> India -> Account Determination -> Specify G/L Accounts per Excise Transaction
    Check the G/L accounts for Excise Transaction Type CAPE and maintain the same G/L accounts for ETT CAPE with <b>Sub Trn Type IP</b>.
    Hope this clarifies.
    Thanks

  • Error - Excise modvat accounts not defined for DLFC transaction and 01 exci

    Dear All,
    Getting below error while  doing J1IIN - Posting Excise invoice for Sale.
    "Excise modvat accounts not defined for DLFC transaction and 01 excise group"
    I checked with the settings GL are assigned to for DLFC and 01 excise group.
    Is anywhere else I need to mantain the modvat GL
    Regards,
    Rakesh

    Check if you are using any subtransaction type along with excise transaction type.
    Excise group, ETT, company code, sub transaction type (if any), Chart of account, Modvat account (pls maintain all the entries over here) search for modavat clearing field and maintain it.
    BR
    Edited by: Sujoy on Jan 15, 2010 9:45 AM

  • VERSION 0 IS NOT DEFINED FOR FISACL YEAR 2007,

    i am learning SAP PP and i hv ides 4.7,
    now WHEN SAVING ORDER i.e DURING COST CALCULATION I GET A MESSAGE THAT VERSION 0 IS NOT DEFINED FOR FISACL YEAR 2007,
    ON ANALYSING IT LEADS TO T.CODE OKEV BUT HERE SYSTEM DOES NOT PERMIT TO CHANGE THE VERSION, BUT IN ECC 5.0 IT ALLOWS ,
    WHAT IS THE PROBLEM, CAN ANY ONE PL. HELP ME,
    analysis of error gives following message:
    Activation of the indicator is not permitted
    Message no. KT253
    Diagnosis
    You activated an indicator (Plan, Actual, WIP/results analysis or Variance calculation ) in the basic settings for version 1 in controlling area 1000. However, a higher order of settings (general version definition) prevents you from setting this indicator in version 1.
    Note
    The following should be taken into account when maintaining a version:
    In general version definition you decide whether a version is allowed for
    •     Panning (with the Plan indicator)
    •     Actual data update (with the Actual indicator)
    Note: In Overhead Cost Controlling, actual data is updated in operational version 0.
    Actual versions different from 0 are found at present only for delta versions in Activity Based Costing (CO-ABC), and when you work with parallel assesment ( additional versions):
    •     A data version from results and WIP determination manages (indicator WIP)
    •     Another version from variance determination manages (indicator Variance)
    •     A version for exclusive use (field exclusive application)
    You must maintain the version basic settings for each controlling area in which you want to update transaction data. General version definition restricts the settings possible for the controlling area:
    •     If general version definition does not allow plan and/or actual data update for version, this applies to the version in all controlling areas. If plan and/or actual data updating is allowed for a version in general definition, this can be reset for each controlling area separately (unmark the plan or actual indicator).
    •     Delta versions in ABC may not be used for parallel valuations in the actual; the same goes for versions with exclusive applications. In both cases, the valuation fields may not be maintained.
    To set indicators WIP/Results- or Variance-determination the following conditions apply:
    •     Both indicators may be set only during setup for the controlling area, when they are already established in the higher level general version definition
    •     If either indicator is already active in the data bank, then the actual indicator may not be subsequently activated
    •     If the actual indicator is inactive and either of these indicators is active, then the valuations in the corresponding versions and in version "000" must agree
    •     If the actual indicator is active, then both indicators must be activated
    Versions 0 and 1 are used regularly for various purposes by the system, which sets the following limitations/restrictions:
    •     Version 0 must always be available. It cannot be used exclusively. The plan and actual indicators must always be active.
    •     The actual indicator may not be activated in version 1.
    If these conditions are violated during version maintenance, error messages are issued. There are three types of error message:
    1. While maintaining the general version definition, you can only make changes if they do not violate the conditions outlined above.
    2. While maintaining the basic settings in the controlling area, the entries must remain consistent with the higher level entries.
    3. You want to maintain version 0 or 1. The restrictions outlined above apply.
    Use the "Extras" menu option to display the structure of the entries in the complex data object version:
    •     Select a version and choose Extras -> Version use.
    The SAP System shows which controlling areas use this version.
    •     Select Extras -> Versions in CO area
    This displays all versions used in the current controlling area.
    The subordinate entries in the hierarchy (settings for each fiscal year, strategic Activity-Based Costing: transactions for a delta versions) will also be shown for both cases.
    Procedure
    Do not activate the indicator, or change the higher order of settings in the general version definition.

    Raj,
    What are you trying to change?
    To me you are not suppose to make any changes, you need to select the version "0" and then hit "Settings for each Fiscal year" subfolder.... here you copy the settings of 2006 and change the year to 2007. This should resolve the problem.
    Regards,
    Prasobh

Maybe you are looking for