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 ...
随机推荐
- 类 __new__方法实现单例
继承了单例的类,子类也是单例模式
- Java中测试StringBuilder、StringBuffer、String在字符串拼接上的性能
应一个大量字符串拼接的任务 测试一下StringBuilder.StringBuffer.String在操作字符串拼接时候的性能 性能上理论是StringBuilder > StringBu ...
- codeforces-1114F-线段树练习
https://www.cnblogs.com/31415926535x/p/10391639.html 概述 这是一道用线段树维区间值的一道题,,题意很简单,,就是对于给定的一个序列,,初始时每个数 ...
- BZOJ.3252.攻略(贪心 长链剖分/线段树)
题目链接 贪心,每次选价值最大的一条到根的链.比较显然(不选白不选). 考虑如何维护这个过程.一个点的价值选了就没有了,而它只会影响它子树里的点,可以用DFS序+线段树修改.而求最大值也可以用线段树. ...
- Codeforces.842D.Vitya and Strange Lesson(Trie xor)
题目链接 /* 异或只有两种情况,可以将序列放到01Tire树上做 在不异或的情况下在Tire上查找序列的mex很容易,从高位到低位 如果0位置上数没有满,则向0递归:否则向1 (0位置上的数都满了 ...
- [Beijing wc2012]算不出的算式
OJ题号:BZOJ2659 思路:数学. 建立平面直角坐标系.在第一象限作直线y=qx/p,易得Σ[kq/p]即为当x<(p/2)时,直线下方(包括直线)的整点数:Σ[kp/q]为当y<( ...
- 如何调整eclipse中代码字体大小
找到windows--->preferences---->General------>Appearance---->color and fonts ---->ba ...
- Codeforces Round #408 (Div. 2) 题解【ABCDE】
A - Buying A House 题意:给你n个房间,妹子住在第m个房间,你有k块钱,你想买一个离妹子最近的房间.其中相邻的房间之间距离为10,a[i]=0表示已经被别人买了. 题解:扫一遍更新答 ...
- SIGALRM信号和SIGCHID信号
在进行堵塞式系统调用时.为避免进程陷入无限期的等待,能够为这些堵塞式系统调用设置定时器.Linux提供了alarm系统调用和SIGALRM信号实现这个功能. 要使用定时器.首先要安装SIGALRM信号 ...
- Revit API创建房间
start [Transaction(TransactionMode.Manual)] [Regeneration(RegenerationOption.Manual)] ); ...