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.

Implementing ERP – Selection to Rolling out

When implementing new a ERP system, implementing on time and on budget is not by chance. As with any project plan, a detailed and methodical process is required for success. A plan for selecting and implementing new ERP software is no different than any major project being undertaken by a corporation. It requires a significant investment of time and resources, requires the involvement of virtually the entire organization, as well as a considerable amount of research, planning, and reevaluation along the way.

The best project is well thought out and fully researched. It is not limited to a budget and time line, but focuses on tasks, owners, goals, and milestones. It begins at the time of software selection and goes well beyond go-live. And although most projects will stumble along the way, successful implementations that actually end on time and on budget are quite possible if managed properly.

we preach the importance of a solid selection and implementation plan. So much so, that we will voluntarily chose not to participate in the evaluation project if we feel the prospect’s selection process lacks structure. Why would we ever do that? Because the company will never be happy. If they do not know how to evaluate their own requirements or communicate those needs to others, they’ll never be able to successfully evaluate if a vendor’s ERP solution is a good fit for their unique requirements. And unfortunately if we can’t review their requirements with them, we cannot help evaluate if our package is a good fit either.

A solid evaluation project for new ERP software is broken out into some fairly set project goals and milestones. Regardless of the company, a proper project plan should include:

- A Review of Key Business Objects & Long-term Goals
- A Formation of a Selection Team & Project Leader
- An Ongoing Project Plan
- Research & Budget Preparation
- Clearly Defined Requirements & Project Goals
- Vendor Demonstrations & an RFP
- Reference Checks
- Data Migration
- Testing, Testing, & More Testing
- Training, Training, & More Training

In reality, you can easily execute on time, on task, and on budget by controlling the entire project through conception and go live. Led by in house or through an outside professional, flawless executions of software implementations are possible. They do not happen by chance, on their own, or without effort. But they are certainly a reality if given the right team and project plan.

Oracle A.I.M. Methodology – template list

Oracle A.I.M. Methodology encompasses a project management methodology with documentation templates that support the life cycle of an implementation. The life cycle methodology and documentation templates allows A.I.M. to be a very useful tool for managing implementation projects successfully. This is a depiction of the A.I.M. methodology life cycle:

Application Implementation Method is a proven approach for all the activities required to implement oracle applications. there are eleven processes of implementation.

1. Business Process Architecture [BP] – This phase outlines:

• Existing Business Practices
• Catalog change practices
• Leading practices
• Future practices

BP.010 Define Business and Process StrategyBP.020 Catalog and Analyze Potential Changes

BP.030 Determine Data Gathering Requirements

BP.040 Develop Current Process Model

BP.050 Review Leading Practices

BP.060 Develop High-Level Process Vision

BP.070 Develop High-Level Process Design

BP.080 Develop Future Process Model

BP.090 Document Business Procedure

 

 

 

 

 

2. Business Requirement Definition [RD] - This phase explains about the initial baseline questionnaire and gathering of requirements.

RD.010 Identify Current Financial and Operating Structure RD.020 Conduct Current Business Baseline RD.030 Establish Process and Mapping Summary RD.040 Gather Business Volumes and Metrics RD.050 Gather Business Requirements RD.060 Determine Audit and Control Requirements RD.070 Identify Business Availability Requirements RD.080 Identify Reporting and Information Access Requirements

3. Business Requirement Mapping [BR] – In this phase the requirements of business are matched with the standard functionality of the oracle applications.

BR.010 Analyze High-Level GapsBR.020 Prepare mapping environment

BR.030 Map Business requirements

BR.040 Map Business Data

BR.050 Conduct Integration Fit Analysis

BR.060 Create Information Model

BR.070 Create Reporting Fit Analysis

BR.080 Test Business Solutions

BR.090 Confirm Integrated Business Solutions

BR.100 Define Applications Setup

BR.110 Define security Profiles

 

 

 

 

 

4. Application and Technical Architecture [TA] – This outlines the infrastructure requirements to implement oracle applications.

TA.010 Define Architecture Requirements and StrategyTA.020 Identify Current Technical Architecture

TA.030 Develop Preliminary Conceptual Architecture

TA.040 Define Application Architecture

TA.050 Define System Availability Strategy

TA.060 Define Reporting and Information Access Strategy

TA.070 Revise Conceptual Architecture

TA.080 Define Application Security Architecture

TA.090 Define Application and Database Server Architecture

TA.100 Define and Propose Architecture Subsystems

TA.110 Define System Capacity Plan

TA.120 Define Platform and Network Architecture

TA.130 Define Application Deployment Plan

TA.140 Assess Performance Risks

TA.150 Define System Management Procedures

 

 

 

 

 

5. Build and Module Design [MD] – This phase emphasizes the development of new functionality (customization) required by the client. It mainly details how to design the required forms, database and reports.

MD.010 Define Application Extension StrategyMD.020 Define and estimate application extensions

MD.030 Define design standards

MD.040 Define Build Standards

MD.050 Create Application extensions functional design

MD.060 Design Database extensions

MD.070 Create Application extensions technical design

MD.080 Review functional and Technical designs

MD.090 Prepare Development environment

MD.100 Create Database extensions

MD.110 Create Application extension modules

MD.120 Create Installation routines

 

 

 

 

 

6. Data Conversion [CV] – Data Conversion is the process of converting or transferring the data from legacy system to oracle applications. Ex. Transferring customer records from the legacy to the Customer Master.

CV.010 Define data conversion requirements and strategyCV.020 Define Conversion standards

CV.030 Prepare conversion environment

CV.040 Perform conversion data mapping

CV.050 Define manual conversion procedures

CV.060 Design conversion programs

CV.070 Prepare conversion test plans

CV.080 Develop conversion programs

CV.090 Perform conversion unit tests

CV.100 Perform conversion business objects

CV.110 Perform conversion validation tests

CV.120 Install conversion programs

CV.130 Convert and verify data

 

 

 

 

 

7. Documentation [DO] – Documentation prepared per module that includes user guides and implementation manuals.

DO.010 Define documentation requirements and strategyDO.020 Define Documentation standards and procedures

DO.030 Prepare glossary

DO.040 Prepare documentation environment

DO.050 Produce documentation prototypes and templates

DO.060 Publish user reference manual

DO.070 Publish user guide

DO.080 Publish technical reference manual

DO.090 Publish system management guide

 

 

 

 

 

8. Business System Testing [TE] – A process of validating the setup’s and functionality by QA(functional consultant) to certify status.

TE.010 Define testing requirements and strategyTE.020 Develop unit test script

TE.030 Develop link test script

TE.040 Develop system test script

TE.050 Develop systems integration test script

TE.060 Prepare testing environments

TE.070 Perform unit test

TE.080 Perform link test

TE.090 perform installation test

TE.100 Prepare key users for testing

TE.110 Perform system test

TE.120 Perform systems integration test

TE.130 Perform Acceptance test

 

 

 

 

 

9. Performance Testing [PT] - Performance testing is the evaluation of transactions saving time, transaction retrieval times, workflow background process, database performance, etc

PT.010 – Define Performance Testing StrategyPT.020 – Identify Performance Test Scenarios

PT.030 – Identify Performance Test Transaction

PT.040 – Create Performance Test Scripts

PT.050 – Design Performance Test Transaction Programs

PT.060 – Design Performance Test Data

PT.070 – Design Test Database Load Programs

PT.080 – Create Performance Test TransactionPrograms

PT.090 – Create Test Database Load Programs

PT.100 – Construct Performance Test Database

PT.110 – Prepare Performance Test Environment

PT.120 – Execute Performance Test

 

 

 

 

 

10. Adoption and Learning [AP] – This phase explains the removal of the legacy system and oracle application roll out enterprise wide.

AP.010 – Define Executive Project StrategyAP.020 – Conduct Initial Project Team Orientation

AP.030 – Develop Project Team Learning Plan

AP.040 – Prepare Project Team Learning Environment

AP.050 – Conduct Project Team Learning Events

AP.060 – Develop Business Unit Managers’Readiness Plan

AP.070 – Develop Project Readiness Roadmap

AP.080 – Develop and Execute CommunicationCampaign

AP.090 – Develop Managers’ Readiness Plan

AP.100 – Identify Business Process Impact onOrganization

AP.110 – Align Human Performance SupportSystems

AP.120 – Align Information Technology Groups

AP.130 – Conduct User Learning Needs Analysis

AP.140 – Develop User Learning Plan

AP.150 – Develop User Learningware

AP.160 – Prepare User Learning Environment

AP.170 – Conduct User Learning Events

AP.180 – Conduct Effectiveness Assessment

 

 

 

 

 

11. Production Migration [PM] – The process of “decommissioning” of legacy system and the usage(adoption) of oracle application system.

PM.010 – Define Transition Strategy

PM.020 – Design Production Support Infrastructure

PM.030 – Develop Transition and Contingency Plan

PM.040 – Prepare Production Environment

PM.050 – Set Up Applications

PM.060 – Implement Production Support Infrastructure

PM.070 – Verify Production Readiness

PM.080 – Begin Production

PM.090 – Measure System Performance

PM.100 – Maintain System

PM.110 – Refine Production System

PM.120 – Decommission Former Systems

PM.130 – Propose Future Business Direction

PM.140 – Propose Future Technical Direction

thanks – Shivmohan Purohit

Oracle Property Manager – Introduction – Overview

Introduction

The Property Management Module is designed as a property database for organisations with large property  management portfolios. This paper is to provide an overview of the module describing its features and functionality. Using this structured database users can manage space allocations within their portfolio for both employees and/or customers. Customers’ space can be charged via an interface to the Accounts Receivable package or invoices for rent can be generated and interfaced to the Accounts Payable Module.

The database will hold various types of data including, features, contacts, tenancies, lease and other documentation such as insurances, rights, obligations and milestones. The module also has the standard flexfield functionality as in other Oracle Modules for the capture of user-defined data.

Property Definition

The database of properties has an inbuilt hierarchy starting at the top by grouping properties within regions and office parks. A property is then defined as a combination of land detail and building detail. Land can be subdivided into parcels. Land details include area, conditions and features that can be recorded against each land or parcel record. The use of flexfields would allow for the recording of asset numbers, title details, etc. Building details can include address, tenure, user defined class and status. Additional details include rentable, useable and assignable area, occupancy area, features and contacts. Buildings can be further subdivided into floors, and again into offices with the same level of detail being recorded against each individual record at each level.

Assignments

Properties can be assigned to either employees or customers at any of the levels described above. With each of these assignments cost centres or GL codes can be associated for revenue or costing purposes. The facility to record Project/Task/Organisation data has also been provided. The system provides statistical information on the assignments and total occupancy at the building, floor and office levels. Query screens are provided to enquire on the assignment data at each of the levels.

Leases and Documents

Lease details and various classifications of documents can be associated with each building floor or office. The details of these documents can be recorded and may form the basis for either billing customers through Accounts Receivable or the payment of rent through Accounts Payable. Recurring invoices for either accounts Receivable or Accounts Payable can be constructed within this module and after approval, interfaced directly to the other modules. This approval can be into the future.

Detail in these screens is extensive with tabs for Detail, Contacts, Locations, Insurances, Rights, Obligations, Options, Billings and Notes. There is a facility to record milestones which will generate notifications to responsible officers so they can be notified of specific occurrences with lead times set by the user. Using the details from Lease Documents the system will generate individual entries for export to Accounts Payable and Accounts Receivable. Each entry is created as a draft and must be approved prior to export. Details of these entries are maintained in Property Manager.

Agents

The system also maintains a list of agents or contacts related to each property. These contacts can be used throughout the module. They are divided into Customers, Suppliers and Employees. Using the standard integration of Oracle Applications these contacts are maintained in their respective modules. A contact role is available for allocation throughout the Property Module.

Reports

Standard reports with the system are divided into Space, Rent, Employee, Lease and other reports. The system has some 30 standard reports including 7 RXi reports. Specific reports based on client needs will require the use of Discoverer or other reporting tool. The module also has facilities to import and export data to CAD models for space allocations and locations.

In General

The Property Management Module can be interfaced to both the Accounts Payable and Accounts Receivable modules and if required, using flexfields, linked with the Fixed Asset module. The module is not used for maintenance cost recording however, property numbers could be referenced in Accounts Payable using flexfields for the creation of a property cost reporting mechanism. Our client uses the system as a Property Register, which records all possible information about a property. Security suppliers, cleaning suppliers, landlords, insurances, renewal dates, etc can all be recorded and found quickly. The major benefit from the system is the billing of rent to customers. Our client is a Water and Power utility that rents space for communications towers on various infrastructure assets. Tracking all the rent invoices on a monthly basis was completed using spreadsheet. The Property Management Module allows for the tracking of what has or has not been billed and in conjunction with the Accounts Receivable module what has or has not been paid.

Oracle Reports (Report 6i) – Technical – Interview – Question Answers

Oracle Reports (Report 6i) – Technical – Interview – Question Answers

 Question: How many types of columns are there and what are they

Formula columns: For doing mathematical calculations and returning one value
Summary Columns: For doing summary calculations such as summations etc.
Place holder Columns: These columns are useful for storing the value in a variable 

 

Question: Can u have more than one layout in report

Answer: It is possible to have more than one layout in a report by using the additional layout option in the layout editor. 

Answer: Yes it is possible to run the report without parameter form by setting the PARAM value to Null

Question:  What is the lock option in reports layout

Answer:  By using the lock option we cannot move the fields in the layout editor outside the frame. This is useful for maintaining the fields. 

Question: What is Flex

Answer: Flex is the property of moving the related fields together by setting the flex property on 

Question: What is the minimum number of groups required for a matrix report

 

 Question: How many different triggers are available in Report?

 Answer: There are five types of triggers in report 6i

 1) Before report trigger

2) After report trigger

3) Before Parameter trigger

4) After parameter trigger

5) Between pages trigger

 

Question: What is the Firing sequence of report trigger?

Answer: First the before parameter trigger will raise, after firing this trigger parameter form will displayed, after passing parameter after parameter trigger will fire query will parsed & then before report trigger will fired then if there are number of pages in your report then the between pages trigger will fired but it will fire between first & second & so on pages but it will not fired in reverse condition the after report trigger will fire after closing the runtime parameter form is closed.

 

Question: What is bind variables?

Answer: Bind variables are used in report 6i for replacing the single parameter in the select statement

 Question: What is lexical parameter?

Answer: Lexical Parameter is used to replace the where, order by ………conditions at run time.

 

Question: What are different types of column in reports?

Answer: There are three types of columns in the report 6i these are:

1) Placeholder Column – Placeholder column is used to store a value for a variable.

2) Formula Column

3) Summary Column

Answer: The minimum of groups required for a matrix report are 4

Question: Can u run the report with out a parameter form

Learning New Tools – A Perspective

Learning new tools and technologies has become part of daily chores of any IT professional. There is no way out. Or there is no good reason of why one should not learn new things. I personally am a tech savvy guy and always in lookout of learning new things. The interest is not just to learn things pertaining to data warehouse and BI but everything, which comes on way. The only thing that the new tools/technology I learn should have some fundamentals or concepts to take home.

During this last 6-7 years of being into IT, I have learned numerous theories, technologies, programming languages, tools etc. Most of them were through self-learning. But this self-learning was dependent on all my previous learnings, which I inculcated in the past and without which all this self learning would not have been possible. Today I just picked one more tool/technology to build some understanding on it. I don’t have the access to the software but just the documentation. This is one among few tools/technology I am trying to learn for which I don’t have the access of the software. Though I have hands on extensive hands-on experience on a similar kind of technology by another vendor.

This whole thing lead me to think of how can one approach taking up new tool/technology. Possibly three ways which came into my mind:

1. First hit the document.. get some background. and then come to the tool/hands-on and then again go back to the manuals/references. .. an then back to hands on.. May be over the period doing both things simultaneously.
2. First hit the tool ..let your intuition take over the wheel first.. play around stretch your understanding/intuition… and then come back to references/manual/docs/some text and then back to the tool. Over the period both doing both things simultaneously.
3. First attend some seminar ,some talk, some discussion ( as good as 1 but instead of text you are get into more live things) and then hit the tool may be then back to the manuals tools.. come back to tool/hands-on then go back to discussion and so forth. May be I call it Spaghetti approach. In this approach it could be that you start with Books first and then tools an then talks or any combination.

Which to choose?? Time and availability of resources can give the right call for this.. I keep trying all this approaches. Most of the times approach 2 is a good deal for me. Approach 1 is something we have been trying since the college days. First read about the “c” language, listen some lectures… and then get to the labs for some hands-on. And that was good since one didn’t had so many fundamentals/concepts built up, not so much of exposure to the tools/languages of similar kind. Again like all my postings, there is no need to reach to conclusion of which is better and which not. Depends like everything else. My idea here is just to bring out some points.

Run Posting (GLPPOS), or other concurrent programs from the Command line

Run Posting (GLPPOS), or other concurrent programs from the Command line?

 How to Run Posting (GLPPOS), or other concurrent programs from the Command line?

 You can run any GL program from the command line. Follow these steps:

 1) Verify that you run this at a time when there are no incompatible Programs running. To find the incompatible programs:

    Responsibility = System Administrator

   GUI Navigation = Concurrent/Program/Define

    Query on GLPPOS in the Short Name field.

   Click on the Incompatibilities button.

     

2) Change the profile “Concurrent Hold Request” to Yes.

    Responsibility = System Administrator

   GUI Navigation = Profile/System 

    Query on the profile option ‘Concurrent Hold Requests’.

   Set it to Yes at the User level and Save.

 

3) Select a journal batch for posting. The request will be put on hold.

    Responsibility = General Ledger Super User

   GUI Navigation = Journals/Post

 

4) Go to the Concurrent Requests form and get the parameters for the Posting concurrent process.

       The parameters for posting are:

        set of books id

        chart of accounts id

        posting_run_id

 

5) Run posting from the command line.

 $GL_TOP/bin/GLPPOS <username/pwd> 0 Y <parameters> X 2> <File name>

 Where:   <username/pwd> : apps username and password

              <parameters>   : The parameters for the program, separated by spaces. For NULL parameters you need to specify closed double quotes (“”).

              X              : Indicates that you want to run the program in debug mode. This can be any character and is optional.

              2> <File name> : Use this to redirect standard errors and output to a file. File name is the output  file name it will create. It will be created in your current directory, if a full path                                is not specified. This is optional

                               but recommended.

   Example:

   If you go to the concurrent requests form and see in the Parameters field: 1,101,2546, you would enter the following command at the Unix prompt:

 $GL_TOP/bin/GLPPOS <username/pwd> 0 Y 1 101 2546 X 2> <myfile.txt>

 6) Change the profile option ‘Concurrent Hold Requests’ back to its  original setting. Be sure to run the program from a directory for which you have write Privileges. That is where the log and out files will be created.

Also make sure that you are in the proper application environment.

 

Here is an example of the command and the output you will see.

 $>$GL_TOP/bin/GLPPOS apps/apps 0 Y 8 50128 84 2 2> njpost2.out

 DEBUG: started in debug_mode……

  $> ls

 L54536.log   L54540.log   O54536.out   O54540.out   njpost.out   post.out

 L54538.logL54542.log   O54538.out   O54542.out   njpost2.out  test

 $> more njpost2.out

 Log filename    : L54542.log

 Report filename : O54542.out

 glpmai() fnd_user_id is -1

 glpmai() fnd_user_name is ANONYMOUS

 glpmai() req_id is 0

 glpmai() sob_id is 8

 etc.

 selected General Ledger programs can be run in debug

      mode by setting the profile option ‘GL: Debug Mode’ to Yes at the

      appropriate level.

      These programs are:

      - GLCRVL – Revaluation

      - GLPPOS – Posting

      - GLTTRN – Translation

      - GLCCON – Consolidation Transfer

      - GLAMAS – Run MassAllocations

 

Account Recievables – Conversion – Invoices

Whenever we are going in for implementation of Receivables module, we have to consider the necessity of bringing in customer open balances from the old system to Oracle Receivables.

Some of the key questions that needs to be addressed before we take up a conversion activity. This is just a sample list and not an exhaustive one:

1. What are the different types of invoices in existing system Provide invoice samples? (invoices, credit/ debit memos, commitments, chargebacks)

2. Do we need to migrate only open invoices?

3. Do we migrate closed invoices also, if yes, then for what time period?

4. Please explain the invoice numbering mechanism? Is it automatic?

5. What are the interfaces from/to your existing receivables system?

6. Will the old system still be in place for querying and reporting purpose?

 

One can adopt one of the following three strategies for conversion:

1. Consolidate all the open balances customer-wise and create a single open invoice for each customer in the new Oracle system. The advantage of this system is that it is quite easy and not data intensive and makes good business sense in case of small businesses with very few customers. The major demerit of this approach is that later on one cannot track the individual invoices which the customer had sent and can become an audit issue also. In case of dispute over payment, this invoice will remain open till the dispute is resolved. Also, aging of invoices and dunning history will be lost.

2. Bring in all the open and partially paid invoices, credit/debit memos into the new system. Migrate all the unapplied and partially applied receipts to the new system. The advantage of this process of conversion is that you can track all open invoices individually and apply the correct receipt to correct invoice. Also, the conversion effort will be moderately low compared to case if you migrate all open and closed invoices. The disadvantage of this approach is that you cannot have a track of closed invoices in the new system. Also, it would be tough to handle scenarios where there is a dispute regarding incorrect receipt application, etc. This is the most common approach taken for receivables invoice, credit/debit memo and receipt migration.

3. Migrate all open and closed invoices to the new system. Reapply the migrated receipts to invoices in the new system. This approach makes sense if your receivables data is quite small else the effort involved in migrating all closed invoices and credit memos to the new system does not make much business sense.

The next question that arises is how we should migrate the invoices, credit/debit memos and receipts to the new system. Oracle provides standard interfaces to load the same. We can also use tools like Dataloader or manually key in the data into Oracle.

In this article i will talk of invoice, credit/debit memo conversion only. Prior to invoice migration, customer migration should be over apart from other pre-requisites. Following is the list of pre-requisites that should be completed prior to invoice, credit/debit memo conversion:

•Set-up of Customer Payment Terms should be complete

•Set-up of Currencies should be complete (this is necessary in case you have foreign currency invoices also)

•Set-up of Transaction Types should be complete

•Set-up of Accounting Rules should be complete

•Set-up of Tax rates and Tax codes should be complete

•Set up for sales representative should be complete

•Set up for debtor area should be complete

•Set up for income category should be complete

•Automatic customer invoice numbering should be set to ‘No’

•Customer and Customer address should be migrated in the system

•Disable the Invoice interface purge program so that the data successfully imported should not get purged in the interface table.

•Set up for invoice batch source name should be complete

In the next step extract Invoice data from the legacy files and using SQL loader populate the interface tables RA_INTERFACE_LINES_ALL and RA_INTERFACE_DISTRIBUTIONS_ALL. Submit the Auto Invoice open interface program. Data from the two interface tables will be uploaded to the following base tables using the Invoice open interface program:

•RA_CUSTOMER_TRX_ALL

•RA_CUSTOMER_TRX_LINES_ALL

•RA_CUST_TRX_LINE_GL_DIST_ALL

•RA_BATCHES_ALL

•RA_CUST_TRX_LINE_SALESREPS_ALL

•AR_RECEIVABLE_APPLICATIONS_ALL

•AR_PAYMENT_SCHEDULES_ALL

•RA_INTERFACE_ERRORS_ALL

Ensure that the Purge Interface check box is not checked when you submit the Autoinvoice program. In the Autoinvoice errors form you can see the error corresponding to failed records. Correct the errors in the interface table and rerun the Autoinvoice program. Submit the Autoinvoice Purge Program separately. Only records that have been successfully processed by Autoinvoice are purged.

Using autoinvoice you can migrate invoices, credit/debit memos and on-account credits into Oracle. However, you have to set grouping rules (Navigation > Setup > Transactions > Autoinvoice > Grouping Rule) to group lines to create one transaction and ordering rules (Navigation > Setup > Transactions > Autoinvoice > Line Ordering Rules) to determine the order of the transaction lines on a particular invoice.

How to restrict functions and menus available to a user in menus

Hello Friends, Using this article, i wanted to give brief on how we can exclude some forms/ function as security in oracle applications. plz see i am trying to use two different way to get the same functionality.
There are two possibilities:
                    A – Restrict an existing menu:   
1) Log in as System Administrator responsibility  
2) Find the name of the appropriate menu      Navigator: Application -> Menu  
3) Create a new responsibility       Navigator: Security -> Responsibility -> Define  
4) Assign the appropriate menu to the new responsibility  
5) Enter functions in the Function and Menu Exclusions section of the form Responsibilities  
6) Save  
7) Assign the new responsibility to the appropriate user
 
Example:  Restrict a user to be able to do only Assignments in the Asset Workbench.
  1) Log in as the System Administrator responsibility
  2) Find the name of the appropriate menu:
   Description: %Asset%
  2) Create a new responsibility: ASSET – assignments
  3) Assign the menu FA_TRANSACTION to the responsibility ASSET – assignements
  4) Enter all functions from the LOV in the Function and Menu Exclusions
     section except of the Responsibilities form except “Asset Workbench” and
     “Assets:Assignments”
  5) Save
  6) Assign the responsibility ASSET – assignments to the appropriate user

                      B – Create a new menu: 
1) log in as System Administrator responsibility 
2) Create a new menu: Navigator: Application -> Menu      The new menu should contain only the functions and menus which should be accessible for the user. 
3) Create a new responsibility       Navigator: Security -> Responsibility -> Define 
4) Assign the appropriate menu to the new responsibility 
5) Save 
6) Assign the new responsibility to the appropriate user
                 
Example:  Restrict a user to be able to do only Assignments in the Asset Workbench.
 1) Log in with the System Administrator responsibility
2) Create the new menu menu:
   Navigator: Application -> Menu
   Menu: FA_ASSIGN
   User Menu Name: FA Assignement
   Description: FA Assignement
   Seq: 1 Navigator Prompt: Assignment Function: Asset Workbench
   Seq: 2 Navigator Prompt: Assignment Function: Assets:Assignements
3) Create a new responsibility: ASSET – assignments
4) Assign the menu FA_ASSIGN to the responsibility ASSET – assignements
5) Save
6) Assign the responsibility ASSET – assignments to the appropriate user

 

Please share your feedback and also if you think this article is helpful for you. or if this is difficult to understand and use, so i can improve on my future articles. thanks – Shivmohan Purohit

Distribute the workload of concurrent requests in the same node

How to distribute the workload of concurrent requests in the same node?
In order to distribute concurrent requests to distinct concurrent managers on the same node, you
have to :
1 – Create a new concurrent manager on the forms Define Concurrent Managers from the System Administrator responsibility ( set the same setup as the Standard Concurrent manager ), then click on the button Specialization Rules and Include the concurrent programs you want to run on this concurrent manager.
2 – Query the Standard concurrent manager on the forms Define Concurrent Managers from the System Administrator responsibility, then click on the button Specialization Rules and Exclude the concurrent programs you include in step 1 for the new concurrent managers.
3 – Bounce the concurrent managers.

Thanks – Shivmohan Purohit