Oracle Project Intercompany Invoices to Payables


Friends, here is Oracle Project billing insight on its integration with AR. How to Interface Oracle Project Intercompany Invoices to Payables

 

To explain how intercompany invoices are interfaced to Payables

 

When the provider operating unit runs the Tieback Invoices from Receivables process, the intercompany invoices are automatically copied into the interface table of the receiver operating unit’s Payables. Intercompany invoices interfaced to Payables are identified with the following attributes:

 

Source. All intercompany invoices have a source of Projects Intercompany Invoices.

• Supplier. The supplier is identified by the provider operating unit’s internal billing implementation options.

• Supplier Site. The supplier site is based on how the provider operating unit defines the receiver controls for the receiver operating unit.

• Invoice Amount. The Payables invoice amount is the amount of the related Receivables invoice, including taxes. The interface process populates the project–related attributes for intercompany Payables invoice distributions, as indicated below:

• Project Number. The number of the cross charged project indicated in the invoice line.

Task Number. The number of the task specified in the Intercompany Tax Receiving Task field on the cross charged project.

• Expenditure Item Date. The invoice date of the intercompany Receivables invoice.

• Expenditure Type. The expenditure type specified by the receiver operating unit in the Receiver Controls tab.

Expenditure Organization. The expenditure organization specified by the receiver operating unit in the Receiver Controls tab.

 

In addition, the interface process matches the tax code from each invoice line of the Receivables invoice to the appropriate Oracle Payables tax code. This process indicates that the Payables invoice distributions do not include tax amounts, so that the Payables Open Interface process creates the invoice distributions for the entire invoice by grouping the tax lines based on the following attributes:

 

Tax code

Project information (project, task, expenditure item date, expenditure type, expenditure organization)

thanks – shivmohan purohit

DataLoad with Oracle E-business Suites (Oracle Applications/ Financials)


DataLoad with Oracle E-business Suites (Oracle Applications/ Financials)

 

 

 

 

 

DataLoad is a tool for manipulating the data and commands in Oracle E-Business and other software by sending pre-defined data and commands to the target program. These help pages are the primary source of information about DataLoad and how to use it. Follow one of the menu links on the left to the section which best fits your question or use the table of contents to find the information you are looking for. Implementing or supporting any application often requires significant effort to configure and load master and transaction data, for example from legacy systems, an expensive and time-consuming activity.

DataLoad reduces the time and costs associated with data migration. Its easy-to-use interface means that it can be used by non-technical employees, giving end-users an active role in the implementation and support of any system.

·   Non-technical users can easily configure and load data into any system

·   Recommended by Oracle, DataLoad contains specific additional features to load large volumes of data in any implementation of Oracle Applications.

·   DataLoad is sponsored by leading UK systems integrator Edenbrook, which has committed to support and improve the tool.

·   DataLoad is available in Classic and Professional editions, catering to all types of application implementation from the simple to the vastly complex.

·   DataLoad Classic is available to download free of charge.

 

 

 

Q. Can I use DataLoad with Oracle E-Business 11i, E-Business R12, etc?

A. DataLoad works with any Windows based applications and contains enhancements for use with Oracle E-Business. DataLoad has been tested with all current versions of E-Business that are supported by Oracle and has been proved to work correctly. As new versions of E-Business are released DataLoad is tested with these releases to ensure continued support. Full R12 compatibility was added in DataLoad V4.3.9.0.

 

Oracle – Technical FAQ – Part 4


 Q18.) What are the OOPS concepts in Oracle?

A18.) Oracle does implement the OOPS concepts. The best example is the Property Classes. We can categorise the properties by setting the visual attributes and then attach the property classes for the objects. OOPS supports the concepts of objects and classes and we can consider the property classes as classes and the items as objects.

 

Q19) What is the difference between candidate key, unique key and primary key?

A19) Candidate keys are the columns in the table that could be primary keys and the primary key is the key that has been selected to identify the rows. Unique key is also useful for identifying the distinct rows in the table.

 

Q20) What is concurrency?

A20) Concurrency is allowing simultaneous access of same data by different users. Locks useful for accessing the database are

a) Exclusive — The exclusive lock is useful for locking the row when an insert , update or delete is being done. This lock should not be applied when we do only select from the row.

b) Share lock — We can do the table as Share_Lock as many share_locks can be put on the same resource.

 

Q21) What are the Previleges and Grants?

A21) Privileges are the right to execute a particular type of SQL statements. The grant has to be given by the owner to object.

 

Q22) What are Table Space, Data files, parameter file, control files?

A22) Table space: The table space is useful for storing the data in the database. When a database is created two table spaces are created.

a) System Table space : This data file stores all the tables related to the system and dba tables.

b) User Table Space: This data file stores all the user related tables.

We should have separate table spaces for storing the tables and indexes so that the access is fast.

Data files : Every oracle Data base has one or more physical data files. They store the data for the database. Every datafile is associated with only one database. Once the data file is created the size can not change. To increase the size of the database to store more data we have to add data file.

Parameter file:Parameter file is needed to start an instance. A parameter file contains the list of instance configuration parameters e.g. db_block_buffers = 500

db_name = ORA7

db_domain = u.s.acme lang

Control files : Control files record the physical structure of the data files and redo log files . They contain the DB name, name and locations of dbs , data files, redo log files and time stamp.

 

Q23) What is physical storage of the Data?

A23) The finest level of granularity of the data base are the blocks.

Extent : Extent is the number of specific number of contigious data blocks.

Segments : Set of Extents allocated for Extents. There are three types of segments

a) Data Segment : Non clustered tables has data segment data of every table is stored in cluster data segment.

b) Index Segment : Each index has index segment that stores data.

c) Rollback Segment : Temporarily store ‘undo’ information.

 

Q24) What is Normalisation ? Explain 1NF, 2NF, 3NF.

Normalization is a process of eliminating data redudancy.

1NF- No repeating groups.

2NF- Eliminates the functional dependency on the partial key field.

3NF- Eliminates the functional dependency on the non-key field.