DBA Data[Home] [Help]

PACKAGE BODY: APPS.PA_CLIENT_EXTN_PRE_CAP_EVENT

Source


1 PACKAGE BODY PA_CLIENT_EXTN_PRE_CAP_EVENT AS
2 -- $Header: PACCXCBB.pls 115.2 2003/08/18 14:30:45 ajdas noship $
3 
4 PROCEDURE PRE_CAPITAL_EVENT(p_project_id    IN      NUMBER,
5                             p_event_period_name     IN      VARCHAR2,
6                             p_asset_date_through    IN      DATE,
7                             p_ei_date_through       IN      DATE DEFAULT NULL,
8                             x_return_status    OUT NOCOPY VARCHAR2,
9                             x_msg_data         OUT NOCOPY VARCHAR2) IS
10 
11 BEGIN
12  /* This client extension contains no default code, but can be used by customers
13     to perform logic prior to Capital Event creation.  One example of such logic
14     would be to automatically create Project Assets (or Retirement Adjustment Assets)
15     based on transactional data, such as Inventory Issues or Supplier Invoices
16     against a blanket project.
17 
18     When creating Project Assets, be sure to use the CREATE_ASSETS public API to ensure
19     validation on asset and asset assignment data. Standard business rules surrounding
20     Asset Assignments must be adhered to, such as the concept that asset assignments cannot
21     simultaneously exist as multiple Grouping Levels.  For example, if one asset is assigned
22     to the project, another asset cannot be assigned to a Top Task.  Or if one asset is
23     assigned to a Top Task, another asset cannot be assigned to a child task beneath that
24     Top Task, or vice versa.
25 
26     The p_event_period_name, p_asset_date_through, and p_ei_date_through parameters are
27     the run-time parameters of the PRC: Create Periodic Capital Events program.  These are
28     included here so that if the customer chooses to create assets as part of this client
29     extension, he can use these parameters to ensure that the newly created assets will or
30     will not be picked up by the Event creation program.
31 
32     The mandatory OUT Parameter x_return_status indicates the return status of the API.
33     The following values are valid:
34         'S' for Success
35         'E' for Error
36         'U' for Unexpected Error
37 
38  */
39 
40     x_return_status := 'S';
41     x_msg_data := NULL;
42 
43     RETURN;
44 
45 EXCEPTION
46   WHEN OTHERS THEN
47       x_return_status := 'U';
48       x_msg_data := SQLCODE||' '||SQLERRM;
49       fnd_msg_pub.add_exc_msg(p_pkg_name     => 'PA_CLIENT_EXTN_PRE_CAP_EVENT',
50                               p_procedure_name => 'PRE_CAPITAL_EVENT',
51                               p_error_text => SUBSTRB(x_msg_data,1,240));
52       RAISE;
53 END;
54 
55 END;