Follow on Document details not correct

Hello Experts,
We are in SRM 4.0 Classic
One Shopping Cart has been created with 1Goods and 7 Service line items....
PR has been created in backend...... (we see generally SC line item 1,2,3.... follow sequece 10,20,30 in PR, But here this order is shuffled.... though all the SC and PR line item details are correct)
Now for SC line item 2, 'follow on document' tab shows details of PR line item 40 and vice versa.... which is incorrect....
Except these two SC line items, all other SC items shows correct PR line item details in follow on document
Can anyone advise on such system behaviour? Is thr any way to fix this?
Thanks,
Dhananjay

Hi,
Did you delete some line items and again added them in your SC? Are you using cost distribution in your SC?
Regards,
Nikhil

Similar Messages

Follow on document details not updating in shopping cart

Hi Experts,
I created a shopping cart and created PO as a follow on document from sourcing cockpit after assigning vendor.
but Shopping cart is not updating with follow on document (PO)details even after running BBP_GET_STATUS_2 report also.
Is there any other settings required to do for updating shopping cart with follow on document details.
Thanks,
Bhaskar.

Hi ,
Please check the repots ( jobs ) CLEAN_REQREQ_UP And BBP_GET_STATUS _2 are running..
Check in RZ20 is there any error message for the follow on document.
Thanks
prasad.s

Follow-on documents are not visible in MIRO in TEST server, awsys = PRD300.

Dear Experts ,
The Test Server was refreshed around mid-June 2011 with data of
Production Server. The follow-on documents are not visible for the
invoice documents in MIRO in TEST server due to value in tables
BKPF,RBKP : field : AWSYS = PRD300 .
The newly created Purchase Orders after the refresh, the accounting
documents can be seen for the Goods Receipt (MIGO_GR-display) and
Invoice documents (MIRO).
we had already raised this issue in March & got the feedback from SAP
as shown below.
accordingly we have developed & run the program "zzlogsys2" which
updates the Logsys/Awsys field from PRD300 ( of production server ) to
that of the current server i.e. TST300 as required.
after which the FI documents for the material documents are visible in
MIGO,but follow-on documents are not visible for the invoice documents
in MIRO.
we have Checked notes 781498 and 28958 to see if the logical system is
correctly assigned , where we found that in table RBKP after entering document number, Fiscal Year , the
Field AWSYS is "PRD300" & not "TST300" as it should be. We will take up the activity of updating table RBKP
also as we are currently doing for tables MKPF & BKPF.
But to have clear picture as to what we are doing is correct , pl
advise about the following :
1) Is it a correct process done by our SAP-Basis team , that every time
any Server ( e.g. Test or Quality ) is refreshed with Production server
data, the Field AWSYS in various transaction tables gets value as
"PRD300" which then is required to replaced by running program such as
ZZlogsys.
REPORT ZZLOGSYS.
TABLES: T000, MKPF.
DATA: NEW_SYS LIKE MKPF-AWSYS.
PARAMETER: OLD_SYS LIKE MKPF-AWSYS.
SELECT SINGLE * FROM T000 WHERE MANDT EQ SY-MANDT.
NEW_SYS = T000-LOGSYS.
CHECK NOT NEW_SYS IS INITIAL.
UPDATE MKPF SET AWSYS = NEW_SYS
WHERE AWSYS = OLD_SYS.
WRITE:/ 'Number of updates: ', SY-DBCNT.
2) if the above process is correct & normal , then which are the other
tables in a particular server ,apart from tables MKPF,BKPF,RBKP , which
needs to be updated the value of field "AWSYS" in the same way
replacing value "PRD300".
3) if the process in point no. 1 is not correct , then what is the
correct process that the Basis team can do while refreshing any target
server with production data so that target server retains its value in
Field AWSYS & not showing "PRD300".
With 3 servers TEST,DEV & Quality , recently refreshed with production
server to bring all servers in Sync for a HR patch application, we have
this situation now in all 3 servers .
Thanks in advance ,
Anil Shanbhag

It is appropriate to move this thread from ERP-MM to [Enterprise Resource Planning (ERP)|Enterprise Resource Planning (SAP ERP);
Edited by: Jeyakanthan A on Jul 7, 2011 4:56 PM

SC Item in Transfer process active - follow on document status not updated

Hi Gurus,
    Follow on document is not updated in SRM after PO creation. Ours is classic scenario (SRM 5.5, ECC6.0) and passed thru the following steps - SC (FFT) created, document approved, sent to SoCo, purchaser assigned vendor and created PO, PO created in ECC.
In SRM SoCo screen displays message 'PO created 45xxxxxxxxxx' successfully. Checked the BE PO 45xxxxxxx that was created successfully.
Ran BBP_GET_STATUS_2 and CLEAN_REQREQ_UP jobs. jobs finished successfully. But status is not updated in SRM. RZ20/SLG1 does not have any errors.
BBP_PD shows following statuses:
     I105   Awaiting Approval         X
     I1021 Created
     I1038 Complete
     I1106 SC ordered
     I1129 Approved
     I1111 Item in Transfer process
                    The last status I1111 is still active.
Any advise are welcome. Not sure if I am missing any OSS Notes.
Regards
Viktor Paul

Hi,
1. Check in table BBP_DOCUMENT_TAB if the entry exists use CLEAN_REQREQ_UP program.
2. If entry in the table not exists then check in transaction BBP_PD if the follow on document ( PO ) Number reserved for
the SC .. then use FM BBP_PD_SC_RESUBMIT.
3. none of these use normal process execute BBP_REQREQ_TRANSFER And then use CLEAN_REQREQ_UP
Thanks,
prasad.s

Item in Transfer Process - Follow on documents status not displayed

Hello experts,
User created a shopping cart of 12 line items (out of that no 3rd is deleted) and PO is created in backend r/3 system.
Now when i see the status of my last item ie 12th line item is "Item in Transfer Process". and for 3rd item which is deleted for that also Status shown PO NO (I1113) i can see that PO no is there when i check follow on document.Problem is i want to change the status of 12th line item with its respective PO no .
Activity done by me to solve
If i manually update the status in the table CRM_JEST then the status will get changed but the follow on document is not displayed evenafter run reports like CLEAN_REQREQ_UP and Get status2. i am trying to run a report BBP_ALERT_SB_NOTTRANSFERED but it got cancelled. even i tried to run a function module BBP_PD_SC_RESUBMIT but short dump will come. i have implemeted a suggested SAP note 729967 but still problem persist.
In BBP_PD and in table BBP_PDBEI field ( BE_OBJECT_ID ) in this field Ponumber is there against that line item.
Thanks
Sunny Sharma

Hi Sunny,
the manual action taken on the transfer is dangerous and can cause even more inconsistency.
Hence you may have changed some tables of the SC manually, I would suggest rather to delete SC items, and create a new SC for them.
Regards,
Peter

Vendor Invoices - Entered on and parked details not correct

Hi since we upgraded to ECC6 we have noticed that the dates stored in the Header of both LIV and Direct Entry invoices are not correct.
If we Park a invoice we have a the corrected Entered on and Entered By details is correct.
Then when the document is posted the entered on date and user name then changes to the date the invoice was posted on the system.
We need to be able to see when the document was originally put on the system as a parked document so we can determine how long it takes us to process them.
I have checked in bkpf and usname and ppnam is the same and nothing in sname.
I cant see any OSS notes to say this is a known problem. Does anyone know how to resolve this.
Thanks

Hi,
Unfortunately it is not that simple.
We need to use the vendor tax date in the document date so this cannot be used.
We could also do with storing the date we scanned the invoice to workflow but there is no spare fields for this either.
Thanks

Now and Next details not correct

Seems that my box updated a couple of weeks ago and since then the now and next function doesn't work properly.
Often the display states "No Info" or displays the incorrect time and program for what is actually being shown on the channel.
Anyone else experiencing issues?

I've noticed that as well in the last few days. It is usually slow to complete the info when changing channel and sometimes displays info that is just plain wrong. I wonder if it's a fault with the 7.1.7 version of the software?
I also noticed that a few times I had paused a live program and then left it paused until after the program ended. Pressing info then gave no info at all. The box had got confused and given up. Not sure if it does that every time.

Document is not relevant for billing

Dear All,
We are implementing ECC 6 in one of our client.
Our client manufacturer of x finished product, they want monitor the production process through Project system and deliver should be through project system,
We did the complete configuration from Production order till delivery in PS is working fine.
But when we try to post billing document from the delivery document, the system is showing the following error,
Document is not relevant for billing: LP is not relevant for F2.
Our doubt is in this process, whether excise invoice will be generated or not?
this LP is hard coded in SAP, We are unable to rectify the error,
our GO-LIVE date is 1st March
can any one help us to solve this issue?
Thanks in advance
regards
Elango

LP is not relevant for F2
What is LP ?? Is it Delivery type or Item Category ?? Nevertheless, copy control is missing in VTFL.
whether excise invoice will be generated or not?
If physical material movement is there from a manufacturing plant to outside, then definitely, you should generate an excise invoice
thanks
G. Lakshmipathi

Error creating follow on documents for Shopping cart

Hi expert
we are on srm 701
and we are using classic scenario
We are currently facing an issue with follow-on documents are not created in R/3
i Define Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders)
when my manger approve Sc i havent any follow on doc in my back-end and i have this error in RZ20 :Shopping cart 0010000376: Error creating the follow-on document
but when is using FM : BBP_PD_SC_TRANSFER the reservation created (for which material that define on Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders as created reserve)
but i cant create PO or PR
Please help to resolve this issue.

Hello,
check this section:
Shopping Cart Transfer
Regards.
Laurent.

List of PO's with no follow on documents

Hi all,
Is there any FM which gives the list of PO's for which the follow on documents are not created.?

Hi,
I am not aware of FM. But I know the tables which can give the required inforamtion to you.
Pass item GUID of RFx response to CRM_JEST-OBJNR. If it has a record with STAT=I1113 then it means that the follow on document created.
Further you can find the meaning of status in CRM_JEST, in TJ02T table.
Hope it will help you.
GH

I1112 status of Shopping cart- Need to create a follow on document

Hello Experts,
I have one issue in which enduser had created a shopping cart and header status is approved but no follow on document is generated. at line item level the status is Error in Process.
When i ran the report BBP_ALERT_SB_NOTTRANSFERED. then my Shopping cart status changed from I1111(item in transfer) to I1112"error in transmission'..
In Applicaiton monitor : the message is Not transferred to backend and Shopping cart 3100001911: Follow-on document(s) not transferred. we are using Extended Classic Scenario and i dont know why we are getting this issue, we are getting this same issue only for 2 Shopping carts.
Please guide me how i can repost the document so that follow on document will get generated.
I am in ECS scenario with SRM 7.0
Help will be appriciated.
smriti

Hi,
If it is only the problem with only few carts, Check if any Short dumps are occuring in SRM as Well as in R/3.
We faced a simialr situation and observed that it was resulting in a short dump due to bad coding in one BADI.
regards,
MRao

Error: Document could not be found...

The last four documents that we have sent to individuals for signatures through Adobe eSignatures have encountered the following issue:
"Document could not be found because of one of the following reasons:
* Document was rejected by one of signatories
* Document was cancelled by initiator
* Document was deleted by initiator
* Document has expired".
The document still remains in the Awaiting Signature tab and has not been rejected, cancelled, deleted or expired by any of the signatories or initiator. When an attempt is made to cancel the document and re-send, the same error occurs. Is there any way to troubleshoot this error?

Hello PW, I am having this problem and all suggestions haven't worked yet. Where is the Preferences|Documents you are referring to? I am on a PC and using Windows.
EDIT: I found it and did, but still not working.

IPhone/iTouch "password not correct" on home WiFi

This problem reads like many others threads but I haven't really seen an answer - Do Apple Employees Administrate these forums??
I have an iTouch and an iPhone 3Gs both now on os4 but this prob has happened through last 3 firmware versions.
They both connect to the home WiFi, but wont remain connected and will ask for the WiFi Password followed by a Password Not Correct message. You can continue to input the password and occasionally it is accepted or you can power cycle the router but both are temp fixes as the Apple's will drop back off again (sometimes minutes later or hours later). I have exhausted my efforts with the router (firmware upgrades and every combination of security setting) Other devices (laptop, wii etc)don't have any WiFi issues. In saying that, the iPhone stays connected to the work WiFi no problems.
I have tried WEP and WPA security. I've enabled MAC Address filtering which didn't help but after reading one of the threads I have disabled WiFi security and have MAC Address filtering enabled and it seems to be holding up (only attempted a couple of hours ago.) Is this a secure workaround or does someone know what I need to do? I'd prefer not to use this method as it's handy to let visiting friends/family use my WiFi.
The router is a Linksys WRT54GP2 and the signal level is high throughout the house and always seen by the Apple's
Any help would be greatly appreciated! Thanks.
The iPad purchase is next if I can get an answer (a mate has brought his around and had the same problem) - so come on Apple employees, put your heads together!

Yeah you aren't the only one. I have the same router, and my iPod, dads iPhone, and 2 other apple macbooks always had troubles with the router. A temp fix would be restarting the router, but keyword here is temp.
Unfortuantely we cant use custom linux firmware as per http://www.dd-wrt.com/site/support/router-database
My router firmware version is
Firmware Version: 1.30.05
I recall I upgraded from version 1.00 ages back but that did nothing.
Anyway I shall try google around for more solutions, I'll get back to you if there is a fix.

My document did not convert correctly. Can I fix it in the PDF version?

My document did not save as it was originally written. Can I fix it once it has been changed to a PDF?

Hi iamreadytoscream,
Did you use PDF Pack to convert a file to PDF? What was the original file format? And, can you provide a little detail about what didn't convert correctly?
I think the best approach is to figure out why the file didn't convert correctly. You would need Acrobat to edit the PDF once it's created. And, as Acrobat isn't a word processor, it really isn't meant for major editing or formatting.
Please tell me a bit more about the file that you converted and we'll go from there.
Best,
Sara

Failed to retrieve a schema URI (document namespace) for /userprofiles/emailNotification.usr; please see the following exception for details

I get this exception (and long stack trace) when attempting to start my weblogic server. I'm running Weblogic 7 with Portal 7 (sp 1). I'm using Oracle 8.1.7. I upgraded this application from weblogic portal 4.0, and never had this problem there. As part of the migration process, I ran the tool to migrate all of the database tables, and I re-synched the EBCC project using version 7 of EBCC. I did a search for this problem and found a few mentions of it that seemed to be related to Oracle's handling of CLOB data. Apparently, there is a patch, but I can't seem to find this patch. I'm also not sure if this is indeed the problem since I didn't have this issue with the older version of weblogic using the same database. Any suggestions?

If you have a support contract please open a case so we can work through
this problem.
Can you run an sqlplus session on your database, execute the commands
"delete from data_sync_item" and "commit", then resync to see if it will
get you around the problem. The data_sync_item table will be fully
populated after you sync. This should get you running.
Between 4.0 and 7.0 the DefaultRequestPropertySet.req file was reduced
in size -- the CLOB would be smaller in the data_sync_item table.
I would recommend using the Version Checker against your installation --
find it on the dev2dev.bea.com site to see if the upgrade installer work
ed properly. Also consider running the full installer to avoid possible
problems that might occur with upgrade installers.
As a result of that patch you referenced in 4.0 the CLOB handling logic
was changed in 7.0 -- this is why it is strange you are seeing cleaving
errors. In 7.0 SP2 to be release next week the data sync and
persistence code was changed also.
Are you using the OCI or Thin driver?
-- Jim
Rob Goldie wrote:
Jim Litton <replyto@newsgroup> wrote:
Rob,
The CLOB issue was related to wlportal4.0 and should not be a factor
in
7.0.
Could you post the entire stack trace?
####<Jan 27, 2003 4:21:47 PM EST> <Warning> <Data Synchronization> <PFIDEV5> <pfeAricept1Server>
<main> <kernel identity> <> <000000> <Application: gmiAriceptApp; Failed to retrieve
a schema URI (document namespace) for /request/DefaultRequestPropertySet.req;
please see the following exception for details.>
Exception[com.bea.p13n.management.data.doc.DocumentProcessingException: Unable
to analyze and/or cleave document]
     at com.bea.p13n.management.data.doc.cleaver.CleavingDocumentProcessor.process(CleavingDocumentProcessor.java:94)
     at com.bea.p13n.management.data.repository.internal.DataItemImpl.getSchemaUri(DataItemImpl.java:136)
     at com.bea.p13n.management.data.repository.DataRepositoryFactory.createDataItem(DataRepositoryFactory.java:363)
     at com.bea.p13n.management.data.repository.persistence.JdbcDataSource.createDataItems(JdbcDataSource.java:523)
     at com.bea.p13n.management.data.repository.persistence.JdbcDataSource.refresh(JdbcDataSource.java:442)
     at com.bea.p13n.management.data.repository.persistence.ReadOnlyJdbcPersistenceManager.refresh(ReadOnlyJdbcPersistenceManager.java:107)
     at com.bea.p13n.management.data.repository.internal.AbstractDataRepository.<init>(AbstractDataRepository.java:193)
     at com.bea.p13n.management.data.repository.internal.MasterDataRepository.<init>(MasterDataRepository.java:46)
     at com.bea.p13n.management.data.repository.DataRepositoryFactory.getMasterDataRepository(DataRepositoryFactory.java:255)
     at com.bea.p13n.placeholder.internal.PlaceholderServiceImpl.ejbCreate(PlaceholderServiceImpl.java:191)
     at com.bea.p13n.placeholder.internal.PlaceholderServiceImpl_9p0jz2_Impl.ejbCreate(PlaceholderServiceImpl_9p0jz2_Impl.java:117)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.ejb20.pool.StatelessSessionPool.createBean(StatelessSessionPool.java:151)
     at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:188)
     at weblogic.ejb20.manager.StatelessManager.initializePool(StatelessManager.java:380)
     at weblogic.ejb20.deployer.EJBDeployer.initializePools(EJBDeployer.java:1472)
     at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:1367)
     at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:864)
     at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:81)
     at weblogic.j2ee.Application.addComponent(Application.java:294)
     at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:164)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:375)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:303)
     at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:256)
     at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:207)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:732)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:714)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:417)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
     at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:926)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:470)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:198)
     at $Proxy9.updateDeployments(Unknown Source)
     at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:4060)
     at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:2259)
     at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:373)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:235)
     at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:61)
     at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:806)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:295)
     at weblogic.Server.main(Server.java:32)
Caused by: org.xml.sax.SAXException: No message available. Resource not found:
repository.cleaver.no.xsi.namespace.exception Resource bundle: com/bea/p13n/management/data/datasync
     at com.bea.p13n.management.data.doc.cleaver.DocumentCleaver.mapNamespaces(DocumentCleaver.java:135)
     at com.bea.p13n.management.data.doc.cleaver.DocumentCleaver.startElement(DocumentCleaver.java:235)
     at weblogic.apache.xerces.parsers.SAXParser.startElement(SAXParser.java:1384)
     at weblogic.apache.xerces.validators.common.XMLValidator.callStartElement(XMLValidator.java:1299)
     at weblogic.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScanner.java:1821)
     at weblogic.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XMLDocumentScanner.java:964)
     at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:396)
     at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:1119)
     at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:135)
     at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:133)
     at com.bea.p13n.management.data.doc.cleaver.CleavingDocumentProcessor.process(CleavingDocumentProcessor.java:80)
     at com.bea.p13n.management.data.repository.internal.DataItemImpl.getSchemaUri(DataItemImpl.java:136)
     at com.bea.p13n.management.data.repository.DataRepositoryFactory.createDataItem(DataRepositoryFactory.java:363)
     at com.bea.p13n.management.data.repository.persistence.JdbcDataSource.createDataItems(JdbcDataSource.java:523)
     at com.bea.p13n.management.data.repository.persistence.JdbcDataSource.refresh(JdbcDataSource.java:442)
     at com.bea.p13n.management.data.repository.persistence.ReadOnlyJdbcPersistenceManager.refresh(ReadOnlyJdbcPersistenceManager.java:107)
     at com.bea.p13n.management.data.repository.internal.AbstractDataRepository.<init>(AbstractDataRepository.java:193)
     at com.bea.p13n.management.data.repository.internal.MasterDataRepository.<init>(MasterDataRepository.java:46)
     at com.bea.p13n.management.data.repository.DataRepositoryFactory.getMasterDataRepository(DataRepositoryFactory.java:255)
     at com.bea.p13n.placeholder.internal.PlaceholderServiceImpl.ejbCreate(PlaceholderServiceImpl.java:191)
     at com.bea.p13n.placeholder.internal.PlaceholderServiceImpl_9p0jz2_Impl.ejbCreate(PlaceholderServiceImpl_9p0jz2_Impl.java:117)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.ejb20.pool.StatelessSessionPool.createBean(StatelessSessionPool.java:151)
     at weblogic.ejb20.pool.Pool.createInitialBeans(Pool.java:188)
     at weblogic.ejb20.manager.StatelessManager.initializePool(StatelessManager.java:380)
     at weblogic.ejb20.deployer.EJBDeployer.initializePools(EJBDeployer.java:1472)
     at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:1367)
     at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:864)
     at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:81)
     at weblogic.j2ee.Application.addComponent(Application.java:294)
     at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:164)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:375)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:303)
     at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:256)
     at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:207)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:732)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:714)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:417)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
     at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:926)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:470)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:198)
     at $Proxy9.updateDeployments(Unknown Source)
     at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:4060)
     at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:2259)
     at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:373)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:235)
     at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:61)
     at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:806)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:295)
     at weblogic.Server.main(Server.java:32)
Are you using a UTF-8 Oracle database?
Yes
If you create a new User Profile in the EBCC and compare it to your
migrated .usr file do you see differences in the DTD's?
I recreated a new version of the .usr in the EBCC, and still got the same error.
I also tried deleting everything from the data-sync-item table and re-synching.
What does the DocumentManager section of your application-config.xml
look like?
<DocumentManager
ContentCacheName="documentContentCache"
ContentCaching="true"
DocumentConnectionPoolName="default"
MaxCachedContentSize="32768"
MetadataCacheName="documentMetadataCache"
MetadataCaching="true"
Name="default"
PropertyCase="none"
UserIdInCacheKey="false"
/>
What does the document.jar Targets="" parameter look like in config.xml?
<EJBComponent Name="document" Targets="pfeCluster" URI="document.jar"/>
-- Jim
Rob Goldie wrote:
I get this exception (and long stack trace) when attempting to start
my weblogic server. I'm running Weblogic 7 with Portal 7 (sp 1). I'm
using Oracle 8.1.7. I upgraded this application from weblogic portal
4.0, and never had this problem there. As part of the migration process,
I ran the tool to migrate all of the database tables, and I re-synched
the EBCC project using version 7 of EBCC. I did a search for this problem
and found a few mentions of it that seemed to be related to Oracle's
handling
of CLOB data. Apparently, there is a patch, but I can't seem to find
this patch. I'm also not sure if this is indeed the problem since I
didn't have this issue with the older version of weblogic using the
same database. Any suggestions?

Follow on Document details not correct

Similar Messages

Maybe you are looking for