Price updation in table EIPA

Hello Friends
We are using 7 types of Purchase Orders and net price is updating for all type of purchase orders except one which is the PO type is FP (Using exclusively for foreign material procurement).
I have observed in table u201CEIPAu201D - Order Price History: Info Record and field u201C PREISu201D price is not updating ONLY in FP type PO. In P, item level, Material data tab u2013 Info Update has been selected,
Could u please explain why it is not updating in EIPA-PREIS, what are the reasons?
Note -Info record has been created
Thanks
Vijayakumar TVN

NO ONE ANSWERED HENCE ISSUE HAS BEEN MARKED AS CLOSED

Similar Messages

Not able to view actual Price updated 'Value' in Change Tracker

I was able to get my Change tracker to work and it is functioning. (SRM 5.0 MDM5.5 )... Configured Portal iViews for change tracker.
If I change a description I can see it in the change tracker application. But if I try and track a Price change it only shows me a date-time and user as to I when the price was changed it doesnu2019t show me the actual value changed, for my audit purposes.
On the portal the change tracker "Field" dropdown shows -> Price Updated. this is what is tracking any change of price.
In MDM Console-> Admin->Change Tracker I am tracking under Catalog Items: Price information, Price Updated, Special search terms, long description.
When I look at the Data manager in the Record Detail, I see u2018Price Updatedu2019 and it only has a Date and time stamp. In this same Record Detail, I see the field Price Information that contains :Lower bound, Purchasing Info record ID, Purchasing Organization, Amount and Currency. Amount-> contains the actual price value. This is what i want to see in the portal iView as Old value and New value....this is what I am unable to view? theres one small step i am not doing...
I am trying to track the actual change in the filed u2018Amountu2019u2026 I have tried to search for it in the Portal iView fields (table, record contains, fields, record)
cheers
alex

Hi Alex,
I would not here comment on change Tracking functionality but can you suggest another workaround to achieve this requirement. If it fits in your requirement you can go ahead with it.
In MDM, Create another field in Main table say Initial Price and for already existing field Amount replace its name with Updated Price in Qualified table Price.
now after this you will see that your by default Updated Price has values as it was your Amount field earlier and Initial Price field as empty. Now for next time, if any record comes using Import Manager then MDM workflow should trigger at Record Import.
This workflow contains following steps.
Start(Checkout)>Assign>Stop(CheckIn)
Assign step should have below expression and assignment:
Price Information.Updated Price
Where I am assuming Price Information is the field in main table which is look up to this qualified table Price.
So in this way you can maintain both existing and updated values of Price and cant then show in your Catalog.
suppose you have already existing record say 1 which has value of Amount as 20.
So that means you have Updated Price as 20 and Initial Price as empty(Null)
Now when same record 1 updates with new Amount say 40, it triggers this workflow on record import which will then assign value of existing updated Price 20 to Initial Field after that Updated Price will update by 40.
Note: This Assignment works well only if your main table record has this Qualified table link as single record. If your main table record contains more than one qualified links then this Assignment would not work fine. So use only if it fits.
Regards,
Mandeep Saini

Stop price update of delivered but un-invoiced (non-invoiced) line items

Hi Gurus,
I need some help regarding price update of line items which are delivered but not invoiced yet.
Case 1:
I am calling the FM 'BAPI_SALESORDER_CHANGE' and passing the line item (say 10) whose price needs to be updated. This line item is neither delivered nor invoiced. Result, correct change of price for line item 10.
Case 2:
In the above order, i am adding another line item (say 30), which is completely delivered, but I have not yet created an invoice for it. I want that this line item's price should not be changed (as delivery is already created for it). So, in my price update report, I check and filter this line item (10) and pass only line item 30 to the BAPI. Result: not only line item 30 but line item 10 also gets updated with new price!!
Case 3:
I created a new line item(40) and created an invoice for it after completely delivering it. When I call the BAPI now, I again filter the line items 30 and 40 and pass only line item 10 which i want to be updated.
Result:
Line item 10 - updated with new price
Line item 30 - updated with new price
Line item 40 - not updated
Requirement:
Any line item that is completely delivered should not be updated with the new price regardless of it having an invoice or not.
Assumptions:
I am running a custom report to find the line items that need change and calling the BAPI_SALESORDER_CHANGE and passing those line items to update the price.
Problem faced:
This process is updating all line items in the SO that are not invoiced regardless of weather I am passing it to the BAPI or not
As far as i know, the checking of the invoice is in some standard program, and hence had debugged the BAPI and got the FM SD_SALES_DOCUMENT_SAVE which in my opinion is doing the change. But on further debugging I lost track of the tables which were holding the data as the code is flowing through a number of user exits and standard forms.
Please help!

Hi Soumyo,
In Pricing Update screen, you will find pricing type X, Y and Z which you can use to define your own pricing update scenarios. Check OSS note 24832. This note provides enough details about each of the update pricing options and also explains on how to use pricing update X, Y, and Z. Let me know if you need any more help on this.
Thanks & Regards
Kapil Sharma
Author - Configuring SAP ERP Sales and Distribution

User Defined Field that gives the date output of the last price update.

We would like to create a User Defined Field (UDF) with a Formatted Search (FMS) on the Item Master form that gives the date output of the last price update specifically the wholesale price.
Last Price Update
Pricelist 2 = Wholesale
Is this feasible?
If it is feasible what is the recommended approach?
Current working UDF on Item Master.
/* Date output is based on all the latest updates on the Item Master.*/
select max(updatedate)
from aitm
where itemcode = $[oitm.itemcode]
Resources that were helpful.
1.(Note:1165947 - Tracking Item Price Changes.)
2. Case 4-I6: Query on price updates. Mastering SQL Queries for SAP Business One By: Gordon Du

Thank you Gordon,
We are looking for the date output of the 'Last Price Update' based on 'Pricelist 2 = Wholesale' which is the challenge.
These 2 are the parameters for the date output, I should have mentioned that in my original message.
Last Price Update
Pricelist 2 = Wholesale
Per reading a bunch of other similar Forum Questions it looked like it is might not be possible to do. With there being no date on the AIT1 table and AITM.Updatedate is based on any and all updates not just last 'Last Price Update' and not sure how to use the loginstanc.
Thanks,
Vern

FM CRMXIF_COND_REC_SLIM_SAVE not updating conditions table

Hi All,
Even I am using the FM CRMXIF_COND_REC_SLIM_SAVE to update conditions in the conditions table SAP004 and SAPSC012 , but for me the conditions are getting updated in table SAPSC012 but not SAP004.
I want to update using the conditoin record guid and want to
update the condition rate value.
Can anyone please help .
Thanks,
Poonam.

Hi Hemanth,
I am using the same FM CRMXIF_COND_REC_SLIM_SAVE to Insert the condition record. In my case, the condition recording getting Inserted and it matches with the Price date and if already exist the put the 'd' as deletion mark and recreate the new condition record.
Similarly I want to delete the Condition record (without Inserting, only 'd' mark should to be updated).
Can you pls help me to solve this issue.
Thanks
Shankar
For Inserting...
=============================================
ls_vardata-fieldname = 'AAAAA'.
ls_vardata-fieldvalue = 'DE7Bdfd1844F001999586C37'.
APPEND ls_vardata TO lt_vardata.
ls_vardata-fieldname = 'KBETR_PRT'.
ls_vardata-fieldvalue = '30'.
APPEND ls_vardata TO lt_vardata.
ls_vardata-fieldname = 'KONWA'.
ls_vardata-fieldvalue = '%'.
APPEND ls_vardata TO lt_vardata.
ls_vardata-fieldname = 'DATE_FROM'.
ls_vardata-fieldvalue = '20090730'.
APPEND ls_vardata TO lt_vardata.
MOVE lt_vardata TO ls_entry-cond_record-variable_fields.
ls_entry-cond_record-object_task    = 'M'.
ls_entry-cond_record-ct_application = 'CRM'.
ls_entry-cond_record-ct_usage       = 'PR'.
ls_entry-cond_record-cond_table_id = 'ABC90012'.
ls_entry-cond_record-cond_type      = 'YSHA'.
ls_entry-object_representation      = 'E'.
APPEND ls_entry TO ls_data.
CALL FUNCTION 'CRMXIF_COND_REC_SLIM_SAVE'
EXPORTING
    data   = ls_data
IMPORTING
    return = lt_return.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
IMPORTING
return        = lt_ret.
For Deleting..... I have tried with below code but its not working.
===================================================
ls_vardata-fieldname = 'AAAAA'.
ls_vardata-fieldvalue = 'DE7B43423AE659F1844F001999586C37'.
APPEND ls_vardata TO lt_vardata.
MOVE lt_vardata TO ls_entry-cond_record-variable_fields.
ls_entry-cond_record-object_task    = 'D'.
ls_entry-cond_record-cond_table_entry_id   = 'DE7CECCB980CA6F1844F001999586C37'.
ls_entry-cond_record-ct_application = 'CRM'.
ls_entry-cond_record-ct_usage       = 'PR'.
ls_entry-cond_record-cond_table_id = 'ABC90012'.
ls_entry-cond_record-cond_type      = 'YSHA'.
ls_entry-object_representation      = 'E'.
APPEND ls_entry TO ls_data.
CALL FUNCTION 'CRMXIF_COND_REC_SLIM_SAVE'
EXPORTING
    data   = ls_data
IMPORTING
    return = lt_return.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
IMPORTING
    return = lt_ret.

Change of Costing Variant in Marking Allowance for CK24 price update

Dear All,
In CK24, price updation previously i had selected one costing variant for one particular material and released the standard price. Now, I am trying to do price update for a different material for which I used different costing variant for doing the material cost estimate. Now when I am going to Marking Allowance in CK24 for that particular company code the previous costing variant is only displaying. But now for the current material that is not the costing variant for which i need price updation. It is just displaying the old costing variant.
Please let me know how to change the costing variant for the same period.
Regards
Srikanth

Hi Srikanth,
1. IMG: Logistics - General, Retail Pricing
Define list variant and assign items
              Enhance or create a new list variant with list field VKP01
2. IMG: Logistics - General, Retail Pricing
Texts for list fields
              Adjust the text for the list field, for example, PP old
3. Define a new SD condition type ZEKA, for example as a copy of VKP0 (Transaction V/06)
              You can create this new condition either as a separate condition or if it is always determined together with, for example VKP0, you can define it as a condition supplement of VKP0. You achieve this by not assigning an access sequence to ZEKA but including it in the condition supplement schema (schema VKP000 in the standard system) instead. In addition, assign the supplement schema of the main condition (master data subscreen, for example schema VKP000). The main condition must be contained in the calculation schema used so that the condition supplements can be found.
4. Insert the new condition type ZEKA in the sales price calculation schema (Transaction V/08)
              Enhance the schema (assignment per pricing type) with the new condition ZEKA. In the standard system, we deliver schema WWS001 and WWS002. You can insert ZEKA at the end of the schema as a statistical condition.
5. IMG: Logistics - General, Retail Pricing
Control - control per list field, allowed costing levels
              For the sales price calculation schema used, you must set control parameters for the list fields EKPNN and VKP01.
List field EKPNN: In the lower subscreen (Saving list fields in master conditions) enter the new condition type ZEKA (application V). If the new condition type has an access sequence, that is, it is not used as a condition supplement, then you must specify in screen 'Allowed pricing levels' the condition tables in which ZEKA should be stored.
List field VKP01: In the mid subscreen (Transport calculating schema data for list field), specify ZEKA as SP condition type.
Note: if you want to send ZEKA for example in the assortment list as a condition, then you must also enhance the schema for calculating the sales price (VKP001, VKP002 or VKP003 in the standard system) with ZEKA.
If still not working ping me,
Regards,
Srinivas Muthyala

Updating a table hz_parties

Hi
I have a question about a table in oracle hz_parties
I have update this table and changed the perons_last_name in sql
plus and then commit now when I go into the applications
from the receivable user then customer standar but the data does
not change here but when I query up the data from sql plus it
has changed.
Any idea why would that happend
alpha

The update statement will be something like this
UPDATE
   service
SET
   service.total = (SELECT price FROM part, service_charge WHERE part.id = service_charge.part_id)
WHERE
   service.id = (select id from service_charge where id = service.id)Alternatively check this link on Merge.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_9016.htm#i2081218
Regards
Raj
P.S : I have not tested the code and you should bear in mind if the select returns more than one row then you will hitting an error.

Moving average price updation when goods receipt posted

Hi,
Please let me know in which tables the moving average prices changes get updated when goods receipt is posted. Also let us know the process as to how moving average price gets updated in the accounting1 view in material master.

Hi,
Its updating in the table MBEW.
To see the log of moving averae price updation, use report S_P00_07000139.
Example :
Stock quantity : 10No's.
MAP : 100Rs.
GR : 10No's@12Rs
Now MAP will become 11Rs (220/20)
Regards,
Prabu

API to update PO_LINE_LOCATIONS table

Does anyone know any public/private API to update po_line_locations table.
We have the following requirement.
-We are planning to implement iSupplier portal for Consignment Suppliers.Since we don't have VMI enabled, We need to create Purchase Orders before suppliers could create ASN.
So, we automated this process by importing Purchase Orders through Open Interface(PDOI).
Oracle has a known BUG with Open Interface that it does not allow importing Consignment PO's.Therefore,We need to update po_line_locations.is_consigned_flag ='Y' after PO is created.
Any help would be greatly appreciated.
Thanks,

Hi,
I recommend performing following setups and then try importing the standard PO.
1. Create a blanket purchase agreement mentioning the respective supplier, site, item and price.
2. Create a sourcing rule for the supplier and site used in the BPA.
3. Note the assignment set value from the profile option of "MRP: Default Sourcing Assignment Set".
4. Assign the sourcing rule created in step-2 to the assignment set noted in step-3 as "Item-Organization" assignment.
5. Setup Approved Supplier List (ASL) for the item and map supplier and site mentioned in the BPA.
6. Go to ASL attributes and map the BPA number in the "Source Documents" tab.
7. Next, go to "Inventory" tab of the same form and check the "Consigned from Supplier" checkbox.
Now you try importing the standard PO for the item, supplier and site involved in the above setups.
It should get the CONSIGNED_FLAG checked in the line_locations table, as the standard PO created through front end does the same.
Let me know how you go.
Thanks,
PS.

How to create a Maintenance view in order to update 4 tables

Hello,
I want to update 4 tables having the same key. MANDANT + SIRET (fiscal french ID).
I try to create a maintenace view, i need to update the 4 tables using a single screen.
When i use the relationship the system display a message "Relationships with unsuitable cardinality"
The first table contain only the ID, the 3 others contains some informations (adress, name, and others)
Thanks for your help
Christophe

Hello,
you could check, if your other three tables have a correct foreign key definition on the field SIRET.
Tranaction SE11 -> pstion on the field and press the foreign key button.
Check Table has to be your first table; cardinality has to be 1 :1 or 1 to N.
Regards Wolfgang

While updating a table i am getting ORA-00600 error.

Hi all,
While updating a table i am getting the following:
**SQL Error: ORA-00600: internal error code, arguments: [qkebCreateConstantOpn1], [], [], [], [], [], [], [], [], [], [], []**
**00600. 00000 - "internal error code, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]"**
I am not getting how to proceed on this. Please guide me.
Thanks,
Ritesh

While performing some unspecified action (no DML) on an unknown table (no DDL) in an unknown version and edition of the Oracle database you had an untrapped Oracle exceptions.
There are too many unknowns to help you beyond recommending you open an SR at MyOracleSupport.

Error in updating to table WRPT

Hi All,
I am trying to update lenght, width and height for Material .
After i save the article and go back "It gives Express Document " which doesnot save the changes ..
When i checked SM31 it gives error" Error in updating to table WRPT"
Regards
Vikrant M Kelkar

Still not sorted

Error in updating OBNK Table ( Bank Statements and Reconciliations,Manual)

PLease advise ,
Bank Statements and Reconciliations,Manual Reconciliation
Client is receiving the following message:
Error in updating OBNK Table
Edited by: Philip Eller on May 20, 2008 9:03 AM

Hi Darpal Thiarha,
Please kindly refer to note 1132591 and note 1128677 to see if these are relevant to this issue. Upgrading to 2007A PL15 or above may avoid such issues relevant with the error 'Error in updating OBNK Table'.
Regards,
Candice Ren
SAP Business One Forums Team

Error in updating condition table 372

Hello,
While saving Excise Invoice I am facing error 'Error in updating condition table 372'.Could you please solve this probelm?
Thanks in Advance

Dear All,
I done this--by doing some configuration changes.
Normally while doing Exports we are tempted to use the same sales area and accordingly we may give the combination of excise grp+series grp+export type in IMG>>>Logistics General>>>India>>>Business transactions>>>Outgoing excise invoices>>>Maintain default excise groups and series groups.
Once after removing the export type to your sales area combination--system will show this error--and we cannot even post the Excise invoices.(J1IIN)
I tried in my IDES--that with export type(Ex.Export under Bond)--with this assignment--i am able to post my excise invoices.
Once after removing this assignment of export type--again i am getting this error.
Actually i am not even aware why it is happening--almost after two months of struggle--i find this.
(i feel it is in the same way that we cannot even open/See a sales order by deleting sales group which was created&used previously)
i am sharing this because somebody may get a little help with my thread.
Mark this if helpful--there by others can easily find this thread.
Phanikumar

ADF master-detail master selection not updating detail tables properly

Hi All,
I am using JDev version : 11.1.2.0.0
I created new Fusion Web Application Module. In that module I created a master-detail data model and added them to a page fragment with a query panel. When I run it as a separate module, It works perfectly and Master selection correctly updates detail tables.
But when I integrate that module to another Fusion Application(Add application jar file to the Master Application libraries), Master-details master selection not updating detail tables properly. This problem occurred sequentially.
The problem is that.
After the page load, first selection of the Master Table works correctly and detail tables update correctly.
But second selection doesn't work, means detail table doesn't get update according to the Master table.
And again in the third selection works correctly.
This happens in a sequential manner. I monitor the behavior using Firebug. Observations are as follows,
When running correctly, Response of the Post Definition is
<?xml version="1.0" ?> <partial-response><changes><update id="pt1:t1"><![CDATA[<div tabindex="0" id="pt1:t1" class="xpa xpi" _leafColClientIds="['pt1:t1:c1','pt1:t1:c2','pt1:t1:c3','pt1:t1:c4','pt1:t1:c5','pt1:t1:c6','pt1:t1:c7','pt1:t1:c8','pt1:t1:c9','pt1:t1:c10','pt1:t1:c11','pt1:t1:c12','pt1:t1:c13']"><div id="pt1:t1::ch" style="overflow:hidden;position:relative;width:1365px;" _afrColCount="13" class="xz4"><table class="xz6" summary="This table contains column headers corresponding to the data body table below" id="pt1:t1::ch::t" style="position:relative;table-layout:fixed;width:1365px" cellspacing="0"><tr><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th></tr><tr><th id="pt1:t1:c1" _d_index="0" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c1::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">DateFormat</div></th><th id="pt1:t1:c2" _d_index="1" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c2::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">DefinisionId</div></th><th id="pt1:t1:c3" _d_index="2" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c3::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldId</div></th><th id="pt1:t1:c4" _d_index="3" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c4::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldLabel</div></th><th id="pt1:t1:c5" _d_index="4" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c5::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldLength</div></th><th id="pt1:t1:c6" _d_index="5" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c6::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldOffset</div></th><th id="pt1:t1:c7" _d_index="6" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c7::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldOrder</div></th><th id="pt1:t1:c8" _d_index="7" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c8::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldStatus</div></th><th id="pt1:t1:c9" _d_index="8" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c9::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldType</div></th><th id="pt1:t1:c10" _d_index="9" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c10::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldTypeLen</div></th><th id="pt1:t1:c11" _d_index="10" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c11::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">IgnoreField</div></th><th id="pt1:t1:c12" _d_index="11" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c12::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">IsMandatory</div></th><th id="pt1:t1:c13" _d_index="12" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c13::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">RecordType</div></th></tr></table></div><div id="pt1:t1::db" class="xyx" style="position:relative;width:100%;overflow:hidden" _afrColCount="13"></div><div id="pt1:t1::sm" class="xzt" style="position:absolute;display:none"></div><div id="pt1:t1::ri" class="xyz" style="position:absolute;display:none;overflow:hidden"></div><div id="pt1:t1::dataW" style="display:none"></div></div>]]></update><update id="f1::postscript"><![CDATA[<span id="f1::postscript"><span id="f1::postscript:st"><input type="hidden" name="javax.faces.ViewState" value="!-75cc188st"></span></span>]]></update><update id="d1::iconC"><![CDATA[<span id="d1::iconC" style="display:none"><span id="af_table::disclosed-icon"></span><span id="af_table::undisclosed-icon"></span></span>]]></update><update id="javax.faces.ViewState"><![CDATA[!-75cc188st]]></update><eval><![CDATA[AdfPage.PAGE.__handleRichResponseAction('/MillenniumCSD-ViewController-context-root/faces/FileDefinition?_adf.ctrl-state=cmpl0ptfg_7');]]></eval><eval><![CDATA[AdfPage.PAGE.sendStreamingRequest("pt1:t1");]]></eval><extension id="adf-script-library">/MillenniumCSD-ViewController-context-root/afr/partition/gecko/default/opt/dnd-SHERMAN-1147.js</extension><extension id="adf-script-library">/MillenniumCSD-ViewController-context-root/afr/partition/gecko/default/opt/nav-SHERMAN-1147.js</extension><extension id="adf-script-library">/MillenniumCSD-ViewController-context-root/afr/partition/gecko/default/opt/menu-SHERMAN-1147.js</extension><extension id="adf-script-library">/MillenniumCSD-ViewController-context-root/afr/partition/gecko/default/opt/table-SHERMAN-1147.js</extension><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/JarLoaderPages/jquery-1.7.1.min.js');</eval><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/JarLoaderPages/dis_contx.js');</eval><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/js/floating_bar_bottom.js');</eval><eval>if(self.window.name != "MillenniumDepository"){ self.location = "mcsd.html"; }</eval><eval><![CDATA[AdfDhtmlLookAndFeel.addSkinProperties({"af|table-tr-column-scroll-animation-duration":"300","af|table-tr-column-reorder-animation-duration":"600","af|table-tr-hover-highlight-row":"true"});AdfPage.PAGE.addComponents(new AdfRichTable('pt1:t1',{'rowSelection':'single','rowBandingInterval':0,'editingMode':'none','afrSelListener':true}),new AdfRichColumn('pt1:t1:c1',{'sortProperty':'DateFormat','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c2',{'sortProperty':'DefinisionId','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c3',{'sortProperty':'FieldId','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c4',{'sortProperty':'FieldLabel','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c5',{'sortProperty':'FieldLength','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c6',{'sortProperty':'FieldOffset','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c7',{'sortProperty':'FieldOrder','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c8',{'sortProperty':'FieldStatus','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c9',{'sortProperty':'FieldType','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c10',{'sortProperty':'FieldTypeLen','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c11',{'sortProperty':'IgnoreField','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c12',{'sortProperty':'IsMandatory','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c13',{'sortProperty':'RecordType','sortable':true,'minimumWidth':12,'rowHeader':false}));AdfPage.PAGE.__recordSessionTimeout(1800000, 120000, "http://127.0.0.1:7101/MillenniumCSD-ViewController-context-root/faces/FileDefinition");AdfPage.PAGE.__initPollingTimeout(600000);AdfPage.PAGE.clearMessages();AdfPage.PAGE.clearSubtreeMessages('pt1:t1');AdfPage.PAGE.clearSubtreeMessages('pt1:resId1');]]></eval></changes></partial-response>
When not running correctly, Response of the Post Definition is
<?xml version="1.0" ?> <partial-response><changes><update id="f1::postscript"><![CDATA[<span id="f1::postscript"><span id="f1::postscript:st"><input type="hidden" name="javax.faces.ViewState" value="!-75cc188st"></span></span>]]></update><update id="javax.faces.ViewState"><![CDATA[!-75cc188st]]></update><eval><![CDATA[AdfPage.PAGE.__handleRichResponseAction('/MillenniumCSD-ViewController-context-root/faces/FileDefinition?_adf.ctrl-state=cmpl0ptfg_7');]]></eval><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/JarLoaderPages/jquery-1.7.1.min.js');</eval><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/JarLoaderPages/dis_contx.js');</eval><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/js/floating_bar_bottom.js');</eval><eval>if(self.window.name != "MillenniumDepository"){ self.location = "mcsd.html"; }</eval><eval><![CDATA[AdfPage.PAGE.__recordSessionTimeout(1800000, 120000, "http://127.0.0.1:7101/MillenniumCSD-ViewController-context-root/faces/FileDefinition");AdfPage.PAGE.__initPollingTimeout(600000);AdfPage.PAGE.clearMessages();AdfPage.PAGE.clearSubtreeMessages('pt1:t1');AdfPage.PAGE.clearSubtreeMessages('pt1:resId1');]]></eval></changes></partial-response>
I could not figure out what went wrong when integrating to another module.
Can you please help me to rectify this problem.
Thanks
dk

Hi,
sound to be an implementation specific issue that is hard to comment on without knowing how to reproduce it. If you have a rerooducible test case based on the Oracle HR schema using JDeveloper 11.1.1.6, zip it up, rename the "zip "extension to "unzip" and sent it to the mail address you find in my OTN profile. If you don't have that test case, explain how this can be reproduced
Frank

Price updation in table EIPA

Similar Messages

Maybe you are looking for