Show TOC

Background documentationCustomizing for Trade Repository Reporting

 

Before you can use the functions of trade repository reporting, you have to make settings in Customizing.

  • Under Start of the navigation path Treasury and Risk Management Next navigation step Transaction Manager Next navigation step General Settings Next navigation step Information System Next navigation step Define Legal Basis End of the navigation path, you need to define the legal basis.

    Example Example

    • EMIR

    • Dodd-Frank Act

    End of the example.

  • Under Start of the navigation path Treasury and Risk Management Next navigation step Transaction Manager Next navigation step General Settings Next navigation step Information System Next navigation step Assign Countries to Legal Basis End of the navigation path, assign to each legal basis the countries for which it is valid.

  • The following Customizing activities are available in the SAP reference IMG under Start of the navigation path Treasury and Risk Management Next navigation step Transaction Manager Next navigation step General Settings Next navigation step Information System Next navigation step Trade Repository Reporting End of the navigation path:

    • Define Trade Repository

    • Define Product Classifications

    • Define Settings for Trade Repository

      Note Note

      If you want to use logical path names, define these under Start of the navigation path SAP Customizing Implementation Guide Next navigation step SAP NetWeaver Next navigation step Application Server Next navigation step System Administration Next navigation step Platform-Independent File Names Next navigation step Cross-Client Maintenance of File Names and Paths End of the navigation path.

      1. Choose New Entries.

      2. Enter the following two lines:

        Logical file path

        Name

        FTRM_TARO_IMPORT

        Import of trade repository

        FTRM_TARO_SEND

        Send to trade repository

        FTRM_TARO_ERROR

        Imported files containing errors

        FTRM_TARO_ARCHIVE

        Files that have been imported and processed successfully

      3. Save your entries.

      4. Select the line FTRM_TARO_IMPORT, and choose Assignment of Physical Paths to Logical Path.

      5. Choose New Entries, and, in the Syntax group field, enter UNIX (all Unix platforms), and, in the Physical Path field, enter /tmp/<FILENAME>.

      6. Save your entries.

      7. Choose Logical File Name Definition, Cross-Client.

      8. Choose New Entries.

      9. Create the following file names:

        • Logical file: FTRM_TARO_IMPORT

          • Name TRM: Received from trade repository

          • Data format DIR

          • Application area TR

          • Logical path FTRM_TARO_IMPORT

        • Logical file: FTRM_TARO_SEND

          • Name TRM: Send to trade repository

          • Data format DIR

          • Application area TR

          • Logical path FTRM_TARO_SEND

        • Logical file: FTRM_TARO_ERROR

          • Name TRM: Error

          • Data format DIR

          • Application area TR

          • Logical path FTRM_TARO_ERROR

        • Logical file: FTRM_TARO_ARCHIVE

          • Name TRM: Imported and processed successfully

          • Data format DIR

          • Application area TR

          • Logical path FTRM_TARO_ARCHIVE

        • Save your entries.

      End of the note.

    • Managing Trade Repository Objects

      • Notes on implementation

      • BAdI: Fill Content for Trade Repository Object (BADI_TLR_TARO_FILL_CONTENT)

        This BAdI is delivered to you with an implementation. You can use this implementation.

        If you only want to fill some of the TARO field values differently, you can define rules for determining the field values in Customizing activities Determine Field Values for TARO Content Data and Determine Field Values for TARO Derived Content Data. You can also create your own BAdI implementations for filling the field values.

      • BAdI: Fill Derived Content Based on TARO Content (BADI_TLR_TARO_FILL_DER_CONTENT)

        This BAdI is delivered to you with an implementation. You can use this implementation.

        If you only want to fill some of the TARO field values differently, you can define rules for determining the field values in Customizing activities Determine Field Values for TARO Content Data and Determine Field Values for TARO Derived Content Data. You can also create your own BAdI implementations for filling the field values.

      • BAdI: Create File Based on TARO Content (BADI_TLR_TARO_FILE_CREATE)

        This BAdI is delivered to you with an implementation. You can use this implementation.

        For the creation of XML files by the implementation, the necessary settings in the Data Medium Exchange Engine (DMEE) have been delivered.

        See also: Send Trade Repository Objects and also SAP Notes 1849910Information published on SAP site and 1853746Information published on SAP site.

        Check whether the XML messages created using the implementation delivered are accepted by your trade repository. If this proves not to be the case, you have to create your own BAdI implementation.

      • BAdI: Send File to Trade Repository (BADI_TLR_TARO_FILE_SEND)

        This BAdI is delivered to you with an implementation. You can use this implementation.

        It defines the output channel for the trade repository messages.

        The system uses the default implementation to write to the application server the trade repository notification (= file) that was created using the BAdI: Create File Based on TARO Content (BADI_TLR_TARO_FILE_CREATE).

        You can use this BAdI to change the system behavior and create your own implementation. In this way, you can use alternative output channels.

      • BAdI: Get Data from Incoming Messages for TARO (BADI_TLR_TARO_INBOUND)

        This BAdI is delivered to you with an implementation. You can use this implementation.

        Test whether the incoming messages are correctly interpreted by your trade repository. Should this not to be the case, you have to create your own BAdI implementation.

    • Determination of field values for trade repository objects

      (Derviation tools)

      During creation of the TAROs, the system fills the fields by calling the BAdIs BAdI: Fill Content for Trade Repository Object (BADI_TLR_TARO_FILL_CONTENT or BAdI: Fill Derived Content Based on TARO Content(BADI_TLR_TARO_FILL_DER_CONTENT) and then by calling the derivation tools. You can also use the derivation tools to fill the fields of the TARO with values. If you are generally satisfied with how the BAdIs are implemented in the standard delivery but you would like to alter how some fields are filled, you can define rules for this.

      • Determine Field Values for TARO Content Data

      • Determine Field Values for TARO Derived Content Data

  • Under Start of the navigation path Treasury and Risk Management Next navigation step Transaction Manager Next navigation step General Settings Next navigation step Transaction Management Next navigation step BAdI: Default Value for External Trade ID in Financial Transactions End of the navigation path, there is a BAdI that you can use to fill the External Trade ID field in the financial transaction data (on the Administration tab).

  • To store the incoming and outgoing trade repository messages in Document Management (DMS), you need to make the settings in DMS that have been delivered.

    See also: Customizing Settings in DMS for TRM Documents and SAP Note 1849910Information published on SAP site

See the documentation on the Customizing activities.