IDOC Header Configuration

hi experts,
tell me about the IDOC Fields and its Creation.
(Where to define
Reciever Port, Partnernumber
Sender Port, Partnernumber
actually i created one and for all the fields, but when i tried with those it shows status message as 37 ( Sender port)
help me to resolve this
tell me how the entire system ( of outbound idoc) works
thanks in advance
nikhilbos

Hi,
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):
Also refer ALE configuration for pushing idocs from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
Thnx
Chirag Gohil

Similar Messages

File- XI- IDoc: Idoc header data not saved correctly

Hi guys!
I have a very strange problem:
I have a file to xi to IDoc scenario. Everything seems to be fine, IDoc is created in target system, but with strange error: <MESCOD>XX</MESCOD> segment is not written in IDoc header segment. This segment is available in message sent to ECC (after mapping), so there is no problem with ommiting the segment in mapping. But it's not saved.
This scenario worx fine in QA, but not in PRO.
Any ideas, what to look at?
Thanx a lot! Olian

Hi,
check the IDoc which was in PROD. and see the ibound status and actual reason .
depending upon the actual status you can resolve the issue.
Chilla

Idoc adapter configuration

while idoc adapter configuration we uncheck the option " apply control record values from payload" why and when it will be usefull?

Hi Sudhakar,
When you want to map control record values from the Target payload .....
Then you choose the option apply control record from payload.
Follow the link below to understand the concept better....
(Configuring the Receiver IDoc Adapter --> Fields of the IDoc Control Record)
http://help.sap.com/saphelp_nw04/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/frameset.htm
Regards,
Sushil.

IDoc Adapter configuration for very high volumes

Hi PI Expert,
I'd like to have some tips about Idoc Adapter configuration in case of very very hudge volumes in "file to Idoc scenario" (adressing ECC) : How to optimize Idoc transmission time PI -> ECC ?
=> parallelization PI -> ECC by using differents comm channel IDocs with differents RFC destinations ?.
=> some other technical parameters in adapter IDoc
=> ...
Thanks a lot
Best regard.
Etienne

Hi,
for sure idoc bundling will greatly increase performance: https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/2762. [original link is broken] [original link is broken] [original link is broken]
If you are in 7.1 you can also leverage message packaging: http://help.sap.com/saphelp_nwpi71/helpdata/en/46/79e8e13872275ae10000000a11466f/frameset.htm
Regards,
Sergio

How to send single person-records with HRMD_A Idoc and change Idoc header?

Hello group,
we have different companies in our SAP system (BUKRS). Now when an infotype is changed the changepointers are activated and using program RBDMIDOC we can send Idocs of type HRMD_A to f.i. files. In order to have these files distributed to different parties depending on BUKRS of the person we would like to have HRMD_A to deliver single records, an Idoc for each person and the Idoc header fields for variant and function should be filled so that the partner profile would distribute the Idoc to the partie.
Is this possible? And if yes how?
Regards, Léon Hoeneveld The Netherlands

Transaction PFAL lets me trigger the Idoc manually, but with a job for RBDMIDOC this is automatically.
I found fm RH_HRMD_BLOCK_SIZE in wich you can enhance the code to set the block size for an Idoc-type to 1.
But now I still have to change the Idoc header with an enhancement of user-exit.
HRALE00OUTBOUND_IDOC BADi does not have the functionallity.
Regards, Léon Hoeneveld

IDoc to File with different file name and data based on the IDoc header dat

Hi,
I got a requirement to implement IDOC to file senario. In this the Converted file should have the file name and file content based on IDoc Header data. Means If one of the IDoc header field value is
'A' - then the file name recieved by reciever system should be 'A.txt' and with the columns A B C D F.
'B' - then the file name recieved by reciever system should be 'B.txt' and with the columns C D F.
In both the case IDoc message type is same.
Please suggest me what i need to do to achieve this.
Thanks in Advance. ...
Regards
Sri

Hi,
As per my requirement, we need to create one file for each IDoc based on IDoc header data. SAP program generates 10 IDocs for each run. All 10 IDoc's message type is same. Each IDoc has one header record with the file name. Base on the name in the IDoc header record, file needs to be created with different columns and file name. Means..
IDoc 01- Header Description contains 'A' - than file will be generated should have name as 'A.txt' and columns 'parent' 'child' 'descripion'.
IDoc 02- Header Description contains 'B' - than file will be generated should have name as 'B.txt' and columns 'Name' 'Department' 'Description'.
IDoc 10- Header Description contains 'J' - than file will be generated should have name as 'J.txt' and columns 'Order No' 'Materail' 'Description'.
Hope this will give more clarity on my requirement. Please let me if you are still not clear on requirement.
Thanks for your all help..
Thanks & Regards
Sreeni

Idoc Sender Configurations

Hi,
Our requirement is to do Idoc to File scenario in which what are all the configurations that are to be done in R/3 and as well as in XI server.
regards,
Kishore

Hi Kishore,
Please go through /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
also i give a quick checklist, chk it out.
1)Create an RFC destination to XI in the sender SAP system using SM59
2)Create a transactional port to XI using the RFC destination created in the above step
3)Create a Partner agreement usign transaction we20 and port using we21 in the sender SAP system
4)Create a logical system using transaction bd54 for the partner agreement created in the above step
5)Select an IDOC using transaction we19 and change the EDIDC header recepient port & LS name
6)Create an RFC destination to the Sender SAP system using SM59
7)Create port to sender system using idx1 in the XI system for the RFC destination created in the above step
8)Create SLD entries(technical and business system) for the sender SAP system.
In IR , import IDOC metadata, create ur target XSD , create ur Message Mapping , Interface Mapping, thats it.
In ID, import ur sender R/3 system & receiver systems, U dont need a IDOC sender CC , so only File receiver CC is reqd. Now create a receiver determination, interface determination & receiver agreement ,activate & ur done.
Use WE19 , select an IDOC and do an outbound processing and u shud see the IDOC in XI.
Rgds
joel
Edited by: joel trinidade on Feb 23, 2009 2:44 PM

Set/change dynamic header configuration from ABAP Proxies

This question is with reference to Async ABAP Proxies.
Is it possible to set or change dynamic configuration header of an outbound (client) proxy, from within an inbound (server) proxy ? If it is, how do I do it?
Can someone please advise?
Thanks,
Badari

I am sorry to have to say, that this is not possible.
Regards
Stefan

IDOC Header Record

Our scenario is File(s) ---> XI -
> IDOC
We are receiving 3 Different Files, with Employee information from 3 different Countries and using XI , the records will be posted into R/3. Each record from the file will be treated as an IDoc.
The File is going to contain the Header Record, followed by the Detail records.
The header record will determine from whom this file was sent and we need to map the header info with the Control record.
How can I achieve the above task of separating the Header Record and the other detail records in the Message Mapping.
I would Greatly appreciate the Help.

hi Karen,
if you target XML fill contain
one header and many details (which have to be transformed into many idocs) then you can do it in
1:N mapping
1 file N idocs
just map the header so that it occures many times
(as many as the details section)
if I understand your issue correctly
Regards,
michal

Setting up independant dual-head configuration in the usual way?

I'm preparing to set up a dual monitor system pretty soon using an ATI Radeon card. I went through the wiki and read what the ATI page has to say:
Independent dual-headed setups can be configured the usual way
The problem is that it gives no indication of what the usual way is. I vaguely have an idea that I might need xinerama, but couldn't find a wiki page on that either... I've also tried googling with limited results.
Is anyone able to let me know of a good resource for this?
Last edited by phunni (2011-12-26 20:15:38)

Check this out: https://wiki.archlinux.org/index.php/Xorg
I'm using a radeon 6870 with kde and in my case I was able to set up my dual screens using Settings > System Settings > Hardware > Display and Monitor > Size & Orientation, clicking Save as Default once I had things set up the way I wanted made the settings permanent
If you're going to use Ati's catalyst control center driver then you should probably also read this page: https://wiki.archlinux.org/index.php/ATI_Catalyst

Idoc Adapter Configuration Issues

Dear Collegues,
I have given up almost all hope on configuring my Idoc adapter as I have an error message that I am not sure of how to fix; I have read just about everything I can get my hands on....any help would be so much appreciated:
Scenario: Demonstrate a simple 'proof of concept' to send MATMAS from R3 ->XI -> R3
Sending system: [R3 4.6b] CL0510
Rec'g system: [R3 4.6b] EL0510
XI system 3.0: NXL220
Current error message in outbound RFC layer of CLO:
No service for system SAPCL0, client 510 in Integration Directory
Per the documentation I have done the following:
- RFC connections are all complete
- Port and Partner Profiles complete
- ALE model from sender for MATMAS
- IDX1 in nxl for ports
- IDX2 - matmas metadata
- Integration Builder [config]:
 *Technical and Biz systems set up
 *CL0510 is set up as 'services w/o party' and there is
 a generated idoc channel.
 *The Adapter Specific Identifier is the CL0510 log
 syst.
 *Receiver Determination is created w/
 idoc_inbound_asychronous as interface; not sure
 what "namespace" is so I threw the word Idoc in there
 *Interface Determination is created w/ above
 parameters except the receiver party and service have
 asterisks in them I can't seem to remove
 *Sender and Rec'r Agreements set up [again what goes
 in that namespace field?]
I think that identifies all of the configuration I have attempted to enter. I have been only able to read documentation and weblogs as XI training won't be happening for me and my collegues until another several weeks.
Thanks so much,
Jennifer Edmondson
Intel Corp, AZ

Hi Jennifer,
for the inbound to XI, e.g. CL0510 you don't have a sender agreement since when you setup up the WE21 trfc Port on CL0510 it points to the XI system as a regular type T SM59 connection. On the connection you can enable the TRACE flag and see in the trace what payload got sent and any errors. I had a problem with that as my user / password to the XI machine was wrong.
The other part I'm missing from your message is, did you do all the Repository stuff beforehand, e.g. import the IDOCs for each Software Components(defined in the SLD, Tech and Buiz System), then when you use the dropdown in the Directory the Namespaces will default as the urn:sap-com:document:sap:idoc:message. Again once you have done the repository there is no need to write namespaces by hand at all. Do not put an IDOC into a Message Interface, may be into an action if you like to put a scenario into the IR (not necessary).
On the Receiving IDOC Adapter you will specify all the RFC stuff for the EL0510 system and this one goes into an receiver agreement.
I'm sending MATMAS from R/3 to XI to File Adapter or SOAP and no issues at all.
On CLN510 in BD87 does the IDOC has a status of send? Does it look ok?
I hope this helps. I can make some screenshots of my config if that helps. Send me an e-mail to [email protected]
Cheers
Stefan

Idoc Communication Configurations and Proxy Runtime Configurations for PI

We have a fresh PI 7.1 system, fresh ECC6 system, and an existing 4.6C system.
is there any blog/doc with step-by-step instructioins/screenshots for following tasks:
1. Configuring Abap proxy runtime between ECC6 and PI 7.1 Systems, for using sproxy from ECC6.
2. Configuring for IDOC communication between ECC6 and PI 7.1
3. Configuring for IDOC communication between 4.6C system and PI 7.1
It involves creating of sm59 rfc destination creations, usage of idoc related transactions on PI system and the other system.. I searched on sdn/forum, but it seems to be addressing specific issues faced.
Pls suggest any step-by-step instructions docs/blogs available.
thanks in advance.
Madhu.

Madhu,
Refer the links below:
1. /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
2& 3 :
https://wiki.sdn.sap.com/wiki/display/XI/SAPR3%28Idocs%29ToXI--Steps+Summarized
http://www.riyaz.net/blog/xipi-settings-in-r3-partner-system-to-receive-idocs/
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c&overridelayout=true
http://www.riyaz.net/blog/beginners-guide-to-ale-and-idocs-a-step-by-step-approach/
Also, I think u hv just started learning XI ..so following link might help:
http://wiki.sdn.sap.com/wiki/display/NWTech/QAforPI-Onestopforall%28Part-1%29

ME59 Purchase order outbound idoc header text missing in segment

Hi All,
When Purchase Order created via ME59 for third party vendor Outbound Idoc is created but Header Text of PO not copied into IDOC Segment.This Problem occurs when PO has sales order assignment.
Please Advice..
Thanks,
Vinod.

Hi Ankur,
I am not an expert in this area but I'm looking on an ORDERS05 iDoc where I have the following data for E1EDK14:
E1EDK14 014:
QUALF: 014
ORGID: [Purchasing organization ID]
E1EDK14 009:
QUALF: 009
ORGID: [Purchasing Group ID]
E1EDK14 013:
QUALF: 013
ORGID: [Purchase Order type, e.g. EC]
E1EDK14 011:
QUALF: 011
ORGID: [Company Code]
Hope this helps!
Regards,
Kristoffer

Can anybody explain all the details about idoc like configuration settings etc..

Hi all can anybody explain the idoc configuration settings, communication channels sender and receiver settings

Hi,
Common steps in both Sender and Receiver:
Create logical system and assign to client
Create RFC Destinations in SM59
Create RFC Ports in WE21
Steps in Sender
Create table in SE11 and insert data
Create Segments in Tcode WE31.Define the table fields in segment
Create basic IDOC type in WE30.Specify the above created segment name,save and release the IDOC
Create message type in WE81
Assign message type to IDOC type in WE82 and release
Create partner profile in BD64,add the message type ,specify sender,receiver,message type and generate partner profile and execute.Distribute the model view
Check the partner profile in WE20
Develop a report in SE38 with code that transfers the data from source to destination
Execute the report and specify the fields to be transferred
Check the control records in WE02
Steps in Receiver:
Create an update function module in SE37
Assign the function module to logical message
Define input method in Tcode BD51
Create process code in WE42
Generate partner profile in BD64
After executing the report in sender system check in the destination system table wheather the fields are transferred
In this case a custom table has been created in sender and receiver with same structure.We can even transfer the standard table fields by using idocs
Thanks & Regards,
Sravanthi Polu

Idoc ACCONF configuration

Hi friends,
We have inbound INVOIC message type configured in our system to post vendor invoices for both MM ( process code INVL ) and FI ( process code INVF ).
Upon the idoc posting is complete the requirement is to send a ACCONF idoc back to the sender with the status on the invoice idoc posting. I'm having trouble finding any information on what needs to be set-up to trigger this ACCONF Idoc type ACCONF01I.
Can anyone help with this?
Thanks in advance for your time.

Hi,
I am not sure if this is the best way how to create your IDoc but you can try to use Business transaction event. There is event for posting FI documents. You can try to use this event to call FM which will generate your IDoc. Another possibly better way might be to define your IDoc as output message for FI document. Hence SAP will generate it automatically after creating FI document. You can find some examples of setting IDoc as output message in transaction NACE. Look for output types with word EDI in description. I would try the second option first.
Cheers

IDOC Header Configuration

Similar Messages

Maybe you are looking for