Partial field value comparison

Hi ,
I have a small but tricky requirement ...atleast for me ...
I have a table called ABCD in that table have field called WBS which is having data format as 1234560000.01.02
but in my project internal table got PROJECT which will be data format as just 1234560000 so i want to get data from ABCD table based on comparison of PROJECT with WBS ...and i need to use the "for all entries option" here to populate the RESULT_PACKAGE
select * from ABCD into corresponding fields of table
RESULT_PACKAGE
for all entries in itab_docitem where WBS =itab_doc-PROJECT
and objvers = 'A'.
So just want to use similar to above statement in my start routine but only problem is WBS has to compared partially only...
So can any one pls help me to get this ...
Thanks & Regards,
BRK

Hi,
You cant compare pattern with the all entires in addin. you need to go for all entries with select.
The abap statement for select to get pattern is as below:
select * from ABCD into table itab where wbs = '10004566%'.
You have to work with this statement or rewrite the logic, there is no possibility of pattern check with all entries in.
Regds,
Shashank

Similar Messages

Can file name get from partial field value ?

Hi, Friend:
I have file receiver with FCC, I used variable substitution (I have to use this rather than dynamic configuration, since there are multiple files created by multi-mapping), so the file name is pass via payload to adapter.
In advanced tab, we can assigned to a variable like: payload:MT_XXXX,1,Filename,1
Now I do not want full value of Filename, I just need part of the value of it.
I will not consider an option of create another field to store part of the value, since after FCC, a blank line is created which is not acceptable by our integration partner.
Is there any way to get it ?
Thanks
Liang

Kevin:
If you can see from what Madhusudana Reddy suggested:
I created a node, saying "Tail" in end of structure, add one child node to it saying "Filename"
Now in my mapping program, I can pass real file name I wanted to child node "Filename"
In Variable substitution, I get the whole value of the node "Filename" when we naming the created file.
In FCC, I used Madhusudana suggested, it would not created blank line when using Tail.endSeparator '0'
Hope this give you some hints
@Carlos:
Java Mapping is different approach which we do not want to go at this stage.
Regars
Liang

Reference field value in the F110 Payment document

Dears
We are running the automatic payment run for the vendor invoices posted.
In each vendor invoice, we have filled the reference field, text field, etc. However, while running the payment in F110, the system does not reproduce this reference field value in the payment document. Hence we are not able to match the items for comparison.
Have we left out any setting in FBZP or somewhere ?

Hello,
Apart from above suggestions, you can check linked invoices to payment document through below option.
Open payment document in FB03, go to Menu->Environment->Payment usage
This will list all invoices cleared through that payment document.
If you are looking for tables, Pass payment document number , company code, year, account type and account to AGKO table and get the clearing date. Pass these details to BSAK and get list of cleared documents.
AUGDT = Clearing date from AGKO
AUGBL= Clearing document from AGKO
and other details passed earlier.
Hope this helps.
Thanks,
V V

Value Mapping - Partial Hierarchy values in MDM

Hello Experts,
I have a scenario where the Material Number has partial Hierarchy filed value maintained e.g: if the actual Hierrachy lookup has 4 levels of hierarchy maintained and if the Material being imprted has Product Hierarchy value set only upto 2 levels, this raises a concern.
Even though the data is imported successfully, MDM creates a duplicate value(upto 2nd level) in the Hierarchy lookup table and automatically maps the incoming Product hierarchy field value (of Material) to this duplicate leaf element craeted.
Is there a solution to handle such a scenario?
Kindly advice,
Thaks in advance,
Elizabeth.

Hi Elizabeth
Materials need to be assigned to the final leaf node and MDM does not allow assignment of parent nodes to records.
If this the requirement you can also introduce a Lookup table storing all the hierachy nodes with Descriptions and assign the parent nodes with blank hierachy. Once full hierachy is known the lookup value as well as hierarchy value can be updated.
thanks
Ravi

Deleting a Date/Fields value

Hi I'm developing a XDP Form to be depolyed under XHTML, and I cannot find a way to clear a Date/Time Fields current value using Javascript.
I've tried fieldname.rawValue = "", fieldname.value = "", and fieldname.formattedValue = "", and = null for all properties mentioned. These do seem to visually remove the date's value (or put the string "null"), However when a server side script tries to read the value (should be empty) from the date/time field it still returns the original date value.
I've also tried combinations of xfa.host.resetData(), which only partially works if the date field had an original value of empty not if it was populated with a value, plus it seems to clear all the other fields on the form which is not desireable.
Is there any way to delete the Date/time fields value client side?
Any ideas would be greatly appreciated?

No attachment appears on this end ....can you mail it to [email protected]
Thanks
Paul

Re:invalid partial field access: negative offset

Hi,
       iam getting error invalid partial field access: negative offset, what is this mean

negative off set not allowed
Access Using Offset and Length Specifications
Offset and length specifications are generally critical since the length of each character is platform-dependent. As a result, it is initially unclear as to whether the byte unit or the character unit is referred to in mixed structures. This forced us to put in place certain considerable restrictions. However, access using offset or length specifications is still possible to the degree described in the following. The tasks subject to this rule include accessing single fields and structures, passing parameters to subroutines and working with field symbols.
Single field access
Offset- or length-based access is supported for character-type single fields, strings and single fields of types X and XSTRING. For character-type fields and fields of type STRING, offset and length are interpreted on a character-by-character basis. Only for types X and XSTRING, the values for offset and length are interpreted in bytes.
Structure access
Offset- or length-based access to structured fields is a programming technique that should be avoided. This access type results in errors if both character and non-character-type components exist in the area identified by offset and length.
Offset- or length-based access to structures is only permitted in a UP if the structures are flat and the offset/length specification includes only character-type fields from the beginning of the structure. The example below shows a structure with character-type and non-character-type fields. Its definition in the ABAP program and the resulting assignment in the main memory is as follows:
BEGIN OF STRUC,
a(3) TYPE C,   "Length: 3 characters
b(4) TYPE N,   "Length: 4 characters
c     TYPE D,   "Length: 8 characters
d     TYPE T,   "Length: 6 characters
e     TYPE F,   "Length: 8 bytes
f(26) TYPE C,   "Length: 28 characters
g(4) TYPE X,   "Length: 2 bytes
END OF STRUC.
Internally, the fragment view contains four fragments. Offset- or length-based access in this case is only possible in the first fragment. Statements like struc(21) or struc7(14) are accepted by the ABAP interpreter and treated like a single field of type C. By contrast, struc57(2) access is now only allowed in an NUP. If offset-/length-based access to a structure is permitted, both the offset and length specifications are generally interpreted as characters in a UP.
Passing parameters to subroutines
Up to now, parameter passing with PERFORM has allowed you to use cross-field offset and length specifications. In future, this will no longer be allowed in a UP. In a UP, offset and length-based access beyond field boundaries returns a syntax or runtime error. For example, access types c15 or c5(10) would trigger such an error for a ten-digit C field c.
If only an offset but no length is specified for a parameter, the entire length of the field instead of the remaining length was previously used for access. As a result, parameter specifications are cross-field if you use only an offset, and therefore trigger a syntax error in a UP. PERFORM test USING c+5 is consequently not permitted.
In addition, in a UP, you can continue to specify the remaining length starting from the offset off for parameters using the form field+off(*).
Ranges for offset and length access when using field symbols
A UP ensures that offset- or length-based access with ASSIGN is only permitted within a predefined range. Normally, this range corresponds to the field boundaries in case of elementary fields or, in case of flat structures, to the purely character-type starting fragment. Using a special RANGE addition for ASSIGN, you can expand the range beyond these boundaries.
Field symbols are assigned a range allowed for offset/length specifications. If the source of an ASSIGN statement is specified using a field symbol, the target field symbol adopts the range of the source. If not explicitly specified otherwise, the RANGE is determined as follows:
ASSIGN feld TO <f>.
In a UP, the field boundaries of field are assigned to <fs> as the range, where field is no field symbol.
ASSIGN <g> TO <f>.
<fs2> adopts the range of <fs1>.
ASSIGN elfeld+off(len) TO <f>.
In a UP, the field boundaries of the elementary field elfield are assigned to <fs> as the range.
ASSIGN <elfld>+off(len) TO <f>.
<fs> adopts the range of the elementary field <elfield>.
ASSIGN struc+off(len) TO <f>.
ASSIGN <struc>+off(len) TO <f>.
In a UP, the purely character-type starting section of the flat structures struc or <struc> determines the range boundaries.
If the assignment to the field symbol is not possible because the offset or length specification exceeds the range permitted, the field symbol is set to UNASSIGNED in a UP. Other checks such as type or alignment checks return a runtime error in a UP. As a rule, offset and length specifications are counted in characters for data types C, N, D, and T as well as for flat structures, and in bytes in all other cases.
Offset without length specification when using field symbols
Up to now, ASSIGN field+off TO <fs> has shown the special behavior that the field length instead of the remaining length of field was used if only an offset but not length was specified. Since an ASSIGN with a cross-field offset is therefore problematic under Unicode, you must observe the following rules:
As previously, the field length of field is used as the length. Using ASSIGN field+off(*)... you can explicitly specify the remaining length.
ASSIGN <fs1>+off TO <fs2> is only permitted if the runtime type of <fs1> is flat and elementary, that is, C, N, D, T (offset in characters), or X (offset in bytes).
ASSIGN field+off TO <fs2> is generally forbidden from a syntactical point of view since any offset <> 0 would cause the range to be exceeded. Exceptions are cases in which a RANGE addition is used.
These rules enable you also in future to pass a field symbol through an elementary field using ASSIGN <fs>+n TO <fs>, as it is the case in a loop, for example.
Processing Sections of Strings
You can address a section of a string in any statement in which non-numeric elementary ABAP types or structures that do not contain internal tables occur using the following syntax:
<f>[+<o>][(<l>)]
By specifying an offset <o> and a length (<l>) directly after the field name <f>, you can address the part of the field starting at position <o>1 with length <l> as though it were an independent data object. The data type and length of the string section are as follows:
Original field
Section
Data type
Data type
Length
C
C
<l>
D
N
<l>
N
N
<l>
T
N
<l>
X
X
<l>
Structure
C
<l>
If you do not specify the length <l>, you address the section of the field from <o> to the end of the field. If the offset and length combination that you specify leads to an invalid section of the field (for example, exceeding the length of the original field), a syntax or runtime error occurs. You cannot use offset and length to address a literal or a text symbol.
You should take particular care when addressing components of structures. To ensure the correct platform-specific alignment of type I and F components, they may contain filler fields, whose lengths you need to consider when calculating the correct offset. Furthermore, SAP plans to convert the internal representation of character types to UNICODE, in which one character will no longer occupy one byte, but instead two or four. Although offset and length specifications can work for character fields (types C, D, N, and T) or for hexadecimal fields (type X), incompatible changes may occur in structures containing a mixture of numeric, character, and hexadecimal fields. SAP therefore recommends that you do not use offset and length to address components of structures.
In nearly all cases, you must specify offset <o> and length <l> as numeric literals without a preceding sign. You may specify them dynamically in the following cases:
When assigning values using MOVE or the assignment operator
When assigning values with WRITE TO
When assigning field symbols using ASSIGN.
When passing actual parameters to subroutines in the PERFORM statement.
DATA TIME TYPE T VALUE '172545'.
WRITE TIME.
WRITE / TIME+2(2).
CLEAR TIME+2(4).
WRITE / TIME.
The output appears as follows:
172545
25
170000
First, the minutes are selected by specifying an offset in the WRITE statement. Then, the minutes and seconds are set to their initial values by specifying an offset in the clear statement.
Offset and Length Specifications in the MOVE Statement
For the MOVE statement, the syntax for specifying offset and length is as follows:
MOVE <f1>[<o1>][(<l1>)] TO <f2>[<o2>][(<l2>)].
Or, when you use the assignment operator:
<f2>[<o2>][(<l2>)] = <f1>[<o1>][(<l1>)].
The contents of the part of the field <f1> which begins at position <o1>1 and has a length of <l1> are assigned to field <f2>, where they overwrite the section which begins at position <o2>1 and has a length of <l2>.
In the MOVE statement, all offset and length specifications can be variables. This also applies to statements with the assignment operator, as long as these can also be written as MOVE statements. In statements where no field name is specified after the assignment operator, (for example, in Numeric Operations), all offset and length specifications must be unsigned number literals.
SAP recommends that you assign values with offset and length specifications only between non-numeric fields. With numeric fields, the results can be meaningless.
DATA: F1(8) VALUE 'ABCDEFGH',
F2(20) VALUE '12345678901234567890'.
F26(5) = F13(5).
In this example, the assignment operator functions as follows:
DATA: F1(8) VALUE 'ABCDEFGH',
F2(8).
DATA: O TYPE I VALUE 2,
L TYPE I VALUE 4.
MOVE F1 TO F2. WRITE F2.
MOVE F1+O(L) TO F2. WRITE / F2.
MOVE F1 TO F2+O(L). WRITE / F2.
CLEAR F2.
MOVE F1 TO F2+O(L). WRITE / F2.
MOVE F1O(L) TO F2O(L). WRITE / F2.
This produces the following output:
ABCDEFGH
CDEF
CDABCD
ABCD
CDEF
First, the contents of F1 are assigned to F2 without offset specifications. Then, the same happens for F1 with offset and length specification. The next three MOVE statements overwrite the contents of F2 with offset 2. Note that F2 is filled with spaces on the right, in accordance with the conversion rule for source type C.
Offset and Length Specifications in the WRITE TO Statement
For the WRITE TO statement, the syntax for specifying offset and length is as follows:
WRITE <f1>[<o1>][(<l1>)] TO <f2>[<o2>][(<l2>)].
The contents of the part of the field <f1> which begins at position <o1>1 and has a length of <l1> are converted to a character field and assigned to field <f2>, where they overwrite the section which begins at position <o2>1 and has a length of <l2>.
In the WRITE TO statement, the offset and length specifications of the target field can be variables. The offset and length of the target field must be numeric literals without a preceding sign.
DATA: STRING(20),
NUMBER(8) TYPE C VALUE '123456',
OFFSET TYPE I VALUE 8,
LENGTH TYPE I VALUE 12.
WRITE NUMBER(6) TO STRING+OFFSET(LENGTH) LEFT-JUSTIFIED.
WRITE: / STRING.
CLEAR STRING.
WRITE NUMBER(6) TO STRING+OFFSET(LENGTH) CENTERED.
WRITE: / STRING.
CLEAR STRING.
WRITE NUMBER TO STRING+OFFSET(LENGTH) RIGHT-JUSTIFIED.
WRITE: / STRING.
CLEAR STRING.
This produces the following output:
123456
123456
123456
The first six characters of the field NUMBER are written left-justified, centered, and right-justified into the last 12 characters of the field STRING.

Unable to capture field values in Master agreement Line Items

I am trying to get the field values from master agreement line items page. I have written the following code to get the line item details which is working fine to capture part number and quantity->
agreementBean = doc.getRootParentIBean();
lineItemCollection = agreementBean.getLineItems();
collectionsize = lineItemCollection.size();
for(i=0;i<collectionsize;i++){
     collectionbean = lineItemCollection.get(i);
     partNum = ""+collectionbean.getPartNumber() ;
     Quantity = ""+collectionbean.getQuantity();
     throw doc.createApplicationException(null,partNum + " , " + Quantity );
Now, my problem is that I am unable to capture the following field item values in the master agreement > line items page.
1. Price Unit
2. Unit Price
3. Product Category
4. Plant
Please help me to find the values.
Thankx in Advance.
Su
Edited by: subrataindra on Aug 10, 2010 11:11 AM

This will return the name of the plant.
.getExtensionField("PLANT").get().getDisplayName(session);
Check if this returns the product category
collectionbean.getExtensionField("ITEM_CAT").get().getDisplayName();
This will Return the Price
collectionbean.getExtensionField("PRICE").get().getPrice();
(return type :BigDecimal)
This will return the currency
collectionbean.getExtensionField("PRICE").get().getCurrency;
(Return type:String)
Similarly to retrieve other fields for which there are no standard functions, use .getExtensionField("Field ID")
Hope this helps
Regards,
Immanuel

Unable to capture Input field value on BSP page

Hi
I have copied ROS (SRM) standard application ROS_PRESCREEN3 into custom and added one input field .
Now when user enters some value in it , i am not able to get that value in my back-hand code.
I have treid the availble code on Fourm , its not working .
Regards
Raul

Hi ,
I am getting the input field values in my back hand using MVC .
Regards
Raul

How can I pass field value betwen view in ICWC?

Hi experts,
I am new to this BSP programming. I have some requirements to modify standard ICWC in CRM 5.0
Hope can get some advices and helps here.
I have added a new field called <status> to context note SEARCHCUSTOMER in BupaSearchB2B view and also the same field name to context note CUSTOMER in BupaCreate view.
I have added the field into both the HTM views and able to execute thru WebClient. However, I have one problem in passing the <status> value from BupaSearchB2B view to the BupaCreate view when I click on the 'create' button.
I do search and saw this thread How can I pass field value beetwen view in IC Web Client? , but i cant figure out how it works.
Do I need to create the field <status> to context note CUSTOMER in BupaSearchB2B? Currently the context note does not have any attributes.
Really appreciate for any help.
Edited by: mervyn tay on Apr 7, 2009 11:42 AM

solved by myself...
code in the CREATE_ACCOUNT method.
ev_entity->set_property( iv_attr_name = 'ZZICNO'
iv_value = lv_icnum1 ).

How To Print Field Value in TOP-OF-PAGE During Line Selection.

How To Print Field Value in TOP-OF-PAGE During Line Selection when double click on field.

(If my memory serves me well (not used for long time ago)
Assign values to system fields sy-tvar0 - sy-tvar9, they will replace the placeholders "&0" through "&9" in the list headers and column headers.
TOP-OF-PAGE DURING LINE-SELECTION.
WRITE: / 'Interactive Report &3'.
WRITE record-vbeln TO sy-tvar3.
Regards,
Raymond

How can I add form field value to the file name in save as dialog box

I do not want the form to be saved automatically, just want the form to auto populate the "file name" only.
A little background on the forms I want to use: My company has 70 retail outlets, I'll use one of our pdf forms called an "Incident Report" as an example. I would like for a store manager to be able to complete the form, then email the form to the main office (I already have javascript to add field values and form name to the email subject line), once the main office receives it, I want for them to be able to file the pdf electronically on our server. We have mutliple forms that we use so I do not want any of the forms to automatically save anywhere, (at this time anyway) I just want the office personnel to be able to click "save as" (or whatever they will need to click) and the form automatically add certain field values from the pdf they have received, of which will be different each time the form is sent to the office (Date, store #, employee name etc.) in addition to the name of the form in the "File name" of the "Save As" dialog box. The main office employees will decide into which server file the pdf should be saved.
I'm using Acrobat 8 professional, the stores and office personnel use Adobe reader.
One little note: We currently print and file a lot of paper on a daily bases, as soon as I can get this to work, we are going green.
Me and a lot of trees in this will really apprecitate any help you can give with this! :-)

You might want to take a look at the document "Developing Acrobat Applications Using JavaScript" (js_developer_guide.pdf) which is part of the Adobe Acrobat SDK, which can be downloaded here. Read the "Privileged versus non-privileged context" (p. 45ff.). You will find an example for "Executing privileged methods in a non-privileged context". Should be almost exactly what you are looking for.
Small Outline: For security reasons ("the user always has to know what's going on") you are not allowed to use the "Doc.saveAs"-method without the user permission (--> in a non-privileged context). In order to reach the goal of a privileged context you can use a trusted function. You do this by creating a JavaScript file (*.js) in either the Application-JavaScript-Folder (default location on Windows systems: "%ProgramFiles%\Adobe\Acrobat 10.0\Acrobat\Javascripts") or the User-JavaScript-Folder (default location on Windows systems: "%AppData%\Adobe\Acrobat\10.0\JavaScripts"). Add the following content to the new file:
myTrustedBrowseForDoc = app.trustedFunction( function ( oArgs ) {
     app.beginPriv();
          var myTrustedRetn = app.browseForDoc( oArgs );
     app.endPriv();
     return myTrustedRetn;
myTrustedSaveAs = app.trustedFunction( function ( doc, oArgs ) {
     app.beginPriv();
          var myTrustedRetn = doc.saveAs( oArgs );
     app.endPriv();
     return myTrustedRetn;
The developer guide actually wants you to add this content to the existing "config.js" file. I recommend creating a new file, since its easier to deploy in a network. Either way, every client/user who needs to be able to save documents this way, needs this JavaScript Code in his Application/User-JavaScript-Folder.
Within the Acrobat Document, which you want to obtain a certain file name, you can now use the trusted functions "myTrustedBrowseForDoc" and "myTrustedSaveAs" to store the file. To call the trusted functions and deliver the file name you can either you use a form field (button) or you add a new menu item. Add the following JavaScript Action to the button/menu item and change "Roller Coaster" to the name of the field which contains the value which you want to become the new file name:
var fileName = this.getField("Roller Coaster").valueAsString;
try {
     var oRetn = myTrustedBrowseForDoc({bSave: true, cFilenameInit: fileName + ".pdf"});
     try {
          myTrustedSaveAs(this, { cPath: oRetn.cPath, cFS:oRetn.cFS });
     catch(e) {
          console.println("Save not allowed, perhaps readonly.");
catch(e) {
console.println("User cancelled Save As dialog box");
Good Luck!

File to RFC/BAPI - Async- How to capture response field value

Hi,
I am doing File to RFC/BAPI Scenario. I have Two BAPI's. THe same source xml file is mapped to the Two Target BAPI's.
For the first flow i.e File to BAPI1, I need to capture BAPI Response, field value and pass this value as Input to the BAPI2.
How do I proceed with the Mapping. I am working on PI 7.1
Any input would be Appreciated.
Thanks & Regards,
Varun

Hi Varun,
apparently you need a Business Process:
XML -> BP (asynchronous), Map to Bapi1 request structure
BP -> BAPI 1 (synchronous)
Transformations step with multi mapping merging XML and Bapi1 response to Bapi2 request structure
BP-> BAPI2
Regards,
Udo

How to clear input field value on back

Hi All,
I have developed an application, in which user put sales order on first page and press a button then its detail display on second page using restAPI. Now when I press back button on second page then it takes me to first page with holding previous sales order value in input field. And when I change its value and press that button again then it shows me previous sales order detail.
Please suggest me, how to refresh cache and input fields value on back button?
Thanks & Regards
Shubhanshu

Hi Viren,
My code is,
First view
sap.ui.jsview("uitest2.first", {
getControllerName : function() {
return "uitest2.first";
createContent : function(oController) {
var text = new sap.m.Label({
        text: 'Dealer Code',
       layoutData: new sap.m.FlexItemData({alignSelf: sap.m.FlexAlignSelf.Center })
var input = new sap.m.Input("CUSTOMER",{
        type: sap.m.InputType.Text,
      placeholder: 'Enter Dealer code...',
      layoutData: new sap.m.FlexItemData({growFactor: 1, alignSelf: sap.m.FlexAlignSelf.Center})
var Dealer = new sap.m.HBox({
            items:[ text,input
//                   new sap.m.Label({
//                   text: 'Dealer Code'
//                   new sap.m.Input("CUSTOMER",{
//                   type: sap.m.InputType.Text,
//                   placeholder: 'Enter Dealer code...'
                   height : "6em"
      var button = new sap.m.Button({
           text: "Submit",
           press: function(oEvent) {
              oController.loadData();
              app = sap.ui.getCore().byId("myApp");
              app.to("idsecond1");//, sap.ui.getCore().byId("CUSTOMER").getValue());
           layoutData: new sap.m.FlexItemData({alignSelf: sap.m.FlexAlignSelf.Center})
      return new sap.m.Page({
     title: "Sales Dealer Info",
     content: [ Dealer,button
First controller
sap.ui.controller("uitest2.first", {
    loadData: function() {
        var oParameters = ({
        "CUSTOMER" : sap.ui.getCore().getElementById('CUSTOMER').getValue(),
         console.log(oParameters);
         var url = "http://###########:8000/sap/bc/zrst_customer?sap-client=800/";
         var oModel = new sap.ui.model.json.JSONModel();
         $.ajax({
         url : url ,
         dataType : "jsonp",
         type : "POST",
         data: oParameters,
         success: function(data,textStatus,jqXHR) {
         data = JSON.parse(data);
                 console.log(data);
                 oModel.setData(data);
         sap.ui.getCore().setModel(oModel);
Second View
sap.ui.jsview("uitest2.second", {
getControllerName : function() {
return "uitest2.second";
createContent : function(oController) {
var oTable = new sap.m.Table("table",{
       headerText: "Dealer data",
       columns: [
         new sap.m.Column({
           header: new sap.m.Label({text: "NAME"}),
demandPopin : true,
minScreenWidth : "Tablet",
         new sap.m.Column({
           header: new sap.m.Label({text: "CITY"}),
demandPopin : true,
minScreenWidth : "Tablet",
         new sap.m.Column({
           header: new sap.m.Label({text: "COUNTRY"}),
demandPopin : true,
minScreenWidth : "Tablet",
         new sap.m.Column({
           header: new sap.m.Label({text: "COUNTRYISO"}),
demandPopin : true,
minScreenWidth : "Tablet",
         new sap.m.Column({
          header: new sap.m.Label({text: "STREET"}),
demandPopin : true,
minScreenWidth : "Tablet",
         new sap.m.Column({
          header: new sap.m.Label({text: "PST_CODE"}),
demandPopin : true,
minScreenWidth : "Tablet",
         new sap.m.Column({
          header: new sap.m.Label({text: "TELEPHONE"}),
demandPopin : true,
minScreenWidth : "Tablet",
         new sap.m.Column({
          header: new sap.m.Label({text: "EMAIL"}),
demandPopin : true,
minScreenWidth : "Tablet",
       items: {
       path: "/KEY",
       template: new sap.m.ColumnListItem({
       cells: [
               new sap.m.Text({                              //new sap.m.ObjectIdentifier
               text: "{NAME}"
               new sap.m.Text({
               text: "{CITY}"
               new sap.m.Text({
               text: "{COUNTRY}"
               new sap.m.Text({
               text: "{COUNTRYISO}"
               new sap.m.Text({
               text: "{STREET}"
               new sap.m.Text({
               text: "{PST_CODE}"
               new sap.m.Text({
               text: "{TELPHONE}"
               new sap.m.Text({
               text: "{EMAIL}"
return new sap.m.Page({
title: "Dealer Info",
showNavButton: true,
navButtonTap:function(){
app = sap.ui.getCore().byId("myApp");
app.to("idfirst1");
sap.ui.getCore().getElementById('CUSTOMER').setValue("");
oModel.refresh();
content: [ oTable
Index.htm
<!DOCTYPE HTML>
<html>
<head>
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<script src="resources/sap-ui-core.js"
id="sap-ui-bootstrap"
data-sap-ui-libs="sap.m,sap.ui.commons"
data-sap-ui-theme="sap_bluecrystal">
</script>

<script>
sap.ui.localResources("uitest2");
var app = new sap.m.App("myApp",{initialPage:"idfirst1"});
var page = sap.ui.view({id:"idfirst1", viewName:"uitest2.first", type:sap.ui.core.mvc.ViewType.JS});
var page1 = sap.ui.view({id:"idsecond1", viewName:"uitest2.second", type:sap.ui.core.mvc.ViewType.JS});
app.addPage(page).addPage(page1);
app.placeAt("content");
</script>
</head>
<body class="sapUiBody" role="application">
<div id="content"></div>
</body>
</html>
Thanks
Shubhanshu

How to transfer the field values in MA form RFX

Hi
We have two fields ( extended field of date type ) in Rfx page . Now client wants that this two field value will be transferred to Master Agreement page while creating MA form Rfx award .
Is there any possible way to do this ?
Regards
Sudipta
Edited by: Sudipta62 on Dec 20, 2011 10:38 AM

Sudipta, Vikram,
If names are the same, are the fields transferred automatically? Or do we still write code?
Thanks,
MP

Who has changed the Custom Field value?

Dears,
Need to know the information regarding how to fetch that who has changed the Custom field value from PWA/MPP.
Example:
There is a PDP (say ProjectInfo):
There is a Custom Field added to that PDP (say Project Status = In Progress).
Now for ProjectA, someone has checked out and changed the Custom Field "Project Status" from "In Progress" to "Closed".
I need to fetch the information regarding who has changed that Custom field.
In which direction should I move: Event Handlers, PSI???? Any other stuff?
Thanks & Regards,
Shravan

Hi Shravan,
I'm not a developer but I do know that you can use an event handler pushing the resource name and date in custom fields.
Another way is to use a 3rd-party tool like
FluentPro Audit Tool.
Hope this helps,
Guillaume Rouyre, MBA, MVP, P-Seller |

Partial field value comparison

Similar Messages

Maybe you are looking for