afs: implementing sd contract allocation kathleen steffes wolverine world wide

AFS: Implementing SD Contract Allocation

Kathleen SteffesWolverine World Wide

Presentation Agenda

SD Contract Allocation

• Wolverine World Wide environment

• Process before new functionality

• SAP Contract Allocation available in 3.0B/4.6C !!!

• Benefits of Contract Allocation

• Implementation of ‘Allocatable Contracts’ at WWW

• Including issues encountered

• Implementation Tips

• Q & A

Work, Outdoor Sport and Uniform Active Lifestyle

Wolverine World Wide Brands

Casual and Leisure

Wolverine World Wide Brands


SAP at Wolverine World Wide


• April 1999 – FI/CO, SD, MM, 3.1H/1.0C

• November 1999 – Upgrade to 3.1I/1.0D

• July 2002 – Upgrade to 4.6C 27/3.0B 1

• March 2003 – 4.6C 38/3.0B 2 & 3

SAP at Wolverine World Wide


Billing

TaxesPurchasingDelivery

Ded. MgmtUPCsPricing

CreditGridsAllocation

ArchivingGL, AR, APInv. MgmtOrder Entry

OtherFI/COMMSD


WWW ‘Old’ Contract Process

• CQ contracts - not ATP relevant• automatic reference• cannot be allocated • reference 1 contract per order

Strategies used to imitate Contract Allocation:• ZBLK - order created instead of contract to allocate pairs

• orders not referenced • manual maintenance

• ZHLD - orders are created and allocated each night • custom programming• based on open contracts • analysis difficult

Issues with ‘Old’ Contract Processes


• Customer Requirements were not always met because contracts were not allocated in advance

• Manual work to maintain the contracts and orders

• Many manual allocations, de-allocations, and deliveries were done to support these processes

• Analysis of the order fulfillment process was difficult because of these different processes

• Extra processing time creating the ZHLD Orders each night

SD Contract Allocation Functionality


• Reserve available stock to contracts

• Allocated pairs on contracts are automatically transferred to the release orders

• Option to automatically allocate release order to fixed status when release rule criteria is met to allow delivery

• Reductions and cancellations on release orders can be configured to return the allocation to the contract

Benefits of Contract Allocation


• Provide the business a better way to manage customer contracts to ensure that our major customers are serviced

• Reduce the amount of manual work done by Customer Service to maintain the current contracts and orders

• Decrease the number of manual allocations and deliveries

• Improve tracking of data through the order fulfillment process

• Save time in the production schedule each night by eliminating the ZHLD creation and deletion jobs

• Method to support JC Penney’s new Purchase Order Management

Implementation Objectives


• Create a new Order Type for ‘Allocatable’ Contracts (ZAC)

• Convert current Contracts and Contract-like Orders to ZAC’s

• Change the nightly Allocation Process to include ZAC’s

• Remove the ZHLD process

• Block the ZBLK and ZHLD Order Types

Project Plan HighlightsProject Plan Highlights


• Gather Requirements from Business Owners

• Analysis & Planning

• Configuration & ABAP development

• Testing and Re-testing

• Resolving issues and applying OSS notes

• Training

• Cutover

Business Requirements


• Restore open order and allocated quantities to valid contracts when release orders are cancelled

• Keep CQ contract types and discontinue the use of the contract like orders

• Allocate based on priority

• Need a way to keep orders from de-allocating

Configuration


• New Contract Order Type - ZAC

• New Item Category - ZAC

• Convert SAP Item Category to EDI Item Category

• New Schedule Line Category - ZC

• Copy Control setup

• Transfer of Requirements

• Allocation Configuration for new order type

• Customer Group Setup for de-allocation block

• Create new Management Tool Type

ABAP Development


• User Exits to control how an order references a contract had to be changed for SAPLJ4AS

• Function Module to change the sales document type of the contract when posting the IDOC

Issues Note: Fixpack 2 & 3 notes appliedNote: Fixpack 2 & 3 notes applied


• Contract Release Orders not selected in Mgmt Tool• Use VBAK-VBELN instead of J_3ABDBS-VBELN

• Grid Entry in New Contract Type uses different screen• Configuration of grid entry screen in Maintain Sales Doc

Types for AFS >> Select screen used (2270 for item w/drop down)

• Reserved qty not transferred to EDI Release Orders correct• Apply OSS notes in Fixpack 4 (615335)• OSS is currently working on a correction for the ‘old’

documents

Issues (cont.) Corrected with Fixpack 4 Notes Corrected with Fixpack 4 Notes


• Contracts with allocated qty, but no open reference quantity

• Release Orders copy in completed lines from Contract

• Requested Delivery Date on Contract copied incorrectly to the release order• Item Level• Schedule Line Level

Functionality Change


• Release Orders copy the entire open quantity from the Contract automatically• Previous releases allowed control of this in the

Configuration of the Order Type, but is no longer supported in AFS Release 3.0B

• See OSS note 591724 for a modification to revert back to the old functionality

Very Important Unresolved Issue


• Contracts are still open for processing after the validity period and cancel date have passed

• Cancellations on Release Orders referencing Expired Cancellations on Release Orders referencing Expired

Contracts will:Contracts will:• Increase the Contract Open Reference Quantity Increase the Contract Open Reference Quantity • Return the Reserved Quantity to the ContractReturn the Reserved Quantity to the Contract

• We really need to find a solution for this issue!!

Training


• Training Documents updatedTraining Documents updated

• Training scheduled to review new functionality:Training scheduled to review new functionality:

• New Contract Order Type

• Automatic Transfer of Reserved Quantity

• Review procedures for changing Reserved to Fixed

• Overview of Nightly Allocation Changes

• Show examples of new process

Cutover


Phase 1: Conversion to new Contract TypePhase 1: Conversion to new Contract Type• Create ZAC contracts from old contract/order types

• ‘Cancel’ contracts/orders as the ZAC contracts are created

• Create new ARun MAS Sets to allocate ZAC contracts

• Create new ARun Variants and Schedule in Nightly Jobs

• Continue to Allocate old contract-like order types

• Keep running other (ZHLD) jobs until all contracts are converted

Cutover


Phase 2: All Contracts are ConvertedPhase 2: All Contracts are Converted• Change config. to turn off old contract & order types

• Mark old ARun Selection Sets for Deletion

• Update ARun Selection Sets as needed

• Remove old ARun Steps from Nightly Jobs

• Remove other (ZHLD) process from the Nightly

Schedule

Tips for a Successful Implementation


• Know the benefits to get buy-in from the business

• Apply OSS notes to avoid issues

• Investigate the EDI process for user exits

• Block de-allocation of a contract?

• Find a way to ‘Complete’ the contracts

• Test the process thoroughly

• Reporting of New Sales Doc Type and References

• Cutover considerations

Questions and Answers?


Note:

Additional information including the project plan used

and configuration notes will be posted on the ASUG

Website

Thank you for attending!Please remember to complete and return your evaluation form following this session.

Session Code: 3209

afs: implementing sd contract allocation kathleen steffes wolverine world wide

Documents

nightly allocation process

night slide

customer contracts

business requirements

current contracts

zhld process

order fulfillment process

zblk order