Follow on documenets on inbound delivery

Hi,
There are two cases where the follow on documents on inbound delivery are created differently:
1) The follow on document created was "confirmation of services"
2) The follow on document created was "GR goods receipt"
The question is on what configuration this setup depends?
Regards,
Patrick

Look at the Confirmations configuration on service POs. As far as my understanding the two processes are not either or it is the sequence. The inbound delivery is an indication that Goods receipt or Service execution is impending. Once goods are received or service executed, it is confirmed in the system and that triggers the posting of GR

Similar Messages

Serial numbers in Inbound delivery for Handling units

Hello Experts,
I have the following scenario:
Purchase order + Inbound delivery + GR
Inbound delivery is used because I need to create handling units, the materials included in these handling units are serialized and I am getting from the vendor an excel document with Handling unit number and the serial numbers included in each handling unit.
So I would like to use this document to do the packing process in my inbound delivery instead of manually typing the serial numbers.
What would be the best option to do this?
I also need to do the same for MIGO when no HU are needed.
Any Ideas??
Thanks a lot in advance for your comments.

Thanks a lot for your quick answer.
I would like to avoid creating my own Z transaction, is there any point in packing process where I can include some enhancement to upload the serial numbers, I gues the HU and packing process can be done manually by the user.
I was planning to enhance MIGO for the same process without handling units and I know that there a tab can be added at item level. But I do not know where or how to do it while packing.
Any suggestions?
Thanks a lot for your time!

Creating outbound delivery with reference to inbound delivery

Dear all,
My requirement is as follows:
I get an inbound delivery from my vendor for the our sales orders. (For n number of sales orders having same shipping point, shipto party ad sold to party, we get one inbound delivery) As of now we are using that inbound delivery and read data from LIPK and LIPS and using 'BAPI_DELIVERYPROCESSING_EXEC' to create outbound delivery.
But, it is creating one delivery each for every sales order. What we require is to create only one outbound delivery.
I have searched in forums and tried to use VL10A, VL10C but since the delivery dates of each order are different I cant use those transactions.
Now I have two options:
1) Take inbound delivery as reference and create outbound delivery. Are there any FM's or BAPI's for this which will create 1 outbound for each inbound?
2) Can we combine multiple sales orders into a single delivery when the delivery dates are different.
Could you please help me.
Thanks in advance,
Aravind

Hi Aravind,
I am facing some issues while creating Outbound delivery using the BAPI 'BAPI_DELIVERYPROCESSING_EXEC'. I am getting the error message in return parameter as "No instance of object type OutboundDelivery has been created. External reference:"
If you are successful in creating Outbound delivery, please suggest what may be the issue for this message. Iam passing the exact sales order no and item no., quantty and unit of quantity. Also manual creation of Delivery using VL01N is successful but using the BAPI it is unsuccessful. Please suggest with your valuable points on this.
Regards,
Vimala P

Inbound Delivery (WM) with Serial Numbers and HU's

Hey,
I want to use Serial Numbers with Handling Unit Management in WM.
I want to use MIGO to GR a Purchase Order and then Auto Pack the Inbound Delivery.
I also want to be able to Auto Pack the HU's with the Serial Numbers that i enter into the WM tab of the MIGO transaction.
I post the GR of my PO and get my inbound delivery. The delivery is Packed onto an HU ... BUT the serial numbers i enter are not present in the HU ?!?
Does anyone know if this is possible via MIGO? or is this available only when receiving IM deliveries??
thanks,
Adam.

Hi Nagesh,
The process will be to use transaction MIGO for all goods receipts, therefore i would like to automate the Inbound Delivery Create AND pack process so that we minimise the amount of user input.
Once we have entered the GR for the PO i want to automatically do the following:
1) Create the inbound delivery (which the system does because the item is going into an HU managed storage location).
2) Pack the inbound delivery (which the system does because i set the Delivery Type to 'Auto Pack')
3) Assign entered Serial Numbers to the HU - which at the moment is not happening.
I thought that by entering the Serial Numbers in the 'Serial Numbers' tab in transaction MIGO that these would be copied into the HU but this is not happening ?!?
(NB: I have serialisation procedure MMSL: Maintain goods receipt and issue doc. - set on my serial number profile).
We do not want to go into the Inbound Delivery and manually assign the serial numbers as this adds complexity and is time consuming for the User.
thanks,
A

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.

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

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

Inbound Delivery Modification n follow on activities

Hi,
Is there a way to modify EWM Inbound delivery once it is locked for processing. For e.g. I received an Inb del in EWM, due to me not specifying the storage bin for the warehouse task, I specified the bin in customizing. Now, I get the same error message that storage bin is not able to be determined. Do I've to resend the inbound delivery from ECC to EWM again after rejecting this. How does the process work?

Look at the Confirmations configuration on service POs. As far as my understanding the two processes are not either or it is the sequence. The inbound delivery is an indication that Goods receipt or Service execution is impending. Once goods are received or service executed, it is confirmed in the system and that triggers the posting of GR

Creation of Inbound delivery mandatory for ASN process in classic scenario?

Dear Experts,
We are going for classic scenario for our green field SRM implementation process. Our client is not using ASN process in their existing MM process. However, they are now looking for an oppurtunity to enable Suppliers to trigger ASN using SUS. In such case, is creation of inbound delivery from Buyer side a mandatory process?
Is the below the process correct?
PO -> ASN (Supplier using SUS) -> Inbound delivery (Optional) -> Goods Receipt (Mandatory) -> Invoicing.
Here, I understand that Goods receipt can be verified against the PO or via Inbound delivery to PO. ASN will inform the store keeper in advance about impending goods receipt and smoothen the confirmation process.
Could you please comment on the above process? Could you please suggest the best practices followed here?
Thanks and regards,
Ranjan
Ranjan Sutradhar

Hey Ranjan!,
You are on track.
The process flow you have shown is true. ASN is available as a standard as part of the MM-SUS process. It makes the buyer aware of any delays in delivery or to make arrangements on shipping docks to receive goods on a said date etc.
Regards,
Nikhil

Error in creation of inbound delivery

hi
When I tried to create inbound delivery against schedule agreement
1) Following warning message is coming when I enter the quantity for each and every line item
u201CAcknowledgment for PO item contains data varianceu201D
2)Following error message is coming when I saved the delivery
u201CTermination during purchase order updateu201D
So I am unable to create the inbound delivery
Note: this error is coming for a particular vendor only

Hi ,
Goto SM13 .
Find the terminations based on user and creation date.
Get the same analysed by ur ABAP team.
Also check the confirmations in PO at Item level.
Regards
Ramesh Ch

Reg: How to capture the Excise Invoice with respect to Inbound delivery

Hi All,
Please give the process follow for capturing the excise invoice with respect to inbound delivery.
Thanks & Regards
Siva

Hi Siva,
Please check this link
CIN with Example..?
Regards,
Bijoy Kumar

SAP System inconsistency for Inbound delivery / MIGO and a "sap note"

Hello Friends ,
After following SAP instruction on how to remove the inconsistency between posting GR through MIGO (Inv. mang.) and the reflection of the goods movement status in the inbound delivery document - done that using sap note 570991
the problem is that the system start behaving in a weird way throwing unjustified Error messages for any suggested goods receipt using MIGO with reference to inbound
for example after creating an inbound delivery document and trying to post it via migo , an error will pop up
- Inbound delivery storage location cannot be changed to here Message no. VLA316
the thing is i didn't even maintain any storage location entry up to that point and yet i cannot post any stock !!
also another error like
- Inbound delivery batch cannot be changed to *** here
which doesn't make any sense because there is not batches in the inbound document !!
i think this behavior is coming from the "Document Flow Update for Stock Postings" inbound indicator at the shipping parameter at client level customization
i need help on how to overcome this annoying SAP Bug/Problem specially i am in a post go live critical situation

Hi,
The messages you mentioned were introduced to avoid inconsistency between inbound delivery and IM, through the note: 1050944 - GR for inbound delivery using inventory mgmt as of ECC 6.00
If the messages are issued incorrectly, then you may check for SAP notes (I couldnt find anything relevant) or raise an OSS ticket to SAP.
Regards,
AKPT

Exit or Badi to prevent MIGO Goods Receipt on PO with Inbound Delivery

Hi,
I am hoping that someone can provide me with some direction on how to prevent the use of MIGO for GR when the PO being received is (or should be) linked to an inbound delivery.
For purchase orders with a confirmation control key an inbound delivery is to be created and the goods receipt needs to be done from the inbound delivery. This scenario also includes the case of stock transport orders whereby an inbound delivery is created form the outbound delivery. On the other hand for purchase orders without a confirmation control key no inbound delivery is created and the MIGO transaction is to be used to post the goods receipt.
Since both processes are possible, I would like to prevent people from posting the GR using MIGO if certain conditions pre-exist.
Can anyone suggest a means to accomplish this goal? Is there an exit or badi in MIGO that you would suggest using?
Thanks,
Paul

Hi,
The following user eixts and badis available for migo transaction:
Enhancement/ Business Add-in            Description
Enhancement
MB_CF001
Customer Function Exit in the Case of Updating a Art. Doc.
MBCF0011
Read from RESB and RKPF for print list in MB26
MBCF0010
Customer exit: Create reservation BAPI_RESERVATION_CREATE1
MBCF0009
Filling the storage location field
MBCF0007
Customer function exit: Updating a reservation
MBCF0006
Customer function for WBS element
MBCF0005
Article document item for goods receipt/issue slip
MBCF0002
Customer function exit: Segment text in article doc. item
Business Add-in
MB_RESERVATION_BADI
MB21/MB22: Check and Complete Dialog Data
MB_QUAN_CHECK_BADI
BAdI: Item Data at Time of Quantity Check
MB_PHYSINV_INTERNAL
Connection: Core Inventory and Retail AddOn
MB_MIGO_ITEM_BADI
BAdI in MIGO for Changing Item Data
MB_MIGO_BADI
BAdI in MIGO for External Detail Subscreens
MB_DOC_BADI_INTERNAL
BAdIs when Creating an Article Document (SAP Internal)
MB_DOCUMENT_UPDATE
BADI when updating article document: MSEG and MKPF
MB_DOCUMENT_BADI
BAdIs when Creating an Article Document
MB_CIN_MM07MFB7_QTY
Proposal of quantity from Excise invoice in GR
MB_CIN_MM07MFB7
BAdI for India Version exit in include MM07MFB7
MB_CIN_LMBMBU04
posting of gr
MB_CHECK_LINE_BADI
BAdI: Check Line Before Copying to the Blocking Tables
ARC_MM_MATBEL_WRITE
Check Add-On-Specific Data for MM_MATBEL
ARC_MM_MATBEL_CHECK
Check Add-On-Specific Criteria for MM_MATBEL
If it is helpful rewards points
Regards
Pratap.M

Document flow of Inbound Delivery

Dear Gurus,
We have upgraded to support pack SAPKH60018 from SAPKH60010.
Earlier the process for goods receipt was followed as described below
1. Purchase order
2. Inbound Delivery
3. GR in to Blocked stock against Inbound Delivery (mvmt type 103)
3. Release GR blocked stock (mvmt type 105)
Now after upgrading the support pack when GR blocked stock is made against the Inbound Delivery system is not updating the Document number in the document flow and PGR button is not disabled though 103 mvmt type document is made through migo.
System is also not allowing to make the Release GR block stock through MIGO and prompting to use Inbound Delivery Dialog instead.
Request for immediate assitance in regard to this issue.
Regards
Danish Alam.

With the support pack in case if material is serialized for such plant you can post goods receipt only in VL32N which would happen only during 105 mvt type and you cannot post goods receipt using MIGO.

Error during the replication of inbound delivery document to GTS

Hi
While trying to transfer an inbound delivery from the feeder system to the GTS system, I am getting the following error, eventhough the customs document type TRLOIM is assigned to the Feeder sys doc type EL, at application level MM0B in customs management. The inbound delivery document has been maintained with the Prev Doc Type T1 & Prem Doc No in the Foreign trade Data
Customs document type cannot be determined for external document type
Message no. /SAPSLL/API_INBOUND020
Thanks & Regards
Ram

Hi Ram,
Please use OSS note1238850 to fix the issue, this error comes as your doc type EL is not getting transferred when you are sending I/B delivery.
Hope this helps.
Kind Regards,
Sameer

Follow on documenets on inbound delivery

Similar Messages

Maybe you are looking for