Inbound delivery IDoc to 3PL

[rangaswamy_govindaraj]

Hi Experts,

We need to send out inbound delivery document through an EDI. We intend to use the inbound delivery output message to trigger to PI/PO and send out to external system. We plan to use DESADV, DELIVERY05.

Could you please explain the mandatory requirements to process the output, any BAPI required, how does the validations performed on outgoing message. A detailed steps process will be helpful. Thank you RG

[DominikTylczyn · Accepted solution]

Hello rangaswamy.govindaraj

Your requirement is a bit non standard one, as typically inbound delivery is processed with inbound IDocs. Outbound ALE DESADV message (IDoc type DELVRY05) is for outbound deliveries.

If you think about outbound delivery DESADV is triggered by an output type e.g. LAVA. Then you assign output process code DELV (it's defined in WE41) to the partner profile in WE20. The output process code DELV points to IDOC_OUTPUT_DELVRY function. It gets the output record (NAST table) and generates the IDoc:

As inbound and outbound deliveries are maintained in the same tables, I think you should be able to easily adapt the above functionality to work with inbound deliveries:

• Define an output type for inbound delivery (transaction NACE, application E1) similar to LAVA for outbound deliveries. Here you can decide how you want to determine the output type and define access sequence accordingly. Make sure to assign processing routines RSNASTED EDI_PROCESSING for 6 EDI medium and/or RSNASTED ALE_PROCESSING for A ALE Distribution ALE medium, depending to what partner type you need to send the message.
• Define partner profile in WE20. Assign output message DESADV and link it with your output type and process code in "Message Control" tab - like this:

1. That is your DESADV message type
2. E1 output determination application for inbound deliveries
3. Put your output type here
4. The DELV process code that point to IDOC_OUTPUT_DELVRY in WE41.

I've not tested that constellation but my educated guess is that it's going to work. If not you at least know now the settings and can define your own process code in WE41, pointing to your own function module that build the IDoc from the output record.

Best regards

Dominik Tylczynski

[rangaswamy_govindaraj · Accepted solution]

Hello Dominik,

First of all thanks a lot for a detailed explanation.

I am able to set up with your guidance.

Best regards,

RG

[rangaswamy_govindaraj · Accepted solution]

Hello Dominik,

Greetings.

I have an another requirement which is quite uncommon and not standard too.

Is it possible to auto create an Inbound delivery in the buyers PO by processing suppliers Inbound delivery output message ?. Because supplier is either not creating an outbound delivery or processing goods issue and the physical goods are delivered by external party.

Scenario is : An intercompany dropshipment scenario involved 3 companies.

Company A raises a PO to Company B which raises a SO to A and a PO to replenish from Company C and goods directly delivered to A.

There is no outbound delivery or Goods issue from B to A as the goods are directly delivered by C to A..

However when C makes a shipment an ASN is sent to B and an Inbound delivery is auto created by DESADV, DELVERY05. The same ASN is to be send from Inbound delivery B to A and update in their PO. In the PO or IBD of B is to vendor C and there is no details about A (like delivery address). How to achieve this!!

Can we use outbound SPED output program, routine special function '8' functionality to trigger an inbound delivery from an Inbound?

Appreciated if you could advice on the mandatory setup is required and partner function, port, etc.

Best regards,

RG