How to use segment ZCRMXIF_PARTNER_SAVE01 in LSMW to Generate/Change BP data using IDOC

Hi Gurus,
I have an requirement to add contact person first name and last name using Relationship kind as '0001' for an BP.
This requirement i need to work with LSMW and generate IDOC for respective changes.
To work with LSMW and IDOC i need to pass data to ZCRMXIF_PARTNER_SAVE01.
Can you all suggest me what are the mandatory fields to be passed to this segment and what are the fields to which i can pass FIRST NAME and LAST NAME of the CONTACT PERSON of the BP.
Please post me your replies in detail iam new to crm i can understand.
Thanks & Regards,
Saravanan Sambandam

Hi Saravanan,
Which method you used.
Regards,
Madhu.

Similar Messages

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.

How to use idoc infrec01

Any example or docu about how to use idoc infrec01?
Thanks.

This idoc is for Purchasing info record.
U can get the docu in we60 tcode.
enter the name in basic type and go menu documentation->html format.
Regards

How to use IDoc. in data migration?

Dear Expert,
How can I use IDoc. method in Data Migration???

Hi,
You can use Idoc method in data migration using LSMW - Idoc method.
In LSMW select the Idoc method and give the Message type and Basic type according to your requirement.
Before that you need to maintain the Idoc inbound processing.
Goto LSMW initial screen,
LSMW -> Settings -> IDoc Inbound Processing. Maintain File port, partner type and partner no.
After maintaining the Partner no. goto WE20 (maintain partner no.) and add the message type in the Inbound parameters of the partner no. Also we need to maintain the Process code for the message type.
After all this settings we can use Idoc method for data migration.
The rest of the steps are same as other methods till convert data.
Regards,
Asif Ali Khan

How to Use IDOC in Java Mapping?

Hello -
1. How can i use an IDOC to map to an xml file using Java mapping in an IDOC -> XI -> XML file scenario?
2. How can i test this scenario outside XI, i mean using Eclipse?
3. How can i create a test data for IDOC for the above scenario in XML format to test it using Java program?
Thanks,
Tirumal

Hi,
***1. How can i use an IDOC to map to an xml file using Java mapping in an IDOC -> XI -> XML file scenario?
It will be a direct xml to xml mapping. Is your requirement requires Java Mapping? Otherwise you can easily do without that - check this-
Is there simply way to map an idoc to an flatfile?
***2. How can i test this scenario outside XI, i mean using Eclipse?
You need to have XML input for this. Just try to get the IDoc XML or create xml input based on the Idoc Structure. You can make use of WE60 to get IDOC xsd .
***3. How can i create a test data for IDOC for the above scenario in XML format to test it using Java program?
Go to Tcode WE19 in the R/3 and generate the outbound Idoc . And then use that xml ( for question no 2). as a test data to test independently.
Hope this helps..
Regards,
Moorthy

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

How to use Idoc script in HTML

I know how to make my own fragments made with idoc. It works fine.
But i don't know how to write idoc without using fragments. When i write it inside html on the page, it just get outputs as it is, it doesn't get executed. What tag do i need to use? Can someone give a small example?

Hi,
 
Is the same as using fragments.
I use this code in a primary template
<div class="foto-doble">
<div>
 
  
  
 
 
 
Are you using external browser to view the page or "Preview"?

How to get "Synchronize with database" to compare/generate changes for database 'contexts'?

Hi
Using SDDM 3.3.
How does one get to synchronise changes/differences in 'contexts' (defined in physical model - Oracle DB)?
I have tried to synchronize both ways, i.e. model to db and db to model, but never does it show the DDL necessary to create the missing context.
Yes, Context is selected/ticked under preferences for Oracle DB synchronization preferences.
Thank you & Regards

Hi Philip
If I use the "generate DDL" option from the toolbar, it does generate DDL for the context I have in the physical model. I can select/deselect them in the DDL Generation Options window.
Why then would it not generate DDL when comparing the model with the database, i.e. using the "synchronise data dictionary to model" option? It successfully generates a 'patch'/change script for tables, views, packages, etc.?
Thank you & Regards
PS. I am asking for a way to get it to generate me a complete 'patch'/change script.

How can I get rid of a type generated by the Data/Services return type wizard?

Hi All,
I have a JSON service that returns an object called "error". The Data/Services "Configure Return Type" wizard automatically turned this into a class "Error".
However, this caused over a hundred errors to show up inside the generated classes, "Call to a possibly undefined method Error." That's because of lines like this:
throw new Error(propertyName + " is not a data property of entity Agreements");
It's trying to throw a regular "Error" object, but now that there's an "Error" class in the same package, that is taking precedence--and that Error object doesn't have a constructor with a single parameter. At least, that's what I think is going on.
I tried to fix it by deleting _ErrorEntityMetadata.as, _Super_Error.as, and Error.as from the valueObjects package. I then opened the FML file and deleted the definition for the entity "Error" and every reference to the Error entity (class) in my FML file.
I then changed my JSON service so that it returns an object called "serviceError" instead of just "error".
But, whenever I re-run the "Configure Return Type" wizard, it regenerates the Error class, even though I've deleted it from everywhere I can find it. That breaks my project completely! How can I end this and get Flash Builder to *stop* generating this type!
In the "Configure Return Type" wizard I very carefully inspected the type of every bit of data coming back to make sure none of them show up as type "Error." And they don't (as expected, since I changed the object's name to serviceError--now the type of that object is ServiceError.
-Josh

I think you are facing this known issue https://bugs.adobe.com/jira/browse/FB-29770
Please vote it.
Thanks for the link--I just voted for it.
To avoid this, in the last page of "Configure Return Type", edit return type name to something else (You can also edit subnodes's name too in the wizard).
Actually, that's exactly what I saw doing; I apologize if that wasn't clear in my post.
I closed and restarted Flash Builder, and once I did that Flash Builder stopped generating the Error class. My guess is that the FML file, even though I had updated it (by deleting all references to the Error class), was cached in some fashion by Flash Builder, and restarting Flash Builder forced it to reread the FML file?
Additional point of clarification: my understanding is that the FML file stores all the metadata about the services that Flash Builder has been able to figure out so far, and when you run the Configure Return Type wizard, it will regenerate *every* type in the FML file, even if that type is not mentioned anywhere in the particular return value that you are working with.
Edited to provide additional thoughts on FML file.

LSMW Vendor Create /Change (XK01/XK02) by IDOC CREAMS05 for CONTACT PERSON

Hi Experts,
Can you Please help me for CONTACT PERSON (create/ change) upload for vendor using the IDOC type CREMAS05.
which structure is appropriate for CONTACT PERSON in CREMAS05
Thanks in advance,
Babumiya Mohammad

okay, this screen is not active in my system. (are you doing retail?)
if it is address data, then it is usually transmitted with the ADR3MAS idocs
this is at least the case for customer contacts.
Edited by: Jürgen L. on Feb 20, 2012 5:13 PM

How to attempt production orders and get feedback by using IDocs

Hi,
I'm new new to SAP and R3 respectively mySAP. I need to know how to use IDocs (over file system) to attempt production orders to an extern application and how to get the feedback of the whole orders and single operations.
I found the IDoc-base-type "PPCC2RECORDER01" to send production orders. Is that the right base type for production orders?
(In consideration of compatibility and support me was recommend to avoid the old types OPERA2 and CONF21.)
What IDoc-types do I need to get feedback about a production order and its operations?
I hope someone is understanding my questions is able to help me. Please apologize my broken English.
Thanks!
Hannes

PROGRAM....... ZRCCLORDPROC
TITLE......... Production Odrer Idocs
AUTHOR........ Aveek Ghose
DATE WRITTEN.. 15/09/2006
R/3 RELEASE... 4.6C
=====================================================================*
COPIED FROM... N/A
DESCRIPTION...
*& Creation of production order IDOCs to a given selection
*& This program selects to an input given via the selection screen the *
*& corresponding production orders from the database. Then the function
*& module for creation of planned order idocs is called. *
*& In general this report is called from the report RCCLTRAN, but it *
*& can also be used for its own. *
=====================================================================*
PROGRAM TYPE.. Outbound Interface
DEV. CLASS.... ZPD1
LOGICAL DB.... N/A
=====================================================================*
SCREENS....... N/A
GUI TITLE..... N/A
GUI STATUS.... N/A
TRANSACTIONS.. N/A
USER EXITS.... N/A
=====================================================================*
CHANGE HISTORY *
Date By Correction Number & Brief Description Release
Tables / Structures
REPORT zrcclordproc
 NO STANDARD PAGE HEADING
 MESSAGE-ID ZCUST
 LINE-COUNT 65(0)
 LINE-SIZE 255.
INCLUDE RCORDO01. " PBO-Modules *
INCLUDE RCORDI01. " PAI-Modules *
INCLUDE RCORDF01. " FORM-Routines *
--> Global data
TYPE-POOLS: cloi.
include zprodata. "Types / constants for Orderselection
include zrcordtop. "Tables / Data for this report
include zrcordtop1.
include yrccl_constants.
TABLES : jcds,
 tvarv,
 zzzz_xref_data.
TYPES: BEGIN OF ty_date,
 aufnr TYPE aufnr,
 aedat TYPE aufaedat,
 aezeit TYPE co_chg_time,
 erdat TYPE auferfdat,
 erfzeit TYPE co_ins_time,
 loekz TYPE aufloekz,
 indicator(1) TYPE c,
 END OF ty_date.
DATA: is_enhancement type isu_ord_segments_determine.
DATA: itab_date TYPE STANDARD TABLE OF ty_date
 INITIAL SIZE 0 WITH HEADER LINE.
DATA: f_objnr TYPE j_objnr.
DATA: g_report_sub_head(72) TYPE c, "Sub-Header hold area
 g_report_head(72) TYPE c, "Header hold area
 g_run_date(72) TYPE c, "Holds message for Run date
 g_run_time(72) TYPE c. "Holds message for Run time
DATA:
f_old_date TYPE datum,
f_old_time TYPE uzeit,
f_continue(1) TYPE c.
END OF INSERTION DS001
--> Überschrift für sonstige Einstellungen
SELECTION-SCREEN SKIP 2.
SELECTION-SCREEN BEGIN OF BLOCK miscellaneous WITH FRAME.
SELECTION-SCREEN SKIP 1.
SELECTION-SCREEN COMMENT 1(30) text-001. "#EC
SELECTION-SCREEN SKIP 1.
*>> Logical system comes from Report RCCLTRANS
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(30) text-002.
SELECTION-SCREEN POSITION 35.
PARAMETERS opt_sys LIKE tbdlst-logsys.
SELECTION-SCREEN END OF LINE.
*>> Messagetype comes from Report RCCLTRANS
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(30) text-003.
SELECTION-SCREEN POSITION 35.
PARAMETERS mestyp LIKE tbdme-mestyp.
SELECTION-SCREEN END OF LINE.
*>> Messagetype comes from Report RCCLTRANS
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(30) text-004.
SELECTION-SCREEN POSITION 35.
PARAMETERS: p_date TYPE sydatum. "last run date
SELECTION-SCREEN END OF LINE.
*>> Messagetype comes from Report RCCLTRANS
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(30) text-005.
SELECTION-SCREEN POSITION 35.
PARAMETERS: p_time TYPE syuzeit. "last run time
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END OF BLOCK MISCELLANEOUS.
*MOD-006
*>> Messagetype comes from Report RCCLTRANS
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(30) text-006.
SELECTION-SCREEN POSITION 35.
PARAMETERS: p_update AS CHECKBOX DEFAULT space.
SELECTION-SCREEN END OF LINE.
*MOD-006
*MOD-006
*>> Messagetype comes from Report RCCLTRANS
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(30) text-007.
SELECTION-SCREEN POSITION 32.
SELECT-OPTIONS: s_rundt FOR sy-datum NO-EXTENSION.
SELECTION-SCREEN END OF LINE.
*MOD-006
*MOD-006
*>> Messagetype comes from Report RCCLTRANS
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(30) text-008.
SELECTION-SCREEN POSITION 32.
SELECT-OPTIONS: s_runtm FOR sy-uzeit NO-EXTENSION.
SELECTION-SCREEN END OF LINE.
*MOD-006
**MOD-006
*SELECTION-SCREEN BEGIN OF LINE.
*SELECTION-SCREEN COMMENT 3(30) text-009.
*SELECTION-SCREEN POSITION 32.
*SELECT-OPTIONS: s_emat FOR zzzz_xref_data-z_in_value.
*SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END OF BLOCK miscellaneous.
**MOD-006
Write selected AUFPL numbers via ranges table to memory ?
PARAMETERS:
ordtomem TYPE cloi_x DEFAULT '' NO-DISPLAY. "X: yes
do not select from MARC, but use ranges tables directly. MK 4.0C
matnr_gl and werks_gl must have the same length.
PARAMETERS: no_sel TYPE c DEFAULT ' ' NO-DISPLAY.
--> Normal selection parameters for ORD comes from the logical db
*& Event START-OF-SELECTION
START-OF-SELECTION.
--> Select the ORD according to the selected
 MRP controller, Material, work center and plant
*MOD-006
Validate the last run date & Time
PERFORM validate_last_run_date_time.
*MOD-006
BEGIN OF INSERTION DS001
get the entry of the last program run
select single * for update from ycloidownlprot
 where logsys = OPT_SYS and
 downloadtype eq C_DOWNL_PROCESS_ORDERS.
if YCLOIDOWNLPROT-IN_PROGRESS eq CLOI_TRUE.
program is already running, do not allow to start again
 write : / text-004, YCLOIDOWNLPROT-USERNAME.
 exit.
endif.
YCLOIDOWNLPROT-MANDT = SY-MANDT.
YCLOIDOWNLPROT-LOGSYS = OPT_SYS.
YCLOIDOWNLPROT-START_DATE = SY-DATUM.
YCLOIDOWNLPROT-START_TIME = SY-UZEIT.
YCLOIDOWNLPROT-USERNAME = SY-UNAME.
YCLOIDOWNLPROT-DOWNLOADTYPE = C_DOWNL_PROCESS_ORDERS.
YCLOIDOWNLPROT-IN_PROGRESS = CLOI_TRUE.
insert or update entry (dependant if entry already exists)
MODIFY YCLOIDOWNLPROT.
COMMIT WORK.
CLEAR CREATED_MASTERIDOCS_PRO.
EXPORT CREATED_MASTERIDOCS_PRO TO MEMORY ID 'YLOI001'.
END OF INSERTION DS001
BEGIN OF INSERTION DS001
if not sscrfields-ucomm = 'ONLI'. mk zu 4.0
exit.
endif.
if s_dispo is initial and
 s_matnr is initial and
 s_arbpl is initial and
 s_werks is initial.
 exit.
endif.
Send only orders with type 40 - process orders
p_autyp = '40'.
END OF INSERTION DS001
*>> Put the ranges tabs back into matwrk list if no selection (NO_SEL)
IF no_sel = cloi_true.
 CLEAR t_matwrk_key. REFRESH t_matwrk_key.
 LOOP AT s_matnr.
 t_matwrk_key-matnr = s_matnr-low.
 READ TABLE s_werks INDEX sy-tabix.
 t_matwrk_key-werks = s_werks-low.
 APPEND t_matwrk_key.
 ENDLOOP.
 SORT t_matwrk_key BY matnr werks.
 DELETE ADJACENT DUPLICATES FROM t_matwrk_key.
delete duplicate duplicates from ranges table. Therfore sort by LOW
(HIGH is not used in this case).
 SORT s_matnr BY low.
 DELETE ADJACENT DUPLICATES FROM s_matnr.
 SORT s_werks BY low.
 DELETE ADJACENT DUPLICATES FROM s_werks.
ENDIF.
--> Determine which segments are selected in the message type
PERFORM ord_segments_determine
 USING mestyp
 CHANGING afpo_x
 jstk_x
 afab_x
 affl_x
 afvo_x
 kbed_x
 jstv_x
 resb_x
 kbeu_x
 afuv_x
 is_enhancement
 jstu_x.
Export the flags to the memory, because the following subroutine
must not have any parameters !!!
EXPORT affl_x
 afvo_x
 kbed_x
 resb_x
 kbeu_x
 afuv_x
 TO MEMORY ID 'LOI03'.
MK 19980326 enhanced selections on header/operation level
get selection profile for log system from customizing if available
SELECT SINGLE * FROM tcloi9 WHERE logsys = opt_sys.
if entry exists for the logical system
IF sy-subrc = 0.
if an selection profile for the order is entered, use it for selection
 IF NOT tcloi9-ord_selid IS INITIAL.
 p_selid = tcloi9-ord_selid.
 ENDIF.
 IF NOT tcloi9-ord_opr_selid IS INITIAL AND
 NOT afvo_x IS INITIAL AND NOT affl_x IS INITIAL.
 ord_opr_selid = tcloi9-ord_opr_selid.
 ENDIF.
ENDIF.
initialize control key table for selections
CALL FUNCTION 'CLOI_STEUS_GET'
 EXPORTING
 logsys_to_init = opt_sys
 IMPORTING
 no_entry_for_logsys = no_entry_for_logsys
 TABLES
 t_steus = t_steus
 EXCEPTIONS
 logsys_not_initialized = 1
 OTHERS = 2.
Write structure information into the memory
perform fill_memory_selobj.
-> import table with already sent orders
IMPORT gt_aufnrdone FROM MEMORY ID 'LOIAUFNRTAB'. "N599845
SORT gt_aufnrdone BY low. "N599845
--> Read header information
GET ioheader.
Check if material/plant combination is selected MK 4.0C
CLEAR check_flg.
IF no_sel = cloi_true.
 READ TABLE t_matwrk_key
 WITH KEY matnr = ioheader-matnr
 werks = ioheader-werks BINARY SEARCH.
 IF sy-subrc <> 0.
 check_flg = cloi_true.
 ENDIF.
ENDIF.
-> check if order was already sent
IF NOT gt_aufnrdone[] IS INITIAL. "N599845
 READ TABLE gt_aufnrdone WITH KEY "N599845
 low = ioheader-aufnr "N599845
 TRANSPORTING NO FIELDS "N599845
 BINARY SEARCH. "N599845
 IF sy-subrc = 0. "N599845
 -> order already sent
 check_flg = cloi_true. "N599845
 ENDIF. "N599845
ENDIF. "N599845
leave GET routine if check_flg is set.
CHECK check_flg IS INITIAL.
CLEAR t_afpo. REFRESH t_afpo.
CLEAR t_affl. REFRESH t_affl.
MOVE-CORRESPONDING ioheader TO t_afko.
GET ioheader LATE.
BEGIN OF INSERTION DS001
Check whether the process order has been changed since the last
run of the program
clear f_continue.
if the CHANGED date is greater than the last run or initial
IF IOHEADER-AEDAT GT F_OLD_DATE OR
 ( ioheader-aedat is initial and
 ioheader-aezeit is initial ).
if the CHANGED date is initial check the creation date
 if ioheader-aedat is initial.
if the creation date is greater than or equal to the date of the last
run, if it is equal the creation time must be later or equal to the
start time of the last run
 IF IOHEADER-ERDAT GT F_OLD_DATE OR
 ( IOHEADER-ERDAT EQ F_OLD_DATE AND
 IOHEADER-ERFZEIT GE F_OLD_TIME ).
 f_continue = 'X'.
 endif.
 else.
 f_continue = 'X'.
 endif.
if the CHANGED dat is not initial check it against the last run
ELSEIF IOHEADER-AEDAT EQ F_OLD_DATE AND
 IOHEADER-AEZEIT GE F_OLD_TIME.
 f_continue ='X'.
endif.
Aenderung 295/99 Selektions-Aenderung vom 26. August 99
Wenn Auftrag bereits techn. abgeschlossen ist, so darf kein IDOC
erzeugt werden, wenn Auftrag zum löschen vorgemerkt wird.
CONCATENATE 'OR' IOHEADER-AUFNR INTO F_OBJNR.
SELECT SINGLE * FROM JEST
 WHERE OBJNR = F_OBJNR
 AND STAT = 'I0045'.
IF JEST-INACT EQ SPACE AND SY-SUBRC EQ 0.
 SELECT * FROM JCDS WHERE OBJNR EQ F_OBJNR AND
 STAT EQ 'I0045' AND
 INACT EQ SPACE.
letzte Aenderung des Status TABG wird geprueft Beg. WA 354/99
 ENDSELECT.
IF ( F_OLD_DATE GT JCDS-UDATE OR " Beg JB_02
 ( F_OLD_DATE EQ JCDS-UDATE AND
 F_OLD_TIME GT JCDS-UTIME ) ) AND " End JB_02
 SY-SUBRC EQ 0.
 CLEAR F_CONTINUE.
 ENDIF.
ENDIF.
Ende 295/99
check f_continue eq 'X'.
END OF INSERTION DS001
t_afko-t_afpo = t_afpo[].
t_afko-t_jstk = t_jstk[].
t_afko-t_affl = t_affl[].
t_afko-t_afab = t_afab[].
APPEND t_afko.
IF jstk_x = cloi_x.
 t_objnr-objnr = ioheader-objnr.
 APPEND t_objnr.
ENDIF.
*---> Remember the orders that are already selected for the global
 selection parameters
IF ordtomem = cloi_x. "write order numbers to memory
 t_aufnr_range_done-sign = 'I'.
 t_aufnr_range_done-option = 'NE'.
 t_aufnr_range_done-low = ioheader-aufpl.
 APPEND t_aufnr_range_done.
ENDIF.
*---> Remember the orders internal/external keys for AFAB (relationship)
IF afab_x = cloi_x.
 MOVE-CORRESPONDING ioheader TO t_aufpl_aufnr.
 APPEND t_aufpl_aufnr.
ENDIF.
check afpo_x = cloi_x.
GET ioitem.
BEGIN OF INSERTION DS001
Check whether the process order has been changed since the last
run of the program
CLEAR F_CONTINUE.
if the CHANGED date is greater than the last run or initial
IF IOHEADER-AEDAT GT F_OLD_DATE OR
 ( ioheader-aedat is initial and
 ioheader-aezeit is initial ).
if the CHANGED date is initial check the creation date
 if ioheader-aedat is initial.
if the creation date is greater than or equal to the date of the last
run, if it is equal the creation time must be later or equal to the
start time of the last run
 IF IOHEADER-ERDAT GT F_OLD_DATE OR
 ( IOHEADER-ERDAT EQ F_OLD_DATE AND
 IOHEADER-ERFZEIT GE F_OLD_TIME ).
 f_continue = 'X'.
 endif.
 else.
 f_continue = 'X'.
 endif.
if the CHANGED date is not initial check it against the last run
ELSEIF IOHEADER-AEDAT EQ F_OLD_DATE AND
 IOHEADER-AEZEIT GE F_OLD_TIME.
 f_continue ='X'.
endif.
Aenderung 295/99 Selektions-Aenderung vom 26. August 99
Wenn Auftrag bereits techn. abgeschlossen ist, so darf kein IDOC
erzeugt werden, wenn Auftrag zum löschen vorgemerkt wird.
CONCATENATE 'OR' IOHEADER-AUFNR INTO F_OBJNR.
SELECT SINGLE * FROM JEST
 WHERE OBJNR = F_OBJNR
 AND STAT = 'I0045'.
IF JEST-INACT EQ SPACE AND SY-SUBRC EQ 0.
 SELECT * FROM JCDS WHERE OBJNR EQ F_OBJNR AND
 STAT EQ 'I0045' AND
 INACT EQ SPACE.
letzte Aenderung des Status TABG wird geprueft
 ENDSELECT.
IF ( F_OLD_DATE GT JCDS-UDATE OR " Beg JB_02
 ( F_OLD_DATE EQ JCDS-UDATE AND
 F_OLD_TIME GT JCDS-UTIME ) ) AND " End JB_02
 SY-SUBRC EQ 0.
 CLEAR F_CONTINUE.
 ENDIF.
ENDIF.
Ende 295/99
check f_continue eq 'X'.
END OF INSERTION DS001
IF afpo_x = cloi_x.
 MOVE-CORRESPONDING ioitem TO t_afpo.
 APPEND t_afpo.
ENDIF.
Put matnr and ltrmi in a help structure, which later goes to t_afpo
IF ioitem-posnr = '0001'.
 MOVE-CORRESPONDING ioitem TO help_afpo.
 APPEND help_afpo.
put PSP element (internal key) into order header. Unique for positions
 IF t_afko-pspel IS INITIAL.
 t_afko-pspel = ioitem-projn.
 ENDIF.
ENDIF.
CHECK affl_x = cloi_x.
GET iosequen.
CLEAR t_afvo. REFRESH t_afvo.
MOVE-CORRESPONDING iosequen TO t_affl.
GET iosequen LATE.
t_affl-t_afvo = t_afvo[].
APPEND t_affl.
CHECK afvo_x = cloi_x.
GET iooper.
CLEAR t_kbed. REFRESH t_kbed.
CLEAR t_afuv. REFRESH t_afuv.
CLEAR t_resb. REFRESH t_resb.
MOVE-CORRESPONDING iooper TO t_afvo.
"Temporary storing of operation information if for a phase
"the corresponding operation has is needed
MOVE-CORRESPONDING iooper TO t_aufpl_aplzl_vornr.
APPEND t_aufpl_aplzl_vornr.
check, if selection profile (if exists) for the operation is ok
IF NOT ord_opr_selid IS INITIAL.
 CALL FUNCTION 'STATUS_CHECK_BY_SELSCHEM'
 EXPORTING
 objnr = iooper-objnr
 selid = ord_opr_selid
 IMPORTING
 fullfill = status_ok
 EXCEPTIONS
 no_stat_tab = 1
 no_stat_scheme = 2
 OTHERS = 3.
 IF sy-subrc <> 0.
 status_ok = cloi_x.
 ENDIF.
ELSE.
 status_ok = cloi_x.
ENDIF.
check if control key (STEUS) should not be selected.
control_key_ok = cloi_x.
IF no_entry_for_logsys IS INITIAL.
 READ TABLE t_steus WITH KEY
 steus = iooper-steus BINARY SEARCH.
 IF sy-subrc <> 0.
 CLEAR control_key_ok.
 ENDIF.
ENDIF.
CHECK NOT status_ok IS INITIAL.
CHECK NOT control_key_ok IS INITIAL.
GET iooper LATE.
t_afvo-t_kbed = t_kbed[].
t_afvo-t_afuv = t_afuv[].
t_afvo-t_resb = t_resb[].
APPEND t_afvo.
IF jstv_x = cloi_x.
 t_objnr-objnr = iooper-objnr.
 APPEND t_objnr.
ENDIF.
CHECK kbed_x = cloi_x.
GET ioopcap.
MOVE-CORRESPONDING ioopcap TO t_kbed.
APPEND t_kbed.
CHECK resb_x = cloi_x.
GET ioopcomp.
do not transfer RESB entries with deletion flag
CHECK ioopcomp-xloek IS INITIAL.
MOVE-CORRESPONDING ioopcomp TO t_resb.
APPEND t_resb.
CHECK afuv_x = cloi_x.
GET iosoper.
CLEAR t_kbeu. REFRESH t_kbeu.
MOVE-CORRESPONDING iosoper TO t_afuv.
check if control key (STEUS) should not be selected.
control_key_ok = cloi_x.
IF no_entry_for_logsys IS INITIAL.
 READ TABLE t_steus WITH KEY
 steus = iooper-steus BINARY SEARCH.
 IF sy-subrc <> 0.
 CLEAR control_key_ok.
 ENDIF.
ENDIF.
CHECK NOT control_key_ok IS INITIAL.
GET iosoper LATE.
t_afuv-t_kbeu = t_kbeu[].
APPEND t_afuv.
IF jstv_x = cloi_x.
 t_objnr-objnr = iosoper-objnr.
 APPEND t_objnr.
ENDIF.
CHECK kbeu_x = cloi_x.
GET iosocap.
MOVE-CORRESPONDING iosocap TO t_kbeu.
APPEND t_kbeu.
*& Event END-OF-SELECTION
END-OF-SELECTION.
*MOD-006
DATA: itab_matnr TYPE zzzz_xref_data OCCURS 0.
DATA: l_wa_matnr TYPE zzzz_xref_data.
DATA: l_wa_matnr_value TYPE zzzz_xref_data-z_in_value.
DATA: l_wa_afko TYPE cloi_afko_struct.
SELECT *
FROM zzzz_xref_data
APPENDING TABLE itab_matnr
WHERE trans_id = 'ZELCUSMATLOOKUP' AND
 ( z_in_value IN s_matnr OR
 z_out_value IN s_matnr ).
IF sy-subrc = 0.
 LOOP AT ITAB_MATNR INTO L_WA_MATNR.
 L_WA_MATNR_VALUE = L_WA_MATNR-z_OUT_VALUE.
 S_MATNR-LOW = L_WA_MATNR_VALUE.
 S_MATNR-SIGN = 'I'.
 S_MATNR-OPTION = 'EQ'.
 APPEND S_MATNR.
 ENDLOOP.
 DELETE itab_matnr WHERE NOT in_value IN s_emat.
 SORT itab_matnr BY out_value.
ENDIF.
CLEAR: l_wa_matnr.
**MOD-010
Data which is not in the material lookup table but in the T_AFKO.
LOOP AT t_afko INTO l_wa_afko.
 READ TABLE S_MATNR WITH KEY LOW = L_WA_AFKO-MATNR BINARY SEARCH.
 READ TABLE itab_matnr INTO l_wa_matnr
 WITH KEY z_out_value = l_wa_afko-matnr BINARY SEARCH.
 IF sy-subrc NE 0.
 l_wa_afko-rgekz = 'X'.
 MODIFY t_afko FROM l_wa_afko TRANSPORTING rgekz.
 ENDIF.
 IF NOT P_DATE IS INITIAL.
 IF T_AFKO-GSTRP < p_date OR
 ( T_AFKO-GSTRP = p_date AND
 T_AFKO-GSUZP > p_time ).
 L_WA_AFKO-RGEKZ = 'X'.
 MODIFY T_AFKO FROM L_WA_AFKO TRANSPORTING RGEKZ.
 ENDIF.
 ENDIF.
ENDLOOP.
Delete Data which is not in the material lookup
table but in the T_AFKO.
DELETE t_afko WHERE rgekz = 'X'.
*MOD-010
*MOD-006
BEGIN OF INSERTION DS001
DATA: l_wa_itab_date TYPE ty_date.
Check whether the process order has been changed since the last
run of the program
CLEAR f_continue.
IF NOT t_afko IS INITIAL.
 SELECT aufnr aedat aezeit erdat erfzeit loekz
 INTO TABLE itab_date
 FROM aufk
 FOR ALL ENTRIES IN t_afko
 WHERE aufnr = t_afko-aufnr.
 IF sy-subrc = 0.
 IF NOT p_date IS INITIAL.
 CLEAR: itab_date.
Check whether the process order has been changed since the last
run of the program
 LOOP AT itab_date INTO l_wa_itab_date.
if the CHANGED date is greater than the last run or initial
 IF l_wa_itab_date-aedat GT p_date OR
 ( l_wa_itab_date-aedat IS INITIAL AND
 l_wa_itab_date-aezeit IS INITIAL ).
if the CHANGED date is initial check the creation date
 IF l_wa_itab_date-aedat IS INITIAL.
if the creation date is greater than or equal to the date of the last
run, if it is equal the creation time must be later or equal to the
start time of the last run
 IF l_wa_itab_date-erdat GT p_date OR
 ( l_wa_itab_date-erdat EQ p_date AND
 l_wa_itab_date-erfzeit GE p_time ).
 f_continue = 'X'.
 ELSE.
 l_wa_itab_date-indicator = 'X'.
 MODIFY itab_date FROM l_wa_itab_date TRANSPORTING indicator.
 ENDIF.
 ELSE.
 f_continue = 'X'.
 ENDIF.
if the CHANGED dat is not initial check it against the last run
 ELSEIF l_wa_itab_date-aedat EQ p_date AND
 l_wa_itab_date-aezeit GE p_time.
 f_continue ='X'.
 ELSE.
 l_wa_itab_date-indicator = 'X'.
 MODIFY itab_date FROM l_wa_itab_date TRANSPORTING indicator.
 ENDIF.
 ENDLOOP.
*MOD-006
ELSE.
 CLEAR: ITAB_DATE.
 LOOP AT ITAB_DATE INTO L_WA_ITAB_DATE.
if the CHANGED date is greater than the last run or initial
 IF L_WA_ITAB_DATE-AEDAT GT P_RUNDT OR
 ( L_WA_ITAB_DATE-aedat is initial and
 L_WA_ITAB_DATE-aezeit is initial ).
if the CHANGED date is initial check the creation date
 if l_wa_itab_date-aedat is initial.
if the creation date is greater than or equal to the date of the last
run, if it is equal the creation time must be later or equal to the
start time of the last run
 IF L_WA_ITAB_DATE-ERDAT GT P_RUNDT OR
 ( L_WA_ITAB_DATE-ERDAT EQ P_RUNDT AND
 L_WA_ITAB_DATE-ERFZEIT GE S_RUNTM-LOW OR
 L_WA_ITAB_DATE-ERFZEIT LE S_RUNTM-HIGH ).
 f_continue = 'X'.
 else.
 l_wa_itab_date-indicator = 'X'.
 MODIFY ITAB_DATE FROM L_WA_ITAB_DATE
 TRANSPORTING INDICATOR.
 endif.
 else.
 f_continue = 'X'.
 endif.
if the CHANGED dat is not initial check it against the last run
 ELSEIF L_WA_ITAB_DATE-AEDAT EQ P_RUNDT AND
 L_WA_ITAB_DATE-AEZEIT GE S_RUNTM-LOW.
 f_continue ='X'.
 ELSE.
 l_wa_itab_date-indicator = 'X'.
 MODIFY ITAB_DATE FROM L_WA_ITAB_DATE
 TRANSPORTING INDICATOR.
 endif.
 ENDLOOP.
*MOD-006
 ENDIF.
 ENDIF.
ENDIF.
DELETE ITAB_DATE WHERE INDICATOR = 'X'.
*MOD-006
CLEAR: itab_date.
IF s_rundt-high IS INITIAL AND NOT s_rundt IS INITIAL.
 s_rundt-high = sy-datum.
ENDIF.
LOOP AT itab_date INTO l_wa_itab_date.
 IF NOT s_rundt IS INITIAL.
if the CHANGED date is greater than the last run or initial
 IF ( l_wa_itab_date-aedat IS INITIAL AND
 l_wa_itab_date-aezeit IS INITIAL ).
if the CHANGED date is initial check the creation date
 IF l_wa_itab_date-aedat IS INITIAL.
if the creation date is greater than or equal to the date of the last
run, if it is equal the creation time must be later or equal to the
start time of the last run
 IF ( l_wa_itab_date-erdat GT s_rundt-low AND
 l_wa_itab_date-erfzeit GT s_runtm-low ) AND
 ( l_wa_itab_date-erdat LT s_rundt-high AND
 l_wa_itab_date-erfzeit LT s_runtm-high ).
 f_continue = 'X'.
 ELSE.
 l_wa_itab_date-indicator = 'X'.
 MODIFY itab_date FROM l_wa_itab_date
 TRANSPORTING indicator.
 ENDIF.
 ELSE.
 f_continue = 'X'.
 ENDIF.
if the CHANGED dat is not initial check it against the last run
 ELSEIF ( l_wa_itab_date-aedat GE s_rundt-low AND
 l_wa_itab_date-aezeit GE s_runtm-low ) AND
 ( l_wa_itab_date-aedat LE s_rundt-high AND
 l_wa_itab_date-aezeit LE s_runtm-high ).
 f_continue ='X'.
 ELSE.
 l_wa_itab_date-indicator = 'X'.
 MODIFY itab_date FROM l_wa_itab_date
 TRANSPORTING indicator.
 ENDIF.
 ENDIF.
ENDLOOP.
DELETE itab_date WHERE indicator = 'X'.
*MOD-006
**MOD-006
LOOP AT t_afko INTO l_wa_afko.
 READ TABLE itab_date INTO l_wa_itab_date
 WITH KEY aufnr = l_wa_afko-aufnr BINARY SEARCH.
 IF sy-subrc NE 0.
 l_wa_afko-rgekz = 'X'.
 MODIFY t_afko FROM l_wa_afko TRANSPORTING rgekz.
 ENDIF.
ENDLOOP.
DELETE t_afko WHERE rgekz = 'X'.
**MOD-006
-> initialize logical data base to reduce memory consumption
PERFORM ldb_process_init(sapdbioc)
 CHANGING
 lv_subrc.
--> add information to the order structure that is not
 selected via logical database:
 - if AFVO-entry is a phase (phflg) --> fill field for
 corresponding operation number (PVZNR)
 The internal node number (aplzl) of the corresponding operation
 is in field PVZKN of the phase
 - relationship information: E1AFABL
 especially: select external numbers for the used
 internal numbers in the table AFAB
 - status information of the order header: E1JSTKL
 - status information of the operation: E1JSTVL
--> Put matnr and ltrmi in the table t_afko
SORT t_afko BY aufnr.
LOOP AT help_afpo.
 READ TABLE t_afko WITH KEY aufnr = help_afpo-aufnr
 ASSIGNING -gltri = help_afpo-ltrmi.
 ENDIF.
ENDLOOP.
--> Select entries for order and operation status
IF NOT t_objnr[] IS INITIAL.
 SELECT objnr stat FROM jest INTO TABLE t_jest2
 FOR ALL ENTRIES IN t_objnr
 WHERE objnr = t_objnr-objnr
 AND inact <> 'X'.
ENDIF.
--> Select entries for relationships from afab for all orders
 into table t_afab_tmp
SORT t_aufpl_aplzl_vornr BY aufpl aplzl.
IF afab_x = cloi_x AND NOT t_aufpl_aufnr[] IS INITIAL.
-> select afab data
 SELECT * FROM afab INTO TABLE t_afab_tmp
 FOR ALL ENTRIES IN t_aufpl_aufnr
 WHERE aufpl_vor = t_aufpl_aufnr-aufpl.
 SELECT * FROM afab APPENDING TABLE t_afab_tmp
 FOR ALL ENTRIES IN t_aufpl_aufnr
 WHERE aufpl_nch = t_aufpl_aufnr-aufpl.
 SORT t_afab_tmp
 BY aufpl_vor aplzl_vor aufpl_nch aplzl_nch aobar mimax.
 DELETE ADJACENT DUPLICATES FROM t_afab_tmp
 COMPARING aufpl_vor aplzl_vor aufpl_nch aplzl_nch aobar mimax.
-> read external order numbers out of data base
 CLEAR t_aufpl. REFRESH t_aufpl.
 LOOP AT t_afab_tmp ASSIGNING -aufpl_nch.
 COLLECT t_aufpl.
 ENDLOOP.
 CLEAR t_aufpl_aufnr. REFRESH t_aufpl_aufnr.
 IF NOT t_aufpl[] IS INITIAL.
 SELECT aufpl aufnr FROM afko INTO TABLE t_aufpl_aufnr
 FOR ALL ENTRIES IN t_aufpl
 WHERE aufpl = t_aufpl-aufpl.
 SORT t_aufpl_aufnr BY aufpl.
 ENDIF.
-> add order numbers to afab data
 LOOP AT t_afab_tmp ASSIGNING -aufnr_nch = t_aufpl_aufnr-aufnr.
 ENDIF.
 ENDLOOP.
-> read operation numbers out of data base
 CLEAR t_aufpl_aplzl. REFRESH t_aufpl_aplzl.
 LOOP AT t_afab_tmp ASSIGNING -aplzl_nch.
 COLLECT t_aufpl_aplzl.
 ENDLOOP.
 IF NOT t_aufpl_aplzl[] IS INITIAL.
 SELECT aufpl aplzl vornr FROM afvc
 APPENDING TABLE t_aufpl_aplzl_vornr
 FOR ALL ENTRIES IN t_aufpl_aplzl
 WHERE aufpl = t_aufpl_aplzl-aufpl
 AND aplzl = t_aufpl_aplzl-aplzl.
 SORT t_aufpl_aplzl_vornr BY aufpl aplzl.
 ENDIF.
-> add operation numbers to afab data
 LOOP AT t_afab_tmp ASSIGNING -vornr_nch = t_aufpl_aplzl_vornr-vornr.
 ENDIF.
 ENDLOOP.
ENDIF. "afab_x
--> fill AFAB (relationship information) and status information
SORT t_aufpl_aufnr BY aufnr.
LOOP AT t_afko ASSIGNING .
-> fill order head status information
 IF jstk_x = cloi_x.
 CLEAR t_jstk. REFRESH t_jstk.
 LOOP AT t_jest2 INTO wa_tjest2 WHERE objnr = -t_jstk = t_jstk[].
 ENDIF.
-> fill afab information
 IF afab_x = cloi_x.
 CLEAR t_aufpl_aufnr.
 READ TABLE t_aufpl_aufnr WITH KEY
 aufnr = -t_afab = t_afab[].
 ENDIF.
-> fill operation and suboperation status information
 IF jstv_x = cloi_x OR afvo_x = cloi_x.
 LOOP AT .
 -> read status information of suboperation
 IF jstu_x = cloi_x.
 LOOP AT -t_jstu = t_jstu[].
 ENDLOOP.
 ENDIF.
 -> read status information of operation
 IF jstv_x = cloi_x.
 CLEAR t_jstv. REFRESH t_jstv.
 LOOP AT t_jest2 INTO wa_tjest2 WHERE objnr = -t_jstv = t_jstv[].
 ENDIF.
 -> Read operation for a phase
 IF NOT -pvznr = t_aufpl_aplzl_vornr-vornr.
 ENDIF.
 ENDIF.
 ENDLOOP.
 ENDLOOP.
 ENDIF.
-> collect order numbers
 CLEAR wa_aufnrdone.
 wa_aufnrdone-low = -aufnr.
 APPEND wa_aufnrdone TO lt_aufnrdone.
ENDLOOP.
-> append collected order numbers to global table
APPEND LINES OF lt_aufnrdone TO gt_aufnrdone.
EXPORT gt_aufnrdone TO MEMORY ID 'LOIAUFNRTAB'.
-> free large tables
CLEAR t_jest2. REFRESH t_jest2.
CLEAR t_afab_tmp. REFRESH t_afab_tmp.
CLEAR t_aufpl. REFRESH t_aufpl.
CLEAR t_aufpl_aufnr. REFRESH t_aufpl_aufnr.
CLEAR t_aufpl_aplzl. REFRESH t_aufpl_aplzl.
CLEAR t_aufpl_aplzl_vornr. REFRESH t_aufpl_aplzl_vornr.
-> create idocs
CALL FUNCTION 'CLOI_MASTERIDOC_CREATE_LOIPRO'
 EXPORTING
 opt_sys = opt_sys
 message_type = mestyp
 TABLES
 order_data = t_afko
 EXCEPTIONS
 OTHERS = 1.
-> export already selected order numbers via ranges tab to memory
EXPORT t_aufnr_range_done TO MEMORY ID 'LOI002'.
**MOD-006
IMPORT created_masteridocs_pro FROM MEMORY ID 'YLOI001'.
ycloidownlprot-end_date = sy-datum.
ycloidownlprot-end_time = sy-uzeit.
ycloidownlprot-idocs_selected = created_masteridocs_pro.
ycloidownlprot-in_progress = cloi_false.
insert or update entry (dependant if entry already exists)
MODIFY ycloidownlprot.
COMMIT WORK.
MESSAGE i967(z001) WITH created_masteridocs_pro.
**MOD-006
Update last run date and time
IF p_update = 'X'.
 PERFORM update_last_run.
ELSE.
MESSAGE s000 WITH text-022.
 "Last Run Date and Last Run Time not updated
 LEAVE LIST-PROCESSING.
ENDIF.
INCLUDE rcordf01.
*& Form validate_last_run_date_time
 text
--> p1 text
<-- p2 text
*FORM validate_last_run_date_time.
IF p_date IS INITIAL OR
 p_time IS INITIAL.
 IF sy-batch IS INITIAL.
 MESSAGE s000 WITH text-017.
 "Last Run date & Last Run Time can not be blank
 LEAVE LIST-PROCESSING.
 ELSE.
 MESSAGE e000 WITH text-017.
 "Last Run date & Last Run Time can not be blank
 ENDIF.
ENDIF.
*ENDFORM. " validate_last_run_date_time
*& Form update_last_run
 text
--> p1 text
<-- p2 text
FORM update_last_run.
CONSTANTS:
 l_c_name TYPE rvari_vnam VALUE 'Z_PROC_DATE',
 l_c_name1 TYPE rvari_vnam VALUE 'Z_PROC_TIME',
 l_c_type TYPE rsscr_kind VALUE 'P',
 l_c_numb TYPE tvarv_numb VALUE '0000'.
Update last run date
UPDATE tvarv SET low = sy-datum
 WHERE name = l_c_name AND
 type = l_c_type AND
 numb = l_c_numb.
IF sy-subrc = 0.
 COMMIT WORK.
ELSE.
 ROLLBACK WORK.
 g_run_date = text-015. "#EC
 "Updation of TVARV table failed for ZLAST_RUN_DATE. Update manually
ENDIF.
Update last run time
UPDATE tvarv SET low = sy-uzeit
 WHERE name = l_c_name1 AND
 type = l_c_type AND
 numb = l_c_numb.
IF sy-subrc = 0.
 COMMIT WORK.
ELSE.
 ROLLBACK WORK.
 g_run_time = text-016. "#EC
 "Updation of TVARV table failed for ZLAST_RUN_TIME. Update manually
ENDIF.
ENDFORM. " update_last_run

Requesting all to help me how to create lsmw using idoc method

hi
thanx for ur answer
requesting every body in the forum to help me how to create lsmw using idoc method.
regards,
balaji

Hi Balaji,
LSMW using IDOC is similar to using flat file method. Here you are getting data from IDOC container and mapping data with Idoc segments insted of flatfile column.
Hope this is what you are looking for. If helpful then dont forget to reward me for that
Darshan

How to use LSMW on CRM for bulk master data creation?

Hello Experts,
I need your help to able to use LSMW on CRM for bulk master data creation. Below is described my detailed requirement; -
We have CRM 2007 integrated with SAP ISU (ECC6.0). As per business process all Business Master Data (BP details, Business Agreement details etc) and Technical Master Data (Connection Object, PoD etc.) is created in CRM and then it is replicated in ISU. We are going to start Assembly Test soon. Now we need to have all master data in place. Tool we want to use is LSMW.
Now can you help me right from scratch on how to use LSMW for bulk master data creation in CRM?
Please give me documents / links etc that is relevant.
Regards,
Rohit

Hi,
I have looked into your query.
These are some information which might be useful to you.
What is LSMW?
Legacy System Migration Workbench or LSMW is SAP standard program that can be used to easily load / change master data or transactions in SAP without any programming at all. It can be used to upload data at cutover, such as: open orders, contracts, materials, vendors, stock on hand. It can also be used in a production system to make changes to existing data. Very limited authorization checks are available on the transaction, so the use of it must be very well controlled.
One input file can be used to create all the views of the material master. For all the material types. Even if different views and fields are used for the different materials.
Steps to take
1. Create text file with data to be loaded
2. Set up and run LSMW
The following link will provide good information on LSMW Idoc method:
[http://help.sap.com/saphelp_nw04/helpdata/en/ad/2d54a41d7011d2b42e006094b944c8/frameset.htm]
I hope this helps.
Regards,
Venkat

How to use pkmc by using lsmw

I have many items their location need to be changed from one to another ,and qty is also need to be changed if needed,so I want to using the automatic method -lsmw, but when I have recorded the steps and save the table to excel version at step 3,it only includes some fields as blow
TABNAME          CHAR     30
TCODE          CHAR     20
WERKS          CHAR     4
PRVBE          CHAR     10
BEHMG          QUAN     17
but as you know ,I at least need the art.no field and two PRVBE to let me input two different locations,
so who knows how to get this table includes GS_SEARCH-VALUE(the art.no),two RMPKR-PRVBE(two supply areas)
or who knows how to using this automatic method to let me change location and qty by batch?
and I also find one BDC_OKCODE is ccy_dbcl ,I think it means double click the art.no to move to the next view,but later when i execute this lsmw program, no action happened except I double-click this art.no manually,why?
how to record the action of double-click in view SAPLMPK_CCY_UI 0110
Thanks in advances
Helai
Message was edited by:
        lai he

still want to get answer
Thanks,
helai

Explain how to use standard LSMW for MM01

Can anyone explain how to use standard LSMW for MM01 Tcode.pls explain briefly.

Hi
Create a project using 0020 as method.
Max

How to use segment ZCRMXIF_PARTNER_SAVE01 in LSMW to Generate/Change BP data using IDOC

Similar Messages

Maybe you are looking for