About WE21, BD64, sm59

Hi Friends,
I am not sure if this is the right place to ask this question, please let me know if I should put it in some other forum.
communicating with ALE (IDoc) Inbound,outbound using SAP Java Connector .
trying to understand these setting in SAP, what these means in ground level.. to understand clearly.
why we need:-
1. define logical system .      ./nSALE
2.distribution model setting     /nbd64
3.partner profile check            /nwe21
what are the significance of these settings.
Thanks.

Hi,
1> SALE - Here you are giving some meaningful name to the system . Further communication will be happen using this logical name only.But generaly there will be no authorization given to all.Once its done then it will be assigned to the clients in TCODE SCC4.
2>SM59 - It is nothing but to create the RFC destination.Here u will specify the destination address.
3>. Distribution Model - BD64 - It gives idea about what data you are going to transport and also u generate the partner profiles from here.Also gives the information of sender and receiver also.
4> Partner Profile - Her u will specify the reciver (partner number) and also whther u require outbound or inbound.Also u will specify the mesage type and basic type here.Also the port.
5>Port is created in tocde WE21.
Regards,
Nagaraj

Similar Messages

Exporting WE20, WE21 and SM59 Entries

Hi,
Can anyone knows how can we export or keep a copy of WE20, WE21 and SM59 Entries for later use. As We are going to refresh the development server with quality and wish to restore the orignal DEV servers parameter (Enteries) settings.
How can we do Export and Import. Pl. suggest me some solution.
Thanks,
Raj

Try this Script . Go to /usr/sap/trans/bin create a file ( <filename>.ctl > with the following entries
export
file '/usr/sap/trans/data/filename1.dat'
delete from rfcattrib
select * from rfcattrib
delete from rfcdes
select * from rfcdes
delete from rfcdoc
select * from rfcdoc
delete from rfcsysacl
select * from rfcsysacl
delete from rzllitab
select * from rzllitab
delete from rzlliclass
select * from rzlliclass
delete from sxroute
select * from sxroute
delete from rfccheck
select * from rfccheck
2 ) execute the command R3trans -w <filename>.log <filename.>.ctl , a log file will be created in /usr/sap/trans/bin with the file name <filename>.log , R3trans return code should be 000 0r 004.
3) If you want to reimport it to the same system at a later point of time create a script <filename2>.ctl in /usr/sap/trans/bin
import
file '/usr/sap/trans/data/filename1.dat'
4) R3trans -w filename2.log -u 1268 <filename2>.ctl
The return code should be 000 or 004 , compare the no of table enties in the exported and imported log files , they should be in sync .
Edited by: Mann Mohandas on Feb 20, 2010 8:33 AM

System Copy : Transactions sm59, we20, we21, bd64

Hi forum,
if you are to make a system copy, one system - as a rule QA - is overwritten by a production system. You can save
the RFC connections by consistently exporting (by use of brspace f.ex.) all table starting with rfc* and after the copy
you can reimport it. Same as for transactions we20 and we21. The tables in question are mentioned in note 181172.
But what can you do to export and later reimport the contents of transaction bd64 ???
Kind regards
OEggert2706

Hello,
Did you try the following option?
BD64--> Edit --> Model View --> Transport
Partner profiles are stored in the following tables. I think you can add these tables in a transport request, release it before refresh and import the same after refresh.
EDPP1: General partner profile
EDP12: Partner profile outbound, additional data NAST
EDP13: Partner profile outbound
EDP21: Partner profile inbound
EDIPHONE: Connection to SAP telephony (optional)
Thanks,
Siva Kumar
Edited by: Siva Kumar Arivinti on Dec 13, 2011 8:28 PM

Function Module to create Outbound IDoc

I have created a segment (ZSEGPRO), basic type (ZIDOCPRO) and message type (ZMSGPRO) to create a custom IDoc. Now I have to write a Function Module to create Outbound IDoc.
I want to know what will be in Import, Export, Changing, Tables, Exceptions and Source code of that function module. The fields used in the segment ZSEGPRO is given below:
Fld NameSource Data Elmn     Description
PRODUCT MARA MATNR     Material number
TEXT     MAKT     MAKTX     Material description
PRN     MARA     YYBCEZNDR     Print Field
Additional information: Export parameter will be BAPIRETURN for holding error message(if any).
These Function Module need not require to be RFC enabled.

Hi ,
Refer these:
There are two main reasons
1) Make sure you call COMMIT WORK after the MASTER_IDOC_DISTRIBUTE
http://help.sap.com/saphelp_nw04/helpdata/en/78/21783151ce11d189570000e829fbbd/content.htm
2) The rest of the setting of the ALE IDoc might not have been done
http://help.sap.com/saphelp_46c/helpdata/en/78/2177c951ce11d189570000e829fbbd/frameset.htm
You can use the Area Menu WEDI and do the rest of the settings.
ALE Quick Start guide and ALE Programming Guides for your reference
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
Recent discussion which could be helpful,
About WE21, BD64, sm59
Regards
Shiva Kumar

Idoc sent in green status, but no trace

Hi experts,
we send idoc via we19 to XI, but we have absolutely NO TRACE of the message, even though the statuts of the sent idoc is green id bd87.
We checked everything:
idx2
we20
we21
bd64
sm59
but everything is fine
do you have by any chance any idea of whats goin on???
Any help would be appreciated
kind regards,
Jamal

Hi,
I had this problem once that RFC connection test was ok but not the authorization test.
If this is not the reason maybe this guide could help:
http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/frameset.htm
Regards
Patrick

ECC System Refresh - impacts IDOC connections to PI

All,
Whenever we refresh ECC QA system with prod, we have to do all the ale/IDOC settings all over again in ECC QA to connect to QA PI.
Can you please list the tables that are used for We20, We21, BD64, SM59 so that BASIS can take a backup of these tables before refresh and apply the backup once the system refresh is complete.
Thanks.

Hi Vicky,
Partner profile (WE20) is store in below tables
EDPP1: General partner profile
EDP12: Partner profile outbound, additional data NAST
EDP13: Partner profile outbound
EDP21: Partner profile inbound
regards,
Harish

PI7.1 Idoc Sender Adapter cannnot work

Hi,
I'd like to transport data from ERP to MDM. So I get data from ERP by PI IDoc adapter.
First I made RFC connection(ABAP connection) on Trcd:SM59, and IDoc port on Trcd:IDX1 in PI server.
Then I configured Trcd:IDX2.
Next I configured Trcd:SM59,WE21,BD64 on ERP server.
I did Trcd:MDM_CLNT_EXTR on ERP, then I checked the IDoc result in Trcd:BD87.
The result status was 03, it's OK.
But I checked in Trcd:SM58, I got following message from ERP.
"Neither system SAPE09 nor client 200 are served in IntegrationDirectory."
I select the message, and push F6 button. But I got following message in the status bar from ERP.
"The function module was unregistered or EXCEPTION was generated."
Are some settings insufficient?
PI Server:
Windows2003 Server Standard x64 Edition SP2
MSSQL 2005
NetWeaver PI 7.1 SP7
ERP Server:
Windows2003 Server Standard x64 Edition SP2MSSQL 2003
MSSQL 2005
ECC6.0 SP13
Regards,
Hiromitsu Ishizawa

Hi,
In ERP system by transaction BD54 create a logical system for your PI system.......then in ERP system by WE20 transaction, add your this IDOC in outbound parameters of your PI logical system which you created above........then try to reprocess your SM58 entries.........
Regards,
Rajeev Gupta

Logical System not maintained

Dear Experts,
I need to generate JVRD condition idoc using FV13 for a new site for some articles.JVRD condition is maintained in SAP.But when i try to send the condition type using the above t-code it generates no Idoc and shows me the message
Segment is not intended for reciever LS_E111. However for other stores its running f9.Do i need to maintain or define Logical System 'LS_E111' some where for this new site? I hv already checked in WE20 for partner profile .Pls help

Hello,
I'm not familiar with JVRD. Have you checked the receiver port in WE21 and SM59? You can find the receiver port in WE20 outbound parameters
Regards,
Michael

Inbound idoc type

i have to do an inbound idoc. first i need to retrieve data from one function module and use the data of that FM into another function module.
so there is a Z function module which has information of both the function module.
i am using the following idoc type
MBGMCR02.
i need to add some more zsegment into it of the other function module the function moduke is WS_DELIVERY_UPDATE 2.
kindly guide please.

Hi Kamlesh,
In we30 you have to create a new Extension idoc type and add the segments. and then from the menu release the idoc type.
Create a new message type ZMBGMCR using we81 or we82.
Create a new Function module to cater to your requirement.
Create a new inbound Process code through WE42 or we41 and attach this function module to the process code.
Link the idoc type, message type and function module through WE57 or BD57
Set the partner profile We20 for the new message type and idoc type and also set the message control tab
Set the port through we20. and give this port in the we21 partner profile.
Create a Customer distribution model BD64 and give the sendor and receiver and from the menu distribute the partner profiles.
Use We19 tcode to test the inbound idoc.
Use we02 or we05 to view the status of the idoc.
The tables for idoc are
EDIDC - control record
EDID4 - Data record
EDIDS - Status record
Some transactions are
SCC4
We20
We21
BD64
we81
we82
bd87
we19
wedi
we02
Hope this helps
Regards
Arun

IDoc Adapter 151 - Transaction aborted

Hi fellows,
after patching our XI-System to SP19 we try to do a new IDoc2File Szenario. We have one from the old XI-Level which runs really good. It's going from external R/3 to our XI server into the file system.
the new scenario has some selfmade IDoc and i already checked EVERYTHING (we20, we21, sm58, sm59, idx1, idx2, idx5, sm21) Following i give some hints what kind of problems i see. perhaps u can help me?!
in the sender-system:
sm58: IDOC_INBOUND_ASYNCHRONOUS, some mistake in IDX1 saying RFC-Destination is corrupt. But i can successfully use the remote login and the connection test.
in the receiver system:
idx5: nothing displayed concerning the new szenario
sm21:Transaction aborted IDOC_ADAPTER 151
I have no clue what it can be, has someone had same experiences?!
thx best regards, Jens

Thx!
> From SE91 the error message IDOC_ADAPTER 151 means:
>
> Short Text
> Transaction IDX1: Port &1, client &2, RFC destination
> &3 contain error
>
> Diagnosis
> Transaction IDX1: Port &1, client &2, RFC destination
> &3 contain errors
>
> System response
> You tried to fetch the metadata for the current IDoc
> from the reference system, using RFC.
>
> In doing so, an error occurred that was caused by one
> of the following:
>
> 1. You have not yet assigned a port/client to the RFC
> destination.
>
> 2. You have not yet created the RFC destination or it
> contains errors.
>
> 3. The target system is unable to receive.
>
> Procedure
> 1. Check your RFC destination in transaction SM58.
>
Yes, SM58 in the sender system says an error concerning IDX1. RFC destination is wrong - BUT it's all working fine. in case of reading the metadata i also configured IDX2 in XI System to get the metadata in advance. RFC remote login and Connection test runs fine!!
I have no clue again because when i use WE19 with the old IDoc-Scenario and the SAME parameters of sending the IDoc it's working, with the new one it doesn't.
some ideas
null

One IDOC genearates 2

Hi All,
We have change points configured for SO (ORDERS.ORDERS05).
When I create or change (ve02) any SO, two IDOCs are generated in WE02 and the the same 2 IDOCS are sent to PI.
Both the IDOCS have same data in data and control records. The only thing that differs is IDOC No.
I checked in WE20, WE21, BD64 for any duplicate entries. All of them seemed correctly configured.
Where are the things go wrong?
If someone has faced similar issue, let me know
Thanks,

>
Nikhil A wrote:
> Hi All,
>
> We have change points configured for SO (ORDERS.ORDERS05).
> When I create or change (ve02) any SO, two IDOCs are generated in WE02 and the the same 2 IDOCS are sent to PI.
> Both the IDOCS have same data in data and control records. The only thing that differs is IDOC No.
>
> I checked in WE20, WE21, BD64 for any duplicate entries. All of them seemed correctly configured.
>
> Where are the things go wrong?
> If someone has faced similar issue, let me know
>
> Thanks,
Hi Nikhil,
It is configuration issue. two areas you will need to check.
1. Functional area where outputs types are configured ( Functional Person will be able to help you )
2. IDOC config, Partner profile config....
Do not waste your time debugging. It is basic config issue.
Good Luck.

Configurations required in SLD,IR,ID,SM59,BD64 to Start with IDOCS

Hello all,
Can You Post me the Above details.
thanks,
Srinivasa

Hi Srinivas,
Let us explore the need for each steps and detail it now...
Step-1 : You need RFC destinations for placing the metadata of the IDoc.
Use transaction SM59 to maintain an RFC destination for the IDoc sender/receiver system.
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.
Step-2 : Next You need IDx1 for getting IDoc metadata from the Sender system.
Use transaction IDX1 to assign a port (RFC destination) to the system that contains the metadata of the IDoc types.
Note:
There is a mechanism on the Integration Server that uses this RFC destination to retrieve and cache the metadata at runtime if it is not yet available on the Integration Server.
Nut-Shell:
Since IDoc metadata is cross-client, you should only assign one port for each system.
If several ports are assigned, ensure that they are all working.
This is Done in Partner Profile.
If you are not able to load the metadata from this system (because of administrative or security-related restrictions, for example),
you can also load it from a reference system (for example, a test system) and use transaction IDX2 to assign it to your production system afterwards.
For non-SAP systems, either the ports in transaction IDX1 have to point to a reference SAP system, or you copy the metadata with transaction IDX2.
I come to mean that if you double click the OutBound Parameter in the Partner Profile you will be allowed to choose the Idoc type like Matmas,Debmas blabla..
There after providing the receiver destination in that partner profile which is nothing but your Maintaining Metadata through a port,
which on double click leads to RFC destination alloted with a port to transfer its data from sender to receiver Server.
Step-3 : Goto SLD and do the following.
Access the System Landscape Directory (SLD) to maintain the technical systems for the sender and receiver business systems of your system landscape.
You have to define a technical system (and a client in the case of SAP systems) to which your business system belongs.
When you define a client number, you also have to specify the corresponding logical system name in the Technical System Browser.
Note:
The technical system configuration is not required if your business system is configured as a data supplier for the SLD.
Step-4 : Goto Integration Directory and do the folllowing.
Access the Integration Directory to define your business systems as services without party.
a) Either you can choose from the Objects Business Service where your client is defined for it.
With this Selected Business Service you just rightclick and choose ASSIGN TO BUSINESS SCENARIO.
b) Second choice is to choose the business system which was done in SLD.
Do the receiver determination and interface determination but since the adapter is not required to choose for Idoc dont do sender determination.
Note:
The IDoc adapter only uses the service definition (business system) together with the corresponding adapter-specific identifiers in the Integration Directory.
The maintenance of your IDoc sender system in the SLD is therefore not sufficient.
It is recommended that you assign your business system definition retrieved from the SLD to a service in the Integration Directory.
Nut-Shell:
Using this information about the system ID, client, and logical system name for a specific business system, the IDoc adapter is able to specify the corresponding service in the XML header. Routing is then based on service names.
You need the
 logical system, SAP system ID, and client for an IDoc receiver SAP system
 SAP system ID and client for an SAP system
 logical system for a non-SAP system.
This means that the business systems used for the routing definitions in the IDoc-XML message header are retrieved from the adapter-specific identifiers of the service definitions in the Integration Directory,
where for each business system client, the corresponding system ID, client, and logical system name is defined.
Caution:
Use the import function to retrieve the adapter-specific identifiers for a service (business system) to avoid double maintenance in the SLD and Integration Directory.
Step-5 : Steps in Integration Repository.
Export the IDoc in Imported Objects.
Double click the Idoc to view the structure.
This Idoc type is decided in the partner Profile.
See step-3 for further details.
Create the Interface Objects like
1.Data Type for Receiver File.
2.Message type which wrapps this Data type.
3.Interface Type.
a) For Sender Idoc just drag the Idoc name which you have loaDED IT IN YOUR imported objects.
b) For Receiver File It just wrapps the Message type of the file.
4.Message Mapping:
The Fields selected in the data type for the file should be the mandatory fields in the Idoc.
Since the Idoc is in the sender side,it just performs similar operation like selecting things from a database.
Begin and Other Attributes are neednt be worried to map.
The Mandatory fields which was chosen will need to be mapped with the target file.
5.Interface Map:
Just Wrapps the Message mapping.
Step-6 : BD64 is to Distribute the Idoc to Various Acceptors.
1.Create Model View.
2.Add Message Type to it.
3.So that it displays your model view with your Message type like MATMAS.
4.Goto Environment and click Generate Partner Profiles.
5.Executing it,you will get a log indicating the Partner,port and Outbound Parameters.
6.After Doing this goto Edit Menu available in the tool Bar and give Distribute.
7.After distributing it ,it shows your logical system name along with the technical name.
8.Now to fill the IDOCs with Data we have to go to Transaction bd10.
9.We can give our own selection criterias and select the list of materials accordingly.
10.Now to check whether the IDOCs has been correctly created and sent to the receiving system (in this case it is the SAP XI Server)
11.we have to check it out in Transaction WE05.
12.Now we can go to the Location we specified in the Configuration where the file will be created.

Can you please explain in detail about the T-Code SM59

Can you please explain in detail about the T-Code SM59

Hi Raja,
detailed explanation is already available over help.sap.com.
For your ready reference check below links
http://help.sap.com/saphelp_spm21_bw/helpdata/en/57/898009a859493a8bce56caaf0f8e13/frameset.htm
http://help.sap.com/saphelp_webas610/helpdata/en/da/11df3a9b10355ae10000000a11405a/frameset.htm
http://help.sap.com/saphelp_snc70/helpdata/en/3f/7ffb40ef74f923e10000000a155106/frameset.htm
Regards
Jitender

Introduction about XI

Hi,
I am a J2EE developer and new into SAP.I dont have any idea about SAP XI. Can anyone tell about the documents which i can read so that my basics of XI can clear.I just need very simple and basic docs.
Regards,
Deepika

HI deepika
go thru the below
For scenarios refer this wiki.
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/step-by-step+guides
for guides try this link.
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/home
SAP XI INTRODUCTION
Aspirant to learn SAP XI...You won the Jackpot if you read this!-Part I
Aspirant to learn SAP XI...You won the Jackpot if you read this!-Part II
Aspirant to learn SAP XI...You won the Jackpot if you read this!-Part III
http://www.erpgenie.com/sap/netweaver/xi/namingconventions.htm
http://www.erpgenie.com/sap/netweaver/xi/howto.htm
http://www.erpgenie.com/sap/netweaver/xi/tips.htm
http://www.erpgenie.com/sap/netweaver/xi/xiauthorizations.htm
https://www.sdn.sap.com/irj/sdn/wiki
Interfacing to XI from Webdynpro
Understanding message flow in XI
Ready Reference for XI Developers
Message Mapping
Message Mapping Simplified - Part I
/people/sravya.talanki2/blog/2005/12/08/message-mapping-simplified-150-part-ii
http://help.sap.com/saphelp_nw04/helpdata/en/43/c4cdfc334824478090739c04c4a249/frameset.htm
New functions in the Graphical Mapping Tool XI 3.0 SP13
File Content Conversion for Multi Hierarchical Structure
Message Splitting Using the Graphical Mapping Tool
Number formatting to handle LARGE Numbers
Optimizing Lookup's in XI
Minimize memory usage during Message Mapping when replicating an element
Mapping Context Changes in XI
/people/jeyakumar.muthu2/blog/2005/12/19/data-mining-using-apriori-algorithm-in-xi-150-part-ii
/people/jeyakumar.muthu2/blog/2005/11/23/data-mining-using-apriori-algorithm-in-xi-150-part-i
/people/jeyakumar.muthu2/blog/2005/12/30/data-mining-using-apriori-algorithm-in-xi-150-part-iii
Java Mapping to handle flat files in SAP XI
xpath functions in xslt mapping
"JAVA MAPPING", an alternate way of reading a CSV file
B2B Mapping Techniques Using the Graphical Mapping Tool
Duplicating Subtrees and Numbering Them Using the Graphical Mapping Tool
How to parse "XX/YY/ZZ;AA/BB/CC;11/22/33" in message mapping.
Introduction to queues in message mapping
Handling of Mixed Content Element in XI
The specified item was not found.
The specified item was not found.
ValueMapping using the Graphical Mapping Tool
Accessing Value Mapping defined in Directory using Java functions
Comparing Performance of Mapping Programs
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
Runtime WorkBench Monitoring
XI CCMS Alert Monitoring : Overview and Features
The specified item was not found.
The specified item was not found.
http://help.sap.com/saphelp_nw04/helpdata/en/58/d22940cbf2195de10000000a1550b0/content.htm
The specified item was not found.
The specified item was not found.
The specified item was not found.
The specified item was not found.
XI : How to Re-Process failed XI Messages Automatically
BPM
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/integrationProcess%28ccBPM%29inXI&
Walkthrough with BPM
Reconciliation of Messages in BPM
RFC Scenario using BPM --Starter Kit
The specified item was not found.
Schedule Your BPM
Demonstrating Use of Synchronous-Asynchronous Bridge to Integrate Synchronous and Asynchronous systems using ccBPM in SAP Xi
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken]
Sync/Async scenarios without BPM
Sync/Async communication in JMS adapter without BPM (SP19)
IDOCs (Multiple Types) Collection in BPM
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
File to File Scenario
Step by Step Guide: XML File 2 XML File Scenario: Part I
Step by Step Guide: XML File 2 XML File Scenario: Part II
Converting XML to PDF using XI
Introduction to simple(File-XI-File)scenario and complete walk through for starters(Part1)
Introduction to simple (File-XI-File)scenario and complete walk through for starters(Part2)
"JAVA MAPPING", an alternate way of reading a CSV file
Dynamic File Name using XI 3.0 SP12 Part - I
Dynamic file name(XSLT Mapping with Java Enhancement) using XI 3.0 SP12 Part -II
Push Data to MVC Architectured application using XI
How to send any data (even binary) through XI, without using the Integration Repository
XI in the role of a FTP
The specified item was not found.
The specified item was not found.
The specified item was not found.
The specified item was not found.
IDOC Scenario
Introduction to IDoc-XI-File scenario and complete walk through for starters.
Troubleshooting File-to-IDOC Scenario in XI.
Convert any flat file to any Idoc-Java Mapping
IDOCs (Multiple Types) Collection in BPM
Outbound Idoc's - Work around using "Party"?
Troubleshooting File-to-IDOC Scenario in XI.
RFC Scenario
Exposing BAPI as Web Services through SAP XI
RFC Scenario using BPM --Starter Kit
The specified item was not found.
The specified item was not found.
HTTP to RFC - A Starter Kit
Also refer the below help:
1) What is XI:
http://help.sap.com/saphelp_nw04/helpdata/en/3c/831620a4f1044dba38b370f77835cc/frameset.htm
2) Design and Configuration:
http://help.sap.com/saphelp_nw04/helpdata/en/3c/831620a4f1044dba38b370f77835cc/frameset.htm
3) Integration Processes (ccBPM)
http://help.sap.com/saphelp_nw04/helpdata/en/3c/831620a4f1044dba38b370f77835cc/frameset.htm
4) Central Monitoring:
http://help.sap.com/saphelp_nw04/helpdata/en/3c/831620a4f1044dba38b370f77835cc/frameset.htm
5) Adapters:
http://help.sap.com/saphelp_nw04/helpdata/en/ae/d03341771b4c0de10000000a1550b0/frameset.htm
Just go through the below link which has all the topics:
http://www.sap.com/services/education/certification/certificationtest.epx?context=FFC760B8923D16BB5150DAE63E7C1A6B331AF0B9E3A8F73CE3A9B7046E051044503600C911DBA13DCE978D3AC9057626D2B68111A7CD2D707E2EEC31213097E46EB790DD0106435EE0756F7B22F3FA4B4FF0645C06954BF3A150E023B4164DA282F33B1BD441FBE4083F2C923E33EA0C5960F8C8950FDEB6081ABED6E0E05E2617A693D85077260F9EA218716A79AEF3AA57C7D5E8975334%7cE41BF735AA1862BF88AE1830FD06B8FCD2D8AECBF5109A3E
If u ahve serach on SDN then u will able to get all the scenarios:
File 2 file:
Step by Step Guide: XML File 2 XML File Scenario: Part I
File content conversion:
FCC
Ref:
Sender -
Introduction to simple(File-XI-File)scenario and complete walk through for starters(Part1)
Key value:
How to send a flat file with various field lengths and variable substructures to XI 3.0
Content Conversion (Pattern/Random content in input file)
NAB the TAB (File Adapter) -
TAB delimited
File Content Conversion for Unequal Number of Columns
Content Conversion ( The Key Field Problem )
The specified item was not found.
NAB the TAB (File Adapter)
NAB the TAB (File Adapter)
Receiver FCC no need of Endseparator
File Adapter (Receiver) - Are we "really" sure about the concepts?
RFC:
Weblog to send Response from RFC to File in Asyn Mode Using Proxy
HTTP to RFC - A Starter Kit HTTP to RFC - A Starter Kit
Weblog to send Response from RFC to File in Asyn Mode Using Proxy: Weblog to send Response from RFC to File in Asyn Mode Using Proxy
IDOC:
ALE configuration for pushing idocs from SAP to XI
ALE configuration for pushing idocs from SAP to XI
IDOC testing using WE19
Reposting IDocs instead of Recreating - For Testing Purpose (XI)
IDOC configuration :
This is expalined both the scenarios:
Please follow the below process for configuration:
Pre-requisites for Inbound IDoc to R/3 from PI:
Configuration required at Xi side:
Go to IDX1: configure the port.
Go to IDX2: load the DOC metadata.
Go to SM59: Create RFC destination which points to R3 system this is require in the case where your IDOC is sent to R 3 system,
Configiration required at R3 side:
Maintain Logical System for PI (SALE transaction):
Maintain Partner Profile for XI system(WE20):
Pre-requisites for Outbound IDoc from R/3 to PI:
Configurations required in R/3:
Maintain Logical System (SALE)
Define RFC Destination (SM59) which points to PI system Maintain Port (WE21) Maintain partner profile. (WE20):
Maintain Distribution Model (BD64):
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
IDOC Collecting
ave a look at this Blog
Collection of Multiple type IDOCs in BPM By Pooja Pandey Collecting IDocs without using BPM By Stefan grube's
Collecting IDocs without using BPM
XI:Idoc Message Packages By Sravya Talanki Collecting from Multiple Interface and sending it to R3 By Prasad Babu Nemalikanti
Idoc to File:
Introduction to IDoc-XI-File scenario and complete walk through for starters.
Collection of IDoc to Single File
IDOCs (Multiple Types) Collection in BPM
BPM:
Walkthrough with BPM - Walk through BPM BPM in XI https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/integrationProcess%28ccBPM%29inXI&
BPM-1 Walkthrough with BPM
BPM-2 Reconciliation of Messages in BPM
BPM-3 RFC Scenario using BPM --Starter Kit
BPM-4 The specified item was not found.
Schedule BPM Schedule Your BPM
Use of Synch - Asynch bridge in ccBPM Demonstrating Use of Synchronous-Asynchronous Bridge to Integrate Synchronous and Asynchronous systems using ccBPM in SAP Xi
Use of Synch - Asynch bridge in ccBPM https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken]
without BPM Sync/Async scenarios without BPM
without BPM1 Sync/Async communication in JMS adapter without BPM (SP19)
IDOC BPM IDOCs (Multiple Types) Collection in BPM
multimapping without BPM /people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
PRoxy:
First start with configuration:
ABAP Proxy configuration:
How do you activate ABAP Proxies?
ABAP Proxies in XI(Client Proxy)
Smarter Approach for coding ABAP Proxies
http://help.sap.com/saphelp_nw04/helpdata/en/2b/f49b21674e8c44940bb3beafd83d5c/frameset.htm
for java proxies
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a068cf2f-0401-0010-2aa9-f5ae4b2096f9
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f272165e-0401-0010-b4a1-e7eb8903501d
ABAP proxy:
ABAP Proxy
Client Proxy -
ABAP Proxies in XI(Client Proxy)
In this case you can define you scenario as a proxy to File. The blog explains the proxy part. Map the structure to a file and complete the scenario.
Please chekc this PDF :
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3dfac358-0d01-0010-5598-d4900e81a30c
Server Proxy -
ABAP Server Proxies
File to Inbound Proxy:
File to R/3 via ABAP Proxy
Debugging Inbound Proxy:
XI: Debug your inbound ABAP Proxy implementation
reward points if helpfull
regards
kummari
Edited by: kummari on Jul 9, 2008 7:46 AM
Edited by: kummari on Jul 9, 2008 11:24 AM

A problem about IDOC Receiver

Hi, everybody.
This time, I'm developing a IDOC Receiver though the SAPIDocReceiver class. With the dotnet Connector manual from SAP, the receiver side on dotnet is easy to develop. But how to configure the SAP R/3 to send IDOC to the dotnet side, I can't find the clear steps in the manual.
So I searched some material about how to configure IDOC, and hope it will be useful to my work. But most of them mainly focus on how to configure a IDOC transformation between SAP system but not NON-SAP system.
So what I want to ask is IS there some difference with the two configuration, I mean the SAP to SAP one and the SAP to NON-SAP one. I guess the difference should be have. Are the necessary configure step like create a logic system, allocate logical systems to clients and so on also necessary under the NON-SAP case? I think some of the configure actions is different in this two case. Can anyone give me some clear steps or tell me where I can get them?
thanks to all.

Hi,
for testing purposes you can do the following:
(1) via SM59 create the RFC destination for your dotnet application
(2) via WE21 create a trfc-port pointing to the RFC destination created in (1)
(3) via SM30 maintain view V_TBDLS to create a new logical system for your dotnet application for example DOTNET (and maybe for the SAP client you are testing with - here the name could be for example <SID>CLNT<CLIENT>)
(4) via SCC4 assign the logical system to the SAP client (for example <SID>CLNT<CLIENT>) only if not already maintained.
(5) In WE20 create a partner profile for logical system created for the dotnet application in step (3)
(6) In WE20 add outbound parameters for the message type (for example MATMAS) and idoc type (MATMAS03) you want to send. As partner port use the trfc-port of step (2)
(7) In WE19 create an IDoc via basic type (the idoc type used in step (6), for example MATMAS03) and maintain the following fields in the control record EDIDC:
recipient port the port created in step (2)
recipient partner number the logical system name of the dotnet application created in (2)
recipient partner type'LS'
sender port SAP<SID>, where SID is the SAP system id
sender partner number the logical system name the SAP client maintained in step step (4)
sender partner type'LS'
message type the message type used in step (6), for example MATMAS
In the other segments E1* you can fill in whatever you like
Hit the push button "Standard outbound processing"
(8) you can check if the IDoc has been sucessfully created by BD87. If an error has occurred in the receiving application or there is any other error you can also see it here. Maybe the IDoc is not passed to the receiver, then you can process the IDoc also from here.
This is how you can create your test environment. If you want to get the IDoc created form the SAP application it depends on the application how to do that!
Best regards,
Willy

About WE21, BD64, sm59

Similar Messages

Maybe you are looking for