Redwood Documentation

Product Documentation

 

›Configuration of RFA

Finance AutomationSAP FCc Setup

Introduction

  • Introduction

Preparations

  • Preparations

Configuration of RFA

  • Initialization for FCc Process List
  • Connecting to Redwood Finance Automation from SAP AS ABAP
  • Connecting to Redwood Server from SAP AS ABAP
  • Integrating into Solution Manager
  • Integrating Into Financial Closing Cockpit

SAP BW Content Activation

  • FCc Content Activation
  • Preparations
  • Create Source of FCc data
  • Installing BW Content
  • Create Infopackage / Hierarchies
  • 0FCC_TEMITM Template Item
  • OFCC_TEMPL Template
  • 0FCC_TGITEM Task Group Item
  • 0FCC_TSKGRP Task Group
  • 0FCC_AGENTTY Processor Type
  • 0FCC_GLOBID Global ID
  • 0FCC_TASKTY Closing Task Type
  • 0FCC_STATUS Closing Task Status
  • 0FCC_TSKLST Closing Task List
  • 0FCC_TASK Closing Task
  • 0FCC_STRUTY Closing Item Type
  • 0FCC_ITEM Closing Item
  • 0FCC_R10 Closing Status
  • 0ACCESSTP Access Type
  • Avoid Duplicate Records
  • FCC_HIERARCHY
  • FCC_HIERARCHY_TG
  • FCC_MD_PART1
  • FCC_MD_PART2
  • FCC_MD_PART3
  • FCC_MD_PART4
  • Automation
← Initialization for FCc Process ListConnecting to Redwood Server from SAP AS ABAP →

finance-related topic Connecting to Redwood Finance Automation from SAP AS ABAP

SAP Business Automation Enabler (BAE) connectors are RFC servers and allow ABAP stacks to connect to Redwood Finance Automation and interact with the scheduler. Redwood Finance Automation interfaces with the SAP Applications API, which allows you to schedule processes in Redwood Finance Automation, for example from SAPGui. At the time of this writing, the following SAP components have been optimized for SAP BAE connectors (SAP Applications API):

  • Closing Cockpit
note

More SAP components are currently being optimized to make use of SAP BAE.

note

You need an ABAP stack of NetWeaver 7.00 SPS 16 or later to connect to SAP Business Automation Enabler.

You start the SAP Inbound Connector which, when started, will start an RFC server in Redwood Finance Automation. It will also create an RFC connection in the SAP instance you specified to Redwood Finance Automation. The SAP user must be Enabled.

Security

ABAP users are mapped to Redwood Finance Automation users and need the SAP_BC_BATCH_ADMIN_REDWOOD role in the SAP R3 subsystem and Business Automation User for the SAP System in Redwood Finance Automation.

SAP Solution Manager Setup

Please see SAP Note 1729766 - Solution Manager Setup for information on setting the Solution Manager connection.

SAP Gateway Hardening

Newer SAP releases have hardened SAP gateway configurations that prevent external programs from connecting to the central Redwood Finance Automation server, by default. If the gw/acl_mode gateway parameter is set to 1, you must register Redwood Finance Automation as an external program in gw/reg_info. See SAP Note 1843782 and Defining the reginfo File for more information.

Example

In the following example, the gw/acl_mode is set to 1, so gw/reg_info points to a file with the contents below; in SM59 the name of your RFC connection is CPSECCMLS, 10.0.0.5 is the IP of the SAProuter client and 10.1.2.9 is the IP of the central Redwood Finance Automation server.

TP=CPSECCMLS HOST=10.0.0.5,10.1.2.9

Security

By default, users can log in from all clients. You create BAE-only logins by granting these the scheduler-bae-only-user role which prevents users from accessing Redwood Finance Automation from other interfaces. Users with this role will not be allowed to log into the Redwood Finance Automation web interface, for example.

User Mapping

By default, the SAP usernames are mapped to users with the same name in Redwood Finance Automation.

To map SAP users to specific Redwood Finance Automation users, you create a table named BAE_User_Mapping_Configuration_Definition; the table needs a VALUE column (case-sensitive).

The key is in the format <SAPUSERNAME>@<Partition>.<SAP Inbound Name>, the VALUE is the name of the Redwood Finance Automation user.

Example:

keyVALUE
JDOE@example.PR1jsmith
EMUSTERMANN@example.BW1jsmith
CBERTHIER@example.IS1jsmith

Prerequisites

  • XBP 3.0 is required in the SAP instance
  • a free slot is required in the ProcessServerService.SAP.BAEConnector.limit license key

Procedure

Enabling the RFC server in Redwood Finance Automation

  1. Navigate to "Environment > SAP Inbound".
  2. Choose _New _ from the context-menu.
  3. On the SAPBASE Connector, fill in the Name, RFC Connect String, and Time Zone fields.
  4. Choose the Check connection button, if the connection fails, check the RFC connect string.
  5. On the On the SAP BAE Configuration tab, choose Add.
  6. Fill the Client Number, the username, and Password fields.
  7. Choose Check Connection Settings, if the connection fails check the client/username/password combination.
  8. Choose Save & Close.
  9. Choose Start from the context-menu of the SAP BAE Connector.

Testing the RFC Destination to Redwood Finance Automation

  1. Open transaction SM59.
  2. Expand TCP/IP connections.
  3. Choose the entry: CPS-nnnnnn@::.
  4. Choose Display and, once the details of the RFC connection are displayed, choose Connection Test.

Example

Enabling the RFC server in Redwood Finance Automation and creating a connection to it from the PR1 SAP instance

  1. Navigate to "Environment > SAP Inbound".
  2. Choose _New _ from the context-menu.
  3. On the SAPBASE Connector tab, fill PR1 into the Name, ASHOST=pr1.example.com SYSNR=15 TRACE=0 into the RFC Connect String, and Paris into Time Zone fields.
  4. On the SAP BAE Configuration tab, choose Add.
  5. Fill 200 into the Client Number, jdoe into the username, and mybestkePtseCret into the Password field.
  6. Choose Save & Close.
  7. Choose Start from the context-menu of the SAP BAE Connector named PR1.

Checking the RFC connection

  1. Open transaction SM59.
  2. Expand TCP/IP connections.
  3. Choose Display and, once the details of the RFC connection are displayed, choose Connection Test.

See Also

  • Closing Cockpit

financeTopic

← Initialization for FCc Process ListConnecting to Redwood Server from SAP AS ABAP →
  • Security
  • SAP Solution Manager Setup
  • SAP Gateway Hardening
  • Example
  • Security
  • User Mapping
  • Prerequisites
  • Procedure
  • Example
  • See Also
Docs
Getting StartedInstallationFinance InstallationConcepts
TroubleshootingArchiving
Learn and Connect
Support Portal
BlogEventsResources
ISO/ IEC 27001 Information Security Management
Automate to be human

2023 All Rights Reserved |

Terms of Service | Policies | Cookies | Glossary | Third-party Software | Contact | Copyright | Impressum |