Before you run the Process Bank Corrections File flow, use the HCM Data Loader to load the information returned by the bank.
The bank returns a file containing details of the payments that are rejected. Before you load the information, transform this information returned by the bank into the HCM Data Loader .dat file formats required by the Object Group HCM Data Loader.
Provide a unique name in the Object Group Name field each time you create an HCM DataLoader .dat file. You must then load the Object Group HCM Data Loaderfile into the Oracle Web Center Content server.
The bank information is stored in the Object Grouptable, under the Process Information Group Object Group Type. Usethe Object Group UI and the name given in the Object Group HCM DataLoader file to view the information loaded by the ObjectGroup.dat and ObjectGroupStore.dat files, as part of the Process BankCorrections Flow.
When you load the ObjectGroupStore.dat file into the Oracle Web Center Content server, a UCM ID is generated.The Process Bank Corrections File flow uses the UCM ID to retrieveand use the bank information necessary for the flow.
Load Process Information Group Object Group
Create and use the following HCM Data Loader .datfiles to process the bank information by the HCM Data Loader.
-
ObjectGroup.dat file to createthe object group
-
ObjectGroupStore.dat file to loadthe bank information returned by the bank
ObjectGroup.dat File Format
This table lists the attributes for loading the ObjectGroup.datfile.
| HCM Data Loader Attribute | Required | User Interface Prompt | Description |
|---|---|---|---|
| ObjectGroupName | Yes | Name | The name of the object. |
| ObjectGroupCode | Yes | Doesn't appear on the UI. | The code of the object group. |
| LegislativeDataGroup | Yes | Legislative Data Group | THE NAME OF THE LEGISLATIVE DATA GROUP. |
| ObjectGroupTypeCode | Yes | The meaning of the code is displayed in the Typefield. | The code of the object group type. The supportedvalue for the process information group type is |
| StartDate | Yes | Start Date | The start date of the object group. |
| EndDate | Yes | End Date | The end date of the object group. |
ObjectGroupStore.dat File Format
This table lists the attributes for loading the ObjectGroupStore.datfile.
| HCM Data Loader Attribute | Required | User Interface Prompt | Description |
|---|---|---|---|
| ObjectGroupCode | Doesn't appear on the UI. | The code of the object group. | |
| LegislativeDataGroup | Legislative Data Group | THE NAME OF THE LEGISLATIVE DATA GROUP. | |
| SequenceNumber | Yes | Sequence | A unique identifier for a row of data in the objectgroup store file. |
| assignmentNumber | Assignment Number | The assignment number of the employee whose paymentis rejected, or whose bank information needs updating. | |
| paymentDate | Payment Date | The original payment date of the rejected payment. | |
| processDate | Process Date | This date overrides the process date entered in theflow. The date entered here, is stamped against each process in theflow. It's the date the personal payment method is end dated and thepayment is voided. Enter a value if you want one particular paymentto have a different payment date to that of the payment date enteredin the flow. | |
| paymentReference | Yes | Payment Reference | A unique identifier for a specific payment line, such as the payment in the original NACHA file that was sent to the bank. |
| Amount | Amount | The original amount of the rejected payment. | |
| checkNumber | Check Number | The check number used in the External manual paymenttask and printed on the manual external payment check template. | |
| replacementBranchNumber | Replacement Branch Number | Enter a value if the branch number (routing transitnumber) needs updating. If a value is entered in this column, ittells the process that the bank account associated to the personalpayment method (PPM) used for payment needs updating. | |
| replacementAccountType | Replacement Account Type | Enter a value if the employee's account type needsupdating. If a value is entered in this column, it tells the processthat the bank account associated to the PPM used for payment needsupdating. | |
| replacementAccountNumber | Replacement Account Number | Enter a value if the employee's account number needsupdating. If data is entered in this column, it tells the processthat the bank account associated to the PPM used for payment needsupdating. | |
| makeExternalPayment | Make External Payment | Enter 'Yes' if you want to void the original paymentand make a manual external check payment. Valid values for this attributeare 'Yes' or 'No'. | |
| | Return Reason Code | The reason for rejecting an EFT payment. The enteredvalue is stamped on the external manual pay record. | |
| | Employee Name | Name of the employee whose payment is rejected, orwhose bank information needs updating. |
The Update Personal Payment Methods task within theflow determines, through built in logic, whether the personal paymentmethod needs end dating or updating. The logic is as follows:
-
If there's a value in the 'ReplacementBranch Number' field, the 'Replacement Account Number' field or the'Replacement Account Type' field, then the process updates the PersonalPayment Method.
-
If any of the above mentioned fields are null then the process end dates the Personal Payment Method.
You can delete information loaded to the processinformation group object group type using the HCM Data Loader. Youmust take care when deleting the records, because you can't recoverthe deleted records.
For more information on creating the HCM Data Loader.dat files and using the HCM Data Loader to upload data, refer tothe HCM Data Loader User's Guide on My Oracle Support.
