FM for Attribute type

can anyone suggest a FM for finding the type of attribute of a program: if it is a module pool, executable , etc.
thanks!

FUNCTION MODULES
http://www.erpgenie.com/abap/functions.htm
http://www.sapdevelopment.co.uk/fmodules/fmssap.htm
http://www.erpgenie.com/abap/index.htm
http://www.geocities.com/victorav15/sapr3/abapfun.html

Similar Messages

Value 'defaultNs:AddBP2Type' is not allowed for attribute 'type'

Hi All,
I created the wsdl for mobile and I tried to send a SOAP request from Altova XMLSpy. However when I geive the wsdl in 'wsdl file location' I receive the following.
File http://127.0.0.1:8080/B1iXcellerator/exec/dummy/com.sap.b1i.vplatform.scenarios.setup/vPac.sap.B1Mobile/001sap0003_sap.B1Mobile.wsdl is not valid.
Invalid XML schema: 'Value 'defaultNs:AddBP2Type' is not allowed for attribute 'type'.'
Error location: wsdl:definitions / wsdl:types / xs:schema / xs:element / @type
Any Idea?
Vangelis

Hi,
it seems that Altove did not cope with defaultNs prefix that is used for marking default namespace.
just look up in your <xs:schema > tag what namespace prefix is used for your namespace - you shall find there something like this
<xs:schema xmlns:ns0="your.namespace.com" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"
and replace prefix defaultNs with prefix of your namespace (in example above it would be ns0)
There might be several usages of defalutNs iside of WSDL (at least in my case were two) so replace it everywhere using same approach
Best regards, Artem

URGENT HELP! - The prefix "xsi" for attribute "xsi:type" is not bound

Hi! i createD a WebService using the JWSDP 1.2. In the server-side i read a xml file, create another empty Document and using the importNode() method i populate the empty created doc. The problem is when i try to send client this created document. I'm using the DOMSource to send it to client side. Both client and WS method code are below! Does anyone know the answer??
And I'm getting this error:
[java] Endpoint address = http://localhost:8080/cm/ContextManager
[java] [Fatal Error] :2:42: The prefix "xsi" for attribute "xsi:type" is not bound.
[java] javax.xml.transform.TransformerException: org.xml.sax.SAXParseException: The prefix "xsi" for attribute "xsi:type" is not bound.
[java] at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:469)
[java] at contextclient.CMClient.main(Unknown Source)
[java] Caused by: org.xml.sax.SAXParseException: The prefix "xsi" for attribute "xsi:type" is not bound.
[java] at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1139)
[java] at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:452)
[java] ... 1 more
[java] ---------
[java] org.xml.sax.SAXParseException: The prefix "xsi" for attribute "xsi:type" is not bound.
[java] at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1139)
[java] at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:452)
[java] at contextclient.CMClient.main(Unknown Source)
====================CLIENT CODE================================
Source getdevice = manager.getDevice("How");
DOMResult domResult = new DOMResult();
// getting a transformation factory instance
TransformerFactory transformerFactory = TransformerFactory.newInstance();
Transformer transformer = transformerFactory.newTransformer();
transformer.transform(getdevice, domResult);
Node node = domResult.getNode();
DOMSource domSRC = new DOMSource(node);
StreamResult streamResult = new StreamResult(System.out);
transformer.transform(domSRC, streamResult);
===============================================================
===================WebService Method CODE======================
     public Source getDevice(String primaryContext)
          Source src = null;
          try
               String uri = "C:\\foo\\DeviceInstance.xml";
               DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
               DocumentBuilder builder = factory.newDocumentBuilder();
               //create the first Document
               Document doc1 = builder.parse(uri);
               //create the second Document
               Document doc2 = builder.newDocument();
               //create the second doc's root element and append it
               Element rootDoc2 = (Element)doc2.createElement("device");
               doc2.appendChild(rootDoc2);
               //get root of first document
               Element rootDoc1 = doc1.getDocumentElement();
               NodeList list = rootDoc1.getElementsByTagName(primaryContext);
               for(int i = 0; i < list.getLength(); i++)
                    Element nodeToMove = (Element) list.item(i);
                    Node newNode = doc2.importNode(nodeToMove, true);
                    rootDoc2.appendChild(newNode);
               src = new DOMSource(doc2);
          catch(DOMException dome)
               dome.printStackTrace();
          catch(Exception e)
               e.printStackTrace();
          return src;
===============================================================
Does anyone know what could it be? Please, it's very urgent!
Tks in Advance,
Rodrigo.

The xml i'm trying to send is below. It's important explain that in a standalone app it works perfectly. Unfortunately, when i perform the same actions in the WS world, it doesn't work. See, i tried to put the attributes inside the root element with the setAttributeNS() method but i got the same error again. How could i bound the attribute with no errors like that said before???
<?xml version="1.0" encoding="UTF-8"?>
<device xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="context.xsd">
<Identity xsi:type="fooType">
               <Name>
                    <GivenName>Rodrigo</GivenName>
                    <FamilyName>Felicio</FamilyName>
               </Name>
          </Identity>
<Identity xsi:type="foowType">
               <DeviceID>dev00345</DeviceID>
          </Identity>
</device>
Regards,
Rodrigo.

Prefix for attribute while defining data type

Hello can we add any prefix for attribute of a field while defining any data type .
will get data "DA". and I need to add "rr" to this becomes "rrDA"
or do we need to do this while doing message mapping.

Hi satya ,
you could also design the XSD for the masse in an external editor (e.g. XMLSPY) and upload into external definitions.
Regards Mario

Oracle.jbo.AttrValException: JBO-27019: Get method for attribute

Hi Guys,
I am trying to add a new column to Oracle quoting.It has already been customized by some consultant few years back. I followed the note 392728.1 on metalink and also have the documentation by the previous consultant but getting the error oracle.jbo.AttrValException: JBO-27019: Get method for attribute Draft in HeaderVO could not be resolved after adding my column, when I try to print the quote.
Here are the steps I took
1) added a column to the query (at the end) in HeaderVO.xml
2) added the below code in the HeaderVO.xml
<ViewAttribute
Name="DRAFT"
IsQueriable="false"
IsPersistent="false"
Precision="100"
Type="java.lang.String"
AliasName="DRAFT"
ColumnType="VARCHAR2"
Expression="DRAFT"
SQLType="VARCHAR" >
<DesignTime>
<Attr Name="_DisplaySize" Value="100" />
</DesignTime>
</ViewAttribute>
3). Modify HeaderVORowImpl.java file to add setters and getters for the newly added view attribute. For example,
a) case 67: //
setDRAFT((String)obj);
return;
b) case 67:
return getDRAFT();
c) ublic void setDRAFT(String s)
setAttributeInternal(67, s);
public String getDRAFT()
return (String)getAttributeInternal(67);
d) protected static final int DRAFT = 67;
Everything is dont exactly as per the manual but not sure why I am getting this issue. Any help will be appreciated.

a) case 67: //
setDraft((String)obj);
return;
b) case 67:
return getDraft();
c)public void setDraft(String s){
setAttributeInternal(67, s);
public String getDraft(){
return (String)getAttributeInternal(67);
d) protected static final int DRAFT = 67;
can u change it as explained above.. setDRAFT should be setDraft.. and getDRAFT should be getDraft..
and make sure that the index.. number is exactly matching with the attribute order in the VO

DBSequence entity attribute type not available

Hi OTN,
I want to set an entity attribute type to DBSequence. But there's no such type in a drop-down list, only Java types.
I tried to set the type in source manually but at runtime framework doesn't assign a negative integer to the attribute at Create operation.
In simple test application DBSequence type is available and negative integers get assigned.
I have found a proper thread (Re: DBSequence type no longer available for entity attributes? but the solution there is to recreate the whole datamodel. That isn't suitable for me.
Maybe there is a better solution now?
Jdeveloper 11.1.1.2, ADF BC
Thanks.

I logged Bug 9380578 - "SQL FLAVOUR" AND "TYPE MAP" CAN BE CHANGED IN "PROJECT PROPERTIES"
(published in My Oracle Support).
NB: in JDeveloper 9.x, it was possible to change the "SQL Dialect" (as it was called at that time), but the ADF BC objects and the custom code weren't changed;
hence it was decided to gray out that choice after the Project creation.
Regards,
Didier.

Default value for attribute "COUNTRY" in BP_HEAD_SEARCH/MainSearch

Hi Gurus,
Requirement is to set default value for attribute "COUNTRY" in BP_HEAD_SEARCH/MainSearch when user clicks on Corporate Account.
Below is code that i have written in DO_PREPARE_OUTPUT.
Code is working fine and in the debug also i can see the value of COUNTRY is set to DE, but it is not showing on the screen for first time but when i load component second time(Refresh the screen), it shows me value.
Any help would be appreciated. If somebody has otheralternative kindly share.
CALL METHOD super->do_prepare_output( iv_first_time = iv_first_time ).
Calling Super Method
CALL METHOD super->do_prepare_output
   EXPORTING
     iv_first_time = abap_true.
Data Declatation
DATA :lr_col            TYPE REF TO if_bol_bo_col,
        lr_current        TYPE REF TO if_bol_bo_property_access,
        lr_param          TYPE REF TO if_bol_bo_property_access,
        lr_qs             TYPE REF TO cl_crm_bol_dquery_service,
        lv_attr_name      TYPE name_komp,
        lv_sign           TYPE bapisign,
        lv_option         TYPE bapioption,
        w_country_exist   TYPE c,
        w_param           TYPE string,
        w_value           TYPE string,
        w_flag            TYPE c.
Getting SEARCH Context Node
lr_qs ?= me->typed_context->search->collection_wrapper->get_current( ).
Get Selection Parameters
lr_col ?= lr_qs->get_selection_params( ).
Start from first parmaters
lr_current = lr_col->get_first( ).
Clearing Variables
CLEAR : w_country_exist, w_flag, w_param, w_value.
Loop till we have selection paramters
WHILE lr_current IS BOUND.         " While loop 1
checking attribute name is COUNTRY then setting some variable
    w_param = lr_current->get_property_as_string( 'ATTR_NAME' ).
    CASE w_param.
      WHEN 'COUNTRY'.
If country is filled then setting variable
        w_value = lr_current->get_property_as_string( 'LOW' ).
        IF w_value IS NOT INITIAL.
          w_country_exist = abap_true.
        ENDIF.
When we got COUNTRY attribute then setting flag
        w_flag = abap_true.
    ENDCASE.
Calling next parameter
    lr_current = lr_col->get_next( ).
ENDWHILE.                          " While loop 1
In below block we are checking is COUNTRY attribute is blank and
we have found COUNTRY attribute in current selection paramters
IF lr_qs IS BOUND.                 " SEACRCH CONTEXT BOUND
If vairable is blank means DE or any other value is not filled in COUNTRY Attribute
    IF w_country_exist IS INITIAL.   " w_contry_exist
We have to add selection attribute if we come accross COUNTRY attribute during our search
      IF w_flag EQ abap_true.        " w_flag
Adding COUNTRY attribute with default value 'DE'
        lr_qs->add_selection_param( EXPORTING iv_attr_name = 'COUNTRY'
                                              iv_sign      = 'I'
                                              iv_option    = 'EQ'
                                              iv_low       = 'DE' ).
      ENDIF.                         " w_flag
    ENDIF.                           " w_contry_exist
ENDIF.                             " SEACRCH CONTEXT BOUND
In below block we will remove COUNTRY attribute when it has blank value
IF lr_qs IS BOUND AND w_country_exist IS INITIAL.
    lr_current = lr_col->get_first( ).
    WHILE lr_current IS BOUND.
      w_param = lr_current->get_property_as_string( 'ATTR_NAME' ).
      CASE w_param.
        WHEN 'COUNTRY'.
          w_value = lr_current->get_property_as_string( 'LOW' ).
          IF w_value IS INITIAL.
            lr_col->remove( iv_bo = lr_current ).
          ENDIF.
      ENDCASE.
      lr_current = lr_col->get_next( ).
    ENDWHILE.
ENDIF.
Edited by: Harsharandeep Singh on Apr 28, 2011 3:44 PM

Hi,
Try it like this:
DATA:
    lr_bo        TYPE REF TO if_bol_bo_property_access ,
    lv_attr_name TYPE name_komp.
FIELD-SYMBOLS:
    <ls_param>   TYPE crms_thtmlb_search_criterion.
READ TABLE parameters
       ASSIGNING <ls_param>
       WITH KEY field = 'COUNTRY'.
IF ( sy-subrc = 0 ).
    <ls_param>-value1 = ip_pfct.
ENDIF.
CHECK ( me->parameter_collection IS NOT INITIAL ).
lr_bo = me->parameter_collection->get_first( ).
WHILE lr_bo IS BOUND.
    CALL METHOD lr_bo->get_property_as_value
      EXPORTING
        iv_attr_name = 'ATTR_NAME'
      IMPORTING
        ev_result    = lv_attr_name.
    IF lv_attr_name EQ 'COUNTRY' .
      CALL METHOD lr_bo->set_property
        EXPORTING
          iv_attr_name = 'LOW'
          iv_value     = 'DE'.
      EXIT.
    ELSE.
      lr_bo = me->parameter_collection->get_next( ) .
    ENDIF.
ENDWHILE .
Kind regards,
Micha

Access to Attribute Type via Java API

Hi,
I'm writing an aplication in Java to access out OLAP schema and display certain DIMENSION/LEVEL and ATTRIBUTE values. This is working out really well but I'm hitting one issue at the moment which has me stumped.
When I display a Dimension value in a table I want to default the attribute we display to a sensible display value. In AWM there is a field "Attribute Type" which offers drop down selections for "User", .... "Member Short Description", "Member Long Description"...
See the General Tab under Attributes for a particular Attribute. Looking at the Help text for the "Member Long Description" I see the following.
"Long descriptive names typically used by Oracle Business Intelligence tools for displaying dimension members in selection lists, crosstabs, and graphs." Looks perfect for what I want. My Dataware house architect already has an Attribute for each hirearchy
marked with this property so in theory I should be able to look for the Attribute in the Dimension with this property and bingo I have my default display Atttribute!
The problem is I seem to be able to find api's to access every aspect of the MdmAttribute object except this particular property.
Here is a snippet from the OLAP api sample code augmented with some println's of my own:
if (mdmAttr.getName().equals(name)) {
     System.out.println("Attribute : " + mdmAttr.getID());
     System.out.println(" name : " + mdmAttr.getName());
     System.out.println(" desc : " + mdmAttr.getDescription());
     System.out.println(" s desc: " + mdmAttr.getShortDescription());
     System.out.println(" type : " + mdmAttr.getType());
     System.out.println(" type id: " + mdmAttr.getType().getID());
return mdmAttr;
None of the avaiable APIs of MdmAttribute seem to fit the bill.
The question is ... is there an API somewhere I can call on the MdmAttribute object or an associated object that will give me back the "Attribute Type" as listed in this dropdown. Note that getType returns DataType!String which denotes the fundemental type of the Attribute (int, String etc) rather than this abstract Attribute Type property we need. Not listed here is the getDataType() api which also returns DataType!String and seems to be equivalent to the getType api.
Regards
Fergal

One small clarification if its not already obvious. We are using the OLAP Java api's directly ... not via BI Beans.
Regards
Fergal

Adobe Offline Form - Parse method is not possible for this type

Hi All,
I have developed an application for the offline scenario of interactive adobe form. I tried to load the adobe form from my desktop. After pressing the button "Display form" it throws an error "Parse method is not possible for this type".
If I include wdContext.getNodeInfo().getAttribute("pdfObject").getModifiableSimpleType() in the doInit() method of the view I receive this error -
com.sap.tc.webdynpro.progmodel.context.ContextException: MappedAttributeInfo(UploadView.pdfObject): must not modify the datatype of a mapped attribute
When I comment it out and upload I receive the error enclosed -
Parse method is not possible for this type
Can someone please help me with a step by step solution to this problem?
Any help is highly appreciated.
Many thanks,
Divya

Hi Divya,
Please try to do it as stated below:
     IWDAttributeInfo attInfo = wdContext.getNodeInfo().getAttribute("pdfObject");
     ISimpleTypeModifiable type = attInfo.getModifiableSimpleType();
     IWDModifiableBinaryType binaryType = (IWDModifiableBinaryType)type;
Try putting the code in wdInit() or wdDoModifyView().
Let me know if you still face the issue.
Regards,
Arafat

Parse method is not possible for this type Exception in web dynpro

I have a file upload component and one button in a view.
I have created a binary type context element and mapped it with fileupload component.while clicking the submit button I am getting " Parse method is not possible for this type" exception.
help me out.

Hi sridhar,
Use this code for Upload
context u create one attribute(up),u assign the data type as "Resource"(which is dictionary type)
InputStream text = null;
    int temp = 0;
    try
         File file = new File(wdContext.currentContextElement().getUp().getResourceName());
         FileOutputStream op = new FileOutputStream(file);
         if(wdContext.currentContextElement().getUp()!=null)
              text = wdContext.currentContextElement().getUp().read(false);
               while((temp=text.read())!=-1)
                                                                   op.write(temp);
         op.flush();
         op.close();
    catch(Exception e)
     e.printStackTrace();

Report RFDUZI00 claims about entry for movement type CREIR

Hello,
we have moved from R/3 4.6 to ECC 6.0. Now we have some errors coming up in FI module.
One is this:
Report RFDUZI00 (debitor interest calc. run) ends with a comment before posting:
"For movement type CREIR and interest attribute 01 the table of time dependent interest conditions is not maintained" (message translated from german).
We had to add this entry in transaction OB81 to get rid of this issue.
In 4.6 we didin´t need this entry to run the report successful.
We have checked and did not find any comments in release notes.
Question: Can anybody confirm to this new requirement of the system, which looks like RFDUZI00 or dependent include etc. was enhanced to check entries for creditors (for which reason?).
Possibly we found the answer in OSS 670117, which explains changes in RFDUZI00 relevant since R/3 4.7.
Regards
Dirk
Message was edited by:
Dirk Meinhard

Solved on my own!

Custom screen for attribute BP relationship (t-code: BUBA)

Dear experts,
It is possible to create custom screen for attribute BP Relationship (t-code: BUBA)?
any document for this case?
(Go to t-code: BUBA -> Block BP Relationship Type -> Click BP Views)
Need your response...
Thanks and Regards,

Dear experts,
any updated for this case???
Need your response..
Thanks and regards,

Fld selection for movement type 601/ act 425000

hi all
When i try to do PGI for delivery, i am getting given below error.
"Fld selection for movement type 601/ act 425000 differs for customer goods movement (015)" Please guide me to solve this issue. Rgds
Madhavan

Dear Madhavan,
For mvt type 601,in OMJJ, customer field is set as optional.
You can check this in OMJJ - mvt type 601 - field selections - Material management.
Check in FS00 - the field status group assigned to GL account - 40005900, then open the attributes of that field selection group in OBC4, check customer field is suprresed.
You can change either (suggest to check with FI consultant to change in field status group).
Alternatively you can go to t/code se38 & run RM07CUFA program with variants to compare these two settings and make necessary changes.
Hope this could help you resolve this issue. TQ
rgds,
nema

Personal Profile service for Brazil - Type Conflict for infotype 0002

Hello All,
We are enabling personal profile service for Brazil. And we did all the required configuration for that.
When I access the personal info service I can see the overview page with personal data. But when I click on display link, I get the error message saying -
Type conflict with ASSIGN in program CL_HRPA_UI_CONVERT_0002_BR
Is there any configuration missing?
Thanks,
Bhushan

Short text
    Type conflict with ASSIGN in program "CL_HRPA_UI_CONVERT_0002_BR====CP".
What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_HRPA_UI_CONVERT_0002_BR====CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
    You attempted to assign a field to a typed field symbol,
    but the field does not have the required type.
How to correct the error
    Adapt the type of the field symbol to the type of the field or use an
    untyped field symbol or use the "CASTING" addition.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "ASSIGN_TYPE_CONFLICT" " "
    "CL_HRPA_UI_CONVERT_0002_BR====CP" or "CL_HRPA_UI_CONVERT_0002_BR====CM003"
    "IF_HRPA_UI_CONVERT_STANDARD~OUTPUT_CONVERSION"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
Line SourceCde
    6   DATA: attributes           TYPE hrpad_field_attribute_tab.
    7   DATA: l_object_key         TYPE hcm_object_key.
    8   DATA: l_subrc              TYPE sysubrc.
    9
   10   FIELD-SYMBOLS <r0002_br>   TYPE hcmt_bsp_pa_br_r0002.
   11   FIELD-SYMBOLS <p0002_br>   TYPE p0002.
   12   FIELD-SYMBOLS <p0625>      TYPE p0625.
   13
   14   is_ok = if_hrpa_ui_convert_standard~true.
   15   ASSIGN screen_structure    TO <r0002_br>.
   16   l_object_key = <r0002_br>-object_key.
   17   MOVE-CORRESPONDING pnnnn TO super_screen_ref.
   18
   19   CALL METHOD super->if_hrpa_ui_convert_standard~output_conversion
   20     EXPORTING
   21       screen_structure_name = a_super_screen_structure_main
   22       pnnnn                 = pnnnn
   23       message_handler       = message_handler
   24       field_metadatas       = field_metadatas
   25     IMPORTING
   26       screen_structure      = super_screen_ref
   27       is_ok                 = is_ok
   28       field_attributes      = field_attributes.
   29
   30   MOVE-CORRESPONDING super_screen_ref TO screen_structure.
   31
   32   CASE a_super_screen_structure_main.
   33     WHEN 'HCMT_BSP_PA_XX_R0002'.
   34       ASSIGN pnnnn                  TO <p0002_br>.
   35       ASSIGN screen_structure       TO <r0002_br>.
>>>>>       ASSIGN pnnnn2                 TO <p0625>.
   37       MOVE-CORRESPONDING <p0002_br> TO <r0002_br>.
   38       MOVE-CORRESPONDING <p0625>    TO <r0002_br>.

How to create new group for material type

Hello all experts,
Im unable to create a new group for materials types, diff groups for FG and raw materials material type??
Could you pls help ??
Thanks in advance.

Hi
When you create a new material you have to specify the material types like finished goods or raw material like that in the initial screen
For this new material types can be defined in
SPRO -> Logistic - General -> Material Master -> Basic Settings -> Material Type ->Define attribute of material Type
T code OMS2
After specifying the material type and giving organizational data like plant, storage location,sales org etc we go on to create the material
In one of the tabs the material groups should be specified and from MM point of view it is a reqd entry
this can be defined in
Define Material Group
SPRO -> Logistic - General -> Material Master -> Setting for Key Field -> Define Material Group
T .Code: OMSF
I beleive this is what you are asking about
Regards
Raja

FM for Attribute type

Similar Messages

Maybe you are looking for