Derivation type "Derivation rule" works the following way: IF x THEN y.
Scenario: Depending on Product Groups different Profit Centers are assigned.
Header 1 | Header 2 | Header 3 |
---|---|---|
Security | PC80001 | Securities TRM department |
Loans | PC80002 | Loans TRM department |
OTC Transactions: Money Market, FX, Derivatives | PC80003 | OTC TRM department |
Listed Options / Futures | PC80004 | Option/Futures TRM department |
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 (tr. TPM_DERIVE_ACCNT)
In general screen of derivation press "Create step" button or F5.
Select "Derivation rule" step.
Enter Source field - PRODUCT_GROUP "product group".
Target fields - PRCTR "Profit center"
For your purposes you can use other fields
The full list of Source fields:
SOURCES | AA_REF | Account Assignment Reference of Position Management |
SOURCES | ACCOUNTING_CODE | Accounting Code |
SOURCES | ACCOUNT_GROUP | Securities Account Group |
SOURCES | ACC_SYMBOL | Account Symbol for Account Assignment Reference |
SOURCES | BP_RLTYP | BP Role |
SOURCES | BUSTRANSCAT | Business Transaction Category |
SOURCES | BUSTRANSID | Identifier of the Distributor Business Transaction |
SOURCES | CHART_OF_ACCOUNTS | Chart of Accounts |
SOURCES | COMPANY_CODE | Company Code |
SOURCES | CURRENCY_CAT | Currency Category |
SOURCES | DEAL_NUMBER | Financial Transaction |
SOURCES | DIS_FLOWTYPE | Update Type |
SOURCES | DOCUMENT_DATE | Document Date in Document |
SOURCES | DOCUMENT_TYPE | Document Type |
SOURCES | FLOW_NUMBER | Number of a Distributor Flow |
SOURCES | FUND | Fund |
SOURCES | GL_ACCOUNT | General Ledger Account |
SOURCES | GRANT_NBR | Grant |
SOURCES | IGT_STATUS | IGT: Status of an Intragroup transaction |
SOURCES | ISSUER | Issuer Identity Key |
SOURCES | KONTRAHENT | Business Partner Number |
SOURCES | LOANS_CONTRACT | Contract Number |
SOURCES | PORTFOLIO | Portfolio |
SOURCES | POSITION_ACCOUNT | Futures Account for Listed Options and Futures |
SOURCES | POSTING_CAT | Posting Category |
SOURCES | POSTING_DATE | Posting Date in the Document |
SOURCES | POSTING_KEY | Posting Key |
SOURCES | POSTING_PERIOD | Fiscal Period |
SOURCES | POSTING_YEAR | Fiscal Year |
SOURCES | PRODUCT_GROUP | Product Group |
SOURCES | PRODUCT_TYPE | Product Type |
SOURCES | RFHAZU | Transaction activity |
SOURCES | SECURITY_ACCOUNT | Securities Account |
SOURCES | SECURITY_ID | Security ID Number |
SOURCES | TRANSACTION_TYPE | Financial Transaction Type |
SOURCES | VALUATION_AREA | Valuation Area |
SOURCES | VALUATION_CLASS | Valuation Class |
SOURCES | VBUND | Company ID of Trading Partner |
The full list of target fields is
TARGETS | GSBER | Business Area |
TARGETS | PARGB | Trading Partner's Business Area |
TARGETS | PPRCTR | Partner Profit Center |
TARGETS | PRCTR | Profit Center |
TARGETS | PSEGMENT | Partner Segment for Segmental Reporting |
TARGETS | RMVCT | Transaction Type |
TARGETS | SEGMENT | Segment for Segmental Reporting |
TARGETS | VBUND | Company ID of Trading Partner |
TARGETS | XREF3 | Reference Key for Line Item |
And press "Maintain Rule Values".
Enter data from scenario table into Derivation rule.
------------------------------------------------------------------------------------
One of the usefull things is we can use Source fields intervals - button when you create Derivaton rules.
Example: Depending on Amount in Nominal Currency and Nominal Currency we assign Financial Transaction Type to newly created transaction from external systems.
IMG -> Financial Supply Chain Management -> Treasury and Risk Management -> Transaction Manager -> General Settings -> Transaction Management -> External Link -> Define Mapping for Spot Exchange and Forward Exchange Transactions (tr. FTR_XI_MAP_FXLEG)
------------------------------------------------------------------------------------
Let's get back to our first scenario about Profit centers. We are not using Conditions, so our derivation step will be executed always.
On "Attributes" tab we can define additional parameters: it's up to you to use this attributes.
You can choose attribute to specify for each derivation step whether an error message should appear if no target values are found. For derivation rules, this option is automatically set as the default setting. If you do not want to maintain derivation rule values for every possible combination of source values, you should deactivate this error message display.
If you activate this attribute, you can then make derivation rule entries for rules that have a "valid from" date.
This attribute is not required in general. It is only useful if you program, for example, a batch input for the data input transaction KEDE and want to directly access maintenance for a specific rule. To activate this attribute, right from general screen of Derivation choose "Goto -> Direct call using step ID". You can then enter one of the available step IDs.
The derivation step is ready. Save it.
Don't forget to Test it Derivation: Test your derivation steps.
For other Derivation topics reffer to TRM Derivation (index)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
2 | |
2 | |
2 | |
2 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 |