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.
Refer to the file SAP_CloCo.zip.ucc in the directory IMAGE:FRAMEWORK\SAPCLOSINGCOCKPIT which contains the supplied files in encoded form.
![]() |
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
![]() |
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 |
---|
![]() |
6. | Testing the connection |
---|
Start the program UC4/CC_REPORT via the transaction SE38 to test the connection from ABAP to the AE system.
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)
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 |