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

Similar Messages

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.

PO Confirmation Date (OA) & Inbound Delivery Date Report

Dear All,
Please let me know SAP Standard Report
PO Confirmation Date (OA) & Inbound Delivery Date Report
Regards
Amey

Hi,
I guess ME2A will give u unconfirmed orders that require a confirmation, but have not yet been confirmed according to the dates configured for your monitoring period. First, ensure that you have such an order
Also, ensure that your confirmation control (OMGZ) has BOTH a value in Monitoring period AND Reference date.
Pls chk note for more information. https://service.sap.com/sap/support/notes/500502
BR,
Krishna

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.

Production date in inbound delivery in batch split

Hi,
I have a issue with production date update in inbound delivery.
I have created a inbound delivery for 10 PC. The inbound delivery has only one line item and there are no batch details on it. As soon as the inbound delivery is created a message is sent to the 3PL . Once the 3PL receives the goods from vendor he send us a message with the batch details. Say the 3PL has received multiple batches from the vendor. So he send us back an SHPCON message with multiple batch details. That is batch A with QTY 6 and batch B with QTY 4. He also send us the production date for each batch via the shpcon idoc. say batch A has production date as 10.02.2011 and batch B has production date as 21.03.2011.
The IDOC is created successfully in our system and the inbound delivery is also updated correctly with the batch split details with correct QTY. That is line item 10 has batch split line items 900001 with batch as A and QTY as 6 and line item 900002 with batch as B and QTY as 4. The issue is only with updation of date of production for each of the above batch. Both batch A & B are updated with date of production as 21.03.2011. Instead of batch A being updated with date of production as 10.02.2011 it is updated with the batch B date of production. I checked in the idoc. In the idoc each batch has correct production date. only when updating the inbound delivery it has updated wrongly.. Has any one come across similar kind of situation. ? How did u manage it?
Ram

I found out the issue and the approriate changes has been made in the message handling

Actual GR Date in Inbound Delivery takes current Date

Hello Everybody,
The Output SPED gets issued after PGI from the Outbound in an Intercompany, it generates an Inbound automatically.
Problem: On the Inbound the field "Actual GR Date" gets populated with the same date as when PGI occurs. The PGI occurs in the US Plant while the PGR is supposed to occur in Europe. The Route Transit Time is 30 days.
Example: If the PGI Date is today, 18th May the system populates the Inbound Delivery field "Actual GR Date" as 18th May.
Research into Causes:
It appears the system is not adding the Route Transit Time. We used the "New Route Determination Time" the the value "A" for the Inbound as well as the Outbound and we do not maintain entries in Table TROAL. Yet, the Inbound still populates with the PGI Date from the Outbound.
Business Impact:
The ATP in Europe considers Stock In-Transit for real-time updates. So, this Inbound gets considered for ATP in Europe starting from today's date, 18th May 2011; so Europe will start promising their customers that these goods will be available from today; however, in reality the products will be available in Europe only after 30 days. This is the impact of the field "Actual GR Date" on the Inbound Delivery.
Thanks,
SR

Check the SPED functional module how the atcual date is passing.Check with technical team if they can insert alogic the actual date should be after PGI date +30 days as the delay required to reach the material.If you are not able to insert the logic then stop passing the actual GR date in GR.I think it is possible.

GurtVLO6if will not show PGR Date in inbound delivery

hi gurus,
Pls provide me the flow on how to link the inbound delivery number with the material document number, as I need to get the material doc number based on that delivery number and then I need to get the receipt date i.e. document date or posting date from the material document master tables and fill in the enhanced structure field that I added for the goods receipt date in standard structure,, for this purpose and at last inside the user exit to fill values for report vl06if.
Regards
NNeeti

hi nneti,
put thevariant parameter and check with material master

VLO6if will not show PGR Date in inbound delivery

hi Gurus,
VL06IF will not show the Post good receipt date of an inbound delivery,
need this date inserted in the report.last column good recepit does not show any dates
showing last column empty
please check
thanks,
Joan

Hi,
Check Note 128150 - VL06: Designing your own display variants. It explains how to do with enhancement V50Q0001.
I hope this helps you
Regards,
Eduardo

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

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!

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.

Need Fm/BAPI to change Actual GR date(WADAT_IST_LA) in inbound delivery

Hi ,
Need a function module/BAPi to change the Actual Goods Receipt date for inbound delivery . Any suggestion would be appreciated . Have tried with WS_DELIVERY_UPDATE and BAPI_INB_DELIVERY_CHANGE . Am I missing something here ?
Regds,
Sanjeev

Hello Sanjeev,
Need a function module/BAPi to change the Actual Goods Receipt
date for inbound delivery . Any suggestion would be appreciated .
Have tried with WS_DELIVERY_UPDATE and BAPI_INB_DELIVERY_CHANGE .
Am I missing something here ?
I am not a ABAP expert but may be upon calling BAPI_TRANSACTION_COMMIT, try using UPDATE command to insert the Actual GR date. Please explore around this pointer and post an update on this thread.
Regards,
Sarthak

Delivery date field grey in inbound delivery not editable

Hi,
Can any one tell me how to edit delivery date in inbound delivery when we are in change mode.
Delivery date field is editable in (ECD) where as grey in ECQ & ECP.
we creating inbound delivery through idoc from outbound deliveri.
How can we chane the field that was in Grey mode ?

i found the answer on my own

PO delivery date vs Inbound delivery date

Similar Messages

Maybe you are looking for