![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
|
Previous | Next | Contents | Index | Glossary | Library |
Table 3 - 3 lists the Cost Management client extensions and their predefined template function files. The template function files are stored in the Cost Management admin/sql directory.
Standard Cost Client Extensions | Package Specification File | Package Body File |
---|---|---|
Accounting Entry Extension | CSTSCHKS.pls | CSTSCHKB.pls |
Account Generation Extension | CSTSCHKS.pls | CSTSCHKB.pls |
Average Cost Client Extensions | Package Specification File | Package Body File |
Transaction Cost Extension | CSTACHKS.pls | CSTACHKB.pls |
Accounting Entry Extension | CSTACHKS.pls | CSTACHKB.pls |
Account Generation Extension | CSTACHKS.pls | CSTACHKB.pls |
Table 3 - 3. Client Extensions (Page 1 of 1) |
Client extensions and functions can be used in either average costing organizations or both average and standard costing organizations as indicated below:
To define company specific rules using client extensions, you design and write these rules using PL/SQL functions; these functions are called during specific points in the normal processing flow of Cost Management.
These functions that you write are extensions rather than customizations because they are supported features within the product and are easily upgradable between releases of the product. Customizations are changes made to the base product which are not supported and are not easily upgraded.
Attention: You are responsible for the support and upgrade of the logic within the functions that you write, which may be impacted by changes between releases of the Oracle Applications.
Implementing Client Extensions
Determining Your Business Needs
Writing PL/SQL Procedures/Functions
Previous | Next | Contents | Index | Glossary | Library |