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

Similar Messages

How can u creat LSMW port in Idoc Processing

how can u creat LSMW port in Idoc Processing
actullay i'm using Lsmw with bapi

Hello Ronei
             *After giving the project ,sub project ,object & short description
                  *go to menu bar click on settings in that select idoc inbound processing ,
                  *in that screen click on maintain port push button
                  *port creation screen will be displayed in that left menu expand the file
                  *after that select file_port
                  *click on copy button
                  *provide your port name
                  *provide the short description
                  *after that deselect the uni code check box
      --->*this is the main step
                 *in the directory you will provide the path of your flat file other wise your
                  project will be terminated after 13 th step .
thanks .
prasad gandepalli

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

IDOC process

gud mrng,
after creating the idoc function module,how are we writing the code?
how are we using the standard idoc?

Hi Priya ,
Check this .....
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
Reward if useful.
Regards,
Chitra

Inbound Idoc processing issues - Partner Profiles - error status 56

Hello All,
I'm having a little difficulty posting an idoc coming from MDM. It's a CREMDM04 xml coming from an MDM system. It is getting mapped through PI and is being split into ADRMAS02 and CREMAS04 Idocs. The message is being passed through XI and being posted to the ECC system, but certain fields in the EDI_DC40 header table are not being populated correctly (i believe). I'm using nothing but standard mapping/material from the SAP Business Content for XI. After looking through the standard XSLTs i cannot find the field-to-field mapping where the fields below are being populated.
The RCVPOR value (SAP[SID]) is correct when i view it in SOAP Header, but does not appear in the remote system under the receiver port for the inbound idoc.
The RCVPRN value ([String Value]) is incorrect in the SOAP Header and does appear in the remote system under the receiver partner number for the inbound idoc. How is the RCVPRN value being populated?
SOAP Header in IDocOutbound tag
<SAP:RCVPOR>SAP[SID]</SAP:RCVPOR>
<SAP:RCVPRN>[String Value]</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
I've been trying to trace down the string value for the RCVPRN, but i cannot find it anywhere. Perhaps i'm just overlooking it?
When i set the proper values (port = SAP<SIDofECC> and partner number = <LSnameof ECC>) using WE19 in the remote system then the partner profile is found and i'm left with different error to please specify an address group.
Any help is very much appreciated! :-D

Hi Jason ,
Just check out if you have done the following steps most of us make minor mistake here ....... I think this would solve your problem
To Configure the IDOC SCENARIOS ,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC INTO SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Receiving System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select Create New button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in XI towards R/3
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Inbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Message Type and Process Code.
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
do let me know if it helped
Edited by: Tom Jose on Feb 21, 2008 9:04 AM

IDOC processing speed

Dear All
Anyone have any idea how we can improve IDOC processing speed
And what are the factor that have affect IDOC processing speed
Thanks & Regards
Amit Shivhare

Hi,
1. data which is posted thru idoc
finally goes thru some standard bapi,
which ultimately posts the data.
2. bapis are standard sap code,
which do a lot of vlaidations
before putting data into tables.
3. Hence, i don't think,
we can much upon their improvement !
what are the factor that have affect IDOC processing speed?
Re: Issue of grouping IDOC segments in huge loads
Idoc Segment limit ?
It is the standard program flow of transaction WE02 which checks the number of segments.if the count is more than 1000,it creates a another group and displays it for the sake of readability.
Anyway it does not affect the inbound processing of the IDOC.
Reward points
Regards

Creation of rfilr ports in WE21 from LSMW IDOC Processing

Hi,
I am trying to defile a file port for INBOUND IDOC processing status in LSMW.
Now when I go to create a file port in WE21, I give some dummy Physical directory name. But what should I give in
Function module field and Outbound file field ? Is it compulsary to put something in these fields...
Please help.....

Hi,
Function module field is used to define the path functionality of file generated.
EDI_PATH_CREATE_CLIENT_DOCNUM is the recommned fucntion by SAP .
Function is used to prevent unprocessed files being overwritten.Tihs function generates file directory path dynamically.
Hope this helps.
Thanks.
Mark points if helpful.

After updating latest security update for my OSX 10.7.5 one of my usb port is not working now.how do i know what is cause that usb port is not working after security update

one of usb port in my macbook pro havent work after i ve updated latest security update for osx 10.7.5, how do i know what is cause that usb port is good or bad

On a Mac running v10.7.2, the only way to reinstall Safari is to reinstall OS X using OS X Recovery.
Safari 5.1.1 is for Snow Leopard. It will not run on a Mac with v10.7 installed.

What is the serialization concept in ALE/IDOC?

what is the serialization concept in ALE/IDOC?

Hi Srinu ,
IDoc Serialization means, sending/posting the idocs in sequence.
We serialize IDocs in the following cases:
· If you want the Integration Server to process the corresponding IDoc XML messages in the same sequence that it receives them from the IDoc adapter at the inbound channel.
· If you want the receiver to receive the IDocs in the same sequence that the IDoc adapter sends them at the Integration Server outbound channel.
The sequence at the Integration Server inbound or outbound channel can only be guaranteed if only IDocs are processed, and not if different protocols (for example, IDocs and proxies) are processed together.
Do not confuse IDoc serialization using the IDoc adapter with the ALE serialization of IDocs.
Prerequisites
· The quality of service EOIO (Exactly Once In Order) must be specified in the message header.
· The receiver system or the sender system must be based on SAP Web Application Server 6.40 or higher. If this is not the case, the quality of service is automatically changed to EO for compatibility reasons and the message is processed accordingly.
Procedure
If you want the Integration Server to process the IDoc XML messages created by the IDoc adapter in the same sequence that the IDocs are sent by your application, proceed as follows:
· Enter a queue name in your application. You can use 16 alphanumeric characters. The prefix SAP_ALE_ is then added.
The IDoc adapter checks the prefix and replaces it with the prefix of the corresponding Integration Server inbound queue (for example, XBQI0000).
If you want the receiver to receive the IDocs in the same sequence that they are sent by the Integration Server using the IDoc adapter, proceed as follows:
· In the communication channel, select the check box Queue processing for the receiver.
The IDoc adapter replaces the prefix of the outbound queue (XBQO) with the prefix SAP_ALE_.
You can display the individual messages in the qRFC monitor of the outbound queue. To do this, do one of the following:
¡ Use the queue ID in the list of displayed messages in the monitor for processed XML messages.
¡ Use the transaction ID in the list of displayed XML messages in the IDoc adapter.
¡ Call the transaction qRFC Monitor (Outbound Queue)(SMQ1).
To navigate directly to the display of messages in the IDoc adapter, double click the transaction ID of a message in the outbound queue.
To do this, you must have registered the display program IDX_SHOW_MESSAGE for the outbound queue in the qRFC administration (transaction SMQE) beforehand.
In both cases, the function module IDOC_INBOUND_IN_QUEUE is called, which enables EOIO processing of the messages. The processing sequence is determined by the sequence of the function module calls.
Unlike the other function modules (interface versions from the communication channel), with this function module you have to transfer segment types rather than segment names in the data records.
Serialization of Messages
Use
Serialization plays an important role in distributing interdependent objects, especially when master data is being distributed.
IDocs can be created, sent and posted in a specified order by distributing message types serially.
Errors can then be avoided when processing inbound IDocs.
Interdependent messages can be serially distributed in the following ways:
Serialization by Object Type
Serialization by Message Type
Serialization at IDoc Level
(not for IDocs from generated BAPI-ALE interfaces)
Serialization at IDoc Level
Use
Delays in transferring IDocs may result in an IDoc containing data belonging to a specific object arriving at its destination before an "older" IDoc that contains different data belonging to the same object. Applications can use the ALE Serialization API to specify the order IDocs of the same message type are processed in and to prevent old IDocs from being posted if processing is repeated.
SAP recommends that you regularly schedule program RBDSRCLR to clean up table BDSER (old time stamp).
Prerequisites
IDocs generated by BAPI interfaces cannot be serialized at IDoc level because the function module for inbound processing does not use the ALE Serialization API.
Features
ALE provides two function modules to serialize IDocs which the posting function module has to invoke:
· IDOC_SERIALIZATION_CHECK
checks the time stamps in the serialization field of the IDoc header.
· IDOC_SERIAL_POST
updates the serialization table.
Check the following link:
http://help.sap.com/saphelp_nw04s/helpdata/en/0b/2a66d6507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/78/2175a751ce11d189570000e829fbbd/frameset.htm
Ex: ADRMAS, DEBMAS(customer)
ADRMAS, CREMAS(Vendor)
In this case, Before posting Customer Data or Vendor Data it requires Address Data.
Rgds
Sree m

HT2498 how do I find out what kind of fire wire port I have on my desktop? I want to transfer video from my camcorder.

how do I find out what kind of fire wire port I have on my desktop? I want to transfer video from my camcorder.

If you have Firewire 800 it's a boxy looking port, the Firewire 400 is thinner and has a arrow looking shape, you can get a adpater.
FW800 is simply FW 400 x 2, so the adapter gives you FW 400.

What is the Difference btwn PORT and SOCKET

Hai, what is the diff. between Port and Socket and is Port related to Hardware?

Or another way, A socket is the connection you make, the port is the channel that the socket connected on.
A lot of ports are assigned to a certain use eg 80 = http. So when you try to access a web page, your browser tries to make a connection to the server on port 80, the server software will listen on port 80 on the server computer for htp request.

What is the need of xi in idoc to idoc related scenarios

Hi all,
Can any one explain me what is the need of xi in idoc to idoc related scenarios.\
we can Send Idoc with out Xi right?
Thanks,
Srinivas

IDOC to IDOC Scenario
pass through idoc to idoc scenario
IDoc to IDoc Scenario with High Volumes
SM58 Error For IDOC to IDOC Scenario

Error: Metadata EDISDEF for port SAPEC1, IDoc typ

I am getting following error in my File-2-IDOC scenario.
Could anyone please help me out?
Error: Metadata EDISDEF for port SAPEC1, IDoc typ
CREMAS04 and CIM type not maintained
I defined RFC Destination and Port properly..
Did I miss out anything.
Thanks in advance for the help.
Venu

Hi,
A few checks to be done,
1. GO to the RFC destination 9in SM59 and see if the Remote Log on and Test COnnectiivyt to the R# system works.
2. Go to IDX2 and deleted the exisitng Metadata and import the same meta data manually. IS the import succesful?
3. Check if you have entered valid POrt value and RFC destintion in IDOC adapter.
Regards,
Bhavesh

Hi guru's what is outbound program to run in idocs

hi guru's what is outbound program to run in idocs , plz help me

Hi Sri,
If u want to run outbound program for 'Z' segment and Idoc type use this type of program
DATA: Begin of imara occurs 0,
matnr like mara-matnr,
mtart like mara-mtart,
mbrsh like mara-mbrsh,
meins(3) type c,
end of imara.
data: begin of imakt occurs 0,
maktx like makt-maktx,
end of imakt.
DATA: wamas_con LIKE edidc,
imas_data LIKE edidd OCCURS 0 WITH HEADER LINE,
icom_con LIKE edidc OCCURS 0 WITH HEADER LINE.
PARAMETERS: e_matnr LIKE mara-matnr,
e_msgtyp LIKE edidc-mestyp,
e_rcvprn LIKE edidc-rcvprn.
retrive app. data from DB
SELECT matnr mtart mbrsh meins FROM mara INTO TABLE imara WHERE
matnr = e_matnr.
SELECT maktx FROM makt INTO TABLE imakt WHERE
matnr = e_matnr and SPRAS = 'E'.
*Master idoc control record
wamas_con-rcvprt = 'LS'.
wamas_con-rcvprn = e_rcvprn.
wamas_con-idoctp = 'YMATMAS1'.
wamas_con-mestyp = e_msgtyp.
master idoc data records
LOOP AT imakt.
imas_data-segnam = 'YMAKT1'.
move imakt to imas_data-sdata .
APPEND imas_data.
ENDLOOP.
LOOP AT imara.
imas_data-segnam = 'YMARA1'.
move imara to imas_data-sdata .
APPEND imas_data.
ENDLOOP.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
EXPORTING
master_idoc_control = wamas_con
OBJ_TYPE = ''
CHNUM = ''
TABLES
communication_idoc_control = icom_con
master_idoc_data = imas_data
EXCEPTIONS
ERROR_IN_IDOC_CONTROL = 1
ERROR_WRITING_IDOC_STATUS = 2
ERROR_IN_IDOC_DATA = 3
SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
OTHERS = 5
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
COMMIT WORK.
otherwise material master transfer using BD10
customer master using BD12
vendor master using BD14
Regards,
Vijay

What standards are the USB ports on a Dual 2.3 GHz PowerPC G5?

What standards are the USB ports on a Dual 2.3 GHz PowerPC G5? USB1 or USB2? If USB1, is there a card to equip the computer for USB2 or USB3?

USB 2.0. USB 3.0 is not yet supported in OS X. You can purchase USB 3.0 cards for Macs, but I don't know if they work in your slots. See www.caldigit.com, for example.
Message was edited by: Kappy

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

Similar Messages

Maybe you are looking for