IDoc type "DELVRY03" for INBOUND delivery confirmation and Outbound Deliver

Hi ,
We have a requirement where we have to send Inbound delivery confirmation as well as outbound delivery notification to our same customer. (3PL case)
We have a EDI partner who is receiving our messages and transforming them before sending it to customer.
Now my problem is , since I am using same idoc type (DELVRY03) for both cases therefore wondering how my EDI partner will differentiate whether received message is a INBOUND delivery confirmation or OUTBound delivery notification.
regards
Shrey

Thx for your reply ...
Wondering about the impacts , if I create a new message type like ZDESADV and attach it to DELVRY03.
In this i could have two message types DESADV and ZDESADV.
Will it impact anywhere ?
Regards
Shrey

Similar Messages

IDoc Message Type to create Inbound Delivery + Confirm + GR

Hi Experts,
I need IDoc message type which can create Inbound Delivery / Confirm / Create GR with Inbound Delivery as reference and i dont want to use DELVRY05
because I need to create Inbound Delivery / PICK / Confirm but not with Transfer Order Creation means Unnecessarily we dont want to create Transfer Orders. We need to exclude Transfer Orders and create GR.
Please do the needful.

Dear Kishore,
It's possible via writing code in enhancement spots of transaction code VL31N, MIGO_GR/MB01.
R,
Amala

SAP System inconsistency for Inbound delivery / MIGO and a "sap note"

Hello Friends ,
After following SAP instruction on how to remove the inconsistency between posting GR through MIGO (Inv. mang.) and the reflection of the goods movement status in the inbound delivery document - done that using sap note 570991
the problem is that the system start behaving in a weird way throwing unjustified Error messages for any suggested goods receipt using MIGO with reference to inbound
for example after creating an inbound delivery document and trying to post it via migo , an error will pop up
- Inbound delivery storage location cannot be changed to here Message no. VLA316
the thing is i didn't even maintain any storage location entry up to that point and yet i cannot post any stock !!
also another error like
- Inbound delivery batch cannot be changed to *** here
which doesn't make any sense because there is not batches in the inbound document !!
i think this behavior is coming from the "Document Flow Update for Stock Postings" inbound indicator at the shipping parameter at client level customization
i need help on how to overcome this annoying SAP Bug/Problem specially i am in a post go live critical situation

Hi,
The messages you mentioned were introduced to avoid inconsistency between inbound delivery and IM, through the note: 1050944 - GR for inbound delivery using inventory mgmt as of ECC 6.00
If the messages are issued incorrectly, then you may check for SAP notes (I couldnt find anything relevant) or raise an OSS ticket to SAP.
Regards,
AKPT

IDoc or BAPI for inbound delivery creation with reference to PO.

Hi
I have requirement to create a inbound delivery, I will get a ASN from external system with PO, Vendor Material number & batch. I want to know is there any BAPI or IDoc that can be used to create inbound delivery in R/3. I used BBP_INB_DELIVERY_CREATE to create inbound delivery and I was successful but problem is that inbound delivery was not updated with Vendor Material number & Batch. Can some one suggest me any other BAPI or IDoc ?
Thanks in advance
Nagendra P Boggarapu
Edited by: Nagendra P Boggarapu on May 6, 2010 4:06 PM

Use Delvry0* IDOC.
Reddy

UserExit for Inbound Delivery Confirmation

Hi All,
We are getting inbound IDOC GSVERF02 (Message Type: DELCON) to post DeliveryConfirmations.
I need to add update 2 fields to this IDOC before posting DeliveryConfirmations. Can any one tell which user exit should I use???
Thanks

Hi Pavan,
I am sorry, but I don't have access to a ECC5 version system. Also, looks like your is a industry specific(Automotive industry) solution(based on the link you posted).
But here is what I can guess. In the versions I know of, SAP almost always has user exits in these processing function modules. Look at the code of this function module IDOC_INPUT_DELCON and somewhere within there, may be a user exit that you can use.
Best of luck,
Srinivas

Restructuring the basic IDoc type DELVRY03

Hi experts,
My rek is to restructure the Basic Idoc type DELVRY03 for outbound delivery.
I am using IDOC_OUTPUT_DELVRY.
Is there any exit or badi for this.
Thanks

we31:
Create your new segment.
Save and remember release (edit-set release)
we30:
Create your new idoc type. Create like extension.
In your linked idoc type fill your standard idoc type.
Press create new sement button for add segments and put your Z segment created in we31 with min and max quantity.
Save and release the idoc type
Regards

Transfer Order for Inbound delivery with multiple line items...

Hi All,
<The flow of my report pgm is >
PO creation using Transaction - me21n
My report pick the PO created as per date given in selection screen-
Creates outbound Deliveries using BAPI_OUTB_DELIVERY_CREATE_STO
Create Transfer order FM L_TO_CREATE_DN
Confirm Transfer order FM L_TO_CONFIRM
GI is done - Inbound delivery is created
Create Transfer order FM L_TO_CREATE_DN for Inbound delivery
Confirm Transfer order FM L_TO_CONFIRM
Goods receipt.
If PO is having one item - the entire flow is working perfectly.
if my PO is having multiple items,
While creating TO for inbound deliveeies - i am facing the error.
Before calling FM,
I am assigining these values like
wa_delit-nlpla = wa_ltap_vb-vlpla.    "Source Storage Bin To Destination Bin
      wa_delit-nltyp = wa_ltap_vb-vltyp.    "Source Storage Type To Destination Storage type
      wa_delit-anfme = wa_ltap_vb-nsolm.    "Actual destination quantity
      wa_delit-letyp = wa_ltap_vb-letyp.    "Storage Unit Type
      wa_delit-altme = wa_ltap_vb-meins.    "Unit of measure
      LOOP AT i_lips INTO wa_lips WHERE vbeln = WA_VBFA-IN_DELIV.
        wa_delit-posnr = wa_lips-posnr.
        APPEND wa_delit TO it_delit.
         ENDLOOP.
As i am appending i am getting 2 line items in the tabke it_delit.
Function module :
CALL FUNCTION 'L_TO_CREATE_DN'
EXPORTING
   i_lgnum                         = l_lgnum
   i_vbeln                         = wa_vbfa-in_deliv
   i_commit_work                   = 'X'
   i_bname                         = sy-uname
   it_delit                        = it_delit
IMPORTING
   e_tanum                         = gv_tonum_1
TABLES
   t_ltap_vb                       = i_ltap_vb_1
EXCEPTIONS
   foreign_lock                     = 1
   dn_completed                     = 2
   partial_delivery_forbidden       = 3
   xfeld_wrong                      = 4
   ldest_wrong                      = 5
   drukz_wrong                      = 6
   dn_wrong                         = 7
   squit_forbidden                  = 8
   no_to_created                    = 9
   teilk_wrong                      = 10
   update_without_commit            = 11
   no_authority                     = 12
   no_picking_allowed               = 13
   dn_hu_not_choosable              = 14
   input_error                      = 15
   error_message = 16
   OTHERS = 32.
Here i am getting as input error, i need to create only one TO for multplie items
If i pass this i a loop - then it will create 2 Transfer order which is WRONG ...so please help me to over come this error.
Thanks
Senthil
Edited by: Senthil Kumar on Dec 7, 2009 3:29 PM

Hi,
Please check FM L_TO_CREATE_MULTIPLE.
Regards,
Ferry Lianto

BAPI For Inbound Delivery using Purchase Order Number

Hi All,
Is there any BAPI for posting Inbound Delivery (VL31N) using Purchase Order as reference.
thanks
bobby

Not sure what it has to do with enhancements and modifications, but there is no such BAPI:
http://tech.groups.yahoo.com/group/ABAP/message/38307
http://sap.ittoolbox.com/groups/technical-functional/sap-log-mm/bapi-for-inbound-delivery-creation-and-update-vl31n-1201265
FYI all BAPIs may be viewed in BAPI transaction.

Post Goods Receipt for Inbound Delivery via IDoc SHPCON (DELVRY03)

hi all,
I'm using IDoc SHPCON (Delvry03) for posing goods receipt for inbound delivry.
Can anyone give a sample IDoc or tell which segments must be filled.
Thanks!
Regards,
Hui

Hi Uwe,
Can an inbound WHSCON IDoc used for doing both the goods receipt in the PO and the update of the message flow in the delivery?
The binary answer would be no. You should use WMMBXY or MBGMCR instead.
But if we are doing goods receipt against Inbound delivery then answer is YES with additionally E1EDL18-QUALF = 'PIC' populated. But please remember no partial receipt is possible against Inbound Delivery.
We should populate E1EDL20-VBELN with our Inbound delivery number and line item info should go to E1EDL24.
I have done a similar interface recently where we are doing receipt against Inbound delivery. But our case was a bit complex because we had to support against Inbound delivery. So we had to go for a custom solution on top of IDOC_INPUT_DELVRY.
Hope this helps. Let me know if you have more questions.
Regards,
Rudra

Post Goods Receipt for Inbound Delivery using WHSCON IDoc

Dear All
Currently I am working on a big project dealing with EDI connections to our logistics partner for the Export business. The entire message flow between Lindt and our partner should be via EDI. Our SAP release is (still) 4.6c.
We will create two kinds of despatch advice messages, one for inbound deliveries and one for outbound deliveries for customers.
I would appreciate your support in the following problem that I am facing with the inbound delivery scenario:
We create stock transport orders (purchase orders, POs) for the goods intended to be delivered into the plant at our partner
We create a delivery (type NL = replenishment delivery) for this POs
As soon as we post the goods issue we send the despatch advice (as EANCOM D96A DESADV message) to our partner.
At this point the delivery is basically completed, i.e. packing status (PS) and goods movement status (GM / GS) are equal to 'C' (= completed).
Our logistics partner uses the same EDI message to send us the goods receipts data, e.g.:
We dispatched 50 units of a product => QTY:50:12
The partner received indeed 50 units => QVR:50:66
Please note that we do not use the QVR segment for the quantity difference (between despatched and received quantity) but it contains the received units. This way we avoid negative values in the QVR segment.
When the logistics partner sends back the DESADV message containing the received quantities (QVR segment) we want to make
the goods receipts for the products in the original stock transport order and
upate the message flow in the delivery
My idea was to transform the incoming DESADV message into a WHSCON.DELVRY03 IDoc based on the documentation in: [Delivery Interface|http://help.sap.com/saphelp_crm40/helpdata/en/e2/654b15a9f411d184ec0000e81ddea0/content.htm]
In the delivery header control E1EDL18 I used QUALF = 'PGI' (Post goods issue).
I prepared an inbound WHSCON IDoc according to the documentation mentioned below. I managed to get some feedback from the Idoc processing implying that the system tried to do the goods receipt in the PO but failed.
To make a long story short here are my questions:
Can an inbound WHSCON IDoc used for doing both the goods receipt in the PO and the update of the message flow in the delivery?
Does anybody have an example on how to fill the WHSCON IDoc?
Or is my approach a cul-de-sac ?
Kind Regards
Uwe
PS: A related question can be found here: Goods Receipt in PO AND Message Flow Update in Inb. Delivery using WMMBXY

Hi Uwe,
Can an inbound WHSCON IDoc used for doing both the goods receipt in the PO and the update of the message flow in the delivery?
The binary answer would be no. You should use WMMBXY or MBGMCR instead.
But if we are doing goods receipt against Inbound delivery then answer is YES with additionally E1EDL18-QUALF = 'PIC' populated. But please remember no partial receipt is possible against Inbound Delivery.
We should populate E1EDL20-VBELN with our Inbound delivery number and line item info should go to E1EDL24.
I have done a similar interface recently where we are doing receipt against Inbound delivery. But our case was a bit complex because we had to support against Inbound delivery. So we had to go for a custom solution on top of IDOC_INPUT_DELVRY.
Hope this helps. Let me know if you have more questions.
Regards,
Rudra

IDOC inbound: delivery confirm - set storage location at position

Hi all,
I have the issue to set with an inbound IDOC for shipping confirmation the storage location on item level. We are working with an external logistic provider so the final storage location where the goods are taken from is not not at creation time of the delivery. We have two possible storage locations.
EDI message type SDPICK cannot be used, there is no place for the storage location information LGORT.
So we tried SHPCON with process code DELV. FM: IDOC_INPUT_DELVRY
The field is in the IDOC type DELVRY03 but it is not used.
Do you have any idea how we could set the storage location on item level in the delivery with an incoming shipping / picking confirmation idoc?
Thanx a lot
regards
Hans

used a userexit in the inbound function module to get the IDOC field to the internal tables.

Mandatory fields for inbound delivery idocs

hi all
i want to generate inbound idocs for inbound delivery ASN
i am using message type DESADV and idoc type /AFS/DELVRY03
in order to generate inbound idoc what are mandatory values i have to pass to the idocs
thanks
Anil

HI,
I created inbound idoc for ASN Inbound delivery in test mode we19
i got idoc with status 62, when i am trying to process the idoc in bd87, its allowing me
is there any other way to process the idocs , so that status will be 53
thanks

Confirmation control key check for inbound delivery creation

Hi,
Currently, in the Client's company, the process of receiving goods from purchase orders looks like that (SAP-wise):
- create a purchase order,
- receive goods using MIGO and automatically create an inbound delivery,
- pack the delivery and post goods receipt.
Recently, some patches have been installed, including one described by note 1602047 (which basically enforces checking confirmation control keys if goods receipt assignment and goods receipt relevance are activated for inbound deliveries). Note says that it only affects two-step stock transfer and creation of automatic inbound deliveries using SPED output but it seems it also affects other basic processes like PO receipt in MIGO.
Now, when using the old control key (that had MRP-Relevant and GR-Relevant fields checked), the system is unable to automatically create an inbound delivery after the goods receipt is posted with MIGO (with message VL148 - Not possible to create an inbound delivery). I learned that this is because the "GR Assignment" field must be checked in the confirmation control key so it's possible to automatically create aninbound delivery after receiving a purchase order in MIGO.
After changing the confirmation control key to have the missing field checked it's not possible anymore to receive goods from PO in MIGO as the PO requires shipping notification in order to be processed in MIGO thus requiring of manual creation of an inbound delivery.
Is there any way to skip this check so the process would remain the same (this model has been working fine for few years in the Client's system) and the inbound delievery would be created automatically after posting the receipt in MIGO?
Thanks in advance,
Piotr

Hi,
don't know if you found a solution, but we received the following message from SAP:
The advent of the new version requires some attention to the users. It
was necessary to avoid inconsistencies which in the past version the
system was susceptible.
Main Program SAPMM07M
Source code of MM07MLVS
sy-msgid VL sy-msgty E sy-msgno 148
I have checked the process and through debugged I could confirm the
following information SAP is providing to all similar incidents reportedfor us:
Error message VL 148 is issued if in the confirmation control key used
in the purchase order, the fields for MRP-relevance (T163G-KZDIS),
GR relevance (T163G-WEREL) and GR assignment indicator (T163G-WEZUO)
are not set.
The correction of note 1602047 was necessary to avoid inconsistencies
(table EKES) in the purchase order. Without having the GR assignment
(T163G-WEZUO) set, there is no unique reference created between the
purchase order history (table EKBE) and the inbound delivery
confirmation (table EKES) at goods receipt which leads to a problem if
several inbound deliveries exist for the same purchase order.
If you set T163G-WEZUO to 'X', this assures that, for an inbound
delivery, the confirmation record (EKES) belonging to this inbound
delivery (EKES-VBELN) is also accurately updated at goods receipt.
How to solve the issue?
Use a confirmation control key with the GR assignment indicator set
and then create the inbound delivery with VL31N. If you want to be able
to create the inbound delivery with reference to a certain line item in
the PO, use transaction VL34.
If you still want to use transaction MIGO, there is the following
workaround:
- Create a purchase order without any confirmation control key
- Create a goods receipt (GR) in transaction MIGO with reference to this PO and post the GR to a non-HU-managed storage location
- Create a transfer posting with MIGO using movement type 311 to
transfer the goods from the non-HU-managed storage location to the
HU-managed storage location.
As the transfer posting is an additional step for the user, the whole
process could be automated using a partner storage location
(T001l-PARLG) for the GR which then triggers (through a modification)
the BAPI 'BAPI_GOODSMVT_CREATE' to create the transfer posting without
user interaction.
I hope to have satisfied you on the reason why it is now happening and
also I believe you can explain to business that it is a new behavior
necessary done from SAP side to avoid worse situations, we are aware of
potential dissatisfaction it might cause. SAP Support is always
available to clarify any issue.
Sorry for not having a more positive answer.
I hope it helps!
Leentje

Different delivery type for inbound delivery

Hi,
Somebody knows if it is possible to assign diferent delivery types for inbound delivery from differents document type of PO?
for example, delivery type EL for "NB" PO and delivery type "ZEL" for UB (Stock Transp. Order).
thanks
RZ

Dear,
Check: Different inbound delivery types from PO conf control keys
Regards,
Syed Hussain.

Message No delivery type defined for supplying plant BP01 and document type

Hi all,
I am trying to create a purchase order with a BP01 supplier and the BP02 division but I get the following error message No delivery type defined for supplying plant BP01 and document type.
When I create a PO with a BP02 supplier and the BP01 I do not get any message.
How can I fix it ?
Thanks
Regards
Pierre

1)Create one Customer for Supplying Plant Sales area and assign this Customer no with Receiving Plant in OLME---> PO -
> Set up STO -
> define Shipping Data for plants. and maintain the same sales area in your Supplying plant.
2) In OLME---> PO -
> Set up STO.....for your Document Type: UB and Suppying plant Combination assign Del. Type NL and Checking rule RP
3) In OLME---> PO -
> Set up STO...for your Supplying Plant and Receiving Plant combination Maintain Doc. Type : UB
Make sure you are maintaining Sales View for your Material at Supplying Plant.
4) Maintain Shipping point at, SPRO----> Logistics Execution -
> Shipping -
> Basic Shipping Functions -
> Shipping Point Determination for Plants.....there for your Loading group,Shipping Condition, Shipping Plant combination maintain Shipping plant..
Now Create STO in ME21N with Doc.type: UB at Receiving Plant.
Then Create Delivery in VL10B from Supplying Plant...
Then Do PGI in VL02N from supplying Plant.
Then do GR at Receiving Plant based on Outbound Delivery at Receiving Plant...

IDoc type "DELVRY03" for INBOUND delivery confirmation and Outbound Deliver

Similar Messages

Maybe you are looking for