Skip to main content
Solved

DIRDEL and Invoice not working for INET_TRANS

  • May 11, 2026
  • 4 replies
  • 42 views

Forum|alt.badge.img+3

Hello Community,

Need your expertise on below scenario, any input or ideas are welcome as I am trying to figure this out still.

 

We are running a bit unusual intercompany set up with an integration between app 8 and cloud.

we are using INET_TRANS as media code to support this as it generates an application message

for DIRDEL and INVOICE message classes INET_TRANS does not seem to trigger the application messages , my requirement is to generate an application message for DIRDEL and INVOICE so we can communicate to APP8 from cloud to process direct delivery and invoicing, dispatch advice is triggering. I have message class added in both ends message defaults enabled to create automatically as well.

 

 

Best answer by Piyal Perera

Hi ​@XitKushmG,

  I chat with Cursor and would like to share with the following information, hoping it may useful.

 

DIRDEL is intentionally not in that list in the current implementation: it stays on the connectivity message path only, even when the media code is INET_TRANS.

The procedure is even documented as generating a DIRDEL EDI/MHS message:

-- Send_Direct_Delivery

--   Generate a internal direct delivery (DIRDEL) EDI/MHS message for

--   the specified order.

So if you configure INET_TRANS as the media for DIRDEL, you still get the connectivity outbox flow for that message; you do not get the ITS-style application message that other message types use. 

Message Class that support INET_TRANS:

Area

Message class / context

message_function (routing)

Order

ORDRSP (customer order confirmation)

SEND_CUST_ORD_CONF_INET_TRANS

Order

PRICAT (price list / agreement)

SEND_PRICAT_FOR_PRICE_LIST_INET_TRANS, SEND_PRICAT_FOR_AGREEMENT_INET_TRANS

Shipment

DESADV (dispatch advice)

SEND_DISPATCH_ADVICE_INET_TRANS

Purchase

ORDERS

SEND_PURCHASE_ORDER_INET_TRANS

Purchase

ORDCHG

SEND_PURCHASE_ORDER_CHANGE_INET_TRANS

Purchase

RECADV

SEND_RECEIVING_ADVICE_FOR_INET_TRANS

Purchase

SBIINV (self-billing)

SEND_SELF_BILLING_INV_INET_TRANS

Supplier schedule

(supplier schedule transfer)

SEND_SUPP_SCHED_INET_TRANS

Invoicing

INVOIC (customer invoice)

SEND_INVOICE_INET_TRANS

4 replies

Piyal Perera
Hero (Employee)
Forum|alt.badge.img+12
  • Hero (Employee)
  • Answer
  • May 12, 2026

Hi ​@XitKushmG,

  I chat with Cursor and would like to share with the following information, hoping it may useful.

 

DIRDEL is intentionally not in that list in the current implementation: it stays on the connectivity message path only, even when the media code is INET_TRANS.

The procedure is even documented as generating a DIRDEL EDI/MHS message:

-- Send_Direct_Delivery

--   Generate a internal direct delivery (DIRDEL) EDI/MHS message for

--   the specified order.

So if you configure INET_TRANS as the media for DIRDEL, you still get the connectivity outbox flow for that message; you do not get the ITS-style application message that other message types use. 

Message Class that support INET_TRANS:

Area

Message class / context

message_function (routing)

Order

ORDRSP (customer order confirmation)

SEND_CUST_ORD_CONF_INET_TRANS

Order

PRICAT (price list / agreement)

SEND_PRICAT_FOR_PRICE_LIST_INET_TRANS, SEND_PRICAT_FOR_AGREEMENT_INET_TRANS

Shipment

DESADV (dispatch advice)

SEND_DISPATCH_ADVICE_INET_TRANS

Purchase

ORDERS

SEND_PURCHASE_ORDER_INET_TRANS

Purchase

ORDCHG

SEND_PURCHASE_ORDER_CHANGE_INET_TRANS

Purchase

RECADV

SEND_RECEIVING_ADVICE_FOR_INET_TRANS

Purchase

SBIINV (self-billing)

SEND_SELF_BILLING_INV_INET_TRANS

Supplier schedule

(supplier schedule transfer)

SEND_SUPP_SCHED_INET_TRANS

Invoicing

INVOIC (customer invoice)

SEND_INVOICE_INET_TRANS


Forum|alt.badge.img+3
  • Author
  • Do Gooder (Partner)
  • May 12, 2026

Dear Piyal,

Thank you for the swift response ! Its great to hear from you 

Invoice works for Inet Transfer when triggered with send invoice.

Do you know if we can generate DIRDEL app message other than from MHS set up, i tried connect and EDI as well but app message does not seem to create , only MHS work through but with connectivity.

 

 

i have set the message defaults on for send multi tear delivery notification on as well, but not sure it has an impact, and shipment delivery note is also printed when shipment is processed

 

Also do you know why a shipment will not come to this window? Type of shipment i want for this set up does not come here, i was hoping if it comes i can trigger it through for connect or something else other than MHS, as list is showing other message classes. May be my thinking is wrong :)

 

Thank you very much for your response anyway so we can drop Inet Transfer as a possibility

 

Best Regards

Kushmi


Piyal Perera
Hero (Employee)
Forum|alt.badge.img+12
  • Hero (Employee)
  • May 14, 2026

Hi ​@XitKushmG ,

   No, according to cursor’s finding DIRDEL only support MHS. So if you configure INET_TRANS as the media for DIRDEL, you still get the connectivity outbox flow for that message; you do not get the ITS-style application message that other message types use. 

regards,

Piyal


Forum|alt.badge.img+3
  • Author
  • Do Gooder (Partner)
  • May 18, 2026

Thank you for the reply ​@Piyal Perera 

Best Regards !!!

Kushmi