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 Identification
INT 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
1.0
Additions/Modifications
22-Oct-2012
CR#
Initial Release for review
Prepared/Revised
by
Srini Nemala
Document Review/Approval History

Date
22-Oct-2012
Document
Version
1.0
Name
Srini Nemala
Organization/Title
MST
Comments
Initial Release
Distribution of Final Document

The following people are designated recipients of the final version of this document:
Name
Daniel Fryer
Organization/Title
MST/EDI Analyst
Nancy Levenson
Bill Walke
Dinnetta Kinman
Document Control Information

2-Nov-12
Page ii

115519074.doc
Functional Specification (Interface)EDI 810

Interface MD 50 Spec
Table of Contents
1 Interface Overview....................................................................................................................................4
1.1 Objective..........................................................................................................................................4
1.2 Business Needs...............................................................................................................................4
1.3 Major Features ................................................................................................................................4
1.4 Modules Involved.............................................................................................................................4
1.5 Systems Involved............................................................................................................................4
1.6 Assumptions....................................................................................................................................5
1.7 Dependencies and Prerequisites....................................................................................................5
1.8 Related Documents.........................................................................................................................5
1.9 Nomenclature...................................................................................................................................5
2 References to Requirements....................................................................................................................7
3 Functional Approach/Process Description..............................................................................................8
3.1 Source and Target Systems Description........................................................................................8
3.2 Process Flow Diagram.....................................................................................................................8
3.3 Process Steps Description..............................................................................................................8
4 Application Setup Requirements...........................................................................................................10
4.1 Core Application Module Setup....................................................................................................10
4.2 System Parameters........................................................................................................................10
4.3 Lookup Definitions........................................................................................................................10
4.4 Value Sets......................................................................................................................................10
4.5 Profile Options...............................................................................................................................10
4.6 Cross Reference Lookups.............................................................................................................10
4.7 Programs and Parameters ............................................................................................................10
5 Detailed Functional Specifications........................................................................................................11
5.1 Interface Specifications.................................................................................................................11
5.1.1 Interface Summary..............................................................................................................11
5.1.2 Business Rules....................................................................................................................11
5.2 Data Mappings...............................................................................................................................11
5.3 Additional Processing Logic.........................................................................................................11
5.4 Data Criteria Specifications...........................................................................................................11
5.4.1 Data Selection and Filtering Criteria...................................................................................12
5.4.2 Pre Extract Clean up Criteria...............................................................................................12
6 Test Scenario / Acceptance Criteria.......................................................................................................13
7 Other Requirements................................................................................................................................14
7.1 Volume and Performance Requirements......................................................................................14
7.2 Initiation, Frequency, and Scheduling Requirements..................................................................14
7.3 Security and Controls Requirements...........................................................................................14
8 Exception and Error Handling................................................................................................................15
8.1 Log Output.....................................................................................................................................15
8.2 Restart Procedures........................................................................................................................15
9 Open/Closed Issues................................................................................................................................16
9.1 Open Issues...................................................................................................................................16
9.2 Closed Issues.................................................................................................................................16
10 Appendix Misc Attachments..............................................................................................................17
Table of Contents
2-Nov-12
Page iii

115519074.doc

1
1.1
Interface Overview
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 Macys
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
Macys 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
1.5
Modules Involved
EC Gateway
Accounts Payable
Payments
Purchasing/iProcurement
Systems Involved
Oracle EBS
EDI Translation tool.
Detailed Functional Specifications

2-Nov-12
Page 4 of 17

115519074.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
1.8
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
Related Documents
Document Name
Revision
RPT_FS_MACYS_PO_RP
T001
1.9
Document Description
PO output for communications (Non
EDI suppliers)
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.

2-Nov-12
Page 5 of 17

115519074.doc

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-Nov-12
Page 6 of 17

115519074.doc

References to Requirements
Requirement Id

2-Nov-12
Description
Page 7 of 17

115519074.doc

Functional Approach/Process Description
3.1
Source and Target Systems Description

Source: Oracle EBS & GXS
Target: Banks
3.2
Process Flow Diagram
Oracle Outbound EDI 820 (Payment & Remittance)

EC Gateway / EBS
Create
Directory
Location
Create/
update
Code
conversions
EDI Translator
Internal Bank
Translate
payment &
remittance text file
to VICS format
Process Payment
Request
Enable EDI
820
Transaction
Create/Upd
Internal Bank
Supplier Bank
Payment
Attributes as
Elecronic
Payer to
Run
Payment
Request
One Time Configuration

Payment User Regular Activity
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)

2-Nov-12
Page 8 of 17

115519074.doc

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.

2-Nov-12
Page 9 of 17

115519074.doc

4.1
4.2
Application Setup Requirements
Supplier Site (EDI Location Code)
Internal Bank (Edi Location Code)
EC Gateway Trading Partner, Code Conversion, Profiles
Core Application Module Setup
Supplier Site (EDI Location Code)
Internal Bank (Edi Location Code)
EC Gateway Trading Partner, Code Conversion, Profiles
System Parameters
System Parameter
4.3
Description
Meaning
Description
Profile Options
Profile Option Name
4.6
Meaning
Value Sets
Value Set Name
Type & Size
Validation
Value
4.5
Value
Lookup Definitions
Lookup Type
Application
Description
Lookup Code
4.4
Application
Application
Accessibility Level
Value
Cross Reference Lookups

None
4.7
Programs and Parameters

N.A

2-Nov-12
Page 10 of 17

115519074.doc

5
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.>
820_Transaction_La
EP Check example
yout_Definition_041012.xlsx with Remit.pdf
5.3
Additional Processing Logic

None
5.4
Data Criteria Specifications

2-Nov-12
Page 11 of 17

115519074.doc

Data Selection and Filtering Criteria
N.A
Pre Extract Clean up Criteria
N.A

2-Nov-12
Page 12 of 17

115519074.doc

Test Scenario / Acceptance Criteria

Test
Case #
1
Type
Invoice#
Amount
Internal
Bank
Supplier
Bank
Error
Positive
Inv1 .. 10
300
BoA
Loyds
bank
None

2-Nov-12
Page 13 of 17

115519074.doc

7
7.1
Other Requirements
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

2-Nov-12
Page 14 of 17

115519074.doc

Exception and Error Handling
S.NO.
Error/Exception
Code
8.1
Log Output
8.2
Restart Procedures

2-Nov-12
Error/Exception
Type
Page 15 of 17
Description
Handler

115519074.doc

9
9.1
Open/Closed Issues
Open Issues
Issue Id
Description
Opened By
Description
Resolution
Responsible
Due
Date
1
2.
3.
9.2
Closed Issues
Issue Id
Signoff
Closed
Date
1.
2.
3.

2-Nov-12
Page 16 of 17

115519074.doc

10 Appendix Misc Attachments

2-Nov-12
Page 17 of 17

115519074.doc

Int Fs Macy Iby Iby056 Edi 820 Payment Outbound

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Int Fs Macy Iby Iby056 Edi 820 Payment Outbound

Enviado por

Direitos autorais:

Formatos disponíveis

Macy's Financial Application

Document Control Information

INT FS_MACY_<Product Short

Functional Specification (Interface)

MACYS Financials Application

Document Edit History

Initial Release for review

Document Review/Approval History

Distribution of Final Document

Document Control Information

MACYS Financials Application

Functional Specification (Interface)EDI 810

MACYS Financials Application

Functional Specification (Interface)EDI 810

following basic business needs.

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

Ability for banks to pay suppliers appropriately.

Detailed Functional Specifications

MACYS Financials Application

Functional Specification (Interface)EDI 810

Dependencies and Prerequisites

Create outbound directories to store raw file data content.

Define code conversion as required

Required configuration / setup would be available for Interface

All related master data would be converted prior to this Interface

Interchange Control Header

Authorization qualifiers, security

Transaction Set Header

EDI translator envelope Identification

Beginning Segment for Invoice

Currency Details Segment for

Address Segments of Invoice

Ship To , Remit Address etc.

Reference Number Segment for

Supplier Number, Line Numbers,

Baseline Item Data segments for

Line Item Number, Quantity, UOM etc...

Terms Segment of Invoice

Discount Terms like Discount %, Net

Detailed Functional Specifications

MACYS Financials Application

Functional Specification (Interface)EDI 810

Total Monetary Value Summary

Total Dollar value of Invoice

Transaction Totals Segment of

Total number of line Items in the

Transaction set Trailer segment of

Includes number of segments,

Automated Clearing House

NACHA Payment Format (Cash

NACHA Payment Format

Payment Process Profile

Payment Process Template

Payment Process Request

Preliminary Payment Register

National Automatic Clearing

Detailed Functional Specifications

MACYS Financials Application

Functional Specification (Interface)EDI 810

Detailed Functional Specifications

MACYS Financials Application

Functional Specification (Interface)EDI 810

Functional Approach/Process Description