Fields in VOV8

[Former Member]

Please tell me the functionality of the following fields in VOV8

1. Risk Management

2. Material entry Type

3. Output Application

4. Commitment date

5. Status Profile

6. Varient

7. Use(Scheduling agreement)

8. Shipment cost information profile

9.Condition type line items

10. Data type

11. Product attribute Messages

12. Scheduling agreement Fields.

13. Correction Delivery type

14. Delivery block

15. Use

16. MRP for delivery Scheduling type.

Please tell me even if you know the usage of only some fields .

Points guaranteed!!!!

Venkat

[Former Member]

> Please tell me the functionality of the following

> fields in VOV8

>

> 1. Risk Management

>

<b> 2. Material entry Type</b>

>Material entry

Controls how the entry field for the material or material order number should be interpreted in the sales order.

3. Output Application

<b> 4. Commitment date</b>

Commitment dates switch for calculation rule

Key that controls how the commitment quantities should be calculated per sales document type.

Use

The commitment date is calculated using the delivery time for releases to contracts with delivery times, or sales orders that refer to quotations containing delivery times. The committed quantity results from the agreed delivery time or the confirmed quantity, according to the calculation rule set here.

Dependencies

You can set the following calculation rules:

A: Consider agreed delivery time

Here, all required schedule lines are committed for the date that lies at the agreed distance from the delivery time, according to the date on which the order was placed. If the customer requests a later date, this can be confirmed. The confirmation does not affect the calculation. If you do not enter a delivery time, the system does not calculate a committed quantity.

B: First confirmation date

The committed quantity is calculated according to the first confirmed quantities. If a delivery time exists for the item, the system takes it into account, as in calculation rule A, and confirms the earlier date. The commitment date is recalculated if the material, quantity, first date, or delivery time change. The quantities confirmed then are valid once the document has been saved.

C: First confirmation date

Rule C is the same as calculation rule B but for new items. If you save a document again but the system can confirm more for the customer, the more favorable situation will be saved as the commitment. As in rule B, the commitment date will be recalculated if changes are made to the material, quantity, requested delivery date, or delivery time.

No entry

Commitment dates are not calculated or displayed

<b>5. Status Profile</b>

Status profile

Cross-Application Components (CA)

A profile used to control user statuses.

A status profile is created by the user in general status management.

In a status profile you can:

Define the sequence in which user statuses can be activated

Define initial statuses

Allow or prohibit certain business transactions

Case Management (BC-SRV-CM)

Customizing setting that determines the possible status values and status transfers of a case.

One status profile is assigned to each case.

Industry-Specific Components for Hospitals (IS-H)

A customer-defined number of user statuses and rules relating to Basic Medical Documentation.

<b> 6. Variant</b>

Transaction variant

> 7. Use(Scheduling agreement)

Usage indicator

Defines how the material is used.

Use

The usage defines the conditions under which a material is sold. It can be entered at item or header level. Entries made at header level are valid for all items.

The same material, but with different uses, can be sold to the same customer in separate items or orders.

Procedure

Enter whether the material is:

A spare, or replacement part

A sample

Part of a series, used in repetitive manufacturing

> 8. Shipment cost information profile

Shipment Cost Information Profile

The shipment cost information profile contains proposal values for the shipment cost information in the sales order, such as the transportation planning point, the shipment type and the shipment cost pricing procedure. You can also assign different transportation planning profiles to a shipment cost information profile. These profiles are used to carry out different options for shipment cost determination (deliveries are combined differently, or a different mode of transport is used) You can change the proposal data in the shipment cost information.

> 9.Condition type line items

Condition type for copying costs from line items

This is where you enter the condition type which you want to use to determine the results of the sales order pricing for a sales and distribution document item.

Use

If you enter the condition type into the requirements class, this condition type is used for all sales and distribution document items containing a requirements type, which indicates this requirements class.

The definition of the condition type per requirement class allows you to determine different condition types for the different items of a sales and distribution doc. For example, you could carry out pricing for one item on the basis of a sales order pricing procedure, while the value of the sales order pricing might only be forwarded statistically for another item in the same document. The sales order costing refers to the sales order item.

If you enter the condition type into the sales document type, this condition type is used for all items in a sales document of this sales document type.

In the standard version of the SD system, two condition types are provided for the cost transfer of line items:

EK01

If you choose this condition type, the result of the sales order costing is first printed to the pricing screen for the item. The value can be used as the basis for price computation.

EK02

If you choose this condition type, the result of the sales order costing is simply a statistical value, which you can compare with the price.

Dependencies

Take the following points into account:

The condition type must have condition category 'Q' (costing).

The condition type must agree with the condition typ

> 10. Data type

Date type (day, week, month, interval)

Identifies the date type internally in the system.

Use

When you create schedule lines for a sales document, you can specify different formats for the delivery date (day, week, or month). This indicator enables the system to refer to a particular format, independent of the language in which it appears on the user interface.

> 11. Product attribute Messages

>

> 12. Scheduling agreement Fields.

>

> 13. Correction Delivery type

>

> 14. Delivery block

Delivery block (document header)

Indicates if an entire sales document (a sales order, for example) is blocked for delivery.

Procedure

The system can propose the delivery block indicator according to sales document type. You can also enter a block manually in the header. A block in the header applies to the entire document. If you want to block one or more specific items, you can enter the block at item level.

The delivery block at header level is only effective if this block is assigned to the corresponding delivery type in the Customzing table (TVLSP). Regardless of the settings in Customizing, the delivery block is always effective at schedule line level.

Example

You can block delivery automatically for certain sales document types (for example, free of charge deliveries) where it is important that someone checks the details before shipping takes place.

Dependencies

If you use a credit limit check, the system can automatically block delivery. You can change this block. However, as soon as you change any of the values in the sales document, the system automatically reapplies the delivery block.

> 15. Use

>

> 16. MRP for delivery Scheduling type.

>

> Please tell me even if you know the usage of only

> some fields .

>

> Points guaranteed!!!!

>

> Venkat

[Former Member]

2. Material entry Type

· The value of this field determines product catalog if the material exists in any product catalog and also it determines the entry of material in the sales order. If the material exists in any product catalog then the system automatically determines the relevant product catalog.

3. Output Application

· Identifies the applications from which output can be sent (for example, sales order processing or invoice processing). The output is divided according to output types and assigned to these applications.

· Assign application area of the sales documents to determine the outputs that the system automatically proposes while defining output determination procedure in IMG.

4. Commitment date

· Key that controls how the commitment quantities should be calculated per sales document type.

· The commitment date is calculated using the delivery time for releases to contracts with delivery times, or sales orders that refer to quotations containing delivery times. The committed quantity results from the agreed delivery time or the confirmed quantity, according to the calculation rule set here.

5. Status Profile

· Same functionality as the authorization group in customer master table.

· In IMG we can define status profile in which we can maintain the sequence of user status that can be activated, initial statuses and what kind of transactions which are prohibited or allowed.

6. Varient

· With the help of the technical consultants, screen variants can be defined to hide some tabs in the sales order during sales order processing by default, depending upon the transaction types.

· Ex.: Small_Sales_Variant, whenever this variant is used only ‘Item Overview’ tab in the sales document appears all the other tabs do not appear.

7. Use(Scheduling agreement)

In scheduling agreements one material can be given with different usages.

· The usage can be specified at the header level that applies to all line items in the scheduling agreements.

· The usage defines the conditions under which a material is sold. It can be entered at item or header level. Entries made at header level are valid for all items.

8. Shipment cost information profile

· In IMG, Shipping cost info profile can be defined in which we can define transportation planning point, Shipping cost calculation procedure, shipment type etc. can be assigned for carrying out shipment and transportation with reference to this sales document.

· The shipment cost information profile contains proposal values for the shipment cost information in the sales order, such as the transportation planning point, the shipment type and the shipment cost pricing procedure.

9.Condition type line items

· In business, pricing can be carried out based on sales order line item costing and also by following methods:

o Product Costing: It is going to be carried out based on sales order BOM which could be part of super BOM.

o Unit Costing: In this sales order line item cannot be participated.

· If it is a product cost, then condition type EK01 and EK02 can be used as a base to calculate price.

10. Data type

· Assign date format that system automatically uses to propose date in sales document.

· Identifies the date type internally in the system.

· When you create schedule lines for a sales document, you can specify different formats for the delivery date (day, week, or month). This indicator enables the system to refer to a particular format, independent of the language in which it appears on the user interface.

11. Product attribute Messages

· The value of this field determines the system response if the product attributes are going to be changed during sales order processing if the product is copied from the preceding document.

· There will be a warning or an error message during the sales order processing.

· Enter an indicator here if you want to check whether the ship-to party accepts the attributes of a product which is entered manually in a sales document.

Scheduling agreement Fields

13. Correction Delivery type:

· Assign delivery document type LFKO – Correction Delivery Type for scheduling agreement types to correct the deliveries in scheduling agreement.

· System automatically proposes this delivery document type when the user initiates correction deliveries with reference to this scheduling document types.

14. Delivery block

· Delivery block can be assigned at scheduling agreement document header level. So that system proposes delivery block for all items in the scheduling agreement as some one in the business has to check scheduling agreement before initiating outbound deliveries.

· Field for setting a delivery block when the tolerance check in the scheduling agreement is not successful, meaning a tolerance limit (percent, quantity, days) was not met or exceeded.

15. Use

· In scheduling agreements one material can be given with different usages.

· The usage can be specified at the header level that applies to all line items in the scheduling agreements.

· The usage defines the conditions under which a material is sold. It can be entered at item or header level. Entries made at header level are valid for all items.

16. MRP for delivery Scheduling type.

· The value of this field determines whether MRP check should be carried out for scheduling agreement document types.

· Specifies whether forecast delivery schedules or JIT delivery schedules are relevant for planning and/or delivery.

Regards

AK

Reward points if helpful

[Former Member]

hi,

<b>Material Entry type</b>: the value of this field determines how the material can be entered in sales order. i.e. specifying material number or product catalogue number.

<b>Commitment date</b>: the value of this field specifies the commitment date for the sales order line items.

<b>Status Profile</b>: in IMG status profile is used to define the system status and user status for this sales doucment type.

<b>Variant</b>: in IMG we define variants with help of ABAPERS. EX: screen variants by which default values , default tabs can be proposed for a sales document types

<b>USE:</b> in scheduling agreements one material can be given with different usages the usage can be specific at the header level that applies to all the line items in the schedulling agreements.

<b>Product attribute messages</b>: the value of this field determines system responses if the product attributes are going to be cahnged during sales order processing whether warning or error messages

<b>Shipment cost info profile</b>: Ex: standard, in img we define the shipping cost info profile in which we can specify transactions like planning point,shipping type, shipment cost calculation procedure etc, this is used by the system for shipment and transportation

<b>condition type line items</b>: assign condition types that is used by system as a base for carrying out pricing based on the sales order line item cost

<b>correction delivery type</b>: assign delivery document type LFKO for scheduling agreement types to correct the deliveries in scheduling agreement.

system automatically proposes this delivery document type when the user initate correction deliveries with reference to this scheduling agreement

<b>Delivery Block</b>:delivery block can be specified at scheduling agreement document header level. So that system proposes delivery block for all items in the scheduling agreement as some one in the business has to check scheduling agreement before initiating outbound deliveries

<b>MRP for delivery scheduling type:</b> the value os this filed determines whether system has to carry out MRP on scheduling agreement line items

pls reward points if the answer is helpful

REgards,

Murali