ItemRequirement & Distrbtn Mode IN ovlk

[Former Member]

experts please share some business process on this fields and when to use this 2 fields.

In defining delivery doc types OVLK we have a field ItemRequirement.

List of permitted routines

Routine

000 Text not maintained

001 Header

002 Header Correction

003 Header Contract

051 Combination

101 Item

102 Item w/o transport

151 Combination

201 No ord.w.indep.item

202 Order w.indep.item

In our company we are using 201.can experts tell when we need to have each one of the above..

please give me atleast one line description for each requirement, that is a great help to me in understanding the business requirement.

There is another field Distrbtn Mode -

we have following as a drop down ..

distrubution control by warehouse number,stop distribution,distribution at delivery creation.

please share the business scenario when we need to use which one of this

[Former Member · Accepted solution]

Dear,

Item Requirement field is for

Identifies a requirements routine for a delivery item that does not refer to a sales document. The delivery item must meet the requirements of the routine before it can be further processed.

Regards,

Kapil

[Former Member · Accepted solution]

experts views needed please

[ravi_kumar100 · Accepted solution]

Hi,

Check out this thread for your understanding to use as per business need.

DELIVERIES COPYING REQUIREMENT 1: HEADER

This is the standard delivered copy requirement to verify that the preceding sales order header is

valid for delivery. Specifically, the following attributes of the sales order are checked: credit block,

user status and global delivery flag. If there are any blocks or the status check reveals an

incompatible entry, copying is not permitted.

Example:

When using credit management, it is logical that a delivery should not be created for a credit blocked

order until the credit manager has reviewed the situation and determined that the document can be

released. In order to prevent a delivery from being created if it still contains a credit block, this

requirement can be assigned to the delivery header copy routine for the sales order.

DELIVERIES COPYING REQUIREMENT 2: HEADER CORRECTION

This requirement has the same checks as the standard delivered copy requirement '01' that verifies

that the preceding sales order header is valid for delivery. Additionally, this requirement checks that

the preceding document is a rush order. The standard checks performed are: credit block check, user

status check and global delivery flag check. If there are any blocks or the status check reveals an

incompatible entry, copying is not permitted.

Example:

If your company allows the immediate pick-up of goods upon order placement, rush orders can be

implemented to facilitate this process. In this process, deliveries are created automatically when the

sales order is saved. In order to insure that the delivery is not created for credit blocked items, this

requirement can be assigned to the appropriate rush order delivery type to have the standard checks performed.

DELIVERIES COPYING REQUIREMENT 3: HEADER CONTRACT

This requirement verifies that the preceding document is either an order or a contract, prior to

permitting copying. Additionally, the following attributes of the reference document are checked:

credit block, user status and global delivery flag. If there are any blocks or the status check reveals

an incompatible entry, copying is not permitted.

Example:

If your company delivers services to your customers, these can be established in the R/3 system as

service or maintenance contracts. This requirement can be assigned to the debit memo request for

the contract to insure that the delivery is not created if there are any credit or user blocks present in the Contract itself.

DELIVERIES COPYING REQUIREMENT 51: COMBINATION

This requirement determines if sales documents can be combined in one delivery document.

Specifically, the following attributes of the sales document must be identical: delivery type, sales

organization, full delivery rules, and billing type. If any of these entries are not identical,

combination is not permitted.

Example:

When using collective processing to create deliveries, it is possible to combine multiple orders into

one delivery document. In order to prevent incompatible orders from being combined together, this

requirement can be assigned to the delivery copy routine to insure that only valid documents are

combined.

DELIVERIES COPYING REQUIREMENT 101: ITEM

This requirement checks specific attributes of the reference sales document item prior to permitting

the line to be copied. Specifically, the following attributes of the reference document items are

checked: delivery relevance, incompletion status, delivery completeness, shipping point, batch, credit

block, credit check, user status and export data. If there are any blocks, or the status check reveals an

incompatible entry, copying of the affected line is not permitted.

Example:

All line items in a delivery note must share the same shipping point. In order to insure this, this

requirement is assigned to the appropriate delivery item category copy rule.

DELIVERIES COPYING REQUIREMENT 102: ITEM W/O TRANSPORT

This requirement checks specific attributes of the reference sales document item for non-stockable

items / text items prior to permitting the line to be copied. Specifically, the following attributes of

the non-stockable items are checked: delivery relevance, incompletion status, and delivery

completeness. If there are any blocks, or the status check reveals an incompatible entry, copying of

the affected line is not permitted.

Example:

A sales order is created with material as well as text items. When creating a delivery that will

contain the text items, different checks should be performed against the text item than those that are

done for material (stockable) items. In order to have standard checks such as consistent shipping

points removed from the check for item text transfer, this requirement can be assigned to the item

category copy rules for the non-stockable items (text) as an item copy requirement.

Regards,

Ravi

Edited by: ravi kumar on Dec 8, 2009 12:37 PM

[ravi_kumar100 · Accepted solution]

Hi,

Delivery Requirement Routines Continued:

DELIVERIES COPYING REQUIREMENT 151: COMBINATION

This requirement checks whether additional items can be added manually to an existing delivery

using the 'deliver order' functionality. If the addition of new items is permitted, the following fields

must be consistent in the new items as compared with the existing delivery items: incoterms,

payment guarantee procedure, financial document number, letter of credit data, and customer group.

If there are any incompatible entries, copying is not permitted.

Example:

When changing an existing delivery, the 'deliver order' functionality can be used to bring in

additional relevant order lines from the specified sales document. In order to insure that only items

with consistent incoterms and other risk management identifiers are selected, this requirement can be

assigned to the delivery item category.

DELIVERIES COPYING REQUIREMENT 201: CANNOT ADD ITEMS THAT DO NOT

REFERENCE AN ORDER

This requirement is used to indicate that items which do not reference an order cannot be manually

added to a delivery. No additional validation checks against the items are performed.

NOTE: This requirement is delivered as a sample and is not used in any standard copy scenarios.

Example:

If a delivery was created with reference to a sales order, company policy states that no additional

items can be added to the delivery. In order to prevent users from manually adding items in a

delivery, this requirement can be assigned to the appropriate delivery.

DELIVERIES COPYING REQUIREMENT 202: ITEM WITHOUT A REFERENCE TO AN

ORDER

This requirement is used to indicate that items that do not reference a sales order can be manually

added to a delivery if specific validation checks are passed. Specifically, if the delivery has already

been goods issued and invoiced, no new items can be added.

NOTE: This requirement is delivered as a sample and is not used in any standard copy scenarios.

Example:

If a delivery was created with reference to a sales order, company policy states that additional items

can be added to the delivery as long as the delivery has not yet been invoiced. This requirement can

be assigned to the appropriate delivery copy rules to permit the addition of new items in the delivery documents.

Have a Nice Day.

Regards,

Ravi

[former_member396676]

Hi,

Go to T-code VOFM.

Click on Copying requirements- select deliveries

You would see list of item requirements.

Select any one of them and hit F5 or F6. You would find detailed description of the same.

Thanks,

Vrajesh

[Former Member]

please help with business scenarios when to use which requirement.