TBAI / LROE common parameter configuration (including middleware parameterization)
Transaction: /EDGE/TC_TB_017
In this transaction, the constants are parameterized (with parameter name, parameter value) to be parameterized to manage relations with the Middleware system, among others, the constants are the following:
Meaning of the constants to be parameterized:
Constant | Meaning |
---|---|
Extractor class | Class that implements the product extraction code, table recovery like bkpf bseg, bset etc. From product, the class /EDGE/CL_TB_EXTRACTOR_GEN is given by default, although a class Z that inherits from the abstract class /EDGE/CL_TB_ABS_EXTRACTOR can be created to be able to modify any logic of this class. This Z class must be parameterised in this table. |
Communications class | Class that encapsulates communication with the Middleware system. This class must inherit from the / EDGE / CL_TB_ABS_COM class. By default, the three types of communication are provided:
|
Version (TCI) | Version of the AEAT XML that is being used |
Tenant (TCI) | When there is communication by TCI it is the ID that represents the client. There may be clients that have multiple ID_Tenant |
Origin (TCI) | Identifies the issuer of the invoice, as a general rule it is a SAP system. |
Product (TCI) | TICKETBAI is always indicated by default |
Nivel de log de Alarmas | Scope of log severity level values:
|
b+ LROE monitor application class
| API class for the b+ LROE monitor. By default, the /EDGE/CL_TB_LROE_API_BPLUS class is given by product, although a Z class can be created that inherits from the abstract class /EDGE/CL_TB_LROE_API in order to be able to modify any logic of this class. This class Z must be parameterised in this table. |
Avvale 2024