Mastersaf SAP Conector Integration_EN

Ahlstrom Mastersaf DFE

Mastersaf DFE x SAP – Integration Prerequisites

Document History Version

Author

Date

Main Changes

V.01

Roberto Zanini

02/Set/2014

Document Creation

22/11/14 Mastersaf DFE x SAP – Integration Prerequisites

1

Table of Contents 1. Project Description..................................................................................................... 3 2. Prerequisites.............................................................................................................. 4 3. ABAP Programs Installation........................................................................................ 5


2

1.1.

Project Description

Connection to SAP ECC 6.0 is performed via SAP Java Connector (SAP JCo 3) adapters, which is a "Java Application Software" that allows the development of supported integrations with SAP and Java applications. SAP JCo 3 supports communication with the SAP Server in both directions:  

Incoming calls (Java calls ABAP) Outbound calls (ABAP calls Java).

The SAP JCo 3 adapter connects to SAP through an RFC (Remote Function Call) user, which is the default interface to establish connections between SAP and non-SAP systems. All types of RFC are transferred via TCP / IP. The connection to the Mastersaf DFE Portal is performed through Web Services. The Connector performs connection to SAP RFC Server using the SAPJCO 3, which expose invoices sent by the SAP ECC 6.0 through attributes and functions of XML_OUT and XML_IN MASTERSAF structure and functions.


3

1.2.

Prerequisites

1) SAP and RFC Server SAP and Remote Function Call Server must be installed, configured and interconnected. 2) SAP JCO 3 SAP Connector configured and installed on the same server as the connector. To perform SAP JCo 3 download, visit: http://service.sap.com/connectors Attention to SAP instructions: The SAP JCo 3.0.9 is unrestrictedly available for the following platforms: Windows XP/Vista/7 (Intel IA32, Intel EM64T and AMD64), Windows Server 2003/2008/2008 R2 (Intel IA32, Intel EM64T and AMD64, Itanium),Linux (Intel IA32, Intel EM64T and AMD64, Itanium, IBM eServer zSeries, PowerPC), HP-UX (PA-RISC and Itanium),AIX, z/OS, IBM i, Solaris (SPARC, Intel EM64T and AMD64) and Apple OS X (Intel IA32, Intel EM64T and AMD64). For exact platform and JRE prerequisites see SAP Note 1077727. For correct operation of SAPJCO3, it is required to configure the file: C:\WINDOWS\system32\drivers\etc\services This file is made available for the proper SAP Client installation. It was not required the installation of SAP Client in our environments, only the availability of the file in the specified location. Nonconformities in SAPJCO 3 facility must be treated with the SAP support. 3) SAP Notes SAP note 1589975 contains an overview of SAP solutions to meet the legal requirements of Brazil that involve Invoices Electronic published through Technical Notes in the website of the Ministry of Finance. It contains all the notes launched by SAP for the correct functioning of the electronic invoice. For more information: http://service.sap.com/sap/support/notes/1589975 This does not only refer to commercial invoice, invoices also involves service and every process of issuing notes.


4

4) SAP Permissions The communication user needs to be linked to role R3_RFCCALL:

1.3.

ABAP Programs Installation

1) Namespace Preparation The objective of this topic is to help SAP Basis Administrator to execute Mastersaf Requests for SAP environments. Upon completion of the latter transport process for the DEV environment, you can start the project and configure the connector.


5

2) Setting Up /MSAFDFE/ Namespace in SAP The namespace /MSAFDFE/ is reserved for Mastersaf to their default programs. This namespace is type "C", of Customer. No development or change on the objects of this license will be allowed in this space. So there is no authorization to create or change programs in this namespace. Any change must be provided by Mastersaf through a request. Before starting the transport of Mastersaf programs in ECC, you must create this space in the SAP environment by following these steps:      

Create namespace / MSAFDFE / in SAP; Access SE03 transaction; In the "Administration" group click "View / Modify set of names"; Click on "View -> Modify" button; Next, click on "New Entries"; Fill in the fields to create the namespace;


6

The namespace /MSAFDFE/ will be configured as shown below:

3) Request Transport Well as the installation of applications, Mastersaf requests should always be the most current. Apply external request in the SAP environment. After creating the namespace, you are allowed to transport Requests received by Mastersaf. Inside the zip file attached to the email, you will find two files: o o

K900XXX.DV1; R900XXX.DV1;

Each file must be placed in a specific folder within the SAP server. Thereafter, the transport can be made with SAP STMS transaction.


7

4) Make the inclusion of a new Request It is important that requests with Mastersaf prefix be placed in a new request created in the development environment of your company, so that it acquires a specific numbering. This can be done by SE09, in the inclusion of objects.


8

This way, the Mastersaf request is ready to be transported to the other SAP environments in your company.


9


10

Mastersaf SAP Conector Integration_EN

Recommend Documents