Object Group HCM Data Loader Files for Bank Reprocessing
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.
You must transform this information returned by the bank into the HCM Data Loader .dat file formats required by the Object Group HCM Data Loader.
You must provide a unique name in the Object Group Name field each time you create an HCM Data Loader .dat file. You must then load the Object Group HCM Data Loader file into the Oracle Web Center Content server.
The bank information is stored in the Object Group table, under the Process Information Group Object Group Type. Use the Object Group UI and the name given in the Object Group HCM Data Loader file to view the information loaded by the ObjectGroup.dat and ObjectGroupStore.dat files, as part of the Process Bank Corrections 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 retrieve and use the bank information necessary for the flow.
Load Process Information Group Object Group
Create and use these HCM Data Loader .dat files to process the bank information by the HCM Data Loader.
-
ObjectGroup.dat file to create the object group
-
ObjectGroupStore.dat file to load the bank information returned by the bank
ObjectGroup.dat File Format
Here's the list of attributes for loading the ObjectGroup.dat file.
HCM Data Loader Attribute |
Required |
User Interface Prompt |
Description |
---|---|---|---|
ObjectGroupName |
Yes |
Name |
The name of the object. |
ObjectGroupCode |
Yes |
Does not 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 Type field. |
The code of the object group type. The supported
value 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
Here's the list of attributes for loading the ObjectGroupStore.dat file.
HCM Data Loader Attribute |
Required |
User Interface Prompt |
Description |
---|---|---|---|
ObjectGroupCode |
Does not 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 object group store file. |
assignmentNumber |
Assignment Number |
The assignment number of the employee whose payment is 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 the flow. The date entered here, is stamped against each process in the flow. It is the date the personal payment method is end dated and the payment is voided. Enter a value if you want one particular payment to have a different payment date to that of the payment date entered in the flow. |
|
paymentReference |
Yes |
Payment Reference |
A unique identifier for a specific payment line on the original NACHA file that was sent to the bank. |
Amount |
Amount |
The original amount of the rejected payment. |
|
chequeNumber |
Cheque Number |
The cheque number used in the External manual payment task and printed on the manual external payment cheque template. |
|
replacementBranchNumber |
Replacement Branch Number |
Enter a value if the branch number (routing transit number) needs updating. If a value is entered in this column, it tells the process that the bank account associated to the personal payment method (PPM) used for payment needs updating. |
|
replacementAccountType |
Replacement Account Type |
Enter a value if the employee's account type needs updating. If a value is entered in this column, it tells the process that the bank account associated to the PPM used for payment needs updating. |
|
replacementAccountNumber |
Replacement Account Number |
Enter a value if the employee's account number needs updating. If data is entered in this column, it tells the process that the bank account associated to the PPM used for payment needs updating. |
|
makeExternalPayment |
Make External Payment |
Enter 'Yes' if you want to void the original payment and make a manual external cheque payment. Valid values for this attribute are 'Yes' or 'No'. |
|
|
Return Reason Code |
The reason for rejecting the direct deposit payment. The entered value is stamped on the external manual pay record. |
|
|
Employee Name |
Name of the employee whose payment is rejected, or whose bank information needs updating. |
The Update Personal Payment Methods task within the flow determines, through built in logic, whether the personal payment method needs end dating or updating. The logic is as follows:
-
If there is a value in the 'Replacement Branch Number' field, the 'Replacement Account Number' field or the 'Replacement Account Type' field, then the process updates the Personal Payment Method.
-
If any of the above mentioned field is null then the process end dates the Personal Payment Method.
You can delete information loaded to the process information group object group type using the HCM Data Loader. You must take care when deleting the records, because you can't recover the deleted records.
For more information on creating the HCM Data Loader .dat files and using the HCM Data Loader to upload data, refer to the HCM Data Loader User's Guide on My Oracle Support.