Dates/Events in Inbound Delivery

Hi! Does anyone know whether it is at all possible to use the Dates function in the Inbound Delivery document? I went to the tab but the Add button is greyed out.
Thanks!
SF

Hi SF,
Actually there is no functionality of scheduling in connection with the inbound delivery . The reason is we dont have any information regarding loading point of a supplier, transit time to a goods receiving point or duration of putaway.
Due to the above reasons, there is no use of dates/events in the inbound delivery.
Regards,
ALV Ramana

Similar Messages

How to change data in an inbound delivery

Hi,
I want to change the following data in an Inbound delivery:
Challan No (LIKP-LIFEX, LIKP-VERUR)
Date (LIKP-LFDAT, LIKP-ERDAT)
Quantity (LFIMG)
I have gone through the thread
how to change delivery date (LFDAT) in a inbound delivery
But still, it says only about changing the date.
Please provide solution so as to change Challan No and Quantity.

LIFEX is in HEADER_DATA-EXTDELV_NO
If you really want to get the any other field in LIKP, you can use the BADI SMOD_V50B0001 method EXIT_SAPLV50I_009.
You will need to put your additional fields in the EXTENSION1. Then you can move them to the correct fields in the tables.

Update Delivery date programatically for inbound delivery

Hi all,
I need to update the delivery date in the inbound delivery programatically...How cna i do that?any FM available?
The field to be updated is LIKP-LFDAT.
Thanks.

Check WS_DELIVERY_UPDATE , BAPI_INB_DELIVERY_SAVEREPLICA
ALso check how to change delivery date (LFDAT) in a inbound delivery

Dates on the inbound delivery header

Hi Gurus,
Can anybody please explain me what is the use of dates tab on the inbound delivery header. What is it used for? How can we activate/populate this. We are looking for the ASN functionality to be turned on. Any help is greatly appreciated
Thanks
Anusha

Picking = planned time to start picking
Trans. Planning = planned time to start processing shipment
Loading = planned time for loading
Planned GI = planned goods issue date
Delivery Date = planned date to deliver
The dates can be used for planning various warehouse activities and they should be populated by the system when the delivery is released based on entries maintained in the sales order.
The dates can all be the same or different depending on your needs. They are used for various things (depending on your config) we use the planned goods issue date to show the date we want to the delivery to ship and we us the transportation planning date (same as planned goods issue) to calculate transit time for revenue recognition.
basically delivery processing, shipping scheduling dates that can be used or not depending on your needs

GR Date Control In Inbound Delivery

Hi Mentors
I have one query
As on today in my sap, when i am doing the MIGO system will check Latest GR Date ( in po - item details-Delivery) and compare with date and post the MIGO.
If date is over the Gr making date system through the message " Gr Date Expaired.
But, my client want that control in Inbound delivery time. i have check standard settings and user exiss also.
if any standard settings for this pls tell me.
Rewarded for right answer.
Thanks in advance
Regards
Laxman

Hi All
Pls go thru my thread and suggest me what to do ?
Laxman

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

PO delivery date changed according to delivery date on the inbound delivery

Hi!
Initial PO date is changed according to the inbound delivery date when I create inbound delivery.
For example, initial PO has order qty. 1000 and delivery date 8/10/07.
And then I created inbound delivery for that PO with qty. 500 and changed delivery date to 8/5/07 on the inbodund delivery. Then when I check PO again, PO line item delivery date was changed to 8/5/07 which is
inbound delivery date. I think remaining 500 should have the same
delivery date originally assigned unless we change manually.
If somebody have experience, please let me know.
Thank you!

Dear Wan Lee,
I think you also need to check for your Configuration setting for confirmation:IMGMM> Purchasing-->Confirmation.
Regards,
w1n

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.

Function Module to Fetch data of Vendor for Inbound Delivery at runtime

Hi All,
I am new to EWM. I am using BADI /SCWM/EX_DLV_DET_PROCTYPE method CHANGE_PROCTYPE to change process type of the inbound delivery as per some logic from a custom table. However the parameter Vendor is not available in IS_ITEM during inbound delivery creation. Vendor is one of the key fields in my table.
Does anyone know any solution/function modules to fetch vendor data for the inbound delivery at runtime. I know the database tables to fetch vendor but this works only once the inbound delivery is saved.
Thanks and Regards,
Vanessa Noronha

Hi All,
I am new to EWM. I am using BADI /SCWM/EX_DLV_DET_PROCTYPE method CHANGE_PROCTYPE to change process type of the inbound delivery as per some logic from a custom table. However the parameter Vendor is not available in IS_ITEM during inbound delivery creation. Vendor is one of the key fields in my table.
Does anyone know any solution/function modules to fetch vendor data for the inbound delivery at runtime. I know the database tables to fetch vendor but this works only once the inbound delivery is saved.
Thanks and Regards,
Vanessa Noronha

Inbound Delivery (DESADV): How to transmit SLED/BBD and Manufacture Date?

Hello
We have another challenging task to solve. Here is the scenario (SAP Release ERP 6.0):
One Lindt company (supplier) sends an outbound DESADV IDoc to another Lindt company (Purchaser). Here the inbound DESADV should create an inbound delivery. Finally, the inbound delivery is replicated to the external WHS partner who does the Goods Receipt against this inbound delivery.
The outbound DESADV contains all logistical data including SSCC. In particular, the batches have a manufacture date (LIPS-HSDAT) and a SLED/BBD (LIPS-VFDAT).
SLED = Shelf Life Expiration Date
BBD = Best-Before Date
In the outbound DESADV the SLED/BBD is mapped by default into segment E1EDL24/VFDAT. For the manufacture date we implemented an user-exit.
How does the inbound delivery look like? The batch number appears as "Vendor batch". The SLED/BBD does NOT show up even though the inbound DESADV contains the date in E1EDL24/VFDAT. This inbound DESADV did NOT contain any controlling segment E1EDL19. Adding this segment (QUALF = 'VDT' = Shelf Life Expiration or Best-Before Date) had no effect.
Here is my assumption why the SLED/BBD does not show up in the inbound delivery created by the inbound DESADV:
Because we do not yet have the "real" batch (just the "Vendor batch") the system ignores any SLED/BBD. As soon as the external WHS partner sends the GoodsReceipt message (as inbound WHSCON ) the inbound delivery is updated with the "real" batch as well as the SLED/BBD.
QUESTIONS:
(1) Why does the SLED/BBD not show up in the inbound delivery created by an inbound DESADV?
(2) Do we need another user-exit to map the manufacture date into the inbound delivery?
Once again thank you for sharing your time and expertise with us.
Regards
   Uwe

Apply SAP Note
Note 1576788 - Transfer of exp. date
(IDOC_INPUT_DESADV1) to inb. delivery
Here are the correction instructions for your reference:
=========================================
FORM DESADV_IDOC_PARSE
Delta001Context Block
        IF NOT t_dlgn-vbelv IS INITIAL.
          t_dlgn-posnv = s_dl24-posex.
        ENDIF.
Delete Block
        mv s_dl24-brgew t_dlgn-brgew.
Insert Block
        mv s_dl24-vfdat t_dlgn-vfdat.                         "n_1576788
        mv s_dl24-brgew t_dlgn-brgew.
Have fun!
- Joemil

Inbound Delivery for Schedule Lines of future date

We have a requirement where in we want to disallow inbound creation for scheduling agreements for schedule lines of the future. For example if we have the following schedule line for a scheduling agreement
       Month        Quantity
M    01.2010     100
M    02.2010     200
M    03.2010     150
Currently the system is allowing inbound delivery creation of quantity = 450 (100 + 200 + 150) in the month of February, 2010.
But I want that the system should allow inbound delivery creation in February, 2010 for quantity 300 only (100 + 200). Please let me know how we can do so in the system.
Regards,
Pratima.

Hi Rami ,
Maintain different schedule lines in PO - Item Details - Delviery Schedule tab.
This would allow only those qty that is due on that date when creating inbound delivery.
Regards
Ramesh Ch

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.

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

Dates/Events in Inbound Delivery

Similar Messages

Maybe you are looking for