Knowledge Base > Automation Engine and Target Systems > SAP > SAP Closing Cockpit Integration with FCC 2.0 Add-on

Integrating the Automation Engine in SAP Closing Cockpit with FCC 2.0 Add-on

The SAP Financial Closing Cockpit can be used to schedule several tasks that should be executed in a particular order and at a particular point in time. Through the integration of AE, you can activate objects of an AE system via Closing Cockpit tasks.

You may use an alternative integration method from SAP. You may find the respective SAP website pages at: Creating External Jobs

As of version 11, SAP Closing Cockpit may also be used with the FCC 2.0 Add-on. Below you find the installation steps for SAP Closing Cockpit with this Add-on.

Requirements:

AE Internal Webservice

 The AE Internal Webservice can be used with the following applicationAn application is a software which helps a user to fulfill specific tasks. In the context of ARA see also: Application entity. servers:

Use the installation guide to set up the required application server. Make sure to use the current version of the AE Internal Webservice.

SAP version

SAP Basis requires a particular or a later support packageA Package is an instance (a version, a revision, a tag, …) of your application and defines the content which you want to deploy. Here you decide, if you want to deploy the entire application or just a few specified components. version depending on the SAP releaseReleases combine a set of activities and a set of packages as well as other release artifacts under a timeline (a plan including milestones and phases), which can be planned, baselined and tracked. version which is used.

Release Package name
700 SABKB70017
701 SABKB70101
710 SABKB71007

Another requirement is SAP ERP version 6.00.

Supplied Files 

Refer to the file SAP_CloCo.zip.ucc in the directory IMAGE:FRAMEWORK\SAPCLOSINGCOCKPIT which contains the supplied files in encoded form.


Installation

1. Decoding the supplied file
2. Loading SAP transports

Specific ABAP programs are required for the integration process. Load them to the SAP system by means of an import. The archive SAP_CloCo.ZIP includes two corresponding files.

The transport request is based on SAP Closing Cockpit 7.00. Therefore the componentA component is a single deployable application artifact. As an example, this can be yourfile.war to be deployed into a Tomcat container. Each component has different properties which determine where to get it from, how to configure it, etc. You will need one component per application artifact: e.g., one for the application tier and one for the database backend. would not match, as the FCC 2.0 Add-on might run on 7.40.

3. Configuring the HTTP RFC connection

Call the transaction SM59 and select "HTTP connections to the external server". Now create a new connection.

Enter a name for the RFC destination (e.g.: AE_WEBSERVICE) and a description.

Tab: Technical settings:
In the field Target hostComputer, target system., enter the host name of the application server where the AE Internal Webservice runs. Enter the port number in the field Service number.

Tab: Logon and Security:
Select the option Basic authentication. Specify the data for accessing the AE system: in the field User, enter the AE clientA closed environment within an Automation Engine system where you can create and run objects. A client name consists of a 4-digit number that must be indicated when a user logs on to the Automation Engine system. Users and their rights are also defined in clients. A particular Automation Engine object type., user nameName of the Automation Engine user. and the departmentDepartment name to which the Automation Engine user belongs. (separated by a slash). Now enter the passwordA secret combination of characters for a Automation Engine user. and store the RFC connection.

4. Defining the logical port

Start the transaction SOAMANAGER

  1. Select the link "Web Service Configuration" ("Service Administration" tab)
  2. Search for the object typeAn individual object is provided for the individual activities: There are User, UserGroup, Notification, Cockpit, CodeTable, Documentation, Event, Agent, FileTransfer, Group, Include, Job, Workflow, Calendar, Login, Client, RemoteTaskManager, Schedule, Script, Server, Sync, Variable and TimeZone objects "Consumer ProxySeparate Automic product that can be used as an additional service program in combination with the Automation Engine. Combines and reroutes CP connections." which is named /UC4/CO_UC4PORT_TYPE and select it.



  3. After selecting the objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task, the following window will open. Click on "Create - Manual Configuration":


  4. In the following dialog, enter "UC4" as "Logical Port Name" and activate the "Logical port is Default" checkbox:


    Click "Next" to continue.

  5. Select "User ID / Password" in the authentication settings.
    Enter a user name using the format <AE Client>/<USER>/<DEPARTMENT>
    Enter the password for this AE userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management. and click "Next" to continue.

  6. Enter "/uc4ws/uc4ws" in the "URL Access Path" field.
    Enter the host name where the web service is deployed and its port in the fields "Computer Name of Access URL" and "Port Number of Access URL" as shown below:




    Click "Next" to continue.

  7. Select "Suppress ID Transfer" in the Message ID (Synchronous) section:



    Click "Next" to continue.

     
  8. Activate "Suppress sending of IBC Identifier" and click "Finish":


 

5. Registering the ABAP reportA report provides more detailed information about a task's execution or a component. for the FCC 2.0 Add-on
  1. Execute the program RDDKOR54
  2. Enter SCMAPROGRAMS as table name and select "Execute" (F8).
  3. Click on the "Create Reservation" (F5) button.
  4. Enter "/UC4/*" as namespace and save the changes. The result will look as follows:



     
  5. Call transaction sm30 and enter the table name SCMAPROGRAMS.
  6. Add a new entry with the program /UC4/CC_REPORT and application CUSTOMER
  7. Save this entry.
6. Testing the connection

Start the program UC4/CC_REPORT via the transaction SE38 to test the connection from ABAP to the AE system.

 

Add customer exits in /UC4/CC_REPORT program

Business Add Ins (BAdI) are special extensions for SAP. Detailed information is available on the SAP website.
Below you find a description how to use a BAdI with the /UC4/CC_REPORT program.

A BAdI will be added to the /UC4/CC_REPORT program. The default implementation does nothing and the program continues.
You may create another implementation which performs some checks based on the Automic object name and user (SY-UNAME)

Create a BAdI implementation

The enhancement spot is called /UC4/AUTH_CHECK:

Example

This BAdI can be used to implement a permission check based on a table with user names and jobAn Automation Engine object type for a process that runs on a target system. names.

If the user is 'ANG' and the object name is JOBP.TEST1, the program will show a message box with user and object name and exit.

 

See also:

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH