IDOC Outbound Segment Extension Does Not Show

[Former Member]

Hello Experts!

I created an extension (ORDERS05EXT) with reference to basic type ORDERS05 for message type ORDERS.

In the ORDERS05EXT extension, I inserted a new segment type ZE1EDC01 as child to parent segment E1EDC01.

NACE:

EF (Purchase Order) > ZEDI (Output Type) > RSNASTED > EDI_PROCESSING (Routine)

FM: IDOC_OUTPUT_ORDERS

Basic Type: ORDERS05

New Message TYpe: ZORDERS

Extension: ORDERS05EXT

Object: BUS2012

Partner profiles properly set-up, CMOD project is activated, all new segments and message types are released.

Problem:

In ME29N

Purchase Order: 4300000419 (for example)

Using Message Type: ORDERS and Basic Type ORDERS05,

E1EDC01 shows with the other segments - green status in WE02 - OK!

but after adding my message type in the outbound messages in partner profiles,

Purchase Order: 4300000419 (for example)

Using Message Type: ZORDERS, Basic Type ORDERS05, Extension ORDERS05EXT,

E1EDC01 with my new segment ZE1EDC01 DOES NOT SHOW, but some segments are still populated - green status in WE02 - NOT OK!

Any ideas why this is happening?

[SuhaSaha]

Hello,

Did you populate data in the fields of the custom segment ZE1EDC01?

AFAIR if no fields are populated in a segment, it doesn't get displayed in WE02. You can check for the custom segment in WE19 though.

BR,

Suhas

[Former Member]

Hi Nicole,

In WE20(Partner Profil), in the OUTBOND params, in the MESSAGE TYPE, have provided the EXTENSION ?

Regards

HM

[Former Member]

Hi Suhas,

I don't know if the segments in ZE1EDC01 are populated, but it's PARENT segment E1EDC01 is not populated this time (using the ZORDERS message type); it was previously populated using the ORDERS message type.

Hi HM,

Yes, that's also configured in WE20.

Question: How do I assign ORDERS05 as the FirstPredecessor for extension ORDERS05EXT?

[SuhaSaha]

Hello HM,

I don't think you've this option while setting up partner profiles via WE20. The extension is maintained when you define the message type-idoc type linkage in WE82, where you've to maintain the extension name, if any.

BR,

Suhas

[Former Member]

Hi Sudhi,

In fact, there is a setting in WE20 where I indicated the extension to be used.

[SuhaSaha]

My Bad !!! I was checking for inbound parameters

[Former Member]

Hi ,

It seems to be a data related isue : Please re-run and check if that data is goin to other custom segment, or that perticular segment is getting some value.

Thanks,

Rahul

[Former Member]

Use EXIT_SAPLEINM_002 tp add your code to fill the custom segment.

[Former Member]

Hello Gunasekhar B,

Yes, that's where I placed my code to populate the new segments for outbound processing.

This exit is activated in a cmod project; but still, in ME29N repeat output of message, it wouldn't pass this part of the code.

[Former Member]

Hi Nicole,

"I don't know if the segments in ZE1EDC01 are populated, but it's PARENT segment E1EDC01 is not populated this time (using the ZORDERS message type); it was previously populated using the ORDERS message type."

In the FM "IDOC_OUTPUT_ODERS" there is a validation against Message Type, check Include - LEINMF4E, Routine - "READ_SERVICE_PACKAGE" and since "E1EDC01" relates to the Service specifications general data, this is the reason.

Just to be sure debug the above routine by placing a breakpoint and check for both the conditions that is MESTYP = "ORDERS" and "ZORDERS".

Note: If you have already copied "IDOC_OUTPUT_ORDERS" under customer name space, you can change it. If you want to continue to use the standard FM, then you can use an implicit enhancement in the below routines to fill up EDI_ESLL.

Include - LEINMF3L, Routine - FILL_SRV_ORDERS

Include - LEINMF4E, Routine - READ_SERVICE_PACKAGE

Regards,

Chen