Parlant amb el SAP des MB

SAP is the largest Enterprise Resource Planning (ERP) solution provider. SAP is actually the name of the company, officially SAP AG, based on the phrase Systeme, Anwendungen und Produkte in der Datenverarbeitung.

Systems Applications Products in Data Processing (SAP) is a client/server application that helps you manage your business processes in sales, materials management, and distribution. SAP has mainframe and UNIX solutions to support an interface for an EDI subsystem.

The R/3 product is their client-server solution for Enterprise Resource Planning. mySAP.com is the current offering. It is an evolution of R/3 bundled with a number of additional components, as CRM, Business Warehouse plus SAP's middleware platform, SAP NetWeaver.

{2012 wiki} : SAP's products focus on Enterprise Resource Planning (ERP). The company's main product is SAP ERP. The current version is SAP ERP 6.0 and is part of the SAP Business Suite. Its previous name was R/3. The "R" of SAP R/3 stood for realtime even though it is not a realtime solution. The number 3 related to the 3-tier architecture: database, application server and client (SAPgui).

SAP ERP is one of five enterprise applications in SAP's Business Suite. The other four applications are:

• Customer Relationship Management (CRM) helps companies acquire and retain customers, gain marketing and customer insight
• Product Lifecycle Management (PLM) helps manufacturers with product-related information
• Supply Chain Management (SCM) helps companies with the process of resourcing its manufacturing and service processes
• Supplier Relationship Management (SRM) enables companies to procure from suppliers

SAP provides a range of business applications including customer relationship management (CRM), supply chain management (SCM), and product lifecycle management (PLM).

SAP integration overview [*** entry point ***]

• R/3 : realtime data processing { == SAP ERP }
• ERP : enterprise resource planing
• APO : advanced planner and optimizer
• BW : bussiness information warehouse
• CRM : customer relationship management
• SRM : supplier relationship management
• HRMS : human resource management systems
• PLM : product lifetime management
• XI : exchange infrastructute = SAP integration broker !
• KW : knowledge warehouse
• GRC : governance, risk and compliance - pdf.

El XI es la eina de integració de moduls SAP, així com la única via de comunicació amb l'exterior. Parla MQ i JMS amb el "Adapter for (SAP) XI" que porta el MB.

    .--------.           .--------.
    |        |           |        |
    |  SAP   |           |  SAP   |
    |        |           |        |
    .--------.           .--------.
        |                |        |
        |                |   XI   |
        |                |        |
        |                .--------.
        |                    |
        |                    |
  .-----------.        .-----------.
  |           |        |           |
  | Adapter   |        | Adapter   |
  | for mySAP |        | for XI    |
  |           |        |           |
  .-----------.        .-----------.

Detalls XI :

• wiki XI
• SAP - search fo "XI" !
• help SAP

SAP Exchange Infrastructure (SAP XI) enables you to implement cross-system processes. It enables you to connect systems from different vendors (non-SAP and SAP) in different versions and implemented in different programming languages (Java, ABAP, and so on) to each other.

Top

url

SAP generates application data in the SAP Intermediate Document (IDoc) layout.

url

The connected systems transfer or receive IDocs through their IDoc RFC interface.

IDoc adapter

IDoc concepts (wiki), links, sample,

SAP designed IDocs ("Intermediate Documents") for exactly this purpose -- for encapsulating, moving around, and processing just the sections of data needed for specific purposes.

url

Data distribution SAP to WebSphere MQ: one-way (for IDoc) pattern.
IDoc processing message flows - for each message flow complete the following steps:

1. Run the Adapter Connection wizard and find the IDoc that you want to process with the message flow. The wizard generates a message set that describes the model for your chosen IDoc.
2. Create a message flow and add an MQInput node. Also:
   • Set the Queue name property to match the queue to which the IDoc is routed by the IDoc Routing flow.
   • Select DataObject as the message domain.
   • Select the message set that was generated in the previous step.
   • Select SAP ALE IDoc as the message format.
3. Develop the remainder of the message flow. The incoming IDoc exits the Out terminal of the MQInput node in the same format as if it is the Out terminal of an SAPInput node but with the addition of an MQMD header.

Un mensaje IDoc ALE típico que se ha enviado desde SAP al enlace WebSphere MQ para R3 consta de una cabecera MQMD, una cabecera MQSAPH y el propio IDoc ALE. El IDoc consta de estructuras de tamaño fijas:

• La primera estructura es la estructura de control (DC). Este es un elemento complejo con una longitud de 524 bytes que contiene un conjunto fijo de elemento simples definidos por SAP.
• Una o varias Estructuras de datos (DD). Cada DD es un elemento complejo con una longitud de 1063 bytes que contiene un conjunto fijo de elementos simples definidos por SAP que ocupa 63 bytes, seguido de 1000 bytes de datos de segmento definidos por el usuario.

url

A typical ALE IDoc message that has been sent from SAP to the WebSphere MQ link for R3 consists of an MQMD header, an MQSAPH header, and the ALE IDoc itself. The IDoc is made up of fixed size structures:

• The first structure is the Control Structure (DC). This is a complex element 524 bytes long that contains a fixed set of SAP-defined simple elements.
• One or more Data Structures (DDs). Each DD is a complex element 1063 bytes long that contains a fixed set of SAP-defined simple elements that occupies 63 bytes, followed by 1000 bytes of user-defined segment data.

url

MQSAPH fields - 12 parser's ! WS MB Information Center [*****]
See Pager sample {com.ibm.etools.mft.samples.pager.res} & See Soccer Results sample ! {com.ibm.etools.mft.samples.soccer.res} [ VMware MB - c:\PF\ibm\ws\evtoolkit\eclipse\plugins\com ... ]

IDoc format/contents : Your best bet to answer this question before someone else does is to use AMQSBCG to dump a message produced by SAP.

Todos los campos se deben especificar y establecer. La sintaxis es:

Los nombres de campo, que se deben especificar en orden, son:

url

• WE02 - IDoc List report - This report can be used to display and edit IDocs.
• WE19 - Test tool for IDoc processing - This transaction allows the creation of IDocs for testing.
• WE20 - Partner Profile - This transaction determines a processing code based on the partner profile identified by the control record of the IDoc.
• WE21 - Ports in IDoc processing - This transaction identifies an external port (RFC, File, ABAP-PI, etc.) that controls the IDoc flow to an external system.
• WE41 - Outbound process code - This transaction links an outbound processing code specified in a partner profile to a function module.
• WE42 - Inbound process code - This transaction links an inbound processing code specified in a partner profile to a function module.
• BD87 - Inbound processing - This transaction processes inbound IDocs.
• BD88 - Outbound processing - This transaction processes outbound IDocs.

url

Consejo: El SupportPac IA0F contiene una descripción ms detallada de los pasos que hay para crear el modelo de mensaje IDoc.

Quan establim un conector SAP, importem un(s) IDoc(s). Es guarden al Toolkit en forma de fitxers .mxsd.

See Manipulating messages in the IDoc domain - url url
Also from SAP IDoc to XML and viceversa - mqseries.net Utilice el ejemplo de ESQL siguiente desde un nodo Compute:

La primera lnea del cdigo copia el IDoc de entrada en el IDoc de salida.
La segunda lnea establece el nombre de tabla de la primera DC.
La tercera lnea utiliza el segundo segmento DD, que en este ejemplo es de tipo E2MAKTM001, y establece el campo maktx.

url

Top

• BAPI's are programming interface to access SAP Database from within SAP or other development platforms external to R/3 that support the Remote Function Call (RFC) protocol. The main objective of BAPI is to achieve integration between the R/3 System and external applications, legacy systems etc. This gives you the option to have non-SAP front-end for occasional users.

• ALE is also programming interface. The integration of various applications is achieved by using synchronous and asynchronous communication, rather than by means of a central database. Uses IDoc document / messages.
  It uses RFC API.

url

ABAP - programming language, similar to Java, used to access SAP database.

A BAPI is a ABAP program that has been made visible to external world.

1. create a custom IDoc and Message Type
   1. create segments transaction WE31
   2. create Basic IDoc type transaction WE30
   3. create/Assign Message type transactions WE81/WE82
2. configure Outbound settings
   1. define Logical Systems and Assign Client to Logical System transaction SALE
   2. maintain RFC Destinations transaction SM59
   3. define Ports transaction WE21
   4. maintain Distribution Model transaction BD64
   5. generate/Create Partner Profile transactions BD82/WE20
   6. distribute Model View transaction BD64
3. write an Outbound IDoc Generation Program - create an executable program ZRZ_ORDER_IDOC in SE38.
4. write Inbound Function Module to post Inbound IDoc - in the receiving system, create a function module Z_IDOC_INPUT_ZRZSO_MT using SE37.
5. configure Inbound settings
   1. define Logical Systems transaction SALE
   2. assign Client to Logical System transaction SALE
   3. maintain RFC Destinations transaction SM59
   4. define Ports transaction WE21
   5. generate/Create Partner Profile transactions BD82/WE20
   6. assign Function Module to Logical message transaction WE57
   7. define Input method for Inbound Function Module transaction BD51
   8. create a Process Code transaction WE42
6. test ALE scenario to transmit data between systems distributed across the network
   1. on the sender system, execute the IDoc Generation Program. Check the status of IDoc using transaction WE02.
   2. check the status of the IDoc in the receiver system using transaction WE02. You can also check the contents of DDic tables to make sure that the records have been created in the receiver system.

Part 1, part 2, part 3.

Page 1, page 2, page 3, page 4, page 5, page 6, page 7, page 8.

Top

The R3/Link product consists of an inbound server, reading IDocs from an input queue and passing them into SAP, and an outbound server, reading IDocs from SAP and writing them to an output queue. Both these apps run on the MQ machine, and make a TCP connection to the SAP system using SAP RFC calls.

MQ Series link for R/3 User Guide

MQ Series link for R/3 User Guide (on-line)

MQ Series Link for R/3 v 1.2 CSD03

• que son els conectores standard MYSAP ?
• el accés des Domino a MB (Message Broker) es via JMS, fent servir el adaptador MQ standard.
• el accés des SAP es mitjançant el Adapter For MySAP ...
• ens cal MQ al SAP : url

Top

What is RFC ? Remote Function Call
ICS had a "RFC trace" - does MB have anything similar ?

David : the adapter uses JCO to access LIBRFC32.DLL, the RFC API.

Yo prefiero el JCA adapter que viene con Broker 6.1 [emir]

Toolkit [6.1] + "SAP" ; [int]

Top

You get everything in the standard version and you are allowed to use them in "unit test" but to use them for real you have to pay an additional license fee for the sap nodes (they have a pid I believe). Their sales person should be able to work out a price. From the technical side nothing else has to be installed. In fact there is no direct checking or enforcement on our part in the code.
Regards, John.
John Reeve, WebSphere Message Broker Developer

Top

To interact with an SAP application, you have to :

• obtain external software dependencies
• optional: if you are using Application Link Enabling (ALE) processing, register a Remote Function Call (RFC) destination on the SAP server and configure the SAP server,
• run the Adapter Connection wizard
• develop a message flow
• then deploy the relevant resources

url

If we have no connection to SAP at deploy time, we get :

Top

Before you configure the WebSphere Adapter for SAP Software for Application Link Enabling (ALE) processing, you must :

• register a Remote Function Call (RFC) destination on the SAP server - SM59
• configure a receiver port - WE21
• configure a logical system - BD54
• configure a distribution model - BD64
• configure a partner profile on the SAP server - WE20

url

• SM59 - create RFC destination
• BD54 - create Logical System
• BD64 - create Distribution Model and Partner Profile
• WE21 - port in IDoc processing
• WE20 - configure Partner Profile

A message flow application that uses one of the WebSphere Adapters requires the following resources:

• one or more message flows that contain one or more WebSphere Adapters nodes
• a message set that contains the XML Schema Definitions (XSD) for each business object in the Enterprise Information System (EIS)
• an adapter component file for the WebSphere Adapter that is being used

The Adapter Connection wizard creates these resources automatically.

The following steps describe how to connect to an EIS.

1. switch to the Broker Application Development perspective.
2. click File > New > Adapter Connection. The Adapter Connection wizard opens. When you have completed the steps in the wizard, the specified message set project contains a message set with a message type for each business object that is to be used, and the specified message flow project references the message set project
3. ensure that a message flow is open in the Message Flow editor so that the message flow canvas is available.
4. in the Broker Development view, expand the folders beneath the message set until you see the adapter component, which has a suffix of inadapter or outadapter.
5. drag the adapter component onto the message flow canvas. The component appears as a message flow node.
6. configure the node, as decribed here

To display all SAPConnection configurable services, use the WebSphere Message Broker Explorer, or the mqsireportproperties command, as shown:

Top

SAP Connectivity sample.

The SAPInput node is used to capture information (for example an IDoc) that is output by the SAP system, so that it can be passed to a message flow for processing.

The SAPInput node allows you to interact with SAP applications. For example, the SAPInput node monitors an SAP system for any new purchase orders. When a new purchase order occurs, the SAPInput node generates a message tree that represents the business object with the new purchase order details. The message tree is propagated to the Out terminal so that the rest of the message flow can use the data to update other systems, or to audit the changes.

MB v 6.1 "Message Flows", page 996 [1004/1580]

When you get a message, try it this way

1. copy the Properties folder
2. create the MQMD and then set any properties you might need in the MQMD
3. copy the Data

Have you looked at the data coming into the flow with a trace node ? This will help you name the folders correctly ( get a trace of the root : Pattern := "${Root}" )

The SAPRequest node is used to send information to the SAP system and retrieve the response from SAP. In this sample message flow, SAPRequest nodes are used to invoke remote functions in SAP (BAPIs).

The SAPRequest node allows you to interact with SAP applications. For example, the SAPRequest node requests information from a SAP Enterprise Information System (EIS). A customer business object is sent to SAP, causing SAP to retrieve information about a customer, such as an address and account details. The response information that is retrieved by the SAPRequest node can then be used by the rest of the message flow. The SAPRequest node can send and receive business data.

MB v 6.1 "Message Flows", page 1000 [1008/1580]

Descripció general: use the SAPReply node to send a reply to an SAP synchronous callout. Use this node with an SAPInput node to implement a message flow application that acts as a remote function call (RFC) destination.

Detall: a SAP program can call functions on remote RFC servers. These functions can be called asynchronously or synchronously, where they must provide a reply. A message flow can act as an RFC destination and receives the function call through the SAPInput node. When the function is called synchronously, use the SAPReply node to send a reply back.

Under "Transports and Connectivity", you can find:

• SAP call out to an asynchronous system sample
• SAP call out to a synchronous system sample
• SAP connectivity sample

Top

Inbound adapters allow data to be passed from the EIS system to the MB.

• Switch to the Broker Application Development perspective.
• Expand the SapInboundMatMasSampleMSet message set project.
• Double click SapMatMasInbound.inadapter to open an editor where you can specify the connection parameters required to access your SAP system.
• Click Adapters > Inbound > SAP.
• Enter the following settings in the editor:
  • Hostname or IP address of the SAP Application server.
  • RFC Program ID, for example, SAMPRFC.
  • Gateway hostname or IP address.
  • Gateway service, for example, sapgw00.
    The Gateway Service can be found using transaction code SMGW (Gateway monitor) under the column titled Remote TP Name.
  • SAP Client ID (from SAP txn SCC4).
  • Language Code if the language is not English.
  • SAP System Number.
  • Username for SAP system.
  • Password corresponding to the username.
  Save the updated adapter.

Outbound adapters allow data to be passed from the MB to the EIS system.

Top

Open

1. Help
2. Samples gallery
3. Technology samples
4. Message Broker
5. Transports and connectivity
6. SAP connectivity
7. 2 samples : Input & Request.

Information Center - MB tkt v7 :

1. MB v 7.0.0.2 - url
2. developing message flow applications - url
3. connecting client applications - url
4. using websphere adapters - url
5. developing applications by using websphere adapters - url
6. interacting with an SAP application - url.

Top

The Object Discovery Agent (ODA) and Bussiness Object Designer (BOD) are two design-time tools that can be used to extract metadata from the target system - in this case, SAP.

The ODA is the connector-specific component that connects to the targer system and then waits for requests to obtain metadata. The BOD connects to the ODA and requests metedata from it. The BOD displays the data returned, allowing the user to edit it if they wish, and then saves this metadata as XML schemas (.xsd files).

The ODA acts as an intermediary between BOD and SAP, and is used to extract IDoc metadata from the target SAP system.

ALE & IDoc

RFC & BAPI

SAP and WBI MB Integration for Dummies v0.pdf (\\T400\WS-BI-MB\SAP\Emir\) 
SAP and WebSphere Message Broker Integration for Beginners v1.2.pdf (\\T400\WS-BI-MB\SAP\Emir\)  

Top

The IBM MQSeries Link for SAP R/3 allows us to both put and get data into and out of SAP R/3 from and to other data sources and legacy applications. It consists of three parts:

• MQSeries
• MQSeries Integrator
• The SAP Integration Libraries

The MQSeries SAP Link uses ALE to load SAP IDoc metadata into the MQSeries Integrator Formatter. This means that it can handle bidirectional IDoc formats.
A library of IDocs is provided and additional or customized IDocs can be loaded dynamically into the Formatter via the IDoc loader.

Using the MQSeries Integrator Version 1.0 , SG24-5386-00

Top

• description
• Name / IP of the SAP Application Server
• System ID : 3-chars directory at "/usr/sap/"
• System Number : 2-chars at end of directory name at "/usr/sap/EC1/DVEBMGS10"
• Client Number, User & Password

• SAP Input node
• SAP Request node
• Wizard to discover business object information from SAP system and generate connection definitions - Enterprise Metadata Discovery Wizard

v 6.1 adapters : configure BAPI, configure ALE, etc etc (education assistent)

Generates :

• Adapter Component
• Message Set definition (DataObject domain)

High-level steps :

• connect to EIS
• select services
• select business objects
• select operations
• refine connection properties for broker runtime
• generate message set

Adapter Connection Wizard can be invoked from :

• Menu option : File -> New -> Adapter Connection
• Broker Development View : right click, New -> Adapter Connection
• using Quick start wizard : Broker Development view + "Start from adapter connection"

WMB61_Beta_Adapters.ppt

The Adapter Connection wizard creates the following resources in the Toolkit:

• An adapter component file
• A message set that contains the XML Schema Definitions (XSD) for the business objects in SAP
• A message flow containing the WebSphere Adapters nodes

Once these resources are deployed to broker runtime via BAR file, the broker uses the same resources to connect to SAP

Broker runtime also gets some details from SAP configurable service

Integrating MB V7 with SAP, Vivek Grover. \\T400\WS-BI-MB\SAP\WSTE-04082010-IntegratingWMBV7withSAP-Grover.pdf

Top

Una forma sencilla de aprender y practicar ABAP es instalar MiniSAP. MiniSAP es un release 4.6D de SAP totalmente funcional durante 1 mes (ampliable 90 días más) con el que practicar la creación de Reports, ALVs, módulos de función, Module Pool, etc.
It is a downscaled version of SAP system without the SAP applications (FI, CO, MM, SD, HR etc.). Very helpful to those who are just starting to learn ABAP.

Requires : "SDN User id" & "Hardware key (HWID)"

Install How-To. Description, download & License Key

Working on http://www.sap.com/minisap page.

Top

Few transactions I've found :

• BD54 = Change View Logical Systems
• BD64 = Distribution Model
• SM59 = Display and Maintain RFC Destinations
• ST11 = see RFC trace
• WE20 = Partner Profiles
• WE21 = Ports in IDoc processing

Top

IBM has announced a world-record 4-processor result on Linux on the two-tier SAP Sales and Distribution (SD) standard application benchmark. This new result was achieved on the IBM System x 3850 X5, running IBM DB2 9.7 and Red Hat Enterprise Linux 6.2, and SAP enhancement package 4 for the SAP ERP application Release 6.0. Among the notable details of the benchmark, the x3850 X5 achieved 12,560 SAP SD benchmark users with 0.99 seconds average dialog response time, 68,580 SAPS, measured throughput of 4,115,000 dialog steps per hour (or 1,371,670 fully processed line items per hour), and an average CPU utilization of 98% for the central server. The x3850 X5s result beats the previous-best four-processor result of 12,204 SAP SD benchmark users on Linux achieved by the HP ProLiant DL580 G7.

The x3850 X5 was configured with four Intel Xeon E7-8870 processors at 2.40GHz with 30MB shared L3 cache per processor (4 processors/40 cores/80 threads), 512GB of memory, 64-bit DB2 9.7, Red Hat Enterprise Linux 6.2, and SAP enhancement package 4 for SAP ERP 6.0. The server accessed the DB2 9.7 database on an IBM System Storage DS4800 disk system.

For the latest SAP benchmark results, visit http://www.sap.com/benchmark.

Top

SAP GUI is SAP's universal client for accessing SAP functionality in SAP applications such as - SAP ERP, SAP Business Suite (SAP CRM, SAP SCM and SAP PLM), SAP Business Intelligence and so on. SAP GUI functions like a browser. It gets information from the SAP server like what, where, when and how, to display contents in its window. All members of the SAP GUI family have unique attributes that make them especially suited for different user environments.

download it here.

Per entrar al SAP via SAG GUI, ens cal :

• IP
• nmero de sistema : es tracta de 2 dígits, normalment "00" però també pot ser 01 o 02
• ID de sistema : són 3 lletres, as "EC1" ;
• usr/pwd
• client : 3 xifres numèriques, as "100" ;

[/]

It uses local:2232 and remote:3200

Top

• Convert RFC / BAPI to WSDL and use it instead of RFC - url.
• convert WSDl to BAPI :