Oracle ERP 11i_R12 Functional_Technical Materials_ API Integration

8/1/13

Or acl e ERP 11i /R 12 Functi onal /Technical Mater i al s: API Integ r ati on

Oracle ERP 11i/R12 Functional/Technical Materials

Orcac le R12

O2C Cy C y c le

P 2P C y c le

A pps Installation

Apps Techn Technic al

ERP Ques tio ns

V ide o Tutoria ls

Search This Blog

Showing posts wit h label API Integration. Integration. Show all posts

earch

How to change the Default Value for Segment Qua Qualifier lifier - Account Type T hu hur sd sd ay ay , J un une 27 27, 20 20 13 13

Oracle Applications & Modules

P os os te te d b y Ja ga ga de de es es an an M 0 comments

While Whil e Defining Values for Natural Account segment in General Ledger. We observe that

Account Payables Account Acc ount Receivable s

Segment Seg ment Qualifier gets default value as "Expense". Here the requ requirement irement is to change change that

Advanced Supply Chain Planning (ASCP)

default defa ult value to "Assets".

AIM AIM Methodology Alerts in Oracle API Integration Apps Installation Apps Technical Basic Accounting Beginner Bills Bil ls of Mate rial Cash Management Configure-to-Order ERP Questions Error Solution Finance Fixed Fix ed Assets FSG General Ledger HRMS Implementation Implementation Impl ementation in production Interview FAQ Inventory Key Flexfields Legal Entity Configurator Metalink MOAC

Solution:

O2C Cycle OBIEE

For changing the default value. Go to Oracle Application Developer responsibility.

OPM Oracle 11i

Navigation: Flexfield Navigation: Flexfield > Key > Register.

Oracle Approvals Management Oracle Apps

Query the Accounting Flexfield and Click on Qualifier Button

Oracle Apps r12 User Guides Oracle Oracl e Asse ts Oracle Oracl e Cos t Management Oracle CRM Oracle E-Business Suite Oracle E-Business Tax Oracle Fusion Oracle GRC Oracle iExpense Oracle Oracl e iExpenses Oracle iProcurement Oracle iStore Oracle JDeveloper

or acleer pfuncti onal .bl og spot.i n/sear ch/l abel /API Integ r ati on

1/15

8/1/13

Oracle ERP 11i/R12 Functional/Technical Materials: API Integration Oracle Manufacturing Oracle Navigation Oracle OAF Oracle Payments Oracle Payroll Oracle Personalizations Oracle P ricing Oracle Projects Oracle R12 Oracle Workflow Order Management P2P Cycle Purchasing Purchasing Order Release R12 SCM SLA Subledger Accounting Supply Chain Management System Administrator Video Tutorials

After Clicking on Qualifier Button. Query the Natural Account Seg ment for which value to be default. After querying the Natural Account you will find the Default Value column with "Expense" a s shown in below screenshot.

Warehouse Management XML Publisher

Blog Archive ▼ 2013 (44) ▼ June (44)

New and Cha nged Features in Oracle Financials of 1... RXi Sales register completes in warning with Error... AP/AR Netting for different currencies Error: Encumbrance Accounting h as been turned off Companies providing Oracle Apps and Oracle BI Cons ... Oracle E-Busines s Tax: Regime to Rate Flow in Orac... In Oracle Release12, there has be en some ve ry sign... Business Units and Shared Service model in Fusion ... Invoice Image Processing Architecture in Fusion Pa... Fusion Applications Security Oracle eBS R12 customers can coexist with Fusion ...

Change the Value from "Expense" to "Asset". Save the Work and close the forms

What to Convert in GL: Balance or Transaction Deta... New Fe atures in Approving Expense Reports in Oracl... Payables Hold Release Workflow Oracle Projects – Part 1 Oracle Projects – Part 2 Exploring Oracle Self Billing (Payment on Receipt)... Customer Refund in Receivables Business case - Customer on Credit Hold Conversion (Data Migration) of Invoices in Receiva... Is process re-engineering required before you star... What it takes to be come a successful ERP Consultan... How to modify an a ccount logic in existing Subledg... Oracle Assets r12 Summary

oracleerpfunctional.blogspot.in/search/label/API Integration

2/15

8/1/13

Oracle ERP 11i/R12 Functional/Technical Materials: API Integration Oracle Accounts Receivable r12 Summary Oracle Ca sh Manage ment r12 Summary Oracle Sub Le dger Accounting (SLA) r12 Summary Oracle Sub Le dger Accounting (SLA) r12 Summary R12 Subledger Accounting Part 1 How to change the Default Value for Segment Q ualif... How to change the Default Value for Segment Q ualif... Unable to access Form Personalization Page Form Personalization - All data entered s hould app... FRM-92050: Failed to connect to the Server:/forms/... How to Run AP List for Oracle PayablesHow to Run A... Form Personalization - Changing Prompt in the form...

For Checking the default value. Go to General Ledger Responsibility. Navigate to Setup > Financial > Flexfield > Key > Value. Enter a new Value and in Segment Qualifier you observe Account type as "Asset" as de fault value.

Subledger Accounting & Methods of Create Accountin... Oracle R12 - Erp Financials Study Mate rial - (AR, ... Key Flexfields Is process re-engineering required before you star... How to modify an a ccount logic in existing Subledg... Oracle Subledger Accounting Method Concept Expla... Assets Overview of Oracle Accounts Payables (AP) Module ► 2012 (620)

Followers Join this site w ith Google Friend Connect

Membe rs (17)

Already a member? Sign in

Procure To Pay Cycle in Oracle Apps R12 (P2P Cycle)

You might also like:

Procure To Pay Cycle in Oracle Apps R12 (P2P Cycle) Here in this post, I tried to explain the steps involved in Procure to Pay Cycle. Thi...

Implementing the Chart of Accounts for Oracle General Ledger Oracle Accounts Receivable r12 Summary How to change the Default Value for Segment Qualifier - Allow Budgeting Oracle Projects – Part 1 Customer Refund in Receivables LinkWithin

Account Payables, Account Receivables, API Integration, General Ledger, Oracle Apps r12 User Guides, Oracle R12

Oracle Property Manager Conversion Thursday, September 27, 2012

Posted by Jagadeesan M 0 comments


AP Invoice Approval workflow setup and usage Organizations might prefer to set AP invoices to be a pproved through an approval process before the invoice is paid off. This is us eful fr... Oracle General Ledger (OGL) Oracle General Ledge r (OGL) Oracle Financial comprises of the following

3/15

8/1/13

Oracle ERP 11i/R12 Functional/Technical Materials: API Integration

Oracle Property Manager Conversion Oracle Property Manager provides an effective tool to manage major real estate tasks, including lease administration and off ice space allocat ion. It also produces reports in a variety of formats that present records, depending upon the business needs. Property Manager automatically generates payment or billing sc hedules for eac h lease you define, normalizing the payment or billing stream in accordance with GAAP (Generally Accepted Accounting Principles). Property manager helps to maintain following information related to the business • Payment terms • Billing terms • Options • Key contacts for vendors or service providers • Landlord services • Insurance requirements It is integrated with ot her Oracle applicat ions like Payables and billings generated c an be exported in Payables Application. Conversion approach

core Finance Modules: 1) General Ledger 2) Accounts Payable ...

Oracle Internet Expenses /iExpense setup Oracle Internet expenses is an iModule of Oracle. This module is used to allow e mployees of an organization to enter their expenses which a... SQL queries to ge t Requisition, PO and PO Receipt details I had to provide data to auditors on the Internal & Purchase Requisitions created by users Purchase O rders created for the requisition...

Visitor

Live Traffic Feed

During this Conversion the approach followed was st andard three Stage approach 1. Insertion of Data into staging table from legacy Tables 2. Validation of Data 3. Insertion of Data into Oracle tables using Standard Insert Packages. Creation of Sc hedules and Items The conversion was carried out for creation of Prime and Sub leases with lease status as ‘Act ive’ and approval stat us as ‘Final’. Also it was required to generate t he Payment Schedule and Items for the leases. Different Programs with similar conversion approach were used for conversion of Sublease and Prime Leases as different details were required t o be populated. The Conversion was done to populate following details in the leases 1. Lease Header 2. Lease Details 3. Milestones 4. Party Roles 5. Contacts 6. Rights and Obligations 7. Options 8. Payments/Billings and its Account Distribution 9. Notes Following is the detailed approach for t he Property Manager Conversion. 1. Insertion: First the Data from legacy system was put into the Staging Tables. Different Tables were used to populate different details of the Leases. The different staging tables that were created as a part of the Conversion Process are a) Header staging table: Data for creating Lease Header and Lease Details was stored in this table. b) Payments staging table: Data for c reating Payments/Billings was stored in t his table. T he Payments/Billings acc ount Distribution and Payments Milestones was also created using the data from this table. c) Other Charges staging table: The Data for creating other charges payment streams along with the account Distribution was stored in this table. d) Comments staging table: Data f or Lease not es Creation. e) Options staging table: Data for Creation of Renewal and Original terms Option along with Options Milestones. f) Lease Contacts staging table 2. Columns such as Process status, Error flag and Error description were created in the staging table. The value in the column Process status indicates the stage at which data is being processed by the Conversion program. Following are oracleerpfunctional.blogspot.in/search/label/API Integration

4/15

8/1/13


the Proces s stat us values that were followed during this conve rsion Process a. ‘1’ – Insertion of Data into St aging Tables b. ‘2’ – Validation c. ‘3’ – API insertion into t he Base Tables d. ‘4’ - Completion of Processing The columns process stat us, error flag and error desc ription were updated whenever the errors were encountered for the record at different stages of processing. 3. Validation: Once the Data was inserted into the Staging tables the process status was updated to ‘1’. Various validations such as Business specific validations, Mandatory values, etc ... were performed on the Data. For validation only those Header records and c orresponding Payments, Milestones, Options and Notes records which have error flag as ‘N’ were picked and processed. Then the next header and corresponding records from other staging tables were picked and validated. If the record is validated successfully the process status was updated to ‘2’. Incase the record failed validation the process status was updated to ‘2’, also the error flag and error description columns for the record were updated for the specific validation failure Message. 4. API’S insertion into Base T ables: Those Lease header records which are validated successfully were picked for further processing. Corresponding to Header record, Payments, Milestones, Opt ions and Notes records which have error flag as ‘N’ were picked and using the Standard Insert Packages the data was inserted into the Oracle Base tables. Incase of any errors the insertion for that particular Lease record was roll back and then record was updated as proces s st atus ‘3’ along with error flag and error description. For all successfully inserted records the process status was updates as ‘4’. 5. Schedules and Items: Once the Lease record was created successfully the ‘Schedules and Items’ program was submitted with lease context as 'ABS' to finalize the Lease. This Program finalizes the Lease and creates the Payment Schedules and items for that lease. Setups for Property Manager Conversion

Some of the important set ups required for this c onversion are 1) Define t he Lookup Codes: According to the Specific Business requirement various custom lookup code and meaning should be defined in the Standard Lookups. Responsibility: Property Manager User Setup>Options>Lookups

Live Traffic Feed

A visitor from Chennai, Tamil Nadu viewed "Oracle ERP 11i/R12 Functional/Technical Materials: Frequently asked question to Techno-Functional Consultant" 12 mins ago A visitor from Ada, Michigan left "Oracle ERP 11i/R12 Functional/Technical Materials: R12 : Setting up for AP/AR Netting" via 1.b p.blogspot.com 12 mins ago A visitor from Delhi viewed "Oracle ERP 11i/R12 Functional/Technical Materials: How to Merge the Tow Supplier Documents" 13 mins ago A visitor from Bangalore, Karnataka viewed "Oracle ERP 11i/R12 Functional/Technical Materials: Oracle iExpense Setups and Common issues" 13 mins ago A visitor from Edison, New Jersey viewed "Oracle ERP 11i/R12 Functional/Technical Materials: Oracle EBS R12 Training - HRMS Create New Employee" 14 mins ago A visitor from Bangalore, Karnataka viewed "Oracle ERP 11i/R12 Functional/Technical Materials: FSG Basics" 15 mins ago A visitor from Ada, Michigan viewed "Oracle ERP 11i/R12 Functional/Technical Materials: R12 : Setting up for AP/AR Netting" 15 mins ago

Some of the Important Lookups that needs to be setup are a) PN_LEASE_CLASS: This lookups store the Classes for Leases such as Direct, Sub lease, etc… b) PN_MILESTONES_TYPE: Lookup c ode for Milestones t ype is def ined in this lookup. c) PN_LEASE_OPTION_TYPE: This lookup stores the Option types that can be created for the Lease. d) PN_NOTE_TYPE: This lookup store the different Note types that can be created for the Lease. e) PN_PAYMENT_PURPOSE_TYPE: Define any cust om Payment types in this Lookup. f) PN_PAYMENT_TERM_TYPE: Define any custom Payment term types in this Lookup. g) PN_TENANCY_USAGE_TYPE: This Lookup is used to define any custom Usage type for the Locations in the Lease. h) PN_RIGHTS_TYPE: oracleerpfunctional.blogspot.in/search/label/API Integration

A visitor from India viewed "Oracle ERP 11i/R12 Functional/Technical Materials: Blogger Templates by Blog Forum

5/15

8/1/13

Oracle ERP 11i/R12 Functional/Technical Materials: API Integration Define any cust om Right types that will be creat ed for the Leases. 2) Define Locations: Locations for which lease is to be created needs to be defined in this screen. The name of Locat ion was defined as Profit c enter number (Store Number) for the store and class of Location was defined as ‘Store’. The Tenure needs to be defined as ‘Leased’. Address of the Store was defined as the address of the Location. The Start and End date of the locations defines the period for which the location will be occupied during the lease agreement. Responsibility: Property Manager User Assignments>Define Locations

3) Define Contacts: The Contacts for each company was defined in this screen. A single company can have number of roles and each role can have different contact person all these data can be entered here. The details such as Contact Roles, Site address, Te lephone number and Contac t names we re defined. Responsibility: Property Manager User Agents>Contacts

APIs used for Conversion:

Standard Insert packages were used for the conversion. The details of the API’S used are given below in the sequence which they were used in the Conversion Program. 1. Lease Header and Details API This API creates the Lease Header and Details. pn_leases_pkg.insert_row Tables populated: PN_LEASES PN_LEASE_DETAILS PN_LEASE_CHANGES

Parameters for API: pn_leases_pkg.insert_row ( /*Output Parameter for Row Id*/ x_rowid

=> v_c hr_rowid

/*Output Parameter f or lease Id*/ ,x_leas e_id => v_num_lease _id /*Output Parameter for lease change Id*/ ,x_lease_c hange_id => v_num_lease_c h_id oracleerpfunctional.blogspot.in/search/label/API Integration

6/15

8/1/13

Oracle ERP 11i/R12 Functional/Technical Materials: API Integration /*Output parameter for Lease Detail id*/ ,x_lease_det ail_id

=> v_num_det ail_id

/* Input t he Lease Name*/ ,x_name

=> 'Test1'

/* Input Lease number*/ ,x_lease_num ,x_parent_lease_id

=> v_c hr_lease_num => NULL

/*Input lease t ype and c lass code set in the above lookups*/ ,x_lease_type_c ode => v_chr_lease_code ,x_lease_c lass_code => v_chr_lease_class /*Input the Proration rule Value*/ ,x_payment _term_proration_rule ,x_abstrac ted_by_user

=> 365 => g_num_user_id

/*Input approval status as ‘DRAFT’. Initially lease will be c reated in ‘DRAFT’ stat us and t he Sc hedules and Items Program will finalize t he Lease* / ,x_stat us => 'D' --DRAFT ,x_lease_stat us => ‘ACT’ –-Ac tive Status /*WHO Columns*/ ,x_creation_date ,x_creat ed_by ,x_last_updat e_date ,x_last_updat ed_by ,x_last _updat e_login ,x_responsible_user ,x_expense_ac count_id ,x_acc rual_acc ount_id ,x_receivable_ac count_id ,x_term_template_id

=> g_dte_sysdate => g_num_user_id => g_dte_sy sdat e => g_num_user_id => g_num_login_id => g_num_user_id => NULL => NULL => NULL => NULL

/*Input Commencement, T ermination and Exec ution Date for Lease*/ ,x_lease_c ommenc ement_date => v_dte_ls_com_dte ,x_lease_termination_date => v_dte _ls_ter_dte ,x_lease_execut ion_date => c_xshs_rec .lease_date /*Pass t he values of any Att ribute Columns*/ ,x_att ribute_c ate gory => NULL ,x_att ribute1 => v_dte _begin_date ,x_att ribute2 => v_dte _at_end_dat e ,x_att ribute3 => NULL ,x_at tribute 4 => NULL ,x_att ribute5 => NULL ,x_att ribute6 => c_xshs_rec.rent_deposit ,x_att ribute7 => v_chr_auto_lye ,x_att ribute8 => v_chr_rent_invoice ,x_att ribute9 => v_chr_spl_terms ,x_att ribute10 => corp_number ,x_att ribute11 => v_c hr_escrow ,x_at tribute 12 => NULL ,x_at tribute 13 => NULL ,x_at tribute 14 => NULL ,x_at tribute 15 => NULL ,x_org_id

=> g_num_org_id

/*Input Loc ation Id from PN_LOCATIONS for t he Profit Cente r (Store Number) and Customer Id for which the is to be created*/ ,x_locat ion_id => v_num_locat ion_id ,x_customer_id => v_num_cus tomer_id ,x_grouping_rule_id => NULL ); This API returns the Lease Id, Lease details Id and Lease change Id as the output parameters. 2. Locations API’s: oracleerpfunctional.blogspot.in/search/label/API Integration

7/15

8/1/13

Oracle ERP 11i/R12 Functional/Technical Materials: API Integration This API populates the Location Details for the Lease. This Location was created for the Profit Center (Store) which is defined as Location in PN_LOCATIONS. pn_tenancies_pkg.insert_row Tables populated: PN_TENANCIES

Parameters for API: pn_tenancies_pkg.insert_row ( /*Ouput row id*/ x_rowid /*Output Te nancy Id*/ ,x_tenanc y_id /*Input Locat ion Id for Profit Cent er*/ ,x_locat ion_id

=> v_c hr_row_id1

=> v_num_tenancy_id

=> v_num_locat ion_id

/*Input the Lease Id and Lease Change Id from the Lease Header API*/ ,x_lease_id => v_num_lease_id ,x_lease_c hange_id => v_num_lease_c h_id /*Input Property Class Lookup Code*/ ,x_tenanc y_usage_lookup_c ode ,x_primary_f lag

=> property_c lass => 'N'

/*Inpute t he Lease Commence ment and T ermination Date* / ,x_estimated_oc cupanc y_date => v_dte_ls_com_dte ,x_expiration_date => v_dte _ls_ter_dte

,x_occ upanc y_date => NULL ,x_assignable_flag => NULL ,x_subleaseable_f lag => NULL ,x_tenants_proportionate_share => 100 ,x_status => 'A' – Act ive Stat us /*Input At tribute Values*/ ,x_att ribute_c ate gory => NULL ,x_at tribut e1 => NULL ,x_at tribut e2 => NULL ,x_at tribut e3 => NULL ,x_at tribut e4 => NULL ,x_at tribut e5 => NULL ,x_at tribut e6 => NULL ,x_at tribut e7 => NULL ,x_att ribute8 => NULL ,x_att ribute9 => NULL ,x_at tribut e10 => NULL ,x_at tribut e11 => NULL ,x_attribut e12 => NULL ,x_attribut e13 => NULL ,x_attribut e14 => NULL ,x_attribut e15 => NULL /*WHO columns*/ ,x_creation_date => g_dte_sysdate ,x_creat ed_by => g_num_user_id ,x_last_updat e_date => g_dte_sysdat e ,x_last_updat ed_by => g_num_user_id ,x_last _updat e_login => g_num_login_id ,x_org_id => g_num_org_id /*T his is the output parameter whic h gives the warning Message if t he Location is used by some other lease with in same tenure. */ ,x_tenancy_ovelap_wrn => v_chr_tenancy _wrn ,x_recov ery_ty pe_c ode => NULL ,x_recov ery_spac e_st d_code => NULL ,x_fin_oblig_end_date => NULL ,x_c ust omer_id => NULL ,x_customer_site_use_id => NULL ,x_lease_rentable_area => NULL ,x_leas e_usable_area => NULL ,x_lease_assignable_area => NULL ,x_lease_load_fac tor => NULL ,x_locat ion_rentable_area => NULL


8/15

8/1/13


,x_locat ion_usable_area => NULL ,x_locat ion_assignable_area => NULL ,x_locat ion_load_factor => NULL ); This API returns tenancy id for the location. 3. Options API’s: This API’s was used to create the various Options such as Renewal, Original terms for the Lease. pn_options_pkg.insert_row Tables populated: PN_OPTIONS

Parameters for API: /*Creat ion of Lease Orignal Terms for Header*/ pn_options_pkg.insert_row( /*Output parameter Row id*/ x_rowid => v_c hr_row_id2 /*Output parameters Option Id and Option Number*/ ,x_opt ion_id => v_num_option_id ,x_option_num => v_c hr_option_num /*Input parameter Lease Id and Lease Change Id*/ ,x_lease_id => v_num_lease _id ,x_lease_c hange_id => v_num_lease_c h_id /*Input Option type Code from ‘PN_LEASE_OPTION_TYPE’ */ ,x_option_type_code => v_chr_option_type_c ode

/*St art date and End Date* / ,x_start_date => c_xshs_rec.begin_date ,x_expiration_dat e => c_xshs_rec.end_date1 ,x_opt ion_size => NULL ,x_uom_code => NULL /*Input Option stat us lookup from ‘PN_OPTION_STAT US_TYPE’*/ ,x_option_status_lookup_code => v_chr_option_stat us_code /*Input att ributes*/ ,x_att ribute_c ate gory => NULL ,x_att ribute1 => NULL ,x_att ribute2 => NULL ,x_att ribute3 => NULL ,x_att ribute4 => NULL ,x_att ribute5 => NULL ,x_att ribute6 => NULL ,x_att ribute7 => NULL ,x_att ribute8 => NULL ,x_att ribute9 => NULL ,x_at tribut e10 => NULL ,x_at tribut e11 => NULL ,x_at tribut e12 => NULL ,x_at tribut e13 => NULL ,x_at tribut e14 => NULL ,x_at tribut e15 => NULL /*WHO columns*/ ,x_creation_date => g_dte_sysdate ,x_creat ed_by => g_num_user_id ,x_last_updat e_date => g_dte_sysdat e ,x_last_updat ed_by => g_num_user_id ,x_last _updat e_login => g_num_login_id ,x_option_exer_start_dat e => NULL ,x_option_exer_end_date => NULL ,x_option_ac tion_dat e => NULL ,x_option_c ost => NULL ,x_option_area_c hange => NULL ,x_option_reference => NULL ,x_option_not ice_reqd => NULL ,x_opt ion_c omment s => NULL ,x_org_id => g_num_org_id ); This API returns the Option id and Option Number for the lease. 4. Rights API’s: This API’s was used to create the type of Rights such as Buyout, Purchase, etc... for the Lease. PN_RIGHTS_PKG.Insert_Row


9/15

8/1/13

Oracle ERP 11i/R12 Functional/Technical Materials: API Integration Tables populated: PN_RIGHTS

Parameters for API: PN_RIGHTS_PKG.Insert_Row ( /*Output Parameter for Row id*/ x_rowid => v_c hr_row_id8, /*Out put Parameter for Right Id and Right Number*/ x_right_id => v_num_right_id, x_right_num => v_num_right_num, /*Input Parameter f or Lease and Lease Change ID for the Lease Header*/ x_lease _id => v_num_lease _id, x_lease_change_id => v_num_lease_c h_id, /*Input Parameter for Right type code from ‘PN_RIGHTS-T YPE*/ x_right_ty pe_c ode => v_c hr_right_type_c ode, /*Input Parameter for Right St atus c ode*/ x_right_st atus_code x_right_refe rence =>

=> NULL,

'N',

/*Input Lease Commencement Date and T ermination Date as st art and End date for the lease*/ x_start_date => v_dte _ls_com_dte, x_expiration_date => v_dte _ls_ter_dte,

x_right_c omment s x_attribute_c ate gory x_att ribute 1 x_att ribute 2 x_att ribute 3 x_att ribute 4 x_att ribute 5 x_att ribute 6 x_att ribute 7 x_att ribute 8 x_att ribute 9 x_attribut e10 x_attribut e11 x_attribut e12 x_attribut e13 x_attribut e14 x_attribut e15

=> => => => => => => => => => => => => => =>

=> NULL, => NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL,

/*WHO Columns*/ x_creation_date => g_dte_sysdate, x_creat ed_by => g_num_user_id, x_last_updat e_date => g_dte_sy sdat e, x_last _updated_by => g_num_user_id, x_last _updat e_login => g_num_login_id, x_org_id => g_num_org_id ); This API returns the Right Id and Right Number for the Lease. 5. Contacts API’s: This API’s was used to create the type of Rights such as Buyout, Purchase, etc... for the Lease. PN_CONTACT_ASSIGNMENTS_PKG.Insert_Row Tables populated: PN_CONTACT_ASSIGNMENTS

Parameters for API: PN_CONTACT_ASSIGNMENTS_PKG.Insert_Row( /*Output Parameter for Row id*/ x_rowid => v_c hr_row_id7, /*Ouput parameter f or Contact assignment Id*/ x_cont ac t_ass ignment_id => v_num_cnt _assig_id, /*WHO Columns*/ x_last _update_date => g_dte_sysdat e, x_last_updat ed_by => g_num_user_id, x_creat ion_date => g_dte_sy sdat e, x_created_by => g_num_user_id, x_last_updat e_login => g_num_login_id, /*Input t he Company Id and Company Site Id for t he Contac t def ined in the Contacts screen*/ oracleerpfunctional.blogspot.in/search/label/API Integration

10/15

8/1/13


x_company_id => v_num_company_id, x_company_site_id => v_num_comp_site_id, /*Input lease Header Id and change Id*/ x_lease _id => v_num_lease_id, x_lease _change_id => v_num_lease_c h_id, x_location_id => NULL, x_stat us => 'A', -- Act ive Stat us /*At tribute Columns*/ x_attribute_c ate gory => NULL, x_att ribute 1 => NULL, x_att ribute 2 => NULL, x_att ribute 3 => NULL, x_att ribute 4 => NULL, x_att ribute 5 => NULL, x_att ribute 6 => NULL, x_att ribute 7 => NULL, x_att ribute 8 => NULL, x_att ribute 9 => NULL, x_att ribute 10 => NULL, x_att ribute 11 => NULL, x_att ribute 12 => NULL, x_att ribute 13 => NULL, x_att ribute 14 => NULL, x_att ribute 15 => NULL, x_org_id => g_num_org_id ); This API returns the Contact assignment Id for the Lease as output parameter. 6. Payme nt/Billings and Account Distribution API’s: This API’s was used t o c reate t he Billing streams for Sublease and Payment streams for Prime Lease. In order to create the Account Distribution for the Payment stream pn_distributions_pkg.insert_row was used. First payment streams were created for each lease by calling the Payments API. Then the Account distribution was created for the Payment stream calling the Distribution API for each account entry. Payment streams were created for Regular and Other Charges Payments. pnt_payment_terms_pkg.insert_row Tables populated: PN_PAYMENT_TERMS

Parameters for API: pnt_payment_terms_pkg.insert_row ( /*Output parameter f or Row Id*/ x_rowid => v_c hr_row_id6 /*Output Parameter f or Payment T erm Id*/ ,x_payment _term_id => v_num_payment _te rm_id /*Input Billing Purpose Code and t he Billing term*/ ,x_payment_purpose_c ode => v_c hr_billing_purpose ,x_payment_term_type_code => v_c hr_billing_term /*Input t he frequency as Montly, One t ime, et c. .. * / ,x_frequenc y_c ode => v_chr_billing_frequency /*Input parameter Lease Id and lease Change Id*/ ,x_leas e_id => v_num_lease_id ,x_lease_c hange_id => v_num_lease_c h_id /*Input St art and End date f or the Payment Stream*/ ,x_start _date => v_dte _mon_start_dat e ,x_end_date => v_dte _mon_end_date ,x_vendor_id => NULL ,x_vendor_site_id => NULL ,x_c ust omer_id => v_num_cust omer_id ,x_customer_site_use_id => v_num_site_use_id ,x_target _date => NULL /*Input t he Amount for Payment Stream*/ ,x_act ual_amount => c_xsos_rec.payment_amount ,x_estimated_amount => NULL /*Input Set of Books and Currency*/ ,x_set_of_books_id => g_num_set _books_id ,x_currency _code => g_chr_currency ,x_rate => 1 /*Input Normalize flag value as ‘Y ’ if the payment s tream needs t o be Normalized*/ ,x_normalize =>’Y’ ,x_loc at ion_id => NULL /*Input Spec ial terms and Customer ship to Site*/ oracleerpfunctional.blogspot.in/search/label/API Integration

11/15

8/1/13

Oracle ERP 11i/R12 Functional/Technical Materials: API Integration ,x_schedule_day => v_c hr_special_terms ,x_cust_ship_site_id => v_num_cus t_ship_site /*Input t he term Id from the t able RA_TERMS and transact ion Id from RA_CUST_TRX_TYPES*/ ,x_ap_ar_term_id => v_num_term_id ,x_cust_t rx_type_id => v_num_trx_type_id ,x_project_id => NULL ,x_task_id => NULL ,x_organizat ion_id => NULL ,x_expenditure_ty pe => NULL ,x_expenditure_item_date => NULL ,x_tax_group_id => NULL /*Input t he tax Code Id from the table AR_VAT_TAX* / ,x_tax_code_id => v_num_tax_c ode_id ,x_tax_included => NULL ,x_distribution_set _id => NULL ,x_inv_rule_id => NULL ,x_acc ount_rule_id => NULL ,x_salesrep_id => NULL ,x_approved_by => NULL ,x_stat us => NULL ,x_index_pe riod_id => NULL ,x_index_t erm_indicat or => NULL ,x_po_he ader_id => NULL ,x_c ust _po_number => NULL ,x_rec eipt _met hod_id => NULL ,x_var_rent_inv_id => NULL ,x_var_rent_ty pe => NULL ,x_period_billrec_id => NULL ,x_rec _agr_line_id => NULL ,x_amount_ty pe => NULL ,x_change d_flag => NULL ,x_term_template _id => NULL ,x_att ribute_c ate gory => NULL ,x_att ribute1 => NULL ,x_att ribute2 => NULL ,x_att ribute3 => NULL ,x_att ribute4 => NULL ,x_att ribute5 => NULL ,x_att ribute6 => NULL ,x_att ribute7 => NULL ,x_att ribute8 => NULL ,x_att ribute9 => NULL ,x_at tribut e10 => NULL ,x_at tribut e11 => NULL ,x_at tribut e12 => NULL ,x_at tribut e13 => NULL ,x_at tribut e14 => NULL ,x_at tribut e15 => NULL ,x_project _att ribute_c ate gory => NULL ,x_project _att ribute1 => NULL ,x_project _att ribute2 => NULL ,x_project _att ribute3 => NULL ,x_project _att ribute4 => NULL ,x_project _att ribute5 => NULL ,x_project _att ribute6 => NULL ,x_project _att ribute7 => NULL ,x_project _att ribute8 => NULL ,x_project _att ribute9 => NULL ,x_project _att ribute10 => NULL ,x_project _att ribute11 => NULL ,x_project _att ribute12 => NULL ,x_project _att ribute13 => NULL ,x_project _att ribute14 => NULL ,x_project _att ribute15 => NULL /*WHO Columns*/ ,x_creation_date => g_dte_sysdate ,x_creat ed_by => g_num_user_id ,x_last_updat e_date => g_dte_sy sdat e ,x_last_updat ed_by => g_num_user_id ,x_last _updat e_login => g_num_login_id /*Input Calling form value*/


12/15

8/1/13

Oracle ERP 11i/R12 Functional/Technical Materials: API Integration ,x_c alling_form => 'PNTLEASE' ,x_org_id => g_num_org_id ,x_lease_stat us => 'ACT' -- Act ive Stat us ,x_recov erable_flag => NULL ,x_area_type _code => NULL ,x_area => NULL ,x_grouping_rule_id => NULL ); This API returns the Payment term Id which will be used for creating the Account Distribution and Milestones for the Payments. pn_distributions_pkg.insert_row Call this API with different Account Classes for a Payment stream in order to create multiple Acc ount distribution. Tables populated: PN_DISTRIBUTIONS

Parameters for API: pn_distributions_pkg.insert_row ( /*Output Parameter for Rowid*/ x_rowid => v_c hr_row_id /*Out put Parameter for Distribution Id*/ ,x_dist ribution_id => v_num_dist_id /*Input Ac count Id from the t able GL_CODE_COMBINATIONS*/ ,x_acc ount_id => v_num_account_id /*Input Payment term for which acc ount Distribution is to be creat ed*/ ,x_payment _term_id => in_num_payment_t erm_id ,x_term_template _id => NULL /*Input Ac count Class such as ‘Revenue’*/ ,x_account _class => in_chr_acc ount_class /*Input Perce ntage Distribution for each acc ount*/ ,x_percentage => 100 /*Output Line Number*/ ,x_line_number => v_num_line_number /*WHO Columns*/ ,x_last_updat e_date => g_dte_sy sdat e ,x_last_updat ed_by => g_num_user_id ,x_creation_date => g_dte_sysdate ,x_creat ed_by => g_num_user_id ,x_last _updat e_login => g_num_login_id ,x_att ribute_c ate gory => NULL ,x_att ribute1 => NULL ,x_att ribute2 => NULL ,x_att ribute3 => NULL ,x_att ribute4 => NULL ,x_att ribute5 => NULL ,x_att ribute6 => NULL ,x_att ribute7 => NULL ,x_att ribute8 => NULL ,x_att ribute9 => NULL ,x_at tribut e10 => NULL ,x_at tribut e11 => NULL ,x_at tribut e12 => NULL ,x_at tribut e13 => NULL ,x_at tribut e14 => NULL ,x_at tribut e15 => NULL ,x_org_id => g_num_org_id ); 7. Milestones API’s: This API’s can be used to create the Milestones for any of the following a. Lease Payment streams b. Lease Details c. Lease Options d. Insurance Depending upon the Parameters passed to this API, it will creat e the Milestone for that part of the lease. For example: to create the Milestone for Payment Stream pass the value of the parameter payment_term_id and pass the ‘NULL’ to Option id and Insurance requirement id. pn_lease_milestones_pkg.insert_row Tables populated: PN_LEASE_MILESTONES

Parameters for API: pn_lease_milestones_pkg.insert_row( oracleerpfunctional.blogspot.in/search/label/API Integration

13/15

8/1/13


/*Output Parameter for Row Id*/ x_rowid => v_c hr_row_id4 /*Output Milestone Id*/ ,x_leas e_milestone_id => v_num_milest one_id /*Input lease Id and Lease Change Id*/ ,x_lease_c hange_id => v_num_lease_c h_id ,x_leas e_id => v_num_lease_id /*Input t he Milestone type code from lookup ‘PN_MILESTONES_TYPE’*/ ,x_milestone _type _code => v_c hr_ml_type_c ode /*Input Option Id If the Milestone is to be creat ed for Option otherwise pass it as NULL*/ ,x_opt ion_id => v_num_option_id /*Input insurance requirement Id If t he Milestone is to be c reated for Insurance otherwise pass it as NULL*/ ,x_insuranc e_requirement_id => NULL /*Input Payment term Id If t he Milestone is to be c reated for Payment term otherwise pass it as NULL*/ ,x_payment _term_id => NULL /*Input Lead days and Every Days value*/ ,x_lead_days => 185 ,x_every_days => 90 ,x_act ion_taken => NULL ,x_act ion_date => NULL ,x_att ribute_c ate gory => v_c hr_ml_type_c ode /*Input t he Milestone Message in the corresponding Att ribute*/ ,x_att ribute1 => 'Test Renewal' ,x_att ribute2 => NULL ,x_att ribute3 => NULL ,x_att ribute4 => NULL ,x_att ribute5 => NULL ,x_att ribute6 => NULL ,x_att ribute7 => NULL ,x_att ribute8 => NULL ,x_att ribute9 => NULL ,x_at tribut e10 => NULL ,x_at tribut e11 => NULL ,x_at tribut e12 => NULL ,x_at tribut e13 => NULL ,x_at tribut e14 => NULL ,x_at tribut e15 => NULL /*Input t he Milestone Date*/ ,x_milestone _date => c_xsrs_rec .renewal_ntc e_date /*Input t he WHO Columns*/ ,x_use r_id => v_num_user_id ,x_creation_date => g_dte_sysdate ,x_creat ed_by => g_num_user_id ,x_last_updat e_date => g_dte_sy sdat e ,x_last_updat ed_by => g_num_user_id ,x_last _updat e_login => g_num_login_id ,x_org_id => g_num_org_id ); Schedules and Items Program: Once the Lease and its Payment terms are created the next step will be to submit the Concurrent Program ‘Schedules and Items’. This Program will perform following things a. Create e ntries into Pay ment Schedules t able(PN_PAYMENT_SCHEDULES) for each Payment term of the Lease b. Create Entries into Payment Items Table(PN_PAYMENT_ITEMS)for each Payment Schedule. c. Finalize the Lease. The Program will finalize the Lease if the Lease context is passed as ‘ABS’. The same program can be submitt ed for Renewing the Lease or Extending the Lease by passing different Lease Context. The Payment Schedules generated is viewed in Responsibility: Property Manager User Payments>Authorize


14/15

8/1/13


Click on Details tab to check the Payment Items for each Payment Schedule.

This Payment Schedule can be approved and then exported to the Oracle Payables by using the Export to Payables in the same menu option. You might also like: Oracle pa ssw ord recovery method GL Funds che ck functionality Period Types Procure to Pay - Order to Cash - End to End Cycle Functional Documents Purchasing Setup: Min-Max Planning LinkWithin

API Integration, Oracle R12

Home

Older Posts

Subscribe to: Posts (Atom)

Copyright 2008-2009 Wordpress Theme by NeoEase. Blogger Templates by Blogcrowds.


15/15

Oracle ERP 11i_R12 Functional_Technical Materials_ API Integration

Recommend Documents