SAP Software Knowledge: SAP IMG Configuration

Showing posts with label SAP IMG Configuration. Show all posts

Thursday, April 30, 2009

Set the number range for Deliveries

The internal and external number range for delivery are control by the delivery type.

First you define the number range for deliveries in 'VN01'.

Then you assign the number range for the delivery type in transaction '0VLK'.

Related Topics:
Set the number range for Deliveries
Set the default start variant for VL10
Adding additional fields to Delivery Due List
Checking Fields with Incompletion procedures for Delivery
Exclude inventory in Storage Locations during Delivery Creation
Avoiding delivery creation when items quantity are zero
SAP WMS - Decentralized Warehouse Management System Integration Setup
SAP Customizing Picking Output

Adding additional fields to Delivery Due List

If you would like to add additional fields to the Delivery Due List - Transaction VL04.

These fields do not exist in the list of additional fields in the IMG.

You will need to have a user exit written.

This OSS notes will help you in creating the additional fields :-

198137 - VL10: Customer-specific enhancements / user exits

415716 - User exits in delivery processing

Related Topics:
Set the number range for Deliveries
Set the default start variant for VL10
Adding additional fields to Delivery Due List
Checking Fields with Incompletion procedures for Delivery
Exclude inventory in Storage Locations during Delivery Creation
Avoiding delivery creation when items quantity are zero
SAP WMS - Decentralized Warehouse Management System Integration Setup
SAP Customizing Picking Output

Checking Fields with Incompletion procedures for Delivery

Define your incomplete procedures in OVA2.

There are 3 levels :-

Groups
Procedures
Fields -> 1. here you define the Status Group to used
2. you define whether a warning message should be issued

Assign incompletion procedures to partner functions in SM30 - V_TPAR_VUV

Assign incompletion forms to the delivery types in SM30 - V_TVLK_VUV

Assign Incompletion Forms to the Delivery Item Types in SM30 - V_TVLP_VUV

Define the Status Group in SM30 - V_TVUVS

You use this function to block a document for delivery, billing, or pricing etc.

In an incompletion procedure you group together the fields that are to be checked for
completion. If you have not entered data in one of the fields in the document, the document
is incomplete. Depending on the status group you can block certain subsequent activities for
the document.

For every field in the procedure you also have to define whether a warning message should
be issued during processing if no data is entered in this field.

Related Topics:
Set the number range for Deliveries
Set the default start variant for VL10
Adding additional fields to Delivery Due List
Checking Fields with Incompletion procedures for Delivery
Exclude inventory in Storage Locations during Delivery Creation
Avoiding delivery creation when items quantity are zero
SAP WMS - Decentralized Warehouse Management System Integration Setup
SAP Customizing Picking Output

Set the default start variant for VL10

In transaction SU01, tabstrips Parameters.

Assuming you have created a variant TEST

Parameters Value Text
LE_VL10_USER_VARIANT TEST Default Selection Parameters for Delivery Creation

Related Topics:
Set the number range for Deliveries
Set the default start variant for VL10
Adding additional fields to Delivery Due List
Checking Fields with Incompletion procedures for Delivery
Exclude inventory in Storage Locations during Delivery Creation
Avoiding delivery creation when items quantity are zero
SAP WMS - Decentralized Warehouse Management System Integration Setup
SAP Customizing Picking Output

Avoiding delivery creation when items quantity are zero

Deliveries are created collectively using VL10.

In the definition of delivery item category 0VLP, there is a field Check Quantity 0.

Set the value to B or C.

This will prevent delivery with zero lines from being created.

However, if you want to include zero quantity items but if they are all zero, you do not
want to create the delivery then you have to used the user exit USEREXIT_SAVE_DOCUMENT_PREPARE.

Related Topics:
Set the number range for Deliveries
Set the default start variant for VL10
Adding additional fields to Delivery Due List
Checking Fields with Incompletion procedures for Delivery
Exclude inventory in Storage Locations during Delivery Creation
Avoiding delivery creation when items quantity are zero
SAP WMS - Decentralized Warehouse Management System Integration Setup
SAP Customizing Picking Output

Exclude inventory in Storage Locations during Delivery Creation

When you exclude MRP planning for a storage location, SAP will not consider the stocks when
you do a delivery creation.

You used SM30 - V_T001L_D to include/exclude the storage location for MRP.

If you does not wish to include/exclude the storage location for all the materials, you can
just goto MM02 -> MRP View 4 to include/exclude it for that particular materials only.

Take note that when you set the parameters in SM30 - V_T001L_D, the settings only affect
those newly created materials starting from the days you set the parameters.

For those materials already created, you have to changed it manually one by one or write an
ABAP program to mass changed it automatically.

Related Topics:
Set the number range for Deliveries
Set the default start variant for VL10
Adding additional fields to Delivery Due List
Checking Fields with Incompletion procedures for Delivery
Exclude inventory in Storage Locations during Delivery Creation
Avoiding delivery creation when items quantity are zero
SAP WMS - Decentralized Warehouse Management System Integration Setup
SAP Customizing Picking Output

SAP WMS - Decentralized Warehouse Management System Integration Setup

You can operate the SAP Warehouse Management System (WMS) as a stand-alone decentralized system that is independent of a central Enterprise Resource Planning (ERP) System.

You make the necessary settings for the ERP (Enterprise Resource Planning) system within the WMS component (Warehouse Management System).

The steps are set up as a checklist and guide you through the process of configuring the system parameters.

Checklist (For those with the Table Views used transaction code SM30).

1. Customizing for "Enterprise Structure"

- Create storage location in OX09 (if necessary).

- Define warehouse number in Views V_T3001.
(you should not copy the warehouse number in the ERP system)
Activities within a warehouse, like goods movements and physical inventory, are assigned to a specific
warehouse number.
The physical warehouse where these activities take place is identified by the warehouse number.

- Assign plant/storage location to warehouse number in Views V_T320.
(Valid if the component MM-IM (Inventory Management) is implemented.)
Fields : Plant + Sloc + WhN

2. Customizing for "Decentralized WMS integration", section "Central processing" -> Application

- Activate decentralized WMS in Views V_T340DM.

- Define interface to Inventory Management in Views :-
V_156S_WM - Assign WM movement type references to IM movement types
V_T3211 - Delivery-Relevant Parameters for Reference Movement Type
V_T340DL - Delivery-Relevant Data for Warehouse Number

- Exclude stock in decentralized WMS in Views V_T321B
(if the decentralized WMS is not an SAP R/3 system)

- Finally do a consistency check for decentralised WMS in transaction OL20.

3. Customizing for "Application Link Enabling (ALE)", section "Basis Components"

Maintaining Logical Systems in Views V_TBDLS.

Assign logical system to client in Views T000.

4. Make basic settings for RFC in transaction BD97.(if necessary)

5. Customizing for "Application Link Enabling (ALE)", section "Maintain Distribution Model"

You can define the Reduce message types and Activate message types in transaction BD53.

SAP recommends that you use message types :
"MATMAS" (material master tables) and
"DEBMAS" (customer master) as a template.

Be aware that only those fields that are absolutely necessary are transferred from the master data tables in
the ERP system to the decentralized WMS.

6. Customizing for "Decentralized WMS integration", section "Central processing" -> Distribution

Use transaction OL19 to generate distribution model. As far as the application is concerned, when the model
is generated, application-specific Customizing parameters are modified or set (for example, activate
decentralized WMS).

Display or check distribution model

Generate partner profile in transaction BD82.
(you can also perform this activity using ALE Customizing)

Distribute distribution model in transaction BD64 (model view) using menu item "Edit"

If both the ERP system and the decentralized WMS are SAP R/3 systems, the distribution model should be
distributed on a central basis only, that is, via the ERP system.

7. Customizing for "Application Link Enabling (ALE)", section "Maintain Distribution Model" (transaction BD64)

Activate the change pointers for master data distribution using transactin BD61.

If necessary, reduce the message types concerned with transaction BD53.

8. Customizing for

"Logistics - General" - "Material Master" - "Tools" - "Data Transfer : Material Master" -
-> "Define required-field check for ALE/Direct Input" (Views V_T130S)