Regarding IDOC Collect

Hi All,
When we are transfering vendors through Tcode [BD14], program is generating single IDoc per vendor.
But my requirement is to club all the IDoc's into one single IDoc at the sender side only.
I have found one standard program "RSEOUT00" to process all selected IDoc's but it is generating single XML file when using XML file port. But I want an IDoc using Trfc port.
Please help.
Thanks
Tarun

Hello,
What about the param. "NUmber of Vendors per Process" ?
I checked in the code & depending on this counter vendor master idocs are generated.
Also AFAIK "Collect Idocs" will not club the idocs into 1 single idoc, rather send them in package size maintained in WE20.
Plz refer to this for details: [http://help.sap.com/saphelp_sm32/helpdata/en/5f/45f93b4139b478e10000000a11402f/content.htm|http://help.sap.com/saphelp_sm32/helpdata/en/5f/45f93b4139b478e10000000a11402f/content.htm]
Please revert back.
BR,
Suhas

Similar Messages

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

IDoc Collection in BPM and Without BPM

Hi All
I'm much confused on IDoc collection for which i require your expertise to clear my doubts. My primary question is based on the context "Multimapping doest work with idocs".
consider the case -> collect files-idoc scenario. Using BPM i need to have
a multimapping scenario. In the transformation step we will have a container element where mutiline is enabled so that the collected files are transformed into one abs interface. my dopubt arises here when i consider this scenario without bpm that is N:1 mapping (no collection). in this case why this multimapping works in bpm process and not incase of non-bpm scenarios? is it because in bpm the mapping happens in BPE?
pls clarify.
thks
Prabhu

>>>>In an N:1 scenario without BPM, how could you send more than one message to your multi-mapping? You can't.
yes we cant as this validation is not supported at abap stack level and N:1 is possibkle without BPM (or i'm missing something here). but this same step with bpm get executed succceffuly. whats the logic behind it
Message was edited by:
Prabhu S

Regarding IDOCS.....

Hii All,
kindly suggest me some links regarding IDOCs, as I need to create one regarding PO.
Points for sure......:)
Regards,
Ashish

Hi
If u want any material giev me ur mail id i'll forward u some documents
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.
Check 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://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
Please check this PDF documents for ALE and IDoc.
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
Reward points for useful Answers
Regards
Pavan

BPM Idoc collection without calling the mapping in BPM

Hi Expert,
I have an IDOC to file scenario in which source side I have to collect multiple IDOC and map it to a single file .I am achieving it through BPM . at present I am using one multimapping and calling this mapping in the BPM under transformation step its working fine but due to some constraint , Now I want to achieve it using BPM but without calling the Mapping in the BPM i.e I don't want to use Transformation step in the BPM. Is it possible ????
Regards,
Saurabh

Hi Saurabh,
If that is the case it is preferable to collect the IDocs in ECC and then send them to XI at one go.
Cheers !
Lokesh

Help regarding IDOCs

Hi i'm new to SAP..I'm working on developing a new adapter in java called IDOC which converts flat format idoc files (3 idoc object types: Product, Account and SalesOrder) to XML..
We get IDoc files over FTP and these files have to be read from the FileSystem.
I have a few questions here..
1) Do we need to get predefined schemas for Product, Account and SalesOrder idocs ? whether any schemas for these IDOC objects exists ??
2) I have a topical collection of IDoc and segment Definitions.
a) IDOCTYP;NR;SEGTYP;PARSEG;PARPNO;PARFLG;MUSTFL;OCCMIN;OCCMAX;HLEVEL
/DSD/HH_CONTROL01;0001;/DSD/HH_E1CTHD01;;0000;X;X;0000000001;0000000001;01
b) SEGTYP;POS;FIELDNAME;ROLLNAME;EXPLENG;ISOCODE
/DSD/E1BPRACLEARING;0001;VISIT_ID;/DSD/HH_VISIT_ID;0006;
Can anyone please tell me the what these abbravations are (NR, PARSESEG etc..)
Thanks in advance..

parseg means parent segment.......
I think remaining are some of the fields.....
You will have Idoc type,Message type linked with that and all these segments with the fields in it.
All you have to do is configuration in we20....Partner profiles..
regards,
sandeep.

BPM: Multiple IDOC collect into one file

Hi
I have done collecting multiple IDOCs of same type into one file using BPM
I have used the following blog which is collecting different types of IDOCs.
IDOCs (Multiple Types) Collection in BPM
But i have done collecting of IDOCs which are same type.
Source side it is showing successful and its reaching to BPM also . But in target i am not getting any file. Could any one please help me how to check where exactly I am failing.
Thanks & Regards
Sowmya

Check whether the Outbound Status is successful or not in sxm_moni. Is there any message created from Integration Process to receiver File system.
Check this
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/80a22ce8-8e72-2b10-3fba-e9511c6f0b8b
Regards,
Prateek

Idoc collective processing

Hi We have a custom idoc(Inbound) for posting goods movements...Actually it does goods movements through two seperate BDC calls and returns the material document number in the status.When we process two or more idocs through a batch processing at a same time..the first idoc goes through do the posting corretly but the second and third doesnt do anything but gets 53 status and also picks up the material doc number of the first idoc in status...
Each idoc goes through correctly when processed individually...What might be the problem....?and how it could be corrected...?
Thanks,
Larry

Hi,
As Manohar said ,the problem is due to variables refresh. One of the variables is setting to success status after processing of the first idoc , i think the same status is transfered to next idoc's also.
follow below steps to identify the problem.
1.Change the partner profile settings to 'Collective method' , then idoc's will be created with 64 status.
2.then put a break point at processing function module.
3.use BD87 or program : RBDAPP01 to process 64 status idoc's , while processing idoc's take more than one 64 status idoc. then you will know the exact problem.due to break point, program will go to debug mode, after processing of the first idoc then start debugging the program with second idoc processing.
Regards
Appana

Automation of idoc collect during customer planned system outage

Hi All,
In our landscape we are dealing with customer through IDOCs , now we have preplanned system outage of customers and every customer has its own planned downtime . Now we want to collect the idoc for the customer
during their downtime and trigger after the downtime . Can we automate this process to collect the idoc during the specific time and then the release .
Has anyone tried to change the partner profile (automated) during specific time to put idoc in collect mode and then trigger immediatly as most of the planned downtime is in night an no one around for changing this ?
Thanks in advance
Regards
Vijay

I found a thread about this.

IDOC collection

Hello -
Scenario is IDOC to XML to HTTP.
IDOCs will be coming into XI and based on the vendors will be routed to various Suppliers.
I used BPM to configure the error handling.
If i get an IDOC and is successfully sent then i have no problem.
Lets say there is a problem in transmission of the IDOC then i need to keep sending the IDOC for a period of time. If within that period of time if i get a response then well and fine else throw an exception.
Now while the above scenario is running another IDOC is picked up by XI. now will this IDOC overwrite the previous IDOC?
Will the older messages be overwritten by the newer ones or internally XI handles through multithreading?
TIA
Jerry

Hi Lloyd,
Are u using BPMcollect pattern for Idocs?
If so, then it is working based on Correlation concept.. So foreach correlation id it will create one new instance.
There will be a chance of Message loss during this .
This blog may give some hints-
/people/sravya.talanki2/blog/2005/12/09/xiidoc-message-packages
Some of the SAP Notes- 898131, 852019
Hope this helps,
Regards,
Moorthy

IDoc Collection Scenario (IDoc to Mail Interface)

Hi,
I am configuring IDoc to Mail Scenario using BPM.
I gone through following link for develop the scenario. I am still unable to complete the scenario.
Collect Idoc
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
I have done following steps in my configuration. Please correct my steps if i am wrong.
Source is Outbound Invoice IDoc (SAP System).
Target is Inbound EDI 810 format send as a email(Mail System).
1. Create an Abstract Interface for Invoice IDoc(MI_IDoc_ABS)
2. Create a Message Interface for EDI 810 for Inbound(MI_EDI810_IN)
3. Create an Abstract Interface for EDI 810(MI_EDI810_ABS)
4. Message Mapping between Outbound IDoc and Abstract Invoice IDoc. I did this as per one of the above link. but did not understand the importance of this. On Message tab of Message Mapping, it shows the occurance as 1 for both source and target. I did not see the mention of this mapping in the BPM. Not sure if this was required?(MM_IDoc_ABS)
5. Message mapping between Abstract Invoice IDoc to Abstract EDI 810. On the message tab of message mapping, occurance of Source message is changed to 0-unbounded and occurance of target is kept as 1.(MM_EDI810_ABS)
6. Define Interface Mapping for above mappings
a) IM_IDoc_ABS - Outbound Invoice IDoc + MI_IDoc_ABS
MM_IDoc_ABS
b) IM_EDI810_ABS - MI_IDoc_ABS + MI_EDI810_ABS
MM_EDI810_ABS
7. Create a BPM in Integration process. Define 3 Containers namely
a) collectIDoc - Abstract Interface - MI_IDoc_ABS
b) collectIDocList - Abstract Interface - MI_IDoc_ABS(Multiline)
c) targetFile - Abstract Interface - MI_EDI810_ABS
8. Create a Block and define a infinite while loop with Block. Condition to be defined as (1=1)
9. Define a deadline block withing Block with duration = 5minutes
10. Define a Correlation in Correlation editor as SNDPOR as a ID.
11. Define a recieve step inside infinite while loop with following properties
Message = collectIDoc
Start Process = Checked
Use Correlation = Correlation
Activate Correlation = Correlation
Correlation
SNDPOR = collectIDoc./INVOIC02/IDOC/EDI_DC40/SNDPOR
12. Define Container operation next to recieve step. properties are
Target = collectIDocList
Operation = Append
expression = collectIDoc
13. Outside the block, there is Transformation Step with following properties
Interface Mapping = IM_EDI810_ABS
Source message = collectIDocList
Target message = targetFile
Acknowledgement = None
Reciever From = Send Context
Now the next step is to define Communication Channel and Receiver determination, Interface determination in the Integration Directory.
I don't know, how to go further on these steps.
In addition, could you please validate my above steps.
I appreciate your help.
Thanks,
Gowri

Hi Bhavesh,
Thanks for the directions and help. I appreciate your help. I understand the steps but i am unable to implement it.
I have few more questions on above answer.
a) Do i have to create Sender Agreement?
b) Do i have to import bmp process in Integration Process in Integration Directory?
The steps that i carried out in Integration Directory.
1. Create a Scenario EDI810_Scenario
2. Create a party called EDI810_Party and EDI810_Service.
3. In EDI810_Service, Receiver tab has interfaces defined. MI_EDI_IN and MI_IDoc_ABS. In sender tab, it is INVOIC.INVOICE02 (IDoc) and MI_EDI810_ABS.
4. Define a receiver communication channel CC_EDI810_Receiver(RFC).
5. Business System for SAP is defined in Service without Party.
6. Defined Sender communication channel CC_IDoc_Sender(IDoc)
7. Create Interface Determination (First)
Properties are
Sender Service : SAP Business System
Sender Interface : INVOIC.INVOICE02 (IDoc)
Sender Namespace : IDoc namespace
Receiver Party : EDI810_Party
Receiver Service : EDI810_Service
Configured Inbound Interface is
MI_IDoc_ABS and IM_IDoc_ABS
8. Create Interface Determination Determination (Second)
Properties are
Sender Service : BPM_IP (Bpm process is imported in Integratio directory)
Sender Interface : MI_EDI810_ABS
Receiver Party : EDI810_Party
Receiver Service : EDI810_Service
Configured Inbound Interface is
MI_EDI_IN. I do not see IM_EDI_ABS in the list. How do i get that.
What step did i miss?
Thanks,
Gowri

Regarding IDOC in XI

Dear All,
For scenario:
System A (RFC adapter) --> XI --> System B (IDOC adapter).
How should i configure for the partner profile?
1. In System A --> Logical System to System B, and put my message type as outbound.
2. In System B --> Logical System to System A, and put my message type as inbound.
3. or i need to configure in XI partner profile? Logical system A (outbound) and Logical system B (inbound).
Please clear my doubts.
Thanks,
Victor.

Hey,
   For RFC you do not need to make any entries in partner profile.
For IDOC(i.e) in system B create a partner profile as inbound.
Please refer to these steps if any issues.
teps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
WE42 process code
WE47 status info.
regards,
     Milan

Query Regarding IDOC "WMMBID02"

Hi,
I have a follwoing requirement that makes use of a standart IDOC WMMBID02. This IDOC WMMBID02 has data stored within into different segments that have structures. I need to read that data and store it into an INTERNAL Table.
Is there any specific SAP Function Module that would help me to obtain such requirement. If not, what are the options that could be used to read data from IDOC WMMBID02 and populate our INTERNAL Table.
Kindly Suggests,
Thanks & Regards,
Rajesh

Rajesh,
Either you can use the function IDOC_TYPE_COMPLETE_READ
Or use the code as below.
SELECT * from EDID4 into t_idoc_data where docnum = ???
data : wa_E1MBXYH type E1MBXYH,
wa_E1MBXYI type E1MBXYI,
wa_E1MBXYJ type E1MBXYJ
loop at t_idoc_data into wa_idoc_data.
case segnam.
when 'E1MBXYH'.
move wa_idoc_data-data into wa_E1MBXYH.
when 'E1MBXYI'.
move wa_idoc_data-data into wa_E1MBXYI.
when 'E1MBXYJ'.
move wa_idoc_data-data into wa_E1MBXYJ.
endcase.
move corresponding fields of wa_E1MBXYH into wa_itab.
move corresponding fields of wa_E1MBXYI into wa_itab.
move corresponding fields of wa_E1MBXYJ into wa_itab.
append wa_itab to itab.
Clear all the work areas here
endloop.
Regards,
Ravi
Note : Please mark the helpful answers

BPM Idoc collection without transformation step

Hello
I have a simple scenario of outbound invoice idocs. The tricky thing now is that I want to collect them within a BPM process.
The BPM is basically working as long as I have a transformation step before the sending wich transforms from a multiline idoc to a "non-multiline" file.
My problem is that I don't want to put a mapping in the BPM, because depending on the values in the idoc I need to run different mappings.
What I really want to do is to send back the collected files to the IE and process them with separate receiver determination per receiver.
In this way I would only need 1 BPM and the configuration is done in the directory.
Problem is already that I can't specify a multiline message in the sending step - not allowed.
Anyone with a similar scenario who can help? I'm not sure what the receiverDetermination step does in a BPM, could this solve my issue?
thanks
David

Hello
I tried the ForEach block, but now the BPM is first collecting the idocs and sends them out individually in the send step.
I've never used the forEach before, so the chance is good I made something wrong.
After collecting I'm running
1. Block - forEach
- MultiLineElement = collected idocs
- CurrentLine = wasn't sure, used abstract interface of the single idoc
- local correlation = same correlation than in the collecting step
2. Sending (inside block)
- message = single idoc
- Receiver from = send context
- Conversation ID = I've choosen an Xpath expression
- correlation = same than for collecting
What I'm missing here as well is how to diferenciate the idocs I send back to the IE in the receiver determination since all come from the same service with the same interface? That's why I tried to set te Conversation ID, but it didn't appear anywhere in the XML trace.
any idea?
thx!

R/3 - XI Idoc Collection Based On Same tRFC Call

We have solution where RSEOUT00 sends idocs out in one tRFC call to a system running Mercator. These idocs represent 1 transaction if you will, and are then mapped into 1 outbound file.
I am trying to figure out what the best option to do this in XI is. The requirement is to not collect based on a deadline, but to collect based on the chunk of idocs that were released online by the user in the same RSEOUT00 transaction.
Is this possible or any suggestions to accomplish this? I do have the flexibility to customize RSEOUT00 (its already custom actually) and have been toying with the idea of sending another message that is an "all are sent" or even something like a control message with a listing of all of the idoc numbers that belong to that group, but have yet to come up with a design that I'm comfortable with as the idocs are all sent asynchronously thorugh tRFC.
Thanks
Peter

Hi Peter,
If we can check the TID of the IDOC then that make your job easy..is it not ?
Because all the IDOCs send in one tRFC call will have the same TID..
Now i am trying to see what is the best way to get that...i checked standard context objects given by SAP ..it doesnot have this TID :(...
I have suggestion ..this will work for sure...however it maynot be the most optimal one...
In the BPM where you are collecting IDOCs...after the recieve..have a mapping from IDOC to a dummy message which will basically return TID....now this mapping should be an ABAP mapping ...now from the ABAP code...query the IDXSNDPOR table and get the TID for the current IDOC and return it..
Back in the BPM, check if this is a new TID or not...if it is new..we can bundle it and stop the collection...
if we have a better way to get the TID.....we can make this better...
Thanks.

Regarding IDOC Collect

Similar Messages

Maybe you are looking for