Connector for SAP Business Suite - Developer's Manual - Appendix

Establish connection to the SAP system

Close connection to the SAP system

Load BAPI/RFC function

Execute BAPI/RFC function

End BAPI/RFC function

Focus on import parameter

Focus on import parameter

Focus on import table

Focus on export parameter

Focus on export structure

Focus on export table

Focus on table from table parameter

Focus on field from the current structure

Focus on field from the current table (rows)

Get number of table rows in the current table

All table rows in the current table as a quantity

Focus on a row in the current table

Add a row to the current table

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

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

Get the value of the current parameter as a string

Reset error messages

Get last error message as a string

Checks an existing connection to the SAP system "p_instance" in the login mode "p_loginmode". If "p_connect = true" you are not connected yet, a connection will be established.

Close a connection to the SAP system "p_instance"

Close a connection to the SAP system "p_instance" of the user

Create a connection to the SAP system "p_instance"

Create a user connection to the SAP system "p_instance" with username and password

Set the login information via a token for an SAP system manually. The token (e.g. SSO ticket) contains the parameter "p_token". Depending on the type of token, the parameter "p_method" must be set (e.g. "MYSAPSSO2" for SSO ticket)

Set the login information username/password or a user from the current sessions manually

Reset the login information for a user (e.g. SSO ticket information, for user switch)

Integrating this function in Velocity enables you to use the SAP interface of the utilizing page. SSO initializations are performed and SSO JavaScript functions are made available, for example. The parameter "p_request" expects the transfer of the Velocity $Request object. The mapping of SAP URLS is controlled using the flag "p_mapurl"

Using this function in Velocity integrates an SAP web interface as an iFrame. The call requires the function "ssoPrepare" on the same page to be able to use the necessary JavaScript functions (e.g. set SAP ticket, initialize URL mapping). The URL mapping is activated via the active flag "p_mapurl".

This function enables you to log in to the Intrexx portal via an Intrexx page (anonymously). Once the login is successful, a session ID will be 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 populated) are defined in "p_extra". The start screen can be skipped with "p_skip = "true"". The flag "p_url" controls whether the portal URL needs to be evaluated (e.g. different SAP router strings). To do this, the page needs to have been initiated with "ssoPrepare" in Velocity.

Like the function "biasap_start_transaction_url" but without URL evaluation

Starts a report in the specified SAP system with or without variants. The flag "p_url" controls the adjusting of the path to the SAP system via the portal URL.

Like the function "biasap_start_report_url" but without URL evaluation

Set a cookie (e.g. for SSO)

Get a cookie

Delete a cookie

Set the SSO ticket for SAP web interfaces. If identifying a valid SSO token is not possible and an error message is available via "p_message", this error message will be displayed. The parameter "p_cancel_on_error" controls whether a defective ticket should cancel the processing of the script and also subsequent scripts (e.g. for buttons). This means the SAP web interface will not be displayed of the ticket is erroneous.

This method initializes the SAP OCI functions of the Connector for SAP Business Suite. This method is intended for integration on a view page (Velocity). The current session and the request are transferred. The third parameter defines which authentication method should be used. Default is "PlainAuth" which has to be configured in the portal. A login to the portal is performed with the transferred parameters and the received parameters are checked for validity for SAP OCI. The result is boolean. If the value is "true", then the login was successful. If the value was "false", then either the login was incorrect or the transferred parameters are not valid for SAP OCI.

This function checks whether a valid SAP OCI session is active. Use this function to, for example, adjust link destinations in the application if the application is not used for SAP OCI scenarios.

This function returns an HTML text that contains the current OCI information. The function can be used to present technical OCI information quickly.

With this function, a specific value can be identified from the OCI data. With "$!GSAP.ociGetInfo("vendor")" for example, the vendor number can be read and used as a suggested value for edit fields. Possible values for "p_info" are:

• sapuser
  

  Technical name of the logged-in SAP user

• login
  

  Login name for the portal

• domain
  

  Login domain for the portal

• customer
  

  Customer number of the purchaser at the vendor

• vendor
  

  Supplier number at the vendor

• oci_version
  

  OCI version

• opi_version
  

  OPI-Version

Sets the return address after sending. A button is expected to be transferred. A button is expected to be transferred.

Generates the most important transfer data for a basket item (of the line "row")

Generates more data for a basket item. In "name", the technical name of the OCI specification is expected (e.g. "VENDORMAT")

Generates a longtext at the position

Generates a another transfer field stating the technical name

To initialize the SAPGUI from the portal

Diverse JavaScripts with utility functions

Adjust the timezone for time stamp fields. SAP systems often run in the CET timezone, Intrexx in UTC on the server. This causes displacements when times are being displayed. However, it is better to define the timezone in the configuration of the data source (attribute in the file sap.cfg).

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

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

Variant of the SAP handler (e.g. "DEFAULT"). Can be used for a divergent identification of the SAP datahandler

Option to transfer controlling parameters to the SAP handler. The values are available in the CONTROL structure in the SAP datahandler.

Option to activate the debugging for the pertaining external data group only. "True" activates the debugging. SAP debugging is only possible if the portal is on your own computer and SAPGUI is installed.

When accessing tables, you can define that data should only be identified if a filter is not active with this parameter (active = "true"). This prevents hidden tables from being accessed in the SAP system in conjunction with dynamic filters.

Activates the trace for this data group. Extended messages for this will be provided in the logfile in doing so.

Contains a specification of which version of the business logic is required to avoid errors in advance (use of new features).

bia-simplekeyBooleanDG For SAP data groups with complex keys (e.g. VBAP), only a count from 1...n is used as the key for simplification reasons. A link to a details page is not possible here. However, this option can simplify access to cells within a free layout table.

If this option is acitvated, the data will be cached on the server. If the data in the SAP system is changed, the old data will still be displayed in the portal. The option is especially well-suited for customizing tables that are used as references (performance). The server-side cache can be reset by closing the connection to SAP.

This option is only relevant in the datahandlers for the Developer API. The SAP API method "Get_Detail" is not usually requested for new data records. However, this can be forced with this option to preallocate values from SAP.

This option is also only relevant within the Developer API. New data records are generally given the ID -1 by Intrexx. With this option, this default key is deleted. In SAP it would then be requestable with "if iv_key eq space".

As an alternative to the corresponding bia-variant, this option activates that the text table is not determined automatically in SAP. This allows problem cases such as the table MARA to be displayed in the portal with reasonable effort.

This option activates that specific data is transferred as HTML code instead of normal text. This option is, for example, used in the datahandler "Generic Report" to transfer an SAP report in the SAP-typical colors.

This option activates the transfer of longer texts as longtext instead of multiple lines. This option is used in the datahandler "Generic Report". The report is therefore not transferred in lines and needs to be presented as a free layout table. A string field contains the entire report with this option.

This option activates an automatic mapping of SAP-typical numberical keys. Via the defined length, the logic of the Connector for SAP Business Suite knows that this field needs to be completed with leading zeroes when transferrring to SAP (alphanumerical keys are an exception). These fields are presented without the leading zeroes in the portal. If this option is implemented at the data group level, the key is automaticall treated as a numerical SAP ID.

This option tries to solve the problem that time stamps usually are not used in SAP but separate fields for date and time instead. Whereas Intrexx uses time stamps and additionally can present these as "date only" or "time only". Using this option, the data field from the SAP system is informed as to which SAP field contains the corresponding time. The SAP date field becomes the time stamp in doing so and can be used as such (e.g. in calendar controls). When presenting times, the time is often displaced (e.g. 2h). This is because the SAP server and the portal run in different timezones (CET vs UTC). That is way, the SAP timezone can be configured in the data source or via bia-timezone. This function should also work the other way round (writing time stamps to two separate SAP fields). The field for the SAP date is key here as well. The corresponding time field may need to be available on the pages (hidden), however.

Encodings are often used in SAP systems (typical characters 1...6 fields; e.g. VBAK-VBTYP). These are transferred as text - meaning as SAP code - and cannot be used by the user therefore. There is of course the option to connect the corresponding customizing table in a language-dependent manner as a reference. However, this can be very complex in some circumstances. A simple option is available: the datahandler "Generic View" tries to identify suitable texts from the configured search help or other SAP mechanisms. This approach cannot be used everywhere (e.g. in more complex search helps with multiple keys).

With this option, URLS can be mapped whilst taking the portal URL into account. This is required for hiding the real URL on the SAP systems (calling archived documents), for example. An internal access can be mapped from "sapsystem.internesicht.net" to "archiv.externesicht.com" as soon as the user uses the exernal access to the Intrexx portal.

Makes the value upper-case. Useful in SAP matchcode fields.

Data browser: Display table contents

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

Implementation guide: Central SAP customizing

Table maintenance of configuration tables

Maintain RFC destinations: Configure access to external systems

Internet connectivity: Released services

Dump analysis: Debugging after cancellations

System log: Debugging for system problems

Application log: Protocols for many applications

Data exchange with external systems with qRFC and tRFC

User maintenance

Maintenance of permission objects: Generate with the function "SAP_ALL" among others

Roles and permissions

Permissions trace

Users online

Logged-in remote systems

ABAP Workbench: Central development transaction

ABAP reports: Development and start

Function modules/BAPI: Develop, test

BAPI browser