All types of accounts we learnt in the last chapter viz. Personal, real, and nominal are summarized in Ledger. Ledger is a book which contains a classified and permanent record of all the transactions of a business.
Ledgers are bound book or loose leaf with each account starting on new page, and each page numbered. Loose-leaf ledger allows addition of pages, removal of completed accounts, and rearrangement of accounts. Ledger is principal book containing all the accounts also called “Book of Final Entry” or “Book of secondary entry” because transactions are recorded here finally. Ledger offers following benefits. Ledger gives snapshot of an account, all at one place. For example all cash transactions at one place.
Trial balance can be prepared to check arithmetical accuracy of the accounts in ledger. It facilitates preparation of final accounts for ascertaining operating result and financial position of the firm. Ledger Book Dr Cr Date Particulars J.F Amount Date Particulars J.F Amount Year Month Date To (Name of Credit Account in Journal) Year Month Date By (Name of Debit account in Journal) As shown above each ledger account is divided into two parts: left hand side is known as debit side and right hand side credit side. Debit and credit is abbreviated as ‘Dr.’ and ‘Cr.’ Account name is mentioned in the middle and at the top of the account. ‘To’ is used on the debit side in the particulars column.
Similarly, the word ‘By’ is used on the credit side. The name of the account affected is written in debit or credit side in particulars column. Journal page number is entered in J.F column.
For amount a separate column is also provided. Posting of Transactions Posting is the process of transferring entries from journal to the respective accounts in the ledger. All transactions relating to a particular account are grouped in ledger. It is necessary to know the net effect of various transactions during a given period on particular account. Now we shall see the procedure of posting entries from journal to ledger.
Let us assume a scenario of posting for an account which has been debited in the journal entry. First locate account to be debited. Enter date of the transaction in date column. Record the name of the account credited in the Journal in the particulars column on the debit side as “To. (Name of the account credited)”. Record the page number of the Journal in the J.F column on the debit side and in the Journal, write the page number of the ledger on which a particular account appears in the L.F.
Enter the relevant amount in the amount column on the debit side.For scenario of posting for an account which has been credited in the journal entry, procedure is same, except at step 1 and 2. These steps would be as follows.
First locate account to be credited. Enter date of the transaction in date column. Record the name of the account debited in the Journal in the particulars column on the credit side as “By. (Name of the account debited)”. For example If you have started business with cash Rs. 5000 on 1st June 2009.
The above transaction will appear in Journal and Ledger as under. Date Particulars L.F Debit Rs Credit Rs Jun 1, Cash A/c Dr.
![]()
10 5000 - 2009 To Capital A/c 23 - 5000 (Business started) Here two accounts are involved, Cash Account and your capital account, so ledger shall have page for each account. Cash Account Cr Date Particulars J.F Amount Date Particulars J.F Amount June 1, 2009 Cash A/c 5000 Posting of Opening Entries We learnt about opening entries which are passed at the beginning of new financial year which is nothing but the debit or credit balance of an account at the end of accounting period. Let us see the procedure. An account with debit balance is recorded with words “TO BALANCE B/D” on debit side and with credit balance “BY BALANCE B/D” on credit side. We can not say this process as “posting” but merely incorporating in the ledger.
Let us take one example of posting the opening entry into the ledger of PHPL as on 1st April 2010, cash in hand Rs. 10,000; Loan Rs.
OracleAppsGuide (OAG) is a platform for Oracle Apps R12 and 11i to understand and share live experience on it. Its online knowledge sharing hub and the best platform for learner and Experience holder as well. OAG makes easy to do your assignment in Oracle Apps R12 and 11i. But OAG will not be responsible for any fault, failure, data damage and error. Make sure about your steps whatever you are doing on your instance; it’s a platform to help in that!
But only you are the responsible for any misshaping in your apps. We are trying to always resolve your problems and error up to the level best.
All Copyright content, trademark, process, pictures, and any legal content used only for sharing the knowledge for the reader. “A GUIDE FOR ORACLE E-BUSINESS SUITE” – A complete Solution and Learning platform For Oracle Apps R12/11i, Training, India Localization, Technical, P2P, O2C, Drop-shipment, AR/AP Cycle, Implementation, Bug or error in Oracle Apps R12/11i, Up-gradation, Support, Alert, Personalization, Discoverer management, OracleApps R12/11i Module, Finance, SCM, MRP, ASCP, WIP, BOM, FA, AP, AR, OM, INV, AOL, MOAC, TCA structure, Project Accounting, CM, Functional,Oracle DBA, ERP, Techno-functional, OAF, Oracle Apps Interview Question and Error in Oracle apps R12/11i. For More Information Visit on Or Subscribe your email-id on OracleAppsGuide. SELECT pa.agentid, papf.personid, papf.employeenumber, papf.emailaddress, pa.categoryid, pa.locationid, papf.effectivestartdate, papf.effectiveenddate FROM poagents pa, perallpeoplef papf, hrallorganizationunits haou WHERE pa.agentid = papf.personid AND papf.businessgroupid = haou.businessgroupid AND TRUNC (SYSDATE) BETWEEN papf.effectivestartdate AND papf.effectiveenddate -AND emailaddress = '[email protected]' -AND PAPF.EFFECTIVEENDDATE SYSDATE -AND HAOU.BUSINESSGROUPID = 100. “A GUIDE FOR ORACLE E-BUSINESS SUITE” –A complete Solution and Learning platform For Oracle Apps R12/11i, Training, India Localization, Technical, P2P, O2C, Drop-shipment, AR/AP Cycle, Implementation, Bug or error in Oracle Apps R12/11i, Up-gradation, Support, Alert, Personalization, Discoverer management, OracleApps R12/11i Module, Finance, SCM, MRP, ASCP, WIP, BOM, FA, AP, AR, OM, INV, AOL, MOAC, TCA structure, Project Accounting, CM, Functional,Oracle DBA, ERP, Techno-functional, OAF, Oracle Apps Interview Question and Error in Oracle apps R12/11i. For More Information Visit on Or Subscribe your email-id on OracleAppsGuide. “A GUIDE FOR ORACLE E-BUSINESS SUITE” –A complete Solution and Learning platform For Oracle Apps R12/11i, Training, India Localization, Technical, P2P, O2C, Drop-shipment, AR/AP Cycle, Implementation, Bug or error in Oracle Apps R12/11i, Up-gradation, Support, Alert, Personalization, Discoverer management, OracleApps R12/11i Module, Finance, SCM, MRP, ASCP, WIP, BOM, FA, AP, AR, OM, INV, AOL, MOAC, TCA structure, Project Accounting, CM, Functional,Oracle DBA, ERP, Techno-functional, OAF, Oracle Apps Interview Question and Error in Oracle apps R12/11i.
For More Information Visit on Or Subscribe your email-id on OracleAppsGuide. “A GUIDE FOR ORACLE E-BUSINESS SUITE” –A complete Solution and Learning platform For Oracle Apps R12/11i, Training, India Localization, Technical, P2P, O2C, Drop-shipment, AR/AP Cycle, Implementation, Bug or error in Oracle Apps R12/11i, Up-gradation, Support, Alert, Personalization, Discoverer management, OracleApps R12/11i Module, Finance, SCM, MRP, ASCP, WIP, BOM, FA, AP, AR, OM, INV, AOL, MOAC, TCA structure, Project Accounting, CM, Functional,Oracle DBA, ERP, Techno-functional, OAF, Oracle Apps Interview Question and Error in Oracle apps R12/11i.
For More Information Visit on Or Subscribe your email-id on OracleAppsGuide. “A GUIDE FOR ORACLE E-BUSINESS SUITE” – A complete Solution and Learning platform For Oracle Apps R12/11i, Training, India Localization, Technical, P2P, O2C, Drop-shipment, AR/AP Cycle, Implementation, Bug or error in Oracle Apps R12/11i, Up-gradation, Support, Alert, Personalization, Discoverer management, OracleApps R12/11i Module, Finance, SCM, MRP, ASCP, WIP, BOM, FA, AP, AR, OM, INV, AOL, MOAC, TCA structure, Project Accounting, CM, Functional,Oracle DBA, ERP, Techno-functional, OAF, Oracle Apps Interview Question and Error in Oracle apps R12/11i. For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on. Brief, some pre-seeded lookups given by Oracle cannot be modified. For example, Oracle has a lookup type called a termination type as shown in above figure. Oracle has some rules defined within the Payroll Engine program that read the value of a termination type code for employees before calculating their final salaries.
Such lookup codes, if changed, can affect the logic within the Payroll Engine. For this reason, Oracle flags some lookups as system lookups, and the Lookup Entry screen will not let you modify those lookup codes.
Sometimes there is a need to create a database view that becomes the source of information for data transfer to other third-party systems. You might have to put filtration rules in place; for example, for HRMS Extract, people with person types Employee and Applicant should be extracted. To achieve this, instead of hard-coding Employee and Applicant in the database view, you can do the following: 1-Create a lookup type XXEXTRACTEMPLOYEETYPES. 2-Add lookup codes Employee and Applicant to this lookup type.
3-In the database view, join the HR Person Types from HR Tables with FNDLOOKUPVALUES for this lookup type. So through this manner, Lookup also gives you the flexibility to change hard-code Value in Code. “A GUIDE FOR ORACLE E-BUSINESS SUITE” –A complete Solution and Learning platform For Oracle Apps R12/11i, Training, India Localization, Technical, P2P, O2C, Drop-shipment, AR/AP Cycle, Implementation, Bug or error in Oracle Apps R12/11i, Up-gradation, Support, Alert, Personalization, Discoverer management, OracleApps R12/11i Module, Finance, SCM, MRP, ASCP, WIP, BOM, FA, AP, AR, OM, INV, AOL, MOAC, TCA structure, Project Accounting, CM, Functional,Oracle DBA, ERP, Techno-functional, OAF, Oracle Apps Interview Question and Error in Oracle apps R12/11i. For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on. “A GUIDE FOR ORACLE E-BUSINESS SUITE” –A complete Solution and Learning platform For Oracle Apps R12/11i, Training, India Localization, Technical, P2P, O2C, Drop-shipment, AR/AP Cycle, Implementation, Bug or error in Oracle Apps R12/11i, Up-gradation, Support, Alert, Personalization, Discoverer management, OracleApps R12/11i Module, Finance, SCM, MRP, ASCP, WIP, BOM, FA, AP, AR, OM, INV, AOL, MOAC, TCA structure, Project Accounting, CM, Functional,Oracle DBA, ERP, Techno-functional, OAF, Oracle Apps Interview Question and Error in Oracle apps R12/11i. For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on.
“A GUIDE FOR ORACLE E-BUSINESS SUITE” –A complete Solution and Learning platform For Oracle Apps R12/11i, Training, India Localization, Technical, P2P, O2C, Drop-shipment, AR/AP Cycle, Implementation, Bug or error in Oracle Apps R12/11i, Up-gradation, Support, Alert, Personalization, Discoverer management, OracleApps R12/11i Module, Finance, SCM, MRP, ASCP, WIP, BOM, FA, AP, AR, OM, INV, AOL, MOAC, TCA structure, Project Accounting, CM, Functional,Oracle DBA, ERP, Techno-functional, OAF, Oracle Apps Interview Question and Error in Oracle apps R12/11i. For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on.
Lightbulboutline Please take our October 2018 developer survey. Android includes support for high performance 2D and 3D graphics with the Open Graphics Library (OpenGL®), specifically, the OpenGL ES API. OpenGL is a cross-platform graphics API that specifies a standard software interface for 3D graphics processing hardware. OpenGL ES is a flavor of the OpenGL specification intended for embedded devices.
Android supports several versions of the OpenGL ES API:. OpenGL ES 1.0 and 1.1 - This API specification is supported by Android 1.0 and higher. OpenGL ES 2.0 - This API specification is supported by Android 2.2 (API level 8) and higher. OpenGL ES 3.0 - This API specification is supported by Android 4.3 (API level 18) and higher. OpenGL ES 3.1 - This API specification is supported by Android 5.0 (API level 21) and higher. Caution: Support of the OpenGL ES 3.0 API on a device requires an implementation of this graphics pipeline provided by the device manufacturer. A device running Android 4.3 or higher may not support the OpenGL ES 3.0 API.
For information on checking what version of OpenGL ES is supported at run time, see. Note: The specific API provided by the Android framework is similar to the J2ME JSR239 OpenGL ES API, but is not identical. If you are familiar with J2ME JSR239 specification, be alert for variations. Also see.
The basics Android supports OpenGL both through its framework API and the Native Development Kit (NDK). This topic focuses on the Android framework interfaces. For more information about the NDK, see the. There are two foundational classes in the Android framework that let you create and manipulate graphics with the OpenGL ES API:. If your goal is to use OpenGL in your Android application, understanding how to implement these classes in an activity should be your first objective. This class is a where you can draw and manipulate objects using OpenGL API calls and is similar in function to a. You can use this class by creating an instance of and adding your to it.
However, if you want to capture touch screen events, you should extend the class to implement the touch listeners, as shown in OpenGL training lesson,. This interface defines the methods required for drawing graphics in a. You must provide an implementation of this interface as a separate class and attach it to your instance using. The interface requires that you implement the following methods:.: The system calls this method once, when creating the. Use this method to perform actions that need to happen only once, such as setting OpenGL environment parameters or initializing OpenGL graphic objects.: The system calls this method on each redraw of the.
Use this method as the primary execution point for drawing (and re-drawing) graphic objects.: The system calls this method when the geometry changes, including changes in size of the or orientation of the device screen. For example, the system calls this method when the device changes from portrait to landscape orientation.
Use this method to respond to changes in the container. OpenGL ES packages Once you have established a container view for OpenGL ES using and, you can begin calling OpenGL APIs using the following classes:. OpenGL ES 1.0/1.1 API Packages. This package provides a static interface to the OpenGL ES 1.0/1.1 classes and better performance than the javax.microedition.khronos package interfaces. This package provides the standard implementation of OpenGL ES 1.0/1.1.
OpenGL ES 2.0 API Class. This package provides the interface to OpenGL ES 2.0 and is available starting with Android 2.2 (API level 8). OpenGL ES 3.0/3.1 API Packages. This package provides the interface to the OpenGL ES 3.0/3.1 classes.
Version 3.0 is available starting with Android 4.3 (API level 18). Version 3.1 is available starting with Android 5.0 (API level 21). If you want to start building an app with OpenGL ES right away, follow the class.
Declaring OpenGL requirements If your application uses OpenGL features that are not available on all devices, you must include these requirements in your file. Here are the most common OpenGL manifest declarations:.
OpenGL ES version requirements - If your application requires a specific version of OpenGL ES, you must declare that requirement by adding the following settings to your manifest as shown below. For OpenGL ES 2.0:
Note: The OpenGL ES 3.x API is backwards-compatible with the 2.0 API, which means you can be more flexible with your implementation of OpenGL ES in your application. By declaring the OpenGL ES 2.0 API as a requirement in your manifest, you can use that API version as a default, check for the availability of the 3.x API at run time and then use OpenGL ES 3.x features if the device supports it. For more information about checking the OpenGL ES version supported by a device, see. Texture compression requirements - If your application uses texture compression formats, you must declare the formats your application supports in your manifest file using. For more information about available texture compression formats, see. Declaring texture compression requirements in your manifest hides your application from users with devices that do not support at least one of your declared compression types. For more information on how Google Play filtering works for texture compressions, see the section of the documentation.
Mapping coordinates for drawn objects One of the basic problems in displaying graphics on Android devices is that their screens can vary in size and shape. OpenGL assumes a square, uniform coordinate system and, by default, happily draws those coordinates onto your typically non-square screen as if it is perfectly square. Default OpenGL coordinate system (left) mapped to a typical Android device screen (right). The illustration above shows the uniform coordinate system assumed for an OpenGL frame on the left, and how these coordinates actually map to a typical device screen in landscape orientation on the right.
![]() Oracle R12 Gl Implementation Guide
To solve this problem, you can apply OpenGL projection modes and camera views to transform coordinates so your graphic objects have the correct proportions on any display. In order to apply projection and camera views, you create a projection matrix and a camera view matrix and apply them to the OpenGL rendering pipeline. The projection matrix recalculates the coordinates of your graphics so that they map correctly to Android device screens. The camera view matrix creates a transformation that renders objects from a specific eye position.
Projection and camera view in OpenGL ES 1.0 In the ES 1.0 API, you apply projection and camera view by creating each matrix and then adding them to the OpenGL environment. Projection matrix - Create a projection matrix using the geometry of the device screen in order to recalculate object coordinates so they are drawn with correct proportions. The following example code demonstrates how to modify the method of a implementation to create a projection matrix based on the screen's aspect ratio and apply it to the OpenGL rendering environment. Kotlin var extensions = gl.glGetString(GL10.GLEXTENSIONS) Java String extensions = gl.glGetString(GL10.GLEXTENSIONS); Warning: The results of this call vary by device model! You must run this call on several target devices to determine what compression types are commonly supported. Review the output of this method to determine what OpenGL extensions are supported on the device. Android Extension Pack (AEP) The AEP ensures that your application supports a standardized set of OpenGL extensions above and beyond the core set described in the OpenGL 3.1 specification.
Packaging these extensions together encourages a consistent set of functionality across devices, while allowing developers to take full advantage of the latest crop of mobile GPU devices. The AEP also improves support for images, shader storage buffers, and atomic counters in fragment shaders. For your app to be able to use the AEP, the app's manifest must declare that the AEP is required.
In addition, the platform version must support it. Declare the AEP requirement in the manifest as follows: To verify that the platform version supports the AEP, use the method, passing in as the argument.
The following code snippet shows an example of how to do so. Kotlin var deviceSupportsAEP: Boolean = packageManager.hasSystemFeature(PackageManager.FEATUREOPENGLESEXTENSIONPACK) Java boolean deviceSupportsAEP = getPackageManager.hasSystemFeature (PackageManager.FEATUREOPENGLESEXTENSIONPACK); If the method returns true, AEP is supported. For more information about the AEP, visit its page at the. Checking the OpenGL ES version There are several versions of OpenGL ES available on Android devices. You can specify the minimum version of the API your application requires in your, but you may also want to take advantage of features in a newer API at the same time. For example, the OpenGL ES 3.0 API is backward-compatible with the 2.0 version of the API, so you may want to write your application so that it uses OpenGL ES 3.0 features, but falls back to the 2.0 API if the 3.0 API is not available.
Before using OpenGL ES features from a version higher than the minimum required in your application manifest, your application should check the version of the API available on the device. You can do this in one of two ways:. Attempt to create the higher-level OpenGL ES context ( ) and check the result.
Create a minimum-supported OpenGL ES context and check the version value. The following example code demonstrates how to check the available OpenGL ES version by creating an and checking the result. This example shows how to check for OpenGL ES 3.0 version.
Oracle R12 Training Material
Oracle Financial Services Accounting Hub Implementation Guide Browser version script Oracle Financial Services Accounting Hub Implementation Guide Release 12.1 Part Number E13420-05 Manual Subledger Journal Entries API Manual Subledger Journal Entries API Overview The manual subledger journal entries APIs enable implementers to create, update, delete, complete, and reverse manual subledger journal entries. This API creates one subledger journal entry header or line at a time; therefore, it is not intended to create subledger journal entries in bulk. See: Subledger Journal Entry Definition Overview, Oracle Subledger Accounting Implementation Guide Technical Overview A manual subledger journal entry is not associated with a transaction or document of a subledger application. When users create a manual subledger journal entry, it is created with the event class and event type Manual that is seeded automatically when the subledger application is registered. The figure below shows the create and complete manual journey entry process and is described in the following text. Create and Complete Manual Journey Entry The create and complete manual journal entry process includes the following steps:. Create journal entry header by calling CREATEJOURNAL ENTRYHEADER API.
Create journal entry line by calling CREATEJOURNALENTRYLINE API. Optionally, update the journal entry header by calling UPDATEJOURNALENTRYHEADER API. Optionally, update the journal entry line by calling UPDATEJOURNALENTRYLINE API. Optionally, delete the journal entry line by calling DELETEJOURNALENTRYLINE API. Complete the journal entry by calling COMPLETEJOURNALENTRY API. Optionally, reverse the journal entry by calling REVERSEJOURNALENTRY API.
Users can delete the journal entry at anytime by calling DELETEJOURNALENTRY API if the journal entry is not transferred to General Ledger. XLAJOURNALENTRIESPUBPKG This section includes the following topics:.
Global Constants The table below describes the constants that are defined in the package specifications.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |