Skip to main content
Solved

EDI - Direct Delivery (DIRDEL)

  • September 21, 2022
  • 2 replies
  • 379 views

Forum|alt.badge.img+5

Is it possible to receive a DIRDEL message of an external company which is not in IFS?
If yes, how does this work?

Best answer by Kanishka Dilana

@flesabriw At the moment, we can’t receive DIRDEL messages through Web-services (it is not listed in web-services as a BizAPI), hence your requirement can’t be accomplished using the functionalities available in the Core version of IFSAPPS10.

I see below note in the one of the Product Development reference documents  further explaining this,

“..Note that in the first versions of the DIRDEL messages they were actually called DESADV…When the more advanced DESADV was introduced the old, more internal DESADV was renamed to DIRDEL
As mentioned above the DIRDEL is mainly supposed for internal use – used for registering direct delivery transactions. It mainly uses the MHS technique, meaning that messages are directly copied between out and in box. So from my point of view, I can’t really see the use of ITS for DIRDEL, as long as the “MHS” technique (copy from message out to message in-box) still exists.“

That why the DIRDEL message class doesn’t exist in the BizApi format.

Do you feel any customer willing to get support for the DIRDEL message in the BizApi format, please let us know and we can create an ‘Idea’ so that your requirement/request is considered for Future releases.

View original
Did this topic help you find an answer to your question?

2 replies

Kanishka Dilana
Superhero (Employee)
Forum|alt.badge.img+16
  • Superhero (Employee)
  • 122 replies
  • Answer
  • September 21, 2022

@flesabriw At the moment, we can’t receive DIRDEL messages through Web-services (it is not listed in web-services as a BizAPI), hence your requirement can’t be accomplished using the functionalities available in the Core version of IFSAPPS10.

I see below note in the one of the Product Development reference documents  further explaining this,

“..Note that in the first versions of the DIRDEL messages they were actually called DESADV…When the more advanced DESADV was introduced the old, more internal DESADV was renamed to DIRDEL
As mentioned above the DIRDEL is mainly supposed for internal use – used for registering direct delivery transactions. It mainly uses the MHS technique, meaning that messages are directly copied between out and in box. So from my point of view, I can’t really see the use of ITS for DIRDEL, as long as the “MHS” technique (copy from message out to message in-box) still exists.“

That why the DIRDEL message class doesn’t exist in the BizApi format.

Do you feel any customer willing to get support for the DIRDEL message in the BizApi format, please let us know and we can create an ‘Idea’ so that your requirement/request is considered for Future releases.


Forum|alt.badge.img+5
  • Author
  • Sidekick (Partner)
  • 6 replies
  • September 21, 2022

Hello Kanishka,

thanks so much for your quick and useful answer.
That correspond with my analysis.

 

Yes, I have a customer which wants to send DIRDEL from an company which is not in IFS.
Currently, they create customer orders with supply code “purchase transit”, which will create a purchase order. This purchase order is sent via ORDERS (bizapi) to the other company. The other company then sends back a DESADV (bizapi).
Now, they want to send a DIRDEL (= direct delivery message) instead of DESADV, so that the delivery is directly registered. This means, the supply code of the customer order is “purchase direct”.

Thanks for your help.


Frbese
Do Gooder (Partner)
Forum|alt.badge.img+2
  • Do Gooder (Partner)
  • 5 replies
  • March 10, 2025

I also have a customer case where the external supplier deliveries directly to end customer XY and want to info the main supplier, which perform a direct delivery:

 

So, there is a use case for this

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings