Code
FND_USER_PKG is stand function
BEGIN
FND_USER_PKG.ADDRESP
('USERID',
'SYSADMIN',
'SYSTEM_ADMINISTRATOR',
'STANDARD',
'Add Sysadmin Responsibility to A user from Backend',
SYSDATE - 1,
SYSDATE + 99
);
COMMIT;
DBMS_OUTPUT.PUT_LINE ('Responsibility Added Successfully');
EXCEPTION
WHEN OTHERS
THEN
DBMS_OUTPUT.PUT_LINE ( ' Sys Admin Resp cannot be added: '
|| SQLCODE
|| SUBSTR (SQLERRM, 1, 100)
);
END;
Oracle workflow has 3 kinds of levels. Customization /access / Protection levels
A numeric value ranging from 0 to 1000. Every workflow user operates at specific access level. The access level defines whether the user can modify certain workflow data. You can only modify data that is protected at a level equal to or higher than your access level.
You can change protection and customization level using options, once you have checked preserve customization then you can not do customization in workflow. once you have checkbox for lock at the access level . The protection level can change with existing access level and access level has decide with oracle workflow access level .
Suppose I want to do customization in std workflow, I do not want to override my customized objects in workflow , then you have must to understand access level concept, each std oracle workflow design with 20 access level , It has checked range between customization and protection level, In std workflow , you have observed that range 0 - 20 0 as customization and 20 as protection level our access level is 20 , those item or objects has level 20 then once oracle patch has applied it will override existing definition.
case 1 -- Need to modify items of std workflow
In such case existing oracle workflow process gets great out you can not modify because exiting std process access level is 20, you can modify up-to 20 access level only , if you want modify std workflow then you have to set access level less than 20 , it is not right practice.
Customization access level protection level
0 18 20
here now access level is between 0-20 range so you can modify change.
Case 2 :- New custom process called in std workflow and not to modify override custom process once Oracle patch applied
While create new custom process, please update access level as 100. and update protection level as 100
Customization access level protection level
0 100 100
access level 100 is range between customization (0) and protection level (100), you can modify custom process. you can not modify std process , it will be get grad out. you can called custom process in std workflow
Oracle Workflow Upload and Download
Oracle workflow always store in oracle database . Oracle workflow is workflow flat file with extension .wft. you can download workflow .wft file from database and after modification you can upload wft file into database. for upload and download , we have used oracle workflow utility , called as WFLOAD
YOU HAVE TO RUN BELOW COMMAND ON UNIX
sysntax
WFLOAD apps/<pwd>@EBSDEV 0 Y UPLOAD <name.wft>
WFLOAD apps/<pwd>@EBSDEV 0 Y UPGRADE <name.wft>
WFLOAD apps/<pwd>@EBSDEV 0 Y FORCE <name.wft>
UPLOAD ---- it will be check Customization and protection level , Access level should be in range between customization and protection level
FORCE -- It will ignore any customization and protection level.
UPGRADE --
WFLOAD apps/<pwd>@EBSDEV 0 Y DOWNLOAD < NAME.WFT> NAME
WFLOAD apps/<pwd>@EBSDEV 0 Y DOWNLOAD POAPPRV.wft POAPPRV
Hi Team
There are 5 ways to learn oracle cloud free. you have to plan and motivate your self to study oracle cloud , there are two types of cloud positions in market, Oracle cloud technical and oracle cloud Functional.
First way
Login https://support.oracle.com/portal/ and check tab Knowledge
here you can get lot of documentation
2nd Way
3rd ways
https://cloudcustomerconnect.oracle.com/
4th ways
doc.oracle.com
partner.oracle.com
demo.oracle.com
ilearning.oracle.com
Oracle Golden Tax was introduced in Oracle Apps R12 so it is not available to prior e-business suites. Golden Tax Adaptor helps transfer information from Account Receivables into Oracle Golden Tax and send it to Golden Tax system.
In China there are 2 types of credit memo, Special VAT credit Memo and other one called common VAT (Value added Tax ) credit memo, To issue a Special VAT credit memo, you need to first fill application form and get approval from tax bureau. The 16 digit number on form needs to be put into description in golden tax Adaptor, The remaining process as handle in AR invoices.
withing the Golden Tax system you need to maintain bank name, bank branch name and bank account number for your customers , these information should keep in Chinese
Golden Tax System is stand alone system is used to create and print customer vat invoices whenever you sell products or services to Chinese customers.
Vat Invoice Type can map with AR transaction types while configuring Golden Tax Adaptor .
Golden Tax System (ASINO) requires Customer name, address,tax player id, bank information,invoice reviewer's name and collector's name apart from this we also need to setup the invoice amount limit, number of limit,etc in oracle system
Deposit Golden Tax Invoice : there is not any VAT involved, so there is no VAT with Golden system.In oracle Financials AR you can define transaction types which will interface to the golden tax System.
you can define custom transfer rules , The rules helps to prevent unwanted AR transaction types transfer into golden tax modules.
Programs used in golden Tax
Receivables Transfer to Golden Tax Adaptor
Hello Friends,
In last session, we had been talked about e-mail format, We are discussing about email sentences with respective situation.
Create table script
CREATE TABLE BNE.XXST_GOLD_IMPORT_INT_BNE_T
(
OPERATING_UNIT VARCHAR2(100),
SOURCE VARCHAR2(100),
INVOICE_NUM VARCHAR2(200),
INVOICE_LINE_NUM VARCHAR2(10),
CURRENCY VARCHAR2(20),
BILL_TO_CUSTOMER_NAME VARCHAR2(1000),
VAT_CODE VARCHAR2(100),
VAT_NUMBER VARCHAR2(100),
VAT_DATE DATE,
CREATION_DATE DATE,
USER_NAME VARCHAR2(100),
RESPO_NAME VARCHAR2(100),
STATUS VARCHAR2(5)
)
---Check Table name in Fnd_Tables
select * from fnd_tables where table_name='XXST_GOLD_IMPORT_INT_BNE_T';
---- Delete table from fnd_tables
EXEC AD_DD.delete_table('BNE','XXST_GOLD_IMPORT_INT_BNE_T')
---Register Table name
EXEC AD_DD.REGISTER_TABLE ('BNE','XXST_GOLD_IMPORT_INT_BNE_T','T');
--- Register Column names in Table
EXEC AD_DD.REGISTER_COLUMN ('BNE','XXST_GOLD_IMPORT_INT_BNE_T','OPERATING_UNIT',1,'VARCHAR2',100,'Y','N');
EXEC AD_DD.REGISTER_COLUMN ('BNE','XXST_GOLD_IMPORT_INT_BNE_T','SOURCE',2,'VARCHAR2',100,'Y','N');
EXEC AD_DD.REGISTER_COLUMN ('BNE','XXST_GOLD_IMPORT_INT_BNE_T','INVOICE_NUM',3,'VARCHAR2',200,'Y','N');
EXEC AD_DD.REGISTER_COLUMN ('BNE','XXST_GOLD_IMPORT_INT_BNE_T','INVOICE_LINE_NUM',4,'VARCHAR2',10,'Y','N');
EXEC AD_DD.REGISTER_COLUMN ('BNE','XXST_GOLD_IMPORT_INT_BNE_T','CURRENCY',5,'VARCHAR2',20,'Y','N');
EXEC AD_DD.REGISTER_COLUMN ('BNE','XXST_GOLD_IMPORT_INT_BNE_T','BILL_TO_CUSTOMER_NAME',6,'VARCHAR2',1000,'Y','N');
EXEC AD_DD.REGISTER_COLUMN ('BNE','XXST_GOLD_IMPORT_INT_BNE_T','VAT_CODE',7,'VARCHAR2',100,'Y','N');
EXEC AD_DD.REGISTER_COLUMN ('BNE','XXST_GOLD_IMPORT_INT_BNE_T','VAT_NUMBER',8,'VARCHAR2',100,'Y','N');
EXEC AD_DD.REGISTER_COLUMN ('BNE','XXST_GOLD_IMPORT_INT_BNE_T','VAT_DATE',9,'DATE',9,'Y','N');
EXEC AD_DD.REGISTER_COLUMN ('BNE','XXST_GOLD_IMPORT_INT_BNE_T','CREATION_DATE',10,'DATE',9,'Y','N');
EXEC AD_DD.REGISTER_COLUMN ('BNE','XXST_GOLD_IMPORT_INT_BNE_T','USER_NAME',11,'VARCHAR2',100,'Y','N');
EXEC AD_DD.REGISTER_COLUMN ('BNE','XXST_GOLD_IMPORT_INT_BNE_T','RESPO_NAME',12,'VARCHAR2',100 ,'Y','N');
EXEC AD_DD.REGISTER_COLUMN ('BNE','XXST_GOLD_IMPORT_INT_BNE_T','STATUS',13,'VARCHAR2',5 ,'Y','N');
