Sender port in an Outbound IDoc

Hi
Can someone please mention where is configuration for IDoc sendor port.
We generally give Receiver port information in outbound parameters in partner profile(WE20). But there is no place where we give the Sender port information.
When an outbound idoc gets created, in the control records you can find the Sender port. Can someone tell from where this port is picked up.
In most of the cases I can find port name SAP<SYSID>. Is this something SAP standard. ?
Thanks,
J.

Hi Brad,
Can you tell me where its hard coded. which program/func module. ?
Thanks,
J.

Similar Messages

Sender Port in FILE to IDOC scenario

Hi all,
I am trying to do a File - SAP XI-IDOC scenario.
The idoc which is getting created in XI is having senderport as SAPABC where ABC is my XI system id.
i have not craeted this sender port and i am not able to find it in idx1 tx.code of XI.
Can anyone please tell me how and where is this port is getting created. Will it get genarated automatically by the XI system for posting the idocs?
thanks in adavance
Jagruthi

Hi Jagruti,
Please refer to these blogs and threads:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/73527b2c-0501-0010-5398-c4ac372c9692
/people/sravya.talanki2/blog/2006/12/25/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-i
/people/sravya.talanki2/blog/2006/12/26/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-ii
/people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
Hope these blogs help you.
Regards,
Sarvesh Desai

SENDING WBS ELEMENT IN OUTBOUND IDOC ORDRSP

Hi Experts,
i need to update idoc ORDRSP (to distribute Sales order) with field WBS ELEMENT , you can find this under item tab "Account assignment" field COBL-PS_POSID
I generated outbound idoc on several sales orders but none of them has this information.
do you know how to have this information populated in this idoc ?
Thanks and regards

Hi,
You need to do the following steps to create a custom segment and populate values into that:-
1. Create a custom segment using the T Code WE31
2. Add the created custom segment to the orders05 basic type by creating a new extension using WE30 transaction
3. Maintain a new entry in WE82 transaction for the message type, basic type and extension
4. Update the extension in all the necessary partner profiles WE20
5. You have lot of function exits in the function module IDOC_OUTPUT_ORDRSP, you can see them as customer function in that function module. You need to write the code in that include
6. Create a project for the function exit and activate the project.
Once you do all the above 6 steps then you can see values populated into the custom segment.
Thansk,
Mahesh.

Procedure to Error Out Outbound IDocs

Hello,
         I have a Requirement in which I am using ORDERS05 IDoc Type and extended it to ZORDER05 to populate Custom Fields and sending the Purchase Order Outbound IDoc to the Vendor from SAP System. Now, my requirement is that if any of the Custom Fields are not maintained in SAP and not populated in the IDoc, I need to Error Out the IDoc with Error Status 26. I am currently working on the SAP ECC 5.0. I have implemented similar Error Handling Mechanism earlier by using Enhancement Framework as I was working in ECC 6.0 environment where I've added the Code by Creating an Enhancement Implementation in the Function Module IDOC_CREATE_ON_DATABASE. But since ECC 5.0 does not have the Enhancement Framework feature, please let me know how to achieve this.
Thank You,
Venkata Phani Prasad K

Hi
why don't you try using the standard method for validation of data?
By implementing the customer-function EXIT_SAPLEINM_002 or BAdI MM_EDI_ORDERS_OUT you can make checks of completeness of the idoc segments (in your case, additional custom data) and, if they were not complete, report an error message raising the exception DATA_NOT_RELEVANT_FOR_SENDING
ie
if <Idoc Custom Field> is initial.
MESSAGE ID 'S1'
               TYPE 'E'
               NUMBER '333'
               WITH Additional data are incomplete'
               RAISING data_not_relevant_for_sending.
endif.
Thus you have the evidence of the error in the processing log of the output message while the IDOC is not created.
The solution works very well and is not invasive.
Regards.
Andrea

Create event Outbound Idoc

Hi Community,
I configured all to send by Nast an outbound idoc DELVRY03 message type DESADV.
Now I wish to know idoc number e its status in order to update custom table about process.
Is there some event (like Created) that I could catch after the idoc is created? Have you any suggestion to solve my trouble?
thanks in advance,
Frank

hi ,
Check in trx <b>WE05</b> for idoc list.
there u can get idocno,status,...
Cheers
ALfred
Reward points for helpful answers.

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

What is sender port in idoc control record!

Dear all
In idoc control records it is showing two ports Receiver port and sender port.receiver port we cen configured in WE21.
where we configured senderport!
how it is updated in control records!
Thanks & Regards
raj

When you generate the outbound idoc you provide info for Receipent
"control record
idoc_control-idoctp = 'ACC_GL_POSTING01'.
idoc_control-doctyp = 'ACC_GL_POSTING01'.
idoc_control-mestyp = 'ACC_GL_POSTING'.
idoc_control-rcvprt = 'LS'.           "Partner Type of Receiver
idoc_control-rcvprn = 'WCP100'.       "Partner Number of Recipient
idoc_control-rcvpor = 'WCP100'.        "Partner Port of Recipient
idoc_control-direct = '1'.             "outbound idoc
When you receive and inbound idoc you nedd to provided similar info but for Sender
Port for Sender is just like port for Receipent. Both you check in WE21.
Edited by: Marcin Pciak on Oct 17, 2008 9:47 AM

How to send Outbound IDocs through an RFC-enabled FM

Good day to all;
A partner system (AS/400) wants to use a Java Connection to execute a RFC Function Module, in SAP, that will then return a collection of IDocs.
Currently, the Function Module builds the IDocs, but I'm not exactly sure how to simply send those IDocs back to the AS/400.
If anyone can help in this regard, that would be great.
My current thoughts are to use Master_IDoc_Distribute, but then I imagine that requires a port configuration for the AS/400. And if this is the case, does that mean that SAP will send the IDocs back itself instead of using the RFC interface?

Hi Tavares,
If you want to send outbound IDoc to AS/400 (external system), you need to setup file port (t/code WE21).
For RFC interface, you need to setup RFC file port with RFC Destination (t/code SM59). In this case, SAP will send IDoc (individually or batch) to receiver system (AS/400). Perhaps you need a middleware for data transformation, if AS/400 does not perform data mapping for outbound IDoc.
For FTP interface, you need to setup flat/XML file port for outbound. then you can FTP the file to AS/400 later on.
In addition to file port configuration, you also need to setup partner profile for outbound parameter (t/code WE20) and the distribution model (t/code BD64).
Hope this will help.
Regards,
Ferry Lianto

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

Changing sender port in IDOC scenario

Hi,
i am trying to change the sender port in XI (name of the XI-System is CXE) to ZSAPCXE.
I have successfully done the mapping of the IDOC header field (populating the field SNDPOR with ZSAPCXE).
Now i have started my test scenario - sending an IDOC from source system...
In transaction SXMB_MONI i can see, that the mapping was ok (<SNDPOR>ZSAPCXE</SNDPOR>).
But if i start transaction WE02 in the target sytem the port of the incoming IDOC is SAPCXE. What is the problem?
Thanks for any help!

Thanks for your help.
So you say, there is no chance to change the sender port?
But why is in transaction WE02 in the target system the inbox port automatically set to SAPCXE?
Is there a user exit for the function module MASTER_IDOC_DISTRIBUTE or anything else available?
Is there a chance to change the sender port in the target system before processing begins automatically?
Is there no option within XI to overwrite the default?
I cant believe that...
Thanks for any ideas

IDoc Message: Invalid Sender Port in FM IDOC_INBOUND_SINGLE

Hi experts
For inbounding IDocs I use the FM IDOC_INBOUND_SINGLE.
My problem is, the IDocs always gets the status 56 with error message <Sender port in control record is invalid>.
I don't understand the message, because all ports are maintained in WE21.
When I execute BD84 for created IDocs everything is OK.
But my problem is, that I don't want to execute BD84 after every IDoc which will be created by the FM IDOC_INBOUND_SINGLE.
So could anyone help with the error message <Sender port in control record is invalid>.
Thx for every help

Hello Sachin
Thx for fast help.
However, a few minutes ago I solved the problem (debugged SAP-FM).
Problem had been, that direction was 1 instead of 2.

Trigger an outbound idoc to sender system after inbound idoc has status 53

Hi all,
We have two different partners (say A and B)which send inbound idoc to ECC of same message type WMMBXY. This updates goods movement. The partner A collects the idocs(WE20 partner profile setting) and partner B trigger's immediately. Now our requirement is after successful processing of idocs (satus 53) we need to send another type of idocs to the sender regarding the updation/ changes occured in ECC.
Since partner A collects the idocs how can we check that it reaches 53 status and send the outbound idoc to A.
Kindly help me in solving this issue.
Thanks,
Aravind

Create a new process code WMMB to ZMMB & assign a FM ZL_IDOC_INPUT_WMMBXY
& call the standard FM L_IDOC_INPUT_WMMBXY , check the status or any error other wise create a new IDOC using
Master_IDOC_CREATE, hope the solution works for you

Outbound IDOC - Sender and reciever

Hello SDNites,
I have created a report pgm which is equipped to send an outbound IDOC i.e used FM 'MASTER_IDOC_DISTRIBUTE'. Can someone please tell me how do I decide my sender and reciever when populating the control record in this FM.
I know sender will be my system and reciver will be third party system but can you please tell me what values need to be opulated there or

Thanks for the information,
Can you please give the info in following form,
1. Partner profile configuration with the values in your system.
2. Code snippet where control records are poulated for Outbound IDOC with the values you specified in step 1.
This will help me in understanding the same.
Regards,
Abhi

To send the outbound IDOC DEBMDM from R/3

Hi,
I have created an extension for DEBMDM06 as ZDEBMDM06.
Please sent me the outbound FM and the process code that is used for the above type.
When i checked with the system i got the peocess code DEBM that is relevant for DEBMAS type.
And also the transaction that is used for creating the IDOCS, because BD12 is relvant for DEBMAS idoc type.
please confirm me whether the tcode MDM_CLNT_EXTR is used for sending the IDOC from R/3.
Above mentioned is an outbound IDOC that will be sent from R/3. please suggest me some solution for solving this issue.
Thanks in advance.
Praba

Hello,
As you rightly said, you can use the Transaction BD12 to Send Customer Master Data.
However, if you have a specific requirement to add some Extended Segment / Fields, you can go for a Custom Program / Report in which you can extract all the Customer Master Data required along with the Extended Segment Fields and send it through MASTER_IDOC_DISTRIBUTE. This program can be scheduled for Background Job as and when you want.
Thanks and Regards,
Venkat Phani Prasad Konduri

Creation of Inbound Idoc for the Outbound Idoc in same client

Hi,
My requirement:
Whenver an PO is created an Outbound IDOC is generated in system ABC with client 100.I want to pass this IDOC data to create an Inbound Idoc for Sales Order(SO) in the same client.
It would be helpful if anyone can answer on how to Transfer the Outbound Idoc after it crosses the port.
I found there is a field for function module in WE21,can this be used to get the requirement done.
Please suggest.
Regards,
Amar

Example of a program that create and post an inbound idoc....maybe that will help you:
report zzinbound_idoc.
data: g_idoc_control_record like edi_dc40 occurs 0 with header line.
data: g_edidd like edi_dd40 occurs 0 with header line.
data: g_e1bpache09 like e1bpache09.
parameter: mode type c default 'A'.
refresh: g_idoc_control_record, g_edidd.
clear:   g_idoc_control_record, g_edidd.
*-Build Control Record -*
g_idoc_control_record-mestyp = 'ACC_DOCUMENT'.   "Message type
g_idoc_control_record-idoctyp = 'ACC_DOCUMENT03'. "IDOC type
g_idoc_control_record-direct = '2'.              "Direction
* Receiver
case sy-sysid.
when 'DE2'.
    g_idoc_control_record-rcvpor = 'SAPDE2'.     "Port
    g_idoc_control_record-rcvprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-rcvprt = 'LS'.             "Partner type
g_idoc_control_record-rcvpfc = ''.               "Partner function
* Sender
g_idoc_control_record-sndpor = 'A000000002'.      "tRFC Port
case sy-sysid.
when 'DE2'.
    g_idoc_control_record-sndprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-sndprt = 'LS'.             "Partner type
g_idoc_control_record-sndpfc = ''.               "Partner function
g_idoc_control_record-refmes = 'Customer clearing'.
append g_idoc_control_record.
*-Build Idoc Segments -*
*---E1KOMG
clear g_edidd.
clear g_e1bpache09.
g_edidd-segnam               = 'E1BPACHE09'.
g_edidd-segnum               = 1.
move g_e1bpache09 to g_edidd-sdata.
append g_edidd.
*-Create idoc -*
*-Syncronous
if mode = 'S'.
call function 'IDOC_INBOUND_SINGLE'
    exporting
      pi_idoc_control_rec_40              = g_idoc_control_record
*     PI_DO_COMMIT                        = 'X'
*   IMPORTING
*     PE_IDOC_NUMBER                      =
*     PE_ERROR_PRIOR_TO_APPLICATION       =
    tables
      pt_idoc_data_records_40             = g_edidd
    exceptions
      idoc_not_saved                      = 1
      others                              = 2.
if sy-subrc <> 0.
    message id sy-msgid type sy-msgty number sy-msgno
            with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
*-Asynchronus
else.
call function 'IDOC_INBOUND_ASYNCHRONOUS'
    in background task as separate unit
    tables
      idoc_control_rec_40 = g_idoc_control_record
      idoc_data_rec_40    = g_edidd.
commit work.
endif.
write: / 'Well done!'.

Sender port in an Outbound IDoc

Similar Messages

Maybe you are looking for