Error while creating fixed asset using BAPI BAPI_FIXEDASSET_OVRTAKE_CREATE

Hi
I am getting an error stating "O DEP START field is not ready for input, while trying to create asset using the BAPI BAPI_FIXEDASSET_OVRTAKE_CREATE.How to make the field input enabled in BAPI .Kindly suggest.
Thanks

Hello,
Review AO21.
Regards
Waza

Similar Messages

Error while creating activity by using BAPI

Hi,
While creating activity by using BAPI Im getting error as follows,
Start processing of refference object handle generated.
Integrity rule a d0008 broken
business partner with function from vbkakom not vbpakom
Integrity rule a d0008 broken
edit all incomplete field .
Please help me for solving this issue.
Regards,
Suresh

Not received any proper reply Closing the issue.

Error while Creating WBS element using BAPI 'BAPI_BUS2054_CREATE_MULTI'

Hi Expert,
I've a requirement to create WBS elements using BAPI. And I am using BAPIs in the following manner.
CALL FUNCTION 'BAPI_PS_INITIALIZATION'
CALL FUNCTION 'BAPI_BUS2054_CREATE_MULTI'
 EXPORTING
 i_project_definition = g_pdwbs
TABLES
 it_wbs_element = it_wbs_element
 et_return = it_return
EXTENSIONIN =
EXTENSIONOUT =
 CALL FUNCTION 'BAPI_PS_PRECOMMIT'
 CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
When I do so I am getting the below errors. Please suggest.
"Individual check for creating the object WBS Element C-497082 required ".
"Individual check for creating the object WBS Element C-497082-0001 required".
Please suggest how to correct this error.
<REMOVED BY MODERATOR - REQUEST OR OFFER POINTS ARE FORBIDDEN>
Edited by: Alvaro Tejada Galindo on Aug 18, 2008 5:25 PM

I am getting the same error, but I cannot figure it out how to detect it and fix it. Will you please share your solution?
Thanks,

Error while creating Legacy Asset using AS91

Error is as follows
E698 SYST: Abnormal termination (ANLB-LGJAN 1 not equal to ANLC-GJAHR
In 2008 during implementation, there was a mis match between FI & AA.
In AA Takeover values were not updated but GL entry was made. Now since depreciation is run, it is not allowing to update takeover values in AS92.
Now the i have planned to follow this procedure
Firstly Reset Depreciation
Then to create new Assets in AA copying previous assets without Takeover values using AS 91 & update those takeover values in new assets.
Then FI & AA values would match & then i can run depreciation.
But in 2nd step i am stucked, as when i try creating new asset using AS91 it is giving above error.
What should be date of legacy data transfer in spro? i have maintained 30.09.2008
In OAAQ i have maintained closed FY =2007
In OB52 i have Opened both 2008 & 2009 posting periods.
What more has to be done?

Hi Paul
I have taken a production copy in different client & have done all these with the client's permission.
Following are the reasons with example
suppose these are 4 assets at the time of implementation
1 Asset A       Acquisition value 100000/-      Accumulated Depreciation       20000/-
2 Asset B       Acquisition value 200000/-      Accumulated Depreciation       30000/-
3 Asset C       Acquisition value 300000/-      Accumulated Depreciation       40000/-
4 Asset D       Acquisition value 400000/-      Accumulated Depreciation       50000/-
In implementation following happened by mistakenly
Asset A & B were properly created using AS91 & in GL also entry properly made using OASV
but for Asset C, entry was made using OASV but in AA Tcode AS91 Asset Master was created but Takeover values were not updated.
for Asset D entry was made in OASV but in AA Asset number was not at all created.
so when you see asset master C in AW01N acquisition value is blank & planned depreciation is also missing.
i think individually all data was not cross tallyied.
So the Balance sheet is tallyied with entry in FI
but
in AA there are 100 assets without takeover values & 300 assets for which Asset Masters are not at all created in AA.
& depreciation for 2008 has been run on other assets excluding these 400 assets.
So now AA closing cannot be done as the FI & AA balances are not reconciled.
& now we have to update takeover values creating new asset masters using AS91 but system is not allowing us.
Could you suggest some solution for these problems
Thanks in Advance

Error while creating the ASSET using LSMW BAPI method ( BUS1022 )

Hello,
Im creating assets using the below LSMW BAPI method
Business Object      BUS1022
Method                     CREATEINCLVALUES
Message Type         FIXEDASSET_CREATEINCLVALU
Basic Type              FIXEDASSET_CREATEINCLVALU
the following errors were triggered while populating the values to ACQ_VALUE and ORD_DEP value.
Correction to ordinary dep. greater than acc. dep. in area 01
Correction to ordinary dep. greater than acc. dep. in area 30
Correction to ordinary dep. greater than acc. dep. in area 31
Correction to ordinary dep. greater than acc. dep. in area 32
if i pass only ACQ_VALUE, I am able to create the asset with out any issues.
Can you guys plz guide me to fix this issue to create the asset with both ACQ_VALUE and ORD_DEP values??
Cheers,
Sriram.

Hello,
Review AO21.
Regards
Waza

Unable to capture error message while creating an SO using bapi

Hi,
Can anybody suggest how to capture the error message while creating a SO using BAPI.
I have developed a customeized BAPI and using the BDC format to create the SO.
Note: i am using a call transaction method for the BDC.
I am sending the message into message1.
but i am unable to send the same into an internal table
shyam.

Hi Shyam
If my understanding is correct, you are performing BDC process within the customized BAPI...
And you want to collect the messages from BDC to an internal table and pass to the output.
Proceed as below:
1. While calling BDC, use CALL TRANSACTION .... with addition: MESSAGES INTO itab. The structure of itab should be like BDCMSGCOLL.
2. Now the messages will be collected in ita.
3. Prepare the messages using FM: FORMAT_MESSAGE
4. Collect to the returning table.
Hope this helps...
Though i could not understand the reason of creating a BDC within BAPI, you can opt for loading orders via BAPI's like: BAPI_SALESORDER_CREATEFROMDAT1 or BAPI_SALESORDER_CREATEFROMDAT2.
Kind Regards
Eswar

Error while creating resource group using non-globalzones.

Dear all,
Hi techs please guide me how to create failover resource group in nongloablzones.
I'm getting error while creating resource group using non-globalzones.
My setup:
I have two node cluster running sun cluster 3.2 configured and running properly.
node1: sun5
nide2: sun8
I have create non-globalzone "zone1" in node:sun5
I have create non-globalzone "zone2" in node:sun8
node:sun5# clrg create -n sun5:zone1,sun8:zone2 zonerg
*(C160082) WARNING: one or more zones in the node list have never been fully booted in the cluster mode,verify that correct zone name was entered.*
kindly guide me how to create Apache resource group using non-glabalzones, i'm new to sun cluster 3.2. please guide me step by step information.
Thanks in advance,
veera
Edited by: veeraa on Dec 19, 2008 1:54 AM

Hi Veera,
Actually you are getting a warning message where one of two things could have happened. Either you specified an incorrect zone name or one of the zones has not been fully booted. It's likely that you haven't booted the zones, so please follow this:
zoneadm list -iv
If zone1 or zone2 are not running then boot and configure them
zoneadm -z <zone> boot
zlogin -C <zone>
After that you can continue to follow the step by step instructions at
http://docs.sun.com/app/docs/doc/819-2975/chddadaa?a=view
These may also help
http://blogs.sun.com/Jacky/entry/a_simple_expample_about_how
http://blogs.sun.com/SC/en_US/entry/sun_cluster_and_solaris_zones
Regards
Neil

Create Excise invoice(J1IIN) document while creating billing document using bapi BAPI_BILLINGDOC_CREATEMULTIPLE

Dear Experts,
My scenario is:
We have batch split scenario, where the parent line item of billing document has 0 quantity and its subsequent item (item with batch number) holds actual quantity data.
When we create billing document using VF01 against delivery document, system creates billing document along with excise invoice document (J1IIN Document). And in excise document contain same number of line items that of billing document. Please see the below attachment:
Biiling document screen shot:
While creating billing document, the J1IIN Document created automatically. Below is the screen-shot for the same.
Now the issue is:
When we create billing document using BAPI: BAPI_BILLINGDOC_CREATEMULTIPLE system creating only billing document and not creating excise invoice document.
When we create excise document manually using J1IIN the zero quantity line items are excluded in excise invoice document.
Please see the below screen-shot for the same; The z quantity line items are missing.
We want excise document to be created while creating billing document using BAPI BAPI_BILLINGDOC_CREATEMULTIPLE. Or is there any other BAPI for the same purpose.
Customization is also maintained for creating excise invoice document automatically.
Regards,
Rajesh Sadula.

HI
Pricing will be carried basing on the pricing
procedure.
Case1: Prices will be carried out automatically if
necessary condition records are maintained for the
condition type.
For this you can go to Sales Order-> Item Conditions
In the screen you can click on command button Analysis,
which gives you the list of condition types associated
to the pricing procedure. By clicking on the condition
type you can know the action that has taken place.
Case2: Manually forcing prices for Items.
To do this, you have to populate ORDER_CONDITIONS_IN &
ORDER_CONDITIONS_INX. Also note to identify the item
numbers, you manually pass the item number for each item
in the sales order, use the same item number for
populating conditions.
Parameters required:
ORDER_CONDITIONS_IN:
ITM_NUMBER, COND_TYPE, COND_VALUE, CURRENCY
ORDER_CONDITIONS_INX:
ITM_NUMBER, COND_TYPE, UPDATEFLAG, COND_VALUE,CURRENCY.
Hope the above info helps you. Do revert back if you
need more info.
Kind Regards
Eswar

Error while creating new projects using api

Hello,
I am having error while creating projects using standard api, PA_PROJECT_PUB.CREATE_PROJECTS. The error I am having is as follow.
Source template ID is invalid.
===
My code is as follow:
SET SERVEROUTPUT ON SIZE 1000000
SET VERIFY OFF
define no=&amg_number
DECLARE
-- Variables used to initialize the session
l_user_id NUMBER;
l_responsibility_id NUMBER;
cursor get_key_members is
select person_id, project_role_type, rownum
from pa_project_players
where project_id = 1;
-- Counter variables
a NUMBER := 0;
m NUMBER := 0;
-- Variables needed for API standard parameters
l_commit VARCHAR2(1) := 'F';
l_init_msg_list VARCHAR2(1) := 'T';
l_api_version_number NUMBER :=1.0;
l_return_status VARCHAR2(1);
l_msg_count NUMBER;
l_msg_data VARCHAR2(2000);
-- Variables used specifically in error message retrieval
l_encoded VARCHAR2(1) := 'F';
l_data VARCHAR2(2000);
l_msg_index NUMBER;
l_msg_index_out NUMBER;
-- Variables needed for Oracle Project specific parameters
-- Input variables
l_pm_product_code VARCHAR2(30);
l_project_in pa_project_pub.project_in_rec_type;
l_key_members pa_project_pub.project_role_tbl_type;
l_class_categories pa_project_pub.class_category_tbl_type;
l_tasks_in pa_project_pub.task_in_tbl_type;
-- Record variables for loading table variables above
l_key_member_rec pa_project_pub.project_role_rec_type;
l_class_category_rec pa_project_pub.class_category_rec_type;
l_task_rec pa_project_pub.task_in_rec_type;
-- Output variables
l_workflow_started VARCHAR2(100);
l_project_out pa_project_pub.project_out_rec_type;
l_tasks_out pa_project_pub.task_out_tbl_type;
-- Exception to call messag handlers if API returns an error.
API_ERROR EXCEPTION;
BEGIN
-- Initialize the session with my user id and Projects, Vision Serves (USA0
-- responsibility:
select user_id into l_user_id
from fnd_user
where user_name = 'SSHAH';
select responsibility_id into l_responsibility_id
from fnd_responsibility_tl
where responsibility_name = 'Projects Implementation Superuser';
pa_interface_utils_pub.set_global_info(
p_api_version_number => l_api_version_number,
p_responsibility_id => l_responsibility_id,
p_user_id => l_user_id,
p_msg_count => l_msg_count,
p_msg_data => l_msg_data,
p_return_status => l_return_status);
if l_return_status != 'S' then
raise API_ERROR;
end if;
-- Provide values for input variables
-- L_PM_PRODUCT_CODE: These are stored in pa_lookups and can be defined
-- by the user. In this case we select a pre-defined one.
select lookup_code into l_pm_product_code
from pa_lookups
where lookup_type = 'PM_PRODUCT_CODE'
and meaning = 'Conversion';
-- L_PROJECT_IN: We have to provide values for all required elements
-- of this record (see p 5-13, 5-14 for the definition of the record).
-- Customers will normally select this information from some external
-- source
l_project_in.pm_project_reference := 'AGL-AMG Project &no';
l_project_in.project_name := 'AGL-AMG Project &no';
l_project_in.created_from_project_id := 1;
l_project_in.carrying_out_organization_id := 2864; /*Cons. West*/
l_project_in.project_status_code := 'UNAPPROVED';
l_project_in.start_date := '01-JAN-11';
l_project_in.completion_date := '31-DEC-11';
l_project_in.description := 'Trying Hard';
l_project_in.project_relationship_code := 'Primary';
-- L_KEY_MEMBERS: To load the key member table we load individual
-- key member records and assign them to the key member table. In
-- the example below I am selecting all of the key member setup
-- from an existing project with 4 key members ('EE-Proj-01'):
for km in get_key_members loop
-- Get the next record and load into key members record:
l_key_member_rec.person_id := km.person_id;
l_key_member_rec.project_role_type := km.project_role_type;
-- Assign this record to the table (array)
l_key_members(km.rownum) := l_key_member_rec;
end loop;
-- L_CLASS_CATEGORIES: commented out below should fix the error we get
-- because the template does not have an assigment for the mandatory class
-- 'BAS Test'
l_class_category_rec.class_category := 'Product';
l_class_category_rec.class_code := 'Non-classified';
-- Assign the record to the table (array)
l_class_categories(1) := l_class_category_rec;
-- L_TASKS_IN: We will load in a single task and a subtask providing only
-- the basic fields (see pp. 5-16,5-17,5-18 for the definition of
-- the task record)
l_task_rec.pm_task_reference := '1';
l_task_rec.pa_task_number := '1';
l_task_rec.task_name := 'Construction';
l_task_rec.pm_parent_task_reference := '' ;
l_task_rec.task_description := 'Plant function';
-- Assign the top task to the table.
l_taskS_in(1) := l_task_rec;
-- Assign values for the sub task
l_task_rec.pm_task_reference := '1.1';
l_task_rec.pa_task_number := '1.1';
l_task_rec.task_name := 'Brick laying';
l_task_rec.pm_parent_task_reference := '1' ;
l_task_rec.task_description := 'Plant building';
-- Assign the subtask to the task table.
l_tasks_in(2) := l_task_rec;
-- All inputs are assigned, so call the API:
pa_project_pub.create_project
(p_api_version_number => l_api_version_number,
p_commit => l_commit,
p_init_msg_list => l_init_msg_list,
p_msg_count => l_msg_count,
p_msg_data => l_msg_data,
p_return_status => l_return_status,
p_workflow_started => l_workflow_started,
p_pm_product_code => l_pm_product_code,
p_project_in => l_project_in,
p_project_out => l_project_out,
p_key_members => l_key_members,
p_class_categories => l_class_categories,
p_tasks_in => l_tasks_in,
p_tasks_out => l_tasks_out);
-- Check the return status, if it is not success, then raise message handling
-- exception.
IF l_return_status != 'S' THEN
dbms_output.put_line('Msg_count: '||to_char(l_msg_count));
dbms_output.put_line('Error: ret status: '||l_return_status);
RAISE API_ERROR;
END IF;
-- perform manual commit since p_commit was set to False.
COMMIT;
--HANDLE EXCEPTIONS
EXCEPTION
WHEN API_ERROR THEN
FOR i IN 1..l_msg_count LOOP
pa_interface_utils_pub.get_messages(
p_msg_count => l_msg_count,
p_encoded => l_encoded,
p_msg_index => i,
p_msg_data => l_msg_data,
p_data => l_data,
p_msg_index_out => l_msg_index_out);
dbms_output.put_line('ERROR: '||to_char(l_msg_index_out)||': '||l_data);
END LOOP;
rollback;
WHEN OTHERS THEN
dbms_output.put_line('Error: '||sqlerrm);
FOR i IN 1..l_msg_count LOOP
pa_interface_utils_pub.get_messages(
p_msg_count => l_msg_count,
p_encoded => l_encoded,
p_msg_index => i,
p_msg_data => l_msg_data,
p_data => l_data,
p_msg_index_out => l_msg_index_out);
dbms_output.put_line('ERROR: '||to_char(l_msg_index_out)||': '||l_data);
END LOOP;
rollback;
END;
===
Msg_count: 1
Error: ret status: E
ERROR: 1: Project: 'AGL-AMG Project 1123'
Source template ID is invalid.
PL/SQL procedure successfully completed.

I was using a custom Application, which had a id other then 275 (which belongs to Oracle projects)

Error while creating new crosstab using

I am getting the following error while creating a new crosstab object within Swing application. This error has started coming after we applied Oracle patch 9206 on database. The error originates from one of the classes in the olap_api_92.jar.
==========================================================
Wed Feb 02 09:13:51 CST 2005 In BuilderWizardValidateAdapter::wizardValidatePage
oracle.express.idl.util.OlapiException: No more data to read from socket
 at oracle.express.idl.ExpressOlapiDataSourceModule.DefinitionManagerInterfaceStub.crtCurMgrs2(DefinitionManagerInterfaceStub.java:927)
 at oracle.express.olapi.data.full.DefinitionManagerSince9202.createOLAPICursorManagers(DefinitionManagerSince9202.java:611)
 at oracle.express.olapi.data.full.ExpressDataProvider.createCursorManagers(ExpressDataProvider.java:1325)
=========================================================
Please check the BIcheckconfig output. It does not show any errors.
=========================================================
<?xml version="1.0" encoding="UTF-8" ?>
<BICheckConfig version="1.0.2.0">
<Check key="JDEV_ORACLE_HOME" value="C:\Mohan\Installs\Jdev904"/>
<Check key="JAVA_HOME" value="C:\Mohan\Installs\Jdev904\jdk"/>
<Check key="JDeveloper version" value="9.0.4.0.1419"/>
<Check key="BI Beans release description" value="BI Beans 9.0.4 Production Release"/>
<Check key="BI Beans component number" value="9.0.4.23.0"/>
<Check key="BI Beans internal version" value="2.7.5.32"/>
<Check key="host" value="db03schgefage"/>
<Check key="port" value="1521"/>
<Check key="sid" value="biolapp"/>
<Check key="user" value="nairs5"/>
<Check key="Connecting to the database" value="Successful"/>
<Check key="JDBC driver version" value="9.2.0.4.0"/>
<Check key="JDBC JAR file location" value="C:\Mohan\Installs\Jdev904\jdev\lib\patches"/>
<Check key="Database version" value="9.2.0.6.0"/>
<Check key="OLAP Catalog version" value="9.2.0.6.0"/>
<Check key="OLAP AW Engine version" value="9.2.0.6.0"/>
<Check key="OLAP API Server version" value="9.2.0.6.0"/>
<Check key="BI Beans Catalog version" value="N/A; not installed in nairs5"/>
<Check key="OLAP API JAR file version" value="9.2"/>
<Check key="OLAP API JAR file location" value="C:\Mohan\Installs\Jdev904\jdev\lib\ext"/>
<Check key="OLAP API Metadata Load" value="Successful"/>
<Check key="Number of metadata folders" value="3"/>
<Check key="Number of metadata measures" value="569"/>
<Check key="Number of metadata dimensions" value="5"/>
<Check key="OLAP API Metadata">
<![CDATA[==============================================================================
Type Name (S=Schema, C=Cube, M=Measure, D=Dimension)
========= ====================================================================
Folder... ROOT
Folder... Auto Claim Measures
Folder... Service Measures
Folder... Claim Counts
Folder... Cell Summary Cube
Folder... Actual Measures
Measure.. Actual Acceptance Rate
Measure.. Actual Annualized Bill amt
Measure.. Actual Application Count
Measure.. Actual Avg Annual Billing
Measure.. Actual Contacts Count
Measure.. Actual Commission Amt
 at oracle.express.olapi.data.full.ExpressDataProvider.internalCreateCursorManager(ExpressDataProvider.java:680)
 at oracle.express.olapi.data.full.ExpressDataProvider.createCursorManager(ExpressDataProvider.java:586)
 at oracle.olapi.data.source.DataProvider.createCursorManager(DataProvider.java:268)
 at oracle.dss.dataSource.QueryUtilities.setUpCursors(QueryUtilities.java:559)
 at oracle.dss.dataSource.QueryServer._setUpCursorsForMainQuery(QueryServer.java:7039)
 at oracle.dss.dataSource.QueryServer._getCursorForCube(QueryServer.java:4098)
 at oracle.dss.dataSource.QueryServer._updateCube(QueryServer.java:4055)
 at oracle.dss.dataSource.QueryServer._applySelections(QueryServer.java:2661)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at oracle.dss.util.Operation.execute(Operation.java:69)
 at oracle.dss.dataSource.OperationQueue.update(OperationQueue.java:68)
 at oracle.dss.dataSource.common.BaseOperationQueue.addOperation(BaseOperationQueue.java:176)
 at oracle.dss.dataSource.common.BaseOperationQueue.addOperation(BaseOperationQueue.java:146)
 at oracle.dss.dataSource.QueryServer.queueOperation(QueryServer.java:7076)
 at oracle.dss.dataSource.QueryServer.applySelection(QueryServer.java:2192)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at oracle.dss.util.Operation.execute(Operation.java:69)
 at oracle.dss.dataSource.QueryManagerServer.sendQueue(QueryManagerServer.java:1549)
 at oracle.dss.dataSource.common.OperationQueue.update(OperationQueue.java:198)
 at oracle.dss.dataSource.common.BaseOperationQueue.addOperation(BaseOperationQueue.java:176)
 at oracle.dss.dataSource.common.BaseOperationQueue.addOperation(BaseOperationQueue.java:146)
 at oracle.dss.dataSource.common.OperationQueue.addOperation(OperationQueue.java:127)
 at oracle.dss.dataSource.client.QueryClient.applySelection(QueryClient.java:970)
 at oracle.dss.dataSource.common.QueryQueryAccess$SelCursor.getDataAccess(QueryQueryAccess.java:1133)
 at oracle.dss.dataSource.common.QueryQueryAccess.getDataAccess(QueryQueryAccess.java:278)
 at oracle.dss.datautil.QueryAccessUtilities._getValues(QueryAccessUtilities.java:639)
 at oracle.dss.datautil.QueryAccessUtilities._getValues(QueryAccessUtilities.java:705)
 at oracle.dss.datautil.QueryAccessUtilities.getValues(QueryAccessUtilities.java:608)
 at oracle.dss.queryBuilder.QueryBuilderUtils.getSelectedMeasures(QueryBuilderUtils.java:623)
 at oracle.dss.queryBuilder.SelectedItemsPanel.populateTree(SelectedItemsPanel.java:298)
 at oracle.dss.queryBuilder.SelectedItemsPanel.refreshTree(SelectedItemsPanel.java:333)
 at oracle.dss.queryBuilder.SelectedItemsPanel.setActive(SelectedItemsPanel.java:366)
 at oracle.dss.queryBuilder.ItemsPanel.setActive(ItemsPanel.java:251)
 at oracle.dss.datautil.gui.DefaultBuilderDialog.setActive(DefaultBuilderDialog.java:1072)
 at oracle.dss.datautil.gui.DefaultBuilderDialog.validateNextPreviousEvent(DefaultBuilderDialog.java:1396)
 at oracle.dss.datautil.gui.DefaultBuilderDialog$BuilderWizardValidateAdapter.wizardValidatePage(DefaultBuilderDialog.java:2113)
 at oracle.bali.ewt.wizard.WizardPage.processWizardValidateEvent(Unknown Source)
 at oracle.bali.ewt.wizard.WizardPage.validatePage(Unknown Source)
 at oracle.dss.datautil.gui.CustomImageWizardPage.validatePage(CustomImageWizardPage.java:81)
 at oracle.bali.ewt.wizard.BaseWizard.validateSelectedPage(Unknown Source)
 at oracle.bali.ewt.wizard.BaseWizard.doNext(Unknown Source)
 at oracle.dss.datautil.gui.CustomWizard.doNext(CustomWizard.java:415)
 at oracle.bali.ewt.wizard.BaseWizard$Action.actionPerformed(Unknown Source)
 at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1786)
 at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1839)
 at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
 at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
 at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:245)
 at java.awt.Component.processMouseEvent(Component.java:5100)
 at java.awt.Component.processEvent(Component.java:4897)
 at java.awt.Container.processEvent(Container.java:1569)
 at java.awt.Component.dispatchEventImpl(Component.java:3615)
 at java.awt.Container.dispatchEventImpl(Container.java:1627)
 at java.awt.Component.dispatchEvent(Component.java:3477)
 at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:3483)
 at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3198)
 at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3128)
 at java.awt.Container.dispatchEventImpl(Container.java:1613)
 at java.awt.Window.dispatchEventImpl(Window.java:1606)
 at java.awt.Component.dispatchEvent(Component.java:3477)
 at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
 at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
 at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
 at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:141)
 at java.awt.Dialog$1.run(Dialog.java:540)
 at java.awt.Dialog.show(Dialog.java:561)
 at java.awt.Component.show(Component.java:1133)
 at java.awt.Component.setVisible(Component.java:1088)
 at oracle.bali.ewt.wizard.WizardDialog.runDialog(Unknown Source)
 at oracle.dss.datautil.gui.DefaultBuilderDialog.runDialog(DefaultBuilderDialog.java:489)
 at oracle.dss.datautil.gui.DefaultBuilderDialog.run(DefaultBuilderDialog.java:466)
 at oracle.dss.queryBuilder.QueryBuilder.run(QueryBuilder.java:2401)
 at gecf.pmg.PmgBiOlapApp.newCrosstabWiz(PmgBiOlapApp.java:1622)
 at gecf.pmg.PmgBiOlapApp.mNewCrosstab_ActionPerformed(PmgBiOlapApp.java:1563)
 at gecf.pmg.PmgBiOlapApp$5.actionPerformed(PmgBiOlapApp.java:696)
 at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1786)
 at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1839)
 at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
 at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
 at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:245)
 at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:231)
 at java.awt.Component.processMouseEvent(Component.java:5100)
 at java.awt.Component.processEvent(Component.java:4897)
 at java.awt.Container.processEvent(Container.java:1569)
 at java.awt.Component.dispatchEventImpl(Component.java:3615)
 at java.awt.Container.dispatchEventImpl(Container.java:1627)
 at java.awt.Component.dispatchEvent(Component.java:3477)
 at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:3483)
 at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3198)
 at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3128)
 at java.awt.Container.dispatchEventImpl(Container.java:1613)
 at java.awt.Window.dispatchEventImpl(Window.java:1606)
 at java.awt.Component.dispatchEvent(Component.java:3477)
 at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
 at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
 at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
 at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
 at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
 at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)

I suspect that you have either not fully applied the patch or alternatively the patching process did not complete.
If you are using an analytic workspace, connect as OLAPSYS account and run the following commands:
exec CWM2_OLAP_METADATA_REFRESH.MR_REFRESH
exec CWM2_OLAP_METADATA_REFRESH.MR_AC_REFRESH
If this does not resolve the error, and assuming your system worked prior to applying the 9206 patch, then the patch may need to be reapplied.
Hope this helps
Business Intelligence Beans Product Management Team
Oracle Corporation

Error while creating a material using Bapi_material_savedata

Hi,
there is an error encountered while creating a material using BAPI_MATERIAL_SAVEDATA..
The Error description is " Material description is not transfered " even after supplying the Material description and other mandatory field information like industrial sector, material type ,basic view indicator,Base UOM,Base UOM ISO code.
Please let me know the solution, if you know.

Hi,
Please search the SCN for the answers
https://www.sdn.sap.com/irj/scn/advancedsearch?query=errorinBAPI_MATERIAL_SAVEDATA+&cat=sdn_all

Error while creating logical file using transaction FILE

Hello there,
I am facing an error while creating Logical File name definition using transaction FILE
This is the input which I'm trying to give
Logical file name: ZTEST
Name : ZTEST
Physical file : ZTEST_1<DATE><TIME>.csv
Data format: ASC
Application area: BW
Logical path:ZTEST_1_DATAOUT
when I tried to save it throws me an error like ASSIGN_SUBSTRING_NOT_ALLOWED
Please help.

Hi,
Please check the OSS Notes :
Note 792061 - SP Case Locator: Dump: ASSIGN to a substring isn't allowed.
SAP Note 1297989 - Short dump ASSIGN_SUBSTRING_NOT_ALLOWED
Hope this solves the problem.
-Vikram

Error while creating Group Asset

Dear All
While Creating Group Asset I am getting the Following error:
No depreciation area in company code 1000 allows group assets.
Message no. AY160
Diagnosis
You cannot create group assets in company code 1000. There are no depreciation areas that can manage group assets in this company code.
Procedure
Make sure that you really want to create a group asset in company code 1000.
If so, then allow group assets in the desired depreciation areas.
Please advice.
Thanks & Regards
Kanwaljit

Hi,
Check the config in OAYM and OAAX.
Then your issue will get solved.
Thanks,
Srinu

Setting user specific contract data while creating sales order using BAPI

Hi all,
I am creating sales order using BAPI - BAPI_SALESORDER_CREATEFROMDAT2.
Now my problem is that there is no structure for contract data (i.e. VEDA), system automatically set contract data using customization values.
I am doing some validations on cotract data in MV45AFZZ which fails, because these validations are performed on standard values, user specific values r not set.
How to handle this issue, your small clue may help a lot.
Regards,
S@meer

HI
Pricing will be carried basing on the pricing
procedure.
Case1: Prices will be carried out automatically if
necessary condition records are maintained for the
condition type.
For this you can go to Sales Order-> Item Conditions
In the screen you can click on command button Analysis,
which gives you the list of condition types associated
to the pricing procedure. By clicking on the condition
type you can know the action that has taken place.
Case2: Manually forcing prices for Items.
To do this, you have to populate ORDER_CONDITIONS_IN &
ORDER_CONDITIONS_INX. Also note to identify the item
numbers, you manually pass the item number for each item
in the sales order, use the same item number for
populating conditions.
Parameters required:
ORDER_CONDITIONS_IN:
ITM_NUMBER, COND_TYPE, COND_VALUE, CURRENCY
ORDER_CONDITIONS_INX:
ITM_NUMBER, COND_TYPE, UPDATEFLAG, COND_VALUE,CURRENCY.
Hope the above info helps you. Do revert back if you
need more info.
Kind Regards
Eswar

Error while Creating a PO using BAPI_PO_CREATE1

Hi Friends,
     The following issue that I have observed and as explained below is one of the weirdest scenarios that I have seen while working with SAP. Hence, kindly help me with possible errors from my end. I am working on ECC 6.0.
Requirement: To automatically create a PO.
Option used: I have used a BAPI: u2018BAPI_PO_CREATE1u2019
Scenario: When I execute the BAPI u2018BAPI_PO_CREATE1u2019 directly in sequence with u2018BAPI_TRANSACTION_COMMITu2019, the PO gets created successfully. The data entered as input is:
POHEADER-COMP_CODE
POHEADER-DOC_TYPE
POHEADER-PMNTTRMS
POITEM-PO_ITEM
POITEM-QUANTITY
POITEM-TAX_CODE
POITEM-TAXJURCODE
POITEM-RFQ_NO
POITEM-RFQ_ITEM
POITEM-PREQ_NO
POITEM-PREQ_ITEM
POITEM-PREQ_NAME
POSCHEDULE-PO_ITEM
POSCHEDULE-SCHED_LINE
POSCHEDULE-QUANTITY
POSCHEDULE-PREQ_NO
POSCHEDULE-PREQ_ITEM
Problem: I need to pass data to the BAPI through code, so I called the BAPI u2018BAPI_PO_CREATE1u2019 and u2018BAPI_TRANSACTION_COMMITu2019 in a test function module as well as report. I passed the same data as mentioned above i.e. while creating the PO by passing data to the BAPI directly.
But the BAPI returns an error BAPI header data still faulty, enter plant, Pur. Org., Pur. Grp., etc.
I tried by passing all the available data for the header and then for the items, but finally, I still get an error that the item is from a different order account and just cannot create a PO.
The Test FM code is as shown below:
DATA : PYMNT_TERMS    TYPE YOAF_SEC_MASTER-TER_PYMNT.
DATA : ITEM_NO(4) .
DATA : CURRENCY TYPE LFM1-WAERS.
DATA : POHEAD         TYPE BAPIMEPOHEADER.
DATA : POHEADX        TYPE BAPIMEPOHEADERX.
DATA : EXP_HEAD       TYPE BAPIMEPOHEADER.
DATA : POITEM         TYPE TABLE OF BAPIMEPOITEM WITH HEADER LINE.
DATA : POITEMX        TYPE TABLE OF BAPIMEPOITEMX WITH HEADER LINE.
DATA : POSCHED        TYPE TABLE OF BAPIMEPOSCHEDULE WITH HEADER LINE.
DATA : POSCHEDX       TYPE TABLE OF BAPIMEPOSCHEDULX WITH HEADER LINE.
DATA : EX_PO_NUMBER   TYPE BAPIMEPOHEADER-PO_NUMBER.
CONSTANTS : C_X VALUE 'X'.
POHEAD-COMP_CODE = 'P110'.
POHEAD-DOC_TYPE   = DOC_TYPE.
POHEAD-PMNTTRMS   = 'P10'.
POHEADX-COMP_CODE = C_X.
POHEADX-DOC_TYPE   = C_X.
POHEADX-PMNTTRMS   = C_X.
POITEM-PO_ITEM    = '00001'.
POITEM-QUANTITY   = '1.000'.
POITEM-TAX_CODE   = 'D2'.
POITEM-TAXJURCODE = 'MH01'.
POITEM-RFQ_NO     = '2300009491'.
POITEM-RFQ_ITEM   = '00001'.
POITEM-PREQ_NO    = '200003583'.
POITEM-PREQ_ITEM   = '00001'.
POITEM-PREQ_NAME = 'SACHIN'.
APPEND POITEM.
POITEMX-PO_ITEM    = '00001'.
POITEMX-PO_ITEMX   = C_X.
POITEMX-QUANTITY   = C_X .
POITEMX-TAX_CODE   = C_X .
POITEMX-TAXJURCODE = C_X .
POITEM-RFQ_NO      = C_X.
POITEM-RFQ_ITEM    = C_X.
POITEM-PREQ_NO     = C_X.
POITEM-PREQ_ITEM   = C_X.
POITEMX-PREQ_NAME = C_X.
APPEND POITEMX.
POSCHED-PO_ITEM        = '00001'.
POSCHED-SCHED_LINE     = '0001'.
POSCHED-QUANTITY       = '1.000'.
POSCHED-PREQ_NO        = '1200003583'.
POSCHED-PREQ_ITEM      = '00001'.
APPEND POSCHED.
POSCHEDX-PO_ITEM        = '1'.
POSCHEDX-SCHED_LINE     = '0001'.
POSCHEDX-PO_ITEMX       = C_X.
POSCHEDX-SCHED_LINEX    = C_X.
POSCHEDX-QUANTITY       = C_X.
POSCHEDX-PREQ_NO        = C_X.
POSCHEDX-PREQ_ITEM      = C_X.
APPEND POSCHEDX.
CALL FUNCTION 'BAPI_PO_CREATE1'
      EXPORTING
        POHEADER                     = POHEAD
        POHEADERX                    = POHEADX
      IMPORTING
        EXPPURCHASEORDER             = EX_PO_NUMBER
        EXPHEADER                    = EXP_HEAD
           EXPPOEXPIMPHEADER             =
      TABLES
        RETURN                       = RETURN_ERROR
        POITEM                       = POITEM
        POITEMX                      = POITEMX
           POADDRDELIVERY               =
        POSCHEDULE                   = POSCHED
        POSCHEDULEX                  = POSCHEDX
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      WAIT   = 'X'
    IMPORTING
      RETURN = RETURN_ERROR.

Hi,
As mentioned that this error was one of the wierdest SAP issues I have faced, it was due to the silliest copy paste errors on my behalf. I completely overlooked the POITEMX naming.
For 4 values of RFQ_NO, RFQ_ITEM, PREQ_NO, PREQ_ITEM, I didnt have the 'X' for POITEMX and kept on looking for errors for days.
BAPI_PO_CREATE1 works with min. possible inputs successfully.
Thanks to all!

Error while creating fixed asset using BAPI BAPI_FIXEDASSET_OVRTAKE_CREATE

Similar Messages

Maybe you are looking for