Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
LO-INT-TRM (Application Component) Treasury and Risk Management Integration⤷
LOG_TRM_INTEGRATION (Package) Log. & TRM Integration
IMG Activity
| ID | LOG_TRM_INT_RELBADI | BAdI Implementation: Relevance Determination for Logistics-TRM Integration |
| Transaction Code | S_EBS_44000446 | (empty) |
| Created on | 20110419 | |
| Customizing Attributes | LOG_TRM_INT_RELBADI | BAdI Implementation: Relevance Determination for Logistics-TRM Integration |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | LOG_TRM_INT_RELEVANCE_BADI |
Use
In the context of Treasury and Risk Management integration, this filter dependent BAdI may be used to determine and set the relevance of purchase order/sales order items and purchase contract/sales contract items from Logistics for integration with Exposure Management 2.0 in Treasury and Risk Management.
The TRMRISK_RELEVANT field is a key prerequisite for the follow-on functions for the transfer of exposures to TRM.
Relevance determination is carried out via the default implementation for MM purchase orders (LOG_PO_COMMODITY_RELEVANCE), MM purchase contracts (LOG_MM_CTR_COMMODITY_RELEVANCE) and sales orders and sales contracts (LOG_SO_COMMODITY_RELEVANCE). The default implementations check that at least one item condition type is assigned to a commodity ID in table L2TC_CONDICOMM. In addition, there are SD and MM specific checks:
- SD specific checks
In the SD specific implementation, the following checks are performed:
- Sales order items (VBTYP = 'C' and VBKLT = SPACE) are set as relevant for TRM integration only if delivery related billing (FKREL = A, H, J or M) is selected.
- Sales contract items (VBTYP = 'G' and VBKLT = SPACE) are set as relevant for TRM integration only for a quantity contract (target quantity > 0) that is not relevant for billing (FKREL = SPACE).
- MM purchase order specific checks
The MM implementation checks if price date category of the PO item = #GR date#.
For MM, the complete functionality of Treasury and Risk Management integration is available if the PO item has price control type = #5# (ekpo-meprf), which means an additional raw exposure can be created at goods receipt, replacing the corresponding PO-based raw exposure.
In some business scenarios, repricing at goods receipt is not required. In such cases, the integration of purchase orders without price date category = #GR date# can be achieved by overwriting the default implementation and setting PO items as TRMRISK_RELEVANT when price date category is <> #GR date#. Note, however, that certain restrictions apply when you use the Treasury and Risk Management Integration with price date category <> #GR date#:
- Only purchase order items write a raw exposure. The complete item quantity is always relevant, independent of already delivered quantity or final delivery flag. If the goods receipt quantity is > 0, the raw exposure gets delivery status set to #delivered#. If the invoice quantity is > 0, the raw exposure gets invoice status set to partially/finally invoice. The raw exposure activity type (firm, asset/liability) is not changed.
- Goods receipt does not write a raw exposure. Thus, the corresponding purchase order raw exposure quantity remains in place.
- MM purchase contract specific checks
The MM purchase contract implementation checks for document category = #K# contract whether the item category = #0# normal, and whether the item is not flagged for deletion and not flagged for return.Note, that a contract based raw exposure will be only created if a risk distribution plan is assigned to the respective contract item.
Further information
MM specific checks for relevance determination for differential
The default implementation LOG_PO_COMMODITY_RELEVANCE uses the filter value 02 Purchase Order to determine whether a purchase order item is relevant for differential invoicing and proceeds as follows:
- The purchase order item is set as Relevant if you have set the value Relevant in the Differential Invoicing field in the related info record.
- The purchase order item is set as Not Relevant if you have set the value Not Relevant in the Differential Invoicing field in the related info record or if there is no info record available.
If you deactivate the default implementation, the system sets the value Not Relevant. If you use a customer implementation, you should deactivate the default implementation.
Note that the commodity relevance determination for differential invoicing is subject to certain restrictions in the current release version. For information on this, see SAP Note 1584025 and the restrictions documentation attached to this SAP Note.
Requirements
Standard settings
Activities
Example
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20110420 |
| SAP Release Created in | 606 |
