CE Bank and Branch Upload

Description

CE Bank and Branch Upload creates and maintains banks and their bank branches in Oracle Cash Management directly from Excel – one branch per row, with the parent bank created automatically the first time it is referenced. Each row names a bank (by country and name) and a branch beneath it, so you can load an entire bank and branch structure, spanning several countries if needed, in a single pass.

When to use it

  • Load a large set of new banks and branches during implementation or a new-bank rollout.
  • Add branches to a bank that already exists – the bank is reused automatically.
  • Bulk-update branch attributes: branch number, branch type, BIC / SWIFT code, EFT number, alternate name or description.
  • Load banks and branches for several countries in one file.
  • Populate branch- or bank-level descriptive flexfield segments in bulk.
  • Maintain the bank and branch reference data that bank accounts and bank statement import rely on.

Before you start

  • Blitz Report is installed and you are signed in to a responsibility authorized for Cash Management bank setup.
  • Every row has the three identifying values: Country, Bank Name and Branch Name.
  • The Country is a valid country from the standard list.
  • If you use a Branch Type, it is one of the standard routing or clearing types (ABA, CHIPS, SWIFT, Other).

Step 1 – Open the upload and choose a mode

Run CE Bank and Branch Upload from the Blitz Report menu and choose an Upload Mode:

  • Create – an empty template for entering new banks and branches.
  • Create, Update – downloads existing bank branches so you can edit and re-upload them. Any new rows you add are still created.

The upload decides per row whether to create or update by matching what you enter (see Step 4); the mode mainly controls whether existing data is downloaded into the template.

Step 2 – Set the parameter and download the template

This upload has a single parameter:

ParameterPurpose
Upload ModeCreate (empty template) or Create, Update (existing bank branches downloaded for editing). Default is Create.

Click Download to open the Excel template.

Step 3 – Enter the bank

On each row enter the bank’s Country and Bank Name (both required); add a Bank Number if you use one. The first time a bank is referenced it is created, and its Short Bank Name, Alternate Bank Name and any Bank Attribute (flexfield) values are applied. If the bank already exists, it is reused unchanged.

Step 4 – Enter the branch

Enter the Branch Name (required) and the branch attributes: Branch Number, Branch Type (ABA, CHIPS, SWIFT or Other – leave blank for a generic branch), BIC / SWIFT Code, EFT Number, Alternate Branch Name, Description, and any branch Attribute (flexfield) values. The branch is matched within its bank by name: if it exists it is updated, otherwise it is created.

Step 5 – Validate and Save

Click Validate and Save. This checks for missing required values and runs any extra validation the upload defines, then saves the file. Correct anything it flags before continuing.

Step 6 – Upload and view the result

Back in Blitz Report, click Upload and select your saved file. This submits the Blitz Upload request, which processes each row. When it finishes, a result report opens showing each row as success or error.

What’s produced

  • Banks and bank branches in Cash Management, ready for bank-account setup and statement import.
  • A result report listing every row with a status (success or error) and a message – “Branch created” or “Branch updated” on success, or the validation or API message on failure.

Common questions

Does this update an existing bank’s details?
No. Banks are only ever created. If a matching bank already exists it is reused, and only the branch fields are created or updated. The short and alternate bank name and bank flexfields apply only when the bank is first created.

How does it know whether to create or update?
By matching. The bank is found by Country and Bank Name (and Bank Number if supplied); the branch is found by its bank and Branch Name. No match means create; a match means update (for branches).

Can I load banks for several countries in one file?
Yes. Country-specific routing-number format checks are switched off so multi-country data loads cleanly.

What if I leave Branch Type blank?
The branch is created with a generic type. Set it only when a specific routing or clearing type (ABA, CHIPS, SWIFT, Other) applies.

Can I delete a bank or branch with this upload?
No. It only creates and updates; it does not delete banks or branches.

Troubleshooting

MessageCauseWhat to do
Country is required / Bank Name is required / Branch Name is requiredOne of the three mandatory identifying fields is blank on the row.Fill in Country, Bank Name and Branch Name on every row.
Bank creation failedThe bank did not exist and Cash Management rejected the new bank (invalid or duplicate data).Read the appended message, correct the bank fields (Country, Bank Name, Bank Number) and re-upload.
Branch creation failedThe new branch was rejected (for example an invalid Branch Type, BIC / SWIFT code or flexfield value).Fix the offending branch field or flexfield value per the message and re-upload.
Branch update failedThe existing branch could not be updated.Review the appended message, correct the field and re-upload the row.
Branch Type or Country not in listA value typed into a validated column is not a recognized list value.Pick the value from the dropdown.
select
null action_,
null status_,
null message_,
null request_id_,
null modified_columns_,
to_char(null) row_id,
(select ft.territory_short_name from fnd_territories_vl ft where ft.territory_code=cbbv.bank_home_country) country,
cbbv.bank_name,
cbbv.bank_number,
cbbv.short_bank_name,
cbbv.bank_name_alt alternate_bank_name,
cbbv.bank_branch_name branch_name,
cbbv.branch_number,
xxen_util.meaning(cbbv.bank_branch_type,'BANK_BRANCH_TYPE',222) branch_type,
cbbv.eft_swift_code bic_swift_code,
cbbv.eft_user_number eft_number,
cbbv.bank_branch_name_alt alternate_branch_name,
cbbv.description,
hp.attribute_category,
hp.attribute1,
hp.attribute2,
hp.attribute3,
hp.attribute4,
hp.attribute5,
hp.attribute6,
hp.attribute7,
hp.attribute8,
hp.attribute9,
hp.attribute10,
hp.attribute11,
hp.attribute12,
hp.attribute13,
hp.attribute14,
hp.attribute15,
hp.attribute16,
hp.attribute17,
hp.attribute18,
hp.attribute19,
hp.attribute20,
hp.attribute21,
hp.attribute22,
hp.attribute23,
hp.attribute24,
hpb.attribute_category bank_attribute_category,
hpb.attribute1 bank_attribute1,
hpb.attribute2 bank_attribute2,
hpb.attribute3 bank_attribute3,
hpb.attribute4 bank_attribute4,
hpb.attribute5 bank_attribute5,
hpb.attribute6 bank_attribute6,
hpb.attribute7 bank_attribute7,
hpb.attribute8 bank_attribute8,
hpb.attribute9 bank_attribute9,
hpb.attribute10 bank_attribute10,
hpb.attribute11 bank_attribute11,
hpb.attribute12 bank_attribute12,
hpb.attribute13 bank_attribute13,
hpb.attribute14 bank_attribute14,
hpb.attribute15 bank_attribute15,
hpb.attribute16 bank_attribute16,
hpb.attribute17 bank_attribute17,
hpb.attribute18 bank_attribute18,
hpb.attribute19 bank_attribute19,
hpb.attribute20 bank_attribute20,
hpb.attribute21 bank_attribute21,
hpb.attribute22 bank_attribute22,
hpb.attribute23 bank_attribute23,
hpb.attribute24 bank_attribute24
from
ce_bank_branches_v cbbv,
hz_parties hp,
hz_parties hpb
where
1=1 and
cbbv.branch_party_id=hp.party_id and
cbbv.bank_party_id=hpb.party_id
Parameter NameSQL textValidation
Upload Mode
:p_upload_mode like '%' || xxen_upload.action_update
LOV