OM-HTMOMSE Sales Order Diagnostic Script (文档 ID 133464.1)


HTMOMSE Sales Order Diagnostic Script (文档 ID 133464.1)转到底部转到底部

APPLIES TO:

Oracle Order Management - Version 11.5.10.0 to 12.2.6 [Release 11.5.10 to 12.2]
Oracle Inventory Management - Version 11.5.10.2 to 12.2.6 [Release 11.5.10 to 12.2]
Oracle Shipping Execution - Version 11.5.10.0 to 12.2.6 [Release 11.5.10 to 12.2]
Oracle Release Management - Version 11.5.10.0 to 12.2.6 [Release 11.5.10 to 12.2]
Oracle Advanced Pricing - Version 11.5.10 to 12.2.6 [Release 11.5 to 12.2]
Information in this document applies to any platform.

MAIN CONTENT



Purpose

The purpose of this script is to collect information related to a Sales Order, its Pricing Adjustments, Shipment lines, Workflow status, Inventory transactions and Receivables transactions.

A new version has been created that is non Release dependent, please use this version for both releases 11.5 and 12:

click here to download HTMomse.sql in ZIP format  -- Last update 31-Oct-2016

 

Usage

1. Run the script from SQL*Plus connected as APPS user as follows: 

    sqlplus apps/<password_for_apps> @HTMomse.sql

    Then follow the prompts on the screen.
    Most entries has default value 'Yes' (when left blank).

2. The script shows the Server Name, file name and location of the output file.

Parameters

Order Number

Required

Header_Id

Required only if more than one HEADER_ID returned. If there is only one header_id returned after inputting the order number, simply hit enter and this header_id will be assumed.

Line_Id

Entering a line_id is only required when you wish to have output for one order line. Otherwise, hit enter without entering a line_id and all lines will be output in the script.

Validation

If 'Yes' then the script would generate a report of the sales order data, and also perform some basic analysis on the data and report on any errors found. If 'No' then the script would simply generate a report of the sales order data, and perform no analysis. The default is 'Yes'.

Display Options

The script allows you to choose whether or not to print some sections of the output. The OM and WSH sections are mandatory. WF, QP, PO, REC, WIP, INV and AR are optional. The default display option is 'Yes'.

Output

The output file will be located on the DB Server in the 'utl_file_dir' directory. (The script will display the output file name and location upon completion).

Notes:

  • This script is developed and maintained by Oracle Support Services. It has been tested internally and should work as documented.
  • This script is being updated periodically. Please download it from My Oracle Support every time you need to run it in order to have the latest version.
  • If you experience long execution times when running the script with the Validation parameter set to 'Y' please terminate and resubmit with this parameter set to 'N' and you should see some improvement in the performance.

Please note that Diagnostic script HTMomse can also to be installed as a Concurrent Process Note 1401831.1

 

Related Documents

For additional diagnostic tools for the Order Management Product Suite, go to:

    1. MyOracleSupport Home Page
    2. See E-Business Suite Diagnostics 11i Test Catalog.
    3. See E-Business Suite Diagnostics R12 Test Catalog.

For a Whitepaper on how to read the output of the HTMOMSE script, please refer to document Understanding the HTMomse12 Output for Order Management Note 1427369.1

 

Old Versions

These old versions will remain in this Note for consistency (references from other Notes) but will not be maintained, it is recommended to use the new version.

click here to download HTMomse11i.sql in ZIP format  -- Last update 11-Jun-2016
click here to download HTMomse12.sql in ZIP format  -- Last update 24-Mar-2016

 

Still have questions?

To discuss this script and its' output further with Oracle experts and industry peers, we encourage you to review, join the HTMOMSE Sales Order Diagnostic Script Note 133464.1 - Feedback and General questionsdiscussion.

REFERENCES

NOTE:1427369.1 - Understanding the HTMomse12 Output for Order Management
NOTE:1401831.1 - Diagnostic script HTMomse to be installed as a Concurrent Process

HTMOMSE Sales Order Diagnostic Script (文档 ID 133464.1)转到底部转到底部

APPLIES TO:

Oracle Order Management - Version 11.5.10.0 to 12.2.6 [Release 11.5.10 to 12.2]
Oracle Inventory Management - Version 11.5.10.2 to 12.2.6 [Release 11.5.10 to 12.2]
Oracle Shipping Execution - Version 11.5.10.0 to 12.2.6 [Release 11.5.10 to 12.2]
Oracle Release Management - Version 11.5.10.0 to 12.2.6 [Release 11.5.10 to 12.2]
Oracle Advanced Pricing - Version 11.5.10 to 12.2.6 [Release 11.5 to 12.2]
Information in this document applies to any platform.

MAIN CONTENT



Purpose

The purpose of this script is to collect information related to a Sales Order, its Pricing Adjustments, Shipment lines, Workflow status, Inventory transactions and Receivables transactions.

A new version has been created that is non Release dependent, please use this version for both releases 11.5 and 12:

click here to download HTMomse.sql in ZIP format  -- Last update 31-Oct-2016

 

Usage

1. Run the script from SQL*Plus connected as APPS user as follows: 

    sqlplus apps/<password_for_apps> @HTMomse.sql

    Then follow the prompts on the screen.
    Most entries has default value 'Yes' (when left blank).

2. The script shows the Server Name, file name and location of the output file.

Parameters

Order Number

Required

Header_Id

Required only if more than one HEADER_ID returned. If there is only one header_id returned after inputting the order number, simply hit enter and this header_id will be assumed.

Line_Id

Entering a line_id is only required when you wish to have output for one order line. Otherwise, hit enter without entering a line_id and all lines will be output in the script.

Validation

If 'Yes' then the script would generate a report of the sales order data, and also perform some basic analysis on the data and report on any errors found. If 'No' then the script would simply generate a report of the sales order data, and perform no analysis. The default is 'Yes'.

Display Options

The script allows you to choose whether or not to print some sections of the output. The OM and WSH sections are mandatory. WF, QP, PO, REC, WIP, INV and AR are optional. The default display option is 'Yes'.

Output

The output file will be located on the DB Server in the 'utl_file_dir' directory. (The script will display the output file name and location upon completion).

Notes:

  • This script is developed and maintained by Oracle Support Services. It has been tested internally and should work as documented.
  • This script is being updated periodically. Please download it from My Oracle Support every time you need to run it in order to have the latest version.
  • If you experience long execution times when running the script with the Validation parameter set to 'Y' please terminate and resubmit with this parameter set to 'N' and you should see some improvement in the performance.

Please note that Diagnostic script HTMomse can also to be installed as a Concurrent Process Note 1401831.1

 

Related Documents

For additional diagnostic tools for the Order Management Product Suite, go to:

    1. MyOracleSupport Home Page
    2. See E-Business Suite Diagnostics 11i Test Catalog.
    3. See E-Business Suite Diagnostics R12 Test Catalog.

For a Whitepaper on how to read the output of the HTMOMSE script, please refer to document Understanding the HTMomse12 Output for Order Management Note 1427369.1

 

Old Versions

These old versions will remain in this Note for consistency (references from other Notes) but will not be maintained, it is recommended to use the new version.

click here to download HTMomse11i.sql in ZIP format  -- Last update 11-Jun-2016
click here to download HTMomse12.sql in ZIP format  -- Last update 24-Mar-2016

 

Still have questions?

To discuss this script and its' output further with Oracle experts and industry peers, we encourage you to review, join the HTMOMSE Sales Order Diagnostic Script Note 133464.1 - Feedback and General questionsdiscussion.

REFERENCES

NOTE:1427369.1 - Understanding the HTMomse12 Output for Order Management
NOTE:1401831.1 - Diagnostic script HTMomse to be installed as a Concurrent Process
深度学习是机器学习的一个子领域,它基于人工神经网络的研究,特别是利用多层次的神经网络来进行学习和模式识别。深度学习模型能够学习数据的高层次特征,这些特征对于图像和语音识别、自然语言处理、医学图像分析等应用至关重要。以下是深度学习的一些关键概念和组成部分: 1. **神经网络(Neural Networks)**:深度学习的基础是人工神经网络,它是由多个层组成的网络结构,包括输入层、隐藏层和输出层。每个层由多个神经元组成,神经元之间通过权重连接。 2. **前馈神经网络(Feedforward Neural Networks)**:这是最常见的神经网络类型,信息从输入层流向隐藏层,最终到达输出层。 3. **卷积神经网络(Convolutional Neural Networks, CNNs)**:这种网络特别适合处理具有网格结构的数据,如图像。它们使用卷积层来提取图像的特征。 4. **循环神经网络(Recurrent Neural Networks, RNNs)**:这种网络能够处理序列数据,如时间序列或自然语言,因为它们具有记忆功能,能够捕捉数据中的时间依赖性。 5. **长短期记忆网络(Long Short-Term Memory, LSTM)**:LSTM 是一种特殊的 RNN,它能够学习长期依赖关系,非常适合复杂的序列预测任务。 6. **生成对抗网络(Generative Adversarial Networks, GANs)**:由两个网络组成,一个生成器和一个判别器,它们相互竞争,生成器生成数据,判别器评估数据的真实性。 7. **深度学习框架**:如 TensorFlow、Keras、PyTorch 等,这些框架提供了构建、训练和部署深度学习模型的工具和库。 8. **激活函数(Activation Functions)**:如 ReLU、Sigmoid、Tanh 等,它们在神经网络中用于添加非线性,使得网络能够学习复杂的函数。 9. **损失函数(Loss Functions)**:用于评估模型的预测与真实值之间的差异,常见的损失函数包括均方误差(MSE)、交叉熵(Cross-Entropy)等。 10. **优化算法(Optimization Algorithms)**:如梯度下降(Gradient Descent)、随机梯度下降(SGD)、Adam 等,用于更新网络权重,以最小化损失函数。 11. **正则化(Regularization)**:技术如 Dropout、L1/L2 正则化等,用于防止模型过拟合。 12. **迁移学习(Transfer Learning)**:利用在一个任务上训练好的模型来提高另一个相关任务的性能。 深度学习在许多领域都取得了显著的成就,但它也面临着一些挑战,如对大量数据的依赖、模型的解释性差、计算资源消耗大等。研究人员正在不断探索新的方法来解决这些问题。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值