Creation of New Types Alerts

Hi
I need to create a new alert,  its possible to create a new type in AMON1 or if its possible to change one standard alert?
Thank you,
Lucas

If anybody has the same doubt this document can solve your questions...
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/80b31362-7806-2d10-84a0-d2886880c282?QuickLink=index&…

Similar Messages

  • Creation of new condition type: MWST

    Hi, Everyone.
    I would like to ask for some help regarding this issue: Creation of new condition type: MWST with the following details:
    1. For the country French Polynesia, Create a new VAT condition of 10%.
    2. Create a new one called : Class : Z u2013 Designation : France : TOM corresponding to 10 % of VAT to be invoiced
    and then associate this new VAT code u201CZu201D to the applicant Nr 221860
    If you could provide me a step by step process on how to resolve this, it would be very much appreciated.  Thank you so much.

    Hello
    What type of condition type you want.
    It is always advisable to create a new conditon type copying a standard condition type.
    For gross price condition types select PB00/PBXX
    For freight charges, Copy FRA1/FRB1
    Regards

  • Block creation of new Internal Order Type

    Hello,
       We have several internal Orders types and we want to block the creation of new IO. Is there any way through customizing to do that?
       I have considering to do it using an step in a validation but I think can be a better way.
    Thanks,

    Hi,
    Ravi is right, you can restrict through authorizations. To do that, you have to modify the role assigned to users that allow them to create internal orders of any type. Use the transaction SUIM, search the role by user or by transaction (KO01). Then, in the role, there is an entry that corresponds to Controlling (CO) -
    > CO-OPA: General authorization object for internal orders (K_ORDER) -
    >
    Order Type  (AUFART)   : Select for example RA01
    Internal order authorization  (AUTHPHASE) :
    Actions for CO-OM Authorizatio (CO_ACTION) :  0000  Master Data.
    Cost Element  (KSTAR) :    
    CO-OM Responsibility Area  (RESPAREA) : 
    Usually a BASIS do the modification of the role.
    Regards,
    David Z.

  • Requirement of creation of new condition types and Account keys tax codes

    Hi,
                   In what all possible scenarios will the requirement to create new Condition types and accont keys arise for the creation of new depreciation keys.
    Thanks
    Raja.
    Edited by: Raja Gopal 345 on Aug 29, 2010 1:06 PM

    Unless you use jurisdiction codes, and no external tax system, for
    example with tax procedure TAXUSJ, there is no validity dates for the
    condition records.  You can see this differnce by comparing the tables
    A003 without jurisdiction codes and A053 with jurisdiction codes.  A053
    contains the extra fields DATBI (key field) and DATAB.  This is the
    standard functionality.
    Please have a look at the following part of note 418582:
    " Changing past percentage rates has to be inhibited in order to avoid
    database inconsistencies. For this reason, the functions which allow you
    to transport time-dependent tax codes with percentage rates from the
    past are not supported."

  • Creation of new Excise Condition

    I wanted to create a New Condition type for one specific NON CENVATABLE EXCISE duty .....
    I am clear about creation of Condition types and addition of that condition at required place in PROCEDURE.
    Do i need to make any other settings also ?
    Regards
    Shrey

    HI
    Check if needed to assign any account key to this new condition type in your procedure if needed, then mantain the GL acc for the same.
    If you are adding this condition type in your TAXINN procedure (assuming so) you need to create the condition type for the same by using trax FV11.
    If you are adding your condition type in Pricing procedure then no ned to create the condition record.
    Regards
    Sujoy

  • Creation of new internal delivery channel using AQ

    Hi,
    I wanted to route one of Trading partner data to a different queue.(no want to use existing queues - IP_IN /IP_OUT queue).
    This needs to create a new delivery channel using AQ in B2B.
    I have gone thru the steps & entered all entries, but I am not able to find any queues created in B2B schema.
    Do I need to create a queue using PL/SL in B2B to make it available as internal delivery channel or this setup itself will create a queue in B2B?
    PFA the entirs:
    for transport parameters
    - transport server (B2B server IP)
    - Protocol as AQ
    -URI - b2b.<uri_name> (name of Queue, wanted to create)
    - Hostname
    - Port
    -SID - b2b
    -consumer - b2buser
    - receiptient - null
    -Polling interval - 6000
    Transport server details:
    Host name - (IP)
    IP - Host IP
    username -
    Pswd - for B2B schema
    Any pointers will be a great help.
    Regards,
    MS

    As mentioned by TH in the above post, first thing is to create the data type that is used for messages - IP_MESSAGE_TYPE. This data type will already be present in the B2B database and could be reused.
    For a new data type you could do the following.
    ==============================================================
    Create a new data type using the following
    ==============================================================
    create type IP_MSG_TYPE as OBJECT (
         MSG_ID VARCHAR2(128),
         INREPLYTO_MSG_ID VARCHAR2(128),
         FROM_PARTY VARCHAR2(512),
         TO_PARTY VARCHAR2(512),
         ACTION_NAME VARCHAR2(512),
         DOCTYPE_NAME VARCHAR2(512),
         DOCTYPE_REVISION VARCHAR2(512),
         MSG_TYPE INT,
         PAYLOAD CLOB,
         ATTACHMENT BLOB
    Once you have created a new Data type ( or are reusing the existing data type), you need to create Queue Table that will hold the Outbound and Inbound message queues. The existing Queue table is "IP_QTAB" which can again be reused.
    For new Queue table you could do the following
    ==============================================================
    Create a new Queue Table using the following
    ==============================================================
    execute dbms_aqadm.create_queue_table (     queue_table => 'MY_QTAB',
                             queue_payload_type => 'IP_MSG_TYPE',
                             multiple_consumers => FALSE);
    If you need to reuse the datatype change the queue_payload_type to 'IP_MESSAGE_TYPE'.
    Once we have the Queue Table that will hold the queues, we need to add and start the queues that are to be used for the inbound and outbound messages.
    ==============================================================
    Create the new Queues into the Queue Table using the following
    ==============================================================
    execute dbms_aqadm.create_queue (queue_name => 'B2B.MY_OUT_QUEUE', queue_table => 'B2B.MY_QTAB');
    execute dbms_aqadm.create_queue (queue_name => 'B2B.MY_IN_QUEUE', queue_table => 'B2B.MY_QTAB');
    execute dbms_aqadm.start_queue(queue_name => 'B2B.MY_OUT_QUEUE', dequeue => TRUE, enqueue => TRUE);
    execute dbms_aqadm.start_queue(queue_name => 'B2B.MY_IN_QUEUE', dequeue => TRUE, enqueue => TRUE);
    If you are reusing the queue table IP_QTAB for creation of new queues, then reference that for the queue_table in above commands.
    You need to reference the queue_name eg. B2B.My_OUT_QUEUE in the B2B UI screen.
    Hope this helps.
    AKT

  • Creation of new Sales order

    Hi,
           While creating a new Sales Order(tcode VA01) depending on the material, Item category will be generated and depending on the Item category purchase requisition screen(ME51n) will be automatically opened and PR will be created.
    Now to automate this process, BAPI_SALESORDER_CREATEFROMDAT1 will be called to create the sales order. But the requirement is that we need to pass Requisitioner and Vendor to the BAPI for creation of PR.
    But in this BAPI there is no option/field to pass Requisitioner and Vendor. So is there any other BAPI/Function Module where a new Sales order is created and also we can pass Requisitioner and Vendor required for creation of new PR.

    REPORT  ZSALESORDER.
    Parameters
    Sales document type
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
    PARAMETERS: p_auart TYPE auart OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Sales organization
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
    PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Distribution channel
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
    PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Division.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
    PARAMETERS: p_spart TYPE spart OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    SKIP 1.
    Sold-to
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
    PARAMETERS: p_sold  TYPE kunnr OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Ship-to
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
    PARAMETERS: p_ship  TYPE kunnr OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    SKIP 1.
    Material
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
    PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Quantity.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
    PARAMETERS: p_menge TYPE kwmeng  OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Plant
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
    PARAMETERS: p_plant TYPE werks_d .
    SELECTION-SCREEN END OF LINE.
    Complete Deliver
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text10 FOR FIELD p_autlf.
    PARAMETERS: p_autlf TYPE autlf DEFAULT 'X'.
    SELECTION-SCREEN END OF LINE.
    Data declarations.
    DATA: v_vbeln            LIKE vbak-vbeln.
    DATA: header             LIKE bapisdhead1.
    DATA: headerx            LIKE bapisdhead1x.
    DATA: item               LIKE bapisditem  OCCURS 0 WITH HEADER LINE.
    DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
    DATA: partner            LIKE bapipartnr  OCCURS 0 WITH HEADER LINE.
    DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
    DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                             WITH HEADER LINE.
    DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                             WITH HEADER LINE.
    DATA: lt_schedules_ink    TYPE STANDARD TABLE OF bapisdhead1
                             WITH HEADER LINE.
    Initialization.
    INITIALIZATION.
    v_text   = 'Order type'.
    v_text1  = 'Sales Org'.
    v_text2  = 'Distribution channel'.
    v_text3  = 'Division'.
    v_text4  = 'Sold-to'.
    v_text5  = 'Ship-to'.
    v_text6  = 'Material'.
    v_text7  = 'Quantity'.
    v_text9  = 'Plant'.
    v_text10 = 'Complete delivery'.
    Start-of-selection.
    START-OF-SELECTION.
    Header data
    Sales document type
      header-doc_type = p_auart.
      headerx-doc_type = 'X'.
    Sales organization
      header-sales_org = p_vkorg.
      headerx-sales_org = 'X'.
    Distribution channel
      header-distr_chan  = p_vtweg.
      headerx-distr_chan = 'X'.
    Division
      header-division = p_spart.
      headerx-division = 'X'.
      headerx-updateflag = 'I'.
    *Complete delivery
        header-COMPL_DLV = p_autlf.
        header-COMPL_DLV = 'X'.
    Partner data
    Sold to
      partner-partn_role = 'AG'.
      partner-partn_numb = p_sold.
      APPEND partner.
    Ship to
      partner-partn_role = 'WE'.
      partner-partn_numb = p_ship.
      APPEND partner.
    ITEM DATA
      itemx-updateflag = 'I'.
    Line item number.
      item-itm_number = '000010'.
      itemx-itm_number = 'X'.
    Material
      item-material = p_matnr.
      itemx-material = 'X'.
    Plant
      item-plant    = p_plant.
      itemx-plant   = 'X'.
    Quantity
      item-target_qty = p_menge.
      itemx-target_qty = 'X'.
    item category
      itemx-ITEM_CATEG = 'X'.
      APPEND item.
      APPEND itemx.
      ITEM DATA
      itemx-updateflag = 'I'.
    Line item number.
      item-itm_number = '000020'.
      itemx-itm_number = 'X'.
    Material
      item-material = p_matnr.
      itemx-material = 'X'.
    Plant
      item-plant    = p_plant.
      itemx-plant   = 'X'.
    Quantity
      item-target_qty = p_menge.
      itemx-target_qty = 'X'.
      APPEND item.
      APPEND itemx.
      Fill schedule lines
      lt_schedules_in-itm_number = '000010'.
      lt_schedules_in-sched_line = '0001'.
      lt_schedules_in-req_qty    = p_menge.
      APPEND lt_schedules_in.
      Fill schedule line flags
      lt_schedules_inx-itm_number  = '000010'.
      lt_schedules_inx-sched_line  = '0001'.
      lt_schedules_inx-updateflag  = 'X'.
      lt_schedules_inx-req_qty     = 'X'.
      APPEND lt_schedules_inx.
      Fill schedule lines
      lt_schedules_in-itm_number = '000020'.
      lt_schedules_in-sched_line = '0001'.
      lt_schedules_in-req_qty    = p_menge.
      APPEND lt_schedules_in.
      Fill schedule line flags
      lt_schedules_inx-itm_number  = '000020'.
      lt_schedules_inx-sched_line  = '0001'.
      lt_schedules_inx-updateflag  = 'X'.
      lt_schedules_inx-req_qty     = 'X'.
      APPEND lt_schedules_inx.
    Call the BAPI to create the sales order.
      CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
           EXPORTING
                sales_header_in     = header
                sales_header_inx    = headerx
           IMPORTING
                salesdocument_ex    = v_vbeln
           TABLES
                return              = return
                sales_items_in      = item
                sales_items_inx     = itemx
                sales_schedules_in  = lt_schedules_in
                sales_schedules_inx = lt_schedules_inx
                sales_partners      = partner.
    Check the return table.
      LOOP AT return WHERE type = 'E' OR type = 'A'.
        EXIT.
      ENDLOOP.
      IF sy-subrc = 0.
        WRITE: / 'Error in creating document'.
      ELSE.
    Commit the work.
        COMMIT WORK AND WAIT.
        WRITE: / 'Document ', v_vbeln, ' created'.
      ENDIF.

  • Reg: Creation of Table Types

    Hi All,
    I have a small question regaridng the creation of Table type.
    Let us suppose I am creating Table type for a custom table zsample which is having 5 fields. I am generally creating a structure similar to custom table and using that structure as line type for the table type. Let us suppose if there are any changes in the custom table like change in the order of fields or if new fields are added the table type will give dump.
    My question is If I use the custom table itself as a line type, will there be any effect in the performance or some thing or I can go ahead and use it..
    Thanks,
    Ravee

    What dump are you expecting ???
    It is idea behind the creation with reference to get structures and tables which always look like
    the tables they refer to.
    I can not see a possibilty for a dump as long as you create only an internal table.
    A dump could appear, if the internal table is later used to update another db-table. But there it should be clear that the structure of an internal should be created with reference to the tables which they change.
    Siegfried

  • Creation of Document type

    Hi Please guide me about creation of document types for PR/PO.
    If i want to create document type for the capital item as say ZCAP.
    What are the item categories I should select. Also how does the item category affects the document type and further creation of PO/PR?
    What is the significance of linkage PR.?
    Also for creating the new document type we use the NB document type , why? Why do we create new one, cant we use the NB instead of creating new one?
    If any body can explain with example that would be great.
    Warm Regards,
    Bhasker VB.

    <b>Hi Please guide me about creation of document types for PR/PO.</b>
    U can create new non standred document type for PR and Po
    <b>If i want to create document type for the capital item as say ZCAP.
    What are the item categories I should select. Also how does the item category affects the document type and further creation of PO/PR?</b>
    U can create Doc type ZCAP bu coping std Doc type NB or u can creat as your own
    Item categories help system to ask for a relevent data as if u give item category L which is for subcontracting then it will ask for supplied components
    If u say U the it will change venter in to suppling plant and also change relevent things for stock transfer
    <b>Also for creating the new document type we use the NB document type , why? Why do we create new one, cant we use the NB instead of creating new one?</b>
    We can use NB document type for creating new one but ist not compalsory u can directely create your own. We copy so that, all the releating item catagories can be copied.
    we create new one if u want different number range for asset proc and others.
    or if u want to have subcontracting po diffrent form others. etc.
    but there is no relation between Account assig cat and document type.
    hope things r clear
    reward accordingly

  • PROBLEM AT THE TIME OF CREATION OF VALUATION TYPE(SPLIT VALUATION)

    Dear cons
      I want to create a valuation type ( t-code- OMWC) in configuration client. Then I will transport to quality as well as production. but it is a matter of great regret that at the time creation of valuation type no transport request no. is genereted. without TRansport request no. how can I transport to quality as well as production. pl. help me.
    nrk

    Hi,
    This is a client level configuration so Transport Requests are not getting generated directly. Here follow this procedure;
    Go to OMWC, Click on Global types. , Click on Types > Transport in the menu bar
    The sytem will prompt for a request, create the request. A new screen for selcection of Valuation cateogires & valuation types will come. You can select here & transport.
    Click on Save after selection, all the selcted items will be added to the request

  • Definition of a new type of invoice for Evaluated Receipt Settlemen (ERS)

    Hello,
    I need to define a new type of invoice for Evaluated Receipt Settlemen (ERS). Is it possible? What should i do to configure the system?
    Thanks in advance,
    Luis Álvarez.

    Hi,
    ERS is used for invoice plan & invoicing plan for leasing agreements like, aim to considerably reduce the manual data entry effort in the purchasing and invoice verification (A/P) department.
    The invoicing plan enables you to schedule the desired dates for the creation of invoices relating to the planned procurement of materials or services independently of the actual receipt of the goods or actual performance of the services. It list the dates on which you wish to create and then pay the invoices.
    The steps are,
    1.XK02: In Purchasing Data tick the check box of AutoEvalGRSetmt Del,
    2.ME12: Should not select No ERS check box,
    3.ME21N: Create PO,
    4.MIGO: Receive Goods,
    5.MRRL: Evaluated Receipt Settlement
    Link may be useful.
    http://help.sap.com/saphelp_srm30/helpdata/en/fb/8dec38574c2661e10000000a114084/content.htm

  • Yet another case of new type[array] and parametrized type

    I suppose this is an often asked question, to which I seem not to be able to find a simple answer. I know of the "incompatibility" of arrays and generics, and yet in such a seemingly simple case I run into a mystery, or a compiler bug. Look at this warning:
    Set<Integer>  C[];
    foo/bar/some.java:1148: warning: [unchecked] unchecked conversion
    found   : java.util.HashSet[]
    required: java.util.Set<java.lang.Integer>[]
                    C=new HashSet[H-L+1];So far so good, but precisely this *"Set<type>[]"* does not exists, does it? When I try to add a parametrized type to this new statement, compiler says:
    Set<Integer>  C[];
    foo/bar/some.java:1148: generic array creation
                    C=new HashSet<Integer>[H-L+1];
                      ^
    1 errorIn a regular case we can easy deal with the "unchecked" warnings, e.g. Effective Java 2nd Ed, Item 24 discusses this, but all this seem to be ignoring this case. When generic array creation is not permitted, than why this warning stating that *"java.type<typeparam>[] required"* appear, and how to resolve this for safety and correctness? Of course, I can still ignore the warning and do a few instanceof checks and casts, like before, but I am really curious how to transfer this into the new paradigm.
    As much generics improve and help in many cases, I regret their arcane complexity. To paraphrase C.A.R. Hoare, the Java language itself becomes now the problem, not its solution.
    Thomas

    I wonder if we have someplace recent measure just an array stack against a current implementation of a set in Java? In JDK1.4 I remember array was several times faster, 350% faster if my memory serves me, and I do have the classic "inner loop" operation, very repetitive. I can live with the warning, what's the problem?
    Of course all this are considerations fully aside of the issue at hand, that the JDK1.6 compiler prints a nonsense warning message that a parametrized array is expected, what is in fact illegal in current implementation of generics. Which is in my eyes severely faulty, but that would be yet another assault on the Braha Ivory Tower, wouldn't it?
    Thomas

  • Training and event management - create new type of attendee

    Hi all,
    For training and event management, I have to create a new type of attendee besides sap existing attendee type such as company, contact person, customer, external person and so on.
    Via IMG -> Training and event management -> basic settings -> object type modeling enhancement -> object type -> define object types, then how can I define OrgObj Type for new object type I want to create?
    Thanks & regards,
    WCC

    S_AHR_61016216 - Cancellations per Attendee , i think there is no standard report for cencelation of business events, type and group.
    for cancellations per attendee reports is available in the system.
    good luck
    Devi

  • CUP - Issue regarding creation of New SAP ID in CUP.

    System :  SAP GRC 5.3 SP 12..
    We have requirement where in we need to design a workflow for creation of New SAP ID.
    The Naming convention followed for SAP ID is FIRST LETTER of FIRST NAME and LAST NAME with maximum 8 characters.
    For Eg
    JOHN SMITH would have SAP ID as JSMITH
    JERRY SMITH would  have SAP ID as  JSMITH01
    The requirement here is when user fill the REQUEST FORM for NEW User ID there is field where in the requestor need to put the desired SAP ID,
    Can a validation be set OR Logic be written so that user can put the SAP ID as per the naming convention..?
    Also , any other solution as to how the situtation can be handled in CUP...
    Regards.
    Ajit

    Hi Ajit,
    Yes, you can maintain the user ID in the Active Directory. User id will be now auto populated in the request form, from Active Directory when  we data Source is LDAP -Actice directory. So when user login to end user form to create a request, It's all information( user details + manager details ) will fetched from Active Directory.
    It is not possible to change userid in later stage of approval in the request.
    You can have security as final stage and guide them to create user manually as per naming convention.
    Make auto provisioning OFF in CUP
    Kind Regards,
    Srinivasan

  • Error in creation of Object Type from XML passed

    Hi,
    I am facing a problem creating a appropriate a object type for a XML.
    Below are the details:
    XML Passed
    <mer_offer_action_data>
    <form_id>
    134039588
    </form_id>
    <action_cd>
    OA
    </action_cd>
    <offer_decline_reason_cd>
    </offer_decline_reason_cd>
    <start_dt>
    </start_dt>
    <candidate>
    <ds_prs_id>
    109315
    </ds_prs_id>
    <ds_prs_id>
    110534
    </ds_prs_id>
    <ds_prs_id>
    110059
    </ds_prs_id>
    </candidate>
    </mer_offer_action_data>
    Types Declaration
    +CREATE OR REPLACE type MER_OFF_CANDIDATE
    AS
    OBJECT
    DS_PRS_ID NUMBER
    CREATE OR REPLACE TYPE MER_OFF_CANDIDATE_t
    AS
    TABLE OF MER_OFF_CANDIDATE;
    CREATE OR REPLACE type MER_OFFER_ACT_DATA
    AS
    OBJECT
    FORM_ID NUMBER,
    ACTION_CD VARCHAR2(6),
    OFFER_DECLINE_REASON_CD VARCHAR2(6),
    START_DT VARCHAR2(11),
    CANDIDATE MER_OFF_CANDIDATE_t
    CREATE OR REPLACE TYPE MER_OFFER_ACT_DATA_t
    AS
    TABLE OF MER_OFFER_ACT_DATA;
    CREATE OR REPLACE type MER_OFFER_ACTION_DATA
    AS
    OBJECT
    MER_OFF_ACT_DATA MER_OFFER_ACT_DATA_t
    /+
    My Declaration
    +merOffActDataXML      xmltype;
    merOffActData     MER_OFFER_ACTION_DATA := MER_OFFER_ACTION_DATA(MER_OFFER_ACT_DATA_t());+
    Inside Pl/SQL block
    +-- Converts XML data into user defined type for further processing of data
    xmltype.toobject(merOffActDataXML,merOffActData);+
    when I run the Pl/Sql block it gives me error
    ORA-19031: XML element or attribute FORM_ID does not match any in type ORADBA.MER_OFFER_ACTION_DATA
    which means the object type mapping is wrong
    I would like to know whether the object type I had created is correct or not.
    Thanks for your help
    Beda

    Bedabrata Patel wrote:
    Below are the details:The details except for a description of the problem
    I am facing a problem creating a appropriate a object type for a XML.And which error you are getting
    Error in creation of Object Type http://download.oracle.com/docs/cd/E11882_01/server.112/e10880/toc.htm
    And which version of Oracle you are getting the unknown error creating the unknown problem.

Maybe you are looking for

  • HELP NEEDED ,Syntax Error.

    Whenever i try to execute the following program, i get the following syntax error. "ALPHA AND IT-F1 ARE TYPE-INCOMPATIBLE." data: begin of it occurs 12,           f1,           end of it,           alpha(12) value 'ABCDEFGHIJKL'. do 12 times varying

  • Follow up of activities from old opportunity to new opportunity

    Hi Team members, I want to create a new opportunity for a customer, but the activities from the earlier opportunity (of the same customer) should get displayed in the new opportunity Please let me know the steps or hints Thank you and kindest regards

  • My mac is not showing up in manage my devices

    My mac says it is authorized but it doesn't show my itunes library and doesn't show in manage my devices.  Anyone have an answer?

  • EDI Error Supressing

    We have a need to generate 997 Functional Ack for 856 inbound with AK5 status as E (Accepted with Error) instead of R (Rejected) for some data Error codes in (ST & SE segments only ) . To make this work ,we modified the SeverityConfig.xml file for ED

  • Read Simple container element

    Hi, I have implemented the SAP_WAPI_READ_CONTAINER module function in Java Web Dynpro. This module function retreive information stored in a workflow container. In my view, I have mapped the simple container context element to a table and I can see t