Need to create IDOC

HI Helpful Hearts,
I need to create IDOC for some file its also with me, Please help me how to create IDOC, and also i need that IDOC number.
Tobe frank this is the first time i am going to create IDOC.
Please do needful.
Thanks in advance.

Hi,
Beginners guide for IDoc to File scenario:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
The above link will provide you the step by step details.
Idoc number is contained in the DOCNUM field under EDI_DC segment in the IDoc.
Hope it helps buddy
Thanks
Biswajit

Similar Messages

Need to create Idoc using with BAPI in BP

Hi Experts,
Business Partners are created/changed in SAP either directly by using transaction BP or indirectly created from DTI or using the BAPIBUSISM007_CREATEFROMDATA BAPI for new customers and BAPIBUSISM007_CHANGE to change customers. When a business partner is created or changed via transaction BP an IDOC is generated when the create or change is saved. This IDOC is then sent to the appropriate DTI (Third party) clients to ensure the customers remain in sync.
Now issue is that creates and changes made using a BAPI do not generate an IDOC. Therefore, new customers and customer changes made by DTI clients do update ECC but are not being passed on to Ad Sales since an IDOC is not created. The same is true when a customer is created/changed by Ad Sales. The change is made in ECC via the BAPI but since no IDOC is generated the create/change doesn’t get moved to the DTI clients.
what the IDOC triggering mechanism is for generating IDOCS from the BAPIBUSISM007_CREATEFROMDATA BAPI and the BAPIBUSISM007_CHANGE BAPI. This mechanism should be some type of ALE Message that can be used in the partner profile setup to automatically generate the IDOC.
Any inputs about my issue.
Thanks,
Anji

Hi Experts,
Any updates or suggestions on this issue.
Thanks,
Anji

STEPS for creating IDOC .

I need to creat IDOC for whenever delivery is created .

Hi
Take the correct Idoc type and Message Type and process code from EDBAS and EDMSG tables and use
see the doc
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.
>>>> SAP ALE & IDOC<<<<
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 points for useful Answers
Regards
Anji

I need help to create idoc from scrach.

i need help to create idoc from scrach.

Swamy Katta,
Please read "[the rules|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement]" before you post any further, and confirm that you have read them?
=> Search first, ask questions later please!
Julius

ALE, IDOC - need to send IDOC and create a text file

Hi,
i need to send idoc to some other system and create a text file in that.
I want sent data to Channel Cluster.
what are the settings required for that in transactions
BD54
SCC4
SM59 - which connection is required
WE21 - which type of port
WE20 - which partner
BD64
Is there any other function modules required.
which function module is suitable like MASTER_IDOC_DISTRIBUTE.

Hi,
SM59 - Use TCP/IP Connection with connection type 'T'
WE20 - Partner Name can be logical system name, if it is a vendor/customer you can configure it under the respective names.
Thanks
Krithika

Do we need to create message interfaces for idocs and rfcs thatare imported

do we need to create message interfaces for idocs and rfcs thatare imported
from sap server
in scenarios from sap system to file or vice versa
i knew that we need not create message types
do we also skip creating message interfaces

hi,
you create an abstract message interface for IDOC only if you want to use
them in a BPM (integration process)
for more about IDOCs have a look at my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

I need to create RFC function module which creates the IDOC

Hi-
Any idea how to create RFC function module which creates the outbound IDOC. If you have any sample code please forward to me.
Thanks,
Sony

My Problem is
Whenever they create Invoice using T-code's like FV65(Parked Document), automatically should create IDOC's...
I have used message type FIDCC1 but this message type is usefull only for Posting documents.
1. Whenever they create parked document, entries will be stored in BKPF(Parked Document-Filed-BKPF-BSTAT = 'V') and Bseg....
2. I have to read entries from those tables and should create IDOC...
3. I checked FM's(FI_IDOC_CREATE_FIDCC1, FI_IDOC_PREPARE) but are not useful...
4. Now I need to write one RFC function module and that FM should create the IDOC's....
Can anyone please help me out?
Thanks,
Sony

How to create IDOC from Function module or RFC

Hi all,
I have tested one inbound IDOC for Time Upload to CAT2 using basic type "CATS_INSERT01" in WE19 through function module BAPI_IDOC_INPUT1 .It works well.
Now i need to create this IDOC once the sale order gets created thru BAPI.
For creation of Sale order i wrote one RFC in which i will call the Standard Sale Order Bapi.My question is once the Sale order gets created in that RFC How do i trigger the IDOC for CATS upload.

Hi,
Which SAP product of wich release of which SP are you using ?
The procedure is documented in help.sap.com and in blogs and SDN forum messages.
It means that the use of the SEARCH button should give plenty of answers...
>When I check "Local object" checkbox I get a message "Test objects cannot be created in foreign >namespaces"
As usual, begin your choosen name with an "Z".
Regards,
Olivier

Need to create Customer to multiple sites record in one run.

Hi all,
we have one table called (e.g.) Prospect. To this table we can associate three different sites: one the legal
site, one admin and one for logistic. All the three sites refer to the main Prospect table via the Prospect_id
and related info are all saved into the same Site_all table (the site type is not stored directly into the site_all
table but via a use_site_all table, similarly to what happens with some standard OApps tables).
We need to create the Prospect and associated three sites via an OA Framework page (actually multiple steps).
So to visually resume:
_ Site1 ---- use:legal
Prospect - Site2 -- use:admin
- Site3 --- use:logistic
What's the best approach to achieve the creation of the records in the tables ?
a) to add three EO for the Site table (with related AO) and one big ProspectAllVO view object containing all the fields
from the three EO ?
b) to add just one EO for the site and reference it three times while defiing the ProspectAllVO ?
c) to specify a View Link (but this should be done three times and I'm not sure how to synchronize and manage
the transaction for the creation ?
d) AOB ?
Thanks in advance. Regards.
Giuseppe Naldi

is it really just one IDOC?
I have never seen that SAP just does a part of one IDOC.
the structure of DEBMAS ist like this:
E1KNA1M
--E1KNVVM
E1KNVPM
E1KNVDM
E1KNVIM
--E1KNB1M
which means for your example it should be like this
E1KNA1M
--E1KNVVM
E1KNVPM
E1KNVDM
E1KNVIM
--E1KNVVM
E1KNVPM
E1KNVDM
E1KNVIM
--E1KNB1M
and in this case I am very certain that it would never just process and create the part for one sales area.
Maybe your customer already exists from ealier tests with just one sales area.
Display your IDOC in WE02 or WE05 and make sure you have a value in name1 field

Need to create sale order from the flat file & mail has to be sent

Hi Experts,
I have a requirement to create a sale order from a flat file and once the oder is created, mail has to be sent to customer as well as to internal user with the order details. I want to know how this process can be implemented and what adapters are needed to execute this.
it would be very helpful, if i get an step-by-step procedure.
Points assured for any helpful answers.
Thanks in Advance
Jai

HI Jai,
You need to create two interfaces as file will be sending the Sales oreder details that you need to capture in IDOC or RFC and then have to trigger to create the sales order. For this Standard BAPIs are also available.
These RFC or BAPIs will response with Sales order details that you need to divert to Mail adapter with the use of BPM and also have to go for Async to Sync bridge.
File -
>XI (BPM) ---> BAPI/RFC (Request)
MailAdapter <- XI (BPM) <--- BAPI/RFC (Response)
For this refer below links for step by step
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit - File to RFC
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1685 [original link is broken] [original link is broken] [original link is broken] - File to Mail
/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm - Walk through BPM
/people/siva.maranani/blog/2005/05/22/schedule-your-bpm - Schedule BPM
/people/sriram.vasudevan3/blog/2005/01/11/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] - Use of Synch - Asynch bridge in ccBPM
If you will use IDOC then In IDOC inbound processing you need to trigger for Sales order creation and then have to send the Sales Order generated IDOC as an Outbound to Mail Adapter
Flat file -
> XI ---> IDOC
IDOC -
> XI ---> Mail
This will be bit easy scenario to develope as compare to using BAPI with BPM
/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping - Any flat file to any Idoc
configuring IDOC-XI-Mail scenario using following web-log:
/people/michal.krawczyk2/blog/2005/03/07/mail-adapter-xi--how-to-implement-dynamic-mail-address
/people/sravya.talanki2/blog/2005/08/18/triggering-e-mails-to-shared-folders-of-sap-is-u - Triggering Email from folder
Thanks
Swarup

Creating idocs based on invoice number ocurrences

Hi ,
I want to create idocs based on invoice numbers .
Lets say i have a file coming in from sender system
Invoice1 material customer value
Invoice1 materail1 ..........
imvoice2 material2.....
invoice2 material1.....
invoice1 material3..
Invoice3. material4....
So for Invoice1 only one Idoc should be created similarly for invoice 2 which is ocurring twice in the file
only 1 idoc should be created
Let me know how to achieve this .. by UDF , or by split by value
please help
thnx
Chirdip

Hi,
Change the IDOC occurance to 0-unbounded.Export the xsd change the occurance and import it to external definition.
Map Like below:
invoice number--removecontext--sort--splitbyvalue(valuechange)--IDOC
other fields you need to map like below.
invoice number--removecontext--sortbykey--SplibyValue(Each)---IDOC fields
source field----removecontext------
Regards,
Prakasu.M

Help needed in inbound IDoc for ORDERS....

Hello all,
I need help in IDoc for ORDERS.. Here is the situation. I have an ORDERS IDoc coming to my SAP system from my customer. When I see the SO it creates.. it says that it has incomplete data.. Information like pricing, inco terms, payment terms. load data, load date etc. is not filled in. How do get those filled automatically.. my customer can not, obviously, give me all the information needed for the SO.. Where do I configure and how?
Thanks,
Charles

Hi,
You can use user exits available in FM IDOC_INPUT_ORDERS to populate additional information.
Also you can use form CUSTOMER_FUNCTION_DYNPRO to populate additional information for BDC screens of VA01. This form is available in FM IDOC_INPUT_ORDERS as well.
Regards,
Ferry Lianto
Please reward points if helpful.

Doubt in creating idocs

Hi
I had created IDOCS by following this procedure
Step 1 Analyse Hierarchy Levels:
Analyse the data relationships being processed in the interface. Define the appropriate hierarchical Parent-to-Child relationships.
Navigate to transaction code WEDI
Transaction WEDI displays the IDOC main menu. This allows navigation around the various development and control areas to create a customised IDOC.
Step 2 Create a new segment:
via wedi : Development - IDOC Segments or Transaction code WE31.
Enter segment name and click on Create.
The name of the segment type must start with Z1 , and have a maximum of eight characters.
Enter description and enter the relevant field names and data elements.
The segment should represent a structure in the program so for each field in the segment a field name and a data element must be defined.
Save the segment and enter Person Responsible and Processing Person .
Go to Edit and Set Release.
Repeat this procedure for each new Segment in the IDOC.
Step 3 Create a new IDOC Type
via wedi Development - IDOC Types or Transaction WE30.
Enter segment name (starting with Z), click on Basic Type and then Create.
Create as new, enter Person Responsible and Processing Person and enter description.
On Create Basic Type screen decide where segments should be inserted and go to Edit/Create Segment.
Complete relevant fields in the Maintain Attributes screen:
From the relevant segments created in Step 2 enter the Segment type and if mandatory segment.
The Minimum and Maximum number of segments to be allowed in the sequence. (One minimum and one maximum if segment is mandatory).
The Parent Segment and Hierarchy Level will be automatically created depending on where in the IDOC tree you decided to create that particular segment.
Repeat this process for each segment needed in the IDOC type, deciding whether to add the next segments at the same level or as a Child.
When IDOC created return to initial screen. Go to Edit and Set Release.
Go to Transaction WE60 to view the IDoc Type you have created.
Step 4 Create new Message Type
via wedi Development - Message Types or Transaction WE81.
Display/Change and click on New Entries
Create a new Message Type and Save.
Step 5 Link Message Type to IDOC Type
via wedi Development - IDOC Type/Message or Transaction WE82.
Display/Change and then click on New Entries.
Enter Message Type, Basic Type (IDOC Type) and Release (46C) and Save.
Now my problem from this step
Step 6 Create an entry in EDP13 via transactions WE20 and BD64.
The partner profile for the Idoc must be set up and generated in the transaction BD64 and transaction WE20.
WE20 Add Message Type to appropriate Partner Type, Enter Message Type, Receiver Port and Idoc Type and Save.
BD64 Create a Model View, Enter Sender and Receiver Ports, Attach Message Type. Go to Environment on Menu and click on Generate Partner Profiles and generate (not save) profile.
From where i have to add message type to partner type
Can any one explain me clearly step by step after this step
Helpfull points will be surely rewarded
Regards
Pavan

Hi Pavan,
You have the Partner number? which is nothing but your Logical system name or vendor or customer. I think in your case, it is Logical system.
Select or create an logical system. If already exist, select the option LS in the left hand side and display it. IN WE20. Now, give you Message type and save it.
But, If we say in your case as ALE, Goto Tcode SALE, Nagivate and create logical system for sender and reciver.
2. Then assign these Logical system to the clients.
3. GOto Tcode SM59 and create RFC destination.
4.Tcode- BD64 , Display it and select create model view options. and save it.
5. Now, go for Assign message type and assingn the message type alon with your logical system name for recevier and sender.
6. Goto Status bar ENVIRONMENT and select generate partner profile. Automatically, a partner profile will be generated.
7.Now GOTO EDIT , Model view -
distribute.
Thanks
Manju.

Want to create IDoc to Webservice Scenario

Hi All,
I wan to do Idoc to Web Service Scenario, I have already done Idoc to File Scenario and I have mapped the file of both end in ESR and I am done with Configuration in Integration Directory.
Now If I want to convert it to IDoc to Web Service Scenario, what all steps need to be done. and also want to know that How we can access and Send the files from Web Service to PI 7.1. As such web service is not available need to create the same also.
Can anyone provide How to guide on this scenario.
Regards,
Nitin Patil
Edited by: Nitin Patil on Dec 19, 2008 2:44 PM

Hey,
 as you have familiar with idoc to file, the idoc to webservice scenario is not different.
 You need to do the ALE settings on the R\3 side. import the Idoc in XI.
 Now for mapping purpose you need the source and the target structure.
 In case of webservice you need to import the WSLD (unlike the file in which you wold have created the data type and message type)
In order to import the WSLD, you need to do following things.
Ou require NWDS and the following settings needs to be done
Deployement of Web Services:-
Step 1)
 Goto Windows->Open Perspective->J2EE development.
Step 2)
 Goto File->new->Ejb module(give project name).
Step 3)
 Right Click on the <project name> eg. work_ejb select new->Ejb.
Step 4)
 Give an appropriate EJB name and default package (eg. com.xxx.yyy).
 Also select stateless Ejb.
 Click next then next and then next.
Step 5)
 Add method with an appropriate name.
 Mention the return type and also assign the required parameters.
 Logic is written in the EJB module bean.
Step 6)
 Right click on the <project name> and build.
 Creates .jar
Step 7)
 Goto File->new->Enterprise Application project(to create EAR)
Step 8)
 Give project name, assign EJB and build.
 Creates EAR.
Step 9)
 Right Click on the EJB.
 Goto new->Web services.
 Specify name of the web service.
 Specify EAR in the WEB service.
Step 10)
 Build EAR.
 Build Ejb.
Step 11)
 Goto Windows->Prefrences->SAP j2EE engine.
 Give the message server host name.
Step 12)
 Right Click on EAR and deploy.
Step 13)
 Goto-> http://<host name>:<port no.>/index.
Step 14)
 Choose the web service name,test it and download it(default WSDL).
Step 15)
 Import port(WSDL) in External definition of SAP PI.
After you import the wsld, you need to follow the same procedure as idoc to file.
regards,
Milan

VKP0 is not to be maintained as mandatory condition while creating IDOC

We have a very awkward need from our client.The bussiness doesnt want the condition type VKP0 to be mandatory condition while creating IDOC for article master data.
In the bussiness terms they send some articles to POS without creating price.They dont want to have the value of KONWERT field as 'ZERO'..
We have upgraded ECC 5.0(IS Retail) to ECC 6.0(IS Retail).It was techinical upgrade hence no functional configuration has been done.
Moreover we have compared POS outbound profile in ECC 6.0 with ECC 5.0.Every configuration is same and all required prerequisites for POS Outbound profile are same in both the versions.The Idoc in ECC 5.0 is getting created even though the price of the artilce is not required to be mainatained.
All of us know that if prices are not maintained system shows'X' mark in price field in T.Code WPER2.
But,instead the IDOC is getting created in ECC 5.0.
Please help us to make the IDOC creation possible in ECC 6.0 even without creating the price.
Edited by: ajay das on Nov 15, 2008 8:00 PM

Hello Ajay,
Are IDocs for other transactional data getting created? In case these are, you can try to check the message control settings.
Regards,
Nimish

Need to create IDOC

Similar Messages

Maybe you are looking for