SAP ABAP IMG Activity FOT_IMG_BC (Set Up Exchange Infrastructure (XI))
Hierarchy
☛ SAP_FIN (Software Component) SAP_FIN
   ⤷ FI (Application Component) Financial Accounting
     ⤷ FOT_EDECLARATION (Package) Electronic Advance Return for Tax on Sales/Purchases
IMG Activity
ID FOT_IMG_BC Set Up Exchange Infrastructure (XI)  
Transaction Code S_AC0_52000125   (empty) 
Created on 20041013    
Customizing Attributes FOT_V_FOTETAXC   Electronic Communication with Authorities 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name FOT_IMG_BC    

Use

The components ELSTER and XI 7.0 are used as follows during the implementation of the electronic advance return for tax on sales/purchases:

  • The advance return for tax on sales/purchases is sent from the ERP system to the Integration Server in the form of a message using client proxy. This message has a supranational format for an advance return for tax on sales/purchases.
  • The message is mapped in the Integration Server to the national format of the electronic advance return for tax on sales/purchases. This is the ELSTER format for the German advance return for tax on sales/purchases.
  • In the SOAP Adapter of the SAP XI Adapter Engine, the ELSTER-specific encryption and compression is performed by a special Java module. Then the ELSTER server is called.
  • The encryption and decompression of the answer in the ELSTER format is done by another Java module in the SOAP Adapter.
  • The encrypted answer of the clearing house is mapped to the supranational format of the confirmation of the advance return for tax on sales/purchases and is returned to the ERP system using the client proxy.
  • The certificate of the clearing house that is required for encryption and your own certificate for the encryption and decryption of the answer are stored in the keystore of the J2EE Engine.

Requirements

The settings described here are based on the standard delivery of XI (SAP Exchange Infrastructure 7.0).

You need to be registered to access the software component ELSTER. To do this, enter a customer message under the component FI-GL-GL-F. The ELSTER component contains the mapping rules to the German taxes on sales/purchases format and its interface definitions.

Activities

To set up the SAP Exchange Infrastructure, proceed as follows:

    1.     Deployment of the Java Module and XI Content

    2.     Set Up Visual Administrator

    3.     Create Configuration Scenario from Integration Repository

    4.     Activate Transfer using SAP Exchange Infrastructure

1. Deployment of the Java Module and XI Content

  1. Get the current version of the XI content from the SAP Service Marketplace (http://service.sap.com/swdc), software component XI CONTENT ELSTER 2.0, and upload this to the Integration Repository.
  2. Get the current patch of the XI content (XI content SAP_APPL 600) for your ERP system from the SAP Service Marketplace and also upload this to the Integration Repository.
  3. Get the SCA with the JAVA modules from the SAP Service Marketplace , software component ELSTER 2.0, and perform a deployment on the Adapter Engine used (see Note 656711). The deployment must take place on the J2EE Engine on which the Adapter Engine of the Integration Server runs (SOAP Adapter). Normally this is the central Adapter Engine of the Integration Server.
  4. If you have not used any encryption functions or signature functions in the Integration Server up to now, then it may be necessary to deploy the SAP Java Cryptographic Toolkit on the J2EE Engine. This deployment is described in the SAP Netweaver 04 documentation under Security -> System Security for SAP Web AS Java (http://help.sap.com/saphelp_nw04/helpdata/en/8d/cb71b8046e6e469bf3dd283104e65b/frameset.htm).

2. Visual Administrator

You need to perform the following activities in the Visual Administrator of the J2EE Engine on which the Adapter Engine is running:

  1. Store the certificates in the keystore

    To do this, choose Cluster -> Services -> Key Storage. Create a new view such as Elster or select an existing view.

    1. Upload the public key of the clearing house in the selected view using Entry -> Load (for example, from http://service.sap.com/elster-fin). You can change the Clearing House name if required using Rename.
    2. Generate your own certificate using Entry -> Create in the same view or in another view. The following fields must be filled:
      - Country Name (DE)
      - Common Name (for example, XYZ, Inc.)
      - Entry Name (for example, XYZ, Inc.)
      - Select Store Certificate
      - Key Length (2048) (the number must be entered manually)
      - Algorithm (RSA)
    3. Generate a certificate using Generate. The private key is stored under the name <Entry Name>, such as XYZ, Inc., the certificate is stored under the name <Entry Name>-cert such as XYZ, Inc.-cert. You can change the name using Rename. You can also use an existing 2048 bit certificate.
  2. Authorization to access the keystore using the Elster encryption module:
    1. Choose Cluster -> Services -> Security Provider.
    2. On the tab page Protection Domains, choose the protection domain sap.com -> com.sap.fin.xi.elster -> EJBContainer -> applicationjars -> fin_elster.jar.
    3. Using Available permissions -> java.lang.RuntimePermission -> TARGETS select the New pushbutton.
    4. Enter the target XiSecurityRuntimePermission under Add new permission under Specify target name, choose No action and OK.
    5. Under Granted permissions choose the entry java.lang.RuntimePermission and under Available permissions -> java.lang.RuntimePermission -> VARIANTS -> XiSecurityRuntimePermission and assign the authorization using the Grant pushbutton.

3. Integration Directory

  1. Create a configuration scenario with reference to the integration scenario Elster_VAT_600 with the naming convention http://sap.com/xi/ELSTER/VAT/2005 from the Integration Repository . Save the scenario but do not yet start the integration scenario configurator.
  2. Create a partner for the tax authorities such as Clearing House and assign it to the configuration scenario.
  3. Create a business service for this partner such as ElsterServer1.
  4. Create a communication channel for this service such as ElsterHTTP . Select the communication channel template ElsterAdapterChannel from the naming convention http://sap.com/xi/ELSTER/VAT/2005 using Communication Channel -> Transfer Template.
    Then make the following settings for this channel:
    1. On the Parameter tab page:
      - Choose the required Adapter Engine (the Adapter Engine on which the Java module runs, see steps 2 and 3.)
      - Enter one of the four target URLs of the financial authority (see Note 789875).
      - If a proxy is used, select Use Proxy and enter the necessary data.
    2. On the Module tab page under Processing Sequence:
      - Insert the module at position 1 (before the SOAP module):
      Module name: localejbs/sap.com/com.sap.fin.xi.elster/ElsterSendModul
      Type: Local Enterprise Bean
      Module key: ElsterSend
      3. - Insert the module at position 3 (after the SOAP module):
      Module name: localejbs/sap.com/com.sap.fin.xi.elster/ElsterReceiveResponseModul
      Type: Local Enterprise Bean
      Module key: ElsterReceive
    3. Make the following entries on the Module tab page under Module Configuration (module key, parameter name, parameter value):
      - soap, XMBWS.NoSOAP, true
      - ElsterSend, Own.KeyStore, <name of the view under which your own certificate was stored> (for example, Elster)
      - ElsterSend, Own.Certificate, <Entry-Name of your own certificate>(for example, XYZ, Inc.-cert)
      - ElsterSend, TaxAuthority.KeyStore, <name of the views under which the certificate of the clearing house was stored> (for example, Elster)
      - ElsterSend, TaxAuthority.Certificate, <Entry-Name of the certificate of the clearing house> (for example, clearing house)
      - ElsterReceive, Own.KeyStore, <name of the view under which your own private key was stored> (for example, Elster)
      - ElsterReceive, Own.Key, <Entry-Name of your own private key> (for example, XYZ, Inc.)
  5. Copy the business service (for example, ElsterServer1) three times, for example, to the business services ElsterServer2, ElsterServer3 and ElsterServer4. The communication channel is also copied here. Change the communication channels of services 2-4, enter the other three target URLs of the financial authority (see Note 789875).
    Business Attributes
    ASAP Roadmap ID 207   Establish Reporting 
    Mandatory / Optional 1   Mandatory activity 
    Critical / Non-Critical 2   Non-critical 
    Country-Dependency I   Valid for countries specified 
    Maintenance Objects
    Maintenance object type    
    History
    Last changed by/on SAP  20060519 
    SAP Release Created in 600