AIM

MD.050 APPLICATION EXTENSIONS

FUNCTIONAL DESIGN
School Specialty Inc.
Modify Revenue Accounting (ACE 106)

Author: Kim Nelson

Creation Date: July 17, 2008
Last Updated: February 16, 2009
Document Ref: MD050_FIN_Modify_COGS_Workflow_ACE_92_v1.3
Version: 1.3

Approvals:

<Approver 1> Kevin Baehler

<Approver 2> Foeke VandePoel

475372229.doc © 2020 Hitachi Consulting Corporation.  Page i

Last saved on 2/16/2009 All rights reserved.
 Table of Contents
Document Control......................................................................................................................................................iii
Topical Essay.................................................................................................................................................................1
Basic Business Needs.............................................................................................................................................1
Major Features........................................................................................................................................................1
Definitions...............................................................................................................................................................1
User Procedures......................................................................................................................................................1
Examples..................................................................................................................................................................1
Business Rules.........................................................................................................................................................1
Assumptions...........................................................................................................................................................2
Century Date Compliance.....................................................................................................................................2
Form and Report Descriptions...................................................................................................................................3
<Form Title> - Form Description.........................................................................................................................3
<Form Title> Form.................................................................................................................................................3
Prerequisites............................................................................................................................................................3
<Zone 1 name> Zone.............................................................................................................................................3
<Zone 2 name> Zone.............................................................................................................................................3
<Report Title> - Report Description....................................................................................................................3
<Report Title>.........................................................................................................................................................3
Report Parameters..................................................................................................................................................3
Report Headings.....................................................................................................................................................3
Column Headings..................................................................................................................................................3
Concurrent Program Description..............................................................................................................................4
When to Run the Program....................................................................................................................................4
Launch Parameters.................................................................................................................................................4
Business Rules Implemented................................................................................................................................4
Log Output..............................................................................................................................................................4
Restart Procedures..................................................................................................................................................4
Technical Overview.....................................................................................................................................................5
Open and Closed Issues for this Deliverable...........................................................................................................6
Open Issues.............................................................................................................................................................6
Closed Issues...........................................................................................................................................................6

475372229.doc © 2020 Hitachi Consulting Corporation.  Page ii

Last saved on 2/16/2009 All rights reserved.
Document Control

Change Record
1

Author Version Change Reference

17-Jul-2008 Kim Nelson 1.1 No Previous Document

16-Feb-2009 Kim Nelson 1.3 Modified requirements. See updates in Red

Reviewers

Name Position

Distribution

Copy No. Name Location

1
Library Master Project Library
2 Project Manager
3
4

Note To Holders:
If you receive an electronic copy of this document and print it out, please write your name on the
equivalent of the cover page, for document control purposes.
If you receive a hard copy of this document, please write your name on the front cover, for document
control purposes.

475372229.doc © 2020 Hitachi Consulting Corporation.  Page iii

Last saved on 2/16/2009 All rights reserved.
Topical Essay
The business would like to have a P&L by Sales Territory at the operating margin level. The business
would like to be able to control the account distributions for invoicing coils to its print partners and other
miscellaneous non revenue items. When selling coils to Print Partners, the revenue distributions are DR
AR and CR COGS Offset. The COGS distributions are DR COGS Coils and CR Inventory. This is done
because the coils can be used by PP for other jobs and they cannot control consumption. The also need
the flexibility to credit another account other than revenue. An example is if they sell equipment to a
print partner.

Basic Business Needs

In Phase 1 and 2, a custom program SSI Populate AR Interface Distributions is was developed to allow
additional flexibility in deriving revenue account segments. The location code can be used to book
Revenue at a sales territory level.

The SSI Populate AR Interface Distributions process should be modified as follows:

1. For order types beginning with 45%, 047 and 048 use the location code from the Salesperson
Revenue Account to derive the location segment for the Revenue. Add a condition in the
customization that states if the ITEM TYPE assigned to the item on the order line is = "NON
REVENUE" then derive ALL of the account segments from the Sales Account assigned to the
item.

Major Features
See above

Definitions
None

User Procedures
No change

Examples
None

475372229.doc Page 1
Business Rules
None

Assumptions
This assumes that the sales rep assignment process is run before the Revenue distributions are created so
that the sales rep is assigned to the order. This assumes that the items are setup with the correct sales
account

Century Date Compliance

In the past, two character date coding was an acceptable convention due to perceived costs associated
with the additional disk and memory storage requirements of full four character date encoding. As the
year 2000 approached, it became evident that a full four character coding scheme was more appropriate.
In the context of the Application Implementation Method (AIM), the convention Century Date or C/Date
support rather than Year2000 or Y2K support is used. Coding for any future Century Date is now
considered the modern business and technical convention.
Every applications implementation team needs to consider the impact of the century date on their
implementation project. As part of the implementation effort, all customizations, legacy data
conversions, and custom interfaces need to be reviewed for Century Date compliance.
When designing and building application extensions, it is essential that all dates be entered, stored, and
processed using the full four digit year for compliance with Century Date standards. In the case of
custom interfaces, both the program code and imported legacy or third-party application data must be
checked for compliance with Century Date standards.

475372229.doc Page 2
Form and Report Descriptions
No report

<Form Title> - Form Description.

<Form Title> Form

Prerequisites

<Zone 1 name> Zone

<Zone 2 name> Zone

<Report Title> - Report Description

<Report Title>

Report Parameters

Report Headings

Column Headings

475372229.doc Page 3
Concurrent Program Description

When to Run the Program

SSI Populate AR Interface Distributions is run each evening as part of request set SSI Transfer data from
OM to AR Interface - Parallel

Launch Parameters
None

Business Rules Implemented

The business rule implemented by <Component Name> concurrent program is…

Log Output
None

Restart Procedures

475372229.doc Page 4
Technical Overview.
Considerations
If any Oracle Manufacturing tables change in future versions of Oracle Manufacturing,
components of this customization may also require changes to work correctly. Evaluating the
impact of such changes on custom programming is the responsibility of the company, although
additional consulting services can be contracted to assist prior to upgrading.

475372229.doc Page 5
Open and Closed Issues for this Deliverable

Open Issues

ID Issue Resolution Responsibility Target Date Impact

Date

Closed Issues

ID Issue Resolution Responsibility Target Date Impact

Date

475372229.doc © 2020 Hitachi Consulting Corporation.  Page 6

Last saved on 2/16/2009 All rights reserved.