Hello GB
Thanks for your valuable input.
Suppose if we using money market or commodity (and not securities) then also valuation area 001 should be used or we can use other valuation area ( say for ex: Z01).
--
Deepak
Hello GB
Thanks for your valuable input.
Suppose if we using money market or commodity (and not securities) then also valuation area 001 should be used or we can use other valuation area ( say for ex: Z01).
--
Deepak
Hi Georgy,
no, 'Control of Calculation of Derived Bus.Transactions' is relevant to the method of calculation, though posting is a separate thing - you must always use Transaction TPM18 in order to post derived business transactions for foreign exchange transactions and OTC derivatives, even if you use the Online and Same Status function.
hope this will help you.
Kind regards,
Renatas
Please could someone tell me how do we retrieve the archived memos.
In FF7A I select the 'CONVERT' and it says the memo has been archived.
Thanks.
Hi Joilin,
Please see if this update type is maintained in your Securities Account (TC: TRS_SEC_ACC) . If not maintain and try again Let us know if it worked.
Cheers !
Adi
Hi,
In TPM40 for the ID and security account, do you see your dividend/interest flow? If yes what is the status of the flow?
If there is no flow in there, then check in security ID master in FWZZ whether the interest conditions are maintained correctly and if yes, pls run FWUP to update all the flows. Post this check in TPM40.
Regards,
Ravi
Hello Renatas,
I'm not sure that 'you must always use Transaction TPM18'.
There are two case of derived flows:
1) as we discussed above
2) derived flows for position outflows, calculated in transaction of security disposal (example - DBT_E001). Such flows are calculated automatically (with 'online' mode) and posted when you posts transaction of security disposal in TBB1. So in this case we don't need to use tpm18.
I guess the reason of such behaviour is:
1) base flow for HAC_B014 isn't fixed in TBB1 so the derived flow isn't posted too
2) base flow for DBT_E001 is posted in TBB1 so the derived flow is posted together with it.
What do you think ?
Buenas Tardes, alguien sabe por que SAP no soporta el costo amortizado para este tipo de productos ?
Saludos.
Gerardo
Hi Georgy,
I'm afraid your example with DBT_E001 is not very relevant to this discussion, as this specific Update type is not relevant to posting in standard configuration - these kind of Update types are required for position calculation purposes.
from my own experience, all posting relevant Derived flows (Update types DBT_*) are fixed (or posted) with the transaction TPM18.
Kind regards,
Renatas
we want to configure a Z reference category in back office, any SPRO path?
for sure, we are not using SAP standard one
update type is not maintained in master data level, it is assigned with condition type,
pls check with derivation
Reference categories are predefined. And there is no any SPRO path and configuration for new one.
As i wrote you - use REF.
Thanks !
Good morning, i would like to know if someone is aware about a possible solution for this limitations SAP has. I need to increase SAP 8 digits to at least 10 (ten) for money numbers. Thanks in advanced!
Hello, please help me with non-deliverable forward.
I've got forward product type with settlement indicator = Non-deliverable forward.
Next flow types are assigned to it (flow types have default settings):
1000 Buy foreign exchange Principal Increase
1031 Cash settlement Cash Settlement
2000 Sell foreign exchange Principal Increase
When I create Forward transaction with next conditions:
System generates cash flows, but flow 1031 have zero value;
What should I need to do to have flow 1031 = 1 750 000 RUB ??
Hi Georgy,
you have to execute 'Fixing' activity using trans. FTR_EDIT where the settlement amount or settlement exchange rate is entered and the cash settlement is calculated.
Kind regards,
Renatas
Hi,
as I read in SAP note 1779311, 'The highest amount the system can handle is 99.999.999.999,99 (11 digits + 2 decimals). It is not possible to extend the WRBTR/DMBTR fields lenght: the amount that you can insert into a document cannot be longer than 13 digits. These fields remain defined as CURR 13 digits in the BSEG (the most important table for the postings).'
there is also the solution proposed in this note how to overcome the issue if required.
Kind regards,
Renatas
Well, there is no any SPRO path, BUT!!! you can create reference category from table maintanance!
SE11 -> Table ATR1 (Renatas mentioned) -> Display -> Contents (Ctrl+Shift+F10) -> Execute (F8) -> Create (F5)
And you can use it:
By the way, a lot of configuration can be made through table mainantance in TRM!!!
Hello,
When i am trying to delete assignment of update type to Accrual/Deferral i am getting following error
:Table TRLIC_AD is not part of the Customizing object TRLIVC_AD C"
PLs help.