Requirement output inbound delivery

We have developed a requirement on a output for inbound delivery, which only should trigger the output when the inbound delivery has overall status completed (C). That means that all transfer orders for the inbound delivery is confirmed.
The problem we see is that the output is not triggered automatically when the last transfer order is confirmed and overall status for inbound delivery is changed to C.
The output is triggered when we manually go into transaction VL32N and save.
Anyone have any suggestion of how to trigger this output automatically?
Best regards,
Terje

Of course I have set up the condition record in transaction MN24.
The problem is that I have to go into the inbound delivery to get the ouput triggered.
BR
Terje

Similar Messages

Transfer Requirement with Inbound delivery.

Hi Guys,
I have the following problem:
The Warehouse is HU managed.
When I have a Purchase Order and I do a Goods Receipt the system is creating a Material Document and in addition a Transfer Requirement.
But
When I have a Purchase Order and I have an Inbound Delivery, before I can do my Post Goods Receipt I have to do my TO creation and confirmation.
In IMG under Handling Unit Management > Basics > Delivery > Define Sequence of Transfer Order - Goods Receipt I can make my settings so that I can do my Post Goods Receipt before my TO creation and confirmation.
This means that I have again first a Material Document. Only in this scenario I do not get a TR, although in the WM - IM interface for movement 101 TR creation is set to X.
How can I get my TRs?
Thanks in advance for your help.

Answers to your questions:
Yes Yes No.
The MIGO transaction is there to do the GR at the moment the truck is at your door, the inbound delivery transaction (VLxxx) is there to have an ASN creating the inbound delivery days before the truck will arrive. To avoid open TRs sitting there for days, the system normally doesn't create the TRs. The posting of the GR (and the availability for MRP etc) can only be done after the TOs are created and confirmed. If you look at an inbound delivery under the subsequent functions it says "create TO".
So you create TO from the inbound delivery and after that you post the GR.
Only, there is a way to turn around the sequence (when using HUs) but then the Mat Doc is created and not a TR.
We need the TR to be send by IDOC to another system.

MIGO GR to Inbound Delivery Only

We have a requirement to perform GR wrt Inbound Delivery in MIGO. We do not want users to also be able to post GR in MIGO wrt to PO if on inbound delivery.
We use confirmation control 0001 (AB and LA). Currently within deliveries for same vendor some PO's allow posting wrt PO and some do not. The only difference between the deliveries seems to be the type of external ID. Only difference in PO's is document type although this difference is not consistent.
Is there some configuration in PO type or delivery that will accomplish this requirement?

Inbound Delivery Creation
Transactions:
- VL31N, VL34, Idoc DESADV1 (standard cases)
- MIGO, MB01, MB11:
with or without reference to a purchase order
only for HU managed or decentralized storage locations
inbound deliveries are created automatically (instead of posting GR)- VLMOVE:
without reference to a purchase order
not only for HU managed or decentralized storage locations
- VL31W: creation via Internet
- SPED Output (from replenishment delivery)
- VL60: All-in-one transaction
Conditions:
Processing VL31N, VL34, Idoc DESADV1 with respect to purchase order (item) if:
confirmation control key (EKPO-BSTAE) is set
no deletion or final delivery indicator is set (EKPO-LOEKZ/ELIKZ)
no return flag is set (EKPO-RETPO)
purchase order is released and completed (EKKO-FRGRL/MEMORY)
purchase order can be locked
document category must be "purchase order" or "scheduling agreement" (EKKO-BSTYP)
Differences Between VL31n and VL34:
- VL31N: (processing the last inbound delivery in dialogue mode)
accepts only confirmation control keys with internal category "shipping notification" (T163D-IBTYP)
authority check is done with object 'M_BEST_'
- VL34: (mass transaction, processing in background)
accepts confirmation control key only if automatic flag is set (T163L-AAGEN), but no special internal confirmation category "shipping notification" is needed
no authority check is done
Further differences are described in OSS note 386409, that especially describes the quantities that are taken over.

Get inbound delivery number by using material serial number

is anyfuction module to get inbound delivery number by using material serial number?
input---material serial number.
output--inbound delivery number.

Hi,
BAPI_OUTB_DELIVERY_CHANGE
BAPI_GOODSMVT_CREATE
it's ok with the Function module
CALL FUNCTION 'WS_DELIVERY_UPDATE_2'
EXPORTING
VBKOK_WA = LWA_VBKOK
SYNCHRON = ' '
NO_MESSAGES_UPDATE = ' '
COMMIT = 'X'
DELIVERY = P_ITEM-VBELN
IT_SERNR_UPDATE = LT_SERIALS
IMPORTING
EF_ERROR_SERNR_UPDATE = L_SERNR_UPDATE
<b>Reward points</b>
Regards

Inbound Delivery without SUS

I am using SAP ECC 603 and SRM EBP 701 self-service procurement classic scenario. I am investigating changing the confirmation control key on the SAP vendor master to one requiring an inbound delivery. This change would be applied to all purchasing vendors, including those used by SRM. In the case were a vendor is not capable of sending an Advanced Shipment Notification, I would create the inbound delivery manually in transaction VL31N.
I am obviously unable to create the SRM confirmation (goods receipt) against the purchase order if no inbound delivery exists. Is there a way to create an inbound delivery in standard EBP classic scenario?
Thank you in advance,
Cliff

Hi Cliff
Inbound delivery is a SAP ECC business object. There is no Inbound delivery Business object in SRM so we can not create a Inbound delivery in SRM .
Requistion - SRM
PO - ECC
Inbound delivery - ECC manual or by ASN if SUS connected ( if it has confirmation control key)
confirmation - SRM / ECC
Muthu

Link between Inbound delivery and Billing

Hi Experts,
I am new to MM.
It appears to me that inbound delivery is linked to Billing or the other way round.
Can I know how are the 2 processes related?
Can i say a billing doc can require the inbound delivery doc as the reference document at point of creating the billing doc?
If so, inbound is about receiving goods delivered as a result of purchase order sent out to vendor.
So, when creating a billing doc, does it mean the company is billing someone when he is the one who has purchased something?
So, you can see that i am confused.
Please advise. Thank you.
regards
Pascal

Hi,
Need not to confuse about inbound delivery, it is just a shipping document only.
It is normaly used when you do STO process. because without a delivery challan you can't shift any things from one place to another place. So this Inbound delivery doc is accepted as delivery challan by the government.
In STO process, receiving plant will raise the billing document because both plants are within a client only and receiving plant will add shipping cost, loading & unloading cost, etc on the net price of the product to sell to customer. that's why, here receiving plant creating the billing doc.
But if you are consider that the Inbound delivery is created by a vendor with reference to your PO then the billing document will be created by the supplier (Vendor) only.

Inbound delivery creation using shipment Idoc details

Hi,
   My requirement is that I need to create inbound delivery using SHPMNT05 idoc sending from a different plant.
Below are the fields I am getting from the SHPMNT05 Idoc. So I need to create Inbound delivery in Receiving plant.
SAP - Field     IDoc Segment- Position - Field Name
LIKP-LFART     E1EDL21 001 LFART
LIKP-LIFEX     E1EDT01 001 VBELN
LIKP-LIFNR     E1EDT44 009 LIFNR
LIKP-MBDAT     E1EDL24 039 = ABRDT
LIPS-LFIMG     E1EDL24 013 LFIMG
LIPS-MATNR     E1EDL24 002 MATNR
LIPS-VGPOS     E1EDL41 006 POSEX
LIPS-PSTYV     E1EDL26 001 PSTYV
LIPS-VGBEL     E1EDL41 002 BSTNR
LIPS-VRKME     E1EDL24 014 VRKME
VEKP-EXIDV     E1EDL37 001 EXIDV
VEKP-VHILM     E1EDL37 017 VHILM
VEPO-MATNR     E1EDL44 007 MATNR
VEPO-POSNR     E1EDL44 003 - POSNR
VEPO-VBELN     E1EDL44 002 - VBELN
VEPO-VELIN     E1EDL44 001 VELIN
VEPO-VEMEH     E1EDL44 006 VEMEH
VEPO-VEMNG     E1EDL44 005 VEMNG
Could you please help me to find some workaround to solve this ?
Thanks in advance.
Regards.
Ranjith

Hi Ranjith,
I guess there is a BAPI " /SPE/INB_DELIVERY_REPLACE " which can be used to create an inbound delivery.
Documentation-
FU /SPE/INB_DELIVERY_REPLACE
Short Text
Create inbound delivery
Functionality
You can use this method to distribute inbound deliveries from an ERP system to a WM system.
The following parameters are required:
HEADER_DATA Inbound delivery header data
SENDER_SYSTEM System of the sender
HEADER_PARTNER Header data of the partners
HEADER_DEADLINES Header data of the dates
ITEM_DATA Item data of the inbound delivery
ITEM_ORG Organisation data of the inbound delivery
Notes
The required parameters have the following required fields:
Import parameter HEADER_DATA
INB_DELVRY_NO
DLV_TYPE
Import parameter SENDER_SYSTEM
SENDERSYSTEM
Table parameter HEADER_PARTNER
PARTN_ROLE = 'LF'   Vendor is required partner
PARTNER_NO
Table parameter HEADER_DEADLINES
TIMETYPE = 'WSHDRLFDAT' Delivery date
Table parameter ITEM_DATA
INB_DELVRY_NO
ITM_NUMBER
MATERIAL
DLV_QTY
SALES_UNIT_ISO oder SALES_UNIT
Table parameter ITEM_DATA_ORG
PLANT
Further information
HEADER_PARTNER
Since the partners in the delivery are not managed on an item basis, the ITM_NUMBER field in the BAPIDLVPARTNER segment is left blank and not analyzed.
HANDLING_UNIT_ITEM
If the BAPI is used as an external interface for an external system, the packing hierarchy should be described as usual by using external identification numbers for shipping materials (HDL_UNIT_EXID_INTO/HDL_UNIT_EXID).
Parameters
HEADER_DATA
SENDER_SYSTEM
TECHN_CONTROL
HEADER_DATA_SPL
HEADER_CONTROL_SPL
HEADER_PARTNER
HEADER_PARTNER_ADDR
HEADER_DEADLINES
ITEM_DATA
ITEM_ORG
ITEM_STOCK_TRANS
ITEM_CODING_BLOCK
ITEM_REF_PURCHASE_ORDER
ITEM_SERIAL_NO
ITEM_DATA_SPL
TEXT_HEADER
TEXT_LINES
HANDLING_UNIT_HEADER
HANDLING_UNIT_ITEM
HANDLING_UNIT_SERNO
HANDLING_UNIT_ITEM_SPL
HANDLING_UNIT_HEADER_CROSS
HANDLING_UNIT_IDENTIFIERS
EXTENSION1
EXTENSION2
RETURN
TOKENREFERENCE
Exceptions
Function Group
/SPE/INB_DELIVERY
Check if this helps.
Reward helpful answers.
Regards
Parag

BAPI to get inbound delivery from material serial number

BAPI to get inbound delivery number from material serial number?
input---material serial number.
output--inbound delivery number.

Perhaps instead of using a BAPI you can code it like this.
DATA:serial(10) TYPE n VALUE '0000340078',
pos TYPE i VALUE 1.
START-OF-SELECTION.
WHILE pos <= 10 AND serial+pos(1) = 0.
pos = pos + 1.
ENDWHILE.
REPLACE ALL OCCURRENCES OF '0' IN serial(pos) WITH space.
WRITE serial.

Creation of automatic inbound delivery

There is a requirement that inbound delivery should be automatically created after executing 511 movement type. How this can be achieved,Instead of material doc an inbound delivery should be created?

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?

Item Level Details in Output Requirements Control during Inbound Delivery

Hello Experts,
I have a requirement to access item level details of an inbound delivery at the time of processing the output requirement. The output requirement is defined for application E1 and has a related communication structure KOMKBE1. However, this structure does not have item details (Material, Plant, Batch is what is needed) . Is there another global communication structure that stores this data when the output requirement is called? If not, is there any other way to access that data during runtime?
It is not possible to fetch it from the database tables because the delivery creation process is not yet complete and thus it is not stored in the database, as the output requirement is called when the SAVE button is clicked in VL31N.
Thanks,
- Neeraj
EDIT: Found a solution: Using field symbols, I picked up the value of the needed details from the structures available in the calling program SAPMV50A. In this case, I did not use KOMKBE1 at all.
Edited by: NeerajAngal on Oct 6, 2010 12:28 PM

Hi
As per my understanding you can try se63 option ..

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

Output type not trigerring Automatically for inbound delivery

Hi all
We have created a custom output type for Delivery idoc processing ZPOD copy of OPOD and maintained all the settings also condition record for the same has been maintained.
But when we are creating inbound delivery the output type ZPOD is not coming automatically.
In the Delivery document and in the Output screen i have checked Determine analysis for output(VL32N -> Enter IBD No -> Select menu option Extras -> Delivery output -> Header
Go to menu option GoTo -> Determin.Analysis.)
It is showing me ->Message 502-Output ignored (requirement 017 not fulfilled)
Can u please throw some light so that in output message determination the Output type should come automatically for Proof of delivery
Thanks and regards
shailesh

Um... I think the message is pretty clear on this - the reason is "requirement 017 not fulfilled".
Requirements for output control may be found in VOFM transaction, under Requirements -> Output control. 017 is the standard one, the description says 'POD on goods issue'. According to the comments, the output is not issued if "POD status is initial" or "No output, if no goods receipt".
Either correct the document or remove this requirement in output configuration, if it's not applicable.

Triggering output upon GR in inbound delivery

Hi all,
I want to trigger HU label as soon as i do GR on inbound delivery and on (ii)GI on outbound delivery.
For this i set condition records in VV61 and then i assign requirement 1(Delivery GI posted) in SPRO->LOGISTICS GENERAL->HANDLING UNIT MANAGEMENT->OUTPUT->MAINTAIN OUTPUT DETERMINATION PROCEDURE->assign requirement 1
HU label output is triggering automatically upon GI in outbound delivery (VL02N)...but upon GR in inbound delivery(VL32N) HU label output is not triggering
as soon as i remove assignment of requirement 1, HU output is triggering on inbound delivery creation...means my other settings are fine..only thing is that i want output upon GR in inbound delivery...which is not happening..
i tried will all other combination like changing the application from V2 to E1 for requirment 1, keeping application blank for requirment 1. i also tried requirement 35
what can be the problem..
Regards
Rahul

Check the below config also..
SPRO - Logistics Execution - Shipping - Basic Shipping Functions - Output Control - Maintain Output Determination for Inbound Deliveries.
Also not sure, if we have a requirement for goods receipt. But certainly requirement 1 will not work, as that is for PGI of outbound.
Create a new requirement for Application E1, let's say 901 and put the code like below and attach to the output condition.
FORM KOBED_901.
   if komkbe1-wbstk <> 'C'.
    sy-subrc = 4.
    exit.
endif.
ENDFORM.

Inbound Delivery: Output

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

Inbound Delivery Idoc- Create ... help required

Hi,
I'm using DELVRY01 idoc to create deliveries. when i execute using test tool, the idoc gets created with error status 51 with following errors:
Field EXIDV empty
Message no. VL243
Diagnosis
A required field in the intermediate document (IDoc) is not filled. This is the field EXIDV in segment 000042.
Field VHILM empty
Message no. VL243
Diagnosis
A required field in the intermediate document (IDoc) is not filled. This is the field VHILM in segment 000039
But these errors reflect to handling unit from segment E1EDL37 and its sub nodes which are really NOT required in my case.
Now confused if i'm using a wrong reference of creating inbound delivery. Pls shre some thoughts on it on troubleshooting this issue.

Hi Prabhu
these two fields are mandatory .. fill below details
E1EDL37-Handling unit header
EXIDV     <XXXXXXXXXXXXX>     External Handling Unit Identification
GWEIT     <LB>             Weight Unit Tare
BRGEW     <000XX>                             Total Weight of Handling Unit
VHILM     <Dummy Packing Material>     Packaging Materials
E1EDL44-IDoc: Handling Unit Item (Delivery)
VBELN     <Delivery nO>     Sales and Distribution Document Number
POSNR     <900004>     Item number of the SD document
EXIDV     <XXXXXXXXXXXXX> External Handling Unit Identification
VEMNG     <00001>     Base Quantity Packed in the Handling Unit Item
Dont forget to create Dummy packing material no...
i think above mapping helps you...
Thanks
Ramesh

Requirement output inbound delivery

Similar Messages

Maybe you are looking for