Oracle Applications E-Learning Lab

Log in to SYSADMIN User and go to the responsibility User Management Click on Users and query the user Name , Once user name queried then click on Update  After Update new screen will pop up in that Click on Assign Roles Search for ‘Approval%Man%’ and it will give list of roles available Select Roles: 1)    Approvals Management Administrator 2)       Approvals Management business Analyst Click on APPLY   and provide Justification   and click Apply to assign the Roles to the user. Switch Responsibility to    Functional Administrator Click on Create Grant Fill Name and Description with relevant details and Grantee should be User Name which needs grant access and in Object Type it should be AME Transaction Types Click On Next with Data Context Type All Rows Click on Next and select Set as AME Calling Ap

Oracle Pricing Covers the basic feature like defining price lists ,discounts,surcharges for the items. Price Lists : Price Lists allows you to define the prices for the goods. Qualifiers: Qualifiers controls who qualifies for what. You can define qualifier based on customer groups,order types,order amount etc. and attach this to price list . Whenever sales order is entered it verifies whether qualifier is applicable for this price list or not Pricing attributes : This gives you added functionality of defining price based on some attributes. Modifiers : Price list defines the base prices, Modifier controls the discounts for the price list Prerequisites setup required for Price Lists  There are two type of Price list 1.Order Management Price list 2. PO Price List To execute API we need to set the Profile option , based on which price list you want to run API. Below are the option to set the various price lists. FOR OM PRICELIST   a. QP: Pricing Transac

Receipt Write off Activity : This activity will come into role if any adjustments needs to be made against the receipt apply amount For example Receipt amount is $100 and for that already applied amount is $50 and now you want to adjust that $50 from applied amount for that receipt write off functionality Prequisite setup To enable Receipt Write off functionality Approval limits for the users needs to be define Set up for the Approval Limits Receivables Manager à Transactions à Approval Limits  Select the relevant user with which you want to perform write off operations. Where document type has many activities but our aim is to write off amounts so choose  "Receipt Write Off". select currency as USD and set the approval limit amounts  Below is the sample code to create write off amounts but before that  we need to set the context for user without it , API wont kick off  and another mandatory paramter is Receivables_trx_id which can be defined

This API    AR_RECEIPT_API_PUB.Apply_on_account   will comes into picture  when amount needs to be apply against the receipt but there is no valid transaction for the customer . For those records you apply them as ON ACCOUNT against the receipts and later you can associate customer as well from front end. Sample API code to apply ON Account amount against Receipt. DECLARE    p_api_version                    NUMBER;    p_init_msg_list                  VARCHAR2 (200);    p_commit                         VARCHAR2 (200);    p_validation_level               NUMBER;    x_return_status                  VARCHAR2 (200);    x_msg_count                      NUMBER;    x_msg_data                       VARCHAR2 (200);    p_cash_receipt_id                ar_cash_receipts.cash_receipt_id%TYPE;    p_receipt_number                 ar_cash_receipts.receipt_number%TYPE;    p_amount_applied                 ar_receivable_applications.amount_applied%TYPE;    p_apply_date                  

Once Receipt created , Amount needs to apply against receipt amount. Inorder to apply amount against receipt , sample API code has been written. Sample API code to apply amount against Receipt. DECLARE    l_return_status   varchar2 (1);    l_msg_count       number;    l_msg_data        varchar2 (240);    l_count           number;    l_msg_data_out    varchar2 (240);    l_mesg            varchar2 (240);    p_count           number;    l_Rec_num         varchar2 (100);    l_trx_num         varchar2 (100); BEGIN    mo_global.SET_POLICY_CONTEXT ('S', 414);                     -- your org id    mo_global.init ('AR');    ar_receipt_api_pub.Apply (       p_api_version        => 1.0,       p_init_msg_list      => FND_API.G_TRUE,       p_commit             => FND_API.G_TRUE,       p_validation_level   => FND_API.G_VALID_LEVEL_FULL,       p_cash_receipt_id    => 95951,--- <CASH RECEIPT ID >       p_customer_Trx_id    => 289864