How to Simulate the Price Order or Price Line Function using API QP_PREQ_PUB.PRICE_REQUEST
Includes Example Scripts (文档 ID 412545.1)
转到底部

In this Document

Purpose
  Scope
  Details
  Example Scripts to Simulate Price Order
  qp_engine_testing.sql
  qp_test_service.sql
  qp_test_oid.sql

  qp_direct_insert.sql
  qp_manual_adjustments.sql
  qp_override_selling_price.sql
  The setup involves passing information
to the pricing engine using the following:
  Control Record Information:
  Request/Order Line Information:
  Qualifiers and Pricing Attributes Information:
  Additional Resources:
  Available Options To Update the Order Upon
Repricing
  References

APPLIES TO:

Oracle Advanced Pricing - Version 11.5.10 and later

Oracle Order Management - Version 11.5.10.0 and later

Information in this document applies to any platform.

PURPOSE

This note is intended to show how the Price Order or Price Line action may be simulated using an API call. This API call will not result in an update to the order.

SCOPE

The intended audience is for those with technical knowledge of Oracle Applications Code, the usage of public APIs, and those familiar with creating custom solutions for unique business requirements.

This is only a sample code and should be used to develop one's own code to meet business needs. Due to the fact this is  customized code, it is the Customer's responsibility to thoroughly test and to maintain their code. Oracle support may not be able to assist
with these scripts, hence if one is implementing a custom solution and requires assistance, please contact Oracle Consulting.

DETAILS

Example Scripts to Simulate Price Order

The following scripts are used in the examples for the Price Request Application Program Interface.

These scripts help one set up data and make a call to the pricing engine to return the price and any related discounts.

The scripts are located in the following area:   $QP_TOP/patch/115/sql.



Please note then if one upgrades to a new release of Oracle Applications one would need to acquire a new copy of the scripts (same directory) as these scripts may have changes as provided by Oracle Development to work within the new application version.  Therefore
if one used an example script to develop ones own script, for example, on Oracle Applications 11.5.10.2 and then upgraded to Oracle Applications 12.1.1, one would need to review the detailed example scripts for any changes needed.  These are only example scripts
intended to assist with writing of the code needed to call the API.  It is the customers responsibility to thoroughly test and provide final coding needed to achieve desired results to meet individual business needs.

Each script will contain a file version. 



For example, on Release 12.1.1 for example script in file qp_engine_testing.sql shows file version 120.0



REM/* $Header: qp_engine_testing.sql 120.0 2005/06/02 01:05:15 appldev noship $ */

wheres the same script qp_engine_testing.sql on Release 11.5.10.2 shows file version 115.3

REM/* $Header: qp_engine_testing.sql 115.3 2002/05/17 18:43:30 pkm ship $ */
  1. qp_engine_testing.sql

    (All regular Price Lists, Discounts , Surcharges etc.)

  2. qp_test_service.sql

    (Service Item Pricing Setup)

  3. qp_test_oid.sql

    (Other Item Discount Setup)

  4. qp_direct_insert.sql

    (Direct insertion into temporary tables to improve performance)

  5. qp_manual_adjustments.sql

    (Apply manual adjustments)

  6. qp_override_selling_price.sql

    (Override the unit selling price)

Note: Examples provided are from March 2014 from Oracle Applications R12.

The setup involves passing information to the pricing engine using the following:

  • Control Record Information:

The Control Record has parameters which control the behavior of the pricing engine. Please refer to the example scripts above for more details.

  • Request/Order Line Information:

Request Line has information that contains the elements in the calling application that require a base and adjusted price. It may equate to a transaction line or transaction header record in the calling application. Refer to qp_engine_testing.sql
for information on setting up the request line data. LINE_REC_TYPE is the record structure that needs to be completed when passing information related to a request line.

  • Qualifiers and Pricing Attributes Information:

One must pass qualifiers and pricing attributes information that are needed by the pricing engine to determine the applicable price list lines and modifier list lines.   One may wish to reference  "Frequently Asked Questions (FAQ)
for Pricing Attributes Using Pricing APIs Such as Limitations, Request Type, How to Build Context When Using QP_PREQ_PUB.PRICE_REQUEST" (Doc ID 1094603.1).

Additional Resources:

  • For release 12 refer to the Oracle Order Management Open Interfaces, API, & Electronic Messaging Guide
  • For 11.5.10: Order Management - Open Interfaces, API, & Electronic Messaging Guide, B14446-01

    Available through Note 91798.1 Order Management Product Documentation
  • Note 759804.1 - HOW to Use QP_PREQ_PUB.PRICE_REQUEST API to Price an Item
  • Note  1094603.1 - How to Build Context for Pricing Attributes When Using QP_PREQ_PUB.PRICE_REQUEST
  • Note 1393917.2 -
    Information Center: Oracle Advanced Pricing, While on the Overview tab, click on the "Resources" link.

    This is where one will find documents on APIs that complement the Oracle Order Management Open Interfaces, API, & Electronic Messaging Guide.

    Scroll down and one will find a whole section dedicated to the price request API.

Available Options To Update the Order Upon Repricing

  • One could choose to use the Process Order API (OE_Order_Pub.Process_order).

      Refer to Note 1265721.1 - Process Order API - How To Scripts and/or

                  Note 1072272.1 - Can One Use oe_order_pub.process_order API to Create an Order Line With a Selling
    Price Different Than the List Price?
  • In addition, Oracle does provide a seeded Workflow Reprice activity that can be inserted anywhere in the line Workflow, the limitation of this approach is that it only contains a line level activity for repricing. If used, repricing each line is necessary
    and there is no possibility for a header level reprice.
  • Attribute changes on the order line can trigger the pricing engine to reprice the line.

    For a current list of these attributes, refer to Note 578902.1 What Sales Order Attributes Triggers Repricing
    in the Sales order Form? Note that a drawback of this approach is that changing some of these fields may also trigger defaulting rules and add some performance overhead.

Still Have Questions? 

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My
Oracle Advanced Pricing Community
.

REFERENCES

NOTE:759804.1 - HOW to Use QP_PREQ_PUB.PRICE_REQUEST API to Price an Item

NOTE:1393917.2 - Information Center: Oracle Advanced Pricing

NOTE:91798.1 - Order Management Product Documentation

NOTE:1265721.1 - Process Order API - How To Scripts

NOTE:1448751.1 - Qp_preq_pub.Price_request Is Not Showing a Discount Defined at Group of Lines Level

NOTE:578902.1 - What Sales Order Attributes Triggers Repricing in the Sales order Form?

NOTE:1072272.1 - Can One Use oe_order_pub.process_order API to Create an Order Line With a Selling Price Different
Than the List Price?

NOTE:1094603.1 - FAQ for Pricing Attributes Using Pricing APIs Such as Limitations, Request Type, How to Build
Context When Using QP_PREQ_PUB.PRICE_REQUEST

How to Simulate the Price Order or Price Line Function using API QP_PREQ_PUB.PRICE_REQUEST
Includes Example Scripts (文档 ID 412545.1)
转到底部

In this Document

Purpose
  Scope
  Details
  Example Scripts to Simulate Price Order
  qp_engine_testing.sql
  qp_test_service.sql
  qp_test_oid.sql

  qp_direct_insert.sql
  qp_manual_adjustments.sql
  qp_override_selling_price.sql
  The setup involves passing information
to the pricing engine using the following:
  Control Record Information:
  Request/Order Line Information:
  Qualifiers and Pricing Attributes Information:
  Additional Resources:
  Available Options To Update the Order Upon
Repricing
  References

APPLIES TO:

Oracle Advanced Pricing - Version 11.5.10 and later

Oracle Order Management - Version 11.5.10.0 and later

Information in this document applies to any platform.

PURPOSE

This note is intended to show how the Price Order or Price Line action may be simulated using an API call. This API call will not result in an update to the order.

SCOPE

The intended audience is for those with technical knowledge of Oracle Applications Code, the usage of public APIs, and those familiar with creating custom solutions for unique business requirements.

This is only a sample code and should be used to develop one's own code to meet business needs. Due to the fact this is  customized code, it is the Customer's responsibility to thoroughly test and to maintain their code. Oracle support may not be able to assist
with these scripts, hence if one is implementing a custom solution and requires assistance, please contact Oracle Consulting.

DETAILS

Example Scripts to Simulate Price Order

The following scripts are used in the examples for the Price Request Application Program Interface.

These scripts help one set up data and make a call to the pricing engine to return the price and any related discounts.

The scripts are located in the following area:   $QP_TOP/patch/115/sql.



Please note then if one upgrades to a new release of Oracle Applications one would need to acquire a new copy of the scripts (same directory) as these scripts may have changes as provided by Oracle Development to work within the new application version.  Therefore
if one used an example script to develop ones own script, for example, on Oracle Applications 11.5.10.2 and then upgraded to Oracle Applications 12.1.1, one would need to review the detailed example scripts for any changes needed.  These are only example scripts
intended to assist with writing of the code needed to call the API.  It is the customers responsibility to thoroughly test and provide final coding needed to achieve desired results to meet individual business needs.

Each script will contain a file version. 



For example, on Release 12.1.1 for example script in file qp_engine_testing.sql shows file version 120.0



REM/* $Header: qp_engine_testing.sql 120.0 2005/06/02 01:05:15 appldev noship $ */

wheres the same script qp_engine_testing.sql on Release 11.5.10.2 shows file version 115.3

REM/* $Header: qp_engine_testing.sql 115.3 2002/05/17 18:43:30 pkm ship $ */
  1. qp_engine_testing.sql

    (All regular Price Lists, Discounts , Surcharges etc.)

  2. qp_test_service.sql

    (Service Item Pricing Setup)

  3. qp_test_oid.sql

    (Other Item Discount Setup)

  4. qp_direct_insert.sql

    (Direct insertion into temporary tables to improve performance)

  5. qp_manual_adjustments.sql

    (Apply manual adjustments)

  6. qp_override_selling_price.sql

    (Override the unit selling price)

Note: Examples provided are from March 2014 from Oracle Applications R12.

The setup involves passing information to the pricing engine using the following:

  • Control Record Information:

The Control Record has parameters which control the behavior of the pricing engine. Please refer to the example scripts above for more details.

  • Request/Order Line Information:

Request Line has information that contains the elements in the calling application that require a base and adjusted price. It may equate to a transaction line or transaction header record in the calling application. Refer to qp_engine_testing.sql
for information on setting up the request line data. LINE_REC_TYPE is the record structure that needs to be completed when passing information related to a request line.

  • Qualifiers and Pricing Attributes Information:

One must pass qualifiers and pricing attributes information that are needed by the pricing engine to determine the applicable price list lines and modifier list lines.   One may wish to reference  "Frequently Asked Questions (FAQ)
for Pricing Attributes Using Pricing APIs Such as Limitations, Request Type, How to Build Context When Using QP_PREQ_PUB.PRICE_REQUEST" (Doc ID 1094603.1).

Additional Resources:

  • For release 12 refer to the Oracle Order Management Open Interfaces, API, & Electronic Messaging Guide
  • For 11.5.10: Order Management - Open Interfaces, API, & Electronic Messaging Guide, B14446-01

    Available through Note 91798.1 Order Management Product Documentation
  • Note 759804.1 - HOW to Use QP_PREQ_PUB.PRICE_REQUEST API to Price an Item
  • Note  1094603.1 - How to Build Context for Pricing Attributes When Using QP_PREQ_PUB.PRICE_REQUEST
  • Note 1393917.2 -
    Information Center: Oracle Advanced Pricing, While on the Overview tab, click on the "Resources" link.

    This is where one will find documents on APIs that complement the Oracle Order Management Open Interfaces, API, & Electronic Messaging Guide.

    Scroll down and one will find a whole section dedicated to the price request API.

Available Options To Update the Order Upon Repricing

  • One could choose to use the Process Order API (OE_Order_Pub.Process_order).

      Refer to Note 1265721.1 - Process Order API - How To Scripts and/or

                  Note 1072272.1 - Can One Use oe_order_pub.process_order API to Create an Order Line With a Selling
    Price Different Than the List Price?
  • In addition, Oracle does provide a seeded Workflow Reprice activity that can be inserted anywhere in the line Workflow, the limitation of this approach is that it only contains a line level activity for repricing. If used, repricing each line is necessary
    and there is no possibility for a header level reprice.
  • Attribute changes on the order line can trigger the pricing engine to reprice the line.

    For a current list of these attributes, refer to Note 578902.1 What Sales Order Attributes Triggers Repricing
    in the Sales order Form? Note that a drawback of this approach is that changing some of these fields may also trigger defaulting rules and add some performance overhead.

Still Have Questions? 

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My
Oracle Advanced Pricing Community
.

REFERENCES

NOTE:759804.1 - HOW to Use QP_PREQ_PUB.PRICE_REQUEST API to Price an Item

NOTE:1393917.2 - Information Center: Oracle Advanced Pricing

NOTE:91798.1 - Order Management Product Documentation

NOTE:1265721.1 - Process Order API - How To Scripts

NOTE:1448751.1 - Qp_preq_pub.Price_request Is Not Showing a Discount Defined at Group of Lines Level

NOTE:578902.1 - What Sales Order Attributes Triggers Repricing in the Sales order Form?

NOTE:1072272.1 - Can One Use oe_order_pub.process_order API to Create an Order Line With a Selling Price Different
Than the List Price?

NOTE:1094603.1 - FAQ for Pricing Attributes Using Pricing APIs Such as Limitations, Request Type, How to Build
Context When Using QP_PREQ_PUB.PRICE_REQUEST

How to Simulate the Price Order or Price Line Function using API QP_PREQ_PUB.PRICE_REQUEST Includes的更多相关文章

  1. HOW to Use QP_PREQ_PUB.PRICE_REQUEST API to Price an Item

    In this Document Goal   Solution   References APPLIES TO: Oracle Advanced Pricing - Version 11.5.10 ...

  2. Sample Code for Qp_preq_pub.Price_request Api to Simulate an Ask for Promotion Modifier

    DECLARE p_line_tbl QP_PREQ_GRP.LINE_TBL_TYPE; p_qual_tbl QP_PREQ_GRP.QUAL_TBL_TYPE; p_line_attr_tbl ...

  3. AMAZON PRICE TRACKER, AMAZON PRICE HISTORY, AMAZON PRICE DROP ALERT | DROPGG.COM

    DropGG.com is the destination for savvy shoppers looking to save money by buying smart. DropGG.com a ...

  4. mysql之group_concat函数详解

    函数语法: group_concat( [DISTINCT]  要连接的字段   [Order BY 排序字段 ASC/DESC]   [Separator '分隔符'] ) 下面举例说明: sele ...

  5. C# 自定义排序

    /// <summary> /// 实体 /// </summary> public class Product { public int ID { get; set; } p ...

  6. 用 SQL 对关系型数据库进行查询

    前面几节中,我们已经掌握了如何向 SQLite 数据库中写入数据.这一节,我们将学习如何根据需求对数据库进行查询,进而从中获取数据.接下来的例子中会使用 data/datasets.sqlite(之前 ...

  7. 第四模块MySQL50题作业,以及由作业引申出来的一些高端玩法

    一.表关系 先参照如下表结构创建7张表格,并创建相关约束                 班级表:class       学生表:student       cid caption grade_id ...

  8. mysql group_concat函数

    函数语法: group_concat( [DISTINCT] 要连接的字段 [Order BY 排序字段 ASC/DESC] [Separator '分隔符'] ) 下面举例说明: select * ...

  9. 【数据分析 R语言实战】学习笔记 第三章 数据预处理 (下)

    3.3缺失值处理 R中缺失值以NA表示,判断数据是否存在缺失值的函数有两个,最基本的函数是is.na()它可以应用于向量.数据框等多种对象,返回逻辑值. > attach(data) The f ...

随机推荐

  1. UDP单播和组播使用SO_REUSEADDR 测试结果

    UDP单播通信 一. 预置条件 A.B在同一台机器,网络中存在往A.B所在的机器的8888端口发送单播UDP数据 A:端口复用绑定在端口8888上 B:端口复用绑定在端口8888上操作步骤:(1)先启 ...

  2. Ubuntu14下安装svn仓库,以及权限配置

    sudo apt-get update 接下来安装svn apt-get install subversionapt-get install libapache2-svn 检查svn是否安装成功了: ...

  3. Java遍历时删除List、Set、Map中的元素(源码分析)

    在对List.Set.Map执行遍历删除或添加等改变集合个数的操作时,不能使用普通的while.for循环或增强for.会抛出ConcurrentModificationException异常或者没有 ...

  4. erMaster插件

    需求: 在做开源项目时,了解基本业务后.试图从数据库表设计来分析项目.通过visio时绘制操作繁琐,另外不能与数据库连动.于是想找一款快速绘制er图,并且能够和数据库连动的软件工具. eclipse插 ...

  5. 【Unity Shaders】游戏性和画面特效——创建一个夜视效果的画面特效

    本系列主要参考<Unity Shaders and Effects Cookbook>一书(感谢原书作者),同时会加上一点个人理解或拓展. 这里是本书所有的插图.这里是本书所需的代码和资源 ...

  6. [C]simple code of count input lines,words,chars

    This is a simple C program which can count input lines, words and chars. But the number of words are ...

  7. J2EE进阶(十二)SSH框架整合常见问题汇总(三)

    在挂失用户时,发现userid值为空,但是在前台输入处理账号22时,通过后台输出可以看出,后台根据前端输入在数据库中查询到结果对象并输出该对象的userid,而且Guashi对象也获取到了其值. 解决 ...

  8. 如何在Cocos2D 1.0 中掩饰一个精灵(五)

    大熊猫猪·侯佩原创或翻译作品.欢迎转载,转载请注明出处. 如果觉得写的不好请告诉我,如果觉得不错请多多支持点赞.谢谢! hopy ;) 掩饰和CCRenderTexture CCRenderTextu ...

  9. Mybatis源码之Statement处理器SimpleStatementHandler(四)

    SimpleStatementHandler就是使用基本的Statement来执行query.batch.update等操作,其实现还是比较简单的,当然在执行过程中会涉及keyGenerator和Re ...

  10. MySQL进阶(一)主外键讲解

    1.什么是外键: 作为外键的字段. REFERENCES:映射到主表的字段2. ON DELETE后面的四个参数:代表的是当删除主表的记录时,所做的约定. RESTRICT(限制):如果你想删除的那个 ...