You can start sending trade repository objects either from the Monitor for Trade Repository Objects
(transaction FTR_TARO_MONITOR
) or by using the Sending Trade Respository Objects
(transaction FTR_TARO_SEND
) function.
By executing the function you start the sending process for the selected trade repository objects. When you do this, a trade repository message is created from the data of the trade repository object. As each trade repository defines the format in which it should receive the messages, trade repository reporting is designed in such a way that various formats can be supported. To create the file, you have to implement BAdI BADI_TLR_TARO_FILE_CREATE
Create File Based on TARO Content
. The TARO data is the import parameter of the BAdI. The output parameters are the trade repository message as a file in a character string format and the file type (for example, .XML or .txt). The BAdI implementation is called during the send process.
After creation of the trade repository message (file), the BAdI BADI_TLR_TARO_FILE_SEND
is called. You use this BAdI to control the output channel used for the trade repository message. The delivered implementation of this BAdI stores the trade repository message on the application server.
Note
Implementations are delivered for the BAdIs BADI_TLR_TARO_FILE_CREATE
and BADI_TLR_TARO_FILE_SEND
.
You can schedule this function as a background job.
Active implementations must exist for the BAdIs BADI_TLR_TARO_FILE_CREATE
and BADI_TLR_TARO_FILE_SEND
.
The trade repository objects must have the status 01
Created
or 04
Send Failed
.
When you execute the function, the system first calls the BAdI implementation for the method FILL_DERIVED_CONTENT
of BAdI BADI_TLR_TARO_FILL_DER_CONTENT
Fill Derived Content for Trade Repository Objects
, then the derivation tool for the derived content, and also method CHECK_CONTENT
of the BAdI. The system then runs the implementations of the BAdIs BADI_TLR_TARO_FILE_CREATE
Create File Based on TARO Content
and BADI_TLR_TARO_FILE_SEND
Send File to Trade Repository
.
The file created using the BAdI is stored in Document Management.
The implementation of the BAdI BADI_TLR_TARO_FILE_SEND
controls how the file created is handled. The delivered implementation stores the file on the application server. In trade repository reporting Customizing, you have entered the path under which the files are stored on the application server.
You can also display the created file from the monitor for trade repository objects.
Trade repository messages can be sent to the trade repository either individually or in a combined file. When you choose the Combined Files
function in the Monitor for Trade Repository Objects or in the function Send Trade Repository Objects
, the system combines into one message all selected trade repository messages that have the same company code, relate to the same trade repository, and use the same format tree. For this, you can restrict the size of the file by specifying the maximum number of messages per file in the send parameters.
Note
Implementation delivered
Create File
The implementation delivered creates an XML file by calling the Data Medium Exchange Engine (DMEE).
The DMEE (transaction DMEE
) is a tool that you can use to create, manage or display metadata (such as format trees). You can use it to convert ABAP data to XML files. The DMEE is connected to the transport system, so that the metadata created in the DMEE can be transported to the system landscape.
To connect the trade repository object to the DMEE, the tree type TRM0
has been created (with category Outgoing File
, interface type TLRS_TARO_DMEE_IF
, test report R_TLR_DMEETEST_EMIR
, authorization group FC12
).
The following client-independent format trees are delivered for the implementation:
TARO_FT
Full Termination
TARO_TT
Trade Termination
TARO_XT
Reported Trade
TARO_BK
Reporting Backloading
TARO_VU
Valuation Update
TARO_CU
Collateral Update
TARO_MX
Trade Modification
TARO_MX_UTI
Trade Modification UTI
TARO_MX_V
Trade Modification Type 'V'
The BAdI implementation calls the appropriate format tree depending on the action type of the TARO, and the TARO data (in accordance with the settings in the DMEE) is converted to XML format:
Action type | Format tree |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Not supported |
|
|
If you would like to sue other format trees for your outgoing messages, you can define format trees in the DMEE and assign them to action types in the Customizing activity Define Settings for Trade Repositories
. You can use the delivered format trees as a template for your own format trees.
The delivered implementation uses the format trees that you have defined and assigned.
Additional notes:
You can also create other file types.
You are recommended to use the DMEE to create the files, but this is not mandatory.
Using report R_TLR_DMEE_TEST_EMIR
, you create an XML file based on a format tree for a financial transaction. The report calls the BAdIs and the derivation tools to create the TARO, and then creates the XML file. You can check that the XML file is correct using the .XSD file of your trade repository.
Sending Files to Trade Repositories
The implementation of the BAdI BADI_TLR_TARO_FILE_SEND
controls how the file created is handled.
The delivered implementation stores the file on the application server. In trade repository reporting Customizing, you have entered the path under which the files are stored on the application server.
The trade repository notifications are stored together with the attachment for the TARO (if you have assigned a file to the TARO in the Monitor for Trade Repository Objects
(transaction FTR_TARO_MONITOR
) in Document Management (DMS).
One DMS document is created for one trade repository object (TARO), which happens when you first send the trade respository object. The trade repository message - as well as any attachment to the TARO - are assigned to this document. More files are often added to this TARO in any subsequent process (such as the incoming messages from the trade repository), which are then also assigned to the existing DMS document.
A log is issued, both for test runs and production runs.
All selected trade repository objects are listed in the log. The TARO is sorted in accordance with the following criteria:
Trade repository
Company code
Transaction number
TARO number
A traffic light at the start of each line gives you information about the send status. In addition to the traffic light, the status of the trade repository object is displayed in a mouseover text.
During a test run, the traffic lights mean the following:
: The TARO was already sent successfully (status 03
, 07
, 09
and 10
).
: The TARO has 01
or 04
status would be sent in a production run.
:
The TARO is not fit for sending (status 02
, 20
).
The TARO was refused (status 05
, 06
).
The TARO is not relevant (status 08
, 20
).
During a production run, the traffic lights mean the following:
: The TARO was sent successfully
: The TARO was already sent (status 03
, 07
, 09
and 10
).
:
The TARO had 01
or 04
status and the send failed. In addition to the red traffic light, mouseover text displays Errors
.
The TARO is not fit for sending (status 02
, 20
).
The TARO was refused (status 05
, 06
).
The TARO is not relevant (status 08
, 20
).
Call up the function under FTR_TARO_SEND
).
Select the trade repository
to which you want to report.
If you do not select a trade repository, the system sends messages for all trade repositories.
Select the status/statuses
of the trade repository objects.
If you do not set a status, the system sends messages for all TAROs with the send-relevant status 01
Created
or 04
Send Failed
.
Select the action type
. If you do not select an action type, the system sends messages for all action types.
Specify a date for the TAROs in the First Entered On
field.
You can specify the planned send date by which the TAROs are to be selected.
In the Financial Transaction
area, you can use the following financial transaction data to restrict the selection of the TAROs: You can select the following attributes for the financial transactions:
Company code
Transaction number
Product type
Transaction type
External trade ID
In the Sent
area, make the following settings:
Layout
: You can specify a layout for the results log.
Set the Combined Files
("Combine Multiple Trade Repository Messages into One File") indicator if you want to send trade repository messages in combined files.
If you do not set this indicator, the system sends each trade repository message in an individual file.
If you set this indicator, you can then use the Max.No. Messages per File
field to specify the maximum number of messages in a combined file.
Test Run
indicator
You can first send the messages in a test run.