SAP ABAP Data Element EPIC_USAGE_CATEGORY (Usage Category Code)

Hierarchy

☛ SAP_FIN (Software Component) SAP_FIN
   ⤷ FI-LOC (Application Component) Localization
     ⤷ ID-FI-EPIC-BACOM-BL (Package) Globalization: E-Payment Int. Bank Comm. Business Logic

Basic Data

Data Element	EPIC_USAGE_CATEGORY
Short Description	Usage Category Code

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	EPIC_USAGE_CATEGORY
Data Type	CHAR	Character String
Length	2
Decimal Places	0
Output Length	2
Value Table

Further Characteristics

Search Help: Name
Search Help: Parameters
Parameter ID
Default Component name
Change document	☐
No Input History	☐
Basic direction is set to LTR	☐
No BIDI Filtering	☐

Field Label

	Length	Field Label
Short	10	Usage
Medium	15	Usage Category
Long	20	Usage Category Code
Heading	10	Usage

Documentation

Definition

Indicates how and where this bank communication is triggered on the Electronic Payment Integration (China) screen, either by the user or automatically by the system.

Use

Assign the respective usage category to each of your bank communication types:

• Standard (Dialog) Query: For bank communication types that are started by a user only from the Query Bank tab page, for example, queries about account balances, select this usage category.

The system displays this as a possible bank communication type in the selection list on the Query Bank tab page. The user can start the query by entering the necessary communication-specific parameters. The system then automatically processes the response to this query. For queries started from this tab page, the system can display messages or results in an ALV list, depending on your implementation.

For communication types with this usage category, you have to implement the following ABAP repository objects:

• Dialog parameter structure for the parameters that the user will enter on the Query Bank tab page
• Output table structure to show an ALV list of the results. You can use the generic EPIC_S_EXAMPLE_CN_GEN_GAB_LR structure in your bank-specific implementation.

• Dialog and Payment Item Specific Query: If the users should be able to trigger payment item queries from the Process Items tab page and the Query Bank tab page, select this usage category. For communication types with this usage category, you have to implement the following ABAP repository objects:
• Dialog parameter structure for the parameters that the user will enter on the Query Bank tab page
• Other parameter structure. You must use the EPIC_S_ITEM_KEYS_BC_PARAMETER structure in your bank-specific implementation.
• Output table structure to show an ALV list of the results. You can use the generic EPIC_S_EXAMPLE_CN_GEN_GPS_LR structure in your bank-specific implementation.
• Payment Item Specific Query: If you want to allow the users to trigger payment item queries only from the Process Items tab page, select this usage category. Note that for queries started from this tab page, the system can only display messages as a response. For bank communication types with this usage category, you have to implement the following ABAP repository objects:
• Other parameter structure. You must use the EPIC_S_ITEM_KEYS_BC_PARAMETER structure in your bank-specific implementation.
• Payment: For the bank communication types that are automatically sent from your house bank to your SAP ERP system during the payment transfer process, that is, they are automatic response messages to your outgoing payments, select this usage category. A payment can be triggered by clicking the Pay and Send push button on the Process Items tab page or by clicking the Send File push button on the Process Files tab page. As the result of such a bank communication, the system updates the status of payment items and displays messages as needed. For bank communication types with this usage category, you have to implement the following ABAP repository objects:
• Other parameter structure. You must use the EPIC_S_ITEM_KEYS_BC_PARAMETER structure as the other parameter structure in your bank-specific implementation.

Dependencies

Example

History

Last changed by/on	SAP	20140121
SAP Release Created in	607