OUM

RD.140 REQUIREMENTS SPECIFICATION

SFA, Inc.

B2B to OM – OM extensions

Author: Vijay Jayavarapu

Creation Date: Jan 3, 2023
Last Updated: Jan 3, 2023

Document Ref:
Version: DRAFT 1

Approvals:

<Approver 1>

<Approver 2>
RD.140 Requirements Specification Doc. Ref. TAC-E-XXX

1 Document Control

1.1 Change Record

4

Date Author Version Change Reference

2-Jun-23 Vijay Jayavarapu Draft 1 Draft 1

1.2 Reviewers

Name Position

Sakura IT Team IT
Rahul Pathak Delivery Manager

2
File Ref: RD-140_REQ_SPEC_EDI
RD.140 Requirements Specification Doc. Ref. TAC-E-XXX

Contents

1 Document Control.............................................................................................................................................................. 2
1.1 Change Record............................................................................................................................................................ 2
1.2 Reviewers.................................................................................................................................................................... 2
2 Business Need................................................................................................................................................................... 4
2.1 Criteria......................................................................................................................................................................... 4
2.2 RMA Creation Process................................................................................................................................................ 4
Log Output......................................................................................................................................................................... 4
Parameters........................................................................................................................................................................ 5
3 Open and Closed Issues.................................................................................................................................................... 6
3.1 Open Issues................................................................................................................................................................. 6
3.2 Closed Issues.............................................................................................................................................................. 6

3
File Ref: RD-140_REQ_SPEC_EDI
RD.140 Requirements Specification Doc. Ref. TAC-E-XXX

2 Business Need
To protect technician’s time, Sakura ships all matching parts (more than what is need for repair). This will
create a situation where unused parts as a background scheduled job which can run on hourly basis to
generate RMAs for

2.1 Criteria
Following criteria can be used to identify the Service Order shipment lines for which corresponding RMA/RMA Lines need
to be generated

1. Query Orders with ‘Service Order’ type for a newly created order (this will eliminate legacy orders)
2. Select only lines with dollar amount great than $200
3. RMA (Attribute X of DFF on the Sales Order header is set to Y)

Criteria for selecting order line for RMA Creation:

1. Line type should be one of the following:

 Eval-Ship-NoBill MCC-Line
 Ship Only
 Ship-NoBill
 ShipRepair-NoBill
 SSCL-Drop Ship-Line
 Standard-Line
 UPS-Ship-NoBill

2. Order should belong to SFA

3. Order Type should be 'Service Order'
4. Order Source should be OPS
5. if RMA Flag = Y
or Base Unit Price from SERVICE price list >200
6. Order Header Status =
dha.STATUS_CODE not in ('DOO_DRAFT','CANCELED','CLOSED','DOO_CANCEL_REQUESTED')
Order Line Status = AND dfla.STATUS_CODE not in ('CLOSED','CANCELED')
Order Status= AND dha.submitted_flag = 'Y'
Order Submission Time = Submitted in the last 2 hours

2.2 RMA Creation Process

4
File Ref: RD-140_REQ_SPEC_EDI
RD.140 Requirements Specification Doc. Ref. TAC-E-XXX

Program should identify the shipment lines within a Service Order which are shippable and create a reference RMA for
only those lines which are shippable. This will ensure that Labor and Expense (Bill Only) type of lines are not considered
for RMA Creation.
RMAs need to be created with ‘Service RMA’ order type
Use Return Reason Code ‘Automatic RMA’
Ensure that Service Request Number reference from the original order is copied over. This SR reference should be
copied over into the same column as Original Service Order stored the SR reference.
Upon successful generation of RMA, set RMA Needed attribute (Attribute X of DFF on the Sales Order Header) to Yes.
This will ensure that the original order is not selected in the future runs.

Log Output
Log file should be generated at the end of the run with the following data:

 Run Successful or Failed

 RMAs selected for creation
 RMAs created (SR Number of the original orders need to be included for reference)
 Error codes for the failed RMAs

Parameters
• Order Start Date
• Order End Date
• Order Number
• SR Number

5
File Ref: RD-140_REQ_SPEC_EDI
RD.140 Requirements Specification Doc. Ref. TAC-E-XXX

6
File Ref: RD-140_REQ_SPEC_EDI
RD.140 Requirements Specification Doc. Ref. TAC-E-XXX

3 Open and Closed Issues

3.1 Open Issues

ID Issue Resolution Responsibility Target Date Impact Date

3.2 Closed Issues

ID Issue Resolution Responsibility Target Date Impact Date

7
File Ref: RD-140_REQ_SPEC_EDI