EDI Setups for 820 Outbound

Bank Accounts Tab	(At Supplier Site)
	Supplier Name	APPLIED INDUSTRIAL FLOORING
	Site Name	MISSISSAUGA
	Payment Method	Electronic
	Bank Account Name	APPLIED INDUSTRIAL FLOORING
	Number	1
	Bank Name	DUMMY-CAD
	Number	9999
	Branch Name	DUMMY BANK-C

EDI Tab	(At Supplier Site)
	EDI ID Number	99999
	Payment Method	ZZZ
	Remittance Method	EDI to payee
	Remittance Instruction	EDI Remittance Instructions
	Transaction Handling	C

Payment Formats

Document Name	HSBC - CAD CNR
Disbursement Type	Combined
Payment Format	EDI Outbound Program - CAD
Payment Method	Electronic

Define Trading Partners How to you setup EDI Payment Outbound 820? EDI Payment Outbound 820 (ECEPYO)  1 Profile Options Setup  Using the System Administrator Responsibility navigate to Profile -> System Set the following:        Profile = 'ECE: Output file path'      Site = ... (Path for output file directory)             Example: Site = /sqlcom/outbound     2 init.ora setup Add an environment vialable "utl_file_dir" in $ORACLE_HOME/dbs/init.ora  Example:  utl_file_dir = /sqlcom/outbound   This path needs to be exactly same as the path you have defined in Profile  Option.      3 Format Program Setup  Using the Payables Responsibility, navigate to Setup->Payment->Format Set the following:      Payment Format = EDI Outbound Program      Payment Method = Electronic Payments     Currency = USD     Build Payments = Build Payments Program     Format Payments = EDI Outbound Program    4 Internal Bank Account Setup  Using the Payables Responsibility, navigate to Setup->Payment->Banks  setup a Bank Account as follows:        Bank Branch Type = (Select from LOV)      Account Use = Internal     Account Type = EDI     EDI Location = ...(Path for output file directory)   Create a new Payment Document to use  Payment Format = EDI Outbound Program     5 Supplier Bank Account Setup  Using the Payables Responsibility, navigate to Setup->Payment->Banks   Create a new Bank Account, set:        Bank Branch Type = (Select from LOV)     Account Use = Supplier     Account Type = EDI    6 Supplier Site Setup  Using the Payables Responsibility, navigate to Supplier->Entry   Query the supplier, then choose the Site.    Bank Account Region:     Fill in the supplier bank account,     Set Primary to 'Yes'.    Electronic Payment Region: set the following (Contact with your internal bank branch to set them up):      Payment Method     Payment Format     Remittance Method      Remittance Instruction     Transaction Handling   7 Trading Partner Setup Using the EDI Manager Responsibility, navigate to Trading Partners. Define a trading partner for the internal bank branch. Assignment Region:      Bank Branch = the internal bank branch. Contact Region:      Set the contact information. Detail Region:      Document = Payment/Remittance Outbound, EDI = Yes. 8 Invoice for EDI 820  Set "Payment Method = Electronic Payments" for the invoices which you'd like  the payment batch to select. 9 Preliminary Payment Regiter Create a payment batch for using Payment Format = EDI Outbound Program.  View  the Preliminary Payment Register to make sure there is at least one document  going to be paid before you run the Format Payment Program. 10 Format Payment Program and ECEPYO output file If the Format Payment Program completes successfully, view the output, it will  give you a number, for example, the number is 123.  The output file ECEPYO.123 will be in /sqlcom/outbound directory.

hr_locations.location_id = financials_system_parameters.bill_to_location_id	AP Financial Options
Set  Bank Branch = the internal bank branch	EDI Trading Partners	Go to the Trading Partner Setup Assignment Region

Subledger Data Conversion - When two different Calendar is used in Primary and Secondary Ledgers

When Primary and Secondary Ledgers use Different Calendars, It is possible to create a Secondary Ledger with a Subledger Data Conversion.

(i) Secondary ledgers can have a different calendar than the primary ledger.

Secondary ledgers represent the primary ledger's accounting data in another accounting representation that might differs in one or more of the following ways:

• Chart of accounts
• Accounting calendar/period type combination
• Currency
• Subledger accounting method
• Ledger processing options

(ii) Subledger Data Conversion Level

This data conversion level uses both Subledger Accounting and the General Ledger Posting program to create the necessary journals in both the primary and secondary ledgers simultaneously. Subledger Accounting creates the journal entries from subledger transactions if the subledger integrates with Subledger Accounting.
General Ledger Posting creates the journal entries for all other transactions that do not integrate with Subledger Accounting, including manual journal entries

(iii) How data is converted if the calendar is different:

The following conversion rules are used to convert data from the primary ledger to the secondary ledger:

• Calendar Conversion: If the secondary ledger uses a different accounting calendar from the primary ledger, the journal effective date determines the corresponding non-adjusting period in the secondary ledger.

However, when running create accounting from the subledger, user gets the following error message:  "The access set  XXXX Primary Ledger assigned to the system profile option GL: Data Access Set does not include read and write privileges for the ledger Vision operations Secondary Ledger and the balancing or management segment value.

Please use the Data Access Sets window in General Ledger to include read and write privileges for the ledger and segment values or assign a different ledger access set to the system profile option."

Per the Oracle Financials Implementation Guide for Release 12, when creating a data access set, all ledgers and ledger sets assigned to a data access set must share the same chart of accounts and accounting calendar/period type combination.

The way to provide the subledger access to both the primary ledger and secondary ledger, while running create accounting, is to set the following system profile options:

• GL: Data Access Set -- to point to the primary ledger
• SLA: Additional Data Access Set -- to point to the secondary ledger