Oracle EBS R12财务月结基础
https://wenku.baidu.com/view/f39a2d0249649b6648d747f4.html
Oracle EBS R12财务基础-月结
https://wenku.baidu.com/view/dc0bd960a98271fe910ef90f.html?re=view
oracle ebs 财务模块介绍
https://wenku.baidu.com/view/129b9edf50e2524de5187e8f.html?re=view
ORACLE_EBS 基础设置各模块要点介绍
https://wenku.baidu.com/view/eb514a39a45177232f60a2ce.html?re=view
Oracle_ebs_R12_资产模块_FA
https://wenku.baidu.com/view/bd4dfe366bec0975f465e2b6.html
2018年3月9日 星期五
2018年3月8日 星期四
Oracle EBS: 使用ROI針對RMA進行Receive與Deliver
sample script:
HEADER_INTERFACE_ID ,
GROUP_ID ,
PROCESSING_STATUS_CODE ,
RECEIPT_SOURCE_CODE ,
TRANSACTION_TYPE ,
LAST_UPDATE_DATE ,
LAST_UPDATED_BY ,
LAST_UPDATE_LOGIN ,
CUSTOMER_ID ,
EXPECTED_RECEIPT_DATE ,
VALIDATION_FLAG
)
SELECT
RCV_HEADERS_INTERFACE_S.NEXTVAL ,
RCV_INTERFACE_GROUPS_S.NEXTVAL ,
'PENDING' ,
'CUSTOMER' ,
'NEW' ,
SYSDATE ,
1318, --USER_ID
0 ,
40073 , --CUSTOMER_ID
SYSDATE ,
'Y'
FROM DUAL;
INSERT INTO RCV_TRANSACTIONS_INTERFACE
(INTERFACE_TRANSACTION_ID,
GROUP_ID,
HEADER_INTERFACE_ID,
LAST_UPDATE_DATE,
LAST_UPDATED_BY,
CREATION_DATE,
CREATED_BY,
TRANSACTION_TYPE,
TRANSACTION_DATE,
PROCESSING_STATUS_CODE,
PROCESSING_MODE_CODE,
TRANSACTION_STATUS_CODE,
QUANTITY,
UNIT_OF_MEASURE,
INTERFACE_SOURCE_CODE,
ITEM_ID,
EMPLOYEE_ID,
AUTO_TRANSACT_CODE,
RECEIPT_SOURCE_CODE,
TO_ORGANIZATION_ID,
SOURCE_DOCUMENT_CODE,
DESTINATION_TYPE_CODE,
DELIVER_TO_LOCATION_ID,
SUBINVENTORY,
EXPECTED_RECEIPT_DATE,
OE_ORDER_HEADER_ID,
OE_ORDER_LINE_ID,
CUSTOMER_ID,
CUSTOMER_SITE_ID,
VALIDATION_FLAG)
Values
(RCV_TRANSACTIONS_INTERFACE_S.NEXTVAL, --INTERFACE_TRANSACTION_ID
RCV_INTERFACE_GROUPS_S.CURRVAL, --GROUP_ID
RCV_HEADERS_INTERFACE_S.CURRVAL, --HEADER_INTERFACE_ID
SYSDATE, --LAST_UPDATE_DATE
1318, --LAST_UPDATED_BY
SYSDATE, --CREATION_DATE
1318, --CREATED_BY
'RECEIVE', --TRANSACTION_TYPE
SYSDATE, --TRANSACTION_DATE
'PENDING', --PROCESSING_STATUS_CODE
'BATCH', --PROCESSING_MODE_CODE
'PENDING', --TRANSACTION_MODE_CODE
1, --QUANTITY
'Each', --UNIT_OF_MEASURE
'RCV', --INTERFACE_SOURCE_CODE
149, --ITEM_ID
25, --EMPLOYEE_ID
'DELIVER',--AUTO_TRANSACT_CODE
'CUSTOMER', --RECEIPT_SOURCE_CODE
204, --TO_ORGANIZATION_ID
'RMA', --SOURCE_DOCUMENT_CODE
'INVENTORY', --DESTINATION_TYPE_CODE
204, --DELIVER_TO_LOCATION_ID
'Stores', --SUBINVENTORY
SYSDATE, --EXPECTED_RECEIPT_DATE
99442, --OE_ORDER_HEADER_ID
200068, --OE_ORDER_LINE_ID
40073, --CUSTOMER_ID
10144,--CUSTOMER_SITE_ID
'Y');
註: 自R12開始, ORG_ID欄位必須填值
Ref:
How to Receive and Deliver Against RMA Using ROI (Doc ID 339835.1)
INSERT INTO RCV_HEADERS_INTERFACE
(HEADER_INTERFACE_ID ,
GROUP_ID ,
PROCESSING_STATUS_CODE ,
RECEIPT_SOURCE_CODE ,
TRANSACTION_TYPE ,
LAST_UPDATE_DATE ,
LAST_UPDATED_BY ,
LAST_UPDATE_LOGIN ,
CUSTOMER_ID ,
EXPECTED_RECEIPT_DATE ,
VALIDATION_FLAG
)
SELECT
RCV_HEADERS_INTERFACE_S.NEXTVAL ,
RCV_INTERFACE_GROUPS_S.NEXTVAL ,
'PENDING' ,
'CUSTOMER' ,
'NEW' ,
SYSDATE ,
1318, --USER_ID
0 ,
40073 , --CUSTOMER_ID
SYSDATE ,
'Y'
FROM DUAL;
INSERT INTO RCV_TRANSACTIONS_INTERFACE
(INTERFACE_TRANSACTION_ID,
GROUP_ID,
HEADER_INTERFACE_ID,
LAST_UPDATE_DATE,
LAST_UPDATED_BY,
CREATION_DATE,
CREATED_BY,
TRANSACTION_TYPE,
TRANSACTION_DATE,
PROCESSING_STATUS_CODE,
PROCESSING_MODE_CODE,
TRANSACTION_STATUS_CODE,
QUANTITY,
UNIT_OF_MEASURE,
INTERFACE_SOURCE_CODE,
ITEM_ID,
EMPLOYEE_ID,
AUTO_TRANSACT_CODE,
RECEIPT_SOURCE_CODE,
TO_ORGANIZATION_ID,
SOURCE_DOCUMENT_CODE,
DESTINATION_TYPE_CODE,
DELIVER_TO_LOCATION_ID,
SUBINVENTORY,
EXPECTED_RECEIPT_DATE,
OE_ORDER_HEADER_ID,
OE_ORDER_LINE_ID,
CUSTOMER_ID,
CUSTOMER_SITE_ID,
VALIDATION_FLAG)
Values
(RCV_TRANSACTIONS_INTERFACE_S.NEXTVAL, --INTERFACE_TRANSACTION_ID
RCV_INTERFACE_GROUPS_S.CURRVAL, --GROUP_ID
RCV_HEADERS_INTERFACE_S.CURRVAL, --HEADER_INTERFACE_ID
SYSDATE, --LAST_UPDATE_DATE
1318, --LAST_UPDATED_BY
SYSDATE, --CREATION_DATE
1318, --CREATED_BY
'RECEIVE', --TRANSACTION_TYPE
SYSDATE, --TRANSACTION_DATE
'PENDING', --PROCESSING_STATUS_CODE
'BATCH', --PROCESSING_MODE_CODE
'PENDING', --TRANSACTION_MODE_CODE
1, --QUANTITY
'Each', --UNIT_OF_MEASURE
'RCV', --INTERFACE_SOURCE_CODE
149, --ITEM_ID
25, --EMPLOYEE_ID
'DELIVER',--AUTO_TRANSACT_CODE
'CUSTOMER', --RECEIPT_SOURCE_CODE
204, --TO_ORGANIZATION_ID
'RMA', --SOURCE_DOCUMENT_CODE
'INVENTORY', --DESTINATION_TYPE_CODE
204, --DELIVER_TO_LOCATION_ID
'Stores', --SUBINVENTORY
SYSDATE, --EXPECTED_RECEIPT_DATE
99442, --OE_ORDER_HEADER_ID
200068, --OE_ORDER_LINE_ID
40073, --CUSTOMER_ID
10144,--CUSTOMER_SITE_ID
'Y');
註: 自R12開始, ORG_ID欄位必須填值
Ref:
How to Receive and Deliver Against RMA Using ROI (Doc ID 339835.1)
2018年3月7日 星期三
Oracle EBS: workflow通知信持續退信之解決方法
當workflow的通知信未正常完成寄送時(例如email失效), 會一直重試並退信, 最單純的解決方式, 是修正email.
另一個方法是找出notification, 修改status, 再執行script清mail queue.
1.查看資料
另一個方法是找出notification, 修改status, 再執行script清mail queue.
1.查看資料
select * from wf_notifications
where notification_id =95536469
2.更改狀態
update wf_notifications
set mail_status = 'SENT' where notification_id =95536469
and mail_status = 'INVALID'
3.執行script清除queue(先以sqlplus連上DB)
@$FND_TOP/patch/115/sql/wfntfqup.sql <APPSusr> <APPSpw> <FNDusr>
註1: 第3項要telnet到server再執行
註2: FNDusr為applsys
Ref:
1.How To Purge E-Mail Notifications From The Workflow Queue So The E-Mail Is Not Sent (Doc ID 372933.1)
2.How To Purge E-Mail Notifications From The Workflow Queue So The E-Mail Is Not Sent
https://oracleappsfusion.wordpress.com/2014/09/30/how-to-purge-e-mail-notifications-from-the-workflow-queue-so-the-e-mail-is-not-sent/
update wf_notifications
set mail_status = 'SENT'
and mail_status = 'INVALID'
3.執行script清除queue(先以sqlplus連上DB)
@$FND_TOP/patch/115/sql/wfntfqup.sql <APPSusr> <APPSpw> <FNDusr>
註1: 第3項要telnet到server再執行
註2: FNDusr為applsys
Ref:
1.How To Purge E-Mail Notifications From The Workflow Queue So The E-Mail Is Not Sent (Doc ID 372933.1)
2.How To Purge E-Mail Notifications From The Workflow Queue So The E-Mail Is Not Sent
https://oracleappsfusion.wordpress.com/2014/09/30/how-to-purge-e-mail-notifications-from-the-workflow-queue-so-the-e-mail-is-not-sent/
2018年3月6日 星期二
Oracle SQL: 擷取trigger之source code
有以下兩個方式:
select dbms_metadata.get_ddl('TRIGGER','my_trigger_name', user) from dual
select text from user_source where name='my_trigger_name' and type='TRIGGER'
select dbms_metadata.get_ddl('TRIGGER','my_trigger_name', user) from dual
select text from user_source where name='my_trigger_name' and type='TRIGGER'
2018年3月5日 星期一
Oracle EBS: ASCP執行Planning Data Pull時error
Error message:
Either another Planning Data Pull process is running for this instance or an earlier Planning Data Pull process may have terminated abnormally. In the latter case, you need to launch the 'Planning Data Collection - Purge Staging Table' program before launching Planning Data Collections again
Solution:
Launch the 'Planning Data Collection - Purge Staging Table ' program.
註: user怕有問題, 不敢執行, 因這error不常發生, 通常IS就直接幫user處理了.
Ref:
1.Planning Data Pull Fails With Message - Another Planning Data Pull Process Is Running (Doc ID 730037.1)
Either another Planning Data Pull process is running for this instance or an earlier Planning Data Pull process may have terminated abnormally. In the latter case, you need to launch the 'Planning Data Collection - Purge Staging Table' program before launching Planning Data Collections again
Solution:
Launch the 'Planning Data Collection - Purge Staging Table ' program.
註: user怕有問題, 不敢執行, 因這error不常發生, 通常IS就直接幫user處理了.
Ref:
1.Planning Data Pull Fails With Message - Another Planning Data Pull Process Is Running (Doc ID 730037.1)
訂閱:
文章 (Atom)