Proposed delivery quantity in inbound delivery vs purchase schedule line

Hello all
I have got a doubt when creating inbound delivery for an item of purchase schedule line. I want to know how to get the proposed delivery quantity equal to the quantity of all schedule lines until today.
For example I have got 4 schedule lines for a material and today is 28.10.2011
20.10.2011 11ud
28.10.2011 13ud
03.11.2011 17ud
05.11.2011 15ud
when I execute VL31N with date = 28.10.2011, I want to proposed delivery quantity = 11+13 = 24ud.
However, what I got is always the total quantity of all pending schedule lines = 111317+15=56ud.
Do you know how can I achieve my propose?
thank you in advance

Hi Alan
Thank you for your reply.
In some cases (depending on vendor) we are using vendor ASN by EDI. In other cases (when there is no EDI conection with vendor) we use manually VL31N. So in these cases we need a proposed quantity by system in order to know if the quantity that we receive is coherent. Maybe we will try to implement the inbound delivery user exit.
Thanks again!

Similar Messages

Total and pending quantity of inbound delivery

From which table i will find total and pending quantity of inbound delivery number.
Which table and field name???

Dear,
Find out report using T'Code MR11, you will get all required fields (this is standard report)
Regards,
A. Wankhede

Delivery Date in inbound delivery doc not accurate

Dear all,
I have a question with regards to the wrong delivery date appear in our inbound delivery.
Our inbound delivery is created via a message output in the outbound delivery of a standard SAP cross company stock transport order. The delivery date in the inbound delivery is not correct from a business point of view.
+The correct delivery date in the inbound delivery document should be [the Actual GI date field in the outbound delivery] + [transport time (i.e. route field) in the outbound delivery].+
Either way (i.e. the Actual GI date field is later/earlier than the planned GI in the outbound delivery), the delivery date in the inbound delivery is also wrong.
Do you have any idea? We have tried to change the inbound delivery type EL by setting a flag (i.e. X) in the rescheduling (TVLK-NEUTE), and it still doesnu2019t work.
Please help.
Thanks.
Tuff

implements SAP Note 1316614

Delivery Date in Inbound delivery document not correct

Dear all,
I have a question with regards to the wrong delivery date appear in our inbound delivery.
Our inbound delivery is created via EDI output in the outbound delivery of a standard SAP cross company stock transport order. The delivery date in the inbound delivery is not correct from a business point of view.
+The correct delivery date in the inbound delivery document should be [the Actual GI date field in the outbound delivery] + [transport time (i.e. route field) in the outbound delivery].+
Either way (i.e. the Actual GI date field is later/earlier than the planned GI in the outbound delivery), the delivery date in the inbound delivery is also wrong.
Do you have any idea? We have tried to change the inbound delivery type EL by setting a flag (i.e. X) in the rescheduling (TVLK-NEUTE), and it still doesnu2019t work.
Please help.
Thanks.
Tuff

Does anyone know this problem?
appreciate some feedback.

Delivery date in inbound delivery

Hi
WE have the following scenario
WE create a inter-company STO. Outbound delivery is created against STO and then we do PGI.
Suppose planned delivery dt of OBD is 10-jan-2011 and actual PGI is done on 18-jan-2011.
After PGI we create inbuound delivery in receiving plant. In inbound delivery, we are getting delivery date as planned delivery date of outbound delivery i.e. 10-jan-2011. But we want actual PGI date i.e. 18-jan-2011 in delivery date of inbound delivery.
is it possible? Please suggest how can we do this?

Hi,
I think the issue is not related to inbound delivery. Because you probably would not only have delivery date at inbound delivery equal to PGI date. Instead it should be PGI+transit time. Hence, I believe what you should focus is to get planned delivery date corrected at your outbound delivery during PGI.
I do not think standard config supports rescheduling of planned dates at delivery during PGI (even if you setup rescheduling type 'A' at your delivery type). But you can always call SD_SCHEDULING FMs to get new delivery dates and get those posted from outbound to inbound deliveries.
Regards,
Dominik Modrzejewski

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.

Detemine open GR quantity in inbound delivery

Hi gurus,
I have an inbound delivery no with me. Suppose delivery quantity is 50. Now I have done GR through MIGO for 10 quantities against that inbound delivery. So at present open GR quantity is 40.
Now my question is how to calculate the open GR quantity against a inbound delivery because I have to show that in a custom report? Need that a little bit technically...
Secondly, how to understand that GR has been done completely against a inbound delivery?

Use tables EKES and EKBE and you need to apply some logic. contact abaper.

Update GR quantity in Inbound delivery using 'BAPI_INB_DELIVERY_CHANGE'

Hello SDNs,
I have a requirement to update quantity delivered post GR in the Inbound delivery. I'm using 'BAPI_INB_DELIVERY_CHANGE' to do the updation in program. The database is not updated with new quantity.
BAPI returns error message in "Return" table with ID VLBAPI . I'm unable to detect where the problem is.
Below is my code. Please help me resolve it.
loop at it_final.
    CLEAR g_delivery.
    g_delivery = it_final-text(10).
*   g_delivery = '0180000221'.
    g_del_item = it_final-text+10(6).
*    g_del_item = '10'.
    g_material = it_final-text+16(18).
    g_dlv_qty = it_final-text+34(13).
    select single * from lips into wa_lips
        where vbeln = g_delivery
          and posnr = g_del_item
          and matnr = g_material.
    if sy-subrc eq 0.
      wa_lips-lfimg = g_dlv_qty.
      modify lips from wa_lips.
      check sy-subrc eq 0.
    endif.
    CLEAR gt_header_data.
    REFRESH gt_header_data.
    gt_header_data-deliv_numb = g_delivery.
    gt_header_data-volumeunit = wa_lips-voleh.
    APPEND gt_header_data.
    CLEAR gt_header_ctrl.
    REFRESH gt_header_ctrl.
    gt_header_ctrl-deliv_numb = g_delivery.
*    gt_header_ctrl-no_lock = 'Y'.
    APPEND gt_header_ctrl.
    clear gt_tech_ctrl.
    refresh gt_tech_ctrl.
    gt_tech_ctrl-UPD_IND = 'X'.
    gt_tech_ctrl-DLV_TYPE = 'EL'.
    append gt_tech_ctrl.
    CLEAR gt_data.
    REFRESH gt_data.
    gt_data-deliv_numb = g_delivery.
    gt_data-deliv_item = g_del_item.
    gt_data-material = g_material.
    gt_data-dlv_qty = wa_lips-lfimg.
    gt_data-sales_unit = wa_lips-vrkme.
    gt_data-base_uom = wa_lips-meins.
    gt_data-dlv_qty_imunit = g_dlv_qty.
*   gt_data-base_uom_iso =
*    gt_data-
    APPEND gt_data.
    REFRESH gt_ctrl.
    gt_ctrl-deliv_numb = g_delivery.
    gt_ctrl-deliv_item = g_del_item.
* gt_ctrl-del_item   = ' '.
    gt_ctrl-CHG_DELQTY = 'X'.
    APPEND gt_ctrl.
    CALL FUNCTION 'BAPI_INB_DELIVERY_CHANGE'
      EXPORTING
        HEADER_DATA                = gt_header_data
        HEADER_CONTROL             = gt_header_ctrl
        DELIVERY                   = g_delivery
        TECHN_CONTROL              = gt_tech_ctrl
      TABLES
*   HEADER_PARTNER             =
*   HEADER_PARTNER_ADDR        =
*   HEADER_DEADLINES           =
       ITEM_DATA                  = gt_data
      ITEM_CONTROL               = gt_ctrl
*   ITEM_SERIAL_NO             =
*   EXTENSION1                 =
*   EXTENSION2                 =
        RETURN                     = return
*   TOKENREFERENCE             =
*   HANDLING_UNIT_HEADER       =
*   HANDLING_UNIT_ITEM         =
*   PARTIAL_GR_OBJECTS         =
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
      EXPORTING
        WAIT = ' '.
endloop.
Thanks
Shruti

Please check the inbound delivery you are trying to delete is not having goods receipt status as 'completed' OR not having HANDLING UNITS assigned to it.
In any of the above case, please reverse the goods receipt first, then unassign the handling units and then try to delete the inbound delivery. In my opinion, there should be no need to change the qty to 0 and just delete the inbound delivery should work.
In case you still encounter an error, try deleting the delivery using VL32n and you should get a clear error/problem for your case.

Rounding for Quantity in Inbound delivery

Hi all,
Is it possible to round up/down the quantity in the Inbound delivery. If yes, please let me know the SPRO path / Enhacement to meet this requirement.
thanks & regards
Chaitanya Rayaprolu

can you explain this requirement with an example?
you can usually round required quantities e.g. requisition quantity and PO quantity, but not physical quantities

Update Delivery Qty of Inbound Delivery using BAPI_INB_DELIVERY_CHANGE

Hi Experts,
I'm trying to use BAPI_INB_DELIVERY_CHANGE to update the delivery quantity of a line item in an Inbound Delivery. However, I keep on getting this error:
Type: E
ID: VLBAPI
Number: 004
Text: Error in document &1 item &2 (quantity consistency check)
Below is my test program. Any input will be much appreciated.
REPORT ztest.
DATA: deadlines LIKE bapidlvdeadln OCCURS 0.
DATA: wa_deadlines LIKE bapidlvdeadln.
DATA: header_data_t LIKE bapiibdlvhdrchg OCCURS 0.
DATA: wa_header_data LIKE bapiibdlvhdrchg.
DATA: header_control_t LIKE bapiibdlvhdrctrlchg OCCURS 0.
DATA: wa_header_control LIKE bapiibdlvhdrctrlchg.
DATA: item_data LIKE bapiibdlvitemchg OCCURS 0.
DATA: wa_item_data LIKE bapiibdlvitemchg.
DATA: item_control LIKE bapiibdlvitemctrlchg OCCURS 0.
DATA: wa_item_control LIKE bapiibdlvitemctrlchg.
DATA: header_data_t_con LIKE bapiibdlvhdrcon OCCURS 0.
DATA: wa_header_data_con LIKE bapiibdlvhdrcon.
DATA: header_control_t_con LIKE bapiibdlvhdrctrlcon OCCURS 0.
DATA: wa_header_control_con LIKE bapiibdlvhdrctrlcon.
DATA: item_data_con LIKE bapiibdlvitemcon OCCURS 0.
DATA: wa_item_data_con LIKE bapiibdlvitemcon.
DATA: item_control_con LIKE bapiibdlvitemctrlcon OCCURS 0.
DATA: wa_item_control_con LIKE bapiibdlvitemctrlcon.
DATA: return TYPE STANDARD TABLE OF bapiret2.
CLEAR: wa_header_data, wa_header_control.
wa_header_data-deliv_numb = '0180000545'.
wa_header_data-gross_wt = '3001.000'.
*wa_header_data-NET_WEIGHT = '3001.000'.
wa_header_data-unit_of_wt = 'KG'.
wa_header_data-volume = '1500.5'.
wa_header_data-volumeunit = 'M3'.
APPEND wa_header_data TO header_data_t.
wa_header_control-deliv_numb = '0180000545'.
wa_header_control-NET_WT_FLG = 'X'.
wa_header_control-volume_flg = 'X'.
wa_header_control-gross_wt_flg = 'X'.
*wa_HEADER_CONTROL-DELIV_DATE_FLG = 'X'.
APPEND wa_header_control TO header_control_t.
CLEAR: wa_item_data.
wa_item_data-deliv_numb = '0180000545'.
wa_item_data-deliv_item = '000020'.
wa_item_data-dlv_qty = '3000'.
wa_item_data-dlv_qty_imunit = '3000'.
wa_item_data-sales_unit = 'KG'.
wa_item_data-sales_unit_iso = 'KG'.
wa_item_data-base_uom = 'KG'.
wa_item_data-base_uom_iso = 'KG'.
wa_item_data-gross_wt = '3000'.
wa_item_data-unit_of_wt = 'KG'.
wa_item_data-volume = '1500'.
wa_item_data-volumeunit = 'M3'.
APPEND wa_item_data TO item_data.
CLEAR: wa_item_control.
wa_item_control-deliv_numb = '0180000545'.
wa_item_control-deliv_item = '000020'.
wa_item_control-chg_delqty = 'X'.
wa_item_control-VOLUME_FLG = 'X'.
wa_item_control-NET_WT_FLG = 'X'.
wa_item_control-GROSS_WT_FLG = 'X'.
APPEND wa_item_control TO item_control.
CALL FUNCTION 'BAPI_INB_DELIVERY_CHANGE'
EXPORTING
header_data = wa_header_data
header_control = wa_header_control
delivery = '0180000545'
* TECHN_CONTROL =
TABLES
* HEADER_PARTNER =
* HEADER_PARTNER_ADDR =
* HEADER_DEADLINES = deadlines
item_data = item_data
item_control = item_control
* ITEM_SERIAL_NO =
* EXTENSION1 =
* EXTENSION2 =
return = return
* TOKENREFERENCE =
* HANDLING_UNIT_HEADER =
* HANDLING_UNIT_ITEM =
* PARTIAL_GR_OBJECTS =
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.

Hi,
Pls try to use the other structure
ORDER_SCHEDULES_INX type BAPISCHDLX bcoz it is used to update the required field.
Now for the date field add the required days to set it as future date.
ex:
l_date = l_date + 12. // it will be set to future or requred date.
Reward if helpful.
Regards
Chandralekha

VL32N Zero Receiving or Setting Delivery Complete on Inbound Delivery

ERP Retail Scenario:
We receive ASN from vendor creating inbound delivery; however, some items are not received so we enter zero quantity for them into VL32N
Zero quantity does not post to article document and invoice verification process (GR-IV)cannot be done.
1) Can delivery complete flag be enabled in VL32N (currently grayed out) so document flow proceeds as in MB01? We do not want to use MB transactions for EDI process.
OR
2) Can GR-IV process be set to ignore zero received items? Currently if we remove the flag from the PO, it works but we want to do it without removing this flag.
Thanks in advance,

Hi ,
You can Crete VL32N without the available Quantity , I.e You can delete the Zeroed Qnty and Create a new Inbound for the rest . Hope it works.

Delivery quantity changed while delivery was being picked .

Hi Friends .
I have a big problem, because the delivery quantity changes while the delivery was being picked.
This is the positively the 3rd time that we have seen this, possibly the 4th, recently.
Delivery was created this morning for 800pc. Batch determination was telling the picker to pick from perticular storage location SLOC 112. (all 800pc) (25pc =1 pallet)
The picker knew that he was picking 32 pallets from that row.
After he picked 32 pallets, the system was telling him that he needed to pick 2 more pallets.
At that point, I saw delivery .The quantity in the delivery had, at this point, increased to 850.
Delivery shows that 32 pallets that had been picked up to this point.
again it is calling to pick 2 more pallets.
at this point of time delivery is for 850 (not the original 800)
I have not changed the quantity in delivery or in order . how come delivery quantity has changed while materials are being picked .
Kindly I request your speedy reply as it's priority ticket .
Thanks in advance .
Jayapala S.h

Hi jayapala
The delivery qty can change while you pick the quantity if the stock is less than the stock that is to be actually you are going to deliver. As the stock is changing , check the stock in MMBE for that material.
Example :
Say you have created a sales order for 100pcs but when you are doing delivery material is taking only 75pcs because there are only 75pcs of stock in the storage location
Regards
Srinath

PO delivery date vs Inbound delivery date

Hi,
I'm using message number M7-254 and set it as Error message. When I do GR w/ ref to inbound delivery the message M7-254 still considers/reads the PO del date instead of inbound del date during GR. Can it be modified to read the del date from inbound when there's inbound del created for the PO?
Or if not, can you advise another system message that would best suit our customer's requirement where system blocks GR if posting date not equal inbound delivery date?
Thanks in advance.

Hi Marianne,
A quick thought:
Use the BADI - ME_PROCESS_PO_CUST & the method - PROCESS_SCHEDULE to copy the delivery date as per your inbound document to the field - Latest GR Date in Delivery tab of the Item details section.
Then in OMCQ flag the message M7 163 message as E. This would ensure that the system will not allow GR to be done after this date.
Hope the above helps.
Regards,
Vivek

Updating delivery quantity in outbound delivery.

Hi,
I have to update the delivery quantity field of an outbound delivery from the quantity that is coming in through an idoc.Is there any BAPI to do the the updation? Also please explain the parameters which need to be passed in the BAPI.
I tried using a BDC recording but it gave an error that the article is locked.
Its urgently required.
Thanks,
Sandeep.

Hi,
Here are the some useful links.
BAPI to create delivery
Delivery
BAPI Outbound delivery
Please go through them
Regards,
Rama.Pammi

Delivery Date needs to be changed on Schedule lines

Hi All-
I am using BAPI_SALESORDER_CHANGE, to update the delivery date on the schedule lines...If I have 2 lines of schedule, needs to be updated the second one ETENR '0002'...
Bapi returns message that successfully processed, when I go back and look at Sales order, I don't se any changes on schedule line..
I am pssing into BAPI, sales doc and schedule line with the delivery date and the flag 'U'..and also I am using BAPI commit...
But, let me know if I am missing something and also let me know is it possible to change schedule delivery date or not?
Thanks,
Sony

Hi
Please follow this process.
Only specify fields that should be changed
Select these fields by entering an X in the checkboxes
Enter a U in the UPDATEFLAG field
Always specify key fields when changing the data, including in the checkboxes
The configuration is an exception here. If this needs to be changed, you need to complete it again fully.
Maintain quantities and dates in the schedule line data.
1. Minimum entry:
You must enter the order number in the SALESDOCUMENT structure.
You must always enter key fields for changes.
You must always specify the update indicator in the ORDER_HEADER_INX.
2. Commit control:
The BAPI does not run a database Commit, which means that the application must trigger the Commit so that the changes are read to the database. To do this, use the BAPI_TRANSACTION_COMMIT BAPI.

Proposed delivery quantity in inbound delivery vs purchase schedule line

Similar Messages

Maybe you are looking for