topic Re: HLEVEL in Application Development and Automation Discussions

HLEVEL

Former Member — Fri, 20 Feb 2009 06:29:58 GMT

Hi,

I need some help. I am creating an outbound idoc. I have at hlevel = 2 , 1 data segment

hlevel = 3 , 1 data segment and hlevel = 4, 4 data segments.

Pls provide me with a code that will help me pass this as I am currently getting status error 26 for my idoc

Re: HLEVEL

Former Member — Mon, 23 Feb 2009 05:40:46 GMT

Guys!!,

I founnd smething regarding PSGNUM and HLEVEL but couldnt understand what the relationship is!..Please help

Re: HLEVEL

Former Member — Mon, 23 Feb 2009 07:21:23 GMT

Hi,

Do not make use of PSGNUM and HLEVEL. Loop at the idoc_data and look for parent segment and by making use of index insert your segment under that. Here in this example segment Z1YAMARA inserted under parent E1MARAM. 'Z1MDMAM' , Z1MAEXM' and 'Z1MAPEM' inseted under parent E1MARCM.

data : wa_e1maram type e1maram,

v_index type sy-tabix,

wa_z1mdmam type z1mdmam,

wa_z1yamara type z1yamara,

wa_z1maexm type z1maexm,

wa_z1mapem type z1mapem,

lw_data type edidd.

loop at idoc_data into lw_data where segnam = 'E1MARAM'.

v_index = sy-tabix + 1.

move 'Z1YAMARA' to lw_data-segnam.

move wa_z1yamara to lw_data-sdata.

insert lw_data into idoc_data index v_index.

endloop.

clear v_index.

loop at idoc_data into lw_data where segnam = 'E1MARCM' .

v_index = sy-tabix + 1.

move 'Z1MDMAM' to lw_data-segnam.

move wa_z1mdmam to lw_data-sdata.

insert lw_data into idoc_data index v_index.

v_index = v_index + 1.

move 'Z1MAEXM' to lw_data-segnam.

move wa_z1maexm to lw_data-sdata.

insert lw_data into idoc_data index v_index.

v_index = v_index + 1.

move 'Z1MAPEM' to lw_data-segnam.

move wa_z1mapem to lw_data-sdata.

insert lw_data into idoc_data index v_index.

clear lw_data.

endloop.

Thanks,

Asit Purbey.

Re: HLEVEL

Former Member — Mon, 23 Feb 2009 07:29:52 GMT

Hi,

I am sorry but i am getting stats 29 error ... I have created segments and now want to put my data into a variable idoc_data of type edidd.... So i want to know how to avoid this error..What are the posibilities?

Re: HLEVEL

Former Member — Mon, 23 Feb 2009 07:39:56 GMT

Hi,

For data population in custom segment the logic i have mentioned in my earlier post will work. If you are getting some error here then idoc should be in 26 status. For idoc in 29 status, there is some configuration problem. If you tell me the error text then i can help you. You just check the below steps once again.

1) Logical systems(BD54)

2) logical systems to clients(SCC4)

3) RFC destination (SM59)

4) Port(we21)

5) Partner profile(we20)

6) Distribution model model( BD64) and generate partner profile.

Thanks,

Asit Purbey

Re: HLEVEL

Former Member — Mon, 23 Feb 2009 07:40:42 GMT

Hi,

For error status 29: ALE servicw error. Check partner profiles are set up correctly.

Regards

Vinod

Re: HLEVEL

Former Member — Mon, 23 Feb 2009 09:48:48 GMT

I'll try and be a litte more clear about my problem:

I have created a basic type zhrdb_02 with header segm zhrdb_segm whose child is zhrdb_0002(infty 2).The child of zhrdb_002 is zhrdb_0001,zhrdb_0006,zhrdb_0105,zhrdb_0004.

Also, i have created 5 segments segm_hdr , segm_0002 , segm_0001,segm_0105,segm_0004 each containing req data from respective infty...

Now when I run my program I get two errors

1. Status 26 EDI: Syntax error in IDoc (segment cannot be identified)

2. Status 29 Errors when compiling version: Target structure ZHRDB_01 does not match IDoc

Does this have to do with HLEVEL and PSEGNUM?

Re: HLEVEL

Former Member — Wed, 25 Feb 2009 05:40:14 GMT

any help???

Re: HLEVEL

Former Member — Wed, 25 Feb 2009 06:26:10 GMT

Hi,

For error status 29: ALE servicw error. u need to specify the global declaration like

1.go to SALE tcode in that go to Modeling and implementing busniness process

specify the u r organinzational units.

if any queries let me know .

regards

linganna

Re: HLEVEL

Former Member — Wed, 25 Feb 2009 07:38:27 GMT

Hi,

First of all concentrate on 26 status, correct the logic for data fetching part for segments. After correction idocs should directly come in 29 status. Then go for 29 status.

Thanks,

Asit Purbey.

Edited by: Asit Purbey on Feb 25, 2009 8:38 AM

Re: HLEVEL

Former Member — Tue, 03 Mar 2009 04:42:39 GMT

For status 26 I gt d following info

EDI: Syntax error in IDoc (segment cannot be identified)

Message no. E0078

Diagnosis

The segment Z10006_0004 does not occur at the current level of the basic type ZHRDB_02 (extension ).

This error can have several reasons:

The segment Z10006_0004 is assigned to a group whose header segment does not occur.

The segment Z10006_0004 does not exist in the syntax description of the basic type ZHRDB_02 (extension ).

The sequence of segments in the group in which the segment appears is incorrect.

Previous errors ('mandatory' segment or group missing) may be due to this error.

Procedure

Please check the IDoc or the syntax description of the basic type ZHRDB_02 (extension ).

And for status 29,

Diagnosis

The version compiler has determined the target structure (basic IDoc type ZHRDB_01, extension structure ) and found that the IDoc to be processed (basic IDoc type ZHRDB_02, extension structure ) does not contain segments that belong to the target structure.

Procedure

Please check that the target structure has been set correctly in the outbound partner profiles.