Creating Structure, Type, Domain in Data Dictonary.

Can we create Type or Domain or Strucure or Table from within the ABAP program based on internal table?
Thanks in Advance
Deval Bhatt

Although u can create internal talbe dynamically also for this kind of requirement better to use field symbols.
Sameer

Similar Messages

Dynamically create a type

Hi,
is it possible to create dynamically a type ? I take a look on class CL_ABAP_TYPEDESCR but i can't create a new type, so is there a solution ?
Cheers

With all due respect to all, I think he means to create dynamic data types by means of RTTS.
@ ToraTora
Like this
"example table
DATA: BEGIN OF it OCCURS 3,
 pernr TYPE persno,
 kostl TYPE kostl,
 endda TYPE endda,
 END OF it.
"data references
DATA: r_type_struct TYPE REF TO cl_abap_structdescr,
 r_type_table TYPE REF TO cl_abap_tabledescr,
 r_data_tab TYPE REF TO data,
 r_data_str TYPE REF TO data.
" 1. ------------- filling example table IT
it-pernr = '12345678'.
it-kostl = '0112345678'.
it-endda = sy-datum.
APPEND it.
it-pernr = '45678909'.
it-kostl = '3452345678'.
it-endda = sy-datum - 1.
APPEND it.
" 2. ------------ components structure type
gs_comp-name = 'PERNR'.
gs_comp-type ?= cl_abap_elemdescr=>describe_by_name( 'PERSNO' ).
APPEND gs_comp TO gt_comp.
gs_comp-name = 'KOSTL'.
gs_comp-type ?= cl_abap_elemdescr=>describe_by_name( 'KOSTL' ).
APPEND gs_comp TO gt_comp.
gs_comp-name = 'BEGDA'.
gs_comp-type ?= cl_abap_elemdescr=>describe_by_name( 'BEGDA' ).
APPEND gs_comp TO gt_comp.
" 3. ------------- create structure type
TRY.
 r_type_struct = cl_abap_structdescr=>create(
 p_components = gt_comp ).
CATCH cx_sy_struct_creation .
ENDTRY.
" 4. ------------- create table type
TRY.
 r_type_table = cl_abap_tabledescr=>create( r_type_struct ).
CATCH cx_sy_table_creation .
ENDTRY.
" 5. -------------- create table based on RTTS types
CREATE DATA: r_data_tab TYPE HANDLE r_type_table,
 r_data_str TYPE HANDLE r_type_struct.
FIELD-SYMBOLS: <fs_table> TYPE INDEX TABLE,
 <fs_wa> TYPE ANY.
ASSIGN: r_data_tab->* TO <fs_table>,
 r_data_str->* TO <fs_wa>.
You can also create any component you want without knowledge about data element it is refering to (without using methods describe_by_name or describe_by_data ).
So the 2nd step could be replaced with
gs_comp-name = 'PERNR'.
gs_comp-type ?= cl_abap_datadescr=>get_n( 8 ). "PERNR if of type N(8)
APPEND gs_comp TO gt_comp.
gs_comp-name = 'KOSTL'.
gs_comp-type ?= cl_abap_elemdescr=>get_c( 10 ). "C(10)
APPEND gs_comp TO gt_comp.
gs_comp-name = 'BEGDA'.
gs_comp-type ?= cl_abap_elemdescr=>get_d( ). "D
APPEND gs_comp TO gt_comp.
Regards
Marcin

How to create a reference instead of complex type for record in data structure type in BizTalk schema

I have created the record in BizTalk schema but i will give to Data Structure Type as reference For eg:Recordname(Reference) instead of recordname(Complex type).
Please help me to sort this out

You can add a reference to an existing type only.
You might have to manually edit the XSD file to change the xmlns definiton to xmlns:tns and then after you define the record type, set the datatype to tns:.... this creates the XML Type. Then later in your schema you can instantiate this with a name and
then set type to tns:.... (Reference)
Regards.

Create a structure type at runtime

Hi friends,
is it possible to create a local structure type dynamically(at run time).My situation is as follows :
The user gives a period of time - for Example from "05.03.2009" to "04.03.2010"
Depending on the number of months between the period of time
I have to create a structure with field names as follows:
I have calculated the number of months between a period of time and the field name also(Mar-09.Apr-09 extra) using function modules.
The question that is running around my head now is how to create the local structure type at run time with the field names.
TYPES: BEGIN of st_testStruct
     matnr type string,
     land type string,
     "The above to fields in the structure will always be there but depending on the period of time.
     the following fields have to created dynamically.
     Mar-09 type string,     " as the time period starts from "05.03.2009"
     apr-09 type string,
     may-09 type string,
     ........so on
     dec-09 type string,
     jan-10 type string,
     feb-10 type string,
     mar-10 type string,
end of st_testStruct.
depending on the time range the number of field could be more or less in the structure type.Thats why I want to create it dynamically.
Any sample code for this purpose is useful.....
Thanks
P

ABAP RTTS is what you're looking for - check out this [Wiki page|http://wiki.sdn.sap.com/wiki/display/ABAP/RuntimeTypeServices+%28RTTS%29], which should answer your questions... (here's the link to the [ABAP online docu|http://help.sap.com/abapdocu_70/en/ABENRTTI.htm])
Cheers, harald
p.s.: Don't use the hyphen in your field names. This was a bad practice that was used in some old releases. The problem is that fields in a structure are addressed with a hyphen, e.g. like mara-matnr.

Japanese characters alone are not passing correctly (passing like ??? or some unreadable characters) to Adobe application when we create input variable as XML data type. The same solution works fine if we change input variable data type to document type a

Dear Team,
Japanese characters alone are not passing correctly (passing like ??? or some unreadable characters) to Adobe application when we create input variable as XML data type. The same solution works fine if we change input variable data type to document type. Could you please do needful. Thank you

Hello,
most recent patches for IGS and kernel installed. Now it works.

How to define a TYPE REF TO data into my local variable/structure?

Hello,
I am trying to implementing a BADI, in its signature part,
c_accit TYPE REF TO data.
My pseudo code goes like,
DATA: l_itm_details TYPE REF TO data.
l_itm_details = c_accit.
l_itm_details-koart = 'D' =====> here am getting error!
* Do processing
ENDIF.
Here am getting error that, l_itm_details is not a structure! Pls. let me know how to fix it?
Thank you

Hello,
c_accit TYPE REF TO data.
C_ACCIT is a "data reference" parameter. In order to access its components you have to "de-reference" it!
FIELD-SYMBOLS: <l_itm_details> TYPE ANY,
<l_value> TYPE ANY.
ASSIGN c_accit->* TO <l_itm_details>."De-reference the data reference
ASSIGN COMPONENT 'KOART' OF STRUCTURE <l_itm_details> TO <l_value>.
If you know the structure of the data reference variable you can define your field-symbol <l_itm_details> of that type directly, else you can define a generic type as mentioned in the code snippet.
BR,
Suhas

Changing domain-defined Timestamp data type to logical Date doesn't persist

Hi:
Version 3.1.0.691 on Windows 7 Enterprise 64-bit SP1
I imported a domain from Designer, and then imported a schema from a database, all into the same model, in that order. I then changed the data type on several columns from non-domain, logiical Date data types to Domain-defined Timestamp Wth Time Zone data types. After having done this, I decided that I wanted to leave them as they were and tried to change them back. I went into the relational model section for each table/column and de-selected the domain radio button, chose Logical, and then set the data type to Date. I clicked apply, OK, and then saved the entire model. I closed Data Modeler, re-opened it, and then checked the data type change. I found that the change from domain to logical was saved, but the data type remained as Timestamp With Time Zone instead of remaining as Date like I'd set it. I've tried changing from Timestamp With Time Zone to other data types and then to Date but it didn't work.
Am I doing something wrong or is this a bug?
Thanks!
Doc

Hi:
One final comment. I set the domain back to unknown and clicked appy, but left the Column Properties dialog box open. I then clicked the button next to Datatype (which showed UNKNOWN{Unknown}, changed the radio button from Domain to Logical Type, and then selected Date from the list box and clicked OK. Immediately after having clicked OK, the Logical Type dialog box remained open and the Logical Type value within the Logical Type dialog box reverted back to Unknown. I re-selected Date from the list box, clicked OK, and after this second try it kept the change without the "double clutch."
Doc

Structure of the sender Data Type

hi;
i have two tables and want to fetch data from both in one go using sender JDBC adapter.
Can any one tell me the structure of the sender Data Type
if Table1 has A1,A2,A3 as fields and Table2 has B1,B2,B3 as fields.
i want to fetch only A1,A2 fields from Table1 and B1,B3 fields from Table2.

Hi,
Just use Select statement in the Sender JDBC adapter , and your structure should have simple structure with required number of fields.
configuring jdbc adapter with multiple tables
Regards,
Moorthy

Domain type for binary data

Hello,
I want to create domain and data element to save binary data like pictures.
Do you use RAW or RAWSTRING for this?
thx
chris

Refer:
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21f2e5446011d189700000e8322d00/frameset.htm

SQL Developer Data Modelere 2.0.0 Structured Type Method Body

I do not understand how to write a structured type method body.
When I generate a DDL for my type there is no method body text in the script. I only see the text "-- Empty PL/SQL Body" and no code that i've put in the method properties

Hi Artem,
you can try 3.0 EA2 - it's fixed there.
Philip

Create Idoc Type under ECC6

Hi folks,
I've created a new Idoc segment for an existing idoc (The original idoc doesn't have the fields I need). I'm now trying to create a new Idoc type taking into consideration the new Idoc Extension I've created. When I type my new idoc type and select 'basic type', I believe I should get prompted (somewhere) to enter the Basic Idoc type and Extension type, but when I create a new basic type, I don't get the option to add my new extension. And If I copy the original basic type, I don't get my new segments.
Can someone please tell me what I'm missing in the create new Idoc Process?
Cheers,
Steve

Hi Stephen..
According to ur Scenario (Adding new Segments to a Basic type ) , you should not create a Basic idoc type . Rather you should create an Extended idoc type in WE30.
That will ask for the Basic type and the new segments can be added here.
This is the Complete info:
1.
IDOC Enhancement
This is the Complete Steps and Info on this...with an Example...
Enhancing ALE
For example, if in an outbound interface you find that the IDOC type does not contain all the data you need to pass to the other system, you can extend the IDOC to accommodate the additional fields and enhance the ALE function modules to populate the fields. Similarly, if in an inbound interface, there is additional data that needs to be posted to the R/3 application, you can extend the IDOC type to have additional fields populated by the external system or translator or the other R/3 system and then enhance the inbound ALE function modules to post the additional data to the R/3 application.
let us use the SAP Customer Master application as an example. Specifically, letâs focus on the IDOC extension and ALE function module enhancement of IDOC type DEBMAS02 and message type DEBMAS (Customer Master) and the IDOC reduction of message type MATMAS.
IDOC EXTENSIONS
Letâs first look at the concept of IDOC extension. SAP delivers Basic IDOC types such as DEBMAS02, MATMAS02, ORDERS02, and WMMBID01. By extending the Basic IDOC type, you are actually creating a new IDOC type. You create a new segment with the additional fields. This new segment has to be associated with one of the existing Basic IDOC segments. Then you create a new extension type, which is associated with the Basic IDOC type. This results in a new IDOC type. In order for ALE function modules to relate to this new IDOC type, the IDOC type is linked to the corresponding message type.
Note that you should not add fields to existing segments but should create a new segment and associate it with an existing segment. This, in a nutshell, is the process of creating IDOC extensions.
In our example, the Basic IDOC type DEBMAS02 is used to communicate Customer Master data to the SAP Customer Master application. Even though the application has a screen to enter and store a contact personâs business address (see Figure 1), DEBMAS02 does not have a segment or fields that communicate the contact personâs business address. If your business requires that this business address be communicated to the other system through the ALE interface for Customer Master, then you have to extend the DEBMAS02 IDOC type, and enhance the corresponding ALE function module.
In DEBMAS02 the contact person fields are present in segment E1KNVKM and the business address of the contact person is stored on the SADR SAP table. You need to create a new segment, Z1SADRX, that is associated with E1KNVKM. This will be done in the process of creating an extension type ZDEBMASX. This extension type will then be associated with a new IDOC type, ZDEBMASZ. IDOC type ZDEBMASZ will be linked to message type DEBMAS for Customer Master. The final step in the IDOC extension process is to check the new objects. This check also verifies the structural integrity of the IDOC type. Letâs look at each of these steps in more detail.
1. Create an Extension Type and a New Segment.
Determine the fields on table SADR that you are going to provide for in the new segment Z1SADRX. You need fields for name, street, city, region, and country to give the business address of the contact person. You also need fields for the address number. ADRNR is a field in SAP tables such as SADR that uniquely identifies the address of an entity. This field is cross-referenced from other tables to the SADR table to obtain the full description of the address. Because this is an IDOC type for master data, the first field of the new segment will be MSGFN. The message function field informs the receiving system of the action to be taken for that particular segment. In the code that you write for populating the new segment, the value of the message function is the same as that of the parent segment E1KNVKM. In all, you will have 12 fields in segment Z1SADRX (see Table 1).
To create an extension type and new segment:
Use transaction WE30 or from WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object Name.
Choose Extension Type.
Click on Create.
You will see a pop-up screen. Choose Create New, and enter a description. For version 4.x, enter DEBMAS02 in the Linked Basic Type field. Enter.
You will see a screen with ZDEBMASX and its description in the first line. Click on this line, and press Create. For version 4.x, expand the tree of segments, and place the cursor on E1KNVKM.
You will see a pop-up screen. Enter E1KNVKM as the reference segment. Enter.
For 4.x, press Create after placing the cursor on segment E1KNVKM.
You will see a line appear with E1KNVKM hierarchically below ZDEBMASX, with a description "Customer Master contact person (KNVK)."
Click on this line and press Create. You will receive a message indicating that the new segment being created will be a child segment of E1KNVKM. Enter. A pop-up box appears for the new segment.
Enter Z1SADRX as the segment type, 1 for Minimum, 1 for Maximum. Leave Mandatory segment unchecked. These entries imply that there is only one Z1SADRX segment for every occurrence of the E1KNVKM segment, and also that this segment is not mandatory. Note that if the parent segment is not mandatory, then the child segment should not be mandatory, because this could result in a syntax error during the creation or processing of the IDOC.
For 4.x, you must first create the IDOC segment Z1SADRX (Iâll explain why in a moment) from the menu path WEDI -> IDOC -> Development -> IDOC Segment.
Click on Segment Editor.
On the next screen, click on Create.
Enter a development class for the object. Enter.
This will take you to the screen for segment definition. Enter a description for the segment. Enter the field name, data element, and the data element documentation name. In most cases, all three fields may have the same values. If you are using a field in the segment that is not present in the ABAP/4 data dictionary, you must first create the domain, data element, field, and appropriate documentation before using it in the new segment.
Enter these three columns for all 12 fields. Save.
Click on Generate/Activate, F3 to step back.
From screen Maintain Segment, go to Segment Type -> Release. A checkbox now appears beside the segment definition Z1SADRX (see Figure 2). Check this box. Save.
Save again to store the descriptions of the segment, F3 to step back.
Save the extension type.
It is possible to have several new segments with relevant Basic IDOC type parent segments in a single extension type. However, you can form only one IDOC type based on a single extension type.
2. Create an IDOC Type.
The next step is to create an IDOC type by associating the extension type that you created with the Basic IDOC type. This is a simple process:
From transaction WE30 or WEDI go to Development -> IDOC Types.
Enter ZDEBMASZ for Object Name.
Click on IDOC Type.
Click on Create.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter a description.
Enter.
You will see a display of the composite IDOC type with all segments, including Z1SADRX (see Figure 3).
It is possible to associate only one extension type with a Basic IDOC type for a given IDOC type. However, you can have multiple new segments in an extension type.
3. Link IDOC Type to Message Type.
The next step is to link the new IDOC type to its corresponding message type. This is important, because this relationship is referenced in the partner profile parameters where you specify the message type and IDOC type to be used for that particular representative system. To link the message type:
Use transaction WE82, or from WE30, go to Environment -> IDOC Type / Message Type, or from WEDI go to Development -> IDOC Type -> Environment Î IDOC Type / Message Type.
Click on Display <-> Change.
Click on New Entries.
Enter DEBMAS for message type.
Enter DEBMAS02 for Basic IDOC type.
Enter ZDEBMASX for extension type.
Enter your SAP R/3 release number for Release.
Save.
This data is stored on the EDIMSG table and is accessed by several ALE processes to relate the message type to the IDOC type.
4. Check the IDOC Type.
Before checking the IDOC type for consistency, it is important to perform another step that releases the extension type to the IDOC type:
From WEDI go to Development -> IDOC Types -> Extras -> Release Type, or from transaction WE30 go to Extras -> Release Type.
For the Object Name ZDEBMASX and radio button Extension Type, click Yes.
The extension type has now been "released."
You canât edit the extension type once itâs released. To cancel the release for further editing or deactivation, go to WE30 Î Extras Î Cancel release. The final step in the IDOC extension process is checking the validity of the IDOC type:
From transaction WE30 or WEDI go to Development -> IDOC types.
Enter ZDEBMASX for Object name.
Click on Extension Type.
From the Development Object menu select Check.
Repeat the operation for IDOC type ZDEBMASZ.
A check log will be generated for each run with details of correctness or errors (see Figure 4).
In some situations it is possible to receive errors during the check process, especially segment length errors. The incorrect IDOC segment can be repaired and corrected by executing program RSEREPSG. This program checks the formal consistency and repairs incorrect segments. In test mode it will generate a log of formal correctness for the specified segment only. For the program to repair segments in normal mode, the underlying IDOC structures (DDIC structures) must be active. This program rectifies the lengths of the DDIC structures and not the fields themselves. RSEREPSG can also be used to change the person responsible for the object and the release flag.
Menu paths may vary slightly depending on the release/version of SAP R/3, but the procedures and the principles are the same.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
1. The point in the ALE function module where the function exit occurs
2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
Reward if Helpful.

Structure type conflict

Dear Experts,
My smartform gives dump due to identified reason.
That is
Type conflict of one field in the structure.
The data type of this filed READG is declared as p decimals 2
I am not clear how to define this field (as predefined) in the structure.
I have tried different types like DEC, NUMC which are not accepted and smartform gives dump.
I know that a proper data type declaration in the structure for field READG (P DECIMALS 2) would solve my problem.
Kindly help
kind Regards
Jogeswaraa Rao

Hi,
no, You are still missing length in declaration.
Correct will be:
DATA lv_readg(10) TYPE p DECIMALS 2.
If You create structure in ABAP code, use above statement.
If You are creating structure in SE11, there is 'Predefined type' button.
You do not need to create domain and data element,
but sometimes it is better then declaring type.
You can also find other matching data element.
Regards,
Przemysław

Build XML for Custom Nested Accordian (like Tree View Structure) for SharePoint List Data

Expected output in Xml:
<?xml version="1.0" encoding="utf-8" ?>
- <TopRoot>
- <Root id="1" Name="Department">
- <Type id="2" Name="IT">
- <SubType id="3" Name="Technology">
<SubSubType id="4" Name="Sharepoint" />
<SubSubType id="5" Name="ASP.NET" />
<SubSubType id="6" Name="HTML 5" />
</SubType>
</Type>
</Root>
</TopRoot>
List Details:
list details for storing category / sub category data and code to build tree structure for the same.
1.Create Custom List named “CategoryDetails”:
2.Create Column “Category Name” of type single line of text. Make it as required field and check Yes for Enforce Unique values.
3.Create column “Parent Category” of type lookup. under Additional Column Settings.
Get information dropdown, select “CategoryDetails”.
4.Choice column ["SRTypeName"] 1.Root,2.SRTYPE,3.SubSRTYPE, 4.SUBSUBSRTYPE
In this column dropdown, select “Category Name”:
Referance:
http://www.codeproject.com/Tips/627580/Build-Tree-View-Structure-for-SharePoint-List-Data -fine but don't want tree view just generate xml string
i just follwed above link it work perferfectly fine for building tree view but i don't want server control.
Expected Result:
My ultimate goal is to generate xml string like above format without building tree view.
I want to generate xml using web service and using xml i could convert into nested Tree View Accordian in html.
I developed some code but its not working to generate xml /string.
My modified Code:
public const string DYNAMIC_CAML_QUERY =
 "<Where><IsNull><FieldRef Name='{0}' /></IsNull></Where>";
 public const string DYNAMIC_CAML_QUERY_GET_CHILD_NODE =
 "<Where><Eq><FieldRef Name='{0}' /><Value Type='LookupMulti'>{1}</Value></Eq></Where>";
 protected void Page_Load(object sender, EventArgs e)
 if (!Page.IsPostBack)
 string TreeViewStr= BuildTree();
 Literal1.Text = TreeViewStr;
 StringBuilder sbRoot= new StringBuilder();
 protected string BuildTree()
 SPList TasksList;
 SPQuery objSPQuery;
 StringBuilder Query = new StringBuilder();
 SPListItemCollection objItems;
 string DisplayColumn = string.Empty;
 string Title = string.Empty;
 string[] valueArray = null;
 try
 using (SPSite site = new SPSite(SPContext.Current.Web.Url))
 using (SPWeb web = site.OpenWeb())
 TasksList = SPContext.Current.Web.Lists["Service"];
 if (TasksList != null)
 objSPQuery = new SPQuery();
 Query.Append(String.Format(DYNAMIC_CAML_QUERY, "Parent_x0020_Service_x0020_Id"));
 objSPQuery.Query = Query.ToString();
 objItems = TasksList.GetItems(objSPQuery);
 if (objItems != null && objItems.Count > 0)
 foreach (SPListItem objItem in objItems)
 DisplayColumn = Convert.ToString(objItem["Title"]);
 Title = Convert.ToString(objItem["Title"]);
 int rootId=objItem["ID"].ToString();
 sbRoot.Append("<Root id="+rootId+"
Name="+Title+">");
 string SRAndSUBSRTpe = CreateTree(Title, valueArray,
null, DisplayColumn, objItem["ID"].ToString());
 sbRoot.Append(SRAndSUBSRTpe);
 SRType.Clear();//make SRType Empty
 strhtml.Clear();
 SRType.Append("</Root>");
 catch (Exception ex)
 throw ex;
 return SRType.ToString();
 StringBuilder strhtml = new StringBuilder();
 private string CreateTree(string RootNode, string[] valueArray,
 List<SPListItem> objNodeCollection, string DisplayValue, string KeyValue)
 try
 strhtml.Appends(GetSRType(KeyValue, valueArray, objNodeCollection);
 catch (Exception ex)
 throw ex;
 return strhtml;
 StringBuilder SRType = new StringBuilder();
 private string GetSRType(string RootNode,
 string[] valueArray, List<SPListItem> objListItemColn)
 SPQuery objSPQuery;
 SPListItemCollection objItems = null;
 List<SPListItem> objNodeListItems = new List<SPListItem>();
 objSPQuery = new SPQuery();
 string objNodeTitle = string.Empty;
 string objLookupColumn = string.Empty;
 StringBuilder Query = new StringBuilder();
 SPList objTaskList;
 SPField spField;
 string objKeyColumn;
 string SrTypeCategory;
 try
 objTaskList = SPContext.Current.Web.Lists["Service"];
 objLookupColumn = "Parent_x0020_Service_x0020_Id";//objTreeViewControlField.ParentLookup;
 Query.Append(String.Format
 (DYNAMIC_CAML_QUERY_GET_CHILD_NODE, objLookupColumn, RootNode));
 objSPQuery.Query = Query.ToString();
 objItems = objTaskList.GetItems(objSPQuery);
 foreach (SPListItem objItem in objItems)
 objNodeListItems.Add(objItem);
 if (objNodeListItems != null && objNodeListItems.Count > 0)
 foreach (SPListItem objItem in objNodeListItems)
 RootNode = Convert.ToString(objItem["Title"]);
 objKeyColumn = Convert.ToString(objItem["ID"]);
 objNodeTitle = Convert.ToString(objItem["Title"]);
 SrTypeCategory= Convert.ToString(objItem["SRTypeName"]);
 if(SrTypeCategory =="SRtYpe")
 SRType.Append("<Type id="+objKeyColumn+" Name="+RootNode+ ">");
 if (!String.IsNullOrEmpty(objNodeTitle))
 SRType.Append(GetSRType(objKeyColumn, valueArray, objListItemColn));
 if(SrTypeCategory =="SRSubTYpe")
 SRType.Append("<SRSubType id="+objKeyColumn+" Name="+RootNode+
">");
 if (!String.IsNullOrEmpty(objNodeTitle))
 SRType.Append(GetSRType(objKeyColumn, valueArray, objListItemColn));
 if(SrTypeCategory =="SubSubTYpe")
 SRType.Append("<SubSubType id="+objKeyColumn+" Name="+RootNode +"
></SubSubType");
 SRType.Append("</SubType>");
 SRType.Append("</Type>");
 catch (Exception ex)
 throw ex;
 return SRType.ToString();
 // Call method again (recursion) to get the child items

Hi,
According to your post, my understanding is that you want to custom action for context menu in "Site Content and Structure" in SharePoint 2010.
In "SiteManager.aspx", SharePoint use MenuItemTemplate class which represent a control that creates an item in a drop-down menu.
For example, to create or delete the ECB menu for a list item in
"Site Content and Structure", we can follow the steps below:
To add the “My Like” menu, we can add the code below:
<SharePoint:MenuItemTemplate
UseShortId=false
id="OLListItemLike"
runat="server"
Text="My Like"
ImageUrl="/_layouts/images/DelItem.gif"
ClientOnClickNavigateUrl="https://www.google.com.hk/"
/>
To remove the “Delete” menu, we can comment the code below:
<SharePoint:MenuItemTemplate
UseShortId=false
id="OLListItemDelete"
runat="server"
Text="<%$Resources:cms,SmtDelete%>"
ImageUrl="/_layouts/images/DelItem.gif"
ClientOnClickScript="%SmtObjectDeleteScript%"
/>
The result is as below:
More information:
MenuItemTemplate Class (Microsoft.SharePoint.WebControls)
MenuItemTemplate.ClientOnClickScript property (Microsoft.SharePoint.WebControls)
Best Regards,
Linda Li
Linda Li
TechNet Community Support

How to create a report using XML data source from Crystal Report Designer

Hi,
Iu2019m having Crystal Report Designer XI R2 SP4. Iu2019m trying to create a report using XML data source stored on disk. This is a customer order report and the xml is structured in such a way that it has an order details header part (master) and then it has several order lines (detail). One order line can have several order line characteristics (detail-detail). So what I need to know is now I can design this layout from the designer. If this was done using views I can do it with sub-reports but using xml data this seems to be different. Can you help me to design this layout? I have included the xml and xsd as well.
Thank you in advance.
Regards,
Chanaka
XML
<?xml version="1.0" encoding="UTF-8"?>
<CUSTOMER_ORDER_CONF_REP_REQUEST xmlns:xsi="http://www.w3.org/2001/XMLSchema" xmlns="urn:ifsworld-com:customer_order_conf_rep">
 <CUSTOMER_ORDER_CONF_REP>
 <ORDER_NO>D555809</ORDER_NO>
 <PRINTED_DATE>2009-03-26T08:52:54</PRINTED_DATE>
 <AUTHORIZE_NAME>Chanaka</AUTHORIZE_NAME>
 <CUSTOMER_NO>CU-1473-INV</CUSTOMER_NO>
 <CUST_NAME>Mr.Johan Matts</CUST_NAME>
 <SHIP_ADDR_1>93,Main Street</SHIP_ADDR_1>
 <SHIP_ADDR_2>Negambo Road</SHIP_ADDR_2>
 <SHIP_ADDR_3>Watthala</SHIP_ADDR_3>
 <SHIP_ADDR_4>SRI LANKA</SHIP_ADDR_4>
 <BILL_ADDR_1>93,Main Street</BILL_ADDR_1>
 <BILL_ADDR_2>Negambo Road</BILL_ADDR_2>
 <BILL_ADDR_3>Watthala</BILL_ADDR_3>
 <BILL_ADDR_4>SRI LANKA</BILL_ADDR_4>
 <CUSTOMER_PO_NO>112984638</CUSTOMER_PO_NO>
 <CUSTOMER_FAX>112984639</CUSTOMER_FAX>
 <CUSTOMER_EMAIL>abcbababab</CUSTOMER_EMAIL>
 <ORDER_LINES>
 <ORDER_LINE>
 <LINE_NO>1</LINE_NO>
 <CUSTOMER_PART_NO>NW-IP11</CUSTOMER_PART_NO>
 <CUSTOMER_PART_DESC>iPod</CUSTOMER_PART_DESC>
 <SALE_UNIT_PRICE>1200</SALE_UNIT_PRICE>
 <PRICE_TOTAL>1200</PRICE_TOTAL>
 <DISCOUNT>0</DISCOUNT>
 <PRICE_QTY>1</PRICE_QTY>
 <ORDER_LINE_CHARACTERSTICS>
 <CHARACTERISTIC_ITEM>
 <CHARACTERISTIC_ID xsi:nil="1"/>
 <CHARACTERISTIC_VALUE xsi:nil="1"/>
 </CHARACTERISTIC_ITEM>
 </ORDER_LINE_CHARACTERSTICS>
 </ORDER_LINE>
 <ORDER_LINE>
 <LINE_NO>2</LINE_NO>
 <CUSTOMER_PART_NO>NW-IP24</CUSTOMER_PART_NO>
 <CUSTOMER_PART_DESC>XGA Projector</CUSTOMER_PART_DESC>
 <SALE_UNIT_PRICE>500</SALE_UNIT_PRICE>
 <PRICE_TOTAL>1500</PRICE_TOTAL>
 <DISCOUNT>0</DISCOUNT>
 <PRICE_QTY>3</PRICE_QTY>
 <ORDER_LINE_CHARACTERSTICS>
 <CHARACTERISTIC_ITEM>
 <CHARACTERISTIC_ID>1</CHARACTERISTIC_ID>
 <CHARACTERISTIC_VALUE>Free Instalation</CHARACTERISTIC_VALUE>
 </CHARACTERISTIC_ITEM>
 </ORDER_LINE_CHARACTERSTICS>
 </ORDER_LINE>
 <ORDER_LINE>
 <LINE_NO>3</LINE_NO>
 <CUSTOMER_PART_NO>NW-IP02</CUSTOMER_PART_NO>
 <CUSTOMER_PART_DESC>Sony DVD Player</CUSTOMER_PART_DESC>
 <SALE_UNIT_PRICE>1000</SALE_UNIT_PRICE>
 <PRICE_TOTAL>1000</PRICE_TOTAL>
 <DISCOUNT>0</DISCOUNT>
 <PRICE_QTY>1</PRICE_QTY>
 <ORDER_LINE_CHARACTERSTICS>
 <CHARACTERISTIC_ITEM>
 <CHARACTERISTIC_ID>1</CHARACTERISTIC_ID>
 <CHARACTERISTIC_VALUE>Free 5 DVDs</CHARACTERISTIC_VALUE>
 </CHARACTERISTIC_ITEM>
 </ORDER_LINE_CHARACTERSTICS>
 </ORDER_LINE>
 <ORDER_LINE>
 <LINE_NO>4</LINE_NO>
 <CUSTOMER_PART_NO>NW-IP99</CUSTOMER_PART_NO>
 <CUSTOMER_PART_DESC>Flatscreen TV</CUSTOMER_PART_DESC>
 <SALE_UNIT_PRICE>1500</SALE_UNIT_PRICE>
 <PRICE_TOTAL>1350</PRICE_TOTAL>
 <DISCOUNT>10</DISCOUNT>
 <PRICE_QTY>1</PRICE_QTY>
 <ORDER_LINE_CHARACTERSTICS>
 <CHARACTERISTIC_ITEM>
 <CHARACTERISTIC_ID>1</CHARACTERISTIC_ID>
 <CHARACTERISTIC_VALUE>Free Delivery</CHARACTERISTIC_VALUE>
 </CHARACTERISTIC_ITEM>
 <CHARACTERISTIC_ITEM>
 <CHARACTERISTIC_ID>2</CHARACTERISTIC_ID>
 <CHARACTERISTIC_VALUE>1 year additional warranty</CHARACTERISTIC_VALUE>
 </CHARACTERISTIC_ITEM>
 </ORDER_LINE_CHARACTERSTICS>
 </ORDER_LINE>
 <ORDER_LINE>
 <LINE_NO>5</LINE_NO>
 <CUSTOMER_PART_NO>NW-IP56</CUSTOMER_PART_NO>
 <CUSTOMER_PART_DESC>Sony MP3 Player</CUSTOMER_PART_DESC>
 <SALE_UNIT_PRICE>200</SALE_UNIT_PRICE>
 <PRICE_TOTAL>400</PRICE_TOTAL>
 <DISCOUNT>0</DISCOUNT>
 <PRICE_QTY>2</PRICE_QTY>
 <ORDER_LINE_CHARACTERSTICS>
 <CHARACTERISTIC_ITEM>
 <CHARACTERISTIC_ID>1</CHARACTERISTIC_ID>
 <CHARACTERISTIC_VALUE>Free carry belt</CHARACTERISTIC_VALUE>
 </CHARACTERISTIC_ITEM>
 <CHARACTERISTIC_ITEM>
 <CHARACTERISTIC_ID>2</CHARACTERISTIC_ID>
 <CHARACTERISTIC_VALUE>Free promotional 4GB memory bar</CHARACTERISTIC_VALUE>
 </CHARACTERISTIC_ITEM>
 <CHARACTERISTIC_ITEM>
 <CHARACTERISTIC_ID>3</CHARACTERISTIC_ID>
 <CHARACTERISTIC_VALUE>No warranty on memory bar</CHARACTERISTIC_VALUE>
 </CHARACTERISTIC_ITEM>
 </ORDER_LINE_CHARACTERSTICS>
 </ORDER_LINE>
 </ORDER_LINES>
 </CUSTOMER_ORDER_CONF_REP>
</CUSTOMER_ORDER_CONF_REP_REQUEST>
XSD
<?xml version="1.0" encoding="UTF-8"?>
<?report module="ORDER" package="CUSTOMER_ORDER_CONF_REP" ?>
<xs:schema targetNamespace="urn:ifsworld-com:customer_order_conf_rep" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="urn:ifsworld-com:customer_order_conf_rep" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:element name="CUSTOMER_ORDER_CONF_REP_REQUEST">
<xs:complexType>
<xs:all minOccurs="1" maxOccurs="1">
<xs:element name="CUSTOMER_ORDER_CONF_REP">
<xs:complexType>
<xs:choice minOccurs="0" maxOccurs="50">
<xs:element name="ORDER_NO" nillable="true" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:maxLength value="2000"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="PRINTED_DATE" type="xs:dateTime" nillable="true" minOccurs="0"/>
<xs:element name="AUTHORIZE_NAME" nillable="true" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:maxLength value="2000"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="CUSTOMER_NO" nillable="true" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:maxLength value="2000"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="CUSTOMER_PO_NO" nillable="true" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:maxLength value="2000"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="CUST_NAME" nillable="true" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:maxLength value="2000"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="SHIP_ADDR_1" nillable="true" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:maxLength value="2000"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="SHIP_ADDR_2" nillable="true" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:maxLength value="2000"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="SHIP_ADDR_3" nillable="true" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:maxLength value="2000"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="SHIP_ADDR_4" nillable="true" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:maxLength value="2000"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="BILL_ADDR_1" nillable="true" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:maxLength value="2000"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="BILL_ADDR_2" nillable="true" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:maxLength value="2000"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="BILL_ADDR_3" nillable="true" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:maxLength value="2000"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="BILL_ADDR_4" nillable="true" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:maxLength value="2000"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="CUSTOMER_FAX" nillable="true" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:maxLength value="2000"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="CUSTOMER_EMAIL" nillable="true" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:maxLength value="2000"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="ORDER_LINES" nillable="true" minOccurs="0">
<xs:complexType>
<xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:element name="ORDER_LINE">
<xs:complexType>
<xs:choice minOccurs="0" maxOccurs="39">
<xs:element name="LINE_NO" nillable="true" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:maxLength value="2000"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="SALE_UNIT_PRICE" type="xs:float" nillable="true" minOccurs="0"/>
<xs:element name="PRICE_TOTAL" type="xs:float" nillable="true" minOccurs="0"/>
<xs:element name="DISCOUNT" type="xs:float" nillable="true" minOccurs="0"/>
<xs:element name="PRICE_QTY" type="xs:float" nillable="true" minOccurs="0"/>
<xs:element name="CUSTOMER_PART_NO" nillable="true" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:maxLength value="4000"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="CUSTOMER_PART_DESC" nillable="true" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:maxLength value="4000"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="ORDER_LINE_CHARACTERSTICS" nillable="true" minOccurs="0">
<xs:complexType>
<xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:element name="CHARACTERISTIC_ITEM">
<xs:complexType>
<xs:choice minOccurs="0" maxOccurs="6">
<xs:element name="CHARACTERISTIC_ID" nillable="true" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:maxLength value="2000"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="CHARACTERISTIC_VALUE" nillable="true" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:maxLength value="2000"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:choice>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:choice>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:choice>
</xs:complexType>
</xs:element>
</xs:all>
</xs:complexType>
</xs:element>
</xs:schema>

Hi Sourashree,
Thank you for the response and ideas you have given me so far. I can get the fetch the data from the data source without any problem. That is I do the following,
1. New Report
2. From Create New Connection-> XML
3. Provide the u201CLocal XML Fileu201D and have u201CSpecify Schema Fileu201D checked -> Next
4. Provide the u201CLocal Schema Fileu201D -> Finish
Then I can see the following under XML
+ CUSTOMER_ORDER_CONF_REP_REQUEST
 CUSTOMER_ORDER_CONF_REP_REQUEST
 CUSTOMER_ORDER_CONF_REP_REQUEST/CUSTOMER_ORDER_CONF_REP
 CUSTOMER_ORDER_CONF_REP_REQUEST/ CUSTOMER_ORDER_CONF_REP/ORDER_LINES
 CUSTOMER_ORDER_CONF_REP_REQUEST/ CUSTOMER_ORDER_CONF_REP/ORDER_LINES/ORDER_LINE
 CUSTOMER_ORDER_CONF_REP_REQUEST/ CUSTOMER_ORDER_CONF_REP/ORDER_LINES/ORDER_LINE/ORDER_LINE_CHARACTERSTICS
 CUSTOMER_ORDER_CONF_REP_REQUEST/ CUSTOMER_ORDER_CONF_REP/ORDER_LINES/ORDER_LINE/ORDER_LINE_CHARACTERSTICS/CHARACTERSTIC_ITEM
And from here if I add the following three I can get all the fields I need to the report
 CUSTOMER_ORDER_CONF_REP_REQUEST/CUSTOMER_ORDER_CONF_REP
 CUSTOMER_ORDER_CONF_REP_REQUEST/ CUSTOMER_ORDER_CONF_REP/ORDER_LINES/ORDER_LINE
 CUSTOMER_ORDER_CONF_REP_REQUEST/ CUSTOMER_ORDER_CONF_REP/ORDER_LINES/ORDER_LINE/ORDER_LINE_CHARACTERSTICS/CHARACTERSTIC_ITEM
Then I come to the Linking section. Here I canu2019t link anything. There is a common field called u201CInternal_IDu201D but I canu2019t link using it. So I get a message when I click Next. From here I add all the fields.
For this point onwards only I need help. How do I group, add fields and design the layout so I can get an report output as follows.
Date
Order number Authorized code
Customer No
Name
Phone
Fax email
Shipping address 1 Billing Address 1
Shipping address 2 Billing Address 2
Shipping address 3 Billing Address 3
Shipping address 4 Billing Address 4
Order Line 1 detailsu2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026 LINE_NO CUSTOMER_PART_NO CUSTOMER_PART_DESC SALE_UNIT_PRICE PRICE_QTY DISCOUNT PRICE_TOTAL
Characteristic details belonging to Order line 1 CHARACTERISTIC_ID 1 CHARACTERISTIC_VALUE1
 CHARACTERISTIC_ID 2 CHARACTERISTIC_VALUE2
 CHARACTERISTIC_ID 3 CHARACTERISTIC_VALUE3
Order Line 2 detailsu2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026
Characteristic details belonging to Order line 2
Order Line 3 detailsu2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026
Characteristic details belonging to Order line 3
Order Line 4 detailsu2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026
Characteristic details belonging to Order line 4
Order Line 5 detailsu2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026
Characteristic details belonging to Order line 5
How can I achieve this kind of a layout using the give xml and xsd? Should I use grouping if so how should I do the grouping?
I have included the full xml and xsd in the first mail I posted but I canu2019t see it now. I can include that again if you want.
Regards,
Chanaka

How do I create an Integration Domain with 3 servers ?

Hi,
I would like to create a WLI domain with three servers: 
Ã˜ One for the administration console; 
Ã˜ One for WLI; 
Ã˜ And the last to deploy EJB Session (which are the service called by WLI) 
To create the domain, I use the WLI 8.1 SP4 Configuration Wizard. 
After creating the domain with 3 services, I have not succeeded to start the WLI Server. 
For another test, I would like to create a WLI domain with two servers: 
Ã˜ One for the administration console and WLI; 
Ã˜ And the last to deploy EJB Session 
To create the main server, I have used the configuration wizard. For the other, I have used the console administration. With this configuration, the message brocker was not initialised. 
For the last test, I have created a domain with single server and I had no errors. 
So, my question is: What is the method to create a domain with three servers? 
Thanks for your help 
Case 1: Test to define 3 servers
<4 nov. 2005 14 h 45 CET> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "etsoWLI" for domain "complexDomain">
The WebLogic Server did not start up properly.
weblogic.management.AbortDeploymentException: weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
[com.bea.wli.management.BPMComponentInitializationException: Failed to initialize ProcessConfiguration module]
at weblogic.t3.srvr.StartupClassService.addDeployment(StartupClassService.java:92)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
Reason: [Deployer:149601]The deployment framework was unable to resume accepting requests.weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
[com.bea.wli.management.BPMComponentInitializationException: Failed to initialize ProcessConfiguration module]
<4 nov. 2005 14 h 45 CET> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: [Deployer:149601]The deployment framework was unable to resume accepting requests.weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
[com.bea.wli.management.BPMComponentInitializationException: Failed to initialize ProcessConfiguration module]>
 
Case 2 : Test to define 2 servers 
<4 nov. 2005 15 h 03 CET> <Error> <WLI-Core> <BEA-484037> <Process Tracking failed to initialize properly. Tracking data cannot be recorded for process typ
e "/MailProcess/processes/process02.jpd".>
<4 nov. 2005 15 h 03 CET> <Error> <WLI-Core> <BEA-481000> <The Message Broker is not initialized>
<4 nov. 2005 15 h 03 CET> <Error> <WLW> <000000> <Failed to register subscriptions for JPD /MailProcess/processes/process02.jpd
java.lang.RuntimeException: The Message Broker is not initialized
at com.bea.wli.broker.MessageBroker.getMessageBroker(MessageBroker.java:277)
at com.bea.wli.control.MBUtils.registerSubscriptionRules(MBUtils.java:99)
at com.bea.wli.bpm.runtime.JpdDispFile$3.run(JpdDispFile.java:903)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at com.bea.wli.bpm.runtime.JpdDispFile.registerSubscriptions(JpdDispFile.java:912)
at com.bea.wli.bpm.runtime.JpdDispFile.<init>(JpdDispFile.java:212)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at com.bea.wlw.runtime.core.dispatcher.DispUnit.loadDispFile(DispUnit.java:219)
at com.bea.wlw.runtime.core.dispatcher.DispUnit.<init>(DispUnit.java:153)
at com.bea.wlw.runtime.core.dispatcher.DispCache.ensureDispUnit(DispCache.java:578)
at com.bea.wlw.runtime.core.dispatcher.HttpServerHelper.getDispUnit(HttpServerHelper.java:501)
at com.bea.wlw.runtime.core.dispatcher.HttpServerHelper.executeGetRequest(HttpServerHelper.java:541)
at com.bea.wlw.runtime.core.dispatcher.HttpServer.doGet(HttpServer.java:81)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6718)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
>
javax.management.InstanceNotFoundException: lastEtsoDomain:Location=etsoMain,Name=MsgBroker,Type=MsgBrokerRuntime (admin server:true)
at weblogic.management.internal.MBeanHomeImpl.getMBean_helper(MBeanHomeImpl.java:145)
at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.java:130)
at weblogic.management.internal.MBeanHomeImpl.getRuntimeMBean(MBeanHomeImpl.java:557)
at weblogic.management.internal.MBeanHomeImpl.getRuntimeMBean(MBeanHomeImpl.java:549)
at weblogic.management.internal.AdminMBeanHomeImpl.getRuntimeMBean(AdminMBeanHomeImpl.java:580)
at com.bea.wli.management.MBeanHelper.getMsgBrokerRuntimeMBean(MBeanHelper.java:549)
at com.bea.wli.bpm.runtime.__broker.listSubscriptions(__broker.java:178)
at com.bea.wli.bpm.runtime.__broker._jspService(__broker.java:833)
at com.bea.wlw.runtime.core.dispatcher.ServiceView.dispatchToPage(ServiceView.java:269)
at com.bea.wlw.runtime.core.dispatcher.ServiceView.forward(ServiceView.java:438)
at com.bea.wlw.runtime.core.dispatcher.HttpServerHelper.executeGetRequest(HttpServerHelper.java:617)
at com.bea.wlw.runtime.core.dispatcher.HttpServer.doGet(HttpServer.java:81)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6718)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

To use 3 managed servers with Weblogic, I must a cluster environment.
Weblogic say: "WebLogic Integration domain that includes an administrative server and one or more managed servers must include a cluster. A WebLogic Integration domain that includes an administrative server and one or more managed servers without a cluster is an unsupported configuration."
Fred

Creating Structure, Type, Domain in Data Dictonary.

Similar Messages

Maybe you are looking for