Idocs?!? Outbond and Inbond Idocs??

Hi Gurus,
I've some doubts about idocs...
My client has a requirement in order to integrate Sap with other foreign system, and has adopted the solution Java Caps + Idocs. I've been reading some documents about Java Caps and idocs, and as far as i know the creation of the Idoc it's done via RFC, this is, every time that the RFC is called from the other system , do its procedure, creates and sends the idocs.
Well my doubt starts here... Is it possible to send the Idoc to other system without order from the other system? Can i create the Idoc and sent it directly to the other system without action from the other system ?
Thanks in Advance,
Regards,
João Martins

Hi João,
joao martins wrote:
> For what i understanded it's that i can actually create the idoc before the RFC be called, but the only way to reach the destination it's the host call the RFC. Is that it?
Yes, that's how I understand the IDoc and RFC thing.
Yes we realized it like you described it. The external system triggers the SAP-IDoc-pool every 5 minutes to catch the new IDocs and process the data. But I cannot say anything about the external server program to you, because I didn't wrote it (this one has done an external company... )
Point Recognition Program at SDN
thanks, regards
Steffen

Similar Messages

Extra fields IDOC WMTOID01 and L IDOC CREATE WMTOID01

I am using the function module L_IDOC_CREATE_WMTOID01 to create an IDOC
WMTOID01. The problem is thet I need to add a field to the IDOC , I have
done this my creating an extention WMTOID01 and I have made an entry for the
Message Type WMTORD.
But when i try to populate a value in the new segment that i'v created, i find that the segment isnt added to the IDOC_DATA structure.
Could you tell me what i am missing ?

Mani,
Please explain -
1. IDoc is inbound or outbound (to SAP)?
2. What document is created by processing the IDoc?
3. What is the entire document flow?
4. In WE02, you get an error message, have you already created your IDoc? What are you checking in WE02?
Paste the screenshot of that IDoc with error message here.
Typewriter

Sales Process And EDI Idocs Integration

Hi Friends,,
Good Day To You All !!!!
Please enhance my knowledge with your valuable reply.
I am new to ABAP and would like to learn the following .
1. Sales process - Starting from the Purchase Order Till shipment is created (All TCodes and the definations of the terms used like procurement , scheduled line,handling unit and all those terms coming into picture till the Sales process comes to an end).
2 . Idocs - Transaction Codes,Definations Of Terms like message types , basic types etc, etc,
I need the above information to get a clear picture of the process taking below.
What if an interface exists between SAP and a Non-SAP system(say Siebel system ) .The customer being the Non-SAP system and the Vendor our SAP system . Then the flow of the sales process taking place , with the PO coming from the Non-SAP system through inbound idoc and immediate ATP date going from SAP through the outbound Idoc..the process continues with the creation of delivery then shipment.Each of these triggering their respective idocs .
And the idocs update the corresponding status in Siebel .
I hope you guys would have understood by now , as to why i need the information on Sales Process and Idocs.
Thanks.
With regards,
Learner .
Edited by: SAP Technical Consultant on Oct 16, 2008 9:08 AM

Hello,
         If you want to Set up an Inbound Process for Sales Order Changes, all you have to do is
1. Maintain the Partner Profiles for the Inbound Message Type & Process Code in WE20.
2. The Assignment for Function Module IDOC_INPUT_ORDCHG is already available in WE42 Transaction for the Process Code ORDC. So, you don't have to worry about setting up the Process Code.
3. Take a Sample IDoc of Type ORDCHG Message Type in WE19 and try posting it for the Given Sales Order. If you would like to know more about what it does, Post it using Debugging Mode.
            The above Process is for Sales Order Changes via Inbound IDoc. Below are the Steps for the Outbound Delivery IDoc Trigger.
1. The Process Code DELV already has the Selection Program IDOC_OUTPUT_DELVRY in Transaction WE41. So, you dont have to worry about Setting Up the Process Code.
2. Also, check your field list. Open the IDoc Type DELVRY05 in the Transaction WE60 which is for IDoc Documentation. Check if all the Fields mentioned in your the list that you want to send are available in the Standard IDoc Type. If not, create a Custom Segment in WE31 & Assign the Custom Segment at an appropriate place in the Extended IDoc Type in WE30.
     All the Standard Segments / Fields available in the DELVRY05 IDoc Type will be automatically be populated by the Standard Selection Program IDOC_OUTPUT_DELVRY. However, if you have an IDoc Extension and would like to populate the Custom Segment / Fields, then you'll have to use the Customer Exit EXIT_SAPLV56K_002 in which you can write Code for populating the Custom Segments / Fields.
3. The Most important Thing that we need to take care of is Message Control Configuration while handling the Outbound EDI Scenario.
4. You need to Set up the Output Type for the Delivery Application (V2) for which you need to maintain Condition Records so that the Output Type is proposed automatically when the Delivery is being Saved.
5. In general, the Message Control Configuration is done by the Functional Team. So, ask your Functional Consultant to set up the Message Control Configuration for the Delivery IDoc Trigger.
Hope it was clear enough.
Thanks and Regards,
Venkat Phani Prasad Konduri

LSMW Idoc error in start idoc processcing as No data could be selected

Hi Abapers
am uploading the data Using the LSMW-IDOC Method.
it is executing successfully Up to the 13th Step I.e start idoc generation.
when i execute the 14th Step Start Idoc Processing.
am getting the Popup information Error like...
Error: No data could be slelected .
Can any one help me on this issue
Edited by: saeed.abap on May 30, 2011 10:12 AM
Edited by: saeed.abap on May 30, 2011 10:56 AM
Edited by: saeed.abap on May 30, 2011 10:57 AM

Hi Abapers,
Im working on datamigration for Business partner using Lsmw idoc method and getting Idoc status 53 with message crmxif_partner_save function module generated successfully with BP number but some of the entries of the fields is not getting inserted into master table BUT000,can any one put a tip of light what exactly is going wrong as i have taken all necesscary steps if any one can share their views like how to trace the posting program for inbound idoc crmxif_partner_save_m02 and where exactly the data is getting inserted into database table BUT000.
Will appreciate all your help.

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

R/3 to XI manually IDOC sending and problem:

R/3 to XI manually IDOC sending and problem:
I sent IDOC using we19 transaction from R/3 system. After sending it asks me userid and password for XI system. I give necessary UID and PASS. R/3 system says me sucessfully sent.
I check XI (sxmb_moni) but there is nomessage there.
Problem 1: I don't want R/3 ask me UID and password for XI access
Problem 2: I want to see message in XI (sxmb_moni)
Thanks

Hi Cemil,
>>>>After sending it asks me userid and password for XI system. I give necessary UID and PASS. R/3 system says me sucessfully sent.
check the RFC destination from R3 to XI (SM59)
you will find the right one from your port (We21)
you can also check step by step procedures
for IDOC - XI in 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>

Compare two Idoc's and send to te recievers as per the Condition.

Hi,
Scenario: Sender are a Idoc's and Receiver is Mail and File.
Sum the value of field1 of IDOC1 loop and compare with the field 2 of IDOC2. If the Condition satisfy send the data to file and mail reciever else send to only mail reciever.
I tried using a BPM. Steps used in BPM are as follow:
Step: 1
Fork -- with two branches.
Branch 1:loop1-- reciever1 -- container
Branch 2:reciever2
Step2:
Switch with two branches: Check the compare condition of the two Idoc
Branch 1:
Fork with two branches with send step with mail and file recievers
branch 2: Only mail reciever.
However if the condition is true or false the information is send mail to reciever.
I tried with the above steps, but failed.
Any changes required, please let me know.
Regards,
Manoj

sumit,
I recieve N number of IDOC1. I need Sum the value of field1 of IDOC1 loop and compare with the field 2 of IDOC2.
I tried using a BPM . Steps used in BPM are as follow:
Step: 1
Fork -- with two branches.
Branch 1:loop1-- reciever1 -- container
Branch 2:reciever2
Step2: Transfomation with Mapping program, source and Target message
Step3:
Switch with two branches: Check the compare condition of the two Idoc
Branch 1:
Fork with two branches with send step with mail and file recievers
branch 2: Only mail reciever.
When i checked with workflow i observe that that the message is not moving out of transformation step.But the message mapping is succesfully tested
Thanks,
Manoj

LSMW - Report to get IDOC failures and its external reference number

Hi All,
I'm currently using LSMW for data migration in CRM, for Business Partner and transaction data.
I need to generated a report which covers the idocs which have failed and the external identifier for which it has failed. Currently the IDOC reports that are available OOB provide the IDOC number and the reason for failure. It will be great if I can get the external identifier of the transaction as well.
I searched for a report in SAP but could not find any which gives this functionality.
Please advice.
Thanks in advance.

Hi,
1.)If you want the ouput in the same report program which triggers the idoc, it is better to use the control record information.
You will get IDoc Number from XEDIDC(check the below code) and you can store the idoc number into an internal table if more idoc is expecting to be triggered.
     call function 'MASTER_IDOC_DISTRIBUTE'
          exporting
            MASTER_IDOC_CONTROL        = EDIDC
          tables
            COMMUNICATION_IDOC_CONTROL = XEDIDC
            MASTER_IDOC_DATA           = XEDIDD
          exceptions
            others                     = 5.
   read table xedidc index 1.
append xedidc-docno to it_docno.
And finallly use this to display in the output.
2.) if u want it in a seperate report, then select based on date, idoctype, messagetype
Regards,
Sajith

Need IDOC inbound and outbound programs

hi,
i am new to xi.
i want IDOCs , inbound and outbound / function module programs for PURCHASE ORDER
and GOODS RECEIPT.
ex: BD10 for material master (matmas01).
thanks and regards
v ijender

for purchase order.
ORDERS / ORDERS04
ORDCHG / ORDERS04
ORDRSP / ORDERS04
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.
and also check the below link
http://www.erpgenie.com/sapedi/message_types_masterdata.htm
regards
kummari

Urgent - Idoc type and the Message type

Hello
Its very urgent. I want to know the basic idoc type and the message type used for EDI 894 transmission (Delivery / Return Base Record). Please respond at the earliest.
Thanks in advance

HI
Pratibha
How are you ?
Please check the below links:
http://scn.sap.com/thread/990524
http://www.erpgreat.com/pm003.htm
http://scn.sap.com/thread/1386811
http://scn.sap.com/thread/1078741http://www.erpgreat.com/plant/what-is-equipment-master.htm
http://benxbrain.com/en/index.do?onInputProcessing%28brai_object_thread%29&001_threadid=0000835100&001_boardtype=01&sysid=PI1&pgmid=R3TR&object=TABL&obj_name=EQBS&child_param=
Mutti

IDOC number and status

Hi All,
i am using Function Module IDOC_INBOUND_ASYNCHRONOUS to post inventory records.
its posting the data sucsessfully but it does not return IDOC number and status.
i can see the status and number in WE02 but please tell me how can i get that in my program.
Thakns and regards
Pankaj

Hi friend,
       U can get the status and number of IDOC in WE05 and WE07.
       Once u get the number of IDOC got to table EDIDC(Control Rec table),
       EDID4(Data Rec table) and EDIDS(status Rec table) to get the information
       related to status and content of idoc.
       Directly, u can specify it in ur program as Tables:EDIDC,EDID4,EDIDS
       and get the info according to ur idoc number.
Thanks N Regards,
        Manian.

How to encode XML to Idoc and decode Idoc to XML in business connector?

Hi all,
first of all: thanks for all, who are reading and perhaps responding this question!
Here some facts and my question(s):
The facts:
- I have the business connector version 4.6!
- I'm not working with any SAP Netviewer!
- I have XML files on an FTP-server and Idoc-files on an FTP-server --> so no connection between SAP and business connector, meaning: the files are just on the ftp-server!
What am i doing and what is working properly:
- Business connector logs in into the FTP-server (with FTP-service: pub.client.ftp:login)
- gets the file (with FTP-service: pub.client.ftp:get) (the idoc-file, when i want to convert it into XML or the XML-file, when i want to convert it into idoc-format)
- puts the file into another place in the server (with service wm.PartnerMgr.gateway.transport.FTPTransport:OutboundProcess)
!!!So far only getting and putting of the file works!!!
What is missing between getting the file in one format - for example idoc-format - and putting the file into the server in the other format - for example XML-format is:
CONVERSION FROM XML INTO IDOC AND VICE VERSA
My question:
- which services i have to use between getting and putting the files?
Thanks to all,
Tamer

Hi,
I have the same problem. I do fix it?
Thanks
Wilson Xavier
Brazil

File to Idoc Scenario and Idoc to File Scenario's

Hi Friends ,
This is Shalini Shah,
Please give me the details of how many busines sytems required in File to Idoc Scenario and Idoc to File sceanrio's.
In business system , what is the name of Integration server(this name is related to XI ot Third Party)
Please give me the full details of these two scenarios from Scratch.
Thanks in Advance.
Regards,
Shalini Shah.

Hi
These r few links which gives u complete scenarios...
for idoc to file:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
for file to idoc:
part1
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
part2
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
part 3
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
This link is also good:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
Troubleshooting File-to-IDOC Scenario in XI.
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
kindly rewards points if helpful.

Idoc Acknowledgements and Idoc Packaging

All,
I am implementing a requirement wherein we need to post 2 different types of Idoc's from our BPM. The Business requirements is such that until the Idoc 1 is not processed by the R3 system, the Idoc 2 should not be posted from XI as there is dependency in the data.
This can be addressed using Application Acknowledgements. The solution to this is to use the send step in my BPM with application acknowlegement. Until the application acknowledgement is not received for the first send step , the next send step will not be processed and so things will / should work fine.
The problem comes in the fact that the Idoc's being sent out of XI use Idoc Packaging, ie., the First Send Step uses Idoc Packaging to post multiple Idoc's to the target system. A question that arises due to Idoc packaging and Idoc ack's are,
How will the Idoc Ack's be sent back to XI?
I have read through the online help and it states that every ALE AUDIT Idoc can contain the status of maximum 500 Idoc's. Now, in my case , when using my Idoc packaging, if the number of Idoc's are greater than 500, how will the Application Acknowledgement for the Idoc's work? Will I still get a single acknowlegement in my BPM or will I get multiple acknowledgements? Will Send Step with Application acknowledgement still hold good?
Any ideas, thoughts / experiences on using idoc ack's with idoc packaging?
Regards
Bhavesh

If I undestatood correcty you have 2 send step, the first send a message containing multiple IDoc (IDoc Packaging). In this first send step you set the application Acknowledgements.
I think that this is not managed from the BPM, bacause the acknowledgements will come someone positive and someone negative, and so when the first send step will be completed ?
I think that the solution must to be changed a little bit, or removing the IDoc Packaging, or removing the wait of Acknowledgements.
Also take in mind that if you use a BPM with many possible correlation (Acknowledgements) you will have bed performances.
Regards,
Sandro

What is the difference beween idoc package and idoc collection

Hi friends,
    i am unable to understand difference betwen Idoc package and Idoc cillection.
    Please give me clear clarification.
Thanks and regards
Bhanu

Hi Bhanu,
Apart from the replies above, in case you're looking for an answer from ECC perspective, here are some inputs: (ECC is considered as sender here)
1. IDoc Collection:
   This will collect the IDocs and will not immediately send it to the target system after they are created. Program RSEOUT00 can be later scheduled for these collected IDocs to deliver them to the target. You can treat this as a park and process approach which proves useful in several business scenarios.
This standard link gives more insight:
SAP Library - IDoc Interface/ALE
2. IDoc Packaging:
    This defines the number of IDocs to be packed and sent in 1 RFC call (tRFC). If you set is as 20, then 20 IDocs will be sent in 1 tRFC request. This doesn't connote whether the IDocs will be triggered immediately or later, this just talks about the bundling of IDocs per RFC call.
Hope this helps.
Regards,
Abhishek

Idocs?!? Outbond and Inbond Idocs??

Similar Messages

Maybe you are looking for