No IDOCs sends or receive in DES

I got a big trouble in DES.
I'm trying to send an Idoc from an html page that basis guys gave me long time ago. The error is:
Result:
http-Status: 500 <SAP:Error><SAP:Category>XIServer</SAP:Category><SAP:Code>INTERNAL.SLD_NO_OWN_BS</SAP:Code><SAP:P1>XID</SAP:P1><SAP:P2>100</SAP:P2><SAP:Stack>Error while reading the ID of own business system from the SLD for system XID and client 100</SAP:Stack></SAP:Erro
Payload:
When I do the same thing in QAS, the IDOC is sent succesfull, but in DES I got that trouble, so I descart any possibility of any error of mine.
Another guy tries to sent it by XML Spy and he has the OK response from XI but the IDOC dont come here.
Basis guys put down DES and then they put it up, and nothing happens.
This is not a sender problem because I try to sent idocs from diferent services to SAP, and I got the same result.
Any brain guy knows what is my problem? What can I do? Because we cant test anything in DES until this problem is solved

Hello Siva, thanks por the answer.
Please note that everything was working fine, but from a moment to other this problem appears.
I could send and receive IDOCs in XI because I just change the prim. in TC SLDAPICUST. I dont know why or how this works, but it gives me some fresh air here.
By the way, the main problem of this post still exists.
If anyone wants, have a look at this image:
http://img150.imageshack.us/img150/7118/1509pf6.png
Note that when I click on details of the question "Is web service security available?", the next sentence appears:
"Communication error Proxy calls on the sender or receiver side are not permitted on the IS (client)"
Any idea?

Similar Messages

Can IDoc sender and receive system be the same client?

thanks.
I think one client can't assign to two logical system.so?

Can IDoc sender and receive system be the same client?
yes
Regards,
Prateek

Multiple Message Mapping with same Idoc, Sender and Receiver

Hi,
We have one Interface sending INVOIC02 Idoc from SAP R3 4.6C to SAP R3 4.6C through XI 3.0.
On Inbound side we are using SAP standard configuring one Partner Profile with inbound INVOIC MM process code INVL.
In customizing, we have defined one invoic type for the EDI partner.
Now we have to integrate another type of inbound invoic, but in customizing it's not possible to assign more than one invoic type to the same Partner EDI.
So, we have a restriction in SAP 4.6C inbound standard. On the other hand, we can't desing two Integration Scenarios in XI 3.0 with the same idoc INVOIC02, for the same sender service and receiver service because Integration Directory doesn't allow to create two interface determination for them.
We are thinking on using header mapping in XI (receiver agreement to avoid use the same EDI partner profile for the inbound invoic, but we can't assign the same client and technical system with the same ALE Logical System in SLD for two different business systems.
Does anybody have any solution for this problem, SAP side or XI side?.
Thank you
Best regards
Luis

Hi!
In XI configuration - interface determination, you can specify more than one Inbound interface. If you identify more than one, you get a new column where you specify condition (xpath) for selecting between the different inbound interfaces.
In 4.6c, you can have more than one inbound invoic for the same EDI partner profile, if you separate between them using message function. Just add a new inbound parameter with a different message function, or copy the one you have and specify another message function, i,e. "DIFF".
Hope this helps.
Regards,
Oeystein

Sender and Receiver IDOC config Settings

Guys I have just come up with this document as a quick reference guide to enable me to be able to configure IDOC scenarios quickly and efficiently. Couls you please let me know if this looks ok and all is in the correct order.
Quick Guide to Scenarios
Note A Ports only purpose is to allow either the SAP R/3 Backend system to establish an RFC connection with XI or allow the XI to establish an RFC Connection with the Receiver SAP R/3 system.
Note An RFC Destinations purpose is to: A) Communicate with the SAP system
B) Pull metadata from either the Sender/Receiver SAP R/3 System or another reference system that contains the same IDOC.
Sender IDOC Scenario
When configuring an IDOC Sender adapter there are a few things that you need to configure before you even start with the Config Directory itself.
Because IDOC Adapter resides on the ABAP stack no sender agreement or sender Comm Channel is necessary
Your main configuration is in R/3. You configure R/3 to send the IDOC to XI so hence you dont need an IDOC Adapter or Comm Channel.
1. You need to define an RFC destination to XI in the R/3 Backend system. (SM59). This RFC destination is used to retrieve the IDOC metadata from the sender system. The IDOC adapter needs these metadata to create the corresponding IDOC-XML message from the RFC stream.
2. Assign the destination to a Port in the R/3 Backend system (WE21)
3. Define your Partner Profiles for the IDOC you are trying to send and Reference that Port there as well (WE20)
Based on the above conditions, you do not need a Sender Comm Channel for IDOC or a Sender Agreement for the business scenario. Your only configuration in the Config Directory is to define R/3 as a Business System (no Comm Channel) and define the Receiver Business System along with the Receiver Determination, Interface Determination and Receiver agreement.
I'm not sure if this step is necessary in the sender IDOC scenario -
In XI box you must also define the ports in IDX1 which allows you to establish an RFC connection to pull the metadata in from the backend system, by specifying the RFC destination from where you want to get the info from. 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.
There are certain cases which you also need to use IDX2 (Cache). XI itself does need the IDOC metadata to execute the interface but it can usually use IDX1 to pull this data either from the SAP R/3 system or an equivalent reference system. However if there is already cached metadata and the IDOC has changed then IDX1 will not execute. In this instance you can pull this metadata manually using IDX2 (XI Box).
Receiver IDOC
When you receive an IDOC things are a little more complex. You do need a Sender agreement and Comm Channel defined. Again there is much to be done in XI and the R/3 Receiver system before you get to the configuration of the Config Directory.
1. In XI you must configure the RFC destination which enables XI to communicate with the Target System (SM59)
2. In XI you must then create the port which allows you to establish an RFC Connection. In this port you define the RFC destination you previously defined. (IDX1)
3. You then must also ensure that a Partner Profile has been established in the Target system which allows XI to send IDOCs to the Target system. (WE20)
Once the above is completed you can then continue to configure your IDOC scenario in the Config directory. In your Receiver Adapter you reference both the Port and RFC destination that you just established along with the Release which is to be the Target systems release. You must also specify an Interface version which again is the Target systems version.
There are certain cases which you also need to use IDX2 (Cache). XI itself does need the IDOC metadata to execute the interface but it can usually use IDX1 to pull this data either from the SAP R/3 system or an equivalent reference system. However if there is already cached metadata and the IDOC has changed then IDX1 will not execute. In this instance you can pull this metadata manually using IDX2 (XI Box).
Apart from the above the rest of the steps in the Config Directory are as normal.
Message was edited by:
 Alex Ong

Hi,
As per my knowledge you need to configure port in IDXI in XI to pull the metadata.
Its a mandatory step to pull the metadata whatever be scenario like whether you are sending an IDoc or receiving an IDoc.
So please configure RFC destination, IDX1 and IDX2 in XI side.
Only after pulling the IDoc metadata you can proceed with any of the IDoc scenario.
Whenever there a IDoc is changed you need to delete the previous metadata and pull it again. In such situations you can use the already existing port in IDX1.
Hope this helps you out.
Thanks and Regards,
Vineetha

IDOC - BPM - IDOC Error --no sender or receiver interface definition found

I have an integration scenario, IDOC - BPM - IDOC. SAP will send ACC_GL_POSTING IDOC to XI, a BPM will start and then the BPM will send an IDOC to another SAP system.
I have read instructions on weblogs:
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
The scenario has been successfully tested in the Test Configuration Tool. However, when I try send IDOC from the source, I received the message below in the trace.
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_BPE-ENTER_PLSRV">
<Trace level="3" type="T">Processing mode is</Trace>
<Trace level="3" type="T">created BPE proxy for message B45CB0079DFA814BAD22CD1ED64CA6AB</Trace>
<Trace level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 000</Trace>
<Trace level="1" type="T">Message status 000</Trace>
<Trace level="1" type="T">Interface action INIT</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">start CHECK_INTERFACE</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface ACC_GL_POSTING.ACC_GL_POSTING01*</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface ACC_GL_POSTING_abs*</Trace>
<Trace level="1" type="T">select interface namespace http://summaryFinancial.sap.dominofoods.com</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="T">end CHECK_INTERFACE</Trace>
<Trace level="1" type="T">Set interface action DEL into MAST</Trace>
</Trace>
<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA" />
<Trace level="3" type="T">inserted message into pipeline PE_ADAPTER</Trace>
<Trace level="1" type="Timestamp">2007-04-30T18:32:30Z EST qRFC raised on XBQO$PE_WS91000003</Trace>
</Trace>
Thanks,
Sergio

Rajeev,
The source system in the receiver determination is connected to R3. Other IDOCs are coming across the XI system.
Below is some trace information in the Receiver Determination.
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - IP_GeneralLedger</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) IP_GeneralLedger ACC_GL_POSTING_abs</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: ACC_GL_POSTING_abs</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
Thanks,
Sergio

IDoc (Sender ) to File (Receiver): No receiver could be determined

Hi, Dear Friends,
Im implementing scenario Idoc-to-File by means XI.
I try to follow this scenario:
Satish Jaiswal. A Step-by-Step Guide on IDoc-to-File Using Business Service in the XI Integration Directory
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
But I have an error.
In sender system I send IDoc by transaction WE19. After that in transaction WE05 I see IDoc with status 03 (successful).
After that in XI system:
1) in transaction WE05 I don't see any IDoc (IDoc is not received by the Receiver (XI Integration Server))
2) in transaction SXMB_MONI I see my message with error.
Status - System error.
In detail view at stage "Receiver Identification" in item "Error" I see: "No receiver could be determined"
Unfortunately I'm not expert in IDoc.
Can you recommend me what I need to verify?
Or advice me link on another full good example with IDoc.
What I need to read for quick start in IDoc understanding.
Thank you in advance.
Natalia Maslova.

Try these steps:
ALE Settings
SAP XI
1) RFC Destination (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.
2) Create Port (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 SAP XI towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (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.
2) Create Port (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)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (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.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
Message was edited by:
Raghavesh Reddy
null

Message mapping: SOAP Receiver to IDOC Sender

hi,
i have an idoc sent to SOAP receiver. SOAP Response will have only the "Status code" and the "Reason of failure".
IDOC Sender will have the PO Number and the Vendor Name to which we are sending.
The SOAP Response will not have the PO Number and the Vendor Name.
How can i have the Reason of failure, PO Number and Vendor in one message type?
Thanks in advance,
Tirumal

Praveen -
Thanks for the response and appreciate your observation.
Very tight deadlines with the client and have to finish lot of tasks in short time so putting hands in everything.
There are lot of vendors who run their proprietary web services. So cannot change their stuff.
How would i map the SOAP request to the SOAP Response since some information is in one message type and other half of information available in other message type.
I created a SOAP Response Type with the "Reason Code" information.
I created another message type with all the information that i want.
How would i map the SOAP Request to the SOAP Response msg type and the other message type.
Let me know.
Thanks in advance,
Tirumal

Sender and Receiver Idoc

Hi All,
what are the settings need to be done on both XI system and SAP R/3 system while XI system is communicating to any SAP R/3 system through an IDOC on any side sender or receiver.
Will there be any difference in the settings for sender and receiver SAP R/3 systems.
Could any body please suggest me some blogs or documents.
Thanks in advance..
Regards,
Radhika.

Hi Radhika,
Hi
http://help.sap.com/saphelp_nw04/helpdata/en/18/22b800773211d396b20004ac96334b/content.htm
http://www.erpgenie.com/index.php?option=com_content&task=view&id=346&Itemid=57
http://searchsap.techtarget.com/loginMembersOnly/1,289498,sid21_gci994575,00.html?NextURL=http%3A//searchsap.techtarget.com/expert/KnowledgebaseAnswer/0%2C289625%2Csid21_gci994575%2C00.html
http://www.thespot4sap.com/Articles/SAP_ALE_Other_Concepts_Conclusion.asp
Refer this material..
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
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.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
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 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
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.
You can directly create an iDoc using some transaction like...
Use TCODE bd10 - to Send Data
and TCODE bd11 - to Get Data
and you can check the IDoc List using TCODE we02.
As you want step by step procedure.
1. Define Logical System and Assign Logical System
TCODE sale
2. Define RFC
TCODE sm59
3. Define Port
TCODE we21
4. Define Partner Profile
TCODE we20
5. Define Distribution Model
TCODE bd64
6. Send Data
TCODE bd10
7. Get Data
TCODE bd11
8. IDoc List
TCODE we02
There are basically two types of IDOCs.
Basic IDOCs
Extended IDOCs
Idoc Components
Basic Idoc
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extension Idoc
Extending the functionality by adding more segments to existing Basic IDOCs.
Creation of IDoc
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)
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Create IDOC Type
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
u can also check all these links related to idocs
http://www.allsaplinks.com/idoc_sample.html
http://www.allsaplinks.com/
http://www.sap-img.com/
http://www.sappoint.com/abap.html
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html
http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
Reward points if this helps
Regards
Vani.

IDOC Sender Adapter and Receiver Adapter

Hi,
Why we don't require IDOC Sender Adapter to communicate with PI and why IDOC Receiver Adapter is required to communicate with SAP ?
Regards,
J Augastine

Hi,
>>>Why we don't require IDOC Sender Adapter to communicate with PI
you're talking about sender and receiver agreements right ?
as this adapter is based on abap stack - with new functionalities of IDOC adapter
require sender agreement
>>>and why IDOC Receiver Adapter is required to communicate with SAP ?
as we need to put the RFC to the destination system somewhere...
Regards,
Michal Krawczyk

IDoc Message Type different in sending to receiver system

Hi,
I am sending DESADV (message type) IDoc to other SAP system. But problem is in other system Message Type DESADV is available in a different name ie DESADV1.
No of segments and their name are same in both the system are same..
In that case if i am sending DESADV from sending system whether receiver system can get IDoc?
Note: In sending system i could not able create message type DESADV1
Sa_R.

Hii..
Looking like Strange scenario...
Normally we must have the Same message type in both Sender and Receiver systems.
Bcoz whenever the IDOC is Received in the Receiving system it will process based on the Message type. So the Same message type must exist in the Sender as well as Receiver.
I can think of a Solution: Just try..
In the Sender system Create a Reduced message type (Tcode BD53) Of the Message type DESADV. Select all the Segments and Fields
In the Receiver system also Create a Reduced message type with the Same name as Sender system (Tcode BD53) Of the Message type DESADV1. Select all the Segments and Fields.
Then use this Reduced message type since it exists in both the Systems.
Reward if Helpful.

IDoc sending/receiving - XML v/s text IDocs

.NETters,
SAP .NET Connector supports sending and receiving IDocs.
1. For IDoc receiving, can we receive text IDocs as well as XML IDocs?
2. For IDoc sending, can we send text IDocs as well as XML IDocs?
Thank you in advance for enlightening me.
Pradeep

Hi Pradeep,
for NCo help on IDOCs, please read
http://help.sap.com/saphelp_nw2004s/helpdata/en/79/d0b51753406d4d86470debdf027c68/content.htm
SAPIDocReceiver
http://help.sap.com/saphelp_nw2004s/helpdata/en/b1/8d23ec676fa74993d16c4a195c76a7/content.htm
IDoc Receiver
http://help.sap.com/saphelp_nw2004s/helpdata/en/e8/0f499a4221604fb10200f24772c82a/content.htm
IDoc Submitter
http://help.sap.com/saphelp_nw2004s/helpdata/en/ae/fc646926adcd40bce23a981317374e/content.htm
the idoc's sent can be in text form as well as xml, that will depend on the charecteristics of the listener & the sender.
usually keeping them in xml should make parsing simpler for you.
with respect,
amit

IDOC sender: Error in Logical system name?

Hi,
In my current project, the IDOC sender system logical name is P2PCLNT100 but the SLD system name is P2P.
Its an IDOC to proxy scenario. At the receiver system side, the schemeAgencyID is getting populated at P2P and not P2PCLNT100, due to which there is an error on the receiver's side.
Following is already checked:
1. SLD has maintained the proper logical system name for the P2P system
2. The IDOC xml on the XI system has the sender port properly populated as P2PCLNT100
3. I have also debugged the program on the receiver side and fails at a point where it checks the logical system name from the database BBP_BACKEND_DEST.
On the receiver system, the followed error is shown as follows:
- <STANDARD>
<CONTROLLER />
<FAULT_TEXT>An error occured within an XI interface: SLD system P2P is not known Programm: SAPLBBP_BD_MAPPING_SAPXML1; Include: LBBP_BD_MAPPING_SAPXML1F1Y; Line: 96</FAULT_TEXT>
<FAULT_URL />
<FAULT_DETAIL />
</STANDARD>
Thanks in advance for the useful answers.
Sowkhya

Hi,
1. R/3 system's logical system name and SLD business system's logical system name has the same.
Is there a need to have the business system name in SLD to have the same name as R/3 system logical name?? As far as my knowledge goes, business system and logical system need not have the same name. Correct me if in the case IDOC sender scenario is different..
2. SLDCHECK shows following message:
Summary: Connection to SLD does not work
The issue still persists. Will SLDCHECK correct solve the issue?
Regards,
Sowkhya

SAP PI Party setup IDoc - HTTP: no receiver agreement found

Hi,
We have setup SAP IDoc -> SAP PI --> HTTP with 2 parties, as described in the the 'HOW..TO Sample IDoc - XI scenario's' case 7:
For the clarity of the example, the sender at our side is 'AAA', and the receiver side is 'BBB'.
1. Sender Party
Agency -
Scheme -
Name
http://sap/com/xi/XI -
XIParty -
PA_AAA
BS_BBB -
ALE#LI -
0000100581
2. Receiver Party
Agency -
Scheme -
Name
http://sap/com/xi/XI -
XIParty -
PA_BBB
AD2_200 (SAP system) -
ALE#KU -
DE217560
The other components in XI are as follows:
3. Business component: PA_BBB | BS_BBB (party and Business System)
4. Receiver determination: sender AD2_200, receiver party: PA_BBB, receiver component: BS_BBB
5. Receiver agreement: sender AD2_200, receiver party: PA_BBB, receiver component: BS_BBB
 Header mapping: sender comm party: PA_AAA, receiver comm party: PA_BBB
6. Communication channel (HTTP): CC_HTTP_RCV_BBB
 Identifiers: sender agency: BS_BBB ALE#LI, receiver agency: BS_BBB ALE#KU
When we send an IDoc with SNDPRN=AD2_200, RCVPRN=DE217560, RCVPRT=KU, SAPXI doesn't seem to find receiver determination, iinterface determination and receiver agreement
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start with given receiver PA_BBB -</Trace>
<Trace level="2" type="T">Using Receiver Determination 00000000000000000000000000000000</Trace>
<Trace level="1" type="T">No Relation found - accept given Receivers.</Trace>
<SAP:AdditionalText>No receiver agreement found for , AD2_200, PA_BBB, , urn:sap- com:document:sap:idoc:messages,
Can someone explain why these parties have to be indicated in all these different places (the party descriptions, the receiver agreement, the communication channel), and why the receive determination with receiver party PA_BBB is not found, although it is created and refreshed in the cache ?
Regards,
Jan Macken

I am also facing same issue when using 2 parties. Could you please let me know if you got solution for this?

Error while posting idoc in the receiving system.

i have processed idoc in the same system( sending and receiving idoc in the same system ) by creating a dummy logical sys and uploading a text file for customer details.The outbound processing is succesful and it shows a status message 3. But duriing the inbound processing it shows status as 51 with error as 'ENTER VALID VALUE'. but when testing using we19 it is posted sucessfully without any error..is there anything that i have to configure to process inbound idoc sucessfully?? can any suggest me the correct method for doing this.. suggestions please..
thanks
vidya sagar

Hi,
you need to make sure that in WE20 inbound processing parameters for you LS is maintained propperly. You need to give correct function module and enter whether IDoc should be processed immediately or IDocs should be collected and processed as batch. Also you may check whether the distribution model (BD64) is maintained correctly for the specific message type in the system for inbound processing.
Regards,
Kai

Sender and receiver agreement not cerated

Hi .
I am creating configuration scenario in ID by importing the integration scenario which i created in the IR.
I crated communication channel template also and i added it to the integration scenario in connections.
Query 1?
do i have to create Communication channels also.....even After creating communication channel template (because it is not seen the ID below communication channel )
Query 2 ?
once i transfer this integration scenario from IR to ID and cerate the configuration scenario (sender and receiver agreements are not getting created automatically)peace tell me what is the reason???.
and how can i resolve this...
thanks
shakif

Hi Mohamed,
Query 1?
do i have to create Communication channels also.....even After creating communication channel template
Yes You have to create as it's just a template that u created in IR. But u can use the same for creating CC.
Check this link for what's the Diff. B/w CCT in IR and CC in ID
Re: Communication Channels
Query 2 ?
once i transfer this integration scenario from IR to ID and cerate the configuration scenario
Yes. it will create automatically.
Just check my posting in Wiki for simple File to IDOC scenario might be u missing something
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/fileToIDOC&
and check my reply in this thread
Re: Doubt in transfering integration scenario from IR
Regards
Sachin

No IDOCs sends or receive in DES

Similar Messages

Maybe you are looking for