Creating a Material with different values for fields in Transaction MM01

Hello All,
While creating a material i will be giving a Profit Center in Sales:general/plant view, which i can see in Costing1 View. If i change this in this View it automatically changes in the other View. Is there any way to give different values in the two views or then what is the significance in showing the same field again in two different views.
Thanks,
Shashidhar.

Hi,
Its just a way of showing the data in different views for user. It doesn't have any significance.
Regards,
Sudheer.

Similar Messages

How can I create a hashmap() with multiple values for the same key?

I am trying to write an application that will us something like a Map() with multiple values but some have the same key. Is this possible?

i had the same question. just create a List, add all the values u want to it, and then put the List into the map like u would a normal single value. e.g.
List list = new ArrayList();
list.add(value1);
list.add(value2);
map.put(key, list);
i bet u r doing the same course as i am =)

Possible to create a form with different options for different items?

So I want to create a form in DW but the problem is that I have 3 items....and I want different form subjects for each item? Is there a way to do this so that if select item #1 that 1 set of options comes up....if I select item #2 a different set of options etc.??
thanks much!

Another simple example that you can style up.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Untitled Document</title>
<script src="http://code.jquery.com/jquery-1.10.2.min.js"></script>
<script>
$(document).ready(function() {
$('#option_2, #option_3').hide();
$('#selectOption_1').click(function() {
$('#option_1').show();
$('#option_2, #option_3').hide();
$('#selectOption_2').click(function() {
$('#option_2').show();
$('#option_1, #option_3').hide();
$('#selectOption_3').click(function() {
$('#option_3').show();
$('#option_1, #option_2').hide();
</script>
</head>
<body>
<form>
<select>
<option id="selectOption_1" value="option_1">Option 1</option>
<option id="selectOption_2" value="option_2">Option 2</option>
<option id="selectOption_3" value="option_3">Option 3</option>
</select>
<div id="option_1">
<select>
<option value="option_1_1">Option 1_1</option>
<option value="option_1_2">Option 1_2</option>
<option value="option_1_3">Option 1_3</option>
</select>
</div>
<div id="option_2">
<select>
<option value="option_2_1">Option 2_1</option>
<option value="option_2_2">Option 2_2</option>
<option value="option_2_3">Option 2_3</option>
</select>
</div>
<div id="option_3">
<select>
<option value="option_3_1">Option 3_1</option>
<option value="option_3_2">Option 3_2</option>
<option value="option_3_3">Option 3_3</option>
</select>
</div>
</form>
</body>
</html>

Is it possible to create a PDF with different colors for screen and printing?

I'm working on a document that features light colored text on a dark background. I'll be sending this document as a PDF to someone who will likely want to print it. Is it possible to set up the document such that it will display this way when viewed on screen, but will print as black text on a white background, without requiring any special action on the part of the recipient?
Printing a color separation of just the text color produces exactly the results I'm after, but I can't ask the recipient to do that. I need it to happen automatically any time it's printed.
I've tried setting up a duplicate text layer in black and placing it under the background layer, then setting the background layer and colored text to 'never print'. This works within Acrobat Pro, but not when I print the same document from Preview.
Is there an acrobat equivalent of a CSS print stylesheet?
Thanks.

Create the document in layers with the background on a seperate layer than the text. Export the PDF with"Create Acrobat Layers" selected (it will need to be at least version 1.5).
Open the PDF in Acrobat, choose the background layer then Options>Properties>Initial State and under "print" choose "Never prints".

Same Material with different itemcatagory groups

We have 3rd party manufacturers that make product for company and sometimes they send the finished product back to company and other times they will drop ship it to one of our customers.
this scenario we need to have the same material with different itemcatagory groups
i tried to create same material with different storage locations, but it's possible but the thing is when i change the item catagory group for the material , the same is applicable for 2nd same material, my requirement is i need 2 different itemcatagory for the same material, hope u understand my requirement
i will be expecting your possible replys.
Thanks & Regards
Venkat.Dhanemkula

Hi Venkat..
Please explain it more clear manner..
With whatever i have understand, i think you scenerio is manual 3rd party order processing.
In that case the material that you normally deliver yourself but occasionally need to order from a third-party vendor, you can overwrite the item category during sales order processing.
Keep only one material and specify the item category group NORM in the material master.
If, as an exception, you use a third-party material, change the entry TAN to TAS in the ItCa field when processing the sales document. The item is then processed as third-party item.
hope it helps you.
Regards
Harry

Mass changes of Material Master field with different values

Hi,
How to change a field in Material Master for more than thousand materials. I think MM17 can only be used for mass changes of materials with same values. I need to upload different values for different materials. Is there any other way to do this.
Thanks,
K R Vishnu Kumar

Hi Kumar.
I think you have to use LSMW for mass updation for Material Master fields with different values.
Regards,
Rahul.

User Created in OIM 11.1.1.5 with null value for mandatory field.

Hi,
We had updated one UDF as mandatory field on OIM user form. We can see the * in front of that field. Now if we create the user using web console (Using UI), we are not able to create the user without giving some value in that UDF as it is mandatory. However if we created the user with UDF value as null using Trusted recon, User sucessfully created in OIM. I had attached the screen shot for that user which create in OIM with UDF value as null.
Is any thing else also need to do to make UDF as mandatory field.
Regards,
Sid

I am not sure this is a bug. Such mandatory checks will often only apply to administrative changes from the GUI. You may not always be able to enforce the same quality of data in reconciled data as you wish to impose for changes made through OIM, and it may prove an issue in some cases if such users could not be reconciled. In this case the use will go into OIM, but you will be forced to populate a value in the mandatory field if you later try to update them in OIM.

PDF for multiple users with different values

Is there a way to create a PDF to be sent to multiple users but have different values in the PDF? For expample employee A's offer letter is for $50/hour while employee B's offer letter is for $55/hour. But they have the same offer letter just with different values.
I have Enterprise EchoSign and FormsCentral.
Thank you!

Hi,
Thanks for asking, but FormsCentral currently does not support this.
Perry

Issue with Negative Value for Total valuated stock 0VALSTCKQTY.

Hi Experts,
we loaded the Cube with datasources 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM.
We mapped the quanity field from 2LIS_03_BF in transformation either into Key figures "Quantity issued from valuated stock" (0ISSVALSTCK) or "Quantity received into valuated stock" (0RECVALSTCK ) of the cube.
For obtaining the Total Valuated stock, we used the Key figure 0VALSTCKQTY. This key figure is having the Inflow and Out flow values as 0RECVALSTCK and 0ISSVALSTCK. When i tried to check the content of 0VALSTCKQTY, the key figure 0VALSTCKQTY is not present in the infoCube content. I understood that the value for this key figure would be calculated at the time of query execution with the formula
{ Last obtained Valuated stock + (Received Valuated Stock u2013 Issued Valuated Stock ) }.
The issue is the first records in the query is obtained with negative value for the total valuated stock 0VALSTCKQTY even though the values of Received Valuated Stock and Issued Valuated Stock are with Zero. Could any one please help me on how the first record in the query is with a negative value eventhough the inflow and out flow fields of it are with Zero.
Many Thanks in advance.
Jeswanth

Hi Srini,
I observed an interresting reason for the stock being with negative in the first record.
Issue : While executing the BEx report, we have the first record with a negative value.
Let me explain with an example
Material : XYZ
Plant      : A
Date of Stock Initialization for data source 2LIS_03_BX -
> 12th April 2009.
So on 12 Th April 2009 consider that we have a stock in store with a value of 2640.
Then we have loaded wih Data source 2LIS_03_BF for all Historic Movement types.
At the time of query execution we will have the first record with a negative of available stock present on the day of initialization .
So, as we have initilized the data source 2LIS_03_BX on 12 th April 2009, we have at that time a stock of 2640 in availability.
Exactly with the same value of 2640, we are having a negative value i.e. -2640.
and also one more point to be noted is ...as we have initialized the data source 2LIS_03_BX on 12 th APril 2009...it has created a
opening balance of 2640 on the day of initiailization i.e on 12 th April 2009 in infocube....(which is an extra record...)...so if the previous record of 12,04,2009 is having some value in it..then it will get added to 2640 EA..which will give incorrect stock
So in the query the records will appear in the below following manner
Calendar Day     Total stock                                                                Received stock                                          Issued Stock
28.12.2005 ---> - 2640 EA
29.12.2005 --->    2000 EA                                                                       640 EA                                                        0
10.04.2009 --->      0                                                                                0                                                               2000 EA
11.04.2009 -
>    0                                                                                0                                                                0
                             (For making
                              the earlier record of initilization to 0 a negative value -2640 EA is created in the first record )
12.04.2009 (Initializtion day) ---> 2640 EA                                                 0                                                                0
13.04.2009
the day before initialization the total stock will be 0 due to the negative effect introduced by the first record and from the day of initialization the records will be the accurate values... On 12 th april 2009 we can see that a stock of 2640 is brought into the total stock. In fact if there is no negative value i.e. -2640 in the first record then ...the value on 11.04.2009 will be 2640 Ea and this will get summed up with the Opening balance of 2640 EA created by 2LIS_03_BX on the day of intitialization. So on 12 .04. 2009 the total stock will be shown as 5280 EA...so in order to prevent the double value only we observed that the first record is created with the negative of available stock present on the initialization ...to make the record before the day of initialization i.e. 11.04.2009...to be 0...so that from 12 th April 2009 ..will start to see the actual total stock in the query result...
This is happening only if we use both the data sources 2LIS_03_BX and 2LIS_03_BF for loading into BW.....
If we load alone by 2LIS_03_BF ...then as 2LIS_03_BX is ruled out in the loading...then no negative of available stock will be created ...because there will be bno opening balance created on the day of initialization.....and the opeing balance available will be flowing into consecutive records due to the movement types and 12 th April 2009 will be shown with avaialable total stock of 2640 EA.
Kindly let us know your opinions on this...
Thanks.
regards,
Jeswanth

FLEET Table, Possible Values For Field IS SI UNIT

Dear experts,
While doing analysis on fleet data I realized that for field IS_SI_UNIT (PM: Vehicle Data in SI Unit (e.g. Dimensions)) in table FLEET in two separate systems we have vehicle records set with different entries for this field.
In one system vehicles are stored with value F: DB Unit set individually (new)
and in other one with value Y: DB Unit set through (new)
Systems are SAP ECC 6.0
Does anyone know what does it mean and what influence this has? In both systems vehicles are created by end users using standard PM creation transaction and those indicators are set in background while equipment is saved so there is not influence by end user.
I could not find much information on SAP support portal about meaning behind possible values for field IS_SI_UNIT in table FLEET so was wondering if anyone knows more here?
Thanks,
Ivo

Dear,
There will not be any impact.Finally system will consider only SI units for fleet equipment consumption calculation.
Kindly read note:366733 - Equipment/fleet: SI units in table FLEET and 372736 - Equipmt/vehicle:rounding error because of SI units
It may help you.
But in my system i can view only "Y"
Regards,
Pardhu

Creating a material with just the basic view using BAPI

Hi
   I intend to create a new material with just the basic view using BAPI BAPI_MATERIAL_SAVEDATA -
To do this - I believe I have to fill in the structure HEADDATA data - ( mandatory ) with the required values - I fill values for fields IND_SECTOR, MATL_TYPE & basic view ( check this field ) and leave the MATERIAL field as blank (assuming internal numbering ) and then fill values of the CLIENTDATA structure with values for the basic data view.
Is this correct ? Will my material number created be returned in the RETURN structure - how do I look for the material number exclusively in my RETURN structure ?

hi
good
go through this progarm which ll give you detail idea about BAPI_MATERIAL_SAVEDATA
REPORT ZBAPIMM01 LINE-SIZE 255 NO STANDARD PAGE HEADING
                 LINE-COUNT 065(001).
TABLES: T001L, "Storage Locations
        MARA, "General Material Data
        MAKT, "Material Descriptions
        MBEW, "Material Valuation
        MARC. "Plant Data for Material
DATA: BAPI_HEAD   LIKE BAPIMATHEAD,
      BAPI_MAKT   LIKE BAPI_MAKT,    "Material Description
      BAPI_MARA1 LIKE BAPI_MARA,    "Client Data
      BAPI_MARAX LIKE BAPI_MARAX,
      BAPI_MARC1 LIKE BAPI_MARC,    "Plant View
      BAPI_MARCX LIKE BAPI_MARCX,
      BAPI_MBEW1 LIKE BAPI_MBEW,    "Accounting View
      BAPI_MBEWX LIKE BAPI_MBEWX,
      BAPI_RETURN LIKE BAPIRET2.
DATA: BEGIN OF INT_MAKT OCCURS 100.
        INCLUDE STRUCTURE BAPI_MAKT.
DATA: END OF INT_MAKT.
DATA: BEGIN OF INT_MAT OCCURS 100,
         WERKS(4),     "Plant
         MTART(4),     "Material type
         MATNR(18),    "Material number
         MATKL(9) ,    "Material group
         MBRSH(1),     "Industry sector
         MEINS(3),     "Base unit of measure
         GEWEI(3),     "Weight Unit
         SPART(2),     "Division
         EKGRP(3),     "Purchasing group
         VPRSV(1),     "Price control indicator
         STPRS(12),    "Standard price
         PEINH(3),     "Price unit
         SPRAS(2),     "Language key
         MAKTX(40),     "Material description
       END OF INT_MAT.
SELECT-OPTIONS:
            PLANT    FOR MARC-WERKS OBLIGATORY MEMORY ID PLT,
            MATERIAL FOR MARA-MATNR MEMORY ID MAT,
            MATLTYPE FOR MARA-MTART MEMORY ID MTY,
            DIVISION FOR MARA-SPART MEMORY ID DIV.
PARAMETERS: F_FILE LIKE RLGRAP-FILENAME
             DEFAULT 'C:\DATA\ZMATERIAL.XLS' MEMORY ID F_FILE,
             GETDATA AS CHECKBOX, "Tick to download materials data to local harddisk
             UPDDATA AS CHECKBOX. "Tick to update date to Materials Master
IF GETDATA = 'X'.
   PERFORM DOWNLOAD_DATA.
   PERFORM DOWNLOAD_FILE.
ENDIF.
IF UPDDATA = 'X'.
   PERFORM UPLOAD_FILE.
   PERFORM UPDATE_MM.
ENDIF.
FORM DOWNLOAD_DATA.
SELECT * FROM MARC WHERE LVORM EQ ' '
                      AND WERKS IN PLANT
                      AND MATNR IN MATERIAL.
    CLEAR MARA.
    SELECT SINGLE * FROM MARA WHERE MATNR = MARC-MATNR.
    CHECK MATLTYPE.
    CHECK DIVISION.
    CLEAR MBEW.
    SELECT SINGLE * FROM MBEW WHERE MATNR = MARC-MATNR
                                AND BWKEY = MARC-WERKS.
    CLEAR MAKT.
    SELECT SINGLE * FROM MAKT WHERE SPRAS = 'EN'
                                AND MATNR = MARC-MATNR.
    WRITE:/ MARC-WERKS,    "Plant
            MARA-MTART,    "Material type
            MARA-MATNR,    "Material number
            MARA-MATKL,    "Material group
            MARA-MBRSH,    "Industry sector
            MARA-MEINS,    "Base unit of measure
            MARA-GEWEI,    "Weight Unit
            MARA-SPART,    "Division
            MARC-EKGRP,    "Purchasing group
            MBEW-VPRSV,    "Price control indicator
            MBEW-STPRS,    "Standard price
            MBEW-PEINH,    "Price unit
            MAKT-SPRAS,    "Language key
            MAKT-MAKTX.    "Material description
            INT_MAT-WERKS = MARC-WERKS.    "Plant
            INT_MAT-MTART = MARA-MTART.    "Material type
            INT_MAT-MATNR = MARA-MATNR.    "Material number
            INT_MAT-MATKL = MARA-MATKL.    "Material group
            INT_MAT-MBRSH = MARA-MBRSH.    "Industry sector
            INT_MAT-MEINS = MARA-MEINS.    "Base unit of measure
            INT_MAT-GEWEI = MARA-GEWEI.    "Weight Unit
            INT_MAT-SPART = MARA-SPART.    "Division
            INT_MAT-EKGRP = MARC-EKGRP.    "Purchasing group
            INT_MAT-VPRSV = MBEW-VPRSV.    "Price control indicator
            INT_MAT-STPRS = MBEW-STPRS.    "Standard price
            INT_MAT-PEINH = MBEW-PEINH.    "Price unit
            INT_MAT-SPRAS = MAKT-SPRAS.    "Language key
            INT_MAT-MAKTX = MAKT-MAKTX.    "Material description
            APPEND INT_MAT.
            CLEAR INT_MAT.
ENDSELECT.
ENDFORM.
FORM DOWNLOAD_FILE.
call function 'WS_DOWNLOAD'
EXPORTING
    FILENAME                      = F_FILE
    FILETYPE                      = 'DAT'
FILETYPE                      = 'WK1'
tables
    data_tab                      = INT_MAT
EXCEPTIONS
    FILE_OPEN_ERROR               = 1
    FILE_WRITE_ERROR              = 2
    INVALID_FILESIZE              = 3
    INVALID_TYPE                  = 4
    NO_BATCH                      = 5
    UNKNOWN_ERROR                 = 6
    INVALID_TABLE_WIDTH           = 7
    GUI_REFUSE_FILETRANSFER       = 8
    CUSTOMER_ERROR                = 9
    OTHERS                        = 10.
IF SY-SUBRC = 0.
   FORMAT COLOR COL_GROUP.
   WRITE:/ 'Data Download Successfully to your local harddisk'.
   SKIP.
ENDIF.
ENDFORM.
FORM UPLOAD_FILE.
call function 'WS_UPLOAD'
EXPORTING
    FILENAME                      = F_FILE
    FILETYPE                      = 'DAT'
FILETYPE                      = 'WK1'
tables
    data_tab                      = INT_MAT
EXCEPTIONS
    FILE_OPEN_ERROR               = 1
    FILE_WRITE_ERROR              = 2
    INVALID_FILESIZE              = 3
    INVALID_TYPE                  = 4
    NO_BATCH                      = 5
    UNKNOWN_ERROR                 = 6
    INVALID_TABLE_WIDTH           = 7
    GUI_REFUSE_FILETRANSFER       = 8
    CUSTOMER_ERROR                = 9
    OTHERS                        = 10.
IF SY-SUBRC = 0.
   FORMAT COLOR COL_GROUP.
   WRITE:/ 'Data Upload Successfully from your local harddisk'.
   SKIP.
ENDIF.
ENDFORM.
FORM UPDATE_MM.
LOOP AT INT_MAT.
Header
    BAPI_HEAD-MATERIAL        = INT_MAT-MATNR.
    BAPI_HEAD-IND_SECTOR      = INT_MAT-MBRSH.
    BAPI_HEAD-MATL_TYPE       = INT_MAT-MTART.
    BAPI_HEAD-BASIC_VIEW      = 'X'.
    BAPI_HEAD-PURCHASE_VIEW   = 'X'.
    BAPI_HEAD-ACCOUNT_VIEW    = 'X'.
Material Description
    REFRESH INT_MAKT.
    INT_MAKT-LANGU           = INT_MAT-SPRAS.
    INT_MAKT-MATL_DESC       = INT_MAT-MAKTX.
    APPEND INT_MAKT.
Client Data - Basic
    BAPI_MARA1-MATL_GROUP     = INT_MAT-MATKL.
    BAPI_MARA1-BASE_UOM       = INT_MAT-MEINS.
    BAPI_MARA1-UNIT_OF_WT     = INT_MAT-GEWEI.
    BAPI_MARA1-DIVISION       = INT_MAT-SPART.
    BAPI_MARAX-MATL_GROUP = 'X'.
    BAPI_MARAX-BASE_UOM   = 'X'.
    BAPI_MARAX-UNIT_OF_WT = 'X'.
    BAPI_MARAX-DIVISION   = 'X'.
Plant - Purchasing
    BAPI_MARC1-PLANT      = INT_MAT-WERKS.
    BAPI_MARC1-PUR_GROUP = INT_MAT-EKGRP.
    BAPI_MARCX-PLANT      = INT_MAT-WERKS.
    BAPI_MARCX-PUR_GROUP = 'X'.
Accounting
    BAPI_MBEW1-VAL_AREA   = INT_MAT-WERKS.
    BAPI_MBEW1-PRICE_CTRL = INT_MAT-VPRSV.
    BAPI_MBEW1-STD_PRICE = INT_MAT-STPRS.
    BAPI_MBEW1-PRICE_UNIT = INT_MAT-PEINH.
    BAPI_MBEWX-VAL_AREA   = INT_MAT-WERKS.
    BAPI_MBEWX-PRICE_CTRL = 'X'.
    BAPI_MBEWX-STD_PRICE = 'X'.
    BAPI_MBEWX-PRICE_UNIT = 'X'.
    WRITE:/ BAPI_HEAD, BAPI_MARC1.
    call function 'BAPI_MATERIAL_SAVEDATA'
      exporting
        HEADDATA                   = BAPI_HEAD
        CLIENTDATA                 = BAPI_MARA1
        CLIENTDATAX                = BAPI_MARAX
        PLANTDATA                  = BAPI_MARC1
        PLANTDATAX                 = BAPI_MARCX
      FORECASTPARAMETERS         =
      FORECASTPARAMETERSX        =
      PLANNINGDATA               =
      PLANNINGDATAX              =
      STORAGELOCATIONDATA        =
      STORAGELOCATIONDATAX       =
        VALUATIONDATA              = BAPI_MBEW1
        VALUATIONDATAX             = BAPI_MBEWX
      WAREHOUSENUMBERDATA        =
      WAREHOUSENUMBERDATAX       =
      SALESDATA                  = BAPI_MVKE1
      SALESDATAX                 = BAPI_MVKEX
      STORAGETYPEDATA            =
      STORAGETYPEDATAX           =
      IMPORTING
        RETURN                     = BAPI_RETURN
      TABLES
        MATERIALDESCRIPTION        = INT_MAKT
      UNITSOFMEASURE             =
      UNITSOFMEASUREX            =
      INTERNATIONALARTNOS        =
      MATERIALLONGTEXT           =
      TAXCLASSIFICATIONS         =
      RETURNMESSAGES             =
      PRTDATA                    =
      PRTDATAX                   =
      EXTENSIONIN                =
      EXTENSIONINX               =
IF BAPI_RETURN-TYPE = 'E'.
   WRITE:/ 'Error Message ', BAPI_RETURN.
ENDIF.
ENDLOOP.
ENDFORM.
*---End of Program
thanks
mrutyun^

SDIMA: Values for field SUPP_EXIST in condition table CNCCRMPRCUS801 differ

Hi Experts,
when checking condition records consistency between CRM and ERP via transacation SDIMA we get the following error for one of the conditon records: 'Values for field SUPP_EXIST in condition table CNCCRMPRCUS801 differ'. Can anybody explain to me where this message could come from? To my understanding field 'SUPP_EXIST' only exists in CRM condition tables for technical reason. So no way to compare this against an ERP condition table field, is there?
And related to this: I found that this error message is triggered from method CL_CND_DIMA_CRM->COMPARE_MBDOC. As the DIMA-Compare is triggered asynchronously and just setting a break-point is no option therefore, I was wondering if anybody knows a way of debugging this method in order to find out what the coding does in detail before the message is thrown.
Thanks a lot for your help!
Cheers,
Jens

Hi Brian and the other Experts,
thanks for your help. Unfortunately, I don't have a single record with this problem but a lot more. So it is not possible to correct this manually. Also, I would not know how to correct this anyhow as I don't understand what field in R/3 should map to field SUPP_EXIST in CRM condition tables. Let me explain:
From my understanding, in CRM (leave aside scales) we have two database tables for each condition table, a central and a supplemental table. A condition record always creates a data record in the central table and nothing is inserted in the supplemental table in case that the fields form the supplemental table are not needed. However, when there are less common condition features involved (e.g. uppler limits), then an additional data record will be created in the supplemental table with the relevant data. And this is when field SUPP_EXIST comes into play as it is an indicator for the system that a data record exists for that condition record also in the supplemental table.
The condition record data model in R/3 is completely different. For CRM condition table CNCCRMPRCUS801 the following tables in R/3 are involved: A801, KONH and KONP. And there is a data record for each of them for a given condition record. There is no concept of having a supplemental table as far as I understand it so where exactly would I find this SUPP_EXIST in R/3 so that I can make sure it does not deviate from the data in CRM?
Would be great if someone could give me another hint. What am I getting wrong?
Cheers,
Jens

Column with dropdown with different values in each cell

Hello,
I have a Table and one of the columns contains a dropdown list (dropdownbykey). My problem is that the list of values for each drop down element is different because it depends on the value in the rest of the row cells. Obviously I need to calculate the values dynamically at runtime.
I have created a context node and linked it to the table columns, one of the attributes in the node is linked to the 'selectedKey' property of the dropdown. Then in my code I try to give the list of values to this attribute using the method set_attribute_value_set from the if_wd_context_node_info interface. The process it's explained in the DEMO_UIEL_STD_SELECTION component.
But I only get the same values for each row.
I would like to know if it's possible to have dropdowns with different values in the same column of a Table, and if so any indication of how to do that.
Best regards,

Hello Javier,
unfortunately you cannot use dropdown by key if you want to have different dropdowns per line of your table.
Instead you will need to use dropdown by index, and bind your dropdown to a subnode of the table element (ensure that this is a non-singleton node).
To make life easier for yourself, I would also have an attribute in your main structure that holds the selected value of the dropdown by index - update this value on any "onSelect" action of the dropdown by index.
e.g. for a table that holds addresses:
Context Node Address:
attribute street
attribute city
attribute country
attribute region
subnode regionlist
...attribute regionkey
...attribute region_text
table - bound to node address
input field bound to street
input field bound to city
dropdown by key bound to country (onSelect event populates subnode regionlist)
dropdown by index bound to subnode regionlist, text bound to region text, (onSelect event populates address element attribute region with key field of selected element).
I hope this helps,
Chris

How to populate SNDPRN with different values in Development and Production?

Hello experts,
I have to fill the field SNDPRN in the message mapping with a different value in Development and in Production. As I am new to PI, I used a simple solution - but it is rather ugly: I set a constant value in the mapping in development and a different one in Production. However, I would like to know if there is any solution to have a condition in the mapping like:
IF system is Development, set SNDPRN as Constant1.
IF system is Production, set SNDPRN as Constant2.
(And eventually IF system is Test, set SNDPRN as Constant3)
Thanks in advance for your help,
Luis

Hi Luis,
      You can go with the parameterized mapping , where you can provide different values for SNDPRN in interface determination for development and production.
      At point of time if you want to change the values it requires only a change in the configuration.
      Please refer the below links for reference;
Parameterized Mapping Programs - Enterprise Services Repository - SAP Library
http://scn.sap.com/people/jin.shin/blog/2008/02/14/sap-pi-71-mapping-enhancements-series-parameterized-message-mappings
     We are following the same approach for some of our interfaces.
- Muru

Is it possible to create a Synonym with different column names

Hi,
I want to create a Synonym with different columns names (Columns not in original table) . I am not sure if this can be done . Any suggessions...
Thanks in advance....

Synonyms are not limited to tables. Accroding to the SQL Reference, a synonym is:
an alternative name for a table, view, sequence, procedure, stored function, package, materialized view, Java class schema object, user-defined object type, or another synonym.
In fact, synonyms are not even validated until they are used:
SQL> create synonym my_synonym for table_which_does_not_exist;
Synonym created
SQL> select * from my_synonym;
select * from my_synonym
ORA-00980: synonym translation is no longer valid

Creating a Material with different values for fields in Transaction MM01

Similar Messages

Maybe you are looking for