Formats 
Formats
Use
You must specify for each node, per communication method, which message formats are permitted for messages sent by SAPconnect to the node. The communications system converts this format, if necessary, into another format in which it is sent.
If a message generated in the R/3 System has a format that the node does not support, SAPconnect can convert the message into a format supported by the node. An appropriate conversion rule is required for this.
Integration
If a message from an R/3 application or from the Business Workplace is sent to a SAPconnect node, the system checks whether the message format is supported by the node. If the format is supported, the message is sent on to the communications system without being converted. If the format is not supported, the system checks whether a conversion rule exists that converts the message into a format supported by the node.
If a node supports several formats into which messages can be converted, the order of precedence of the conversion rules is used.
If no appropriate conversion rule exists and the message has the SAP internal text format (RAW) or SAPscript format (SCR), intermediate conversion is performed. As standard, messages in RAW format are converted to SCR and messages in SCR format are converted to OTF. The system then searches for conversion rules for the new format. If no conversion rule for a format not supported by the node exists, the send process is terminated.
Examples of Conversion Process Flows:
The following conversion rules are available:
Format |
To format |
Order of precedence |
Function module |
OTF |
|
1 |
SX_OBJECT_CONVERT_OTF_PDF |
OTF |
PS |
2 |
SX_OBJECT_CONVERT_OTF_PRT |
OTF |
RAW |
9 |
SX_OBJECT_CONVERT_OTF_RAW |
RAW |
SCR |
9 |
SX_OBJECT_CONVERT_RAW_SCR |
SCR |
OTF |
9 |
SX_OBJECT_CONVERT_SCR_OTF |
A node has been created that supports the formats RAW, PDF and PS for the address type FAX and all formats (*) for the address type INT.
Message |
Type |
Supported format? |
Conversion |
|
RAW |
The node supports all formats (including RAW) for Internet messages. |
No conversion necessary. | |
Fax generated by an application |
OTF |
The node does not support OTF for fax messages. |
There are three rules that convert OTF into a format supported by the node. The rule highest in the order of precedence that converts the message into PDF format is used. |
Fax created by a user in the SAPscript editor |
SCR |
|
There are no rules that convert SCR into a format supported by the node. Therefore the rule that converts the message into OTF format is used. |
|
There are three rules that convert OTF into a format supported by the node. The rule highest in the order of precedence that converts the message into PDF format is used. | ||
Fax created by a user in the message editor |
RAW |
RAW documents are converted internally into SCR format for faxes. The node does not support SCR for fax messages. |
In conversion the fax message is handled in the same way as a fax in format SCR. |
If you specify that a node supports all formats, the SAP internal formats such as SCR, OTF or ALI are also transferred to the communications system without being converted. If a node supports SCR for example, faxes that were created in the Business Workplace are sent without being formatted in accordance with SAPscript. If a node supports ALI for example, ABAP lists are sent without being converted and may then be unreadable for an external application.
Activities
You assign the formats to a
node during the creation process. You can change formats in node maintenance. The following options are available for formatting:Function |
Description |
Allow all formats |
Select All Formats. All formats are transferred to the external communication system without being converted. |
Allow specified formats only |
Select Only the following formats and under Formats specify the formats that the external communication system supports. |
Disallow all formats except those specified |
Select All formats except the following and under Formats specify the formats that the external communication system does not support. If these are also SAPspecific formats, such as ABAP lists or SAPscript documents, choose SAPinternal formats. These formats (for example, ALI, SCR) are then entered automatically. |
You define the conversion rules in Customizing. You can change the Customizing settings while the system is in operation by choosing Settings ® Conversion rules in SAPconnect administration.
For information on which formats the external communications system can receive, see the relevant documentation. The communications system usually has its own conversion functions, so not all conversions need to be performed in the R/3 System.
SAPconnect can convert into all printer-specific formats for which a device type exists in R/3. The function module SX_OBJECT_CONVERT_OTF_PRT is used for this in the conversion rules. You must specify an appropriate device type for the corresponding format in node maintenance.
When OTF is converted into a printer-specific format, such as PS, temporary spool requests are generated. These are deleted in the next spool reorganization.
In the R/3 System, fax documents have the format OTF.
Example 1
If the connected fax system supports the format PCL, you can specify (for example):
Format: PCL
Device type: HPLJ4.
A conversion rule is required that converts the OTF to PCL:
OTF |
PCL |
1 |
SX_OBJECT_CONVERT_OTF_PRT |
Example 2
If the connected fax system supports the format PS, you can specify (for example):
Format: PS
Device type: POSTSCPT.
A conversion rule is required that converts the OTF to PS:
OTF |
PS |
1 |
SX_OBJECT_CONVERT_OTF_PRT |
The external fax system converts the contained format into the fax format TIF, for example.
You must specify a device type even if the node does not support a printer-specific format (but supports PDF instead, for example). In this case, we recommend that you use the type POSTSCPT.