Problem in Reversal of 57F4 Challan

Hi,
I m unable to reverse the challan. At the time of reverse of chllan excise duty is not comming.
I have already maintained assesable value and excise duty rate in J1ID but in challan asseble value is zero.
So please respond earliest.
Thanks
Richa Agarwal

Hi Richa,
Apart from what you have maintained ,
Kindly check whether you have created subtransaction type 01 for subcontracting or not.
Check whether it is assigned in Specify excise accounts per transaction or not? It should be for ETTs 57FC,57NR,57CM.
And for all these G/L should be assigned in account determination with & without subtrax type.
Regards,
Piyush

Similar Messages

57F4 Challans. CIN version

Hi Gururs,
We are using CIN version 4.0A. Here is one major problem we are facing.
Just after SAP implementation in 2003, materials were sent to subcontractor along with 57F4 challans. When the goods came back, due to lack of awareness, user created new subcontract orders, raised new 57F4 challans and received the goods against them. So original challans are still open. How to close these challans.
What will be the accounting entries ?

Hi,
after a lot of analysis, I found the problem is actually like this:
Initially some subcontractor challans and subcontractor stock was uploaded in the system in 2003 just after implementation.
When the goods came back, for whatsoever reason, user created new subcontracting PO, new subcontracting challan and received the goods against the new challan. The original challan is lying with status "Posted" in the system till date.
(It is also noticed that while creating the challan the system does not create any accounting document. Neither it does any if the goods come back within 180 days.accounting entries to CENVAT account is only made when the goods have not returned fully and somebody tries to complete the challan. At that time system debits the CENVAT account with the amount equal to the excise credit of the unreturned goods)
Now, user wants to close the challans somehow.
My question is, how to close these challans ? If I try to reverse the challan, system tells me to reconcile first. If I try to reconcile, it tells me to reverse first. How to go about it?
Can we just change the status of the challan using ABAP at the tables ? Or is there any better way to do it ?

57f4 challan

hiii...
here we using sap yearfrom 2006 .when i m using j1ifr for display the subcontarcting challan ...then system showing 2006 pending qty...how we clear 57f4 challan?
Thanks
Rekha Shrama

Hello,
I also facing same problem with 57 F4 challan,
But before reconciling it we need to reverse the open qty towards the vendor then reconcile and then close.
but again the period goes beyond the specified days specified in attributes (180)
Also period not open for last year.. what to do as rekha also facing same problem..
So correct me is that i am correct or wrong
Abhinay Waikar.

57F4 Challan Issue

Hi everyone,
Suppose i am transferring material from my plant to Subcontractor place through 57F4 Challan. I have to get back the material within 180 days. If not i have to pay excise from the day one. Is there any transaction so that i can monitor the material lying in the subcontractor place by Day wise???????
Regards
kamal

hi
If you want to monitor the Challans use report J1IFR - Challan Listing , & select the options reversal due . this will list you the challans
If you want to monitor within 180 days period.... select the returns dtae from & to Option....

57f4 challans Annexure IV

Hi experts,
I have a problem with the report for 57f4 challans-J1IFR. In this report it shows "Quantity pending" even when I have reconciled & completed a particular challan. What does this mean?. I have seen the standard Annexure IV, but nowhere this kind of a remark appears. Is there anything else to be done to remove this message?
Regard
nabil

Hi Expert
I did all the step properly..................GR qty against excise qty. and material document is also correct.......can someone send the step from Subcontracting Po to Subcontracting Challan complete.
regard
nabil

57F4 challan print - getting parent item no and po number for child item

Hi ,
In 57F4 challan, Subcontract components - i.e Child items are used for creating the challans.
However while printing needs the parent item no with the purchase order number for that child item number.
It is getting stored in RM07M structure.
Any inputs / suggestions how to retrive parent item number and purchase order number for child item i.e for subcontract items?
Thank you .
Prasad.

Thank you for the reply. I checked the table RSEG table for material document and PO details, however the RSEG gets populated when there is credit or debit entries.
In this 57F4 challan there is no credit or debit enteries hence would not get in RSEG table.
Appreciate your inputs for any other alternative.
OR is there any table or Function Module to get the enteries of the struture of RM07M .

Problem with reversal of Service entry Sheet

Hi All,
I am facing a problem with reversal of service entry sheet. The user has posted the document in dec 2009 and now the user wants to reverse the doc. I told the process how to reverse it. But when she is trying to revoke the acceptance, she is getting error log.I told her to reset the posting date to present date.Now she tried to change the doc date but she is getting error as "604 item 010 WBS element ****** budget exceeded year 2009". So i advised her further to increase the budget in the year 2009. Even that solution is not working.
Please help in this regard
Thanks & Regards
Nisha Prasad

Hi,
The user is not authorised to change the budget. The person resposible for this is telling that increasing the budget wont help. can you tell me how to view whether the budget is available for the system in the period or not? Can you please help me in this regard?
Thanks
Nisha

57F4 Challan printing with Purchase order number and parent material

Dear Team,
As a SAP standard 57F4 subcontracting challan will have only legal entities,child materials, quantity, assable value etc.
but as a client requirement we need to incorporate the PO number and line item in the 57F4 challan, additionally client requires the parent material also printed in 57F4 challan
Anybody can help me how to get the PO number and parent material in 57F4 Printing, because i have already searched in MSEG table but for the material document number iam not able to find the PO number and line item.
iam posing the GI with referenc to purchase order only. but even iam not getting the PO number with reference to the posted document number in the table.
J Sridharan
Satyam Computer Services Limited

thanks for your reply hemalatha,
i have tried with OMJ3 transaction, but it is purely a print parameter settings for J1IF form. please help me where i can maintain this settings to get the output in MSEG table.
moreover iam creating all the subcontract material documents with ref to PO number only through MB1B transaction. please advise.
Regards
Sridharan

Customer 57f4 challan capture

Hi all!
We are doing a mere job wok. Customer is sending raw materials with delivery challan and 57f4 challan. We are processing the raw material and sending the finished material to the customer. I am receiving the raw material by 561 or also i can use 501 mvt type. I can enter the customer DC number in the TEXT field.
But how to capture the 57f4 challan in SAP. Since we have to do ageing analysis to send it within 180 days.. How to do this?
Thanks in advance,
Raj.

hi
1. Define your customer materials (both component and finished product) as non valuated material, because these materials not effecting the our inventory.
2. create Bom for finished product.
3. Create sales order for service charges with reference to your customer PO.
4. Receive the component from your customer through 501 E (with out po sales order specific).
5. Create Production order with reference to sales order through MRP or manual.
6. confirm the production order and receive the
finished product.
7. Delivery to customer as in normal sales process.
8. Then create performa invoice or billing to your customer.
Please maintain the customer excise challanas manually or you can develop z development for tracking purpose
http://help.sap.com/bp_blv1600/V5600/BBLibrary/HTML/150_EN_IN.htm
regards
kunal
award if helpful
Edited by: kunal ingale on Sep 13, 2008 2:09 PM

57F4 Challan no. re. to PO. No.

Hi,
       Is there any std. report with which we can find the subcontract challan number and goodws transfer number ref. to the Subcontracting PO number.
        Also in which table we can get the information easily as if we select the Table MSEG to get the material transfer doucment with movement type 541 , syetms it taking lot of time then after that i have to seelct the challan number from another table .
    regards,
      zafar

Hi,
           Thanks for your reply, it is very usefull, one more think i want to know is there any report in the same way but it should also give the PO numbers for which still there is No GI and 57f4 challan made as in JI17, it is displaying the Po for whcih challan is made.
    regards,
     zafar

Subcontract process (57F4 challan)

Dear SAP Guru,
I implement a scenerio of subcontracting. A new requiremnt is come under subcontracting. i.e A plant send a Material X to subcontractor through 57F4 Challan. And soncontracotr process that material and add some material with X (i.e. Excisable Material which is add to X) and generate FG Y. when we receive the material then subcontractor want to converison charge with ED of adding material. How do we process this scenerio and how we to capture ED with material and how to pay the excise duty to vendor.
thanx

Hi,
U can Map as -
solution1)
If material code u want for added material then -
Create PO with 2 line item against the vendor.one is procurement item i.e added material and second is s/c item i.e. Y.
Solution2)
If u dont want material code then-
Create PO with 2 line item one is service item which is nothing but the added material cost and second is S/c item i.e Y
regards,
sujit

57F4 challan reconcilation

Hello Friends,
i am facing the below error while do the reconcilation for the 57F4 challan.
"Challan not valid, material doc., is valid for another scenario"
Kindly share your ideas to fix the same.
regards,
sathes

Hi Dear,
In IMG u have left the Setting.
Logistic General-->Tax on Goods Mvt->Business Transaction-->
Subcontracting--->Maintain Mvt Type groups---->
0001 541
0002 101
0002 542
0002 543 O
0002 545
Please don't enter Subcontracting challan manually...select subcontracting challan number by pressing of F4 and Select it and ente rthe year.....

Problem in Reversing MIRO Document

Hi Gurus,
I am getting the following problem when reversing the Miro, please help me in this reagrd.
Balance not zero: 716.48 debits: 76,836.52 credits: 77,553.00
Message no. M8534
Diagnosis
The system has discovered a difference between the debits and credits. This difference lies outside the tolerance limits set.
System Response
The system cannot post the document.
Procedure
If this message appears when you are processing a document online, you can
change the amounts or enter new items until you can post the document
change the Invoice Verification type, so that the document can be posted later in the background.
If this message appeared when a document was verified in the background, you can now process the document.
Regards
Shree

hi
what cost ur entering in field of amount
go to MIRO here do the normal process
now just copy the amount from right top o the amount field
plz check that u have ticked for calculate tax before copying amount
now simulate and check
regards
KI

Closing of 57F4 Challan or Making GR after 180 Days

Hi,
   I want to know if we have made a 57F4 Challan   and partial material we have received from the vendor and remaining material we have not recd till the specified period of 180 days then how to make the GR after 180 Days or how to close the challan
second scenarion if we have send material to vendor with 57F4 channlan and we have not receievd material with in 180 Dya then how to close the challan.
regards,
zafar

Hi niti,
    Thanks for reply, i want to know even if after 180 days we have not receieved the material and if we want to cancel all the document how is the sequemce and process for it as we have created PO , MB1B, and J1IF01 challan then how to cancel all the documents
and as u have steps for making GR after 180 Days with J1IF this is std. procedure avalibale for this   is there any effect of this on other FI entry etc.
regards,
    zafar

Problem with reverse mapping

Hi!
I am having a problem with reverse mapping. Here's what I do (copying the
generated files to a correct directory omitted):
% rd-schemagen -properties jdo.properties -file schema.xml
% rd-reversemappingtool -properties jdo.properties -package testi
schema.xml
% javac -d build/classes src/testi/*.java
% rd-importtool -properties jdo.properties src/testi/testi.mapping
Here's a part of the output:
<clip>
2958 INFO [main] jdbc.Schema - Found existing table "Kirja" for schema
"null".
3002 INFO [main] jdbc.Schema - Found existing table "Kustantaja" for
schema "n
ull".
3047 INFO [main] jdbc.SQL - [C: 5948361; T: 15336018]close
3125 INFO [main] jdbc.SQL - [C: 2478770; T: 15336018]open:
jdbc:mysql://localh
ost/kirjakauppa (root)
3129 INFO [main] jdbc.Schema - Found existing table "Kirjailija" for
schema "n
ull".
3140 INFO [main] jdbc.SQL - [C: 2478770; T: 15336018]close
3187 INFO [main] jdbc.SQL - [C: 7529545; T: 15336018]open:
jdbc:mysql://localh
ost/kirjakauppa (root)
3193 INFO [main] jdbc.Schema - Found existing table "Kirjoittaja" for
schema "
null".
3225 INFO [main] jdbc.SQL - [C: 7529545; T: 15336018]close
Exception in thread "main" javax.jdo.JDOFatalInternalException:
java.lang.Illega
lArgumentException: You are attempting to link to a primary key column in
table "Kirja" in a foreign key that is already linked to primary key
columns in table "Kirjailija".
NestedThrowables:
java.lang.IllegalArgumentException: You are attempting to link to a primary
key column in table "Kirja" in a foreign key that is already linked to
primary key c
olumns in table "Kirjailija".
at
com.solarmetric.rd.kodo.impl.jdbc.meta.Mappings.createClassMapping(Ma
ppings.java:160)
at
com.solarmetric.rd.kodo.impl.jdbc.meta.MappingRepository.getMapping(M
appingRepository.java:279)
at
com.solarmetric.rd.kodo.impl.jdbc.meta.MappingRepository.getMetaData(
MappingRepository.java:147)
at
com.solarmetric.rd.kodo.impl.jdbc.meta.MappingRepository.getMapping(M
appingRepository.java:158)
at
com.solarmetric.rd.kodo.impl.jdbc.meta.compat.ImportTool.getMapping(I
mportTool.java:126)
at
com.solarmetric.rd.kodo.impl.jdbc.meta.compat.ImportTool.importMappin
gs(ImportTool.java:57)
at
com.solarmetric.rd.kodo.impl.jdbc.meta.compat.ImportTool.run(ImportTo
ol.java:408)
at
com.solarmetric.rd.kodo.impl.jdbc.meta.compat.ImportTool.main(ImportT
ool.java:385)
NestedThrowablesStackTrace:
java.lang.IllegalArgumentException: You are attempting to link to a primary
key column in table "Kirja" in a foreign key that is already linked to
primary key c
olumns in table "Kirjailija".
at
com.solarmetric.rd.kodo.impl.jdbc.schema.ForeignKey.join(ForeignKey.j
ava:238)
at
com.solarmetric.rd.kodo.impl.jdbc.schema.SchemaGenerator.generateFore
ignKeys(SchemaGenerator.java:625)
at
com.solarmetric.rd.kodo.impl.jdbc.schema.DynamicSchemaFactory.findTab
le(DynamicSchemaFactory.java:111)
at
com.solarmetric.rd.kodo.impl.jdbc.meta.map.BaseClassMapping.fromMappi
ngInfo(BaseClassMapping.java:113)
at
com.solarmetric.rd.kodo.impl.jdbc.meta.Mappings.createClassMapping(Ma
ppings.java:144)
at
com.solarmetric.rd.kodo.impl.jdbc.meta.MappingRepository.getMapping(M
appingRepository.java:279)
at
com.solarmetric.rd.kodo.impl.jdbc.meta.MappingRepository.getMetaData(
MappingRepository.java:147)
at
com.solarmetric.rd.kodo.impl.jdbc.meta.MappingRepository.getMapping(M
appingRepository.java:158)
at
com.solarmetric.rd.kodo.impl.jdbc.meta.compat.ImportTool.getMapping(I
mportTool.java:126)
at
com.solarmetric.rd.kodo.impl.jdbc.meta.compat.ImportTool.importMappin
gs(ImportTool.java:57)
at
com.solarmetric.rd.kodo.impl.jdbc.meta.compat.ImportTool.run(ImportTo
ol.java:408)
at
com.solarmetric.rd.kodo.impl.jdbc.meta.compat.ImportTool.main(ImportT
ool.java:385)
</clip>
Here's what MySQLCC gives for creation statement of the tables:
<clip>
# Host: localhost
# Database: kirjakauppa
# Table: 'Asiakas'
# CREATE TABLE `Asiakas` (
`Asiakas_id` int(11) NOT NULL auto_increment,
`Nimi1` varchar(50) default NULL,
`Nimi2` varchar(50) default NULL,
`KatuOsoite` varchar(50) default NULL,
`Postiosoite` varchar(50) default NULL,
`Email` varchar(50) default NULL,
`Puhelin` varchar(50) default NULL,
`Fax` varchar(50) default NULL,
`Salasana` varchar(50) default NULL,
`ExtranetTunnus` varchar(50) default NULL,
PRIMARY KEY (`Asiakas_id`),
KEY `Asiakas_id` (`Asiakas_id`)
) TYPE=InnoDB;
# Host: localhost
# Database: kirjakauppa
# Table: 'Kirja'
# CREATE TABLE `Kirja` (
`Kirja_id` int(11) NOT NULL auto_increment,
`Kustantaja_id` int(11) default NULL,
`Nimi` varchar(60) default NULL,
`Nimi2` varchar(60) default NULL,
`ISBN` varchar(50) default NULL,
`Kieli` varchar(50) default NULL,
`Kansi_URL` varchar(50) default NULL,
`Sisalto_URL` varchar(50) default NULL,
`Tukkuhinta` decimal(10,2) default NULL,
`Kuluttajahinta` decimal(10,2) default NULL,
`Varastokpl` int(11) default NULL,
PRIMARY KEY (`Kirja_id`),
KEY `Kirja_id` (`Kirja_id`),
KEY `Kustantaja_id` (`Kustantaja_id`),
FOREIGN KEY (`Kustantaja_id`) REFERENCES `kirjakauppa.Kustantaja`
(`Kustantaja_id`)
) TYPE=InnoDB;
# Host: localhost
# Database: kirjakauppa
# Table: 'Kirjailija'
# CREATE TABLE `Kirjailija` (
`Kirjailija_id` int(11) NOT NULL auto_increment,
`Sukunimi` varchar(50) default NULL,
`Etunimi` varchar(50) default NULL,
`Maa` varchar(50) default NULL,
`Kirjailija_URL` varchar(50) default NULL,
PRIMARY KEY (`Kirjailija_id`),
KEY `Kirjailija_id` (`Kirjailija_id`)
) TYPE=InnoDB;
# Host: localhost
# Database: kirjakauppa
# Table: 'Kirjoittaja'
# CREATE TABLE `Kirjoittaja` (
`Kirjoittaja_id` int(11) NOT NULL auto_increment,
`Kirjailija_id` int(11) NOT NULL default '0',
`Kirja_id` int(11) NOT NULL default '0',
PRIMARY KEY (`Kirjoittaja_id`),
KEY `Kirjailija_id` (`Kirjailija_id`),
KEY `Kirja_id` (`Kirja_id`),
FOREIGN KEY (`Kirjailija_id`) REFERENCES `kirjakauppa.Kirjailija`
(`Kirjailija_id`),
FOREIGN KEY (`Kirja_id`) REFERENCES `kirjakauppa.Kirja` (`Kirja_id`)
) TYPE=InnoDB;
# Host: localhost
# Database: kirjakauppa
# Table: 'Koodi'
# CREATE TABLE `Koodi` (
`Koodi_id` int(11) NOT NULL auto_increment,
`Koodi` varchar(50) default NULL,
`Tyyppi` varchar(50) default NULL,
`Arvo` varchar(50) default NULL,
PRIMARY KEY (`Koodi_id`)
) TYPE=InnoDB;
# Host: localhost
# Database: kirjakauppa
# Table: 'Kustantaja'
# CREATE TABLE `Kustantaja` (
`Kustantaja_id` int(11) NOT NULL auto_increment,
`Nimi` varchar(80) default NULL,
`Maa` varchar(50) default NULL,
`Kustantaja_URL` varchar(50) default NULL,
`KirjaLkm` int(11) default NULL,
PRIMARY KEY (`Kustantaja_id`),
KEY `Kustantaja_id` (`Kustantaja_id`)
) TYPE=InnoDB;
# Host: localhost
# Database: kirjakauppa
# Table: 'Luokittelu'
# CREATE TABLE `Luokittelu` (
`Luokittelu_id` int(11) NOT NULL auto_increment,
`Luokka_id` int(11) NOT NULL default '0',
`Kirja_id` int(11) NOT NULL default '0',
PRIMARY KEY (`Luokittelu_id`),
KEY `Luokka_id` (`Luokka_id`),
KEY `Kirja_id` (`Kirja_id`),
FOREIGN KEY (`Luokka_id`) REFERENCES `kirjakauppa.Luokka` (`Luokka_id`),
FOREIGN KEY (`Kirja_id`) REFERENCES `kirjakauppa.Kirja` (`Kirja_id`)
) TYPE=InnoDB;
# Host: localhost
# Database: kirjakauppa
# Table: 'Luokka'
# CREATE TABLE `Luokka` (
`Luokka_id` int(11) NOT NULL auto_increment,
`Luokka` varchar(50) default NULL,
PRIMARY KEY (`Luokka_id`),
KEY `Luokka_id` (`Luokka_id`)
) TYPE=InnoDB;
# Host: localhost
# Database: kirjakauppa
# Table: 'Myyja'
# CREATE TABLE `Myyja` (
`Myyja_id` int(11) NOT NULL auto_increment,
`Myyja` varchar(50) default NULL,
`Myyja_URL` varchar(50) default NULL,
PRIMARY KEY (`Myyja_id`),
KEY `Myyja_id` (`Myyja_id`)
) TYPE=InnoDB;
# Host: localhost
# Database: kirjakauppa
# Table: 'Tilaus'
# CREATE TABLE `Tilaus` (
`Tilaus_id` int(11) NOT NULL auto_increment,
`Asiakas_id` int(11) NOT NULL default '0',
`Myyja_id` int(11) default NULL,
`TilausPvm` timestamp(14) NOT NULL,
`EnsimmToimitusPvm` timestamp(14) NOT NULL,
`ViimToimitusPvm` timestamp(14) NOT NULL,
`Tila` int(11) NOT NULL default '0',
`Mk` decimal(10,2) default NULL,
PRIMARY KEY (`Tilaus_id`),
KEY `Asiakas_id` (`Asiakas_id`),
KEY `Myyja_id` (`Myyja_id`),
KEY `Tilaus_id` (`Tilaus_id`),
FOREIGN KEY (`Asiakas_id`) REFERENCES `kirjakauppa.Asiakas`
(`Asiakas_id`),
FOREIGN KEY (`Myyja_id`) REFERENCES `kirjakauppa.Myyja` (`Myyja_id`)
) TYPE=InnoDB;
# Host: localhost
# Database: kirjakauppa
# Table: 'Tilausrivi'
# CREATE TABLE `Tilausrivi` (
`TilausRivi_id` int(11) NOT NULL auto_increment,
`Tilaus_id` int(11) NOT NULL default '0',
`Kirja_id` int(11) NOT NULL default '0',
`TilausLkm` int(11) default NULL,
`Ahinta` decimal(10,2) default NULL,
`Alepros` float default NULL,
`Mk` decimal(10,2) default NULL,
`ToimitettuLkm` int(11) default NULL,
`ToimitusPvm` timestamp(14) NOT NULL,
`ViimToimitusPvm` timestamp(14) NOT NULL,
`Tila` int(11) NOT NULL default '0',
PRIMARY KEY (`TilausRivi_id`),
KEY `Tilaus_id` (`Tilaus_id`),
KEY `Kirja_id` (`Kirja_id`),
FOREIGN KEY (`Tilaus_id`) REFERENCES `kirjakauppa.Tilaus` (`Tilaus_id`),
FOREIGN KEY (`Kirja_id`) REFERENCES `kirjakauppa.Kirja` (`Kirja_id`)
) TYPE=InnoDB;
</clip>
I can find the original creation script if it is necessary.
My guess was that I need to define the foreign keys myself into the
generated schema.xml This is stated in the manual. However, this did not
help, although it changed the stack trace a little (it complains about
different classes than before):
<clip>
Exception in thread "main" javax.jdo.JDOFatalInternalException:
java.lang.IllegalArgumentException: You are attempting to link to a primary
key column in table "Myyja" in a foreign key that is already linked to
primary key columns in table "Asiakas".
NestedThrowables:
java.lang.IllegalArgumentException: You are attempting to link to a primary
key column in table "Myyja" in a foreign key that is already linked to
primary key columns in table "Asiakas".
at
com.solarmetric.rd.kodo.impl.jdbc.meta.Mappings.createFieldMapping(Mappings.java:208)
</clip>
I don't think I fully understand the error message, what exactly is wrong
here? How can I fix it?
Here's a sample of the changes I made to schema.xml:
- added the name - attribute to schema (it was missing)
<schema name="kirjakauppa">
- added the foreign key elements according to the table creation statements
given above
<fk name="Kustantaja_id" to-table="Kustantaja" column="Kustantaja_id"/>
etc...
-Antti

On Mon, 16 Jun 2003 17:55:35 -0500, Abe White <[email protected]>
wrote:
It seems the last three options are being ignored - I still get a
mapping
file with schema names in front of tables (e.g. kirjakauppa.Asiakas, not
Asiakas),That, unfortunately, is impossible to turn off. The -useSchemaName
option controls whether the schema name is included as part of the
generated class name; it doesn't affect the mapping data that is
generated. What problems does including the schema name in the mapping
data cause?
rd-importtool -properties jdo.properties gensrc/testi/testi.mapping0 INFO [main] kodo.MetaData - Parsing metadata resource
"file:/home/akaranta/work/kurssit/jdo/Harjoituskoodi/kirjakauppa/gensrc/testi/testi.mapping".
Exception in thread "main"
com.solarmetric.rd.kodo.meta.JDOMetaDataNotFoundException: No JDO metadata
was found for type "class testi.Asiakas".
FailedObject:class testi.Asiakas
at
com.solarmetric.rd.kodo.meta.JDOMetaDataRepositoryImpl.getMetaData(JDOMetaDataRepositoryImpl.java:126)
at
com.solarmetric.rd.kodo.impl.jdbc.meta.MappingRepository.getMetaData(MappingRepository.java:184)
at
com.solarmetric.rd.kodo.impl.jdbc.meta.MappingRepository.getMapping(MappingRepository.java:197)
at
com.solarmetric.rd.kodo.impl.jdbc.meta.compat.ImportTool.getMapping(ImportTool.java:128)
at
com.solarmetric.rd.kodo.impl.jdbc.meta.compat.ImportTool.importMappings(ImportTool.java:60)
at
com.solarmetric.rd.kodo.impl.jdbc.meta.compat.ImportTool.run(ImportTool.java:400)
at
com.solarmetric.rd.kodo.impl.jdbc.meta.compat.ImportTool.main(ImportTool.java:377)
This exception goes away if I edit the schema name out of the mapping
file from all classes.
separate classes are being generated for join tables with
primary keysDo these join tables have an extra primary key column? TheYes, they do. Ok, now I know where the problem is.
-primaryKeyOnJoin flag tells Kodo to ignore a join table with a primary
key on the join columns. But Kodo can't handle join tables with extra
column(s) just for a primary key identifier. This isn't a limitation of
the reverse mapping tool, it's a limitation of Kodo. Kodo wouldn't know
what to insert in those extra primary key column(s) when adding membersWhy not? If it can handle single numeric pk columns when making the
generated classes use data store identity, it has to generate something to
those columns. I can't see why this is different.
That is simply out of curiosity - the next thing fixed my problem:
to the join table. Of course, if the primary key is an auto-increment or
something where Kodo can ignore it for inserts, you can just remove the
<column> elements and the <pk> element from your .schema file and the
reverse mapping tool will map it as a join table appropriately.It is auto-increment, so I did this and it worked. Thanks.
, and application id is used for all classes.Are your primary keys on single, numeric columns? Kodo uses Java longsYes (int in MySQL), so that should not be a problem. They are also auto-
incremented. This seems to be the only real problem remaining with this
schema.
-Antti

Problem in Reversal of 57F4 Challan

Similar Messages

Maybe you are looking for