Previous Next JavaScript must be enabled to correctly display this content

## 3.1 Relationship

This topics describes the information to perform the bulk upload for the Relationship in Oracle® Banking Cash Management

Table 3-1 Relationship - Master Records File Upload

S.No | Attribute Name | Type | Character | Mandatory/Optional | Description
--- | --- | --- | --- | --- | ---
1 | INDICATOR | VARCHAR2 | 1 | M | This indicates if the record is for Main.
2 | CORPORATE_ID | VARCHAR2 | 20 | M | The corporate for whom the Relationship is being created / updated. Based on system flag if only OBSCF is implemented then this can be a Non customer id however then counterparty id’s have to be CIF’s only and cannot be non-customer. If OBCMS is implemented then this has to be a CIF only and cannot be non -customer id. In this case Counterparties can be a mix of NCID and/or CIF.
3 | EFF_FROM_DATE | DATE | - | CM | This field can be equal to Business Date or greater. This field has to be less than “Valid until Date” field. If left blank will be defaulted to branch CBD. In case if the user is uploading the file to only add a counterparty or modify a counterparty this field can be blank and the last saved Date will remain as is thus indicating no update to the file via file upload.
4 | EXPIRES_ON | DATE | - | O | Expires On
5 | AUTO_DEBIT_APPLICABLE | VARCHAR2 | 1 | O | Debit applicable flag is mandatory at Relationship Level. The value maintained at relationship level automatically applies to all the child records i.e. records in the grid, with respect to buyer or supplier or both unless the bank user explicitly maintains the record for a specific counterparty/spoke at grid level.
6 | HOLIDAY_TREATMENT | CHAR | 3 | CM | Next Business Date or Previous Business Date.Value can be NBD or PBD.
7 | AUTO_ACCEPTANCE | VARCHAR2 | 1 | O | If auto acceptance should be marked as Y Or N, at master level of the scheme. If Blank it will be defaulted to “N”. If auto acceptance days is blank and auto acceptance is Y then on upload of invoice the invoice should get accepted. If auto acceptance days is 0 and auto acceptance is Y then in the same day EOD the invoice should get accepted.
8 | NO_OF_DAYS | NUMBER | - | CM | If Auto acceptance is “Y” then user can input No. of Days after which the Auto Acceptance is valid. This field can be blank. Maximum value allowed is 999.
9 | ALLOW_OVERDUE_RCV | VARCHAR2 | 1 | O | Allow Overdue Receivables
10 | MAX_DAYS_OVERDUE | NUMBER | 3 | O | Maximum Days Overdue
11 | EXCESS_HANDLING | VARCHAR2 | 50 | O | Excess Handling
12 | EXCESS_REFUND_PARTY | VARCHAR2 | 20 | O | Excess Refund Party
13 | EXCESS_REFUND_PAYMENT_MODE | VARCHAR2 | 20 | O | Refund Payment Mode
14 | VALIDATE_LINKED_PO | VARCHAR2 | 1 | O | Validate Linked PO
15 | PAY_AUTO_DEBIT_APPLICABLE | VARCHAR2 | 1 | O | Automatic Debit Applicable for payables
16 | PAY_HOLIDAY_TREATMENT | VARCHAR2 | 3 | CM | Holiday Treatment for payables
17 | PAY_AUTO_ACCEPTANCE | VARCHAR2 | 1 | O | Automatic Acceptance for payables
18 | PAY_NO_OF_DAYS | NUMBER | - | CM | Number Of Days for payables
19 | PAY_ALLOW_OVERDUE_RCV | VARCHAR2 | 1 | O | Allow Overdue Receivables for payables
20 | PAY_MAX_DAYS_OVERDUE | NUMBER | 3 | O | Maximum Days Overdue for payables
21 | PAY_VALIDATE_LINKED_PO | VARCHAR2 | 1 | O | Validate Linked PO for payables
22 | PAY_EXCESS_HANDLING | VARCHAR2 | 50 | O | Excess Handling for payables
23 | PAY_EXCESS_REFUND_PARTY | VARCHAR2 | 20 | O | Excess Refund Party for payables
24 | PAY_EXCESS_REFUND_PAYMENT_MODE | VARCHAR2 | 20 | O | Refund Payment Mode for payables
25 | IS_ANOMALY_DETECTION_REQ | VARCHAR2 | 1 | O | Anomaly Detection Required in Invoices
26 | PAY_IS_ANOMALY_DETECTION_REQ | VARCHAR2 | 1 | O | Payable Anomaly Detection Required in Invoices

Table 3-2 Relationship - Child Record

S.No | Attribute Name | Type | Size | Mandatory Y/N | Description
--- | --- | --- | --- | --- | ---
1 | INDICATOR | VARCHAR2 | 1 | Y | Counter Party Indicator
2 | CORPORATE_ID | VARCHAR2 | 20 | Y | Corporate Id
3 | COUNTERPARTYID | VARCHAR2 | 20 | CM | Counter Party Id
4 | REGISTRATION_NUMBER | VARCHAR2 | 30 | CM | Registration Number
5 | PARTY_TYPE | VARCHAR2 | 5 | Y | Party Type
6 | STATUS | VARCHAR2 | 2 | N | Status
7 | PROGRAM_CODE | VARCHAR2 | 20 | N | Program Code
8 | NAME | VARCHAR2 | 105 | Y | Name
9 | SHORT_NAME | VARCHAR2 | 50 | N | Short Name
10 | INDUSTRY | CHAR | 20 | N | Industry
11 | CATEGORY | VARCHAR2 | 20 | N | Category
12 | ADDRESS_TYPE | VARCHAR2 | 15 | Y | Address Type
13 | COUNTRY_CODE | VARCHAR2 | 4 | Y | Country Code
14 | ADDRESS_LINE_1 | VARCHAR2 | 105 | Y | Address Line 1
15 | ADDRESS_LINE_2 | VARCHAR2 | 105 | N | Address Line 2
16 | ADDRESS_LINE_3 | VARCHAR2 | 105 | N | Address Line 3
17 | ADDRESS_LINE_4 | VARCHAR2 | 105 | N | Address Line 4
18 | PIN | VARCHAR2 | 20 | Y | Pin Code
19 | COUNTRY | VARCHAR2 | 3 | CM | Country
20 | PREFFERED_COMM_MODE | VARCHAR2 | 10 | M | Preferred Communication Mode
21 | MOBILE_NUMBER | VARCHAR2 | 20 | CM | Mobile Number
22 | PHONE_NUMBER | VARCHAR2 | 20 | CM | Phone Number
23 | EMAIL | VARCHAR2 | 50 | CM | Email
24 | FAX_NUMBER | VARCHAR2 | 50 | CM | Fax Number
25 | TAX_REF_NO_1 | VARCHAR2 | 50 | N | Tax Reference Number 1
26 | TAX_REF_NO_2 | VARCHAR2 | 50 | N | Tax Reference Number 2
27 | GIIN | VARCHAR2 | 50 | N | Giin
28 | EXPIRES_ON | DATE | - | N | Expires On
29 | AUTO_DEBIT_APPLICABLE | VARCHAR2 | 1 | N | Automatic Debit Applicable
30 | HOLIDAY_TREATMENT | CHAR | 3 | N | Holiday Treatment
31 | AUTO_ACCEPTANCE | VARCHAR2 | 1 | N | Automatic Acceptance
32 | NO_OF_DAYS | NUMBER | - | N | Number Of Days
33 | EXTERNAL_CODE | VARCHAR2 | 30 | N | External Code
34 | DIVISION_CODE | VARCHAR2 | 30 | N | Division Code
35 | CORPORATE_DIVISION_CODE | VARCHAR2 | 30 | N | Corporate Division Code
36 | ALLOW_OVERDUE_RCV | VARCHAR2 | 1 | N | Allow Overdue Receivables
37 | MAX_DAYS_OVERDUE | NUMBER | 3 | N | Maximum Days Overdue
38 | EXCESS_HANDLING | VARCHAR2 | 50 | N | Excess Handling
39 | EXCESS_REFUND_PARTY | VARCHAR2 | 20 | N | Excess Refund Party
40 | EXCESS_REFUND_PAYMENT_MODE | VARCHAR2 | 20 | N | Refund Payment Mode
41 | VALIDATE_LINKED_PO | VARCHAR2 | 1 | N | Validate Linked PO
42 | IS_ANOMALY_DETECTION_REQ | VARCHAR2 | 1 | - | Anomaly Detection Required in Invoices

Table 3-3 Relationship - External Code

S.No | Attribute Name | Type | Character | Mandatory Y/N | Description
--- | --- | --- | --- | --- | ---
1 | INDICATOR | VARCHAR2 | 1 | Y | Party Type Indicator
2 | CORPORATE_ID | VARCHAR2 | 20 | Y | Corporate Id
3 | COUNTERPARTYID | VARCHAR2 | 20 | Y | Counter Party Id
4 | EXTERNAL_CODE | VARCHAR2 | 30 | Y | External Code
5 | DIVISION_CODE | VARCHAR2 | 30 | N | Division Code
6 | CORPORATE_DIVISION_CODE | VARCHAR2 | 30 | N | Corporate Division Code

Parent topic: File Upload