Sie sind auf Seite 1von 9

EBS Development Team Meeting

Documentation Discussion

June 16, 2017

© 2016 HDR, Inc., all rights reserved.


AGENDA
• Project Documentation Flow
• Instructions for Creating New RICEW Folders
• BR100 Documentation Storage
• RICEW Documentation Cleanup

2
Project Documentation Flow

Project Submission & Approval Documentation Testing & Move to Production Close-Out

APPROVED Requests
Project Request is Documentation is
HPQC Ticket Test Scripts are Testing issues RICEW folder stores
uploaded to uploaded to RICEW
Gets Opened RICEW Folder is Created logged final documentation
Approval Site folder
created

SYSTEM HPQC Project Application Application HPQC HPQC Application


Approval Spec Spec Spec
Management Management Management
DELIVERABLE HPQC Ticket # Completed Requirement Technical Specs Test Script HPQC issues Final
and details Project Request Document Design Docs Identified logged for items Documentation
Data Mapping Tester(s) found in testing
Etc. BR100
Testing
Comments
TASK OWNERS BAMs, TAMs, TAMs submit BAMs create Tech Team BAMs create BAMs, TAMs, BAMs, TAMs,
and Tech team project requests Requirement creates Test Scripts and and Tech Team and Tech Team
create HPQC with input from Documents technical assign track status and ensure final
issues BAMs and Tech documentation functional provide updates documentation
Teams Tech Team testers is in the folder
creates RICEW
folder

3
Instructions for Creating New RICEW Folders
1. GETTING STARTED:

a. Enter the Application Specification Management Site

http://collaboration/sites/asm/SitePages/Home.aspx

2. Name the RICEW Object:

a. Click on the RICEW DB Link on the Left Navigation under “Lists”

b. Determine the next sequential number to name the RICEW object. To do this, open the folder for the Thread you are adding a new
RICEW Object to. The items in this folder are sorted by the type of Object

i. CNV = Conversion - Conversion programs to transfer data from a legacy system to the new system
ii. EXT = Extension - Enhancements\extensions to the existing system to add additional functionality to existing system without
disturbing the core software functionality of the system
iii. INT = Interface - Interfaces to external systems. Linking (Programs) between other systems to ERP system in order to
synchronize the Data. They can be Manual, Batch or Real-Time. Interfaces can be either outbound or inbound. An outbound
interface reads data from Oracle Apps tables and usually creates output files in the third party tool specified format. An
inbound interface reads data from flat files (usually) and calls Oracle APIs to upload data into Oracle Apps
iv. RPT = Report - Create reports that are not available as standard reports in the oracle apps modules, or change existing
reports.
v. WKF = Workflow - Create\Change existing workflows available to meet business requirements

c. Scroll down to see the next number. For instance if you are creating a new Extension, and there are already extensions named
ATC_EXT_001, ATC_EXT_002 and ATC_EXT_003 the name of the next Extension would be ATC_EXT_004.
• No Not Create an Entry at this time

4
Instructions for Creating New RICEW Folders
3. CREATE A FOLDER FOR THE NEW EFFORT:

a. To create the folder for the extension, Click on the RICEW Database link under LIBRARIES on the left nav.
http://collaboration/sites/asm/RICEW%20Database/Forms/AllItems.aspx

b. On the top Navigation bar select DOCUMENTS + NEW FOLDER

c. Enter the name of the new folder and SAVE. Make sure to use the format of:

THREAD + “underscore” +RICEWTYPE + “underscore” + next sequential number using 3 digit format. i.e.
ATC_EXT_004

d. Once the folder has been created, OPEN it.

e. HIGHLIGHT the URL at the top of the page and COPY it (CTRL/C)

5
Instructions for Creating New RICEW Folders
4. UPDATE THE LIST INFORMATION WITH THE NEW FOLDER:
a. Click on RICEW DB under LISTS on the left nav

b. Scroll to bottom of screen and click ADD NEW ITEM

c. Fill in the information on the screen and click SAVE:

• Required fields have an asterisk next to them.

6
Instructions for Creating New RICEW Folders
i. HPQC Case ID = The HPQC case attached to this request

ii. Track = The Thread that’s associated to this effort. Should match the same Thread you created the folder in on 3c
iii. RICEW ID = Enter the name of the folder you created in Step 3c.

iv. RICEW Description = A short description of what this effort is.

v. RICEW Type = Report, Integration, Conversion, Extension, or Workflow. This should align to the middle 3 characters of the
Folder you created.

vi. Func Spec Author = Who created the Functional Spec. Normally the BAM contact.
vii. Tech Spec Author = Who is in charge of creating the Technical Spec.

viii. Tech Lead = Who is the developer in charge of coding this effort
ix. BR100 Name = If there is a configuration needed for this effort, what BR100 is associated.

x. Documentation Location, Web Address = CTRL/P to enter the location of the folder you created previously in step 3d

xi. Documentation Location, Description = Enter the name of the folder you created in Step 3c.

7
BR100 Document Storage
1. GETTING STARTED:

a. Enter the Application Specification Management Site

http://collaboration/sites/asm/SitePages/Home.aspx

a. Click on BR100 in left Navigation and they are stored there by thread
http://collaboration/sites/asm/BR100/Forms/AllItems.aspx

8
RICEW Documentation Cleanup
1. GETTING STARTED:

a. Go to eRoom files on CorpData Share drive (Corp Data, Financial Services, eRoom_docs AND link on APP SPEC site)

X:\Financial Services\eRoom_docs AND file://omac-infs01/ebs_eroom AND Hard Drives

1. Anything more recent than June 2016 needs to be saved on the Application Specifications collaboration site under
appropriate RICEW Objects

http://collaboration/sites/asm/BR100/Forms/AllItems.aspx

2. Review all RICEW’s for your thread to ensure that all documentation is in the Application Specifications Collaboration site.

3. Request your TAM to provide you with any Requirements documents that are missing. Upload to the site (or have them)