Inbound Delivery changes DELVRY03.

Hi ,
Iam facing a problem in my inbound Delivery changes   interface.
Message Type: DESADV
Basic type:        DELVRY03 are using for the interface .
This interface is working fine for creation .
we are using the same interface for in bound delivery change also by the help of FM    IDOC_INPUT_DELVRY.
it is successfullu posted with a message " Delivery <no> changed.
But the quantity values iam changing is not reflecting .
I tried with E1EDL18-Qualifier as ORI as well as CHG.
Is there anything else to do...
please help
Thanks ,
Sarath P

hi,
Still issue is not solved.
the interface i created internally using the FM WS_DELIVERY_UPDATE_2 to update the delivery .
i changed the quantity , but its not reflectiong in vl33n .
Experts , please help
Sarath

Similar Messages

Inbound Delivery Change

Hi
i am having a requrement to change the Inbound Delivery .
Iam able to find the message type for Inbound Delivery creation ( ALE-IDOC {(Basic type: DELVRY03) Message Type: DESADV )
Please suggest the MESSAGE TYPE / BAPI for Inbound Delivery Change.
Thanks in advance,
Sar.

Hi ,
My req is to create an interface , which can accommodate Inbound Delivery Change.
Through interface all the Inbound Delivery changes in 4.7 needed to be brought to the 6.0
how can i make use of this , please help
thanks
Sar

Finding BAPI for inbound Delivery change(VL32N)

HI,
Plz help me For finding BAPI for inbound Delivery change(VL32N).
I have to pass delivery no as input parameter and should able to change shipment heder information
like Special processing indicator.
REGARDS,
Sunil Sahoo.

hi ,
there are three BAPI your requirment
1) BAPI_INB_DELIVERY_CONFIRM_DEC
2) BAPI_INB_DELIVERY_SAVEREPLICA
3) BAPI_INB_DELIVERY_CHANGE
but for requirment
The third BAPI
BAPI_INB_DELIVERY_CHANGE
will Sound promising. try this out
regards
Prashant

Trigger internal serial nos creation for inbound delivery using DELVRY03

Hi all,
I am working in ECC 6.0 I need to update serial nos in the inbound delivery. The internal serial nos. that will be generated by the system, I have to trap them for a given delivery and map it to a set of external serial nos.(length is 40 chars) and update in a Z table.
For changing the delivery, I am using idoc DELVRY03 (message SHPCON). Within the idoc I am not able to find any such field which will trigger the automatic creation of internal serial nos. In case of idoc MBGMCR03 (goods movement), there is a field E1BP2017_GM_ITEM_CREATE-SERIALNO_AUTO_NUMBERASSIGNMENT which when set to 'X', the internal serial nos are automatically generated and can be found in table SER03.
I want a similar thing for the DELVRY03 idoc. Can anyone help me on this?
If not possible through Idoc, then whats the other option?
My aim is to just get the internal serial nos created through delivery change activity.
Note - The serial no. profile cannot have the option of serial no. usage set to '04 - automatic' in SPRO as per the client's business process.
Thanks,
Shoma

Hi Shoma,
copy the FM which is assigned to your processcode and copy to ZFM and write your modifications on that ZFM.
It will resolves your problem.
Regards,
Venkat.

BAPI/FM Inbound delivery change

Hi All,
Problem- I am trying to change inbound delivery field wadat_ist(actual GR date)
I found FM: WS_DELIVERY_UPDATE which can help me do that.
However, for the change to be effective i need to select the field WABUC(Post good issue automatically) as the FM checks for that field, which does the goods receipt.
Is there a way in which I can change the actual GR date without doing a Goods receipt. If so, please let me know.
I also looked at BAPI_INBOUND_DELIVERY_CHANGE...apparently it does not have an option for field wadat_ist(i could have missed it, but so far I could not find it)
P.S: I am using 4.6C
Thanks in advance for all your help!!!

hi,
check this
BAPI_IBDLV_CREATE_FROM_OBDLV BAPI Inbound Delivery from Outbound Delivery
BAPI_INB_DELIVERY_CONFIRM_DEC BAPI for Inbound Delivery Confirmation from a Decentralized System
BAPI_INB_DELIVERY_SAVEREPLICA BAPI Function Module for Replication of Inbound Deliveries
BAPI_OUTB_DELIVERY_CONFIRM_DEC BAPI for Outbound Delivery Confirmation from a Decentralized System
BAPI_OUTB_DELIVERY_SAVEREPLICA BAPI Function Module for Replication of Outbound Deliveries

Inbound Delivery IDOC-DELVRY03; Right User Exit? WMTC1D01 IDOC for STOs??

Hi Experts,
The scenario is:
As soon as the user saves the DELIVERY in external_system, flat file is sent to Gentran, where its transfrred to IDOC and then, this IDOC is directed to SAP.
So, this Inbound_Delivery_IDOC- - DELVRY03 will be received by SAP system and updates the delivery related stuff in SAP system.
So, here, AT THIS POINT,
1)I need to capture this IDOC of Inbound_Delivery_IDOC - DELVRY03,
2) Need to check its(Inbound_Delivery_IDOC) MESSAGE CODE for TOA
3) If its TOA, I need to UPDATE the associated Stock Transfer Order/STO(record in LTAK, LTAP tables) stuff through IDOC of WMTCID01
so, let me know that,
1) Wht is the User Exit, I need to look, Which User Exit is correct? I mean, At Wht point I need to add my code in this whole process?
2) How to execute the UPDATED WMTC1D01 IDOC of Stock Transfer Order-STO?
thanq

no reply

EDI Inbound delivery DESADV delvry03

I'm waiting on a translator for the mapping the above to create inbound deliveries but while I wait I'd like to set up a few scenarios on our system. Does anyone have a mapping documnet I could have a look at? If so could you send it to the e-mail address below.
Thanks for your help, Mark
[email protected]

Hai Mark,
Check this mapping template for delvry03 ...
<b>http://www.sapgenie.com/sapgenie/docs/o856v4010_template.xls</b>
Hope it will surely help u...
Regards,
Sridhar

Packing Inbound Delivery

Hi ,
Can anyone help me changing the Inbound Delivery through Function Module. My Scenario is i have to pack the Inbound delivery ( Change )through Function Module. For this i'm using 'PROCESS_HU_INBOUND_DLVRY'. This is creating Handling Unit but not picking the Material.
thanks in advance,
anjani.

Hi,
There is small sample (of course you must adjust it according to your master data):
DATA: HEADERPROPOSAL LIKE BAPIHUHDRPROPOSAL,
      ITEMSPROPOSAL LIKE BAPIHUITMPROPOSAL OCCURS 0 WITH HEADER LINE,
      HUHEADER LIKE BAPIHUHEADER,
      HUKEY LIKE BAPIHUKEY-HU_EXID,
      RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE,
      HUITEM LIKE BAPIHUITEM OCCURS 0 WITH HEADER LINE.
HEADERPROPOSAL-PACK_MAT = '000000000000600001'.
ITEMSPROPOSAL-HU_ITEM_TYPE = 1.
ITEMSPROPOSAL-PACK_QTY = 5.
ITEMSPROPOSAL-BASE_UNIT_QTY = 'KG'.
ITEMSPROPOSAL-MATERIAL = '000000000000706602'.
ITEMSPROPOSAL-BATCH = '0000800468'.
ITEMSPROPOSAL-PLANT = '0000'.
ITEMSPROPOSAL-STGE_LOC = '0000'.
APPEND ITEMSPROPOSAL.
CALL FUNCTION 'BAPI_HU_CREATE'
EXPORTING
    HEADERPROPOSAL       = HEADERPROPOSAL
IMPORTING
    HUHEADER             = HUHEADER
    HUKEY                = HUKEY
TABLES
    ITEMSPROPOSAL        = ITEMSPROPOSAL
    RETURN               = RETURN
    HUITEM               = HUITEM.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
HUHEADER-PACK_MAT_OBJECT = '01'.
HUHEADER-PACK_MAT_OBJ_KEY = '0080002891'.
CALL FUNCTION 'BAPI_HU_CHANGE_HEADER'
EXPORTING
    HUKEY           = HUKEY
    HUCHANGED       = HUHEADER
IMPORTING
    HUHEADER        = HUHEADER
TABLES
    RETURN          = RETURN.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
DATA: LS_VBKOK_WA TYPE VBKOK,
      LT_PROT TYPE TABLE OF PROTT,
      LT_REHANG TYPE TABLE OF HUM_REHANG_HU,
      LT_REHANG_WA TYPE HUM_REHANG_HU.
LS_VBKOK_WA-VBELN = '0080002891'.
LS_VBKOK_WA-WABUC = 'X'.
LS_VBKOK_WA-VBELN_VL = '0080002891'.
LS_VBKOK_WA-VBTYP_VL = '7'.
LOOP AT HUITEM.
LT_REHANG_WA-VENUM = HUHEADER-HU_ID.
LT_REHANG_WA-VEPOS = HUITEM-HU_ITEM_NUMBER.
LT_REHANG_WA-RFBEL = '0080002891'.
LT_REHANG_WA-RFPOS = '000010'.
APPEND LT_REHANG_WA TO LT_REHANG.
ENDLOOP.
CALL FUNCTION 'WS_DELIVERY_UPDATE'
EXPORTING
    VBKOK_WA           = LS_VBKOK_WA
    SYNCHRON           = 'X'
    COMMIT             = 'X'
    DELIVERY           = '0080002891'
    NICHT_SPERREN      = space
TABLES
    PROT               = LT_PROT
    IT_HANDLING_UNITS = LT_REHANG.
Krzys

Issue with Message Type Triggering during Inbound Delivery Creation

Hi Experts,
Hi Experts,
Currently we are facing issue with message type triggering during inbound delivery creation:
In NACE transaction for Inbound delivery we have 3 custom output types:
Pricing Procedure Used is standard one -> E10001
Z140 Inbound Delivery Create (This should get triggered when IB delivery is created)
Z141 Inbound Delivery Change (This should get triggered when IB Delivery is changed)
Z142 Inbound Delivery Delete(This should get triggered when IB Delivery is deleted).
At present if i check delivery in VL33 -> Extras -> Delivery Output
Both Z140 and Z141 are being triggered during IB delivery creation. While it should be only Z140.
Could you please suggest that are we missing any configuration in SPRO or we need to create any custom routine (requirement) to handle this?
Thanks

Hi,
There is no fine-tuned control for inbound delivery messages as for Purchase order. Hence I guess to meet your above requirement, you have to go for a custom solution similar to the PO fine tune control settings.
Thanks,

New inbound delivery type creation???

Hi,
May I create a new inbound delivery type instead the standard EL?
If not, which enhancement can be used to change the item category ELN to another self-defined category during inbound delivery creation via VL31N?
Kindly please advise.
Thanks!

Hi
yes you can create a new Inbound delivery & change the Item category
Create new inboun delivery type in
SPRO-> IMG-> Logistics Execution-> Shipping-> Deliveries-> Define Delivery Types
Maintain the Combination of Item category & delivery type in
SPRO-> IMG-> Logistics Execution-> Shipping-> Deliveries->Define Item Category Determination in Deliveries
Thanks & Regards
Kishore

Inbound Delivery creation in ECC6.0 through IDoc (DELVRY03.DESADV)

Inbound Delivery creation in ECC6.0 through IDoc (DELVRY03.DESADV)
From SCM ICH system Supplier creates ASN on the WEBUI & sends it ECC 6.0 using XI.
This is Proxy (DespatchedDeliveryNotification) to IDOC (DELVRY03.DESAV) scenario
But at the receiver end i.e. ECC6.0 its giving me error at Tcode WE02 as action is not supported.
Can you suggest me how to tackle this issue.
Thanks in Advance.
Regards,
N>B.Shanmukha

hi,
>>>giving me error at Tcode WE02 as action is not supported.
there are many segments in delvry03 with a first field - action (like, delete, create, 001,002, etc)
check all of them as probably you're using one which is not supported
and this is the real cause of the error
you can check it like this:
open this IDOC in We19
then open action field and F4 and see if the one you use in the idoc is in F4
change the wrong one and it will work :for 100%
Regards,
Michal Krawczyk

Inbound Delivery DELVRY03 Segment E1EDT13

I am able to create an Inbound Delivery using the Basic IDoc type DELVRY03 with correct Delivery Date in Segment E1EDT13 qualifier '007'.
However I am not able to populate the correct Document Date (LIKP-BLDAT) with qualifier '015' Document Date? The Delivery creates but the Document Date is todays date. Basically nothing is happening with the date in this segment.
Is there something else needed to get the Document Date to post from the IDoc?
Thanks in advance,
Craig

Thank you again for your input!
See below for Function Module code that appears to call out this Segment and should be processing the different qualifiers. Include I56IDOVA (pertinent extract below) appears to have the qualifiers present but doesn't process? Is it your belief that we will need to make changes to the processing code to correctly populate the Document Date?
Inbound function module IDOC_INPUT_DESADV1
      WHEN 'E1EDT13'.
        s_dt13 = idoc_data-sdata.
        CASE s_dt13-qualf.
          WHEN e1edt13_qualf-lfdat.
            mv s_dt13-ntanf t_dlgn-lfdat.
            mv s_dt13-ntanz t_dlgn-lfuhr.
            PERFORM field_check USING s_dt13-ntanf 'NTANF'.
            PERFORM date_syntax_check USING s_dt13-ntanf.
            PERFORM date_syntax_check USING s_dt13-ntanf.
            PERFORM TIME_SYNTAX_CHECK USING S_DT13-NTANZ.   "n_947083
          WHEN OTHERS.
        ENDCASE.
Include I56IDOVA
deadlines on delivery header
CONSTANTS: BEGIN OF e1edt13_qualf,
             tddat      LIKE e1edt13-qualf   VALUE '001', "shipm.plang.
             lddat      LIKE e1edt13-qualf   VALUE '003', "loading
             wadat      LIKE e1edt13-qualf   VALUE '006', "goods issue
             lfdat      LIKE e1edt13-qualf   VALUE '007', "delivery
             ankft      LIKE e1edt13-qualf   VALUE '008', "arrival
             abfrt      LIKE e1edt13-qualf   VALUE '009', "departure
             kodat      LIKE e1edt13-qualf   VALUE '010', "picking
<<< START_OF_INSERTION_HP_204779 >>>
             bldat      LIKE e1edt13-qualf   VALUE '015', "doc date
<<< END_OF_INSERTION_HP_204779 >>>
             frei       LIKE e1edt13-qualf   VALUE '499', "others
           END OF   e1edt13_qualf.

Idoc delvry03 - Create inbound delivery without ref. to purchase order?

Hello,
we want to use LES with handling-unit management. For this we have to create inbound-deliverys without any reference to an purchase-order. Manually we can do this via TA MB1C with movement type 501 for a handling-unit storage location. In this case MB1C creates an inbound-delivery with delivery-type "HID". Then we can pack handling-units with TA VL32N. Now i will do this with idoc desadv/delvry03 but the FM idoc_input_desadv1 checks the existence of an purchase order so we cannot even change an existing delivery. Has anyone done this before or any idea to do this?
regards
Andreas

Hi Andreas,
I have a similar requirement. Did you get any solution for the same?
Himanshu

Change in PO Qty. after Inbound Delivery.

Hi,
Suppose against a Purchase Order an inbound delivery of 100 pc. is created(PO Order Qty. is also 100).
Once a delivery is created,then Iam change the PO qty. from 100 to 80(System only throws an info message ME545,which I tried to convert it into error,but still it throws an info.).
Why system is allowing me to change the PO qty?Kindly advise.

system will allow changes for all PO qty untill and unless the item is bloced or deletion indicator is set. the system will not stop changes to qty even if you recieve full qty of material.
the only way to stop is to make use os user exit as prescribed by Charlie
vikrama

Change inbound delivery using /SPE/IDOC_INPUT_DESADV1

Hello -
We are creating an inbound delivery using the idoc function module /SPE/IDOC_INPUT_DESADV1. I have need to be able to change an existing delivery via idoc processing, so we are populating and mapping an E1EDL18 segment with the qualifier 'CHG'. However, in /SPE/IDOC_INPUT_DESADV1, it does not appear to handle CHG. I have debugged down into the code and in method PARSE_AND_HANDLE_IDOC_DELVRY03, when the segment is E1EDL18, there is a case statement that looks at the qualifier, and CHG is not dealt with.
Any ideas how to handle this? Or is this a legitimate bug I should report to SAP?
Thanks for any help!
Sharon McClure

Sharon McClure wrote:
Or is this a legitimate bug I should report to SAP?
Hard to say. Why not just report it? The worst they can do is say it's a consulting issue.
Rob

Inbound Delivery changes DELVRY03.

Similar Messages

Maybe you are looking for