Transfer BENEFIT3 IDoc to XI System

Hi All
   I have a small requirement to send BENEFIT3 IDoc in SAP 4.7 to SAP XI...
I was familiar in SAP SAP IDoc Transfer; so I tried similar configuration in both system, but I couldnt succeedPlease help to complete necessary configuration and step to test.
     1.      Defined Logical System
     2.     Assigned Logical System to Client
     3.     Setup RFC connection in both systems I have no idea the Type RFC to establish both 4.7- Xi systems (i.e.) Can I use R/3 or TCP/IP connection
     4.     Hope to create a transactional port
     5     Setting Partner profile Configured BENEFIT3 IDoc with BENREP Message type in Benefit Provider.But in SAP XI, am not finding BENEFIT3 IDoc to configure BENREP message typeI dont know, how to import BENEFIT3 IDoc in XI
     6     Distribute Model View
These are the step, I have a plan to configure in both systemPlease help whether am missing any step.

Hi Moorthy
Thanks for your reply...Still I have some question reg. port & partner profile...
In R/3
1. What type of RFC and port has to configure to connect to XI?
Based on your reply, I came to understand that NO need to maintain Partner profile in XI system.. Pls Correct me if am wrong...
Our scenario is to Convert R3 Idoc into Flat file in Xi...Am not finding BENEFIT3 IDoc Type in XI...
How to import BENEFIT3 IDoc structure in XI? I can understand IDX1 & 2 T.code to import metadataBut I dont know how to import the structure?? Pls let me know the steps to bring Idoc Segment Structure in XI
....Thanks
Babu.K

Similar Messages

Idocs are unable to transfer from R3 to PI system, IDOC status is 03

Hello Gurus,
Idocs are unable to transfer from R3 to PI system, IDOC status is 03
in sm58 getting below error
RFC are working fine
"EDISDEF: Port SAPCEP segment defn Z2SH_DESCR000 in IDoc type MATMAS03 CIM"
Regrds
vamsi

Hi,
I am also facing same problem, Can any one suggest me what is the issue..

Steps of EDI is used to transfer IDOC from R3 system to non sap system

Hi Experts,
Can you provide me Steps to configure EDI is used to transfer IDOC from R3 system to non sap system?
Full points will be assigned.
Thanks in advance!
Sapna

Hello,
 The EDI Configuration required to be done for Transfering IDoc to non SAP System is.
1. First of all, we need to identify the Transaction Data which is required to be Transfered to external System.(Ex: Sales Order Data or Shipment Data or Delivery Related Data).
2. Secondly, Identify the IDoc Type & Message Type. IDoc Type can be found in Transaction WE30 & Message Type Can be explored in Transaction WE81.
3. After that, assign the IDoc Type to Message Type in WE82.
4. Identify the Selection Program (Outbound) which is generally a Function Module in the Form of IDOC_OUTPUT_<Message Type>. Example, if the Message Type is ORDERS, the FM will be IDOC_OUTPUT_ORDERS.
5. Assign the Function Module to a Process Code in WE41 (Process Code for Outbound).
6. Configure Port Definitions in WE21 for which the RFC destinations are to be maintained in Transaction SM59.
7. Maintain Partner Profiles for the Outbound Message Processing in WE20.
8. Last, but not the Least, we need to Focus Mainly on Message Control Configuration which is nothing but maintaining the Output Type for the Outbound IDoc to be Triggered for the Sales Order Application or Delivery Application.
 i. In Message Control Configuration, we'll maintain
 a. Condition Tables
 b. Access Sequences
 c. Output Types
 ii. To Create the above elements, we can go to SPRO Transaction and do the same depending on the Application Area such as Sales / Shipping / Logistics Execution etc.
 iii. For Output Types & Access Sequences, we can go to the Transaction NACE or VK01 in which we'll maintain the Output Types / Access Sequences & Condition Records.
 Please note that all the above steps may not be needed if we are using some of the Standard Elements provided by SAP such as Message Type, Process Code, IDoc Type & Selection Program as many of the Standard SAP Applications have their own Elements for different Application Areas.
 For example, if you want to send an Order Confirmation IDoc when the Sales Order is saved, you can use the Message Type ORDRSP, IDoc Type ORDERS05 & Selection Program as IDOC_OUTPUT_ORDRSP.
 However, Message Control Configuration is the Key Factor and is required for all the Applications as per the Customer's / Client's Requirements.
Hope the above procedure was clear.
Thanks and Regards,
Venkat Phani Prasad Konduri

Transfer Idocs from one system to other

Hi,
Please check below scenario regarding Idoc transfer from Source to Receiver system:
I have source system SRC and receiver system REC.
I want to send Idocs from SRC to REC based on some data checks in REC system.
For ex, I am sending Sales order Idocs from SRC to REC, but should send the Idocs only when corresponding Sales area customizing is maintained in REC to avoid creating error IDocs in REC.
Is there a way to check on REC customizing data before sending Idocs from SRC system?
Thanks,
Yogita

As you said "I would probably have a program running every x minutes to check for required changes in REC system"
But the required changes in REC system is the customizing data which I need to check against the Idocs in SRC system. So how will I link it with the Idocs in SRC?
Also do you think it is possible with RFC call from SRC system to check customizing data in REC system which is releated to SRC Idocs ?
What I was thinking is:
1 Collect SRC Idocs to be sent to REC
2 RFC call from SRC to check customizing data related to collected IDocs
3 If Customizing exists, do outbound(RSEOUT00)
else
dont post Idocs from SRC
Do you think this is achievable?
Thanks,
Yogita

Data transfer with IDoc

Hi All,
Can any one please explain me about "Data transfer with IDoc".

Dear Prasad,
Using the IDoc option , you will not have a staging in BW like PSA were you can do corrections if required,
We can use IDOC option when we are very sure that data we are loading is error free,
and in older versions we are forced to use only IDOC option when doing hierarchy loads and its ruled out now,
Data transfer with IDoc
The data is packed into IDocs by the source system and sent to the Business Information Warehouse. In BW your data is saved persistently and intransparently in the IDoc store. From there the IDocs can be updated in the IDocs manually or automatically.
It is used for hierarchies load Limitations with IDoc is:
transfer structure must not have more than 1000 Bytes in the character format.
If it is a critical data we can use IDocs it can't be modified here. In case the load fails we need to load data from source system.
http://help.sap.com/saphelp_nw04/helpdata/en/7d/724d3caa70ea6fe10000000a114084/frameset.htm
Hope this helps u..
Best Regards,
VVenkat.
Edited by: Venkata Narayana Jakkampudi on Dec 23, 2008 12:03 PM

To transfer the data Cross the systems why we are not using BAPI Method?

Hello All,
To transfer the data Cross the systems why we are not using BAPI Method? why we are using only ALE/IDoc's?

Hi Naveen,
   Listing down those I know -
   1. Master data is expected to be changed/created less frequestly.
   2. Transactional data is expected to be chnaged/created more frequestly.
   3. Transactions to create/change/display master data do no have message control integration, since you are not supposed to print/fax/mail master data to your partners.
   4. Distribution of master data in generally supposed to happen within Enterprise boundry and typically you will have one central server maintaining master data which will be distributed to multiple downstream operation system (Some thing where MDM fits). So ideally when distributing master data using ALE you will be sending it to multiple systems.
   5. Distributing transactional data PO/SO etc is same as sending fax/print which fits with the requirement of message control.
Hope this helps,
Regards,
Sanjeev

View the Idocs in Source System

Hello
I have triggered a ino package load to BI. Now the job is just hanging and is not bringing in any data. Please can someone tell me where can i view these idocs in the source system.
Thanks

Hi
IDocs at Source system --BD87 / WE19/WE20/WE30/WE02 are the Tcodes for IDOCs
Till42 Outbound Idocs after 50 Inbound Status Idocs.
You can even see the Idocs at Info Package -- Monitoring -- Environment - Idocs at Source system.
Check your RFC at SM58/SM59 -- If the Queue Stuck -- Execute LUWs Manually.
When the IDOCs are Taking time to process it is always better to Make the yellow request to Red and Delte the Request and Go for Repeat .
Hope it helps

Passing Changed extended fields using ALE-IDOC to receiving system

Hi all,
Please tell me how passing changed extended fields using ALE-IDOC to receiving system can be achieved. Is it possible by Chnage pointer concept.Do i need to do some coading after data enters into receiving system as it is required while creating the entries in database table.
For ex. in matmas05 extended for classification and inspection view and then created using 'CREATION'
related bapi.Do i also need to incorporate the changes by change related bapi or ir can be handled by change pointer concept.
Thanks.

Hi Sanu
1) Please tell me how passing changed extended fields using ALE-IDOC to receiving system can be achieved. Is it possible by Chnage pointer concept.
=> Looks like you have extended standard IDOC here. so you need to find User Exit or BADI for the Push program to populate the additional fields. Yes, it is possible thru change pointers as well.
1) Do i need to do some coading after data enters into receiving system as it is required while creating the entries in database table.
=> Yes, as suggested in 1 try finding User Exits/BADIs.
Regards
Shital

IDoc Adapter - Logical System - File to IDOC configuration

I have a scenario reading a File ->XI->IDoc in R/3. I'm looking to have the control record parameter for SNDPRN reflect the Environment dealt with. I unchecked the 'Apply Control Record Values from Payload' & 'Take Sender from Payload' boxes but the problem I'm getting is that the system is reading from the business service (IDoc Adapter - Logical System) and feed it in the Partner Profile in the IDOC. This means that I should all the time redefine 3 this Logical System in config before transporting my scenario from DEV/QA/PRD. Any idea how I can avoid this kind of 'hardcode' ?
Thanks

Hi,
Why u r using three different LS can't u use only one LS and send all the IDOCs to same LS. That will ease ur task.
Do let me know why u r going for three different LS.
In the file r u getting any data which will help u to identify that this file is for which LS. IF that is the scenario then u can use the value mapping and based on the value which is coming in file u can map it to the IDOc filed which u have mentioned and in the configuration it will take the respective configuration.
Thnx
Chirag

SAP system IDOC - XI - SAP system IDOC

Hi,
I have created several scenarios for sending IDOCs between different SAP systems, but I have a problem with just one SAP system that is a copy of our production system when is acting as a source.
When sending the IDOC from source system, I can see the IDOC in SM58, with the following error message;
"client xxx is not available in this system" where the client is actually the client of the receiving system.
I have successfully sent IDOCs from other SAP systems to the same target SAP system so there is nothing wrong with the target system.
Anyone experienced the same? Any ideas?
best regards
Torstein

Hi,
I am facing the same issue too. My target system is also release 700 and I have done all my SALE config, we21 settings. But still the error repeats as " Client XXX is not available in the system". How did you fix this issue?
-Teresa

IDOC from external system

Hi,
I have scenarion in that we will receive IDOC from external system (SAP system) in XI i.e. IDOC- XI -IDOC scenrio. from my Understanding ,to configure the scenario I have to do ALE from sender side and IDOC receiver channel in receiving side.
External system (SAP) -(ALE)-> XI -(IDOC rcv)--> Our System (SAP)
Please can anyone provide me steps to do ALE from external system.
Edited by: tapan singh on Feb 28, 2011 11:51 AM
Edited by: tapan singh on Feb 28, 2011 11:52 AM

Hi,
We can have alternate ways to send IDocs from external system to SAP system. One way is in below link
http://help.sap.com/saphelp_46b/helpdata/en/52/16abf6543311d1891c0000e8322f96/content.htm.
http://help.sap.com/saphelp_40b/helpdata/ru/52/16abcf543311d1891c0000e8322f96/content.htm
I can think of few more, like In external system after generating Idoc, save it as a tex and send it to SAP system using Http post or using web service.
Look out to below discussion.
Send IDoc from External System to SAP system
Regards
Aashish Sinha
Edited by: Aashish Sinha on Feb 28, 2011 1:16 PM

Error Loading Hierarchy Error when updating Idocs in Source System

Hello Friends,
I am loading hierarchy data using Info pac into 0FUNDS_CTR . I have selected a hierarchy under hierarchy selections tab in the Info pac .
All Partner profiles in WE20 seems OK . But When I loaded data , throwing errrr message as below
Error when updating Idocs in Source System
Diagnosis
Errors have been reported in Source System during IDoc update:
System Response
Some IDocs have error status.
Procedure
Check the IDocs in Source System . You do this using the extraction monitor.
Error handling:
How you resolve the errors depends on the error message you get.
When I checked in TC WE05 says that IDoc: 0000000000355113 Status: Error during syntax check of IDoc (outbound) with status 26 .
Please advice .
Many thanks

Hi Krishna4bi,
Actually we will monitor idoc status in BD87 in SAP BI As well ECC , while extracting the data from source sytem if any idoc struck we will manually process in BD87 , But you are telling that while loading the datasource the error occurred , so please check once in ECC side . Otherwise see how many packets are still process, make it red that infopackage and do manually update.
Hope it helps,
By,
Praveen Yagnamurthy,
SAP BI Consultant,
Blue Marlin Systems-INDIA.
http://bluemarlinsys.com/bi.

Error when updating Idocs in Source System - Urgent

Hi Team,
When i was loading the data from SAP R/3 to BW, i was facing the error "Error when updating Idocs in Source System" (0 From 0 Records).
When i check in the Environment>Transaction RFC->In the Source System, it was displaying the error--
" Import container contains errors (are any obligato) in the Function Module: IDOC_ERROR_WORKFLOW_START_R".
Can any one please help me to solve this error.
This is am Urgent requirement for me to deliver.
Thanks & Best Regards,
Venkata.

Hello VenkaTa,
How r u ?
The workflow settings are not proper it seems. Ask the BASIS people to correct the Work Flow Settings. Then try Updating the IDOCs manually.
Also check the Inbound and outbound IDOCs in the Source system. The outbound should contain some warnings or errors.
Best Regards....
Sankar Kumar
+91 98403 47141

Error when updating Idocs in Source System

Hi All,
We did a recent copy from QAS to DEV,after which am unable to run my process chains ,the load status still showin yellow signal,whereas job is getting finished but am unable to load datas to the targets. Am getting the following error message when i see the display message in process chain.
System Response
Some IDocs have error status.
Procedure
Check the IDocs in Source System . You do this using the extraction monitor.
Error handling:
How you resolve the errors depends on the error message you get.
Error when updating Idocs in Source System
Could anyone please let me know what can be done ?
Thanks
con

Hello All,
I have same problem but its RESOLVED by the following process.
Step - 1
execute the Function module "SCP_LANGUAGES_IN_INSTANCE". It may or maynot give some output. Just note if it give the output
Step - 2
in Transaction SE38 execute the program "RSCPINST".
Just Click on the Activate button (dont select anything).
Step - 3
Again do the same thing specified in Step - 1. Now it will give the output saying that Language is DE.
So by the above procedure my issue is been resolved.
Regards
Sankar

Send IDoc from External System to SAP system

Hi Folks,
I have a requirement to send IDocs from an external system to the SAp system. Basically the external system is a subsystem which is able to send & receive idocs. The external system is currently able to send idocs to SAP system through the ALE layer but now we have to replace it by PI. Now the external system has to send teh IDocs to the SAP ECC system through the SAP PI 7.0.
Kindly let me knowq how I can achieve it.
Regards,
Santosh

Hi Satish,
You can achieve this requirement
1)If your external system going to support web service cals then send IDoc from External system as a web service, in PI use sender side SOAP and receiver side IDoc receiver channel to send IDoc.
or
2)Use proxy program ,implement the same ALE logic in PI.
or
3)Copy the Extenal IDoc message in to file folder as XML,then use file adapter to pick up this message and send it SAP using IDoc.
Regards,
raj

Transfer BENEFIT3 IDoc to XI System

Similar Messages

Maybe you are looking for