Connector for SAP Business Suite - Developer's Guide: Appendix

Establish a connection to the SAP system

Disconnect from the SAP system

Load BAPI/RFC Function

Execute BAPI/RFC Function

Exit BAPI/RFC Function

Focus on Import Parameters

Focus on the import structure

Focus on the Import Table

Focus on Export Parameters

Focus on the Export Structure

Focus on the Export Table

Bring a table from the table parameters into focus

Bring a field from the current structure into focus

Bring a field from the current table (row) into focus

Determine the number of rows in the current table

All rows of the current table as a set

Highlight a row in the current table

Add a new row to the current table

Set the value of the current parameter/field as a string

Set the value of the current parameter/field to a Double

Determine the value of the current parameter as a string

Reset Error Messages

Get the last error message as a string

Check for an existing connection to the SAP system "p_instance" in the "p_loginmode" login mode. If "p_connect = true" and a connection has not yet been established, a connection is established.

Establish a connection to the SAP system "p_instance"

Establish an SAP connection to the user's SAP system p_instance

Establish a connection to the SAP system "p_instance"

Establish a user connection to the SAP system "p_instance" using a username and password

Manually set the token-based credentials for an SAP system. The token (e.g., SSO ticket) contains the "p_token" parameter. Depending on the type of token, the "p_method" parameter must be set (e.g., "MYSAPSSO2" for an SSO ticket)

Manually set the username and password for a user in the current session

Reset a user's login credentials (e.g., SSO ticket information, for switching users)

Integrating this feature into Velocity allows you to use SAP interfaces on the page where it is used. SSO initializations are performed, and SSO JavaScript functions, for example, are made available. The "p_request parameterr expects the Velocity $Request object to be passed to it. The "p_mapurl" flag controls the mapping of SAP URLs.

Using this feature in Velocity embeds an SAP web interface as an iFrame. This call requires the "ssoPrepare" function to be called on the same page in order to perform the necessary JavaScript functions (e.g., setting the SAP ticket, initializing URL mapping). URL mapping is enabled via the "p_mapurl" flag.

This feature allows you to log in to the Intrexx portal via an Intrexx page (anonymously). If the login is successful, a session ID is returned.

Starts the SAPGUI for the specified SAP data source as a transaction in the given login mode (usually "user"). Additional parameters (e.g., fields to be filled in) are specified in "p_extra". Setting "p_skip = 'true'" allows you to skip the startup screen. The "p_url" flag controls whether the portal URL needs to be evaluated (e.g., different SAP router strings). However, for this to work, the page must have been initialized with "ssoPrepare" in Velocity.

How to use the "biasap_start_transaction_url" function without URL evaluation

Runs a report in the specified SAP system, with or without a variant. The "p_url" flag controls the customization of the path to the SAP system via the portal URL.

Like "biasap_start_report_url" but without URL evaluation

Set a cookie (e.g., for SSO)

Identify a cookie

Delete a cookie

Set the SSO ticket for SAP web interfaces. If a valid SSO token cannot be obtained and an error message is available via "p_message," this error message is displayed. The "p_cancel_on_error" parameter controls whether an invalid ticket should terminate the processing of the script and any subsequent scripts (e.g., for buttons) (Result: the SAP Web Interface is not displayed if the ticket is invalid).

The method initializes the SAP-OCI functions of the connector for SAP Business Suite. This method is intended for integration into a view page (Velocity). The current session and the request are passed. The third parameter specifies the authorization method to be used. The default setting is "PlainAuth," which must be configured in the portal. The portal logs in using the parameters provided and checks the received parameters for validity with SAP-OCI. The result is a Boolean. If the value is "true," the login was successful. If the value is "false," either the login was incorrect or the parameters passed are not valid for SAP-OCI.

This function checks whether a valid SAP OCI session is active. Use this function to customize jump targets in the application, for example, if the application is used for scenarios other than SAP OCI.

This function returns HTML text containing the current OCI information. This function can be used to quickly display technical OCI information.

This function can be used to determine a specific value from the OCI data. For example, you can use "$!GSAP.ociGetInfo("vendor")" to retrieve the vendor number and use it as a default value for input fields. Possible values for "p_info" are:

• sapuser
  

  Technical name of the logged-in SAP user

• login
  

  Portal username

• domain
  

  Login domain on the portal

• customer
  

  The purchaser's customer number with the supplier

• vendor
  

  Supplier number on the buyer's side

• oci_version
  

  OCI Version

• opi_version
  

  OPI Version

Sets the redirect URL after sending. A button is expected to be passed.

Generates the most important transfer data for a shopping cart item (the "row")

Generates additional data for a shopping cart item. "name" should contain the technical name of the OCI specification (e.g., "VENDORMAT")

Generates a long text for the item

Creates an other transfer field by specifying the technical name

To launch SAPGUI from the portal

Various JavaScript files with utility functions

Adjusting the time zone for timestamp fields. SAP systems often run in the CET time zone, while Intrexx runs on the server in UTC. This causes discrepancies in the display of times. However, the time zone should be set in the data source configuration (attribute in the sap.cfg file).

Login mode for SAP access (<system>|<user>|<mixed>)

Handlers for SAP access (e.g., "GENERIC_VIEW," "DEVELOPER_API")

Variant of the SAP handler (e.g., "DEFAULT"). Can be used to define a different SAP data handler

Ability to pass control parameters to the SAP handler. The values are available in the SAP Data Handler within the CONTROL structure.

Option to enable debugging only for the specific external data group. "True" enables debugging. SAP debugging is only possible if the portal is running on your own computer and SAPGUI is installed.

This parameter (active = "true") can be used to control table access so that no data is retrieved if no filter is active. This prevents access to the SAP system when tables are hidden in connection with dynamic filters.

Enables tracing for this data group. As a result, the log file contains more detailed entries.

Includes information about which version of the business logic is required in order to prevent errors in advance (use of new features).

For SAP data groups with complex keys (e.g., VBAP), a simple sequence from 1 to n is used as the key for the sake of simplicity. It is not possible to jump to a detail page this way. However, this option can make it easier to access cells within custom-designed view tables.

If this option is enabled, the data is cached on the server. Even if the data in the SAP system changes, only the old data is displayed in the portal. This option is particularly suitable for Customizing tables that are used as references (performance). The server-side cache can be reset by disconnecting from SAP.

This option is only relevant in the data handlers of the Developer API. For new records, the SAP API method "Get_Detail" would not normally be called. However, this can be enforced using this option to pre-populate values from SAP.

This option is also only relevant within the Developer API. New records are generally assigned the ID -1 by Intrexx. This option deletes this predefined key. In SAP, this could be queried using "if iv_key eq space."

This option, as an alternative to the corresponding bia-variant, prevents SAP from automatically determining the text table. This makes it possible to display complex cases such as the MARA table in the portal with a reasonable amount of effort.

When this option is enabled, certain data is passed as HTML code instead of plain text. This option is used, for example, in the "Generic Report" data handler to render an SAP report in the standard SAP colors.

This option enables longer texts to be displayed as a single block of text rather than across multiple lines. This option is used in the "Generic Report" data handler. The report will then no longer be transferred line by line and must be displayed as a freely formatted table. When this option is selected, a string field contains the entire report.

This option enables automatic mapping for numeric keys typical of SAP. Based on the specified length, the logic of the connector for SAP Business Suite knows that leading zeros must be automatically added to this field during transfer to SAP (with the exception of alphanumeric keys). When displayed in the portal, these fields are shown without leading zeros. If this option is used at the data group level, the key is automatically treated as a numeric SAP ID.

This option attempts to resolve the issue that SAP typically uses separate fields for date and time rather than timestamps. Intrexx, on the other hand, uses timestamps and can also display them as "date only" or "time only." This option tells the SAP system's data field which SAP field contains the corresponding time. This turns the SAP date field into a timestamp, and it can be used as such (e.g., in calendar controls). When displaying times, time shifts often occur (e.g., 2h). This is because the SAP server and the portal run in different time zones (CET vs. UTC). Therefore, the SAP time zone can be configured at the data source or via bia-timezone. This behavior should also work in reverse (writing timestamps to two separate SAP fields). The SAP date field is the leading field here again. However, the corresponding time field may need to be available (hidden) on the pages.

In SAP systems, codes are often used (typically 1- to 6-character fields; e.g., VBAK-VBTYP). These are transferred as text—that is, as SAP code—and are therefore unusable by users in this form. Of course, it is possible to link the relevant Customizing tables as references based on the language. However, this can sometimes involve a lot of effort. This option provides a simple solution: the "Generic View" data handler attempts to identify suitable texts based on the configured search help or other SAP mechanisms. This method is not possible in all cases (e.g., more complex search filters with multiple search criteria).

This option allows you to map URLs based on the portal URL. This is required, for example, to hide the actual URL on SAP systems (when accessing archived documents). Internal access can thus be mapped from "sapsystem.internesicht.net" to "archiv.externesicht.com" as soon as the user accesses the Intrexx portal via the external interface.

Converts the value to uppercase. Useful in SAP matchcode fields.

Data Browser: Viewing Table Contents

Dictionary: Displaying technical information about Dictionary objects (e.g., tables, views)

Implementation Guide: Central SAP Customizing

Maintenance of Configuration Tables

Maintaining RFC Destinations: Configuring Access to External Systems

Internet Connectivity: Enabled Services

Dump Analysis: Troubleshooting Crashes

System Log: Troubleshooting System Problems

Application Log: Logs for Many Applications

Data Exchange with External Systems Using qRFC and tRFC

User Management

Maintaining authorization objects: including generating them using the "SAP_ALL" function

Roles and Permissions

Authorization Trace

Logged-in Users

Registered Remote Systems

ABAP Workbench: Central Development Transaction

ABAP Reports: Development and Execution

Function Modules/BAPIs: Development, Testing

BAPI Browser