Z quotation type not getting picked up in create quotation workcenter link

Dear Webui experts,
We have a custom quotation type created from copying the standard one AGIS.
The workcenter link for create quotation works fine and displays list of quotations standard available in the system, but does not display the custom created quotation.
And the following message is displayed;
"Details" No transaction type is available for creating a transaction. On clicking on details its says either the transaction type is not configured or the user doesnot have authorisation. I have checked both and that is not the issue.
The pfcg fole has create authorisation for this transaction type in the authorisaion objects;
CRM_ORD_PR
CRM_ORD_LP.
I have checked for any SAP notes with th system message but did not find solution.
Can you pleaes guide what needs to be done
Thanks
Satish

Thanks Pankaj and Kunstej,
The problem still exists.
I made the entry for 'CRM webclient UI' in the channel for the Z transaction type for quote. But still it is not appearing in the webui. Rather all other transaction in the sytem disappeared. As you explained it was because if I maintain it for one it has to be maintained for all.
So I had to revert the channel entry 'CRM webclkient UI' as it actually did not solve the problem.
Also I noticed that other custom transaction types are visible in webui although ''CRM webclient UI' entry is not maintained for transaction type in channel. so it seems that the channel entry is not mandatory.
So may be problem is elsewhere. Please guide me if I need to check anyting else.
Also I was curious that anywhere (unlike R/3) in the transaction type we do not tell the system that it is a quotation or order, then how does system know that it has has to popuplate certain transaction types in 'Create quotation' link and certain in the 'Create Order' link.

Similar Messages

Output Message Type MAHN not getting picked up in PO

Hello Experts
   I have configured customized output type ZMAH (similar to MAHN) for reminder process. When I am creating PO this output type is not getting picked up automatically. If I am maintaining it manually I am able to send message for ME9F (Purchase Order) and ME91F (Reminder) successfully. Upon deremination analysis I am getting this message 502 " Output ignored (requirement 103 not fulfilled) ". Reminder are getting picked up from Purchase Value Key to PO.
Any help is appreciated.
Thanks
Ankit

Hello Tej
I have maintained output device but same result.
Here I am listing all parameters that I have used for configuration can anyone please take a look and let me know if I am missing anything
Steps for new Message Type for PO Reminder (ZMAH)
1.     Defined new Table 026 Purchasing Output Determination: Document Type
                                                    (ii) 027 Purchasing Output Determination: Purch. Org./Vendor for EDI
2.     Defined new access sequence Z515 Access Sequence for Archiving.
Following are parameters to the Access Sequence
Access Sequence Number = 1
Table = 026
Description = Purchasing Output Determination: Document Type
Requirement = 103
Exclusive = Yes (box checked)
Access Sequence Number = 2
Table = 027
Description = Purchasing Output Determination: Purch. Org./Vendor for EDI
Requirement = 103
Exclusive = Yes (box checked)
3.     Maintain Output Type ZMAH for PO
General Data
Access Sequence = Z515
Access to condition (Checked)
Multiple Issuing (Checked)
Change Output
Program = SAPFM06P
FORM Routine = ENTRY_NEU
Replacement of Text Symbol
Program = SAPMM06E
FORM Routine = TEXT_SYMBOL_REPLACE
Default Values
Dispatch Time = Send Immediately (when saving application)
Transmission Medium = External Send
Communication Strategy = 0001 (E-mail Document)
Processing Routines
Transmission Medium = 5 (External Send)
Program = SAPFM06P
Form Routine = ENTRY_NEU
Form = MEDRUCK
Partner Roles
Medium = External Send
Funct = VN
Name = Vendor
4.     Fine-Tuned Control: Purchase Order
Oprat. = 3
CType = ZMAH
Name = Output for Reminder
Short Text = Urging letter (expediter)/reminder
Update Print Related Data = Yes (checked)
5.     Maintain Message Determination Schema: Purchase Order
Procedure RMBEF1 (Purchase Order)
Step = 101
Cntr = 3
CTyp = ZMAH
Description = Output for Reminder
Requirement = 103
6.     Assign Schema to Purchase Order
Procedure RMBEF1
7.     Define Partner Roles for Purchase Order
Out. = ZMAH
Med = 5 (External Send)
Funct = VN
Name = Output for Reminder
Name = Vendor
8.     Test Condition Maintained in MN04 (Master Data)
Purch. Org. = 0001
Vendor = 101281
Partner Funct = VN
Medium = 5 (External Send)
Date/Time = 4 Send immediately (when saving application)
Output Device = LP01
Cover Page Text = Reminder PO number &EKKO-EBELN&
Also I have configured Purchasing Value Key, reminders are coming to PO correctly.
Thanks
Ankit

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.

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$

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

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.

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,

WT not getting picked up under 3PR

Hi All
We are facing an issue wherein the wage type is not getting picked up in 3PR even though it is coming under remuneration statement.
Can you please advise what could be the reason ?
Regards
Neha

As far i understand system will always considers the retro values when ever any changes are there pertaining to wage type accordingly system will do the posting.
Either it is a positive arrear or negative arrear system will bring it to the current period you do not want retro calculation delimit the record maintain 78 with effective date on wards.
Regards
Venkatesh

Re : Condition record not getting picked

Hi All,
This is with reference to Inter-company PO.
A condition record has been maintained for MWST condition type(for key combination of Departure country -ID & Destination Country BE).But the system is not picking this condition record but it is picking the condition record maintained for MY to BE.
Could you please tell me where I need to check if a condition record is not getting picked.
Regards,
Mahesh.

Dear Mahesh
- Check your Ship To Party Country
- Ensure that the tax code you have maintained for the combination of ID -- BE
thanks
G. Lakshmipathi

Pricing procedure is not getting picked

I have defined a pricing procedure for my service PO and I have created a new PO document type for my service PO. But my pricing procedure is not getting picked up for this PO. please help how to get it resolved.
Regards,
Pankaj

hello pankaj
After defining Calculation schema, ensure that you have defined schema group for vendor and assignment of the same to Purchase organisation.
you can also determine calculation schema for standard POs.
finally goto change vendor and in purchasing Data input schema group in Vendor schema field.
regards
Chetan

Asset GL accounts not getting picked up in ABST2 run

Hi,
There are few asset GL accounts i.e APC and AccDep accounts which are not getting picked up in ABST2 run. What could be the reason? Please advise as to how can we ensure that we get a spool of all the GL accounts post ABST2 run.
Thanks,
DP

Are the missing GL accounts set up as asset reconciliation accounts go to FS03, enter GL account number, and go to control data tab, field recon account for account type should be A for Assets.
Thanks,
Tammy

VA00 condition type not getting determined for the returns order

Hi All,
I have a case where VA00 condition type not getting determined for the returns order that has been created with respect to the billing document.
When the pricing conditions are being copied from invoice it is getting copied but later it is getting deleted in the include LV61AA42.
Note:VA00 condition type is getting deleted from the internal table tkomv[].
If any one came across this scenario can you please help me.
Request your valuable inputs

Hi,
Please check the copy control setting in VTAA.
Maintain the pricing type as "D" at item category level for the respective document type .
Hope this will resolve your issue.
Regards,
Krishna O

File not getting picked with Sender Adapter

Hello Experts,
i have configured file sender adapter which is polling configured directory every 60 sec. But i could see file not getting picked up. when looked into Communication channel monitoring i could see following error:
Putting message into send queue failed, due to: com.sap.aii.af.ra.ms.api.DuplicateMessageException : Message ID aa2ec9a0-44b3-11dc-9c5b-0003baa19669(OUTBOUND) already exists in database: com.sap.sql.DuplicateKeyException: ORA-00001: unique constraint (SAPDX1DB.SYS_C00120924) violated.
is this due to adapter cache. we are on SP20.
has anybody faced this problem earlier?
Thanks in advance.
Regards
Rajeev

Hello
actually there was small problem in file generation and hence it was failing in message mapping which is resolved. but still that problem is there when it is attempting to delete the file. hence it is not able to delete that file.
can we manually clear the send queues or should we refresh CPA cache?
Thanks
Rajeev

Debit Items not getting picked while making payment with F110

HI,
When making payment with F110, items with Debit balance is not getting picked.
Example:
Payment method is assigned in the Maser data.
For a particular vendor one item has a credit balance- posting key 31.
We have posted another JV with F-02 and debited that vendor with Posting key 21. (Payment Method is not entered in the line item)
When we run F110 the credit balance is picked and debit balance is being shown in exception list.
When we got to FB02 and insert payment method in debit line item and then again run the F110 then system pickes all line items and pays the net amount.
The question is why system is not considering Payment Method from Master Data in debit line item, while in credit line item it is picking payment method from the master data.
Do I need to do any setting for it so that it should automatically take payment method from master data even in case of Debit line items.
Regards
Sanjay

Hi All,
Thanks for your quick replies.
But it does not solve my problem.
When I am not assigning any payment method to either Debit or credit line items, system picks (payment method from Master data) for only credit line items and ignores debit line items.
But the problem is that when I assign payment method to debit line item (which is similar to what has been assigned to vendor Master Data) system groups both debit and credit line items and makes payment of only net amount.
My question was why system considered the debit line item for making payment if I manually enter payment method in the line item, if system has been designed only for out going payment. In my opinion It should have reacted similarly irrespective of whether payment method entered in the line item or not.
Regards
Sanjay

Z quotation type not getting picked up in create quotation workcenter link

Similar Messages

Maybe you are looking for