tibco activematrix adapter for sap examples

Copyright © 1996-2021. TIBCO Software Inc. All Rights Reserved.

TIBCO ActiveMatrix® Adapter for SAP

ExamplesVersion 7.3.0October 2021

| ii

Contents

Chapter 1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Examples Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2BusinessWorks 5 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Prerequisites of Running Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Required Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Importing the Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Starting the EMS Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 2 Dynamic Logon and External Commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Example Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Configuring the Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Running the Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Expected Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 3 Inbound IDoc with Inbound BAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Example Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Configuring the Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Running the Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14


Chapter 4 Outbound IDoc with Remote TIDManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17





Chapter 5 Outbound RFC with Inbound BAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23





TIBCO ActiveMatrix® Adapter for SAP Examples

iii |

Chapter 6 IDocFormat Publishing Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Example Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Configuring the Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31


Expected Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 7 Salesforce Opportunity to SAP Order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Example Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Configuring the Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37


Expected Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

TIBCO Product Documentation and Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45How to Access TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Other TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Third-Party Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46How to Contact TIBCO Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47How to Join TIBCO Community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Legal and Third-Party Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48


| 1

Chapter 1 Introduction

TIBCO ActiveMatrix® Adapter for SAP is a bidirectional gateway between SAP applications and applications configured for the TIBCO environment.

The adapter can remotely connect and operate with SAP systems running on OS platforms not supported by the adapter.

This manual explains how to run packaged examples in TIBCO Designer™.

This chapter describes the example projects packaged with TIBCO ActiveMatrix Adapter for SAP and preparation you need to do before running the sample projects.

Topics

• Examples Overview, page 2

• Prerequisites of Running Examples, page 3


2 | Introduction

Examples Overview

TIBCO ActiveMatrix Adapter for SAP provides seven examples to show how the adapter interacts with the SAP system.

After installing TIBCO ActiveMatrix Adapter for SAP, navigate to the TIBCO_ADR3_HOME\examples directory. You can find two example folders. The ActiveMatrix BusinessWorks 5 examples are in the BusinessWorks5 folder.

BusinessWorks 5 ExamplesYou can find the following examples in the BusinessWorks5 folder:

• Dynamic Logon and External Commit

This example shows how to use the dynamic logon and the Inbound BAPI transaction support features provided by the adapter in TIBCO Designer.

• Inbound IDoc with Inbound BAPI

This example shows how to use the Subscription Service service and Request-Response Service service in TIBCO Designer.

• Outbound IDoc with Remote TIDManager

This example shows how to use the remote TIDManager instance and how to use the Publication Service service in multiple adapter instances in TIBCO Designer.

• Outbound RFC with Inbound BAPI

This example shows how to use the Request-Response Invocation Service service and Request-Response Service service in TIBCO Designer.

• IDocFormat Publishing Mode

This example shows how to use the adapter for sending and receiving IDocs without any significant mapping, and the usage of JMS properties for the Publication Service service and the IDoc confirmation.

• Salesforce

— Salesforce Opportunity to SAP Order

This example shows how to set up communication between the SAP system and Salesforce.com by using the adapter in TIBCO Designer.

Before running these examples, you need to import the example projects into TIBCO Designer. See Importing Examples to TIBCO Designer on page 3.

.


Prerequisites of Running Examples | 3

Prerequisites of Running Examples

Before running the examples, you need to install the required software, import the examples and start the TIBCO Enterprise Message Service (EMS) server.

For the required software, see Required Software on page 3.

For how to import examples and start the EMS server, see Importing the Examples on page 3 and Starting the EMS Server on page 4.

Required SoftwareYou need to install the following software to run the ActiveMatrix BusinessWorks 5 examples:

• TIBCO ActiveMatrix Adapter for SAP

• TIBCO ActiveMatrix BusinessWorks 5.x

• TIBCO Runtime Agent

• TIBCO ActiveMatrix BusinessWorks™ Plug-in for Salesforce.com

Importing the ExamplesBased on the platform in which you run the examples, choose one of the following ways to import the examples:

• Importing Examples to TIBCO Designer, page 3

Importing Examples to TIBCO Designer

This procedure is specific to the ActiveMatrix BusinessWorks 5 examples in the BusinessWorks5 folder.

To import an example to TIBCO Designer:

1. Open TIBCO Designer.

2. In the startup window, click New empty project.

3. In the Save Project window, click next to the Project Directory field to select a directory for the new project and specify a name for it.

4. Select UTF-8 from the TIBCO Messaging Encoding list.

For the ActiveMatrix BusinessWorks 5 example, the version of TIBCO ActiveMatrix BusinessWorks Plug-in for Salesforce.com must be 2.4.1 or later.


4 | Introduction

5. (Optional) Select one option from the Multi-User System list and specify the applicable values according to your system setting.

6. Click OK.

7. Click Project > Import Full Project.

8. In the Import Project window, click the ZIP Archive tab and click to locate the example to be imported. Click OK.

The examples are located in the TIBCO_ADR3_HOME\examples\BusinessWorks5 directory.

9. In the Import - Options window, click Replace existing global variables with those in import and Overwrite on name conflict. Click Apply.

10. Click Save to save the project.

The selected example is displayed in TIBCO Designer.

Starting the EMS ServerAll of the examples use the JMS transport type. Ensure that the EMS server is running and accessible to the machine on which the adapter is installed before starting the adapter.

To start the EMS server, click Start > All Programs > TIBCO > TIBCO EMS [version_number] > Start EMS Server.


| 5

Chapter 2 Dynamic Logon and External Commit

This chapter describes how to configure and run the DynamicLogonExternalCommit example in TIBCO Designer.

Topics

• Example Overview, page 6

• Configuring the Example, page 7

• Running the Example, page 9

• Expected Results, page 10


6 | Dynamic Logon and External Commit

Example Overview

The DynamicLogonExternalCommit example shows how to use the dynamic logon and the Inbound BAPI transaction support features provided by the adapter. This example contains two processes, Create SalesOrder and Create SaleOrder with Auto Commit.

Both of the processes are configured with the Request-Response Service services. When running the processes, the adapter creates a dynamic connection to create sales orders in the SAP system.

The adapter packages the Create_SalesOrder_Send_Template.xml file in the TIBCO_ADR3_HOME\examples\BusinessWorks5\DynamicLogonExternalCommit directory. The Create_SalesOrder_Send_Template.xml file contains the input data of these two processes.

The adapter invokes the BAPI_SALESORDER_CREATEFROMDAT1 function module to create a sales order in the SAP system based on the input data in the Create_SalesOrder_Send_Template.xml file.

If an error occurs when the adapter invokes the BAPI_SALESORDER_CREATEFROMDAT1 function module, the error is written to the OrderStatus.xml file.

However, these two processes use different function models and mechanisms to commit and roll back a sales order in the SAP system:

• In the Create SalesOrder process, if the adapter fails to create a sales order, the adapter invokes the BAPI_TRANSACTION_ROLLBACK function module to roll back the sales order.

Otherwise, the adapter invokes the BAPI_TRANSACTION_COMMIT function module to commit the created sales order.

• In the Create SaleOrder with Auto Commit process, if the adapter fails to create a sales order, the sales order is automatically rolled back without the invocation of any function module.

Otherwise, the BAPI_TRANSACTION_COMMIT function module is automatically invoked to commit the created sales order.


Configuring the Example | 7

Configuring the Example

After importing the example to TIBCO Designer, as described in Importing Examples to TIBCO Designer on page 3, you need to ensure that the adapter can access the SAP system before running the process.

To set up a connection between the adapter and the SAP system:

1. In TIBCO Designer, open the DynamicLogonExternalCommit example project.

2. In the Global Variables panel, click . The Global Variables editor is displayed.



3. Enter values for the following global variables:

— UDConnection\AppServer

— UDConnection Client

— UDConnection\ConnectionType

— UDConnection\GroupName

— UDConnection\Language

— UDConnection\MsgServer

— UDConnection\Password

— UDConnection\SNC_lib

— UDConnection\SNC_mode

— UDConnection\SNC_partnername

— UDConnection\SNC_qop

— UDConnection\SNC_bSSO

— UDConnection\SNC_ssoSend

— UDConnection\SNC_x509

— UDConnection\SystemName

— UDConnection\SystemNumber

— UDConnection\UserName

— JMSProviderUrl

— ASAP_HOME

ASAP_HOME is the home directory where you install the adapter. For example, E:\TIBCO_HOME\adapter\adr3\7.3.

4. Click OK.

5. In the Project panel, click the adapter instance, and then, in the Configuration panel, click the Design-Time Connection tab.

6. Click Test Connection to validate your connection.


Running the Example | 9

Running the Example

Ensure that you have configured the example, as described in Configuring the Example on page 7.

To run the example, complete the following tasks:

• Task A, Start the Adapter, page 9

• Task B, Run the Process, page 9

Task A Start the Adapter

The adapter must be running before you run the example.

To start the adapter:

1. In TIBCO Designer, click Tools > Show Adapter Tester.

2. In the Adapter Tester window, click the adapter instance in the left panel.

3. In the Run Settings tab in the right panel, specify the directory where you run the processes and the executable file.

4. Click Start to start the adapter.

Task B Run the Process

After starting the adapter, complete the following steps to run the process:

1. In the Project panel, click the process that you want to run.

2. In the Tester panel, click to load the process.

3. In the Select Process to Load window, click Load Selected.

4. Navigate to the TIBCO_ADR3_HOME\examples\BusinessWorks5\

DynamicLogonExternalCommit directory and update the Create_SalesOrder_Send_Template.xml file.

The process is automatically triggered.



Expected Results

You can view the example results in the TIBCO_ADR3_HOME\examples\BusinessWorks5\

DynamicLogonWithExternalCommit directory.

When the process is finished, all the results of creating a sales order are written to the output file named OrderStatus.xml. If the creation is successful, you can also check the sales order information in the SAP system.

You can also check the symbolic destination of the active connection in the SAP server or check the adapter log file to get the dynamic connection result.

The log file is located in the TIBCO_ADR3_HOME\logs directory.


| 11

Chapter 3 Inbound IDoc with Inbound BAPI

This chapter describes how to configure and run the InboundIDocWithInboundBAPI example in TIBCO Designer.

Topics






12 | Inbound IDoc with Inbound BAPI

Example Overview

The InboundIDocWithInboundBAPI example shows how to use the Subscription Service service and the Request-Response Service service.

This example contains the Vendor process.

Once you update the VendorInputFile.xml file, the Vendor process is triggered. The Request-Response Service service invokes the BAPI_GL_ACC_EXISTENCECHECK functional module to validate the G/L account in the VendorInputFile.xml file.

You can find the VendorInputFile.xml file in the TIBCO_ADR3_HOME\examples\BusinessWorks5\InboundIDocWithInboundBAPI directory.

If the G/L account in the VendorInputFile.xml file is valid, the Vendor process publishes a message to the adapter to create a vendor based on the information in the VendorInputFile.xml file. Once the adapter receives the message as a CREMAS05 IDoc, the CREMAS05 IDoc is used to create a vendor in the SAP system.

If the G/L account is invalid, an error message is written to the output file.






1. In TIBCO Designer, open the InboundIDocWithInboundBAPI example project.



— AppServer

— Client

— GatewayService

— Password

— SystemNumber

— UserName

— JMSProviderUrl

— ASAP_HOME


4. Click OK.

5. (Optional) Change the Inbound TID management mode:

a. In the Project panel, click the R3AdapterConfiguration adapter instance.

b. In the Configuration panel, click the Adapter Services tab.

c. Change the TID management mode.



Ensure that the TIDmanager clients in all the adapter instances match the TID manager server in the TIDManager instance, when you select the Remote TID management mode.



Running the Example










3. In the Run Settings tab in the right panel, specify the directory where the processes run and the executable file.




1. In the Project panel, click the Vendor process.



4. Navigate to the TIBCO_ADR3_HOME\examples\BusinessWorks5\

InboundIDocWithInboundBAPI directory and update the VendorInputFile.xml file.


If you have configured the adapter instance with the remote Inbound TIDManagement, before starting the adapter, first start the TIDManager.


Expected Results | 15

Expected Results

You can view the example results in the TIBCO_ADR3_HOME\examples\BusinessWorks5\InboundIDocWithInboundBAPI directory.

If the G/L account is valid, a vendor is created in the SAP system. You can check the vendor information in the SAP system.

If the G/L account is invalid, the error is written to the error.xml file.


| 17

Chapter 4 Outbound IDoc with Remote TIDManager

This chapter describes how to configure and run the OutboundIDocWithRemoteTIDManager example in TIBCO Designer.

Topics






18 | Outbound IDoc with Remote TIDManager

Example Overview

The OutboundIDocWithRemoteTIDManagerexample shows how to use the remote TID manager and how to use the Publication Service services in multiple adapter instances.

This example contains the following three processes:

• CREMAS Process Receives a message from the Publication Service service and saves the message containing SAP Vendor Master Data to an output file.

• DEBMAS Process Receives a message from the Publication Service service and saves the message containing SAP Customer Master Data to an input file.

• MATMAS Process Receives a message from the Publication Service service and saves the message containing SAP Material Master Data to an input file.






1. In TIBCO Designer, open the OutboundIDocWithRemoteTIDManager example project.

2. In the Global Variables panel, click . The Global Variable editor is displayed.


— AppServer

— Client

— GatewayService

— Password

— SystemNumber

— UserName

— JMSProviderUrl

— ASAP_HOME


4. Click OK.





Running the Example



• Task A, Start the Adapter and TIDManager, page 20


Task A Start the Adapter and TIDManager

The TIDManager and the adapter must be running before you run the example.

To start the TIDManager and the adapter:


2. In the Adapter Tester window, click the TIDManager instance in the left panel.


4. Click Start to start the TIDManager instance.

5. In the left panel, click the adapter instance.




After starting the adapter and TID manager, complete the following steps to run the process:

1. In the Project panel, click the process which you want to test.





4. Log on to the SAP system and send an IDoc to start the process:

— To start the MATMAS process:

Send a MATMAS01 IDoc using ALE/IDoc messaging and execute the SAP transaction BD10.

— To start the DEBMAS process:

Send a DEBMAS01 IDoc using ALE/IDoc messaging and execute the SAP transaction BD12.

— To start the CREMAS process:

Send a CREMAS01 IDoc using ALE/IDoc messaging and execute the SAP transaction BD14.

The process is triggered automatically.



Expected Results

You can find the example results in the TIBCO_ADR3_HOME\examples\BusinessWorks5\

OutboundIDocWithRemoteTIDManager directory:

• The CREMAS_IDocNumber.xml file that contains the Vendor Master Data is created, when the CREMAS process is completed.

• The DEBMAS_IDocNumber.xml file that contains the Customer Master Data is created, when the DEBMAS process is completed.

• The MATMAS_IDocNumber.xml file that contains the Material Master Data is created, when the MATMAS process is completed.


| 23

Chapter 5 Outbound RFC with Inbound BAPI

This chapter describes how to configure and run the OutboundRFCWithInboundBAPI example in TIBCO Designer.

Topics






24 | Outbound RFC with Inbound BAPI

Example Overview

The OutboundRFCWithInboundBAPI example shows how to use the Request-Response Invocation Service service and the Request-Response Service service.

This example contains two processes. The only difference between the two processes is that the Using JMS process uses the JMS transport but the Using RV process uses the Rendezvous transport.

The Using JMS and the Using RV processes receive an event from the SAP system by invoking the BAPI_XBP_EVENT_RAISE function module. The Request-Response Invocation Service service forwards this event to the Request-Response Service service.

• When the value of the EVENTID parameter in the incoming event is CUSTOMER, the adapter invokes the BAPI_CUSTOMER_GETDETAIL2 function module to check if the customer number provided for the EVENTPARAM parameter is valid.

If the customer number is valid, the process writes the customer information to an output file. Otherwise, the Request-Response Invocation Service receives an error message.

• When the value of the EVENTID parameter in the incoming event is VENDOR, the adapter invokes the BAPI_VENDOR_GETDETAIL function module to check if the customer number provided for the EVENTPARAM parameter is valid.

If the customer number is valid, the process writes the customer information to an output file. Otherwise, the Request-Response Invocation Service receives an error message.

When the value of the EVENTID parameter in the incoming event is neither CUSTOMER nor VENDOR, the Request-Response Invocation Service service receives an error message.






1. In TIBCO Designer, open the OutboundRFCWithInboundBAPI example project.



— AppServer

— GatewayHost

— ProgramID

— Client

— GatewayService

— Password

— SystemNumber

— UserName

— JMSProviderUrl

— ASAP_HOME


4. Click OK.





Running the Example










3. In the Run Settings tab in the right panel, specify the directory where the processes are run and the executable file.




1. In the Project panel, click the process which you want to test.



4. Log on to the SAP system and execute the SAP transaction SE37.

5. Execute the BAPI_XBP_EVENT_RAISE the function module.

6. Enter the RFC Destination based on the configuration in the TIBCO Designer project.



7. Configure the customer and vendor information according to events to be tested:

a. To validate a customer master record, set the EVENTID parameter to CUSTOMER and enter a customer number for the EVENTPARAM parameter.

b. To validate a vendor master record, set the EVENTID parameter to VENDOR and enter a vendor number for the EVENTPARAM parameter.

c. To test an invalid event, enter a value for the EVENTID parameter that is neither CUSTOMER nor VENDOR.




Expected Results

You can view the example results in the TIBCO_ADR3_HOME\examples\BusinessWorks5\OutboundRFCWithInboundBAPI directory:

• The vendor.xml is created when the value of the EVENTID parameter is VENDOR.

• The customer.xml is created when the value of the EVENTID parameter is CUSTOMER.

• The SAP system receives an error message when the value of the EVENTID parameter is neither VENDOR nor CUSTOMER.


| 29

Chapter 6 IDocFormat Publishing Mode

This chapter describes how to configure and run the IDocFormatPublishingMode example in TIBCO Designer.

Topics






30 | IDocFormat Publishing Mode

Example Overview

The IDocFormatPublishingMode example shows how to use the adapter for sending and receiving IDocs without any significant mapping. This is useful in cases where there are systems or applications that understand the SAP IDoc format. In addition to demonstrating the usage of the IDocFormat publish mode, this example also shows the usage of JMS properties for the Publication Service service and the IDoc confirmation for the Subscription Service service.

This example contains four processes, ReceiveIDocFromSAP, SendCREMASToSAP, SendDEBMASToSAP, WaitIDocConfirmation.

The configurations of the SendCREMASToSAP and SendDEBMASToSAP processes are the same except for the IDoc type.

The ReceiveIDocFromSAP process is triggered when the Publication Service service publishes an IDoc from the SAP system. After the IDoc is received, it is written to the .idoc file. The adapter passes the control fields of IDocs as JMS properties. You can check the control fields in the JMS Application Properties resource.

Then, the SendCREMASToSAP or SendDEBMASToSAP process is triggered. The received IDoc is published back to the SAP system.

Finally, the WaitIDocConfirmation process is triggered to wait for the IDoc confirmation message report after the Subscription Service service receives the IDoc.

The SAPIDOC_MESTYP property has been defined in the JMS Application Properties resource. You can also define the JMS properties that you want in this resource.




After importing the example to TIBCO Designer, as described in Importing Examples to TIBCO Designer on page 3, ensure that the adapter can access the SAP system before running the process.


1. In TIBCO Designer, open the IDocFormatPublishingMode example project.



— AppServer

— Client

— GatewayHost

— GatewayService

— Password

— ProgramID

— SystemNumber

— UserName

— ASAP_HOME


4. Click OK.





Running the Example














1. In the Project panel, click the process that you want to run.


3. In the Select Process to Load window, select all the displayed processes except the WaitIDocConfirmation process.

4. Click Load Selected.

5. Log on to the SAP system and publish a CREMAS01 IDoc or a DEBMAS01 IDoc.

The processes are automatically triggered.



Expected Results

You can view the example results in the TIBCO_ADR3_HOME\examples\BusinessWorks5\IDocFormatPublishingMode directory.

When the IDoc confirmation report message from the SAP system is received, the message is written to the idoc_confirmation.txt file.

The IDoc published from the SAP system is also written to the debmas.idoc or cremas.idoc file.

Figure 1 debmas.idoc File Example


| 35

Chapter 7 Salesforce Opportunity to SAP Order

This chapter describes how to configure and run the SalesforceOpportunityToSAPOrder example in TIBCO Designer.

Topics






36 | Salesforce Opportunity to SAP Order

Example Overview

The SalesforceOpportunityToSAPOrder example shows how to set up communication between the SAP system and Salesforce.com by using the adapter. The example contains two processes, SyncOpportunityProcess and OrderDeliveryProcess.

• SyncOpportunityProcess process

The workflow action is triggered to send outbound messages to the process when you create a record of the Opportunity object with the stage of Closed Won or edit a record of the Opportunity object by setting the stage to Closed Won in the Salesforce.com.

The adapter invokes the BAPI_SALESORDER_CREATEFROMDAT1 function module to create a sales order in the SAP system based on the outbound messages. When an error occurs in the invocation, this error is written to the OrderStatus.xml file.

If the adapter fails to create the sales order, the adapter invokes the BAPI_TRANSACTION_ROLLBACK function module to roll back the sales order.

Otherwise, the adapter invokes BAPI_TRANSACTION_COMMIT function module to commit the created sales order. Then update the opportunity object in the Salesforce.com with the sales order number.

• OrderDeliveryProcess process

This process is triggered when the adapter publishes a DESADV05 IDoc containing the Opportunity ID. This process updates the Opportunity object in Salesforce.com with the SAP delivery number as the tracking number.




After importing the example to TIBCO Designer, as described in Importing the Examples on page 3, you need to ensure that the adapter can access the SAP system before running the process.

Based on the platform in which you run the example, choose one of the following ways to set up a connection between the adapter and the SAP system before you run the process:

• Set Up a Connection in TIBCO Designer, page 37

Set Up a Connection in TIBCO Designer

1. In TIBCO Designer, open the SalesforceOpportunityToSAPOrder example project.



— AppServer

— Client

— GatewayHost

— Password

— ProgramID

— SystemNumber

— UserName

— GatewayService

— Salesforce.connection\salesforce.password

— Salesforce.connection\salesforce.username

— Salesforce.connection\serverURL

— ASAP_HOME


4. Click OK.




Running the Example






The adapter must be running before you run this example.

Based on the platform in which you run the example, choose one of the following ways to start the adapter:

• Start the Adapter in TIBCO Designer, page 39

Start the Adapter in TIBCO Designer






Based on the platform in which you run the example, choose one of the following ways to run the process:

• Run the Process in TIBCO Designer, page 39

Run the Process in TIBCO Designer

1. In the Project panel, click the process which you want to test, and then click the Tester panel.





4. To start the process, do one of the following tasks:

— SyncOpportunityProcess process

Create a record of the Opportunity object with the stage of Closed Won or edit a record of the Opportunity object by setting the stage to Closed Won.

— OrderDeliveryProcess process

Publish a DESADV05 IDoc, after creating a delivery of a sales order in the SAP system. You can create the delivery in the SAP system either by executing SAP transaction VL01N and referencing the sales order or by executing the SAP Delivery Due List report.



Expected Results

You can view the results of the ActiveMatrix BusinessWorks 5 example in the TIBCO_ADR3_HOME\examples\BusinessWorks5\Salesforce\

SalesforceOpportunityToSAPOrder directory:

When the SyncOpportunityProcess process is finished, all the results of creating a sales order are written to the OrderStatus.xml file. If the creation is successful, you can also update the Salesforce.com to check the sales order number.

When the OrderDeliveryProcess process is finished, the sales order information is written to the DOCNUM.xml file. You can update the Salesforce.com to check the tracking number.


| 43

Index

D

dynamic logon 5

E

exampleconfiguration 7, 13, 19, 25description 6, 12, 18, 24prerequisites 3procedure 9, 14, 20, 26results 10, 15, 22, 28


44 |

TIBCO ActiveMatrix Adapter for SAP Examples

45 | TIBCO Product Documentation and Support Services

TIBCO Product Documentation and Support Services

For information about this product, you can read the documentation, contact TIBCO Support, and join the TIBCO Community.

How to Access TIBCO DocumentationDocumentation for TIBCO products is available on the TIBCO Product Documentation website, mainly in HTML and PDF formats.

The TIBCO Product Documentation website is updated frequently and is more current than any other documentation included with the product.

Product-Specific Documentation

The following documentation for this product is available on the TIBCO ActiveMatrix® Adapter for SAP page.

• TIBCO ActiveMatrix® Adapter for SAP Release Notes

• TIBCO ActiveMatrix® Adapter for SAP Installation

• TIBCO ActiveMatrix® Adapter for SAP Concepts

• TIBCO ActiveMatrix® Adapter for SAP Configuration and Deployment

• TIBCO ActiveMatrix® Adapter for SAP Examples

To directly access documentation for this product, double-click the following file:

TIBCO_HOME/release_notes/TIB_<productID>_version_docinfo.html

where TIBCO_HOME is the top-level directory in which TIBCO products are installed. On Windows, the default TIBCO_HOME is C:\tibco. On UNIX systems, the default TIBCO_HOME is /opt/tibco.

Other TIBCO Product DocumentationWhen working with TIBCO ActiveMatrix® Adapter for SAP, you may find it useful to read the documentation of the following TIBCO products:

TIBCO Product Description

TIBCO ActiveMatrix BusinessWorks This product provides an integration platform that enables companies to rapidly integrate systems and automate business processes.


https://docs.tibco.com/



https://docs.tibco.com/products/tibco-activematrix-adapter-for-ldap

https://docs.tibco.com/products/tibco-activematrix-adapter-for-ldap

https://docs.tibco.com/products/tibco-activematrix-adapter-for-sap




Third-Party DocumentationYou may also find it useful to read the documentation on the following websites:

• http://help.sap.com

This website is the SAP Help Portal where you can find documentation on all SAP products, including SAP ECC 6.0 releases and SAP NetWeaver. In order for TIBCO ActiveMatrix Adapter for SAP to exchange data with SAP systems, you must make configuration in the SAP system to allow for communication and the exchange of messages to take place. This website offers detailed information on such configuration required.

• http://service.sap.com/instguides

This website is provided by the SAP Support Portal and contains documentation on installations and upgrades. The documentation available contains information on components that can be used along with TIBCO ActiveMatrix Adapter for SAP, and the installation of the Secure Network

TIBCO® Adapter SDK This product provides a class library that helps developers implement an adapter with minimal effort.

TIBCO Administrator™ This product provides capabilities for managing users, monitoring machines, and deploying and managing applications that use TIBCO products.

TIBCO Designer™ This product provides a graphical user interface to create TIBCO ActiveMatrix BusinessWorks process definitions, or create or modify TIBCO Adapter configurations.

TIBCO Enterprise Message Service™ This product sends messages from your applications in a format that conforms to the Java Messaging Service (JMS) specification.

TIBCO Hawk® This product is for monitoring and managing distributed applications and systems throughout the enterprise.

TIBCO Rendezvous® This product uses messages to enable distributed application programs to communicate across a wide variety of hardware platforms and programming languages.

TIBCO Runtime Agent™ This product is a bundle of TIBCO software and third-party software that is required to run many TIBCO applications such as TIBCO ActiveMatrix BusinessWorks, TIBCO Adapters, and so on.

TIBCO Product Description


http://help.sap.com

http://service.sap.com/instguides


Communications (SNC) libraries where security is required between the adapter and SAP systems.

• http://service.sap.com/connectors

This website provides information on the different types of SAP Connectors available. TIBCO ActiveMatrix Adapter for SAP is based on the SAP Java Connector libraries. You can download the latest versions of these libraries from this website. For more information on the SAP JCo libraries and configuration related to these libraries, see the available documentation from this website.

How to Contact TIBCO SupportGet an overview of TIBCO Support. You can contact TIBCO Support in the following ways:

• For accessing the Support Knowledge Base and getting personalized content about products you are interested in, visit the TIBCO Support website.

• For creating a Support case, you must have a valid maintenance or support contract with TIBCO. You also need a user name and password to log in to TIBCO Support website. If you do not have a user name, you can request one by clicking Register on the website.

How to Join TIBCO CommunityTIBCO Community is the official channel for TIBCO customers, partners, and employee subject matter experts to share and access their collective experience. TIBCO Community offers access to Q&A forums, product wikis, and best practices. It also offers access to extensions, adapters, solution accelerators, and tools that extend and enable customers to gain full value from TIBCO products. In addition, users can submit and vote on feature requests from within the TIBCO Ideas Portal. For a free registration, visit TIBCO Community.


https://www.tibco.com/services/support

https://ideas.tibco.com/portal_session/new

https://ideas.tibco.com/portal_session/new

https://support.tibco.com

https://community.tibco.com


http://service.sap.com/connectors



48 | Legal and Third-Party Notices

Legal and Third-Party Notices

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME. This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.TIBCO, the TIBCO logo, the TIBCO O logo, ActiveMatrix, ActiveMatrix BusinessWorks, TIBCO Administrator, TIBCO Designer, Enterprise Message Service, Hawk, Rendezvous, and TIBCO Runtime Agent are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.Java and all Java based trademarks and logos are trademarks or registered trademarks of Oracle Corporation and/or its affiliates.All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.This software may be available on multiple operating systems. However, not all operating system platforms for a specific software version are released at the same time. See the readme file for the availability of this software version on a specific operating system platform.THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.This and other products of TIBCO Software Inc. may be covered by registered patents. Please refer to TIBCO's Virtual Patent Marking document (https://www.tibco.com/patents) for details.Copyright © 1996-2021. TIBCO Software Inc. All Rights Reserved.

https://www.tibco.com/patents

tibco activematrix adapter for sap examples

Documents