Basic SAP Data Types
Basic SAP Data Types
The parameter types that the Microsoft BizTalk Adapter 3.0 for mySAP Business Suite supports are governed by the:
- ABAP data types that SAP supports
- Database data types that SAP supports
This section presents a mapping between the ABAP and database data types, and their corresponding .NET and XML schema types.
![]() |
---|
The information in this section applies to RFCs, tRFCs, and BAPIs. SAP data types are always represented as strings (xsd:string) in IDOCs. This is to support the BizTalk Server flat file parser. |
The Microsoft BizTalk Adapter 3.0 for mySAP Business Suite supports safe typing for some ABAP data types. When safe typing is enabled, these data types are represented as strings. You configure safe typing by setting the EnableSafeTyping binding property. Safe typing is disabled by default. For more information about the SAP adapter binding properties, see Working with BizTalk Adapter 3.0 for mySAP Business Suite Binding Properties.
The following table shows how the ABAP data types are surfaced when safe typing is not enabled. (EnableSafeTyping is false). Data types that are surfaced differently when safe typing is enabled are marked with an asterisk (*).
ABAP Data Type | RFC Type | XSD type | .NET type | Format string |
---|---|---|---|---|
I (Integer) |
RFC_INT |
xsd:int |
Int32 |
- |
Internal (RFC_INT1) |
RFC_INT1 |
xsd:unsignedByte |
Byte |
- |
Internal (RFC_INT2) |
RFC_INT2 |
xsd:short |
Int16 |
- |
F (Float) |
RFC_FLOAT |
xsd:double |
Double |
- |
P (BCD number) |
RFC_BCD |
xsd:decimal if length <= 28 |
Decimal |
Decimal number. with 0 decimal places |
C (Character) |
RFC_CHAR |
xsd:string |
String |
- |
D (Date: YYYYMMDD)* |
RFC_DATE |
xsd:dateTime |
DateTime |
Internally, the adapter deserializes the value into a DateTime object. It then invokes theDateTime.ToUniversalTime method to convert the value of this object to UTC. Finally the date component (DateTime.Date) is used to create the value that is sent to the SAP system. The SAP system treats this date value as local time. You should specify date values as UTC to avoid conversion.
|
T (Time: HHMMSS)* |
RFC_TIME |
xsd:dateTime |
DateTime |
Internally, the adapter deserializes the value into a DateTime object. It then invokes theDateTime.ToUniversalTime method to convert the value of this object to UTC. Finally the time component (DateTime.Time) is used to create the value that is sent to the SAP system. The SAP system treats this time value as local time. You should specify time values as UTC to avoid conversion.
For example, if your local time is 9:15 am, express this as "(001-01-01)T(09:15:00)Z" |
N (Numeric string)* |
RFC_NUM |
xsd:int if lenrth <= 9 |
Int32 |
- |
X (Byte) |
RFC_BYTE |
xsd:base64Binary |
Byte[] |
- |
STRING |
RFC_STRING |
xsd:string |
String |
- |
XSTRING |
RFC_BYTE |
xsd:base64Binary |
Byte[] |
- |
*Indicates that the data type is surfaced differently when safe typing is enabled.
Safe Typing Enabled
The following table shows the ABAP data types that are surfaced differently when safe typing is enabled (the EnableSafeTyping binding property is true).
ABAP Data Type | RFC Type | XSD type | .NET type | Format string |
---|---|---|---|---|
D (Date: YYYYMMDD) |
RFC_DATE |
xsd:string |
String |
SAP date format: YYYYMMDD. Characters are allowed for date digits, so the value is essentially an eight character string |
T (Time: HHMMSS) |
RFC_TIME |
xsd:string |
String |
SAP time format: HHMMSS. Characters are allowed for time digits, so the value is essentially a six character string |
N (Numeric string) |
RFC_NUM |
xsd:string |
String |
An n character string; where n = length of the numc field. |
ABAP data types that are not in this table are surfaced in the same way as when safe typing is not enabled.
Support for Date and Time Fields
When safe typing is not enabled, ABAP Date (D) and Time (T) types are surfaced as xsd:dateTime; however, the pattern facet surfaced for the Date and Time types is different.
- The pattern facet for Date is:
(\d\d\d\d-\d\d-\d\d)T(00:00:00)(.*)
For example, July 7, 2007 (2007-07-07) is represented as:
(2007-07-07)T(00:00:00)
. - The pattern facet for Time is:
(0001-01-01)T(\d\d:\d\d:\d\d)(.*)
For example, 18:30:30 (6:30 pm and 30 seconds) is represented as:
(0001-01-01)T(18:30:30)
.
How does the Adapter Represent Minimum and Maximum Time Values on Inbound Messages (from SAP)?
The SAP adapter uses the following guidelines when it receives time values from the SAP system:
- The adapter treats 000000 (hhmmss) and 240000 (hhmmss) as 0 hours, 0 mins, and 0 seconds.
The way in which the Microsoft BizTalk Adapter 3.0 for mySAP Business Suite surfaces database data types also depends on whether safe typing is enabled. The following table shows how the adapter surfaces database data types when safe typing is not enabled (the EnableSafeTyping binding property is false). Data types that are surfaced differently when safe typing is enabled are marked with an asterisk (*).
Database Data Type | RFC Type | XSD | .NET Type |
---|---|---|---|
ACCP (Posting Period)* |
RFC_NUM |
xsd:int |
Int32 |
CHAR |
RFC_CHAR |
xsd:string |
String |
CLNT (Client) |
RFC_CHAR |
xsd:string |
String |
CURR (Currency field) |
RFC_BCD |
xsd:decimal ![]() The SAP adapter rounds off the decimal values based on the definition of the DECIMAL parameter. For example, if a DECIMAL parameter can accept up to five digits after the decimal point, a value such as 4.000028 is rounded off to 4.00003.
|
Decimal |
CUKY (Currency Key) |
RFC_CHAR |
xsd:string |
String |
DATS (Date field)* |
RFC_DATE |
xsd:dateTime Internally, the adapter deserializes the value into a DateTime object. It then invokes theDateTime.ToUniversalTime method to convert the value of this object to UTC. Finally the date component (DateTime.Date) is used to create the value that is sent to the SAP system. The SAP system treats this date value as local time. You should specify date values as UTC to avoid conversion. The following pattern is recommended: "(\d\d\d\d-\d\d-\d\d)T(00:00:00)(.*)Z". |
DateTime You should specify date values as UTC (DateTime.Kind = DateTimeKind.Utc) to avoid conversion. |
DEC (Amount) |
RFC_BCD |
xsd:decimal ![]() The SAP adapter rounds off the decimal values based on the definition of the DECIMAL parameter. For example, if a DECIMAL parameter can accept up to five digits after the decimal point, a value such as 4.000028 is rounded off to 4.00003.
|
Decimal |
FLTP (Floating point) |
RFC_FLOAT |
xsd:double |
Double |
INT1 |
RFC_INT1 |
xsd:unsignedbyte |
Byte |
INT2 |
RFC_INT2 |
xsd:short |
Int16 |
INT4 |
RFC_INT |
xsd:int |
Int32 |
LANG (Language Key) |
RFC_CHAR |
xsd:string |
String |
LCHR |
RFC_STRING |
xsd:string |
String |
LRAW (long byte seq) |
RFC_BYTE |
xsd:base64binary |
Byte[] |
NUMC* |
RFC_NUM |
xsd:int |
Int32 if length <=9 |
PREC (Accuracy) |
RFC_INT2 |
xsd:short |
Int16 |
QUAN (Quantity) |
RFC_BCD |
xsd:decimal ![]() The SAP adapter rounds off the decimal values based on the definition of the DECIMAL parameter. For example, if a DECIMAL parameter can accept up to five digits after the decimal point, a value such as 4.000028 is rounded off to 4.00003.
|
Decimal |
RAW (byte sequence) |
RFC_BYTE |
xsd:base64binary |
Byte[] |
RAWSTRING (variable length) |
RFC_BYTE |
xsd:base64binary |
Byte[] |
STRING (variable length) |
RFC_STRING |
xsd:string |
String |
TIMS (Time field)* |
RFC_TIME |
xsd:datetime Internally, the adapter deserializes the value into a DateTime object. It then invokes theDateTime.ToUniversalTime method to convert the value of this object to UTC. Finally the time component (DateTime.Time) is used to create the value that is sent to the SAP system. The SAP system treats this time value as local time. You should specify time values as UTC to avoid conversion. The following pattern is recommended: "(0001-01-01)T(\d\d:\d\d:\d\d)(.*)Z". For example, if your local time is 9:15 am, express this as "(001-01-01)T(09:15:00)Z" |
DateTime You should specify time values as UTC (DateTime.Kind = DateTimeKind.Utc) to avoid conversion. |
UNIT (Unit for Qty) |
RFC_CHAR |
xsd:string |
String |
[Unsupported] |
-- |
-- |
String |
*Indicates that the adapter surfaces the data type differently when safe typing is enabled.
Safe Typing Enabled
The following table shows the database data types that are surfaced differently when safe typing is enabled (the EnableSafeTyping binding property is true).
Database Data Type | RFC Type | XSD | .NET type | String Value Format |
---|---|---|---|---|
ACCP (Posting Period) |
RFC_NUM |
xsd:string |
String |
Character string |
NUMC |
RFC_NUM |
xsd:string |
String |
Character string |
DATS (Date field) |
RFC_DATE |
xsd:string |
String |
YYYYMMDD |
TIMS (Time field) |
RFC_TIME |
xsd:string |
String |
HHMMSS |
Data types that are not in this table are surfaced in the same way as when safe typing is not enabled.
The SAP adapter supports the following XSD facets.
RFC Type | XSD Facet (EnableSafeTyping = false) | XSD Facet (EnableSafeTyping = true) |
---|---|---|
RFC_BCD |
XSD pattern facet Zero decimal places: One or more decimal places: |
same |
RFC_NUM |
XSD totalDigits facet if length <=19 XSD pattern facet if length > 19 |
XSD maxLength facet (depends on the length of the value on SAP) |
RFC_DATE |
XSD pattern facet
Pattern contains time 00:00:00 to be compatible with |
XSD maxLength facet = 8 |
RFC_TIME |
XSD pattern facet
Pattern contains date 0001-01-01 to be compatible with |
XSD maxLength facet = 6 |
RFC_CHAR |
XSD maxLength facet |
same |
Basic SAP Data Types的更多相关文章
- Core Java Volume I — 3.3. Data Types
3.3. Data TypesJava is a strongly typed language(强类型语音). This means that every variable must have a ...
- 【12c】扩展数据类型(Extended Data Types)-- MAX_STRING_SIZE
[12c]扩展数据类型(Extended Data Types)-- MAX_STRING_SIZE 在12c中,与早期版本相比,诸如VARCHAR2, NAVARCHAR2以及 RAW这些数据类型的 ...
- Oracle Schema Objects——Tables——Oracle Data Types
Oracle Schema Objects Oracle Data Types 数据类型 Data Type Description NUMBER(P,S) Number value having a ...
- C and SQL data types for ODBC and CLI
C and SQL data types for ODBC and CLI This topic lists the C and SQL data types for ODBC and CLI a ...
- allow zero datetime=true导致datetime转换失败:MySql.Data.Types.MySqlDateTime”的对象无法转换为类型“System.Nullable`1[System.DateTime]
allow zero datetime=true导致datetime转换失败:MySql.Data.Types.MySqlDateTime”的对象无法转换为类型“System.Nullable`1[S ...
- "SQL Server does not handle comparison of NText, Text, Xml, or Image data types."
"SQL Server does not handle comparison of NText, Text, Xml, or Image data types." sql2000 ...
- ExtJS笔记 Ext.data.Types
This is a static class containing the system-supplied data types which may be given to a Field. Type ...
- Entity Framework Code First (七)空间数据类型 Spatial Data Types
声明:本文针对 EF5+, Visual Studio 2012+ 空间数据类型(Spatial Data Types)是在 EF5 中引入的,空间数据类型表现有两种: Geography (地理学上 ...
- Delphi Data Types
http://docwiki.embarcadero.com/RADStudio/XE6/en/Delphi_Data_Types Integer Data Types Type Descriptio ...
随机推荐
- php字符串截取
保留字符串前面的 substr($str,start[,$length]); start 为负数 则从后面开始截取 leng为负数则返回的字符串将从 $str 结尾处向前数第 start 个字符开始 ...
- SQL HAVING 子句使用
HAVING 对由sum或其它集合函数运算结果的输出进行限制. 比如,我们可能只希望看到Store_Information数据表中销售总额超过1500美圆的商店的信息,这时我们就需要使用HAVING从 ...
- Vijos.lxhgww的奇思妙想(k级祖先 长链剖分)
题目链接 https://blog.bill.moe/long-chain-subdivision-notes/ http://www.cnblogs.com/zzqsblog/p/6700133.h ...
- JavaScript 比较好的建议
规范JavaScript 编码 1,一个函数体内的变量声明只使用一个var var aaa, bbb, ccc; 2, 保持框架习惯一致性 比如使用jQuery的 $获取DOM ,就不要再去混合使用g ...
- 3DMax 2014中文版安装破解教程
周末的时候,因为帮忙别人做动画,要用到3dmax.然后发现自己真的很菜啊....弄了好久,然后终于阔以了,以后在慢慢研究.贴出详细的步骤: . 1.如果没有软件,就请自行下载[百度上很多的] 2.双击 ...
- java连接数据库插入数据中文乱码
解决方案: jdbc连接数据库,向表中插入中文查看数据乱码:修改数据库连接url为jdbc:mysql://127.0.0.1:3306/test?characterEncoding=utf-8 注意 ...
- A - K进制下的大数
https://vjudge.net/contest/218366#problem/A 中间溢出,注意求模. #include<iostream> #include<cstdio&g ...
- NDArray自动求导
NDArray可以很方便的求解导数,比如下面的例子:(代码主要参考自https://zh.gluon.ai/chapter_crashcourse/autograd.html) 用代码实现如下: im ...
- 使用OClint进行iOS项目的静态代码扫描
使用OClint进行iOS项目的静态代码扫描 原文链接:http://blog.yourtion.com/static-code-analysis-ios-using-oclint.html 最近需要 ...
- ${pageContext.request.contextPath}无法解析
摘要 突然出现无法解析${pageContext.request.contextPath}的问题,在点击<a href="${pageContext.request.contextPa ...