Creating new work order - error on %001

Hi all,
Creating a new work order from the SAP Work Manager 6.0 application should be a standard functionality,
However, on the system of our client, this goes wrong.
Upon creating a new work order, we get the error 'Enter a numerical operation number'.
New objects get an ID that starts with 'LOCAL_xx:xx:xx', which is converted to %001.
SAP should recognize this and convert this automatically to 0010, 0020, ...
how come this does not happen?
it works fine on our SAP system, our customer's system gives an error.
Kind regards,
Judith

Have you done any enhancement to standard product "specifically create method of Work Order Class handler" . or the standard product functionality itself is not working ?
I don't see any reason why it works in your system but not in customer system. Try to put break point in create method of Work order class handler and check what values are passed for operation number before invoking Work Order create BAPI.
Infact Work Manager product converts local numbers to incremental sequential numbers before invoking create BAPI for Work Order.
BR,
Manju - SAP CEG UX/Mobile

Similar Messages

Create a work order using the BAPI for IW31

Hi,
      I want to create a work order using the BAPI for IW31 tr. can any one help me with the program description.
Full points will be awarded for the useful answers.
Thanks and regards,
Sunil

hi,
first use fm "bapi_po_create".
then use fm "BAPI_ACC_GL_POSTING_POST"
The demo environment was made with real business scenario in mind, but following subjects need to be addressed in a live implementation:
     No exceptions and error handling is implemented, except the order rejection (e.g. partly delivery);
     In Navision both XML Ports and the XML DOM has been used to integrate with SAP XI, because XML ports has some drawbacks regarding to Namespaces in XML Documents (mandatory in SAP XI);
     A minimum of SAP and Navision customization is required to implement this solution. (e.g. user exit in SAP, Navision XML DOM).

BAPI for transaction IW31 (creating a work order)

Hi all,
I need to be able to create a work order ( IW31) using ABAP code and was wondering if any knew if there was a BAPI that should be used for this functionality.
Thanks in advance
Mart

hi,
You can use
BAPI_ALM_ORDER_MAINTAIN.
Have a look at the following documentation.
FU BAPI_ALM_ORDER_MAINTAIN
Text
Process Maintenance-/Service Order
Functionality
This Business Application Programming Interface (BAPI) is used for changing maintenance- or service orders and their lower-level objects. The following objects of an order can be processed (for restrictions, see the note at the end of the documentation):
Order header
Partner
User status
Order operations
Relationships
Components
Long texts for order header, operations, and components
Function
Calling up this BAPI once allows you to perform all the operations. For this the system supplies the function module with a method table containing the methods to be performed. The entries in the method table refer to data records in the optionally filled-out data tables. All the methods from the method table are performed. Alternatively, just lower- level objects from existing orders can be changed.
You can process the transferred data with the Business Add-In (BAdI) IBAPI_ALM_ORD_MODIFY to, for example, merge data from the external system with data from the R/3 system. The BAdI is called up as soon as the transferred data is converted into the internal format. The tests then take place after this.
Construction of Method Table
REFNUMBER Reference number for linking object methods - attributes
The reference number is the line of the database which contains the corresponding data. The data table is determined by the object type.
OBJECTTYPE Object category
The object category specifies which object from the order should be processed. The key words listed here are not language-dependent and must be transferred exactly as they are. The following objects exist:
HEADER Order header
PARTNER Partner data
USERSTATUS User status
OPERATION Operation data
RELATION Relationships
COMPONENT Components
TEXT Long texts
(empty) ,General BAPI functions (save)
METHOD Methods
The methods with which the data should be processed. The following functions exist:
CREATE Create objects
CHANGE Change objects
DELETE Delete objects
RELEASE Release
TECHNICALCOMPLETE Technically complete
ATPCHECK Availability check
CALCULATE Calculate
SCHEDULE Schedule
DELELTEDSEX Delete the status for external scheduling at operation level
SAVE Save all data
DIALOG Call-up dialog. See explanation below.
TRACE Write trace file in the specified file to the frontend
OBJECTKEY SAP external object key
This key is for assigning the lower-level objects correctly to the corresponding objects, as there is always just one key in the data table. The key must have the following structure:
1-12 Order number
When creating orders with internal number assignment, a reference number beginning with % must be entered here. The BAPI then returns this number and the number actually assigned.
13-16 Operation number
17-20 Sub-operation number
For relationships, the key is structured as follows:
1-12 ,Order number from
13-16 Operation number from
17-28 Order number to
29-32 Operation number to
The following methods are permissible for the individual objects:
HEADER:
CREATE, CHANGE, RELEASE, TECHNICALCOMPLETE, ATPCHECK, CALCUALTE, SCHEDULE
OPERATION
CREATE, CHANGE, DELETE, DELETEDSEX
PARTNER, RELATION, COMPONENT, USERSTATUS, TEXT:
CREATE, CHANGE, DELETE
(empty):
SAVE, DIALOG, TRACE
Data tables and update tables
The objects have one or more data tables. For some objects you can specify which of the fields specified in the structure should be changed. For this you must set the field in the corresponding table to X as in the data table. If no update-table is transferred, then only those fields are set that have a value that is not initial. This simplifies the transfer data. However, this means it is not possible to delete fields. If an update structure should only be specified for some data records, the table with the update fields must nonetheless have the same amount of lines as the data table. The empty lines are then treated as if no update structure was transferred. The objects "Partner", "User Status", and "Text" have no update tables. The whole data record is always copied here.
References
The objects use the field REFNUMBER from the method table to refer to the lines in the data table. Counting always begins with 1. In doing this, REFNUMBER also refers to the update table. However, in the method table there is a second reference to higher-level objects for lower-levels objects. The field OBJECTKEY must be filled with order number, operation number, and sub-operation number, as specified above. If lower-level objects of a newly-created order should be changed, then you must enter a temporary order number that must begin with %. Several orders can be numbered serially, for example, with %00000000001, %00000000002 ... .
The following objects have special treatment for REFNUMBER:
Partner
Texts
Partners have an order number in the data table. During processing of the method table, all those entries in the data table are processed which have an order number that is the same as that in the line to which the method refers. Thus, through just one entry in the method table, several partners can be changed.
Texts are composed of two tables. The first table (IT_TEXT) is made up of the header data of the text. Here you must specify the object and the first and last line of the text table (respectively inclusive, counting from 1). Through this, a line segment is specified in the text line table (IT_TEXT_LINES).
Peculiarities in processing
The BAPI processes the transferred methods in a particular sequence, which must not correspond to the sequence in the methods table.
Write trace file
Change user status time period 1
Delete objects (dependent first)
Create new objects
Change existing or newly-created objects
Change user status time period 2
Status change of order
Save data
The methods are performed such that lower-level objects can also be assigned to newly-created objects. For example, first the operations are created, and then the components. Long texts can also be created for the objects.
Components have an exceptional position. Components are created through the assignment to an operation, that is, using the "key" order/ operation (item number). However, as this is not the unique component key, you can only access the components to change them, delete them, or add long texts by using the reservation number/-item, which is only given after saving. This means that, for example, you cannot create a long text when you create the component.
User status changes can take place at two different time points. Time point 1 is before the object changes, time point 2 is after the object changes and before the status change of the system. These time points should be defined in the transfer table in the field CHANGE_EVENT. The field documentation contains the possible values.
The external scheduling is offered by the BAPI as a special function. THe BAPI can set the date field directly at the operation level, and select the operation with the status DSEX "Date set by external system". This status prevents any further scheduling of the operation, it keeps the transferred dates. For this, set the category 'X' in the restriction categories. When reading the operation, this category is also returned, independent of the category of restriction set in the dialog. To delete the status, you can call up the method DELETEDSEX for the object operation. The external scheduling cannot be influenced in the dialog. All changes to the scheduling restrictions in the dialog are saved as normal, but are not relevant for the scheduling as long as the status DSEX is active.
Every time the BAPI is called up, a SAVE or DIALOG method must be transferred. Normally, calling up a BAPI is seen as a transaction. All data that is changed in the BAPI should be saved to the database immediately. The BAPI checks whether a SAVE method exists, otherwise it terminates processing. A test run of the BAPI is composed of a normal call-up using the SAVE method and a subsequent BAPI_TRANSACTION_ROLLBACK. To call up the BAPI without the SAVE method, for example, to realize dialog transactions, the BAPI can be called up with the DIALOG method. This switches off the check for the SAVE method. The processor must then ensure that later either a SAVE method or a BAPI_TRANSACTION_ROLLBACK is called up.
A BAPI_TRANSACTION_COMMIT without SAVE method terminates processing in the update to ensure that no inconsistent data is written to the database. The processor who called up the BAPI does not receive any confirmation for the termination of the update in the target system. This logic is necessary as the order data was flagged for updating with BAPI_TRANSACTION_COMMIT through the SAVE method. However, the status information was already flagged for updating when the BAPI was called up. A BAPI_TRANSACTION_COMMIT without SAVE method then just saves the status information and would generate inconsistent orders, if the updating was not terminated.
Customer Enhancement
The BAdI IBAPI_ALM_ORD_MODIFY can be used to change the transferred data. The BAdI is called up after the conversion of the transfer structure into the structures used internally. Additional data can be transferred using the table EXTENSION_IN. Only then is the data checked.
Example
The following examples should clarify the use.
Creating an order
OBJECTKEY should be filled with a temporary key. The BAPI returns this key together with the assigned order number in the return table ET_NUMBERS . The order number in the HEADER table should also be filled with the number. For external number assignment, the external number should be specified. The update structure can be transferred if necessary.
Methods table
REFNUMBER OBJECTTYPE METHOD OBJECTKEY
1 HEADER CREATE %00000000001
IT_HEADER
ORDERID ORDER_TYPE PLANPLANT ...
%00000000001 PM01 1000 ...
Creating an order with operation and long text
Methods table
REFNUMBER OBJECTTYPE METHOD OBJECTKEY
1 HEADER CREATE %00000000001
1 OPERATION CREATE %00000000001
1 TEXT CREATE %000000000010010
IT_HEADER
ORDERID ORDER_TYPE PLANPLANT ...
%00000000001 PM01 1000 ...
IT_OPERATION
ACTIVITY SUB_ACTIVITY CONTROL_KEY WRK_CNTR ...
10 PM01 MECHANIC ...
IT_TEXT
ACTIVITY ... TEXTSTART TEXTEND
10 ... 1 2
IT_TEXT_LINES
TDFORMAT TDLINE
Longtext for operation 10, line 1
Line 2 of the long text
Notes
Using the BAPI to process the order data cannot support all the functions of the transaction. This applies in particular for the following functions:
Order header data
The object list cannot be processed.
Refurbishment orders are not supported.
The estimated costs cannot be processed - only the estimated overall costs of the order.
Notification data cannot be processed with the order BAPI. Even if the settings in Customizing are such that the orders and notifications can be maintained on one screen, no notification is created for the order.
Permits cannot be processed.
The order addresses cannot be processed.
Individual partner addresses cannot be maintained.
The settlement rule cannot be maintained.
Order functions
Printing the papers is not possible.
Locking and unlocking the order is not possible.
Accepting and rejecting quotations is not possible.
Business completion is not possible.
Flagging for deletion is not possible.
The log cannot be displayed.
User default values are not used.
The field selection is not checked.
The Customer Exits/BAdIs are not executed completely.
Joint ventures are not supported.
Funds Management is not supported.
Investment orders are not supported.
No integration of service products with task lists possible.
No integration of configurable service products possible.
Assignment of sales document items with service products in accordance with the aforementioned conditions.
Operation data
A change of the control key in the operation is not possible, if this leads to a change of the processing type (internal-/external processing)
User status change not possible.
Production resources and tools cannot be processed.
Service lines cannot be processed.
Task list integration is not supported.
Linking operations with object list is not supported.
Component data
User status change not possible.
BOM data cannot be processed.
The delivery address cannot be processed.
Further Information
See also the documentation for the individual transfer tables.
Parameters
IT_METHODS
IT_HEADER
IT_HEADER_UP
IT_HEADER_SRV
IT_HEADER_SRV_UP
IT_USERSTATUS
IT_PARTNER
IT_PARTNER_UP
IT_OPERATION
IT_OPERATION_UP
IT_RELATION
IT_RELATION_UP
IT_COMPONENT
IT_COMPONENT_UP
IT_TEXT
IT_TEXT_LINES
EXTENSION_IN
RETURN
ET_NUMBERS
Exceptions
Function Group
IBAPI_ALM_ORDER
~~Guduri

How to create New Work Center

Dear Experts
How to create New Work Center?, what are all the inforamtions need while creating workcenter.
Regards
Rajakarthik

Hi,
In addition to the above post, you need to identify that:
1. Whether you need separate activity types and cost center for the newly created work center. These details are entered in the Costing View of the Work Center.
If these are required then use KL01 to create new activity, KP26 to define the activity price.
If required create cost element using T Code KA01 and Cost Center using KS01.
Take help from the CO guy on this.
2. Also you need to ask the concerned about the operating times for the wor center. That is Start time and End time of WC. It is used for capacity evaluation and scheduling of the orders. It is maintained in the capacity view (Bottom left Button in the view).
this view will also contain the details regarding the calendar, to be assigned to the work center, if needed. Collect details for this requirement. Also you can assign a different calendar to WC apart from factory calendar.
3. Find out whether this WC will be operating in shifts or not. Accordingly maintain the details.
Hope it is useful for you.
Revert for clarifications
Regards,
Rohit.

Creating new sales-order item with text using BAPI_SALESORDER_CHANGE

Hi all.
I want to create new sales-order item in an existing sales-order by using BAPI_SALESORDER_CHANGE. This works fine.
I also want to enter item-texts for the new item in the same call, but this doesn't work.
When I call the BAPI I do not assign an item-number for the new item, thus I have no item-number to assign to ITM_NUMBER in table ORDER_TEXT. IF ITM_NUMBER is empty, it's treated as a header text....
Any clues?
Regards
/Elisabet

increment the last itemnumber and pass it to that.
if they are following a sequence 10,20,30.
find the next sequence and send it to the ITEMNUMBER field.
or else you add the text after the Function call.

Customization for create 2 Work orders for different vendors against 1 PR

Hi,
What are the customization settings to create 2 work orders for 2 different vendors against 1 PR with half-half quantity?

thank you Mario.
Actuly its infrastructure cmpany & user wants create Purchase order(service work order) for two different vendors with reference to single PR with alocating 60% quantity to 1st vendor & remaining 40% to another vendor.
user allready created Po for 1st vendor (60% Quantity).
Now system showing error " Quantity is allready full for reference PR"
I want to know what is the procedue to solve this issue & customization.

When Creating a Work Order Import Standard Operations

A client is requesting the following functionality when creating a Work Order: Create the first nine operations with different work centers and number operations 0001 u2013 0009. For operation ten continue numbering with 0010 and increase by 10, ie, 0020, 0030, etcu2026 . And operation 0010 would default header data.
Can this be accomplished through standards configuration or would this entail a user exit?
Thanks in advance!!
JAM

It can be possible, depending on how you create the Work Order. If these operations are used often and are in a task list, you can create a work order and import the task list operations by using the menu "extras -> task List selections" inside the work order. If it is part of a preventative maintenance plan, you can configure that your task list is automatically copied to the notification/work order when generated by your maintenance plan. Of course in the task list you could save all the increments and work centers as you want. But this would never be a dynamic check to your header data, it would only be as accurate as your task list.

Every time system create new production order after releasing sales order c

Hi Guru,
FG material strategy: 82 (sales order creates production order).
After creating the sales order it goes in to credit block. Whenever we release sales order from credit block through VKM1, system has created production order. We confirmed this production order and delivered.
But after this sales person change the sales order value, because of which again sales order goes into the credit block and after releasing sales order from credit block system create new production order even if one production order already confirmed and delivered against the same sales order.
*Every time system create new production order after releasing sales order credit block.
Thanx & regards
pnu

PNU,
So, to restate:
In MD04, you have Unrestricted Sales order Stock ('E' Stock) on hand.
In the same MRP segment, and against the same Storage Location as the stock, you have a Sales Order requirement that was recently blocked and unblocked.
During the unblocking event, the system produced a new production order.
This is not normal. If the above accurately depicts your situation, I would look for an altered Strategy 82, or a userexit. SAP ATP (the beginning event of the Strat 82 process) will normally first check for the availability of stock. Only if the stock is not available, then it will create the new production order.
Best Regards,
DB49

Error creating new work space

I logged in as admin and tried to create a new work space for a developer. At the last step, I got error:
ORA-04063: package body "FLOWS_030100.WWV_FLOW_SAMPLE_APP" has errors ORA-06508: PL/SQL: could not find program unit being called: "FLOWS_030100.WWV_FLOW_SAMPLE_APP"
Error provisioning XXXXXXX.
Return to application.
Please help!
Edited by: user10255537 on Sep 16, 2008 6:47 AM

It looks like it is failing on the attempt to load the sample objects into the new workspace. Go to Manage Service / Feature Configuration and toggle Create demonstration objects... to OFF.
Try creating the workspace after that and see if it works. I don't know why the sample app install might fail but this should get you moving.
Jason Aughenbaugh (aka. WileECoyote)
Precision Guesswork Blog: http://citemreh.spaces.live.com

After creating new sales order through BAPI, it is not showing in VA03

Hi Experts
I am developing one program to create sales order using FM BAPI_SALESORDER_CREATEFROMDAT2. In output screen it is showing that the new sales order number created with new sales order number. But whenever I want to display the newly created sales order via VA03 it shows an error message SD document 10007547 is not in the database or has been archived but in program output it shows that 10007547 is created. This is in DEV server. Document numbers are generated by the system sequencially, but it is not reflected in database.
I am also attaching my code below.
REPORT z_bapi_salesorder.
DATA : gt_header LIKE bapisdhd1,
       gt_item TYPE TABLE OF bapisditm,
       gt_itemx TYPE TABLE OF bapisditmx,
       gt_partner TYPE TABLE OF bapiparnr,
       gt_return TYPE TABLE OF bapiret2.
DATA : gs_item LIKE LINE OF gt_item,
       gs_itemx LIKE LINE OF gt_itemx,
       gs_partner LIKE LINE OF gt_partner,
       gs_return LIKE LINE OF gt_return.
DATA : v_vbeln TYPE vbeln_va.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(30) ord_type FOR FIELD p_auart.
PARAMETERS : p_auart TYPE auart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN SKIP 1.
SELECTION-SCREEN : BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
PARAMETERS       : p_vkorg TYPE vkorg OBLIGATORY,
                   p_vtweg TYPE vtweg OBLIGATORY,
                   p_spart TYPE vbak-spart OBLIGATORY,
                   p_sold TYPE kunnr OBLIGATORY,
                   p_ship TYPE kunnr OBLIGATORY,
                   p_matnr TYPE matnr OBLIGATORY,
                   p_menge TYPE kwmeng OBLIGATORY,
                   p_plant TYPE werks_d OBLIGATORY.
SELECTION-SCREEN : END OF BLOCK b1.
INITIALIZATION.
ord_type = 'Order Type'.
START-OF-SELECTION.
*Header information data.
gt_header-doc_type = p_auart.
gt_header-sales_org = p_vkorg.
gt_header-distr_chan = p_vtweg.
gt_header-division = p_spart.
*Partner information data.
gs_partner-partn_role = 'AG'.
gs_partner-partn_numb = p_sold.
APPEND gs_partner TO gt_partner.
CLEAR gs_partner.
gs_partner-partn_role = 'WE'.
gs_partner-partn_numb = p_ship.
APPEND gs_partner TO gt_partner.
CLEAR gs_partner.
*Item data
gs_item-itm_number = '000010'.
gs_itemx-itm_number = 'X'.
gs_item-material = p_matnr.
gs_itemx-material = 'X'.
gs_item-plant = p_plant.
gs_itemx-plant = 'X'.
gs_item-target_qty = p_menge.
gs_itemx-target_qty = 0.
APPEND gs_item TO gt_item.
APPEND gs_itemx TO gt_itemx.
CLEAR : gs_item, gs_itemx.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
    EXPORTING
SALESDOCUMENTIN               =
      order_header_in               = gt_header
ORDER_HEADER_INX              =
SENDER                        =
BINARY_RELATIONSHIPTYPE       =
INT_NUMBER_ASSIGNMENT         =
BEHAVE_WHEN_ERROR             =
LOGIC_SWITCH                  =
TESTRUN                       =
CONVERT                       = ' '
   IMPORTING
     salesdocument                = v_vbeln
    TABLES
     return                       = gt_return
     order_items_in               = gt_item
     order_items_inx              = gt_itemx
     order_partners               = gt_partner
ORDER_SCHEDULES_IN            =
ORDER_SCHEDULES_INX           =
ORDER_CONDITIONS_IN           =
ORDER_CONDITIONS_INX          =
ORDER_CFGS_REF                =
ORDER_CFGS_INST               =
ORDER_CFGS_PART_OF            =
ORDER_CFGS_VALUE              =
ORDER_CFGS_BLOB               =
ORDER_CFGS_VK                 =
ORDER_CFGS_REFINST            =
ORDER_CCARD                   =
ORDER_TEXT                    =
ORDER_KEYS                    =
EXTENSIONIN                   =
PARTNERADDRESSES              =
IF v_vbeln <> space.
    COMMIT WORK.
    WRITE :/ 'Document', v_vbeln ,'created'.
    CLEAR : v_vbeln, gt_header.
    REFRESH : gt_partner, gt_item, gt_itemx.
ELSE.
    WRITE :/ 'Error in creating document'.
ENDIF.
Please give the possible solutions for this. What is reason for that update termination.

CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT1'
    EXPORTING
      ORDER_HEADER_IN           = ORDER_HEADER_IN
WITHOUT_COMMIT            = ' '
CONVERT_PARVW_AUART       = ' '
   IMPORTING
     SALESDOCUMENT             = SALESDOCUMENT
SOLD_TO_PARTY             =
SHIP_TO_PARTY             =
BILLING_PARTY             =
     RETURN                    = RETURN
    TABLES
      ORDER_ITEMS_IN            = ORDER_ITEMS_IN
      ORDER_PARTNERS            = ORDER_PARTNERS
ORDER_ITEMS_OUT           =
ORDER_CFGS_REF            =
ORDER_CFGS_INST           =
ORDER_CFGS_PART_OF        =
ORDER_CFGS_VALUE          =
ORDER_CCARD               =
ORDER_CFGS_BLOB           =
     ORDER_SCHEDULE_EX         = ORDER_SCHEDULE_EX
use bapi_transaction_commit.
Regards,
Venkat

Left over of Sales Order creates new planned order of whole batch

Hi Gurus,
We are using planning without Assembly strategy (52) and Sales order is created in our sales plant and Purchase order from sales plant creates STO on manufacturing plant which than produces material using process order.
Now sales order says 5000 EA but actual production is if 4985 EA in Manufacturing plant which is transported into Sales plant and sales plant receives 4985 EA which keeps sales order of 5EA in the system
When MRP runs overnight creates planned order for left over quantity and it is of whole batch 5000 EA. This confuse our planner.
Can anyone provide me the solution please?
Regards,
SAPPPPI

Hi,
For strategy 52 FX never works so we have lot sixe "EX".
We have set up tolerance limit of +/- 10% but when less quantity is received (4985 instead of 5000) from manufacturing plant system thinks there is an open sales sales order of 15 and creates a new planed order.
If we have materials 4980 in stock and we create a sales order for 5000, tolerance will be considered for this and there won't be any open sales order but in our case Sales order allows us to procure and when GR quantity is less than sales order it is treated as left over and create planned order.
Please help me by replying if any one knows.
Regards
SAPPPPI

PM Work Order Error

Hi Experts,
While creating work order i am getting the below given error :
Number of capacities in activity exceeds capacities in work center
I want to know why i am getting this error.
Suppose i have a workcenter with following data under the capacity screen:
tart time =8:00 End Time =17:00
Lenght of Break = 1hr
Capacity utilization = 90
No of individual capacity= 5
Operating time=7.20
Capacity=36
Please explain based on the above given workcenter data
Regards,
Kavvya

Increase the Capacity " No of individual capacity= 5 " instead of 5 to x value,
note : you have mentioned in work order operation " Number of capacities required " more than the value " 5 "
Otherwise system will automatically calculate the work hours based on the Cc-Key selection.

Create new work center in HR by using bapi.

Hello, everyone.
I'm trying to create a new work center in HR related to an organizational unit by using the bapi: BAPI_HRMASTER_SAVE_REPL_MULT.
For some reason I'm getting an error message:
"Object [work_center_id] does not exist in status 1".
This status comes from the field PL_STATUS at 1001, 1032 infotypes that I'm sending to the bapi.
Does anyone have a solution for me ??
Thanks in advance,
A.S.

Not relevant anymore

BEA Portal 8.1 Sp4 - Cannot Create new Desktop - DB Error Returned?

Please help.
We are trying to migrate to streaming portal, and are encountering a problem. It appears to be a new problem as it wasn't coming up last week.
Under the Weblogic Admin Portal, I create a Portal. Success
- I then try to create a Desktop using a Portal Template File.
- I select the Portal file we have, and the only Portal file from the dropdown.
- I click "Create New Desktop"
- When the popup displays "WARNING: Portal Template Contains Duplicate Resources" comes up, if I select "Replace conflicting Portal Resources" or "Replace Markup" it fails.
The Javascript alert says (or tries to say)
Error: The desktop could not be disassembled.
Data exception -- row already exist in index AX1_PAGE_DEF on table PF_PAGE_DEFINITION
Any idea what is going on? We haven't taken this a step further due to this problem.
Before you suggest:
- We haven't been doing anything fancy.
- I have not gone into PointBase manually (I wouldn't know how)
- By all accounts it appeared to be working fine, and then it stopped.
Current Setup
- BEA Weblogic 8.1 SP4
- "Production" Domain using JRockit SDK
- Currently using the workstation's PointBase database for the Admin tools.
Full Error
Error: The desktop could not be disassembled.
[com.bea.netuix.application.transform.disassembler.view.ViewDisassemblerException: javax.transaction.TransactionRolledbackException: EJB Exception: : javax.ejb.EJBException: SQL Error while trying to createPageDefinition: SQL [insert into PF_PAGE_DEFINITION ( PAGE_DEFINITION_ID, MARKUP_DEFINITION_ID, IS_PUBLIC, IS_HIDDEN, INTERSECTION_ID, PAGE_LABEL, WEBAPP_NAME) values (?,?,?,?,?,?,?)] database error code [25,222] SQL state [22028] .; nested exception is: java.sql.SQLException: Data exception -- row already exist in index AX1_PAGE_DEF on table PF_PAGE_DEFINITION.java.sql.SQLException: Data exception -- row already exist in index AX1_PAGE_DEF on table PF_PAGE_DEFINITION. at com.pointbase.net.netJDBCPrimitives.handleResponse(Ljava.io.DataInputStream;)V(Optimized Method) at com.pointbase.net.netJDBCPrimitives.handlePrimitiveResponse(Ljava.io.DataInputStream;)Ljava.lang.Object;(Optimized Method) at com.pointbase.net.netJDBCPreparedStatement.executeUpdate()I(Optimized Method) at weblogic.jdbc.wrapper.PreparedStatement.executeUpdate()I(Optimized Method) at com.bea.netuix.application.manager.persistence.jdbc.PageDefinitionDelegate.createPageDefinition(Ljava.sql.Connection;Lcom.bea.netuix.application.definition.PageDefinition;)Lcom.bea.netuix.application.definition.PageDefinition;(PageDefinitionDelegate.java:850) at com.bea.netuix.application.manager.persistence.jdbc.PageDefinitionManagerImpl.createPageDefinition(Lcom.bea.netuix.application.manager.CustomizationContext;Lcom.bea.netuix.application.definition.PageDefinition;)Lcom.bea.netuix.application.definition.PageDefinition;(PageDefinitionManagerImpl.java:875) at com.bea.netuix.application.manager.persistence.jdbc.PageDefinitionManager_c4el9c_EOImpl.createPageDefinition(Lcom.bea.netuix.application.manager.CustomizationContext;Lcom.bea.netuix.application.definition.PageDefinition;)Lcom.bea.netuix.application.definition.PageDefinition;(PageDefinitionManager_c4el9c_EOImpl.java:906) at com.bea.netuix.application.transform.disassembler.view.DefinitionManagerFacade.createPageDefinition(Lcom.bea.netuix.application.manager.CustomizationContext;Lcom.bea.netuix.application.view.PageView;)Lcom.bea.netuix.application.transform.disassembler.view.CreatePageDefinitionResult;(DefinitionManagerFacade.java:956) at com.bea.netuix.application.transform.disassembler.view.PageViewDisassembler.disassemble(Lcom.bea.netuix.application.view.View;Lcom.bea.netuix.application.manager.CustomizationContext;)Lcom.bea.netuix.application.identifier.Id;(PageViewDisassembler.java:75) at com.bea.netuix.application.transform.disassembler.view.ViewDisassemblerDelegator.disassemble(Lcom.bea.netuix.application.view.View;Lcom.bea.netuix.application.manager.CustomizationContext;)Lcom.bea.netuix.application.identifier.Id;(ViewDisassemblerDelegator.java:134) at com.bea.netuix.application.transform.disassembler.view.BookViewDisassembler.disassemble(Lcom.bea.netuix.application.view.View;Lcom.bea.netuix.application.manager.CustomizationContext;)Lcom.bea.netuix.application.identifier.Id;(BookViewDisassembler.java:102) at com.bea.netuix.application.transform.disassembler.view.BookViewDisassembler.disassemble(Lcom.bea.netuix.application.view.View;Lcom.bea.netuix.application.manager.CustomizationContext;)Lcom.bea.netuix.application.identifier.Id;(BookViewDisassembler.java:116) at com.bea.netuix.application.transform.disassembler.view.BookViewDisassembler.disassemble(Lcom.bea.netuix.application.view.View;Lcom.bea.netuix.application.manager.CustomizationContext;)Lcom.bea.netuix.application.identifier.Id;(BookViewDisassembler.java:116) at com.bea.netuix.application.transform.disassembler.view.ViewDisassemblerDelegator.disassemble(Lcom.bea.netuix.application.view.View;Lcom.bea.netuix.application.manager.CustomizationContext;)Lcom.bea.netuix.application.identifier.Id;(ViewDisassemblerDelegator.java:134) at com.bea.netuix.application.transform.disassembler.view.PageViewDisassembler.disassemble(Lcom.bea.netuix.application.view.View;Lcom.bea.netuix.application.manager.CustomizationContext;)Lcom.bea.netuix.application.identifier.Id;(PageViewDisassembler.java:109) at com.bea.netuix.application.transform.disassembler.view.ViewDisassemblerDelegator.disassemble(Lcom.bea.netuix.application.view.View;Lcom.bea.netuix.application.manager.CustomizationContext;)Lcom.bea.netuix.application.identifier.Id;(ViewDisassemblerDelegator.java:134) at com.bea.netuix.application.transform.disassembler.view.BookViewDisassembler.disassemble(Lcom.bea.netuix.application.view.View;Lcom.bea.netuix.application.manager.CustomizationContext;)Lcom.bea.netuix.application.identifier.Id;(BookViewDisassembler.java:102) at com.bea.netuix.application.transform.disassembler.view.ViewDisassemblerDelegator.disassemble(Lcom.bea.netuix.application.view.View;Lcom.bea.netuix.application.manager.CustomizationContext;)Lcom.bea.netuix.application.identifier.Id;(ViewDisassemblerDelegator.java:134) at com.bea.netuix.application.transform.disassembler.view.ViewDisassemblerFactory.createDesktopDefinition(Lcom.bea.netuix.application.manager.CustomizationContext;Lcom.bea.netuix.application.view.DesktopView;Ljava.lang.String;)Lcom.bea.netuix.application.definition.DesktopDefinition;(ViewDisassemblerFactory.java:113) at com.bea.netuix.application.manager.persistence.jdbc.DesktopDefinitionManagerImpl.createDesktopDefinition(Lcom.bea.netuix.application.manager.CustomizationContext;Lcom.bea.netuix.application.view.DesktopView;Ljava.lang.String;)Lcom.bea.netuix.application.definition.DesktopDefinition;(DesktopDefinitionManagerImpl.java:378) at com.bea.netuix.application.manager.persistence.jdbc.DesktopDefinitionManager_8c1hh8_EOImpl.createDesktopDefinition(Lcom.bea.netuix.application.manager.CustomizationContext;Lcom.bea.netuix.application.view.DesktopView;Ljava.lang.String;)Lcom.bea.netuix.application.definition.DesktopDefinition;(DesktopDefinitionManager_8c1hh8_EOImpl.java:46) at com.bea.jsptools.portal.PortalDisassembler.disassemble(Lcom.bea.netuix.application.identifier.PortalPath;Lcom.bea.netuix.application.identifier.DesktopPath;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;ILjava.io.InputStream;Ljavax.servlet.http.HttpServletRequest;)Lcom.bea.netuix.application.definition.DesktopDefinition;(PortalDisassembler.java:133) at com.bea.jsptools.portal.PortalAdminManager.createDesktopFromTemplate(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;ILjava.util.Locale;Ljavax.servlet.http.HttpServletRequest;)V(PortalAdminManager.java:427) at jsp_servlet._portaltools.__portalmgmttree._jspService(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(__portalmgmttree.java:3293) at weblogic.servlet.jsp.JspBase.service(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(Optimized Method) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run()Ljava.lang.Object;(ServletStubImpl.java:1006) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Lweblogic.servlet.internal.FilterChainImpl;)V(Optimized Method) at weblogic.servlet.internal.TailFilter.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Ljavax.servlet.FilterChain;)V(TailFilter.java:28) at weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(FilterChainImpl.java:27) at com.bea.p13n.servlets.PortalServletFilter.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Ljavax.servlet.FilterChain;)V(PortalServletFilter.java:293) at weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(FilterChainImpl.java:27) at weblogic.servlet.internal.RequestDispatcherImpl.include(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Z)V(RequestDispatcherImpl.java:644)javax.ejb.EJBException: SQL Error while trying to createPageDefinition: SQL [insert into PF_PAGE_DEFINITION ( PAGE_DEFINITION_ID, MARKUP_DEFINITION_ID, IS_PUBLIC, IS_HIDDEN, INTERSECTION_ID, PAGE_LABEL, WEBAPP_NAME) values (?,?,?,?,?,?,?)] database error code [25,222] SQL state [22028] .; nested exception is: java.sql.SQLException: Data exception -- row already exist in index AX1_PAGE_DEF on table PF_PAGE_DEFINITION. at com.bea.netuix.application.manager.persistence.jdbc.PageDefinitionDelegate.createPageDefinition(Ljava.sql.Connection;Lcom.bea.netuix.application.definition.PageDefinition;)Lcom.bea.netuix.application.definition.PageDefinition;(PageDefinitionDelegate.java:866) at com.bea.netuix.application.manager.persistence.jdbc.PageDefinitionManagerImpl.createPageDefinition(Lcom.bea.netuix.application.manager.CustomizationContext;Lcom.bea.netuix.application.definition.PageDefinition;)Lcom.bea.netuix.application.definition.PageDefinition;(PageDefinitionManagerImpl.java:875) at com.bea.netuix.application.manager.persistence.jdbc.PageDefinitionManager_c4el9c_EOImpl.createPageDefinition(Lcom.bea.netuix.application.manager.CustomizationContext;Lcom.bea.netuix.application.definition.PageDefinition;)Lcom.bea.netuix.application.definition.PageDefinition;(PageDefinitionManager_c4el9c_EOImpl.java:906) at com.bea.netuix.application.transform.disassembler.view.DefinitionManagerFacade.createPageDefinition(Lcom.bea.netuix.application.manager.CustomizationContext;Lcom.bea.netuix.application.view.PageView;)Lcom.bea.netuix.application.transform.disassembler.view.CreatePageDefinitionResult;(DefinitionManagerFacade.java:956) at com.bea.netuix.application.transform.disassembler.view.PageViewDisassembler.disassemble(Lcom.bea.netuix.application.view.View;Lcom.bea.netuix.application.manager.CustomizationContext;)Lcom.bea.netuix.application.identifier.Id;(PageViewDisassembler.java:75) at com.bea.netuix.application.transform.disassembler.view.ViewDisassemblerDelegator.disassemble(Lcom.bea.netuix.application.view.View;Lcom.bea.netuix.application.manager.CustomizationContext;)Lcom.bea.netuix.application.identifier.Id;(ViewDisassemblerDelegator.java:134) at com.bea.netuix.application.transform.disassembler.view.BookViewDisassembler.disassemble(Lcom.bea.netuix.application.view.View;Lcom.bea.netuix.application.manager.CustomizationContext;)Lcom.bea.netuix.application.identifier.Id;(BookViewDisassembler.java:102) at com.bea.netuix.application.transform.disassembler.view.BookViewDisassembler.disassemble(Lcom.bea.netuix.application.view.View;Lcom.bea.netuix.application.manager.CustomizationContext;)Lcom.bea.netuix.application.identifier.Id;(BookViewDisassembler.java:116) at com.bea.netuix.application.transform.disassembler.view.BookViewDisassembler.disassemble(Lcom.bea.netuix.application.view.View;Lcom.bea.netuix.application.manager.CustomizationContext;)Lcom.bea.netuix.application.identifier.Id;(BookViewDisassembler.java:116) at com.bea.netuix.application.transform.disassembler.view.ViewDisassemblerDelegator.disassemble(Lcom.bea.netuix.application.view.View;Lcom.bea.netuix.application.manager.CustomizationContext;)Lcom.bea.netuix.application.identifier.Id;(ViewDisassemblerDelegator.java:134) at com.bea.netuix.application.transform.disassembler.view.PageViewDisassembler.disassemble(Lcom.bea.netuix.application.view.View;Lcom.bea.netuix.application.manager.CustomizationContext;)Lcom.bea.netuix.application.identifier.Id;(PageViewDisassembler.java:109) at com.bea.netuix.application.transform.disassembler.view.ViewDisassemblerDelegator.disassemble(Lcom.bea.netuix.application.view.View;Lcom.bea.netuix.application.manager.CustomizationContext;)Lcom.bea.netuix.application.identifier.Id;(ViewDisassemblerDelegator.java:134) at com.bea.netuix.application.transform.disassembler.view.BookViewDisassembler.disassemble(Lcom.bea.netuix.application.view.View;Lcom.bea.netuix.application.manager.CustomizationContext;)Lcom.bea.netuix.application.identifier.Id;(BookViewDisassembler.java:102) at com.bea.netuix.application.transform.disassembler.view.ViewDisassemblerDelegator.disassemble(Lcom.bea.netuix.application.view.View;Lcom.bea.netuix.application.manager.CustomizationContext;)Lcom.bea.netuix.application.identifier.Id;(ViewDisassemblerDelegator.java:134) at com.bea.netuix.application.transform.disassembler.view.ViewDisassemblerFactory.createDesktopDefinition(Lcom.bea.netuix.application.manager.CustomizationContext;Lcom.bea.netuix.application.view.DesktopView;Ljava.lang.String;)Lcom.bea.netuix.application.definition.DesktopDefinition;(ViewDisassemblerFactory.java:113) at com.bea.netuix.application.manager.persistence.jdbc.DesktopDefinitionManagerImpl.createDesktopDefinition(Lcom.bea.netuix.application.manager.CustomizationContext;Lcom.bea.netuix.application.view.DesktopView;Ljava.lang.String;)Lcom.bea.netuix.application.definition.DesktopDefinition;(DesktopDefinitionManagerImpl.java:378) at com.bea.netuix.application.manager.persistence.jdbc.DesktopDefinitionManager_8c1hh8_EOImpl.createDesktopDefinition(Lcom.bea.netuix.application.manager.CustomizationContext;Lcom.bea.netuix.application.view.DesktopView;Ljava.lang.String;)Lcom.bea.netuix.application.definition.DesktopDefinition;(DesktopDefinitionManager_8c1hh8_EOImpl.java:46) at com.bea.jsptools.portal.PortalDisassembler.disassemble(Lcom.bea.netuix.application.identifier.PortalPath;Lcom.bea.netuix.application.identifier.DesktopPath;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;ILjava.io.InputStream;Ljavax.servlet.http.HttpServletRequest;)Lcom.bea.netuix.application.definition.DesktopDefinition;(PortalDisassembler.java:133) at com.bea.jsptools.portal.PortalAdminManager.createDesktopFromTemplate(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;ILjava.util.Locale;Ljavax.servlet.http.HttpServletRequest;)V(PortalAdminManager.java:427) at jsp_servlet._portaltools.__portalmgmttree._jspService(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(__portalmgmttree.java:3293) at weblogic.servlet.jsp.JspBase.service(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(Optimized Method) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run()Ljava.lang.Object;(ServletStubImpl.java:1006) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Lweblogic.servlet.internal.FilterChainImpl;)V(Optimized Method) at weblogic.servlet.internal.TailFilter.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Ljavax.servlet.FilterChain;)V(TailFilter.java:28) at weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(FilterChainImpl.java:27) at com.bea.p13n.servlets.PortalServletFilter.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Ljavax.servlet.FilterChain;)V(PortalServletFilter.java:293) at weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(FilterChainImpl.java:27) at weblogic.servlet.internal.RequestDispatcherImpl.include(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Z)V(RequestDispatcherImpl.java:644) at weblogic.servlet.internal.RequestDispatcherImpl.include(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(RequestDispatcherImpl.java:423) at com.bea.netuix.servlets.controls.content.JspContent.beginRender(Ljava.io.Writer;)Z(JspContent.java:533) at com.bea.netuix.nf.ControlLifecycle$1.visit(Lcom.bea.netuix.nf.UIControl;Ljava.lang.Object;)Z(ControlLifecycle.java:495) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(Lcom.bea.netuix.nf.VisitorType;Lcom.bea.netuix.nf.UIControl;Ljava.lang.Object;)V(ControlTreeWalker.java:485); nested exception is:
javax.ejb.EJBException: SQL Error while trying to createPageDefinition: SQL [insert into PF_PAGE_DEFINITION ( PAGE_DEFINITION_ID, MARKUP_DEFINITION_ID, IS_PUBLIC, IS_HIDDEN, INTERSECTION_ID, PAGE_LABEL, WEBAPP_NAME) values (?,?,?,?,?,?,?)] database error code [25,222] SQL state [22028] .; nested exception is: java.sql.SQLException: Data exception -- row already exist in index AX1_PAGE_DEF on table PF_PAGE_DEFINITION.]."));

You might have already checked it but just in case, did you check the server console when this happens ?
If there is any problem with the template file, it doesnt create a desktop even though it doesnt complain about this explicitly in the Portal Admin.
Cheers,
Satish

Create New gives an error "Could not find the user document directory"

Fresh installed Adobe Edge Animate CC (2014). When I try to Create New, I get an Error popup "Could not find the user document directory"

I think this worked!
I just downloaded an example file and tried opening from outside of the program. At first it gave me some errors but then loaded it up.
After that I've re-saved it and now I can create new files and open files.
Before that I also uninstalled old CC programs that were not showing in the Adobe Creative Cloud apps.

Creating new work order - error on %001

Similar Messages

Maybe you are looking for