Maintaining Entity Group Transaction Profiles

This transaction is used to maintain entity group transaction profiles. The Entity Group Transactions Profile supplements the global Application Transactions Profile with settings that apply to the relevant Entity Group. Entity group transaction profiles contain the information the application needs to process/maintain this transaction.

Note: For every transaction being used, both the Application Transactions Profile and the Entity Group Transactions Profile must be defined correctly. Failing to do so may lead to system malfunctions. Additional details about Transaction Profiles and Configuration (ATP) is provided under general information in the preceding link.

The “Transaction” field is used to select the transaction whose profile is to be displayed.

All the settings entered here apply to the Entity Group in which they were defined.

The right-hand side of the screen displays the abbreviation for the Entity in which the user is currently located. The transaction Info Entity (INFETY) can be used to check to which Entity Group the Entity belongs. To edit settings for a different Entity Group, the user must first switch to an Entity belonging to that Entity Group.

The following transactions can be started from here by clicking the icons in the list below for:

• Adding an Entity Group Transaction Profile
• Modifying Enity Group Transaction Profile
• Deleting Entity Group Transaction Profile
• printing entity group transaction profile(s).
• creating Entity Group Transaction Profile List
• showing the Version Log of the modifications to the entity group transaction profile(s).

Transaction parameters control how business transaction are to be released.

• Source in Transaction - The “Set_Wfs_Release” release rule programmed within the transaction is used. This rule is triggered from the 'MTABUT\SAV order 500' rule for the relevant business transaction. Both may have to be entered by a member of the support team in the source.
• Single Signature required - The required signature (field TRN/RELREQ) from the release transaction “Control and Release of Transactions” (TRNREL) is set to 'A'. Detailed information on release and signatures can be found under “Configuration”.
• No Release required - No release method is required for this transaction
• Multi Signature required - More than a single authorizer could be defined with different amount limit slab for every business transaction. Detailed information can be found under Maintaining Multi Signature Setting
• Other customized release methods can be defined

The combobox “Relevant Amount” is only active if ' Single / Multiple Signature required' has been selected. For example, 'Maximum Amount' (MAXAMT) can be selected here, but not the specific amount that is to be used for the release. If an open amount in a transaction is a negative number, the relevant amount for release is 0.

Each business transaction should be connected to one transaction class if Service Level Agreements (SLA) are used. The allowed duration time for a SLA relevant customer order can be defined in the SLA static data transaction per group of transactions for “Opening”, “Amendment”, “Document/ Claim Presentation” or “Other”.

The following settlement details can be controlled via the transaction profile:

• Open reduction amount - controlled via the combobox and depends on whether the field 'Reduction amount' located in the Details Settlement panel of the business transaction is open for user entries.
  The combobox offers a choice of three values:
  • Active - the field is open for entries in the business transaction.
  • Not active - the field is not open for entries in the business transaction.
  • Source in transaction - the rule programmed into the transaction – “SetRedFlg” – is applied. This rule is usually called from the RegisterSettlement rule of the relevant business transaction. If necessary, both must therefore be entered into the source by a supporter.
• Loading Temporary Settlement allowed - if the checkbox is checked, the transaction will be permitted to load temporary settlements.

This is the interface for connecting an external, bank-specific Compliance Check System.
This combobox provides three options:

• None - No compliance check will be performed in the selected transaction.
• per Message - In the selected transaction a compliance check will be performed for each individual document.
• per Transaction - In the selected transaction a compliance check will be performed.

Further information about the corresponding services (CCS, PDC, and PDS) can be found in the “service table”.

Additional Transaction Profile
Compliance