Int Fs Macy Iby Iby056 Edi 820 Payment Outbound

Macy's Financial Application Project

Functional Specification (Interface)

EDI 820 Outbound Payment and Remitance Advice

Document Control Information

Document Information

Document IdentificationINT FS_MACY_<Product Short

Code>_<FRICEWID>_Description.doc

Document Name Functional Specification (Interface)

Project Name MACYS Financials Application

Client MACYS

Document Author Srini Nemala

Document Version Ver 1.0

Document Status Draft

Date Released 02-Nov-2012

Document Edit History

Version Date Additions/ModificationsCR# Prepared/Revised

by

1.0 22-Oct-2012 Initial Release for review Srini Nemala

Document Review/Approval History

DateDocument

VersionName Organization/Title Comments

22-Oct-2012 1.0 Srini Nemala MST Initial Release

Distribution of Final Document

The following people are designated recipients of the final version of this document:

Name Organization/Title

Daniel Fryer MST/EDI Analyst

Nancy Levenson

Bill Walke

Dinnetta Kinman

Document Control Information8-Apr-23

Page ii MACYS Financials Applicationdocument.doc

Functional Specification (Interface)EDI 810Interface MD 50 Spec

Table of Contents

1 Interface Overview 51.1 Objective 51.2 Business Needs 51.3 Major Features 51.4 Modules Involved 51.5 Systems Involved 51.6 Assumptions 51.7 Dependencies and Prerequisites 51.8 Related Documents 51.9 Nomenclature 6

2 References to Requirements 7

3 Functional Approach/Process Description 83.1 Source and Target Systems Description 83.2 Process Flow Diagram 83.3 Process Steps Description 8

4 Application Setup Requirements 94.1 Core Application Module Setup 94.2 System Parameters 94.3 Lookup Definitions 94.4 Value Sets 94.5 Profile Options 94.6 Cross Reference Lookups 94.7 Programs and Parameters 9

5 Detailed Functional Specifications 105.1 Interface Specifications 10

5.1.1 Interface Summary 105.1.2 Business Rules 10

5.2 Data Mappings 115.3 Additional Processing Logic 115.4 Data Criteria Specifications 11

5.4.1 Data Selection and Filtering Criteria 115.4.2 Pre Extract Clean up Criteria 11

6 Test Scenario / Acceptance Criteria 12

7 Other Requirements 137.1 Volume and Performance Requirements 137.2 Initiation, Frequency, and Scheduling Requirements 137.3 Security and Controls Requirements 13

8 Exception and Error Handling 148.1 Log Output 148.2 Restart Procedures 14

9 Open/Closed Issues 159.1 Open Issues 159.2 Closed Issues 15

10 Appendix – Misc Attachments 16

Table of Contents8-Apr-23

Page iii MACYS Financials Applicationdocument.doc


1 Interface Overview

1.1 Objective

This functional design document is intended to provide EDI Analyst and EDI developer all the key information, assumptions, rules, and logic that are required to write accurately the Interface EDI Outbound Payment and Remittance Advice going to external trading partners.

1.2 Business Needs

EDI Outbound Payment and Remittance Advice provide you with the features you need to satisfy the following basic business needs.

Ability to generate EDI file based on the format by Banks.

Ability for banks to pay suppliers appropriately.

.

Electronically make a payment, or make a payment and send a remittance advice to Macy’s creditors.

The payment portion of this transaction is a request to your financial institution to perform cash application to relieve your account and to pay your payee's account.

The remittance advice portion of this transaction contains the payment distribution by invoice

1.3 Major Features

The major features of EDI Outbound Payment and Remittance Advice includes

Electronically make a payment, or make a payment and send a remittance advice to Macy’s creditors.

The payment portion of the transaction is a request to your financial institution to perform cash application to relieve internal cash clearing account and to payee's account

The remittance advice portion of this transaction contains the payment distribution by invoice

1.4 Modules Involved

EC Gateway

Accounts Payable

Payments

Purchasing/iProcurement

1.5 Systems Involved

Oracle EBS

EDI Translation tool.

Detailed Functional Specifications8-Apr-23

Page 4 of 17 MACYS Financials Applicationdocument.doc


1.6 Assumptions

The design recommendations/solution in this document is based on the following assumptions

The payment instrument assigned to supplier which drives electronic payment process is in CTX Format.

Every Pay Run (PPR) will automatically generate the 820 raw text file at the end of payment cycle.

Bank of America, PNC Bank and Citizens bank are the only internal banks involved in the exchange of electronic payments.

Pay group for each internal bank should exist to make payments from respective banks.

1.7 Dependencies and Prerequisites

Create outbound directories to store raw file data content.

Define Trading Partner relationship and enable transaction for the trading partner.

Define code conversion as required

Required configuration / setup would be available for Interface

All related master data would be converted prior to this Interface

1.8 Related Documents

Document Name Revision Document Description

RPT_FS_MACYS_PO_RPT001

PO output for communications (Non EDI suppliers)

1.9 Nomenclature

Acronym Meaning Description

ISA Interchange Control Header Authorization qualifiers, security qualifier, sender/receiver qualifier and identifier details

ST Transaction Set Header EDI translator envelope Identification

BIG Beginning Segment for Invoice

CUR Currency Details Segment for Invoice

N1 Address Segments of Invoice Ship To , Remit Address etc.

REF Reference Number Segment for Invoice at Header, Line levels

Supplier Number, Line Numbers, Freight Carrier Numbers etc.

IT Baseline Item Data segments for Invoice lines

Line Item Number, Quantity, UOM etc...

ITD Terms Segment of Invoice Discount Terms like Discount %, Net Due Date, Discount Amount etc.




Acronym Meaning Description

TDS Total Monetary Value Summary segment of Invoice

Total Dollar value of Invoice

CTT Transaction Totals Segment of Invoice

Total number of line Items in the transaction set. Translator will generate this.

SE Transaction set Trailer segment of Invoice

Includes number of segments, Transaction set control. Populated by translator

ACH Automated Clearing House

CCD NACHA Payment Format (Cash Concentration or disbursement)

CTX NACHA Payment Format (Corporate Trade Exchange)

PPP Payment Process Profile

PPT Payment Process Template

PPR Payment Process Request

PPR Preliminary Payment Register

NACHA National Automatic Clearing House Association




2 References to Requirements

Requirement Id Description




3 Functional Approach/Process Description

3.1 Source and Target Systems Description

Source: Oracle EBS & GXS

Target: Banks

3.2 Process Flow Diagram

3.3 Process Steps Description

One time configurations are done for every eligible electronic supplier and internal bank enabling the payment and remittance details sent out from EP team (Macys Business can perform the activity),

One time EC Gateway configurations like enabling 820 transaction, trading partners etc are performed to complete the payment process. (Macys MST team can perform the activity)

Payment User will schedule/run a pay run process which creates the EDI text file in a designated location( Macys payment users can perform the activity)




EDI Translators at both treading partners will conclude the communication channel and format of the document. Sets up the directory where the Translated files will reside on EBS server to be processed.

EDI Translator team picks up 820 files generated by EC-Gateway and translates into a X12-VICS 5010 format and transmits it to bank.

Bank will process the payment and credits the supplier provided in the extract.




4 Application Setup Requirements

Supplier Site (EDI Location Code)

Internal Bank (Edi Location Code)

EC Gateway – Trading Partner, Code Conversion, Profiles

4.1 Core Application Module Setup

Supplier Site (EDI Location Code)

Internal Bank (Edi Location Code)

EC Gateway – Trading Partner, Code Conversion, Profiles

4.2 System Parameters

System Parameter Application Value

4.3 Lookup Definitions

Lookup TypeApplicationDescriptionLookup Code Meaning Description

4.4 Value Sets

Value Set NameType & SizeValidationValue Meaning Description

4.5 Profile Options

Profile Option Name Application Accessibility Level Value

4.6 Cross Reference Lookups

None

4.7 Programs and Parameters

N.A




5 Detailed Functional Specifications

5.1 Interface Specifications

Interface Summary

Interface Name

PPR (Payment Process request – Pay Run Cycle)

Interface Short Description:

Direction: Inbound

Data Category: N.A

Interface Type: N.A

Business Priority: N.A

Frequency: Batch and On Demand

From System: Oracle EBS N.A

Additional Comments:

Business Rules

None.

5.2 Data Mappings

<List the details of Source to Target data field mappings, including logic and rules to be applied for the target system fields.>

5.3 Additional Processing Logic

None




5.4 Data Criteria Specifications

Data Selection and Filtering Criteria

N.A

Pre Extract Clean up Criteria

N.A




6 Test Scenario / Acceptance Criteria

Test Case #

Type Invoice# Amount Internal Bank

Supplier Bank

Error

1 Positive Inv1 .. 10 300 BoA Loyds bank

None




7 Other Requirements

7.1 Volume and Performance Requirements

1. Estimated # Records / Batch: <#>

2. Average Size / Record: <#>

7.2 Initiation, Frequency, and Scheduling Requirements

On Demand and Scheduled to run hourly.

7.3 Security and Controls Requirements

Supplier Address Book (EDI Location Code)

Internal Banks (EDI Location Code)

EC Gateway – Trading Partner, Code Conversion and Profiles




8 Exception and Error Handling

S.NO.Error/Exception

CodeError/Exception

TypeDescription

Handler

8.1 Log Output

8.2 Restart Procedures




9 Open/Closed Issues

9.1 Open Issues

Issue Id Description Opened By Responsible Due Date

1

2.

3.

9.2 Closed Issues

Issue Id Description Resolution Signoff Closed Date

1.

2.

3.




10 Appendix – Misc Attachments

