Object Type 'StandardMaterial' in Bapi explorer not browsable.

Hi,
In bapi explorer when we drill down as Logistics-general --> Logistics basic Data --> StandardMaterial.
Till here i can drill down, but when i click on the methods available in it 'StandardMaterial', it doesn't display the methods details and give informative message as ''The requested information has not been found".
Is it a know problem, bcos we have done a fresh installation and no changes being done, still problem exists. Point to remember, its IDES system. Searched for any OSS notes, not present.
One thing i found out, the object type 'BUS1001006' is delegated to delegation type 'ZRSP1001', which is not implemented. Is it advisable to either implement the delegation or delete the delegation.
Thnx in advance.

Guys,
Deleted the delegation type "ZRSP1001" as it doesn't have any extra functionality implemented in it. Now we are able to browse properly in Bapi.
Taj.

Similar Messages

Object type component method name is not supported by object type BOR

Hi All,
Just want to get your help on the above error message in my workflow step.
The method is successfully created in the BO, no errors, status is released/implemented. This error only occurs when the workflow is triggered by a RFC call using SWE_EVENT_CREATE FM. But when using t.code SWUS or SWUE the workflow will run as expected, no error. And when the erroneous workitem is restarted using SWPR, it will run or continue successfully.
Another thing, this is newly created task and method inserted in the workflow. If i delete this task, the workflow will run successfully when triggered by the same RFC.
Hope you guys have already experienced this kind of error.
Thanks in advance.
Matt

Hi Matt,
I am trying to analyse the problem.
When you trigger the workflow using function module it gives error. But when you trigger using SWUE or restart workflow then you do not get error.
In both the cases ( SWUE or restart workflow ) event is getting called using system. But when you trigger it prgramatically it throws error. I hope you are triggering it correctly.
But as you are saying, when you delete the task and method it works fine. So that means it should not be triggering issue.
Just do consistency check for the business object. Check if there is any issue in method.

Event of delegeted Object type not showing up in event trace

Hi,
Please forgive me if this question has already been posted, I created a subtype for the object BUS2032 as ZSALESDOC and delegated the later the to the standard object type BUS2032 , but when i create a sales order it is not showing up in the event trace (TCODE : SWEL), only standard object type BUS2032 is showing up, and the ZSALESDOC object type's CREATED event is not showing up, Please i need inputs on any other thing i am missing out for delegating this object.
Regards
Narendiran Rathinavelu

Hi
check whether you have done the following after delegation:
Event creation in status management(BSVW)
Press Customer settings
New entries
enter status(VBK) - Your copied object type ZSALESDOC
Status Restrictions
I00002 (syst Status) ..REL (released)..SAVE and see once again
Reward points if useful
Regards
Anji

Object type not visible in transaction bapi

hi all.
I'm very new to Bapi,and recently I created a custom object type 'ZTEST' which was inherit from oject 'BUS1001'(material),then I add some custom method(BAPI) to 'ZTEST'.After I released all the object type 'ZTEST', I go to BAPI Explorer(t-code : BAPI), there I found my object 'ZTEST' exist in Alphabetical list but not in hierarchical list.
How can I add my object type to the hierarchical list?
thanks in advance

Hi Bhokal,
I suggest you put the question under ABAP General or similar category as this is not directly related to CRM 7.0 - in order to get faster response to the question.
I hope it helps.
Thanks,
Rohit

Object type RSDS not supported in BAPI source system

Hi
We have a problem when trying to create Data Source in NW2004s with 3rd party tool 'Ascential Datastage' as source system.The error message is "DataSource XXX (DS-DEV): Object type RSDS not supported in BAPI source system".
Is there any note or patch avaialable to be implemented to resolve this problem.Our support package is 07.
Regards
D.Ellora
Message was edited by:
Ellora Dobbala

Hi Ellora,
The latest BI release in SAP NetWeaver 7.0 (2004s) includes a new type of DataSource for which staging BAPI has not yet been aligned.
Third party ETL tool vendors can therefore only implement their load processes using the original type of DataSource from BW 3.x. This DataSource is still provided in the new release without any changes. Upgrading to NetWeaver 7.0 (2004s) BI (BI 7.0) does not therefore endanger existing implementations based on BW 3.x and NetWeaver 2004 (BW 3.5).
It is also possible to migrate third party ETL implementations based on BW 3.x into the new data-flow concept of a NetWeaver 7.0 (2004s) BI environment using new DataSources, transformations (also new), and data transfer processes (DTP) (also new). This is possible because the system provides an emulated view for BW 3.x DataSources, which makes it possible to combine them with NetWeaver 7.0 (2004s) transformations and DTPs for regular batch load processing (this does not include direct access and real-time data acquisition (RDA)).
This allows the benefits of the new data loading concept to be made available in such third party ETL-based loading scenarios.
Regards,
Anil

BAPI not showing in BAPI Explorer

HI,
I have just created a BAPI, but it is not being shown in the BAPI Explorer. Are there any specific checks that I can perform to make sure that everything was created in the correct manner? And how do I get the BAPI to display in BAPI Explorer?
Regards,
Munish

HI,
You can use the BAPI explorer to get a step by step instruction / checklist in how to create a BAPI. In the BAPI explorer select the Project tab.
When the Business object has been checked and the documentation created, the following steps must be carried out:
1) Release the BAPI function module (in the Function Builder).
2) Release the business object type (in the BOR ObjectType -> Change release status to -> Implemented ).
3) Release the BAPI as a method in the BOR (Release the methods you has created - Set the cursor on the method then Edit -> Change release status -> Object type component -> To released )
4) For potential write BAPIs: Release the IDoc and its segments
You can now display the BAPI in the BAPI Explorer:
Assign the Points if this is helpful
Regards
Sudheer

I can't see release business object in bapi explorer.

Hi,
i can't see my business object in bapi explorer which is already released.
Regards,
Gurprit

Hello Gurprit
I am not sure whether customer BAPIs are displayed in the BAPI explorer at all. However, you could try to push the button with the filter icon and choose option "All (BAPIs)".
Regards
Uwe

BAPI 001 No instance of object type purchaseorder has been created

Hello All,
I get teh following error message in SC monitor (backend application error) as well as in RZ20. I tried to push into backend but no luck.Scenario Classic.SRM 5.0
Shopping cart XXXXX(PO XXXXX) BAPI 001 No instance of object type purchaseorder has been created.
The latest log in BBP_PD
0000000001 I1111 Item in Transfer Process X
0000000001 I1112 Error in transmission
Any clue is appreciated.
Muthu
Edited by: Muthuraman Govindasamy on Oct 7, 2008 2:59 PM

Hi Andrea
We can create a PO vis sourcing cockpit in classic mode.
SC: Error in transmission BAPI 001
Note :- 973952 and follow the Peter instructions. This error message misleads
regards
Muthu

BAPI Not appearing in BAPI Explorer

Hi,
I have created a business object in SW01 and released it.But it does not appear in bapi explorer.
I am using ECC 6.0
Please guide me.
Regards,
Sanjay

hi sanjay
you should refer to this link for the solution of your problem
http://help.sap.com/saphelp_nw04/helpdata/en/68/891e3aa03ddb0fe10000000a11402f/frameset.htm
regards
Saurabh goel

OSB to Object Types: difference between NULL value and not available

Hello all,
I have a question about Object Types. More specifically, how to differentiate between an empty value (null) and a string not available.
This is my case:
I have created an object type with three parameters.
CREATE OR REPLACE TYPE OSB_EMP_OBJ_TYPE AS OBJECT
(EMP_ID NUMBER
,DEPT_ID NUMBER
,ORDER_ID NUMBER
,CONSTRUCTOR FUNCTION OSB_EMP_OBJ_TYPE
RETURN self as result
/I would like to see what happens when I put an empty string into emp_id, NULL into DEPT_ID and nothing into ORDER_ID.
To do so I have this test script:
declare
p_emp OSB_EMP_OBJ_TYPE := OSB_EMP_OBJ_TYPE();
begin
p_emp.EMP_ID := '';
p_emp.DEPT_ID := null;
-- p_emp.ORDER_ID := null;
if p_emp.EMP_ID is null
then
    dbms_output.put_line('Empty');
end if;
if p_emp.DEPT_ID is null
then
    dbms_output.put_line('NULL');
end if;
if p_emp.ORDER_ID is null
then
    dbms_output.put_line('Not available');
end if;
end;The result of this is:
Empty
NULL
Not availableIt seems that Oracle treats all three situations alike. What I would like to achieve is a way to see that p_emp.ORDER_ID was not initialized.
To elaborate a bit: in our production system this procedure would be called from OSB and the object type would by the input for that procedure. Our database version is 10.2.0.5.0.
Our procedures look something like this:
procedure p_procedure ( p_emp in osb_emp_obj_type )
is
begin
do_something;
end;Can anyone tell me if there is a way to achieve this, so I can see whether or not a value in the object type was filled?
Thanks in advance!

Darn...
Eventually we want to use this for an update procedure. The client gets all current data from the database by calling a webservice that (using OSB) selects the data from our database. What we want to achieve is that the client can update that data, by returning only the changed fields to an update procedure.
We then handle an empty tag to update the field to null, and we ignore missing tags.
OSB itself can handle this, but PL/SQL can't.
I'm now thinking of adding an indicator to each optional field (clear_field_yn). OSB can still check for empty tags or missing tags. When a tag is empty, it's corresponding indicator will be set to 'Y'. If the tag is missing, then it will be set to 'N'.
Is that a solution to consider, or is there a much simpler approach possible?

E5 - unable to open. object type not supported

hi.
2 Month back i brought Nokia E-5 Mobile and after few weeks i upgraded the Memory from 2Gb to 8GB. After copying all files from 2gb to 8gb am not able to open or install any existing programs and files. Even maps are not working. When trying to open or install the files am getting this erro " unable to open object type not supported " . Kindly help on this error.
Thanks
Velavan

I have never attempted what you did, so can't say for certain, but I don't think memory card data is meant to be copied from one card to another (unless we're talking about data files like pictures or mp3's). I don't understand what you mean by being unable to install files. Are you trying to reinstall the programs that aren't working? If your 2GB card still works normally, I suggest you format the 8 GB card, reinstall the programs to the empty card, and re-download the maps data. If the programs still give you trouble, you may need to uninstall them from the 2 GB card first, but I don't think that should be necessary. I hope that helps.

Error: Object type '' could not be generated when creating sales order

Hello Friends,
I am using a SAP standard ITS service to create sales order.
When I am creatin SO, it gives me error Object type '' could not be generated.
Can you plz suggest me what is that issue & how I can reslove it.
Regards,
Narendra

any inputs around this plz??

IDoc Error -Instance of object type could not be changed

Hi All
I am getting IDoc failed with the error massaeg "Instance of object type could not be changed"
Message type :PORDCR
Basic type : PORDCR05
Message no. BAPI003
Status : 51
Please suggest on this
Thanks
Ajit

Hi Madhu
All these POs are uploaded during the Cutover Activities only, I am not sure whether it is uploaded through LSMW or not. What I guess is If its uploaded thrugh LSMW , then we can't change any value in the PO.
Please sugest how can I process allthese IDocs.
Thanks
Ajit

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);

IDoc failed with the error massaeg "Instance of object type could not be ch

Hi All
I am getting IDoc failed with the error massaeg "Instance of object type could not be changed"
Message type :PORDCR
Basic type : PORDCR05
Message no. BAPI003
Status : 51
All POs are get uploaded in SAP during Cut over activities only.
Please suggest on this.It will be a great help.
Thanks
Ajit

Hi
After uploading POs into SAP we are changing quantity and value in PO in Legacy system, and for this all IDocs are failed, subsequently these changes are not triggering to ECC.
Please help
Thanks
Ajit

Object Type 'StandardMaterial' in Bapi explorer not browsable.

Similar Messages

Maybe you are looking for