How to Map IDOC Extensions in LSMW

HI,
I am working on a conversion for uploading material master using IDOC Method, There is an extension in the IDOC can anyone tell me how to map the extensions in the LSMW.
ADVANCE Thanks
Guhapriyan Subrahmanyam

Hi guhapriyan,
if you have any extension associated with MATMAS then it will display when you press F4 on extension, form the list you can choose the extension.
and proceed ....
the extension is for custom fields ,for this you need extend the idoc. if you add the extension to it, in lsmw extension you can see them...
Regards
vijay

Similar Messages

How to map Idoc fields with external file

Hi All,
How to map Idoc fields with external file.
I want to check the settings where Idoc fields are mapped with external file.
Thanks in advance.
Regards,
Govind.

If you have configured a fileport where on trigger of IDOC you are creating the file, you can look at the message type documentation and get the offset values for each field in each segment

How to map idoc segment field E1IDB02-FIIKONTO with BSEG-ESRNR.

Hi,
I have searched for lot of threads in the forum , and also i tried myself but i am not able to map this fields segment with my logic, so please anyone kindly contribute in mapping idoc segment field with the logic given below:
idoc type :PAYEXT outbound idoc.
message type: PEXR2002
This is my logic: i need to populate the ISR number(BSEG-ESRNR ) in idoc segment field( E1IDB02-FIIKONTO)
DATA : str1 TYPE string,
      len1 TYPE i,
      len2 TYPE i,
      str2 TYPE string,
      str3 TYPE string.
str1 = '01-1234-4'. ---> BSEG-ESRNR "ISR Subscriber Number
REPLACE FIRST OCCURRENCE OF '-' IN str1 WITH '_'.
REPLACE ALL OCCURRENCES OF '-' IN str1 WITH space.
CONDENSE str1.
len1 = STRLEN( str1 ).
IF len1 LT '9'.
len2 = '9' - len1.
CASE len2.
   WHEN '1'.
     REPLACE ALL OCCURRENCES OF '_' IN str1 WITH '00'.
   WHEN '2'.
     REPLACE ALL OCCURRENCES OF '_' IN str1 WITH '000'.
   WHEN '3'.
     REPLACE ALL OCCURRENCES OF '_' IN str1 WITH '0000'.
   WHEN '4'.
     REPLACE ALL OCCURRENCES OF '_' IN str1 WITH '000000'.
   WHEN OTHERS.
ENDCASE.
ELSEIF len1 EQ '9'.
REPLACE ALL OCCURRENCES OF '_' IN str1 WITH '0'.
ELSEIF len1 GT '9'.
REPLACE ALL OCCURRENCES OF '_' IN str1 WITH space.
CONDENSE str1.
ENDIF.
Thanks in Advance.

Resolved.

HOW TO MAP IDOC TO XML

Hi,
I need to map IDOC to xml but the problem is I have 400 fields in IDOC which are to be mapped to 20 elements in XML.
As it a tedious process to go to 400 fields for each xml element.Is their any better way to find correct field in IDOC with very minial time rather going 400 fields for each xml element.
thanks
sreeram

hi,
>>1)Even SAP it self does not encourage to use ABAP >>MAPPING and
i dont know where you have read this, but ABAP mapping is one of the most popular/ most efficient and highly recomended by SAP. I have used it in tons of places.
>>2)More over Iam not ABAP resource.
you could also do a java mapping.
there is no other easy way if you are not doing abap/java mapping. you are then left with the only option of using the graphical editor.
cheers,
Naveen
Message was edited by: Naveen Pandrangi

How to Map Idoc-Orders05 Qualifier permitted values to a flat file Str

Hi All,
My scenario is IDoc-xi-flat file. I have a problem in mapping the respective qualifier value in IDoc to the flat file structure. I am using the function fix values in Message Mapping. Suggest how should the target field should look like to map to the qualifier.
Thanks
Gowri K.

hi,
can you tell a little bit more on what are you trying to achive?
do you only need one qualifier in file or all or what?
can you use the same structure as in IDOC ?
be a little more precise
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

How to map idoc segments to multiple output structures

Dear experts,
On Pi I need to map segments from an Idoc to 2 different outputstructures. My scenario is as follows:
incoming Idoc on PI -> if segment eq 'X' then map to outputstructure '1'; if segment eq 'Y' then map to outputstructure '2'
Idoc structure is as follows:
- 1 header segment
- 1..n detail segments (which I need to map to outputstructure 1)
- 1 summarisation segment (which I need to map to outputstructure 2)
Output needs to be a .txt file.
I would like to use the graphical message mapping on PI, how can I map the Idoc to multiple output structures?
Thanks in advance,
William

Hi
You can do 1:n multimapping
in message mapping in messages tab ..add both the structures in target tab and do the mapping
and in operation mapping add both the message interface on the target side
PLease go through this blog
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible

How to map IDoc segment with qualifiers

Hi everyone!
I have the following problem: In an IDoc of type DESADV01 there can be several segments of type E2EDS01. Each segment has a different qualifier, which is the value of the field SUMID in this case. My target structure (type EDIFACT) now has several segments, each again with a sort of qualifier. Now I have to map the values of certain source segments to the respective target segments.
Exaple (in XML format):
Source
<E1EDS01 SEGMENT="1">
 <SUMID>021</SUMID>
 <SUMME>0000000001.000</SUMME>
 <SUNIT>KGM</SUNIT>
</E1EDS01>
<E1EDS01 SEGMENT="1">
 <SUMID>022</SUMID>
 <SUMME>0000000001.000</SUMME>
 <SUNIT>KGM</SUNIT>
</E1EDS01>
Target
<S_MEA>
 <C_C502>
 <D_6313>N</D_6313>
 </C_C502>
 <C_C174>
 <D_6411>KGM</D_6411>
 <D_6314>1</D_6314>
 </C_C174>
</S_MEA>
<S_MEA>
 <C_C502>
 <D_6313>G</D_6313>
 </C_C502>
 <C_C174>
 <D_6411>KGM</D_6411>
 <D_6314>1</D_6314>
 </C_C174>
</S_MEA>
(i have omitted several details here, but I'm only interested in the general procedure anyway).
So in general the source segment with qualifier "021" should be mapped to a target structure with qualifier "N" etc.
How can this be done using standard XI mapping techniques?
Regards, Joerg

Hi everyone!
Thanks for your input data - unfortunately this wasn't quite what I was looking for. However I thik I solved my original problem and I just wanted to share this solution with you - maybe it helps others, maybe some of you have suggestions what I could do differently.
To sum up the requirement: There can be multiple input segments, each with a certain qualifier. These input segments have to be mapped to the target segments, respectively - however, the qualifiers change. There can be several segments with qualifiers that do not match the requirement, and required segments might be missing.
So here's what I came up with:
Use the qualifier of the source segments as an input to a FixValues function. In this function, map the desired qualifiers to the value true, use false as the default value. Map the output of the FixValues function to a createIf function and use this to create the desired output segment. This way, for each of the required segments, one target segment will be created. All other segments (with unwanted qualifiers) will be removed.
So far, this technique worked for me - do you have improvements/suggestions?
Regards, Joerg

LSMW - ME21 How to map multiple line items

Hi all,
I am using LSMW tool with batch input recording technique to create POs via ME21. I have defined source structures as HEAD with POSI as its subordianted structure. This settings worked perfectly for one single item line. However, it created a new transaction for each line item in the file. I did some searches in this forum and I noticed that someone suggested to dynamically set the line positon at the processing points. I tried a few times and could not get it work. Anyone knows how to map multiple items in LSMW, please help.
Here is part of my recording:
EKPO-EMATN(01)                 000995NM
EKPO-MENGE(01)                                 1      RM06E-EEIND(01)                2006.04.27             EKPO-NETPR(01)                             10         EKPO-WERKS(01)                 0001                   EKPO-LGORT(01)                 0001
My input file looks like this:
H 77777400 NB2006.05.140001001T
L000995NM00000000052006.05.15         1000010001CAON
L000998NM00000000052006.05.15         1000010001CAON
H 77777400 NB2006.05.140001001T
L000995NM00000000052006.05.15         1000010001CAON
Thanks!

Hi
If you have used a b.i. recording, all abap code is inserted in std table /SAPDMC/LSGBDC.
The program to generate the B.I. session is automatically created when you run "Create Batch Input Session" step.
What means the numbers of items you can insert depend on the totals of items you have used while creating your b.i. recording:
If you have simulated to insert only one item, you'll be able to insert only one item in your project.
So you should simulate to insert severals items not only one, but I think it should be better you use a std method to create PO by LSMW:
- Std B.I: object 0085, method 0001 (RM06EEI0);
- BAPI   : object BUS2012, method CREATEFROMDATA1
Max

How to create an extension for generated type idoc

Hi all,
Can u please look into this
How to create an extension for generated type idoc ? for example Idoc type BATMAS02

Enter transaction WE30 (ALE->Extension-> IDOC types->Maintain Idoc type)
- Type in your name of the extended IDOC type (usually starting with 'Z') and click on the Basic IDoc type, click the create icon.
- Click on Create new and enter a description and press enter.
- Click on ZIDOCTYPE01 and then on the Create icon.
- Enter ZIDOCTYPE as the segment type, click on Segment Editor.
- Enter a description for your segment type and create.
- Enter a description for your segment, enter each field required in your IDoc and press enter to validate.
- Save and generate, press back
- To release the segment choose Goto, Release from the menu.
- Check the box on the line of your segment.
- Save, back and enter.
- Your Idoc type structure should be displayed with your new segment.
- Save and back.
- To release the Idoc type choose Extras, Release type from the menu and Yes.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
1. The point in the ALE function module where the function exit occurs
2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
regards,
srinivas

How to resolve error while importing data using IDoc method in LSMW ?

Hi
I am trying to import my data using IDoc method in LSMW.
But after completing the whole LSMW process, when I look into the IDOC generated, the error description is as this.
It talks about the process code and other stuff.
Function module not allowed : APPL_IDOC_INPUTI
Message No. B1252
Diagnosis :
The function module APPL_IDOC_INPUTI and the application object type which were determined are not valid for this IDoc.
I am not able to resolve the problem.
Please help.
Regards,
Rachesh Nambiar

check the below link.
/people/stephen.johannes/blog/2005/08/18/external-data-loads-for-crm-40-using-xif-adapter

How to convert IDOC-PI-JMS to IDOC-PI-File with exsting mapping?

I have a scenario, ECC-PI-Message broker. ECC sending IDOC to PI, PI execute mapping and sends data to Message borker(thru JMS channel).(with almost one to one mapping)., IDOC(AAE)-PI-JMS. Now my requirement is., from PI after mapping we need to create file with same data what ever send to Message broker and put the file in SAP folder without touching mapping. Is it possible? Please advise with the steps. We are using the ICO for this senario. Quick response is appriciated.

Hello,
U can add one more receiver for file and reuse the same message mapping
Thanks
Amit Srivastava

How to use mapviewer extension for jdevelop?

I am working on the mapviewer. But my problem is that I can not connect mapviewer, or I can not start mapviewer using the embedded oc4j by jdeveloper. In mapviewer faq I read that:
"How do I view the mapping metadata through JDeveloper's Connections Navigator?
We have developed an Oracle JDeveloper extension that lets you browse the available list of styles, themes and basemaps defined in a datasource through JDeveloper's Connections Navigator. To do this, you will first need to download the mvconnection.jar file from OTN's MapViewer site. This jar contains the code that defines a MapViewer connection type for JDeveloper. To install, simply drop this jar file to the JDeveloper extension directory, normally $JDEV_HOME/jdev/lib/ext. Then restart JDeveloper, and you are all set.
But when I restart jdeveloper, I got the message:
"H:\Programme\jdev\jdev\lib\ext\mvpalette.jar!\META-INF\jdev-ext.xml
Error: jar:file:/H:/Programme/jdev/jdev/lib/ext/mvpalette.jar!/META-INF/jdev-ext.xml<Line 105, Column 18>: XSD-2021: (Error) Element not completed: 'jsplibrary'
H:\Programme\jdev\jdev\lib\ext\mvconnection.jar!\META-INF\jdev-ext.xml
Error: jar:file:/H:/Programme/jdev/jdev/lib/ext/mvconnection.jar!/META-INF/jdev-ext.xml<Line 25, Column 20>: XSD-2034: (Error) Element 'description' not expected.
Error: jar:file:/H:/Programme/jdev/jdev/lib/ext/mvconnection.jar!/META-INF/jdev-ext.xml<Line 26, Column 13>: XSD-2034: (Error) Element 'help' not expected.
I use Jdeveloper 10g. Have you ever met the same problem?
Thanks in advance

The Map Viewer extension is still not available for JDeveloper 10g. It works with JDeveloper 9.
The Mapping group is currently working on an upgrade.

How to map journal fields and whats is the better process type

/Journal/JournalSuspenseCostCentre     NULL
/Journal/JournalBalancingCentre     Lookup from Organisation ID
/Journal/JournalMultiCompany     u2018Nu2019
/Journal/JournalBatchNumber     NULL
/Journal/JournalNumTransactions     Total number of /Journal/JournalLine transactions
/Journal/JournalBaseDRTotal     Sum of /Journal/JournalLine/JournalLineBaseValue u2013 Debit Values only
/Journal/JournalBaseCRTotal     Sum of /Journal/JournalLine/JournalLineBaseValue u2013 Credit Values only
How to map journal fields and whats is the better process type idoc/proxies?please let me know
Journal Line
Multiple journal lines per header:
Schema Element     Data
/Journal/JournalLine/JournalLineCostCentre     Bank account control Cost Centre
/Journal/JournalLine/JournalLineAccount     Bank account control Account Code
/Journal/JournalLine/JournalLineMoneyTotal     Transaction Line Amount
/Journal/JournalLine/JournalLineVolume     NULL
/Journal/JournalLine/JournalLineDescription     Payee Name
/Journal/JournalLine/JournalLineChequeBookReference     NULL
/Journal/JournalLine/JournalLineMatchField     Cheque Number
NB Contra accounting entries should be posted to:
Schema Element     Data
/Journal/JournalLine/JournalLineCostCentre     Bank account control Cost Centre
/Journal/JournalLine/JournalLineAccount     Bank account control Account Code
/Journal/JournalLine/JournalLineMoneyTotal     Transaction Line Amount * -1
/Journal/JournalLine/JournalLineDescription     Payee Name
/Journal/JournalLine/JournalLineMatchField     Cheque Number
/Journal/JournalPeriod     Current General Ledger Period
/Journal/JournalYear     Current General Ledger Year

It looks you are new to PI,
you have to develop scenario end to end, by creating source data type and target data type(if you have XSD's not required),then use Graphical mapping (message mapping) to map source and target structures.
Search in sdn for one end to end scenario you will understand easily
Regards,
Raj

Mapping IDoc to File Doubt

Hello!!
I have send the IDoc CHRMAS.CHRMAS04 from my R/3 to another system via file adapter.
My problem is I have to pass several fields of the idoc to a complex structure on the XML with the structure:
<ITEM>
 <FIELDNAME>Weight</FIELDNAME>
 <FIELDVALUE>17.0 </FIELDVALUE>
</ITEM>
<ITEM>
 <FIELDNAME>Colour</FIELDNAME>
 <FIELDVALUE>Blue</FIELDVALUE>
</ITEM>
Somebody knows how to map for each segement of the IDoc an ITEM substructure?
I hope will be clear enough.
Thanks and regards,
Manuel.

And in which way is this workflow related?
Regards,
Martin

Problem with mapping [Idoc to EDI]

Hi experts,
i am facing a new problem in my mapping (idoc to edi scenario)
my target is as follow:
InvoiceDME
>Invoice 1..1
>>InvoiceHeader 1..1
>>>IncotermsCode 1..1
My Idoc is as follow:
IDOC
>E1EDK17 0..20
>>QUALF
>>LKOND
>>LKTEXT
There can be 2 scenarios in my source:
1st:
IDOC
>E1EDK17
>>QUALF = 001
>>LKOND = lkond001
>>LKTEXT
2nd:
IDOC
>E1EDK17
>>QUALF = 001
>>LKOND = lkond001
>>LKTEXT
>E1EDK17
>>QUALF = 002
>>LKOND = lkond002
>>LKTEXT = lktext002
If QUALF=002 then I have to take both values of LKOND and LKTEXT and map them to incotermcode
else if qualf=001 alone, then map LKOND to incotermcode
my mapping is as follow:
http://www.flickr.com/photos/30317046@N05/2862446903/
as you can see, the problem is if i am in my second scenario, i get the wrong value in incotercode (lkond001 instead of the concatenate of LKOND and LKTEXT for QUALF = 002)
Do you have any idea how I can solve this??
Thanks a lot,
Regards,
Jamal

Actually i used java mapping:
 //write your code here
try
 String returnString = "";
 for (int i = 0; i < QUALF.length; i++)
 if (("002".equals(QUALF.trim())))
 returnString = returnString +" "+ LKOND +" "+ LKTEXT;
 result.addValue(returnString);
catch(Exception e)
 e.printStackTrace();
and the condition on the 'count' of QUALF (if = 2 then else)
Thanks,
Regards,
Jamal

How to Map IDOC Extensions in LSMW

Similar Messages

Maybe you are looking for