Oracle Release 12

deliverable template
Oracle advanced planning system
assign allocation rule
Configuration setup guide

Client name
Project name
Date
Authors
First name Last name, Title
Address: Placeholder for text
City: Placeholder for text
Tel: Placeholder for text
Fax: Placeholder for text
E-mail: Placeholder for text
Version history
Description
PwC 1
First name Last name, Title
Address: Placeholder for text
City: Placeholder for text
Tel: Placeholder for text
Fax: Placeholder for text
E-mail: Placeholder for text
Draft
Version Draft date Author
First name Last name, Title
Address: Placeholder for text
City: Placeholder for text
Tel: Placeholder for text
Fax: Placeholder for text
E-mail: Placeholder for text
Final
Approval date Approver
Table of contents
1. Introduction............................................................................................................................................................. 3

2. Oracle advanced planning system assign allocation rule.....................................................................................3

3. Additional information............................................................................................................................................ 6

4. Appendices................................................................................................................................................................ 7

Blue Italics are special instructions for completing the template. When creating a template, insert detailed
instructions in blue italics. Before finalizing a deliverable, Delete all blue italic text, instructions and
unused material.
 On Title Page: Insert document name and date of submission
 On Author and Version History Page:
– Author Table: Insert author names and delete generic references;
– Version History Table: track ongoing history of changes to this document. Approver should be highest
level person, persons or committee required to validate and adopt this document.
– Copyright Version: May require adjustment based on the Terms and Conditions of the Engagement
Contract. Year reference may require adjustment based on current date.
– Select View>>Header and Footer to adjust Headers/Footers. Select item, right click and select
Update Field
 On the Table of Contents Page: Right Click within the Table of Contents. Select Update Field>>Update
Entire Table
 This document contains generic text and formatting references to assist in development. Adjust, duplicate by
adding additonal sections, build on and replace this text as appropriate for your document.
 1.
Introduction
This document is a supplement to the Oracle Advanced Planning Suite (APS) Global Order Promising (GOP)
Configuration Guide and serves to provide more detail regarding setup of Allocation Rules assignments in PwC
Methodology for Oracle. If you are setting up a new install from scratch or modifying PwC Methodology for Oracle,
use this document as a guide and modify it as needed to meet Client requirements. Note that this document only
contains the steps that warrant explanation; refer to the Oracle Advanced Supply Chain Planning (ASCP)
Configuration Guide for an explanation of all the setup steps in the recommended order of execution.

Overview

ATP Allocation provides significant control over the demand fulfillment process to achieve customer service and
profitability goals.

The allocation rules can be assigned at Global, Item Category, Item, Item Organization or Organization levels.
Notifications are sent to you if scheduling fails, or if scheduling is only successful by stealing allocation from
other nodes.

<Source Materials include the Oracle user and implementation guides, white papers and notes on new release.>
<Note to project teams: Please carefully review all information included in the Configuration Setup Guide,
evaluate if the setups are reusable at your client sites and make modification when necessary. Please complete the
setup rationale as pertinent to your client’s business requirements.>

2. Oracle advanced planning

system assign allocation rule
<In this table outline the Configuration tasks including the application and module name, the configuration task
that the setup guide outlines, the configuration steps involved in the setup and applicable prerequisites.>
Value Details
Application: Global Available to Promise
Configuration task: Assign Allocation Rule
Configuration step(s): GATP-12
Prerequisite(s): Define Allocation Rule (see ASCP Define Allocation Rule Setup.doc for further
information)

The following setup steps are presumed to occur using the Oracle Advanced Supply Chain Planner responsibility
unless otherwise noted.
 2.1.
Assign application rule setup
2.1.1. Navigation
Navigate to ATP > Allocation>Assign Allocation Rule

2.1.2. Screen print

2.1.3. Configuration
Field name Description R/O/C/D/E User action Comments
and value
<Reference each field <Describe the field <Capture the field <Enter comments to
that will be reviewed values available and value entered or action indicate whether this
by name.> the business impact taken setup is complete,
<References may tie of the decision made> by configurator> under review,
back to screen print pending other task
above or related <example: Document completion, etc.>
document> <If Name field if check is
configuration data chosen the check is
document enter system generated if
name here> manual is chosen the
user may use this
value to enter checks
produced outside
the application to
later record
the transaction>
Assign to: R Select Global, Item
Category, Item
Organization or
 Field name Description R/O/C/D/E User action Comments
and value
Organization from the
list of values
Org (Organization): O Select the inventory
organization if you
choose Assign to:
values of “Item
Organization”
or“Organization”
Item: R Select the item if you
choose Assign to:
values of “ Item” or
“Item Organization”
Category: O Select the category if
you choose Assign to
values of
“Item Category”
Allocation Rule: O Choose the Allocation
Rule you wish to use.
Allocation rule
methods are controlled
by Site Level Profile
Option MSC:ATP
Allocation Method
Choices are: User-
Defined Allocation
Percentages or
Demand Priority
See Table Legend at end of this section for an explanation of R/O/C/D/E abbreviations.

2.2. Legend
 R (Required) The field listed is a required field. Data must be entered for the transaction to
be completed.
 O (Optional) The field listed is an optional field. Data may be entered but it is not required to complete
a transaction. When a business variation warrants data in this field, it should be entered.
 C (Combined) The field listed is required only if other related fields have not been populated. The
requirement is combined across two or more fields; it is required that one of the fields
listed be populated.
 D (Display) The field listed is a display only field. Data cannot be entered into this field.
 E (Empty) The field listed should be left blank.
 3.
Additional information
<The following sections may be appropriate to include as the last sections of a document>

3.1. Definitions, acronyms, and abbreviations

<Provide an alphabetical listing of all acronyms, abbreviations, and their meanings as used in this document and
a list of any terms and definitions needed to understand the document. This information may be provided by
reference to one or more appendices or by reference to other documents>
Term Definition
<Topic> 1.00

3.2. Open issues and future considerations

<If there are known open issues or questions that will potentially impact this document etc., list them here.
Describe any important attributes, considerations, timeframe, anticipated follow up, tracking, and
options/resolution, including the owner or go to person assigned the open questions, etc.>
Number Issue Status Owner
<Topic>
1.00

3.3. References and related documents

<If there are related documents the reader should consider or may be of interest, list them here>
<List the title, revision, date, and publishing organization of all referenced documents. Identify the sources from
which the documents can be obtained. Client policies and procedural document, organization charts, and user
manuals may be referenced as internal source documents. This information may be provided by reference to an
appendix or by reference to another document.>
Number Document name Version
<Topic>
1.00 Oracle Advanced Planning Suite
(APS) Global Order Promising
(GOP) Configuration Guide

The Configuration Setup Guide document provides further instruction on steps documented in the Configuration
Checklist document and further explains the set up of the step that require additional detail. The Configuration
Checklist document provides the setup sequence of steps.
 4.
Appendices
<Appendices may be used to provide information published separately for convenient document maintenance
(e.g., classified data) or to provide additional information about a particular topic (e.g., integration practices
and procedures). Each appendix should be referenced in the main body of the document where the data would
normally have been provided. Appendices may be bound as separate documents for ease in handling. Appendices
should be lettered alphabetically (A, B, etc.).>

4.1. Appendix A: Title

Placeholder for text

4.2. Appendix B: Title

Placeholder for text