Error in MDM to SAPR3 scenario

Hi,
i am configuring a scenario where my sender is MDM 7.1 and receiver is SAPR3 system. i am getting a error as Configuration error: unknown for the MDM adapter which is sender. Kindly let me know what can be the issue. It will be of great help
Best Regards
Deepika
Edited by: Deepika Reddy on Jun 18, 2009 12:55 PM

Hi ,
How this scenario will get triggred , any transaction ? Here both are R/3 systems and MDM can process huge size of data or records.
Briefly explain the scenario
Regards,
B.Jude

Similar Messages

Communication Channel Error with MDM PI Adapter

Dear Experts,
We had new sever for PI(image copy). In new PI server we are facing problem only with MDM adapterin communication channel monitoring and below error occuring.
*" MDM Adapter listener could not start due to: Can not create repository session '<server=SAPMDMD serverUser=Admin repository=TTSL_Vendor_Dev user=Admin>' caused by: Connection Failed: Cannot create connection to MDM Server 'SAPMDMD' for one of the following reasons: (1) server does not exist, (2) server is not started, or (3) input/output problem while creating connection, error code: UnknownServer "
Any expert please help us to resolve this.
Thanks in advance.
Regards,
Hemu.

Hello Heymanth,
Make sure that connection is fine between systems. Test the RFC's in both systems. Also check the services too.
/people/harrison.holland5/blog/2006/12/20/xi-configuration-for-mdm-integration--sample-scenario
/people/ramesh.gulipalli2/blog/2009/11/16/sap-47-to-mdm-integration-using-pi71-part1
Regards
Pothana

Com.splwg.base. error in MDM 2.1 while starting weblogic server

Error in MDM 2.0 while trying to start the application. Would be great if someone can give any pointers.
2013-01-19 18:41:22,791 [SchedulerDaemon] ERROR (support.context.ComponentContainerLookupHelper*) Didn't find lookup class for interface interface com.splwg.base.api.lookup.TableClassificationLookup*
com.splwg.shared.common.LoggedException: Didn't find lookup class for interface interface com.splwg.base.api.lookup.TableClassificationLookup
     at com.splwg.shared.common.LoggedException.raised(LoggedException.java:67)
     at com.splwg.base.support.context.ComponentContainerLookupHelper.getLookupFor(ComponentContainerLookupHelper.java:104)
     at com.splwg.base.support.context.ComponentContainer.getLookupFor(ComponentContainer.java:457)
     at com.splwg.base.api.datatypes.LookupHelper.getLookupInstance(LookupHelper.java:23)
     at com.splwg.base.support.hibernatetypes.LookupType.nullSafeGet(LookupType.java:65)
     at org.hibernate.type.CustomType.nullSafeGet(CustomType.java:124)
     at org.hibernate.type.AbstractType.hydrate(AbstractType.java:106)
     at org.hibernate.persister.entity.AbstractEntityPersister.hydrate(AbstractEntityPersister.java:2701)
     at org.hibernate.loader.Loader.loadFromResultSet(Loader.java:1541)
     at org.hibernate.loader.Loader.instanceNotYetLoaded(Loader.java:1473)
     at org.hibernate.loader.Loader.getRow(Loader.java:1373)
     at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:640)
     at org.hibernate.loader.Loader.doQuery(Loader.java:850)
     at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:289)
     at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:259)
     at org.hibernate.loader.Loader.loadEntity(Loader.java:2042)
     at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:82)
     at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:72)
     at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:3710)
     at org.hibernate.event.internal.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:439)
     at org.hibernate.event.internal.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:420)
     at org.hibernate.event.internal.DefaultLoadEventListener.load(DefaultLoadEventListener.java:204)
     at org.hibernate.event.internal.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:251)
     at org.hibernate.event.internal.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:148)
     at org.hibernate.internal.SessionImpl.fireLoad(SessionImpl.java:992)
     at org.hibernate.internal.SessionImpl.access$1900(SessionImpl.java:170)
     at org.hibernate.internal.SessionImpl$IdentifierLoadAccessImpl.load(SessionImpl.java:2336)
     at org.hibernate.internal.SessionImpl.get(SessionImpl.java:888)
     at com.splwg.base.support.context.FrameworkSession.get(FrameworkSession.java:1045)
     at com.splwg.base.api.datatypes.SingleFieldId.getEntity(SingleFieldId.java:182)
     at com.splwg.base.api.EntityToTableHelper.privateGetTableForEntityName(EntityToTableHelper.java:66)
     at com.splwg.base.api.EntityToTableHelper.getTableForEntityName(EntityToTableHelper.java:50)
     at com.splwg.base.support.changehandlers.CobolExtensionChangeHandler.getExitProgramName(CobolExtensionChangeHandler.java:137)
     at com.splwg.base.support.changehandlers.CobolExtensionChangeHandler$1.execute(CobolExtensionChangeHandler.java:129)
     at com.splwg.base.support.changehandlers.CobolExtensionChangeHandler$1.execute(CobolExtensionChangeHandler.java:126)
     at com.splwg.base.support.context.SessionExecutable.doInCurrentSession(SessionExecutable.java:174)
     at com.splwg.base.support.context.SessionExecutable.doAsReadOnlyInCurrentSessionIfAvailable(SessionExecutable.java:97)
     at com.splwg.base.support.context.SessionExecutable.doAsReadOnlyInCurrentSessionIfAvailable(SessionExecutable.java:86)
     at com.splwg.base.support.changehandlers.CobolExtensionChangeHandler.hasUserExits(CobolExtensionChangeHandler.java:133)
     at com.splwg.base.support.context.ContainerRegisteredEntityData.getChangeHandlerWrappers(ContainerRegisteredEntityData.java:250)
     at com.splwg.base.support.changehandlers.HandlerPrepareMethodRunner.fireForAllHandlers(HandlerPrepareMethodRunner.java:36)
     at com.splwg.base.support.api.AbstractBusinessEntity.performPrepareAddOrChange(AbstractBusinessEntity.java:311)
     at com.splwg.base.support.api.AbstractBusinessEntity.privateSetAbstractDTOValuesMiddle(AbstractBusinessEntity.java:341)
     at com.splwg.base.domain.batch.batchJobQueue.BatchJobQueue_Per.setAbstractDTOValues(BatchJobQueue_Per.java:511)
     at com.splwg.base.support.api.JavaPersistenceStrategy.updatePersistentBackendForAdd(JavaPersistenceStrategy.java:58)
     at com.splwg.base.support.context.FrameworkSession.createBusinessEntity(FrameworkSession.java:1453)
     at com.splwg.base.support.impl.AbstractDataTransferObject$1.run(AbstractDataTransferObject.java:78)
     at com.splwg.base.support.impl.AbstractDataTransferObject$JumpFromDTORunner.run(AbstractDataTransferObject.java:172)
     at com.splwg.base.support.interception.SessionInterceptionManager.notifyGenericCallStackJump(SessionInterceptionManager.java:293)
     at com.splwg.base.support.context.FrameworkSession.notifyGenericCallStackJump(FrameworkSession.java:2074)
     at com.splwg.base.support.impl.AbstractDataTransferObject.abstractNewEntity(AbstractDataTransferObject.java:84)
     at com.splwg.base.domain.batch.batchJobQueue.BatchJobQueue_DTO.newEntity(BatchJobQueue_DTO.java:389)
     at com.splwg.base.support.batch.TimerBatchJobSchedulerIteration$2.execute(TimerBatchJobSchedulerIteration.java:192)
     at com.splwg.base.support.batch.TimerBatchJobSchedulerIteration$2.execute(TimerBatchJobSchedulerIteration.java:185)
     at com.splwg.base.support.context.SessionExecutable.doInNewSession(SessionExecutable.java:65)
     at com.splwg.base.support.batch.TimerBatchJobSchedulerIteration.addRunInNewSession(TimerBatchJobSchedulerIteration.java:185)
     at com.splwg.base.support.batch.TimerBatchJobSchedulerIteration.scheduleRun(TimerBatchJobSchedulerIteration.java:175)
     at com.splwg.base.support.batch.TimerBatchJobSchedulerIteration.monitorTimer(TimerBatchJobSchedulerIteration.java:78)
     at com.splwg.base.support.batch.TimerBatchJobSchedulerIteration.access$100(TimerBatchJobSchedulerIteration.java:37)
     at com.splwg.base.support.batch.TimerBatchJobSchedulerIteration$1.execute(TimerBatchJobSchedulerIteration.java:56)
     at com.splwg.base.support.batch.TimerBatchJobSchedulerIteration$1.execute(TimerBatchJobSchedulerIteration.java:52)
     at com.splwg.base.support.context.SessionExecutable.doInReadOnlySession(SessionExecutable.java:149)
     at com.splwg.base.support.context.SessionExecutable.doAsReadOnlyInCurrentSessionIfAvailable(SessionExecutable.java:99)
     at com.splwg.base.support.context.SessionExecutable.doAsReadOnlyInCurrentSessionIfAvailable(SessionExecutable.java:86)
     at com.splwg.base.support.batch.TimerBatchJobSchedulerIteration.privateExecute(TimerBatchJobSchedulerIteration.java:52)
     at com.splwg.base.support.batch.TimerBatchJobSchedulerIteration.execute(TimerBatchJobSchedulerIteration.java:48)
     at com.splwg.base.support.cluster.SchedulerDaemon.run(SchedulerDaemon.java:47)
Edited by: 982930 on Jan 19, 2013 7:09 PM

Did you get an answer or not yet? if not then try doing artifact gen

Error in mapping program in scenario

Hi all,
here i am facing an issue which is to be fixed very urgently. please help me masters.
here i am having a single source structure and multiple receiver structures. after confirming many sources i finally started my work with the help of this blog.
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
But now i am facing a problem that my mapping program and interface mapping are executing the file successfully when i tested in the test tab of both of them.
When i tried to test my scenario in TOOLS-----TEST CONFIGURATION . there it is showing error in the interface determination/mapping step.
here on the receiver side we are going to use proxies. for that we used XI adapter.
please check the above blog and let me know whether my total procedure is perfect or not
THANKS in advance to all .
HELPFUL ANSWERS WILL BE REWARDED.

Hi Ramana !
Could you take a screenshot of your error and put it in www.imageshack.us, then give us the link to see exactly which error are you getting. Please expand the node of the error message.
Does the scenario works actually?? I've noticed some cases where the test tool gives errors but once the scenario is running everything works fine.
Regards,
Matias
Message was edited by:
Matias Denker

SRM-MDM Catalog - XI Scenario

Hi,
I am working on SRM-MDM Catlog 1.0 integration with XI.
I have to configure scenarios in XI for:
1) Upload of Supplier catalog via Server File System to SAP MDM catalog. for example in XML Format.
2) Replication of Product and COntract data.
We have to use SRM_MDM_CATALOG scenario contained within XI Content uploaded for SRM_MDM.
=>I already have uploaded the XI Integration Content in Integration repository (SRM_MDM_CATALOG).
=>I already have SRM-MDM 1.0 catalog Configuration guide, But it doesnot detail much about scenario(components involved in Integration Repository and Integration Directory)
Do anyone have some document which details about scenario or any help material regarding the same/or if some expert can Guide/Brief me on the scenario.
Thanks and Regards,
Vijay Raheja

Hi,
Please see the below link
/people/harrison.holland5/blog/2006/12/20/xi-configuration-for-mdm-integration--sample-scenario
Regards
Chilla..

FSCT - Having Error "There were errors during running WordFileClose.dll scenario" when running the FSCT in controller & non-windows file server

I encounter 2 errors in the controller when running FSCT.
- "There were errors during running WordFileClose.dll scenario"
- "There were errors during running WordFileClose.dll scenario"
Does anyone has any ideas for this errors?
I am using the following server to run the FSCT:
- AD Server: Windows 2008 R2 SP1 x64
- FSCT Controller: Windows 2008 R2 SP1 x64
- Client: Windows 7 x64
- File Server: Non-Windows Server (EMC Isilon)
And the commands are as follows:
> fsct prepare dc /users 10 /clients testing /password password
> fsct prepare controller
> fsct prepare client /server ofscluster /password password /users 10 /domain abc.local /server_ip 192.168.2.16
> fsct prepare server /clients testing /password password /users 10 /domain abc.local /volumes \\ofscluster\fsroot1 /workload HomeFolders /create_only_fileset
> fsct run client /controller fsctcon /server ofscluster /password password /domain abc.local
fsct run controller /server ofscluster /password password /volumes \\ofscluster\fsroot1 /clients testing /min_users 2 /max_users 10 /step 2 /duration 360 /workload HomeFolders

Dear all,
The errors were:
<Error>1264 DeviceIoControl 1{WINERR}</Error>
<Error>Error executing scenario: WordFileOpen.dll</Error>
<Error>943 DeviceIoControl 50{WINERR}</Error>
<Error>Error executing scenario: WordFileClose.dll</Error>
Do you have any idea about what the errors mean?
Thanks,
Rayson

SRM -MDM in classic scenario

Hi,
Please let me know if am using SRM MDM in classic scenario then
u2022If I create a shopping cart in SRM do I need to maintain the product category of the items selected from MDM in SRM as well.
u2022Also, if PO is created in MM then does it mean that all the products in MDM have to be created in MM as well. If not then what is the scenario like.
Thanks,
Manu
Edited by: Manu Agrawal on Apr 24, 2009 12:15 PM

Hi
If my understanding is correct ,i will reproduce your question again . If you create shopping cart from the supplier catalogue in a classic scenario how the Material group sync happens when PO is created in the Back end R/3.
My assumption and the practice followed generally is that a Fixed Material group is decided and automatically maintained via OCI interface when shopping cart is created .Which means we define the rule for all catalogue items to determine and populate respective material group automatically into shopping cart.
As shopping cart is created since for the catalogue items there will be contract and source assigned in the ERP ,as soon as PR is replicated to R/3 as per classic scenario , the PR will have supplier assignment and if you run auto order transaction code system will generate PO in R/3 and sent to the supplier based on the condition records.
For the Material group you will configure it in R/3 for all catalogue items and replicate it in SRM and also you will provide input for the BADI or FM which create shopping cart automatically from catalogue through OCI method.
Hope this helps..
regards
Narahari

Error after unarchive process - Error: The MDM respository is invalid

Hi Experts:
We are on the process to unarchive a repository, but we are getting this error when trying to logon to load it.
Repository connect failed
Error: The MDM repository is invalid
p.s. We are trying to copy our Production environment to our Test Environment.
Thanks,
Claudia Hardeman

Hi Claudia,
I have been across this scene many times the easiest and fastest way to get rid of this problem is -
1) Delete the repository from Database
Step 1 u2013 Connect to the Database using the Database Management tool
Step 2 u2013 Delete the databases - RepositoryName_z000 and RepositoryName_m000
Step 3 u2013 Delete repository specific entry from the table A2i_Catalogs in A2i_xCat_DBs database
2) Unarchive the repository from old archive
3) Load the repository
This will solve the issue.
Regards.

Error mounting MDM Server

Hi,
Error mounting MDM Server
We are unable to mount the MDM server, the error message saying
(The specified SAP instance does not exist on server mdm-sr)
mdm-sr : hostname of mdm server
FYI: The mdm server and mdm console running on the same host .
Thanks
Faris

Hi Deep,
restarted both DB and then MDM server, but still not working, giving same error message
(Error mounting MDM Server, The specified SAP instance does not exist on server mdm-srv)
FYI: The mdm server and mdm console running on the same host .
But the DB instance is runing on the diffrent server
Tx,
FSS

Error in Idoc-XI-File scenario

dear all,
i am doing one Idoc to Xi and then to a flat file scenario. i have created one BS of type 3rd party for receiver and ont BS of type Web as ABAP. Then I created one namespace and import the Idoc type there. I have not created any DT, MT, MI, MM. I have created one interface Mapping where both sender & receiver has same structure & I have selected there mapping type of ABAP-Class with one Z program name.
Then, in ID, I created two CC channel one as receiver of File type & second sender as Idoc type.
Now, the thing is tht I am not able to get the file at the receiver end. Can anybody help me tht where I am doing an error?
Warm Rgards,
N.Jain

Then, in ID, I created two CC channel one as receiver of File type & second sender as Idoc type. 
>>
you dont need a Sender IDoc channel to be configured.
Now, the thing is tht I am not able to get the file at the receiver end. Can anybody help me tht where I am doing an error?
>>>
1. what does it say in SXMB_MONI ? Has the IDoc come into XI ?
2. In communication channel monitoring what is the error for the recv. file adapter

Error in IDOC-XI-IDOC scenario

Hi folks,
Let me explain the issue. This is an IDOC-XI-IDOC scenario. No BPMs involved. SAX parsing used to parse the IDOCs.
We had around 35000 IDOCs coming in from Brazil system, and they are all stuck in SMQ2 (Inbound queue) in XI. The first message of every queue is in SYSFAIL status, with the status text as Problems found during the EXPORT to specified keyin table.
When I try to execute the queue manually, nothing happens, but an error comes at the bottom of the screen, saying Function module does not exist or EXCEPTION raised.
I checked the dump on ST22, and it shows 130 runtime errors yesterday. The name of the runtime error is EXPORT_TABLE_UPDATE_CONFLICT.
In the what happened? part of the dump, it says Error in ABAP application program. The current ABAP program CL_XMS_PERSIST=============CP had to be terminated because one of the statements could not be executed. This is probably due to an error in the ABAP program.
Even SXMB_MONI is not opening (for yesterdays date). When I try to open it, it hangs for a long time, and finally opens an ABAP Runtime Errors page with the runtime error titled as SNAP_NO_NEW_ENTRY and the error short text as Runtime error: Unable to write short dump
Please advise.Thanks a ton!
cheers,
Prashanth

Hello Prashanth,
First of all this is an XI issue and belongs in that forum.
The export problem is typical to situations where your XI DB is out of space/out of table space. Please check with your Basis team.
Function module does not exist or EXCEPTION raised- This message is a standard ABAP RFC message. For an RFC function call to succeed, you need the same RFC function to exist on both systems. However this is probably not the case- it is more likely that you're out of DB space as I already wrote.
Good Luck (don't forget to award points)
Ofer

How to suppress the Acknowledgement Error in IDOC to File scenario?

Hi -
I got the status in SXMB_MONI as 'Processed Successfully' for the IDOC to File scenario but the Acknoledgement status throws an error saying 'Acknowledgement not possible'.
I read one of the documents in the forums on how to suppress the acknowledgement using a table on R/3 side using IDXNOALE,
i tried that option but i still get the 'Acknowledgement not possible' error.
Is there any other way to suppress this error?
Thanks,
Tirumal

Hi Tirumal,
Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender. Acknowledgements are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments. The RNIF and CIDX adapters are exceptions to this rule, since they also support scenario-dependent application acknowledgments. Sender adapters of the Adapter Engine do not request any acknowledgments.
This means, JDBC adapter does only send system acks, however IDoc adapter is requesting application acks. Therefore as mentioned by the previous poster, you have to disable acks for this scenario using report IDX_NOALE.
Also go through these documents for any further help:
http://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how to handle acknowledgments for idoc.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
Regards,
abhy

Error in HTTP to file scenario

Hey guys
we have a HTTP to file scenario in which our client has to send the Invoices over HTTP in XML format,when we test the scenario from within our landscape we are getting the output file correctly but when we test from the client site,we get an error message saying that the file has missing semi colon (,the URL which we are getting from the local HTTP client is something like this
http://scosap005.sap.com:8001/sap/xi/adapter_plain?namespace=urn%3ANOVInvoiceToSCO&interface=MI_Invoice_sender&service=BS_test_invo&party=&agency=&scheme=&QOS=EO&queueid=httpclient&sap-user=&sap-password=&sap-client=100&sap-language=EN
and the one which we are getting from the client is
http://xx.xxx.xx.xx:8001/sap/xi/adapter_plain?namespace=urn%3ANOVInvoiceToSCO&interface=MI_Invoice_sender&service=BS_test_invo&party=&agency=&scheme=&QOS=EO&queueid=httpclient&sap-user=&sap-password=&sap-client=100&sap-language=EN
why am i getting this error?
thanx
ahmad

Hey guys
i m having a very strange problem with my scenario,we are doing a HTTP to file scenario,now as both the sender and receiver have same structure i havent done any mapping,client is sending XML over HTTP from another location which is not in our landscape,he is using web methods Business connector .when he send us the XML message to our XI server some stuffs are added at the top of the payload,its something like this
namespace=urn%253ANOVInvoiceToSCO&interface=MI_Invoice_sender&service=BS_test_invo&party=&agency=&scheme=&QOS=EO&queueid=httpclient&sap-user=nov_test&sap-password=xi_test&sap-client=100&sap-language=EN&
these are actually the parameters which are used in the URL to send the XML to us.but because of this i m unable to process the XML .
so my XML looks something like this
namespace=urn%253ANOVInvoiceToSCO&interface=MI_Invoice_sender&service=BS_test_invo&party=&agency=&scheme=&QOS=EO&queueid=httpclient&sap-user=nov_test&sap-password=xi_test&sap-client=100&sap-language=EN&
<?xml version="1.0" encoding="UTF-8"?>
<Invoice transactionPurposeIndicator="Original">
 <InvoiceProperties>
 <InvoiceNumber>0094372098</InvoiceNumber>
 <InvoiceDate>20070319</InvoiceDate>
 <VendorNumber>VENDOR #</VendorNumber>
but when i try this scenario from within our landscape it works fine and nothing is added on top of XML.
they are sayin that nothin extra is being added from thr side and their XML does not have the extra addition on top.
how should i solve dis problem?
its urgent
thanx
ahmad

Error in File to IDOC Scenario

Hi,
I have File to IDOC scenario.
I am getting error in sender file channel.
"Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
Despite of this error in sender channel I am receiving the message in XI.
But in XI also it throws error :
"Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
Any help on this ?
Thanks,
Vikas

Hello Vikas,
I am getting error in sender file channel.
"Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
Check your flat file structure whether the key field you have chosen is appropriate and also recheck the FCC details whether you have assigned the value for the key field i.e. keyFieldValue.
"Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
regarding the above error refer this
https://wiki.sdn.sap.com/wiki/display/XI/Unable%20to%20convert%20Sender%20system%20to%20ALE%20logical%20system
Regards,
Prasanna

Error in File to File scenario

Hi All,
im trying out the file to file scenario [binary file using file content conversion]from SDN Wiki:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/main&
On the runtime workbench, adapter engine is in red/error status due to error in the receiver comunication channel.
The sender communication channel is working fine. During testing, my file is being picked up and deleted(processing mode set to delete).
I am able to see the msgs in sxmb_moni and in Message Monitoring, the status is delivered.
However, the receiver channel does not show any error msgs at all.
Yday when i tested , i got the foll error msg:
Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter 'EMP.Contacts.fieldFixedLengths' or 'EMP.Contacts.fieldSeparator' is missing
However tdy i dont see any new error msgs during testing (no changes made to the recvr channel).
Given that the sender communication channel is wrking, can i safely assume that file adapter is wrking fine. If not, how do i check the status of the file adapter [in RWB, i can see the file adapter and various other adapters(with a grey diamond icon next to them). how do i interpret the status of the adapter?
Would really appreciate if anyone can advice on how to troubleshoot this?
Many thanx!
cheers
Prachi
I hv tried doing a full cpa cache refresh.

Hello Prachi ,
I thinks its because of receiver File Processing Parameters,as you are considering here File Content Conversion.
If your structure is like this
<?xml version="1.0" encoding="UTF-8"?>
<ns1:Proveedor_100011 xmlns:ns1="http://sap.com/xi/webservices/buyordint">
<config>
<directory>c:/tmp</directory>
<filename>dynamicFile3.txt</filename>
</config>
<root>
<string>Header;423423</string>
<lines>
<value>LINE;</value>
</lines>
</root>
</ns1:Proveedor_100011>
Then your content conversion is -
RecordSet Structure: config,root
root.fieldSeparator = ;
root.endSeparator = 'nl'
config.fieldFixedLenghts = 0
config.fixedLenghtTooShortHandling = CUT
http://help.sap.com/saphelp_nw2004s/helpdata/en/d2/bab440c97f3716e10000000a155106/frameset.htm
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
With Regards,
Raju.
Please give points if useful.....

Error in MDM to SAPR3 scenario

Similar Messages

Maybe you are looking for