Use of identifier in ByD Studio business objects

Question

As Wed Feb 2nd in VQ3), we introduced a new identifier data type for partner BOs.
ByD Studio contains 2 identifier:
element ID                 : ID;                  // identifier 2 (SAP "best practiceu201D)
element Identifier   : Identifier;           // identifier 1 (u201CCCTS compliant")
As the CCTS-complient  data type u201CIdentifieru201D has various difficulties, we recommend urgently to use the data type "ID". The differences between the two data types is explained below:
1. Length
The DT Identifier has a length of 255 char.
The DT ID has a length of 60 char.
2. Upper case conversion
The DT ID supports upper case only. User entries with lower case characters are automatically converted to upper case. This is the same behavior as almost all ByD identifier data types (e.g. BusinessTransactionDocumentID, ProductID, BusinessPartnerID, etc.)
The DT Identifier supports lower case letters as well.
3. Alpha conversion
The DT ID supports alpha conversion. User entries which contain number characters only are filled with zeros from the left side (leading zeros). On the UI the leading zeros are suppressed automatically. This is the same behavior as almost all ByD identifier data types (e.g. BusinessTransactionDocumentID, ProductID, BusinessPartnerID, etc.) The DT Identifier does not support alpha conversion. This leads to an u201Cunexpectedu201D sort order on the UI.
This leads to the following sort behavior:
Sort order ID     Sort order Identifier:
.1.1                           .1.1
1                            1
5                            1.1
10                            10
15                            100
50                            15
100                            5
1.1                            50
ABC                            abc
(no lower case)       ABC
4. Structure
The ID data type is flat. There is no need for the u201C.Contentu201D suffix any longer.
The Identifier data type is structured (contains supplementary components), so the  u201C.Contentu201D suffix  is needed (although the supplementary components are disabled in the BO).
5. Behavior in ByD script coding:
The following coding works fine:
import ABSL;
var x = 1;
if (this.ID == "") {
// is true if ID is initial
this.ID = x.ToString();
this.ID = "1";
if (this.ID == "1") {
// is does not work, because u201C1u201D was filled with leading zeros
if (this.ID == "000000000000000000000000000000000000000000000000000000000001") {
// is true now because u201C1u201D was filled with leading zeros
raise IDMessage.Create("I", this.ID);
// leading zeros are suppressed on the UI: u201CID: 1u201D
6. Restrictions in Extensibility and Analytics:
Only the ID data type will be supported in extensibility and analytics:
Extensibility: It will be possible to add an extension field in an BO extension (planned for FP3.0).
element ID                 : ID;                  
Analytics: Analytics supports only character fields with a maximum length of 60 characters & alpha conversion.
Consequence: the u201CIdentifieru201D DT cannot be used in Extensibility and Analytics.
7. Adoption
If you have used the data type "Identifier" before and want to change the BO to "ID", the following adoption tasks are necessary:
a)     Business Object: change the BO definition file (see point 1)
Note: During my tests I got a activation error. In this case I solved the problem by Clean -> Save -> Activate. In this case, test data are lost
b)     Business Object: Implementation: remove the u201C.Contentu201D suffix
c)     UI: After the BO change, the following runtime error occurs in the affected UI. In the error text the following text occurs: u201CMapping of proxy name of attribute  failed.u201D
Solution: Open the UI Designer,
(1)     Tools -> Update Meta Data
(2)     Go to the data model and do u201CUnbindu201D and u201CBindu201D again for the affected field
(3)     Save & Activate
d)     MDAV, Forms, Web services -> not analyzed. Assumption here is that the dependent objects have to be cleaned and activated.

Answer 1

OK, I have found your code in your previous post.
It works in 9.2.0.1.0 and 8.1.7.0.0.
SQL> CREATE OR REPLACE TYPE t_assoc_agents_address AS OBJECT
  2  (V_CONTACT_NAME VARCHAR2(120),
  3  V_ADDRTYPE VARCHAR2(80),
  4  V_ADDRESS_LINE1 VARCHAR2(50),
  5  V_ADDRESS_LINE2 VARCHAR2(50),
  6  V_ADDRESS_LINE3 VARCHAR2(50),
  7  V_CITY_STATE_ZIP VARCHAR2(100),
  8  V_PHONE VARCHAR2(50),
  9  V_ADDRESS_FAX VARCHAR2(30),
10  V_ADDRESS_EMAIL VARCHAR2(80)
11  )
12  /
&nbsp
Type created.
&nbsp
SQL> CREATE OR REPLACE TYPE nt_assoc_agents_address AS TABLE OF t_assoc_agents_address
  2  /
&nbsp
Type created.
&nbsp
SQL> var c refcursor
SQL> col v_address_fax format a15
SQL> col v_address_email format a15
SQL> declare
  2   lv_assoc_agents_add_out nt_assoc_agents_address
  3   := nt_assoc_agents_address(
  4     t_assoc_agents_address(null,null,null,null,null,null,null,
  5     'New Fax', 'New Mail')
  6   );
  7  begin
  8   open :c for select V_ADDRESS_FAX,V_ADDRESS_EMAIL from
  9   table(cast(lv_assoc_agents_add_out as nt_assoc_agents_address));
10  end;
11  /
&nbsp
PL/SQL procedure successfully completed.
&nbsp
SQL> print c
&nbsp
V_ADDRESS_FAX   V_ADDRESS_EMAIL
New Fax         New MailWhat is your Oracle release and how are you using ref cursor (if I interpret your example right) ?
Rgds.