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

Similar Messages

Why do I get the message "CoCreateInstance failed - Could not create 3D mouse device" with Acrobat9?

Had a crash and reinstalled everything. All is OK, except when I open Acrobat 9, I get the message "CoCreateInstance failed - Could not create 3D mouse device". Tried unchecking anything in Acrobat preferences having to do with 3D, and I don't currently have a 3D mouse device installed. Can't find any other reference in Google that includes both Acrobat and the contents of the message, part or all. Ran "repair acrobat installation" and rebooted, and that didn't help. Totally stumped!

use the cs cleaner.
first uninstall your cs5 programs (including acrobat) and uninstall adobe reader.
run the cleaner for reader: http://labs.adobe.com/downloads/acrobatcleaner.html
restart your computer.
then run the cs cleaner (http://www.adobe.com/support/contact/cscleanertool.html)
restart your computer
and finally reinstall your cs5 programs including acrobat (but not reader).

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

** 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

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

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?

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

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

DPM 2012 Install Fails, The Database was not Created ID 811

Hi.
I've tried installing DPM on a Standalone Server (SQL + DPM), and get the "Database was not Created" error. I initially tried DPM 2012 R2, and found that there is an issue with Disjoint Namespaces, so went to DPM 2012 SP1, but still getting
the same error.
The Install Account has full access rights (sysadmin) to the DPM SQL Instance, however cannot seem to get it right. The account using to do the install has full Enterprise admin, Domain Admin, Backup Operators & Administrators rights.
When opeining SQL Managemet studio, I can see the database has been created but the setup fails and requires me to revert.Here is the last few lines of the Install Log File, please help I always mark as answer.
2014-10-01 08:54:49 PM] Information : Configuration.DBConfigurator: Setting Read_Committed_SnapShot ON
[2014-10-01 08:54:49 PM] Information : Creating tables
[2014-10-01 08:54:49 PM] Information : Execute the SQL script
[2014-10-01 08:54:49 PM] Data : FileName = "D:\Program Files\Microsoft System Center 2012\DPM\SQL\100\Tools\Binn\SQLCMD.EXE"
[2014-10-01 08:54:49 PM] Data : Arguments = -b -E -d DPMDB_S_PRODBACKUP -i MiniSetupDBConfiguration.sql -r -S S-PRODBACKUP\SCDPM
[2014-10-01 08:54:49 PM] Data : Error code = 0
[2014-10-01 08:54:49 PM] Information : Adding DPM Server entry in tbl_AM_Server table
[2014-10-01 08:54:49 PM] Information : Preloading Microsoft.Internal.EnterpriseStorage.Dls.AgentManager.DB.InstalledAgents
[2014-10-01 08:54:49 PM] Information : Preloading Microsoft.Internal.EnterpriseStorage.Dls.EngineUICommon.DpmThreadPool
[2014-10-01 08:54:50 PM] Data : Database connection string = Integrated Security=SSPI;server=S-PRODBACKUP\SCDPM;Pooling=false;database=DPMDB_S_PRODBACKUP;Pooling=false
[2014-10-01 08:54:50 PM] Information : Grant execute permissions on dbo.prc_MOM_ProductionServer_Get to DPMDBReaders$S-PRODBACKUP
[2014-10-01 08:54:50 PM] Information : Grant execute permissions on dbo.prc_MOM_HeartBeat_Get to DPMDBReaders$S-PRODBACKUP
[2014-10-01 08:54:50 PM] Information : Configuration.DBConfigurator: Registering DPM category
[2014-10-01 08:54:50 PM] Information : Configuration.DBConfigurator: Adding DPM Category to GlobalSettings table
[2014-10-01 08:54:50 PM] Information : Configuration.DBConfigurator: Adding ConsiderOfflineMediaToCheckOffsiteReady to GlobalSettings table
[2014-10-01 08:54:50 PM] Information : Add job definitions
[2014-10-01 08:54:52 PM] Information : Creating schedules
[2014-10-01 08:55:00 PM] * Exception : => System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Runtime.InteropServices.COMException (0x800706BE): The remote procedure call failed. (Exception
from HRESULT: 0x800706BE)
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at Microsoft.Internal.EnterpriseStorage.Dls.Engine.CProxyUtils.HandleErrors(Int32 hr, tagSAFEARRAY* exceptionResult)
   at Microsoft.Internal.EnterpriseStorage.Dls.Engine.SchedulerServicesProxy.Register(String scheduleXml)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Configuration.DBConfigurator.RegisterScheduleXml(String scheduleXml)
[2014-10-01 08:55:00 PM] * Exception : => The DPM database was not created.Use Add or Remove Programs in Control Panel to remove the DPM files and registry entries that were created during Setup. Verify that SQL Server is properly installed and that
it is running, and then run Setup again.Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.BackEndErrorException: exception ---> Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.DatabaseConfigurationException: exception ---> System.Reflection.TargetInvocationException:
Exception has been thrown by the target of an invocation. ---> System.Runtime.InteropServices.COMException (0x800706BE): The remote procedure call failed. (Exception from HRESULT: 0x800706BE)
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at Microsoft.Internal.EnterpriseStorage.Dls.Engine.CProxyUtils.HandleErrors(Int32 hr, tagSAFEARRAY* exceptionResult)
   at Microsoft.Internal.EnterpriseStorage.Dls.Engine.SchedulerServicesProxy.Register(String scheduleXml)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Configuration.DBConfigurator.RegisterScheduleXml(String scheduleXml)
   --- End of inner exception stack trace ---
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Configuration.DBConfigurator.RegisterScheduleXml(String scheduleXml)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Configuration.DBConfigurator.RegisterSchedule(String scheduleXmlFile)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Configuration.DBConfigurator.PopulateDefaultScheduleDefinitionsInDatabase(DBConfigurationReader dbCfgReader)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Configuration.DBConfigurator.AddJobAndScheduleDefinitions()
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.MiniSetupConfiguration.PopulateDB(Boolean upgrading, Boolean isRemoteDb, String sqlServerMachineName)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.BackEnd.MachineSpecificConfiguration(Boolean existingDB, Boolean upgrading, Boolean isRemoteDb, String sqlServerMachineName, String instanceName)
*** Mojito error was: DatabaseCreateFailed; 0; None
   --- End of inner exception stack trace ---
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.BackEnd.MachineSpecificConfiguration(Boolean existingDB, Boolean upgrading, Boolean isRemoteDb, String sqlServerMachineName, String instanceName)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.BackEnd.Configure(Boolean existingDB, Boolean upgrading, String databaseLocation, String sqlServerMachineName, String instanceName, Boolean oemSetup)
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.DpmInstaller.Configure()
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ProgressPage.InstallDpm()
   at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ProgressPage.InstallerThreadEntry()
*** Mojito error was: DatabaseCreateFailed; 0; None
[2014-10-01 08:55:02 PM] *** Error : The DPM database was not created.
Use Add or Remove Programs in Control Panel to remove the DPM files and registry entries that were created during Setup. Verify that SQL Server is properly installed and that it is running, and then run Setup again.
ID: 811
[2014-10-01 08:55:02 PM] Information : Data Protection Manager installation has failed. To return the server to its original state, you must uninstall Data Protection Manager by using Add or Remove Programs in Control Panel. This will remove all files and components
copied during installation.
For details, click the Error tab.
[2014-10-01 09:33:51 PM] Data : Error Code Web Link =
http://go.microsoft.com/fwlink/events.asp?ProdName=Microsoft System Center Data Protection Manager&ProdVer=4.1.3313.0&EvtID=811&EvtSrc=MSDPM&LCID=1033&P2wAppId=p2wMsdpmEE

Hi,
Check the SQL Agent account on the remote SQL server and make sure the user account syntax is in the form of UserName\DomainName and not UserName@DomainName - if it is change it.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This
posting is provided "AS IS" with no warranties, and confers no rights.

IDOC_INBOUND_ASYNCHRONOUS FM not creating new IDOC?

Hi,
IDOC_INBOUND_ASYNCHRONOUS function module is not creating new IDOC in SAP.
I configured all related functions against message type and idoc type.
Please let me know the issue.
I am processing old IDOC (created from non sap system) through BD87 and using custom function module. I called IDOC_INBOUND_ASYNCHRONOUS in custom function module.
Chandra

Hello,
Aren't you getting any error messages ? You may check by creating watch points on the message id and / or number .
Thanks

IDOC is created with status 51( application document not posted)

Hi experts
iam working on File-IDOC scenario, when i test the process the XML message is created with no errors and
but the IDOC is created with status 51( application document not posted)
the details error shows:
An error occurred in CALL TRANSACTION USING or CALL DIALOG USING
during a synchronous update.
The error was caused by the transaction VA01.
previously i used same test data that time it was working fine,
please tell me how can i fix the issue.
regards
vasavi

Key in your Idoc number in BD87, execute
select the error message and then follow the menu path :
EDIT --> restrict and process (Select)
In the next screen UNCHECK the Bkgd Processing and execute
Now EDIT --> Process --> foreground from error or in foreground mode.
This will lead you the screen where it errored out.
Thx
PSR

F9N7- IDOC FINSTA not created

Hi,
We are using IHC for inter company cash within group. Normally an IHC process chain runs overnight and we have no issue. However, today we manually ran F9N7, as overnight job did not pick up some payment orders and did not create bank statement.
On running F9N7 we were able to create bank statement(I see entry in table BKKM1) however system did not create IDOC type FINSTA.
How do we create idoc type FINSTA for both sending and receiving companies(bank statements) as i am unable to rerun F9N7 as bank statement is already created.
Kindly advise
Umang

Have you resolved the issue?

P.O. IDoc not being created

Hi all,
I've configured all (I think) required steps to trigger IDocs when Creating/Changing PO's.
My requirement is to send them to PI and then to SQL DB and soon as they're created/changed.
I've followed many threads here to get it configured and I'm also following the Michal's book (Mastering IDoc B.S. with PI).
It was done:
NACE configs
> EF (tried to use NEU and tried creating another output type ZSB).
ZSB output type created: General Tab - Access to condition TRUE / Multp. Issuing TRUE / Access sequence 0001 DocType/PurchOrg/Vendor (I'm not sure about its usage and whether it's correct or not) / Prog. Output 'FM06AEND' / Form Routine 'CHANGE_FLAG'. Default Values - Send Immed. / Distr.(ALE) / LS.
Partner Functions - Distrib. (ALE) / LS
Proc. Routines - Distrib. (ALE) / RSNASTED / ALE_PROCESSING
It's added to EF > RMBEF1 > Procedures > Control (Step 100)
Condition Record - Purch. Output Determination: Doc. Type. Using only Doc.Type=NB / Funct=LS / Medium=A / Dat=4
In our WE20, Part. Type LS, I created in the Outbound paramts. the ORDCHG and ORDERS with corresponding port, ORDERS05 and EF / ZSB / ME10/ME11(respectively).
When creating a new PO or changing an existing one, no IDocs can be seen at WE02.
Don't know where else I could check to get it working.
Please suggest.

Jonny, what should I check in the NAST table?
I have these information there:
App     Object key     Msg Type     Partner     Role     Med
EF     4500078279     NEU          100064     BA     A
EF     4500078279     NEU          100064     LF     5
EF     4500078279     ZSB          100064     BA     A
EF     4500078279     ZSB          100064     RS     A
Order status field - Not processed
Output ZSB (that I created for Purchase Order)
Medium - A
Function is set to 'OA' and partner = '100064' Lang = 'EN'
Tried to put the Function='LS' and got the message 'Partner 100064 does not exist for partner function LS'. When trying to put LS without partner number, it requires a partner number.
It looks pretty self explaining message but I think that, as I'm not sending it to a Vendor partner, I just cannot put a VN function (as the How-To tells to do), so I put this LS with no partner number. I don't know if I'm doing that wrong, although the messages confirms that.
Processing log button shows 'No processing log exists' message.
In the end, I got a green icon message at footer - No communication data has been defined for transmission medium A
Please advice.

Failed IDOC not creating a Workitem

Similar Messages

Maybe you are looking for