IDOC PORTS

Hi,
what r the different types of ports in idoc.
how to activate change pointers globally?
differnt types of IDCOS ?
what is difference between basic idoc and communication idoc?
with regards'
m.srikanth.

hi,
1) A port is a logical representation of a communication
channel in SAP, with the data communicated being IDOCs.
The process flow depends on the port type. Port types are file, trfc, CPI-C, Internet, Programming Interface, XML.
2) To activate change pointers generally, go to BD61 and check the checkbox Change pointers activated - Generally and save.

Activating Change Pointers
Change pointer generation has to be activated at both the
general level and message type.
1) Goto BD61, check the checkbox Change pointers activated - generally.
2) Save
3) Goto BD50, Choose the row for message type MATMAS, and check mark the corresponding field
4) Save
Converting change pointers to IDOCs
Create, change or mark for deletion materials using
transaction MM01, MM02, or MM06.
Execute transaction BD21
Enter Message type MATMAS
Execute
You can see tha changes gets reflected in 810 client that are done in 800 client.
Regards,
sailaja.

Similar Messages

PI: File to IDOC port is empty in R/3 system

Hi,
We send an IDOC from PI. We can see the IDOC in R/3 (WE20) but the "port" is missing under "recipient infromation", there is no character in there. The other fields are all set. Where we have to set our port? In the communication channel is nothing to set.
Thanks
Ronny
Edited by: Ronny Pol on Feb 12, 2010 4:22 PM

No, we are not populating control record data in PI. We deactivated these fields...
Then I guess its unable to pick all the information(regarding sender/receiver port) from standard configuration.
Check the configuration once again that you have done(Abhijit's post above states the steps).
or
If you have time try the approach to populate EDIDC40 node in mapping and checking the option(Apply control record data from payload) in receiver IDOC channel.
Regards
Soumen...

File- idoc, port in control segment not being populated

Hi guys,
I have a file->idoc scenario. Everything works fine, but the receiver port in control segment of idocs has no value. I'm surprised, because this is provided in the Idoc adapter so I thought it is taken from this parameter.
Any ideas, what could be wrong?
Thank you,
Olian

You pls set the indicator - Apply Control Record Values from Payload
If you set the indicator, the conversion of communication parties to the IDoc partner is only possible for systems that are not logical systems.
If you do not set the indicator, all combinations of communication parties and services are handled as services without party.
If the IDoc XML structure contains a control record during outbound processing on the Integration Server, it is rejected and created again by the IDoc adapter. If you want to include additional values in the control record, set the indicator and provide an appropriate mapping for the values
http://help.sap.com/saphelp_nw70/helpdata/EN/96/791c42375d5033e10000000a155106/frameset.htm

IDOC - PORT

We are generating Order05 IDOC and based on a particular condition some IDOCS are needed to be released to Receiving Partner otherwise they need to be collected in the Batch file for Processing.
Immediate Idocs needs to go to the PORT1 and Batch IDOCS needs to go to the PORT2
We have written a Z abap program to meet the above conditions, but our ABAPer says that its not Possible to send the IDOCS to two different Port condition?
Wheter ALE never allow to send an IDOC to more than one PORT?
Thanks.

Hi,
I think you are using Z program to trigger IDoc?
Configure 2 different ports and assign partner profile , while creating you can use partner type LS and for other use US.
then use following fm and fill up the control record with port 1 and call fm
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
EXPORTING
master_idoc_control = idoc_control
TABLES
communication_idoc_control = t_comm_control
master_idoc_data = t_idoc_data
then refresh the control record and fill with port 2 and call fm
aRs

Inbound Idoc port ???

Hi All,
I am working on proxy to IDoc_AAE scenario. Can anybody tell me from where inbound Idoc will take port?? I have imported inbound parameters in respective partner profile, but not sure from where this idoc is picking port value. Kindly suggest.
Thanks & Regards,
Rashmi Joshi

Hello,
If you already know the port no , you can do that by filling the EDIDC Segment of the Idoc .
Else the Idoc will be sent via the RFC destination configured in the rcver idoc channel
and during the TRFC call system will check for the existing partner profile (the entries set up in we21).
hope this helps .
rgds
Kishore

IDOC Port defnition *** Urgent***

Hello Gurus,
Could you provide me steps on how to define port and partner profile for IDOCs...
Any help would be highly appreciated.. and points will be rewarded generously..
Thanks and Regards,
Pavan P.

Hi Pavan,
The Port Definition
Transaction: WE21
Path: From the ALE customizing in IMG, choose Sending and Receiving Systems,
Systems in Network, Asynchronous Processing, Assigning Ports, DefinePort.
A port defines the medium in which data is exchanged between the two systems. In the ALE
process, IDocs are transferred via memory. As of release 4.6, six port types are available.
--Transactional RFC (tRFC) :ports used for ALE communication
-- File ports :used by EDI
-- CPI-Cports :used to communicate with R/2 systems
-- Internet ports :used to connect with Internet applications
-- ABAP-PI :ports used to process data via the ABAP programming interface
-- XML ports : used to process files in XML format
NOTE: For port definitions to be generated automatically, the RFC destination
name must be the same as the logical system name.
Port definitions are client-independent objects. The tRFC port used in the ALE process can be
generated automatically when you generate partner profiles, or it can be maintained manually.
Reward with points if helpful.
Regards,
Vijay

IDOC- PORT CREATION

Hi all,
1. How to create the port.
2.wats the need of creating port.
3.port has to created for outbound or indound .
please give me the relevent answer.

Hi surprith,
check this..
Port Definition
The port definition defines the medium in which data is exchanged between the two systems in the ALE process, IDocs are transferred via memory. Six port types are available.
     Transactional RFC (tRFC) ports used for ALE communication.
     File ports used by EDI
     CPI-C ports used to communicate with R/2 systems
     Internet ports used to connect with Internet applications
     ABAP-PI ports used to process data via the ABAP programming interface
     XML ports used to process files in XML format.
Port Settings
Implementation Guide for R/3 Customizing (IMG) - Basis Components - Application Link Enabling (ALE) - Sending and Receiving Systems - Systems in Network - Asynchronous Processing
- Define Number Range for Ports
- Define Port
Transaction:   Port Definition     WE21
Port Definition
The port defines the technical characteristics of the connection between SAP and the Subsystem. It also defines the medium in which data is exchanged between the two systems. In the EDI process, IDocs are transferred to external systems via ports. The EDI processes use the file port. The type of port also depends on the receiving side. If the receiver cannot accept data in the medium used by a port, the port cannot be used. For example, the tRFC port cannot be used for EDI unless the receiving subsystem has support for tRFC.
Types of Ports
Port     Function
Transactional RFC     Used for ALE Communication
File     Used by EDI
CPI-C     Used to communicate with R/2 system
Internet     Used to connect with Internet Application
ABAP-PI     Used for Custom IDoc processing via ABAP Programming Interface
XML     Used for processing files in IDoc/XML format
A port is a client-independent object. The parameters specified for port definitions are
     Port: The port name is any meaningful name that uniquely identifies the port.
     Description: This is for documentation purpose only.
     Version: The internal structure of the IDoc has changed in every major release.
     Message Edited by
shibu kurian

Idoc - port xml

hi people,
I have an internal table with 1308 entries. I divide it in internal tables with 300 entries that i send through an idoc in xml format. I run the report but seeing in we05 only i send 3 idocs when should be 5 (4 of 300 segments and 1 of 108). Well, i decide debugg and see possibles errors. I have not found any, i go to we05 and i can see 5 idocs! what?
I repeat this process twice. Is it possible that when I try to create 5 idocs by the xml port is saturating this and it send only 3 and when I debug i am giving time to allow to create 5 idocs?

Hi Manel,
To confirm that this might be an XML port problem,
why don't you create a dummy file port in we21, attach it for your scenario in WE20...and test the program again...
Please verify that all 5 required idocs are created in this case without debugging....
Thanks,
Renjith

Port Concept in File to Idoc Scenario

Hi All,
i have some doubts in File to Idoc scenarion.......... for sending file i m using Business Service. In adapter specific Identifier i have "FILE".
1. So i hv to configure partner profile with this name.......... M I Right????
2. At my receiver side (R3) i have many ports configured for XI. so which one will be used to post idoc???
Thanks,
Maheshwari.

> 1. So i hv to configure partner profile with this
> name.......... M I Right????
U are correct. You need to create a Logical System Name on R3 for this in BD54 and then add the inbound partner profile entry in We20.
> 2. At my receiver side (R3) i have many ports
> configured for XI. so which one will be used to post
> idoc???
As it is a File to Idoc, ports on R3 do not matter. You need to create a port in IDX1 in XI.
Regards
Bhavesh

What is CPI-C in "Ports in Idoc processing (we21)?

Hi all,
CPI-C is below file in the tee on left pane. What is it? Please explain in layman terms also and if possible point me to related files or threads.
Thanks,
Charles.

Hi,
Ports are a logical representation of the communication channels in SAP R/3.
There are defined types of IDoc port:
1. tRFC Ports: For ALE Purpose
2. File ports: For EDI
3. ABAP-PI: For internal use
4. XML: For exchanging in XML Format
5. CPI-C: For connecting to R/2
ALE can use all port types to distribute IDocs.
You use the port maintenance in the IDoc adapter to establish an RFC connection to the system that contains the metadata that the IDoc adapter requires to convert IDocs (Intermediate Documents) that have been sent to it to IDoc XML format. This system is defined by the sender port and the client in the IDoc control record. It is either the sender SAP system or an SAP reference system.
You must maintain a port in the IDoc adapter for all clients in each SAP system that you want to connect to the Integration Server using IDocs.
This is also the case for receiver systems if they are subsystems (non-SAP systems). Systems of this kind are defined using the receiver port in the respective communication channel.
http://help.sap.com/saphelp_nw04/helpdata/en/3b/beb13b00ae793be10000000a11402f/content.htm
Regards,
Ferry Lianto

Ports in IDOC Processing

I have been exporting IDOCs out of an RFC port (WE21) and it has been in a certain format. Now I need to use the file port (WE21) and the formant is different. Is there a way to make the file port have the same layout as the RFC port?
The differencenes are...
RFC --- FILE
E1RDID --- E2RDID000
plus on the column placements are different.
If anyone can help, I would appreciate it.
Thanks
Skip Ford

Hi,
Ports are a logical representation of the communication channels in SAP R/3.
There are defined types of IDoc port:
1. tRFC Ports: For ALE Purpose
2. File ports: For EDI
3. ABAP-PI: For internal use
4. XML: For exchanging in XML Format
5. CPI-C: For connecting to R/2
ALE can use all port types to distribute IDocs.
You use the port maintenance in the IDoc adapter to establish an RFC connection to the system that contains the metadata that the IDoc adapter requires to convert IDocs (Intermediate Documents) that have been sent to it to IDoc XML format. This system is defined by the sender port and the client in the IDoc control record. It is either the sender SAP system or an SAP reference system.
You must maintain a port in the IDoc adapter for all clients in each SAP system that you want to connect to the Integration Server using IDocs.
This is also the case for receiver systems if they are subsystems (non-SAP systems). Systems of this kind are defined using the receiver port in the respective communication channel.
http://help.sap.com/saphelp_nw04/helpdata/en/3b/beb13b00ae793be10000000a11402f/content.htm
Regards,
Ferry Lianto

How can I convert IDoc in XML format w/DTD into a string?

I want to send by e-mail outbound IDoc in XML format with its document type definition (DTD).
I want to be able to get the same output result into a string than the XML file IDoc port type with DTD activated. I have created a FM (based on SAP "OWN_FUNCTION") assigned to an IDoc port of type ABAP-PI that executes the following processing steps:
1-Extract outbound IDoc information to get the sender & recipient mail addresses (EDP13 / EDIPHONE tables).
2-Convert & Transform IDoc data into XML string using FM IDX_IDOC_TO_XML.
3-Prepare and send e-mail with XML attachement using FM SO_NEW_DOCUMENT_ATT_SEND_API1.
I cand generate the e-mail with the XML file attachement but FM IDX_IDOC_TO_XML does not convert the IDoc with proper formating and DTD.
What should I use to accomplish the IDoc conversion to XML w/DTD into a string?
Should I use XSLT tools ?
How does that work?
Thank you
Carl

muks wrote:
Use decimal string to number
Specifically, you can define a constant with a different datatype on the input on the lower left if you need a different datatype (e.g. U8, I64, DBL, etc) Are all your values integers or do you also need to scan fractional numbers? In this case, you should use "fract/exp string to number" instead.
LabVIEW Champion . Do more with less code and in less time .

JDBC to IDOC Error

Hi Guys
On my Scenario Jdbc to Idoc (Asynch) I am using FLCUSTOMER_CREATEFROMDATA.FLCUSTOMER_CREATEFROMDATA01
as a Receiver Interface, now when testing on the sxmb_moni I get two flags the Black and While and the Red the one the is Back and While shows that the Sender is my JDBC Adapter which is right
but now the Red flag show that the Sender is IDoc(FLCUSTOMER_CREATEFROMDATA.FLCUSTOMER_CREATEFROMDATA01) is also Sender of which I used it as a Receiver Interface, I dont know how to stop this IDoc Adapter not to send but to receiver.
Basical my scenario is meant to create an IDoc but is is not doing it when going to TCode WE02/WE05 I get message : "No IDocs selected"
Thanks
Yonela

Hi
I don't have any conditions, to Send and Receive, by the way I went to TCode IDX5 my Outbnd is right but Inbound thats where I get the below error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error
I have done these:
SM59- To Create RFC Destinations
WE21- To Create IDoc Ports
SALE- To Create Logical System
WE20- To Create Partner Profiles
IDX1- Port Maintenance in IDoc Adapter
IDX2- Metadata Overview for IDoc
On the ID I created the the IDoc Receiver:
RFC Destinatin: IDOC_RECEIVER
Interface Version: SAP Release 4.0 or Higher
Port: SAPPI1
SAP Release: 701
What could be the problem
Thanks,
Yonela

Creation of sales order using inbound idoc

hello all,
         I have a scenario where i need to read data from a flat file, then create a sales order with the flat file data using IDOC. we can also create sales order using BAPI but the problem is that we need to handle serveral errors so we want to use IDOC.
       we are trying to use the function modules 'Idoc_input_orders' but we are not sure how exactly we need to pass the parameters into the function module, actullays data control structure is asking for different parameters like partner, idoc number, idoc port etc which we need not have as we are processing it internally in the same system.
    It would be great if some one could help me regarding.
Thanks
krishnam raju N
Message was edited by:
        krishnam Raju N
krishnam Raju N

Hi,
see FUNCTION 'IDOC_INBOUND_FROM_FILE'
Regards,
Clemens

IDOC to and from eternal system

Hi All,
I've following scenario:
Sender SAP R/3 system is sendind IDOC of type say A to XI system, XI system is mapping IDOC of type A to say IDOC B, then finally XI is sending IDOC B to receiver SAP R/3 system [External system}
Note: Reverse scenario is also there in which we are receiving IDoc from external r/3 system and mapping it to different IDOC in XI then sending to SAP System.
Development done so far:
ID:
I've imported IDOC A in XI. SInce I didn't had authoriztion to import IDOC B from target so I asked client to provide XSD od IDOC B.
I created one inbound message interface using IDOC B XSD and also completed the mapping part using same XSD.
IR:
I've created one IDOC receiver communcation channel for external system. I completed the configuration
ALE:
I've created on RFC destination of type 3 to connect external SAP system. I created port in IDX1 for IDOC communcaition.
Problem:
When I am sending IDoc to exxternal sap system then message is getting failed in moni. IDoc adapter is not accepting the message interface creted based on IDoc XSD.
I believe I need to import IDoc meta data from target system for IDOC B. since in XI i didn't imported IDOC instead I used IDO XSD.
it may be the reason.
Please help me to solve the problem

HI Experts,
I am doing testing of my scenario.
As I've described the scenario in my last post. I am sending a IDoc A from my sender system and traslating it to IDoc B in XI, then sending it to the external SAP system (SAP 4.6). Basically IDOC XI IDC scenario but with the slightly change of converting one idoc to other.
During test:
I received following error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>I::000</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: I::000</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Trace:
<Trace level="1" type="T">Parse XML-BODY</Trace>
<Trace level="1" type="T">Get the Metadata for port SAPLSD</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
I've created one idoc port in XI named 'SAPLSD' inside I've used RFC destination to the target system. During runtime metadata is not loaded in IDX2.
When I tried importing metadata manually, i received the following error
"No RFC destination is maintained for the port"
is there any particular naming i should use for idx port and for rfc destination??
what could be the problem?? ....
Q. is it because of the RFC destination is not OK or
Q. the I do not have proper authoirsation to import metadata from LES system or
Q. Since target system is SAP 4.6 system.... is it could be the problem? [Unicode]
Please suggest

IDOC PORTS

Similar Messages

Maybe you are looking for