IDoc config

Hi,
i've done all the necessary configurations like SALE,WE21,WE20,...in development server.Now can i move these settings to production? If yes how should I do it?
If we can't move these settings to production server, do we need to create all these configurations in production server again?
thanks,
ravi

Yes.
You need to create them in ur Target server as well.
Partner Profiles , Port and the setting has to be done .
regards,
vijay

Similar Messages

Receiver IDOC Config

Hi there
Is there some documentation that could help me find a technical issue I have with my idoc config? Im looking for a step by step showing where I must check for all the config. like in sm59 and idx1, but explaining what everything is used for. I seem to get idoc status 51 if I try and reprocess some old idocs that have worked before so I guess there is something wrong with the technical side.
Thanx,
Jan

Hello again,
I have 2 systems, XID150 - sender and ECD999 receiver.
In SM59 in ECD999 I have a ABAP Connection, XIDCLNT150 pointing to XI which is type 3. I tested it and it works.
In We21 in ECD999 I have a Transactional RFC SAPXID with the RFC Destination XIDCLNT150.
In We20 in ECD999 I have a profile under Type KU, B006 and in the Inbound parameters I have the idoc WALREQ01 which im using.
In We19 I create the idoc and Start inbound processing and it gives me: Partner profile found with status green.
If I go to We02 and look at the Idoc which was successful in we19 it shows status 51 as I mentioned before.
On the XI side:
In sm59, I have ECDCLNT999 pointing to my receiver system. Connection tested and works.
In idx1 I have SAPECD as a port name and it points to client 999 on RFC ECDCLNT999. with Partner Nr B006 and Type KU.
and in idx2 I have the IDOC loaded there. So everything seems to be working fine except for we02.

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

Doubt on IDoc Config

Hi xperts,
May i request for clarifications on points to consider for configuring inbound and outbound idoc?
I have read couple of blogs for reference yet posting to get more clarification
what all configs required in R3 to post idoc to xi and vice versa? and in this case what basic points to be considered...something like logical sys name to be same as business syste etc? pls share .

Hi,
Need to follow like this
SAP R/3
1. Create a partner profile using tcode we20 (need to maintain an entry in tables based on partner type)
2. Create a RFC destination of Type 3 pointing to XI
3. Create a port and assign RFC destination
4. Create an entry of outbound message type and assign port..
PI
1. Create a RFC destination of type of 3 pointing to R/3
2. Create a port using idx1...and assign above RFC destination name
in order to receive the data from R/3 business system/service created for R/3 should contain logical system name as partner profile name...created in R/3
Hope this clears all your queries...
Regards
Rajesh

IDOC Config Problem... Transaction BDFG giving error mesage..

Hi ,
Transaction BDFG, If i click on the change button i get an error as Message (Idoc Message Name) has not been generated,Furthur Processing is not problem. Reason being in Table EDBG the Generated field for Idoc Message is blank.
How can i get in generated.. Do help..

Hi ,
Could you please check the below links.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/406efa7e-388a-2910-f9b8-81913b0ca57f?QuickLink=index&overridelayout=true
http://help.sap.com/saphelp_erp2004/helpdata/en/00/a814b5d05b11d6b2ca00508b6b8b11/content.htm
Regards,
Ratheesh BS

Missing IDoc - config question

I need to send SHPORD.DELVRY03 IDocs from SAP and convert it in XI to a file.
The outgoing IDoc in the SAP system has status
"03 - Data passed to port OK"
"The IDoc was sent to an R/3 System or an external program via a transactional RFC.
The TID is 0A62019724E14444EF7F0311."
Nothing however shows up in XI.
Any idea what to look into, what I need to check?
Don't know where to start, the connections were
set up between the source SAP system and the XI box.
Thanks a lot,
Viktor

Hi,
Is it may be because of Authorization Problem?
Just check this Thread.
I::000 what does it mean
Also check this-
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/frameset.htm
Hope this helps,
regards,
Moorthy

BAPI IDoc Config for LSMW

Hello all,
I would like to use LSMW to change CRM Business Partner data via BAPI. I have located the correct BAPI to use, but I now need to perform the proper port config, Partner profile setup, etc. Does anyone have straightforward documentation on how to convert this BAPI so that it can be used by LSMW? The Bus. Object is BUS1006005, but it has not yet been prepared for use by LSMW. I have plenty of LSMW experience using BDC, so full LSMW documentation is not necessary. Thanks in advance for your help.
Kind Regards,
Jason

Hi Jason,
The port config & Partner profile setup, etc. are generally done by basis consulatants. I think bass consultants can help in this as the Ports are beng created one time in a system.
Ashvender

IDoc Configuration steps

Hi Guru's
Can any one of you explain the Idoc configuration steps in brief with t.codes?
rgds,

Cherukuri:
<a href="http://www.scribd.com/doc/24447/SAP-R3-IDoc-Cookbook-for-EDI-and-Interfaces-by-Axel-Angeli">IDoc Config Guide</a>
In case the link doesn't work:
Google this: "Axel Angeli SAP R/3 guide to Idoc"
Idoc Transactions:
Transaction Code
SALE:Display ALE Customizing
SM59:RFC Destinations (Display/Maintain)
BD64:Maintenance of Distribution Model
BD82:Generate Partner Profiles
WE20:Partner Profiles
WE21:Port definition
WE30:IDoc Type Development ( View Segments of an IDOC )
WE60:IDOC segment field description
WE19:Test tool for IDOC Processing
WE05:IDOC Lists
WE09:Search for IDOC in Database
BD87:Status Monitor for ALE Messages (Process IDOC manually)
BD73:Start Error Handling for Non-Posted IDocs
WEDI:IDOC and EDI Basis
Change Pointers:
BD50:Activate change pointer for message type
BD61:Activate Change pointer generally
BD52:Triggering table and field name
BD21:Creates and sends the Idoc for Change pointer method
BD59:Set the field for Filter in Distribution Model
BD95:Along with BD59 , used for setting a filter in Distribution model
BD60:Assigning FM to the outbound IDOC , and specifying Change pointer Table and Object
BD56:Segment Filtering
Inbound IDOC:
WE81:Create Logical message types
WE82:Assign Messages for IDoc Type
WE31:Development IDoc Segment
WE57:Assignment of FM to Log, Message and IDoc Type
BD51:Characteristics of Inbound FM
WE42:Creating Inbound Process Code
BD67:Function modules for Inbound ALE-EDI
Assign points if info helps Vj

Idoc settings for Backend Contract creation in SRM 5.0

Hello,
Im working on SRM 5.0 (HP 11) and want to create a Backend contract in R/3 (46C) directly.
I do not need Local Contracts or GOAs en SRM!
As I interprete the config guide for Sourcing (page 59 and 70-75, the scenario I need uses the BADIs:
BBP_DETERMINE_LOGSYS (determining Back End System)
BBP_CTR_BE_CREATE (for Mapping SRM settings with R/3)
I also understand that the Idoc configuration only needs to be done in the backend!!? (page 73 / 74)
Trx: WE42 and WE20.
Is this correct? Or do I have to maintain also the the IDOCs config in the SRM system?
Thanks for any clue.
Aart

Hi,
Pls refer the foll thread for all settings:
Follow-on contract from Bid Invitation
BR,
Disha.
Do reward points for useful answers.

Third party is sending IDOC (EDI_DC40 relevant?)

Hi,
I need to send an IDOC from a third party to an SAP system via XI. My problem is the first part: ThirdParty->IDOC.
Now I have done the following steps:
- RFC connection between Third party and XI works fine
- define Third Party as busines system in SLD and assign a logical system name to it
- enter logical system name in BD54 in XI and SAP
- define sending IDOC communication channel
- define receiving IDOC communication channel
My question for the sending part:
Are there any entries in EDI_DC40 for the sending third party system neccessary for XI (Sender System/Port/... Receiver System/Port/... etc.)? If yes which entries are neccessary?

Logical System name you should maintain when you are creating a Business System inSLD not in BD54 of XI, then you should create the same logical system in SAP using BD54 transaction and maintain a partner profile and inbound idoc config.
After you import the Business System into Integration Directory, then you should open the business system (double click) and menu Service --> Adapter-Specific Identifiers and make sure it is populated.
regards
SKM

Configuring IDOC Listener on MII 12.1

Hi,
I had a basic question around the configuration.
This is from 12.1 help:
"The SAP Java Resource Adapter (SAP JRA) server is used to connect to SAP ERP Central Component (SAP ECC) to receive remote function calls (RFC) and IDocs. You can use the asynchronous HTTP interface to post data to SAP MII for asynchronous transaction processing."
In this regard is it mandatory to first configure SAP JRA on NW and then proceed with the IDOC specific config both on the R/3 as well as NW side?
The reason I ask this is that we are currently struggling with this config on 12.1.8 (build 30) where the BASIS folks are observing that the system hangs when they try to add enteries to the XMIIIDOC component . Before going through with the IDOC config they made sure that the JRA is configured and followed the steps as mentioned in the 12.1 installation guide under "Configuring JRA for JRA Actions" & "Cloning the default JRA Config" sections.They are simultaneously also following up in the NW forums to find a solution.
Additionally I had another question (this one's specifically for MIke Appleby ). Would one have to follow similar config steps as IDOC when configuring the RFC listener , atleast from the NW CE perspective? We are trying to download Control Recipes from R/3.
Thanks
Udayan

Hi Udayan,
Yes, the configuration for the RFC Listener is essentially the same as the IDoc Listener, except the binding is different (do not change either type from the default values and you should be fine).
The differences between the two Listener types are really on the ECC side. The installation instructions for Batch Manufacturing included the RFC Listener setup. Keep meaning to write a separate document for RFC Listeners, but haven't yet.
One general note of caution for all readers:
Do not reuse ProgIDs from an IDoc Listener in an RFC Listener and vice versa. Only use a unique ProgID once (and deleting them from one Listener or MII server to use them elsewhere is generally not advisable).
Roughly 90% of the tickets entered for IDoc Listeners with MII are because of ProgIDs used in more than one place.
Regards,
Mike

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.

Configure idocs for User management ack settings?

1. IDOC config idoc says acknowledgments should not be requested, and run idx_noale ? why should we turn off and how to do this ?
2. IDOCs sent to IS should not be processed by IDoc adapter, advises insert the relevant idoc types into exception table, execute report idx_select_idoctyp_without_is
why we need to configure explicitly for each relavant ido types?
thanks

Hi Kumar,
Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender. Acknowledgements are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments. The RNIF and CIDX adapters are exceptions to this rule, since they also support scenario-dependent application acknowledgments. Sender adapters of the Adapter Engine do not request any acknowledgments.
This means, JDBC adapter does only send system acks, however IDoc adapter is requesting application acks. Therefore as mentioned by the previous poster, you have to disable acks for this scenario using report IDX_NOALE.
Also go through these documents for any further help:
http://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how to handle acknowledgments for idoc.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
I hope this clears all your doubts.
Regards,
abhy
PS: AWARD POINTS FOR HELPFUL ANSWERS.

Data Ditribution Model BD64 config

Hi All,
I want to know when do i need to do the BD64 configuration. In my project i checked most of the time bd64 config is missing still idocs are moved to SAP system or PI or legacy sytem without issue.
Few BD64 config they have done which are attached with filters. Can my idoc config be complete without creating distribution model. if yes from where it get's destination server( is it from the RFC connected to port) !!! ...and when is it required for bd64 model

Generally you configure the Distribution model when you are working with Master Data.
Based on the Distribution model, SAP generates the IDOCs for each system, if there are more than one LS involved.
If you want to use the Message Reduction for standard message type, you need to use the Distribution Model.
If you want to do the filtering based on the data, you can specify that in the DM.
If you are using the FM MASTER_IDOC_DISTRIBUTE, you don't need to maintain the Distribution Model. It can generate the IDOC based on your specified control record.
Regards,
Naimesh Patel

Error while processing XML for more than 5 serial no of a material

Dear Expert
While processing Idoc through some third party system we are getting foloowing error
" No Batch input data for screen RIEQUI21 1000"
As this error is related with serial no. But this happening only when we are using more than 5 Quantity for a material in a sales order and all having different Serial No. and orders having less than 5 quantity of material is running properly.
We are using order type "ORDER 05" in Idoc config in SAP.
Is there any note available in SAP so that we can take more than 5 serial no for a material.
Please revert with your valuable concern.
Regards,
Surendra

Hi Gurus,
Please revert with your responses. If you need any input from my side. please let me know.
Its an issue of high priority.
Thanks
Surendra

IDoc config

Similar Messages

Maybe you are looking for