Oracle Project Costing (PJC)

This chapter covers the following topics:

Add and Assign Asset to Capital Project through PLSQL APIs

The objective of the current flow is to create a project asset and assign the asset to a specific task within the capital project.

Flow Type

PLSQL

Technical Name

PJC_Add_Assign_Asset_PLSQL

Prerequisites

The following are the prerequisites for executing the flows:

Profile Options

The following profile options must be set:

Profile Value
GL Ledger Name Vision Project Mfg (EUR)
MO: Operating Unit Vision Project Mfg
MO: Security Profile Vision Corporation

Predefined Data

The following predefined data must be used:

Entity Field Name Field Value
FND_GLOB_APPS_INITIALIZE & PA_SET_GLOBAL_INFO User Id 1013837
  Resp Id 55395
  Resp Appl ID 275
PA_SET_GLOBAL_INFO Operating Unit ID 600

Setup Data

The following data must be set up:

Entity Field Name Field Value
PA_PROJECT_ASSETS_PUB_ADD_PROJECT_ASSET_Main PA Project ID 6364
  Location Id 824
  Assigned To Person Id 53
  Asset Category Id 17
  Book Type Code PROJ MFG CORP2
  Depreciation Expense Ccid 470003
PA_PROJECT_ASSETS_PUB_ADD_ASSET_ASSIGNMENT_Main PA Project ID 6364
  PA Task ID 211219

Description of the Scenarios in the Flow (Project Costing)

Following are the details of the scenarios in the flow:

Scenario Objective Artifact Method Component Set Main Component
ADD_ASSET This scenario creates a project asset. PA_PROJECT_ASSETS_PUB.ADD_PROJECT_ASSET - PA_PROJECT_ASSETS_PUB_ADD_PROJECT_ASSET_Main
ASSIGN_ASSET This scenario assigns the asset created above to a specific task within the same project PA_PROJECT_ASSETS_PUB.ADD_ASSET_ASSIGNMENT - PA_PROJECT_ASSETS_PUB_ADD_ASSET_ASSIGNMENT_Main

Create Deductions through PLSQL APIs

The objective of the current flow is to create project deduction with multiple deduction lines. The flow also approves the deduction created and verifies the debit memo which gets auto-created in Oracle Payables.

Flow Type

Hybrid

Technical Name

PJC_Create_Deductions_PLSQL

Prerequisites

The following are the prerequisites for executing the flows:

Profile Options

The following profile options must be set:

Profile Value
GL Ledger Name Vision Project Mfg (EUR)
MO: Operating Unit Vision Project Mfg
MO: Security Profile Vision Corporation

Predefined Data

The following predefined data must be used:

Entity Field Name Field Value
SELECT User_Name APLQA
  Responsibility_Key PROJECTS_PROJECT_MFG
  Product_Code PA
PA_SET_GLOBAL_INFO Operating Unit ID 600
Navigate_OAF Resp Projects SU, Vision Project Mfg (EUR)
  Resp Payables, Vision Project Mfg (EUR)

Setup Data

The following data must be set up:

Entity Field Name Field Value
PA_DEDUCTIONS_PUB_CREATE_DEDUCTION_HDR_Main Project ID 6362
  Vendor ID 7
  Vendor Site ID 505
  Currency Code EUR
  Org ID 600
PA_DEDUCTIONS_PUB_CREATE_DEDUCTION_TXN_Main Task ID 211209
  Task ID 211210
  Expenditure Type Consulting
  Expenditure Org ID 600

Description of the Scenarios in the Flow (Project Costing)

Following are the details of the scenarios in the flow:

Scenario Objective Artifact Method Component Set Main Component
Get_Variables     - SELECT
Create_Deductions This scenario creates the project deduction request header record PA_DEDUCTIONS_PUB.CREATE_DEDUCTION_HDR - PA_DEDUCTIONS_PUB_CREATE_DEDUCTION_HDR_Main
Create_Deduction_Transactions This scenario creates two deduction transaction lines for the above header record. PA_DEDUCTIONS_PUB.CREATE_DEDUCTION_TXN - PA_DEDUCTIONS_PUB_CREATE_DEDUCTION_TXN_Main
Get_Deduction_Num     - Get_DEDUCTION_REQ_NUM
Verify_Debit_Memo This scenario created with UI based components to verify the deduction and deduction lines and submit the deduction created by the above PLSQL. The scenario also verified the debit memo which gets auto-created in Oracle Payables.   - UI Components: FIND_DEDUCTION VRF_DEDUCTION_HDR VRF_DEDUCTION_TRANS VRF_DEDUCTION_TRANS SUB_DEDUCTION VRF_DEDUCTION_HDR Verify_Invoice_WB

PJC Transaction Import through Open Interface

The objective of the current flow is to import different types of transactions from external systems into Oracle Projects using the Projects Transaction Open Interface.

Flow Type

Hybrid

Technical Name

PJC_Transaction_Import_OI

Prerequisites

The following are the prerequisites for executing the flows:

Profile Options

The following profile options must be set:

Profile Value
GL Ledger Name Vision Project Mfg (EUR)
MO: Operating Unit Vision Project Mfg
MO: Security Profile Vision Corporation

Predefined Data

The following predefined data must be used:

Entity Field Name Field Value
SELECT User_Name APLQA
  Responsibility_Key PROJECTS_PROJECT_MFG
  Product_Code PA
PA_SET_GLOBAL_INFO Operating Unit ID 600

Setup Data

The following data must be set up:

Entity Field Name Field Value
PA_TRANSACTION_INTERFACE_ALL TRANSACTION_SOURCE PJC_TS1
  TRANSACTION_SOURCE PJC_TS2
  TRANSACTION_SOURCE PJC_TS3
  TRANSACTION_SOURCE PJC_TS4
  TRANSACTION_SOURCE PJC_TS5
  ORGANIZATION_NAME Vision Project Mfg
  PROJECT_NUMBER Proj-Ind-Accr-None
  TASK_NUMBER 1
  EXPENDITURE_TYPE Consulting
  ORG_ID 600
  DR_CODE_COMBINATION_ID 35100
  CR_CODE_COMBINATION_ID 75526
  CREATED_BY 1013837
  PERSON_BUSINESS_GROUP_NAME Vision Corporation

Description of the Scenarios in the Flow (Project Costing)

Following are the details of the scenarios in the flow:

Scenario Objective Artifact Method Component Set Main Component
Get_Variables     - SELECT
Import_Transactions This scenario e imports the transactions from open interface to Projects PA_TRANSACTION_INTERFACE_ALL - PRC_Transaction_Import_PAXTRTRX