Error Updating table condition table 372 in J1IIN

Hello all,
I am facing the problem while working in ECC 6.0 environment in the transaction code J1IIN.
I have maintained the condition type JEXP ( A/R BED %) as 14% with the Key combination Country/Plant/Control Code (Table 357). While iam saving the Excise invoice the system is throwing the error like error updating the table condition table 372
I have gone through the post given by Ms. Jyoti few days back and tried to do some changes in the customisation.
I tried to maintain a different access sequence for the condition type JEXP i.e a new Access sequence(ZJEX) and also a new condition tpe (ZJEP). We don't have other Excise condition type in our Pricing procedure.
In the access sequence except condition table 372, I have maintained all other condition tables.
Still the error is persisiting. Can anyone put some light on the issue.
I have even traced the values being hit in the tables directly. There is no relation of table 372, then why is it being cause of the error.
Also while debugging it gives a message "An exception (CX_BADI_INITIAL_REFERENCE) occured".
Does this help in anyways.
Gurus plz give u r suggestions.
Thanks in advance,
Regards,
Karthik.

Hello Srinivas/Sandeep
Please ensure that access sequence in the condition type JEXC has got the table 372. If it is not there please maintain it.
The standard access sequence used in all duty condition type
is JEXC which has got the table 372 this will get updated once
you save your excise invoice.
If the issue is resolved, kinldy close the message.
Regards
MBS

Similar Messages

Error updating table 372"

Hi friends,
when iam generating a excise invocie the system triggers"Error updating table 372"
Any possible solution for this?
Thanks
Ivy

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

Error updating table 37

HI,
When I am generating a excise invoice the system triggers u201CError updating table 372"
I have not maintained of table 372 in access seq (Cd type (JEXP) . Previous i have maintained this table in my access seq and its working fine but I am not able to save the document,
in that time i got error like
No account is specified in item 0000000001
Message no. F5670
Diagnosis
No account was specified for account type "S" in item "0000000001" of the FI/CO document.
System Response
The Financial Accounting program cannot process the document.
Procedure
A system error has probably occurred in the application you called up. Check the data transferred to item "0000000001" of the FI/CO document.
Pl let me know if anything else is required to avoid further problems
All errors I have attached with screen shot pl give me reply .
Pl let me know if anything else is required to avoid further problems
Any possible solution for this?
1 ) IN VKOA transaction G/L accounts which are assigned in our sales account keys with combination of condition table fields is :
App CndTy. ChAc SOr AAG AAG ActKy G/L acct
V KOFI CAIN ERRO 01 06 ERL 300009 Sales
V KOFI CAIN ERRO 01 06 EXD 140014 CENVAT Clearing
V KOFI CAIN ERRO 01 06 EXS 140009 Ed Cess
V KOFI CAIN ERRO 01 06 MW3 140071 VAT
V KOFI CAIN ERRO 01 06 MWS 140071
V KOFK CAIN ERRO 01 06 ERL 300009
V KOFK CAIN ERRO 01 06 EXD 140014
V KOFK CAIN ERRO 01 06 EXS 140009
V KOFK CAIN ERRO 01 06 MW3 140071
V KOFK CAIN ERRO 01 06 MWS 140071
In Customer account assignment group and material account assignment groups. Setting is correct
in the IMG settings
IMG>Logistics general>Tax on Goods movements>India>Account determination.
What GL should be assign here
Excise G/L A/c for RG23A BED CENVAT offset account Mod.Clerng
ARE1
ARE3
DLFC ? ? ? ? ?
EWPO ? ? ? ? ?
GRPO
TR6C
UTLZ
Pl let me know if anything else is required to avoid further problems
Regards
SAPCO

Solved. Thanks to....
http://www.vecna.com/whatWeDo/projects/9ias-experience.html

U201CError updating table 372"

HI,
When I am generating a excise invoice the system triggers u201CError updating table 372"
I have not maintained of table 372 in access seq (Cd type (JEXP) . Previous i have maintained this table in my access seq and its working fine but I am not able to save the document,
in that time i got error like
No account is specified in item 0000000001
Message no. F5670
Diagnosis
No account was specified for account type "S" in item "0000000001" of the FI/CO document.
System Response
The Financial Accounting program cannot process the document.
Procedure
A system error has probably occurred in the application you called up. Check the data transferred to item "0000000001" of the FI/CO document.
Pl let me know if anything else is required to avoid further problems
All errors I have attached with screen shot pl give me reply .
Pl let me know if anything else is required to avoid further problems
Any possible solution for this?
1 ) IN VKOA transaction G/L accounts which are assigned in our sales account keys with combination of condition table fields is :
App CndTy. ChAc SOr AAG AAG   ActKy G/L acct
V   KOFI    CAIN   ERRO 01   06      ERL   300009 Sales
V   KOFI    CAIN   ERRO 01   06      EXD 140014 CENVAT Clearing
V   KOFI    CAIN   ERRO 01   06      EXS 140009 Ed Cess
V   KOFI    CAIN   ERRO 01   06      MW3 140071 VAT
V   KOFI    CAIN   ERRO 01   06      MWS 140071
V   KOFK   CAIN ERRO   01 06      ERL    300009
V   KOFK   CAIN ERRO   01 06      EXD   140014
V   KOFK   CAIN ERRO   01 06      EXS   140009
V   KOFK   CAIN ERRO   01 06      MW3   140071
V   KOFK   CAIN ERRO   01 06      MWS   140071
In Customer account assignment group and material account assignment groups. Setting is correct
in the IMG settings
IMG>Logistics general>Tax on Goods movements>India>Account determination.
What GL should be assign here
Excise G/L A/c for RG23A BED     CENVAT offset account               Mod.Clerng
ARE1
ARE3
DLFC    ?            ?                      ?           ?          ?
EWPO ?           ?                       ?          ?          ?
GRPO
TR6C
UTLZ
Pl let me know if anything else is required to avoid further problems
Regards
SAPCO

Hi
If you are using subtransaction type then ensure the same setting as of without subtransaction type for ETT DLFC under CIN customization.
I mean you should maintain same setting for ETT DLFC with and without subtransaction type.
Also check the setting ETT GRPO EWPO and DIEX should be same as with and without subtransaction type.
Regards
MBS

Error updating the table condition table 372 in J1IIN

Hello all,
I am facing the problem in the transaction code J1IIN (In CIN).
I have maintained the condition type JEXP ( A/R BED %) as 16% with the Key combination Country/Plant/Control Code (Table 357). While iam saving the Excise invoice the system is throwing the error like Error updating the table condition table 372
I have gone through the post given by Ms. Jyoti few days back and tried to do some changes in the customisation.
I tried to maintain a different access sequence for the condition type JEXP i.e In the access sequence except condition table 372, I have maintained all other condition tables.
Still the error is persisiting. Can anyone put some light on the issue.
I have even traced the values being hit in the tables directly. There is no relation of table 372, then why is it being cause of the error.
Gurus plz give ur suggestions.
Thanks
Srinivas

Hello Srinivas/Sandeep
Please ensure that access sequence in the condition type JEXC has got the table 372. If it is not there please maintain it.
The standard access sequence used in all duty condition type
is JEXC which has got the table 372 this will get updated once
you save your excise invoice.
If the issue is resolved, kinldy close the message.
Regards
MBS

Error Updating Table with "Get Active UnitOfWork" Checked

Hi everyone.
I call invoke the a DB Adapter twice to update table in one BPEL, and so I have checked "Get Active UnitOfWork" so that each update can be persisted. I am seeing inconsistent results. What could be causing this?

Hi, Have you checked the .jca source to make sure this value is indeed checked? Sometimes even when you check this option in the wizard it doesn't reflect in the source when you also perform a select operation: http://docs.oracle.com/cd/E12839_01/relnotes.1111/e10133/adapter.htm. Also are you using the xADataSource driver in the data source and the xADataSourceName ConnectionFactory property?
21.1.5.1 The Value Of the Active Unit Of Work Property Is Not Saved for Outbound SELECT Operation
While configuring an outbound Oracle Database Adapter to perform a SELECT operation, if you select Get Active Unit of Work in the Adapter Configuration Wizard - Advanced Option page, then the value of the GetActiveUnitofWork property is not saved in the .jca file.
The workaround for this issue is to manually add this property in the .jca file of the Oracle Database Adapter, as shown in the following example:
<property name="GetActiveUnitOfWork" value="true"/>

Error updating tables based on schema

Hello,
I'm trying to update a table based on the next schema:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xdb="http://xmlns.oracle.com/xdb" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
     <xs:element name="HILO" xdb:SQLType="HILO_TYPE" xdb:defaultTable="HILO_TABLE">
          <xs:complexType>
               <xs:sequence>
                    <xs:element name="MENSAJE" maxOccurs="unbounded" xdb:SQLType="MENSAJE_TYPE" xdb:maintainOrder="false">
                         <xs:complexType>
                              <xs:sequence>
                                   <xs:element name="FECHA" type="xs:date" xdb:SQLType="DATE"/>
                                   <xs:element name="TITULO" xdb:SQLType="VARCHAR2">
                                        <xs:simpleType>
                                             <xs:restriction base="xs:string">
                                                  <xs:maxLength value="200"/>
                                             </xs:restriction>
                                        </xs:simpleType>
                                   </xs:element>
                                   <xs:element name="CUERPO" type="xs:string" xdb:SQLType="VARCHAR2"/>
                                   <xs:element name="DNI_CREADO_POR" xdb:SQLType="VARCHAR2">
                                        <xs:simpleType>
                                             <xs:restriction base="xs:string">
                                                  <xs:maxLength value="9"/>
                                             </xs:restriction>
                                        </xs:simpleType>
                                   </xs:element>
                                   <xs:element name="ASIGNATURA" xdb:SQLType="VARCHAR2">
                                        <xs:simpleType>
                                             <xs:restriction base="xs:string">
                                                  <xs:maxLength value="3"/>
                                             </xs:restriction>
                                        </xs:simpleType>
                                   </xs:element>
<xs:element name="APROBADO" xdb:SQLType="VARCHAR2">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="APROBADO"/>
<xs:enumeration value="RECHAZADO"/>
<xs:enumeration value="PENDIENTE"/>
</xs:restriction>
</xs:simpleType>
                                   </xs:element>
                              </xs:sequence>
                              <xs:attribute name="NUMERO" type="xs:int" use="required" xdb:SQLType="INTEGER"/>
                         </xs:complexType>
                    </xs:element>
               </xs:sequence>
               <xs:attribute name="CONTADOR" type="xs:int" use="required" xdb:SQLType="INTEGER"/>
          </xs:complexType>
     </xs:element>
</xs:schema>
And the update that i'm trying to do is the next one:
UPDATE hilo_table p
SET value(p) =
updatexml(value(p),'/HILO/MENSAJE/CUERPO/text()', 'Edit' )
where existsnode(VALUE(p), 'HILO[@CONTADOR="1"]') = 1;
ERROR en línea 1:
ORA-01732: operación de manipulación de datos no válida en esta vista
I have updated another tables based on schema and it works fine, any idea?

OK this is your decision. However If you are building a production system that is important to your orgnanization as the product manager I strongly recommend that you either upgrade to a least 9.2.0.3.0 or discontinue using XML DB technology completely
There are probably somewhere in the order of 500 serious XML DB related bugs fixed between 9.2.0.1.0 and 9.2.0.7.0, all of which have been regarded as serious enough to impossible for a customer to develop or deploy a production system. None of these will EVER be fixed or available as patches for 9.2.0.1.0.
The way in which we store the data on the disc is different in 9.2.0.3.0, and while in theory we migrate the on disc format when you upgrade in practice I know that is has never been tested with any significant amount of data present.
Also you really want to take the support situation into account. Image this, it's 3:00am in the morning and your production system fails due one of the bugs that have been fixed in a later release of the product. You cannot find a workaround and you call oracle support for help. They WILL say, sorry there is nothing we can do until you upgrade to 9.2.0.3.0. Now you have to upgrade in hurry and then re-test everything you have done before you can even start working on a fix.
From a business perspective staying on 9.2.0.1.0 and continuing to use the XML DB technology makes no sense. I hope I have made this clear. If you want I will be more than happy to discuss this issue with your development managers.

29875; error updating table with geometry but without index

hi,
I've a table with next description
AGGREGATEDUNIT_ID NOT NULL NUMBER(38)
DATASET_ID NUMBER(38)
GEOMETRY MDSYS.SDO_GEOMETRY
REDEFINEDMETADATA SYS.XMLTYPE
I dont need a spatial index in column GEOMETRY, but when I try an update operation:
INSERT INTO AGGREGATEDUNIT (AGGREGATEDUNIT_ID, DATASET_ID) VALUES (389, 893)
I get next error:
INSERT INTO AGGREGATEDUNIT
ERROR en lmnea 1:
ORA-29875: fallo al ejecutar la rutina ODCIINDEXINSERT
ORA-13203: fallo al leer la tabla USER_SDO_GEOM_METADATA
ORA-13203: fallo al leer la tabla USER_SDO_GEOM_METADATA
ORA-06512: en "MDSYS.SDO_INDEX_METHOD_9I", lmnea 183
ORA-06512: en lmnea 1
anybody knows?
thanx

Hi,
Whether you need the index or not, someone has created a spatial index on the table.
You can drop the index, or you can add the metadata for the table into user_sdo_geom_metadata (it was there at the time the index was created).
Hope this helps,
Dan

EJB Error updating table

I am getting Error while updating a table ..the error message is
JBO-29000: Unexpected exception caught javax.ejb.EJBException, msg=Transaction was rolled back. java.lang.NullPointerException; nested exception is java.lang.NullPointerException.
Transaction was rolled back: java.lang.NullPointerException; nested exception is java.lang.NullPointerException.
I have a CMP for a table. This beans use Data Transfer Objects also to retain the session values. To update the Database and also to fetch the value.
When updating from the form DTO gets updated..but not the actual table.
Can somebody let me know why and how to fix this
Thanks in advance

Transaction was rolled back: java.lang.NullPointerException
Is a value added for a NOT NULL column null?

Error updating table with form

All i have setup a application using the tabular form, and i went through the wizard and now when the table comes up with the entries that i can change i get this error
Error in mru internal routine: ORA-20001: no data found in tabular form
Error Unable to process update.
OK
Even when i use the delete i get
ORA-20001: Error in multi row delete operation: row= 5, ORA-01403: no data found,
Error multi row operation failed
OK
And i am unable to update any rows

It looks to me you wrongly selected the P-Key for the tabular form.
If you can provide some more information like the table columns, p-key etc we may help you out in debugging.

Error while creating the Excise Doc in J1IIN

Hi Friends,
When we are trying to create an excise doc using J1IIN, we are getting error:
"Error updating table J_1IPART2."
What could be the possible reason for this?
Regards,
Abhishek

Dear Abhishek
Go to IMG Path -- Logistics-General --> Tax on Goods Movements --> India --> Account Determination --> Specify G/L Accounts per Excise Transactions.
Here check whether you have maintained G/L Accounts in all the columns starting from RG23A BED.
thanks
G. Lakshmipathi

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

Error updating the table 372

Hi Gurus,
I maintained the JCEP ( A/R Cess %) as 3%. While iam saving the Excise invoice the system is throwing the error like error updating the table condition table 372
Gurus plz give u r suggestions.
regards,
jyothi.
Edited by: jyothi. on Feb 25, 2008 7:26 AM

Hi Murali!
Even I am facing the same problem while working in ECC 6.0 environment. I am continuing in the same post as I feel it is most relevant post to continue the issue instead of opening a new issue.
I tried to maintain a different access sequence for the condition type JEXP i.e a new Access sequence(ZJEX) and also a new condition tpe (ZJEP). We don't have other Excise condition type in our Pricing procedure.
In the access sequence except condition table 372, I have maintained all other condition tables.
We have maintained the values against table 357- Country/Plant/Control Code.
Still the error is persisiting. Can you put some light on the issue.
I have even traced the values being hit in the tables directly. There is no relation of table 372, then why is it being cause of the error.
Thanks in advance,
Regards,
Karthik.

Error updating in table

Hi,
I'm updating a Master-Detail table, when I'm updating table its generate following error i.e
Current version of data in database has changed since user initiated update.current checksum = "650813AF26DC2A7B5B371364DA0947F4", item checksum = "8A5BD352579816A64B541699495E9B20".
Thanks in advance.
Baloch.
Edited by: Baloch on Dec 28, 2010 11:12 AM

Hello Srinivas/Sandeep
Please ensure that access sequence in the condition type JEXC has got the table 372. If it is not there please maintain it.
The standard access sequence used in all duty condition type
is JEXC which has got the table 372 this will get updated once
you save your excise invoice.
If the issue is resolved, kinldy close the message.
Regards
MBS

"Error in updating Table J_1iexchdr"

Hi ,
When I am creating the excise invoice, It's terminated the program and gives the following error
"Error in updating Table J_1iexchdr"
What can be the reason?
Regards
Prem

Hi prem
Look if these threads can help
RG23C Update Problem
Problem in SAP Script
billing document not creating
return delivery
************Reward points if usefull**************

Error Updating table condition table 372 in J1IIN

Similar Messages

Maybe you are looking for