NAD010 data type must be 'Alphanumeric' in EDIFACT D96A INVOIC

Hi B2B GURUS,
I am new to B2B, I was trying to integrate EDIFACT D96A INVOIC from BPEL to B2B.
I got below error in B2B:Can some one please help on this.
Element NAD010 data type must be 'Alphanumeric'. Segment NAD is defined in the guideline at position 0120.{br}{br}This error was detected at:{br}{tab}Segment Count: 6{br}{tab}Element Position: 3 {br}{tab}Characters: 2012 through 2049
XML published to B2B ==>
<Invoke_SendInvoiceToB2b_Enqueue_InputVariable_1><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="Transaction-INVOIC"><Transaction-INVOIC xmlns:ns1="urn:oracle:integration:b2b:EB1F987EE11A4A3E98E3345554E5DB13" Standard="EDIFACT" Version="VD96A" GUID="{2d333538-3630-3735-3039-313132343638}" xmlns="urn:oracle:integration:b2b:EB1F987EE11A4A3E98E3345554E5DB13">
<ns1:Segment-UNH>
<ns1:Element-0062>3210012325</ns1:Element-0062>
<ns1:Composite-S009>
<ns1:Element-0065>INVOIC</ns1:Element-0065>
<ns1:Element-0052>D</ns1:Element-0052>
<ns1:Element-0054>96A</ns1:Element-0054>
<ns1:Element-0051>UN</ns1:Element-0051>
<ns1:Element-0057>EAN008</ns1:Element-0057>
</ns1:Composite-S009>
</ns1:Segment-UNH>
<ns1:Segment-BGM>
<ns1:Composite-C002>
<ns1:Element-1001>380</ns1:Element-1001>
</ns1:Composite-C002>
<ns1:Element-1004>3210000019</ns1:Element-1004>
</ns1:Segment-BGM>
<ns1:Segment-DTM>
<ns1:Composite-C507>
<ns1:Element-2005>137</ns1:Element-2005>
<ns1:Element-2380>21120821</ns1:Element-2380>
<ns1:Element-2379>102</ns1:Element-2379>
</ns1:Composite-C507>
</ns1:Segment-DTM>
<ns1:Loop-Group_1>
<ns1:Segment-RFF>
<ns1:Composite-C506>
<ns1:Element-1153>VN</ns1:Element-1153>
<ns1:Element-1154>3210012325</ns1:Element-1154>
</ns1:Composite-C506>
</ns1:Segment-RFF>
<ns1:Segment-DTM>
<ns1:Composite-C507>
<ns1:Element-2005>171</ns1:Element-2005>
<ns1:Element-2380>21120821</ns1:Element-2380>
<ns1:Element-2379>102</ns1:Element-2379>
</ns1:Composite-C507>
</ns1:Segment-DTM>
</ns1:Loop-Group_1>
<ns1:Loop-Group_2>
<ns1:Segment-NAD>
<ns1:Element-3035>BY</ns1:Element-3035>
<ns1:Composite-C082>
<ns1:Element-3039>541218011234</ns1:Element-3039>
<ns1:Element-3055>9</ns1:Element-3055>
</ns1:Composite-C082>
<ns1:Composite-C058>
<ns1:Element-3124>Flex ABC Division GH-94404</ns1:Element-3124>
</ns1:Composite-C058>
<ns1:Composite-C080>
<ns1:Element-3036>ABC ABC Ltd</ns1:Element-3036>
</ns1:Composite-C080>
<ns1:Composite-C059>
<ns1:Element-3042>tyu Wei 45</ns1:Element-3042>
</ns1:Composite-C059>
<ns1:Element-3164>werentem</ns1:Element-3164>
<ns1:Element-3251>B-455</ns1:Element-3251>
<ns1:Element-3207>BE</ns1:Element-3207>
</ns1:Segment-NAD>
</ns1:Loop-Group_2>
<ns1:Loop-Group_7>
<ns1:Segment-CUX>
<ns1:Composite-C504>
<ns1:Element-6347>2</ns1:Element-6347>
<ns1:Element-6345>EUR</ns1:Element-6345>
<ns1:Element-6343>4</ns1:Element-6343>
</ns1:Composite-C504>
</ns1:Segment-CUX>
</ns1:Loop-Group_7>
<ns1:Loop-Group_8>
<ns1:Segment-PAT>
<ns1:Element-4279>5</ns1:Element-4279>
<ns1:Composite-C110>
<ns1:Element-4277>30</ns1:Element-4277>
</ns1:Composite-C110>
<ns1:Composite-C112>
<ns1:Element-2475/>
<ns1:Element-2009/>
<ns1:Element-2151>D</ns1:Element-2151>
<ns1:Element-2152>30</ns1:Element-2152>
</ns1:Composite-C112>
</ns1:Segment-PAT>
<ns1:Segment-DTM>
<ns1:Composite-C507>
<ns1:Element-2005>12</ns1:Element-2005>
<ns1:Element-2380/>
<ns1:Element-2379>102</ns1:Element-2379>
</ns1:Composite-C507>
</ns1:Segment-DTM>
<ns1:Segment-PCD>
<ns1:Composite-C501>
<ns1:Element-5245>12</ns1:Element-5245>
<ns1:Element-5482/>
</ns1:Composite-C501>
</ns1:Segment-PCD>
<ns1:Segment-MOA>
<ns1:Composite-C516>
<ns1:Element-5025>21</ns1:Element-5025>
<ns1:Element-5004/>
</ns1:Composite-C516>
</ns1:Segment-MOA>
</ns1:Loop-Group_8>
<ns1:Loop-Group_25>
<ns1:Segment-LIN>
<ns1:Element-1082>1</ns1:Element-1082>
</ns1:Segment-LIN>
<ns1:Segment-PIA>
<ns1:Element-4347>NH</ns1:Element-4347>
<ns1:Composite-C212_1>
<ns1:Element-7140>LDI323010</ns1:Element-7140>
</ns1:Composite-C212_1>
</ns1:Segment-PIA>
<ns1:Segment-IMD>
<ns1:Element-7077>F</ns1:Element-7077>
<ns1:Element-7081>DSC</ns1:Element-7081>
<ns1:Composite-C273>
<ns1:Element-7008>ABCD IND/ Lux</ns1:Element-7008>
</ns1:Composite-C273>
</ns1:Segment-IMD>
<ns1:Segment-QTY>
<ns1:Composite-C186>
<ns1:Element-6063>46</ns1:Element-6063>
<ns1:Element-6060>10</ns1:Element-6060>
</ns1:Composite-C186>
</ns1:Segment-QTY>
<ns1:Loop-Group_28>
<ns1:Segment-PRI>
<ns1:Composite-C509>
<ns1:Element-5125>AAA</ns1:Element-5125>
<ns1:Element-5118>769.31</ns1:Element-5118>
</ns1:Composite-C509>
</ns1:Segment-PRI>
</ns1:Loop-Group_28>
<ns1:Loop-Group_29>
<ns1:Segment-RFF>
<ns1:Composite-C506>
<ns1:Element-1153>ON</ns1:Element-1153>
<ns1:Element-1154>3210000025</ns1:Element-1154>
<ns1:Element-1156>1</ns1:Element-1156>
</ns1:Composite-C506>
</ns1:Segment-RFF>
</ns1:Loop-Group_29>
<ns1:Loop-Group_33>
<ns1:Segment-MOA>
<ns1:Composite-C516>
<ns1:Element-5025>124</ns1:Element-5025>
<ns1:Element-5004>461.59</ns1:Element-5004>
</ns1:Composite-C516>
</ns1:Segment-MOA>
</ns1:Loop-Group_33>
<ns1:Loop-Group_38>
<ns1:Loop-Group_43>
<ns1:Segment-TAX>
<ns1:Element-5283>7</ns1:Element-5283>
<ns1:Composite-C243>
<ns1:Element-5278>6</ns1:Element-5278>
</ns1:Composite-C243>
<ns1:Element-5305>S</ns1:Element-5305>
</ns1:Segment-TAX>
</ns1:Loop-Group_43>
</ns1:Loop-Group_38>
</ns1:Loop-Group_25>
<ns1:Loop-Group_50>
<ns1:Segment-MOA>
<ns1:Composite-C516>
<ns1:Element-5004/>
</ns1:Composite-C516>
</ns1:Segment-MOA>
</ns1:Loop-Group_50>
<ns1:Segment-UNT>
<ns1:Element-0074>#SegmentCount#</ns1:Element-0074>
<ns1:Element-0062>3210000019</ns1:Element-0062>
</ns1:Segment-UNT>
</Transaction-INVOIC>
</part></Invoke_SendInvoiceToB2b_Enqueue_InputVariable_1>

Hi Vikky,
Glad that it worked but I am wondering why alphanumeric will allow only UPPERCASE characters. It works properly for me with lowercase characters as well. If you don't mind, can you please forward your ecs, xsd and the sample payload to my id (in my profile). Just want to check where is the gap.
Regards,
Anuj

Similar Messages

Data types pls..

Hi All,
What are all the data types we have, let me know each data type purpose pls....
Akshitha.

Data types describe the technical attributes of data objects. They are purely descriptive and do not take up any memory space
Data Types in the ABAP Dictionary
The ABAP Dictionary allows you to define global data types. You can use the TYPE addition of an appropriate ABAP statement to refer to these data types in any ABAP program in the system.
There are three groups on the initial screen:
Database Tables and Views
One of the most important tasks of the ABAP Dictionary is to administer database tables in the R/3 database. The Dictionary contains metadescriptions of the database tables, and uses these to create the physical tables in the database. A view is a "virtual table" containing fields from one or more tables.
In the description of a database table, the table lines consist of single fields or columns. An elementary data type must be assigned to each column. The elementary types in the ABAP Dictionary are data elements. Like data objects in ABAP programs, database tables and views have data types as attributes. A line of a database table or view has the data type of a flat structure, which consists of individual data elements.
In ABAP programs, you can use the TYPE addition with the data type of a database table or view. You may refer to the whole structure or to individual components:
... TYPE <dbtab> ...
refers to the complex data type of the structure,
... TYPE <dbtab>-<ci> ...
refers to the elementary data type of component <ci>.
If you define a complex data type <t> as a structure using
TYPES <t> TYPE <dbtab>.
the components of the data type <t> inherit the names of the components of the database table or view, and can be addressed in the program using <t>-<ci>.
To ensure compatibility with previous releases, you can still use the LIKE addition to refer to database tables or views, except within classes. The reason for this is that in earlier releases, the physical presence of the database tables as objects was emphasized, even though the Dictionary only contains metadescriptions and data types.
Defining program-local data types by referring to database tables and views is one of the essential techniques for processing data from database tables in ABAP. Data objects that you define in this way always have the right type to contain data from the corresponding database table. ABAP Open SQL allows you to read a single field, a range of fields, or an entire database table or view into an internal table.
TYPES: city type spfli-cityfrom,
 spfli_type TYPE STANDARD TABLE OF spfli WITH DEFAULT KEY.
DATA: wa_city TYPE city,
 wa_spfli TYPE spfli_type.
SELECT SINGLE cityfrom FROM spfli
 INTO wa_city
 WHERE carrid = 'LH' AND connid = '400'.
SELECT * FROM spfli INTO TABLE wa_spfli.
This example defines an elementary data type CITY that refers to a single field of the database table SPFLI and an internal table SPFLI_TYPE, whose line type is the same as the structure of the database table. The SELECT statement reads data from the database into the corresponding data objects.
Data types
Data types are the actual type definitions in the ABAP Dictionary. They allow you to define elementary types, reference types, and complex types that are visible globally in the system. The data types of database tables are a subset of all possible types, namely flat structures. Global object types (classes and interfaces) are not stored in the ABAP Dictionary, but in the class library. You create them using the Class Builder.
For a detailed description of data types and their definitions, refer to the Types section of the ABAP Dictionary documentation. The following descriptions mention the types only briefly, along with how you can refer to them from ABAP programs.
Data Elements
Data elements in the ABAP Dictionary describe individual fields. They are the smallest indivisible units of the complex types described below, and are used to specify the types of columns in the database. Data elements can be elementary types or reference types.
Elementary Types
Elementary types are part of the dual-level domain concept for fields in the ABAP Dictionary. The elementary type has semantic attributes, such as texts, value tables, and documentation, and has a data type. There are two different ways to specify a data type:
By directly assigning an ABAP Dictionary type.
You can assign a predefined ABAP Dictionary type and a number of characters to an elementary type. The ABAP Dictionary has considerably more predefined types than the ABAP programming language. The number of characters here is not the field length in bytes, but the number of valid characters excluding formatting characters. The data types are different because the predefined data types in the ABAP Dictionary have to be compatible with the external data types of the database tables supported by the R/3 System.
When you refer to data types from the ABAP Dictionary in an ABAP program, the predefined Dictionary types are converted to ABAP types as follows:
Dictionary type
Meaning
Maximum length n
ABAP type
DEC
Calculation/amount field
1-31, 1-17 in tables
P((n+1)/2)
INT1
Single-byte integer
3
Internal only
INT2
Two-byte integer
5
Internal only
INT4
Four-byte integer
10
I
CURR
Currency field
1-17
P((n+1)/2)
CUKY
Currency key
5
C(5)
QUAN
Amount
1-17
P((n+1)/2)
UNIT
Unit
2-3
C(n)
PREC
Accuracy
2
X(2)
FLTP
Floating point number
16
F(8)
NUMC
Numeric text
1-255
N(n)
CHAR
Character
1-255
C(n)
LCHR
Long character
256-max
C(n)
STRING.
String of variable length
1-max
STRING.
RAWSTRING
Byte sequence of variable length
1-max
XSTRING
DATS
Date
8
D
ACCP
Accounting period YYYYMM
6
N(6)
TIMS
Time HHMMSS
6
T
RAW
Byte sequence
1-255
X(n)
LRAW
Long byte sequence
256-max
X(n)
CLNT
Client
3
C(3)
LANG
Language
internal 1, external 2
C(1)
("max" in LCHR and LRAW is the value of a preceding INT2 field. The "internal" length of a LANG field is in the Dictionary, the "external" length refers to the display on the screen.
Assigning a domain
The technical attributes are inherited from a domain. Domains are standalone Repository objects in the ABAP Dictionary. They can specify the technical attributes of a data element. One domain can be used by any number of data elements. When you create a domain, you must specify a Dictionary data type (see above table) and the number of characters.
Reference Types
Reference types describe single fields that can contain references to global classes and interfaces from the ABAP class library.
In an ABAP program, you can use the TYPE addition to refer directly to a data element. The predefined Dictionary data types of the domain are then converted into the corresponding ABAP types.
If you define a local data type in a program by referring to a data element as follows:
TYPES <t> TYPE <data element>.
the semantic attributes of the data element are inherited and will be used, for example, when you display a data object with type <t> on the screen. Since all data types in the ABAP Dictionary are based on data elements, they all contain the corresponding semantic attributes.
TYPES company TYPE s_carr_id.
DATA wa_company TYPE company.
wa_company = 'UA '.
WRITE: 'Company:', wa_company.
This example defines a local type COMPANY that refers to the data element S_CARR_ID. The data element is linked to the identically-named domain S_CARR_ID. The domain defines the technical attributes as data type CHAR with length 3. The local data type COMPANY in the program therefore has the ABAP type C(3). COMPANY also adopts the semantic attributes of the data element. In the above example, we declare a data object WA_COMPANY with this type and display it on a list. If the user chooses F1 help for the output field, the help text stored in the ABAP Dictionary will appear in a dialog box.
Structures
A structure is a sequence of any other data types from the ABAP Dictionary, that is, data elements, structures, table types, or database tables. When you create a structure in the ABAP Dictionary, each component must have a name and a data type.
In an ABAP program, you can use the TYPE addition to refer directly to a structure.
If you define a local data type in a program by referring to a structure as follows:
TYPES <t> TYPE <structure>.
the construction blueprint of the structure is used to create a local structure <t> in the program. The predefined Dictionary data types of the domains used by the data elements in the structure are converted into the corresponding ABAP types. The semantic attributes of the data elements are used for the corresponding components of the structure in the program. The components of the local structure <t> have the same names as those of the structure in the ABAP Dictionary.
To ensure compatibility with previous releases, it is still possible to use the LIKE addition in an ABAP program to refer to a structure in the ABAP Dictionary (except in classes).
Suppose the structure STRUCT is defined as follows in the ABAP Dictionary:
Field name
Type name
Description
COL1
CHAR01
Character field with length 1
COL2
CHAR08
Character field with length 8
COL3
CHAR10
Character field with length 10
The types CHAR01 to CHAR10 are data elements with corresponding domains. We can refer to this structure in ABAP:
TYPES struct_type TYPE struct.
DATA wa TYPE struct_type.
wa-col1 = '1'.
wa-col2 = '12345678'.
wa-col3 = '1234567890'.
This program creates a local structure in the program - STRUCT_TYPE - and a corresponding data object WA. We can address the components using the component names from the original structure.
Table Types
Table types are construction blueprints for internal tables that are stored in the ABAP Dictionary. When you create a table type in the ABAP Dictionary, you specify the line type, access type, and key. The line type can be any data type from the ABAP Dictionary, that is, a data element, a structure, a table type, or the type of a database table. You can also enter a predefined Dictionary type directly as the line type, in the same way that you can with a domain.
In an ABAP program, you can use the TYPE addition to refer directly to a table type.
If you define a local data type in a program by referring to a table type as follows:
TYPES <t> TYPE <table>.
the construction blueprint of the table type is used to create a local internal table <t> in the program. The predefined Dictionary data types of the domains used by the data elements in the structure are converted into the corresponding ABAP types. The semantic attributes of the data elements are used for the corresponding components of the internal table in the program.
Suppose the table type STRUCT_TABLE is defined in the Dictionary with the line type STRUCT from the previous example. We can refer to this in ABAP:
TYPES table_type TYPE struct_table.
DATA: table_wa TYPE table_type,
 line_wa LIKE LINE OF table_wa.
LOOP AT table_wa INTO line_wa.
WRITE: line_wa-col1, line_wa-col1, line_wa-col1.
ENDLOOP.
This program defines an internal table type TABLE_TYPE. From it, we define data objects TABLE_WA and LINE_WA. LINE_WA corresponds to the line type of the table type in the Dictionary, and is therefore compatible with the structure STRUCT.
Type Groups
Before Release 4.5A, it was not possible to define standalone types in the ABAP Dictionary to which you could refer using a TYPE addition in an ABAP program. It was only possible to refer to flat structures. Structures in programs corresponded to the structures of database tables or structures in the ABAP Dictionary. In ABAP programs, you could only refer to database tables and structures in the ABAP Dictionary using LIKE. It was, however, possible to refer to individual components of the Dictionary type. Complex local data types such as internal tables or deep structures had no equivalent in the ABAP Dictionary. The solution to this from Release 3.0 onwards was to use type groups. Type groups were based on the include technique, and allowed you to store any type definitions globally in the Dictionary by defining them using TYPES statements.
The definition of a type group is a fragment of ABAP code which you enter in the ABAP Editor. The first statement for the type group <pool> is always:
TYPE-POOL <pool>.
After this came the definitions of data types using the TYPES statement, as described in Local Data Types in Programs. It was also possible to define global constants using the CONSTANTS statement. All the names of these data types and constants must begin with the name of the type group and an underscore:
In an ABAP program, you must declare a type group as follows before you can use it:
TYPE-POOLS <pool>.
This statement allows you to use all the data types and constants defined in the type group <pool> in your program. You can use several type groups in the same program.
Let the type group HKTST be created as follows in the ABAP Dictionary:
TYPE-POOL hktst.
TYPES: BEGIN OF hktst_typ1,
 col1(10) TYPE c,
 col2 TYPE i,
 END OF hktst_typ1.
TYPES hktst_typ2 TYPE p DECIMALS 2.
CONSTANTS hktst_eleven TYPE i VALUE 11.
This type group defines two data types HKTST_TYP1 and HKTST_TYP2, as well as a constant HKTST_ELEVEN with the value 11.
Any ABAP program can use these definition by including a TYPE-POOLS statement:
TYPE-POOLS hktst.
DATA: dat1 TYPE hktst_typ1,
 dat2 TYPE hktst_typ2 VALUE '1.23'.
WRITE: dat2, / hktst_eleven.
The output is:
1,23
11
The data types defined in the type group are used to declare data objects with the DATA statement and the value of the constant is, as the output shows, known in the program.

How to handle "Variant" data type?

I am using SQL 2000, and want to use "Variant" data type. Can I handle it in java with ODBC connection? What classes and methods need I use? Thanks a lot.

ODBC does not have a notion of variant types. This limits the use of the sql_variant data type with an ODBC driver in SQL Server 2000. In SQL Server 2000, if binding is specified, the sql_variant data type must be bound to one of the documented ODBC data types.
(Quote from http://msdn.microsoft.com/library/en-us/odbcsql/od_6_020_28yr.asp )
Possible solutions:
- CAST or CONVERT the datatype to another suitable data type in the query
OR
- Retrieve the column as a binary stream

Regarding QUAN data type and Parameter id

Dear all
i have a doubt that is...im creating 3 fields LENGTH,BREADTH,THICKNESS for which i have used (LAENG,BRIET)but the data type QUAN is of length 13 characters, now im using theses fields in a screen and when i try to enter 3 digit value into these input fields i get the error ....Entry too long (enter in the format ~.__). and i replace it with 2 digit it will accept.
and one more.
each and every screen field value can be passed to the program only by PRAMAETER id statement or can u please suggest me the best possible way to pass the screen values to the program.

Hi Naren
If you have to consider the commas and dots also in output lenght which is 17
10 digits
3 digits after decimal point
= 13 "Length
1 decimal point
3 commas
= 4
13 + 4 = 17 "Output Length
if you enter 1,234,567,890.123 OR 1234567890 it will except
But if you will enter 12345678901 it will not because ... it will not accept 11 digits... less then 11 digits it will except...
also if you pass the 10 digits then decimal point and then upto 3 digits afrter the decimal point then also it will accept...
Try to Debug the code and check the value of the parameter ID you are passing in screen...
Check for the above validation...
also check out the data type must match...
post your code as well here so we can give better suggestion on it...
Also there is no parameter ID for the Dataelement LAENG
For passing values to other report have a look on below thread..
Reg: SUBMIT WITH Free Selections
Also Search on SCN using SUBMIT and also have a look on ABAP help for SUBMIT statmetn for better idea...
Hope it will solve your problem..
Thanks & Regards
ilesh 24x7
ilesh Nandaniya

Please help me in understanding the EDIFACT D96A format for INVOICE

Hi,
Im doing an INVOICE02 IDOC to EDIFACT D96A INVOIC scenario. Im new to EDI.
Pls Pls Pls Pls kindly help me in understanding the following EDIFACT D96A file.
UNBUNOA:35410033000055:145400110000009:14070612:085511137INV96A+EANCOM1'
UNH1INVOIC:D:96A:UN:EAN008'
BGM3805010237529+9'
DTM+137:200706120000:203'
DTM+35:20070612:102'
DTM+454:20070612:102'
RFF+ON:32210'
DTM+171:20070612:102'
RFF+DQ:000030585715'
DTM+171:20070612:102'
NADSU5410148000001::9+BVBA Unilever Belgium SPRLBl.De L?'Humanité 292 292Bruxelles1190BE'
RFF+VA:BE438390312'
RFF+ARA:0438390312'
NADBY5400110000009::9+D.L.L.RUE OSSEGHEM 53-MOLENBEEKMOLENBEEK-SAINT-JEAN1080BE'
NADDP5400110000009::9+D.L.L.RUE OSSEGHEM 53-MOLENBEEKMOLENBEEK-SAINT-JEAN1080BE'
NADIV5400110000009::9+DELHAIZE FRS. CENTRALESRUE OSSEGHEM , 53BRUSSEL-MOLENBEEK1080BE'
RFF+VA:BE402206045'
RFF+ARA:0402206045'
CUX+2:EUR:4'
LIN10+8000920900987:EN'
PIA1000000000019009801:SA'
IMDF+IN:::IGLO POELEE LEGUMES CHAMPIGNONS 6X8'
QTY+47:81'
QTY+46:81'
MOA+203:1584.4'
PRI+AAA:19.56'
PRI+AAB:21.24'
TAX7VAT+++:::6.000'
MOA+125:1584.4'
ALCA++1'
PCD+1:0:1'
ALCA++1'
PCD+1:1.97:1'
ALCA++1'
PCD+1:1.96:1'
LIN20+5410148126459:EN'
PIA1000000000011264501:SA'
IMDF+IN:::Epinards hachis en portions '
QTY+47:112'
QTY+46:112'
MOA+203:1061.01'
PRI+AAA:9.47'
PRI+AAB:10.96'
TAX7VAT+++:::6.000'
MOA+125:1061.01'
ALCA++1'
PCD+1:0:1'
ALCA++1'
PCD+1:1.97:1'
ALCA++1'
PCD+1:1.96:1'
LIN40+5410148013452:EN'
PIA1000000000010134500:SA'
IMDF+IN:::15 Fish Sticks Colin d?'Alaska '
QTY+47:256'
QTY+46:256'
MOA+203:4937.63'
PRI+AAA:19.29'
PRI+AAB:20.16'
TAX7VAT+++:::6.000'
MOA+125:4937.63'
ALCA++1'
PCD+1:0:1'
ALCA++1'
PCD+1:1.97:1'
LIN50+5414807999958:EN'
PIA1000000000019999501:SA'
IMDF+IN:::Iglo Poisson Pané Epinards 7X400g'
QTY+47:180'
QTY+46:180'
MOA+203:4160.31'
PRI+AAA:23.11'
PRI+AAB:24.08'
TAX7VAT+++:::6.000'
MOA+125:4160.31'
ALCA++1'
PCD+1:0:1'
ALCA++1'
PCD+1:1.97:1'
LIN60+5410148120952:EN'
PIA1000000000011209501:SA'
IMDF+IN:::Epinards Crhme en Portions '
QTY+47:112'
QTY+46:112'
MOA+203:1594.69'
PRI+AAA:14.24'
PRI+AAB:15.92'
TAX7VAT+++:::6.000'
MOA+125:1594.69'
ALCA++1'
PCD+1:0:1'
ALCA++1'
PCD+1:1.97:1'
ALCA++1'
PCD+1:1.96:1'
LIN70+5410148124158:EN'
PIA1000000000011241503:SA'
IMDF+IN:::EPINARDS HACHES EN PORTIONS 450G'
QTY+47:144'
QTY+46:144'
MOA+203:938.01'
PRI+AAA:6.51'
PRI+AAB:7.44'
TAX7VAT+++:::6.000'
MOA+125:938.01'
ALCA++1'
PCD+1:0:1'
ALCA++1'
PCD+1:1.97:1'
ALCA++1'
PCD+1:1.96:1'
LIN120+5410148016729:EN'
PIA1000000000010167201:SA'
IMDF+IN:::Macaroni Fromage/Jambon '
QTY+47:260'
QTY+46:260'
MOA+203:4337.55'
PRI+AAA:16.68'
PRI+AAB:17.58'
TAX7VAT+++:::6.000'
MOA+125:4337.55'
ALCA++1'
PCD+1:0:1'
ALCA++1'
PCD+1:1.97:1'
LIN130+5410148441255:EN'
PIA1000000000014412503:SA'
IMDF+IN:::CHOUX ROUGES AUX POMMES 450G'
QTY+47:144'
QTY+46:144'
MOA+203:1756.99'
PRI+AAA:12.2'
PRI+AAB:13.36'
TAX7VAT+++:::6.000'
MOA+125:1756.99'
ALCA++1'
PCD+1:0:1'
ALCA++1'
PCD+1:1.97:1'
ALCA++1'
PCD+1:1.96:1'
LIN140+5410148017702:EN'
PIA1000000000010177001:SA'
IMDF+IN:::Frit?'Kot 1'
QTY+47:60'
QTY+46:60'
MOA+203:1102.6'
PRI+AAA:18.38'
PRI+AAB:22'
TAX7VAT+++:::6.000'
MOA+125:1102.6'
ALCA++1'
PCD+1:0:1'
ALCA++1'
PCD+1:1.97:1'
ALCA++1'
PCD+1:4.9:1'
LIN180+8000920801796:EN'
PIA1000000000018017901:SA'
IMDF+IN:::EPINARDS EN BRANCHES 10 X 450'
QTY+47:190'
QTY+46:190'
MOA+203:2204.2'
PRI+AAA:11.6'
PRI+AAB:12.9'
TAX7VAT+++:::6.000'
MOA+125:2204.2'
ALCA++1'
PCD+1:0:1'
ALCA++1'
PCD+1:1.97:1'
ALCA++1'
PCD+1:1.96:1'
LIN200+5410148014268:EN'
PIA1000000000010142602:SA'
IMDF+IN:::PETITS POIS EXTRA FINS 450G'
QTY+47:238'
QTY+46:238'
MOA+203:1999.6'
PRI+AAA:8.4'
PRI+AAB:9.24'
TAX7VAT+++:::6.000'
MOA+125:1999.6'
ALCA++1'
PCD+1:0:1'
ALCA++1'
PCD+1:1.97:1'
ALCA++1'
PCD+1:1.96:1'
LIN230+8000920807248:EN'
PIA1000000000018072403:SA'
IMDF+IN:::IGLO POUL ET PENNE AUX LEG.SOLEI. 6'
QTY+47:99'
QTY+46:99'
MOA+203:1727.54'
PRI+AAA:17.45'
PRI+AAB:18.3'
TAX7VAT+++:::6.000'
MOA+125:1727.54'
ALCA++1'
PCD+1:0:1'
ALCA++1'
PCD+1:1.97:1'
UNS+S'
CNT+2:12'
MOA+124:1644.27'
MOA+86:29048.8'
MOA+79:27404.53'
MOA+125:27404.53'
TAX7VAT++:::6.000S'
MOA+125:27404.50'
MOA+124:1644.27'
UNT2121'
UNZ111137'
Advance appreciations,
Ram.

Its very simple:
UNB-segment : Interchange Header
S001     SYNTAX IDENTIFIER
0001     Syntax Identifier                    UNOA
0002     Syntax version number               2
S002     INTERCHANGE RECIPIENT
0004     Sender Identification                    8711382000091 (= GLN Code Tilburg)
0007     Identification Code Qualifier               14
S003     INTERCHANGE SENDER
0004     Recipient Identification               8711700400008(= GLN Code Unilever)
0007     Identification Code Qualifier               14
S004     DATE/TIME OF PREPARATION
0017     Date                            YYMMDD
0019     Time                            HHMM
0020     INTERCHANGE CTRL REF.     Unique message reference number
0026     APPLICATION REFERENCE          WMS0330
UNH-segment: Message header
0062     MESSAGE REFERENCE NUMBER      Unique sequence numbe within UNB
S009     MESSAGE IDENTIFIER
0065     Message type     identifier               INVRPT
0052     Message type version number               D
0054     Message type release number               96A
0051     Controlling agency                    EN
0057     Association assigned code               EAN004
BGM-segment: Beginning of message
C002     DOCUMENT/MESSAGE NAME
1001     Document/message name, coded 35     (= Inventory report)
3055     Code list responsible agency, coded     9     (= EAN)
1004     DOCUMENT/MESSAGE NUMBER     Unique Number assigned by CS (= Date/Time CCYYMMDDHHMMSS)
1225     MESSAGE FUNCTION, CODED          9     (= Original)
DTM-segment: Date/time/period
C507     DATE/TIME/PERIOD
2005     Date/time/period qualifier 137     (=Document/message date/time)
2380     Date/time/period     Document date
2379     Date/time/period format qualifier     102     (= CCYYMMDD)
RFF-segment: Reference
C506     REFERENCE
1153     Reference code qualifier ON     (= Order number)
1154     Reference identifier     Agreement number
NAD-segment: Name and address
3035     PARTY QUALIFIER     GY     (= Inventory reporting party = CS)
               GM     (= Inventory controller = XYZ)
C082     PARTY IDENTIFICATION DETAILS
3039     Party id. identification          GLN code
3055     Code list responsible agency, coded     9     (= EAN)
LIN-segment: Line item
1082     LINE ITEM NUMBER               Unique Line Number
C212     ITEM NUMBER IDENTIFICATION
7140     Item number               EAN Material code
7143     Item number type, coded          EN     (= EAN)
PIA-segment: Additional Product Information
4347     PRODUCT ID FUNCTION IDENTIFIER     "1"(= Additional Information)
C212     ITEM NUMBER IDENTIFICATION
7140     Item number          Promotional Variant
7143     Item number type, coded     "PV     (= Promotional variant)
QTY-segment: Quantity
C186     QUANTITY DETAILS
6063     Quantity qualifier     12      (= Despatch quantity)
6060     Quantity           Number of stock units
PRI: Represent price
TAX: represent tax.
Try to go to the below website where you will able to get the information regarding all the sgements and elements of Invocie.
http://www.edifactory.de/messages.php?s=D96A
Also refer the below link for EDI understanding:
http://www.gxs.com/pdfs/Tutorial/Tutor_EDIFACT_GXS.pdf
Thnx
Chirag Gohil

Unicode - "DMBTR" must be a character-type field (data type C,N,D or T)

Greetings Experts!
I am trying to convert legacy code to Unicode for a current ERP6.0 reinstallation and have encountered the syntax error "DMBTR" must be a character-type field (data type C,N,D or T)
The field is part of a structure and the fields attributes are as follows:
COMPONENT = DMBTR
COMPONENT TYPE = DMBTR
DATA TYPE = CURR
LENGTH = 13
DECIMALS = 2
DESCRIPTION = Amount in Local Currency
The code in question is as follows:-
macro Move_Zoned.
Converts a numeric variable to zoned format and moves it to a
target variable.
DEFINE move_zoned.
 &1 - source variable
 &2 - Number of Decimal Places
 &3 - 'To'
 &4 - Target Variable.
write &1 to w_zoned no-grouping decimals &2.
condense w_zoned.
 Remove the Decimal Points.
search w_zoned for '...'.
while sy-subrc = 0.
 move sy-fdpos to w_to_point.
 if w_to_point = 0.
 w_to_point = 1.
 endif.
 compute w_from_point = sy-fdpos + 1.
 concatenate w_zoned+0(w_to_point)
 w_zoned+w_from_point
 into w_zoned.
 search w_zoned for '...'.
endwhile.
shift w_zoned right deleting trailing space.
translate w_zoned using ' 0'.
call function 'Z_TRANSLATE_ZONED_DECIMALS'
 exporting
 i_input = w_zoned
 importing
 i_output = w_zoned
 exceptions
 x_invalid_zoned_char = c_invalid_zoned_char
 x_numeric_info_lost = c_numeric_info_lost
 others = c_other_zoned_error.
 Get the length of the recipient field so we don't truncate the
 numbers....
describe field &4 length w_flength in character mode.
describe field &4 type w_type.
describe field w_zoned length w_zoned_len in character mode.
if w_zoned_len <= w_flength.
 move w_zoned to &4.
 shift &4 right deleting trailing space.
 translate &4 using ' 0'.
else.
 Get the start position....
 If it's a packed field allow for values up to 6 figures
 compute w_zoned_len = w_zoned_len - w_flength.
 if w_type = 'P'.
 subtract 2 from w_zoned_len.
 clear w_type.
 endif.
 move w_zoned+w_zoned_len &3 &4.
endif.
END-OF-DEFINITION. "Move_zoned
LOOP AT t_single_kunnr.
 move_zoned t_single_kunnr-postamt 2
 to t_single_kunnr-dmbtr.
 DIVIDE t_single_kunnr-dmbtr BY 100.
 MODIFY t_single_kunnr.
ENDLOOP.
Is there a solution to get past this syntax error as I would rather not change the datatype of the field in the structure.
Much Obliged
Elphick.

Type X is not allowed in Unicode. When a field is declared as Type X with Value u201809u2019 or any other value, it can be resolved by using classes.
Before Unicode
 CONSTANTS: c_hex TYPE x VALUE '09'.
Resolution:
Itu2019s work for any value of x.
First a temporary field of Type c should declare. Following class will convert Type x variable into type c.
Example:
CONSTANTS: c_hex TYPE x VALUE '09'.
DATA: LV_TEMP TYPE STRING.
DATA: LV_TMP TYPE C.
TRY.
CALL METHOD CL_ABAP_CONV_IN_CE=>UCCP
EXPORTING
UCCP = c_hex
RECEIVING
CHAR = LV_TMP .
CATCH CX_SY_CONVERSION_CODEPAGE.
CATCH CX_PARAMETER_INVALID_TYPE.
CATCH CX_SY_CODEPAGE_CONVERTER_INIT.
ENDTRY.
CONCATENATE I_OUTPUT-BKTXT I_OUTPUT-BVORG
I_OUTPUT-BUDAT I_OUTPUT-MESSAGE INTO
SEPARATED BY LV_TMP.
I_BUFFER = LV_TEMP.
CLEAR LV_TEMP.
CLEAR LV_TMP.
OR
Note: It works only for type x value 09.
CLASS cl_abap_char_utilities DEFINITION LOAD.
CONSTANTS: c_hex TYPE c VALUE
 abap_char_utilities=>HORIZONTAL_TAB.

Questions on Merging Dis-similar Data Types...

I am using Web-I version 11.5.8.834 (We do not use the Crystal Reports module, all of our reports are built with Web-I).
I have two questions:
Question 1: First I am attempting to create a report from two different universes and need to merge a dimension from each universe. The two dimensions have similar data, but one is set up as a "string", and the other universe has the same data set up as a "number". Our IT department creates and maintains the universes and I have requested that one of the dimension data type be changed to match the other, but I am told that other users have already set up reports using these dimensions and to change them at this point might cause a problem with their reports. So my first question is: Can two separate dimensions be setup within a single universe, using the same data field, each having different data types (e.g., a field with numeric data be set up as a "string" and a second dimension be setup as a "number")? If this works, I can make a recommendation to our IT department to do this and I will not have to resort to Question 2. but just in case, here is Question 2:
Question 2: I have two other dimensions that I might be able to use, but it requires creating a variable and "trimming" data off of each of the fields. The first universe is a part number with three alpha characters followed by four numeric characters (PRT1234). The second universe has a serial number, in which the first four characters match the last four characters of the other universe (1234-00111). If I trim off the first three characters from the first universe using a variable (=right([Part_Number];4), and trim off the last six characters from the second universe using a variable (=left([Serial_Number],4), the variables will have matching data. The second question is: Can variables be merged? I've tried, but it isn't working so far. If so, can someone give me some hints on how to do it?
Edited by: Charles Norman on Aug 8, 2008 11:42 AM
Edited by: Charles Norman on Aug 8, 2008 11:43 AM

Charles,
Can variables be merged?
No, local variables cannot be merged. The manipulation must be performed at the database level via Designer before the data comes across to the report. As an aside, your IT deparatment can create "new" objects just for you, placed in the list under a separate sub-class that manipulates the data to your liking and will not upset other users who already built reports using the original columns of data. I guess my point is that you can have multiple objects placed in your universe that derive from the same column in a given table -- user A has it per their flavor and user B has it per his flavor.
Thanks,
John

How to display images in BI Publisher from a LONG data type

We are storing images in Oracle Database as LONG data type. When I am giving query in BI Publisher and view the XML generated, I am getting the following error.
name was started with an invalid character. Error processing resource 'http://.......
<X_SIGNATURE>"N!0$$$$$$$#B!0$$$"X$$$$!3$$$!2$$#a$$$!1$!1$$$$$d$$$$#7$"X!0$"}@E$e"1"XM">K#@!P!P!Ga}!1!@!P!C#C"O!>...
Can anyone suggest the solution?

Hi
my problem is, for each job_id there is many users. Oh that's something completlty different...
I Strongly Recommand to_
1.*create 2 tables Jobs & users*
2.*create a relation between them* 1 to many to get for each job more than a user that's the way that Must be -- execuse me the bad design of the db pulled u into this trap -
3.then u can deal with it normally no need to a sample code but just a form with Jobs as (Master) and Users as (detail) with a relation and with a simple query u can display each job_id is for many users.
no null values no commas r needed.
Hope this helps...
Regards,
Amatu Allah.

Need to convert long data type to varchar2

I need to convert a long datatype in an existing table to a
varchar2, in either another table or view. I have a 3rd party
application which needs to query the data in the long data type,
but it can "handle" the long.
What is the best way to do this? I tried to make a trigger, but
I must be missing something. Here is the trigger.
CREATE OR REPLACE TRIGGER "PROD".SV_GET_RTG_COMNT
BEFORE INSERT OR UPDATE ON PROD.RELS_RTG_SEQ_COMNT
FOR EACH ROW
WHEN (OLD.rels_rtg_no = NEW.rels_rtg_no)
DECLARE
-- DECLARE VARIABLES
RTG_COMNT_VAR VARCHAR2(32);
RTG_COMNT_LONG LONG;
BEGIN
Select COMNT_TXT into RTG_COMNT_LONG
from rels_rtg_seq_comnt;
RTG_COMNT_VAR := 'TEXT' || substr(RTG_COMNT_LONG,1,32);
-- If INSERTING
Insert into SV_RTG_SEQ_COMNT (print_cd, comnt_no,
seq_no, rtg_no, comnt_txt) values
(:new.print_cd, :new.comnt_no, :new.seq_no, :new.rels_rtg_no,
rtg_comnt_var);
END;
I tried to use the substr command on the comnt_txt in view but
received an invalid datatype error.
Any help would be greatly appreciated.
Doug

create another table with clob datatype
1)create table clob_tab(pkval number,clob_col clob);
2) insert into clob_tab (select pkval,to_lob(long_col) from
long_tab);
3) use dbms_lob package to do string manipulation using
substr,instr functions on clob column.

Difference b/w DATA TYPE and DATA OBJECT & differences b/w TYPE and LIKE

hai
can any one say the differences between Data type and Data Object.
And also differences between TYPE and LIKE
thanks
Gani

hi,
_Data Types and Data Objects_
      Programs work with local program data that is, with byte sequences in the working memory. Byte sequences that belong together are called fields and are characterized by a length, an identity (name), and as a further attribute by a data type. All programming languages have a concept that describes how the contents of a field are interpreted according to the data type.
      In the ABAP type concept, fields are called data objects. Each data object is thus an instance of an abstract data type. There are separate name spaces for data objects and data types. This means that a name can be the name of a data object as well as the name of a data type simultaneously.
Data Types
   As well as occurring as attributes of a data object, data types can also be defined independently. You can then use them later on in conjunction with a data object. The definition of a user-defined data type is based on a set of predefined elementary data types. You can define data types either locally in the declaration part of a program using the TYPESstatement) or globally in the ABAP Dictionary. You can use your own data types to declare data objects or to check the types of parameters in generic operations.
     All programming languages distinguish between various types of data with various uses, such as .. type data for storing or displaying values and numerical data for calculations. The attributes in question are described using data types. You can define, for example, how data is stored in the repository, and how the ABAP statements work with the data.
Data types can be divided into elementary, reference, and complex types.
a. Elementary Types
These are data types of fixed or variable length that are not made up of other types.
The difference between variable length data types and fixed length data types is that the length and the memory space required by data objects of variable length data types can change dynamically during runtime, and that these data types cannot be defined irreversibly while the data object is being declared.
Predefined and User-Defined Elementary Data Types
You can also define your own elementary data types in ABAP using the TYPES statement. You base these on the predefined data types. This determines all of the technical attributes of the new data type. For example, you could define a data type P_2 with two decimal places, based on the predefined data type P. You could then use this new type in your data declarations.
b. Reference Types
Reference types are deep data types that describe reference variables, that is, data objects that contain references. A reference variable can be defined as a component of a complex data object such as a structure or internal table as well as a single field.
c. Complex Data Types
Complex data types are made up of other data types. A distinction is made here between structured types and table types.
Data Objects
      Data objects are the physical units with which ABAP statements work at runtime. The contents of a data object occupy memory space in the program. ABAP statements access these contents by addressing the name of the data object and interpret them according to the data type.. For example, statements can write the contents of data objects in lists or in the database, they can pass them to and receive them from routines, they can change them by assigning new values, and they can compare them in logical expressions.
       Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running (field length, number of decimal places, and data type). You declare data objects either statically in the declaration part of an ABAP program (the most important statement for this is DATA), or dynamically at runtime (for example, when you call procedures). As well as fields in the memory area of the program, the program also treats literals like data objects.
        A data object is a part of the repository whose content can be addressed and interpreted by the program. All data objects must be declared in the ABAP program and are not persistent, meaning that they only exist while the program is being executed. Before you can process persistent data (such as data from a database table or from a sequential file), you must read it into data objects first. Conversely, if you want to retain the contents of a data object beyond the end of the program, you must save it in a persistent form.
Declaring Data Objects
      Apart from the interface parameters of procedures, you declare all of the data objects in an ABAP program or procedure in its declaration part. These declarative statements establish the data type of the object, along with any missing technical attributes. This takes place before the program is actually executed. The technical attributes can then be queried while the program is running.
     The interface parameters of procedures are generated as local data objects, but only when the procedure is actually called. You can define the technical attributes of the interface parameters in the procedure itself. If you do not, they adopt the attributes of the parameters from which they receive their values.
ABAP contains the following kinds of data objects:
a. Literals
Literals are not created by declarative statements. Instead, they exist in the program source code. Like all data objects, they have fixed technical attributes (field length, number of decimal places, data type), but no name. They are therefore referred to as unnamed data objects.
b. Named Data Objects
Data objects that have a name that you can use to address the ABAP program are known as named objects. These can be objects of various types, including text symbols, variables and constants.
Text symbols are pointers to texts in the text pool of the ABAP program. When the program starts, the corresponding data objects are generated from the texts stored in the text pool. They can be addressed using the name of the text symbol.
Variables are data objects whose contents can be changed using ABAP statements. You declare variables using the DATA, CLASS-DATA, STATICS, PARAMETERS, SELECT-OPTIONS, and RANGESstatements.
Constants are data objects whose contents cannot be changed. You declare constants using the CONSTANTSstatement.
c. Anonymous Data Objects
Data objects that cannot be addressed using a name are known as anonymous data objects. They are created using the CREATE DATAstatement and can be addressed using reference variables.
d. System-Defined Data Objects
System-defined data objects do not have to be declared explicitly - they are always available at runtime.
e. Interface Work Areas
Interface work areas are special variables that serve as interfaces between programs, screens, and logical databases. You declare interface work areas using the TABLES and NODESstatements.
What is the difference between Type and Like?
Answer1:
TYPE, you assign datatype directly to the data object while declaring.
LIKE,you assign the datatype of another object to the declaring data object. The datatype is referenced indirectly.
Answer2:
Type is a keyword used to refer to a data type whereas Like is a keyword used to copy the existing properties of already existing data object.
Answer3:
type refers the existing data type
like refers the existing data object
reward if useful
thanks and regards
suma sailaja pvn

Problem in F data type

Hi experts...
I am using F data type and it gets value 5.50000000000E+10.
but I want value like 5.500.
I don't want to use P data type.
Please Help me.
thanks in advance.

Ankita,
Try declaring it as type quann and check.
Some additional info:-
Type F values range from /- 2.2250738585072014E-308 to 1.7976931348623157E308, as well as the number 0, with an accuracy of at least 15 decimal places.
You cannot enter floating point numbers directly in your programs. Instead, you must use text literals that can be interpreted as floating point numbers. You may use the following formats:
Decimal numbers with or without sign, with or without decimal point. The form <mantissa> E<exponent>, where the mantissa is a decimal. The exponent may be specified either with or without sign. You may also use spaces before or after the number. Examples of text literals with "floating point numbers":
'1', '-12.34567', '-765E-04', '1234E5', '12E34', '+12.3E-4', '1E160'.
Use floating point arithmetic if you need a very large value range or you are making decimal calculations, but be aware of the following features of floating point arithmetic.
Internally, the exponent and the mantissa of floating point numbers are stored separately, each in two parts. This can lead to unexpected results, despite the high degree of intrinsic accuracy. These occur mainly when performing conversions from and to type F.
For example, the number 1.5 can be represented exactly in this notation, since 1.5 = 120 + 12**(-1), but the number 0.15 can only be represented approximately by the number 0,14999999999999999. If you round 0.15 up to 1 valid digit, the result is 0.1 rather than 0.2 as you would expect. On the other hand, the number 1.5E-12 is represented by the number 1.5000000000000001E-12, which would be rounded to 2E-12.
Another example which actually occurred is the calculation of 7.27% of 73050 to an accuracy of 2 decimal places. The intermediate result 5.3107349999999997E+03, since the correct result, 5310.735, cannot be represented exactly in two parts with 53 bits. (If the hardware cannot represent a real number exactly, it uses the next representable floating point number. After rounding, you therefore get 5310.73 rather than 5310.74 as you would expect.
The ABAP runtime system calculates commercially and not "numerically" like the underlying machine arithmetic. According to the rounding algorithm of the latter, the end digit 5 must always be rounded to the nearest even number (not the next largest number), i.e. from 2.5 to 2, 3.5 to 4.
You should also note that multiplication using powers of 10 (positive or negative), is not an exact operation. For example, although 100.5 can be represented exactly in two parts, after the operation
F = F / 100 * 100
F has the value 100.49999999999999.
As well as rounding errors, the restricted number of decimal places for the mantissa can lead to the loss of trailing digits. For example, 1 - 1.0000000000000001 results in zero.
This means that you cannot rely on the last digits in floating point arithmetic. In particular, you should not usually test two floating point numbers for equality; instead, you should check whether the relative difference abs((a - b)/a) is less than a predefined limit, e.g. 10**(-7).
K.Kiran.

New Effective CAL essay: How do I create an abstract data type in CAL?

How do I create an abstract data type in CAL? An abstract data type is one whose internal representation can be changed without needing to modify the source code of client modules that make use of that type. For software maintainability, it is a good idea to make a type that is subject to change or enhancement into an abstract data type. Another reason to create an abstract data type is to enforce invariants for values of the type that can only be ensured by using constructor functions (i.e. functions that return values of that type). In principle it is simple to create an abstract data type in CAL. For an algebraic data type, make the type constructor public and all data constructors private. For a foreign data type, make the type constructor public and the implementation scope private. If a scope qualifier is omitted, the scope is taken to be private. For example, the Map algebraic data type has the public type constructor Map and the data constructors Tip and Bin are each private, so it is an abstract data type. /** A map from keys (of type {@code k@}) to values (of type {@code a@}). */ data public Map k a = private Tip | private Bin size :: !Int key :: !k value :: a leftMap :: !(Map k a) rightMap :: !(Map k a); There are a number of invariants of this type: the size field represents the number of elements in the map represented by its Bin value. The keys in leftMap are all less than key, which in turn is less than all the keys in rightMap. In particular, non-empty Map values can only be created if the key parameter type is a member of the Ord type class. Values of the Map type can be created outside the Cal.Collections.Map module only by using constructor functions such as insert: insert :: Ord k => k -> a -> Map k a -> Map k a; public insert !key value !map = ... The owner of the Cal.Collections.Map module must ensure that all invariants of the Map type are satisfied, but if this is done, then it will automatically hold for clients using this function. Some examples of foreign abstract data types are Color, StringNoCase and RelativeDate: data foreign unsafe import jvm private "java.awt.Color" public Color; data foreign unsafe import jvm private "java.lang.String" public StringNoCase; data foreign unsafe import jvm private "int" public RelativeDate; The private implementation scope for Color means that a foreign function whose type involves Color can only be declared in the Cal.Graphics.Color module where the Color type is defined. A foreign function declaration involving the Color type relies on the compiler knowing that the Color type corresponds to java.awt.Color to resolve the corresponding Java entity i.e. it must know about the implementation of the Color type. Having a private implementation scope means that the Color type can be changed to correspond to a different Java class, or indeed to be an algebraic type, without the risk of breaking client code. In all these three cases there are useful, and different, design reasons to adopt a private implementation scope: For RelativeDate, the Java implementation type int represents a coded Gregorian date value in the date scheme used by Crystal Reports. Not all int values correspond to valid dates, and the algorithm to map an int to a year/month/day equivalent is fairly complicated, taking into account things like Gregorian calendar reform. Thus, it is desirable to hide the implementation of this type. For StringNoCase, the implementation is more straightforward as a java.lang.String. The reason to adopt a private implementation scope is to ensure that all functions involving StringNoCase preserve the semantics of StringNoCase as representing a case-insensitive string value. Otherwise it is very easy for clients to declare a function such as: foreign unsafe import jvm "method replace" replaceChar :: StringNoCase -> Char -> Char -> StringNoCase; which does not handle case-insensitivity correctly, but is a perfectly valid declaration. This declaration results in a compilation error when it is placed outside the module in which StringNoCase is defined because of the private implementation scope of StringNoCase. For Color, the issue is somewhat more subtle. The java.awt.Color implementation type is semantically the same as the CAL Color type. The problem is that java.awt.Color is mutable (since it can be sub-classed to create a mutable type). It is preferable for a first-class CAL type to not be mutable, so we simply make the implementation scope private to ensure that this will be the case. A somewhat less encapsulated kind of abstract data type can be created using friend modules and protected scope. For example, if an algebraic type is public, and all its data constructors are protected, then the data constructors can be accessed in the friend modules of the module in which the type is defined. Effectively this means that the implementation of the semantics of the type stretches over the module in which the type is defined, and all of its friend modules. These must all be checked if the implementation of the type is modified. Given the merits of abstract data types discussed above, it is perhaps surprising that most of the core types defined in the Prelude module are not abstract data types. For example: Boolean, Char, Int, Double, String, List, Maybe, Either, Ordering, JObject, JList, and all record and tuple types are non-abstract types. There are different reasons for this, depending on the particular type involved. For example, Boolean, List, Maybe, Either and Ordering are all rather canonical algebraic data types with a long history in functional languages, with many standard functions using them. They are thus guaranteed never to change. In addition, their values have no particular design invariants that need to be enforced via constructor functions. Exposing the data constructors gives clients some additional syntactic flexibility in using values of the type. For example, they can pattern match on the values using case expressions or let patterns. Essentially the same explanation holds for record and tuple types. Although non-tuple record types are less canonical, they do correspond to the fundamental notion of an anonymous named-field product type. The "anonymous" here simply means that the programmer can create an entirely new record type simply by creating a value; the type does not have to be declared anywhere prior to use. Char, Int, Double, String, JObject and JList are foreign types where in fact part of the semantics of the type is that we want clients to know that the type is a foreign type. For example, we want clients to know that Prelude.Int is essentially the Java primitive unboxed int type, and has all the semantics you would expect of the Java int type i.e. this is quite different from RelativeDate which is using int as its implementation type in a very tactical way that we may choose to change. One can think of a public foreign type declaration with public implementation scope as simply introducing the Java type into the CAL namespace. One interesting point here is with CAL's naming convention for public foreign types. We prefix a type name by "J" (for "Java") for foreign types with public implementation type such that the underlying Java type is mutable. This is intended as mnemonic that the type is not a pure functional type and thus some caution needs to be taken when using it. For example, Prelude.JObject has public Java implementation type java.lang.Object. In the case where the underlying Java type is not mutable, we do not use the prefix, since even though the type is foreign; it is basically a first class functional type and can be freely used without concern. For example, Prelude.String has public Java implementation type java.lang.String. In the case where the implementation type is private, then the fact that the type is a foreign type, whether mutable or not, is an implementation detail and we do not hint at that detail via the name. Thus Color.Color has as its private Java implementation type the mutable Java type java.awt.Color. When creating abstract data types it is important to not inadvertently supply public API functions that conflict with the desired public semantics of the type. For example, if the type is publicly a pure-functional (i.e. immutable) type such as Color, it is important not to expose functions that mutate the internal Java representation. A more subtle case of inadvertently exposing the implementation of a type can occur with derived instances. For example, deriving the Prelude.Outputable and Prelude.Inputable type classes on a foreign type, whose implementation type is a mutable Java reference type, allows the client to gain access to the underlying Java value and mutate it
(by calling Prelude.output, mutating, and then calling Prelude.input). The solution in this case is to not derive Inputable and Outputable instances, but rather to define a custom Inputable and Outputable instance that copies the underlying values.

Hi Pandra801,
When you create a the external content type, please try to add a filter based on your select statement.
http://arsalkhatri.wordpress.com/2012/01/07/external-list-with-bcs-search-filters-finders/
Or, try to create a stored procedure based on your select statement, then create ECT using the SQL stored procedure.
A step by step guide in designing BCS entities by using a SQL stored procedure
http://blogs.msdn.com/b/sharepointdev/archive/2011/02/10/173-a-step-by-step-guide-in-designing-bcs-entities-by-using-a-sql-stored-procedure.aspx
I hope this helps.
Thanks,
Wendy
Wendy Li
TechNet Community Support

Error when trying to set a date type edit field

Hi all
I have an edit text field in a form which is bounded to a date type
database field using dbDataSource.
When i try to set the edit text field value with Today's date by code.
I recieve an error message that the value which
i'm trying to set is not legal. the error number is [131-183].
I use the following code to set the edit field:
If oEditText.Value.Trim = String.Empty Then
            Dim strDate As String
            Dim sboBob As SAPbobsCOM.SBObob =
             oCompany.GetBusinessObjec(SAPbobsCOM.BoObjectTypes.BoBridge)
             rs = sboBob.Format_DateToString(Microsoft.VisualBasic.Today)
           strDate = rs.Fields.Item(0).Value.ToString().Trim()
Try
       oEditText.Value = strDate
Catch ex As Exception
    SBO_Application.MessageBox("error setting
current date: " & ex.Message)
End Try
End If
My question is how can i set the edit field with a valid value?

Hi!
When writing to EditText.Value you must always use the B1 "DB-Format" as String.
The following examples are assuming (it's a must!) that the EditText-Fields are bound to a corrosponding DataSource (Type Date, Price etc...)
MyDateEditTxt.Value="20080207"
MyPriceEditTxt.Value="1341.79"
The best of it: It's Windows and SBO-GUI-Language independent.
EditText.String must always be written with the format of the actual Language of the SBO-GUI, which can be changed by the user....
You may also have a look at my statements regarding these problems near the end of this thread:
[How to pass date value to an UDF;
Cheers,
Roland

Problem while accessing a complex data type

hi,
I am getting a problem while accessing a complex data type
I have a wsdl as:
<?xml version="1.0" encoding="UTF-8" ?>
- <definitions name="OutlookReminderService" targetNamespace="http://ws.aftek.com/outlook-reminder" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:ns2="http://ws.aftek.com/outlook-reminder/schemas" xmlns:ns3="http://java.sun.com/jax-rpc-ri/internal" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://ws.aftek.com/outlook-reminder" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- <types>
- <schema targetNamespace="http://ws.aftek.com/outlook-reminder/schemas" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://ws.aftek.com/outlook-reminder/schemas" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
<import namespace="http://java.sun.com/jax-rpc-ri/internal" />
- <complexType name="TaskVO">
- <sequence>
<element name="dueDate" type="long" />
<element name="percentageComplete" type="int" />
<element name="priorty" type="int" />
<element name="reminderDate" type="long" />
<element name="reminderSet" type="boolean" />
<element name="startDate" type="long" />
<element name="status" type="int" />
<element name="subject" type="string" />
<element name="taskId" type="string" />
</sequence>
</complexType>
- <complexType name="NoSuchUserException">
- <sequence>
<element name="message" type="string" />
</sequence>
</complexType>
- <complexType name="ArrayOfContactVO">
- <complexContent>
- <restriction base="soap11-enc:Array">
<attribute ref="soap11-enc:arrayType" wsdl:arrayType="tns:ContactVO[]" />
</restriction>
</complexContent>
</complexType>
- <complexType name="ContactVO">
- <sequence>
<element name="birthDate" type="long" />
<element name="companyAddress" type="string" />
<element name="companyName" type="string" />
<element name="emailID1" type="string" />
<element name="emailID2" type="string" />
<element name="emailID3" type="string" />
<element name="faxNumber" type="string" />
<element name="firstName" type="string" />
<element name="homeAddress" type="string" />
<element name="lastName" type="string" />
<element name="middleName" type="string" />
<element name="mobileNumber" type="string" />
<element name="phoneNumber" type="string" />
<element name="workContactNumber" type="string" />
</sequence>
</complexType>
</schema>
- <schema targetNamespace="http://java.sun.com/jax-rpc-ri/internal" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://java.sun.com/jax-rpc-ri/internal" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
<import namespace="http://ws.aftek.com/outlook-reminder/schemas" />
- <complexType name="arrayList">
- <complexContent>
- <extension base="tns:list">
<sequence />
</extension>
</complexContent>
</complexType>
- <complexType name="list">
- <complexContent>
- <extension base="tns:collection">
<sequence />
</extension>
</complexContent>
</complexType>
- <complexType name="collection">
- <complexContent>
- <restriction base="soap11-enc:Array">
<attribute ref="soap11-enc:arrayType" wsdl:arrayType="anyType[]" />
</restriction>
</complexContent>
</complexType>
</schema>
</types>
<message name="OutlookServer_addTaskResponse" />
- <message name="OutlookServer_getListResponse">
<part name="result" type="ns3:arrayList" />
</message>
- <message name="OutlookServer_getContactListResponse">
<part name="result" type="ns2:ArrayOfContactVO" />
</message>
- <message name="NoSuchUserException">
<part name="NoSuchUserException" type="ns2:NoSuchUserException" />
</message>
- <message name="OutlookServer_getContactList">
<part name="String_1" type="xsd:string" />
</message>
- <message name="OutlookServer_getList">
<part name="String_1" type="xsd:string" />
</message>
- <message name="OutlookServer_addTask">
<part name="String_1" type="xsd:string" />
<part name="TaskVO_2" type="ns2:TaskVO" />
</message>
- <message name="OutlookServer_reminderOccurredResponse">
<part name="result" type="xsd:boolean" />
</message>
- <message name="OutlookServer_reminderOccurred">
<part name="String_1" type="xsd:string" />
<part name="TaskVO_2" type="ns2:TaskVO" />
</message>
- <portType name="OutlookServer">
- <operation name="addTask" parameterOrder="String_1 TaskVO_2">
<input message="tns:OutlookServer_addTask" />
<output message="tns:OutlookServer_addTaskResponse" />
<fault message="tns:NoSuchUserException" name="NoSuchUserException" />
</operation>
- <operation name="getContactList" parameterOrder="String_1">
<input message="tns:OutlookServer_getContactList" />
<output message="tns:OutlookServer_getContactListResponse" />
<fault message="tns:NoSuchUserException" name="NoSuchUserException" />
</operation>
- <operation name="getList" parameterOrder="String_1">
<input message="tns:OutlookServer_getList" />
<output message="tns:OutlookServer_getListResponse" />
<fault message="tns:NoSuchUserException" name="NoSuchUserException" />
</operation>
- <operation name="reminderOccurred" parameterOrder="String_1 TaskVO_2">
<input message="tns:OutlookServer_reminderOccurred" />
<output message="tns:OutlookServer_reminderOccurredResponse" />
<fault message="tns:NoSuchUserException" name="NoSuchUserException" />
</operation>
</portType>
- <binding name="OutlookServerBinding" type="tns:OutlookServer">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
- <operation name="addTask">
<soap:operation soapAction="" />
- <input>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://ws.aftek.com/outlook-reminder" use="encoded" />
</input>
- <output>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://ws.aftek.com/outlook-reminder" use="encoded" />
</output>
- <fault name="NoSuchUserException">
<soap:fault encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" name="NoSuchUserException" namespace="http://ws.aftek.com/outlook-reminder" use="encoded" />
</fault>
</operation>
- <operation name="getContactList">
<soap:operation soapAction="" />
- <input>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://ws.aftek.com/outlook-reminder" use="encoded" />
</input>
- <output>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://ws.aftek.com/outlook-reminder" use="encoded" />
</output>
- <fault name="NoSuchUserException">
<soap:fault encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" name="NoSuchUserException" namespace="http://ws.aftek.com/outlook-reminder" use="encoded" />
</fault>
</operation>
- <operation name="getList">
<soap:operation soapAction="" />
- <input>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://ws.aftek.com/outlook-reminder" use="encoded" />
</input>
- <output>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://ws.aftek.com/outlook-reminder" use="encoded" />
</output>
- <fault name="NoSuchUserException">
<soap:fault encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" name="NoSuchUserException" namespace="http://ws.aftek.com/outlook-reminder" use="encoded" />
</fault>
</operation>
- <operation name="reminderOccurred">
<soap:operation soapAction="" />
- <input>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://ws.aftek.com/outlook-reminder" use="encoded" />
</input>
- <output>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://ws.aftek.com/outlook-reminder" use="encoded" />
</output>
- <fault name="NoSuchUserException">
<soap:fault encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" name="NoSuchUserException" namespace="http://ws.aftek.com/outlook-reminder" use="encoded" />
</fault>
</operation>
</binding>
- <service name="OutlookReminderService">
- <port binding="tns:OutlookServerBinding" name="OutlookServerPort">
<soap:address location="http://truptid:8080/outlook-reminder-service/outlook" />
</port>
</service>
</definitions>
My client is :
private static String BODY_NAMESPACE_VALUE = "http://ws.abc.com/outlook-reminder";
 private static String ENCODING_STYLE_PROPERTY = "javax.xml.rpc.encodingstyle.namespace.uri";
 private static String NS_XSD = "http://www.w3.org/2001/XMLSchema";
 private static String URI_ENCODING = "http://schemas.xmlsoap.org/soap/encoding/";
try{
ServiceFactory factory = ServiceFactory.newInstance();
 Service service = factory.createService(new QName("OutlookReminderService"));
 QName port =new QName("OutlookReminderService","OutlookServerPort");
 Call call =service.createCall(port);
 call.setTargetEndpointAddress("http://localhost:8080/outlook-reminder-service/outlook?wsdl");
 call.setProperty(Call.SOAPACTION_USE_PROPERTY, new Boolean(true));
 call.setProperty(Call.SOAPACTION_URI_PROPERTY, "");
 call.setProperty(ENCODING_STYLE_PROPERTY, URI_ENCODING);
 call.getReturnType();
 call.setOperationName(new QName(BODY_NAMESPACE_VALUE, "getList"));
 QName QNAME_TYPE_STRING = new QName(NS_XSD, "string");
 call.addParameter("String_1", QNAME_TYPE_STRING, ParameterMode.IN);
 //http://ws.aftek.com/outlook-reminder/schemas
 QName QNAME_TYPE_VO = new QName("http://schemas.xmlsoap.org/soap/encoding/", "Array");
 System.out.println("Before Add Parameter");
 // call.addParameter("result", QNAME_TYPE_VO, ParameterMode.OUT);
 call.setReturnType(QNAME_TYPE_VO,ArrayList.class);
 System.out.println("After Add Parameter");
 Object[] params ={oUserVO.getUserName()};
 oArrayList =(ArrayList)call.invoke(params);
 System.out.println("After Invoked");
 //System.out.println("invoked"+ arrayList);
 catch(SOAPFaultException faultException)
 moLogger.debug("SOAPFaultException : ", faultException);
 catch(RemoteException oremoteException)
 moLogger.debug("RemoteException", oremoteException);
 catch(ServiceException oServiceException)
 moLogger.debug("ServiceException", oServiceException); }
Error got is :
trailing block elements must have an id attribute
 at com.sun.xml.rpc.encoding.SOAPDeserializationContext.deserializeMultiRefObjects(SOAPDeserializationContext.java:81)
 at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:239)
 at com.sun.xml.rpc.client.dii.CallInvokerImpl.doInvoke(CallInvokerImpl.java:103)
 at com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:492)
 at com.ail.dhg.poc.business.dao.ContactDAO.getList(ContactDAO.java:255)
 at com.ail.dhg.poc.business.facade.ContactFacade.getList(ContactFacade.java:189)
 at com.ail.dhg.poc.business.AcceptInput.main(AcceptInput.java:72)
java.lang.NullPointerException
 at com.ail.dhg.poc.business.dao.ContactDAO.getList(ContactDAO.java:277)
 at com.ail.dhg.poc.business.facade.ContactFacade.getList(ContactFacade.java:189)
 at com.ail.dhg.poc.business.AcceptInput.main(AcceptInput.java:72)
Message was edited by:
trupti_d

Use lower case letters for your variable names (name, pwd). The code works then.
package com.bluenile.bean;
import java.io.*;
public class Bean1 implements Serializable
private String name="Uname";
private String pwd="Pword";
public String getName()
return name;
public String getPwd()
return pwd;
void setName(String name)
this.name = name;
void setPwd(String pwd)
this.pwd = pwd;
<HTML>
<BODY BGCOLOR="#FFFFFF">
<%@ page language="java" contentType="text/html" %>
<jsp:useBean id="b1" class="com.bluenile.bean.Bean1" />
<ul>
<li>Name : <jsp:getProperty name="b1" property="name" />
<li>Pwd : <jsp:getProperty name="b1" property="pwd" />
</ul>
</BODY>
</HTML>

Adding fields with data type "TIMS" to the BP transaction

hi all,
This is Anil regarding the addition of fields to the BP transaction.
here my problem is for BP transaction I could not find any BADI or screen exit to add the fields. Even EEWB tool does not allow us to cretate the fields with data type "TIMS". so could you please suggest any other way to add these fields to BP?
when I enter the values to the time fields in BP transaction, they must reflect in
BUT000 table also?
Regards,
Anil .

In the physical layer, Column Properties change the data type to int.
If still problem exists, In the Business Model, write a case statement like
case when column1=1 then 1 end
and apply count aggregation on the new calculated column,add the column to presentation table, use that new calculated column for report.
- Madan

NAD010 data type must be 'Alphanumeric' in EDIFACT D96A INVOIC

Similar Messages

Maybe you are looking for