Knowledge Base > Automation Engine and Target Systems > SAP > SAP Closing Cockpit Integration

Integrating the Automation Engine in SAP Closing Cockpit

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.

In order to use the SAP Closing Cockpit with FCC 2.0 Add-on, refer to the alternative installation description.

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.

Copy these files to the transport directory of SAP (e.g.: /usr/sap/trans/). Copy the K file to the subfolder "cofiles" and the R file to "data".

Log on to the SAP system and import the relevant request using the transaction STMS. Open and check the request's transport protocol after the import process: all steps have to show the return codeThe value that represents the result of tasks and script functions. 0 (successfully ended) or 4 (ended with warning).

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 includes *UC4* as the name.



  3. Create a new logical port with the name UC4.
  4. In the "Consumer Security" tab fields "User" and "Password", enter the loginAn Automation Engine object type that stores account credentials used by agents on target systems. data for the Automation Engine systemAn environment that is managed by Automation Engine components. [Formerly called "UC4 system."]:
    Use the following syntax for the user name: <client>/<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.>/<department>. For example: 0001/USER/DEV
    As the password, use the password of the defined Automation EngineThis component drives an Automation Engine system and consists of different types of server processes. user.



  5. In the "Messaging" tab, set the "Message ID protocol" field to the value "Suppress ID Transfer".



  6. "Transport Settings" tab: In the field "URL Access Path", enter the value ""/uc4ws/uc4ws?wsdl".
    Also set the computer name and the port of the Webservice's Application Server.
    Use SOAP 1.1 as the "Transport Binding Type"


Store and activate the logical port.

5. Registering the ABAP reportA report provides more detailed information about a task's execution or a component. for the Closing Cockpit

Call the transaction SM30 and open the table SCMAPROGRAMS for modifications ("Maintain"). Add a new entry with the following values:

Column Value
Program /UC4/CC_REPORT
Application CUSTOMER

Store this new 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.

 

See also:

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

 


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

Copyright © 2016 Automic Software GmbH