Oracle Enterprise Resource Planning | ERP System: Apps Technical

Apps Technical

ERRBUFF and RETCODE in Oracle Apps

By Jag - May 19, 2018

1 Comments

ap_vebdor

API-Update Supplier Sites and assign Tax code

By Jag - May 14, 2018

AP_VENDOR_PUB_PKG.UPDATE_VENDOR_SITE

API-Oracle Apps R12

DECLARE

v_api_version NUMBER;

v_init_msg_list VARCHAR2(200);

v_commit VARCHAR2(200);

v_validation_level NUMBER;

x_return_status VARCHAR2(200);

x_msg_count NUMBER;

v_vendor NUMBER;

x_msg_data VARCHAR2(200);

l_vendor_site_rec apps.ap_vendor_pub_pkg.r_vendor_site_rec_type;

l_existing_vendor_site_rec ap_supplier_sites_all%ROWTYPE;

v_vendor_site_id NUMBER;

v_calling_prog VARCHAR2(200);

v_error_flag VARCHAR2(200):='N';

v_error_message VARCHAR2(4000):='N';

cursor c is

select VENDOR_NAME,TAX_REGISTRATION_NO,TAX_CODE from XX_VENDOR_SITES_STG

GROUP BY VENDOR_NAME,REMITTANCE_EMAIL,TAX_CODE;

CURSOR C1(P_VENDOR VARCHAR) IS SELECT VENDOR_SITE_ID

FROM ap_supplier_sites_all assa

WHERE assa.vendor_id =P_VENDOR;

BEGIN

for i in c loop

BEGIN

v_error_flag:='N';

v_error_message:=null;

select vendor_id into v_vendor from ap_suppliers

where upper(vendor_name)=upper(i.VENDOR_NAME);

EXCEPTION

WHEN OTHERS THEN

v_error_flag:='Y';

v_error_message:='Unable to find the supplier site information for site id';

DBMS_OUTPUT.put_line('Unable to find the supplier site information for site id' ||v_vendor_site_id);

END;

IF v_error_flag='N' THEN

FOR J IN C1(v_vendor) LOOP

fnd_global.apps_initialize(610970,50111,200);

mo_global.init('SQLAP');

fnd_client_info.set_org_context(4556);

v_api_version := 1.0;

v_init_msg_list := fnd_api.g_true;

v_commit := fnd_api.g_true;

v_validation_level := fnd_api.g_valid_level_full;

v_vendor_site_id := J.VENDOR_SITE_ID; -- to be end dated

v_calling_prog := 'Supplier Tax code Update';

l_vendor_site_rec.vendor_site_id := l_existing_vendor_site_rec.vendor_site_id;

l_vendor_site_rec.last_update_date := SYSDATE;

l_vendor_site_rec.last_updated_by := 6147023;

l_vendor_site_rec.vendor_id := l_existing_vendor_site_rec.vendor_id;

l_vendor_site_rec.org_id := l_existing_vendor_site_rec.org_id;

l_vendor_site_rec.vat_code :=I.TAX_CODE;

l_vendor_site_rec.AUTO_TAX_CALC_FLAG:='Y';

l_vendor_site_rec.VAT_REGISTRATION_NUM:=I.TAX_REGISTRATION_NO;

AP_VENDOR_PUB_PKG.UPDATE_VENDOR_SITE(p_api_version => v_api_version,

p_init_msg_list => v_init_msg_list,

p_commit => v_commit,

p_validation_level => v_validation_level,

x_return_status => x_return_status,

x_msg_count => x_msg_count,

x_msg_data => x_msg_data,

p_vendor_site_rec => l_vendor_site_rec,

p_vendor_site_id => v_vendor_site_id,

p_calling_prog => v_calling_prog);

DBMS_OUTPUT.put_line('X_RETURN_STATUS = ' || x_return_status);

DBMS_OUTPUT.put_line('X_MSG_COUNT = ' || x_msg_count);

DBMS_OUTPUT.put_line('X_MSG_DATA = ' || x_msg_data);

END LOOP;

UPDATE XX_VENDOR_SITES_STG

SET STATUS='SUCCESS'

WHERE VENDOR_NAME=I.VENDOR_NAME;

END IF;

IF v_error_flag='Y' THEN

UPDATE XX_VENDOR_SITES_STG

SET STATUS='ERROR',

ATTRIBUTE1=v_error_message

WHERE VENDOR_NAME=I.VENDOR_NAME;

END IF;

COMMIT;

END LOOP;

END;

0 Comments

Apps Technical

Oracle Apps Sales Order Line Status and Definition

By Jag - September 22, 2015

OM = Order Management Sales order form
SE = Shipping Transactions or execution form

1) Entered (OM): Order is saved but not booked

2) Booked (OM): Order is Booked.

3) Awaiting Shipping (OM): Order is set-aside however lines aren't however picked.Navigating to Shipping Execution, the delivery line standing flow is

4) Not Ready to Release (SE): A delivery line could also be during this standing once it's interfaced manually into Shipping, isn't regular and has no reservations. once lines square measure foreign mechanically from Order Management this standing isn't used

5) Released to Warehouse (SE): Pick unharness has started however not however completed. one in all the explanation can be allocation haven't been decide confirmed. The decide unharness method creates a Move Order Header & Mover Order Line in Inventory. this can be a standard standing for users that perform a ballroom dancing decide unharness method. This standing indicates that inventory allocation has occurred but decide conformation has not however taken place.

6) Ready to Release (SE): Order Line is booked and passed to shipping execution. The line is now eligible to pick Release.

7) Backordered(SE): The status of Backorderd is assigned to a line under the following circumstances.
· The Pick Release process attempted to allocate inventory to the line and all or a partial quantity of the item was not available. In this case the system automatically backorders the discrepant quantity.
· At Ship confirm the user enters a shipped quantity for an item that is less than the original requested quantity.
· The user manually Backorders the entire delivery.
8) Shipped (SE): The delivery line is shipped confirmed.

9) Confirmed (SE): The delivery line is shipped or backordered and the trip stops are open.

10) Picked (OM): Pick release is complete, both allocations and pick confirm

11) Picked Partial (OM): This status occurs when a delivery line is not allocated the full quantity during Pick Release and Ship Confirm has not occurred

12) Interfaced (SE): The delivery line is shipped and Inventory interface concurrent process is complete.

13) Awaiting Fulfillment (OM): When fulfillment set is used, Not all shippable lines in a fulfillment set or a configuration are fulfilled

14) Fulfilled (OM): All lines in a fulfillment set are fulfilled.

15) Interfaced to Receivables (OM): The order is linked with Receivables and the invoice is created.

16) Partially Interfaced to Receivables (OM): This status is used in a PTO flow and indicates that the particular PTO item is required for revenue.

17) Closed (OM): Closed indicates that the line is closed.

18) Canceled (OM): Indicates that the line has been completely canceled. No further processing will occur for this line.

1 Comments

Apps Technical

Script to find Scheduled synchronous activities and requesting sets

By Jag - November 03, 2014

0 Comments

Apps Technical

Create Programmatically Flex value for a particular Value set

By Jag - October 26, 2014

0 Comments

Apps Technical

XML Publisher Bursting | Email report output

By Jag - October 09, 2014

0 Comments

Apps Functional

Oracle Forms Personalization Global Variable | Oracle Tech

By Jag - October 06, 2014

0 Comments

Account Payables

Accounts Payable Setup | Financial Options | Payables Options

By Jag - October 05, 2014

0 Comments

Apps Technical

View other users concurrent request output

By Jag - October 02, 2014

View other users concurrent request output

R11

System Administrator à Profile à System

Search for profile à 'Concurrent: Report Access Level'

Level	Value	Result
Site	User	The user can only view the requests submitted by him
Responsibility	Responsibility	That user can also review the log and report output files from all requests submitted from the current responsibility
User	Responsibility	Any user of that responsibility can also view the log and report output files from all requests submitted by any other user of that responsibility

R12

Unfortunately in R12 profile 'Concurrent: Report Access Level' does not work, it is a bit more complex process to achieve this

In R12 this was replaced by Role Based Access Control. The UMX Role Based Access Control (RBAC) is to control who can view request output files.

Note :- You should have SYSADMIN user access.

Functional Developer -> Core Services

>> Search for 'Concurrent Requests'

Click on 'Concurrent Requests' and then on tab 'Object Instance Set'

Ø Click Create Instance Set

Ø Give Name/Code/Description

Ø For Predicate

è Enter below code if you want to see request output for all concurrent programs .

&TABLE_ALIAS.request_id in(

select cr.request_id

from apps.fnd_concurrent_requests cr, apps.fnd_concurrent_programs cp

where cr.concurrent_program_id = cp.concurrent_program_id

and cr.program_application_id = cp.application_id)

è Modify the above query based on your requirement.

n Add and cp.concurrent_program_name if you want to give access only for particular program name, etc.

Ø 'Apply' it and it will give the Confirmation with Code you have entered.

>>> Now login as a SYSADMIN User.

Ø Goto User Management > Role & Role Inheritance

è Click on 'Create Role'

Ø Category – Miscellaneous / Application – Application Object Library

Ø Role Code (Prefix UMX| will be added whatever you provide example : UMX|AKTEST)

Ø Display Name/ Description

Ø 'Apply'

Ø Click on 'Create Grant'

Ø Provide Name / Description

Ø Data Security -> Object -> 'Concurrent Requests'

Ø Click on 'Next'

Ø Data Context Type -> 'Instance Set'

Ø Instance Set -> Instance you Created above, AKTEST

Ø Click 'Next'

Ø Set -> Set -> 'Request Operations'

Ø Click on 'Next' -> Preview and then 'Finish'

Ø It should give you the message for successful creation of Grant.

Known Issue

Sometimes it will give below Error. Just try 3-4 times, it should be fine.

Sorry didn't dig much into it to find the exact reason behind it.

Error Page

You have encountered an unexpected error. Please contact the System Administrator for assistance.

Goto 'User tab

Ø Search for the user you want to assign the grant.

Ø Click 'Update'

Ø Click 'Assign Role'

Ø Search for Role you have created above 'View All Concurrent Requests outputs' (Code -UMX|AKTEST)

Ø Give Justification

Ø You can put active date from past to view previous requests outputs.

Ø DONE... :)

* Now assigned user can see the output of other user's request from the responsibility from which that request had been launched.

>> You can also use the below script to assign the grant to a user.

begin

wf_local_synch.PropagateUserRole(p_user_name => 'USERNAME'

,p_role_name => 'UMX|AKTEST ');

commit;

End;

TAG:

oracle r12 view other users requests

oracle r12 user guide

oracle purchasing user guide r12

oracle r12 user guide pdf

oracle r12 interview questions

oracle r12 documentation