Outbound IDocs to XI - sent but Status 20 (error)

Hi,
the detailed error message from application log says, that a function module has to be maintained for Port <space>.
The IDocs are reveived at XI. What to do?
Regards,
Clemens

... found it myself:
In customizing
Sales and Distribution -> POS Interface -> Outbound -> Maintain Profile For POS Outbound, in the POS outbound Profile detail view, the field 'No Trigger File' has to be checked.
Now everything's fine.
Regards,
Clemens

Similar Messages

Outbound idocs getting 2 mdn messages (status 14 *success* and 15 *unsucces

Hi Experts,
We experienced an issue with Seeburger AS2. We experienced in one of our scenarios when we are receiving 2 MDNs per single outbound transaction, 1 successful and the other unsuccessful. Both MDNs holds the same DOCNUM.
Has anyone experienced this before? By looking through our past issues I can see that we experienced this before in XI. We are now using PI 7.1 and has experienced it again.

I finally fixed this! Somehow my user account only had Read permissions on the /Users/MYNAME/Library/Adobe/ folder. I gave myself R+W permissions and everything works.

How to stop outbound IDOC in PI without error

Hi,
The scenario is Idoc - JDBC and personID is unique field in database.
Now the requirement is, in some cases personID generated after certain process or I can say in some cases personID is not present when this interface runs.
Now I need to stop outbound Idoc in PI system (without any error) if perosnID is not present. Means I dont want to send any data to database if personID is not present. Is there any way to accomplish this task?
Regards,
Chintan

Hi All,
Thanks for replying with very useful information and answers, really appreciated.
I am able to solve this issue by using Node Function at Message Type level. I created following condition at message type level.
personID -> removecontext -> Equals -> 0001 -> removeContext -> createIf -> receiver MT
Here i've to use removeContext two times because the segment which contains personID field is repeated many times so I've to check in each segment.
If this condition fails (if personID is not present ) then the target message structure is not going to be created.
Thank you once again.
Regards
Chintan

ALE IDOC : Probelm in outbound idocs.

Hi,
I am sending an outbound idoc from system A to System B. In we02 i see the idocs are generated successfully with *Status 03 Data passed to port OK.
*With message "The IDoc was sent to an SAP system or an external program via a transactional RFC."
"The TID is xxxxxxxxxxxxxxxxxxxxxxxx'.
But the Idocs have not reached Sytem B.
I checked SM58. Here I see the for TID xxxxxxxxxxxxxxxxx
the below message
"ALEREMOTE | IDOC_INBOUND_ASYNCHRONOUS | SYSTEMB 'No authorization to send IDocs with message type'
*I have send the same IDOC from SYSTEM C (Sandbox) to SYTEM B. *This works and the user profile is same in SYSTEM C and *SYSTEM A.
I am not able to trace the probelm. Can somebody help here.
Also if anybody can help me understand what happens when a outbound idoc is susccessfully processed with status 03.
Is there a program that processes the idoc after status 03 using TID no.
Please help

hi martin,
when i send it from system c (sandbox) with same user the idocs are not in error. but when i try to post the same from system A with same user with same profile(already checked with basis) the error occurs.
can give some hints what could be the reason.

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

Convert custom outbound idoc to CSV file

Hi
I need to send generate a flat file that will be sent to a non SAP partner. A requirement is that the messages go via the IDOC system. This makes it possible to resend them if necessary.
So there are 2 stages
1) create IDOC. I have done this
2) read IDOC and convert to flat file
stage 1
=====
I have defined a custom IDOC, partner profile etc and developed a Function Module to create the outbound IDOCs The FM is triggered by a message in the NAST table. . This works OK.
So I now have custom outbound IDOCs in the DB with status 30 (ready for dispatch) (WE05).
Stage 2
======
Now I want to convert these custom IDOCs into simple flat files (CSV like).
How do I go about making this happen? I guess I need to develop another Function Module. But I dont know how to tie this FM into the system. My questions are:
How will the FM be triggered
what is the interface of the FM
will I need to configure a 2nd partner profile for stage 2 (which is fine)
Peter
Note1 - there is no EDI converter available so must solve this in ABAP
Note2 - I do not want to create the flat file at the same time as I create the IDOC. This would defeat the purpose of going via IDOCs

No, EDI is only one method of transferring data. There's no need for an EDI subsystem in this case.
To the OP, since it seems the you have decided that you must use IDOC processing in this case, I would go ahead and use a file port (or an XML port). You will drop an IDOC formatted flat file into the specified location (for each IDOC, based on your logical file definition). For you, this will merely be a temporary holding location. You can then use a simple program to read the file, re-format it, send it, then move the original file to a 'processed' location. Of course, you could also just throw away the generated files and read the IDOCs directly with the standard functions available and (re)generate/send the files as required.
It's often done this way with 3rd party EDI providers, where the company in question is required to use EDI by their customers but do not have the required systems in place.

SAP IS Retail Outbound Idoc Creation for New Articles

Hi SAP Gurus,
Good day!
I would like to inquire if you are familiar with the necessary set up to create OUTbound Idocs to be sent to POS whenever a new article is created. I have already activated the Change Pointers for the Message Types for IS Retail via BD50. However, this did not solve the issue. I have an existing material which ably triggers the idoc change;however, when I try accessing the materials I created recently, no idocs are created.
Your help is most appreciated.
Best regards,

Hi,
Check in WE20 partner profiles > customer type KU - Customer > choose your store number > under outbound parameters all relevant message type must defined
Look at the following links for more details:
http://allian.uclv.net/saphelp/helpdata/EN/50/94f500470e11d1894a0000e8323352/frameset.htm
http://allian.uclv.net/saphelp/helpdata/EN/50/94f500470e11d1894a0000e8323352/frameset.htm
http://allian.uclv.net/saphelp/helpdata/EN/50/94f500470e11d1894a0000e8323352/frameset.htm
http://allian.uclv.net/saphelp/helpdata/EN/50/94f500470e11d1894a0000e8323352/frameset.htm
Hope you got answer
regards
Satish

Attaching Error Status to Outbound IDOC. ?

Hello Experts,
We have a scenario in SAP PI / XI were upon creation of a Sales Order , Purchase Order or Material Master Flow to Non-SAP System through SAP PI/XI , the IDOC shouldn't flow to SAP PI following a validation on Material Group.
The IDOC is triggered through Output Type , there is a custom Z function module which create outbound communication IDOC. This output type is attached to a Process Code ZSO, ZMPO defined for respective scenarios defined above.
Currently i am attaching the the status = 07 to control data structure & the IDOC is getting created but is having error.
Is this the right practice to follow for attaching error message Outbound IDOC.
Awaiting for your response.
Best Regards
Priyesh Shah

It depends on the business requirement.
in a previous project, if there was any error during the validation of the data within the iDoc before it is created and sent, i would trigger an error and send the error to the person who created the data with the error for them to correct. they would then correct the error within the document and save and the iDoc would be triggered and sent correctly.

How to Reprocess Outbound Idocs in Status 02 (Errors)

Hi,
    I have an urgent problem. How do I re-process an Outbound IDoc in Status '02' (Error Passing Data to Port)
    I have tried reprocessing this IDoc through BD87 using both the options Edit>Process and Edit>Restrict and Process, but it doesn't work
     Please help as we are migrating cutover data from SAP to another system
Regards,
Aditya

Worth to have a look at this thread
Error handling problem with outbound idoc status 02 and XML HTTP Port
Regards
Vivek
Reward points for all the useful answers

PO is getting created but showing error is address with status of IDoc - 51

Hi Experts,
I am using IDoc type - PORDCR103
Process code - copy of IDOC_INPUT_PORDCR1 (Function Module)
After processing through WE19 it is generating an IDoc number with status - 51 showing error in Address , But it is creating a PO.
My requirement is In status -51 It should not create PO.
Inside IDOC_INPUT_PORDCR1 a Bapi 'BAPI_PO_CREATE1' is used for creating PO. Here In RETURN parameter of BAPI a Row is comming with Message type - E. Some other messages are also there of type 'S' and 'W'.
After processing , PO is getting created with staus - 51.
Please help me .
Thanks
Susanta
Edited by: Susanta22 on Oct 11, 2011 12:29 PM

Hi,
in ur code ur filling the idoc data rcord, control record ryt ..before u append data to idoc data , u r also validating and u might be doing in loop for appening the idoc data.
if there is any error in idoc then it won't distribute the data, it will be in error status only..u can only see the data in WE02. Then u can also change the data in WE02 and redistirbute it via BD87.
if u have any conerns let me know
Regards,
Nagaraj

Idoc- can we sent already sended idoc if status is showing error message

hi
Idoc- can we sent already sended idoc if status is showing error message
without making any changes.
Thanks in advance.

Hi raja,
IN BD87.
give the idoc number,its status,messagetype and partner system and resend it.
Regards,
nagaraj

Outbound IDoc Error: Status Code 37 'Sender Port' is invalid

Hi
I have an Error when the Outbound IDoc is triggered.
It shows that 'Sender Port in Control Record is invalid'.
Status Code: 37.
I know that there are some issues with the Sender Port Definition.
Please help me out to solve this problem using some checkpoints at each and every step.
Reward Points Assured.
Regards,
Baburaj

Hi Baburaj Manickam
Good
Follow this simple procedure
1) Send an outbound IDOC data(MATMAS) to a flat file on client1(SENDER).
- Create File Port (WE21) for outbound file.
- Maintain Distribution Model (BD64) for sender ->receiver system.
- Create Partner Profile (WE20) for logical system.
- You can use this program RBDSEMAT (t/code BD10) to generate IDoc MATMAS file(s).
_ Then you can FTP the file(s) to receiver system.
2) Upload the flat file as an IDOC on the inbound sytem
which is Client2(RECIEVER).
- Create File Port (WE21) for inbound file.
- Maintain Distribution Model (BD64) for receiver -> sender system.
- Create Partner Profile (WE20) for logical system.
- You can use this program RSEINB00 to upload IDoc MATMAS file(s).
INBOUND IDOC PROCESSING:
Firstly attach your idoc to a process code.
In the process cod you can tell the system that the specified program should be triggered whenever an idoc of that type comes to the system.
Then you want to have a Z-function module for your idoc processing, if I understand correctly.The steps should be:
1. Create a z function module for idoc inbound posting (copy from a function module idoc_input_*).
2. Set Function Modules as Inbound: - Transaction BD51
3. Assign Function Modules to Logical Messages and Idoc types:- Transaction WE57
4. Create process codes : Transaction WE42, and link the z-function module.
5. Create partner profile: transaction WE20 and attach the message type and process code.
6. In the Z- function module, extract data from the idoc segments, do whatever processing you want to do, and then call BAPI_CREATE_SALES_ORDER_FROMDAT2.
Try the Trasaction WE19 for testing your inbound and outbound IDOCs
Good Luck and Reward me for the same
Thanks
Ashok.N

Outbound IDoc Error status 26

Hello All,
I have got one issue in outbound IDoc scenario. ( Basic type is ORDERS02 ). The IDoc failure status shown in WE02 as 26 (Error during syntax change of IDoc outbound). To solve this I am trying to Repeat Output through VA02 ( as this is related to salesorder) , it does not give the same error status 26 . Rather it gives status as 30 i.e. IDoc Ready for dispatch which I then process through BD87 gives status 03 i.e. Data passed to port OK .
I repeted this for 4-5 times, everytime I do not get any error status (as that was occured at the very first time) .
Kindly suggest what should be done to overcome this.
Thanks in anticipation...

Hi Ubhaka,
In that case you should check the segments associated with the message type.Also, check the partner profile settings.
At first (when you got the error) what was IDOC generation method - was it through VA02 or some custom/standard program? If the methods were different for generating Idocs then check the program.
Hope that helps!
Regards,
Saba

How to update the status of Outbound IDOC in case of error

I want to know about how to update the status of Outbound IDOC in case of error.
I am using message control functionality here.

HI,
If u r using the standard message and basic type
u can do it in the FM attached to the basic and message type.There u need to write ur own message instead of standard SAP message..chek if there r any userexits available in the FM..where u can overwrite ur own message ..
If u r using the Zmessage and Zbasic type
then u need to declare an internal table of EDIDS structure and then append ur message to the internal table..
idoc_status-docnum   = idoc_contrl-docnum.
idoc_status-msgty    = <message type>
idoc_status-msgid    = message-id.
idoc_status-msgno    = message-number.
idoc_status-msgv1    = message-message_v1.
idoc_status-repid    = sy-repid.
idoc_status-status   = <give the error status>.
APPEND idoc_status.
Reward if u find useful
Regards,
Nagaraj

Custom error in outbound idoc FIDCC1

Hi all,
I am generating outbounds idocs for FI documents and i need to put some of them in error. I need the FI Document created and the idoc in error so that i can reprocess it later. To do that i am using the User Exit EXIT_SAPLF050_007
Enhancement - F050S004 FIDCMT, FIDCC1, FIDCC2: Change outbound IDoc/do not send
""Lokale Schnittstelle:
*" IMPORTING
*" VALUE(MESSAGE_TYPE) LIKE EDMSG-MSGTYP
*" TABLES
*" IDOC_DATA STRUCTURE EDIDD
*" CHANGING
*" VALUE(IDOC_CONTROL) LIKE EDIDC STRUCTURE EDIDC
*" VALUE(DISTRIBUTION) LIKE BOOLE STRUCTURE BOOLE
*" OPTIONAL
IDOC_CONTROL-status = '26'.
The problem is that in the UserExit i set the Idoc Status to some value diferent than 3 (Data passed to port OK) but finally the idoc is created with the status 3.
Does anybody know how to change the idoc status in the creation from 3 to for example 26 or 27? ( an error idoc status ).
thanks!!

Hi,
In the partner profile, set the option as Collect IDOC's option.
Create a background job in which the first step of that should be your custom program and the second step is RSEOUT00 program.
In your custom program, validate the idoc if you feel your idoc is correct then leave it like that and if you feel there is some problem in the idoc then flag that error idoc for deletion that means that error idoc will not be sent to your partner.
For flagging an outbound idoc to deletion is nothing setting the idoc status to 31. This you can do with the program RC1_IDOC_SET_STATUS.
Thanks,
Mahesh.

Outbound IDocs to XI - sent but Status 20 (error)

Similar Messages

Maybe you are looking for