Overwrite MESTYP in IDoc Receiver Adapter PI 7.1 SP8

Hi all,
can anybody tell me, how i can overwrite the MESTYP field in Idoc Receiver Adapter in PI 7.1 SP 8
BR,
Martin

If you would have read the link you posted, you would have seen that "Apply Control Record Values from Payload indicator" in the receiver IDoc adapter, only overwrites the following fields:
MESCOD
MESCFT
TEST
EXPRSS
STD
STDVRS
STDMES
SNDSAD
SNDLAD
RCVSAD
RCVLAD
REFINT
REFGRP
REFMES
STATUS
DIRECT
OUTMOD
CREDAT
CRETIM
Sorry but it seems that this forum just get's spammed with answers based on superficial knowledge just in order to increase the count on your answers.
Hopefully SAP-Forum admins quickly implements a quality control for forum answers!

Similar Messages

IDOC Receiver Adapter

Hi,
We have IDOC receiver adapter and data for control record is fed from mapping. For this we have checked the flags " apply control record" and sender receiver from payload.
Recently we copied our QA system from Dev and while testing the Control records are coming from Dev. We have mapping in place whcih looks at the value of receiver and if it does not match with QA, by default it assignment the dev system as receiver
When i am running the interface this mapping is failing and IDOC of QA is getting DEV Control record parameter.
How doe this receiver/sender value is determined in mapping. I checked the SLD and everything looks good.
I cannot test the mapping as while testings is giving 'Test_SenderService' etc which is expected.
Thanks!

We have mapping in place whcih looks at the value of receiver and if it does not match with QA, by default it assignment the dev system as receive
>>> Can you share the UDF?
Are you reading the system name(System.getProperty("SAPSYSTEMNAME")) to determine the environment of the XI system??
Make sure that updated the logical system names in SLD..

Steps to define correctly IDoc receiver adapter

Hi guys,
I try to set up the IDoc receiver adapter, but I still get error, that adapter is not deefined correctly...
Can you pls send me the info, which all steps I have to do, to have it defined correctly?
Thanx in advance, Peter
Message was edited by: Peter Jarsunek

Guys,
I'm in trouble.. I tried all the things you advised me, but nothing works... I still get the error: Communication channel is not defined correctly.
I have read all the links, but please, understand - I'm not a "SAP" man
Could you please write me step-by-step help, what to do??
e.g. 1, on XI box - SM59 (you have to define RFC connection to target system)
PLEASE!!!!!
10 PTS for YOU!!!
Thanx in advance!!

Maximum size of XML files and number of IDocs for IDoc receiver adapter

Hi Guys,
We have an XML file to IDoc scenario where XI picks up an XML file with multiple Customer records in it, it does a simple mapping and creates one DEBMAS06 IDoc per record in the XML file. All IDocs are sent in a single file in XML-IDOC format to IDoc adapter which then posts the separate DEBMAS IDocs to R/3.
a) What is the maximum size of XML files that XI can handle with mapping involved ?
b) What is the maximum number of IDocs in a single file that the receiver IDoc adapter can handle ?
The first time this interface runs almost 200,000 Customer records will be exported in one XML file.
Thank you.

Hi,
Well it is difficult to find out the maximum Size of xml messgaes that can be processed by XI and also Maximum number idocs an recevier Idoc adapter can handle.
This totally depends on your production system loads and the limits can be set totally on trail & error basis..
In my heavy loaded production system, i found out that the maximum size of the successfull messages after processing by XI is around 75 MB (seen in transaction SXMB_MONI). Whereas messages with size around 100 MB went into error.
I havent encounter any such limits with respect to Idocs.
I would suggest that you divide your data into smaller chunks and sent it part by part instead of sending it all once since you data size is huge.
You can vary your batch size as per your system load.
Regards,
- Deepak.

IDOC Receiver Adapter, getting Lock Table Overflow to CRM System

Hello SDN!!!
This scenario is for PI to process a file and send to CRM via IDOC. The IDOCu2019s are only being created and not processed until later.
Problem: I am getting a Lock Table Overflow error in method IDOC_INBOUND_ASYNCHRONOUS via sm58 in PI which points to the CRM box.
I have been searching many forums and every solution seems to indicate increasing the lock table, the problem with that solution is we are currently trying to create (not process yet) 80000 IDOCu2019s. This would allocate too much for the lock table.
So my question is this, Shouldnu2019t the lock be released when the IDOC gets created or none the less when a packet of IDOCu2019s via content management (breaking up the file in 1000 increments) finish. The lock table in CRM keeps increasing until all rows from the file, sent via IDOC adapter in 80 messages with 1000 IDOCu2019s per messagein the table are complete (80 separate messages in sxmb_moni).
Background:
IDOC was imported, changed to include unbounded and reimported.
Content Management breaks the file into 80 different segments, thus creating 80 distinct mappings with distinct MessageIdu2019s.
80 IDOC packets are sent to CRM, via IDOC adapter and sm58.
TCODE sm12 in CRM shows the table to keep growing and locks not released until full message is complete.
Any help would be appreciated
Cheers
Devlin

The only way to process the IDOCs in this case is by increasing the "enque/table_size" parameter in order to create the required IDOCs. You can increase the value for this parameter up to 102400 (beyond that can cause performance issues). Since you need to handle 80000, this shouldn't be an issue.
Please refer to the notes below for more information about the lock queue overflow and management.
[Note 552289 - FAQ: R/3 Lock management|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=552289]
[Note 13907 - System error in the block handler, overflow lock table|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=13907]

Monitoring IDoc Receiver Adapter

Dear experts,
in FILE -> XI -> IDoc scenarios erros are not shown correctly. Neither SXMB_MONI nor RWB shows errors for outbound status of the IDoc when I select for errors. If XI sends an IDoc to another System and the partner for the RFC connection is locked, I only see the error in SM58 or SXMB_MONI (but not in the first column... I have to scroll to the right to see the red flat in column "Outbound Status" and the flag in the first column shows me, that everything is ok).
Is it possible, to configure XI to change the overall status of the message or to show these errors in RWB? It's impractical to use different selections and tools to get all possible errors.
Thanks in advance,
David

Hi David,
Since your scenario is File to IDOC hence if XI has processed the message successfully then you will see the successful flag but as you said if you scroll to the right and there you see a red flag which is also correct behavior because the problem is at outbounding side. So check your configuration again in ID.
Few steps you can varify ....
Check the RFC password has not expired.
Make sure in your receiving system i.e R3, You have setup the partner profile correctly in WE20. Also the Port created in XI which contains the RFC (which connects to R3 system) is working fine.
Also make sure if you have uploaded the IDOC metadata using IDX2 transaction code.
if you are getting any specific error message please let us know.
Secondly it will be not possible to change the standard behvior of Moni to change the overall status of message.
Regards,
Sarvesh

IDOC Sender Adapter and Receiver Adapter

Hi,
Why we don't require IDOC Sender Adapter to communicate with PI and why IDOC Receiver Adapter is required to communicate with SAP ?
Regards,
J Augastine

Hi,
>>>Why we don't require IDOC Sender Adapter to communicate with PI
you're talking about sender and receiver agreements right ?
as this adapter is based on abap stack - with new functionalities of IDOC adapter
require sender agreement
>>>and why IDOC Receiver Adapter is required to communicate with SAP ?
as we need to put the RFC to the destination system somewhere...
Regards,
Michal Krawczyk

Send Idoc flat file message in JMS receiver adapter

Hello,
I am working on a scenario where we send Delvry 03 idoc from ECC to external system. To external system, we send the whole Idoc in flat file structure through JMS queue. I have used Idoc to flat file program in my interface mapping and have configured JMS receiver adapter with just default Module configs but, I am getting an error in communication channel monitoring for the messages.
Please note that Idoc xml to flat file structure conversion is already done in the mapping, I need to just pass this idoc flat structure in the jms adapter. Hence ther eis no content conversion i nthe adapter..
Please give some inputs..Here are the modules in my receiver adapter and nothing else..
SAP XI JMS Adapter/ConvertMessageToBinary
SAP XI JMS Adapter/SendBinarytoXIJMSService
The error I get is in audit log
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: No transition found from state: ERROR, on event: process_commence for DFA: CC_JMS_R:ca336a6689f837da8bd3387140fc4447
in turn the message has this error if I open the message
Whitespace is not allowed at this location. Error processing resource 'http://host:port/mdt/messageconten...
and it shows one of the lines from idoc..flat file
Any idea is greatly appreciated..Thank you..Thanujja

The difference in what I suggest is that it is way simpler.
Maybe you did not understand this, so will try to explain it better. Its not the best thing to do, but if JMS adapter doesn't budge then you can give it a shot.
1. You continue to use the ABAP mapping in your interface mapping to map the Idoc xml to Idoc flat.
2. Write a Java Map that will take the output of the ABAP mapping ; and then create a XML output which would be something like,
<Root>
<Idoc_Flat>
<Data>ABAP Mapping Output<Data>
</Idoc_Flat>
</Root>
3. Now use the simple content conversion in the JMS adapter to convert this to flat file.
Regards
Bhavesh

IDOC as a receiver adapter in XI to 3rd party scenario

Hi All,
I have an requirement to connect sap xi and 3rd party. the scenario as given below:
sap ecc 6.0 --> sap xi --> 3rd party
Here ecc is sending an idoc to the 3rd party. The 3rd party is SAP certified and intelligent enough to receive and send idocs. Here I'm using a idoc adapter as a receiver adapter. In the receiver adapter I have to give a rfc destination and a port name.
My question is how to create a rfc destination for the 3rd party. and which port name we'll use in this case. Is the port name will be the 3rd party port name is yes then how I can create a port in the 3rd party system.
Please help.
Regards,
Santosh

A communication channel with a receiver IDoc adapter can be created automatically for business systems that are defined in the System Landscape Directory. refer this link
[http://help.sap.com/saphelp_nw04/helpdata/en/42/d1a4d665c5574fa6e19784358ec948/frameset.htm]
You need to configure the receiver IDoc adapter to convert Integration Server contents from IDoc-XML to native IDoc format and to forward the IDocs to an SAP system .
you create a port and the rfc destination pointing to receiver in PI system
use tcode sm59 for creating rfc destination and IDX1 to create port and map it to rfc destination.

IDOC Receiver determines no receiving service

Hi,
I have send an R/3 IDOC successfully to XI and find the messag with status OK in the monitor, even the receiving service and the receiving interface is empty.
I have configured a message interface and the receiver has an appropriate communication channel using SOAP. In the repository there is a defined receiver and even in the SXI_cache I can see the receiver.
Has anyone an idea?
Thanks
Juergen

Hi Volker,
the cache is OK, here is the data form the monitor:
Date Time sender Namespace sender Sender Interface Receiver Rceiver Interface
17.03.2006 05:42:53 SAPR3 urn:sap-com:document:sap:idoc:messages REQOTE.PORDCR04.YFUTURA
and here is the SOAP header of the message:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<Trace level="1" type="T">User: RUGE</Trace>
<Trace level="1" type="T">Language: D</Trace>
<Trace level="1" type="T">XML-Conversion for all IDocs </Trace>
<Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling </Trace>
<Trace level="1" type="T">IDoc-Inbound-Handling </Trace>
<Trace level="1" type="T">Syntax-Check-Flag X</Trace>
<Trace level="1" type="T">IDoc-Tunnel-Flag </Trace>
<Trace level="1" type="T">Queueid </Trace>
<Trace level="1" type="B" name="IDX_IDOC_TO_XML">
<Trace level="1" type="T">Get the Metadata for port SAPI01</Trace>
<Trace level="1" type="T">Convert Segment-Definitions to Types </Trace>
<Trace level="1" type="T">Make Syntax check of actual Idoc </Trace>
</Trace>
<Trace level="1" type="T">Set Receiver Routing-object </Trace>
<Trace level="1" type="T">Exit Function IDX_INBOUND_XMB </Trace>
<Trace level="1" type="T">COMMIT is expected by application ! </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"></Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE"></Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE">
</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
</Trace>
<Trace level="1" type="T">**************************************************** </Trace>
<Trace level="1" type="T">* * </Trace>
<Trace level="1" type="T">* * </Trace>
<Trace level="1" type="T">XMB entry processing </Trace>
<Trace level="1" type="T">system-ID = TXI</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = D</Trace>
<Trace level="1" type="T">user = RUGE</Trace>
<Trace level="1" type="Timestamp">2006-03-17T04:42:53Z CET </Trace>
<Trace level="1" type="T">* * </Trace>
<Trace level="1" type="T">* * </Trace>
<Trace level="1" type="T">**************************************************** </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE"></Trace>
<Trace level="1" type="T">Message-GUID = 3B4CA10CF867924D9F60B752E345F378</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC"></Trace>
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0005</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0005</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment </Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK! </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message </Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking </Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST </Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC </Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye ! </Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace>
</SAP:Trace></SOAP:Header><SOAP:Body><SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7"><SAP:Payload xlink:href="cid:[email protected]"><SAP:Name>MainDocument</SAP:Name><SAP:Description/><SAP:Type>Application</SAP:Type></SAP:Payload></SAP:Manifest></SOAP:Body></SOAP:Envelope>
I dont know how to increase the trace level, so ists still 1.
Thanks
Juergen

Filename from payload - FTP receiver adapter

Hello everyone!
I have a scenario wherein I need to get the value from a field coming from an IDOC and then give that value as the "filename" of the file that is saved in the FTP folder.
IDOC > XI > FILE
For example, if /ORDERS05/IDOC/E1EDK02/BELNR = 620000123
then I want the name of the file to be saved in the FTP folder to be 620000123.xml
I understand you may use the 'variable substitution' property in the FTP receiver adapter, but subsequent attempts at trying to configure that property have resulted in errors. Can anyone help me out?
Warm regards,
Glenn

do u have recordset name (root message)
For Ex: If you want to refer to the field which is bold
below is your variable substuition:
payload:root,1,e1,1,e2,2
<?xml version="1.0" encoding="UTF-8" ?>
<root>
<dummy>
 <e1>
 <e2>Data_1</e2>
 <f/>
 <g attr="abc">text</g>
 <e2>Data_2</e2>
 </e1>
</dummy>
<e1>
 <e2>illegal/value</e2>
 <f/>
 <g attr="abc">text</g>
 <e2 attr="fghij">Example Value</e2>
 </e1>
</root>
Similarly
for your strucutre:
<MS_MT>
<order>
 <number>
the variable substuition would be
payload:MS_MT,1,order,1,number,1
you have to give complete XML to arrive to this value.

Adapter-specific message attributes for the JMS Receiver adapter

Dear SAP Community,
We are trying to activate some parameters at message level when SAP XI sent an interface (XML data) to IBM Websphere MQ. Programmaticaly, this is done the following way:
       TextMessage outMessage = session.createTextMessage();
       MQQueue replyToQ = new MQQueue("TESTQM01","SYSTEM.ADMIN.ACTIVITY.QUEUE");
       Destination replyTo = (Destination) replyToQ;
       outMessage.setJMSReplyTo(replyTo);
       outMessage.setIntProperty("JMS_IBM_Report_Exception", MQC.MQRO_EXCEPTION);
       outMessage.setIntProperty("JMS_IBM_Report_Expiration", MQC.MQRO_EXPIRATION);;
       outMessage.setIntProperty("JMS_IBM_Report_COA", MQC.MQRO_COA);
       outMessage.setIntProperty("JMS_IBM_Report_COD", MQC.MQRO_COD);
       outMessage.setIntProperty("JMS_IBM_Report_Discard_Msg", MQC.MQRO_DISCARD_MSG);
This code is working fine.
Since the documentation about this feature (Adapter-specific message attributes) is very light, We am not sure about the interpretation we made.
First, we defined the following attributes: MS_IBM_Report_Exception, JMS_IBM_Report_Expiration, JMS_IBM_Report_COA, JMS_IBM_Report_COD, JMS_IBM_Report_Discard_Msg. All of them are with type int.
Then we changed the mapping (XSL) to pass the value to the dynamic configuration, using the technical names (DCJMSMessageProperty0, ..., DCJMSMessageProperty4) and the value of the constants. We also specified a value in the Reply To Queue parameter of the adapter. As a test, We also change another parameter via the mapping (the correlation ID, to use the idoc number) and according to the log of the processed message, every thing is finde. According to the trace of the JMS adapter, everything is fine to. However, this has no impact on the message, only the correlation ID is changed.
The JMS server is IBM Websphere MQ (v6.0.2.1). It is already in production and working fine. This is a change we have been asked to implement.
Has anyone experience with the JMS receiver adapter-specific message attrbitutes ? What have we done wrong ?
Any help is greatly appreciated.
Regards,
Gregory PFISTER
SAP XI Analyst - Holcim

Hi Neha,
pls do chk the below links for SOAP adapter message attributes
http://help.sap.com/saphelp_nwpi71/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/43/0a7d1be4e622f3e10000000a1553f7/content.htm
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/sap_xi/sapximst38.htm
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/webservices/webservices16.htm
Regards
Sampath

Q? how to change filename of receiver adapter includeing payload attribute?

hi all.
our scenario is IDOC - XI - FILE.
IDOC is standard type .xml"
Despite of searching help library, just read about how to change using payload value.
How to change the filename using payload attribute?
Message was edited by: ChangSeop Song

Hi,
You can create the file name dynamically from the payload of the receiver adapter as follows.
From the requirement you have stated, you want your file to be named as,
TPSDLS<shipmentid>.
For this, in the reciver file adapter, give your filename as TPSDLS%var% and under variable name substitution,
var --> payload:IDOCTYPE,1,Shipments,1,ShipmentID,1
here, var acts as your variable name and it first looks for IDOCTYPE and its first occurence, shipment and its first occurence and finally, shipmentID and its first occurence. There by generating the filename dynamically.
For more info on this, check the topic variable substitution under this link.
http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm
hope this helps,
let me know if you have any clarification,
regards,
bhavesh

Overwriting the File in File Adapter

Hi All,
I hav a module processor (in Receiver file Adapter)which checks the existence of the file by name DOWN.flg befor writing the file by the same name at the same location. if the file already exists, then it has to wait until another system deletes (as per the requirement). if not, it has to write the file. I had done this successfully with an FTP receiver. but when i'm moving the same functionality to the local drive(now the receiver is a local directory on the XI Server), then i'm getting the following error.
Error:Attempt to process file failed with java.lang.Exception: Overwriting file '/cpe/data/DEV/XI_/IN/APD/Commander/DOWN.flg' not allowed due to configuration flag
Error:
Exception caught by adapter framework: Overwriting file '/cpe/data/DEV/XI_/IN/APD/Commander/DOWN.flg' not allowed due to configuration flag
these are the errors which i found in the audit log. i din't check the overwrite Existing File option in the Receiver adapter.Can anyone help me out in resolving this.
Anyhelp wud b greately apprecited...
Thnx in Advance.

Hello Jayakrishnan,
Thank you very much for the tip, actualy it was very tricky, since the overwrite existing file option is not possible in the "append" mode on my XI version (SP12). THis is what we have done :
- modify the communication channel to "create" mode and check the "overwrite existing file option".
- activate it
- chanche back to the "append" mode
- activate it again
And then it works !
Thanks for your help
Guislain

Problems with Seeburger FTP Receiver adapter

Hello,
I am working on a scenario sending ORDERS05 Idocs to EDI vendors.
For this i have configured Seeburger Receiver FTP adapter with 2 modules to convert XML-EDI format. Since this is the test, I have pointed Seeburger to local FTP server with following settings
Hostname <Hostname of our FTP server>
Port <Port # of our FTP server>
Host Path/VAN partner id <some local directory of FTP server>
Payload mode: Maindocument.
At runtime i received following exception
Message could not be forwarded to the JCA adapter. Reason: Fatal exception: javax.resource.ResourceException: >> Description: com.seeburger.jftp.app.exception.FtpExceptionSoftProcessingError: Unexpected reply: 500 'SITE system 1': command not understood>> Details: com.seeburger.jftp.app.exception.FtpExceptionRethrowError: Error in session: {type:FTPConnectionId}{binding:82ea8d3089dc3e898ae2e608d9d8487d}{channel:a52d1aaa8dd63ff59c2f590e78586a77}{toparty:TestEDIParty} CAUSED BY: com.seeburger.jftp.app.exception.FtpExceptionOpenConnectionError: Error while connection to remote host CAUSED BY: com.seeburger.jftp.app.exception.FtpExceptionRethrowError: Error while executing command QUOTE site system 1 CAUSED BY: com.seeburger.jftp.app.exception.FtpExceptionSoftProcessingError: Unexpected reply: 500 'SITE system 1': command not understood>>SendingStatus: NOT_TRANSMITTED>>FaultCategory: COMMUNICATION_ERROR>>Retryable: true>>Fatal: true
Few questions related to this
1] can we use Seeburger adapter to generate EDI files on local FTP server
2] If not Seeburger can we use normal File adapter to do the same. I tried the same by configuring BIC module in File adapter so that it would convert XML to EDI format and was hoping file to be generated on FTP server. It generated one line XML file with following text "<info>Converted message locates in a attachment</info>". Any idea how to retreive attachments in File receiver adapter (as far as i know no attachments are supported in File receiver adapter).
Any idea how to generate EDI files with Seeburger FTP on test server?
Thanks in advance.
Regards
Rajeev

Hi Rajeev,
> 1] can we use Seeburger adapter to generate EDI files on local FTP server
Yes we can use.
> Any idea how to generate EDI files with Seeburger FTP on test server?
It is like a normal process, how to generate the EDI files in normal means without FTP. Check this link
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10b17369-9522-2c10-84a6-d75d8a8ace22
BIC
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00b66651-eeea-2b10-e5a6-8459ec30d948
Regards
Ramesh

Overwrite MESTYP in IDoc Receiver Adapter PI 7.1 SP8

Similar Messages

Maybe you are looking for