Oracle Apps Customer Interface Status error codes

If you are running Customer Interface – RACUST and there is an error message in the
INTERFACE_STATUS column, but you don’t know what it means. Then here is the meaning for every error code.

INTERFACE_STATUS appears in the following tables:
RA_CUSTOMERS_INTERFACE_ALL
RA_CUSTOMER_PROFILES_INT_ALL
RA_CONTACT_PHONES_INT_ALL
RA_CUSTOMER_BANKS_INT_ALL
RA_CUST_PAY_METHOD_INTERFACE

These are the message codes and their meaning:
A1 –> The customer reference for update does not exist in RA_CUSTOMERS
A2 –> The address reference for update does not exist in RA_ADDRESSES
A3 –> Customer reference for insert is already defined in RA_CUSTOMERS
A4 –> Site use for this address reference already exists in the database
A5 –> Customer Number already assigned to a different customer
B1 –> ORIG_SYSTEM_ADDRESS_REF is mandatory when specifying an address
B2 –> ADDRESS1 is mandatory when specifying an address
B3 –> COUNTRY is mandatory when specifying an address
B4 –> SITE_USE_CODE is mandatory when inserting an address
B5 –> PRIMARY_SITE_USE_FLAG is mandatory when inserting an address
B6 –> CUSTOMER_CLASS_CODE is not defined in AR_LOOKUPS
B7 –> CUSTOMER_PROFILE_CLASS_NAME has an invalid value
B8 –> STATE is not defined in AR_LOCATION_VALUES
B9 –> COUNTRY is not defined in fnd_territories
B0 –> SITE_USE_CODE is not defined in AR_LOOKUPS
C1 –> This customer reference has two different customer names defined
C2 –> This customer reference has two different customer numbers defined
C3 –> This customer reference has two different parent customer references
C5 –> Customer reference has two different customer class codes defined
C6 –> This customer reference has two identical primary site uses defined
D1 –> Address reference has two different ADDRESS1 values
D2 –> Address reference has two different ADDRESS2 values
D3 –> Address reference has two different ADDRESS3 values
K1 –> Concurrent request failed
K3 –> This customer reference has two different customer types defined
L1 –> COLLECTOR_NAME is mandatory when no profile class specified
L2 –> TOLERANCE is mandatory when no profile class specified
L3 –> DISCOUNT_TERMS is mandatory when no profile class specified
L4 –> DUNNING_LETTERS is mandatory when no profile class specified
L5 –> INTEREST_CHARGES is mandatory when no profile class specified
L6 –> STATEMENTS is mandatory when no profile class specified
L7 –> CREDIT_BALANCE_STATEMENTS mandatory when no profile class specified
L9 –> DUNNING_LETTER_SET_NAME is mandatory when DUNNING_LETTERS is “Yes”
L0 –> CHARGE_ON_FINANCE_CHARGE_FLAG mandatory when INTEREST_CHARGES is “Yes”
M1 –> INTEREST_PERIOD_DAYS is mandatory when INTEREST_CHARGES is “Yes”
M3 –> COLLECTOR_NAME has an invalid value
M4 –> CREDIT_CHECKING has an invalid value
M5 –> TOLERANCE has an invalid value
M6 –> DISCOUNT_TERMS has an invalid value
M7 –> DUNNING_LETTERS has an invalid value
M8 –> INTEREST_CHARGES has an invalid value
M9 –> STATEMENTS has an invalid value
M0 –> CREDIT_BALANCE_STATEMENTS has an invalid value
N1 –> CREDIT_HOLD has an invalid value
N2 –> CREDIT_RATING has an invalid value
N3 –> RISK_CODE has an invalid value
N4 –> STANDARD_TERM_NAME which contains the payment terms has an invalid value
N5 –> OVERRIDE_TERMS has an invalid value
N6 –> DUNNING_LETTER_SET_NAME has an invalid value
N7 –> STATEMENT_CYCLE_NAME has an invalid value
N8 –> ACCOUNT_STATUS has an invalid value
N9 –> PERCENT_COLLECTABLE has an invalid value
N0 –> AUTOCASH_HIERARCHY_NAME which contains the AutoCash rule has an invalid value
O1 –> STATEMENT_CYCLE_NAME is mandatory when STATEMENTS is “Yes”
O2 –> LOCATION must be null when auto-numbering is set to “Yes”
O3 –> LOCATION is mandatory when auto-numbering is set to “No”
O4 –> CREDIT_CHECKING is mandatory when profile class is null
O5 –> CHARGE_ON_FINANCE_CHARGE_FLAG must be null if INTEREST_CHARGES is No
O6 –> INTEREST_PERIOD_DAYS must be null if INTEREST_CHARGES is “No”
O7 –> INTEREST_PERIOD_DAYS must be greater than zero
P1 –> Postal Code is not in the defined range of system options
Q1 –> A new location was created for a value in an address segment field
Q2 –> Validation failed for the key location flexfield structure
R1 –> CUST_SHIP_VIA_CODE is not defined in ORG_FREIGHT
R3 –> CUSTOMER_CATEGORY_CODE is not enabled in AR_LOOKUPS
R4 –> CUST_TAX_CODE is not defined in AR_VAT_TAX
R5 –> CUST_TAX_REFERENCE cannot be null when CUST_TAX_CODE is ‘EXEMPT’
R6 –> SITE_USE_TAX_CODE is not defined in AR_VAT_TAX
R7 –> SITE_USE_TAX_REFERENCE is required when SITE_USE_TAX_CODE is ‘EXEMPT’
R8 –> Invalid demand class code.
R9 –> SITE_SHIP_VIA_CODE not defined in ORG_FREIGHT
S1 –> The customer reference specified is invalid
S2 –> The address reference specified is invalid
S3 –> The address reference specified is not valid for this customer
S4 –> Payment Method is not defined in AR_RECEIPT_METHODS
S5 –> A bank account does not exist for the specified customer
S6 –> The end date specified cannot be before the start date
S7 –> The address specified must have an active BILL_TO site defined
T1 –> Customer payment method already active between the dates specified
T2 –> Customer site payment method already active between the dates specified
T3 –> Customer already has a primary payment method for specified dates
T4 –> Customer site has a primary payment method on the dates specified
T5 –> This customer payment method is already active in this date range
T6 –> Multiple primary payment methods defined
V2 –> The bank account specified must be of type ‘EXTERNAL’
V3 –> Customer bank account is already active between the dates specified
V4 –> Customer site bank account already active between these dates
V5 –> This customer already has primary bank account for specified dates
V6 –> Customer site can have only 1 primary bank account for the dates specified
V7 –> Duplicate rows exist in Interface table for this Customer Bank and date run
V8 –> Duplicate primary customer banks defined within the interface table
W1 –> BANK_NAME is mandatory when creating a new bank account
W2 –> BANK_BRANCH_NAME is mandatory when creating a new bank account
W3 –> BANK_ACCOUNT_CURRENCY_CODE is mandatory creating a new bank account
W4 –> BANK_ACCOUNT_CURRENCY_CODE is not defined in FND_CURRENCIES
W5 –> Bank number already exists.
W6 –> Duplicate bank number in interface table.
W7 –> Primary flag should be ‘Y’ or ‘N’.
W8 –> Duplicate bank and branch name in interface table.
W9 –> Duplicate Location
W0 –> Bank and branch name already exists.
X1 –> AUTO_REC_INCL_DISPUTED_FLAG mandatory when profile class is null
X2 –> TAX_PRINTING_OPTION is mandatory when no profile class specified
X3 –> GROUPING_RULE_NAME is mandatory when no profile class is specified
X4 –> CHARGE_ON_FINANCE_CHARGES_FLAG has an invalid value
X6 –> CURRENCY_CODE has an invalid value
X7 –> CREDIT_BALANCE_STATEMENTS is mandatory when STATEMENTS is “Yes”
X8 –> CREDIT_BALANCE_STATEMENTS must be “No” when STATEMENTS is “No”
X9 –> STATEMENT_CYCLE_NAME must be null when STATEMENTS is “No”
X0 –> OVERRIDE_TERMS is mandatory when no profile class is specified
Y1 –> PARTY_NUMBER must be null when auto-numbering is set
Y2 –> PARTY_NUMBER is mandatory when auto-numbering is set to “No”
Y3 –> Party Number already assigned to a different party.
Y4 –> This party reference has two different party numbers defined in RA_CUSTOMERS_INTERFACE.
Y5 –> PERSON_FLAG has an invalid value
Y6 –> Party Site Number already assigned to a different address
Y7 –> Address reference has two different party site numbers defined in RA_CUSTOMERS_INTERFACE.
Y8 –> PARTY_SITE_NUMBER must be null when auto-numbering is set
Y9 –> PARTY_SITE_NUMBER is mandatory when auto-numbering is set to “No”
Z1 –> CREDIT_BALANCE_STATEMENTS must be null when STATEMENTS is null
Z2 –> STATEMENT_CYCLE_NAME must be null when STATEMENTS is null
Z3 –> CHARGE_ON_FINANCE_CHARGE_FLAG must be null when INTEREST_CHARGES is null
Z4 –> INTEREST_PERIOD_DAYS must be null when INTEREST_CHARGES is null
Z5 –> DISCOUNT_GRACE_DAYS must be null when DISCOUNT_TERMS is null
Z6 –> DISCOUNT_GRACE_DAYS must positive
Z7 –> DISCOUNT_GRACE_DAYS must be null when DISCOUNT_TERMS is “No”
Z8 –> DUNNING_LETTER_SET_NAME must be null when DUNNING_LETTERS is “No”
Z9 –> DUNNING_LETTER_SET_NAME must be null when DUNNING_LETTERS is null
Z0 –> CURRENCY_CODE is mandatory when a profile amount value is populated
a1 –> Customer record for insert must have validated profile record defined
a2 –> TAX_PRINTING_OPTION has an invalid value
a3 –> The customer profile for this customer reference already exists
a4 –> The customer profile class for update does not exist
a7 –> Duplicate record within the interface table
a8 –> Conflicting profile classes specified for this customer/site
b1 –> Both TRX_CREDIT_LIMIT and OVERALL_CREDIT_LIMIT must be populated
b2 –> TRX_CREDIT_LIMIT may not be greater than the OVERALL_CREDIT_LIMIT
b3 –> DUNNING_LETTER_SET_NAME must have a unique value
b4 –> COLLECTOR_NAME must have a unique value
b5 –> STANDARD_TERM_NAME must have a unique value
b6 –> STATEMENT_CYCLE_NAME must have a unique value
b7 –> BANK_ACCOUNT_NUM is mandatory when creating a new bank account
b8 –> AUTO_REC_INCL_DISPUTE_FLAG has an invalid value
b9 –> PAYMENT_GRACE_DAYS must be a positive value
e2 –> Bill_to_orig_address_ref should only be defined for Ship-to Addresses
f1 –> You may have only one active Dunning site use for each customer
f2 –> For each customer, you may only have one active “Statements” type
f3 –> For each customer, you may only have one active Legal site
f4 –> Clearing Days must be greater than or equal to zero
f5 –> Address language is not installed
f6 –> Address reference has different languages
f7 –> Duplicate telephone reference in table RA_CONTACT_PHONES_INTERFACE
f8 –> A bank and branch with this bank number and branch number already exists
f9 –> Customer Prospect Code must be either CUSTOMER or PROSPECT
g1 –> This customer reference has two different customer prospect codes
u5 –> Contact reference has two different e-mail addresses
w2 –> CREDIT_CLASSIFICATION must have a valid value
y0 –> CONTACT_JOB_TITLE is not defined
y1 –> PHONE_COUNTRY_CODE is not defined in HZ_PHONE_COUNTRY_CODES
y2 –> This customer is already assigned to a different party
y3 –> This customer is already assigned to a different party
y4 –> LOCKBOX_MATCHING_OPTION must have a valid value
y6 –> TELEPHONE_TYPE cannot be updated from telex to any other type or any other type to telex.
y7 –> You cannot update this address. A printed, posted, or applied transaction with an associated tax line exists for this address
Advertisements
Posted in customer interface error codes, customer interface in r12, r12 customer interface, R12 training | Leave a comment

How to find the correct Jdeveloper version & Installation for OAF

Get OAF online training from the experts in AppsPhor Software Solutions

We need to download correct version JDeveloper to develop OAF forms. This article explains how to find correct version of the JDeveloper for installation.

Follow the steps:
1. Open your Oracle Applications homepage
2. At the bottom left you can see “About this Page”. Click on it.
3. Click on “Technology Components” tab
4. Check OA Framework version.


Based on the following information pickup the right Patch from oracle support and download. (Installation steps fallows after below table)
Release 11i
OA Framework 5.10 patch
JDeveloper 9i Patch
ATG.PF.H (patch 3438354 or Oracle Applications 11.5.10)
Patch 4045639 9IJDEVELOPER WITH OA EXTENSION ARU FOR FWK.H
ATG PF CU1 (patch 4017300)
Patch 4141787 9IJDEVELOPER WITH OA EXTENSION ARU FOR CU1
ATG PF CU2 (patch 4125550)
Patch 4573517 Oracle9i JDeveloper with OA Extension for 11.5.10 CU2
11i.ATG_PF.H RUP3 (patch 4334965)
Patch 4725670 9IJDEVELOPER WITH OA EXTENSION ARU FOR 11i10 RUP3
11i.ATG_PF.H RUP4 (patch 4676589)
Patch 5455514 9IJDEVELOPER WITH OA EXTENSION ARU FOR 11i10 RUP4
11i.ATG_PF.H RUP5 (patch 5473858)
Patch 6012619 9IJDeveloper With OA Extension ARU FOR 11i10 RUP5
11i.ATG_PF.H.RUP6 (patch 5903765)
Patch 6739235 9IJDeveloper With OA Extension ARU FOR 11i10 RUP6
11i.ATG_PF.H.delta.7 (patch 6241631)
Patch 8751878 9I JDEVELOPER WITH OA EXTENSION ARU FOR 11I RUP7


Release 12.0
ATG Release 12 Version
JDeveloper 10g Patch
12.0.0
Patch 5856648 10g Jdev with OA Extension
12.0.1  (patch 5907545)
Patch 5856648 10g Jdev with OA Extension
12.0.2  (patch 5484000 or 5917344)
Patch 6491398 10g Jdev with OA Extension ARU for R12 RUP2 (replaces 6197418)
12.0.3  (patch 6141000 or 6077669)
Patch 6509325 10g Jdev with OA Extension ARU for R12 RUP3
12.0.4 (patch 6435000 or 6272680)
Patch 6908968 10G JDEVELOPER WITH OA EXTENSION ARU FOR R12 RUP4
12.0.5 (No new ATG code released)
No new JDev patch required
12.0.6  (patch 6728000 or patch 7237006)
Patch 7523554 10G Jdeveloper With OA Extension ARU for R12 RUP6
Release 12.1
 ATG Release 12.1 Version
JDeveloper 10g Patch
12.1 (Controlled Release – only included for completeness)
Patch 7315332 10G Jdev with OA Extension ARU for R12.1 (Controlled Release)
12.1.1 (rapidInstall or patch 7303030)
Patch 8431482 10G Jdeveloper with OA Extension ARU for R12.1.1
12.1.2 (patch 7303033 or patch 7651091)
Patch 9172975 10G JDEVELOPER WITH OA EXTENSION ARU FOR R12.1.2
12.1.3 (patch 9239090 or patch 8919491)
Patch 9879989 10G JDEVELOPER WITH OA EXTENSION ARU FOR R12.1.3
12.1.3.1 (patch 11894708)
Patch 9879989 10G JDEVELOPER WITH OA EXTENSION ARU FOR R12.1.3

Installation/Deploying Steps:
1. Unzip the downloaded Patch (Say in 
D:\).
2. Rename the folder (Say 
OAF)
3. You can see 3 folders under it(
D:\OAF). They are jdevbin, jdevdoc, jdevhome
4. Place the dbc file in 
D:\OAF\jdevhome\jdev\dbc_files\secure
    Location of dbc file in 11i
         
$FND_TOP/secure OR $FND_SECURE
    Location of dbc file in R12
         
$INST_TOP/appl/fnd/12.0.0/secure
5. Set the Environment Variables
    Right click on My Computer > Click on Properties > Click on Advanced System Settings > Click on Environment Variables > Click on New > Give the following 
    Variable Name: JDEV_USER_HOME
    Variable Value:  D:\OAF\jdevhome\jdev
    Finally click on OK
6. Create a shortcut on your Desktop. Goto 
D:\OAF\jdevbin\jdev\bin
    Right click on 
jdevW > Send to > Desktop (Shortcut) [For Windows]
7. Double click on the Desktop Shortcut to open JDeveloper
Posted in Correct JDeveloper, Installation of OAF, OAF training | Leave a comment

Oracle Cash Management – Payment Reconciliation Statements

Creating Bank Reconciliation Statements
Cash Management lets you create new bank statement lines when reconciling available transactions. This is useful if you want to reconcile without entering statement line information first.
a. Payment Reconciliation
N: – Bank Statements-> Bank Statements and Reconciliation


To create a new bank statement line from reconciled transactions:
1. Navigate to the Find Bank Statements window.
2. Enter the query criteria for the statement you want to reconcile, or leave the criteria blank to query all existing statements.
3. Choose Find to see the Reconcile Bank Statements window containing the statements that meet your query criteria.
4. Select the statement you want to reconcile, and choose Review. Optionally, choose New to enter a new bank statement.
5. If you are entering a new bank statement, enter the bank statement header information. If you select an existing bank statement, Cash Management displays the corresponding bank information.
6. Choose Available to search for detail or batch transactions that are available for reconciliation.
7. Enter your search criteria in the Find Transactions window, or leave the criteria blank to search for all available transactions.
8. Choose Find.
9. Select the detail or batch transactions that apply to the bank statement line you want to create.
10. Choose reconcile. Cash Management creates a new bank statement line with an Amount and Type that match the reconciled transaction(s) for that line.


Click on Find button

Click on Lines button

Click on Available button

Enable AP Payment and Click on Find button

Select the Payment Transaction Document Number ‘1001’
Check the Status as Negotiable
Click on Reconcile button

Click on Reconciled Button

Check the Status as Reconciled Unaccounted
Switch Responsibility: – Ivas_Payables

N:- Payments-> Entry-> Payments


Query the Document Number ’1001’ and Press Ctrl+F11

Check the Status as Reconciled Unaccounted
Click on Actions…1 and enable Create Accounting and Final Post

Click on OK button
Menu-> Tools-> View Accounting Events


Posted in bank statement reconciliation, how to process cash payments, journal entries for bank reconciliation statement, payment cash management, what is a bank reconciliation statement | Leave a comment

How to Create a user in Oracle Apps

Open the Windows Internet Explorer
And select the URL of the application server say: http://nivasr12.apps.com:8005/

 Enter the User Name as Operations and Password as welcome

 Click on Login

Click on System Administrator
Click on Security -> User -> Define

Create a new User Name as ‘IVAS_USER’ and Password as ‘123456’

Add General Ledger Super User and System Administrator Responsibilities to this User

And Save your work
Close the form
Login With new user IVAS_USER
Posted in assign responsibility, create user, Oracle apps, Oracle apps R12 Tutorial, system administrator, system administrator in oracle apps | Leave a comment

Oracle Cash Management Setups – Defining Bank Transaction Codes

If you want to load electronic bank statements or use Cash Management’s Auto Reconciliation feature, you must define, for each bank account, the transaction codes that your bank uses to identify different types of transactions on its statements. You should define a bank transaction code for each code that you expect to receive from your bank. Payment and Receipt codes may be defined more than once if they apply to transactions from multiple sources.
You can enter effective date range fields, Start Date and End Date, so that you can make a bank transaction code inactive. You can also delete codes that have not been used, in case you make a mistake in creating one.

N: – Setup-> Banks-> Bank Transaction Codes
To define a bank transaction code:
1. Navigate to the Bank Transaction Codes window.
2. In the Find Bank window, select the bank, whose codes you are defining. Alternatively, you can query the bank account number. The system displays the Bank Transaction Codes window, which includes bank account, bank information, and a region for entering transaction codes.
3. For each transaction code you are defining, select a transaction type from the list of values. The transaction type determines how Cash Management will match and account for transactions with that code.
Bank statement lines are coded to identify the transaction type the line represents. Since each bank might use a different set of transaction codes, you need to map each code a particular bank uses, to one of the following Cash Management transaction types.
You can select from the following list of values:
o Payment: Payments such as generated or recorded checks, payment batches, wire transfers, electronic funds transfers, or payroll checks.
o Receipt: Receipts such as received checks, remittance batches, direct debits, and bills of exchange.
o Miscellaneous payment: Payments not associated with supplier invoices, such as petty cash transactions directly posted to cost accounts or bank charges.
o Miscellaneous receipt: Receipts not associated with customer invoices, such as petty cash transactions directly posted to revenue accounts, such as interest received.
o Stopped: Stopped payments previously entered, generated, or cleared, such as callback of check. A stopped transaction type matches only to Voided or Stopped payments in Payables or Oracle Payroll.
o Rejected: Receipts rejected for reasons other than non-sufficient funds, such as an invalid bank account. A rejected transaction type matches only to reversed receipts in Receivables.
o NSF (Non-Sufficient Funds): Receipts rejected by the bank because the accounts on which they were drawn had non-sufficient funds. You can reverse these receipts by creating a standard reversal. Cash Management reopens the invoices you closed with the original receipt. When you match bank statement lines with transactions, an NSF transaction type only matches to reversed receipts in Receivables.
o Sweep In. Incoming funds transfer from an internal bank account. This bank transaction type identifies the originating bank account.
o Sweep Out. Outgoing funds transfer from an internal bank account. This bank transaction type identifies the receiving bank account.
4. Enter the code used by your bank.
5. Optionally enter a description of the transaction.
6. Enter start and end dates to determine when the bank transaction code is considered active.
7. Enter the number of float days that you want Cash Management to add to or subtract from the statement date to create an anticipated value date for automatic lockbox receipts.
8. Enter a Transaction Source for payment and receipt transactions. Choose Journal from the list of values to reconcile statement lines, with the assigned transaction code, to General Ledger journals. Choose Open Interface to reconcile statement lines to settlements in Oracle Treasury or external transactions in the Reconciliation Open Interface. Choose Payables Payments or Receivables Receipts to reconcile statement lines to transactions in Oracle Payables or Oracle Receivables. Choose Payroll Payments to reconcile statement lines to transactions in Oracle Payroll. Choose Cash Management to reconcile statement lines to cash flows in Oracle Cash Management.
9. Enter the Reconciliation Sequence number. If the same code with bank transaction type Payment or Receipt is entered more than once with different transaction sources this number is used by the AutoReconciliation program to determine the order in which to search the transaction sources for a matching transaction.
10. Optionally select a value for the Payroll Payment Format field to reconcile statement lines, with the assigned transaction code, to Payroll EFT payments. The Payroll Matching Order field is automatically populated based on the value selected in the Payroll Payment Format field. It is populated after a Payroll Payment Format has been selected. This field indicates the order in which you need to set up the format for the BANK_TRX_NUMBER in the bank statement mapping template.
11. If the transaction type is Miscellaneous Receipt or Miscellaneous Payment, use the Matching against field to determine the order of matching and the type of transactions to match.
Since the same transaction code may be used for matching against both miscellaneous transactions and/or correcting statement errors, you need to indicate, for miscellaneous payments and miscellaneous receipts, the transaction type to match. If you use a transaction code for both miscellaneous transactions and correcting statement errors, you can also specify the matching sequence. You can choose from the following values to indicate how to use this bank transaction code:
o Misc: Only match against miscellaneous transactions.
o Stmt: Identify the statement line as a correcting entry. The statement line will match against existing statement lines. The netted amount of these lines is used to match to sub ledger transactions.
o Misc, Stmt: First try to match against miscellaneous transactions, if there is no match, and then try to match against statement lines (corrections).
o Stmt, Misc: First try to match against statement lines (corrections), if there is no match, and then try to match against miscellaneous transactions.

12. Choose the correction method your bank uses when correcting bank errors: Reversal, Adjustment, or Both.
This field is only applicable for those Miscellaneous Receipt or Miscellaneous Payment transaction codes that may be used to match to correction statement lines.

13. Choose whether to create transactions for any miscellaneous payments and miscellaneous receipts reported on the bank statement when no transaction number is provided.

14. If you selected the Create option in the previous field, specify the Receivables Activity type and payment method for any miscellaneous transactions (receipts or payments) you create from within Cash Management.

15. Define each additional bank transaction code, following the previous steps.

16. Save your work.

Enter the mandatory fields for Bank Transaction Code Types
Save your work and Close
Posted in cash management in oracle apps r12, Define Bank transaction codes, oracle cash management, oracle cash management interview questions, oracle cash management setup steps | Leave a comment

Oracle Cash Management Setups – Bank Account Creation

Bank Account Creation

 1. Click on Create Account icon

2. Enter the Required data and Click on Continue button

 3. Select the Bank Account Owner i.e. Legal entity name as ‘ivas legal entity’

Enable Account use
> Payables and
> Receivables
Click on Next button 
4. Enter the Account name, Account Number and Currency then
Click on Save and Next button

 5. Enter the required data and Click on Save and Next

 6. Click on Add Organization Access button

7. Enable Account Use as
> Payables and
> Receivables
And Select the organization as ivas operating unit
Click on Continue button

 8. Enter the required data and click on Apply button

 9. Click on save and next button


10. Click on Finish button

11. Select ivas current account and Click on Manage Payment Documents


12. Then click on Create button
13. Enter the required data and Apply

Posted in cash management in oracle apps r12, oracle cash management, oracle cash management interview questions, oracle cash management setup steps | Leave a comment

Oracle Cash Management Setups – Bank Branch Creation

Bank Branch Creation

 1. Click on Create Branch icon

2. Enter Country name as United States and Bank Name then Click on Continue button

 3. Enter the Bank Branch Name and required data then Click on Save and Next button

 4. Click on Create button for bank branch address information or click on Save and Next button

5. Click on Create Contact button for bank branch Contact information if required or click on Finish button 
Posted in Labels: cash management in oracle apps r12, oracle cash management, oracle cash management interview questions, oracle cash management setup steps | Leave a comment