Loading weight information is missing in Inbound Delivery

Hi,
I have a problem in one of my inbound delivery where I canu2019t able to view the loading weight information. (Ie, loading weight field is blank).
Can any body tell me what has gone wrong and how to rectify the same?
Awaiting for your replies.
Cheers,
Kumar.S

Hi,
Where to check those details,
Please elobrate.
Cheers,
Kumar.S

Similar Messages

Storage location missing in Inbound delivery

Hi ,
When I am getting the ASN or confirmation for my purchase order.
automatically Inbound delivery is getting created.
But here the problem is missing the storage location in inbound delivery.
I maintained the storage location determination (with situation) setup.
could you please help me.

The entry in OMB2 indicates that automatic creation of storage location data in the material master record at the time of the first goods receipt is allowed.
As well the storage location data is only created automatically if the quantity is posted to the "normal" storage location stock. If you have goods movements to special stock (for example, to sales order stock), the data is not created.
To my knowledge the PO generally does not have storage locations,while creating inbound delivery (manually or automatically) storage locations are copied from the material master. So, also check what S.loc. your material master has for the materials you are creating inbound deliveries.
Regards,
PATHIK

Inbound Delivery Notification Document is missing EWM

Dear Experts,
Inbound Delivery document is created successfully in ECC, Prior to that PO is created in ECC which is replicated in SCM due to active integration model, based on the PO inbound delivery document is created, but it is not replicated automatically in SCM, I am not able to figure what is missing, is there any special customization is needed to send delivery document to EWM, Give your valuable suggestions.
Thanks and Regards,
Babu

Hi Babu,
1) Check whether the data is getting struck in inbound/outbound queues
2) Check is there any inconsistencies
3) Check is there active integration model for delivery documents
Regards
R. Senthil Mareeswaran.

Missing material line in Inbound delivery

Hi All,
Outbound delivery and inbound delivery are created successfuly, but in the inbound there is no material appear. There is only 1 material in the outbound. What is the cause of the issue and how to fix the inbound issue?
Thanks.

Hi,
I guess this is not the correct forum to post question on functional stuff. you can put this may be eaither in ABAP General or BPX forum.
Thanks,
Chandra

Inbound Delivery: Output Missing

Hi Gurus,
I am encountering problems with the initial display of Inbound delivery (VL33). The output does not appear in the header portion.
Here's the scenario:
1. Inbound delivery created using the PO with output details (VL31).
2. But when I initially display the inbound delivery (VL33), there is no output (Path: Header Menu > Output)
3. When I change the inbound delivery (VL32) and go to Header > Output, there are values.
Everything is working fine on VL31N.
Can someone shed some light on this please. Points will be rewarded if found helpful.
Thanks in advance

Hi,
I think the situation is the following:
You create the document with VL31 -> before saving the outputs are visible -> when you save -> function module MESSAGING is run -> here the output records get deleted from XNAST (necessary condition field are empty, requirements ?)
-> after saving the document check if there are really no entries in table NAST -> then you enter TA VL32 -> now the condition fields necessary to find the output condtion records are filled (and remain filled during saving) -> outputs are saved -> entries in NAST exist -> outputs can displayed with TA VL33.
Conclusion: set a breakpoint in FM MESSAGING (during VL31 saving) in order to determine which and why some fields that are necessary to find the output condition record are not filled or still not available duing VL31 saving process.
Regards,
Andreas

MIGO & Inbound delivery

Hi all,
What is the main difference between the MIGO and Inbound delivery?
regards
RP

Hi,
Inbound processing covers the physical inbound delivery processing that succeeds the procurement process. It includes ASN processing, physical Goods Receipt and put away of materials in Warehouse Management up to sending the proof of delivery to the business partners.
Outbound processing comprises the preparation of goods to be delivered from a warehouse to a receiving location. Outbound processing within the scope of warehouse management typically comprises activities like the notification of goods to be supplied from a warehouse to a customer for which the outbound delivery serves as the reference document, picking, packing, physical goods issue in warehouse, loading, goods issue and goods issue posting to IM, advising advanced shipping notifications to business partners and, obtaining a proof-of-delivery from the receiving business partner
For more check the links:
http://www50.sap.com/businessmaps/503FC98E125841BABC365D208D214617.htm
http://erp.esworkplace.sap.com/socoview(bD1kZSZjPTgwMCZkPW1pbg==)/smdisplay.asp?id=7E1E658E603711DA36BB000F20DAC9EF&fragID=&packageid=CBD4F2B708B8144DAEA05442D8FD491E&iv=
http://esoadocu.sap.com/socoview(bD1lbiZjPTgwMCZkPW1pbg==)/render.asp?packageid=DBBB6D8AA3B382F191E0000F20F64781&id=6E8A57AE47AF11DA36BB000F20DAC9EF
Were as Inbound Delivery is
In its role as central object of the inbound process, the inbound delivery supports all activities such as putaway, packing, transportation and goods receipt. During the inbound delivery process, planning information is recorded, the status of different activities is monitored, and data accumulated during inbound shipment processing is documented. When the inbound delivery is created, activities such as putaway or scheduling are initiated, and data that is generated during processing of the inbound delivery is included in the delivery.
Process flow
An inbound delivery can be created as follows:
With reference to a purchase order
With collective processing for several purchase orders
With reference to a stock transport order
With reference to a customer return
Depending on your requirements, you can create inbound deliveries automatically using work lists, or manually. Overviews allow you to monitor the inbound deliveries that were created and activities relating to those deliveries that are due to be carried out.
The system carries out the following activities when an inbound delivery is created:
Checks the order and materials to make sure an inbound delivery is possible
Determines the delivery quantity of an item
Calculates the weight and volume of the delivery
Calculates work expenditure
Assigns a storage location for putaway
Updates order processing
You can subsequently make changes in a delivery in order to report the quantity that was put away or if the delivery situation changes in any way. In addition, you can use the display function to access inbound-delivery information in a delivery.
Regards,
Prem.
Edited by: prem cherukuri on Jun 11, 2008 1:00 PM

Problem with HU during creation of Inbound Delivery using IDoc

Hi,
When I am creating Delivery manually and perform Packing, Handling Unit information is stored in VEKP and VEPO tables.
But when I am processing through IDoc, after passing data to Handling Unit Segments E1EDL37 (Handling unit header), E1EDL39 (Control Segment for Handling Units), E1EDL44 (IDoc: Handling Unit Item - Delivery), It is creating delivery successfully but Handling Unit information is not getting stored in VEKP, VEPO tables.
Tried most of the notes 912470, 678464, 682506 and all of them say "You use the Idoc DESADV to create inbound delivery with packing data. The delivery is created, Idoc gets status 52 but the Handling Units (HUs) are missing. This is due to a program error. In case the IDoc contains segments to create HUs (E1EDL37), the IDoc processing should end in error status (51) as long as no packing data could be created.".
Need your advice whether we have to maintain any customizing for this or how to proceed with it.
Thanks in advance,
Murali.

IDocs and BAPIs sometimes behave differently than transactions. You might need to add a user exit specifically for IDoc processing. Otherwise send a message to SAP and have them look at it.

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

Collective posting of Inbound Delivery with reference to External ID

Hi,
I have created few Inbound Delivery (for different PO) with same External ID reference.
Now when I try to process these Inbound Delivery through T. Code: VL06IG with reference to External ID, system doesnot consider any Inbound Delivery.
The External Identification Type used is "Free usage".
I have checked in the Inbound delivery all the informations are correctly copied. for e.g. the storage location, etc. Also the Storage location is WM activated
Can you please help me if I am missing any settings.

First of all I want to clarify this transaction will pick deliveries which are ready for goods receipt.Tat means pick and confirmation should be completed.Now you have to check all your inbound deliveries which has same external id Picking and confirmation completed ?.If yes are you entering same test external id which is in delivery in report.Just copy test in delivery and paste the text in report.System will pick those deliveries.Text is case sensitive.so you should type text correctly.I have tested your scenario and it is working fine.

Goods Receipt reversal posing for Inbound delivery

Hi Gurus,
There is an interface running which create, IDOC, Inbound delivery, HU and material received (material document created - 521mvt type) to stock.
Now there is some problem in the HU weight and I need to reverse the Material docuement with 522 mvt type.
As the GR is created through VL32n, I can not reverse the GR using MBST or MIGO cancellation. I am also not allowed to reverse through VL09. I am getting error This is not possible with movement type 522.
Kindly inform me if you have any suggestion to reverse this material document.
Best Regards,
Mohan

Hi,
VL09 is the correct transaction.
I doubt if this will work but try looking at theconfig of the 521 and 522 movement types and check the "allowed transactions" see if VL09 is linked to it, if not then link it and try VL09 again.
It is a longshot but VL09 shouldwork (although my HU knowledge is not good).
Steve B

GR via Inbound Delivery or Purchase Order

Hi,
Inbound Delivery has been created for the purchase order, but we still can perform goods receipt to purchase order via MIGO --> Purchase order, my question is, it should not be possible to perform GR against purchase order directly once inbound delivery was created, so which setting is missing?
Kindly please advise.
Thanks.

Hi,
my situation is:
- a WM managed warehouse, society A;
- a HU managed warehouse (without WM), society B;
- a purchasing process of HU from society A towards society B.
Society B have a scheduling agreement; when a delivery schedule appears, in society A born a sales order and a delivery. After the registration of the delivery good issue, an idoc transfer information for inbound delivery creation.
This process is ok without WM, but with a WM managed warehouse the idoc has the following problem:
"V51VP - item was not found - process cancelled".
Can you help me to transfer these HU?

Po to inbound delivery

Dear friends
I have a scenario where i need to bring the master data text to inbound delivery text.what are the settings required.Is it possible?
Regards
Aaryabalaji

Hi,
This note should help to map the text determination procedure from the
purchase order in the system correctly.
The function 'Text from purchase order' is available as of Support
Package SAPKH46B32 in Release 4.6B and SAPKH46C23 in Release 4.6C.
The following consultation refers to Customizing as of Release 4.70 and
higher - transaction VOTXN.
However, it is also relevant for Releases 4.6B and 4.6C as of the
Support Packages mentioned above - transaction VOTX.
Customizing for the procedure texts from purchase order -> delivery
1. Delivery type definition
Define your own delivery type for texts from purchase orders.
Since preceding documents from purchase order and sales order may
exist for deliveries, a separate delivery type is required for a
correct text determination.
Create access sequences
Example: instead of replenishment delivery RD -> new ZRD
2. Text determination procedure definition
Use transaction VOTXN (VOTX) and create your own text procedure at
header level as well as at item level.
3. Creating access sequences
For the new text determination procedures, use text objects EKKO and
EKPO to create new access sequences.
If you only want to find texts in this access sequence that were
created manually in the purchase order, text object EKKO or EKPO is
sufficient.
Here you should also maintain the condition for both text objects.
These are
EKKO > '1'
EKPO > '50'
The maintenance of additional text objects in these access sequences
is also possible of course, for example, 'TEXT'.
4. Text determination procedure assignment
Assign the new text determination procedure of the header texts to
the new delivery type and the text determination procedure of the
item texts to the relevant item categories.
In VOTXN (VOTX), this assignment is required.
Check in case of errors in the texts from purchase order procedure
1. Check: Customizing
see above
2. Check: Table RVTXOBJ
If the system issues error message VC 220 'Only special text objects
are allowed' when you create the text objects EKKO and EKPO in
transaction VOTXN (VOTX),
check the table RVTXOBJ.
To do this, use transaction SE16 to go to the table.
If the entries EKKO and EKPO are missing there, execute the SDTXNMUP
correction report.
This reorganizes the table. -> For further information, see SAP Note
711954.
3. Check: Table TFRM
Use transaction SE16 to display the table contents of the TFRM table
and enter the 'TXNM' field value as the selection condition for the
group indicator for copying control (GRPZE).
Check if the entries for TXNM with grouping numbers (GRPNO) 018 and
019 exist > EKKO/EKPO.
table TFRM
GRPZE GRPNO BEZEI
TXNM 001 VBBK text name
TXNM 002 VBBP text name
TXNM 003 MVKE text name
TXNM 004 TEXT text name
TXNM 005 VBKA text name
TXNM 006 KNVV text name
TXNM 007 KNVK text name
TXNM 008 KNB1 text name
TXNM 009 KNA1 text name
TXNM 010 MATERIAL text name
TXNM 011 KNMT text name
TXNM 012 VTTK text name
TXNM 013 VBBK text name
TXNM 014 VBBP text name
TXNM 015 KONA rebate payment
TXNM 016 WBRK text name
TXNM 017 WBRP text name
TXNM 018 EKKO text name <<<<<<<
TXNM 019 EKPO text name <<<<<<<
If these two entries are missing, use the solution provided in
Note 524453. The cross-client RV80INCTFRM report generates the
missing entries in TFRM.
Then start the RV80HGEN report that regenerates the relevant
includes.
You must take into account the comments in the long text of Note
524453.
Caution:
You should NOT implement the two entries manually in the FV46TNNN
include
Since this is a generated include, these entries would be lost
during the next generation (RV80HGEN).
Then you would no longer find texts from the purchase order.
Implement Note 524453 instead.
For information about the function of transaction VOFM, see also
Note 327220.
4. Error message VC 220
You receive the above error message with the text
IMPORT_LOGFILE_KEY_TOO_SHORT in the REFER_TEXT_AFTER_COMMIT function
module.
This means that an error occurred in the interface of the update
module during the local update.
To solve the problem, carry out the RSVBLOCL report for the
REFER_TEXT_AFTER_COMMIT function module.
The update module is then regenerated.
Check for a data transfer routine:
Some customers still use the workaround from Note 53593 and have defined
their own text determination routine in transaction VOFM.
As of Note 417883, this is no longer required, since the text
determination procedure from the purchase order is now supported and is
set as default.
5. Transaction ME2O - (Delivery to provision of materials for
subcontract order)
The text determination for deliveries from the provision of
materials for subcontract order is not possible in the standard
system.

Error while activating Inbound Delivery Notification

Hi,
I have created and Inbound delivery in ERP, the material is batch managed and packed with HU. Once saved on ERP system, I find the Inbound Delivery Notification in SCM EWM system with HU, material and batch number appearing. Up to this point all good.
However, when I am trying to hit the button 'Activate' so that I can create Inbound delivery, system comes up with error message - 'Please specify an external number range' (message NR753) I have no idea where it's coming from.
For further information - I am using standard Doc Type INB with Doc Cat. PDI and it's assigned with an Internal Number Range.
What's missing?
I help will be rewarded.
Thanks,
Amit

Thanks Virendra,
You have pointed to the right direction. Basically, without checking for the posts here, which are really helpful, I went to system one more time only to find that I have made a configuration error. I am just sharing if anyone else in future faces same situation, he/she can be benefited out of it.
In EWM system - I had created number range with transaction SNRO for object /SCWM/SSCC putting 01 (from 1 - 1999999) as internal and 02 (from 2000000 - 2999999) as external number range.
In EWM system - I had assigned the number range in following place:
Extended Warehouse Management > Cross Process Settings > Handling Units > External Identification > SSCC Generation Acc. to EAN128 > Maintain SSCC Generation for Each Warehouse Number
In ERP system - I had created number range with SNRO for object LE_SSCC with same attributes as above. i.e. 01 as internal and 02 as external.
Now when I packed the inbound delivery in ERP system, I used packaging material for which the number range is internal (i.e. 01) and it created HU with SSCC number. Up to this all were good. But when the same HU transferred from ERP to EWM system, SAP treated the HU number coming from ERP system as external HU number (which is logical) but it was looking at number range 02 (since it was marked as external) but was failing to match as the allowed numbers doesn't fit along with the number transferred from ERP system. Hence it was giving error.
As a solution I declared 01 as external and 02 as internal and also inverted the number range assignment for SSCC generation in EWM system.
It created Inbound Delivery successfully.
Thanks all of you for helping on it.
Cheers,
Amit

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

GR to a Inbound Delivery

Hi,
I performed a GR to a Inbound Delivery via Tcode MIGO, but nothing changed to the inbound delivery and I can only see the GR history in corresponding Purchase Order, Why? How to solve the problem?
Best Regards.

Hi Alan
The goods receipt process for inbound deliveries is an essential part of the supply chain. This process includes the steps after creation of the purchase order: notification, the inbound delivery, subsequent putaway of goods, and the goods receipt posting of the ordered goods.
The significant advantage of depicting the goods receipt process through the inbound delivery function is that you can execute many processes in advance, even before the actual goods receipt posting takes place. You have all the necessary information beforehand because the supplier notifies you of the inbound delivery ahead of time. The inbound delivery describes exactly which materials or pallets can be received on what date and at what time.
Make absolutely sure that you do not mix up the goods receipt process for inbound delivery (for example, transaction VL32N) with the functions you already know, such as goods receipt (post) for unknown purchase order (transaction MBOA/MIGO), or cancellation of the goods receipt (transaction VL09 as opposed to MBST/MB0A). You must organize your tasks in such a way that the goods receipt posting is only executed using one of the two ways described.
The system carries out the following activities when an inbound delivery is created:
Checks the order and materials to make sure an inbound delivery is possible
Determines the delivery quantity of an item
Calculates the weight and volume of the delivery
Calculates work expenditure
Assigns a storage location for putaway
Updates order processing
There are different way of creating Inbound deliveries , collective run , EDI or Manually .Most of the errors are seen in EDI processing , kindly let us know which process you are using .
regards
kp

Loading weight information is missing in Inbound Delivery

Similar Messages

Maybe you are looking for