en:app:020cor:070ovs:010pty:0040strinf

Structured Infotext and Attachment(s)

Structured Infotext and attachment(s) can be used to add hints and instructions including attachments to a party (both main and additional addresses) in an efficient way.

A Structured Infotext can be structured via categories. Categorization makes it possible to display relevant information only in processing transactions where the content is needed.

A category defines a list of business transactions from one or more business sectors. As many categories as needed as needed can be configured. For more details about categories see Maintaining Categories.

Example: A client requests their banker to always sent physical documents with a special courier service. To ensure that these instructions are followed, the bank using the application can define a category, e.g. “Sending instructions” and link that only to the “Send Documents (xxTSND)” and “Send, Accept and Settle (xxTPAY)” transactions under LC and collection business module.

The Structured Infotext is displayed for all parties connected to the contract, which means that infotexts for parties that may not be visible on the screen are also displayed in subsequent transactions.

Defining Structured Infotext and Attachment(s)

  • The first step is to define categories for business sectors/transactions using transaction Adding Categories.
  • Once the categories are defined, it is possible to use them for a party. Open the required party for which the structured infotext has to be updated using transaction Maintaining Parties
  • Edit the party and in panel “Structured Infotext”, add a line item to include the category that was added and save the changes.
  • All available structured infotext for this party and any available additional addresses can be viewed using the icon in transaction Maintaining Parties

Usage of Structured Infotext in business transactions

  • In business processing, when the party is used in the contract, the infotext will be displayed in the defined transactions but not in business transactions that are not relevant for the information.
  • This avoids unnecessary information to the user and desplays only be the party infotext that is relevant for further processing.
  • Before releasing a contract, the releaser is able to view the infotext and confirm it.
en/app/020cor/070ovs/010pty/0040strinf.txt · Last modified: 2024/02/01 15:47 by dm