Using Different inbound delivery type?

Dear experts,
In the goods receipts process we currently are using the standard inbound delivery type "EL" with the standard item category ELN, which is not "Relevant for putaway".
We are assessing the possibility of start using WM in one of our plants. So, I found out that the we should be using a item category (in the inbound delivery) with the field "Relevant for putaway" flagged. Like, for example, the standard WIDN (maybe together with the standard inbound delivery type WID). But only at those plants with WM!
The issue is that as far as I know the inbound delivery type determination depends on the "Internal Confirmation Categories":
So for the type "2 Shipping Notification" only one delivery type can be chosen, how are we suppose to do it plant dependent?
It looks like a unique delivery type should be used in the client?
Thanks in advanced,
Fortian
P.S.: I already read SAP notes 214604 & 201655 but they are not being helpful so far... Maybe I'm missing something.

From your post I understand that the current plants are IM managed.
So for these plants the put away relevancy will not have any effect so if you enable the put away relevancy for the EL delivery type there will be no impact on the IM plants and for the WM plant the put away will be relevant.
Now the usage of the put away relevancy will also depend on which transaction you are using for posting a goods receipt. If you post via VL32N then you will first have to perform the put away step and then the GR posting. If you use the MIGO/MIGO_GR transaction then the goods receipt in WM will also be posted before the put away happens.

Similar Messages

Different Inbound Delivery Type

Hi All,
I have a requirement to create a new inbound delivery type ZSL for stock transfers for my client.
Only way to assign the inbound delivery type is through confirmation control category.
But in the config, only one inbound delivery type could be assigned to LA Confirmation control category.
We already have an inbound delivery type ZEL used for receipt against external Vendor assigned to LA.
How do I assign the other delivery type ZSL. Or is there another way to make this happen ? So that when I create the inbound delivery for stock transfers, delivery type determined is ZSL.
Any help is appreciated.
Regards,
Ankur

there is no solution in standard system, but SAP created a note with a modification which might help you to achieve your goal, see OSS note 214604 - Workaround for inbound delivery item type determination

Several Inbound Delivery types in one plant?

Hi Guru´s,
1. Is it possible to have several inbound delivery types and also to be able to use all inbound delivery types in one plant at the same time but in different process?
E.g:
1a. I have plant with a sloc and WM connected which I would like to have inbound delivery with picking connected to it
1b. I have the same plant with only sloc connected and would like to have inbound delivery without picking and confirmation of the inbound delivery to be set (PGI)...
2.Is above scenario possible to have?
3.If please guide me on how the correct way is to have this set up because I´m stuck...
4.If not please explain why it is not possible or....
5.Is there anouther way of doing it due to we would like to have the same process in every warehouse...
Thank You in advance to clear things out for me!
BR,
Christian

Hello Christian,
Yes it is possible to use delivery types based on your requirements as mentioned by you.
You will require to customize following things ;
Define delivery Type
SPRO>>Logistics Execution>>Shipping>>Deliveries>>Define Delivery Types.
You can use standard delivery type and create new customized ones by copying them.
Define Item categories for deliveries
SPRO>>Logistics Execution>>Shipping>>Deliveries>>Define Item Categories for Deliveries
Once item categories are defined, you have to assign the item categories to relevant document types.
Now you have to customize for picking and packing control
Picking control;
SPRO>>Logistics Execution>>Shipping>>Picking>>Define Relevant Item Categories
Packing control;
SPRO>>Logistics Execution>>Shipping>>Packing
Br,
Tushar

How to create a Inbound delivery type for a special purchase order type

Hi,
I try to create a special Inbound delivery type for a special purchase order type (a transfer purchase order).
In SD module, I can créate a special outbound delivery and precise the sale order type, but I don't manage to do it for a Inbound delivery type.
Do you know if i can do it without specifiq?
Regards,
Roselyne

Hi Roselyne,
What you experienced is standard system behavior. Inbound delivery type is uniquely assigned to confirmation control key. You can only specify confirmation control key on item level in PO. The assignment of Delivery type can be seen in the following table:
T163D
IBTYP EBTYP LFART RETDLV
1        AB                      X
2        LA        EL           X
3        GW       EG
The field T163D-IBTYP is checked in different programms. For example in programm RM06ENAB (TA: ME92F). If you insist to customize the determination of delivery type by PO type, I strongly suggest you discuss with the Application consultants before making the modifications to ensure it won't impact other areas.

New inbound delivery type creation???

Hi,
May I create a new inbound delivery type instead the standard EL?
If not, which enhancement can be used to change the item category ELN to another self-defined category during inbound delivery creation via VL31N?
Kindly please advise.
Thanks!

Hi
yes you can create a new Inbound delivery & change the Item category
Create new inboun delivery type in
SPRO-> IMG-> Logistics Execution-> Shipping-> Deliveries-> Define Delivery Types
Maintain the Combination of Item category & delivery type in
SPRO-> IMG-> Logistics Execution-> Shipping-> Deliveries->Define Item Category Determination in Deliveries
Thanks & Regards
Kishore

Is it possible to do message mapping using different namespace message type

Hi all,
Is it possible to do message mapping using different namespaces message types
Example :
i am having message type MT_1 in namespace http://sap.com/abc
and second message type MT_2 in namespace http://partner.com/xyz
so MT_1 can be mapped with MT_2 or not having different namespace.
Thanks

Read through my reply in this thread for Defining Software component dependencies.
Though it explains this for Improted Archives, it also holds true for Message Types to be used in message mappings.
Re: Payload Extraction
Regards
Bhavesh

New inbound delivery type

Hi all,
We have a requirement to create a new PO type and link this to a new Inbound delivery type (copy of EL) as part of a new business process. I am led to believe that this is not supported by SAP. Can any clarify please as trawling OSS has not revealed anything.
Rgds
C

Hi,
also check
Go to SPRO->MM->Purchasing>Confirmation>Setup confirmation control
Select the 10 and check the check box Create inb delivery
then select the line and click on the confirmation seq and make GR relevant, MRP relevant and GR assign (all three box checked)
Process Flow: -
1. ME21N - In PO, Confirmation Tab, select the confirmation control key as "Shipping Notification" or "Inbound Delivery"
2. VL31N - Create Inbound Delivery w.r.t. PO
3. MIGO - Goods Receipt > Inbound Delivery
If you don't select the conformation control key in the PO than system wont allow you to create the Inbound delivery against the PO.
Rahul.

Senarious for using different internal table types

please give scenarios for using different internal table types?

Refer to the following.
Internal table types
This section describes how to define internal tables locally in a program. You can also define internal tables globally as data types in the ABAP Dictionary.
Like all local data types in programs , you define internal tables using the TYPES statement. If you do not refer to an existing table type using the TYPE or LIKE addition, you can use the TYPES statement to construct a new local internal table in your program.
TYPES <t> TYPE|LIKE <tabkind> OF <linetype> [WITH <key>]
[INITIAL SIZE <n>].
After TYPE or LIKE, there is no reference to an existing data type. Instead, the type constructor occurs:
<tabkind> OF <linetype> [WITH <key>]
The type constructor defines the table type <tabkind>, the line type <linetype>, and the key <key> of the internal table <t>.
You can, if you wish, allocate an initial amount of memory to the internal table using the INITIAL SIZE addition.
Table type
You can specify the table type <tabkind> as follows:
Generic table types
INDEX TABLE
For creating a generic table type with index access.
ANY TABLE
For creating a fully-generic table type.
Data types defined using generic types can currently only be used for field symbols and for interface parameters in procedures . The generic type INDEX TABLE includes standard tables and sorted tables. These are the two table types for which index access is allowed. You cannot pass hashed tables to field symbols or interface parameters defined in this way. The generic type ANY TABLE can represent any table. You can pass tables of all three types to field symbols and interface parameters defined in this way. However, these field symbols and parameters will then only allow operations that are possible for all tables, that is, index operations are not allowed.
Fully-Specified Table Types
STANDARD TABLE or TABLE
For creating standard tables.
SORTED TABLE
For creating sorted tables.
HASHED TABLE
For creating hashed tables.
Fully-specified table types determine how the system will access the entries in the table in key operations. It uses a linear search for standard tables, a binary search for sorted tables, and a search using a hash algorithm for hashed tables.
Line type
For the line type <linetype>, you can specify:
Any data type if you are using the TYPE addition. This can be a predefined ABAP type, a local type in the program, or a data type from the ABAP Dictionary. If you specify any of the generic elementary types C, N, P, or X, any attributes that you fail to specify (field length, number of decimal places) are automatically filled with the default values. You cannot specify any other generic types.
Any data object recognized within the program at that point if you are using the LIKE addition. The line type adopts the fully-specified data type of the data object to which you refer. Except for within classes, you can still use the LIKE addition to refer to database tables and structures in the ABAP Dictionary (for compatibility reasons).
All of the lines in the internal table have the fully-specified technical attributes of the specified data type.
Key
You can specify the key <key> of an internal table as follows:
[UNIQUE|NON-UNIQUE] KEY <col1> ... <col n>
In tables with a structured line type, all of the components <coli> belong to the key as long as they are not internal tables or references, and do not contain internal tables or references. Key fields can be nested structures. The substructures are expanded component by component when you access the table using the key. The system follows the sequence of the key fields.
[UNIQUE|NON-UNIQUE] KEY TABLE LINE
If a table has an elementary line type (C, D, F, I, N, P, T, X), you can define the entire line as the key. If you try this for a table whose line type is itself a table, a syntax error occurs. If a table has a structured line type, it is possible to specify the entire line as the key. However, you should remember that this is often not suitable.
[UNIQUE|NON-UNIQUE] DEFAULT KEY
This declares the fields of the default key as the key fields. If the table has a structured line type, the default key contains all non-numeric columns of the internal table that are not and do not contain references or internal tables. If the table has an elementary line type, the default key is the entire line. The default key of an internal table whose line type is an internal table, the default key is empty.
Specifying a key is optional. If you do not specify a key, the system defines a table type with an arbitrary key. You can only use this to define the types of field symbols and the interface parameters of procedures . For exceptions, refer to Special Features of Standard Tables.
The optional additions UNIQUE or NON-UNIQUE determine whether the key is to be unique or non-unique, that is, whether the table can accept duplicate entries. If you do not specify UNIQUE or NON-UNIQUE for the key, the table type is generic in this respect. As such, it can only be used for specifying types. When you specify the table type simultaneously, you must note the following restrictions:
You cannot use the UNIQUE addition for standard tables. The system always generates the NON-UNIQUE addition automatically.
You must always specify the UNIQUE option when you create a hashed table.
Initial Memory Requirement
You can specify the initial amount of main memory assigned to an internal table object when you define the data type using the following addition:
INITIAL SIZE <n>
This size does not belong to the data type of the internal table, and does not affect the type check. You can use the above addition to reserve memory space for <n> table lines when you declare the table object.
When this initial area is full, the system makes twice as much extra space available up to a limit of 8KB. Further memory areas of 12KB each are then allocated.
You can usually leave it to the system to work out the initial memory requirement. The first time you fill the table, little memory is used. The space occupied, depending on the line width, is 16 <= <n> <= 100.
It only makes sense to specify a concrete value of <n> if you can specify a precise number of table entries when you create the table and need to allocate exactly that amount of memory (exception: Appending table lines to ranked lists). This can be particularly important for deep-structured internal tables where the inner table only has a few entries (less than 5, for example).
To avoid excessive requests for memory, large values of <n> are treated as follows: The largest possible value of <n> is 8KB divided by the length of the line. If you specify a larger value of <n>, the system calculates a new value so that n times the line width is around 12KB.
Examples
TYPES: BEGIN OF LINE,
COLUMN1 TYPE I,
COLUMN2 TYPE I,
COLUMN3 TYPE I,
END OF LINE.
TYPES ITAB TYPE SORTED TABLE OF LINE WITH UNIQUE KEY COLUMN1.
The program defines a table type ITAB. It is a sorted table, with line type of the structure LINE and a unique key of the component COLUMN1.
TYPES VECTOR TYPE HASHED TABLE OF I WITH UNIQUE KEY TABLE LINE.
TYPES: BEGIN OF LINE,
COLUMN1 TYPE I,
COLUMN2 TYPE I,
COLUMN3 TYPE I,
END OF LINE.
TYPES ITAB TYPE SORTED TABLE OF LINE WITH UNIQUE KEY COLUMN1.
TYPES: BEGIN OF DEEPLINE,
FIELD TYPE C,
TABLE1 TYPE VECTOR,
TABLE2 TYPE ITAB,
END OF DEEPLINE.
TYPES DEEPTABLE TYPE STANDARD TABLE OF DEEPLINE
WITH DEFAULT KEY.
The program defines a table type VECTOR with type hashed table, the elementary line type I and a unique key of the entire table line. The second table type is the same as in the previous example. The structure DEEPLINE contains the internal table as a component. The table type DEEPTABLE has the line type DEEPLINE. Therefore, the elements of this internal table are themselves internal tables. The key is the default key - in this case the column FIELD. The key is non-unique, since the table is a standard table.
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb35de358411d1829f0000e829fbfe/content.htm

L9 528 - Material cannot be used in Inbound Delivery because QM is active

Hi Colleagues,
So we have HUM products going into a warehouse managed location and we know that we cannot create an inbound delivery for these items if QM is active without 'HU inspection' selected in the QM inspection type of the material master
So the question
Is there anyway round this so that we can trigger the inspection lot creation at the goods receipt posting rather than at the HU level in the packing of the inbound delivery
Does anyone know if SAP plan to support this in the future?
Thanks
Steve

We are not using HUM however using WM. Nonetheless, the problem persist while creating inbounds.
We are trying to use the following approach to address this problem.
uncheck 'relev. for putaway' indicator from 'ELN' item category thus enabling VL31N to by-pass the hard stop incurred due to QM activation.
SAP's reason for this hardstop is to avoid inconsistencies that may arise when TO's are created for inbound deliveries before GR is posted. This scenario does not pertain to us since TO for inbounds before GR is not applicable. Therefore, we are enabling the above configuration. By doing this, we are breaking the link between inbound delvy's and WM, and thus disabling the functionality of creating TO's referencing inbound delvy's (transactions like LT03, LT0F become irrelevant).
But, this process will not work if we implement HUM since standard SAP will not allow to create a putaway TO referencing a TR or a material document. It becomes imperative to create a TO referencing a delvy, but this configuraton will break that link hence it will not work.
Best Regards.

Choose the Inbound delivery type for STO process

Hey guys,
I am struggling with this process.
For STO process we are going to use SPED output type to create the Inbound delivery automatically after O/B delivery PGI.
The thing is I do not want the I/B Delivery type to be EL. Cause we are using HUM. I want it to be HID.
I can't find where in config I can't set up the system to choose HID rather than EL.
Does anyone have an idea?
Cheers Guys

Hi,
Thanks for your answer. But what you are describing is more for PO (external purchase) not STO.
What I want is to control the I/B delivery type that get created after PGI of the O/B delivery via the output type SPED (special function).
Cheers
Julien

Customized Inbound Delivery Type

Hello All
My client wants to have a new delivery type than standard as he wants to identify the deliveries easily with different number ranges. We can created new delivery type under LE--> Shipping > Deliveries>Define Delivery types.
Where can i link that for the purchase order document NB my new inbound delivery should be created.
Request you to let me know the steps to link the same.
Regards
Sameer

SPRO>MM>Purchasing>Purchase Order>Set up Stock Transport Order--->Assign Delivery Type and Checking Rule
BR,
Krishna

Problem using different Map key types in one class

I'm running Kodo 2.3.3. It seems I can only have one Map key types for all
maps in a class. For example, if I have two maps in a class, their keys
must be of the same type.
Is there a plan to remove this limitation soon?
Thanks,

Abe White wrote:
Kodo should generate a separate table for each Map. We have internal tests
that use classes with Map fields using a lot of different key/value type
combinations, so there shouldn\'t be a problem.It looks like two maps (keyValues and versions) are sharing the same
table. Here is the table generated by schematool (db: Oracle 8.1.7):
desc persistentmotiveresourcebean_x;
Name Null? Type
ID_JDOIDX VARCHAR2(255)
JDOKEYX NUMBER
KEYVALUESX VARCHAR2(255)
VERSIONSX VARCHAR2(255)
==========================================================================
Following is the simplified code I run:
-----------internal.jdo--------------------------------------
<?xml version=\"1.0\"?>
<jdo>
<package
name=\"com.motive.services.resourceManagementService.internal\">
<class name=\"PersistentMotiveResourceBean\"
identity-type=\"application\"
objectid-class=\"com.motive.model.PrimaryKey\">
<field name=\"id\" primary-key=\"true\"/>
<field name=\"versions\">
<map key-type=\"java.lang.Float\"
embedded-key=\"true\" value-type=\"java.lang.String\"
embedded-value=\"true\"/>
</field>
<field name=\"keyValues\">
<map key-type=\"java.lang.String\"
embedded-key=\"true\" value-type=\"java.lang.String\"
embedded-value=\"true\"/>
</field>
</class>
</package>
</jdo>
Java source:
-----------PersistentMotiveResourceBean.java---------
package com.motive.services.resourceManagementService.internal;
import java.util.HashMap;
public class PersistentMotiveResourceBean
private String id;
private String name;
private HashMap versions;
private HashMap keyValues;
public PersistentMotiveResourceBean()
public String getId() { return id; }
public void setId(String id) { this.id = id; }
public String getName() { return name; }
public void setName(String name) { this.name = name; }
public HashMap getVersions() { return versions; }
public void setVersions(HashMap versions) { this.versions = versions; }
public HashMap getKeyValues() { return keyValues; }
public void setKeyValues(HashMap keyValues) { this.keyValues =
keyValues; }
----------------PrimaryKey.java-------------------------------------
package com.motive.model;
import java.io.Serializable;
public class PrimaryKey implements Serializable
public String id;
public PrimaryKey ()
public PrimaryKey (String id)
this.id = id;
public boolean equals (Object ob)
if (this == ob) return true;
if (!(ob instanceof PrimaryKey)) return false;
PrimaryKey o = (PrimaryKey) ob;
return (this.id == o.id);
public int hashCode ()
return id.hashCode();
public String toString ()
return id;

Trigger output on Inbound Delivery Type

Hello,
I'd like to know if it's possible to trigger output on Inbound Delivery Item in SAP ERP. Reason I ask is that we want to trigger a label printout for every delivery item during goods receipt of the inbound delivery.
I know I can trigger output on Inbound Delivery Header, but not sure how to get a printout per delivery item.
Can anyone let me know if it's possible, and if so, how to set this up?
Regards,
Oliver

Hi,
I am not experienced in printing, and at first glance this does look difficult...
Because in customizing you have two separate paths...
The path given above from Warren, and then it splits:
- Maintain Output Determination for Outbound Deliveries
- Assign Output Determination Procedure
- Maintain Output Determination for Inbound Deliveries
- Assign Output Determination Procedure
Now the difference in these two paths is that:
- if you select the first one, you get a pop-up giving you a choice to "Assign Deliveries (header)" and "Assign delivery items",
- if you select the second one, there is no further selection, you only see delivery types, and this is also filtered, only inbound deliviery types are shown.
So it seems not possible.
BUT: if you select the "Assign delivery item" option in the first path, you see ALL item types; also for inbound. So test it there, hope it works. (I suppose now that you know how to print, have all the determination, etc - yes, you wrote that you know it for outbound).
Brgds
Juergen

No Weight and Volume in inbound delivery type EL

Where do I set the copy control to bring the weight an volume into a delivery type EL that is created from a vendor PO type NB?

Hi Julie,
Please check if weight and volume is maintained in material master for the delivery material. If not maintained pl maintained and then create the delivery.
Hope it'll help.
Regards,
Sudhir

Different delivery type for inbound delivery

Hi,
Somebody knows if it is possible to assign diferent delivery types for inbound delivery from differents document type of PO?
for example, delivery type EL for "NB" PO and delivery type "ZEL" for UB (Stock Transp. Order).
thanks
RZ

Dear,
Check: Different inbound delivery types from PO conf control keys
Regards,
Syed Hussain.

Using Different inbound delivery type?

Similar Messages

Maybe you are looking for