Send ACC_GL_POSTING01 idocs to another system?

Hi all,
i need to send G/L account postings transaction F-02 from one R/3 ro another as soon as the documents is posted or manually distribute through a program.
suppose a FI document is posted in source R/3 in company code '180' and Business Area '7000' then the same document needs to be posted in target R/3 in company code '1870'.
can ACC_GL_POSTING01 iDOC type be used for this?
so what ALE settings needs to be maintained and how to use customer exits at target end to calculate new company code based on source company coade and business area.
valuable inputs needed.
thanks,
Subba

Hi subba Krishna,
Can u please tell me how did u slove this issue. I am also facing the same kind of problem.
Ur help in regard to this is highly appreciated.
Thanks and Regards,
Prasanna.R

Similar Messages

What all configurations to do in SAP R/3 to send an iDOC to XI system

I want to send an idoc from an SAP R/3 ECC5.0 to an XI system Netweaver 04's.
Pls let me know the STEPS I HAVE TO DO IN MY r/3 SYSTEM .
I have created the RFC destination in R/3 and XI system but still the idoc is not going into XI system.
It would be a great help if i can get step bu step guide for the configurations i have to do in R/3 .

Hi,
First check the status , with we02
Also see the below links
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133 - Idocs not reaching XI. Not posted in the receiver SAP
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
Regards
Chilla

Send/receive IDOCs to SOLMAN system using AS2 protocol!

Hi All,
I want to send/receive IDOC file to/from web based SOLMAN system. Currently I'm using FTP server to send/receive IDOC file.
As of now the current process is to send the IDOCs from ECC to FTP server and from FTP to third party and vice-versa. But due to some constraints, I'm bound to use web based SOLMAN system. Please, can you let me know how to send/receive IDOC files to SOLMAN. Is there standrad FM/method to connect to SOLMAN from ECC as in case of FTP we have FM 'FTP_CONNECT'. Heard that same functionality in case of SOLMAN can be achieved through AS2 protocol.
Kindly help.
Thanks.
Regards,
Mukesh

Hello Patrice
We have same issue. Is it possible to use IDoc (XML) directly with SAP 5.0 with SOAP (HTTP) without XI?
Since your que is three years old, I'm sure you must have found some method for this.
We'll highly appreciate your help.
Regards: Gaurave

Error message mes when trying to send PO via IDOCS to another system?

Hi Abap expert,
I am getting wired message what I ma trying to send PO via IDocs to other SAP system.
I went to all partner , port configurations on WE20 and everything there seems to be fine but once I go to ME23N, then GO TO -> MESSAGES , than opens another windows when you key in MESSAGE CONTROL DATA that have been mantained
in the outbound parameters in the PARTNER PROFILE configurations.Then I am getting the message :
'No communication data has been defined for transmission medium 6'-----
The LED on "PO:output screen' is YELLOW and never gets green.
Can someone tell me how to overcome this and send my PO Idocs?Please some more details will be appreciate it!
Thank you much eveyone!
Boby

Hi,
Go and check it in NACE tcode, whether , Condition type, output types are maintained or not? if not maintained, Maintain it for 6 -PO for EDI.
Hope this is the error you are getting.
Thanks
Manju

ME23N Error when trying to send PO via IDOCS to another system?

Hello Experts,
I am getting wired message what I ma trying to send PO via IDocs to other SAP system (XI)
I went to all partner , port configurations on WE20 and everything there seems to be fine but once I go to ME23N, then GO TO -> MESSAGES , than opens another windows when you key in MESSAGE CONTROL DATA that have been mantained
in the outbound parameters in the PARTNER PROFILE configurations.Then I am getting the message :
'No communication data has been defined for transmission medium 6'-----
The LED on "PO:output screen' is YELLOW and never gets green.
Can someone tell me how to overcome this and send my PO Idocs?Please some more details will be appreciate it!
Thank you much eveyone!
Boby

I just got the same problem. Everything worked fine when i was using message type ORDERS01, but when i changed it to ORDERS05 this problem started happening.
This might solve your problem. If you have it solved out can you tell us the solution you found??
regards,
Diogo

T-code ME23N message when trying to send PO via IDOCS to another system?

Hello MM Experts,
I am not sure if my question is more for ABAP guys , but since it is MM related I decided to share it with MM experts as well.
I am getting wired message what I am trying to send PO via IDocs to other SAP system (XI)
I went to all partner , port configurations on WE20 and everything there seems to be fine but once I go to ME23N, then GO TO -> MESSAGES , than opens another windows when you key in MESSAGE CONTROL DATA that have been mantained
in the outbound parameters in the PARTNER PROFILE configurations.Then I am getting the message :
'No communication data has been defined for transmission medium 6'-----
The LED on "PO:output screen' is YELLOW and never gets green.
Can someone tell me how to overcome this and send my PO Idocs?Please some more details will be appreciate it!
Thank you much eveyone!
Boby

Hi Boby ,
TRY going thru this link and check for the details given in it wether they are in place or not specially in the message controls, viz: application EF ,message type NEU and process code ME10
http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7c9f43d711d1893e0000e8323c4f/frameset.htm
regards
kp

What is best way to connect a non-sap sys sending xml idocs to SAP system

Hi Can some one please guide as to what will be the best approach in connecting a NON SAP system to a SAP system.
The non sap system should not be connected to access real time data,it does not support RFC,it can send data in IDOC xml format and i think in teaxt files also.Also I dont think there is any EDI subsystem in place.
There has to be a periodic upload of material data from SAP /stock status/
then there will be incoming data into SAP for sales order/purchase order etc
What would be the best way to connect the two systems,IDOCs with partial EDI looks the best way ,but I am confused as to how will the XML IDOC be converted to normal IDOC and viceversa,how to handle the event triggering mechanism.
If someone has experience in such a scenario ,please help.
There is a option to update the database of the application through SQL also...

Hi,
Check this link.
Web Services from Function Module
it might help u.
Thanks.

During SAP outages,XI unable to send the IDoc to SAP System.

Hi
We have an interface in XI which posts IDoc to SAP .
In the inbound side XI polls the database and executes a query.
But during SAP outages ( Planned/unplanned) though XI executes SQL and process the messages successfully the message fails in the outbound side as SAP is not available.( Column 'c' will be marked with red flag)
Is there any way we can queue up the messages till SAP is available and post the IDocs.
Presently we have to either resend the message from the source system or using
Run time workbench and payload post the IDoc manually.
I guess there could be some settings in the J2EE stack if done can help with.
My environment is XI 3.0 SP14.
Please suggest a feasible solutions.
Thanks in advance,
KP

Hi,
if the quality of service is EO then your idoc is stuck in sm58 and you can force the idoc to be delivered once SAP will come back available.
You can schedule the report RSARFCEX that does exactly this task.
Normally this job is scheduled to run every 5 minutes.
This should solve your problem.
Btw, I suggest you to additionally have a look at this blog <a href="/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically">XI : How to Re-Process failed XI Messages Automatically</a>.
Best Regards,
Sergio

Send IDOC from SAP system to IX but can't see any message in SXI_MONITOR

Hi all,
I have built up an XI system and configured an IDOC to IDOC scenario between two SAP Systems. After completed all configuration necessary:
1. Configuration on Source Side (SAP System that send IDOC) and on Target Side (SAP System that receive IDOC) is OK.
2. SLD is OK: Technical System and Business System are correct for these two SAP System.
3. Integration Repository: all designed Object is OK.
4. Integration Directory: all configuration is OK. "Test Configuration" Function is OK.
5. Runtime WorkBench: is OK. "Test Message" Function of "Integration Server" is OK.
In general, it is all OK.
But when i send an IDOC from SAP System Sour Side (Outbound IDOC from Source Side is OK), on the XI server i can't see any message in Tcode SXI_MONITOR. In this case, my XI server didn't receive any IDOC Message from this Source Side, and so that my XI server can't process and exchange any IDOC sent from Source Side.
Anyone can please help me to explain this problem: why my XI server can't receive any IDOC message from SAP System Source Side when all configuration is OK? Do anyone see the same case as this case?
Thanks a lot for all in advance,
Best regards,
Vinh vo

Hi,
Possible checks
At R/3 side
1) Check in SMQ1 and SM58
At XI Side
1) Check in SMQ2 and IDX5
Check this
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/frameset.htm
Regards
Seshagiri

How to send IDOC to DataWareHouse Systems

Can anyone tell me how to send an IDOC to Datawarehouse systems.

Hi,
please have a look at thread [How to send an IDoc from MII to SAP|http://forums.sdn.sap.com/click.jspa?searchID=60546363&messageID=8112660].
Does this help?
Michael

SAP system IDOC - XI - SAP system IDOC

Hi,
I have created several scenarios for sending IDOCs between different SAP systems, but I have a problem with just one SAP system that is a copy of our production system when is acting as a source.
When sending the IDOC from source system, I can see the IDOC in SM58, with the following error message;
"client xxx is not available in this system" where the client is actually the client of the receiving system.
I have successfully sent IDOCs from other SAP systems to the same target SAP system so there is nothing wrong with the target system.
Anyone experienced the same? Any ideas?
best regards
Torstein

Hi,
I am facing the same issue too. My target system is also release 700 and I have done all my SALE config, we21 settings. But still the error repeats as " Client XXX is not available in the system". How did you fix this issue?
-Teresa

Error sending data to an SCMTM system from an R3 system

Dear Friends
I am trying to send an Idoc from R3 system to an SCMTM system.
I have imported the idoc, message mapping is preconfigured from SAP and requisite configurations in ID have been completed.
I am getting this error in sxmb_moni when I use FTP adapter to post the data to SCMTM system:(it is showing as processed successfully)
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_NOT_FOUND</SAP:Code>
<SAP:P1>,BS_TM7_100</SAP:P1>
<SAP:P2>,BS_ECV_350,,</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>No receiver agreement found for sender ,BS_TM7_100 to receiver ,BS_ECV_350,,</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
When I tried to do this with Idoc receiver adapter but it was giving this following error in Call adapter:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>ShipmentRequestRequest_In</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Unable to interpret IDoc interface ShipmentRequestRequest_In</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Do we have to use some other way of sending data to SCMTM system?or what should we use?
Do we have to suppress any acknowledgements in IDXNOALE,then please give me the steps for it
Please help.
Thank You
Warm Regards
Arjun Ghose
Edited by: Arjun Ghose on Apr 7, 2009 10:48 AM

Hi Rajesh
Found the problem in Receiver agreement/Operation Mapping /Message Mapping after running the test:
Operation Mapping
DESADVDELVRY03_2_ShipmentRequestRequest
Runtime error
Runtime exception occurred during application mapping com/sap/xi/tf/_DESADVDELVRY03_to_ShipmentRequestR~; com.sap.aii.utilxi.misc.api.BaseRuntimeException:Parsing an empty source. Root element expected!
... (136 lines)
In message mapping I tested, but it gave no error.In Operation Mapping there was error:
18:19:04 Start of test
RuntimeException during appliction Java mapping com/sap/xi/tf/_DESADVDELVRY03_to_ShipmentRequestRequest_
com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:ShipmentRequestRequest. Values missing in queue context. Target XSD requires a value for this element, but the target-field mapping does not create one. Check whether the XML instance is valid for the source XSD, and whether the target-field mapping fulfils the requirement of the target XSD at com.sap.aii.mappingtool.tf7.AMappingProgram.processNode(AMappingProgram.java:366) at com.sap.aii.mappingtool.tf7.AMappingProgram.start(AMappingProgram.java:496) at com.sap.aii.mappingtool.tf7.Transformer.start(Transformer.java:133) at com.sap.aii.mappingtool.tf7.AMappingProgram.transform(AMappingProgram.java:626) at com.sap.aii.ib.server.mapping.execution.JavaMapping.executeStep(JavaMapping.java:92) at com.sap.aii.ib.server.mapping.execution.Mapping.execute(Mapping.java:60) at com.sap.aii.ib.server.mapping.execution.MappingHandler.map(MappingHandler.java:87) at com.sap.aii.ib.server.mapping.execution.MappingHandler.map(MappingHandler.java:54) at com.sap.aii.ibrep.server.mapping.rt.MappingHandlerAdapter.run(MappingHandlerAdapter.java:139) at com.sap.aii.ibrep.server.mapping.exec.ExecuteIfMapCommand.execute(ExecuteIfMapCommand.java:33) at com.sap.aii.ib.server.mapping.exec.CommandManager.execute(CommandManager.java:43) at com.sap.aii.ibrep.server.mapping.ServerMapService.execute(ServerMapService.java:40) at com.sap.aii.ibrep.server.mapping.MapServiceBean.execute(MapServiceBean.java:40) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy1579_10000.execute(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351) at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62) at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37) at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
18:19:05 End of test
I could not make out where is the problem .Please help.

Sending PO idoc to create PO in another SAP system

Hi,
SAP A is sending PO idoc (Orders05) to SAP B ...i want it to be posted as PO in SAP B...is it possible or do i have to post it as an SO only ....I found a IDoc type PORDCR01 ...is this correct??
Also once a PO is created in SAP B can i send a ORDRSP back to SAP A? What config is needed for this...only otbound partner profile( with message control) need to have this entry and also a distribution model entry ....what else?
Moderator message: please do more research before asking, show what you have done yourself when asking.
Edited by: Thomas Zloch on Nov 19, 2011 10:39 PM

Please check through MM01 whether these fields are display only or can be input enabled, also check the transportation group (MARA-TRAGR) in both the SAP system are in Sync

IDOC from One System to another

Hi All,
I am sending idocs from one system to another For Eg System A to System B .
Now suppose 2 idocs are generated 1 and 2.
Now how to determine , for idoc 1 in system A, what is the corresponding Inbound Idoc in System B because the data which is coming in System B might be different than in System A for the same Idoc?
Thanks in Advance.

Hi,
direction 1 for outbound idoc,
              2 for inbound idoc,
goto tcode WE02
enter direction - 2.
creation date
and basic type i.e. idoc type
double click on an idoc num.
on L.H.S u have 'Control REc' double click on it..
it contains all the sender details and to what outbound idoc it corressponds to -> basic type, message type
    -> Partner details like partner num, port, partner type
    -> date & time of creation
    -> and the other details
Regards,
Neelima.

Send Idoc to AS2 System via HTTP using XI

Hi,
We need to send Invoice Idocs as XML files from SAP R/3 system to external AS2 system using XI. The communication will happen over HTTP using certificate. I tried using Plain HTTP adapter , but the message went into error 'ATTRIBUTE_CLIENT'. Why this error ?
I came across some blogs saying about Seeburger AS2 adapter , but is this the only possible way ?
Kindly guide.
Thanks.
Tushar

Yes , AS2 adapter is the solution for it.
Refer all the below threads for AS2 information and configuration which need to do for B2B integration:
SEEBURGER EDI adapter
Re: Pls.. Help Needed.. Seeburger Mapping Names..!!
Re: Seeburger AS2 adapter...
Re: AS2 Module tab.. Mapping Names for modified Standard Msg types ? ? BIC ??
AS2 adpater-- Configuration details for both SND and RCV.
AS2 Sender Adapter -- Need few details.

Send ACC_GL_POSTING01 idocs to another system?

Similar Messages

Maybe you are looking for