Content Caching Using IDOC

Hi,
Is it possible to do content caching for the custom component build using java??
Thanks

kinda. you can cache the html output using idocscript. this means your java query only gets executed once every period, say, every half an hour.
but if your java output does not go to a page, like it is some kinda internal processing, then you'll need to figure out some kinda java caching solution.
idoc caching is covered in the manuals, see cacheInclude()

Similar Messages

Content Caching: Servlet.getLastModified()

Hello everyone,
I've been experimenting the past few days in the process of caching the contents of a servlet response, at the client side, and it was a very frustrating experience. After I was able to get a hold of all the mechanics of this process, I decided to share that information here, to relieve whoever is interested from the mess and frustration I've been through, especially that I haven't found much details on the topic in this forum and on the internet in general.
In case of the GET http method, the default implementation of the service() method uses the getLastModified() method to determine weather the servlet supports the idea of "client-side caching" or not. If getLastModified() returns -1 (which is the default behavior) then the service() method determines that caching is not supported by this servlet, and immediately passes control the the doGet() method, to construct the response for the client.
In order to support content caching, one has to override the getLastModified() method to return the date at which the servlet's-response content has been last modified. When the service() method finds that a positive value is returned by the getLastModified() method, one of the following scenarios would take place.
1-If the request coming from the client doesn't contain the If-Modified-Since header, then the service() method would add the Last-Modified header to the response object, specifying the date when the last content-modification took place, then pass control to the doGet() method. The client would then cache that response, take the value from the Last-Modified header and put it in the If-Modified-Since header in all the requests that follow, to that servlet.
2-If the request coming from the client does contain the If-Modified-Since header with a date EQUAL-TO the one returned by the getLastModified() method, then the service() method responds with a 304 (NOT MODIFIED) status to the client without referring to the doGet() method, and the client should use the cached content. Notice that in this case the service() method would NOT include the Last-Modified header to the response, since the client already knows it.
3-If the request coming from the client does contain the If-Modified-Since header with a date EARLIER-THAN the one returned by the getLatModified() method, then the service() method would add the Last-Modified header to the response object, specifying the date when the last content-modification took place, then pass control to the doGet() method. The client would then cache that response,(which is newer than the one it was already caching) and take the value from Last-Modified header and put it in the If-Modified-Since header in all the requests that follow.
One last thing, when you set the modification date, you HAVE TO round it down to the nearest second ( date / 1000 * 1000), as determined by the time precision in communications over the HTTP: if this process is left out, responses will NEVER be cached.
Edited by: 866769 on Aug 27, 2011 7:40 AM

kinda. you can cache the html output using idocscript. this means your java query only gets executed once every period, say, every half an hour.
but if your java output does not go to a page, like it is some kinda internal processing, then you'll need to figure out some kinda java caching solution.
idoc caching is covered in the manuals, see cacheInclude()

How to implement IDOC Serialization(EOIO) using IDOC Adapter

I am sending IDOC from 4.6c to XI to ECC6.0 using IDOC Adapter. I want to ensure that IDOCs are processed serially(EOIO) on the receiver side. I tried setting up the SE16-->IDXQUEUE on XI for the Receiver system and enabled the Queue processing flag on the Receiver communication channel, but the IDOCs are not serialized.
I see that XI is using XBTO_007(EO) Queue. It should be using the queue that I specified in SE16.Please let me know what else needs to be done to implement EOIO for the IDOC adapter.
Please note Sender is 4.6c System while the receiver is ECC 6.0 on WAS>=6.2
Thanks in advance.
Rajeev Gupta

Rajeev,
From http://help.sap.com/saphelp_nw70/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/content.htm
The receiver or sender system must be based on SAP Web Application Server 6.40 or higher.
The blog listed above is when you need to sends Idoc from R3 to XI in EOIO. It does not work with SAP R3 4.6C for the reason above.
For sending Idoc's from XI to R3 ( to ECC in your case ) in EOIO, you need to seelct Queue Processing in the Receiver Idoc adapter and the rest I think is handled implicitly by XI.
Regards
Bhavesh
PS: Have not tried this practically though!
Message was edited by:
Bhavesh Kantilal

To use IDOC or SRM?

Hello -
I have a scenario where i have Purchase Orders created in R/3 through SRM. Until i found the pre-delivered content i thought to use IDOCS in R/3 to generate my xml file output.
Now, my question is which option should i go with
1) R/3 using IDOCs and map it to xml file
2) SRM - use the predelivered content in XI and map it to xml file.
Is there any preferred method?
If its SRM what would be my adapter type and how would i trigger the sender to test my SRM-> XI -> File output.
Thanks,
Tiru

Hi,
1) R/3 using IDOCs and map it to xml file
2) SRM - use the predelivered content in XI and map it to xml file.
Is there any preferred method?
If there is no customization in the Idoc or not in the target file, directly go with SRM predeilivered content in XI. ANd if you require any transformation, then use Idoc to File Scneario concept.
**If its SRM what would be my adapter type and how would i trigger the sender to test my SRM-> XI -> File output.
Are you getting PO from SRM ? Because we have similar scenario, an dwe are getting PO from R/3. ..
Anyway it is like Idoc to File only for XI is concerened. Once PO is triggered it will come to XI as defined in the RFC Destination/Logical system etc.
Regards,
Moorthy

Webinar : Content Caching in Portal Runtime 6.0

SAP NetWeaver Know-How Network Webinar:
Content Caching in Portal Runtime 6.0
Wednesday, 7 July 2004
11 a.m. EDT
On Wednesday 7 July, Ronny Hendrickx, a NetWeaver EP RIG Consultant, hosts the webinar titled Content Caching in Portal Runtime 6.0 as part of the ongoing SAP NetWeaver Know-How Network Webinar Series.
Heres how Ron describes his webinar presentation:
This know-how call covers cache functionality in the PRT for SP2 and SP3 (Cache Validator, Cache Discriminator), the API, PRT configuration, and integration with the asyncResponse. Code demonstrations will accompany the various topics.
SDN invites you to post your questions to the presenter prior to the webinar and continue the online discussion afterward.
How to Participate
(Please go to the SDN Events page to see the article and download the PDF presentation)
Dial-in Information:
Date: Wednesday 7 July 2004
Time: 11 a.m. EDT
Within the U.S., call: +1.888.428.4473
Outside the U.S., call: +1.651.291.0618
Password: NetWeaver04
WebEx Information:
Topic: SAP NetWeaver Know-How Network
Date: Wednesday 7 July 2004
Time: 11 a.m. EDT
Meeting Number: 742391500
Meeting Password: netweaver04 (lowercase)
WebEx Link: sap.webex.com
Replay Information:
A recorded replay of this call will be available for approximately three months after the webinar. Access this recording by dialing the appropriate number and using the replay access code: TBD.
Toll-free: +1.800.475.6701
International: +1.320.365.3844
About the SAP NetWeaver Know-How Webinar Series
The SAP NetWeaver Know-How Webinar Series is driven by the SAP NetWeaver Regional Implementation Group (RIG), part of the SAP Development organization. The mission of the SAP NetWeaver RIG is to enable customers, employees, and partners to successfully implement the SAP NetWeaver solution. This SAP RIG has expertise in BI, EP, XI, and WebAS. They contribute their implementation expertise to the SDN implementation forums as well as to the SAP NetWeaver Know-How Webinar Series.
Disclaimer
SDN is not responsible for any changes to the webinar schedule. The webinar schedule may be changed or cancelled without prior notice.

this might relate to a bug of the early deploy command versions which allowed deployment only to destinct suborgs (-d), so don't deploy you staff to gloabl (-g option).
/u

Why we use IDOC adapter for IDOC as reciever?

hello,
Why we use IDOC adapter while using IDOC as receiver, whereas we don't use IDOC adapter while IDOC is sender?
I am clear about why we don't use adapter for sender IDOCs.
Thank you.
Sarika

Hi Sarika,
>>>>Why we use IDOC adapter while using IDOC as receiver,
maybe the easiest answer would be that we use
IDOC adapter as receiver to tell the XI where he should
send the data - there are many systems to which we can
connect our XI and somewhere there has to be an object
which will tell thx XI "where to" -> which RFC destination should it use
BTW
I believe IDOC apdater is also used as sender
although you don't configure it in AF:
"Once the IDoc has left the application through the RFC interface and has reached the IDoc adapter at the Integration Server inbound channel, the system converts it from IDoc format to IDoc XML format"
from:
http://help.sap.com/saphelp_nw04/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/content.htm
Regards,
michal

How to Use IDOC and ALE in SAP?

Hi anybody,
I want Use Idoc and ALE in sap ABAP. What is inbound and outbout process of IDOC?
Please give me sample code for Idoc . and Sample code for ALE.
anybody Please tell me.
Thanks
Regards,
S.Muthu.
IT Dept.

hi,
Follow the link for step by step ALE/IDOC tutorials.
http://www.sapmaterial.com/idoc_sample.html
http://www.****************/Tutorials/ALE/ALEMainPage.htm
An IDoc is not a process.
The term IDoc stands for intermediate document. It is simply a data container used to exchange information between any two processes that can understand the syntax and semantics of the data. An IDoc is created as a result of executing an outbound ALE or EDI process. In an inbound ALE or EDI process, an IDoc serves as input to create an application document.
IDocs are stored in the database.
In the SAP system, they are stored in database tables. Several utilities are available to display the information contained in an IDoc and present it in different ways. For details, refer to Chapter 11, "Monitoring the Interface."
Every IDoc has a unique number.
When an IDoc is generated in the system, a unique number is assigned to it. This number is unique within a client.
IDocs are independent of the sending and receiving systems. They can be used for SAP-to-SAP and SAP to non-SAP process communication as long as the participating processes can understand the syntax and semantics of the data.
IDocs are based on EDI standards, ANSI ASC X12 and EDIFACT, but are closer to the EDIFACT standards. The size and format of data elements in an IDoc type are derived from these standards wherever applicable. For example, if a material number is represented by 20 characters in an EDIFACT message, the corresponding data element in the IDoc is also 20 characters. If there is a conflict in data size between standards, the one with greater length is adopted. This approach ensures compatibility with most standards.
IDocs are independent of the direction of data exchange. An inbound and an outbound process can use an IDoc. For example, the ORDERS01 IDoc is used by the Purchasing module to send a purchase order, and is also used by the Sales and Distribution module to accept a sales order. Using this technique avoids creating redundant IDoc types for the same information.
IDocs can be viewed in a text editor and do not contain any binary data. Data is stored in character format. When transferred to the operating system, an IDoc is stored in a file in text format and can be viewed using a regular text editor. However, the contents make sense only if you understand the structure and format of the data in that IDoc. In the Appendix, "FAQs, User Exits, and Miscellaneous Resources," you will find an example of an IDoc file.
Hope this helps, Do reward.
Edited by: Runal Singh on Mar 5, 2008 6:09 PM

cm:search and content caching and

Hi All,
This is my environment :
Weblogic Portal 8.1 SP3.
Documentum : We are using DCS for connecting to SCS target system and is used as content repository.
If we use <cm:search> as below :
<%
String queryFor25Content = "i_chronicle_id in ('090000058000556e','090000058000487e','09000005800037c3','09000005800195bd','0900000580003116','0900000580011a61','0900000580004365','0900000580003a98','0900000580004299','09000005800030a9','0900000580004793','09000005800043da','090000058000310e','090000058001a622','0900000580021504','0900000580003536','090000058001bc11','090000058001a7bb','09000005800195b5','0900000580003e57','090000058002403c','0900000580023fed','0900000580024065','0900000580023f92','090000058001a971')";
%>
<cm:search id="contents" query="<%=queryFor25Content%>" useCache="true" cacheScope="application" cacheTimeout="300000"/>
<%
int size = contents.length;
for(int i=0; i< size; i++){
Node node = contents;
%>
-----------------Content Start-----------------
<es:notNull item="<%=node%>">
<cm:getProperty node="<%=node%>" name="_content" default="No Content Found"/>
</es:notNull>
-----------------Content End-----------------
<%
%>
In such case, this is my observation:
The content query will not be fired till cache expires.
What I would like to know is that :
Does this also caches the contents that are returned by this query?
As for as my observation is concerned, the content objects are not cached (meaning the binary propery of the content) rather it caches all other attributes of the content.
Can somebody comment on your experiences?. If i have to cache the whole content itself then, should I create my own Cache using "P13N" cache APIs and put the "com.bea.content.Node" in cache??
TIA,
Prashanth Bhat.

Hi,
Have you checked the following article?
Content Index status of all or most of the mailbox databases in the environment shows "Failed"
http://support.microsoft.com/kb/2807668
After you create new Active Directory group that is named "ContentSubmitters", please grant Admistrators and NetworkService full access to the group. Then please restart the search services to check result.
Here is a similar thread for your reference.
https://social.technet.microsoft.com/Forums/exchange/en-US/fccf9dca-b865-4356-905b-33ac25dcc44d/exchange-2013-content-catalog-index-failed-all-databases?forum=exchangesvravailabilityandisasterrecovery
Hope this is helpful to you.
Best regards,
Belinda Ma
TechNet Community Support

Moving shipment data using IDOC SHPMNT05

Hi guys,
I want to configure ALE process across two SAP systems and moved shipment data using IDOC SHPMNT05.
May I know how to do that.
Plz help me...................
Thankz in advance,
Swetha.

Hi Shwetha,
Please check the following links to start with.
http://help.sap.com/saphelp_nw04/helpdata/en/78/217da751ce11d189570000e829fbbd/content.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
Thanks,
Naren

Creation of PO using IDOC's

Hi,
I am trying to create a PO, using IDocs, in the SAP system. The IDoc will come from a non-SAP system - hence, this is an inbound interface.
Can someone please tell me which Message Type / IDoc Type I should use?
As well, I need to create Characteristics for the Purchase Order. So, I need an IDoc that allows me to create these.
Two options (using existing IDocs):
1. ORDERS/ORDERS05
I have read some of the help documentation and some of the messages posted on this forum and found that the ORDERS/ORDERS05 is used for outbound PO IDocs, and inbound SO IDocs.
Can someone please confirm or correct me? So, this option is OUT.
2. PORDCR/PORDCR05
Apparently, PORDCR/PORDCR05 can be used for inbound PO. However, it does not contain segments for Characteristics. Hence, I will need to extend the IDoc. However, there aren't any useful user-exits to handle the creation of Characteristic values!
Any ideas or suggestions will be greatly rewarded .
Thanks
Bobby

on your points
#1is correct.
#2 yes, if you need any other functionality you need to extend the IDOC. alternately look at BAPI_PO_CREATE* BAPIs to see if they fulfil your requirements

Data transfer b/w SAP to Java using IDOC and Interface SAP Jco

Dear Experts,
The challenging requirement we are having is, we need to create the interface for data transfer between SAP system and the Java system. The data will be transferred from SAP to java and similarly once some processing done in Java again the details needs to be transferred from Java to SAP.
For this data transferred we are planning to use IDOC process and for interface "SAP Java connector (Version 3.0.5)" we are planning to use. As per our understanding, from Java side one program needs to be written to connect with SAP as "Registered program". This registered program will appear in SAP GATEWAY automatically and using tRFC, TCP/IP connection both SAP and Java system will be connected.
In this case we are having some doubts.
1. The data from SAP is going to be transfered from one Custom transaction (Z tcode). Once "Outbound IDOC" will get triggered and will carry the details. Now the doubt is, whether the data / details will get transfered to JAVA system automatically or we need to perform any other steps from SAP ABAP coding...(like converting in to flat file, XML file and etc) ??
2. We are planning to install "SAP Jco" in Java server. Is this correct...??
3. Other than SAP Jco any other softwares needs to be installed or not..??
4. Since we are going to trigger the "outbound IDOC" from custom transaction, we are planning to develope one program in SE37. Other than this any other program we need to develop or not..??
5. Any sample Java program for the SAP Jco version 3.0.5 to create the "Registered program" with SAP..? (e.g. SAP Listener program).?
If anybody has detailed steps or explanation please share it with us.
Thanks in advance
Warm Regards,
VEL

Hi All,
For the above mentioned issue, we implemented JCo software in JAVA system and created the JAVA program including SAP logon credential details like Client, User name, password and Language details.
When this JAVA program was compiled successfully then, that non SAP system will appear in SAP gateway Tcode.
Once non SAP system started appearing in SAP gateway that means, both SAP & Non SAP are connected automatically.
Regards,
Velmurugan P

Working on LSMW using IDoc method for processing Open Sales Orders

We are currently in middle of creation of a new instance of production for a different Business SBU. We are looking to utilise the LSMW tool using IDocs for uploading / transferring the open orders to the new box. If some one has worked on LSMW using IDocs, please get in touch and if you could share any documents on the process of utilising the LSMW tool using Idocs for any kind of conversions, it would be great. The following is a sample case.
1. Each order will have multiple segments with different qualifiers under various segments.
2. Multiple line items would be available under each order.
Issues we are currently looking to solve :
1. How do you manage to loop through the qualifiers during processing for the same segment.
2. How do you prepare the tool to recognise the multiple line items of the same order.
3. What kind of strategy needs to be used to create the input data file(s). Like, splitting the header and detail level information ?
Note : The volume of data we are looking at is somewhere around 40-60 thousand orders worldwide.
Thanks in Advance.

hI vikram check this link
and reward points if helpful
http://www.****************/Tutorials/LSMW/IDocMethod/IDocMethod1.htm
http://www.jt77.com/system-dynamics/model-01395.html

Problem when setting Reason of Rejection for a sales order using IDOC

Hi All,
I am working on a requirement where i need to put a reason for rejection as 'Item Cancelled' for a sales order via IDOC 'IDOC_INPUT_ORDCHG' in a third party scenerio where the PR is created automatically from the sales order . When the IDOC is run in the foreground I get the information message Subsequent function " 'Purchase requisition from sales document' not possible Item & was rejected "(Message V1579) and the IDOC results in a error when run in the background mode because of the same information message. The message should not appear when a sales order is being processed in the background but still the message is being displayed . Is there any way the message can be suppressed ? Thanks in Advance.
Regards,
Sowmya.

can you send the program how you create a so or po using IDOC, as i've a assignment creating PO using IDOC & then creating a sales order of the PO. and i dont know how to create a IDOC. SO IF you have sample program it would be help full
Thanxs

Creation of PO/Contract/Scheduling agreement with ref to PR using IDOC

Hi Experts,
Is it possible to create PO/Contract/Scheduling agreement with reference to PR using inbound IDOC ?
If yes, please let me know the segment type and field to be populated for referencing PR in the IDoc .
Thanks in Advance,
Best Regards,
Mitesh Desai

Hi Aarif,
Thanks for taking time to reply .
We are palnning to integrate SAP and non SAP systems.
The business Process is as under .
(1) PR will be generated in ERP (Manaul/MRP)
(2) PR will be coverted into RFQ (for which there is no appropriate source of supply
in ERP)
(3) Sourcing will be done in non SAP system. RFQ will be created with dummy vednro (for example say "source") to identify RFQs to be sent to another system.
These RFQs needs to be sent using IDOC alonwith reference PR numbers and line item numbers.
Multiple PRs will be combined into one RFQ as multiple line items.
(4) Non SAP system will do sourcing and generates either PO or master outline agreement and have reference PR/RFQ numbers and line item numbers.
No SAP system will send PO/outline agreement information to SAP system in XML file format to generate inbound IDOC in SAP .
(5) This inbound idoc will generate PO/outline agreement in SAP.
From SAP functionality point of view, I ca createPO/outline agreement with reference to PR but My Question is how I can generate PO/outline agreement in SAP through IDOC and using "Reference PR or RFQ numbers".
Looking forward to help ASAP.
Regards,
Mitesh Desai

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.

Content Caching Using IDOC

Similar Messages

Maybe you are looking for