`

Shell scripting
Objectives:

Steps to Register Shell Script as a concurrent program Sample Shell Script to copy the file from source to destination Basic Shell Script Commands Steps to Register Shell Script as a concurrent program step 1: ======= Place the <name>.prog script under the bin directory for your applications top directory. For example, call the script ERPS_DEMO.prog and place it under $CUSTOM_TOP/bin step 2: ======= Make a symbolic link from your script to $FND_TOP/bin/fndcpesr

For example, if the script is called ERPS_DEMO.prog use this: ln -s $FND_TOP/bin/fndcpesr ERPS_DEMO This link should be named the same as your script without the .prog extension. Put the link for your script in the same directory where the script is located. step 3: ======= Register the concurrent program, using an execution method of Host. Use the name of your script without the .prog extension as the name of the executable. For the example above: Use ERPS_DEMO step 4: ======= Your script will be passed at least 4 parameters, from $1 to $4. $1 = orauser/pwd $2 = userid(apps) $3 = username, $4 = request_id Any other parameters you define will be passed in as $5 and higher. Make sure your script returns an exit status also. Sample Shell Script to copy the file from source to destination #Note: If you see # in front of any line it means that its a comment line not the actual code #** ******************************************************************** # Created By : Prudhvi A # Creation Date : 19-FEB-2008 # Script Name : ERPSCHOOLS.prog # Description : This Script accepts three parameters # 1)Data File Name 2)Source Directory Path 3)Target Directory Path # Then copy the file from source location to target location. # If copy fails send the error status/message to concurrent program so that user can see status. # # # ======== # History # ======== # Version 1 Prudhvi A 19-FEB-2008 Created for erpschools.com users # #** ******************************************************************** #Parameters from 1 to 4 i.e $1 $2 $3 $4 are standard parameters # $1 : username/password of the database # $2 : userid # $3 : USERNAME # $4 : Concurrent Request ID

DataFileName=$5 SourceDirectory=$6 TargetDirectory=$7 echo echo Parameters received from concurrent program .. echo Time : `date` echo echo Arguments : echo Data File Name : ${DataFileName} echo SourceDirectory : ${SourceDirectory} echo TargetDirectory : ${TargetDirectory} echo echo Copying the file from source directory to target directory cp ${SourceDirectory}/${DataFileName} ${TargetDirectory} if [ $? -ne 0 ] # the $? will contain the result of previously executed statement. #It will be 0 if success and 1 if fail in many cases # -ne represents not equal to then echo Entered Exception exit 1 # exit 1 represents concurrent program status. 1 for error, 2 for warning 0 for success else echo File Successfully copied from source to destination exit 0 fi echo **************************************************************** Basic Shell Script Commands # Create Directory mkdir <dirname> # Remove Directory rmdir <dirname> #remove folder with files rm -r -f <dirname> # Change Directory cd <newpath> # Create new file vi <newfile.ext> #insert data into file vi <openfilename.ext> esc i <make changes> #Save file esc :wq enter # exit without saving changes esc :q! enter # open existing file vi <existingfilename.ext> #remove file rm <filename.ext> # copy file with same name cp <sourcedir>/<sourcefilename.ext> <destinationdir> # copy file with new name cp <sourcedir>/<sourcefilename.ext> <destinationdir>/<newfilename.ext> # Move file with same name

mv <sourcedir>/<sourcefilename.ext> <destinationdir> # move file with data appended to filename in the front mv <sourcedir>/<sourcefilename.ext> <destinationdir>/`date+%H%M%d%m%y`<filename.ext> #print line echo your text here to print #print date echo `date`

Oracle Receivables Module Technical Details

Oracle Accounts Receivable uses the following tables for recording customer account information: The major tables containing parties and customer accounts information in Oracle Receivables are grouped by business function. HZ_PARTIES HZ_CUST_ACCOUNTS HZ_PARTY_SITES HZ_CUST_ACCT_SITES_ALL HZ_CUST_SITE_USES_ALL HZ_LOCATIONS HZ_PARTY_RELATIONSHIPS HZ_ORGANIZATION_PROFILES HZ_CONTACT_POINTS HZ_CUST_ACCOUNT_ROLES HZ_PERSON_PROFILES HZ_ORG_CONTACTS Transaction Tables RA_CUSTOMER_TRX_ALL RA_CUSTOMER_TRX_LINES_ALL RA_CUST_TRX_LINE_GL_DIST_ALL AR_PAYMENT_SCHEDULES_ALL AR_CASH_RECEIPTS_ALL AR_CASH_RECEIPT_HISTORY_ALL AR_RECEIVABLE_APPLICATIONS_ALL AR_ADJUSTMENTS_ALL HZ_PARTIES A party is an entity that can enter into a business relationship. This table stores basic information about parties, which is true regardless of this relationship to the deploying company. Entities are modeled only once in HZ_PARTIES, regardless of how many roles they play. For example, if an organization is a customer, a distributor, and a partner, there is still only one record for them in HZ_PARTIES. Parties can be one of four types: Organization - Oracle Corporation Person - Jane Doe Group Doc Household Relationship - Jane Doe at Oracle Corporation HZ_LOCATIONS A location is a point in geographical space described by an address and/or geographical Indicators such as latitude or longitude. This table stores information about an address such as: street address and postal code. This table provides physical location information about parties (organizations and people) and customer accounts. Records in HZ_LOCATIONS can store delivery and postal code information about a location, store latitude and longitude, and can be used to determine the appropriate calculations and tax rates for sales tax and VAT calculations. HZ_PARTY_SITES

This table links a party (HZ_PARTIES) and a location (HZ_LOCATIONS) and stores location-Specific party information such as a persons mail stops at their work address. One party can point to one or more party sites. One location can point to one or more party site. Party sites serve as the intersection between parties and locations, allowing for a many-to-many relationship between the two. HZ_RELATIONSHIPS This table stores information about relationships between two entities, for example, one party and another party. The SUBJECT_ID and OBJECT_ID columns specify the relationship that exists between two parties. For example, if the party relationship type is Parent Of, then a holding company could be the SUBJECT_ID in the relationship while one of its subsidiaries could be the OBJECT_ID. Creating a party contact causes a party relationship to be created. A party can have different relationships with one or more other parties that can change over time. HZ_ORGANIZATION_PROFILES This table stores a variety of information about a party of type Organization. This table gets populated when a party of type ORGANIZATION is created. Historical data is also stored in this table. HZ_PERSON_PROFILES This table stores a variety of information about a party of type Person. For example, this table could contain the correct spelling and phonetic pronunciation of the persons name. Some information in this table may also be entered into the HZ_PARTIES table. HZ_ORG_CONTACTS This table stores a variety of information about an organization contact. The records in this table provide information about a contact position such as job title, rank, and department. This table is not used to store information about a specific person or organization. For example, this table may include a record for the position of Vice President of Manufacturing that indicates that the contact is a senior executive, but it would not include the name of the person in that position. HZ_CUST_ACCOUNTS This table stores information about customer/financial relationships established between a Party and the deploying company. Because a party can have multiple customer accounts, this table may contain several records for a single party. For example, an individual person may establish a personal account, a family account, and a professional account for a consulting practice. HZ_CUST_ACCT_SITES_ALL This table stores information about customer/financial account sites information. Stores information about customer sites. One customer account can have multiple sites. HZ_CUST_SITE_USES_ALL This table stores information about the business purposes assigned to a customer account site. A customer account site can have multiple purposes, but each record in this table only specifies one purpose for a customer account site. For example, a customer account site may be assigned as a ship-to site in one record and as a bill-to site in another record. HZ_CUST_ACCOUNT_ROLES This table stores information about a role or function that a party performs as related to a customer account. For example, Jane Doe might be the Legal Contact for a specific customer account of Corporation ABC. Note that account ownership such as financial responsibility for an account is determined by the single party ID that is stored directly on the HZ_CUST_ACCOUNTS table. HZ_CONTACT_POINTS This table stores information about how to communicate with parties or party sites using electronic media or methods such as Electronic Data Interchange (EDI), e-mail, telephone, telex, and the Internet. Each medium or method should be stored as a separate method in this table. For example, the attributes of a complete telephone number connection should be stored in a record, while EDI information should be stored in a different record. RA_CUSTOMER_TRX_ALL This table stores invoice, debit memo, commit-ment, chargeback, bills receivable, and credit memo header information. Each row includes general invoice information such as customer, transaction type, and printing instructions. You need one row for each invoice, debit memo, commitment, and credit memo you create in Oracle Receivables and these are all distinguished by their transaction types stored in RA_CUST_ TRX_ TYPES_ALL.

RA_CUSTOMER_TRX_LINES_ALL This table stores information about invoice, debit memo, credit memo, bills receivable, and commitment lines. It describes to the customer the charges that appear on these documents. AR_PAYMENT_SCHEDULES_ALL This table stores all transactions except adjust-ments and miscellaneous cash receipts. A miscellaneous cash receipt is one that is not connected to a customer. All customer-related activity is logged in this table. This table is updated when an activity occurs against an invoice, debit memo, chargeback, credit memo, on-account credit, bills receivable, receipt, or commitments. RA_CUST_TRX_TYPES_ALL This table stores information about each transaction type for all classes of transactions, for example, invoices, commitments, and credit memos. Each row includes Auto Accounting information as well as standard defaults for the resulting invoices. The primary key for this table is CUST_TRX_TYPE_ID. AR_TRANSACTION_HISTORY_ALL This table is a Bills Receivable-specific table containing the history of a transactions lifecycle. A new row is created each time there is activity on the transaction or the status of the transaction has changed. This table stores the header for the Receivables posting information. AR_DISTRIBUTIONS_ALL This table stores the accounting distributions for cash receipts, miscellaneous receipts, adjustments, credit memo applications, cash receipt applications, and bills receivable transactions. AR_CASH_RECEIPTS_ALL This table stores one record for each receipt entry. All cash receipts are logged in this table. Oracle Receivables creates records concurrently in the AR_CASH _RECEIPT_ HISTORY_ ALL, AR_PAYMENT_ SCHEDULES_ ALL, AR_DISTRI-BUTIONS_ALL, and AR_ RECEIVABLE_ APPLICA-TIONS_ALL tables for invoice-related receipts. For receipts that are not related to invoices, records are created in the AR_MISC_CASH_ DISTRIBUTIONS_ALL table instead of the AR_RECEIVABLE_APPLICATIONS_ ALL table. AR_CASH_RECEIPT_HISTORY_ALL This table stores all of the activity that is contained for the life cycle of a receipt. Each row represents one step. The status field for that row tells you which step the receipt has reached. Possible statuses are Approved, Confirmed, Remitted, Cleared, and Reversed. AR_RECEIVABLE_APPLICATIONS_ALL This table stores all accounting entries for cash and credit memo applications. Each row includes the amount applied, status, and accounting flex field information. AR_MISC_CASH_DISTRIBUTIONS_ALL This table stores all accounting entries for miscellaneous cash applications. Miscellaneous cash cannot be invoiced, such as stock revenue, interest income, and investment income. AR_CASH_RECEIPTS_ALL stores one record for each payment, and this table stores one record for each distribution of the receipt. AR_RECEIPT_CLASSES This table stores the different receipt classes that you define. Receipt classes determine whether the receipt[s] belonging to this class are created manually or automatically, and whether the receipts go through the different steps in a receipts life-cycle. AR_RECEIPT_METHODS This table stores information about Payment Methods, receipt attributes that you define and assign to Receipt Classes to account for receipts and their applications. For automatically created receipts, a Payment Method defines the rules for creating these receipts. For manually created receipts, a Payment Method defines a user-definable type for the receipt.

 Each Payment Method is associated with a set of bank accounts, which forms the set of bank accounts you can assign to your receipt.

SELECT l.session_id||','||v.serial# sid_serial, l.ORACLE_USERNAME ora_user, o.object_name, o.object_type, DECODE(l.locked_mode, 0, 'None', 1, 'Null', 2, 'Row-S (SS)', 3, 'Row-X (SX)', 4, 'Share', 5, 'S/Row-X (SSX)', 6, 'Exclusive', TO_CHAR(l.locked_mode) ) lock_mode, o.status, to_char(o.last_ddl_time,'dd.mm.yy') last_ddl FROM dba_objects o, gv$locked_object l, v$session v WHERE o.object_id = l.object_id and l.SESSION_ID=v.sid order by 2,3; SELECT * FROM DBA_DDL_LOCKS WHERE NAME IN ('XXX_OBJECT_NAME' ,'XXX_OBJECT_NAME') SELECT * FROM DBA_OBJECTS WHERE OBJECT_NAME IN ('XXX_OBJECT_NAME' ,'XXX_OBJECT_NAME') SELECT * FROM SYSTEM.V$SESSION WHERE SID = 2883 OR ROW_WAIT_OBJ# IN (374295,373803,382481,382490) ALTER SESSION SET CURRENT_SCHEMA=SYS ALTER SYSTEM KILL SESSION '1586,395' ALTER SYSTEM FLUSH BUFFER_CACHE ALTER SYSTEM FLUSH SHARED_POOL ALTER SESSION SET CURRENT_SCHEMA=APPS Types of Invoices:

1.

Standard Invoice : Normal trade invoice

2. 3. 4.

Credit Memo : We receive from supplier & record it (negative amount) Debit Memo : We create & send to supplier (negative amount) Expense Report: Record reimbursable business expenditure incurred by employees.

(prerequisites 1> Create employee 2> Assigning employee to supplier 3> Create expense invoice template 5. Mixed Invoice : (+ or both) 6. 7. 8. 9. Prepayment : (like advance) Withhold tax Invoice : Withhold to tax authority Quick Match : Automatic ship lines match to PO PO Default : Matched to PO (Manual)

1. What is MRC and what is its use? The Multi Reporting Currency Feature allows you to report and maintain records at the transaction level in more than one functional currency. You can do by defining one or more set of books in addition to primary set of books. 2. How is the balance of an invoice derived ? It is the total invoice amount minus the amount received from the customer. Use application rule set to control how Receivable will reduce the balance due of open debit items when you apply payments. 3. Explain Accounting for invoice in Advance and Arrears. Accointing for invoice in advance a) Receivable A/c .....................Dr. To Unearned revenue a/c (when we raise the invoice with invoicing rule as advance) b) Unearned Revenue A/c .............. Dr. To Revenue A/c (when we receive the payment, the number of journal entry (b) is depend upon the accounting rules which can be fixed or variable) Accounting for invoice in arrear a) Unbilled receivable a/c ....................Dr. To Revenue a/c (when we receive the payment of unbilled invoice, the number of journal entry (a) is depend upon the accounting rules which can be fixed or variable)) b) Receivable a/c .........................Dr. To Unbilled receivable a/c (when we raise the invoice, with invoicing rule arrear) 4. What is the use of Transaction Flexfield in Autoinvoice ? Transaction Flexfield actually identifies the the uniqueness among the Multiple lines of a single Invoice 5. What are value sets? Value sets are the defined as list of possible values for a specific purpose. These are assigned to flexfields. These are the only possible values to be choosen from. This eliminates the data entry errors. Value set is a set of possible values. There are 8 value set types: 1.Dependent

2.Independent 3.Table 4. None 5.Pair 6.Translatable Dependent 7.Translatable Independent 8. Special 6. Describe the main tables involved in AR, and what is the data stored in them? RA_BATCHES_ALL -- Information about Transaction BATCHES RA_CUSTOMER_TRX_ALL -- Header information about Transaction RA_CUSTOMER_TRX_LINES_ALL -- Lines information about Transaction RA_CUST_TRX_LINE_GL_DIST_ALL - Distribution information about Transaction RA_CUST_TRX_LINE_SALESREPS_ALL -- Sales representative of Transaction Information AR_PAYMENT_SCHDULES_ALL - Information about Payment Schedules AR_APPLICATION_PAYABLES_ALL RA_INTERFACE_ERRORS - Errors in AutoInvoice Interface Data RA_INTERFACE_LINES_ALL - Use this table to enter Header and Lines information in AutoInvoice Interface program RA_INTERFACE_DISTRIBUTIONS_ALL - Distribution Table in AutoInvoice Interface program RA_INTERFACE_SALESCREDITS_ALL - Sales Credits information in AutoInvoice Interface 7. What is the importance of Batch Source set up in AR ? Batch sources control the standard transaction type assigned to a transaction and determine whether Receivables automatically numbers your transactions and transaction batches. You can define two types of transaction batch sources-Manual and Imported 8. What do you mean by HZ_ in customer tables? These are the tables which come into picture after 11.5.9 because of the TCA. HZ stands for Human Zone(HZ_). Anytihing which is related to the human like Customer profiles, their accounts, locations, relationships are stored in these tables only. From release 11i TCA came into picture in Accounts Recievable module, where oracle has grouped all the customer information at one place. Most important tables in TCA areHZ_PARTIES, HZ_CUST_ACCOUNTS_ALL, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, HZ_PARTY_SITES, HZ_PARTY_SITE_USES, HZ_CONTACT_POINTS. few to name. 9. What is the difference between _all, _tl, _vl, _v tables in Oracle Apps ? Also name various other table suffix. _ALL : Table holds all the information about different operating units. Multi-Org environment. You can also set the client_info to specific operating unit to see the data specific to that operating unit only. _TL are tables corresponding to another table with the same name minus the _TL. These tables provide multiple language support. For each item in the table without _TL there can be many rows in the _TL table, but all with different values in the LANGUAGE column. _B these are the BASE tables. They are very important and the data is stored in the table with all validations. It is supposed that these table will always contain the perfect format data. If anything happens to the BASE table data, then it is a data corruption issue.

_F these are date tracked tables, which occur in HR and Payroll. For these there are two date columns EFFECTIVE_START_DATE and EFFECTIVE_END_DATE which together with the PK identifies a row uniquely. The date intervals cannot overlap. Many think they are Secured data. Guess someone from Oracle confirms. _V tables are the views created on base tables _VL are views for multi language tables which combines the row of the base table with the corresponding row of the _TL table where the LANGUAGE = USERENV(LANG). _S are sequences, used for finding new values for the primary key of a table. _A are Audit Shadow Tables _AVN and _ACN are Audit Shadow Views (when data was changed, and with what values) 10. How many Flex fields are there in AR and what are they? Required Key Flex fields: 1. Territory Flex field 2. Sales Tax Location flex field Optional Key Flex fields: 1. Transaction flex field (requied only if Auto Invoicing is enabled) 2. System Items Flex field (If Inventory or OM is installed this should be defined there. other wise, it should be set up in AR). 11. What is FSG and what is its use? FSG is a powerful and flexible tool you can use to build your own custom reports without programming. FSG is only available with GL. Using Financial Statment Generation (FSG), we can create different financial statement and we will get finacial reports. Oracle Apps std reports does not support for reports such as Income Stmt and Final A/c.So we need to go for FSG to prepare Reports Such as P&loss stmt and balance sheet.FSG is Powerful tool for Reporting.Reporting with FSG is Mix and Modify Reuse and Recylce Activity. 12. What is the difference between conversions and interfaces ? Conversion is a process by which we transfer legacy data from temporary tables to base tables. Interfaces also does the same but is a daily process and most of the interfaces are automated by scheduling. Example:AutoInvoice. Conversition is on time process this is before instlation, and interface every time process we can run any time. 13. How many reporting currencies can be attached to Primary Set of Books? We can have a total of 8 SOB's (including the Primary SOB). Therefore, we can have 7 Reporting SOB. 14. What are Different types of transactions in AR? There are 7 type of transactions in ARInvoice, Debitmemo, Creditmemo, Chargeback, Deposits, Guarenty, and Bills Recivable. 15. What is the use of lockboxes?

AutoLockbox (or Lockbox) is a service that commercial banks offer corporate customers to enable them to outsource their accounts receivable payment processing. An AutoLockbox operation can process millions of transactions a month. AutoLockbox eliminates manual data entry by automatically processing receipts that are sent directly to your bank. You specify how you want this information transmitted and Receivables ensures that the data is valid before creating QuickCash receipt batches. Steps for lock box are : 1. The first step involves reading and formatting data from your bank file into AutoLockbox tables. 2. The second step involves submitting the validation program which checks data in the AutoLockbox tables for compatibility with Receivables. 3. Once data is validated, it is transferred into QuickCash tables. At this point, you can optionally query your receipts in the QuickCash window and change how they will be applied before submitting the final step, 4. Post QuickCash. Submitting Post QuickCash updates your customer's balances. 16. What are the interface tables used for ar invoices, customers, receipts for conversion process? Customer interface tables: ra_customer_interface ra_contant_phones_interface ra_customer_banks_interface ra_customer_profiles_interface ra_cust_pay_method_interface Invoice interface tables: ra_interface_lines_all ra_interface_sales_credits ra_interface_distributions Following are the Validation for Autoinvoice: 1- AR Transaction Type Validation : Check if the Transaction type provided in data file is defined in AR transaction types(RA_CUST_TRX_TYPES_ALL) 2- Transaction Batch Source Validation: Check if the source provided in data file is defined in AR transaction Batch source (RA_BATCH_SOURCES_ALL). 3- Invoice Currency Validation: Check if the currency provided in data file is defined in AR Currency (FND_CURRENCIES). 4- Customer Validation: Check if the Bill to Customer Number, Ship to Customer Number, Bill to Custom Location, Ship to Customer Location provided in the data file is defined in AR Customer(ra_customers). 5- Primary Sales Representative Validation: Sales representative number to be hardcode to -3 for No Sales Credit. 6- Term Name : Check if the Term name provided in the data file is defined in Payment terms (RA_TERMS) 7- Validate Sales Credit Type : Sales Credit to hardcode to Quota Sales Credit 8- Inventory Item Validation: Check if the Item provided in data file is defined in Inventory Items (MTL_SYSTEM_ITEMS). 9- Unit of Measurement validation: Check if the UOM provided is defined in MTL_UNITS_OF_MEASURE Table 10- Invoice Tax Code Validation : Check if the Tax Code provided in data file is defined in AR_VAT_TAX_ALL_B Table. 11- Invoice GL Date Validation : Check if the GL Data of provided invoices is in open period.Used ARP_UTIL.IS_GL_DATE_VALID API to validate. Following are the base tables hz_parties

hz_cust_accounts hz_cust_acct_sites_all hz_cust_sit_use_all hz_party_sites hz_locations hz_party_site_uses hz_customer_profiles hz_organization_profiles hz_person_profiles 17. What is Auto Invoicing? Explain? Auto Invoicing is a process of Importing Invoice related information from External / Internal Sources.External will be your business Legacy Systems like Main Frame / AS400 or Non Oracle ERP systems like SAP / JDE or From Custom Oracle Applications. The data is placed into Interface tables and from there either from Application or from PL/SQL , you can call Auto Invoice Concurrent request to validate and transfer data into AR Transaction tables. The data from these tables can be seen when queries from Transaction Screens. Auto Invoicing is a process of creating an invoice automatically in AR when a sales order has been shipped and closed. This process is triggered by a concurrent request 'AUTO INVOICE MASTER PROGRAM'. Auto invoicing is used to import the AR invoices direclty into the AR module. 18. What is AUTO Accounting what are the steps for setting up auto accounting? Auto Accounting is a mechnism for generating defualt accounting flexfields for revenue , receivables, frieght and tax based on the other parameters associated with the invoice you are entering.. since auto accounting looks at the following tables to get the data so please set/define the following depending upon your requirement. 1.Salesrep. 2.Transaction Types. 3.Standard Lines. 4.Taxes. 5.Customer bill-to-site Receivables uses the Auto Accounting rules to determine the GL Accounts that you Enter manually or import using Auto invoice. Receivables creates the Default accounts for the Receivable, revenue, Freight, Tax, Unerned revenue, Finance charges, Unbilled receivables, Bills receivables, and Auto invoice Clearing Accoutns.You need to define these accoutns before you start entering the transactions in AR. However, you can overide these accounts during the Transaction Entry in AR.Setup Autoaccounting:AR>Setup>Transactions>AutoAccountingSelect the Type of the accoutn you wish to define the auto accoutning.In the Segments Block:Choose the segment for which you wish to assign the Auto accounting.Choose the Table Name : Sales Rep, Trxn Type, Site, Std Lines.If you wish to use a Default Constant value, then enter the value in the Constant Field. 19. what are the standard concurent programs for auto invoice interface and customer interfaces? Autoinvoice Import Program -- for auto invoice program Customer Interface Master Conc Program --> for Customer Interface 20. Explain the process of recievables in oracle financials? AR Complete Cycle (hoping that GL is already implemented)Define Transaction SetupsDefine Receipt and Receipt Application SetupsDefine CustomerCreate an InvoiceCreate a ReceiptApply Receipt to InvoiceReview Customer balances (Collections). The BASIC process of Receivables involves the following: 1. Creation of Customer Invoices.

2. Making the receipts of the customer payments. 3. Remittance fo the same to the bank. 21. How do we segregate debit & credit transactions in Receivables and where we will do it? Basically the debit and credit transaction are classified by the transaction class. 22. whether we are defining customer in AR? If it is in AR then how are we placing the order and how the shipment will be done? Customers and the associated information is stored in TCA structure, which is shared across All oracle application modules. If you add a customer in AR, it gets stored TCA underlying tables. When you want to create an Order in Order Management, the customer LOV displays data from Record Group that is created on TCA tables. The basic Oracle ERP data model is the single Data model shared (integrated) by multiple application. The owner of the creation of customer is the AR schema and is shared by other application such as OM. These are usually called as shared entities (Supplier,Partners,Items etc) 23. How To Close Periods In AR? After raising transactions and receiving the RECEIPT amount, transfer the all TRANSATIONS and RECEIPTS to the GENERAL LEDGER. And then only close the PERIOD in AR. 24. Explain about Party and Customer in AR? Party could be a person or an organization which has no business relation with your entreprise, if you establish a sales relation with a department in a party then that particular department is your customer.