CST is not getting picked up in sales order

Dear Experts,
We are following TAXINN procedure and we have maintained condition record for excise condition type - JEXP, JECS & JA1X and tax condition types - JIVC and JIVP. But in sales order, Excise condition types and Vat is getting picked automatically for local customer. But if I chose a CST customer CST is not getting picked automatically even though I have maintained condition record for the same. I have told my client to use alternative tax classification but my client doesnt want to follow this procedure.
Kindly let me know, how can I make the CST to be picked automatically in sales order.
Thanks & Regards,
Reji S

Dear Reji,
These may be the possible areas for the issue.
1.Check the ship to party Tax classification in the customer master>Sales area data>billing tab.
2.Check the Tax classification of the material master-->Sales org data view.
3.Check the region of the ship to party.
I hope this will help you,
Regards,
Murali.

Similar Messages

CESS and VAT not getting picked automatically in Sales Order and Quotation

Hi Experts,
Whenever we create quotation or sales order the Excise Duty, Cess and VAT/CST has to pickup automatically but it is not happening.Sold to party belongs to TN and Karnataka states are picking up properly but not other states.
Regards
Rajeshwari Shenoy

Check if Condition record are maintained, so that it is picked in Sales order. When it is working fine for TN & Karnataka, it is most likely that condition record is not maintained.
Regards,
Rajesh Banka
Reward points if helpful

Issue with freegood item exclusive not getting picked up in the order

Dear experts,
I have done a setup for freegood and activated the freed good functionality in the order.
I have added a material which is different from the standard product. However, the ssyetm doesnt pick
up the added product in the sales order but always the repeats the main product in the next line item.
I want that the system, the time I entered the main material, automatically picked up the free goods exclusive materail in the next
line item.
I dont know what I am missing here.
Thanks for the advice.
Cheers

Hi,
Please check the condition records foro your free goods in VBN1 transaction
whether you have maintained in Exclsive or not
in exclusive view check whether the FREE GOOD category is exclusive and maintain the Additional material in the field AddMat FrGD
thanks,
santosh

MWST not getting determined in CRM Sales Order

Hi All,
I am working on a scenario where we are using MWST for tax calculations. I am able to get the tax calculations correctly in ECC but when I create a Sales Order in CRM, MWST is not getting determined.
I have maintained the following
1) Downloaded the ECC customizing into CRM
2) Downloaded the pricing procedure into CRM
3) Downloaded the pricing conditions into CRM
4) Downloaded the pricing condition tables into CRM
5) Maintained the tax classification for Business Partner
Thanks in advance.
Regards,
Sandeep

Hi Sandeep,
did you try to use the price analysis in SAP GUI (set user parameter PRC_TRACE = X in SU3) to get further details what is missing for MWST determination? There could be multiple reasons for this issue.
Best Regards,
Michael

Right item category not getting copied while copying sales order

Hi,
We have a scenario where we are coping an existing order document and maintaining a new order document.
The problem is that when we are copying the existing order, we ll not get the same item categories in the copied order as available in the original order.
The Free of Cost item categories of the materials got changed to the normal item categories, which should not happen.
Let me know if any configuration changes made in system can fix this issue.
Cheers!!!
Ajay

Hi,
This may be due to copycontrol between these two sales order. In copy controls, you are retriggering the item category determination.
When you define the copy control from SO to SO, select the item category and keep the source and target item category as same. (Same for schedule line category also). Once this is done, your problem will be solved.

ATP Tree Structure is not getting created automatically after Sales Order is saved

In one one of our scenario, when we add material to Sales Order and save with Requirement Type(under Procurrement Tab of Sales Order) , in APO there is no planned order or only planned order which is dynamically pegged created because the ATP Tree in APO is not being converted. There is no pegging relevant item create(e.g. Planned Order). When we are checking the persistent ATP Trees in APO (/SAPAPO/ATREE_DSP - ATP-Trees) we can see that they are not converted automatically. They are still there. If we do it manually via transaction (/SAPAPO/RRP_ATP2PPDS - Conversion ATP Tree Structures -> Production Planning) it works. Afterwards the Planned Order is available and fixed pegged.
Why is APO not converting the ATP tree automatically ?
I also checked the scheduling horizon for conversion of the ATP Tree and it is correct: Is there any relation with Check Mode setting under ATP tab in Material Master?

Hi Prasad ,
This enables you to debug the ATP tree . If you have created an entry here with your user name then it will not let ATP tree get converted into PP/DS orders automatically .
It's very surprising because all seems fine . Just cross check all the settings once with below .
The conversion time depends on the following horizons and dates:
· PP/DS Horizon
· Scheduling horizon for the conversion of ATP tree structures
· Requirements dates in the ATP tree structure
PP/DS immediately converts the ATP tree structure when the sales order is saved
· If the earliest requirements date for components is within the scheduling horizon or
· If the latest requirements date for finished products is within the PP/DS horizon
If none of these conditions are fulfilled when saving the sales order, the system saves the ATP tree structure in SAP APO. In this case you can only convert the ATP tree structure online or in the background when one of the conditions given above is fulfilled. Here, there is an offset for the horizons with which you can achieve an earlier conversion.
You maintain the scheduling horizon for the conversion of ATP tree structures in Customizing for Production Planning and Detailed Scheduling under Maintain Global Parameters and Defaults. You maintain a location product specific PP/DS horizon in the location product master. If no location product specific PP/DS horizon exists, the system uses the PP/DS horizon from the planning version. You maintain these in Model and Planning Version Management.
Love Singh

Urgent !plant is not getting popluated automatically in sales order

Hello,
Plant is not getting poplulated at item level in sales order.
I have checked
1.CMir -->not maintained
2.CMR-->not delivery plant is mainatined
3. MMR ->delivery plant is maintained.
need your advice on this.
Thanks

Hi ,
Please maintained delivery plant in Customer master record for ship to party .
GOTO XD02 , SALES TAB - SHIPPING SCREEN
This will flow in sales order .

Items not getting picked up in Return sales order

Dear all,
I am creating a return sales order with reference to a sales order.
In my delivery doc the items can be categorised into 3 types:
1- Picking done; Movement type determined
2- Picking done; Movement type not determined
3- Picking not-done; Movement type determined
In the return order, only the items of 1st type are coming. Why others not getting picked up? Can they be entered manually?
regards
Sapshed

Dear Hrishikesh,
Thats Ok. Picking is done only for those items for which Relevant for Picking is ticked.
What I want to know is that, for items that have either their picking not done or Goods movement not determined, they are not getting automatically picked up while I create a Return order w/r to a sales order.
thanks
Sapshed

Sales Order not getting Pick Release and getting BACKORDERED

Hi Gurus,
There is an order in oracle production. When user try to Pick Release this order the order is not getting picked instead it is getting backordered. The line quantities are available and it is also not in hold. I also see the log files of ‘Pick Slip Generation report’, but it shows no error message. Do you have any idea on this?
Thanks,
SamD

Are the quantities in a reservable subinventory?
If you go to material workbench, does the quantity show as available to reserve?
Did you specify a subinventory in the release process?
Does the sales order line have a subinventory on it?
Check if your onhand is in staging subinventory?
Check older threads on this issue such as http://kr.forums.oracle.com/forums/thread.jspa?threadID=603998
Sandeep Gandhi

GL Account is not getting picked by billing document

Hi Gurus,
one new GL account is set up by our FI team for a accrual condition type.
case 1:
Now when i have cancelled the previous created billing doc and trying to create again then the new GL account is not getting picked.
case 2:
Whereas when am doing the complete process flow like sales order creation, delivery and billing then the new GL account is getting picked.
Could you please let me know what would be the reason for this, why its not getting picked in first case.
Thanks,
Ashi

Hello Preety,
Unless you see the Revenue Account Determination Analysis for the Billing document, it is very difficult to understand the reason. Please click on the Environment >> Acc.Determination Analysis >> Revenue account in the VF03 screen and find the missing assignment.
Thanks,
Suman$

EXW price is not getting picked up during preference determination

HI .. all,
We have transferred Sales order from ECC to GTS. But during prreferrence determination, EXW price of the Sales order is not getting picked up.
Please suggest if any configuration is missing .
Thnks in Advance .

Hi Sapcongts,
Of course you should not modify standard SAP code, and I will not help you to do that.
I don't agree with your idea of proposed and actual EXW values. The Sales Order is your way of recording the customer's Purchase Order, and the price should be fixed at that point. The billing process should not change the agreed price of the goods - only perhaps re-calculate taxes and any other charges that could not be confirmed at the time of order.
If your standard prices are offered as FOB, then I can understand your needing to subtract some components to reach the EXW price, but in that case you will have problems transferring the correct amount to GTS. As I mentioned earlier, you can manipulate the data in the BAdI /SAPSLL/IFEX_SD0A_R3, but I had not looked closely enough at this specific requirement. Unfortunately the pricing table KONV is not provided in the BAdI and that data will not yet be available in the database. Provided the elements to be subtracted are to be read from Master Data, then you could make that same subtraction again in the BAdI. But if there are complex dependencies, it might not be easy.
Having looked in more detail at the code, I think you would be reasonably entitled to complain to SAP about missing functionality here. In the ERP system, the SD pricing provides a specific sub-total (KOMP-PREVA: subtotal 8) for Preference Value, and you can easily configure that to be filled after your subtractions. But that subtotal is not used in the GTS mapping, and I think that's a mistake. You might want to create an OSS message about it, requesting that the GTS Preference value be taken from the sub-total that was clearly designed exactly for that purpose.
In any case, good luck with the project.
Regards,
Dave

Billing pricing not getting picked up

I created a sales invoice with reference a sales order. In the sales order the price was getting picked up and was displayed.
Delivery was also created. But when the invoice was created and saved the net value is shown as 0. Price is not getting picked up.
The option which many other consultants has given was to cancel the invoice and re create a new invoice. But we want the price to be picked in the same invoice.
This happened only for 5 invoices which was created on a particular day. These 5 inovices show a net value of 0.
Could you please help me out to resolve this issue.
Thanks very much.

Hi,
Please check if the document pricing procedure is same for Order type and billing type.
If its not same please check what is the pricing procedure system taking for Billing document procedure.
In that pricing procedure check what is the Base price condition type.
Check whether condition records maintained for that condition type.
Iff no records maintain then use VK11 to create new condition records.
Then go to Item data - Conditions in billing document press Update button and use B-Carry out new pricing.
Revert if you need more elaborate explanation.
Best Regards,

Serices Material is not getting picked Up in Proforma Invoice

Hi..
While craeting proforma invoice for serices,service material is not getting picked up..
where can be the settings?
Thanks
Manoj

Check if the item category is maintained in copy control from Say Sales Order to Proforma Invoice. T.Code: VTFA. If Item Category not maintained, then maintain it appropriately.
Regards,
Rajesh Banka

Release Strategy for Contract is not getting picked whereas it is ok for PO

Dear Experts,
I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
Kindly resolve the issue.
Satish

S0004830404 wrote:
Dear Experts,
>
> I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
> I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
>
> Kindly resolve the issue.
>
> Satish
hi,
use create other characteristic for value CEKKO-GNETW in this use the mk , wk values in value field and assign this characteristic to your class and save.
Thanking you

Index is not getting picked even after providing hint

Hi All
The index pk_sku is not getting picked even after providing the hints when executing the query.Please kindly give me such recommendations.I am providing the information.
select * from
(select /*+ index(s pk_sku) */
      to_char(t.dstamp, 'YYYYmmDDHH24MI') as sort_1,
      t.client_id as CLIENT_ID ,
      t.site_id as SITE_ID,
      tz.time_zone_name as TIME_ZONE_NAME     ,
      t.owner_id as OWNER_ID,
      t.sku_id as SKU_ID,
      t.reason_id as ADJUST_TYPE,
      to_char(t.dstamp+tz.diff/24, 'DD/mm/YYYY HH24:MI') as ADJUST_DATETIME,
      t.reference_id as RECEIPT_ID,
      t.batch_id as BATCH_ID,
      t.update_qty as UPDATE_QTY,
      t.lock_code as LOCK_CODE,
      s.description as SKU_DESCRIPTION
from mv_inventory_transaction t
      JOIN timezone tz ON tz.site_id = t.site_id ,
       mv_sku s
where   t.sku_id= s.sku_id
and     t.client_id=s.client_id
and   ( :client is null or :client = t.client_id)
and    ( :site is null or t.site_id in (:site))
and    ( :owner is null or t.owner_id in (:owner))
and    t.code= 'Adjustment'
and   (t.dstamp+tz.diff/24) between to_date(:dateFrom, 'DD/mm/yyyy') and to_date(:dateTo,'DD/mm/yyyy')+1
and      (:sku is null or t.sku_id in (:sku))
UNION ALL
(select /*+ index(s pk_sku) */
     to_char(t.dstamp, 'YYYYmmDDHH24MI') as sort_1,
    t.client_id as CLIENT_ID ,
      t.site_id as SITE_ID,
                      tz.time_zone_name as TIME_ZONE_NAME     ,
      t.owner_id as OWNER_ID,
      t.sku_id as SKU_ID,
      t.reason_id as ADJUST_TYPE,
      to_char(t.dstamp+tz.diff/24, 'DD/mm/YYYY HH24:MI') as ADJUST_DATETIME,
      t.reference_id as RECEIPT_ID,
      t.batch_id as BATCH_ID,
      t.update_qty as UPDATE_QTY,
      t.lock_code as LOCK_CODE,
      s.description as SKU_DESCRIPTION
from mv_inventory_transaction_arch t
      JOIN timezone tz ON tz.site_id = t.site_id,
       mv_sku s
where   t.sku_id= s.sku_id
and     t.client_id=s.client_id
and   ( :client is null or :client = t.client_id)
and    ( :site is null or t.site_id in (:site))
and    ( :owner is null or t.owner_id in (:owner))
and    t.code= 'Adjustment'
and   (t.dstamp+tz.diff/24) between to_date(:dateFrom, 'DD/mm/yyyy') and to_date(:dateTo,'DD/mm/yyyy')+1
and      (:sku is null or t.sku_id in (:sku))
order by sort_1,2,3,4,5
version = Release 10.1.0.5.0
SQL> sho parameter optimizer
NAME                                 TYPE        VALUE
optimizer_dynamic_sampling           integer     2
optimizer_features_enable            string      10.1.0.5
optimizer_index_caching              integer     0
optimizer_index_cost_adj             integer     100
optimizer_mode                       string      ALL_ROWS
sho parameter db_file_multiblock_count_read
sho parameter cursor_sharing
SQL> sho parameter optimizer
NAME                                 TYPE        VALUE
optimizer_dynamic_sampling           integer     2
optimizer_features_enable            string      10.1.0.5
optimizer_index_caching              integer     0
optimizer_index_cost_adj             integer     100
optimizer_mode                       string      ALL_ROWS
SQL> sho parameter db_file_multi
NAME                                 TYPE        VALUE
db_file_multiblock_read_count        integer     16
SQL> sho parameter cursor_sharing
NAME                                 TYPE        VALUE
cursor_sharing                       string      EXACTExplain plan
| Id | Operation                              | Name                          | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT                       |                               |    56 | 29736 |   345K (1)| 01:09:07 |
|   1 | SORT ORDER BY                         |                               |    56 | 29736 |   345K (1)| 01:09:07 |
|   2 |   VIEW                                 |                               |    56 | 29736 |   345K (1)| 01:09:07 |
|   3 |    UNION-ALL                           |                               |       |       |            |          |
|   4 |     NESTED LOOPS                       |                               |     2 |   984 | 29686   (1)| 00:05:57 |
|   5 |      HASH JOIN                         |                               |     1 |   326 | 26870   (1)| 00:05:23 |
|   6 |       TABLE ACCESS FULL                | TIMEZONE                      |     4 |    88 |     3   (0)| 00:00:01 |
|   7 |       VIEW                             | MV_INVENTORY_TRANSACTION      |    25 | 7600 | 26866   (1)| 00:05:23 |
|   8 |        UNION-ALL                       |                               |       |       |            |          |
|   9 |         FILTER                         |                               |       |       |            |          |
| 10 |          MAT_VIEW ACCESS BY INDEX ROWID| MV_INVENTORY_TRANSACTION      |     1 |    67 | 24327   (1)| 00:04:52 |
| 11 |           INDEX RANGE SCAN             | IDX_CODE_CLIENTID_690         | 79681 |       |   518   (1)| 00:00:07 |
| 12 |         FILTER                         |                               |       |       |            |          |
| 13 |          MAT_VIEW ACCESS BY INDEX ROWID| MV_INVENTORY_TRANSACTION      |    24 | 2328 | 2539   (1)| 00:00:31 |
| 14 |           INDEX RANGE SCAN             | IDX_CODE_646                  | 9269 |       |    46   (0)| 00:00:01 |
| 15 |      VIEW                              | MV_SKU                        |    37 | 6142 | 2816   (1)| 00:00:34 |
| 16 |       UNION-ALL                        |                               |       |       |            |          |
| 17 |        MAT_VIEW ACCESS FULL            | MV_SKU                        |   335K|    10M| 2535   (1)| 00:00:31 |
| 18 |        MAT_VIEW ACCESS FULL            | MV_SKU                        | 37839 | 1699K|   280   (1)| 00:00:04 |
| 19 |     NESTED LOOPS                       |                               |    54 | 26568 |   315K (1)| 01:03:10 |
| 20 |      HASH JOIN                         |                               |     1 |   326 |   313K (1)| 01:02:37 |
| 21 |       TABLE ACCESS FULL                | TIMEZONE                      |     4 |    88 |     3   (0)| 00:00:01 |
| 22 |       VIEW                             | MV_INVENTORY_TRANSACTION_ARCH |   576 |   171K|   313K (1)| 01:02:37 |
| 23 |        UNION-ALL                       |                               |       |       |            |          |
| 24 |         FILTER                         |                               |       |       |            |          |
| 25 |          MAT_VIEW ACCESS BY INDEX ROWID| MV_INVENTORY_TRANSACTION_ARCH |     1 |    72 | 19258   (1)| 00:03:52 |
| 26 |           INDEX RANGE SCAN             | QUI_IDX_INVTRANS_ARC1         | 36016 |       |   287   (1)| 00:00:04 |
| 27 |         FILTER                         |                               |       |       |            |          |
| 28 |          MAT_VIEW ACCESS BY INDEX ROWID| MV_INVENTORY_TRANSACTION_ARCH |   575 | 55200 |   293K (1)| 00:58:45 |
| 29 |           INDEX RANGE SCAN             | QUI_IDX_INVTRANS_ARC1         |   367K|       | 3466   (1)| 00:00:42 |
| 30 |      VIEW                              | MV_SKU                        |    37 | 6142 | 2816   (1)| 00:00:34 |
| 31 |       UNION-ALL                        |                               |       |       |            |          |
| 32 |        MAT_VIEW ACCESS FULL            | MV_SKU                        |   335K|    10M| 2535   (1)| 00:00:31 |
| 33 |        MAT_VIEW ACCESS FULL            | MV_SKU                        | 37839 | 1699K|   280   (1)| 00:00:04 |
------------------------------------------------------------------------------------------------------------------------when put in sql tuning advisor,It recommended with better plan using indexes
| Id | Operation                              | Name                          | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT                       |                               |    56 | 29736 |   340K (1)| 01:08:01 |
|   1 | SORT ORDER BY                         |                               |    56 | 29736 |   340K (1)| 01:08:01 |
|   2 |   VIEW                                 |                               |    56 | 29736 |   340K (1)| 01:08:01 |
|   3 |    UNION-ALL                           |                               |       |       |            |          |
|   4 |     NESTED LOOPS                       |                               |     2 |   848 | 26900   (1)| 00:05:23 |
|   5 |      HASH JOIN                         |                               |     1 |   326 | 26898   (1)| 00:05:23 |
|   6 |       TABLE ACCESS FULL                | TIMEZONE                      |     4 |    88 |     3   (0)| 00:00:01 |
|   7 |       VIEW                             | MV_INVENTORY_TRANSACTION      |    25 | 7600 | 26894   (1)| 00:05:23 |
|   8 |        UNION-ALL                       |                               |       |       |            |          |
|   9 |         FILTER                         |                               |       |       |            |          |
| 10 |          MAT_VIEW ACCESS BY INDEX ROWID| MV_INVENTORY_TRANSACTION      |     1 |    67 | 24352   (1)| 00:04:53 |
| 11 |           INDEX RANGE SCAN             | IDX_CODE_CLIENTID_690         | 79681 |       |   518   (1)| 00:00:07 |
| 12 |         FILTER                         |                               |       |       |            |          |
| 13 |          MAT_VIEW ACCESS BY INDEX ROWID| MV_INVENTORY_TRANSACTION      |    24 | 2328 | 2542   (1)| 00:00:31 |
| 14 |           INDEX RANGE SCAN             | IDX_CODE_646                  | 9269 |       |    46   (0)| 00:00:01 |
| 15 |      VIEW                              | MV_SKU                        |    37 | 3626 |     2   (0)| 00:00:01 |
| 16 |       UNION-ALL PARTITION              |                               |       |       |            |          |
| 17 |        MAT_VIEW ACCESS BY INDEX ROWID | MV_SKU                        |     1 |    34 |     3   (0)| 00:00:01 |
| 18 |         INDEX UNIQUE SCAN              | PK_SKU                        |     1 |       |     2   (0)| 00:00:01 |
| 19 |        MAT_VIEW ACCESS BY INDEX ROWID | MV_SKU                        |     1 |    46 |     2   (0)| 00:00:01 |
| 20 |         INDEX UNIQUE SCAN              | PK_SKU                        |     1 |       |     1   (0)| 00:00:01 |
| 21 |     NESTED LOOPS                       |                               |    54 | 22896 |   313K (1)| 01:02:38 |
| 22 |      HASH JOIN                         |                               |     1 |   326 |   313K (1)| 01:02:38 |
| 23 |       TABLE ACCESS FULL                | TIMEZONE                      |     4 |    88 |     3   (0)| 00:00:01 |
| 24 |       VIEW                             | MV_INVENTORY_TRANSACTION_ARCH |   576 |   171K|   313K (1)| 01:02:38 |
| 25 |        UNION-ALL                       |                               |       |       |            |          |
| 26 |         FILTER                         |                               |       |       |            |          |
| 27 |          MAT_VIEW ACCESS BY INDEX ROWID| MV_INVENTORY_TRANSACTION_ARCH |     1 |    72 | 19269   (1)| 00:03:52 |
| 28 |           INDEX RANGE SCAN             | QUI_IDX_INVTRANS_ARC1         | 36016 |       |   287   (1)| 00:00:04 |
| 29 |         FILTER                         |                               |       |       |            |          |
| 30 |          MAT_VIEW ACCESS BY INDEX ROWID| MV_INVENTORY_TRANSACTION_ARCH |   575 | 55200 |   293K (1)| 00:58:47 |
| 31 |           INDEX RANGE SCAN             | QUI_IDX_INVTRANS_ARC1         |   367K|       | 3466   (1)| 00:00:42 |
| 32 |      VIEW                              | MV_SKU                        |    37 | 3626 |     2   (0)| 00:00:01 |
| 33 |       UNION-ALL PARTITION              |                               |       |       |            |          |
| 34 |        MAT_VIEW ACCESS BY INDEX ROWID | MV_SKU                        |     1 |    34 |     3   (0)| 00:00:01 |
| 35 |         INDEX UNIQUE SCAN              | PK_SKU                        |     1 |       |     2   (0)| 00:00:01 |
| 36 |        MAT_VIEW ACCESS BY INDEX ROWID | MV_SKU                        |     1 |    46 |     2   (0)| 00:00:01 |
| 37 |         INDEX UNIQUE SCAN              | PK_SKU                        |     1 |       |     1   (0)| 00:00:01 |
------------------------------------------------------------------------------------------------------------------------So ,after checking the recommended plan I tried to execute the query with the hints,even then it is picking up the indexes in the explain plan.So please kindly help in solving the issue
The pk_sku is the index created on client_id and sku_id columns
Thanks
GV

riedelme wrote:
My experience is differernt - hints will be followed if the optimizer determines they will be beneficial and not if they will not, including my current project on 11gR2. The example below (unfortunately only 11gR1) disproves your theory, showing the index hint is followed and that the cost increases by a factor of five.
The most common cases of the optimizer apparently ignoring a hint are due to operator error, the hint is not well formed, or cannot be followed. There are a couple of documented cases where a hint will be ignored - first_rows used in CTAS is one.
Jonathan Lewis writes a lot about it on his blog showing that the optimizer always acts on a well formed hint if it is at all possible.
SQL> create table t (n number not null, c varchar2(1000));
Table created.
SQL> insert into t select 1, rpad('x',1000,'x')
2 from dual connect by level <= 50000;
50000 rows created.
SQL> create index t_ix on t (n);
Index created.
SQL> exec dbms_stats.gather_table_stats(user, 't', cascade => true)
PL/SQL procedure successfully completed.
SQL> explain plan for
2 select max(c) from t where n =1;
Explained.
SQL> select * from table(dbms_xplan.display);
PLAN_TABLE_OUTPUT
Plan hash value: 2966233522
| Id | Operation          | Name | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT   |      |     1 | 1004 | 1574   (1)| 00:00:19 |
|   1 | SORT AGGREGATE    |      |     1 | 1004 |            |          |
|* 2 |   TABLE ACCESS FULL| T    | 50000 |    47M| 1574   (1)| 00:00:19 |
Predicate Information (identified by operation id):
PLAN_TABLE_OUTPUT
   2 - filter("N"=1)
14 rows selected.
SQL> explain plan for
2 select /*+ index (t t_ix) */ max(c) from t where n = 1;
Explained.
SQL> select * from table(dbms_xplan.display);
PLAN_TABLE_OUTPUT
Plan hash value: 3231292748
| Id | Operation                    | Name | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT             |      |     1 | 1004 | 7244   (1)| 00:01:27 |
|   1 | SORT AGGREGATE              |      |     1 | 1004 |            |          |
|   2 |   TABLE ACCESS BY INDEX ROWID| T    | 50000 |    47M| 7244   (1)| 00:01:27 |
|* 3 |    INDEX RANGE SCAN          | T_IX | 50000 |       |    98   (0)| 00:00:02 |
PLAN_TABLE_OUTPUT
Predicate Information (identified by operation id):
   3 - access("N"=1)
15 rows selected.

CST is not getting picked up in sales order

Similar Messages

Maybe you are looking for