Partitioned IOT of Object Type - mapping table not allowed for bitmap index

Hi,
looks like a feature available for standard Partitioned IOTs is not supported for object based tables, namely the MAPPING TABLE construct to support secondary local bitmap indexes.
Can you confirm behaviour is as expected/documented?
If so, is a fix/enhancement to support mapping table for object-based Partitioned IOTs in the pipeline?
Results for partition-wise load using pipelined table function are very good, look-ups across tens of millions of rows are excellent.
Environment = Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
OS = Oracle Enterprise Linux Server release 5.2 (Carthage) 2.6.18 92.el5 (32-bit)
Here's the potted test-case...
1) First the non object based Partitioned IOT - data is range-partitioned across the alphabet
CREATE TABLE IOT_Table (
textData VARCHAR2(10),
numberData NUMBER(10,0),
CONSTRAINT IOT_Table_PK PRIMARY KEY(textData))
ORGANIZATION INDEX MAPPING TABLE PCTFREE 0 TABLESPACE Firewire
PARTITION BY RANGE (textData)
(PARTITION Text_Part_A VALUES LESS THAN ('B') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_B VALUES LESS THAN ('C') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_C VALUES LESS THAN ('D') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_D VALUES LESS THAN ('E') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_E VALUES LESS THAN ('F') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_F VALUES LESS THAN ('G') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_G VALUES LESS THAN ('H') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_H VALUES LESS THAN ('I') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_I VALUES LESS THAN ('J') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_J VALUES LESS THAN ('K') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_K VALUES LESS THAN ('L') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_L VALUES LESS THAN ('M') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_M VALUES LESS THAN ('N') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_N VALUES LESS THAN ('O') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_O VALUES LESS THAN ('P') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_P VALUES LESS THAN ('Q') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_Q VALUES LESS THAN ('R') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_R VALUES LESS THAN ('S') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_S VALUES LESS THAN ('T') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_T VALUES LESS THAN ('U') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_U VALUES LESS THAN ('V') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_V VALUES LESS THAN ('W') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_W VALUES LESS THAN ('X') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_X VALUES LESS THAN ('Y') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_Y VALUES LESS THAN ('Z') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_Z VALUES LESS THAN (MAXVALUE) PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0))
NOLOGGING PARALLEL -- FLASHBACK ARCHIVE IOT_Flashback_Data
SQL> table IOT_TABLE created.
2) Create the local secondary bitmap index utilising the underlying mapping table
CREATE BITMAP INDEX IOT_Table_BMI1 ON IOT_Table (numberData)
LOCAL STORAGE (INITIAL 1M PCTINCREASE 0 NEXT 512K) NOLOGGING PARALLEL;
SQL> bitmap index IOT_TABLE_BMI1 created.
3) Quick test to confirm all ok
SQL> INSERT INTO IOT_Table VALUES ('ABC123',100);
SQL> 1 rows inserted.
SQL> SELECT * FROM IOT_Table;
TEXTDATA NUMBERDATA
ABC123     100
4) Now create a minimal object type to use as the template for object table
CREATE TYPE IOT_type AS OBJECT
textData VARCHAR2(10 CHAR),
numberData NUMBER(10,0)
) FINAL
SQL> TYPE IOT_type compiled
5) Attempt to create an object-based range partitioned IOT, including MAPPING TABLE clause as per step (1)
CREATE TABLE IOTObj_Table OF IOT_type (textData PRIMARY KEY)
OBJECT IDENTIFIER IS PRIMARY KEY ORGANIZATION INDEX
MAPPING TABLE -- we'd like to use this feature to enable use of Bitmap Indexes...
PCTFREE 0 TABLESPACE Firewire
PARTITION BY RANGE (textData)
(PARTITION Text_Part_A VALUES LESS THAN ('B') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_B VALUES LESS THAN ('C') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_C VALUES LESS THAN ('D') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_D VALUES LESS THAN ('E') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_E VALUES LESS THAN ('F') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_F VALUES LESS THAN ('G') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_G VALUES LESS THAN ('H') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_H VALUES LESS THAN ('I') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_I VALUES LESS THAN ('J') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_J VALUES LESS THAN ('K') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_K VALUES LESS THAN ('L') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_L VALUES LESS THAN ('M') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_M VALUES LESS THAN ('N') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_N VALUES LESS THAN ('O') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_O VALUES LESS THAN ('P') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_P VALUES LESS THAN ('Q') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_Q VALUES LESS THAN ('R') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_R VALUES LESS THAN ('S') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_S VALUES LESS THAN ('T') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_T VALUES LESS THAN ('U') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_U VALUES LESS THAN ('V') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_V VALUES LESS THAN ('W') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_W VALUES LESS THAN ('X') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_X VALUES LESS THAN ('Y') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_Y VALUES LESS THAN ('Z') PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0),
PARTITION Text_Part_Z VALUES LESS THAN (MAXVALUE) PCTFREE 0 TABLESPACE Firewire Storage (Initial 10M Next 1M PCTIncrease 0))
NOLOGGING PARALLEL -- FLASHBACK ARCHIVE IOT_Flashback_Data
This errors out with the following...
SQL Error: ORA-25182: feature not currently available for index-organized tables
25182. 00000 - "feature not currently available for index-organized tables"
*Cause:    An attempt was made to use one or more of the following feature(s) not
currently supported for index-organized tables:
CREATE TABLE with LOB/BFILE/VARRAY columns,
partitioning/PARALLEL/CREATE TABLE AS SELECT options,
ALTER TABLE with ADD/MODIFY column options, CREATE INDEX
*Action:   Do not use the disallowed feature(s) in this release.
6) Re-running the create table statement in step 5 without the MAPPING TABLE clause works fine. Not surprisingly an attempt to create a secondary local bitmap index on this table fails as there's no mapping table, like so...
CREATE BITMAP INDEX IOTObj_Table_BMI1 ON IOTObj_Table (numberData)
LOCAL STORAGE (INITIAL 1M PCTINCREASE 0 NEXT 512K) NOLOGGING PARALLEL;
CREATE TABLE with LOB/BFILE/VARRAY columns,
partitioning/PARALLEL/CREATE TABLE AS SELECT options,
ALTER TABLE with ADD/MODIFY column options, CREATE INDEX
*Action:   Do not use the disallowed feature(s) in this release.
CREATE BITMAP INDEX IOTObj_Table_BMI1 ON IOTObj_Table (numberData)
LOCAL STORAGE (INITIAL 1M PCTINCREASE 0 NEXT 512K) NOLOGGING PARALLEL
Error at Command Line:99 Column:13
Error report:
SQL Error: ORA-00903: invalid table name
00903. 00000 - "invalid table name"
7) Creating a secondary local b-tree index is fine, like so...
SQL> CREATE INDEX IOTObj_Table_I1 ON IOTObj_Table (numberData)
LOCAL STORAGE (INITIAL 1M PCTINCREASE 0 NEXT 512K) NOLOGGING PARALLEL;
index IOTOBJ_TABLE_I1 created.
8) A quick test to ensure object table ok...
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('DEF456',500));
SQL> 1 rows inserted.
SQL> SELECT * FROM IOTObj_Table;
TEXTDATA NUMBERDATA
DEF456     500

Thanks Dan,
the intention is to range partition based on the initial character, so A* -> Text_Part_A, B* -> Text_Part_B, and so on.
Here's an example, using an empty IOTObj_Table as created previously.
1) Set up & confirm some test data (two 'D's, one 'N', and two 'Z's)
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('DEF456',500));
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('DDD111',510));
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('N3000',515));
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('ZZ1212',520));
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('Z111X',530));
SQL> COMMIT;
SQL> SELECT * FROM IOTObj_Table;
TEXTDATA NUMBERDATA
DDD111     510
DEF456     500
N3000     515
Z111X     530
ZZ1212     520
2) Just to prove our IOT is enforcing the Primary Key based on the TextData attribute, try to insert a duplicate
SQL> INSERT INTO IOTObj_Table VALUES (IOT_Type('Z111X',530));
Error starting at line 141 in command:
INSERT INTO IOTObj_Table VALUES (IOT_Type('Z111X',530))
Error report:
SQL Error: ORA-00001: unique constraint (OCDataSystems.SYS_IOT_TOP_84235) violated
00001. 00000 - "unique constraint (%s.%s) violated"
*Cause:    An UPDATE or INSERT statement attempted to insert a duplicate key.
For Trusted Oracle configured in DBMS MAC mode, you may see
this message if a duplicate entry exists at a different level.
*Action:   Either remove the unique restriction or do not insert the key.
3) Now confirm that our data has been slotted into the range-based partition we expect using the PARTITION clause of SELECT...
- The two 'D's...
SQL> SELECT * FROM IOTObj_Table PARTITION (Text_Part_D);
TEXTDATA NUMBERDATA
DDD111     510
DEF456     500
- The single 'N'...
SQL> SELECT * FROM IOTObj_Table PARTITION (Text_Part_N);
TEXTDATA NUMBERDATA
N3000     515
- The two 'Z's...
SQL> SELECT * FROM IOTObj_Table PARTITION (Text_Part_Z);
TEXTDATA NUMBERDATA
Z111X     530
ZZ1212     520
4) And to wrap up confirm an empty partition
SELECT * FROM IOTObj_Table PARTITION (Text_Part_W);

Similar Messages

  • ABAP Dictionary type FLTP is not allowed for screen element

    Hi Experts
    I tried to open VBFA in se16 and i got the message in the status bar like this , what does it mean. please explain.
    "ABAP Dictionary type FLTP is not allowed for screen element"

    Hi,
        This is from help
    ABAP Dictionary type FLTP is not allowed for screen element
    Message no. 37048
    <b>Diagnosis</b>
    The format of the ABAP Dictionary field is only for use within the ABAP
    program and cannot be used in the Screen Painter.
    <b>Procedure</b>
    The field cannot be used in screens. If you want to output the
    information in the field or assign a value to the field from the screen,
    you must use an intermediate field with an appropriate format.
    <b>Reward points</b>
    Regards

  • Set type COMM_PR_UNIT is not allowed for product type

    Hello all, I am working in SRM 7.0 and when I try to replicate service master (DNL_CUST_SRVMAS) I have this error:
    Set type COMM_PR_UNIT is not allowed for product type
    What can I do? I think that is an ABAP problem
    Thanks in advance
    Rosa Rodríguez

    Rosa,
    This note is something different and nothing to do with the issue. Can you share how did you resolve the DNL_CUST_SRVMAS issue? We are also getting same error.
    Thanks,
    Jagadish

  • Class type 022 is not defined for object for BATMAS

    Hi Experts,
    while creaitng the LSMW for batch classification,I faced the error during IDOC processing as "Class type 022 is not defined for object".I am using
    Business Object      BUS1001002
    Method               SAVEREPLICA
    Message Type         BATMAS
    Basic Type           BATMAS03
    Pleas guide how to resolve the error.
    Also ,as I intend to make LSMW for batch classifications.Is this the correct way.
    Please guide on this also.
    Regards.

    Hello Jass,
    Symptom
    The BATMAS03 basis type (message type BATMAS) /FB BAPI_BATCH_REPLICATE  cannot transfer any classification information. Please review note 1070634.
    First Option :
    You should first transfer the batmas and then the clfmas idoc.
    Second Option :
    You could create the batch together with classification. Normally the problem is the missing CUOBJ_BM in table MCH1. It is not necessary in all situations that the field have to be filled, but it can be in some cases (And it is better to store the right  information in the corresponding fields). Especially when you transfer batch/classification information in other system the field have to be filled.
    The way to create the batch TOGETHER with classification by using BATMAS IDOC is to set the following parameters correctly :-
    set E1BPBATCHCTRL-DOCLASSIFY to X and fill the segments with relevant classification information
    E1BP3060_ALLOCATION
    E1BP3060_VALUATION_CHAR
    E1BP3060_VALUATION_CURR
    E1BP3060_VALUATION_NUM
    In this case the field mch1-cuobj_bm should be filled with correct CUOBJ. You can also use function module BAPI_BATCH_SAVE_REPLICA to create batches together with classification.
    Hope this information helps
    Regards
    Amber

  • Document type ZD does not allow you to assign to object MARA

    hi ppl,
             I have created a Z document type.but its not allowing me to assign in mm02.what might be the problem..? its throwing an error message Document type ZD does not allow you to assign to object MARA.

    You need to enable object linking to mara on your new document type. Go to Tcode DC10, select the document type and then go to the object links area. Create a new object link for your document type.

  • Value type Mapping Table

    Dear Gurus,
    In R/3 I have value types 1(Plan), 2(Plan:Splitting Among Activity Types) like up to 99 and 9A to 9D types available.
    These value types are showing in RPSCO table.
    But in BW only showing 10(Actual), 20(Plan), 30(Target), 50 (Budget), 70(Variance), 80(Selection) and 85(Accrual Plan).
    My question is which R/3 plan value type is mapped with BW Plan Value type ?
    Is there any value type mapping table to find in R/3 ?
    Regards
    Ramu

    By R/3 Table COSB_VTYPE you can check mapping of all value types
    Regards
    Ramu

  • ZSAPLINK for Object type = CLAS is not working

    Dear Experts,
    ZSAPLINK for Object type = CLAS is not working. On executing by selecting Export Object to Slinkee with Object type = CLAS and class name, It is giving the dump which is shown in below snapshots. Pls guide me how to resolve this error.
    Thanks
    KH

    From the screenshot, It seems that the object  _renderer did not point to any memory location.
    You can verify this by putting a breakpoint in method IF_IXML~CREATE_RENDERER of class CL_IXML
    If the return value RVAL is initial, this mean there something wrong with the kernel module abkm_iXML_CreateRenderer. If it is, you will have to check with your Basis team to apply some kernel patches.
    Hope it helps. Cheers!

  • Object type 'EBAN' is not defined

    Hi All,
    I have a developed a custom workflow for PR release.
    but the workflow is not triggering.
    When i checked in SWU3 configuration, check event linkages, i found that the error message Object type 'EBAN' is not defined.
    Can someone tell me what it means and how can i fix it?
    Thanks and regards,
    Raj

    Hi PK,
    r u using ReleaseStrategy, did u try simulate it, get help from MM consultant, check whether its working perfect.
    If tht works fine, switch on ur SWEL (first go to SWELS and click SwitchOn).
    Create a PR and chk SWEL, see if ur object BUS2105 is triggered ?
    Aditya

  • Class type 022 is not defined for object for batmas in LSMW idoc

    Hi Experts,
    while creaitng the LSMW for batch classification,I faced the error during IDOC processing as "Class type 022 is not defined for object".I am using
    Business Object BUS1001002
    Method SAVEREPLICA
    Message Type BATMAS
    Basic Type BATMAS03
    Pleas guide how to resolve the error.
    Also ,as I intend to make LSMW for batch classifications.Is this the correct way.
    Please guide on this also.
    Regards.

    Hi,
    Go to TCode OMCE and check the batch level.
    If batch is activated at material/client level then use class type 023, if it is at plant level the class type 022.

  • Status profile not allowed for object type

    hi
    i had created a status profile (for having 2 statuses before production order release) and assigned in the order type.
    but while creating the production order i receive the following error.
    Message no - CO622
    status profile not allowed for object type
    please provide your inputs
    regards
    Ramesh

    Ramesh,
    once you cerate a Status profile in BS02 and add status to the same. in the tollbar you will see OBJECT TYPE push button, select teh obejcts like PP/PM order header / operation /comepeoent and PRT ect where that staus can be applied.
    Then assign the statsu profile to order type.

  • Object key for object type WORKITEM is not generated

    Hi experts,
    I have a problem when I create a purchase requisition by workflow. This problem happens a client copy from production to quality system has been done.
    The problem is that the object key for the object type WORKITEM is not generated. I check in transaction SWEL in quality system it displays the following data:
    For the event data I have the following data:
    Event Instance ID - 1099124
    Object Type - BUS2105
    Object key - 0120001588 (purchase requisition number)
    Event - criadaoumodificada (createdorchanged)
    For the Receiver Data I have the following data:
    Receiver Type - WS99900003 
    Object Type  (is not displayed)
    Object Key   (is empty)
    Receiver FM - SWW_WI_CREATE_VIA_EVENT_IBF
    RFC Destination - WORKFLOW_LOCAL_010
    In the Receiver Data the object type is not displayed and the object key is not generated. In production system the object type is WORKITEM, and the object key is filled by a number of workitem.
    Can anyone tell me why this happens?
    Best regards,
    Leonel

    Hi Leonel,
    as far as I remember, those fields are updated once the receiver function module was successfully processed. In your case, I'd suggest, that you ...
    - Check the workflow local RFC destination (SM59, WORKFLOW_LOCAL_<client>)
    - Check the workflow-user (SU01, User-ID WF-BATCH normally),
    - Check for entries that stuck in the event processing (tRFC queue, transaction SM58).
    - To verify the complete system, execute transaction SWU3. The section under "Runtime environment" should be marked green.  (Ignore the red sign on definition environment).
    - For a more extensive workflow runtime check, use the transaction SWUD  (workflow diagnosis).
    After all that, your problem might be solved, or at least you know, what's all okay
    Best wishes,
       Florin

  • It is showing as error *Instance of object type PO could not be changed*

    HI Gurus,,
    i have requirement in PO Change IDOC , i have tested this IDOC .. but it is showing in Status record as error Document is does not exist
    and in Segmentheader for E1BPMEPOHEADER ..it is showing as error Instance of object type PO could not be changed
    SEGMENT NAME : E1BPMEPOHEADER
      PO_NUMBER
      COMP_CODE
      DOC_TYPE
      CREAT_DATE
      VENDOR
      PURCH_ORG
      PUR_GROUP ;;;
    we have entered related entries in it ...
    am uanble to find out where is porblem lies in it... plz help ASAP ...
    Thanks in advance..

    HI srinivas
    "It seems a data issue, Similar PO might be changed already and thus in SAP it is not allowing to change.
    So try changing the test data and post the IDOC again , it will change the PO . "
    yes we have entered the PO create and PO change .. where in PO change we have changed only QUANTITY and DATE .
    and showing this error" *It is showing as error Instance of object type PO could not be changed. "*
    Thanks in advance.

  • QM action not allowed for DTP requests in master data and Text tables

    Hi,
    I have a master data object load request which has failed, returned error in st22 and job finished.
    BUT the request has not turned red in the monitor - it's still yellow. That means that I can not delete request nor start new load to infoprovider because it believes a request is still running. But it's not, I've checked both sm37, sm50 etc.
    When trying to manually change QM status to 'red' it says 'QM action not allowed for DTP requests in master data and Text tables'
    How can I force QM status to red so that I can move on?
    Running NW2004s BI (7.0) Patch 15.
    I searched for this question but there is no answer
    Thank you

    Folks
    I know how frustrating this problem is even in netweaver 7.0 environment. I found a solution for this problem atlast and it works but a not direct way of resolving this issue.
    When this request is in yellow status and not able to change / delete the request, its actually in a pseudo status and it is a bug in the program. This request sits in table RSBKREQUEST with processing type as 5 in data elements USTATE, TSTATE and this 5 is actually "Active" status which is obviously wrong.
    All we need is, ask your basis person to change the status to 3 in both these data elements and then it allows to reload the delta. Once the delta is successfully loaded, you can delete the previous bad request even though it is still in yellow. Once the request is deleted, the request status gets updated as "4" in table RSBKREQUEST.
    Hope this helps.
    Thanks

  • Method SAP_WAPI_WORKITEM_COMPLETE not allowed for type F

    Hi Gurus
    I have created a webdynpro abap application in which these steps
    1. Application triggers the workflow and workitem got created through FM1.
    2. Workitem loads up webdynpro abap application from portal or outlook by changing settings in SWFVISU transaction.
    3. Application completes the workflow by calling FM2.
    Here FM1 is SAP_WAPI_START_WORKFLOW which returns the workitem id. When I am giving the same workitem id in function module SAP_WAPI_WORKITEM_COMPLETE , it is giving me error that Method SAP_WAPI_WORKITEM_COMPLETE not allowed for type F
    My workflow has only one activity step which is mapped with class CL_PT_REQ_WF_ATTRIBS and method DUMMY. I have checked the synchronous method.
    Please let me know how can I correct it.
    With regards
    Manu Sharma

    Hi
    You need to give the workitem id of the dialog task which has been configured in SWFVISU. You will get this workitem id via application parameter in your Webdynpro method.
    Wokflow will be completed, if all the steps has been executed
    Vinoth
    Edited by: S Vinoth on Oct 27, 2010 10:08 AM

  • ME 013 Document type ZEBP is not allowed with doc. category B (Please check

    We are creating shopping cart with specific items using XMA catalogue ME013 message comes
    Shopping cart 0001008270 (Preq. 2900000012) : ME 013 Document type ZEBP is not allowed with doc. category B (Please check input)
    Is it related to PO Document type configuration in R/3!
    Document type ZEBP is not in table T160 (SAP Transaction Control) or Do I need to debug the BAPI_PO_CREATE1.

    Hi
    Which SRM and R/3 versions are you using ?
    Some related useful pointers ->
    Error: ME 013 Document type ECPO not allowed with doc. c ategory B
    Re: Shopping cart contains error
    Error: ME 013 Document type ECPO not allowed with doc. c ategory B
    Hope this will definitely help. Do let me know.
    Regards
    - Atul

Maybe you are looking for

  • Can't get external monitor to work

    I've used a Mac laptop for the last 8 years, finally decided to get an external monitor for home use. I purchased a 25" Hanns-G HZ251. It's not working as I would expect it to work. I've got a standard DVI connection on my older MacBook Pro so I'm co

  • Share function not working

    My Share function is not working.  The last change I've made was to change my AOL password, however don't think that was the cause.  Any suggestions? Thank you Ivy

  • When i try to search for contact or create a new one the keybord does not come up

    when i try to search for contact or create a new one the keybord does not come up

  • Special field in FBL3N

    Hello, Would You help me the next problem: I've added new field to GL line item report, which is vendor number (this is not offsetting account number). Is it possible to add description from vendor master data? BR, Natalija

  • Nokia responds to reports about the N900 micro-usb...

    Hi all, we have just received the following statement from Nokia regarding the micro-USB port of the Nokia N900: We are aware of reports that under certain conditions, the micro-USB port of a very limited amount of Nokia N900 devices can be detached.