I want to use IDOC to launch RFC

Hi,
I my SAP system sends IDOC to XI3.0 Sytem.
XI must map this IDOC to RFC and must send RFC response to FTP receiver.
How can I do this. Is there an example for this type of message.
Thanks

Hi,
you cannot send RFC response to FTP
what you can send is - RFC request
for XI -> RFC
weblog have a look at this one (with BPM):
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
for IDOC -> XI:
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Similar Messages

Hi Using IDOCs with LSM Workbench????

Hello,
I wanted to use IDOCs as one of the methods with the LSM Workbench. I am going to load the data from flat file to a transaction in CRM. I am just curious to know that how do I go forward with it. The first step of LSM Workbench is asking Message Type, Basic Type, Enhancement and structure assignment for EDIDC40. I have used other methods such as Direct input and Batch input. I have not used IDOCs with LSMW. Is it possible that you can give me the steps what we have to follow in order to set up the IDOCs and then use it with LSMW.
I will really appreciate if you can give me the steps or give a link which shows steps of LSMW with IDOCs..
Thanks much.
Warren

hi warren,
   first u have to configure the partner profile in lsmw
lsmw->settings->idoc inbound processing.
then u have to choose the basic type message type all those stuffs.if u have any enhacement u can use it or else leave it blank.
lsmw->settings->idoc inbound processing.
partner profile..
File port              IDOC_TEST
tRFC port
Partn.type             KU
Partn.number           106
Message type         ORDERS        Purchase order / or
Basic type           ORDERS05      Purchasing/Sales
enhancement blank
    tick it. Enable structure relation for EDIDC40
steps are:
Maintain object attributes
Maintain source structures
Maintain source fields
Maintain structure relations
Maintain field mapping and conversion rules
Maintain fixed values, translations, user-define
Specify files
Assign files
Read data
Display read data
Convert data
Display converted data
Start IDoc creation
Start IDoc processing
Create IDoc overview
Start IDoc post-processing
please don't forget to reward points....
regards,
murali.

Create Sales Order using IDoc

Hi All,
Based upon customer's input file which contains header and line item details I have to create sales order in our system. We would like to use IDoc for this. Customer will send us file once a day by email or FTP.
For this I have created a port and partner profile but I am not sure how the process will get initiated?
Can someone please let me know how can I do this? There is now outbound process involved, I just need to create sales order based upon input file using IDoc.
Regards,
Sanjay

HI,
You cannot directly call the function modules that process the idoc, because these functions are called dynamically by the ALE layer and the function expects data in a certian format (IDoc format ).
BAPI would be the best way to go for your scenario.
However there is a workaround if you want to use IDoc only. You can follow this approach :
1. Populate an outbound ORDERS05 IDoc from the file data.
2. Distribute it to the same system, i.e sender system and receiver system is same.
3. On the Inbound side the Idoc that you created on the outbound side will be received and processed.
"R3 File----->Outound ORDRES05 -----
______________________________________|
|
'------> " Inbound ORDERS05 ( in the same R3 system)
The tricky part is sending an Idoc and receiving in the same system, but you can find how to do this on the wiki pages.
regards,
Advait

How to use IDOC and RFC adapter in 1 scenario?

We have AAA field and BBB field and we want to send AAA field to receiver sap system using IDOC adapter and BBB field to receiver sap system using RFC adapter. But how to use IDOC and RFC adapter in 1 scenario and how to map and what are the design and configuration objects we require to create?

To achieve this you have to use
Two Interface Determinations
Two Communication Channels (IDOC & RFC)
& Two Receiver Aggrements.
Use the Enhanced Interface determination and give your conditions there. Based on you condition your interface mapping will be triggered and data will be sent to IDOC & RFC respectively.

Best Scenarios when to use IDOC Adapter, RFC Adapter and Proxy

Please provide me links/weblogs which demonstrate the full scenario that when to use IDOC Adapter, RFC Adapter and Proxy when working with sender R/3 system.
Regards
Rachit

Hi abhinash,
Check these links for java proxy
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a068cf2f-0401-0010-2aa9-f5ae4b2096f9
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f272165e-0401-0010-b4a1-e7eb8903501d
for ABAP Proxy ...
/people/siva.maranani/blog/2005/04/03/abap-server-proxies
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy
http://help.sap.com/saphelp_nw2004s/helpdata/en/48/d5a1fe5f317a4e8e35801ed2c88246/frameset.htm
for RFC .....
RFC-xi-SOAP Scenario
How to send RFC response message back to XI File/FTP adapter?
https://weblogs.sdn.sap.com/pub/wlg/3865//Troubleshooting [original link is broken] [original link is broken] [original link is broken] [original link is broken]
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
Hope you will find them useful ..
Regards
Abhi

I no longer want to use vmware fusion to run my windows session, can I use boot camp to launch my vmware windows install or do I have to start again with a brand new installation?

Hi,
I would like to know if I'm able to use my current VMWare windows installation through Boot Camp, I don't want to use fusion anymore but I'm hoping there's a way to set up boot camp and not have to re-install windows again, if anyone could let me know that would be great

Thank you for your response GabeAlan, am i able to back up my virtual windows without access through VMware fusion? its locked me out since i upgraded to Yosemite, i prefer to see if i can avoid having to pay to upgrade to the latest fusion

Create Sales order from Internal Purchase Order using IDOC

Hello Friends,
I have requirement to create Sales Order from Internal Purchase Order Using IDOC.
Backgorund, we have already configured IDOC orders05 to create Sales Order from external Purchase order from Inbound IDOC, and it is working fine.
Now we have new requirement to create Sales Order from our own Purchase order, i.e. When PO is created in one plant corresponidng sales order automatically must needs to create in another Plant with respect PO.
I m trying to design a solution for above problem as follows,
1.create an Inbound Idoc from PO, by creatiing one new message type on PO save.
2.Process that Inbound IDOC same as it is from external PO.
3.Once processed Sales order will create.
Please help me in step 1. to create Inbound IDOC from PO.
If you want any further clarification please write me.
Thanks,
Mahesh

I had done a similar scenario before and we achieved it through SAP XI. The problem is with the control record. When we create a ORDERS IDOC from a PO the control record will be for outbound transmission. We sent the file to XI and XI resent it back with some data parsing and a new inbound control record. This way it went neat outbound and inbound.
I'm not sure what kind of architecture you have. If you have to do it within your ECC/R/3, then you could create the outbound IDOC to a new port and write a fresh RFC to pick it up from the same folder and create a new control record for inbound processing.
I haven't tried this; but there is a "processing w. trigger (inbound)" option on the outbound process code. May be you can explore into that a bit more.
I'm sure there could be better approaches to handle this within ECC so if you stumble on any, do write back. I would like to know to update my knowledge .

How to send Outbound IDocs through an RFC-enabled FM

Good day to all;
A partner system (AS/400) wants to use a Java Connection to execute a RFC Function Module, in SAP, that will then return a collection of IDocs.
Currently, the Function Module builds the IDocs, but I'm not exactly sure how to simply send those IDocs back to the AS/400.
If anyone can help in this regard, that would be great.
My current thoughts are to use Master_IDoc_Distribute, but then I imagine that requires a port configuration for the AS/400. And if this is the case, does that mean that SAP will send the IDocs back itself instead of using the RFC interface?

Hi Tavares,
If you want to send outbound IDoc to AS/400 (external system), you need to setup file port (t/code WE21).
For RFC interface, you need to setup RFC file port with RFC Destination (t/code SM59). In this case, SAP will send IDoc (individually or batch) to receiver system (AS/400). Perhaps you need a middleware for data transformation, if AS/400 does not perform data mapping for outbound IDoc.
For FTP interface, you need to setup flat/XML file port for outbound. then you can FTP the file to AS/400 later on.
In addition to file port configuration, you also need to setup partner profile for outbound parameter (t/code WE20) and the distribution model (t/code BD64).
Hope this will help.
Regards,
Ferry Lianto

Difference between lsmw using BAPI & lsmw using IDOC?

HI everybody
can anybody tell me difference between lsmw using BAPI & lsmw using IDOC?

IDocs and BAPI are very different, so it should be easy to choose between them depending on your requirements.
IDOCS
Advantages
System can work even if target system not always online. The IDoc will be created and sending will just continue once you get connected to the other system.
No additional programming required. You just need to set up the configuration.
Disadvantages
Receipt/processing on the target system may not be immediate.
The sending system has no way to know whether the target system actually received what you sent (unless you use ALE).
If there is no SAP standard IDoc available for your requirement, it's harder to create a customized IDoc than a customized BAPI.
BAPIS
Advantages
You can tell if your sending was successful or not
Sending to/processing on the other side is immediate
Easier to create your own BAPI than your own IDoc
Disadvantages
Will only work if you have an active online connection.
Some programming required to call the BAPI.
Others interface methods you might also want to consider are ALE and RFCs.

Safari wants to use the "login" keychain. -- Why can't Safari remember???

When I launch the Safari application, I get a dialogue box with a message indicating the following:
Safari wants to use the "login" keychain.
Please enter the keychain password.
Password:
Cancel -- OK
When I get this dialogue box, I enter the login keychain password in the Password text box, and I click the OK button. Then, Safari proceeds as normal. This is extremely annoying, because it happens almost every time that I launch Safari.
This only started to happen after I upgraded on Monday to Mac OS X Leopard version 10.5. During the Leopard upgrade, I had problems with the keychain passwords, and so I then upgraded again with the new "Login and Keychain Update 1.0". But, the problems with Safari forgetting the login keychain password continue.
The strange thing is that there is NO option in the dialogue box to indicate that Safari should REMEMBER the password. The option does NOT exist, so I can NOT click the Remember box.
I also went into the Keychain Access utility and double-checked and confirmed that my First Aid preferences were properly CHECKED for "Synchronize login keychain password with account" and also "Keep login keychain unlocked". Both of these preferences options are checked. So, I can't understand why Safari cannot remember the login keychain password?
I have this exact same problem with the Mail application, as well.
And, it looks like many many people are having the same problem -- See the following link to related discussions:
http://discussions.apple.com/thread.jspa?messageID=5679135&#5679135
Can anyone please help? -- When is Apple going to release a fix for this problem? -- Has anyone received any kind of acknowledgement from Apple that they are aware of this problem and that they intend to fix it?
Please help !!!

I had the same experience and found a solution.
After the upgrade, I had a login keychain (the default) and my original username keychain. Both are in the chain of keychains, but since it has a choice, Mail keeps asking you to confirm.
I moved all the entries out of username into login, deleted username, and all is well.
Note that Keychain asks for your password on EACH ITEM that it moves, which can be tedious. So I changed the keychain password to a single character, just for the duration, then changed it back to something secure.
If, on the other hand, you don't have two keychains, then I can offer no suggestion.

Messages Agent wants to use my confidential information??

Good afternoon,
Every time I restart my computer a window opens up saying:
Messages Agent wants to use your confidential information stored in "FaceTime: email address.com" in your keychain.
do you want to allow access to this item?
Always Allow    Deny       Allow
This has been happening since i've updated to OS X Yosemite 10.10
What is this and should I Allow it?
Thanks

Back up all data before proceeding.
Launch the Keychain Access application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
Select the login keychain from the list on the left side of the Keychain Access window. If your default keychain has a different name, select that.
If the lock icon in the top left corner of the window shows that the keychain is locked, click to unlock it. You'll be prompted for the keychain password, which is the same as your login password, unless you've changed it.
Right-click or control-click the login entry in the list. From the menu that pops up, select
          Change Settings for Keychain "login"
In the sheet that opens, uncheck both boxes, if not already unchecked.
From the menu bar, select
          Keychain Access ▹ Preferences... ▹ First Aid
There are four checkboxes in the window that opens. Check all of them. if they're not already checked. Close the window.
Select
          Keychain Access ▹ Keychain First Aid
from the menu bar and repair the keychain. Quit Keychain Access.
If you use iCloud Keychain, open the iCloud preference pane and uncheck the Keychain box. You'll be prompted to delete the local iCloud keychain. Confirm. Then re-check the box. Follow one of the procedures described in this support article to set up iCloud Keychain on an additional device.

On start up I get message: indentityservicesd wants to use your confidential information stored in FaceTime (email) in your keychain

Hello when I downloaded software OSX 10.9.1 now on startup I get this message 2 times: Identityservicesd wants to use your confidential information stored in Facetime @yahoo.com in your keychain. This is very annoying and slows my computer down. I dont use or dont want to use Facetime and Keychain is annoying also but i dont know how to delete either one.
<Email Edited by Host>

Back up all data.
Launch the Keychain Access application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Keychain Access in the icon grid.
Select the login keychain from the list on the left side of the Keychain Access window. If your default keychain has a different name, select that.
If the lock icon in the top left corner of the window shows that the keychain is locked, click to unlock it. You'll be prompted for the keychain password, which is the same as your login password, unless you've changed it.
Right-click or control-click the login entry in the list. From the menu that pops up, select Change Settings for Keychain "login". In the sheet that opens, uncheck both boxes, if not already unchecked.
From the menu bar, select
Keychain Access ▹ Preferences ▹ First Aid
If the box marked Keep login keychain unlocked is not checked, check it.
Select
Keychain Access ▹ Keychain First Aid
from the menu bar and repair the keychain. Quit Keychain Access.

Hi. I opened iPhoto and, suddenly, it tells me " WHAT IPHOTO LIBRARY DO I WANT TO USE?" but i had a iPhoto library. When i search on my Pictures, i have the file IPHOTO LIBRARY but it appears on a dim letters and i can not open it.

Hi. I need some help on the following problem. I opened iPhoto and, suddenly, it tells me " WHAT IPHOTO LIBRARY DO I WANT TO USE?" but i had a iPhoto library. When i search on my Pictures, i have the file IPHOTO LIBRARY but is was not the icon on it i previously remembered and it appears on a dim letters and it can not be opened ... How can i recover it??

Option 1
Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Choose to Rebuild iPhoto Library Database from automatic backup.
If that fails:
Option 2
Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums and keywords back.
Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one. .
Regards
TD

Transfer data from one server to another server using idocs

hi,crm
   i have a data in crm system, i want to download this data and upload into another crm system by using idocs.
please any one explain.

Hi Ravi,
      my senario is i have to transfer data from crm 5.0 to 7.0.
      i have marketing attributes
    t-code: bp----> marketing attributes
   i want to transfer marketing attributes from A to B.
       i created one structure for marketing attributes around 160. and i added this structure fields into custom segments.
      i created custom idoc type and i added segments into idoc.
    i created one function module for getting data from structure and passing to segments and idoctype.
   check the code below.
FUNCTION ZCRMXIF_MKT_DATA.
*"*"Local Interface:
*" IMPORTING
*"     REFERENCE(EV_MKT_ATTR) TYPE ZCRMXIF_MKT_STR
Data : c_segment type ZE101CRMXIF_MKT_ATTR_DATA,
       c_segment1 type ZE101CRMXIF_MKT_ATTR_DATA1,
       c_segment2 type ZE101CRMXIF_MKT_ATTR_DATA2,
       c_segment3 type ZE101CRMXIF_MKT_ATTR_DATA3,
       c_segment4 type ZE101CRMXIF_MKT_ATTR_DATA4.
data: c_messagetype type c value'zcrmxif_partner_save',
       c_idoc_type type c value'zcrmxif_partner_save_mkt',
       idoc_control like edidc,
       t_comm_control like edidc occurs 0 with header line,
       idoc_data like edidd occurs 0 with header line.
data: lt_mkt_attr type Zcrmxif_mkt_str occurs 0 with header line,
       ls_mkt_attr like zcrmxif_mkt_str.
loop at lt_mkt_attr.
            c_segment-PARTNER = lt_mkt_attr-partner.
            c_segment-PARTNER_GUID = lt_mkt_attr-partner_guid.
              idoc_data-segnam = 'ZE101CRMXIF_MKT_ATTR_DATA' .
              idoc_data-sdata = c_segment.
             append idoc_data.
           c_segment1-ADHAR_NUM = lt_mkt_attr-ADHAR_NUM.
           c_segment1-ADULTS = lt_mkt_attr-ADULTS.
           c_segment1-AGEGROUP = lt_mkt_attr-AGEGROUP.
           c_segment1-AG_CODE = lt_mkt_attr-AG_CODE.
           c_segment1-AMERICANEXPRESS = lt_mkt_attr-AMERICANEXPRESS.
           c_segment1-ANNUALINCOME = lt_mkt_attr-ANNUALINCOME.
           c_segment1-AUTO_TYPE_1 = lt_mkt_attr-AUTO_TYPE_1.
           c_segment1-AUTO_TYPE_2 = lt_mkt_attr-AUTO_TYPE_2.
           c_segment1-AUTO_TYPE_3 = lt_mkt_attr-AUTO_TYPE_3.
           c_segment1-A_HOMEDEL = lt_mkt_attr-A_HOMEDEL.
           c_segment1-BANKNAME = lt_mkt_attr-BANKNAME.
           c_segment1-BLOODPRESSURE = lt_mkt_attr-BLOODPRESSURE.
           c_segment1-BPRELATION = lt_mkt_attr-BPRELATION.
           c_segment1-BRAND = lt_mkt_attr-BRAND.
           c_segment1-CC1001 = lt_mkt_attr-CC1001.
           c_segment1-CC1002 = lt_mkt_attr-CC1002.
           c_segment1-CCCLASSIC = lt_mkt_attr-CCCLASSIC.
           c_segment1-CCGOLD = lt_mkt_attr-CCGOLD.
           c_segment1-CCOTHERS = lt_mkt_attr-CCOTHERS.
           c_segment1-CCPLAT = lt_mkt_attr-CCPLAT.
           c_segment1-CCREDIT = lt_mkt_attr-CCREDIT.
           c_segment1-ccsilver = lt_mkt_attr-ccsilver.
           c_segment1-CCTITA = lt_mkt_attr-CCTITA.
           c_segment1-CDEBIT = lt_mkt_attr-CDEBIT.
           c_segment1-CHILDREN = lt_mkt_attr-CHILDREN.
           c_segment1-CITIBANK = lt_mkt_attr-CITIBANK.
           c_segment1-CNAPP = lt_mkt_attr-CNAPP.
           c_segment1-CNC_PRINT = lt_mkt_attr-CNC_PRINT.
           c_segment1-CNC_SIZE = lt_mkt_attr-CNC_SIZE.
           c_segment1-CNC_SIZE_NEW = lt_mkt_attr-CNC_SIZE_NEW.
           c_segment1-CNC_STATUS = lt_mkt_attr-CNC_STATUS.
           c_segment1-CNC_TIME_ZONE = lt_mkt_attr-CNC_TIME_ZONE.
           c_segment1-CNC_TIME_ZONE_NEW = lt_mkt_attr-CNC_TIME_ZONE_NEW.
           c_segment1-CONDFIRSTZ = lt_mkt_attr-CONDFIRSTZ.
           c_segment1-COMPANY = lt_mkt_attr-COMPANY.
           c_segment1-CONDSECOND = lt_mkt_attr-CONDSECOND.
           c_segment1-CONDTHIRD = lt_mkt_attr-CONDTHIRD.
           c_segment1-CUSTOMERTYPE = lt_mkt_attr-CUSTOMERTYPE.
           c_segment1-CUST_BUSINESS_NAME = lt_mkt_attr-CUST_BUSINESS_NAME.
           c_segment1-DECL_DATE = lt_mkt_attr-DECL_DATE.
           c_segment1-DED = lt_mkt_attr-DED.
           c_segment1-DIST = lt_mkt_attr-DIST.
           c_segment1-DNC = lt_mkt_attr-DNC.
           c_segment1-DNCEMAIL = lt_mkt_attr-DNCEMAIL.
           c_segment1-DNCPHONE = lt_mkt_attr-DNCPHONE.
           c_segment1-DNCPOST = lt_mkt_attr-DNCPOST.
           c_segment1-DOB_FAM_2 = lt_mkt_attr-DOB_FAM_2.
           c_segment1-DOB_FAM_3 = lt_mkt_attr-DOB_FAM_3.
           c_segment1-DOB_FAM_4 = lt_mkt_attr-DOB_FAM_4.
           c_segment1-PLANG = lt_mkt_attr-PLANG.
*           c_segment1-APPL_SNAME = lt_mkt_attr-APPL_SNAME.
             idoc_data-segnam = 'ZE101CRMXIF_MKT_ATTR_DATA1'.
            idoc_data-sdata = c_segment4.
             append idoc_data.
            c_segment2-DTPCARDGIVCOU = lt_mkt_attr-DTPCARDGIVCOU.
            c_segment2-DTPCARDOFF = lt_mkt_attr-DTPCARDOFF.
            c_segment2-DTPCARDOTHSTORE = lt_mkt_attr-DTPCARDOTHSTORE.
            c_segment2-DTPCARDRETCOU = lt_mkt_attr-DTPCARDRETCOU.
            c_segment2-DTPCARDSHREDDED = lt_mkt_attr-DTPCARDSHREDDED.
            c_segment2-DTWELCOMCALL = lt_mkt_attr-DTWELCOMCALL.
            c_segment2-DUDZ = lt_mkt_attr-DUDZ.
            c_segment2-EDUDR = lt_mkt_attr-EDUDR.
            c_segment2-DTPCARDSTORE = lt_mkt_attr-DTPCARDSTORE.
            c_segment2-EDUER = lt_mkt_attr-EDUER.
            c_segment2-EDUG = lt_mkt_attr-EDUG.
            c_segment2-EDUHS = lt_mkt_attr-EDUHS.
            c_segment2-EDULAW = lt_mkt_attr-EDULAW.
            c_segment2-FOURWHEELER = lt_mkt_attr-FOURWHEELER.
            c_segment2-FULL_NAME = lt_mkt_attr-FULL_NAME.
            c_segment2-FWLT15KCC = lt_mkt_attr-FWLT15KCC.
            c_segment2-FAMILY_MEMBER_NAME = lt_mkt_attr-FAMILY_MEMBER_NAME.
            c_segment2-FAMILYMEMBERS = lt_mkt_attr-FAMILYMEMBERS.
            c_segment2-FAMILY_MEMBER_NAME_2 = lt_mkt_attr-FAMILY_MEMBER_NAME_2.
            c_segment2-FAMILY_MEMBER_NAME_3 = lt_mkt_attr-FAMILY_MEMBER_NAME_3.
            c_segment2-FAMILY_MEMBER_NAME_4 = lt_mkt_attr-FAMILY_MEMBER_NAME_4.
            c_segment2-FAMILY_MEMBER_NAME_5 = lt_mkt_attr-FAMILY_MEMBER_NAME_5.
            c_segment2-FWLT1KCC = lt_mkt_attr-FWLT1KCC.
            c_segment2-FWLT2KCC = lt_mkt_attr-FWLT2KCC.
            c_segment2-GEO_WING_LAT = lt_mkt_attr-GEO_WING_LAT.
            c_segment2-GEO_WING_LONG = lt_mkt_attr-GEO_WING_LONG.
            c_segment2-HDFCBANK = lt_mkt_attr-HDFCBANK.
            c_segment2-HSBC = lt_mkt_attr-HSBC.
            c_segment2-ICICIBANK = lt_mkt_attr-ICICIBANK.
            c_segment2-INCMTO = lt_mkt_attr-INCMTO.
            c_segment2-INCT2F = lt_mkt_attr-INCT2F.
            c_segment2-INCT2T = lt_mkt_attr-INCT2T.
            c_segment2-IND_SECTOR = lt_mkt_attr-IND_SECTOR.
            c_segment2-INTERNETCHATTING = lt_mkt_attr-INTERNETCHATTING.
            c_segment2-LICENSE_INFO = lt_mkt_attr-LICENSE_INFO.
            c_segment2-INTERNET_CONNECT = lt_mkt_attr-INTERNET_CONNECT.
            c_segment2-MFAM_INCOME = lt_mkt_attr-MFAM_INCOME.
            c_segment2-MODEL_1 = lt_mkt_attr-MODEL_1.
            c_segment2-MODEL_2 = lt_mkt_attr-MODEL_2.
            c_segment2-MODEL_3 = lt_mkt_attr-MODEL_3.
            c_segment2-MOTHERS_NAME = lt_mkt_attr-MOTHERS_NAME.
            c_segment2-MO_OF_P = lt_mkt_attr-MO_OF_P.
            c_segment2-MO_OF_P2 = lt_mkt_attr-MO_OF_P2.
            c_segment2-MO_OF_P3 = lt_mkt_attr-MO_OF_P3.
            c_segment2-MY_OF_P3 = lt_mkt_attr-MY_OF_P3.
            c_segment2-NOMINEES_NAME = lt_mkt_attr-NOMINEES_NAME.
            c_segment2-NONE = lt_mkt_attr-NONE.
            c_segment2-OCCU_OD_OTHR = lt_mkt_attr-OCCU_OD_OTHR.
            c_segment2-OCC_FAM_1 = lt_mkt_attr-OCC_FAM_1.
            c_segment2-OCC_FAM_2 = lt_mkt_attr-OCC_FAM_2.
            c_segment2-OCC_FAM_3 = lt_mkt_attr-OCC_FAM_3.
            c_segment2-OCC_FAM_4 = lt_mkt_attr-OCC_FAM_4.
            c_segment2-OCC_FAM_5 = lt_mkt_attr-OCC_FAM_5.
            c_segment2-OCC_NOM = lt_mkt_attr-OCC_NOM.
           idoc_data-segnam = 'ZE101CRMXIF_MKT_ATTR_DATA2'.
           idoc_data-sdata = c_segment4.
           append idoc_data.
           C_segment3-PLANG_OTHR = lt_mkt_attr-PLANG_OTHR.
           C_segment3-REF_MAILADD = lt_mkt_attr-REF_MAILADD.
           C_segment3-RELATION_FAM_1 = lt_mkt_attr-RELATION_FAM_1.
           C_segment3-RELATION_FAM_2 = lt_mkt_attr-RELATION_FAM_2.
           C_segment3-RELATION_FAM_3 = lt_mkt_attr-RELATION_FAM_3.
           C_segment3-RELATION_FAM_4 = lt_mkt_attr-RELATION_FAM_4.
           C_segment3-RELATION_FAM_5 = lt_mkt_attr-RELATION_FAM_5.
           C_segment3-REL_ACTIVE_STAT = lt_mkt_attr-REL_ACTIVE_STAT.
           C_segment3-REL_KISAN_MITRA_STAT = lt_mkt_attr-REL_KISAN_MITRA_STAT.
           C_segment3-REL_NOM = lt_mkt_attr-REL_NOM.
           C_segment3-REL_PLASTIC_CARD_STAT = lt_mkt_attr-REL_PLASTIC_CARD_STAT.
           C_segment3-REL_STAFF_STAT = lt_mkt_attr-REL_STAFF_STAT.
           C_segment3-REMARKS = lt_mkt_attr-REMARKS.
           C_segment3-ROCN = lt_mkt_attr-ROCN.
           C_segment3-ROCN_FAM_1 = lt_mkt_attr-ROCN_FAM_1.
           C_segment3-ROCN_FAM_2 = lt_mkt_attr-ROCN_FAM_2.
           C_segment3-ROCN_FAM_3 = lt_mkt_attr-ROCN_FAM_3.
           C_segment3-ROCN_FAM_4 = lt_mkt_attr-ROCN_FAM_4.
           C_segment3-ROOMS_PER_FLAT = lt_mkt_attr-ROOMS_PER_FLAT.
           C_segment3-SCH_NUM = lt_mkt_attr-SCH_NUM .
           C_segment3-SECONDARYEMAIL = lt_mkt_attr-SECONDARYEMAIL.
           C_segment3-SERIAL_NUM = lt_mkt_attr-SERIAL_NUM.
           C_segment3-SOCIETY_MEMBER = lt_mkt_attr-SOCIETY_MEMBER.
           C_segment3-SOC_CONTNO_LL = lt_mkt_attr-SOC_CONTNO_LL.
           C_segment3-SOC_CONTNO_MOB = lt_mkt_attr-SOC_CONTNO_MOB.
           C_segment3-SOC_CONT_DESIG = lt_mkt_attr-SOC_CONT_DESIG.
           C_segment3-SOC_CONT_PER_NAM = lt_mkt_attr-SOC_CONT_PER_NAM.
           C_segment3-STANCHART = lt_mkt_attr-STANCHART.
           C_segment3-ST_CODE = lt_mkt_attr-ST_CODE.
           C_segment3-ST_CODE_OLD = lt_mkt_attr-ST_CODE_OLD.
           C_segment3-ST_EMP_CODE = lt_mkt_attr-ST_EMP_CODE.
           C_segment3-TEENAGERS = lt_mkt_attr-TEENAGERS.
           C_segment3-SBI = lt_mkt_attr-SBI.
           C_segment3-ZLAT1 = lt_mkt_attr-ZLAT1.
           C_segment3-ZLONG1 = lt_mkt_attr-ZLONG1.
           C_segment3-ZWING_GEOCODE = lt_mkt_attr-ZWING_GEOCODE.
           C_segment3-ZNAMEPLATE_PHOTO = lt_mkt_attr-ZNAMEPLATE_PHOTO.
           C_segment3-ZLATITUDE = lt_mkt_attr-ZLATITUDE.
           C_segment3-ZLONGITUDE = lt_mkt_attr-ZLONGITUDE.
           C_segment3-ZLATITUDE_N_LONGITUDE = lt_mkt_attr-ZLATITUDE_N_LONGITUDE.
           C_segment3-ZWING_PHOTO = lt_mkt_attr-ZWING_PHOTO.
           C_segment3-ZCATEGORY_SHOPS = lt_mkt_attr-ZCATEGORY_SHOPS.
           C_segment3-ZNUM_OF_SHOPS = lt_mkt_attr-ZNUM_OF_SHOPS.
           C_segment3-ZELECT_SURVILL = lt_mkt_attr-ZELECT_SURVILL.
           C_segment3-ZBUILDING_TYPE = lt_mkt_attr-ZBUILDING_TYPE.
           C_segment3-ZFLATS_PER_FLOOR = lt_mkt_attr-ZFLATS_PER_FLOOR.
           C_segment3-ZBULDNG_FLOOR = lt_mkt_attr-ZBULDNG_FLOOR.
           C_segment3-ZSWIMMING_POOL = lt_mkt_attr-ZSWIMMING_POOL.
           C_segment3-ZGYM = lt_mkt_attr-ZGYM.
           idoc_data-segnam = 'ZE101CRMXIF_MKT_ATTR_DATA3'.
           idoc_data-sdata = c_segment4.
           append idoc_data.
          c_segment4-others = lt_mkt_attr-others.
          c_segment4-OCCU_OD = lt_mkt_attr-OCCU_OD.
          c_segment4-ZFLAT_TYPE = lt_mkt_attr-ZFLAT_TYPE.
          idoc_data-segnam = 'ZE101CRMXIF_MKT_ATTR_DATA4'.
           idoc_data-sdata = c_segment4.
           append idoc_data.
        ENDLOOP.
        IDOC_CONTROL-MESTYP = c_messagetype.
        IDOC_CONTROL-DOCTYP = c_idoc_type.
          CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
            EXPORTING
              MASTER_IDOC_CONTROL                  = IDOC_CONTROL
*             OBJ_TYPE                             = ''
*             CHNUM                                = ''
            TABLES
              COMMUNICATION_IDOC_CONTROL           = t_comm_control
              MASTER_IDOC_DATA                     = IDOC_DATA
*           EXCEPTIONS
*             ERROR_IN_IDOC_CONTROL                = 1
*             ERROR_WRITING_IDOC_STATUS            = 2
*             ERROR_IN_IDOC_DATA                   = 3
*             SENDING_LOGICAL_SYSTEM_UNKNOWN       = 4
*             OTHERS                               = 5
          IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
          ENDIF.
ENDFUNCTION.
i implement a badi "CRMXIF_PARTNER_MAP"
data ls_mkt_attr type zcrmxif_mkt_str.
LOOP AT cs_data_mapped INTO ls_data_mapped .
    lv_tabix = sy-tabix.
    loop at ls_data_mapped-ZZPARTNER-ZZMKT_ATTR into ls_mkt_attr.
      read table ls_data_mapped-zzpartner-ZZMKT_ATTR into ls_mkt_attr index 1.
       if ls_mkt_attr is not initial.
               CALL FUNCTION 'ZCRMXIF_MKT_DATA'
                 EXPORTING
                   EV_MKT_ATTR       = ls_mkt_attr
               endif.
     endloop.
     read table ls_data_mapped-zzpartner-ZZMKT_ATTR into ls_mkt_attr index 1.
         MODIFY cs_data_mapped FROM ls_data_mapped INDEX lv_tabix.
endloop.
i ddn't get data into sructure.
please explain how to doit.

Communication between SAP and 3rd Party Systems using IDOC HTTP XML Interfa

Hi
i am try do
Communication between SAP and 3rd Party Systems using IDOC HTTP XML Interface
With The help of SDN Contribution
link----
( have look on it)
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/4943f2b7-0a01-0010-37af-faff35b2f08c
I am getting error in
Partner system as HTTPLOG and "Execute" to check the results
Error is -- Port could not be created
RFC destination HTTPLOG Not specified for system HTTPLOG
any 1 have any idea if plzzzzzzzz...........
Thank u
Ram

Hello .
we are also in process of implementing the same
could you share the knowledge pl?
1)is it a separate add on with ALE to saphr
or using ECC ??
2)can u share the configuration part ??
we are trying it on webas as addon 3.0 .

I want to use IDOC to launch RFC

Similar Messages

Maybe you are looking for