Sending IDoc from SAP ECC6 to SAP BC: IDOC_ERROR_METADATA_UNAVAILABLE

Hello,
I am posting an IDoc (COSMAS01) from SAP Backend to SAP BC 4.8.
I am getting this Exception:
2010-04-01 12:17:08 CEST com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "??????????????????????????? ?" with extension " COSSAPRGL RGI_0 ???" is unavailable.
 at com.sap.conn.idoc.rt.DefaultIDocDocument.<init>(DefaultIDocDocument.java:126)
 at com.sap.conn.idoc.jco.rt.JCoIDocDocument.<init>(JCoIDocDocument.java:92)
 at com.sap.conn.idoc.jco.rt.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:170)
 at com.sap.conn.idoc.jco.rt.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:80)
 at com.sap.conn.idoc.jco.JCoIDoc$DefaultJCoIDocRuntime.createIDocDocumentList(JCoIDoc.java:144)
 at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:107)
 at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:153)
 at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3300)
 at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2780)
 at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2598)
 at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2489)
 at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2310)
 at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:277)
 at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:337)
 at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:238)
 at com.wm.util.TimeWrappingProvider$TimeMesuredTask.run(TimeWrappingProvider.java:40)
 at com.wm.pkg.sap.rfc.ListenerThread.run(ListenerThread.java:70)
2010-04-01 12:17:09 CEST com.sap.conn.jco.JCoException: (104) RFC_ERROR_SYSTEM_FAILURE: IDocException occurred (raised by system AS-RGAG-01|a_rfc)
 at com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException(MiddlewareJavaRfc.java:639)
 at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcS
I have manually loaded the IDoc definition in the DDIC cache of the SAP BC, but this was of no help.
For me it looks like an encoding problem as the the JCO adapter seems not to be able to even identify the basic IDoc type, or what else can this mean?:
The meta data for the IDoc type "??????????????????????????? ?" with extension " COSSAPRGL RGI_0 ???" is unavailable.
It is a simpe COSMAS01 IDoc with no extension, btw I tryed other IDoc types as well but I am allways getting this weired message.
Any ideas?
Thanks
Matthias

Hello Rajesh,
as far as I know, I do not have to do this bevorehand.
Normally, the SAP BC is creating a routing rule on the first reicipt of an unknown message (IDoc) .
But in order to do so, it needs to interpret sender | receiver | message type , on which it in my case seems to fail.
Thanks Matthias

Similar Messages

Send IDoc from External System to SAP system

Hi Folks,
I have a requirement to send IDocs from an external system to the SAp system. Basically the external system is a subsystem which is able to send & receive idocs. The external system is currently able to send idocs to SAP system through the ALE layer but now we have to replace it by PI. Now the external system has to send teh IDocs to the SAP ECC system through the SAP PI 7.0.
Kindly let me knowq how I can achieve it.
Regards,
Santosh

Hi Satish,
You can achieve this requirement
1)If your external system going to support web service cals then send IDoc from External system as a web service, in PI use sender side SOAP and receiver side IDoc receiver channel to send IDoc.
or
2)Use proxy program ,implement the same ALE logic in PI.
or
3)Copy the Extenal IDoc message in to file folder as XML,then use file adapter to pick up this message and send it SAP using IDoc.
Regards,
raj

Send IDOC from Business Connector to SAP faster

Hi Developer!
I need to send a very lot of IDOC converted from XML files from the Business Connector to SAP. The XML files are in different directories pro business partner, but they have a same type (ISU_MSCONS).
My problem, that the import take a lot of time. Only in every 3 seconds (IDOC creation time) gets (or works up?) the SAP one IDOC. I start diferent services pro partner at the same time to import the IDOCs, but I couldnt short the 3 second work time in the SAP. So you can count it easy, that in 1 minute I can import 20, in 1 hour 1200, in 1 day 28800 IDOCs instead of 100.000.
It is really parallel import? Have anybody any idea to make the import more faster. I know (asked the SAP Administrator) so, one BC - SAP connection (Program_ID) has more pools (= threads) in the SAP at the same time.
Thanks any help,
Charlie

Hi Satish,
You can achieve this requirement
1)If your external system going to support web service cals then send IDoc from External system as a web service, in PI use sender side SOAP and receiver side IDoc receiver channel to send IDoc.
or
2)Use proxy program ,implement the same ALE logic in PI.
or
3)Copy the Extenal IDoc message in to file folder as XML,then use file adapter to pick up this message and send it SAP using IDoc.
Regards,
raj

Message SR 053 when i send idoc from SAp R/3 4.6C to PI 7

Hi,
I try to send idoc from SAP r/3 4.6C to PI 7. I had made ALE configuration in my sender system ( SAP 4.6C) but idocs are not sent to PI. In SM58 i have message "Name or password is incorrect (repeat logon)". Yet i'm sure that user and password are correct because if i test RFC destination using SM59 , test is OK.
Is somebody can help me ?

Hi,
In R/3 :
my RFC destination is type 3 and point to XI. The port in the partner profile point to this RFC destination. ( all seems good !).
In Xi : i created a port and i load manually idoc in idx2 to be sure that RFC destination was OK. Nothing in IDX5.
When i send idoc MATMAS using BD10 from R3 to Xi i have something very strange: first the message B1 038 "1 master IDocs set up for message type MATMAS" and just after
the XI logon screen appears !! Then message "1 communication IDoc(s) generated for message type MATMAS" and this idoc stay in SM58 with message "Name or password is incorrect (repeat logon)".
Somebody can give me requires caracteristics for XI user used in R/3 RFC destination ?

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

Error sending IDOC from external Java application to Sap ERP system

Hi Experts!
When I try to send Idoc from Java application to XI an error occurs : no service for system CLNTJAVA, client in Integration Server.
My question is: What value the setSenderPort() is excepting?The Java third party business system's logical name or the ERP business system's logical name where the JCO can be found?I tried both of them, but still have the problem.
Please help. I read all threads about this error, but non of those can help me.
My relevant java sourcecode:
doc.setSenderPort("CLNTJAVA");
The XI documentation says that:In the case of non-SAP senders, the entry in the SNDPOR field is interpreted as a logical system name, and the corresponding business system is searched for in the runtime cache.
Both case(third party business sytem and erp business system) I have configured the ID i think correctly. I made a business systems,I configured the adapter specific identifies,I made the IDX1 port,I made the RFC destination,I polled the IDOC type with IDX2 transaction, I have made full cache refresh,I configured the INTEGRATION_DIRECTORY_HMI rfc destination,but I do not made any communication channels, receiver determinations, receiver agreement.
My configurations if it can help for you.
Hostname:sapsp5
System name: NE2
Clients:
000 ERP
001 Integration Server
SLD configurations:
Third Party Technical system name: Java_sytem
Business System:CLNTJAVA
Logical system name: CLNTJAVA
ID configurations:
Business System:CLNTJAVA
adapter-specific identifiers:logical system:CLNTJAVA, the rest is initial,because I cant change it.
IDX1 port name: CLNTJAVA the client is 001. the rfc destination is client_001.
I think the IDX1 port and the adapter specific identifiers are wrong. is it?
my java source if the sender is the JCO
doc.setSenderPort("INTSERV");
My configurations if the sender is the JCO.
SLD configurations:
Technical system name: NE2
Business System:INTEGRATION_SERVER_NE2
Logical system name: INTSERV
ID configurations:
Business System:INTEGRATION_SERVER_NE2
adapter-specific identifiers:logical system:INTSERV,system NE2,client 001.
IDX1 port name: INTSERV the client is 001. the rfc destination is client_001.
Could this error be an autorization error?I tired to connect to the xi from the Java, with the user PIISUSER extended with PISUPER roles.
Thank very much.

Hi!
My SNDPOR already set to my source business system's logical name if you check my configurations(JAVACLNT), so there is another problem unfortunately. I set SNDPRN to JAVA, but it still does not work.
Check this configuration please(posted here:
No service for system ... in Integration Directory)
doc.setMessageType("ACC_DOCUMENT");
doc.setRecipientPort("SAPSE1"); // get stuck in XI mapping if not set
doc.setRecipientPartnerType("LS");
doc.setRecipientPartnerNumber("SE1CLNT500");
doc.setSenderPort("SAP3MA");
doc.setSenderPartnerType("LS");
doc.setSenderPartnerNumber("TREMACLNT");
doc.setClient("100");
Inside XI configuration integration builder
Business Service: Service: TREMACLNT
Under the menu Service - Adapter specific identifiers
Idoc Adapter Logical system: TAPPMAN (This thing is important when sending idoc XI -> SAP and should match the logical sys in the receiving SAP system)
IDoc Adapter and RFC adapter R/3 Sysytem ID: 3MA
Client: 100
In IDX1 trans
Port: SAP3MA (Note that the 3MA here is matched against the IDoc Adapter and RFC adapter R/3 Sysytem ID: 3MA)
(a not so well documented feature)
Client: 100
RFC Destination: SE1 (A SAP test system from where IDOC def can be imported, rfc dests are setup in SM59)
I guess that your idx1 port name is the same as the SNDPOR value. I think it should be, because the XI is whatching the IDOC traffic in the idoc adapter port, so you should send the IDOC from external system to the adapter port. Is it right?
My idx1 port is the same as my SNDPOR value in Java,but still came the error.

Issue in sending IDOC from BODS to SAP

I am getting issue while sending IDOC from BODS to SAP.
Job is getting failed with error : "No authorization to send Idoc with message type CREMAS"
I have checked last authorization in SU53 and it is Successful !!
What would be reason because of which job is getting failed with Authorization error?

Go to sm58-->Select IDOC_INBOUND_ASYNCHRONOUS this function module, in menu mar select edit--> execute LUW.
or take help from sap basis team, can you please check user in the source system have authorizations profile. 'S_BI-WX_RFC' for this u can refer sap note :150315.
if you need more information refer this document:
How to check a BW - SAP source system connection - SAP NetWeaver Business Warehouse - SCN Wiki

How to send IDocs from a non-SAP system to a SAP system

Hi everyone i am new to SAP R/3 System.
Currently i am required to send IDocs from a non-SAP system to a SAP R/3 System.
There is a guide on Cost-Effective and Quick Communication between SAP and 3rd Party Systems using IDOC HTTP XML Interface. But its from a SAP system to a non-SAP system and i am able to do that.
Is there any step by step guide where they teaches you how to send IDocs from a non-SAP system to SAP system via similar method?
Thank You!

Hi,
I hope this link may help you......
http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r1/index.jsp?topic=/com.ibm.swg.im.iis.ds.entpak.sapr3.use.doc/topics/c_pack_r3_Introduction.html

How to send IDOC from nonSAP to SAP

Hi ;
I need to send IDOC from nonSAP to SAP. I have experience it with XI and BC..but now I need sending IDOC to SAP directl without these tools..
Can you explain it via sample? (I know already how to create port , define LP from we20,we21 ).
Firstly Do I need to create a RFC destination ? and I want to send IDOC as XML by HTML post method..Which port must I send?
Must this port point to this RFC?
Thanks.

Hi,
Here you have to generate an IDOC and convert into XML format and put at required server
third party will accept the IDOC XML not the IDOC.
Just check with ur third party in which format the data is accepted.
if its IDOC XML then u can use the file receiver adapter and place the IDOC XML file on 3rd party folder.
You use the IDoc adapter to have IDocs (intermediate documents) processed by the Integration Engine. IDocs from SAP systems Release 3.1x or higher are supported. You can also use the IDoc adapter to connect non-SAP systems to the Integration Engine.
The IDoc adapter converts the IDocs to IDoc XML format so that they can be processed by the Integration Server pipeline.
You can also transfer XML in IDoc format received from the Integration Server to connected systems. The Integration Server pipeline must convert the received XML to IDoc XML, and then transfer this IDoc XML to the IDoc adapter. The IDoc adapter converts the IDoc XML to native IDoc format and sends the IDoc to the identified receiver system using the standard IDoc interface.
Regards,
Shamma

How to Transfer Customizing Data from SAP ECC6 to SAP Solution Manager

Hi all,
I want to Transfer Customizing Data (such as organization structure) from SAP ECC6 to SAP Solution Manager.Please tell me how. Thanks.

Hi,
The system cannot capture the customizing data from your ECC6. This is another myth with SAP Solution Manager. Solution Manager can only smoothen the process of your Project Management.
Hope this solves your problem.
Feel free to revert back.
--Ragu

Sending IDoc from R/3 to XI -ongoing

Hi,
With reference to my previous errors while sending IDoc to XI from R/3 system. I have resolved errors with help of Seshagiri and Kummari advise and help. But now I am getting new kind of error, while sending IDoc from R/3 its getting passed from R/3, but while checking it in XI throug SXMB_MONI I am getting below error:
<?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>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_POCreateIdoc_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_MM_POCreateIdoc_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can any one advise me on this?
Thanks & Regards
Manish

Hi,
There were so many Mapping Objects under different Namespaces and under that different Message Mapping trees.
Under one tree I have tested the XML message and found the below error:
Cannot produce target element /ns0:MT_POFile/POItem/Price. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd Cannot produce target element /ns0:MT_POFile/POItem/Price. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
Kindly check if this is the correct error I am getting related to SXMB_MONI error message.
Regards,
Manish

Sending IDOC from R/3 to MII error

Hi,
We are trying to send IDOC from R/3 4.7 to MII 12.1 (SP8 patch 9 on NW CE 7.11).
We followed the guide below:
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3861e693-0e01-0010-e791-9b44d2693e6c
Connection of message listener to R/3 works fine.
RFC connection test from R/3 to message listener was successful.
But when we try to do model distribution we get this error " - Communication error occured. Server repository could not create function template for 'MODEL_VIEW_REPLICATE'.
Maybe someone encountered this error and can help to resolve it.
Thanks in advance.

Hi Michael,
What do you mean by "manually registered the ProgID"? The message listener configuration property is as below:
ProgramID: MII_IDOC_CONNECT_5
MaxReaderThreadCount: 1
SAPClient: 800
UserName: GAOMX
Password: xxxxxxxx
Language: EN
ServerName: blade01a.memc.com
PortNumber: 00
BindingKey: XMIIIDOC
And also, following is error message found from LOG VIEWER of the MII server:
here is one
Message: not supported FunctionModule MODEL_VIEW_REPLICATE for IDocActivationSpec
Date: 2011-07-21
Time: 15:30:18:060
Category: /System/Server/Connector/Rfc
Location: com.sap.mw.jco.jra
Application: sap.com/sapjra~xMIIIDOC05
Thread: Thread[Managed_Application_Thread_20,5,Managed_Application_Thread]
Data Source: j2ee/cluster/server0/log/system/server_00.log
and another one
Message: Server repository could not create function template for 'MODEL_VIEW_REPLICATE' caused by: java.lang.RuntimeException: not supported FunctionModule MODEL_VIEW_REPLICATE used with IDocActivationSpec registered for MII_IDOC_CONNECT_5 on system blade04a_MIT_00
Date: 2011-07-21
Time: 15:30:18:061
Category: /System/Server/Connector/Rfc
Location: com.sap.conn.jco
Application: sap.com/sapjra~xMIIIDOC05
Thread: Thread[Managed_Application_Thread_20,5,Managed_Application_Thread]
Data Source: j2ee/cluster/server0/log/system/server_00.log
Thanks,
Mike

Problem when sending IDOC from ECC to MII 12.0

Hi all,
   I have followed the document "[How to Send an IDoc from SAP ECC to the SAP MII IDoc Listener|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50775783-6cb1-2b10-90b0-e6bc2c0b8563]" to configure the scenario to send IDOC from SAP ECC 6.0 to MII 12.0.
   But when sending 53 IDOCs by Tcode POIT to MII, I have problem as below:
   - 53 IDOCS were successfully outbounded (list in WE02).
   - 8 IDOCs were successfully sent to MII IDOC listener (these 8 IDOCs messages exist in list of Message Monitor).
   - 45 IDOCS were error with message in SM58: "Bean IDOC_INBOUND_ASYNCHRONOUS not found on host xxx, ProgId=yyy".
   I'm wonder why some IDOCs were successful while some others were error. If the bean IDOC_INBOUND_ASYNCHRONOUS don't exist in EJB, why some IDOCs successful found this bean?
   I have another wonder: in this scenario document, all IDOC message type (SYNCH, LOIPRO) is configured in outbound parameters of RECEIVER (receiver logical system), why they weren't configured them in outbound parameters of SENDER (sender logical system)?
   If some have the same problem and know how to resolve it, could you please help me?
Thank a lot in advance,
Vinh Vo

Hi Vinh,
Please read the following document:
[IDOC Listener|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/bpx-community/manufacturing/how%20to%20send%20an%20idoc%20from%20sap%20ecc%20to%20the%20sap%20mii%20idoc%20listener.pdf]
If you explicitly defined a Prog ID in NW, then you have done an extra step and are confusing NW with the real destination.
In basic terms, you set up an RFC destination (with an assigned ProgID) in ERP, then configure MII to point to it.
I suggest that you follow the document completely and do nothing else to set up a new listener.
If you are not using ECC 6.0, you may find the paths are different, but the transactions codes are generally the same. However, you may want to check with some of the older installation instructions regarding specific modifications. Look in the Wiki for MII under Connectivity.
Good luck,
Mike

Sending IDoc from ERP to PI

Hi all,
I am trying to sent IDoc's from the ERP (SAP ECC) side to PI. But the IDocs are not arriving at the PI side. In ECC tc:we05 they seem to be successfully sent.
The Partner Type in we20 is "LI". I added the IDoc to the Outbound parameters and set the PORT to the Port we use for PI. But unfortunately it is not working.
Any idea why?

When sending IDoc from ECC System to PI.
some settings needed on ECC System & PI System
On ECC System
Create Port in WE21 type LS (Logical System) use RFC Destination TYPE ABAP in that port.
Create Partner Profile using PORT in WE20.
Add the Idoc as Outbound in that Partner Profile.
Now on PI System
PI System does not have structure / matadata of IDoc.
Create Port in IDX1.
Import IDoc Matadata in IDX2 use Port created in IDX1.
Create complete scenario & send IDoc from ECC, it will reach at PI System, if successful at ECC.

Sending IDocs from R/3 to XI

Hello,
I try to connect a R/3 system to an XI system. I have made the SLD configuration, created RFC destinations, ports and so on. Sending IDoc from XI to R/3 was successful.
No I would like to send IDocs from R/3 to XI. I did the necessary steps at R/3 as described in several blogs etc.:
SM59 rfc dest to XI
WE21 tRFC port
I also read about this step: Create receiver sys as logical system in BD54. What is this for? I am not sure if this step was done in my case, cannot check it at the moment.
I am trying to send an IDoc via transaction WE19 (Idoc Test tool). I think there is no need to create a partner profile?
Now I am wondering: Which values must be set in the control record? I inserted the port pointing towards XI, but I am not sure about the other fields.
I know there are several blogs on this topic but for me there are some details missing. I am also interested in some kind of explanation not just WHAT steps have to be done, but WHY they have to be done.
Thanks in advance, point will be awarded.
CHRIS

> 1. The process is like this: The Logical system is
> defined (as its name suggest ) just for Logical
> definition of the communicting parties. The technical
> details are not provided here.
> 2. Then RFC Destination is maintained where actual
> connection parameters r maintained.
> 3. Port here act as the medium through which the
> transmission is done.
> 4. To identify ur particular message, Partner Profile
> is maintained.
>
> Now in we19 test tool, the port provides the medium
> where the data should be sent. Through this medium,
> the connection to the receiver is checked via RFC
> destination.
Also thanks to you. I understand that the message is sent to a port, which points to a certain RFC destination. But still I don't get it: I thought thats exactly what WE19 is for: To send IDocs for testing purposes to ports, while there is no partner profile needed? I thought there is no partner profile necessary as I can set all fields manually in the control record (receiver port, sender port, message type, receiver type and so on).
Kind regards
CHRIS

Send idoc from one version of R/3 to different version

Hi All,
I have a scenario to send idocs from one R/3 system to another (both have different versions) .Can anyone tell me the step by step way to configure. Do I need to program anywhere to send or receive idocs Any help is really appreciated
Thanks
Michael

Hi michael,
The version change technique allows you to exchange idocs with systems using the older version of idocs.
For this v have to configure the sending system to generate back level idoc for receiving system using the partner profile. configuring the partner profile is enough to send idocs in this scenario.
Regards....
Arun.
Reward pts if useful.

Sending IDoc from SAP ECC6 to SAP BC: IDOC_ERROR_METADATA_UNAVAILABLE

Similar Messages

Maybe you are looking for