Automatically inbound delibery creation problem

Hi!
I'm using workflow ws12300004 to create automatically an inbound delibery after the goods issue posting in outbound delibery in a cross-company stock transfer. (WM storages with HU)
Workflow uses function module SHP_IBDLV_CREATE_FROM_OBDLV.
This workflow works great if i set in spro transaction, in Materials Management/Purchasing/confirmations/Define internal confirmation categories:
Intern. Confirm. Cat.      Conf.Cat.         Description               Del. Type
Shipping Notification              LA          Inbound delivery            EL
But if I change 'EL' for 'HID', workflow doesn´t work, and I get the error HUFUNCTIONS 189:
Item &1 &2 cannot be used for HU &3
where &1 is $   1
          &2 is 0000010
and     &3 is HU number
The complete description of the error is:
                                                                                Short Text
Item &1 &2 cannot be used for HU &3
Diagnosis
A HU item in handling unit is to be assigned to item of the object .
The HU item cannot be assigned because of differences in the material
     data.
Procedure
Check the stock data of the document item or assign a different handling
     unit.
Any idea about what's happening?
Regards,
Moisés
Edited by: Moisés Lorenzo on Oct 20, 2008 4:47 PM

Hi!
Question answered.
I went to spro/logistics execution/shipping/Deliveries/Define item categories for deliveries.
And then I set the Movement Type for delivery type 'HIDN'.
That solves the problem.

Similar Messages

Automatic inbound delivery creation.

Hi All
In our STO process, when the outbound delivery is created from the issuing plant it should automatically create inbound delivery in the receiving plant. I think it is happening by triggering output type SPED.
In some cases for the same STO we are able to get inbound delivery for few items and not for other items.
First of all i want to understand usage of SPED and secondly why we are not getting inbound delivery in some cases.
Thanks & Regards
Amit

Hi
Adding to what i have asked, why SPED didn't worked for some materials. What can be the possible points?

Automatic Inbound Delivery Creation in HU Managed Storage Location

Dear all...
I have created PO, packing instruction, and packing instruction determination.
Storage location was set to HU managed already.
Now I want do GR for PO (with MIGO transaction) which can create inbound delivery automatically, and also do the packing process.
Which config/setting should I do?
Thanks before.

HI,
In IMG-Logistics general-HUM-Basics-MM-IM-HU req for SL and default values for deliveries
Select the plant and click Sto Loc there u can find HU ReQ, Check that HU Req Box.
If you set this indicator for a storage location, the system does not create a material document when it carries out a posting, but creates a delivery via Shipping
Regards
Kk

Automatic ORDRSP idoc creation problem for customer order

Requirement;
When client received order from customer through EDI, while creating order it has to check is there any difference in the order quantity and confirmed quantity. If any difference reason code should set up automatically at line item level (I configured reason code as "Quantity short" and it's not big deal to get this in user exit). After inbound EDI order process, order response should invoke only one time that too first time (Not all the time for all orders) when there are line items exist with "Quantity short".
First I'm trying to kick out ORDRSP Idoc from manually created order. While creating order which has confirmed quantity less than order quantity I setup item level reason code as "Quantity Short".
I created condition table with conditions Sales org, Order type, Sold to party(from KOMKBV1) and item level reason code (from KOMPBV1). I maintained condition record, partner profile. But Idoc is not generating automatically after I created order manually with reason code at line item level.
Can any one help me on this.
Thanks in advance.

>
Ram_Lin wrote:
> Requirement;
>
> When client received order from customer through EDI, while creating order it has to check is there any difference in the order quantity and confirmed quantity. If any difference reason code should set up automatically at line item level (I configured reason code as "Quantity short" and it's not big deal to get this in user exit). After inbound EDI order process, order response should invoke only one time that too first time (Not all the time for all orders) when there are line items exist with "Quantity short".
>
> First I'm trying to kick out ORDRSP Idoc from manually created order. While creating order which has confirmed quantity less than order quantity I setup item level reason code as "Quantity Short".
>
> I created condition table with conditions Sales org, Order type, Sold to party(from KOMKBV1) and item level reason code (from KOMPBV1). I maintained condition record, partner profile. But Idoc is not generating automatically after I created order manually with reason code at line item level.
>
> Can any one help me on this.
>
> Thanks in advance.
There are two things here
1) the Output not getting generated
2) Output is triggered but IDOC isnot generated.
I feel the Output must not have triggered. this may be because generally the response IDOCs are riggered from the Header level and in the communication struture ( or in the condition record ) you have inserted a field from the Item level, so when the system is trying to trigger the output , the field value may be blank, you can check this in the determination analsysis and you may find an yellow icon in the field agains item reason code. you may have to modify the user exist to pass the correct value to this field.
an alternative way is to trigger the output manually and see if the idoc is geenrated or not.
If the output is triggered and the idoc is not generated. again look in the Processing log. there must be some error description why the IDOC is not triggered. Let us know the description of the error codes so that we can give an idea of where could you have gone wrong.
Thanks,

Inbound Delivery Creation Problem with multiple batches

I would appreciate if you can guide me if there is any BAPI or FM to create the inbound delivery (VL31N) with the multiple purchase orders and with the multiple batches for the materials.
Regards
Prasad

TRY THIS ONE.
BAPI_INB_DELIVERY_CONFIRM_DEC
*& Report ZZ_BAPI_OUTB_DELIVERY_CONF_DEC
REPORT ZZ_BAPI_OUTB_DELIVERY_CONF_DEC.
data HEADER_DATA like BAPIOBDLVHDRCON.
data HEADER_CONTROL like BAPIOBDLVHDRCTRLCON.
data DELIVERY like BAPIOBDLVHDRCON-DELIV_NUMB.
data HANDLING_UNIT_HEADER_CROSS type table of BAPIDLVHDUNHDR.
data gs_HANDLING_UNIT_HEADER_CROSS type BAPIDLVHDUNHDR.
data RETURN type table of BAPIRET2.
parameters:
* Delivery number
p_deliv like BAPIOBDLVHDRCON-DELIV_NUMB default '0080015271',
* External Handling Unit Identifikation
p_hunr like BAPIDLVHDUNHDR-HDL_UNIT_EXID default '60000000000000000000',
* Handling Unit Material Number
p_humat like BAPIDLVHDUNHDR-SHIP_MAT default '000000000000002387'.
* Work on clean data. Allways.
clear:
header_data,
header_control,
delivery,
gs_HANDLING_UNIT_HEADER_CROSS.
refresh:
HANDLING_UNIT_HEADER_CROSS.
* set data values
header_data-DELIV_NUMB = p_deliv.
header_control-DELIV_NUMB = p_deliv.
delivery = p_deliv.
gs_HANDLING_UNIT_HEADER_CROSS-DELIV_NUMB = p_deliv.
gs_HANDLING_UNIT_HEADER_CROSS-HDL_UNIT_EXID = p_hunr.
gs_HANDLING_UNIT_HEADER_CROSS-SHIP_MAT = p_humat.
append
gs_HANDLING_UNIT_HEADER_CROSS
to
HANDLING_UNIT_HEADER_CROSS.
* Call Function
CALL FUNCTION 'BAPI_OUTB_DELIVERY_CONFIRM_DEC'
EXPORTING
    HEADER_DATA                      = header_data
    HEADER_CONTROL                   = header_control
    DELIVERY                         = p_deliv
TABLES
    RETURN                           = return
    HANDLING_UNIT_HEADER_CROSS       = HANDLING_UNIT_HEADER_CROSS
commit work.
write: 'Finished'.
Edited by: pradeepvonti kumar on Nov 19, 2009 5:46 PM
Edited by: pradeepvonti kumar on Nov 19, 2009 5:48 PM

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?

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

Automatic Sales Order Creation from PO in B1

Hi,
I have this scenario. Purchase order is created in SAP B1 (Business One) which triggers automatic Sales Order creation in SAP ECC 6.0.
The requirement:
For the combination of PO number and Sold to party there should be only one sales order created.
The problem:
Sometimes for the same PO duplicate Sales orders(sometimes 3,4) are getting created in ECC.
Possible causes:
Probably no validations in the interface.
Question:
1. First of all, is it an SD issue or PI (process integration) issue.
2. If it is an SD issue, as a functional consultant what / where can we do to prevent this.
Thanks.
Edited by: SAP SD_Newbie on Oct 20, 2011 6:59 PM
Edited by: SAP SD_Newbie on Oct 20, 2011 6:59 PM
How do I move this to "ERP - Sales and Distribution (SD) General", because this question is not just related to "ERP SD Sales" but SD in general. Isn't there an option for the users to a question from one forum to another.

1. First of all, is it an SD issue or PI (process integration) issue.
- May be PI, or SD or both. I am not sure about the integration mechanism/program so I am not able to pinpoint.
2. If it is an SD issue, as a functional consultant what / where can we do to prevent this.
In t.code VOV8, go to the sales document type. Select value A in the field, check Purchase order Number. Then go to t.code OVAH, there make the message number V4 115 as error message. This will not allow the creation of the sales order, if the Purchase order number duplicates. I assume in your process, the purchase order number is populated in the PO number field of the sales order overview screen.
Regards,

Auto Inbound delivery creation

Hi Sapgurus,
I am trying to create Inbound delivery from Outbound delivery after it has been PGI'ed. These both are related to Intracompany STO. We have WM implemented so both of these deliveries result in TO creation and can be closed only after TO confirmations. I used SAP notes which stated to use SPED output type in output determination procedure for outbound delivery and then assign output determination procedure to delivery type. But I was not successful in getting the desired results.
Can anyone please provide me with the steps of this configuration, I may be doing wrong something somewhere.
Appreciate the help.
Thanks in advance
Manav Anand

Hi,
I think you are talking about stock transfer between two plants. I assume your requirement is after PGI of the replenishment delivery system should create automatic inbound delivery in second warehouse,right?
You can create inbound delivery automatically for second warehouse.I had such scenario in my previous client.I believe through some user exit you can initiate inbound delivery creation immediately.
Please check with your technical person.
Regards,
PRashant

Automatic Inbound Delievery

Dear All;
We have a problem with automatic inbound delivery not being created. In case of STO's for same company code between plants, we create an outbound delivery and do a shipment. After the shipment is saved, a PGI is created for sending plant and an automatic inbound delivery should be created at the Receiving plant. In our case after PGI, the inbound delv is not created. We are in 4.7 Version.
Is there any standard program which does this ?
Any pointers to find out why that is not being created would be greatly appreciated.
Thanks!!!!!

I am facing the same issue, did you figure out what was the reason and how did you fix it ?

Automatic excise invoice creation in STO scenario

Hi All,
This is related to stock transfer from Depot to manufacturing plant.
I have done the replenishment delivery at Depot. Now my requirement is automatic excise invoice creation. For that i have done the required settings like excise and series group. I have checked the Creation EI option in exciser group also.
PO(ME21n) --> VL10B --> VL02N --> VF01 (JEX) --> Automatic excise invoice once save the billing.
Once i sqve the billing, it has to create excise invoice at Depot. It is not happining.
Please let me know if i have to do any more settings.
Regards
Lakshmikanth

Dear Lakki,
Please check, whether for Defined Excise Group:
Path: SPRO --> IMG --> Logistics General --> Tax on Goods Movement --> India --> Basic Settings --> Maintain Excise Group
Select your Excise Group and Mark the Boxes: Create EI, and Box: Depot EIs.
Have you maintained relevant setings, like:
--> Had you checked the Box: Excise Inv during Billing, under Tab: Outgoing Excise Invoice
--> Relevant checks for Depot Settings, under Tab: Depot Settings
Best Regards,
Amit

Inbound delivery creation using VL31N

Hi All,
I could find that the message type DESADV, IDoc type DELVRY01 and process code DELS is used for creation of this.
Let me know if this is correct. When i checked in my system I could not find process code DELS. Do i need to do some additional settings to get this.
What is difference between IDOC type DELVRY01 and DELVRY03. Which one should be used.
Here the ASN received is triggering inbound delivery creation.
Please let me know on this.
Regards,
Shahu

Hi,
Where did you check that process code in WE64?
Check in the correct set(Inbound messages).
DELVRY03 is the latest one. You should use it only.
Regards,
Ravi

Check amount of transition stock during inbound delivery creation

I want to move stock between plans, therefore I have the following steps:
1. Stock Transfer Order (STO), e.g. 500 pieces
2. Sending plant: MIGO (GI for STO) with MT 351 to post to transition stock, e.g. 100 pieces
3. Receiving plant: Inbound Delivery with reference to STO VL31N
4. process Inbound delivery in warehouse (SAP-WM)
The question is:
During step 3, when accessing VL31N the system proposes the full order quantity (e.g. 500 pc.)
I can change the amount to any amount I like, e.g 240 pieces.
How can I tell SAP, that Inbound delivery creation is only possible for the amount
which has been posted to stock in transition (100 pieces)
I want an error/warning message in case user wants to create Inbound delivery quantity higher than the amount that has been posted to transition stock.
Any ideas?

MIGO in sending Plant?
How it is possible? MIGO means, Goods receipt. This should be in Receiving plant.
Sending plant should do the PGI
MIRO in receiving plant
Billing in sending plant
Payment from Receiving palnt and clearing in sending plant
Correct me if i am wrong
Thanks

ASN from vendor and inbound delivery creation

hi
I have a scenario where vendor sends ASN via EDI to R/3.
This inbound ASN should create an inbound delivery.
Can you please help me knowing the idoc type, message type etc which will serve my purpose.
Also the FM / Badi for inbound delivery creation.
thanks in advance,
Jo

Hi,
Use DESADV Message type and basic type DESADV01
Use function module IDOC_INPUT_DESADV
Edited by: Chandra Shekhar Singh on Jul 5, 2011 12:39 PM

Inbound Delivery creation in ECC6.0 through IDoc (DELVRY03.DESADV)

Inbound Delivery creation in ECC6.0 through IDoc (DELVRY03.DESADV)
From SCM ICH system Supplier creates ASN on the WEBUI & sends it ECC 6.0 using XI.
This is Proxy (DespatchedDeliveryNotification) to IDOC (DELVRY03.DESAV) scenario
But at the receiver end i.e. ECC6.0 its giving me error at Tcode WE02 as action is not supported.
Can you suggest me how to tackle this issue.
Thanks in Advance.
Regards,
N>B.Shanmukha

hi,
>>>giving me error at Tcode WE02 as action is not supported.
there are many segments in delvry03 with a first field - action (like, delete, create, 001,002, etc)
check all of them as probably you're using one which is not supported
and this is the real cause of the error
you can check it like this:
open this IDOC in We19
then open action field and F4 and see if the one you use in the idoc is in F4
change the wrong one and it will work :for 100%
Regards,
Michal Krawczyk

Automatically inbound delibery creation problem

Similar Messages

Maybe you are looking for