MATMAS IDOC not creating required views

Hi
We have a scenario where an external system is sending material master data to ECC via PI. The msg type used is MATMAS03. The data gets processed successfully in ECC but does not create the basic data views. The inbound idoc has many fields which belong to basic data views, yet the views that have similar fields other than basic data get created. We have checked the configuration for screen sequencing (Industry standard sequence) and analysed the function module used for inbound processing of idocs. We did not find anything wrong with them. We see that the VPSTA and PSTAT maintenance fields get populated with all other views other than Basic data 1 and 2. This is automatically handled by SAP standard logic.
Does anybody have any idea what could be causing this? Any troubleshooting tips will help.
Thanks
Arvind

do you have a valid warehouse number and data for your warehouse in the IDOC?

Similar Messages

"Could not create the view" error

Hey everyone,
I'm new to Flash Builder and have been following a tutorial video to learn the basics. Today, when I tried to access my project, this error appeared in the Package Explorer:
Could not create the view: Plug-in "com.adobe.flexbuilder.as.editor" was unable to instantiate class "com.adobe.flexbuilder.as.editor.ui.packageexplorer.FlexPackageExplorer".
I also can't seem to create a new Flex project. If I try to, I can never click Finish. The button just remains faded out.
Below are the details on the package explorer error.
Any help would be much appreciated.
Thanks.
java.lang.NoClassDefFoundError: com/adobe/flexbuilder/codemodel/common/CMFactory
 at com.adobe.flexbuilder.as.editor.ui.packageexplorer.FlexPackageExplorer.<init>(FlexPackage Explorer.java:263)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
 at java.lang.reflect.Constructor.newInstance(Unknown Source)
 at java.lang.Class.newInstance0(Unknown Source)
 at java.lang.Class.newInstance(Unknown Source)
 at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(Re gistryStrategyOSGI.java:170)
 at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionR egistry.java:874)
 at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(Configu rationElement.java:243)
 at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(C onfigurationElementHandle.java:51)
 at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:267)
 at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
 at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:263)
 at org.eclipse.ui.internal.registry.ViewDescriptor.createView(ViewDescriptor.java:63)
 at org.eclipse.ui.internal.ViewReference.createPartHelper(ViewReference.java:324)
 at org.eclipse.ui.internal.ViewReference.createPart(ViewReference.java:226)
 at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
 at org.eclipse.ui.internal.WorkbenchPage$ActivationList.setActive(WorkbenchPage.java:4212)
 at org.eclipse.ui.internal.WorkbenchPage$18.runWithException(WorkbenchPage.java:3271)
 at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)
 at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
 at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
 at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3855)
 at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3476)
 at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803)
 at org.eclipse.ui.internal.Workbench$28.runWithException(Workbench.java:1384)
 at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)
 at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
 at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
 at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3855)
 at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3476)
 at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2316)
 at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
 at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
 at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
 at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
 at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
 at com.adobe.flexbuilder.standalone.FlexBuilderApplication.start(FlexBuilderApplication.java :109)
 at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
 at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLau ncher.java:110)
 at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.jav a:79)
 at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
 at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
 at java.lang.reflect.Method.invoke(Unknown Source)
 at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
 at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
 at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
Caused by: org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter$TerminatingClassNotFoundExce ption: An error occurred while automatically activating bundle com.adobe.flexbuilder.codemodel (16).
 at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLa zyStarter.java:125)
 at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java :449)
 at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoade r.java:211)
 at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:381)
 at org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:3 3)
 at org.eclipse.osgi.internal.loader.MultiSourcePackage.loadClass(MultiSourcePackage.java:31)
 at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:454)
 at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)
 at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:398)
 at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.jav a:105)
 at java.lang.ClassLoader.loadClass(Unknown Source)
 at java.lang.ClassLoader.loadClassInternal(Unknown Source)
 ... 51 more
Caused by: org.osgi.framework.BundleException: Exception in com.adobe.flexbuilder.codemodel.internal.bridge.CMBridge.start() of bundle com.adobe.flexbuilder.codemodel.
 at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextIm pl.java:806)
 at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:7 55)
 at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:352)
 at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:280)
 at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:408)
 at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLa zyStarter.java:111)
 ... 62 more
Caused by: java.nio.channels.OverlappingFileLockException
 at sun.nio.ch.FileChannelImpl$SharedFileLockTable.checkList(Unknown Source)
 at sun.nio.ch.FileChannelImpl$SharedFileLockTable.add(Unknown Source)
 at sun.nio.ch.FileChannelImpl.tryLock(Unknown Source)
 at java.nio.channels.FileChannel.tryLock(Unknown Source)
 at org.apache.lucene.store.NativeFSLock.obtain(NativeFSLockFactory.java:246)
 at org.apache.lucene.store.NativeFSLockFactory.acquireTestLock(NativeFSLockFactory.java:79)
 at org.apache.lucene.store.NativeFSLockFactory.setLockDir(NativeFSLockFactory.java:139)
 at org.apache.lucene.store.NativeFSLockFactory.<init>(NativeFSLockFactory.java:117)
 at com.adobe.flexbuilder.codemodel.internal.common.AbstractTextDatabase.start(AbstractTextDa tabase.java:111)
 at com.adobe.flexbuilder.codemodel.internal.search.ASSearchDataProvider.<init>(ASSearchDataP rovider.java:43)
 at com.adobe.flexbuilder.codemodel.internal.search.ASProviderFactory.createDataProvider(ASPr oviderFactory.java:47)
 at com.adobe.flexbuilder.codemodel.internal.search.SearchIndexManager.addISearchDataProvider dFactory(SearchIndexManager.java:70)
 at com.adobe.flexbuilder.codemodel.internal.CMCoreActivator.activate(CMCoreActivator.java:19 9)
 at com.adobe.flexbuilder.codemodel.internal.bridge.CMBridge.start(CMBridge.java:77)
 at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:7 83)
 at java.security.AccessController.doPrivileged(Native Method)
 at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextIm pl.java:774)
 ... 67 more

I'm having this issue since ever with FB 4.7 (the normal IDE version, not the command-line one).
The most consistent way I found to resolve it is to delete the output folders of all flex projects, then restart and perform a clean build.
My suspect is that the incremental compilation is flawed, but cannot be sure of it.
P.S. usually the initial error has this root exception
Root exception:
java.lang.NullPointerException
at com.adobe.flexbuilder.codemodel.internal.bridge.WorkspaceSpecification.getStateLocation(W orkspaceSpecification.java:157)
at com.adobe.flexbuilder.codemodel.internal.bridge.WorkspaceSpecification.getFileInStateLoca tion(WorkspaceSpecification.java:149)
at com.adobe.flexbuilder.codemodel.internal.search.AbstractTextDatabase.start(AbstractTextDa tabase.java:81)
at com.adobe.flexbuilder.codemodel.internal.search.ASSearchDataProvider.<init>(ASSearchDataP rovider.java:25)
at com.adobe.flexbuilder.codemodel.internal.search.SearchIndexManager.initialize(SearchIndex Manager.java:155)
at com.adobe.flexbuilder.codemodel.CMCoreActivator.activate(CMCoreActivator.java:189)
at com.adobe.flexbuilder.codemodel.CMCoreActivator.start(CMCoreActivator.java:76)

Error with test operation 'Could not create the view'

I'm totally new to Flash Builder. I was trucking along developing my first project as a mapping app in FB 4.5 trial version with the ESRI Flex API library. I was testing how to set up WMS and WFS services, and all was going swimmingly until suddenly 'test operations' stopped working. Now when I attempt to test any service, I receive the error "Could not create the view: 1". This error stopped working shortly after I deleted a couple of testing services I had configured, but not immediately after (three or four test worked afterwards before it broke).
I have found almost no information online about this error, but what I have found seems to always reference eclipse. I tried starting a new project, creating a new workspace and uninstalling/reinstalling Flash Builder but the error persists.
Has anyone else ever experienced this error? Any leads at all are appreciated.
Thanks

For anyone else with this problem, it seems to have been an eclipse issue in the workspace. I deleted the 'cascaded' folder and the error went away.

Could not create the view: org/dom4j/io/SAXReader

I'm using the FlashBuilder 4.1 plugin with Eclipse. When trying to access the Data/Services tab in the Flex perspective, I get the following error...
Could not create the view: org/dom4j/io/SAXReader
java.lang.ClassNotFoundException: org.dom4j.io.SAXReader
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:506)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.jav a:107)
at java.lang.ClassLoader.loadClass(Unknown Source)
at fiber.core.impl.FmlModelPersistenceFactory.newModelLoader(FmlModelPersistenceFactory.java :42)
at com.adobe.flexbuilder.dcrad.core.generation.ServicesGenerator.generate(ServicesGenerator. java:69)
at com.adobe.flexbuilder.dcrad.core.generation.ServicesGenerationManager.loadProjectServices (ServicesGenerationManager.java:72)
at com.adobe.flexbuilder.dcrad.core.internal.ServicesManager$ServiceExplorerPartListener.<in it>(ServicesManager.java:1235)
at com.adobe.flexbuilder.dcrad.core.internal.ServicesManager.addListeners(ServicesManager.ja va:302)
at com.adobe.flexbuilder.dcrad.core.internal.ServicesManager.setPage(ServicesManager.java:28 2)
at com.adobe.flexbuilder.dcrad.views.ServiceExplorerView.createPartControl(ServiceExplorerVi ew.java:569)
at org.eclipse.ui.internal.ViewReference.createPartHelper(ViewReference.java:375)
at org.eclipse.ui.internal.ViewReference.createPart(ViewReference.java:229)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
at org.eclipse.ui.internal.WorkbenchPage$ActivationList.setActive(WorkbenchPage.java:4218)
at org.eclipse.ui.internal.WorkbenchPage$18.runWithException(WorkbenchPage.java:3277)
at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4041)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660)
at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803)
at org.eclipse.ui.internal.Workbench$31.runWithException(Workbench.java:1567)
at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4041)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2548)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLau ncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.jav a:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
...Any ideas as to how to fix the problem?
I'm running Windows 7 Home Premium (64 bit), Eclipise Helios Service Release 1, Flash Builder plugin 4.1 (build 277662). On windows XP sp3, with the same version of Eclipse and Flash Builder, I do not get the error.

I'm having this issue since ever with FB 4.7 (the normal IDE version, not the command-line one).
The most consistent way I found to resolve it is to delete the output folders of all flex projects, then restart and perform a clean build.
My suspect is that the incremental compilation is flawed, but cannot be sure of it.
P.S. usually the initial error has this root exception
Root exception:
java.lang.NullPointerException
at com.adobe.flexbuilder.codemodel.internal.bridge.WorkspaceSpecification.getStateLocation(W orkspaceSpecification.java:157)
at com.adobe.flexbuilder.codemodel.internal.bridge.WorkspaceSpecification.getFileInStateLoca tion(WorkspaceSpecification.java:149)
at com.adobe.flexbuilder.codemodel.internal.search.AbstractTextDatabase.start(AbstractTextDa tabase.java:81)
at com.adobe.flexbuilder.codemodel.internal.search.ASSearchDataProvider.<init>(ASSearchDataP rovider.java:25)
at com.adobe.flexbuilder.codemodel.internal.search.SearchIndexManager.initialize(SearchIndex Manager.java:155)
at com.adobe.flexbuilder.codemodel.CMCoreActivator.activate(CMCoreActivator.java:189)
at com.adobe.flexbuilder.codemodel.CMCoreActivator.start(CMCoreActivator.java:76)

** File to IDoc scenario - IDoc not created in target system

Hi friends,
We are doing File to IDoc scenario. We made required setting in both application as well as XI system. While test the scenario, the file is picked up and successfully processed in SXMB_MONI, but the inbound IDoc is not created in target system. What could be the problem?
We are using DEBMAS message type DEBMAS06 IDoc type. We checked the following.
1) SM59 - Connections are OK both application and XI system
2) IDX1 - In XI System, we have assigned SAP<R/3> port.
3) IDX2 - IDoc is imported.
4) In ID - Sender File - Business Service - Adapter-Specific Identifier - Logical System name is given.
5) In application system. - Partner Profile maintained correctly.
6) SM58 - There is no error.
So, what could be the reason ?
Kindly reply, friends,
Thanking you.
Kind Regards,
Jeg P.

Hi,
Check all the steps ..
File to IDOC
Do these configurations in R/3 and in XI...
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
Thanks,
Satya

Multiple MATMAS IDoc getting created through RBDMIDOC program

Hello All,
I am creating MATMAS Idocs by RBDMIDOC proram, but as MATMAS message type is used in multiple distribution models ( i.e. MATAMAS is being sent to multiple partners), its creating multiple IDocs.
I want my IDoc to get triggered only for a particular partner. How can i acheive this ?
Searched on SDN but did not found solution.

As the standard settings, IDOCs will be transmitted to all the Partners which are maintained in WE20 (Partner Configuration). You can restrict the triggering of IDOC based on some condition using the Business transaction event MGV00100 (Publish & Subscribe). This event is called from Function module MASTERIDOC_CREATE_MATMAS (Line number 2074). Documentation of Standard FM SAMPLE_INTERFACE_MGV00100 reads
* Event rissen by the ALE outbound process for MATMAS.
* It allows to modify the idoc's control header the idoc data aswell
* as serialization information created by the standard SAP outbound
* process.
* Raising the EXCEPTION ERROR will prevent the IDOC from being
* submitted to the ALE layer.
* BE CAREFUL WITH ANY CHANGES TO IDOC_CONTROL. IT MAY EFFECT YOUR WHOLE
* ALE-SCENARIO
You have to copy the Standard FM SAMPLE_INTERFACE_MGV00100 to a Z function module and assign it using transaction code FIBF. Search SCN to get more details about configuring Business transaction events using FIBF.

IDOC not created in R/3

Hi,
I am sending IDOC from XI to R/3 using IDOC Adapter.
When I send around 2000 documents(2000 idoc are created in R/3)it works fine and I can see Idoc created in WE02.
But When I send more then 6000 documents,IDOCS are not created in R/3.But I can see in idx5 in XI 6000 outbound idocs.
Thanks in advance.
Rekha.

Have you checked whether the tRFC queue is full and creating with time delay ?
Try to increase remote user login parameter in the instance profile.
regards
Shravan

How to block the sales order for not creating requirement

Dear All,
My client want that whenever a sales order is raise, that should not go create requirement for production unless until account department check whether the prices etc are correctly put or not
how can i do this
thanks

I suggest you can try to use the functionality of Status Profile.
Create one Status Profile with 2 line items-
1: First line : Pricing Approval or PR and check what all you want to block if this status is assigned to the order type.
2: Second line : Released and check what all you want to be released once the Approval is done.
So by default the status profile - Pricing Approval will be assigned to the Sales Order during order creation. Then after your accounts department check the pricing and approves , they can change the status to Released and the order can be processed further.
Regards
Sai

IDOCs not created for Payment method "P" and "B"

Dear Experts,
I have executed the Automatic Payment program for three payment methods (P,V and B - Foreign Currency) in one Run ID. Payment run was successful but it has created IDOCs for the documents / Vendors attached with payment method "V" but IDOCs were not created for the payment methods "P" and "B". I have checked the configuration relating to payment methods and those were assigned with Form details and the maximum amount is also defined in the payment methods.
Can any one suggest me where I had made the mistake / where I need to check the configuration settings.
Thanks a lot.
Regards,
Ramnath.

Hi Surya,
Please find below error log created while executing the Payment run for the issue.
Step 002 started (program SAPFPAYM_SCHEDULE, variant &0000000116195, user ID V-PIZHA)
Step 003 started (program RFFOEDI1, variant &0000003957078, user ID V-PIZHA)
Maintain an output device in your user master record
Job cancelled
Thanks and Regards,
Ramnath,
SAP FIMM Team

Inbound IDOC not creating B007 relationship (HRP1001)

Hi,
I have an inbound IDOC containing object type S (Position) and object type C (Job), plus various relationships including A007 and B007 between the Job and the Position.
All of the relationships get created except the B007 i.e. the Position cannot link to the Job? This is happening for some jobs only....
We checked with all the possible testcases but could not find the clue....
Kindly let me know if anyone have answer ??
Thanks in Advance.

Glen,
Thanks for your Quick response.
Firstly I would like to tell you that the relationship is not created for only couple of Jobs which were existed in the system. But if I do same by creating new records(jobs) its flowing perfectly.
It's giving neither error message nor the Subsegment for this created Object.

Outbound ORDRSP IDOC not created while processing using ALE_PROCESSING .

HI ALL,
i have done all the requiured config for o/b message control for ORDRSP idoc along with config in sale for dist.. model and assigning msg type to model etc and when i save my PO i can see the o/p being proposed but when i process that with A as medium, it is incorectly processed and no ordrsp idoc is created.i am using std idoc_output_ordrsp FM, when i debug the code the see an error in ALE_PROCESSING IN the perform new_dyn_perform
can anyone pls tell me why the idoc is not created.
thanks,

Hi eswar,
i have configured the partner profile for the LOGICAL SYSTEM that i hav created along with the message control deatils in msg ctrl tab( which i think should not really matter) as i have already created a distrib. model for my log. sys and attached my msg typ to that.
when i debug the flow ( rsnast00-rsnasted-ale_processing-idoc_output_ordrsp) i think the error is somewhere in the call function tede1-routid( idoc_output_ordrsp) in the new_dyn_perform subroutine.
but that FM is holding good for other ORDRSP idocs.i am really unable to understand where the error actually is.
thanks

Idoc not created for a particular sales order

Hi,
For a particular sales order , idoc is not created .
The idoc has to be generated when we create a sales order ,
but for a particular sales order , the idoc is not generated when the sales order is created. The program is assigned in
nace for output type zd00.
RSNASTED is the program which triggers the idoc and FM: IDOC_OUTPUT_ORDRSP.
How to debug and see why the idoc is not generated,
i had kept break point in idoc_output_ordrsp function module
and program rsnasted, but my control does not
reaches this point.
can anyone help me in this issue.
Thanks and regards,
A. thirumaran.
Edited by: thirumaran a on Jul 22, 2008 1:35 PM

Hi,
Could you please check if the output is processed or not, whether in the output type what all conditions you have maintained e.g send immediately.
Reward me point if you find this helpful.
regds.......
Sumit

Bug: Can not create materialized view log on 11G XE

Hi,
I log in as HR user and try create materialized view log
CREATE MATERIALIZED VIEW LOG ON HR.EMPLOYEES;I get error
>
Error starting at line 1 in command:
CREATE MATERIALIZED VIEW LOG ON HR.EMPLOYEES
Error at Command Line:1 Column:0
Error report:
SQL Error: ORA-00439: feature not enabled: Advanced replication
00439. 00000 - "feature not enabled: %s"
*Cause: The specified feature is not enabled.
*Action: Do not attempt to use this feature.
>
You can create materialized view log on 10G XE without any problem.
Regards,
Jari
http://dbswh.webhop.net/dbswh/f?p=BLOG:HOME:0

Is it a bug in 11g or 10g?
It was reported earlier in now archived beta forum. {thread:id=2214092}
The current doc lists MV sites only (and "No" for Advanced Replication feature):
http://download.oracle.com/docs/cd/E17781_01/license.112/e18068/toc.htm#BABDFDAI

IDocs not created in file to IDoc scenario

Hi all
I am trying this file to IDoc scenario.
File picked up successfully and sent to R/3 BackendBut Idoc is not postedthe status records
In /n we05 in R/3 Backend shows that EDI: Partner profile inbound not available
I created/tested all basics like RFC dest, port etc.
File service that I am using is a business service hence I am specifying a Logical system name in
Adapter specific Identifiers of the file service.
I disabled EDI_DC40 control tag record as IDoc adapter
takes care of it.
So at first I tried the configuration of IDoc comm. Channel by checking the Apply control record values from payload
But SXMB monitor gave an error regarding this control record tagI guess as we have disabled it so there wont be any values
for control record in payload (correct me if I am wrong).
So I unchecked the checkbox Apply control record values from payload and monitor showed up as successfully processed.
But in the backend I am getting this error regarding partner profile.
I also tried to use an existing profile (LS type) by modifying its inbound parameters to accept CREMAS Idoc.
But the error is as persistent as me
Pls help
Sudhir

Hi
Sender --> LEGACY, maintained in SLD (Logical system).
Receiver--> ENI maintained in SLD with logical sys name M700.
Partner Profile LEGACY maintained in R3.
Following is the IDocOutbound in SXMB monitor in XI.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>100</SAP:MANDT>
<SAP:DOCREL>640</SAP:DOCREL>
<SAP:DOCNUM>0000000000001013</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>CREMAS03</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>CREMAS</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPAXI</SAP:SNDPOR>
<SAP:SNDPRN>LEGACY</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>SAPENI</SAP:RCVPOR>
<SAP:RCVPRN>M700</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL />
<SAP:EXPRSS />
<SAP:STD />
<SAP:STDVRS />
<SAP:STATUS />
<SAP:OUTMOD />
<SAP:SNDSAD />
<SAP:SNDLAD />
<SAP:RCVSAD />
<SAP:RCVLAD />
<SAP:STDMES />
<SAP:REFINT />
<SAP:REFGRP />
<SAP:REFMES />
<SAP:CREDAT>0000-00-00</SAP:CREDAT>
<SAP:CRETIM>00:00:00</SAP:CRETIM>
<SAP:ARCKEY>DF57A2C0532811D9AD84000F206A031B</SAP:ARCKEY>
</SAP:IDocOutbound>
Control record of IDoc in R3
Tab: Typeinfo
 Basic type-->CREMAS03
 Message Type-->CREMAS
Tab: Partner
 Recipient
 Port -->SAPENI
 Partner Number--> M700
 Partner Type-->LS
 Sender
 Port -->SAPAXI
 Partner Number--> LEGACY
 Partner Type-->LS
Pls help
Regards
Sudhir

Failed IDOC not creating a Workitem

Hello Experts,
First of its kind scenario I came across.
I have developed a custom inbound IDOC.
This is processed via a custom Function Module.
When some checks fail in the FM, I update the IDOC Status as failed.
I update RETURN_VARIABLES and WORKFLOW_RESULT = '99999' and then EXIT.
The partner profile is configured for inbound message type (custom).
And for the Process code, I have configured the Function Module to the processing FM,
and
Object type    = IDOCAPLL
Start event     = INPUTERROROCCURRED
End event      = INPUTFINISHED
However, when I test the IDOC in WE19 with erronous data, I see the error status in WE02, however
it does not trigger a failed Worklist Item (under Business Place Workflows)
Any suggestions/solutions experts?
Thanks in advance

Hi,
Have you tried running a trace with transactions SWELS and SWEL?
Kind regards,
Johan Wigert

MATMAS IDOC not creating required views

Similar Messages

Maybe you are looking for