3659477 - System checks both Contract Date and Value Date when running TPM18 for Forex contracts - SAP S/4HANA Cloud Public Edition

When executing TPM18 (Post Derived Business Transaction) for a Forex Transaction (product category 600), if you enter the TRL date as the Contract Date of the Forex Transaction, TPM18 will select the respective Forex Transaction. This transaction will then appear on the subsequent screen in TPM18. However, after clicking the "Fix" button, no postings will be generated. This behavior can be perplexing, as TPM18 selects the Forex Transaction but does not produce any postings.

SAP S/4HANA Cloud Public Edition

1. Open the SAP TPM18 - Post Derived Business Transactions app.
2. Execute the Process for Forex Contracts using a TRL Date that matches the Value Date of the Forex Contract.
3. Observe that the system initially selects Forex Contracts where both the Contract Date and Value Date match the specified TRL Date.

When a Forex Transaction is saved, a derived business transaction is created in the TRM subledger using one of the Update Types: DBT_D161, DBT_D162, DBT_D163, or DBT_D164. The TRL date for this derived business transaction is set to match the Contract Date of the Forex Transaction. Consequently, when TPM18 is executed with the TRL Date specified as the Contract Date of the Forex Transaction, TPM18 selects the transaction because of the presence of this derived business transaction with a matching TRL Date. However, since this derived business transaction is not pertinent to postings, TPM18 does not generate any postings. Instead, TPM18 solely addresses the derived business transaction by fixing it. 

More details of this derived business transaction can be viewed through TPM13 (Treasury Position Flows - Classic).

TPM18, TPM13, Forex Contracts, Contract Date, Value Date, TRL date, Treasury position flows, Posting log , KBA , FIN-FSCM-TRM-AC-2CL , Position Management and Accounting (Public Cloud) , Problem