Send Changes for IDOC ORDRSP

Hi Gurus
Can anyone help me in sending the changes for the IDOC for transactional data.
For Sales Order IDOC -- ORDRSP.
When newly sales order is created, all the sales order information should be sent. --This is not a problem.
When changes are done on the sales order -- Only the changes should be sent in the IDOC. I have activated the change pointers in BD50, BD51 for ORDRSP and in BD52 created the entries for ORDRSP.
but when i trigger the IDOC using the output type, i get to see all the data instead of only the changes.
Is there anything that i am missing???
Any help is really appreciated.
Thanks
Saritha

Hi Linda,
I have documentataion on ALE/IDOCs which may not be helpful to you. If u need that i can send u .
Instead i can help u out if u r facing any issue.
In our case: wen ever sales order is created /changed an idoc shud be genrated.
This can be done thru Message control.
Which involves customization from functional guys in NACE as well as Technical guy in Partner profile/port..
do let me know where ever u r not clear.
regards,
Naveen

Similar Messages

Pls send material for idocs in ECC 6.0

Pls send material for idocs in ECC6.0

Hi sitaram s ,
IDoc
- IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system.
Archiving Processed IDocs
IDoc archiving is a two-step process:
1. Archive the IDoc.
2. After that another job will be generated. You can see in your SARA for your trigger to delete those archived IDocs.
Have a look at transaction WE47, set "Archiving - Possible" for all statuses to be archived. Use transaction SARA with object IDoc to archive. If the above is set then all IDocs are archived the same way.
Transaction SARA works in the following way:
On the main screen enter IDoc as the object. Click on Customising -> Technical settings. This shows the logical filename (configured via transaction FILE & SF01) that will be used to get a filename when writing the archive files. It also shows the document type (that links to an archive via transaction 0AC0) or the archive, depending on SAP version. You can also set the size of the archive files and whether the deletion and storage jobs should execute automatically or not.
On the main screen there are, amongst others, buttons for ARCHIVE, DELETE and MANAGEMENT. When you click on ARCHIVE you will go to a screen where you can create variants, and set the parameters for the archiving job. The EXECUTE button will schedule this job. If the "start automatic" tic for the deletion program was not set in customising, you will need to go to the DELETE button on the main screen to schedule the deletion jobs, after the archive job has finished. This schedules a job per archive file. In MANAGEMENT you will be able to see the statuses of each archive run.
SAP Integration Using ALE(Application Linking and Enabling)
- IDOCS -
http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
Updating IDoc data in segments,Changing a control record of an IDoc,Getting IDocs linked to Application documents,
Displaying and IDoc in a report,Read IDoc from Database,Creating and sending an IDoc,Update IDoc status on the database
ALE Inbound Pre-Processing
http://www.erpgenie.com/sapedi/idoc_abap.htm
cheers!
gyanaraj
reward points if u find this helpful

Do we need a sender channel for IDOC to file scenario.

Hi,
Do we need a sender channel in IDOC to FILE scenario.
Because IDOC is being sent by SAP R/3 System and when creating objects in ID using wizard, it doesn't ask for sender channel.
What is the reason for this?
Regards,
Younus

Younus,
to add more...
From WAS(Web Application Server) 6.20 and above BASIS is not the runtime for SAP.WAS is the runtime for SAP.
And it has got ABAP and JAVA engine in it.
It handles connections made over various protocols such as SMTP for mail, HTTP(S), and SOAP/XML.

The SAP Web AS 6.10 did not have a Java engine.
and IDOC and HTTP are present on the ABAP engine and the rest reside on JAVA engine.
and that is the reason why IDOC and HTTP doesnt require Sender Adapter and Sender Aggrement aswell.
Hope i cleared ur point...
Cheers,
Raghavesh
Message was edited by:
Raghavesh Reddy

Sending Acknowledgements for IDOCs

I have reviewed the document "How To... Handle Acknowledgements for IDOC" and "Configuration Tips for a Business Service/Integration Process to Send Back ALE Audit IDOC". These don't seem to work for the situation I have.
We have two R3 systems sending IDOCs to XI, one located in the US and one in Germany. The above documentation (from what I can tell) expects you to only have one R3 system. For example, when setting up the Adapter-Specific Identifiers, there is only one spot to enter in the Logical System or R3 System ID.
Is there a way to set up IDOC Acknowledgements if you have more than one R3 system that can be sending IDOCs?

Hi Larry,
for each R/3 create one business system service. Depending of the control data in your idoc (you can examine the sender R/3 system in the IDOc header data) create different receiving systems.
Regards Mario

Unable to convert sender service for IDoc to SOAP Scenario

Hi,
I tried to find the solution my way and by using the search function but without any success. I have the folowing scenario:
SYS(my sap system) => IDoc => PI (Process Integration) => SOAP => XML
When i send the IDoc to the PI System and open SXI_Moni the folowing error is shown:
"Unable to convert the sender service receiver_service to an ALE logical system"
I read about Adapter Specific Identifies so i go to ID->Service without partner->Business System->MyBusinessSystem(SYS) then in Menü on Services and checked Adapter Specific Identifies. They are like maintained in SLD.
Next is a Cache refresh i tried a full one but no impact
Then i tried a header mapping in receiver agreement. I mapped there the receiver party to the definied receiver party and the receiver_service to the service.
I have no idea
Thanks for help, be sure that helpful answers will be awarded
regards
Matthias
P.S. What causes this error ? For my opinion ALE has already done all neccesary things (The Idoc is in PI System and the data is available in mesaage payload) so why didn't the pi map it and send it via Soap?

Hi Matthias
>>I dont know if its helpful but in SLD are only the system of our landscape so i have no entry for the external Party.
Party information is generally not required to be maintained in SLD
>>Adapter Specific Identifies
What is the value you have given for sender Business system->adapter specific identifier. Is it the same as the partner profile name in sender SAPECC. if not try making them same.
Regards
Suraj

Multiple customers in Sender Party for IDOC type KU

Hi All,
My scenario is IDOC to HTTP with sender IDOC Type KU.
We are using PO 7.4 and IDOC_AAE.
I have done the following settings.
Created a Sender Party and assigned a customer under party identifiers. (Also I can't add multiple values with same Agency and scheme it throws eror in PI)
For a single customer the end to end scenario is working fine.
But if I try to send the IDOC with other customer Number it fails as the entry is not maintained for that customer in Sender Party identifiers.
Also I can't afford to create a different party for each customer as there are hundreds of customers in the ECC Application system.
I also tried with value mapping but it won't worked.
Please suggest on this.
Regards,
Nitin...

Dear Nitin,
did you solve this problem? A am faced to it right now... ...
Regards,
Markus

Sender change for EWA reports

Hello,
On client demand, we need to change sender of the EWA reports ( currently it is being emailed from my user id ) .
We changed user name for SCOT job but we are not able to change sender.
Can you please let me know how to change sender of EWA report.
Best Regards,
Tushar

Tushar,
Were you able to achieve this. The SM:EXEC SERVICES job and the SCOT job are currently run by user ID: XYZ and the the EWA
is set up by the user ID XYZ.
I changed the following:
Deleted SM:EXEC SERVICES and the SCOT job and recreated them to be run by user ID ABC (the one I want to change to).
It still uses XYZ as the sender (not ABC) because as the configuration is set up by user XYZ, it is creating SM:EXEC SERVICES
on the fly to be run by user ID XYZ.
Please let me know what I am missing. What else need to be changed ? Thanks.
Ravi

Monitoring and sending alerts for IDocs

Hi ,
I have Idoc scenarios both outbound and inbound.
My requirement is that whenever an Idoc goes into error state an alert should be sent to a specified person automatically.
Please also let me know ways to reprocess Inbound and outbound Idocs.
Thanks

Hi,
Your question is mainly for ECC, than for PI...
but you can acheive it, for instance, by creating an abap program which checks the IDoc status, and send an email to a list of persons you determined for instance in a Ztable for each idoc (message type + idoc type + idoc extension). You can scheduled this program by creating a SAP job (tcode SM36).
Another way could be to add an abap enhancement in each idoc process (inbound / outbound) to check the status of this idoc and send an email. But...
Personally, I prefer the 1st solution, as the program is scheduled, you can group several idoc errors and send only one email (!). Keep in mind this case: among 1000 inbound idocs, 750 are in error, because of a bad or a missing data in the source system... What 's the result with the 2nd solution?... it's a spam of 750 emails to the emailbox of your employees (!!!. Not sure they will appreciate...
To retreat Idoc, you can use tcode BD87. Do not give this tcode to all employees, but only to some key users, to avoid that an employee retreat several idocs which are not in its scope (because he/she did not a godd selection in the selection screen) and which should be not be retreat now (exm due to a fiscel year).
regards
Mickael

Why we do not need sender agreement for Mail and SOAP adapter

Hi SDN,
I know, we do not need sender agreement for IDOC ,HTTP,XI adapters. As these three adapters will run in Integration engine of the abap stack.
In our scenario if sender is other than IDOC or HTTP or XI .
By Refering Sivamni's blog.
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
message will be pickedup by communication channel with the help of sender agreement and prepare XI message header by performing cpa cache lookup. then message will go to module processor etc.
In our scenario if sender is IDOC or HTTP or XI .
As these 3 adapters are run in Integration engine.
Doubt 1:
how the integration engine will create the xi message header like sender interface sender system name etc...
Doubt 2:
I believe SOAP and mail adapter will run in adapter engine.but i came to know that we do not need sender agreement and sender comm channel for these two adapters too...then how the XI message header will create...
Please do correct me if i am wrong
and throw some light on the same..
Appreciate your help....
Regards,
Reehan.

Reehan,
Thanks for pointing me to that link. Guess I was wrong .,But,let me try to put to you why you need a sender agreement for a Sender SOAP Adapter,
1. In the sender SOAP adapter , the Sender Interface and the Interface Namespace as provided in the fields Default Interface Name and InterfaceNamespace. The Name of the Sender Service is provided in the WSDL when you ceate the WSDL in the Integration Directory. So, as all details are available in either the Sender SOAP adapter or in the WSDL url you do not need a Sender Agreement. It is not obligatory but you can always create the Sender Agreement.
2. For the mail adapter , if you select the option XIPAYLOAD, you will have the option to mention the Interface Name and Interface Namespace under XI Parameters and so in this case as once again the details provided in the sender agreement are available in the Sender Adapter itself the sender agreement is not needed for the mail adapter when you have select option XIPAYLOAD.
If you have selected XIALL then you need a sender agreement.
Regards
Bhavesh

All Line Items need to send in the PO Change EDI IDoC - ORDCHG

Hi EDI Experts ,
We have ECC 6.04.
We are sending PO Change Message Tyep by using Message Type ORDCHG ( Basic Type ORDERS05)
If PO Changes system trigger IDoc and in Std IDoc it displays only that Line Item who had been changed .
Requierment is that if there is change in any single item, then sytem should send entire/whole PO document ( all Line Items) .
I think we need to write some code in teh routine /requierment ...etc.
Can anyone suggest what I need to do to acehive the above ?
Thanks
NAP

Hello NAP ,
I have the same problem that you. I ´m using the message type ORDCHG with basic type ORDERS05. when sending change order through Idoc only show me the updete/delete Item in segnment E1EDP01.
What object did you use for the message type ORDCHG ?
What settings should I consider for this?
Thanks in advance,
Luis.-

Material Master Change Pointer IDOCs not generated for Moving Avg Price GR

No IDOC is created or distributed when the moving average price
changes. Each time a Goods Receipt is performed, the material master
moving average price (MBEW-VERPR) changes but the change is not
distributed. No change pointer is created in the tables. Why?
We need to send the moving average price each time it changes. In our
case, each time a Inbound Delivery has been Post Goods Receipt this
value changes for that material + plant combination and the value
should be sent.
The field MBEW-VERPR is included in BD52 as a field relevant for change
pointers for the message type.
Please advise.

Hello,
SAP will not generate change pointers (and no IDOCs) for Moving Average Price (MAP) changes. This is because MAP updates are not really Master Data changes and they are driven by transactions such as Goods Receipts, Revaluations etc. For these transactions, SAP will generate respective accouting documents for traceability.
Thanks,
Venu

IORD for sending Order via Idocs

Hi SAP Experts,
Does anybody know how to use T-Code IORD for sending Idocs, every time I run this T-Code not a single Idoc gets created.
Also I would like to know what does 'Status Profile/User status to be set' mean on the selection-screen, I think its happening due to this only.
I've done lots of Idoc Integration using HR Idocs but this is a first Idoc Integration for me in PM module so not sure what should be the best way of sending Order via Idocs to 3rd Party system.
Any help would be appreciated.
Thanks,
Sunny Thakur

Hi Pete,
We are trying to send SAP PM Work Order for production equipment changes , I came to know that IORD generates Idocs for Order but somehow whenever we try to run this T-Code all the orders are getting rejected. Also I've noticed Idoc Type IORDER cannot be used for sending Delta changes , is it true? I can't find any entry for this message type in BD60 so makes me think SAP did not design this Idoc type for delta changes, even though I know we could customize it
Do you know what should be the best way of sending SAP PM Work Order to external system , should we create one custom Idoc type?
Let me know in case you could help me out.
Thanks,
Sunny Thakur

Trying to change Inbound IDOC to Outbound IDOC for testing....

Hi Friends,
I am trying to do the following
1) In our legacy system SAP R/3 3.1H we have received an IDOC from our partner. This has been stored correctly.
2) We now need the same functionality in our SAP R/3 4.6C system so I have created the IDOC type + segments accordingly. I have also set up the partner profiles
3) We need test data but our partner can not send yet so the only other way is to send this INBOUND IDOC from 3.1H to 4.6C.
4) HOWEVER, i have tried everything to do this like using WE19 to edit the idoc, but I can not process it for OUTBOUND processing.... You can in 4.6C but there is no option in 3.1H.
HELP!! Rewards

Hi Friend,
        The test programs allow you to skip certain sections of the processing chain between applications to localize errors. However, they can also be used to simulate an entire business process (for example, purchase order on the customer side with posting of the purchase order on the vendor side) in an SAP System (without any other systems). For this reason, the test programs are an important tool for configuring the IDoc Interface and defining new IDoc types.
Use
You can use the test tool to generate an IDoc manually and send the IDoc for either inbound or outbound processing. You are not restricted to a specific port type. You can start with an IDoc type (an empty IDoc) or use an old IDoc as a template and edit the IDoc, that is, add segments or change data. This is a good way to test new IDoc types, in particular.
You can forward your new IDoc for standard inbound processing (checking partner profiles and so on). You can also call a function module directly. You can therefore test new function modules for new IDoc types.
Activities
·        Start the test tool with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Test Tool (WE19). You can use a template for your test IDoc.
You can choose IDoc types as a template, either directly or according to a specific message type. You can use the F4 Help for IDocs used as a template, which searches for IDocs by selection criteria, in the same way, for example, to IDoc Display. When an IDoc file is used as a template, the IDocs are read from this file and are available to you for selection. A default value for the IDoc file gives you the system using your test port which you can enter in IDoc Administration . This test port must therefore be of the file type. The default file is the inbound file entered there.
·        You generate the IDoc using .
The IDoc is displayed as a tree structure. If you do not use a template to create the IDoc type, at least one more segment must be added.
·        To create segments in the form of tree nodes (colored fields) place the cursor on an existing node (for example a control record at the top) and choose .
You can cut, paste or copy individual segments or entire segment groups by positioning the cursor on the relevant segment and selecting the required action from the Edit menu.
·        Click on the white fields to change data in the segments.
In the case of the control record, only the fields which are relevant for standard inbound processing are displayed. Do not forget the required entries in the partner profiles if you want to send the IDoc for standard inbound processing! You can also change all of the control record data by choosing All fields in the edit screen.
In the All fields editor screen you must enter the non-language specific partner function (for example AG for vendor). This is the only screen in the IDoc Interface in which the partner function is not translated into your language (in English AG becomes vendor VD) - in the partner profiles or in the IDoc display the field is always translated. Thus, you see the partner functions here in the way they are saved in the database. This is a unique value in the SAP System and therefore protected against mistakes.
·        The additional procedure depends on whether you want to test inbound or outbound processing.
Test: Outbound Processing from MC
Use
Use this test program if you have chosen the Message Control module and want to test generation of an outbound IDoc from an existing message status record (table NAST).
Prerequisites
You must be able to post the application documents which are to be converted into IDocs by the Message Control module correctly so that a message status record can be generated. In the case of the Materials Management (MM) and Sales and Distribution (SD) components, the following entries are required:
·        Customer or vendor records
·        Material records
·        Info records
·        MC condition record: The output medium 6 (for EDI) must be entered here. The condition records are maintained as messages from the respective application.
The appropriate file ports and partner profiles must exist in the IDoc Interface.
Outbound processing must be stopped when the message status record has been generated to allow the test program to intervene. To do so, you must set the Message Control dispatch time to 1 (output with selection run) in the corresponding condition record in the application. This test program, therefore, is simply used to start a selection run which retrieves the Message Control records and sends them for further outbound processing. The program is report RSNAST00, which is also generally scheduled with dispatch time 1 in live operation.
Activities
Once the application document has been posted, outbound processing stops after the message status record has been generated and is triggered again by the test program. Choose SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from MC.
Errors are stored in the Message Control processing log (document header) and in the status records of the IDocs. The status records, however, are only available if the IDoc was successfully generated.
Use
This test program selects one or more outbound IDocs and forwards them to the external system. You can choose the IDocs according to various criteria (for example, recipient or business message).
Prerequisites
You require outbound IDocs which were generated without errors (no error status). The partner profiles, therefore, must be maintained completely.
Outbound processing must stop when the outbound IDocs have been generated to allow the test program to intervene. You can check this by setting the output mode to Collect IDocs in the partner profile for the IDoc Interface. If you now generate an outbound IDoc for the partner (for example, using the application or the test tool), the IDoc is only generated in the SAP System and is not forwarded to the external system. This test program, therefore, is simply used to start a selection run which retrieves your IDoc(s) and sends them to the external system. The program is report RSEOUT00, which is also generally scheduled with the output mode Collect IDocs in live operation.
Activities
You start the test program by choosing SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from IDoc (WE14).
You can decide whether the output mode is set to Start subsystem or Do not start subsystem in the partner profile. This defines whether the external (sub) system processes the IDocs further.
Use
This program is used to test whether status confirmations for an outbound IDoc are sent correctly from the external system to the SAP System. The port type here must be set to File.
Prerequisites
A correct status file which can be generated by an EDI subsystem, for example, is required. The status file must refer to an existing outbound IDoc in the SAP System. You can also generate such a status file yourself.
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The SAP System reads the status file. The IDoc number contained in the file refers to the outbound IDoc, to which the status confirmation relates. The confirmed statuses are credited to the relevant IDoc in the form of status records in the SAP System.
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Status ® Edit Status File (WE17) and pass the inbound port, name and directory of the file. These entries overwrite the standard values which you have stored in IDoc administration using the test port.
Test: Inbound Processing: Modified Outbound File
Use
This program converts an outbound file with IDocs to a correct inbound file and sends the new file for inbound processing. The outbound file is not modified and can therefore be used more than once. The port type here must be set to File.
Prerequisites
You need a correct outbound file, for example, a file which is generated by the test tool or using a standard outbound processing. In this case, a port of the type File must be specified in the partner profile for the IDoc Interface, so that the IDoc(s) can be written to a file.
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The program imports sender and recipient data as input parameters from the user. The program reads the IDoc file and changes the corresponding entries in the IDoc control record. The changed data is written to a second IDoc file at the operating system level.
Standard inbound processing is then triggered;
·        Reading the modified file
·        Generating the IDoc(s) in the SAP System
·        Processing in the application
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Mod. Outb. File (WE12).
Set the sender and recipient data, as well as the outbound file and the inbound file to be generated (path and name). Your entries for the inbound file overwrite the standard values which you have stored in IDoc administration.
The recipient in this case is the SAP System. The port is used for identification purposes:
·        SAP (for example RSMITH
Test: Inbound Processing: Original Inbound File
Use
This program reads an inbound file and sends the file for inbound processing. If all data has been successfully read, the file is deleted.
Prerequisites
You require a correct inbound file. In this case, correct means that the:
·        Sender and recipient in the control record are correct
·        Direction in the control record is set to 2 (inbound)
·        Client in the control record and data records are correct or empty
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The program reads the IDoc(s) from the inbound file and sends them for standard inbound processing (with processing within the application).
The file is deleted after being read successfully!
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Orig. Inb.File (WE16) and pass the following data:
·        Inbound port
·        Name and directory of the file
These entries overwrite the standard values, which you have stored in IDoc Administration using the test port.
Thanks

Send output for Changed PO

HI all,
   I am unable to re-send purchase order after making changes.
   After making changes to a purchase order (ME22N) based on either a custom field = 'X' or po total value > $100,000, i like to re-send the output via email to the vendor. In Nace, i saw this program FM06AEND and routine Change-Flag. What is this FM06AEND for ?    Also, do i need to do customization so i can re-send the output ? How does it detect my changes ?
     When i put breakpoint in FM06AEND, it does not stop there.
thanks
Joyce
Edited by: Joyce Chan on May 11, 2010 2:29 PM
Edited by: Joyce Chan on May 11, 2010 2:39 PM

For your output type you have to maintiain Print operation - 2
Follow this menu path
OLME -- >messages -->output control -- message types -->Define message type for PO --> Fine tune conterol
maintain print operation - 2 change
For the current PO ,Goto ME22n ,click message , click repeat outpout on further data tab

Sender Port Error in SAP ECC for IDoc

Hi,
I am creating scenario IDOC -> XI -> JDBC with Customer Master IDoc.
After sending it with we19 he said "IDoc sent to SAP system or external program".
In we02 and we05 the IDOC it says "Data passed to port OK".
But in SM58, the IDoc ends in error saying
Transaction IDX1: Port SAPIDST100, client 600, RFC destination contains error.
What I identified that the port SAPIDST100 is the sender port in the IDoc being send. However, for PI we do not need to maintain sender port.
Business Systems:
Sender : SAP ECC
Receiver: SAPPID
Kindly provide your inputs.
Thanks
Rahul

Hi Rahul,
thanks for the information that your scenario is working fine.
But i want to clarify some points:
 - If you send out an IDoc from an ECC system, the senderport is filled with SAP+<system-id> by the SAP IDOC API,
 i.e. if your system id is "ABC", the senderport is "SAPABC"
 => your senderport SAPIDST does not match this template, so i assume you entered the value for the senderport
 manually in the idoc test utility WE19
 - if you send out an idoc, only the receiver port must be created in transaction WE21, it is not necessary to create
 the senderport in WE21, this is not necessary and did not solve your problem
- the idoc was send from ECC (application system with application IDoc metadata) to an XI/PI system (basis system
 without application idoc metadata
 The IDoc adapter on the pi system must analyze the IDoc segments and must know the idoc application metadata,
 but this is not known. So the idoc adapter on PI side looks at the senderport to identify the sender.
 In transaction IDX1 an rfc-destination can be configured to point to the sendersystem with that senderport
 With this rfc-destination the IDoc adapter tries to read the idoc aplication metadata from the ECC system and stores it on PI side.
 If there is no rfc-destination configured in transaction IDX1 on PI side you get the error mentioned in your request.
 I assume that in transaction IDX1 somebody configured the correct RFC-Destination.
I hope this clarification helps you to understand the error and the solution.
Kind regards,
Andreas Dahl

Send Changes for IDOC ORDRSP

Similar Messages

Maybe you are looking for