Kontakt

Ansicht
Dokumentation

EPIC_C_BPSOTCASV - Add Details for Service Operation Type Codes

EPIC_C_BPSOTCASV - Add Details for Service Operation Type Codes

BAL_S_LOG - Application Log: Log header data   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.
SAP E-Book

In this Customizing activity, you determine how your SAP system obtains and displays the information that is contained in queries to your bank and the response messages by assigning technical objects to the service operation types that you need. There are two possibilities for technically realizing the way in which you obtain and display the information for your service operation types:

  • Create Data Medium Exchange Engine (DMEE) format trees. You can use DMEE format trees to create queries. Note that it is still necessary to create an implementing class to process response messages.
  • Use implementing classes to create queries and process response messages

The technical realization that you choose also depends on the usage category of the service operation type:

  • Standard Query and Response - For this kind of query, you can use either a DMEE format tree or an implementing class. Note that if you create both a DMEE format tree and an implementing class, the system always tries to use the DMEE format tree first.
  • Query and Response for Item # For this service operation type, you must create an implementing class.
  • Response for Outgoing Payment # For this service operation type, you must create an implementing class.

After you have created the technical objects that you need (see the Requirements section), you assign them to the service operation types in this Customizing activity (see the Activities section).

For Queries Using DMEE Format Trees

  • You have created the necessary format trees for the different service operation types. You do this in the Data Medium Exchange Engine (DMEEtransaction).
  • You have assigned the relevant structures to the corresponding format trees in the maintenance view of the Data Medium Exchange Engine by choosing Format Attributes.

For Queries Using Implementing Classes

You have set up the following kinds of implementing classes using the SE80 transaction:

  • For queries with the Query and Response for Item usage category: The implementing classes that you create should use the IF_EPIC_BANK_PAYMENT_SERVICE interface delivered with this solution. This interface contains the following methods:
  • CREATE_REQUEST_MESSAGE: This method creates an outgoing request message for an item in a payment file. The type of message depends on the service operation type for bank payments. The message also contains your logon user ID at the house bank for logon purposes.

  • PROCESS_RESPONSE_MESSAGE: This method reads the response message from your house bank. The system updates the status of the corresponding items on the Electronic Payment Integration (China) screen.

  • For queries with the Standard Query and Response usage category: These classes should use the IF_EPIC_BANK_QUERY_SERVICE interface delivered with this solution. This interface has the same methods mentioned above.

Structures for Item and Standard Queries

Using the SE11 transaction, you have created the necessary structures for storing incoming and outgoing information as follows:

  • For queries about items, you have created an incoming structure for handling the response message. The system uses the FPRLT_ITEM structure (delivered with this solution) for the outgoing query.
  • For standard queries, you have created the following format-specific structures:
  • Format-specific structures for the additional parameters that can be included in outgoing queries. Before the system can send the query, the user must enter the necessary parameters. Every query includes the parameters in the EPIC_S_BNKQ structure delivered with this solution. The parameters in this structure are as follows: paying company code, house bank, bank account ID, service operation type (that is, the type of query). If additional parameters are needed, the user enters them on the Query Bank tab page on the Electronic Payment Integration (China) screen. These entries fill this structure.

  • Format-specific structures for the parameters in the incoming response messages. The values that fill this structure are displayed in the Query Results part of Query Bank tab page.

Implementing Classes and Structures

For each relevant combination of paying company code, house bank, and bank account, you assign the following technical objects to the service operation type with these usage categories

  • Response for Outgoing Payment usage category: Assign an implementing class.
  • Query and Response for Item usage category: Assign an implementing class and the incoming format-specific structure.
  • Standard Query and Response usage category: Assign one of the following:
  • With DMEE: A DMEE format tree for creating the queries, the corresponding outgoing format-specific structure if needed, the implementing class, and the incoming structure

  • Without DMEE: An implementing class, the corresponding outgoing format-specific structure if needed, and the incoming structure

Character Encoding

For those service operation type codes that are used only for outgoing queries (standard and item queries), enter the name of the corresponding character encoding set that is used by the bank communication client, for example, UTF-8, GB2312, or GBK. This ensures that the XML sent by your SAP system is transformed into a format that can be processed by your house bank. You must enter the character encoding set for each combination of company code and house bank for all service operation type codes used for outgoing queries.






ROGBILLS - Synchronize billing plans   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 7057 Date: 20240523 Time: 213719     sap01-206 ( 126 ms )