Setting Up a Coupon Issue Modifier in Oracle Advanced Pricing

Oracle Advanced Pricing offers a flexible way to configure Coupon Issue Modifiers, allowing businesses to provide customers with redeemable coupons for future price adjustments or benefits. This setup ensures that promotional discounts are tracked and applied strategically.

Understanding Coupon Issue Modifier Setup

To create a Coupon Issue Modifier, you must set up two modifier lines within the same Modifier List:

1. Coupon Benefit Modifier – Defines the price adjustment or benefit (e.g., a 10% discount).

2. Coupon Issue Modifier – Defines the coupon details (e.g., name, expiration date, and conditions for redemption).

By linking these modifiers, Oracle ensures that coupons are issued only when the defined benefit applies.

Step-by-Step Setup Guide

Step 1: Create a Modifier List

1. Navigate to Oracle Advanced Pricing > Modifiers > Define Modifier.

2. Create a new Modifier List and define the header details:

   • Set Modifier Type to Promotion (this will act as the parent modifier).

   • Enter a Name (e.g., "Spring Sale Promotion").

   • Define the Effective Dates to control coupon availability.

Step 2: Set Up the Coupon Benefit Modifier

1. In the same Modifier List, create a new modifier line:

   • Modifier Type: Select Discount.

   • Benefit Definition: Set the discount as Percentage (%) or Amount ($).

   • Conditions: Define qualifiers like minimum order value or eligible items.

   • Automatic Flag: Enable to ensure the benefit applies automatically when conditions are met.

   • Save the record.

Step 3: Set Up the Coupon Issue Modifier

1. Add another modifier line to the same Modifier List:

   • Modifier Type: Select Coupon Issue.

   • Coupon Name: Define a recognizable coupon name (e.g., "Spring Sale $20 Coupon").

   • Expiration Date: Set the validity period for coupon redemption.

   • Coupon Modifier Number: Enter the Modifier Number of the Discount Modifier created in Step 2 (this links the coupon issuance to the applied discount).

   • Save the record.

Step 4: Validate Setup

1. Test with a Sales Order:

   • Create an order that qualifies for the Coupon Benefit Modifier (e.g., meets the minimum value for discount).

   • Ensure that the Coupon Issue Modifier applies correctly, issuing the coupon.

   • Review the Pricing History to verify modifier application.

2. Check Coupon Redemption:

   • Ensure the coupon can be used in a future order within the expiration period.

Key Considerations

• Both Coupon Benefit and Coupon Issue Modifiers must belong to the same Modifier List to function correctly.

• Proper Qualifier Setup ensures coupons are issued only for eligible transactions.

• The Coupon Modifier Number field in the Coupon Issue Modifier must correctly reference the Discount Modifier to link the benefit.

Test Modifier Setup 

Test Order line where Coupon got issued

Added another line and applied the previously issued coupon which applied a discount

Read More

In Oracle Order Management, pricing involves several key components that work together to define and apply pricing to orders. Here's an overview of the basic components:

1. Price Lists

• Price lists are the foundation of pricing in Oracle EBS. They define the base price for items and may include additional details such as currency, unit of measure (UOM), and effective dates. Key Attributes:

  • Item Price

  • Currency

  • Effective Period

2. Modifiers

• Modifiers are used to define additional pricing adjustments like discounts, surcharges, promotions, and freight charges. They help tailor pricing to specific business scenarios. Types:

  • Discounts (e.g., percentage, amount)

  • Surcharges

  • Promotions (e.g., buy one, get one free)

3. Qualifiers

• Qualifiers are conditions that determine when a price list or modifier should be applied. They enable flexibility by linking pricing to specific customers, regions, or order attributes. Examples:

  • Customer Groups

  • Item Categories

  • Sales Channels

4. Pricing Attributes

• Pricing attributes are additional fields or characteristics (e.g., ship method, order type) that refine how pricing is applied. They help define complex pricing scenarios such as formula-based pricing.

5. Secondary Price Lists

• Secondary price lists act as a fallback mechanism when items are not priced on the primary price list.

6. Pricing Formulas

• These allow for dynamic pricing by calculating prices based on formulas. For example, a formula might include factors like item cost, quantity, and region-specific adjustments.

7. Freight and Special Charges

• Pricing can include freight costs or special charges, calculated as part of the overall price based on shipping method, carrier, or other factors.

8. Customer Profiles and Agreements

• Customer-specific pricing agreements can be set up to define negotiated prices or discounts for specific customers or groups.

9. Adjustments and Overrides

• Users can apply manual price adjustments or overrides during the order process, provided they have the appropriate authorization.

Read More

Back to Back(B2B) process is used for items that are not typically stocked nor manufactured. In an environment where lead times are often only a matter of 24 hours, the B2B process improves efficiency of the three steps above, by closely linking the Sales Order and the Purchase Order together.

The B2B process automates the creation of a supply order (PO) when a sales order is booked. The supply order is hard pegged (hard-reservation) to the sales order that it is supplying so that once the PO is received, the items are not inadvertently taken by another order or demand. Where the sales order line is within the process, can be visible at all times so that customer service inquiries can be answered. 

This process is also called Supply to Order.

1. Customer orders items (OM).
2. Purchase those items from the supplier (PO) and receive them into the warehouse.
3. Ship those items to the customer (OM).

Create a B2B Item

Go to Inventory > Items > Master Items and define the item as follows :
Enter item name and description.
From Tools > Copy From, apply the Purchased Item template.

 In the Purchasing tab, enter a value in the List Price field.

 In the General Planning tab, set the Make or Buy flag to Buy

 In the Work in Process tab, make sure the Build in WIP flag is checked

  In the Order Management tab, check the Assemble to Order flag (ATO).

Save, and assign to Organization M1

B2B item must be created at item validation org.
Same item in same item validation org cannot be both stock item and a B2B item

Define Sourcing rule for the item

Sourcing rules can be set up in PO to default sourcing information such as the supplier from which the item is purchased.

Assign the item to the price list

Back to Back Order Flow

Create Order

Go to OM > Orders, Returns > Sales Orders.

Create a sales order with Order Type Mixed and enter the B2B item created in previous step in the lines for any quantity.
Book the order. Note down the Order Number

 The line status will move to Supply Eligible (flow_status_code SUPPLY_ELIGIBLE).

Place cursor on the line and go to Actions > Progress Order > Select Create Supply Order - Eligible to progress the workflow of the line 

 

The line status will now show PO-ReqRequested/External Requisition Requested (flow_status_code PO_REQ_REQUESTED).

OM has inserted a record in the PO requisitions interface table.

Go to Purchasing > Reports > Run and run the concurrent program Requisition Import with the Import Source parameter = CTO. Leave the other parameters as default. The concurrent program can also be run from OM > Orders, Returns > Requisition Import.
Go to View > Requests and verify that the Requisition Import has completed successfully.

The line status of the sales order line will now show PO-ReqCreated/External Requisition Open (flow_status_code PO_REQ_CREATED)

From the sales order line, go to Tools > Scheduling > Reservation Details > 'Supply' tab. Verify that the order line is reserved against the requisition. Note down the requisition number seen in this window.

Go to Purchasing > Requisitions > Requisition Summary.

In the Find Requisitions window, enter requisition number found in the previous step and click on Find.
Verify that the status is Approved

Go to Purchasing > Autocreate.
From Edit > Clear > Record, clear any query criteria that may be defaulted like buyer, requester etc.
Enter requisition number and click Find.

  

Check the checkbox to the left of the line, and click on Automatic. Enter the Supplier and Supplier site such as the following and click on Create

 Once the PO created, enter the supplier and site details and once everything is OK, approve the PO

The line status of the sales order line will now show PO-Created/PO Open (flow_status_code PO_CREATED)

From the sales order line, go to Tools > Scheduling > Reservation Details > 'Supply' tab. Verify that the order line is reserved against the PO

Go to Purchasing > Receiving > Receipts.

Enter Purchase Order number and click on Find.
In the Receipts window, check the checkbox to the left of the line and enter and save the receipt

Go to Purchasing > Receiving > Receiving Transactions Summary.

Enter the Purchase Order number and click on Find.
Click on the Transactions button.
Verify a Receive and Delivery transaction. This means that the B2B item has been received into Inventory.

The line status of the sales order line will now show Awaiting Shipping (flow_status_code = AWAITING_SHIPPING).

On the sales order line, Tools > Scheduling > Reservation Details will now show that the item is reserved against Inventory in Subinventory = FGI (PO has been received in this subinventory).

The line can now be pick released, shipped and invoiced to the customer.

This completes the Back to Back Order workflow.

Useful queries

Once you progress the order after Supply Eligible step, use below query to find whether the data inserted to requisition interface or not

select * from po_requisitions_interface_all
where interface_source_line_id = &order_line_id
and interface_source_code = 'CTO';

Read More

Pick Release is the process of Picking the order for ship confirming.
This process includes 3 parts, Move Order creation and Move order Allocation and Move order transaction.

When you do a pick release, it will create a move order, as per the details you have provided in the picking process, it will allocate the move order from the satisfied subinventory, locator, lot, serial, LPN.
And as per the criteria (whether auto pick confirm is Yes or No), it will transact the move order as well.

So in Shipping transaction form, the flow will happen like this

1. Ready to Release: The order is booked and ready and you can run the pick release on this
2. Released to Warehouse: Once you did pick release and if the pick release successful, it will be changed to Released to warehouse. Also if no order satisfies the criteria what you have given, then the status will remain as it is. If Auto Pick confirm is set as Yes, this satus will never come and it will move to next status Satged/Pick released.
3. Backordered: If there is no satisfied source find during the process of pick release, delivery details will be back ordered.
4. Staged/Pick Confirmed: Once pick release process including pick confirm completes (depends on the Auto pick confirm flag), status will be changed to this.

Auto Pick Confirm flag under shipping tab

Mostly this flag was kept as No for Warehouse enabled Organizations, so that the physical pick and drop process can be done from the physical location through Paper based picking or task directed picking. When this flag is No, after pick release, the status in shipping transaction form will be released to warehouse and as per setup pick slip will be printed. Warehouse operator will do the Pick and Drop transaction using the data from the pick slip in MSCA.

Also even if it in not WMS enabled organization, still if you need to manually do the Move order transactions and if your business has some checks, then also you can keep the flag as No.

If the flag is set to Yes, during pick release, system will do the move order transaction as well and status in shipping transaction form will be staged/pick confirmed. Which means pick release is complete and order/delivery is ready for shipping.

Pick release can be done in different ways
Navigation:
Order Management --> Shipping --> Release Sales Order

Using Release Sales Orders form

Here you can enter all required parameter and release the orders either in concurrent or in online method.
In this method, you can pick release individual orders and restrict them with different parameters in the order tab.

In the Shipping tab, you can select how you want to handle the picking batch, whether you want to auto create delivery, whether you want to auto pick confirm, if you want to auto ship confirm the order from this form, also you can do so, if you select Auto pick confirm as Yes and using a ship confirm rule.

You can even restrict or specify certain other parameters like ship method and which sequence rule you want to use.

In the Inventory tab, you can specify from which warehouse, subinventory, locator you want to pick from and which subinventory and locator you want to stage in.

Also you can choose allocation method here whether inventory or cross-docking.

Here you can use business required predefined pick slip grouping rule as well to group the pick slips.

Using Release Sales Orders SRS

Pre-req for this process is to have your Pick release rule defined before hand (explained below).

Benefit of this method is, you can release multiple orders in one request just using a required release Rule name which satisfies your current business need which you have already defined in system.

Note: If you have many Release Rules defined for your business and you want them to be scheduled and executed one by one. You can consolidate all requests in one request set one by one and schedule that request set.

Define Release Rule Form:

Navigation:

Order Management --> Setup --> Shipping --> Picking --> Define Release Rule Form

Pick Release rule is nothing but the predefined pick release rule with all specific restrictions and attributes depending on your business needs.

This form is exactly like the Pick release form we discussed above. The same criteria, same restrictions can be used her as well. But here, you can define the rule, so that instead of manually selecting those criteria, every time, you can use the pre-defined release rule.

You can define multiple release rules with all set of parameters like for different customer, different item category, and all type of business requirements and use the same for Pick release from using the Form or Pick release through SRS.

Post pick Release and Debugging

Post Pick release execution, if any exception occurred, you can find those details in below table

select * from WSH_EXCEPTIONS;

Tables involved in pick release are below

You will be able to find the pick release batch details like what restrictions,, attributes used for the pick release.

SELECT * FROM WSH_PICKING_BATCHES;

Other tables involved here as well for delivery are

WSH_DELIVERY_DETAILS

WSH_DELIVERY_ASSIGNMENTS

WSH_NEW_DELIVERIES

If you want to check which release rules used for which order and what is the pick release batch for your sales order, you can use below script

------------------------------

SELECT wdd.source_header_number,

       oel.line_id,

       mp.organization_code,

       wpb.name,

       mtrl.creation_date,

       mtrl.last_update_date,

       mtrl.request_id mtl_req_id,

       wpb.request_id pick_batch_req_id,

       wdd.batch_id pick_batch_id,

       oel.ship_set_id,

       (select user_concurrent_program_name

          from apps.fnd_concurrent_programs_tl

         where concurrent_program_id =

               (select concurrent_program_id

                  from apps.fnd_concurrent_requests

                 where request_id = nvl(mtrl.request_id, wpb.request_id))) prog_name,

       decode((select concurrent_program_id

                from apps.fnd_concurrent_requests

               where request_id = nvl(mtrl.request_id, wpb.request_id)),

              1003890,

              (select PICKING_RULE_NAME

                 from apps.WSH_PICKING_RULES_V

                where picking_rule_id =

                      (select argument1

                         from apps.fnd_concurrent_requests

                        where request_id =

                              nvl(mtrl.request_id, wpb.request_id)))) rel_rule

  FROM apps.wsh_delivery_details  wdd,

       apps.mtl_txn_request_lines mtrl,

       apps.oe_order_lines_all    oel,

       apps.wsh_picking_batches   wpb,

       apps.mtl_parameters        mp

 WHERE wpb.batch_id = wdd.batch_id

   AND mtrl.line_id = wdd.move_order_line_id

   AND wdd.released_status IN ('S', 'Y', 'C')

   AND wdd.source_code = 'OE'

   AND wdd.source_line_id = oel.line_id

   AND oel.line_id = &LINE_ID

   and oel.ship_from_org_id = mp.organization_id;

---------------------------------------------------------------------------

Read More

Pick Wave is the process of Picking a Group of orders which can be released to different warehouse operator with the use of Pick Release rule WMS Pick rule and WMS Task assignment rule.
Wave picking is a term for a process used in a warehouse management system to describe a process to support managing the work of a warehouse or distribution center. Wave picking is an application of short interval scheduling, to assign orders into groupings (waves) and release them together so as to allow management to coordinate the several parallel and sequential activities required to complete the work.
The individual orders in the wave are dependent on the criteria used to make the selection.

The wave data includes the workload by order or function (case picking, repack picking, pallet movement, pick position replenishment, packing, etc.), providing management the information to calculate staff requirements and assign staff by function, with the expectation that the work in each function, within each wave, can be started and be completed at about the same time. There are two basic planning elements and benefits of wave picking.
To organize the sequence of orders and assignment to waves, consistent with routing, loading and planned departure times of shipping vehicles or production requirements, etc., to reduce the space required for shipping dock handling to assemble orders and load; and
To assign staff to each wave and function within a wave, with the expectation that all the work assigned to each wave will be completed within the wave period, providing management with the ability to monitor and manage performance throughout the day, and respond in a timely way to problems that occur, and more effectively utilize the staffing throughout the shift.
Material handling methods and equipment are independent of waving. Each set of method (e.g., order pick, batch pick, bulk pick) and equipment (e.g.,conveyor and sorter, ASRS, order picker, pallet jack, fork lift) will yield a different expected productivity rate for management to use in determining the number of staff-hours to assign to each function by wave.

Additional benefits of wave picking include the improved ability to

• measure productivity within a function
• budget labor
• estimate the throughput capacity based on staffing levels
• evaluate the impact of changes in methods and equipment by function
• provide feedback regarding performance
• Better understand the nature of the workload as it changes seasonally, as a consequence of demand, and as a consequence of sales efforts and marketing campaigns

Read More

Document Printing

In most of the oracle process, we need documents to be printed.

For example, during shipping, we need pick slip and pack slips to be printed in the warehouse or shipping doc.

Many business do they have multiple printers setup in the warehouse in different zones for the convenience of order fulfillment.

As per the requirement, oracle has given the flexibility to assign printers to the documents.

Below pre-requisites needed for automated document printing

• Required Document Report needs to be defined and registered in oracle
• Printer to be used in the warehouse needs to be defined and installed in the network
• Printer needs to be connected on proper ip in the network

Assigning Printer to the Document

You can assign shipping documents and selected reports to specific printers. For example, you can assign pick slips and pack slips to your warehouse tractor feed printer, your mailing labels to a tractor feed printer stocked with blank labels, and other documents to a laser printer in your order entry office.
You can assign each shipping document and report to a different printer for each user, responsibility, application, or site. If a user or responsibility is not specified, Oracle Order Entry/Shipping uses the printer that you indicate for the application.

Navigate to the Order Management Super user responsibility

Setup --> Shipping --> Documents --> Choose Printer

Expand the Document Option and select the document name for which you want to assign a printer

Here you have multiple flexibility to choose a printer in different level.

You can choose a printer at below levels

• You can choose from Site, Application, Responsibility, or User
• If you select Responsibility or User in the Level field, choose the specific name in this field. If you select Site or Application in the Level field Oracle Order Entry/Shipping displays the name of your site, or Oracle Order Entry, and skips to the next field.
• Select the name of the printer to which you want the shipping document to print.
• Check the Enabled check box to activate the printer assignment

Do the setup as per your convenience.

Read More

Oracle Order Management Setups

Oracle Order management is one of the most important part of the oracle EBS. The Order Management Application provides many flexible features enabling you to set up your system to begin processing order information. These orders can be created in Oracle Order Management Suite as well as in some other front-desk application. We can integrate these applications with Oracle Order Management for keeping a controlled track of orders and proper business flow. We can create different types of orders using this application can be for inventory stock items or for services.
You must define your business order policies, such as how you classify your orders, as well as various control features prior to processing orders within the application.

Important Setup Steps for Order Management

Click on the links to go to individual setup steps

Step	Optional or Required
1. Define multiple organizations in Oracle Inventory	required
2. Setup Multi-Org (Multiple Organization) Access Control	optional
3. Define key and descriptive flexfields	required under certain conditions
4. Define inventory organizations (warehouses), parameters, subinventories, and picking rules in Oracle Inventory	required
5. Define Profiles	required
6. Setting OM System Parameters	required
7. Define invoicing information, Payment Terms	required under certain conditions
8. Define your sales representatives	optional
9. Define Tax Features	required
10. Define Quickcodes	required under certain conditions
11. Define header and line processing flows	required
12. Define Document Sequences for Order Numbering	required
13. Define Order Import Sources	required under certain conditions
14. Define the units of measure	required
15. Define item information	required
16. Define the items that you sell	required
17. Define the configurations that you sell	required under certain conditions
18. Define price lists	required
19. Define customer profile classes	required under certain conditions
20.Define information on your customers	required
21. Define item cross references	required under certain conditions
22. Define your sourcing rules	optional
23. Define Order Management Transaction Types	required
24. Set up Cost of Goods Sold Accounting flexfield combination	required under certain conditions
25. Define Processing Constraints	optional
26. Define Defaulting Rules	optional
27.Define Credit Checking Rules	required under certain conditions
28. Define Automatic Holds	required under certain conditions
29. Define Attachments	optional
30. Define Freight and Special Charge Types	optional
31. Define shipping parameters	required

Read More

Types Of Move Order

Move orders are created from different sources.

This can be identified from the Move Order header move order type field.

Different types of Move Orders are 

Move Order Requisitions: 

These are created from the move order form. Based on the setup at the organization and item level, move orders require approval before they can be allocated and transacted. These requisitions can be created to charge an account or move the material from one subinventory to another.

Replenishment Move Orders: 

These are auto-created with pre approved status. Depending on the planning type you can replenish the quantity in a subinventory for an item. Three types of replenishment plans (in relation to move orders) are available:

• Min-max Replenishment Planning
• Kanban Replenishment Planning
• Replenishing Count planning

Based on these sources, when appropriate programs are run, move orders are automatically created.

Pick Wave Move Order Requisitions: 

These move orders are specifically for the sales order picking process. When Pick Releasing program is run move orders are created as preapproved and allocated(depending on the Pick Release setup). Pick Confirm process transacts these pick wave move orders.

Read More

Internal Requisition to Internal Sales Order

Creation Of Item

Create an Item and assign that to both the source and destination organization

Attributes

• Purchased
• Purchasable
• Internal Order Enabled
• Shippable
• OE transactable

Creation of Internal Requisition

Now go ahead and create and Internal Requisition

Go to Purchasing Responsibility

Requisitions -> Requisitions

Note: You should have been defined as an employee/ buyer to create a requisition

1. Type should be Internal Requisition
2. Enter the item in Lines Tab
3. Enter Quantity
4. Enter Need By Date
5. Select the Destination Organization
6. Destination Location
7. Select Source Organization

Click on Save, It will generate the Requisition Number. Note down the requisition number
Now need to Approve the Requisition
If you want to approve this requisition, then you should have required approval authority.
Lets do the required setup
Go to Human Resources (if Installed) responsibility
People -> Enter and Maintain

else in purchasing
Go to Setup -> Personnel -> Employees
Find the employee (if not created already, select new and create one)

Select Assignment

Here assign a Job

Now lets go and check whether this Job has Requisition Approval authority or not

For this, navigate to Purchasing responsibility

Setup -> Approvals ->Approval Assignments

In this form, select the Job which you have assigned to the employee

Now you can see which all document types are authorized to approve

Make sure Approve Internal Requisitions is entered here

If you can’t see this, then add the value

Make sure the Approval Group which you are assigning here that has the approval limit authorization with in which your IR amount comes

As in this case

Here the limit is max $50,000 and our IR amount is only $100

Now Go back to the requisition and approve the same

Query the requisition and click on the approve button

Make sure Submit for Approval selected (it should be by default) then click on OK

Wait for few min as the background process will check and clear the Approval workflow

And re-query the IR again

If Workflow Background Process not scheduled, you can go ahead and manually submit

Now again requery the IR from requisition summary form

You will see the IR is approved

Creation of Internal Order

Next step is to Run the Create Internal Order concurrent program which will interface the data to Order management for creating internal order

Go to View -> Requests -> Submit a new request -> Single Request

Select Create Internal Orders and submit

Once the program is completed, check the log file,

It means the data transferred to Order Entry

Now lets go to Order Management and import the data to create the Internal Order

Navigate to Order Management responsibility

Go to Orders, Returns -> Import Orders -> Order Import Requests

Now enter the below parameters

1. Source as Internal
2. Select your IR number in Order Reference field

Then Click Ok and Submit.

This will spawn another child order import program

Now go ahead and query your Internal order which is just created by importing the data in order organizer form

Orders, Returns -> Order Organizer

Give today’s date to refine

Select the source as Internal and give the IR number in the Order Source Reference

Now Click on Open.

Your internal order is ready

Tables Involved in this process flow

Differences between Internal Sales Orders and Inter-Organization transfer:

• IR-ISO has approval process whereas there is no approval process for Inter-Org transfer
• The IR cycle useful for more tracking, control (IR, SO), approvals and generating pick slips whereas Inter-Org transfer is a one step transaction, simple flow, more user friendly and no interfaces involved.
• RMA is possible in Internal Sales Order whereas in Inter-Org transfer there is no functionality to Cancel, delete or Return or not receive an In-transit Shipment.

When Internal Sales Order and Internal Requisition will be picked up by Inter-Company invoicing process?

Internal sales order and Internal requisitions will be picked by Inter-company invoice process on the following conditions:

• In shipping method, transfer type should be Intransit
• Profile Option INV:Intercompany Invoice for Internal Orders value is Yes on site level. This will be used for creating Account Payable in the Intercompany Invoice process.

Note: Intercompany AP will be created irrespective of the IR received or not as per the standard functionality, INCIAP does not check for the same, it considers only INCIAR created or not.

Below query can be used to find out the eligible records

SELECT RCTL.*

FROM ra_customer_trx_lines_all RCTL, mtl_intercompany_parameters MIP
WHERE RCTL.interface_line_context = 'INTERCOMPANY'
AND RCTL.interface_line_attribute15 = 'Y'
AND RCTL.interface_line_attribute4 = nvl(93,
RCTL.interface_line_attribute4)
AND MIP.sell_organization_id = to_number(RCTL.interface_line_attribute4)
AND MIP.ship_organization_id = to_number(RCTL.interface_line_attribute5)
AND MIP.flow_type = 1
AND MIP.vendor_id is not null
AND MIP.vendor_site_id is not null
AND (line_type != 'TAX' AND extended_amount != 0)
AND NOT (line_type = 'TAX' AND link_to_cust_trx_line_id is not null);

Read More