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.

Similar Messages

Create PO using Idoc with free goods

Hi guys,
i'am currently working on a projekt i need to create a purchase order containing free goods.
We've already tested the PORDCR/PORDCR1 message and Idoc types PORDCR101/102 with BAPI's
IDOC_INPUT_PORDCR1 - w/ self-defined process code (via we42)
BAPI_IDOC_INPUT1 - w/ standard process code (BAPI)
Nothing worked. Got lots of errors in we05 transaction (mostly status 51)
Important:
We need to give the Idoc the free gods flag so we didnt need to set the net_price.
Thanks for your help guys,
Daniel

Use Order PORDCR102, with your extension say ZPORDCR102.
Create one control table and assign Function module to that table.
Set this new Ztable with all required data like free goods.
Then create new idoc, this new idoc will take message PORDCR102 and extension will pick new table and add free goods flag while creating PO.
Hope this helps

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

How to Test, Inbound idoc ,with out the Sender System, using a Text File

Hi Guru's .
we wanted to test BLAORD03 inbound idoc (Message Type BLAORD).with out the SENDER SYSTEM.
on the same client.
we wanted to test this idoc with text file from our local machine.
Can anyone give us detail steps.like how to create File layout
with Segment name,and values for the fields.how to pass this file to the system.
Thanks in advance.

Hi Aparna.
My requirement is to test the idoc with Inbound File.
Generate a file with the data entered through segments through we19 ,and use the same file for processing through we16.
when i am trying to do this syst complaing about
Partner Profile not available, and some times
port not available. and some times with
'No further processing defined'.
but i maintained part profiles and port perfectly.
Can you help me in testing with test 'File' port.

How outbound IDoc with Z segment is creating without using a program/FM?

Hi,
I am having an outbound IDoc with Z message type and segments.
I need to find how this IDoc/ IDoc segment is getting created. I tried to find
it using the segment’s where used list (in SE11- IDoc segment structure). But it
is showing that the structure and fields are not used anywhere.
How it is possible to create a Z segment in IDoc without
using the corresponding structure in some program or function module?
I have searched in google/scn for a solution, but didn’t find
anything.
Any one please helps me to find how this IDoc segment is
populating?
Regards,
Dipin

Hi Arthur,
This IDoc is catering as part of a flow (Tcode IW21). I have
set a break point in the function module ALE_IDOCS_CREATE and processed the transaction
IW21, but the program didn’t stop in the break point, but the IDoc got created.
Regards,
Dipin

Performance issues in using RBDAPP01 for reprocessing iDocs with Status 64

Hi All,
I am using the Standard ABAP Program 'RBDAPP01' for reprocessing Inbound iDocs with Status 64 (Ready to be posted).
When this is scheduled as a job in background, I find that it opens multiple sessions and occupies all available dialog sessions.
This in turn slows down the entire system.
Also, I find the addition 'Packet Size' on the selection screen for the program.
Is it related in any way to the number of sessions the program creates?
Any pointers in resolving this issue will be extremely helpful.
Thanks in advance.
Regards,
Keerthi

Hi,
When you mention Parallel Processing, it becomes active only if I choose that particular option on the selection screen right?
In my case, I haven't chosen parallel processing, but still the overall system performance seems to have fallen very badly.
Now please correct me if my understanding is wrong.
If I increase my Packet Size, it should improve the system performance, but will increase my runtime for the selected iDocs.
But as I have not selected parallel processing in this current situatuon, it should not have any impact here.
Have I summarized it rightly?
Thanks in advance.
Regards,
Keerthi

LSMW using IDoc Method *Error :No partner exists with the name '', type ''*

Hi All,
I am a newbie. I am trying LSMW using IDoc Method.
I got an error when i executed Start IDoc Generation step: No partner exists with the name '', type ''
Could anyone tell what wrong I might have done,
Thank you,
Shiv Ram

Hi,
You have to setup your IDoc configuration in LSMW:
1) Enter the menu \Settings\IDoc Inbound Processing
2) Create a FILE port by clicking "Maintain Ports"
3) Create a logical system (LS) partner number by clicking "Maintain Partner Numbers"
4) Be sure your partner profile that you create is "Active" by clicking "Classification"
5) In the end click "Activate IDoc Inbound Processing" bottom.
Run your LSMW again. This time it shoud run wothout any problem.
Hope it helps.
Chang

How to create a Return Sales order from a PO with Return Items using IDOCS?

Is it possible to create a Return Sales order in one system with a PO having return Items in the other system using IDOCS.
What kind of sales documents are created from IDOCS created with PO's having return items ?

anyone?

Populate City file using LSM workbench

I need to know how to populate 'City File' using LSM workbench. It would be extremely helpful if anyone answers the following questions:
1) Where to get the US regional structure source data?
2) How to convert it to SAP uploadable format?
3) How to upload the data to SAP system?
In other words, I need to know the steps of the process to populate SAP US regional structure from scratch.
Thanks in Advance.

I need to know how to populate 'City File' using LSM workbench. It would be extremely helpful if anyone answers the following questions:
1) Where to get the US regional structure source data?
2) How to convert it to SAP uploadable format?
3) How to upload the data to SAP system?
In other words, I need to know the steps of the process to populate SAP US regional structure from scratch.
Thanks in Advance.

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

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 .

Need help in populating Text ID using IDOC ORDERS05

I have following scenario.
PO is being send from ECC to EDI partner.
and we received the PO feedback from the EDI partner
For PO feed back, we are using ORDERS05 idoc type and ORDRSP message type.
Custom Text Id(F01) has been added to the Text tab of the header section of the Purchase order screen (ME23N).
Custom Text id (F02) has been added to the Text tab of the Item section of the purchase order screen.
(Text ID F01 and F02 are in object EKKO - checked in transaction se75)
Now, I m posting idoc with the following value but Text field (in header and item level) is not updating while displaying PO.
Header - E1EDKT1
     TDID -   F01
     TSSPRAS- E
                     TDOBJECT - EKKO
              E1EDKT2
     TDLINE   - "My Header Text"
Item Level - E1EDKT1
     TDID -   F02
     TSSPRAS- E
                     TDOBJECT - EKKO
              E1EDKT2
     TDLINE   - "My Item level Text"
Can we update the Text Id in PO using IDOC ORDRSP.ORDERS05? I have tried but it is not updating
Any suggestion.
Edited by: Chetankumar Patel on Mar 14, 2011 10:17 PM

Have you tried with updating other Long texts ? While going through the code of inbound function module IDOC_INPUT_ORDRSP, it is mentioned that only limited fields are available for updation. See remarks in line no : 88 of include LEINMF2O.
read document and prepare for update P.O. Item fields
* possible Update fields of EKPO: LABNR, IDNLF, NETPR

B1358 error while posting inbound idoc with a FM

Hi
We are trying to post and inbound IDOC with the help of an rfc and eventually creating an invoice from a bdc wrapped in the RFC
The idocs are successfully pushed to R/3 while they are not getting posted and the error code in we02 is as follows
No status record was passed to ALE by the application
Message no. B1358
Diagnosis
The application failed to return a status record to the ALE layer after the IDoc was processed.
This is due to an error in the application function module which processed the inbound IDoc.
Procedure
If you wrote the application function module yourself, you need to change the program.
If the function module in question is a standard application function module, you should consult SAP.
Note: we are using a custom function module
regards
krishna

Hi Krishna,
I assume that your function module processing the IDOC does not follow the ALE/IDOC processing rules.
Please check out the programming guidelines in the SAP Online Help under:
<a href="http://help.sap.com/saphelp_nw70/helpdata/en/78/21758051ce11d189570000e829fbbd/frameset.htm">http://help.sap.com/saphelp_nw70/helpdata/en/78/21758051ce11d189570000e829fbbd/frameset.htm</a>
Important are the parameters and tables that need to be returned, containing the correct IDOC processing status. Please take the IDOC processing quite serious in regards to complete Logical Unit of Works.
Best regards,
SIlvia

Hi Using IDOCs with LSM Workbench????

Similar Messages

Maybe you are looking for