2/27/2018 Document 1073685.

Copyright (c) 2018, Oracle. All rights reserved.

Troubleshooting Transmission Protocol: Local File System Delivery (Doc ID 1073685.1)

Modified: Jan 16, 2013 Type: TROUBLESHOOTING

In this Document

Purpose
Troubleshooting Steps
Prototol Parameters
Parameter Behavior

Common Problems

APPLIES TO:

Oracle Payments - Version 12.0.1 to 12.1.2 [Release 12.0 to 12.1]

Oracle Payments - Version 12.2.3 to 12.2.3 [Release 12.2]
Information in this document applies to any platform.
Checked for relevance on 16-Jan-2013

PURPOSE

The final stage of the Create Settlement Batches process is to deliver the formatted payload to the destination as specified by
the transmission configuration attached to the payment system.

Typically EFT (Bank Account Transfer) transactions will require the formatted payload to be sent manually to the bank,
therefore it must be saved in a local file within the EBS instance.

The Transmission Protocol "Local File System Delivery" implements this function.

There have been changes in the way the protocol behaves since base 12.0.0, therefore this guide will explain how different
released versions of the protocol behave and what is the final behavior.

TROUBLESHOOTING STEPS

There are three versions of the protocol: Base, V1 and the last version which is the one intended to remain with no changes.

Prototol Parameters

The Protocol takes three parameters in all its versions. In Oracle Payments Setup > Transmission Configurations creating (or
editing) a transmission configuration based on the protocol "Local File System Delivery" the parameters and possibility to edit
values will be exposed:

- File Directory: a physical directory on the Concurrent Processing Tier where the file is intended to be created.
Directory MUST have sufficient permissions such that the Concurrent Processes can write to it.
- File Name: varies with version, see bellow.
- Append To File (Y/N): Specifies if the file must be opened for appending or overwritting.

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=j76zr9zlo_285&id=1073685.1 1/3
2/27/2018 Document 1073685.1

Parameter Behavior

Base( $JAVA_TOP/oracle/apps/iby/net/FileDumpFunction.class version 120.3 or 120.2):

File Name is fully static, when specified it will not change from batch to batch. Therefore if the Append
parameter was not set to Y batches would overwrite their output (unless file was collected in between batch
runs).
If not specified File Name would default to <concurrent process id>.out
When using no File Name, File Directory was ignored and always would default to $APPLCSF/$APPLOUT
directories in the CP Tier.
Output File can be viewed from the CP User Interface as a normal .out file, this is not a desired effect in several
cases.
Most common symptom: Settlement batch file is not generated in Local File Directory. Batch completes
successfully but no file is written in Local File Directory, instead batch file is being generated in
$APPLCSF/$APPLOUT.
V1 ($JAVA_TOP/oracle/apps/iby/net/FileDumpFunction.class version 120.3.12000000.2 or 120.3.12010000.2. as
delivered in Patch 8331378):
File Name is fully static, when specified it will not change from batch to batch. Therefore if the Append
parameter was not set to Y batches would overwrite their output (unless file was collected in between batch
runs).
If not specified File Name would default to <system timestamp>.out
File Directory is always used and if left blank defaults to $APPLCSF/$APPLOUT.
Output File no longer can be seen in the CP User Interface.
Most common symptom: Settlement batch file is being overwritten between batches.
Final ($JAVA_TOP/oracle/apps/iby/net/FileDumpFunction.class version 120.3.12000000.3 or 120.3.12010000.3, as
delivered in Patch 8354506):
File Name, if specified, is a prefix
to the full file name. The file name will be constructed as
<prefix>_<reference>.out where:
<prefix> is a string entered in the UI for the parameter File Name (can be left blank and there will be
no <prefix>_)
<reference> is the batch_id -or- if no batch_id available the system timestamp
File Directory no more defaulting is allowed the directory has to be explicitly specified, be fully qualified, have
correct permissions and reside in the CP tier. If multiple CP tiers exist the directory name must be common to
ALL tiers (e.g: /tmp/iby_output)
Append To File behaves the same however it has little relevance in this new version.

Global Customer Support recommends upgrading to the final version by applying Patch 8354506

Common Problems

File is not generated

1. Are you looking in the correct Box ? The file will always be generated in the CP tier. If several CP tiers the file will be
only in one of them.
2. Is the directory specified in the Transmission Protocol details existing in the CP tier ? Has the same correct permissions
?
3. If no directory was specified, have you checked $APPLCSF/$APPLOUT directories in each CP Box ?
4. If you did not specify a File Name, are you looking for the file with the CP process id ? try looking for the file with the
Settlement Batch Id, or a long number (system timestamp) as a name.

File is being overwritten

1. The best action is to upgrade to Patch 8354506

2. If not possible either do
https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=j76zr9zlo_285&id=1073685.1 2/3
2/27/2018 Document 1073685.1

1. Do not specify a File Name at all and look for the file named as <cp id>.out or <timestamp>.out
-OR-
2. Collect the file between Create Settlement Batches runs

Is there a way to generate the file with a Custom naming logic ?

While GCS does not support custom code there is a document providing guidance on how to customize this portion of the
application. Note that GCS will require you to reproduce the issue with the vanilla protocol should problems occur with the
custom one.

Note.748309.1 How to customize the file name for transmission protocol Local File System Delivery

Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=j76zr9zlo_285&id=1073685.1 3/3